[go: up one dir, main page]

CN101808308B - Attribution assigned user server addressing method, device and system - Google Patents

Attribution assigned user server addressing method, device and system Download PDF

Info

Publication number
CN101808308B
CN101808308B CN2009100773418A CN200910077341A CN101808308B CN 101808308 B CN101808308 B CN 101808308B CN 2009100773418 A CN2009100773418 A CN 2009100773418A CN 200910077341 A CN200910077341 A CN 200910077341A CN 101808308 B CN101808308 B CN 101808308B
Authority
CN
China
Prior art keywords
user
imsi
identification information
attribution assigned
hss
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CN2009100773418A
Other languages
Chinese (zh)
Other versions
CN101808308A (en
Inventor
闫学霞
时书锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN2009100773418A priority Critical patent/CN101808308B/en
Publication of CN101808308A publication Critical patent/CN101808308A/en
Application granted granted Critical
Publication of CN101808308B publication Critical patent/CN101808308B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a technical scheme of attribution assigned user server addressing method, device and system. The attribution assigned user server addressing method comprises the following steps of: acquiring an MCC (Motor Control Center), an MNC (Mobile Network Code) and the identification information of an attribution assigned user server of a user from the IMSI (International Mobile Subscriber Identification) of the user by a mobile management network element, generating a domain name by utilizing the MCC, the MNC and the identification information of the attribution assigned user server of the user by the mobile management network element, and enquiring the domain name on an enquiry server and acquiring the routing information of the attribution assigned user server corresponding to the domain name by the mobile management network element. In the technical scheme, by utilizing the domain name generated by the MCC, the MNC and the identification information of the attribution assigned user server, the mobile management network element can address the attribution assigned user server of a user attribution domain.

Description

Attribution assigned user server addressing method, device and system
Technical field
The present invention relates to the network communications technology field, be specifically related to attribution assigned user server addressing method, attribution assigned user server addressing device and attribution assigned user server addressing system.
Background technology
(mobile management network element MME) is logic function body in the core net of wireless evolution network to Mobility Management Entity.MME mainly is responsible for the mobile management to the user, to the encryption and the protection of NAS (Non-Access Stratum) signaling, and realizes functions such as roaming and tracking; MME can also distribute the temporary identity sign for the user, realizes safety function etc.
In processes such as user's registration; Because MME need be to the Home of user attaching Subscriber Server (attribution assigned user server; HSS) request authorization data and user contracting data etc.; Therefore, MME needs the HSS of addressed user ownership, above-mentioned request is routed to the HSS place of user attaching.At present, the method for the HSS of MME addressed user ownership mainly contains following two kinds:
Method one, MME are from user's International Mobile Subscriber Identification Number (international mobile subscriber identity; IMSI) obtain Mobile Country Code MCC MCC and mobile network No. MNC in, and the domain name of utilizing MCC and MNC to form is carried out route to request.
Method two, MME obtain MCC and MNC from user's IMSI; And according to MCC and MNC through to the Subscriber of user attaching Location Function (signatory position functions; SLF) inquiry obtains the routing iinformation of the HSS of user attaching, and according to this routing iinformation route is carried out in request; Perhaps MME will ask route to give SLF, by SLF route proceeded in this request.
In realizing process of the present invention, the inventor finds: method one can only route requests to user's home domain, can not route requests to the HSS in user attaching territory; Method two need be in SLF maintenance customer's the corresponding relation of routing iinformation of IMSI and HSS identification information and HSS, open an account the user, when operation such as cancellation causes CAMEL-Subscription-Information to change, the corresponding relation of safeguarding among the SLF should carry out Synchronous Processing.
Summary of the invention
Embodiment of the present invention provides attribution assigned user server addressing method, device and system, can be addressed to the attribution assigned user server in user attaching territory through domain name.
The attribution assigned user server addressing method that embodiment of the present invention provides comprises:
Mobile management network element obtains said user's Mobile Country Code MCC MCC, mobile network No. MNC and attribution assigned user server identification information from user's international mobile subscriber identity IMSI;
Said mobile management network element utilizes said user's MCC, MNC and attribution assigned user server identification information to generate domain name;
Said mobile management network element passes through to obtain to the querying server inquiry routing iinformation of the corresponding attribution assigned user server of domain name according to domain name.
The attribution assigned user server addressing device that embodiment of the present invention provides comprises:
Acquisition module is used for obtaining from user's IMSI said user's MCC, MNC and attribution assigned user server identification information;
The domain name module is used to utilize the user's that said acquisition module obtains MCC, MNC and attribution assigned user server identification information to generate domain name;
Addressed module is used for inquiring about to querying server according to the domain name that the domain name module generates, and obtains the routing iinformation of the corresponding attribution assigned user server of domain name.
The attribution assigned user server addressing system that embodiment of the present invention provides comprises:
Mobile management network element; Be used for obtaining said user's MCC, MNC and attribution assigned user server identification information from user's IMSI; Utilize said user's MCC, MNC and attribution assigned user server identification information to generate domain name, and send the query requests that carries domain name;
Querying server is used for confirming according to the domain name that query requests is carried the routing iinformation of user's attribution assigned user server, and returns the inquiry response that carries said routing iinformation to said mobile management network element.
Description through technique scheme can be known; Through utilizing MCC, MNC and attribution assigned user server identification information to generate domain name; And utilize this domain name to inquire about; Can obtain the routing iinformation of user's attribution assigned user server, thereby make mobile management network element can be addressed to user's attribution assigned user server.
Description of drawings
Fig. 1 is the attribution assigned user server addressing method flow chart of the embodiment of the invention one;
Fig. 2 is the attribution assigned user server addressing method flow chart of the embodiment of the invention two;
Fig. 3 is the attribution assigned user server addressing method flow chart of the embodiment of the invention three;
Fig. 4 is the IMSI structural representation of the embodiment of the invention four;
Fig. 5 is the MSIN structural representation of the embodiment of the invention four;
Fig. 6 is the attribution assigned user server addressing method flow chart of the embodiment of the invention four;
Fig. 7 is the attribution assigned user server addressing apparatus structure sketch map of the embodiment of the invention five;
Fig. 7 a, b, c and d are the acquisition module structural representations of the embodiment of the invention five;
Fig. 8 is the network equipment structural representation of the embodiment of the invention six;
Fig. 9 is the attribution assigned user server addressing system schematic of this embodiment seven.
Embodiment
The inventor finds in realizing process of the present invention: the identification information that can carry the HSS of user attaching among user's the IMSI; If utilize user's MNC, MCC and HSS identification information to generate domain name; Then through carrying out inquiries such as DNS; Can make MME obtain the routing iinformation of the HSS of user attaching, thereby can make MME be addressed to the HSS of user attaching.
Below in conjunction with accompanying drawing various embodiments of the present invention are described.
Embodiment one, attribution assigned user server addressing method.The flow process of this method is shown in accompanying drawing 1.
Among Fig. 1, step 100, MME obtain this user's MCC, MNC and HSS identification information from user's IMSI.
MME is when obtaining the HSS identification information from user's IMSI; Can from IMSI, obtain the HSS identification information according to the particular location of HSS identification information in user's IMSI; Be that MME should know the positional information of HSS identification information in user's IMSI; Afterwards, MME can get access to the HSS identification information exactly according to this positional information from IMSI.
It is multiple that MME knows that the mode of the positional information of HSS identification information in user's IMSI has, and introduces the mode that three kinds of MME are known the positional information of HSS identification information in user's IMSI below.
Mode one, know the positional information of HSS identification information in user's IMSI according to configuration information.
Among the MME stored configuration information can for: at least one type of IMSI information and HSS are identified at the corresponding relation between the positional information among the IMSI.The corresponding relation here can show as number section of IMSI and the corresponding relation between the positional information; A few positions that also can show as among one type of IMSI information and such IMSI are the corresponding relation of HSS identification information, and above-mentioned corresponding relation also can show as other form.When MME confirms the HSS identification information of certain user's correspondence at needs; Should confirm earlier which kind of IMSI this user's IMSI belongs to; Then, from above-mentioned corresponding relation, search the corresponding HSS of that type IMSI that this user's IMSI belongs to again and be identified at the positional information among the IMSI.Need to prove that stored relation can be configured according to signed roaming agreement among the MME.
Mode two, the message (being user's notice) of sending according to the user are known the positional information of HSS identification information in user's IMSI.
The user sends the message that carries the positional information among the IMSI of HSS identification information the user to MME, and this message can be existing message, also can be to be the newly-increased message of notice positional information specially.When utilizing existing message to carry above-mentioned positional information, should expand this existing message to positional information.For example; When existing message is attach request; Can expand the Administrative Data among the USIM (universal subscriber identity module) of attach request to positional information, so that above-mentioned positional information is carried among the Administrative Data.MME from the information that message is carried, obtain positional information, thereby MME is known the position of HSS identification information in user's IMSI after receiving the message that carries positional information that the user sends.Above-mentioned positional information also can be carried in other field among the USIM.
Mode three, determine the positional information of HSS identification information in user's IMSI according to the regulation of standard.
If the equal adherence to standard of the structure of each user's IMSI, and in the standard position of the HSS identification information among the IMSI is stipulated that then MME can be known the positional information of HSS identification information in user's IMSI according to standard.
Above-mentioned three kinds of modes are only given an example and have been explained that MME knows that HSS is identified at the different implementation procedures of the positional information among user's the IMSI; MME also can adopt alternate manner to know above-mentioned positional information, and the embodiment of the invention does not limit the concrete implementation procedure that MME is known above-mentioned positional information.In addition, above-mentioned positional information can be start position information and end position information; Also can be start position information and length information; Can also be end position information and length information or the like.The embodiment of the invention does not limit the concrete manifestation form of above-mentioned positional information.
After MME had been known the positional information among the IMSI of HSS identification information the user, MME can obtain corresponding numeral according to this positional information from user's IMSI, and this corresponding numeral of obtaining is the HSS identification information.MME can adopt existing method from user's IMSI, to obtain MCC and MNC, and MME obtains MCC and MNC from user's IMSI detailed process no longer specifies at this.
In addition, MME also can adopt except that other method of from IMSI, obtaining the HSS identification information according to positional information of above-mentioned introduction and from IMSI, obtain the HSS identification information.For example; MME can store a plurality of HSS identification informations in advance; MME is in the time need obtaining the HSS identification information from user's IMSI; With the HSS identification information of its storage one by one with user's IMSI in pre-determined bit numeral or pre-determined bit bit mate, perhaps during the pre-determined bit bits match, this HSS identification information is user's HSS identification information to the pre-determined bit numeral in the HSS of certain storage identification information and user's IMSI.Above-mentioned pre-determined bit numeral or pre-determined bit bit comprise: numeral or bit among the IMSI except that MCC and MNC.The figure place of pre-determined bit numeral or pre-determined bit bit can be more than or equal to the digit order number or the bit of HSS identification information.
Step 110, MME utilize this user's MCC, MNC and HSS identification information to generate domain name.
The domain name that the embodiment of the invention generates includes MCC, MNC and HSS identification information.The embodiment of the invention does not limit MCC, MNC and the HSS identification information sequencing in domain name and the concrete form of domain name.An object lesson of form that includes the domain name of MCC, MNC and HSS identification information is:
epc.hss<HSS>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
Step 120, MME inquire about to querying server according to the domain name of above-mentioned generation, and from Query Result, obtain the routing iinformation of the corresponding HSS of the domain name of above-mentioned generation.
MME sends the query requests that carries domain name to querying server; Querying server obtains domain-name information from the query requests that receives; Querying server is searched the routing iinformation with the HSS of this domain name coupling in the canned data in advance at it, and the routing iinformation of the HSS of the coupling that will find is carried in the response message of successful inquiring and returns to MME.MME obtains the routing iinformation of HSS from the response message that receives.In addition; If querying server according to its in advance canned data do not find the routing iinformation of the HSS of this domain name coupling; Then querying server can distribute a HSS for this domain name according to strategy, and returns the routing iinformation of the HSS of this distribution to MME through response message.When the routing iinformation of the HSS that does not find this domain name coupling, querying server also can return the response message of inquiry failure to MME.Above-mentioned querying server can be domain name system server DNS, also can be routing table server or other server.The routing table server here can be arranged among the MME, also can close with other network equipment in the network and establish, and certainly, the routing table server also can be independent of the network equipment in the network and be provided with separately.
Can find out from the description of the foregoing description one; MME generates domain name through utilizing MCC, MNC and HSS identification information; And utilize this domain name to inquire about to querying server, make MME can obtain the routing iinformation of the HSS of user attaching, thereby make MME can be addressed to the HSS of user attaching.MME can utilize multiple mode from IMSI, to obtain user's HSS identification information; Can also utilize multiple mode to know the position of HSS identification information in user's IMSI; Facilitate the use this position obtains the user from IMSI HSS identification information, thereby can select diverse ways to realize the HSS addressing according to concrete network environment.Through routing iinformation, avoided the Synchronous Processing problem of additional maintenance corresponding relation in SLF to the HSS of DNS or routing table server lookup user attaching.
Embodiment two, based on the attribution assigned user server addressing method that from the attach request that the user sends, obtains positional information.The flow process of this method is shown in accompanying drawing 2.
Among Fig. 2, step 1, UE send attach request (attach request, i.e. RAUrequest among Fig. 2) message to MME.Carry HSS ID indication information in this attach request message.HSS ID indication information includes the positional information of HSS identification information in user's IMSI.Above-mentioned HSS ID indication information can have multiple expression mode; As to utilize which bit or which digit order number among the IMSI that indicating bit representes to carry in the Attach Request message be the HSS identification information, and a kind of saying that is equal to of the implication that this indicating bit is represented is: which bit in the expression Attach Request message perhaps which digit order number is the HSS identification information.
After step 2, MME receive attach request message; From attach request message, obtain the HSSID indication information; MME obtains MCC and MNC from IMSI; And utilize HSS ID indication information to obtain the HSS id information from corresponding bits position or this digit order number of IMSI, then, MME utilizes MCC, MNC and HSS id information according to epc.hss < HSS>.mnc < MNC>.mcc < MCC>.3gppnetwork.org form structure domain name.
An object lesson of structure domain name is: the IMSI that sets the user is 234560888866666, wherein: MCC=234, MNC=56, HLR=8888 and ID=666666; Then MME according to the domain name that above-mentioned form constructs is: epc.hlr888.mnc056.mcc234.3gppnetwork.org.
Step 3, MME utilize domain name that step 2 constructs to DNS or routing table server lookup, and promptly MME sends the query requests that carries the domain-name information that step 2 constructs to DNS or routing table server.
Step 4, DNS or routing table server obtain domain-name information from query requests, and determine the corresponding Query Result of this domain name, and this Query Result can be the routing iinformation of HSS such as HSS address information.Then, DNS or routing table server return to MME with Query Result through inquiry response.
Step 5, MME receive inquiry response, and send diameter message, this diameter message such as AIR (authentication request) message or ULR (position updating request) message etc. according to the routing iinformation of the HSS in the inquiry response to HSS.
Step 6, HSS handle this request message, and return corresponding message according to result to MME after receiving the request message of MME transmission, as send AIA (Authentication Response) message or ULA (response is upgraded in the position) message to MME.
Step 7, MME return RAU response (RAU response) to UE after receiving AIA message or ULA message.
Embodiment three, obtain the attribution assigned user server addressing method of positional information based on pre-configured information.In this embodiment; Be provided with the corresponding relation of at least one type of IMSI and the positional information of HSS identification information in user's IMSI among the MME in advance; For example; MME can dispose start position information and the length information of the HSS ID among at least one type of IMSI according to signing the roaming agreement that belongs between the operator.The method flow of this embodiment is shown in accompanying drawing 3.
Among Fig. 3, step 1, UE send attach request message (being the RAU request among Fig. 3) to MME.HSS ID indication information can be carried in this attach request message, also HSS ID indication information can be do not carried in this attach request message.
Step 2, MME are after receiving attach request message; Confirm user's the affiliated IMSI class of IMSI; And utilize this corresponding relation to determine user's affiliated corresponding start position information and the length information of IMSI class of IMSI; Afterwards; MME obtains the HSS id information according to start position information and the length information corresponding bits position from IMSI determined, and then, MME utilizes MCC, MNC and HSS id information according to epc.hss < HSS>.mnc < MNC>.mcc < MCC>.3gppnetwork.org form structure domain name.The object lesson of structure domain name such as the description of above-mentioned embodiment two are in this no longer repeat specification.
Step 3, MME utilize domain name that step 2 constructs to DNS or routing table server lookup, and promptly MME sends the query requests that carries the domain-name information that step 2 constructs to DNS or routing table server.
Step 4, DNS or routing table server obtain domain-name information from query requests, and determine the corresponding Query Result of this domain name, and this Query Result can be the routing iinformation of HSS such as HSS address information.Then, DNS or routing table server return to MME with Query Result through inquiry response.
Step 5, MME receive inquiry response, and send diameter message, this diameter message such as AIR message or ULR message etc. according to the routing iinformation of the HSS in the inquiry response to HSS.
Step 6, HSS handle this request message, and return corresponding message according to result to MME after receiving the request message of MME transmission, as sending AIA message or ULA message to MME.
Step 7, MME return RAU response to UE after receiving AIA message or ULA message.
Embodiment four, based on the attribution assigned user server addressing method of standard code position.
In this embodiment four, the IMSI structure of standard code can be like accompanying drawing 4 with shown in Figure 5.
Can know that from Fig. 4 IMSI comprises MCC, MNC and MSIN, wherein, MNC comprises 3 numerals, and MNC comprises 2 or 3 numerals, and MSIN comprises 10 or 9 numerals, and IMSI is no more than 15 numerals.In addition, MNC and MSIN can close and be called NMSI (National Mobile Subscriber Identity).
Stipulated in the standard that MSIN includes the HSS id information, and need in standard, stipulate original position and the length of HSS ID in MSIN.The structure of the MSIN of standard code can be shown in accompanying drawing 5.
Fig. 5 has disclosed two kinds of MSIN, and in the MSIN on Fig. 5 left side, HSS ID is preceding, ID after; In the MSIN on Fig. 5 the right, HSS ID after, ID is preceding.HSS ID among two kinds of MSIN that Fig. 5 discloses is 3 or 4 numerals and ID is 5 or 6 numerals.The structure of the MSIN of standard code can be not limited to the dual mode that Fig. 5 gives an example.
Fig. 4 and IMSI and MSIN shown in Figure 5 only are the explanations of giving an example, and IMSI that stipulates in the standard and MSIN also can be other form.In standard HSS ID has been carried out under the situation of regulation, each user's IMSI form all should be observed this regulation.At this moment, the method flow of embodiment four is shown in accompanying drawing 6.
Among Fig. 6, step 1, UE send attach request message (being the RAU request among Fig. 6) to MME.HSS ID indication information can be carried in this attach request message, also HSS ID indication information can be do not carried in this attach request message.
Step 2, MME are after receiving attach request message; Regulation according to standard is directly obtained MCC, MNC and HSS id information from corresponding bit position or the digit order number of user's IMSI; Then, MME utilizes the above-mentioned MCC that obtains, MNC and HSS id information structure domain name according to epc.hss < HSS>.mnc < MNC>.mcc < MCC>.3gppnetwork.org form.The object lesson of structure domain name such as the description of above-mentioned embodiment two are in this no longer repeat specification.
What be worth explanation is; In Fig. 6 step 2 from the corresponding bit position of user's IMSI or a kind of saying that is equal to that digit order number is directly obtained MCC, MNC and HSS id information be: MME directly obtains MCC, MNC and HSS id information according to the corresponding bit position or the digit order number of regulation from attach request message of standard after receiving attach request message.
Step 3, MME utilize domain name that step 2 constructs to DNS or routing table server lookup, and promptly MME sends the query requests that carries the domain-name information that step 2 constructs to DNS or routing table server.
Step 4, DNS or routing table server obtain domain-name information from query requests, and determine the corresponding Query Result of this domain name, and this Query Result can be the routing iinformation of HSS such as HSS address information.Then, DNS or routing table server return to MME with Query Result through inquiry response.
Step 5, MME receive inquiry response, and send diameter message, this diameter message such as AIR message or ULR message etc. according to the routing iinformation of the HSS in the inquiry response to HSS.
Step 6, HSS handle this request message, and return corresponding message according to result to MME after receiving the request message of MME transmission, as sending AIA message or ULA message to MME.
Step 7, MME return RAU response to UE after receiving AIA message or ULA message.
Embodiment five, attribution assigned user server addressing device.This device is shown in accompanying drawing 7.
Device among Fig. 7 comprises: acquisition module 700, domain name module 710 and addressed module 720.
Acquisition module 700 obtains said user's MCC, MNC and attribution assigned user server identification information from user's IMSI.
Acquisition module 700 is when obtaining the HSS identification information from user's IMSI; Can from IMSI, obtain the HSS identification information according to the particular location of HSS identification information in user's IMSI; At this moment; Acquisition module 700 should be known the positional information of HSS identification information in user's IMSI, and afterwards, acquisition module 700 can get access to the HSS identification information according to this positional information from IMSI.Acquisition module 700 can adopt existing method from user's IMSI, to obtain MCC and MNC.It is multiple that acquisition module 700 knows that the mode of the positional information of HSS identification information in user's IMSI has, concrete like the description among the above-mentioned method embodiment, in this no longer repeat specification.
In addition, acquisition module 700 also can adopt except that other method of from IMSI, obtaining the HSS identification information according to positional information of above-mentioned introduction and from IMSI, obtain the HSS identification information.For example; Acquisition module 700 can be stored a plurality of HSS identification informations in advance; MME is in the time need obtaining the HSS identification information from user's IMSI; With the HSS identification information of its storage one by one with user's IMSI in predetermined bit position or digit order number mate, when predetermined bit position in the HSS of certain storage identification information and user's IMSI or digit order number coupling, this HSS identification information is user's HSS identification information.Above-mentioned predetermined bit position or digit order number are meant bit except that MCC and MNC or digit order number among the IMSI.Concrete like the description among the above-mentioned method embodiment, in this no longer repeat specification.
Domain name module 710 utilizes the user's that acquisition module 700 obtains MCC, MNC and attribution assigned user server identification information to generate domain name.An object lesson of the form of the domain name that includes MCC, MNC and HSS identification information that domain name module 710 generates is:
epc.hss<HSS>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
Addressed module 720 is inquired about to querying server according to the domain name that domain name module 710 generates, and obtains the routing iinformation of the corresponding attribution assigned user server of domain name.
Addressed module 720 can be sent the query requests that carries domain name to querying server; Querying server obtains domain-name information from the query requests that receives; Querying server is searched the routing iinformation with the HSS of this domain name coupling in the canned data in advance at it, and the routing iinformation of the HSS of the coupling that will find is carried in the response message of successful inquiring and returns to MME.Addressed module 720 is obtained the routing iinformation of HSS from the response message that MME receives.In addition; If querying server according to its in advance canned data do not find the routing iinformation of the HSS of this domain name coupling; Then querying server can distribute a HSS for this domain name according to strategy, and returns the routing iinformation of the HSS of this distribution to MME through response message.
Above-mentioned querying server can be domain name system server DNS, also can be routing table server or other server.
An object lesson of the concrete structure of acquisition module 700 is shown in accompanying drawing 7a.
Among Fig. 7 a, acquisition module 700 comprises: first sub module stored 701 and first is obtained submodule 702.
Store configuration information in first sub module stored 701, this configuration information can be the positional information of HSS ID in IMSI that at least one type of IMSI is corresponding.The corresponding relation here can show as number section of IMSI and the corresponding relation between the positional information; Some position (bit or digit order number) that also can show as among one type of IMSI information and such IMSI is the corresponding relation of HSS identification information, and above-mentioned corresponding relation also can show as other form.Need to prove that stored relation can be configured according to signed roaming agreement in first sub module stored 701.
First obtains submodule 702 when confirming the HSS identification information of certain user's correspondence; Should confirm earlier which kind of IMSI this user's IMSI belongs to; Then, first obtain submodule 702 and from the above-mentioned corresponding relation of first sub module stored 701 storage, search the corresponding HSS of that type IMSI that this user's IMSI belongs to again and be identified at the positional information among the IMSI.
Another object lesson of the concrete structure of acquisition module 700 is shown in accompanying drawing 7b.
Among Fig. 7 b, acquisition module 700 comprises: position submodule 703 and second obtains submodule 704.
Position submodule 703 obtains attribution assigned user server and is identified at the positional information among the IMSI from the message that the user sends.Be that the user carries the positional information among the IMSI of HSS identification information the user in the message that MME sends.This message can be existing message, also can be to be the newly-increased message of notice positional information specially.When utilizing existing message to carry above-mentioned positional information, should expand this existing message to positional information.For example, when existing message is attach request, can expand the Administrative Data among the USIM of attach request to positional information, so that above-mentioned positional information is carried among the Administrative Data.
Second obtains the HSS id information that the relevant position of positional information from user's IMSI that submodule 704 obtains according to position submodule 703 obtains the user.
Another object lesson of the concrete structure of acquisition module 700 is shown in accompanying drawing 7c.
Acquisition module 700 among Fig. 7 c comprises: the 3rd obtains submodule 705.
If the equal adherence to standard of the structure of each user's IMSI, and in the standard position of the HSS identification information among the IMSI is stipulated, then the 3rd obtain submodule 705 obtains the user from said user's IMSI according to the position of stipulating in the standard HSS id information.
Another object lesson of the concrete structure of acquisition module 700 is shown in accompanying drawing 7d.
Acquisition module 700 among Fig. 7 d comprises: second sub module stored 706 and matched sub-block 707.
Store a plurality of attribution assigned user server identification informations in second sub module stored 706.
Matched sub-block 707 is in the time need obtaining the HSS identification information from user's IMSI; With the HSS identification information of second sub module stored 706 storage one by one with user's IMSI in pre-determined bit (bit or digit order number) mate; When the pre-determined bit in the HSS of certain storage identification information and user's IMSI was mated, matched sub-block 707 was confirmed as this HSS identification information user's HSS identification information.
Above-mentioned pre-determined bit comprises: digit order number among the IMSI except that MCC and MNC or bit.In addition, the digit of pre-determined bit or number of bits can also can equal the digit or the number of bits of HSS id information greater than the digit or the number of bits of HSS id information.For example; The digit of pre-determined bit is 9; And the HSS id information of storage is 3 numerals in second sub module stored 706; At this moment, when preceding 3 numerals of certain HSS id information that matched sub-block 707 is stored in determining second sub module stored 706 and pre-determined bit or back 3 numeral couplings, then matched sub-block 707 is confirmed as this HSS id information of storage in second sub module stored 706 user's HSS id information.
Embodiment six, the network equipment are the mobile management network element in the network.The structure of this network equipment is shown in accompanying drawing 8.
The network equipment among Fig. 8 comprises: acquisition module 800, domain name module 810 and addressed module 820.
Acquisition module 800 obtains said user's MCC, MNC and attribution assigned user server identification information from user's IMSI.
Acquisition module 800 is when obtaining the HSS identification information from user's IMSI; Can from IMSI, obtain the HSS identification information according to the particular location of HSS identification information in user's IMSI; Be that acquisition module 800 should be known the positional information of HSS identification information in user's IMSI; Afterwards, acquisition module 800 can get access to the HSS identification information according to this positional information from IMSI.Acquisition module 800 can adopt existing method from user's IMSI, to obtain MCC and MNC.It is multiple that acquisition module 800 knows that the mode of the positional information of HSS identification information in user's IMSI has, concrete like the description among the above-mentioned method embodiment, in this no longer repeat specification.
In addition, acquisition module 800 also can adopt except that other method of from IMSI, obtaining the HSS identification information according to positional information of above-mentioned introduction and from IMSI, obtain the HSS identification information.For example; Acquisition module 800 can be stored a plurality of HSS identification informations in advance; MME is in the time need obtaining the HSS identification information from user's IMSI; With the HSS identification information of its storage one by one with user's IMSI in pre-determined bit (bit or digit order number) mate, during pre-determined bit coupling in the HSS of certain storage identification information and user's IMSI, this HSS identification information is user's HSS identification information.Above-mentioned pre-determined bit is meant bit except that MCC and MNC or digit order number among the IMSI.Concrete like the description among the above-mentioned method embodiment, in this no longer repeat specification.
Domain name module 810 utilizes the user's that acquisition module 800 obtains MCC, MNC and attribution assigned user server identification information to generate domain name.An object lesson of the form of the domain name that includes MCC, MNC and HSS identification information that domain name module 810 generates is:
epc.hss<HSS>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
Addressed module 820 is inquired about to querying server according to the domain name that domain name module 810 generates, and obtains the routing iinformation of the corresponding attribution assigned user server of domain name.
Addressed module 820 can be sent the query requests that carries domain name to querying server; Querying server obtains domain-name information from the query requests that receives; Querying server is searched the routing iinformation with the HSS of this domain name coupling in the canned data in advance at it, and the routing iinformation of the HSS of the coupling that will find is carried in the response message of successful inquiring and returns to MME.Addressed module 820 is obtained the routing iinformation of HSS from the response message that MME receives.In addition; If querying server according to its in advance canned data do not find the routing iinformation of the HSS of this domain name coupling; Then querying server can distribute a HSS for this domain name according to strategy, and returns the routing iinformation of the HSS of this distribution to MME through response message.Above-mentioned querying server can be domain name system server DNS, also can be routing table server or other server.
Be directed against the description of Fig. 7 a, b, c, d among the concrete structure of acquisition module 800 such as the above-mentioned embodiment five, in this no longer repeat specification.
Embodiment seven, attribution assigned user server addressing system.The structure of this system is shown in accompanying drawing 9.
System shown in Figure 9 comprises: MME900 and querying server 910.Though only show a MME900 among Fig. 9,, the quantity of MME900 can be at least one in practical application.
MME900 obtains user's MCC, MNC and attribution assigned user server identification information from user's IMSI; Utilize user's MCC, MNC and HSS identification information to generate domain name, and send the inquiry request message that carries above-mentioned domain name to querying server 910.Description among the structure of MME900 such as above-mentioned embodiment five and the embodiment six is in this no longer repeat specification.
Querying server 910 receives inquiry request message; From the information that inquiry request message carries, obtain domain name; Querying server 910 is searched the routing iinformation with the HSS of this domain name coupling in the canned data in advance at it, and the routing iinformation of the HSS of the coupling that will find is carried in the response message of successful inquiring and returns to MME900.In addition; If querying server 910 according to its in advance canned data do not find the routing iinformation of the HSS of this domain name coupling; Then querying server 910 can distribute a HSS for this domain name according to strategy, and returns the routing iinformation of the HSS of this distribution to MME900 through response message.When the routing iinformation of the HSS that does not find this domain name coupling, querying server 910 also can return the response message of inquiry failure to MME900.Above-mentioned querying server 910 can be domain name system server DNS, also can be routing table server or other server.
MME900 obtains the routing iinformation of HSS from the response message that receives.This routing iinformation is used for MME900 to HSS request user's authorization data and user contracting data etc.
Description through above execution mode; Those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential hardware platform; Can certainly all implement, but the former is better execution mode under a lot of situation through hardware.Based on such understanding; All or part of can the coming out that technical scheme of the present invention contributes to background technology with the embodied of software product; This computer software product can be stored in the storage medium, like ROM/RAM, magnetic disc, CD etc., comprises that some instructions are with so that a computer equipment (can be a personal computer; Server, the perhaps network equipment etc.) carry out the described method of some part of each embodiment of the present invention or embodiment.
Though described the present invention through embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, and the claim of application documents of the present invention comprises these distortion and variation.

Claims (13)

1. an attribution assigned user server addressing method is characterized in that, comprising:
Mobile management network element obtains said user's Mobile Country Code MCC MCC, mobile network No. MNC and attribution assigned user server identification information from user's international mobile subscriber identity IMSI;
Said mobile management network element utilizes said user's MCC, MNC and attribution assigned user server identification information to generate domain name;
Said mobile management network element passes through to obtain to the querying server inquiry routing iinformation of the corresponding attribution assigned user server of domain name according to domain name.
2. the method for claim 1; It is characterized in that; Disposes the corresponding attribution assigned user server of at least one type of IMSI in the said mobile management network element and be identified at the positional information among the IMSI, and said mobile management network element obtains said user from user's IMSI attribution assigned user server identification information comprises:
Said mobile management network element confirms that according to said information configured the relevant position from user's IMSI obtains user's attribution assigned user server identification information.
3. the method for claim 1 is characterized in that, said mobile management network element obtains said user from user's IMSI attribution assigned user server identification information comprises:
Said mobile management network element obtains attribution assigned user server and is identified at the positional information among the IMSI from the message that the user sends, and obtains said user's attribution assigned user server identification information according to the relevant position of said positional information from said user's IMSI.
4. method as claimed in claim 3 is characterized in that, the message that said user sends comprises: the attach request that the user sends to mobile management network element through the Non-Access Stratum NAS interface between user and the mobile management network element.
5. method as claimed in claim 4 is characterized in that, said attribution assigned user server is identified in the management data of universal subscriber identity module USIM that positional information among the IMSI is carried at said attach request.
6. the method for claim 1 is characterized in that, said mobile management network element obtains said user from user's IMSI attribution assigned user server identification information comprises:
Said mobile management network element obtains said user's attribution assigned user server identification information from said user's IMSI according to the position of stipulating in the standard.
7. the method for claim 1; It is characterized in that; Store a plurality of attribution assigned user server identification informations in the said mobile management network element, and said mobile management network element obtains said user from user's IMSI attribution assigned user server identification information comprises:
Said mobile management network element matees the pre-determined bit among the attribution assigned user server identification information of its storage and user's the IMSI, and will with the attribution assigned user server identification information of pre-determined bit coupling attribution assigned user server identification information as said user;
Said pre-determined bit comprises: the position among the IMSI except that MCC and MNC, and the figure place of said pre-determined bit is more than or equal to the figure place of attribution assigned user server identification information.
8. an attribution assigned user server addressing device is characterized in that, said device comprises:
Acquisition module is used for obtaining said user's Mobile Country Code MCC MCC, mobile network No. MNC and attribution assigned user server identification information from user's international mobile subscriber identity IMSI;
The domain name module is used to utilize the user's that said acquisition module obtains MCC, MNC and attribution assigned user server identification information to generate domain name;
Addressed module is used for inquiring about to querying server according to the domain name that the domain name module generates, and obtains the routing iinformation of the corresponding attribution assigned user server of domain name.
9. device as claimed in claim 8 is characterized in that, said acquisition module comprises:
First sub module stored is used for storing the positional information that the corresponding attribution assigned user server of at least one type of IMSI is identified at IMSI;
First obtains submodule, is used for obtaining from the relevant position of user's IMSI according to the positional information of said first sub module stored storage user's attribution assigned user server identification information.
10. device as claimed in claim 8 is characterized in that, said acquisition module comprises:
The position submodule is used for obtaining attribution assigned user server from the message that the user sends and is identified at the positional information the IMSI;
Second obtains submodule, and the said positional information that is used for obtaining according to said position submodule is obtained said user's attribution assigned user server identification information from the relevant position of user's IMSI.
11. device as claimed in claim 8 is characterized in that, said acquisition module comprises:
The 3rd obtains submodule, and the position that is used for stipulating according to standard obtains said user's attribution assigned user server identification information from said user's IMSI.
12. device as claimed in claim 8 is characterized in that, said acquisition module comprises:
Second sub module stored is used to store a plurality of attribution assigned user server identification informations;
Matched sub-block; Pre-determined bit among attribution assigned user server identification information that is used for said second sub module stored is stored and user's the IMSI is mated, and will with the attribution assigned user server identification information of pre-determined bit coupling attribution assigned user server identification information as said user;
Said pre-determined bit comprises: the position among the IMSI except that MCC and MNC, and the figure place of said pre-determined bit is more than or equal to the figure place of attribution assigned user server identification information.
13. an attribution assigned user server addressing system is characterized in that, said system comprises:
Mobile management network element; Be used for obtaining said user's MCC, MNC and attribution assigned user server identification information from user's IMSI; Utilize said user's MCC, MNC and attribution assigned user server identification information to generate domain name, and send the query requests that carries domain name;
Querying server is used for confirming according to the domain name that query requests is carried the routing iinformation of user's attribution assigned user server, and returns the inquiry response that carries said routing iinformation to said mobile management network element.
CN2009100773418A 2009-02-18 2009-02-18 Attribution assigned user server addressing method, device and system Expired - Fee Related CN101808308B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2009100773418A CN101808308B (en) 2009-02-18 2009-02-18 Attribution assigned user server addressing method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2009100773418A CN101808308B (en) 2009-02-18 2009-02-18 Attribution assigned user server addressing method, device and system

Publications (2)

Publication Number Publication Date
CN101808308A CN101808308A (en) 2010-08-18
CN101808308B true CN101808308B (en) 2012-08-15

Family

ID=42609882

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2009100773418A Expired - Fee Related CN101808308B (en) 2009-02-18 2009-02-18 Attribution assigned user server addressing method, device and system

Country Status (1)

Country Link
CN (1) CN101808308B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104754670A (en) * 2013-12-30 2015-07-01 中兴通讯股份有限公司 Network switching method and device for multimode card terminal
CN103701954B (en) * 2014-01-03 2017-05-24 中国联合网络通信集团有限公司 Domain name addressing method and domain name addressing device
CN104301992A (en) * 2014-10-14 2015-01-21 大唐移动通信设备有限公司 Method, device and system for selecting adjacent home subscriber servers
CN106464550B (en) * 2014-12-17 2020-01-31 华为技术有限公司 Method and apparatus for determining gateway information
DK3639571T3 (en) * 2018-01-15 2022-11-07 Ericsson Telefon Ab L M Selecting a network function instance
CN112583674A (en) * 2020-12-16 2021-03-30 珠海格力电器股份有限公司 Data processing method and device, electronic equipment and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1878418A (en) * 2006-07-07 2006-12-13 华为技术有限公司 Method, system and network element for obtaining GGSN address of user ascription area
CN101043526A (en) * 2007-04-30 2007-09-26 华为技术有限公司 Method, apparatus and system for processing message in IMS network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1878418A (en) * 2006-07-07 2006-12-13 华为技术有限公司 Method, system and network element for obtaining GGSN address of user ascription area
CN101043526A (en) * 2007-04-30 2007-09-26 华为技术有限公司 Method, apparatus and system for processing message in IMS network

Also Published As

Publication number Publication date
CN101808308A (en) 2010-08-18

Similar Documents

Publication Publication Date Title
CN101790150B (en) Method and device for updating contract allocation of access point name
CN101808308B (en) Attribution assigned user server addressing method, device and system
CN101297515B (en) EAP/SIM authentication for mobile IP to leverage GSM/SIM authentication infrastructure
US8477945B2 (en) Method and server for providing a mobile key
CN101843145B (en) A system and method for reselection of a packet data network gateway when establishing connectivity
US8832433B2 (en) Methods and systems for registering a packet-based address for a mobile device using a fully-qualified domain name (FQDN) for the device in a mobile communication network
US20080270794A1 (en) Method and Server for Providing Mobility Key
CN101300814B (en) Subscriber-specific enforcement of proxy-mobile-ip (PMIP) instead of client-mobile-ip (CMIP)
CN101483675A (en) Network appliance searching method and network appliance
CN102640473A (en) Method for managing a P2P network based on cellular communications
US8630420B2 (en) Method for auto-configuration of a network terminal address
EP1733536A1 (en) A method of configuring a mobile node
CN101789912A (en) Method, device and system for updating gateway information of packet data network
CN101128022A (en) Terminal switching method and device and acquisition method and device for source access gateway address
CN101043526B (en) Method, apparatus and system for processing message in IMS network
Korhonen et al. Local mobility anchor (LMA) discovery for proxy mobile IPv6
CN101594394A (en) Discovering server method, system and equipment
CN104717600A (en) M2M terminal/terminal peripheral accessibility management method and device
CN100563159C (en) Generic authentication system and visit the method that Network in this system is used
CN101877841A (en) Method, system and network equipment for realizing urgent services
CN101990190B (en) Select gateway approach and device in mobile communications network and comprise the system of this device
CN101635915B (en) Method and device for selecting packet data network (PDN)
US20050259626A1 (en) Method of communication
CN101932083B (en) Method for selecting tunnel establishment mode as well as terminal, server and system
CN101179554B (en) Method and network side for notifying boot mode of mobile subscriber terminal

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20120815