WO2010012241A1 - Method for performing information interaction and node for storing user subscribed data - Google Patents
Method for performing information interaction and node for storing user subscribed data Download PDFInfo
- Publication number
- WO2010012241A1 WO2010012241A1 PCT/CN2009/073015 CN2009073015W WO2010012241A1 WO 2010012241 A1 WO2010012241 A1 WO 2010012241A1 CN 2009073015 W CN2009073015 W CN 2009073015W WO 2010012241 A1 WO2010012241 A1 WO 2010012241A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- subscription data
- type
- mobility management
- sgsn
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/12—Mobility data transfer between location registers or mobility servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4588—Network directories; Name-to-address mapping containing mobile subscriber information, e.g. home subscriber server [HSS]
Definitions
- the present invention relates to wireless communication technologies, and more particularly to techniques for information interaction with nodes having mobility management functions during location update procedures.
- EPS Evolved Packet System
- the architecture of the EPS is as shown in FIG. 1 , including an evolved UMTS Terrestrial Radio Access Network (E-UTRAN) for implementing all functions related to the evolved network radio; a mobility management entity (MME, Mobility Management Entity), responsible for the mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, etc.; Serving GW (Serving Gateway), is the user plane anchor between 3GPP access systems Ending the interface of the E-UTRAN; the Packet Data Network Gateway (PDN GW) is a user plane anchor between the 3GPP access system and the non-3GPP access system, and terminates and the external packet data network (PDN) , Packet Data Network ) interface.
- E-UTRAN evolved UMTS Terrestrial Radio Access Network
- MME Mobility Management Entity
- Serving GW Serving Gateway
- PDN GW Packet Data Network Gateway
- the Policy and Charging Rule Function (PCRF) is used for policy control decisions and flow accounting control functions.
- the Home Subscriber Server (HSS) is used to store user subscription data.
- the interface between the MME and the HSS is S6a based on the Diameter (Protocol Name for Implementing AAA Function) protocol, and mainly performs interaction of user location information, user subscription information, and authentication information.
- the UMTS Terrestrial Radio Access Network (UTRAN, UMTS Terrestrial Radio Access Network) and GSM/EDGE Radio Access Network (GERAN, GSM/EDGE Radio Access Network) are used to implement all wireless related functions in existing GPRS/UMTS networks, serving General Packet Radio Service Support Nodes (SGSN, Serving) GPRS Supporting Node), used to implement routing and forwarding, mobility management, session management, and user information storage in GPRS/UMTS networks.
- SGSN General Packet Radio Service Support Nodes
- GPRS Supporting Node used to implement routing and forwarding, mobility management, session management, and user information storage in GPRS/UMTS networks.
- the SGSN will evolve from the original Gn/Gp interface (the interface between the SGSN and the GGSN in the GPRS network) to the S4 interface between the support and the Serving GW, between the SGSN and the HSS.
- the interface will also evolve from supporting the Gr application based on the Mobile Application Part (MAP) to supporting the Diameter-based S6d interface.
- MAP Mobile Application Part
- the GPRS network and EPS will coexist for a period of time.
- GERAN/UTRAN and E-UTRAN will coexist for a long time, thus completing the GERAN/UTRAN access control and session function SGSN and completing E-UTRAN access control and session.
- the functional MME also coexists for a long time.
- the SGSN and the MME may exist separately or together as one node.
- the HSS or Home Location Register (HLR, Home Location Register) may result in different types of stored user subscription data due to different versions of the protocol.
- the SGSN or the MME sends a location update request to the HSS or the HLR, and the HSS or the HLR sends the user subscription data to the SGSN or the MME according to the location update request.
- the inventor of the present invention finds in the process of implementing the present invention that when the SGSN and the MME coexist, when the SGSN, the MME or the MME/SGSN sends a location update request to the HSS or the HLR, the HSS or the HLR cannot determine What type of user subscription data is sent to the node that issued the location update request.
- a technical problem to be solved by the embodiments of the present invention is to provide a method for performing information interaction with a node having a mobility management function during a location update process, and a node for storing user subscription data, for signing a node with a mobile management function to a storage user.
- the node of the data issues a location update request
- the node storing the subscriber subscription data can send the correct type of subscriber subscription data to the node having the mobility management function.
- a method for performing information interaction with a node having a mobility management function during a location update process comprising: receiving a location update request sent by a node having a mobility management function, where the location update request carries a type of the requested subscriber subscription data; The type of the requested user subscription data sends the user subscription data to the node having the mobility management function.
- a method for information interaction with a node having a mobility management function during a location update process comprising: receiving a location update request sent by a node having a mobility management function, the location update request carrying the node type having the mobility management function Related information, the information related to the node type having the mobility management function includes at least the type of the node having the mobility management function; and sending the node having the mobility management function according to the type of the node having the mobility management function User signing data.
- a node for storing user subscription data comprising: a location update request obtaining unit, configured to receive a location update request sent by a node having a mobility management function, where the location update request carries type information related to the node having the mobility management function
- the type-related information includes at least the type of the node having the mobility management function
- the user subscription data sending unit configured to obtain, according to the location update request obtaining unit, the type of the node having the mobility management function, The node with the mobility management function sends the user subscription data.
- the node having the mobility management function sends the location update request
- the node that stores the user subscription data is provided with the type of the user subscription data requested, or the node type information with the mobility management function is specified.
- the node storing the user subscription data can correctly send the user subscription data required by the requesting node according to the type of the user subscription data requested by the node having the mobility management function or the type of the node having the mobility management function.
- FIG. 1 is a schematic structural diagram of a prior art EPS
- FIG. 2 is a flowchart of a method for performing information interaction with a node that stores user subscription data in a location update process according to an embodiment of the present invention
- 3 is a schematic structural diagram of a node having a mobility management function according to an embodiment of the present invention
- FIG. 4 is a flowchart of a method for performing information interaction with a node having a mobility management function in a location update process according to an embodiment of the present invention
- FIG. 5 is a schematic structural diagram of a node for storing user subscription data according to an embodiment of the present invention
- FIG. 6 is a flowchart of a method for performing a location update operation according to an embodiment of the present invention
- FIG. 7 is a schematic structural diagram of another node storing user subscription data according to an embodiment of the present invention.
- FIG. 8 is a flowchart of a first exemplary embodiment of the present invention.
- FIG. 9 is a second embodiment of the present invention; Flow chart of an exemplary embodiment;
- FIG. 10 is a flowchart of a third exemplary embodiment of the present invention
- FIG. 11 is a flowchart of a fourth exemplary embodiment of the present invention
- FIG. 12 is a flowchart of a fifth embodiment of the present invention
- Figure 13 is a flowchart of a sixth embodiment of the present invention
- Figure 14 is a flowchart of a seventh embodiment of the present invention
- Figure 15 is another storage user according to an embodiment of the present invention
- Schematic diagram of the node of the contract data
- Figure 16 is a flowchart of an eighth embodiment of the present invention
- Figure 17 is a flowchart of a ninth embodiment of the present invention
- Figure 18 is a flowchart of a tenth embodiment of the present invention; .
- Step S201 Send a location update request to a node that stores user subscription data, where the location is further
- the new request carries information related to the node type having the mobility management function that issues the location update request, and the information related to the node type having the mobility management function includes at least the type of the node with the mobility management function of the sending location update,
- the type of the node having the mobility management function may directly indicate the type of the node, or may be clarified by requesting an indication of a location update operation on a certain node type, for example, the node having the mobility management function is a joint node.
- the information about the node type with the mobility management function of the location update request carried by the location update request may be an indication of requesting simultaneous location update operations for the MME and the SGSN.
- the location update request may further carry a type of user subscription data required by the node with the mobility management function that issues the location update request, and obtain the type of the node that stores the user subscription data according to the node with the mobility management function.
- the node that stores the user subscription data may obtain the user subscription data sent according to the type of the node having the mobility management function and the type of the user subscription data required, or store the user subscription data.
- the node needs to consider the type of the user subscription data required by the node having the mobility management function.
- the node storing the user subscription data User subscription data of the type required by the node with mobility management is sent. If the node with mobility management function that issues the location update request is MME or
- the SGSN, and the type of the user subscription data required by the MME is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type
- the obtained user subscription data is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type.
- the node with the mobility management function that sends the location update request is the MME, and the user subscription data obtained by the MME is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, then
- the MME sends the user subscription data of the SGSN corresponding type to the SGSN, and the SGSN does not need to request the user type subscription data of the corresponding type to the node storing the user subscription data;
- the node with the mobility management function of the update request is the SGSN, and the user subscription data obtained by the SGSN is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, when the user equipment switches to the MME for providing the service.
- the SGSN sends the user subscription data of the MME corresponding type to the MME, and the MME does not need to request the user subscription data of the corresponding type to the node that stores the user subscription data.
- the node with the mobility management function that sends the location update request is the MME/SGSN, and the user equipment performs location update through one of the MME and the SGSN, the location update request carries the mobility management function.
- the node type related information also indicates that the node that needs to store the user subscription data prioritizes the manner in which the location update operation is performed. Further, the type of the MME/SGSN may have multiple representations, and different representations may represent different information.
- the MME/SGSN may indicate that the user equipment is updated by the MME, and then the user is stored.
- the node of the subscription data should preferentially perform the location update operation corresponding to the MME.
- the subscriber subscription data of the type corresponding to the MME can be preferentially transmitted to the associated node MME/SGSN.
- the node storing the user subscription data generally sends the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN to the MME/SGSN.
- the location update is performed according to the priority manner. Operation, that is, prioritizing the location update operation of the node that needs to be prioritized, and then performing the location update operation of the node that is not prioritized; if the location update operation of the node that needs priority is successfully performed, the unsuccessful execution is not prioritized.
- the location update operation of the node returns a location update operation response to indicate that only the location update operation of the node that needs to be prioritized is performed.
- the location update request also carries the address of the MME. And the address of the SGSN, so that the node storing the user subscription data records the address of the MME and the address of the SGSN.
- the location update request may be separately Using one parameter to indicate the address of the SGSN that is not prioritized; if the type of the associated node MME/SGSN carried by the location update request further indicates that the node that needs to store the user subscription data preferentially considers the manner of performing the location update operation In the SGSN, a parameter is used alone in the location update request to indicate the address of the MME that is not prioritized.
- the address update request in the prior art already includes an address of a node having a mobility management function, and when the node having the mobility management function is the joint node MME/SGSN, the existing address may be used.
- the address of another entity can be represented by a single parameter, and of course the parameters used separately are also carried in the location update request. If a node having a mobility management function and a node storing the user subscription data are provided with a node having a protocol conversion function, the location update request sent to the node storing the user subscription data reaches the storage user subscription data through the node having the protocol conversion function.
- the obtained user subscription data is user subscription data obtained through a node having a protocol conversion function.
- an interworking function may be set between the MME/SGSN and the HSS/HLR, and an S6a/S6d interface between the MME/SGSN and the IWF, which is used by the Diameter protocol, and the HSS/HLR and the IWF.
- the MAP-based Gr/Gr+ interface is used, and the IWF mainly performs the function of protocol conversion.
- the MME/SGSN When the MME/SGSN sends a location update request to the HSS/HLR, the MME/SGSN sends a location update request based on the Diameter protocol to the IWF, and the IWF sends a MAP-based location update request to the HSS/HLR; when the HSS/HLR is directed to the MME/ When the SGSN sends a location update response, the HSS/HLR sends a MAP-based location update response to the IWF, and the IWF sends a location update response based on the Diameter protocol to the MME/SGSN.
- the execution body of the foregoing steps S201 and S202 may be a node having a mobility management function, such as an MME, an SGSN, or a joint node MME/SGSN, and the node storing the subscriber subscription data may be an HSS or an HLR.
- the node storing the user subscription data is sent to the location update response sent by the node having the mobility management function management function.
- an embodiment of the present invention provides a node with a mobility management function. As shown in FIG.
- the node having the mobility management function includes: a location update request sending unit 301, configured to send a location update request to a node that stores user subscription data, where the location update request carries the mobility management function
- the node type related information, the information related to the node type having the mobility management function includes at least the type of the node having the mobility management function for transmitting the location update
- the user subscription data obtaining unit 302 configured to send the location update request
- the node that stores the user subscription data obtains the user subscription data sent according to the type of the node with the mobility management function.
- the node type with the mobility management function that issues the location update request carried by the location update request sent by the location update request transmitting unit 301 The related information may be an indication of requesting simultaneous location update operations for the MME and the SGSN.
- the location update request sent by the location update request sending unit 301 may further carry the type of the user subscription data required by the node having the mobility management function shown in FIG. 3, and the user subscription data obtaining unit 302 obtains the node storing the user subscription data according to the node.
- the node that stores the user subscription data can obtain the type of the node with the mobility management function shown in FIG. 3 and the required user subscription.
- the type of user subscription data in general, the node storing the user subscription data will send the user subscription data of the type required by the node with the mobility management function. If the node with the mobility management function shown in FIG.
- the user subscription data obtaining unit 302 The obtained user subscription data is user subscription data corresponding to the MME type and user subscription data corresponding to the SGSN type.
- the node with the mobility management function shown in FIG. 3 is an independent MME or a separate SGSN
- the independent MME or the independent SGSN requests to obtain all types of user subscription data
- the node that stores the user subscription data will All types of user subscription data are sent to a separate MME or a separate SGSN. If the node with the mobility management function shown in FIG.
- the subscription data is the user subscription data of the corresponding type of the MME and the user subscription data of the corresponding type of the SGSN.
- the MME sends the subscription data of the corresponding type of the SGSN to the SGSN, without The SGSN requests the node that stores the user subscription data to request the corresponding type of user subscription data; if the node with the mobility management function shown in FIG. 3 is the SGSN, and the user subscription data obtained by the SGSN is the user subscription data of the MME corresponding type and the SGSN.
- Corresponding type of user subscription data when the user equipment switches to the MME for location update, the SGSN sends the user subscription data of the MME corresponding type to the MME, and the MME does not need to request the corresponding type of user from the node that stores the user subscription data. Signing data. If the node with the mobility management function shown in FIG. 3 is the MME/SGSN, and the user equipment performs location update through one of the MME and the SGSN, the location update request sending unit 301 sends the location update request.
- the node type related information having the mobility management function also indicates that the node that needs to store the user subscription data preferentially considers the manner of performing the location update operation and the type of the user subscription data sent by the node that needs to store the subscriber subscription data.
- the type of the MME/SGSN may have multiple representations, and different representations may represent different information.
- the MME/SGSN may indicate that the user equipment is updated by the MME, and then the user is stored.
- the node of the subscription data should preferentially perform the location update operation corresponding to the MME.
- the subscriber subscription data of the type corresponding to the MME can be preferentially transmitted to the associated node MME/SGSN.
- the node storing the user subscription data generally sends the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN to the MME/SGSN.
- the location update request sent by the location update request sending unit 301 is further The address of the MME and the address of the SGSN are carried, so that the node storing the subscriber subscription data records the address of the MME and the address of the SGSN. If the type of the MME/SGSN shown in FIG. 3 also indicates that the node that needs to store the user subscription data preferentially considers the MME to perform the location update operation, one of the location update requests may be used alone.
- the parameter indicates the address of the SGSN; if the location update request is sent
- the type of the MME/SGSN carried in the location update request sent by the sending unit 301 also indicates that the node that needs to store the user subscription data preferentially considers the location update operation corresponding to the SGSN, and in the location update request A parameter is used alone to indicate the address of the MME. If a node having a mobility management function and a node storing the user subscription data shown in FIG. 3 are provided with a node having a protocol conversion function, the location update request transmitting unit 301 passes the location update request issued by the node storing the user subscription data. The node having the protocol conversion function reaches the node storing the user subscription data, and the user subscription data obtained by the user subscription data obtaining unit 302 is the user subscription data obtained through the node having the protocol conversion function.
- the node with the mobility management function shown in FIG. 3 may be the MME, the SGSN, or the joint node MME/SGSN, and the node storing the subscriber subscription data may be an HSS or an HLR.
- the user subscription data obtained by the user subscription data obtaining unit 302 may be carried in a location update response sent by the node storing the subscriber subscription data to the node having the mobility management function shown in FIG.
- Embodiments of the present invention also provide a method for performing information interaction with a node having a mobility management function during a location update process. As shown in FIG.
- Step S401 Obtain a location update request sent by a node with a mobility management function, where the location update request carries information about a node type having a mobility management function, where the mobility management function is The node type related information includes at least the type of the node having the mobility management function.
- Step S402 Send user subscription data to the node having the mobility management function according to the type of the node having the mobility management function.
- the location update request may also carry the type of user subscription data required by the node having the mobility management function. If the location update request further carries the type of user subscription data required by the node having the mobility management function, sending the user subscription data to the node having the mobility management function according to the type of the node having the mobility management function At the time, the user subscription data is transmitted to the node having the mobility management function according to the type of the node having the mobility management function and the type of the user subscription data required.
- the subscription data is the type of user subscription data required by the node with mobility management capabilities.
- the node with the mobility management function is the MME or the SGSN, and the type of the user subscription data required is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, the node with the mobility management function is used.
- the user subscription data sent by the MME is the user subscription data of the corresponding type of the MME and the user subscription data of the SGSN corresponding type; if the node with the mobility management function that issues the location update request is the MME, the user equipment switches to the SGSN to provide the service.
- the MME sends the subscriber subscription data of the SGSN corresponding type to the SGSN; if the node with the mobility management function that sends the location update request is the SGSN, when the user equipment switches to provide services for the MME, the SGSN The user subscription data of the MME corresponding type is sent to the MME.
- the location update operation is performed according to the priority consideration manner. If the information related to the node type of the mobile management function carried by the location update request further indicates the type of user subscription data that needs to be prioritized, when the user subscription data is sent, according to the type of the user subscription data that needs to be prioritized Send user subscription data. Further, if the node with the mobility management function is the MME/SGSN, the type of the MME/SGSN may have multiple representations, and different representations may represent different information, for example, MME/ The SGSN may indicate that the user equipment is updated by the MME.
- the location update operation corresponding to the MME should be preferentially performed.
- the user subscription data of the type corresponding to the MME may be preferentially considered.
- the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN are generally sent to the MME/SGSN.
- the node with the mobility management function that issues the location update request is the joint node MME/SGSN
- the addresses of the MME and the SGSN in the setup node MME/SGSN are not the same, and the location update request also carries the address of the MME and The address of the SGSN, after the node storing the subscriber subscription data obtains the location update request sent by the node with the mobility management function, records the address of the MME and the address of the SGSN.
- the node with the mobility management function that issues the location update request is the joint node MME/SGSN, and the information related to the node type with the mobility management function carried by the location update request indicates that the location update operation needs to be prioritized
- a parameter is used to indicate the address of the SGSN in the location update request; if the information related to the node type with the mobility management function carried in the location update request indicates that the location update operation needs to be prioritized
- a parameter is used to indicate the address of the MME in the location update request.
- the obtained location update request issued by the node having the mobility management function is obtained by a node having a protocol conversion function.
- the user subscription data sent to the node having the mobility management function is reached by the node having the protocol conversion function to the node having the mobility management function.
- the execution body of the foregoing steps S401 and S402 may be a node that stores user subscription data, such as an HSS or an HLR, and a node having a mobility management function may be an MME, an SGSN, or a joint node MME/SGSN.
- the node storing the user subscription data is sent to the location update response sent by the node having the mobility management function management function.
- an embodiment of the present invention provides a node that stores user subscription data. As shown in FIG.
- the node for storing user subscription data includes: a location update request obtaining unit 501, configured to obtain a location update request sent by a node having a mobility management function, where the location update request carries the mobility management function Information related to the node type, the information related to the node type having the mobility management function includes at least the type of the node having the mobility management function for sending the location update; the user subscription data sending unit 502, configured to update according to the location
- the type of the node having the mobility management function obtained by the obtaining unit 501 is requested, and the user subscription data is transmitted to the node having the mobility management function.
- the location update request obtained by the location update request obtaining unit 501 may also carry the type of user subscription data required by the node having the mobility management function.
- the location update request further carries the type of user subscription data required by the node having the mobility management function, the number of user subscriptions According to the type of the node having the mobility management function and the type of the user subscription data required by the sending unit 502 to send the user subscription data to the node having the mobility management function according to the type of the node having the mobility management function.
- User subscription data is sent to the node having the mobility management function.
- the user subscription data sending unit 502 sends the user subscription data, in addition to the type of the node having the mobility management function, it is also necessary to consider the type of the user subscription data required by the node having the mobility management function.
- the user subscription data sent by the user subscription data transmitting unit 502 to the node having the mobility management function is user subscription data of a type required by the node having the mobility management function.
- the node storing the user subscription data may further include: a location update operation unit 503, configured to perform a location update operation after the location update request obtaining unit 501 obtains the location update request sent by the node having the mobility management function, where if the location
- the information related to the node type of the mobile management function carried in the update request also indicates that the manner of performing the location update operation and the type of the user subscription data required are prioritized, and the location update operation unit 503 performs the location update operation according to the Location update operations are required in a prioritized manner. If the information related to the node type with the mobility management function carried by the location update request also indicates that the user subscription subscription needs to be prioritized, the subscriber subscription data needs to be prioritized to send the subscriber subscription data.
- the type of the MME/SGSN may have multiple representations, and different representations may represent different information, for example, MME/
- the SGSN may indicate that the user equipment is updated by the MME.
- the location update operation unit 503 should perform the location update operation corresponding to the MME when performing the location update operation.
- the user subscription data sending unit 502 sends the user subscription data, It is preferred to transmit the subscriber subscription data of the type corresponding to the MME to the associated node MME/SGSN.
- the user subscription data sending unit 502 will generally send the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN to the MME/SGSN.
- the node storing the user subscription data may further include: a recording unit 504, configured to record an address of the MME or the SGSN that initiates the location update request. If the node with the mobility management function that issues the location update request is the MME in the joint node MME/SGSN, the joint node MME/SGSN, and The address of the SGSN is different, and the location update request further carries the address of the MME and the address of the SGSN.
- the recording unit 504 After the location update request obtaining unit 501 obtains the location update request sent by the node having the mobility management function, the recording unit 504 simultaneously records the MME. Address and SGSN address. If a node having the protocol conversion function is provided between the node shown in FIG. 5 and the node having the mobility management function, the location update request issued by the node having the mobility management function obtained by the location update request obtaining unit 501 is through protocol conversion. The user subscription data sent by the user subscription data transmitting unit 502 to the node having the mobility management function is obtained by the node having the protocol conversion function to the node having the mobility management function. It should be noted that the node storing the subscriber subscription data shown in FIG.
- the node having the mobility management function may be an MME, an SGSN, or a joint node MME/SGSN.
- the user subscription data transmitted by the user subscription data transmitting unit 502 to the node having the mobility management function may be carried in the location update response sent by the user subscription data transmitting unit 502 to the node having the mobility management function.
- another node for storing user subscription data is provided by an embodiment of the present invention.
- the node storing the user subscription data includes a location update request obtaining unit 1501 and a user subscription data transmitting unit 1502.
- the location update request obtaining unit 1501 is the same as the location update request obtaining unit 501 in the above embodiment; the user subscription data transmitting unit 1502 is the same as the user subscription data transmitting unit 502 in the above embodiment. I won't go into details here.
- the node that stores the user subscription data may further include a first storage unit 1503, and is connected to the location update request obtaining unit 1501, and configured to store the mobile management function received by the location update request obtaining unit 1201. The type of node.
- the node that stores the user subscription data may further include a first sending unit 1504, configured to be connected to the first storage unit 1503, and when the user subscription data corresponding to the node corresponding to the type is updated, The node corresponding to the type sends a user data update request message.
- the location update operation is generally performed.
- an embodiment of the present invention provides a method for performing a location update operation.
- Step S601 Obtain a location update request sent by a node with a mobility management function, where the location update request carries information about a node type having a mobility management function, and the information related to the node type of the mobility management function includes at least sending The type of node with the mobility management function of the location update.
- Step S602 If the type of the node with the mobility management function indicates that the node with the mobility management function is the joint node MME/SGSN, and the information about the node type with the mobility management function also indicates the MME and the SGSN.
- the location update operation corresponding to the MME and the location update operation corresponding to the SGSN are simultaneously performed.
- the address of the MME and the SGSN in the setup node MME/SGSN may be the same, and the addresses of the MME and the SGSN in the setup node MME/SGSN may be different.
- the obtained location update request may carry the addresses of the MME and the SGSN, so that when the location update operation corresponding to the MME and the location update operation corresponding to the SGSN are performed, the MME may be simultaneously recorded. Address and SGSN address.
- a user equipment can only perform location update through one of the MME and the SGSN. It is assumed that a user equipment performs location update by the MME at a certain time, and the MME is the MME in the connection node MME/SGSN, and the connection node MME/SGSN issues a location update request to the node that stores the user subscription data, and stores the user subscription.
- the node of the data simultaneously performs a location update operation corresponding to the MME and a location update operation corresponding to the SGSN.
- the setup node MME/SGSN does not need to be stored again.
- the node that subscribes to the user's subscription data issues a location update request, and the node that stores the user subscription data does not need to perform the location update operation corresponding to the SGSN.
- the execution body of the foregoing steps S601 and S602 may be a node that stores user subscription data, such as an HSS or an HLR, and the node with the mobility management function may be an MME, an SGSN, or a joint node MME/SGSN.
- the node for storing user subscription data includes: a location update request obtaining unit 701, configured to obtain a location update request sent by a node having a mobility management function, where the location update is performed.
- the type of the node having the mobility management function obtained by the location update request obtaining unit 701 indicates that the node having the mobility management function is the joint node MME/SGSN, and the node type having the mobility management function is related.
- the information also indicates that the MME and the SGSN simultaneously perform a location update operation, and simultaneously performs a location update operation corresponding to the MME and a location update operation corresponding to the SGSN.
- the node shown in FIG. 7 may further include a recording unit 704 for simultaneously recording the address of the MME and the address of the SGSN when the location update operation unit 703 performs a location update operation corresponding to the MME and a location update operation corresponding to the SGSN.
- the node storing the user subscription data shown in FIG. 7 may be an HSS or an HLR, and the node having the mobility management function may be an MME, an SGSN, or a joint node MME/SGSN.
- the location update mentioned in the foregoing embodiments may refer to a location update in a user equipment attach process, or may refer to a TAU (Tracking Area Update) or a Routing Area Update (RAU). Updated process.
- the first embodiment combines the node MME/SGSN to send its node type in the location update request through the S6a or S6d interface or request an indication of the location update operation for the MME and the SGSN simultaneously and the type of the user subscription data (optional)
- the request is to simultaneously issue EPS subscriber subscription data and 2G/3G subscriber subscription data supporting S4-SGSN.
- the specific process is as shown in FIG.
- Step S801 The joint node MME/SGSN sends a location update request (Update Location) to the HSS, where the location update request carrying node type is a joint node MME/SGSN or carries a request to the MME and The SGSN simultaneously performs an indication of the location update operation, requesting the EPS user subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN.
- Step S802 The HSS performs location update operations on the E-UTRAN and UTRAN/GERAN access modes simultaneously for the joint node MME/SGSN, for example, 2G/3G and EPS service check, GERAN/UTRAN and EUTRAN roaming limit check, etc.
- the HSS carries the EPS user subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN in the location update response (Update Location Ack) and sends it to the associated node MME/SGSN. It should be noted:
- the location update between the MME/SGSN and the HSS is equivalent to combining the location update procedures defined in S6a and S6d.
- the joint node MME/SGSN does not need to issue a location update request to the HSS.
- the joint node MME/SGSN can use the Diameter application identifier in S6a or S6d to indicate the location update mode that needs to be prioritized by the HSS and the type of user subscription data required.
- the IWF will convert the messages of S6a and S6d into messages suitable for Gr+.
- the joint node MME/SGSN can indicate the location update mode and needs that need to be prioritized by the HSS through the node type information. The type of user subscription data.
- the MME/SGSN indicates that the location update and the EPS user subscription data initiated by the MME are preferentially considered; the SGSN/MME indicates that the location update initiated by the SGSN and the 2G/3G subscriber subscription data are prioritized.
- Second Embodiment This embodiment is applicable to the scenario of interaction between EPS and Rel-8 (Release 8) or Pre Rel-8 (Pre-Release 8) HLR. At this time, there is an IWF between the MME/SGSN and the HLR. The specific process is as shown in FIG.
- Step S901 The joint node MME/SGSN sends a location update request to the IWF, and the location update request carries the node type as the joint node MME/SGSN, and simultaneously requests the EPS user subscription data and Support 2G/3G user subscription data of S4-SGSN.
- Step S902 After receiving the location update request based on the Diameter protocol, the IWF converts the location update request based on the Diameter protocol into a MAP-based location update request, and then sends the MAP-based location update request to the HLR.
- the IWF converts the MAP-based location update response into a location update response based on the Diameter protocol and sends it to the set-up node MME/SGSN. It should be noted:
- the location update between the MME/SGSN and the HLR is equivalent to combining the location update procedures defined in S6a and S6d.
- the joint node MME/SGSN does not need to issue a location update request to the HLR.
- the MME/SGSN may indicate the location update mode that requires the HLR priority and the type of the user subscription data required by the node type. For example, the MME/SGSN indicates that the location update and the EPS subscriber subscription data initiated by the MME are prioritized; /MME indicates that the location update initiated by the SGSN and the 2G/3G subscriber subscription data are prioritized.
- the location update request message needs to carry the addresses of the MME and the SGSN respectively, or combined with the priority representation in the node type, and used separately in the location update request.
- One parameter carries the address of a node that is not prioritized.
- the HLR is the pre-Rel-8 HLR, since the HLR of the pre-Rel-8 cannot support the extended Gr+ interface, the type of the node in the above step S902 and the type of the user subscription data required, pre Rel-8 The HLR is not recognized.
- Pre-Rel-8 HLR only has 2G/3G user sign About the data, the pre-rel-8 HLR can only send the 2G/3G user subscription data based on the Gr interface protocol to the IWF.
- the IWF then converts the 2G/3G subscriber subscription data into EPS subscriber subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN to the associated node MME/SGSN.
- the MME and the SGSN send the node type and the type of the requested user subscription data (required) to the HSS in the location update request through the S6a or S6d interface, and request the simultaneous delivery of the EPS user subscription data and support S4.
- - SGSN's 2G/3G subscriber subscription data The specific process is shown in Figure 10, including:
- Step S1001 The independent MME or the SGSN sends a location update request to the HSS, and the location update request carries the node type as the MME or the SGSN, and simultaneously requests the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN;
- Step S1002 HSS According to the node type, the corresponding location update operation, such as service check, roaming restriction check, etc., when the check passes, the HSS records the address of the MME or the SGSN, and signs the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN.
- the bearer is sent to the MME or the SGSN in the location update response.
- This embodiment is applicable to a scenario in which an EPS interacts with an HLR of Rel-8 (version 8) or pre Rel-8 (a version prior to version 8). At this time, there is an IWF between the MME/SGSN and the HLR. The specific process is shown in Figure 11:
- Step S1101 The independent MME or the SGSN sends a location update request to the IWF.
- the location update request carries the node type as the MME or the SGSN, and simultaneously requests the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN.
- Step S1102 After receiving the location update request based on the Diameter protocol, the IWF converts the location update request based on the Diameter protocol into a MAP-based location update request, and then sends the MAP-based location update request to the HLR.
- Step S1103 The HLR performs corresponding location update operations according to the type of the node, such as service check, roaming restriction check, etc. When the check passes, the HLR records the address of the MME or the SGSN, and the EPS is The user subscription data and the 2G/3G user subscription data supporting the S4-SGSN are carried in the location update response and sent to the IWF.
- Step S1104 The IWF converts the MAP-based location update response into a location update response based on the Diameter protocol and sends it to the MME or the SGSN. It should be noted:
- the HLR When the HLR is the pre-Rel-8 HLR, the extended Gr+ interface cannot be supported. Since the pre-Rel-8 HLR cannot support the extended Gr+ interface, the node type in the above step S1102 and the type of the user subscription data required, The pre-Ll-8 HLR is unrecognizable.
- the pre-rel-8 HLR only has 2G/3G user subscription data, and the pre-Rel-8 HLR can only send the 2G/3G user subscription data based on the Gr interface protocol to the IWF.
- the IWF then converts the 2G/3G subscriber subscription data into EPS subscriber subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN to the associated node MME/SGSN.
- the HSS receives the location update message, and delivers the user subscription data corresponding to the node corresponding to the node type to the requesting node by using the node type carried in the message.
- the HSS stores the received node type at the same time.
- the user data update request message is sent to the node corresponding to the type.
- the following is an example of a node type MME/SGSN joint node.
- the SGSN supports both the S4-SGSN and the 2G/3G SGSN functions.
- the co-located MME/SGSN sends its node type to the HSS in the location update request via the S6a or S6d interface.
- the HSS sends the EPS user subscription data and the 2G/3G user subscription data to the joint node according to the node type.
- the HSS stores the received node type at the same time.
- the HSS determines the stored node type and determines to send the corresponding user data update message to the corresponding node.
- the specific process is shown in Figure 12.
- the method includes: Step S1201:
- the MME/SGSN is configured to send a location update request to the HSS, where the location update request carries the node type as MME/SGSN;
- Step S1202 The HSS performs corresponding location update operations, such as service check, roaming restriction check, etc. When the check passes, the HSS records the address of the MME or the SGSN, and carries the EPS user subscription data and the 2G/3G user subscription data in the location update. The response is sent to the requesting node; Step S1203: The HSS stores the node type received in step S1201; Step S1204: When the 2G/3G user subscription data is updated (including adding, deleting, and modifying), the HSS determines that the stored node type is the joint node MME/SGSN, The HSS triggers a subsequent user data update process;
- Step S1205 The HSS carries the updated 2G/3G subscriber subscription data in the user data update request message and sends the data to the MME/SGSN. If the 2G/3G subscriber subscription data is updated in step S1204, the 2G/3G is referred to. If the user subscription data is deleted, the HSS may carry the corresponding user data deletion indication in the user data update message.
- Step S1206 The MME/SGSN returns a user data update response message.
- the HSS receives the location update message, and sends the node corresponding to the node type or the requested user to the requesting node by using the node type carried in the message and/or the type of the user subscription data (the type of the user subscription data is optional).
- User subscription data corresponding to the type of subscription data The HSS simultaneously stores the received node type or the type of the requested user subscription data, and sends a user data update request to the node when the node corresponding to the type or the user subscription data corresponding to the type of the requested user subscription data is updated. Message.
- the following is an example of the node type being the MME/SGSN connection node.
- the type of the requested subscriber subscription data is the EPS subscriber subscription data and the 2G/3G subscriber subscription data.
- the SGSN supports both the S4-SGSN and the 2G/3G SGSN.
- the combined MME/SGSN sends its node type and the type of the requested user subscription data (optional) to the HSS in the location update request through the S6a or S6d interface.
- the HSS requests the HSS to simultaneously deliver the EPS user subscription data and the 2G/3G user subscription data by using the node type carried in the message or the requested user subscription data type (if the message is carried in the message) carried in the message.
- the HSS stores the received node type or the requested user subscription data type (if the message is carried), and when the subsequent 2G/3G subscription data of the corresponding user changes, the HSS determines the stored node type or the requested user subscription data type. It is determined that the corresponding user data update message is sent to the corresponding node.
- the specific process is shown in Figure 13. Includes:
- Step S1301 The combined MME/SGSN sends a location update request to the HSS, and the location update is requested.
- the carrier type is MME/SGSN, and the EPS user subscription data and the 2G/3G user subscription data are requested;
- Step S1302 The HSS performs corresponding location update operations, such as service check, roaming restriction check, etc.
- location update operations such as service check, roaming restriction check, etc.
- the HSS records the address of the MME or the SGSN, and carries the EPS user subscription data and the 2G/3G user subscription data in the location update.
- the response is sent to the requesting node;
- Step S1303 The HSS stores the node type received in step S1301 or the requested user subscription data type;
- Step S1304 When the 2G/3G user subscription data is updated (including adding, deleting, and modifying), the HSS determines that the stored node type is the joint node MME/SGSN, or the requested user subscription data type is EPS user subscription data and 2G. When the /3G user subscribes to the data, the HSS triggers the subsequent user data update process;
- Step S1305 The HSS carries the updated 2G/3G subscriber subscription data in the user data update request message and sends the data to the MME or the SGSN. If the 2G/3G subscriber subscription data is updated in step S1204, the 2G/3G is referred to. If the user subscription data is deleted, the HSS will send a user data update message carrying the corresponding user data deletion indication.
- Step S1306 The MME/SGSN returns a user data update response message. Note that the type of the requested subscriber subscription data in the location update message in step S1301 is optional.
- Step S1401 The set MME/SGSN sends a location update request to the IWF, and the location update request carries the node type as MME/SGSN.
- Step S1402 After receiving the location update request based on the Diameter protocol, the IWF will be based on
- the location update request of the Diameter protocol is converted into a MAP-based location update request, and the MAP-based location update request is sent to the HLR.
- Step S1403a The HLR performs a corresponding location update operation, such as a service check, a roaming restriction check, etc., when the check passes, the HLR records the address of the MME or the SGSN, and sets the EPS user subscription data and 2G according to the type of the request node carried in S1401.
- the /3G user subscription data is carried in the inserted user data request message and sent to the IWF;
- Step S1403b After the user data is sent, the HLR sends a location update response message to the IWF.
- Step S1404 The IWF converts the user data received in the MAP-based inserted user data message to the location update response based on the Diameter protocol and sends it to the MME/SGSN.
- Step S1405 The HLR stores the node type received in step S1402.
- S1406 When the 2G/3G user subscription data is updated (including adding, deleting, and modifying), the HLR determines that the stored node type is the joint node MME/SGSN, and the HLR triggers the subsequent user data update process;
- Step S1407 The HLR carries the updated 2G/3G user subscription data in the MAP-based user data update request message and sends the data to the IWF. If the 2G/3G user subscription data update in step S1204 refers to the 2G/ If the 3G user subscription data is deleted, the HLR may send the corresponding user data deletion indication in the user data update request message.
- Step S1408 The IWF converts the MAP-based user data update message into a user data update message based on the Diameter protocol.
- Step S1409 The MME/SGSN returns a User Data Update Response message to the IWF;
- Step S1410 The IWF converts the Diameter-based User Data Update Response message into a MAP protocol-based User Data Update message and sends it to the HLR. It should be noted:
- the HLR When the HLR is the pre-Rel-8 HLR, the extended Gr+ interface cannot be supported. Since the HLR of the pre-Rel-8 cannot support the extended Gr+ interface, the HLR of the pre-rel-8 cannot be identified for the node type in the above step S1302. .
- the HLR of the pre-Rel-8 only has the 2G/3G user subscription data, and the HLR of the ReRel-8 can only send the 2G/3G user subscription data based on the Gr interface protocol to the IWF.
- the IWF then converts the 2G/3G subscriber subscription data into EPS subscriber subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN to the associated node MME/SGSN.
- the HSS receives the location update message, and the message carries the type information of the requested subscriber subscription data and the node type related information.
- the HSS stores the type information of the received node and/or the requested user subscription data type (optional).
- the HSS decides to send a user data update request message to the node according to the stored type information of the node and/or the requested user subscription data type.
- the single MME carries the information of the EPS subscription data and the related information indicating the node type (the explicit node type MME, or the single node information + S6a interface indication information) to the HSS in the location update request through the S6a interface.
- the HSS stores the type-related information of the node (which may be directly storing the node type related information in the location update message, or may be an explicit node type MME that is derived from the node type related information) and/or the subscription data requested by the MME. Type information (optional storage).
- the HSS determines that the stored type information of the node is a single MME node or the subscription data type requested by the MME is EPS subscription data, and the HSS will not send the corresponding user data. Update the request message to the node.
- Step S1601 A single MME node sends a location update request message to the HSS.
- the type information of the user subscription data carrying the requested location update request is EPS subscription data, and the node type related information is MME, or single node information + S6a interface indication information; Description: The type information of the requested user subscription data is EPS
- the subscription data may be indicated by an explicit indication of the request for EPS subscription data; or may be initiated by the location update request message not including information explicitly requesting GPRS or 2G/3G subscription data, that is, requesting EPS subscription data is default or Implied.
- the S6a interface is defined for the HSS and the MME.
- the S6a interface indicates the request message.
- the MME from the MME or the MME/SGSN, the single node information further excludes the case of the joint node, and the combination of the two clarifies that the requesting node is a single MME node;
- Step S1603 The HSS stores the node type related information received in step S1601, optionally storing the type information of the user subscription data requested by the node;
- Step S1604 When the user's 2G When the /3G subscription data is updated (including adding, deleting, or modifying), the HSS determines that the stored node type related information is indicated as a single node MME, or the stored requested user subscription data type is EPS subscription data, and the HSS does not trigger user data.
- Step S1605 When the user's subscription data applicable only to the SGSN is updated (including adding, deleting, or modifying), the HSS determines that the stored node type related information is indicated as a single The node MME, HSS does not trigger the user data update process;
- Step S1606 When the user When the EPS subscription data is updated (including adding, deleting, or modifying), the HSS triggers the user data update process.
- Step S1607 The HSS carries the updated user EPS subscription data in the user data update request message and sends the data to the MME.
- Step S1605 If the user EPS subscription data update in step S1605 is that the user's EPS part subscription data is deleted, the HSS will send a user data update request message carrying the corresponding subscription data deletion indication; Step S1608: The MME returns the user data. Update the response message.
- the HSS receives the location update message, and the message carries the type information of the requested user subscription data and/or node type related information (optional).
- the HSS stores the received type information of the user subscription data requested by the node.
- the HSS determines to send a user data update request message to the node according to the type information of the stored user subscription data.
- the following is indicated by the node type related information as a single node type SGSN (optional presence), and the type information of the requested user subscription data.
- EPS + 2G/3G (or GPRS) subscription data as an example.
- the single SGSN sends the request EPS + 2G/3G (or GPRS) subscription data type information and/or its node type related information (clear node type SGSN, or single node information + S6d indication information) in the location update request through the S6d interface ( Node type related information is optional.)
- the HSS stores the subscription data type information requested by the SGSN. When the subsequent EPS or 2G/3G subscription data of the corresponding user is changed, the HSS determines that the stored subscription data type information type information requested by the SGSN is EPS + 2G/3G subscription data, and the HSS sends a corresponding user data update request message to the SGSN.
- the specific process is shown in Figure 17.
- Step S1701 A single SGSN issues a location update request to the HSS.
- the type information of the user subscription data carrying the request in the location update request message is EPS.
- the type information of the requested subscriber subscription data is EPS + 2G/3G (or GPRS).
- the subscription data may be an explicit indication of requesting EPS + 2G/3G (or GPRS) subscription data, or may be through a location update request message. Only explicitly indicating that 2G/3G (or GPRS) subscription data is requested to be launched at the same time, that is, requesting EPS subscription data is default or implicit.
- the S6d interface is defined for the HSS and the SGSN. The S6d interface indicates that the request message must come from the SGSN of the SGSN or the MME/SGSN of the joint node.
- the single node information further excludes the situation of the joint node. Is a single SGSN node;
- Step S1702 The HSS performs a corresponding location update operation check and processing, and returns a location update response message to the requesting node.
- Step S1703 The HSS stores the requested user subscription data type information received in step S1701;
- Step S1704 When the user's 2G/3G (or GPRS) subscription data is updated (including adding, deleting, or modifying), the HSS determines to store The requested user subscription data type information indicates that the request is for EPS subscription data and 2G/3G (or GPRS) subscription data, and the HSS triggers the user data update process;
- Step S1705 The HSS carries the updated 2G/3G (or GPRS) subscription data of the user in the user data update request message and sends the data to the SGSN.
- Step S1704 For example, if the 2G/3G (or GPRS) subscription data update of the user described in step S1704 is that the 2G/3G (or GPRS) subscription data of the user is deleted, the HSS will send the corresponding subscription data deletion. Indicated user data update message. Step S1706: The SGSN returns a user data update response message.
- the HSS receives the location update message and stores the received node type related information.
- the HSS decides to send a user data update request message to the node corresponding to the type according to the stored node type related information.
- the following takes the node type as the MME/SGSN joint node as an example.
- the SGSN supports both the S4-SGSN in the EPS and the SGSN in the 2G/3G.
- the associated MME/SGSN sends its node type related information to the HSS in the location update request through the S6a or S6d interface.
- the node type related information not only indicates that it is a joint node, but also indicates that the UE is in the joint node.
- the MME and SGSN are registered at the same time.
- the HSS stores the information about the node type. When the EPS or 2G/3G subscription data of the corresponding user changes, the HSS determines the stored information about the node type, and determines that only the user data update message is triggered once to the associated node, instead of The user data update message is sent to the MME and the SGSN of the joint node, respectively.
- Step S1801 The set MME/SGSN sends a location update request to the HSS, where the location update request carries node type related information, the node type related information includes indicating that it is a set MME/SGSN node, and indicates that the UE is in the joint node. Information registered at the same time on the MME and the SGSN;
- Step S1802 The HSS performs a corresponding location update operation check and processing, and returns a location update response message to the requesting node.
- Step S1803 The HSS stores the node type related information received in step S1801.
- Step S1804 When the user's EPS or 2G/3G subscription data is updated (including adding, deleting, Or, when the HSS determines that the stored node type related information indicates that it is the joint node MME/SGSN, and the user registers at the same time on the MME and the SGSN of the joint node, the HSS sends only to the MME/SGSN once.
- the user data update request message instead of sending the user data update request message to the MME and the SGSN of the joint node respectively;
- Step S1805 The HSS carries the updated user's EPS or 2G/3G subscription data in the user data update request message. The middle and lower are sent to the MME/SGSN;
- Step S1804 If the EPS or 2G/3G subscription data of the user described in step S1804 is updated, the EPS or 2G/3G partial subscription data of the user is deleted, the HSS may carry a corresponding user data deletion indication in the user data update request message.
- Step S1806 The MME/SGSN returns a user data update response message.
- the requesting data type information of the request carried by the requesting node in the location update request message may indicate that the 2G/3G subscription data is requested, or the GPRS subscription data is requested to be the eighth, and the methods in the ninth and tenth embodiments are also applicable to The scene in which the IWF exists.
- the specific embodiment is easily obtained from a method similar to that described in Embodiment 7, and will not be described again.
- the embodiment of the present invention can not only optimize the location update process, but also enable the node that stores the user subscription data to send the correct type of user subscription data, and can accurately record the location information of the user equipment.
- the HSS/HLR may be configured according to the corresponding The node type information (including the node type related information) or the requested user subscription data type information determines whether to send the user data update request message to the corresponding node, that is, only when the user subscription data corresponding to the corresponding node changes, the HSS/HLR A corresponding user data update request message needs to be sent.
- the HSS does not need to send a user update request message to the MME.
- the MME/SGSN is connected to the node and the UE is simultaneously registered on the MME and the SGSN of the connected node
- the HSS/HLR only needs to send the user data update request message once to the set node, avoiding the MME and the SGSN respectively.
- Send user data update request message effectively reducing HSS and MME or SGSN Signaling interaction between.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A method for performing information interaction with a node having mobility management function in update location procedure is provided. The method includes the following steps: receiving an update location request sent by the node with mobility management function, wherein the update location request piggybacks the type of requested user subscribed data; sending the user subscribed data to the node with mobility management function according to the type of requested user subscribed data. Another method for performing information interaction with a node having mobility management function in update location procedure and a node for storing user subscribed data are also provided.
Description
进行信息交互的方法及存储用户签约数据的节点 Method for information interaction and node for storing user subscription data
本申请要求于 2008 年 8 月 1 日提交中国专利局、 申请号为 200810145082.3、 发明名称为 "进行信息交互的方法、 存储用户签约数据的节 点及具有移动管理功能的节点"的中国专利申请、 于 2009年 4月 10日提交中 国专利局、 申请号为 200910127875.7、 发明名称为 "进行信息交互的方法及存 储用户签约数据的节点"以及于 2009年 5月 18日提交中国专利局、 申请号为 200910141780.0、 发明名称为 "进行信息交互的方法及存储用户签约数据的节 点" 的优先权, 其全部内容通过引用结合在本申请中。 This application claims to be filed on August 1, 2008 with the Chinese Patent Office, application number 200810145082.3, the invention titled "Method for Information Interaction, Node for Storing User Contract Data, and Node with Mobile Management Function", Submitted to the China Patent Office on April 10, 2009, the application number is 200910127875.7, the invention name is "the method of information exchange and the node for storing user subscription data" and submitted to the Chinese Patent Office on May 18, 2009, the application number is 200910141780.0 The invention is entitled "Method of Performing Information Interaction and Node for Storing User Contract Data", the entire contents of which are incorporated herein by reference.
技术领域 Technical field
本发明涉及无线通信技术,尤其涉及在位置更新过程中与具有移动管理功 能的节点进行信息交互的技术。 The present invention relates to wireless communication technologies, and more particularly to techniques for information interaction with nodes having mobility management functions during location update procedures.
背景技术 Background technique
第三代合作伙伴计划 (3GPP, 3rd Generation Partnership Project ) 为了增 强未来网络的竟争能力, 正在研究一种全新的演进网络…演进的分组系统 ( EPS, Evolved Packet System )„ 3GPP, 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) In order to enhance the competitiveness of the future network, a new evolutionary network... Evolved Packet System (EPS) is being studied.
EPS的架构如图 1所示, 包括演进的 UMTS陆地无线接入网(E-UTRAN, Evolved UMTS Terrestrial Radio Access Network ), 用于实现所有与演进网络无 线有关的功能; 移动性管理实体 ( MME, Mobility Management Entity ), 负责 控制面的移动性管理, 包括用户上下文和移动状态管理, 分配用户临时身份标 识等; 服务网关实体( Serving GW, Serving Gateway ), 是 3GPP接入系统间 的用户面锚点, 终止 E-UTRAN的接口; 分组数据网络网关实体(PDN GW, Packet Data Network Gateway )是 3GPP接入系统和非 3GPP接入系统之间的用 户面锚点, 同时终止和外部分组数据网络(PDN, Packet Data Network ) 的接 口。 策略和计费规则功能实体 ( PCRF , Policy and Charging Rule Function )用 于策略控制决定和流计费控制功能。 归属网络服务器(HSS, Home Subscriber Server )用于存储用户签约数据。 MME和 HSS之间的接口是基于 Diameter (用 于实现 AAA功能的协议名称)协议的 S6a, 主要完成用户位置信息、 用户签 约信息和鉴权信息的交互。 在图 1所示的架构中, UMTS陆地无线接入网(UTRAN, UMTS Terrestrial
Radio Access Network )和 GSM/EDGE无线接入网( GERAN, GSM/EDGE Radio Access Network )用于实现所有与现有 GPRS/UMTS网络中无线有关的功能, 服务通用分组无线业务支持节点(SGSN, Serving GPRS Supporting Node ), 用 于实现 GPRS/UMTS网络中路由转发、移动性管理、会话管理以及用户信息存 储等功能。 The architecture of the EPS is as shown in FIG. 1 , including an evolved UMTS Terrestrial Radio Access Network (E-UTRAN) for implementing all functions related to the evolved network radio; a mobility management entity (MME, Mobility Management Entity), responsible for the mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, etc.; Serving GW (Serving Gateway), is the user plane anchor between 3GPP access systems Ending the interface of the E-UTRAN; the Packet Data Network Gateway (PDN GW) is a user plane anchor between the 3GPP access system and the non-3GPP access system, and terminates and the external packet data network (PDN) , Packet Data Network ) interface. The Policy and Charging Rule Function (PCRF) is used for policy control decisions and flow accounting control functions. The Home Subscriber Server (HSS) is used to store user subscription data. The interface between the MME and the HSS is S6a based on the Diameter (Protocol Name for Implementing AAA Function) protocol, and mainly performs interaction of user location information, user subscription information, and authentication information. In the architecture shown in Figure 1, the UMTS Terrestrial Radio Access Network (UTRAN, UMTS Terrestrial Radio Access Network) and GSM/EDGE Radio Access Network (GERAN, GSM/EDGE Radio Access Network) are used to implement all wireless related functions in existing GPRS/UMTS networks, serving General Packet Radio Service Support Nodes (SGSN, Serving) GPRS Supporting Node), used to implement routing and forwarding, mobility management, session management, and user information storage in GPRS/UMTS networks.
GPRS网络在向 EPS演进过程中, SGSN会从原来的支持 Gn/Gp接口(与 GPRS网络中的 SGSN和 GGSN之间的接口 )演进到支持和 Serving GW之间 的 S4接口, SGSN和 HSS之间的接口也会从支持基于移动应用部分(MAP, Mobile Application Part ) 的 Gr接口演进到支持基于 Diameter的 S6d接口。 目前, GPRS网络和 EPS会共存一段时间, 在 EPS中, GERAN/UTRAN 和 E-UTRAN会长期并存, 这样, 完成 GERAN/UTRAN接入控制和会话功能 的 SGSN和完成 E-UTRAN接入控制和会话功能的 MME也会长期共存。 SGSN 和 MME可能分别独立存在, 也可能合设为一个节点。 HSS或归属位置寄存器 ( HLR , Home Location Register )可能会因为协议的版本不同而导致存储的用 户签约数据的类型不同。 在实际应用中, 由于某种或某些原因, SGSN或 MME会向 HSS或 HLR 发出位置更新请求, HSS或 HLR会根据位置更新请求, 向 SGSN或 MME发 送用户签约数据。 本发明的发明人在实现本发明的过程中发现:在 SGSN和 MME共存的情 况下, 当 SGSN、 MME或合设节点 MME/SGSN向 HSS或 HLR发出位置更新 请求时, HSS或 HLR无法确定将何种类型的用户签约数据发送给发出位置更 新请求的节点。 During the evolution of the GPRS network to the EPS, the SGSN will evolve from the original Gn/Gp interface (the interface between the SGSN and the GGSN in the GPRS network) to the S4 interface between the support and the Serving GW, between the SGSN and the HSS. The interface will also evolve from supporting the Gr application based on the Mobile Application Part (MAP) to supporting the Diameter-based S6d interface. At present, the GPRS network and EPS will coexist for a period of time. In the EPS, GERAN/UTRAN and E-UTRAN will coexist for a long time, thus completing the GERAN/UTRAN access control and session function SGSN and completing E-UTRAN access control and session. The functional MME also coexists for a long time. The SGSN and the MME may exist separately or together as one node. The HSS or Home Location Register (HLR, Home Location Register) may result in different types of stored user subscription data due to different versions of the protocol. In an actual application, for some or some reasons, the SGSN or the MME sends a location update request to the HSS or the HLR, and the HSS or the HLR sends the user subscription data to the SGSN or the MME according to the location update request. The inventor of the present invention finds in the process of implementing the present invention that when the SGSN and the MME coexist, when the SGSN, the MME or the MME/SGSN sends a location update request to the HSS or the HLR, the HSS or the HLR cannot determine What type of user subscription data is sent to the node that issued the location update request.
发明内容 Summary of the invention
本发明实施例要解决的一个技术问题是提供在位置更新过程中与具有移 动管理功能的节点进行信息交互的方法及存储用户签约数据的节点,用以当具 有移动管理功能的节点向存储用户签约数据的节点发出位置更新请求时,存储 用户签约数据的节点能够向具有移动管理功能的节点发送正确类型的用户签 约数据。
一种在位置更新过程中与具有移动管理功能的节点进行信息交互的方法, 包括: 接收具有移动管理功能的节点发出的位置更新请求, 所述位置更新请求 携带请求的用户签约数据的类型;根据所述请求的用户签约数据的类型向所述 具有移动管理功能的节点发送用户签约数据。一种在位置更新过程中与具有移 动管理功能的节点进行信息交互的方法, 包括: 接收具有移动管理功能的节点 发出的位置更新请求,所述位置更新请求携带所述具有移动管理功能的节点类 型相关的信息,所述具有移动管理功能的节点类型相关的信息至少包括所述具 有移动管理功能的节点的类型;根据所述具有移动管理功能的节点的类型向所 述具有移动管理功能的节点发送用户签约数据。 A technical problem to be solved by the embodiments of the present invention is to provide a method for performing information interaction with a node having a mobility management function during a location update process, and a node for storing user subscription data, for signing a node with a mobile management function to a storage user. When the node of the data issues a location update request, the node storing the subscriber subscription data can send the correct type of subscriber subscription data to the node having the mobility management function. A method for performing information interaction with a node having a mobility management function during a location update process, comprising: receiving a location update request sent by a node having a mobility management function, where the location update request carries a type of the requested subscriber subscription data; The type of the requested user subscription data sends the user subscription data to the node having the mobility management function. A method for information interaction with a node having a mobility management function during a location update process, comprising: receiving a location update request sent by a node having a mobility management function, the location update request carrying the node type having the mobility management function Related information, the information related to the node type having the mobility management function includes at least the type of the node having the mobility management function; and sending the node having the mobility management function according to the type of the node having the mobility management function User signing data.
一种存储用户签约数据的节点, 包括: 位置更新请求获得单元, 用于接收 具有移动管理功能的节点发出的位置更新请求,所述位置更新请求携带所述具 有移动管理功能的节点的类型相关信息,所述类型相关信息至少包括所述具有 移动管理功能的节点的类型; 用户签约数据发送单元, 用于根据所述位置更新 请求获得单元获得的所述具有移动管理功能的节点的类型,向所述具有移动管 理功能的节点发送用户签约数据。 在本发明实施例中, 具有移动管理功能的节点在发送位置更新请求时, 向 存储用户签约数据的节点提供请求的用户签约数据的类型,或者指明具有移动 管理功能的节点类型相关的信息, 这样,存储用户签约数据的节点就可以根据 具有移动管理功能的节点请求的用户签约数据的类型或具有移动管理功能的 节点的类型, 从而正确发送请求节点需要的用户签约数据。 附图说明 A node for storing user subscription data, comprising: a location update request obtaining unit, configured to receive a location update request sent by a node having a mobility management function, where the location update request carries type information related to the node having the mobility management function The type-related information includes at least the type of the node having the mobility management function; the user subscription data sending unit, configured to obtain, according to the location update request obtaining unit, the type of the node having the mobility management function, The node with the mobility management function sends the user subscription data. In the embodiment of the present invention, when the node having the mobility management function sends the location update request, the node that stores the user subscription data is provided with the type of the user subscription data requested, or the node type information with the mobility management function is specified. The node storing the user subscription data can correctly send the user subscription data required by the requesting node according to the type of the user subscription data requested by the node having the mobility management function or the type of the node having the mobility management function. DRAWINGS
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施 例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地, 下面描述 中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲, 在不付 出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。 In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.
图 1为现有技术的 EPS的架构示意图; 图 2 为本发明实施例的一种在位置更新过程中与存储用户签约数据的节 点进行信息交互的方法流程图;
图 3为本发明实施例的一种具有移动管理功能的节点的结构示意图; 图 4 为本发明实施例的一种在位置更新过程中与具有移动管理功能的节 点进行信息交互的方法流程图; 图 5为本发明实施例的一种存储用户签约数据的节点的结构示意图; 图 6为本发明实施例的一种进行位置更新操作的方法流程图; 1 is a schematic structural diagram of a prior art EPS; FIG. 2 is a flowchart of a method for performing information interaction with a node that stores user subscription data in a location update process according to an embodiment of the present invention; 3 is a schematic structural diagram of a node having a mobility management function according to an embodiment of the present invention; FIG. 4 is a flowchart of a method for performing information interaction with a node having a mobility management function in a location update process according to an embodiment of the present invention; FIG. 5 is a schematic structural diagram of a node for storing user subscription data according to an embodiment of the present invention; FIG. 6 is a flowchart of a method for performing a location update operation according to an embodiment of the present invention;
图 7为本发明实施例的另一种存储用户签约数据的节点的结构示意图; 图 8为本发明实施例的第一种典型实施例的流程图; 图 9为本发明实施例的第二种典型实施例的流程图; FIG. 7 is a schematic structural diagram of another node storing user subscription data according to an embodiment of the present invention; FIG. 8 is a flowchart of a first exemplary embodiment of the present invention; FIG. 9 is a second embodiment of the present invention; Flow chart of an exemplary embodiment;
图 10为本发明实施例的第三种典型实施例的流程图; 图 11为本发明实施例的第四种典型实施例的流程图; 图 12为本发明实施例的第五种实施例的流程图; 图 13为本发明实施例的第六种实施例的流程图; 图 14为本发明实施例的第七种实施例的流程图; 图 15为本发明实施例的另一种存储用户签约数据的节点的结构示意图。 图 16为本发明实施例的第八种实施例的流程图; 图 17为本发明实施例的第九种实施例的流程图; 图 18为本发明实施例的第十种实施例的流程图。 10 is a flowchart of a third exemplary embodiment of the present invention; FIG. 11 is a flowchart of a fourth exemplary embodiment of the present invention; FIG. 12 is a flowchart of a fifth embodiment of the present invention; Figure 13 is a flowchart of a sixth embodiment of the present invention; Figure 14 is a flowchart of a seventh embodiment of the present invention; Figure 15 is another storage user according to an embodiment of the present invention; Schematic diagram of the node of the contract data. Figure 16 is a flowchart of an eighth embodiment of the present invention; Figure 17 is a flowchart of a ninth embodiment of the present invention; Figure 18 is a flowchart of a tenth embodiment of the present invention; .
具体实施方式 detailed description
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。基于本发明中的实施例, 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。 BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.
首先结合图 2 , 对本发明实施例的一种在位置更新过程中与存储用户签约 数据的节点进行信息交互的方法进行说明。 如图 2所示, 包括: 步骤 S201 : 向存储用户签约数据的节点发出位置更新请求, 所述位置更
新请求携带发出所述位置更新请求的具有移动管理功能的节点类型相关的信 息 ,所述具有移动管理功能的节点类型相关的信息至少包括所述发送位置更新 的具有移动管理功能的节点的类型,所述具有移动管理功能的节点的类型可以 直接指示所述节点的类型,也可以通过请求对某节点类型进行位置更新操作的 指示来明确,例如在所述具有移动管理功能的节点为合设节点 MME/ SGSN的 情况下,所述位置更新请求携带的所述位置更新请求的具有移动管理功能的节 点类型相关的信息可以为请求对 MME和 SGSN同时进行位置更新操作的指 示。 步骤 S202: 获得所述存储用户签约数据的节点根据所述具有移动管理功 能的节点的类型发送的用户签约数据。 所述位置更新请求还可以携带发出所述位置更新请求的具有移动管理功 能的节点所需要的用户签约数据的类型 ,获得所述存储用户签约数据的节点根 据所述具有移动管理功能的节点的类型发送的用户签约数据时,可以获得所述 存储用户签约数据的节点根据所述具有移动管理功能的节点的类型及所需要 的用户签约数据的类型发送的用户签约数据, 或者说,存储用户签约数据的节 点在发送用户签约数据时, 除需要考虑具有移动管理功能的节点的类型外,还 需要考虑具有移动管理功能的节点所需要的用户签约数据的类型, 一般来说, 存储用户签约数据的节点会发送具有移动管理功能的节点所需要的类型的用 户签约数据。 如果发出所述位置更新请求的具有移动管理功能的节点为 MME 或First, with reference to FIG. 2, a method for performing information interaction with a node that stores user subscription data in a location update process according to an embodiment of the present invention will be described. As shown in FIG. 2, the method includes: Step S201: Send a location update request to a node that stores user subscription data, where the location is further The new request carries information related to the node type having the mobility management function that issues the location update request, and the information related to the node type having the mobility management function includes at least the type of the node with the mobility management function of the sending location update, The type of the node having the mobility management function may directly indicate the type of the node, or may be clarified by requesting an indication of a location update operation on a certain node type, for example, the node having the mobility management function is a joint node. In the case of the MME/SGSN, the information about the node type with the mobility management function of the location update request carried by the location update request may be an indication of requesting simultaneous location update operations for the MME and the SGSN. Step S202: Obtain the user subscription data sent by the node storing the user subscription data according to the type of the node having the mobility management function. The location update request may further carry a type of user subscription data required by the node with the mobility management function that issues the location update request, and obtain the type of the node that stores the user subscription data according to the node with the mobility management function. When the user subscription data is sent, the node that stores the user subscription data may obtain the user subscription data sent according to the type of the node having the mobility management function and the type of the user subscription data required, or store the user subscription data. When transmitting the user subscription data, in addition to the type of the node having the mobility management function, the node needs to consider the type of the user subscription data required by the node having the mobility management function. Generally, the node storing the user subscription data User subscription data of the type required by the node with mobility management is sent. If the node with mobility management function that issues the location update request is MME or
SGSN, 且所需要的用户签约数据的类型为 MME对应类型的用户签约数据和 SGSN对应类型的用户签约数据, 则获得的用户签约数据是 MME对应类型的 用户签约数据和 SGSN对应类型的用户签约数据。或者说, 当具有移动管理功 能的节点是独立的 MME或独立的 SGSN时,如果独立的 MME或独立的 SGSN 要求获得所有类型的用户签约数据,则存储用户签约数据的节点会将所有类型 的用户签约数据发送给独立的 MME或独立的 SGSN。 如果发出所述位置更新 请求的具有移动管理功能的节点为 MME, 且所述 MME获得的用户签约数据 是 MME对应类型的用户签约数据和 SGSN对应类型的用户签约数据,则当用
户设备切换到 SGSN为其提供服务时,所述 MME会将 SGSN对应类型的用户 签约数据发送给 SGSN,而无须 SGSN向存储用户签约数据的节点请求对应类 型的用户签约数据;如果发出所述位置更新请求的具有移动管理功能的节点为 SGSN, 且所述 SGSN获得的用户签约数据是 MME对应类型的用户签约数据 和 SGSN对应类型的用户签约数据,则当用户设备切换到 MME为其提供服务 时, 所述 SGSN会将 MME对应类型的用户签约数据发送给 MME, 而无须 MME向存储用户签约数据的节点请求对应类型的用户签约数据。 如果发出所述位置更新请求的具有移动管理功能的节点为合设节点 MME/SGSN, 且用户设备通过 MME和 SGSN中的一个实体进行位置更新时, 则所述位置更新请求携带的具有移动管理功能的节点类型相关的信息还表示 需要所述存储用户签约数据的节点优先考虑进行位置更新操作的方式。进一步 来说, 合设节点 MME/SGSN这种类型可以有多种表现形式, 不同的表现形式 可以表示不同的信息, 例如, MME/SGSN可以表示用户设备是通过 MME进 行位置更新的, 那么存储用户签约数据的节点在进行位置更新操作时,应该优 先进行与 MME对应的位置更新操作, 发送用户签约数据时, 可以优先考虑将 与 MME对应类型的用户签约数据发送给合设节点 MME/SGSN。 当然, 如果 合设节点 MME/SGSN 没有特别要求, 存储用户签约数据的节点一般会将与 MME对应类型的用户签约数据和与 SGSN对应类型的用户签约数据一同发送 给合设节点 MME/SGSN。 如果所述位置更新请求携带的具有移动管理功能的 节点类型相关的信息还表示需要所述存储用户签约数据的节点优先考虑进行 位置更新操作的方式, 则根据所述需要优先考虑的方式进行位置更新操作, 即 优先进行需要优先考虑的节点的位置更新操作 ,再执行不被优先考虑的节点的 位置更新操作; 如果成功执行了需要优先考虑的节点的位置更新操作, 未成功 执行不被优先考虑的节点的位置更新操作,返回位置更新操作响应以表明仅执 行了需要优先考虑的节点的位置更新操作。 如果发出所述位置更新请求的具有移动管理功能的节点为合设节点 MME/SGSN, 且合设节点 MME/SGSN中的 MME和 SGSN的地址不相同, 则 所述位置更新请求还携带 MME的地址和 SGSN的地址,以便于存储用户签约 数据的节点记录 MME的地址和 SGSN的地址。
如果所述位置更新请求携带的合设节点 MME/SGSN的类型还表示需要所 述存储用户签约数据的节点优先考虑进行位置更新操作的方式对应的是 MME , 则在所述位置更新请求中可以单独使用一个参数表示未被优先考虑的 SGSN的地址; 如果所述位置更新请求携带的合设节点 MME/SGSN的类型还 表示需要所述存储用户签约数据的节点优先考虑进行位置更新操作的方式对 应的是 SGSN, 则在所述位置更新请求中单独使用一个参数表示未被优先考虑 的 MME的地址。 需要说明的是, 现有技术中的位置更新请求中已经包括一个 具有移动管理功能的节点的地址, 当具有移动管理功能的节点是合设节点 MME/SGSN时, 可以使用所述现有的地址来表示 MME/SGSN中的一个实体 的地址, 另一个实体的地址可以单独使用一个参数表示, 当然单独使用的参数 也携带在位置更新请求中。 如果具有移动管理功能的节点与存储用户签约数据的节点之间设置有具 有协议转换功能的节点,则向存储用户签约数据的节点发出的位置更新请求通 过具有协议转换功能的节点到达存储用户签约数据的节点 ,获得的用户签约数 据是通过具有协议转换功能的节点获得的用户签约数据。 例如, MME/SGSN 与 HSS/HLR 之间可能设置有互通功能 ( IWF , Interworking Function ) , MME/SGSN与 IWF之间釆用的^^于 Diameter协议的 S6a/S6d接口, HSS/HLR 与 IWF之间釆用的是基于 MAP的 Gr/Gr+接口, IWF主要完成协议转换的功 能。 当 MME/SGSN向 HSS/HLR发送位置更新请求时, MME/SGSN会向 IWF 发送基于 Diameter协议的位置更新请求, IWF再向 HSS/HLR发送基于 MAP 的位置更新请求;当 HSS/HLR向 MME/SGSN发送位置更新响应时, HSS/HLR 会向 IWF发送基于 MAP的位置更新响应, IWF再向 MME/SGSN发送基于 Diameter协议的位置更新响应。 需要说明的是,上述步骤 S201和 S202的执行主体可以是具有移动管理功 能的节点, 例如 MME、 SGSN或合设节点 MME/SGSN, 存储用户签约数据的 节点可以是 HSS或 HLR。 另外, 存储用户签约数据的节点向具有移动管理功 动管理功能的节点发送的位置更新响应中。
对应于图 2 所示的方法, 本发明实施例提供一种具有移动管理功能的节 点。 如图 3所示, 这种具有移动管理功能的节点包括: 位置更新请求发送单元 301 , 用于向存储用户签约数据的节点发出位置更新请求, 所述位置更新请求 携带所述具有移动管理功能的节点类型相关信息,所述具有移动管理功能的节 点类型相关的信息至少包括发送位置更新的所述具有移动管理功能的节点的 类型; 用户签约数据获得单元 302, 用于在所述位置更新请求发送单元 301发 出位置更新请求后 ,获得所述存储用户签约数据的节点根据所述具有移动管理 功能的节点的类型发送的用户签约数据。 The SGSN, and the type of the user subscription data required by the MME is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, and the obtained user subscription data is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type. . In other words, when the node with the mobility management function is an independent MME or a separate SGSN, if the independent MME or the independent SGSN requires all types of user subscription data, the node storing the user subscription data will be all types of users. The subscription data is sent to an independent MME or a separate SGSN. If the node with the mobility management function that sends the location update request is the MME, and the user subscription data obtained by the MME is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, then When the user equipment is switched to provide services for the SGSN, the MME sends the user subscription data of the SGSN corresponding type to the SGSN, and the SGSN does not need to request the user type subscription data of the corresponding type to the node storing the user subscription data; The node with the mobility management function of the update request is the SGSN, and the user subscription data obtained by the SGSN is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, when the user equipment switches to the MME for providing the service. The SGSN sends the user subscription data of the MME corresponding type to the MME, and the MME does not need to request the user subscription data of the corresponding type to the node that stores the user subscription data. If the node with the mobility management function that sends the location update request is the MME/SGSN, and the user equipment performs location update through one of the MME and the SGSN, the location update request carries the mobility management function. The node type related information also indicates that the node that needs to store the user subscription data prioritizes the manner in which the location update operation is performed. Further, the type of the MME/SGSN may have multiple representations, and different representations may represent different information. For example, the MME/SGSN may indicate that the user equipment is updated by the MME, and then the user is stored. When performing the location update operation, the node of the subscription data should preferentially perform the location update operation corresponding to the MME. When the user subscription data is transmitted, the subscriber subscription data of the type corresponding to the MME can be preferentially transmitted to the associated node MME/SGSN. Of course, if there is no special requirement for the MME/SGSN, the node storing the user subscription data generally sends the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN to the MME/SGSN. If the information related to the node type with the mobility management function carried in the location update request indicates that the node that needs to store the user subscription data preferentially considers the manner of performing the location update operation, the location update is performed according to the priority manner. Operation, that is, prioritizing the location update operation of the node that needs to be prioritized, and then performing the location update operation of the node that is not prioritized; if the location update operation of the node that needs priority is successfully performed, the unsuccessful execution is not prioritized. The location update operation of the node returns a location update operation response to indicate that only the location update operation of the node that needs to be prioritized is performed. If the node with the mobility management function that sends the location update request is the MME/SGSN, and the addresses of the MME and the SGSN in the MME/SGSN are not the same, the location update request also carries the address of the MME. And the address of the SGSN, so that the node storing the user subscription data records the address of the MME and the address of the SGSN. If the type of the MME/SGSN carried in the location update request indicates that the node that needs to store the user subscription data preferentially considers that the location update operation corresponds to the MME, the location update request may be separately Using one parameter to indicate the address of the SGSN that is not prioritized; if the type of the associated node MME/SGSN carried by the location update request further indicates that the node that needs to store the user subscription data preferentially considers the manner of performing the location update operation In the SGSN, a parameter is used alone in the location update request to indicate the address of the MME that is not prioritized. It should be noted that the address update request in the prior art already includes an address of a node having a mobility management function, and when the node having the mobility management function is the joint node MME/SGSN, the existing address may be used. To represent the address of one entity in the MME/SGSN, the address of another entity can be represented by a single parameter, and of course the parameters used separately are also carried in the location update request. If a node having a mobility management function and a node storing the user subscription data are provided with a node having a protocol conversion function, the location update request sent to the node storing the user subscription data reaches the storage user subscription data through the node having the protocol conversion function. The obtained user subscription data is user subscription data obtained through a node having a protocol conversion function. For example, an interworking function (IWF, Interworking Function) may be set between the MME/SGSN and the HSS/HLR, and an S6a/S6d interface between the MME/SGSN and the IWF, which is used by the Diameter protocol, and the HSS/HLR and the IWF. The MAP-based Gr/Gr+ interface is used, and the IWF mainly performs the function of protocol conversion. When the MME/SGSN sends a location update request to the HSS/HLR, the MME/SGSN sends a location update request based on the Diameter protocol to the IWF, and the IWF sends a MAP-based location update request to the HSS/HLR; when the HSS/HLR is directed to the MME/ When the SGSN sends a location update response, the HSS/HLR sends a MAP-based location update response to the IWF, and the IWF sends a location update response based on the Diameter protocol to the MME/SGSN. It should be noted that the execution body of the foregoing steps S201 and S202 may be a node having a mobility management function, such as an MME, an SGSN, or a joint node MME/SGSN, and the node storing the subscriber subscription data may be an HSS or an HLR. In addition, the node storing the user subscription data is sent to the location update response sent by the node having the mobility management function management function. Corresponding to the method shown in FIG. 2, an embodiment of the present invention provides a node with a mobility management function. As shown in FIG. 3, the node having the mobility management function includes: a location update request sending unit 301, configured to send a location update request to a node that stores user subscription data, where the location update request carries the mobility management function The node type related information, the information related to the node type having the mobility management function includes at least the type of the node having the mobility management function for transmitting the location update, and the user subscription data obtaining unit 302, configured to send the location update request After the unit 301 issues a location update request, the node that stores the user subscription data obtains the user subscription data sent according to the type of the node with the mobility management function.
在图 3所示的具有移动管理功能的节点为合设节点 MME/ SGSN的情况 下,位置更新请求发送单元 301发送的位置更新请求携带的发出所述位置更新 请求的具有移动管理功能的节点类型相关的信息可以为请求对 MME和 SGSN 同时进行位置更新操作的指示。位置更新请求发送单元 301发送的位置更新请 求还可以携带图 3 所示的具有移动管理功能的节点所需要的用户签约数据的 类型, 用户签约数据获得单元 302获得所述存储用户签约数据的节点根据图 3 所示的具有移动管理功能的节点的类型发送的用户签约数据时,可以获得所述 存储用户签约数据的节点根据图 3 所示的具有移动管理功能的节点的类型及 所需要的用户签约数据的类型发送的用户签约数据, 或者说,存储用户签约数 据的节点在发送用户签约数据时,除需要考虑具有移动管理功能的节点的类型 夕卜,还需要考虑具有移动管理功能的节点所需要的用户签约数据的类型, 一般 来说,存储用户签约数据的节点会发送具有移动管理功能的节点所需要的类型 的用户签约数据。 如果图 3所示的具有移动管理功能的节点为 MME或 SGSN, 且所需要的 用户签约数据的类型为 MME对应类型的用户签约数据和 SGSN对应类型的用 户签约数据,则用户签约数据获得单元 302获得的用户签约数据是 MME对应 类型的用户签约数据和 SGSN对应类型的用户签约数据。或者说, 当图 3所示 的具有移动管理功能的节点是独立的 MME或独立的 SGSN时, 如果独立的 MME或独立的 SGSN要求获得所有类型的用户签约数据, 则存储用户签约数 据的节点会将所有类型的用户签约数据发送给独立的 MME或独立的 SGSN。 如果图 3所示的具有移动管理功能的节点为 MME, 且所述 MME获得的用户
签约数据是 MME对应类型的用户签约数据和 SGSN对应类型的用户签约数 据, 则当用户设备切换到 SGSN为其提供服务时, 所述 MME会将 SGSN对应 类型的用户签约数据发送给 SGSN, 而无须 SGSN向存储用户签约数据的节点 请求对应类型的用户签约数据; 如果图 3 所示的具有移动管理功能的节点为 SGSN, 且所述 SGSN获得的用户签约数据是 MME对应类型的用户签约数据 和 SGSN对应类型的用户签约数据,则当用户设备切换到 MME进行位置更新 时, 所述 SGSN会将 MME对应类型的用户签约数据发送给 MME, 而无须 MME向存储用户签约数据的节点请求对应类型的用户签约数据。 如果图 3所示的具有移动管理功能的节点为合设节点 MME/SGSN, 且用 户设备通过 MME和 SGSN中的一个实体进行位置更新时,则位置更新请求发 送单元 301 发出的位置更新请求携带的具有移动管理功能的节点类型相关的 信息还表示需要所述存储用户签约数据的节点优先考虑进行位置更新操作的 方式和需要所述存储用户签约数据的节点发送的用户签约数据的类型。进一步 来说, 合设节点 MME/SGSN这种类型可以有多种表现形式, 不同的表现形式 可以表示不同的信息, 例如, MME/SGSN可以表示用户设备是通过 MME进 行位置更新的, 那么存储用户签约数据的节点在进行位置更新操作时,应该优 先进行与 MME对应的位置更新操作, 发送用户签约数据时, 可以优先考虑将 与 MME对应类型的用户签约数据发送给合设节点 MME/SGSN。 当然, 如果 合设节点 MME/SGSN 没有特别要求, 存储用户签约数据的节点一般会将与 MME对应类型的用户签约数据和与 SGSN对应类型的用户签约数据一同发送 给合设节点 MME/SGSN。 如果图 3所示的具有移动管理功能的节点为合设节点 MME/SGSN, 且合 设节点 MME/SGSN中的 MME和 SGSN的地址不相同, 则位置更新请求发送 单元 301发出的位置更新请求还携带 MME的地址和 SGSN的地址,以便于存 储用户签约数据的节点记录 MME的地址和 SGSN的地址。 如果图 3所示的合设节点 MME/SGSN的类型还表示需要所述存储用户签 约数据的节点优先考虑进行位置更新操作的方式对应的是 MME, 则在所述位 置更新请求中可以单独使用一个参数表示 SGSN的地址;如果位置更新请求发
送单元 301发出的位置更新请求携带的合设节点 MME/SGSN的类型还表示需 要所述存储用户签约数据的节点优先考虑进行位置更新操作的方式对应的是 SGSN, 则在所述位置更新请求中单独使用一个参数表示 MME的地址。 如果图 3 所示的具有移动管理功能的节点与存储用户签约数据的节点之 间设置有具有协议转换功能的节点,则位置更新请求发送单元 301向存储用户 签约数据的节点发出的位置更新请求通过具有协议转换功能的节点到达存储 用户签约数据的节点,用户签约数据获得单元 302获得的用户签约数据是通过 具有协议转换功能的节点获得的用户签约数据。 In the case where the node having the mobility management function shown in FIG. 3 is the joint node MME/SGSN, the node type with the mobility management function that issues the location update request carried by the location update request sent by the location update request transmitting unit 301 The related information may be an indication of requesting simultaneous location update operations for the MME and the SGSN. The location update request sent by the location update request sending unit 301 may further carry the type of the user subscription data required by the node having the mobility management function shown in FIG. 3, and the user subscription data obtaining unit 302 obtains the node storing the user subscription data according to the node. When the user subscription data sent by the type of the node with the mobility management function shown in FIG. 3 is obtained, the node that stores the user subscription data can obtain the type of the node with the mobility management function shown in FIG. 3 and the required user subscription. The user subscription data sent by the type of the data, or the node storing the user subscription data, in addition to the type of the node having the mobility management function, needs to consider the node having the mobility management function when transmitting the user subscription data. The type of user subscription data, in general, the node storing the user subscription data will send the user subscription data of the type required by the node with the mobility management function. If the node with the mobility management function shown in FIG. 3 is the MME or the SGSN, and the type of the user subscription data required is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, the user subscription data obtaining unit 302 The obtained user subscription data is user subscription data corresponding to the MME type and user subscription data corresponding to the SGSN type. In other words, when the node with the mobility management function shown in FIG. 3 is an independent MME or a separate SGSN, if the independent MME or the independent SGSN requests to obtain all types of user subscription data, the node that stores the user subscription data will All types of user subscription data are sent to a separate MME or a separate SGSN. If the node with the mobility management function shown in FIG. 3 is the MME, and the user obtained by the MME The subscription data is the user subscription data of the corresponding type of the MME and the user subscription data of the corresponding type of the SGSN. When the user equipment switches to the SGSN to provide the service, the MME sends the subscription data of the corresponding type of the SGSN to the SGSN, without The SGSN requests the node that stores the user subscription data to request the corresponding type of user subscription data; if the node with the mobility management function shown in FIG. 3 is the SGSN, and the user subscription data obtained by the SGSN is the user subscription data of the MME corresponding type and the SGSN. Corresponding type of user subscription data, when the user equipment switches to the MME for location update, the SGSN sends the user subscription data of the MME corresponding type to the MME, and the MME does not need to request the corresponding type of user from the node that stores the user subscription data. Signing data. If the node with the mobility management function shown in FIG. 3 is the MME/SGSN, and the user equipment performs location update through one of the MME and the SGSN, the location update request sending unit 301 sends the location update request. The node type related information having the mobility management function also indicates that the node that needs to store the user subscription data preferentially considers the manner of performing the location update operation and the type of the user subscription data sent by the node that needs to store the subscriber subscription data. Further, the type of the MME/SGSN may have multiple representations, and different representations may represent different information. For example, the MME/SGSN may indicate that the user equipment is updated by the MME, and then the user is stored. When performing the location update operation, the node of the subscription data should preferentially perform the location update operation corresponding to the MME. When the user subscription data is transmitted, the subscriber subscription data of the type corresponding to the MME can be preferentially transmitted to the associated node MME/SGSN. Of course, if there is no special requirement for the MME/SGSN, the node storing the user subscription data generally sends the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN to the MME/SGSN. If the node with the mobility management function shown in FIG. 3 is the joint node MME/SGSN, and the addresses of the MME and the SGSN in the joint node MME/SGSN are not the same, the location update request sent by the location update request sending unit 301 is further The address of the MME and the address of the SGSN are carried, so that the node storing the subscriber subscription data records the address of the MME and the address of the SGSN. If the type of the MME/SGSN shown in FIG. 3 also indicates that the node that needs to store the user subscription data preferentially considers the MME to perform the location update operation, one of the location update requests may be used alone. The parameter indicates the address of the SGSN; if the location update request is sent The type of the MME/SGSN carried in the location update request sent by the sending unit 301 also indicates that the node that needs to store the user subscription data preferentially considers the location update operation corresponding to the SGSN, and in the location update request A parameter is used alone to indicate the address of the MME. If a node having a mobility management function and a node storing the user subscription data shown in FIG. 3 are provided with a node having a protocol conversion function, the location update request transmitting unit 301 passes the location update request issued by the node storing the user subscription data. The node having the protocol conversion function reaches the node storing the user subscription data, and the user subscription data obtained by the user subscription data obtaining unit 302 is the user subscription data obtained through the node having the protocol conversion function.
需要说明的是, 图 3所示的具有移动管理功能的节点可以 MME、 SGSN 或合设节点 MME/SGSN,存储用户签约数据的节点可以是 HSS或 HLR。另夕卜, 用户签约数据获得单元 302 获得的用户签约数据可以携带于存储用户签约数 据的节点向图 3所示的具有移动管理功能的节点发送的位置更新响应中。 本发明实施例还提供一种在位置更新过程中与具有移动管理功能的节点 进行信息交互的方法。 如图 4所示, 包括: 步骤 S401 : 获得具有移动管理功能的节点发出的位置更新请求, 所述位 置更新请求携带所述具有移动管理功能的节点类型相关的信息,所述具有移动 管理功能的节点类型相关的信息至少包括所述具有移动管理功能的节点的类 型。 步骤 S402: 根据所述具有移动管理功能的节点的类型向所述具有移动管 理功能的节点发送用户签约数据。 It should be noted that the node with the mobility management function shown in FIG. 3 may be the MME, the SGSN, or the joint node MME/SGSN, and the node storing the subscriber subscription data may be an HSS or an HLR. In addition, the user subscription data obtained by the user subscription data obtaining unit 302 may be carried in a location update response sent by the node storing the subscriber subscription data to the node having the mobility management function shown in FIG. Embodiments of the present invention also provide a method for performing information interaction with a node having a mobility management function during a location update process. As shown in FIG. 4, the method includes: Step S401: Obtain a location update request sent by a node with a mobility management function, where the location update request carries information about a node type having a mobility management function, where the mobility management function is The node type related information includes at least the type of the node having the mobility management function. Step S402: Send user subscription data to the node having the mobility management function according to the type of the node having the mobility management function.
所述位置更新请求还可以携带所述具有移动管理功能的节点所需要的用 户签约数据的类型。如果所述位置更新请求还携带所述具有移动管理功能的节 点所需要的用户签约数据的类型,则根据所述具有移动管理功能的节点的类型 向所述具有移动管理功能的节点发送用户签约数据时,根据所述具有移动管理 功能的节点的类型和所需要的用户签约数据的类型向所述具有移动管理功能 的节点发送用户签约数据。 或者说, 在发送用户签约数据时, 除需要考虑具有 移动管理功能的节点的类型外,还需要考虑具有移动管理功能的节点所需要的 用户签约数据的类型, 一般来说, 向所述具有移动管理功能的节点发送的用户
签约数据都是具有移动管理功能的节点所需要的类型的用户签约数据。 The location update request may also carry the type of user subscription data required by the node having the mobility management function. If the location update request further carries the type of user subscription data required by the node having the mobility management function, sending the user subscription data to the node having the mobility management function according to the type of the node having the mobility management function At the time, the user subscription data is transmitted to the node having the mobility management function according to the type of the node having the mobility management function and the type of the user subscription data required. In other words, when sending user subscription data, in addition to considering the type of the node having the mobility management function, it is also necessary to consider the type of user subscription data required by the node having the mobility management function, and generally, to have the mobile User sent by the node that manages the function The subscription data is the type of user subscription data required by the node with mobility management capabilities.
如果所述具有移动管理功能的节点为 MME或 SGSN, 且所需要的用户签 约数据的类型为 MME对应类型的用户签约数据和 SGSN对应类型的用户签约 数据,则向所述具有移动管理功能的节点发送的用户签约数据是 MME对应类 型的用户签约数据和 SGSN对应类型的用户签约数据;如果发出所述位置更新 请求的具有移动管理功能的节点为 MME, 则当用户设备切换到 SGSN为其提 供服务时, 所述 MME将 SGSN对应类型的用户签约数据发送给 SGSN; 如果 发出所述位置更新请求的具有移动管理功能的节点为 SGSN, 则当用户设备切 换到 MME为其提供服务时,所述 SGSN将 MME对应类型的用户签约数据发 送给 MME。 If the node with the mobility management function is the MME or the SGSN, and the type of the user subscription data required is the user subscription data of the MME corresponding type and the user subscription data of the SGSN corresponding type, the node with the mobility management function is used. The user subscription data sent by the MME is the user subscription data of the corresponding type of the MME and the user subscription data of the SGSN corresponding type; if the node with the mobility management function that issues the location update request is the MME, the user equipment switches to the SGSN to provide the service. The MME sends the subscriber subscription data of the SGSN corresponding type to the SGSN; if the node with the mobility management function that sends the location update request is the SGSN, when the user equipment switches to provide services for the MME, the SGSN The user subscription data of the MME corresponding type is sent to the MME.
如果所述位置更新请求携带的具有移动管理功能的节点类型相关的信息 还表示需要优先考虑进行位置更新操作的方式, 则在进行位置更新操作时,根 据所述需要优先考虑的方式进行位置更新操作。如果所述位置更新请求携带的 具有移动管理功能的节点类型相关的信息还表示需要优先考虑的用户签约数 据的类型, 则在发送用户签约数据时,根据所述需要优先考虑的用户签约数据 的类型发送用户签约数据。进一步来说,如果具有移动管理功能的节点是合设 节点 MME/SGSN, 则合设节点 MME/SGSN这种类型可以有多种表现形式, 不同的表现形式可以表示不同的信息, 例如, MME/SGSN可以表示用户设备 是通过 MME进行位置更新的, 那么在进行位置更新操作时, 应该优先进行与 MME对应的位置更新操作, 发送用户签约数据时, 可以优先考虑将与 MME 对应类型的用户签约数据发送给合设节点 MME/SGSN。 当然, 如果合设节点 MME/SGSN没有特别要求, 那么一般会将与 MME对应类型的用户签约数据 和与 SGSN对应类型的用户签约数据一同发送给合设节点 MME/SGSN。 如果发出所述位置更新请求的具有移动管理功能的节点为合设节点 MME/SGSN,合设节点 MME/SGSN中的 MME和 SGSN的地址不相同、 并且 所述位置更新请求还携带 MME的地址和 SGSN的地址,则存储用户签约数据 的节点在获得具有移动管理功能的节点发出的位置更新请求后, 还要记录 MME的地址和 SGSN的地址。
如果发出所述位置更新请求的具有移动管理功能的节点为合设节点 MME/SGSN, 且所述位置更新请求携带的具有移动管理功能的节点类型相关 的信息表示需要优先考虑进行位置更新操作的方式对应的是 MME, 则在所述 位置更新请求中单独使用一个参数表示 SGSN的地址;如果所述位置更新请求 携带的具有移动管理功能的节点类型相关的信息表示需要优先考虑进行位置 更新操作的方式对应的是 SGSN, 则在所述位置更新请求中单独使用一个参数 表示 MME的地址。 If the information related to the node type with the mobility management function carried in the location update request indicates that the location update operation needs to be prioritized, when the location update operation is performed, the location update operation is performed according to the priority consideration manner. . If the information related to the node type of the mobile management function carried by the location update request further indicates the type of user subscription data that needs to be prioritized, when the user subscription data is sent, according to the type of the user subscription data that needs to be prioritized Send user subscription data. Further, if the node with the mobility management function is the MME/SGSN, the type of the MME/SGSN may have multiple representations, and different representations may represent different information, for example, MME/ The SGSN may indicate that the user equipment is updated by the MME. Therefore, when performing the location update operation, the location update operation corresponding to the MME should be preferentially performed. When the user subscription data is sent, the user subscription data of the type corresponding to the MME may be preferentially considered. Send to the set node MME/SGSN. Of course, if there is no special requirement for the MME/SGSN, the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN are generally sent to the MME/SGSN. If the node with the mobility management function that issues the location update request is the joint node MME/SGSN, the addresses of the MME and the SGSN in the setup node MME/SGSN are not the same, and the location update request also carries the address of the MME and The address of the SGSN, after the node storing the subscriber subscription data obtains the location update request sent by the node with the mobility management function, records the address of the MME and the address of the SGSN. If the node with the mobility management function that issues the location update request is the joint node MME/SGSN, and the information related to the node type with the mobility management function carried by the location update request indicates that the location update operation needs to be prioritized Corresponding to the MME, a parameter is used to indicate the address of the SGSN in the location update request; if the information related to the node type with the mobility management function carried in the location update request indicates that the location update operation needs to be prioritized Corresponding to the SGSN, a parameter is used to indicate the address of the MME in the location update request.
如果与具有移动管理功能的节点与存储用户签约数据的节点之间设置有 具有协议转换功能的节点 ,则获得的具有移动管理功能的节点发出的位置更新 请求是通过具有协议转换功能的节点获得的 ,向所述具有移动管理功能的节点 发送的用户签约数据是通过具有协议转换功能的节点到达所述具有移动管理 功能的节点的。 If a node having a protocol conversion function is provided between a node having a mobility management function and a node that stores user subscription data, the obtained location update request issued by the node having the mobility management function is obtained by a node having a protocol conversion function. The user subscription data sent to the node having the mobility management function is reached by the node having the protocol conversion function to the node having the mobility management function.
需要说明的是,上述步骤 S401和 S402的执行主体可以是存储用户签约数 据的节点,例如是 HSS或 HLR,具有移动管理功能的节点可以是 MME、 SGSN 或合设节点 MME/SGSN。 另外, 存储用户签约数据的节点向具有移动管理功 动管理功能的节点发送的位置更新响应中。 对应于图 4 所示的方法, 本发明实施例提供一种存储用户签约数据的节 点。 如图 5所示, 这种存储用户签约数据的节点包括: 位置更新请求获得单元 501 , 用于获得具有移动管理功能的节点发出的位置更新请求, 所述位置更新 请求携带所述具有移动管理功能的节点类型相关的信息,所述具有移动管理功 能的节点类型相关的信息至少包括发送位置更新的所述具有移动管理功能的 节点的类型; 用户签约数据发送单元 502, 用于根据所述位置更新请求获得单 元 501获得的所述具有移动管理功能的节点的类型,向所述具有移动管理功能 的节点发送用户签约数据。 位置更新请求获得单元 501 获得的位置更新请求还可以携带所述具有移 动管理功能的节点所需要的用户签约数据的类型。如果所述位置更新请求还携 带所述具有移动管理功能的节点所需要的用户签约数据的类型,则用户签约数
据发送单元 502根据所述具有移动管理功能的节点的类型向所述具有移动管 理功能的节点发送用户签约数据时,根据所述具有移动管理功能的节点的类型 和所需要的用户签约数据的类型向所述具有移动管理功能的节点发送用户签 约数据。 或者说, 用户签约数据发送单元 502在发送用户签约数据时, 除需要 考虑具有移动管理功能的节点的类型外,还需要考虑具有移动管理功能的节点 所需要的用户签约数据的类型, 一般来说, 用户签约数据发送单元 502向所述 具有移动管理功能的节点发送的用户签约数据都是具有移动管理功能的节点 所需要的类型的用户签约数据。 It should be noted that the execution body of the foregoing steps S401 and S402 may be a node that stores user subscription data, such as an HSS or an HLR, and a node having a mobility management function may be an MME, an SGSN, or a joint node MME/SGSN. In addition, the node storing the user subscription data is sent to the location update response sent by the node having the mobility management function management function. Corresponding to the method shown in FIG. 4, an embodiment of the present invention provides a node that stores user subscription data. As shown in FIG. 5, the node for storing user subscription data includes: a location update request obtaining unit 501, configured to obtain a location update request sent by a node having a mobility management function, where the location update request carries the mobility management function Information related to the node type, the information related to the node type having the mobility management function includes at least the type of the node having the mobility management function for sending the location update; the user subscription data sending unit 502, configured to update according to the location The type of the node having the mobility management function obtained by the obtaining unit 501 is requested, and the user subscription data is transmitted to the node having the mobility management function. The location update request obtained by the location update request obtaining unit 501 may also carry the type of user subscription data required by the node having the mobility management function. If the location update request further carries the type of user subscription data required by the node having the mobility management function, the number of user subscriptions According to the type of the node having the mobility management function and the type of the user subscription data required by the sending unit 502 to send the user subscription data to the node having the mobility management function according to the type of the node having the mobility management function. User subscription data is sent to the node having the mobility management function. In other words, when the user subscription data sending unit 502 sends the user subscription data, in addition to the type of the node having the mobility management function, it is also necessary to consider the type of the user subscription data required by the node having the mobility management function. The user subscription data sent by the user subscription data transmitting unit 502 to the node having the mobility management function is user subscription data of a type required by the node having the mobility management function.
存储用户签约数据的节点还可以包括: 位置更新操作单元 503 , 用于在位 置更新请求获得单元 501 获得具有移动管理功能的节点发出的位置更新请求 后, 进行位置更新操作, 其中, 如果所述位置更新请求携带的具有移动管理功 能的节点类型相关的信息还表示需要优先考虑进行位置更新操作的方式和需 要的用户签约数据的类型, 则位置更新操作单元 503在进行位置更新操作时, 根据所述需要优先考虑的方式进行位置更新操作。如果所述位置更新请求携带 的具有移动管理功能的节点类型相关的信息还表示需要优先考虑的用户签约 需要优先考虑的用户签约数据的类型发送用户签约数据。 进一步来说,如果具 有移动管理功能的节点是合设节点 MME/SGSN, 则合设节点 MME/SGSN这 种类型可以有多种表现形式, 不同的表现形式可以表示不同的信息, 例如, MME/SGSN可以表示用户设备是通过 MME进行位置更新的, 那么位置更新 操作单元 503在进行位置更新操作时,应该优先进行与 MME对应的位置更新 操作, 用户签约数据发送单元 502 发送用户签约数据时, 可以优先考虑将与 MME对应类型的用户签约数据发送给合设节点 MME/SGSN。 当然,如果合设 节点 MME/SGSN没有特别要求, 那么用户签约数据发送单元 502—般会将与 MME对应类型的用户签约数据和与 SGSN对应类型的用户签约数据一同发送 给合设节点 MME/SGSN。 存储用户签约数据的节点还可以包括: 记录单元 504, 用于记录发起位置 更新请求的 MME或 SGSN的地址。如果发出所述位置更新请求的具有移动管 理功能的节点为合设节点 MME/SGSN、 合设节点 MME/SGSN中的 MME和
SGSN的地址不相同、 并且所述位置更新请求还携带 MME的地址和 SGSN的 地址,则在位置更新请求获得单元 501获得具有移动管理功能的节点发出的位 置更新请求后, 记录单元 504同时记录 MME的地址和 SGSN的地址。 如果图 5 所示的节点与具有移动管理功能的节点之间设置有具有协议转 换功能的节点,则位置更新请求获得单元 501获得的具有移动管理功能的节点 发出的位置更新请求是通过具有协议转换功能的节点获得的,用户签约数据发 送单元 502 向所述具有移动管理功能的节点发送的用户签约数据是通过具有 协议转换功能的节点到达所述具有移动管理功能的节点的。 需要说明的是,图 5所示的存储用户签约数据的节点可以是 HLR或 HSS, 具有移动管理功能的节点可以是 MME、 SGSN或合设节点 MME/SGSN。另外, 用户签约数据发送单元 502 向具有移动管理功能的节点发送的用户签约数据 可以携带于用户签约数据发送单元 502 向具有移动管理功能的节点发送的位 置更新响应中。 如图 15所示, 为本发明实施例提供的另一种存储用户签约数据的节点。 该存储用户签约数据的节点包括位置更新请求获得单元 1501和用户签约数据 发送单元 1502。 其中, 位置更新请求获得单元 1501同上面实施例中的位置更 新请求获得单元 501 ; 用户签约数据发送单元 1502 同上面实施例中的用户签 约数据发送单元 502。 这里不再赘述。 可选的, 该存储用户签约数据的节点还可以包括第一存储单元 1503 , 和 所述位置更新请求获得单元 1501相连, 用于存储所述位置更新请求获得单元 1201接收的所述具有移动管理功能的节点的类型。 可选的, 该存储用户签约数据的节点还可以包括第一发送单元 1504, 用 于和所述第一存储单元 1503相连, 当所述类型对应的节点对应的用户签约数 据发生更新时, 向所述类型对应的节点发送用户数据更新请求消息。 在实际应用中,存储用户签约数据的节点获得位置更新请求后, 一般都会 进行位置更新操作。 对此, 本发明实施例提供一种进行位置更新操作的方法。 如图 6所示, 包括:
步骤 S601 : 获得具有移动管理功能的节点发出的位置更新请求, 所述位 置更新请求携带所述具有移动管理功能的节点类型相关的信息,所述具有移动 管理功能的节点类型相关的信息至少包括发送位置更新的所述具有移动管理 功能的节点的类型。 The node storing the user subscription data may further include: a location update operation unit 503, configured to perform a location update operation after the location update request obtaining unit 501 obtains the location update request sent by the node having the mobility management function, where if the location The information related to the node type of the mobile management function carried in the update request also indicates that the manner of performing the location update operation and the type of the user subscription data required are prioritized, and the location update operation unit 503 performs the location update operation according to the Location update operations are required in a prioritized manner. If the information related to the node type with the mobility management function carried by the location update request also indicates that the user subscription subscription needs to be prioritized, the subscriber subscription data needs to be prioritized to send the subscriber subscription data. Further, if the node with the mobility management function is the MME/SGSN, the type of the MME/SGSN may have multiple representations, and different representations may represent different information, for example, MME/ The SGSN may indicate that the user equipment is updated by the MME. The location update operation unit 503 should perform the location update operation corresponding to the MME when performing the location update operation. When the user subscription data sending unit 502 sends the user subscription data, It is preferred to transmit the subscriber subscription data of the type corresponding to the MME to the associated node MME/SGSN. Of course, if there is no special requirement for the MME/SGSN, the user subscription data sending unit 502 will generally send the subscriber subscription data of the type corresponding to the MME and the subscriber subscription data of the corresponding type of the SGSN to the MME/SGSN. . The node storing the user subscription data may further include: a recording unit 504, configured to record an address of the MME or the SGSN that initiates the location update request. If the node with the mobility management function that issues the location update request is the MME in the joint node MME/SGSN, the joint node MME/SGSN, and The address of the SGSN is different, and the location update request further carries the address of the MME and the address of the SGSN. After the location update request obtaining unit 501 obtains the location update request sent by the node having the mobility management function, the recording unit 504 simultaneously records the MME. Address and SGSN address. If a node having the protocol conversion function is provided between the node shown in FIG. 5 and the node having the mobility management function, the location update request issued by the node having the mobility management function obtained by the location update request obtaining unit 501 is through protocol conversion. The user subscription data sent by the user subscription data transmitting unit 502 to the node having the mobility management function is obtained by the node having the protocol conversion function to the node having the mobility management function. It should be noted that the node storing the subscriber subscription data shown in FIG. 5 may be an HLR or an HSS, and the node having the mobility management function may be an MME, an SGSN, or a joint node MME/SGSN. In addition, the user subscription data transmitted by the user subscription data transmitting unit 502 to the node having the mobility management function may be carried in the location update response sent by the user subscription data transmitting unit 502 to the node having the mobility management function. As shown in FIG. 15, another node for storing user subscription data is provided by an embodiment of the present invention. The node storing the user subscription data includes a location update request obtaining unit 1501 and a user subscription data transmitting unit 1502. The location update request obtaining unit 1501 is the same as the location update request obtaining unit 501 in the above embodiment; the user subscription data transmitting unit 1502 is the same as the user subscription data transmitting unit 502 in the above embodiment. I won't go into details here. Optionally, the node that stores the user subscription data may further include a first storage unit 1503, and is connected to the location update request obtaining unit 1501, and configured to store the mobile management function received by the location update request obtaining unit 1201. The type of node. Optionally, the node that stores the user subscription data may further include a first sending unit 1504, configured to be connected to the first storage unit 1503, and when the user subscription data corresponding to the node corresponding to the type is updated, The node corresponding to the type sends a user data update request message. In an actual application, after the node storing the user subscription data obtains the location update request, the location update operation is generally performed. In this regard, an embodiment of the present invention provides a method for performing a location update operation. As shown in Figure 6, it includes: Step S601: Obtain a location update request sent by a node with a mobility management function, where the location update request carries information about a node type having a mobility management function, and the information related to the node type of the mobility management function includes at least sending The type of node with the mobility management function of the location update.
步骤 S602: 如果所述具有移动管理功能的节点的类型指示所述具有移动 管理功能的节点为合设节点 MME/SGSN、 且所述具有移动管理功能的节点类 型相关的信息还表示对 MME和 SGSN同时进行位置更新操作的请求,则同时 进行与 MME对应的位置更新操作和与 SGSN对应的位置更新操作。 对于合设节点 MME/SGSN来说,有时,合设节点 MME/SGSN中的 MME 和 SGSN的地址相同, 而有时, 合设节点 MME/SGSN中的 MME和 SGSN的 地址不相同。 如果 MME和 SGSN的地址不相同, 则获得的位置更新请求可以 携带 MME和 SGSN的地址, 这样, 当进行与 MME对应的位置更新操作和与 SGSN对应的位置更新操作时,就可以同时记录 MME的地址和 SGSN的地址。 在一个时刻,一个用户设备只能通过 MME和 SGSN中的一种方式进行位 置更新。假设一个用户设备在某个时刻通过 MME进行了位置更新,并且 MME 是合设节点 MME/SGSN中的 MME,合设节点 MME/SGSN向存储用户签约数 据的节点发出位置更新请求后, 存储用户签约数据的节点同时进行了与 MME 对应的位置更新操作和与 SGSN对应的位置更新操作。当这个用户设备又需要 通过合设节点 MME/SGSN中的 SGSN进行位置更新, 由于存储用户签约数据 的节点已经进行了与 SGSN对应的位置更新操作,所以,合设节点 MME/SGSN 无须再向存储用户签约数据的节点发出位置更新请求,存储用户签约数据的节 点也无须再进行与 SGSN对应的位置更新操作。 需要说明的是,上述步骤 S601和 S602的执行主体可以是存储用户签约数 据的节点,例如是 HSS或 HLR,具有移动管理功能的节点可以是 MME、 SGSN 或合设节点 MME/SGSN。 对应于图 6 所示的方法, 本发明实施例提供一种存储用户签约数据的节 点。 如图 7所示, 这种存储用户签约数据的节点包括: 位置更新请求获得单元 701 , 用于获得具有移动管理功能的节点发出的位置更新请求, 所述位置更新
请求携带所述具有移动管理功能的节点类型相关的信息,所述具有移动管理功 能的节点类型相关的信息至少包括发送位置更新的所述具有移动管理功能的 节点的类型;位置更新操作单元 703 ,用于如果所述位置更新请求获得单元 701 获得的具有移动管理功能的节点的类型指示所述具有移动管理功能的节点为 合设节点 MME/SGSN、 且所述具有移动管理功能的节点类型相关的信息还表 示对 MME和 SGSN同时进行位置更新操作的请求,则同时进行与 MME对应 的位置更新操作和与 SGSN对应的位置更新操作。 Step S602: If the type of the node with the mobility management function indicates that the node with the mobility management function is the joint node MME/SGSN, and the information about the node type with the mobility management function also indicates the MME and the SGSN. When the request for the location update operation is performed simultaneously, the location update operation corresponding to the MME and the location update operation corresponding to the SGSN are simultaneously performed. For the setup node MME/SGSN, the address of the MME and the SGSN in the setup node MME/SGSN may be the same, and the addresses of the MME and the SGSN in the setup node MME/SGSN may be different. If the addresses of the MME and the SGSN are different, the obtained location update request may carry the addresses of the MME and the SGSN, so that when the location update operation corresponding to the MME and the location update operation corresponding to the SGSN are performed, the MME may be simultaneously recorded. Address and SGSN address. At one moment, a user equipment can only perform location update through one of the MME and the SGSN. It is assumed that a user equipment performs location update by the MME at a certain time, and the MME is the MME in the connection node MME/SGSN, and the connection node MME/SGSN issues a location update request to the node that stores the user subscription data, and stores the user subscription. The node of the data simultaneously performs a location update operation corresponding to the MME and a location update operation corresponding to the SGSN. When the user equipment needs to perform location update through the SGSN in the MME/SGSN, since the node storing the subscriber subscription data has performed the location update operation corresponding to the SGSN, the setup node MME/SGSN does not need to be stored again. The node that subscribes to the user's subscription data issues a location update request, and the node that stores the user subscription data does not need to perform the location update operation corresponding to the SGSN. It should be noted that the execution body of the foregoing steps S601 and S602 may be a node that stores user subscription data, such as an HSS or an HLR, and the node with the mobility management function may be an MME, an SGSN, or a joint node MME/SGSN. Corresponding to the method shown in FIG. 6, an embodiment of the present invention provides a node that stores user subscription data. As shown in FIG. 7, the node for storing user subscription data includes: a location update request obtaining unit 701, configured to obtain a location update request sent by a node having a mobility management function, where the location update is performed. Requesting to carry information related to the node type having the mobility management function, the information related to the node type having the mobility management function at least including the type of the node having the mobility management function for sending the location update; the location update operation unit 703, The type of the node having the mobility management function obtained by the location update request obtaining unit 701 indicates that the node having the mobility management function is the joint node MME/SGSN, and the node type having the mobility management function is related. The information also indicates that the MME and the SGSN simultaneously perform a location update operation, and simultaneously performs a location update operation corresponding to the MME and a location update operation corresponding to the SGSN.
图 7所示的节点还可以包括记录单元 704, 用于当位置更新操作单元 703 进行与 MME对应的位置更新操作和与 SGSN对应的位置更新操作时,同时记 录 MME的地址和 SGSN的地址。 需要说明的是,图 7所示的存储用户签约数据的节点可以是 HSS或 HLR, 具有移动管理功能的节点可以是 MME、 SGSN或合设节点 MME/SGSN。 需要说明的是,上述各个实施例提到的位置更新可以是指用户设备附着流 程中的位置更新, 也可以是指跟踪区更新( TAU, Tracking Area Update )或路 由区 (RAU, Routing Area Update ) 更新的流程。 The node shown in FIG. 7 may further include a recording unit 704 for simultaneously recording the address of the MME and the address of the SGSN when the location update operation unit 703 performs a location update operation corresponding to the MME and a location update operation corresponding to the SGSN. It should be noted that the node storing the user subscription data shown in FIG. 7 may be an HSS or an HLR, and the node having the mobility management function may be an MME, an SGSN, or a joint node MME/SGSN. It should be noted that the location update mentioned in the foregoing embodiments may refer to a location update in a user equipment attach process, or may refer to a TAU (Tracking Area Update) or a Routing Area Update (RAU). Updated process.
为使本领域技术人员更加清楚的理解本发明实施例,下面再以四个实施例 对本发明实施例进行详细说明。 In order to make the embodiments of the present invention more clearly understood by those skilled in the art, the embodiments of the present invention will be described in detail in the following four embodiments.
第一个实施例 合设节点 MME/SGSN通过 S6a或 S6d接口在位置更新请求中发送其节点 类型或请求对 MME和 SGSN同时进行位置更新操作的指示和请求的用户签约 数据的类型(可选)给 HSS,请求同时下发 EPS用户签约数据和支持 S4-SGSN 的 2G/3G用户签约数据。 具体流程如图 8所示, 包括: 步骤 S801 : 合设节点 MME/SGSN 向 HSS 发出位置更新请求(Update Location ), 位置更新请求携带节点类型为合设节点 MME/SGSN或携带有请求 对 MME和 SGSN同时进行位置更新操作的指示, 请求 EPS用户签约数据和 支持 S4-SGSN的 2G/3G用户签约数据。
步骤 S802 : HSS 对合设节点 MME/SGSN 同时进行 E-UTRAN 和 UTRAN/GERAN两种接入方式的位置更新操作,例如 2G/3G和 EPS业务检查、 GERAN/UTRAN和 EUTRAN漫游限制检查等,当检查通过时,同时记录 MME 和 SGSN的地址( 4叚定合设节点 MME/SGSN中的 MME和 SGSN的地址相同)。 HSS将 EPS用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据携带在位置 更新响应 (Update Location Ack ) 中下发给合设节点 MME/SGSN。 需要说明的是: The first embodiment combines the node MME/SGSN to send its node type in the location update request through the S6a or S6d interface or request an indication of the location update operation for the MME and the SGSN simultaneously and the type of the user subscription data (optional) To the HSS, the request is to simultaneously issue EPS subscriber subscription data and 2G/3G subscriber subscription data supporting S4-SGSN. The specific process is as shown in FIG. 8, and includes: Step S801: The joint node MME/SGSN sends a location update request (Update Location) to the HSS, where the location update request carrying node type is a joint node MME/SGSN or carries a request to the MME and The SGSN simultaneously performs an indication of the location update operation, requesting the EPS user subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN. Step S802: The HSS performs location update operations on the E-UTRAN and UTRAN/GERAN access modes simultaneously for the joint node MME/SGSN, for example, 2G/3G and EPS service check, GERAN/UTRAN and EUTRAN roaming limit check, etc. When the check is passed, the addresses of the MME and the SGSN are simultaneously recorded (4. The addresses of the MME and the SGSN in the setup node MME/SGSN are the same). The HSS carries the EPS user subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN in the location update response (Update Location Ack) and sends it to the associated node MME/SGSN. It should be noted:
( 1 )合设节点 MME/SGSN与 HSS之间进行的位置更新等同于将 S6a和 S6d中定义的位置更新过程合并进行。 当同一个用户设备通过另一种接入方式 注册时, 合设节点 MME/SGSN无须再向 HSS发出位置更新请求。 (1) The location update between the MME/SGSN and the HSS is equivalent to combining the location update procedures defined in S6a and S6d. When the same user equipment is registered by another access method, the joint node MME/SGSN does not need to issue a location update request to the HSS.
( 2 )合设节点 MME/SGSN可以使用 S6a或 S6d中的 Diameter应用标识 表示需要 HSS优先考虑的位置更新方式和需要的用户签约数据的类型。 考虑 到 IWF可能存在的场景, IWF会将 S6a和 S6d的消息都转换成适用于 Gr+的 消息,此时,合设节点 MME/SGSN可以通过节点类型信息表示需要 HSS优先 考虑的位置更新方式和需要的用户签约数据的类型。 例如 MME/SGSN表示优 先考虑 MME发起的位置更新和 EPS用户签约数据; SGSN/MME表示优先考 虑 SGSN发起的位置更新和 2G/3G用户签约数据。 (2) The joint node MME/SGSN can use the Diameter application identifier in S6a or S6d to indicate the location update mode that needs to be prioritized by the HSS and the type of user subscription data required. Considering the possible scenarios of the IWF, the IWF will convert the messages of S6a and S6d into messages suitable for Gr+. At this time, the joint node MME/SGSN can indicate the location update mode and needs that need to be prioritized by the HSS through the node type information. The type of user subscription data. For example, the MME/SGSN indicates that the location update and the EPS user subscription data initiated by the MME are preferentially considered; the SGSN/MME indicates that the location update initiated by the SGSN and the 2G/3G subscriber subscription data are prioritized.
( 3 )合设节点 MME/SGSN给 MME和 SGSN分配的地址不同时, 在位 置更新请求消息中需要分别携带 MME和 SGSN的地址,或者结合节点类型中 的优先表示,在位置更新请求中单独使用一个参数携带没有被优先考虑的节点 的地址。 第二个实施例 这个实施例适用于 EPS和 Rel-8 (版本 8 )或 pre Rel-8 (版本 8之前的版 本 )的 HLR之间交互的场景。此时,在 MME/SGSN和 HLR中间会存在 IWF。 具体流程如图 9所示: 步骤 S901 : 合设节点 MME/SGSN向 IWF发出位置更新请求, 位置更新 请求携带节点类型为合设节点 MME/SGSN, 并同时请求 EPS用户签约数据和
支持 S4-SGSN的 2G/3G用户签约数据。 (3) When the address assigned by the MME/SGSN to the MME and the SGSN is different, the location update request message needs to carry the addresses of the MME and the SGSN respectively, or combined with the priority representation in the node type, and used separately in the location update request. One parameter carries the address of a node that is not prioritized. Second Embodiment This embodiment is applicable to the scenario of interaction between EPS and Rel-8 (Release 8) or Pre Rel-8 (Pre-Release 8) HLR. At this time, there is an IWF between the MME/SGSN and the HLR. The specific process is as shown in FIG. 9: Step S901: The joint node MME/SGSN sends a location update request to the IWF, and the location update request carries the node type as the joint node MME/SGSN, and simultaneously requests the EPS user subscription data and Support 2G/3G user subscription data of S4-SGSN.
步骤 S902: IWF 收到基于 Diameter 协议的位置更新请求后, 将基于 Diameter协议的位置更新请求转换为基于 MAP 的位置更新请求, 再将基于 MAP的位置更新请求发给 HLR。 步骤 S903 : HLR 对合设节点 MME/SGSN 同时进行 E-UTRAN 和 Step S902: After receiving the location update request based on the Diameter protocol, the IWF converts the location update request based on the Diameter protocol into a MAP-based location update request, and then sends the MAP-based location update request to the HLR. Step S903: The HLR performs E-UTRAN and the simultaneous connection of the MME/SGSN
UTRAN/GERAN两种接入方式的位置更新操作,例如 2G/3G和 EPS业务检查、 GERAN/UTRAN和 EUTRAN漫游限制检查等,当检查通过时,同时记录 MME 和 SGSN的地址( 4叚定合设节点 MME/SGSN中的 MME和 SGSN的地址相同)。 HLR将 EPS用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据携带在位 置更新响应中下发给 IWF。 步骤 S904: IWF将基于 MAP的位置更新响应转换为基于 Diameter协议 的位置更新响应中发给合设节点 MME/SGSN。 需要说明的是: Location update operations of UTRAN/GERAN access modes, such as 2G/3G and EPS service check, GERAN/UTRAN and EUTRAN roaming restriction check, etc. When the check is passed, the addresses of the MME and the SGSN are simultaneously recorded. The addresses of the MME and the SGSN in the node MME/SGSN are the same). The HLR carries the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN in the location update response and sends the data to the IWF. Step S904: The IWF converts the MAP-based location update response into a location update response based on the Diameter protocol and sends it to the set-up node MME/SGSN. It should be noted:
( 1 )合设节点 MME/SGSN与 HLR之间进行的位置更新等同于将 S6a和 S6d中定义的位置更新过程合并进行。 当同一个用户设备通过另一种接入方式 注册时, 合设节点 MME/SGSN无须再向 HLR发出位置更新请求。 (1) The location update between the MME/SGSN and the HLR is equivalent to combining the location update procedures defined in S6a and S6d. When the same user equipment is registered by another access method, the joint node MME/SGSN does not need to issue a location update request to the HLR.
( 2 )合设节点 MME/SGSN可以通过节点类型表示需要 HLR优先考虑的 位置更新方式和需要的用户签约数据的类型, 例如 MME/SGSN表示优先考虑 MME发起的位置更新和 EPS用户签约数据; SGSN/MME表示优先考虑 SGSN 发起的位置更新和 2G/3G用户签约数据。 (2) The MME/SGSN may indicate the location update mode that requires the HLR priority and the type of the user subscription data required by the node type. For example, the MME/SGSN indicates that the location update and the EPS subscriber subscription data initiated by the MME are prioritized; /MME indicates that the location update initiated by the SGSN and the 2G/3G subscriber subscription data are prioritized.
( 3 )合设节点 MME/SGSN给 MME和 SGSN分配的地址不同时, 在位 置更新请求消息中需要分别携带 MME和 SGSN的地址,或者结合节点类型中 的优先表示,在位置更新请求中单独使用一个参数携带没有被优先考虑的节点 的地址。 ( 4 ) 当 HLR是 pre Rel-8的 HLR时, 由于 pre Rel-8的 HLR无法支持扩 展的 Gr+接口, 所以对于上述步骤 S902中的节点类型和需要的用户签约数据 的类型, pre Rel-8的 HLR都无法识别。 pre Rel-8的 HLR只有 2G/3G用户签
约数据, pre Rel-8的 HLR只能将基于 Gr接口协议的 2G/3G用户签约数据下 发给 IWF。 IWF再将 2G/3G用户签约数据转换成 EPS用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据发给合设节点 MME/SGSN。 (3) When the address assigned by the MME/SGSN to the MME and the SGSN is different, the location update request message needs to carry the addresses of the MME and the SGSN respectively, or combined with the priority representation in the node type, and used separately in the location update request. One parameter carries the address of a node that is not prioritized. (4) When the HLR is the pre-Rel-8 HLR, since the HLR of the pre-Rel-8 cannot support the extended Gr+ interface, the type of the node in the above step S902 and the type of the user subscription data required, pre Rel-8 The HLR is not recognized. Pre-Rel-8 HLR only has 2G/3G user sign About the data, the pre-rel-8 HLR can only send the 2G/3G user subscription data based on the Gr interface protocol to the IWF. The IWF then converts the 2G/3G subscriber subscription data into EPS subscriber subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN to the associated node MME/SGSN.
第三个实施例 独立的 MME、 SGSN通过 S6a或 S6d接口在位置更新请求中发送其节点 类型和请求的用户签约数据的类型 (必选)给 HSS, 请求同时下发 EPS用户 签约数据和支持 S4-SGSN的 2G/3G用户签约数据。 具体流程如图 10所示, 包括: In the third embodiment, the MME and the SGSN send the node type and the type of the requested user subscription data (required) to the HSS in the location update request through the S6a or S6d interface, and request the simultaneous delivery of the EPS user subscription data and support S4. - SGSN's 2G/3G subscriber subscription data. The specific process is shown in Figure 10, including:
步骤 S1001 :独立的 MME或 SGSN向 HSS发出位置更新请求,位置更新 请求携带节点类型为 MME或 SGSN, 并同时请求 EPS用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据; 步骤 S1002: HSS根据节点类型进行相应的位置更新操作,例如业务检查、 漫游限制检查等, 当检查通过时, HSS记录 MME或 SGSN的地址, 并将 EPS 用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据携带在位置更新响应中 下发给 MME或 SGSN。 第四个实施例 这个实施例适用于 EPS和 Rel-8 (版本 8 )或 pre Rel-8 (版本 8之前的版 本 )的 HLR之间交互的场景。此时,在 MME/SGSN和 HLR中间会存在 IWF。 具体流程如图 11所示: Step S1001: The independent MME or the SGSN sends a location update request to the HSS, and the location update request carries the node type as the MME or the SGSN, and simultaneously requests the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN; Step S1002: HSS According to the node type, the corresponding location update operation, such as service check, roaming restriction check, etc., when the check passes, the HSS records the address of the MME or the SGSN, and signs the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN. The bearer is sent to the MME or the SGSN in the location update response. Fourth Embodiment This embodiment is applicable to a scenario in which an EPS interacts with an HLR of Rel-8 (version 8) or pre Rel-8 (a version prior to version 8). At this time, there is an IWF between the MME/SGSN and the HLR. The specific process is shown in Figure 11:
步骤 S1101 : 独立的 MME或 SGSN向 IWF发出位置更新请求,位置更新 请求携带节点类型为 MME或 SGSN, 并同时请求 EPS用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据。 Step S1101: The independent MME or the SGSN sends a location update request to the IWF. The location update request carries the node type as the MME or the SGSN, and simultaneously requests the EPS user subscription data and the 2G/3G user subscription data supporting the S4-SGSN.
步骤 S1102: IWF 收到基于 Diameter协议的位置更新请求后, 将基于 Diameter协议的位置更新请求转换为基于 MAP 的位置更新请求, 再将基于 MAP的位置更新请求发给 HLR。 步骤 S1103: HLR根据节点的类型进行相应的位置更新操作,如业务检查、 漫游限制检查等, 当检查通过时, HLR记录 MME或 SGSN的地址, 并将 EPS
用户签约数据和支持 S4-SGSN的 2G/3G用户签约数据携带在位置更新响应中 下发给 IWF。 Step S1102: After receiving the location update request based on the Diameter protocol, the IWF converts the location update request based on the Diameter protocol into a MAP-based location update request, and then sends the MAP-based location update request to the HLR. Step S1103: The HLR performs corresponding location update operations according to the type of the node, such as service check, roaming restriction check, etc. When the check passes, the HLR records the address of the MME or the SGSN, and the EPS is The user subscription data and the 2G/3G user subscription data supporting the S4-SGSN are carried in the location update response and sent to the IWF.
步骤 S1104: IWF将基于 MAP的位置更新响应转换为基于 Diameter协议 的位置更新响应中发给 MME或 SGSN。 需要说明的是: Step S1104: The IWF converts the MAP-based location update response into a location update response based on the Diameter protocol and sends it to the MME or the SGSN. It should be noted:
当 HLR是 pre Rel-8的 HLR时,无法支持扩展的 Gr+接口, 由于 pre Rel-8 的 HLR无法支持扩展的 Gr+接口, 所以对于上述步骤 S1102中的节点类型和 需要的用户签约数据的类型, pre Rel-8的 HLR都无法识别。 pre Rel-8的 HLR 只有 2G/3G用户签约数据, pre Rel-8的 HLR只能将基于 Gr接口协议的 2G/3G 用户签约数据下发给 IWF。 IWF再将 2G/3G用户签约数据转换成 EPS用户签 约数据和支持 S4-SGSN的 2G/3G用户签约数据发给合设节点 MME/SGSN。 When the HLR is the pre-Rel-8 HLR, the extended Gr+ interface cannot be supported. Since the pre-Rel-8 HLR cannot support the extended Gr+ interface, the node type in the above step S1102 and the type of the user subscription data required, The pre-Ll-8 HLR is unrecognizable. The pre-rel-8 HLR only has 2G/3G user subscription data, and the pre-Rel-8 HLR can only send the 2G/3G user subscription data based on the Gr interface protocol to the IWF. The IWF then converts the 2G/3G subscriber subscription data into EPS subscriber subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN to the associated node MME/SGSN.
第五个实施例 Fifth embodiment
HSS接收到位置更新消息,通过消息中携带的节点类型,向请求节点下发 节点类型对应的节点对应的用户签约数据。 HSS同时存储接收到的节点类型, 当所述类型对应的节点对应的用户签约数据发生更新时,向所述类型对应的节 点发送用户数据更新请求消息。 下面以节点类型为 MME/SGSN合设节点为例 进行说明, 其中的 SGSN同时支持 S4-SGSN和 2G/3G的 SGSN的功能。 合设的 MME/SGSN通过 S6a或 S6d接口在位置更新请求中发送其节点类 型给 HSS。 HSS 根据该节点类型向合设节点同时下发 EPS 用户签约数据和 2G/3G用户签约数据。 HSS 同时存储接收到的节点类型, 当后续对应用户的 2G/3G签约数据发生改变时, HSS判断存储的节点类型,确定发送相应的用户 数据更新消息给对应的节点。 具体流程如图 12所示。 包括: 步骤 S1201 : 合设的 MME/SGSN向 HSS发出位置更新请求, 位置更新请 求携带节点类型为 MME/SGSN; The HSS receives the location update message, and delivers the user subscription data corresponding to the node corresponding to the node type to the requesting node by using the node type carried in the message. The HSS stores the received node type at the same time. When the user subscription data corresponding to the node corresponding to the type is updated, the user data update request message is sent to the node corresponding to the type. The following is an example of a node type MME/SGSN joint node. The SGSN supports both the S4-SGSN and the 2G/3G SGSN functions. The co-located MME/SGSN sends its node type to the HSS in the location update request via the S6a or S6d interface. The HSS sends the EPS user subscription data and the 2G/3G user subscription data to the joint node according to the node type. The HSS stores the received node type at the same time. When the subsequent 2G/3G subscription data of the corresponding user changes, the HSS determines the stored node type and determines to send the corresponding user data update message to the corresponding node. The specific process is shown in Figure 12. The method includes: Step S1201: The MME/SGSN is configured to send a location update request to the HSS, where the location update request carries the node type as MME/SGSN;
步骤 S1202: HSS进行相应的位置更新操作, 例如业务检查、 漫游限制检 查等, 当检查通过时, HSS记录 MME或 SGSN的地址, 并将 EPS用户签约 数据和 2G/3G用户签约数据携带在位置更新响应中下发给请求节点;
步骤 S1203 : HSS存储步骤 S1201中收到的节点类型; 步骤 S1204: 当 2G/3G用户签约数据发生更新 (包括增加、 删除、 修改) 时, HSS判断存储的节点类型为合设节点 MME/SGSN, HSS触发后续用户数 据更新过程; Step S1202: The HSS performs corresponding location update operations, such as service check, roaming restriction check, etc. When the check passes, the HSS records the address of the MME or the SGSN, and carries the EPS user subscription data and the 2G/3G user subscription data in the location update. The response is sent to the requesting node; Step S1203: The HSS stores the node type received in step S1201; Step S1204: When the 2G/3G user subscription data is updated (including adding, deleting, and modifying), the HSS determines that the stored node type is the joint node MME/SGSN, The HSS triggers a subsequent user data update process;
步骤 S1205: HSS将更新后的 2G/3G用户签约数据携带在用户数据更新请 求消息中下发给 MME/SGSN; 如果步骤 S1204中所述的 2G/3G用户签约数据 发生更新是指该 2G/3G用户签约数据被删除, 则 HSS可能携带对应的用户数 据删除指示在用户数据更新消息中; 步骤 S1206: MME/SGSN返回用户数据更新响应消息。 Step S1205: The HSS carries the updated 2G/3G subscriber subscription data in the user data update request message and sends the data to the MME/SGSN. If the 2G/3G subscriber subscription data is updated in step S1204, the 2G/3G is referred to. If the user subscription data is deleted, the HSS may carry the corresponding user data deletion indication in the user data update message. Step S1206: The MME/SGSN returns a user data update response message.
第六个实施例 Sixth embodiment
HSS接收到位置更新消息, 通过消息中携带的节点类型和 /或请求的用户 签约数据的类型 (用户签约数据的类型是可选的), 向请求节点下发节点类型 对应的节点或请求的用户签约数据的类型对应的用户签约数据。 HSS同时存储 接收到的节点类型或请求的用户签约数据的类型,当所述类型对应的节点或请 求的用户签约数据的类型对应的用户签约数据发生更新时,向所述节点发送用 户数据更新请求消息。 下面以节点类型为 MME/SGSN合设节点, 请求的用户 签约数据的类型为 EPS用户签约数据和 2G/3G用户签约数据为例进行说明, 其中的 SGSN同时支持 S4-SGSN和 2G/3G的 SGSN的功能。 合设的 MME/SGSN通过 S6a或 S6d接口在位置更新请求中发送其节点类 型和请求的用户签约数据的类型 (可选)给 HSS。 HSS通过消息中携带的节 点类型或消息中携带的请求的用户签约数据类型 (如果消息中携带时)请求 HSS同时下发 EPS用户签约数据和 2G/3G用户签约数据。 HSS存储收到的节 点类型或请求的用户签约数据类型 (如果消息中携带时), 当后续对应用户的 2G/3G签约数据发生改变时, HSS判断存储的节点类型或请求的用户签约数据 类型, 确定发送相应的用户数据更新消息给对应的节点。 具体流程如图 13所 示。 包括: The HSS receives the location update message, and sends the node corresponding to the node type or the requested user to the requesting node by using the node type carried in the message and/or the type of the user subscription data (the type of the user subscription data is optional). User subscription data corresponding to the type of subscription data. The HSS simultaneously stores the received node type or the type of the requested user subscription data, and sends a user data update request to the node when the node corresponding to the type or the user subscription data corresponding to the type of the requested user subscription data is updated. Message. The following is an example of the node type being the MME/SGSN connection node. The type of the requested subscriber subscription data is the EPS subscriber subscription data and the 2G/3G subscriber subscription data. The SGSN supports both the S4-SGSN and the 2G/3G SGSN. The function. The combined MME/SGSN sends its node type and the type of the requested user subscription data (optional) to the HSS in the location update request through the S6a or S6d interface. The HSS requests the HSS to simultaneously deliver the EPS user subscription data and the 2G/3G user subscription data by using the node type carried in the message or the requested user subscription data type (if the message is carried in the message) carried in the message. The HSS stores the received node type or the requested user subscription data type (if the message is carried), and when the subsequent 2G/3G subscription data of the corresponding user changes, the HSS determines the stored node type or the requested user subscription data type. It is determined that the corresponding user data update message is sent to the corresponding node. The specific process is shown in Figure 13. Includes:
步骤 S1301 : 合设的 MME/SGSN向 HSS发出位置更新请求, 位置更新请
求携带节点类型为 MME/SGSN, 同时请求 EPS用户签约数据和 2G/3G用户签 约数据; Step S1301: The combined MME/SGSN sends a location update request to the HSS, and the location update is requested. The carrier type is MME/SGSN, and the EPS user subscription data and the 2G/3G user subscription data are requested;
步骤 S1302: HSS进行相应的位置更新操作, 例如业务检查、 漫游限制检 查等, 当检查通过时, HSS记录 MME或 SGSN的地址, 并将 EPS用户签约 数据和 2G/3G用户签约数据携带在位置更新响应中下发给请求节点; Step S1302: The HSS performs corresponding location update operations, such as service check, roaming restriction check, etc. When the check passes, the HSS records the address of the MME or the SGSN, and carries the EPS user subscription data and the 2G/3G user subscription data in the location update. The response is sent to the requesting node;
步骤 S1303: HSS存储步骤 S1301中收到的节点类型或请求的用户签约数 据类型; Step S1303: The HSS stores the node type received in step S1301 or the requested user subscription data type;
步骤 S1304: 当 2G/3G用户签约数据发生更新 (包括增加、 删除、 修改) 时, HSS判断存储的节点类型为合设节点 MME/SGSN, 或请求的用户签约数 据类型为 EPS用户签约数据和 2G/3G用户签约数据时, HSS触发后续用户数 据更新过程; Step S1304: When the 2G/3G user subscription data is updated (including adding, deleting, and modifying), the HSS determines that the stored node type is the joint node MME/SGSN, or the requested user subscription data type is EPS user subscription data and 2G. When the /3G user subscribes to the data, the HSS triggers the subsequent user data update process;
步骤 S1305: HSS将更新后的 2G/3G用户签约数据携带在用户数据更新请 求消息中下发给 MME或 SGSN;如果步骤 S1204中所述的 2G/3G用户签约数 据发生更新是指该 2G/3G用户签约数据被删除, 则 HSS将发送携带有对应的 用户数据删除指示的用户数据更新消息; 步骤 S1306: MME/SGSN返回用户数据更新响应消息。 说明:步骤 S1301中的位置更新消息中的请求的用户签约数据的类型是可 选存在的。 Step S1305: The HSS carries the updated 2G/3G subscriber subscription data in the user data update request message and sends the data to the MME or the SGSN. If the 2G/3G subscriber subscription data is updated in step S1204, the 2G/3G is referred to. If the user subscription data is deleted, the HSS will send a user data update message carrying the corresponding user data deletion indication. Step S1306: The MME/SGSN returns a user data update response message. Note that the type of the requested subscriber subscription data in the location update message in step S1301 is optional.
第七个实施例 Seventh embodiment
这个实施例适用于 EPS和 Rel-8 (版本 8 )或 pre Rel-8 (版本 8之前的版 本 )的 HLR之间交互的场景。此时,在 MME/SGSN和 HLR中间会存在 IWF。 具体流程如图 14所示: This embodiment applies to scenarios where the EPS interacts with the HLRs of Rel-8 (version 8) or pre Rel-8 (versions prior to version 8). At this time, there is an IWF between the MME/SGSN and the HLR. The specific process is shown in Figure 14:
步骤 S1401 : 合设的 MME/SGSN向 IWF发出位置更新请求, 位置更新请 求携带节点类型为 MME/SGSN。 Step S1401: The set MME/SGSN sends a location update request to the IWF, and the location update request carries the node type as MME/SGSN.
步骤 S1402: IWF 收到基于 Diameter协议的位置更新请求后, 将基于 Step S1402: After receiving the location update request based on the Diameter protocol, the IWF will be based on
Diameter协议的位置更新请求转换为基于 MAP 的位置更新请求, 再将基于 MAP的位置更新请求发给 HLR。
步骤 S1403a: HLR进行相应的位置更新操作, 如业务检查、 漫游限制检 查等, 当检查通过时, HLR记录 MME或 SGSN的地址, 并根据 S1401 中携 带的请求节点的类型将 EPS用户签约数据和 2G/3G用户签约数据携带在插入 用户数据请求消息中发送给 IWF; The location update request of the Diameter protocol is converted into a MAP-based location update request, and the MAP-based location update request is sent to the HLR. Step S1403a: The HLR performs a corresponding location update operation, such as a service check, a roaming restriction check, etc., when the check passes, the HLR records the address of the MME or the SGSN, and sets the EPS user subscription data and 2G according to the type of the request node carried in S1401. The /3G user subscription data is carried in the inserted user data request message and sent to the IWF;
步骤 S1403b: 用户数据发送完成后, HLR发送位置更新响应消息给 IWF。 步骤 S1404: IWF将从基于 MAP的插入用户数据消息中收到的用户数据 转换到基于 Diameter协议的位置更新响应中发给 MME/SGSN; 步骤 S1405: HLR存储步骤 S1402中收到的节点类型; 步骤 S1406: 当 2G/3G用户签约数据发生更新 (包括增加、 删除、 修改) 时, HLR判断存储的节点类型为合设节点 MME/SGSN, HLR触发后续用户数 据更新过程; Step S1403b: After the user data is sent, the HLR sends a location update response message to the IWF. Step S1404: The IWF converts the user data received in the MAP-based inserted user data message to the location update response based on the Diameter protocol and sends it to the MME/SGSN. Step S1405: The HLR stores the node type received in step S1402. S1406: When the 2G/3G user subscription data is updated (including adding, deleting, and modifying), the HLR determines that the stored node type is the joint node MME/SGSN, and the HLR triggers the subsequent user data update process;
步骤 S1407: HLR将更新后的 2G/3G用户签约数据携带在基于 MAP的用 户数据更新请求消息中下发给 IWF; 如果步骤 S1204中所述的 2G/3G用户签 约数据发生更新是指该 2G/3G用户签约数据被删除, 则 HLR可能发送携带对 应的用户数据删除指示在用户数据更新请求消息中; 步骤 S1408: IWF将基于 MAP的用户数据更新消息转换成基于 Diameter 协议的用户数据更新消息发给 MME/SGSN; 步骤 S1409: MME/SGSN返回用户数据更新响应消息给 IWF; 步骤 S1410: IWF将基于 Diameter的用户数据更新响应消息转换成基于 MAP协议的用户数据更新消息发给 HLR。 需要说明的是: Step S1407: The HLR carries the updated 2G/3G user subscription data in the MAP-based user data update request message and sends the data to the IWF. If the 2G/3G user subscription data update in step S1204 refers to the 2G/ If the 3G user subscription data is deleted, the HLR may send the corresponding user data deletion indication in the user data update request message. Step S1408: The IWF converts the MAP-based user data update message into a user data update message based on the Diameter protocol. MME/SGSN; Step S1409: The MME/SGSN returns a User Data Update Response message to the IWF; Step S1410: The IWF converts the Diameter-based User Data Update Response message into a MAP protocol-based User Data Update message and sends it to the HLR. It should be noted:
当 HLR是 pre Rel-8的 HLR时,无法支持扩展的 Gr+接口, 由于 pre Rel-8 的 HLR无法支持扩展的 Gr+接口, 所以对于上述步骤 S1302中的节点类型, pre Rel-8的 HLR无法识别。 pre Rel-8的 HLR只有 2G/3G用户签约数据, re Rel-8的 HLR只能将基于 Gr接口协议的 2G/3G用户签约数据下发给 IWF。IWF 再将 2G/3G用户签约数据转换成 EPS用户签约数据和支持 S4-SGSN的 2G/3G 用户签约数据发给合设节点 MME/SGSN。
第八个实施例 When the HLR is the pre-Rel-8 HLR, the extended Gr+ interface cannot be supported. Since the HLR of the pre-Rel-8 cannot support the extended Gr+ interface, the HLR of the pre-rel-8 cannot be identified for the node type in the above step S1302. . The HLR of the pre-Rel-8 only has the 2G/3G user subscription data, and the HLR of the ReRel-8 can only send the 2G/3G user subscription data based on the Gr interface protocol to the IWF. The IWF then converts the 2G/3G subscriber subscription data into EPS subscriber subscription data and the 2G/3G subscriber subscription data supporting the S4-SGSN to the associated node MME/SGSN. Eighth embodiment
HSS接收到位置更新消息,消息中携带请求的用户签约数据的类型信息和 节点类型相关信息。 HSS存储接收到的请求的节点的类型相关信息和 /或请求 的用户签约数据类型 (可选)。 当用户签约数据发生更新时, HSS根据存储的 节点的类型相关信息和 /或请求的用户签约数据类型决定向所述节点发送用户 数据更新请求消息。 下面以单一节点类型信息指示为 MME为例进行说明。 单一 MME通过 S6a接口在位置更新请求中携带其请求的是 EPS签约数据 的信息和指示其节点类型的相关信息 (明确的节点类型 MME, 或单一节点信 息 + S6a接口指示信息)给 HSS。 HSS存储该节点的类型相关信息(可以是直 接存储位置更新消息中的节点类型相关信息,也可以是存储从节点类型相关信 息推导出的明确的节点类型 MME )和/或该 MME请求的签约数据类型信息(可 选存储)。 当后续对应用户的 2G/3G签约数据发生改变时, HSS判断存储的该 节点的类型相关信息是单一的 MME节点或该 MME请求的签约数据类型是 EPS签约数据, HSS将不发送相应的用户数据更新请求消息给该节点。 当后续 对应用户的只适用于 SGSN的签约数据发生改变时, HSS判断存储的该节点 的类型相关信息是单一的 MME节点, HSS将不发送相应的用户数据更新请求 消息给该节点。 只有当 EPS签约数据或适用于 MME的签约数据发生改变时, HSS才发送用户数据更新请求消息给 MME。 具体流程如图 16所示。 步骤 S 1601: 单一的 MME节点向 HSS发出位置更新请求消息。 其中, 位置更新请求携带请求的用户签约数据的类型信息为 EPS签约数 据, 及节点类型相关信息为 MME, 或单一节点信息 + S6a接口指示信息; 说明: 其中请求的用户签约数据的类型信息为 EPS签约数据可以通过明 确的请求 EPS签约数据的指示信息来指示; 也可以通过位置更新请求消息中 不包含明确指示请求 GPRS或 2G/3G签约数据的信息来推出,也就是请求 EPS 签约数据是默认或隐含的。 The HSS receives the location update message, and the message carries the type information of the requested subscriber subscription data and the node type related information. The HSS stores the type information of the received node and/or the requested user subscription data type (optional). When the user subscription data is updated, the HSS decides to send a user data update request message to the node according to the stored type information of the node and/or the requested user subscription data type. The following describes the MME as a single node type information as an example. The single MME carries the information of the EPS subscription data and the related information indicating the node type (the explicit node type MME, or the single node information + S6a interface indication information) to the HSS in the location update request through the S6a interface. The HSS stores the type-related information of the node (which may be directly storing the node type related information in the location update message, or may be an explicit node type MME that is derived from the node type related information) and/or the subscription data requested by the MME. Type information (optional storage). When the subsequent 2G/3G subscription data of the corresponding user changes, the HSS determines that the stored type information of the node is a single MME node or the subscription data type requested by the MME is EPS subscription data, and the HSS will not send the corresponding user data. Update the request message to the node. When the subscription data of the corresponding corresponding user only applies to the SGSN, the HSS determines that the stored type information of the node is a single MME node, and the HSS will not send a corresponding user data update request message to the node. The HSS sends a User Data Update Request message to the MME only when the EPS subscription data or the subscription data applicable to the MME changes. The specific process is shown in Figure 16. Step S1601: A single MME node sends a location update request message to the HSS. The type information of the user subscription data carrying the requested location update request is EPS subscription data, and the node type related information is MME, or single node information + S6a interface indication information; Description: The type information of the requested user subscription data is EPS The subscription data may be indicated by an explicit indication of the request for EPS subscription data; or may be initiated by the location update request message not including information explicitly requesting GPRS or 2G/3G subscription data, that is, requesting EPS subscription data is default or Implied.
说明: S6a接口是为 HSS和 MME定义的, S6a接口指示说明请求消息一
定来自 MME或合设节点 MME/SGSN的 MME, 单一节点信息进一步排除了 合设节点的情况, 两者结合明确了请求节点是单一 MME节点; 步骤 S1602: HSS进行相应的位置更新操作检查和处理, 并返回位置更新 响应消息给请求节点; 步骤 S1603: HSS存储步骤 S1601中收到的该节点类型相关信息, 可选地 存储该节点请求的用户签约数据的类型信息; 步骤 S1604: 当用户的 2G/3G签约数据发生更新(包括增加、 删除、 或修 改)时, HSS判断存储的节点类型相关信息指示为单一节点 MME, 或存储的 请求的用户签约数据类型是 EPS签约数据, HSS不触发用户数据更新过程, 也就是不发送用户数据更新请求消息; 步骤 S1605: 当用户的只适用于 SGSN的签约数据发生更新 (包括增加、 删除、或修改)时, HSS判断存储的节点类型相关信息指示为单一节点 MME, HSS不触发用户数据更新过程; 步骤 S1606: 当用户的 EPS签约数据发生更新(包括增加、删除、或修改 ) 时, HSS触发用户数据更新过程; 步骤 S1607: HSS将更新后的用户 EPS签约数据携带在用户数据更新请求 消息中下发给 MME。 如果步骤 S1605中所述的用户 EPS签约数据发生更新是指该用户 EPS部 分签约数据被删除, 则 HSS将发送携带有对应的签约数据删除指示的用户数 据更新请求消息; 步骤 S1608: MME返回用户数据更新响应消息。 第九个实施例 The S6a interface is defined for the HSS and the MME. The S6a interface indicates the request message. The MME from the MME or the MME/SGSN, the single node information further excludes the case of the joint node, and the combination of the two clarifies that the requesting node is a single MME node; Step S1602: The HSS performs corresponding location update operation check and processing. And returning the location update response message to the requesting node; Step S1603: The HSS stores the node type related information received in step S1601, optionally storing the type information of the user subscription data requested by the node; Step S1604: When the user's 2G When the /3G subscription data is updated (including adding, deleting, or modifying), the HSS determines that the stored node type related information is indicated as a single node MME, or the stored requested user subscription data type is EPS subscription data, and the HSS does not trigger user data. The update process, that is, the user data update request message is not sent; Step S1605: When the user's subscription data applicable only to the SGSN is updated (including adding, deleting, or modifying), the HSS determines that the stored node type related information is indicated as a single The node MME, HSS does not trigger the user data update process; Step S1606: When the user When the EPS subscription data is updated (including adding, deleting, or modifying), the HSS triggers the user data update process. Step S1607: The HSS carries the updated user EPS subscription data in the user data update request message and sends the data to the MME. If the user EPS subscription data update in step S1605 is that the user's EPS part subscription data is deleted, the HSS will send a user data update request message carrying the corresponding subscription data deletion indication; Step S1608: The MME returns the user data. Update the response message. Ninth embodiment
HSS接收到位置更新消息,消息中携带请求的用户签约数据的类型信息和 /或节点类型相关信息(可选)。 HSS存储接收到的该节点请求的用户签约数据 的类型信息。 当用户签约数据发生更新时, HSS根据存储的请求用户签约数据 的类型信息决定向该节点发送用户数据更新请求消息。下面以节点类型相关信 息指示为单一节点类型 SGSN (可选存在), 请求的用户签约数据的类型信息
为 EPS + 2G/3G (或 GPRS )签约数据为例进行说明。 单一 SGSN通过 S6d接口在位置更新请求中发送请求 EPS + 2G/3G (或 GPRS )签约数据类型信息和 /或其节点类型相关信息(明确的节点类型 SGSN, 或单一节点信息 + S6d指示信息 ) (节点类型相关信息可选存在)。 HSS存储该 SGSN请求的签约数据类型信息。 当后续对应用户的 EPS或 2G/3G签约数据 发生改变时, HSS判断存储的该 SGSN请求的签约数据类型信息类型信息是 EPS + 2G/3G签约数据, HSS发送相应的用户数据更新请求消息给该 SGSN。 具体流程如图 17所示。 The HSS receives the location update message, and the message carries the type information of the requested user subscription data and/or node type related information (optional). The HSS stores the received type information of the user subscription data requested by the node. When the user subscription data is updated, the HSS determines to send a user data update request message to the node according to the type information of the stored user subscription data. The following is indicated by the node type related information as a single node type SGSN (optional presence), and the type information of the requested user subscription data. For EPS + 2G/3G (or GPRS) subscription data as an example. The single SGSN sends the request EPS + 2G/3G (or GPRS) subscription data type information and/or its node type related information (clear node type SGSN, or single node information + S6d indication information) in the location update request through the S6d interface ( Node type related information is optional.) The HSS stores the subscription data type information requested by the SGSN. When the subsequent EPS or 2G/3G subscription data of the corresponding user is changed, the HSS determines that the stored subscription data type information type information requested by the SGSN is EPS + 2G/3G subscription data, and the HSS sends a corresponding user data update request message to the SGSN. The specific process is shown in Figure 17.
步骤 S1701 : 单一的 SGSN向 HSS发出位置更新请求。 其中, 位置更新请求消息中携带请求的用户签约数据的类型信息为 EPS Step S1701: A single SGSN issues a location update request to the HSS. The type information of the user subscription data carrying the request in the location update request message is EPS.
+ 2G/3G (或 GPRS )签约数据, 同时请求用户的 EPS签约数据和 2G/3G (或 GPRS )签约数据, 可选地携带节点类型相关信息为 SGSN, 或单一节点信息 + S6d指示信息; 说明: 其中请求的用户签约数据的类型信息为 EPS + 2G/3G (或 GPRS ) 签约数据可以是明确的请求 EPS + 2G/3G (或 GPRS )签约数据的指示信息, 也可以通过位置更新请求消息中只明确指示同时请求 2G/3G (或 GPRS )签约 数据来推出, 也就是请求 EPS签约数据是默认或隐含的。 说明: S6d接口是为 HSS和 SGSN定义的, S6d接口指示说明请求消息一 定来自 SGSN或合设节点 MME/SGSN的 SGSN, 单一节点信息进一步排除了 合设节点的情况, 两者结合明确了请求节点是单一 SGSN节点; + 2G/3G (or GPRS) subscription data, requesting the user's EPS subscription data and 2G/3G (or GPRS) subscription data, optionally carrying the node type related information as SGSN, or single node information + S6d indication information; : The type information of the requested subscriber subscription data is EPS + 2G/3G (or GPRS). The subscription data may be an explicit indication of requesting EPS + 2G/3G (or GPRS) subscription data, or may be through a location update request message. Only explicitly indicating that 2G/3G (or GPRS) subscription data is requested to be launched at the same time, that is, requesting EPS subscription data is default or implicit. NOTE: The S6d interface is defined for the HSS and the SGSN. The S6d interface indicates that the request message must come from the SGSN of the SGSN or the MME/SGSN of the joint node. The single node information further excludes the situation of the joint node. Is a single SGSN node;
步骤 S1702: HSS进行相应的位置更新操作检查和处理, 并返回位置更新 响应消息给请求节点; Step S1702: The HSS performs a corresponding location update operation check and processing, and returns a location update response message to the requesting node.
步骤 S1703 : HSS存储步骤 S1701中收到的请求的用户签约数据类型信息; 步骤 S1704: 当用户的 2G/3G (或 GPRS )签约数据发生更新(包括增加、 删除、 或修改)时, HSS判断存储的请求的用户签约数据类型信息指示了请求 的是 EPS签约数据和 2G/3G (或 GPRS )签约数据时, HSS触发用户数据更新 过程;
步骤 S1705: HSS将更新后的用户的 2G/3G (或 GPRS )签约数据携带在 用户数据更新请求消息中下发给 SGSN; Step S1703: The HSS stores the requested user subscription data type information received in step S1701; Step S1704: When the user's 2G/3G (or GPRS) subscription data is updated (including adding, deleting, or modifying), the HSS determines to store The requested user subscription data type information indicates that the request is for EPS subscription data and 2G/3G (or GPRS) subscription data, and the HSS triggers the user data update process; Step S1705: The HSS carries the updated 2G/3G (or GPRS) subscription data of the user in the user data update request message and sends the data to the SGSN.
例如, 如果步骤 S1704中所述的用户的 2G/3G (或 GPRS )签约数据发生 更新是指该用户的 2G/3G (或 GPRS )签约数据被删除, 则 HSS将发送携带有 对应的签约数据删除指示的用户数据更新消息。 步骤 S1706: SGSN返回用户数据更新响应消息。 For example, if the 2G/3G (or GPRS) subscription data update of the user described in step S1704 is that the 2G/3G (or GPRS) subscription data of the user is deleted, the HSS will send the corresponding subscription data deletion. Indicated user data update message. Step S1706: The SGSN returns a user data update response message.
第十个实施例 Tenth embodiment
HSS接收到位置更新消息,存储接收到的节点类型相关信息。 当用户签约 数据发生更新时, HS S根据存储的节点类型相关信息决定向所述类型对应的节 点发送用户数据更新请求消息。 下面以节点类型为 MME/SGSN合设节点为例 进行说明,其中的 SGSN同时支持 EPS中的 S4-SGSN和 2G/3G的 SGSN的功The HSS receives the location update message and stores the received node type related information. When the user subscription data is updated, the HSS decides to send a user data update request message to the node corresponding to the type according to the stored node type related information. The following takes the node type as the MME/SGSN joint node as an example. The SGSN supports both the S4-SGSN in the EPS and the SGSN in the 2G/3G.
•6匕 •6匕
匕。 dagger.
合设的 MME/SGSN通过 S6a或 S6d接口在位置更新请求中发送其节点类 型相关信息给 HSS,该节点类型相关信息不仅表明了它是一个合设节点, 同时 指示出 UE在所述合设节点的 MME和 SGSN同时注册了。 HSS存储该节点类 型相关信息, 当后续对应用户的 EPS或 2G/3G签约数据发生改变时, HSS判 断存储的该节点类型相关信息,确定只触发一次用户数据更新消息给该合设节 点, 而不是对该合设节点的 MME和 SGSN分别发送一次用户数据更新消息。 The associated MME/SGSN sends its node type related information to the HSS in the location update request through the S6a or S6d interface. The node type related information not only indicates that it is a joint node, but also indicates that the UE is in the joint node. The MME and SGSN are registered at the same time. The HSS stores the information about the node type. When the EPS or 2G/3G subscription data of the corresponding user changes, the HSS determines the stored information about the node type, and determines that only the user data update message is triggered once to the associated node, instead of The user data update message is sent to the MME and the SGSN of the joint node, respectively.
具体流程如图 18所示。 The specific process is shown in Figure 18.
步骤 S1801 : 合设的 MME/SGSN向 HSS发出位置更新请求, 位置更新请 求携带节点类型相关信息, 该节点类型相关信息包括指示其为合设 MME/SGSN节点, 并且指示 UE在所述合设节点的 MME和 SGSN上同时注 册的信息; Step S1801: The set MME/SGSN sends a location update request to the HSS, where the location update request carries node type related information, the node type related information includes indicating that it is a set MME/SGSN node, and indicates that the UE is in the joint node. Information registered at the same time on the MME and the SGSN;
步骤 S1802: HSS进行相应的位置更新操作检查和处理, 并返回位置更新 响应消息给请求节点; Step S1802: The HSS performs a corresponding location update operation check and processing, and returns a location update response message to the requesting node.
步骤 S1803: HSS存储步骤 S1801中收到的节点类型相关信息; Step S1803: The HSS stores the node type related information received in step S1801.
步骤 S1804: 当用户的 EPS或 2G/3G签约数据发生更新(包括增加、删除、
或修改) 时, HSS 判断存储的节点类型相关信息指示了其为合设节点 MME/SGSN, 并且用户在该合设节点的 MME和 SGSN上同时注册了时, HSS 只向该 MME/SGSN发送一次用户数据更新请求消息, 而不是对该合设节点的 MME和 SGSN分别发送一次用户数据更新请求消息; 步骤 S1805: HSS将更新后的用户的 EPS或 2G/3G签约数据携带在用户 数据更新请求消息中下发给该 MME/SGSN; Step S1804: When the user's EPS or 2G/3G subscription data is updated (including adding, deleting, Or, when the HSS determines that the stored node type related information indicates that it is the joint node MME/SGSN, and the user registers at the same time on the MME and the SGSN of the joint node, the HSS sends only to the MME/SGSN once. The user data update request message, instead of sending the user data update request message to the MME and the SGSN of the joint node respectively; Step S1805: The HSS carries the updated user's EPS or 2G/3G subscription data in the user data update request message. The middle and lower are sent to the MME/SGSN;
如果步骤 S1804中所述的用户的 EPS或 2G/3G签约数据发生更新是指该 用户的 EPS或 2G/3G部分签约数据被删除, 则 HSS可能携带对应的用户数据 删除指示在用户数据更新请求消息中; 步骤 S1806: MME/SGSN返回用户数据更新响应消息。 If the EPS or 2G/3G subscription data of the user described in step S1804 is updated, the EPS or 2G/3G partial subscription data of the user is deleted, the HSS may carry a corresponding user data deletion indication in the user data update request message. Step S1806: The MME/SGSN returns a user data update response message.
同时请求节点在位置更新请求消息中携带的请求的签约数据类型信息可以指 示是请求 2G/3G签约数据, 或请求 GPRS签约数据 以上第八, 第九和第十实施例中的方法同样也适用于 IWF存在的场景。 具体实施例很容易从类似实施例 7中描述的方法获得, 在此不再赘述。 At the same time, the requesting data type information of the request carried by the requesting node in the location update request message may indicate that the 2G/3G subscription data is requested, or the GPRS subscription data is requested to be the eighth, and the methods in the ninth and tenth embodiments are also applicable to The scene in which the IWF exists. The specific embodiment is easily obtained from a method similar to that described in Embodiment 7, and will not be described again.
综上所述, 本发明实施例不但可以优化位置更新流程,还能使存储用户签 约数据的节点能够发送正确类型的用户签约数据,并能准确记录用户设备的位 置信息。通过存储以上实施例中所述的相应的节点类型信息 (包括节点类型相 关信息)或请求的用户签约数据类型信息, 当后续对应的用户签约数据发生更 新时, HSS/HLR可以根据存储的相应的节点类型信息 (包括节点类型相关信 息)或请求的用户签约数据类型信息确定是否发送用户数据更新请求消息给对 应的节点,也就是只有当对应节点对应的用户签约数据发生改变时, HSS/HLR 才需要发送相应的用户数据更新请求消息。 比如当请求节点是独立的 MME, 而用户的 2G/3G (或 GPRS )签约数据或其它只适用于 SGSN的签约数据发生 更新时, HSS是不需要发送用户更新请求消息给 MME的。而且在 MME/SGSN 合设节点并且 UE在该合设节点的 MME和 SGSN上同时注册了的情况下, HSS/HLR 只需要发送一次用户数据更新请求消息给合设节点, 避免向 MME 和 SGSN分别发送用户数据更新请求消息,有效减少了 HSS和 MME或 SGSN
之间的信令交互。 In summary, the embodiment of the present invention can not only optimize the location update process, but also enable the node that stores the user subscription data to send the correct type of user subscription data, and can accurately record the location information of the user equipment. By storing the corresponding node type information (including the node type related information) or the requested user subscription data type information described in the above embodiments, when subsequent corresponding user subscription data is updated, the HSS/HLR may be configured according to the corresponding The node type information (including the node type related information) or the requested user subscription data type information determines whether to send the user data update request message to the corresponding node, that is, only when the user subscription data corresponding to the corresponding node changes, the HSS/HLR A corresponding user data update request message needs to be sent. For example, when the requesting node is an independent MME, and the user's 2G/3G (or GPRS) subscription data or other subscription data only applicable to the SGSN is updated, the HSS does not need to send a user update request message to the MME. Moreover, in the case that the MME/SGSN is connected to the node and the UE is simultaneously registered on the MME and the SGSN of the connected node, the HSS/HLR only needs to send the user data update request message once to the set node, avoiding the MME and the SGSN respectively. Send user data update request message, effectively reducing HSS and MME or SGSN Signaling interaction between.
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程 , 是可以通过计算机程序来指令相关的硬件来完成,所述的程序可存储于一计算 机可读取存储介质中,该程序在执行时,可包括如上述各方法的实施例的流程。 其中,所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory, ROM )或随机存储记忆体(Random Access Memory, RAM )等。 A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, the program When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
以上所述仅是本发明的优选实施方式,应当指出,对于本技术领域的普通 技术人员来说, 在不脱离本发明原理的前提下, 还可以作出若干改进和润饰, 这些改进和润饰也应视为本发明的保护范围。
The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It is considered as the scope of protection of the present invention.
Claims
1.一种在位置更新过程中与具有移动管理功能的节点进行信息交互的方 法, 其特征在于, 包括: A method for information interaction with a node having a mobility management function during a location update process, comprising:
接收具有移动管理功能的节点发出的位置更新请求,所述位置更新请求携 带请求的用户签约数据的类型; Receiving a location update request issued by a node having a mobility management function, the location update request carrying a type of user subscription data requested;
根据所述请求的用户签约数据的类型向所述具有移动管理功能的节点发 送用户签约数据。 User subscription data is sent to the node having the mobility management function according to the type of the requested subscriber subscription data.
2.如权 1所述的方法, 其特征在于, 包括: 2. The method of claim 1, comprising:
存储具有移动管理功能的节点请求的用户签约数据的类型; The type of user subscription data requested by the node storing the mobility management function;
当所述用户签约数据类型对应的用户签约数据发生更新时,根据存储的具 有移动管理功能的节点所请求的用户签约数据的类型向所述具有移动管理功 能的节点发送用户数据更新请求消息。 When the user subscription data corresponding to the user subscription data type is updated, the user data update request message is sent to the node having the mobility management function according to the type of the user subscription data requested by the stored node having the mobility management function.
3.如权 1所述的方法, 其特征在于, 包括: 3. The method of claim 1, comprising:
如果与发出所述位置更新请求的具有移动管理功能的节点之间设置有具 有协议转换功能的节点 ,则获得的所述位置更新请求是通过具有协议转换功能 的节点获得的,发送的用户签约数据是通过具有协议转换功能的节点到达所述 发出所述位置更新请求的具有移动管理功能的节点的。 If a node having a protocol conversion function is provided between a node having a mobility management function that issues the location update request, the obtained location update request is obtained by a node having a protocol conversion function, and the transmitted user subscription data is The node having the mobility management function that sends the location update request is reached by the node having the protocol conversion function.
4.一种在位置更新过程中与具有移动管理功能的节点进行信息交互的方 法, 其特征在于, 包括: 4. A method of information interaction with a node having a mobility management function during a location update process, comprising:
接收具有移动管理功能的节点发出的位置更新请求,所述位置更新请求携 带所述具有移动管理功能的节点的类型相关信息,所述类型相关信息至少包括 所述具有移动管理功能的节点的类型; 根据所述具有移动管理功能的节点的类型向所述具有移动管理功能的节 点发送用户签约数据。 Receiving a location update request issued by a node having a mobility management function, the location update request carrying type-related information of the node having the mobility management function, where the type-related information includes at least a type of the node having the mobility management function; User subscription data is transmitted to the node having the mobility management function according to the type of the node having the mobility management function.
5.如权利要求 4所述的方法, 其特征在于, 所述位置更新请求还携带所述 具有移动管理功能的节点所需要的用户签约数据的类型 ,所述根据所述具有移 动管理功能的节点的类型向所述具有移动管理功能的节点发送用户签约数据 具体为:根据所述具有移动管理功能的节点的类型和所需要的用户签约数据的
类型向所述具有移动管理功能的节点发送用户签约数据。 The method according to claim 4, wherein the location update request further carries a type of user subscription data required by the node having the mobility management function, the node according to the mobility management function The type of sending the user subscription data to the node having the mobility management function is specifically: according to the type of the node having the mobility management function and the required user subscription data. The type sends user subscription data to the node having the mobility management function.
6.如权利要求 5所述的方法, 其特征在于, 如果所述具有移动管理功能的 节点为移动性管理节点 MME与服务通用分组无线业务支持节点 SGSN合设节 点, 且所需要的用户签约数据的类型为 MME 对应类型的用户签约数据和 SGSN对应类型的用户签约数据时, 则向所述具有移动管理功能的节点发送的 用户签约数据是 MME对应类型的用户签约数据和 SGSN对应类型的用户签约 数据。 The method according to claim 5, wherein if the node having the mobility management function is a node for the mobility management node MME and the serving general packet radio service support node SGSN, and the required user subscription data is The user subscription data sent to the node with the mobility management function is the user subscription data of the corresponding type of the MME and the user of the corresponding type of the SGSN, when the type of the subscriber subscription data of the MME corresponding type and the subscriber subscription data of the SGSN corresponding type are used. data.
7.如权利要求 6所述的方法, 其特征在于, 对于移动性管理节点 MME与 服务通用分组无线业务支持节点 SGSN合设节点, 若所述合设节点已经获得 MME对应类型的用户签约数据和 SGSN对应类型的用户签约数据, 则当用户 设备由 MME切换到 SGSN为其提供服务时,所述 MME将 SGSN对应类型的 用户签约数据发送给 SGSN, 或者, 当用户设备由 SGSN切换到 MME为其提 供服务时, 所述 SGSN将 MME对应类型的用户签约数据发送给 MME。 The method according to claim 6, wherein the mobility management node MME and the serving general packet radio service support node SGSN are combined with a node, and if the association node has obtained the user subscription data of the MME corresponding type, The SGSN corresponds to the type of user subscription data, and when the user equipment is switched from the MME to the SGSN, the MME sends the user subscription data of the SGSN to the SGSN, or when the user equipment is switched by the SGSN to the MME. When the service is provided, the SGSN sends the user subscription data of the MME corresponding type to the MME.
8.如权利要求 4所述的方法, 其特征在于, 如果与发出所述位置更新请求 的具有移动管理功能的节点之间设置有具有协议转换功能的节点,则获得的所 述位置更新请求是通过具有协议转换功能的节点获得的 ,发送的用户签约数据 是通过具有协议转换功能的节点到达所述发出所述位置更新请求的具有移动 管理功能的节点的。 The method according to claim 4, wherein if the node having the protocol conversion function is provided between the node having the mobility management function that issues the location update request, the obtained location update request is The user subscription data transmitted by the node having the protocol conversion function is reached by the node having the protocol conversion function to the node having the mobility management function that issues the location update request.
9.如权利要求 4所述的方法, 其特征在于, 进一步包括: 存储具有移动管 理功能的节点的类型; 当所述类型对应的节点对应的用户签约数据发生更新 时, 向所述类型对应的节点发送用户数据更新请求消息。 The method according to claim 4, further comprising: storing a type of a node having a mobility management function; and when the user subscription data corresponding to the node corresponding to the type is updated, corresponding to the type The node sends a user data update request message.
10.如权利要求 5所述的方法, 其特征在于, 进一步包括: 存储具有移动 管理功能的节点所需要的用户签约数据的类型;当所述用户签约数据类型对应 的用户签约数据发生更新时,向所述具有移动管理功能的节点发送用户数据更 新请求消息。 The method according to claim 5, further comprising: storing a type of user subscription data required by the node having the mobility management function; when the user subscription data corresponding to the user subscription data type is updated, A user data update request message is sent to the node having the mobility management function.
11.一种存储用户签约数据的节点, 其特征在于, 包括: A node for storing user subscription data, comprising:
位置更新请求获得单元,用于接收具有移动管理功能的节点发出的位置更
新请求, 所述位置更新请求携带所述具有移动管理功能的节点的类型相关信 息, 所述类型相关信息至少包括所述具有移动管理功能的节点的类型; a location update request obtaining unit for receiving a location issued by a node having a mobility management function a new request, the location update request carries type-related information of the node having the mobility management function, where the type-related information includes at least a type of the node having the mobility management function;
用户签约数据发送单元,用于根据所述位置更新请求获得单元获得的所述 具有移动管理功能的节点的类型,向所述具有移动管理功能的节点发送用户签 约数据。 The user subscription data sending unit is configured to send the user subscription data to the node having the mobility management function according to the type of the node having the mobility management function obtained by the location update request obtaining unit.
12.如权利要求 11所述的存储用户签约数据的节点, 其特征在于, 进一步 包括: 第一存储单元,用于存储所述位置更新请求获得单元接收的所述具有移动 管理功能的节点的类型; 第一发送单元, 用于和所述第一存储单元相连, 当所述类型对应的节点对 应的用户签约数据发生更新时,向所述类型对应的节点发送用户数据更新请求
The node for storing user subscription data according to claim 11, further comprising: a first storage unit, configured to store the type of the node having the mobility management function received by the location update request obtaining unit a first sending unit, configured to be connected to the first storage unit, and send a user data update request to a node corresponding to the type when the user subscription data corresponding to the node corresponding to the type is updated.
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810145082 | 2008-08-01 | ||
CN200810145082.3 | 2008-08-01 | ||
CN200910127875.7 | 2009-04-10 | ||
CN200910127875 | 2009-04-10 | ||
CN200910141780.0 | 2009-05-18 | ||
CN2009101417800A CN101909274A (en) | 2008-08-01 | 2009-05-18 | Method for interacting information and nodes for storing user subscription data |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010012241A1 true WO2010012241A1 (en) | 2010-02-04 |
Family
ID=41609975
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/073015 WO2010012241A1 (en) | 2008-08-01 | 2009-07-31 | Method for performing information interaction and node for storing user subscribed data |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101909274A (en) |
WO (1) | WO2010012241A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2682856C1 (en) * | 2015-04-03 | 2019-03-21 | Хуавэй Текнолоджиз Ко., Лтд. | Access to the wireless communication network, associated device and system |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1642083A (en) * | 2004-09-23 | 2005-07-20 | 华为技术有限公司 | Network side anthority-discrimination-mode selecting method |
CN1798140A (en) * | 2004-12-28 | 2006-07-05 | 上海贝尔阿尔卡特股份有限公司 | General home location register of supporting signaling in different types of network protocols, and querying method |
-
2009
- 2009-05-18 CN CN2009101417800A patent/CN101909274A/en active Pending
- 2009-07-31 WO PCT/CN2009/073015 patent/WO2010012241A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1642083A (en) * | 2004-09-23 | 2005-07-20 | 华为技术有限公司 | Network side anthority-discrimination-mode selecting method |
CN1798140A (en) * | 2004-12-28 | 2006-07-05 | 上海贝尔阿尔卡特股份有限公司 | General home location register of supporting signaling in different types of network protocols, and querying method |
Non-Patent Citations (4)
Title |
---|
3GPP TSG CT: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diamete Protocol (Release 8)", 3GPP TS 29.272 VL .1.0, June 2008 (2008-06-01) * |
HUAWEI ET AL.: "Clarification the Subscription Data related with S6a, S6d, Gr+ and IWF", 3GPP TSG CT WG4 MEETING #39BIS C4-081669, 23 June 2008 (2008-06-23) * |
HUAWEI: "Clarification on the IWF Scenarios", 3GPP TSG CT WG4 MEETING #39BIS C4-081928, 23 June 2008 (2008-06-23) * |
NORTEL ET AL.: "Pseudo-CR on S6d/S6a Authentication Procedures", 3GPP TSG CT WG4 MEETING #39BIS C4-081989, - 23 June 2008 (2008-06-23) * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2682856C1 (en) * | 2015-04-03 | 2019-03-21 | Хуавэй Текнолоджиз Ко., Лтд. | Access to the wireless communication network, associated device and system |
US10419935B2 (en) | 2015-04-03 | 2019-09-17 | Huawei Technologies Co., Ltd. | Access method in wireless communications network, related apparatus, and system |
Also Published As
Publication number | Publication date |
---|---|
CN101909274A (en) | 2010-12-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5044020B2 (en) | Method, system and apparatus for supporting addressing of user static IP address in LTE system | |
WO2013047822A1 (en) | Communication system, method and apparatus | |
WO2016107161A1 (en) | Communication method, user equipment and communication device | |
WO2009000197A1 (en) | Method and network equipment for establishing and deleting resource | |
US20110287785A1 (en) | Method, device and system for obtaining user equipment location information | |
WO2014056445A1 (en) | Method, system, and controller for routing forwarding | |
WO2009149669A1 (en) | Data communication method, communication system and related devices | |
WO2009121251A1 (en) | A method, system and apparatus for implementing routing optimizing | |
WO2008131681A1 (en) | A method, a system and an apparatus for implementing a service of ip multimedia subsystem in a visit network | |
WO2008086754A1 (en) | Method, device and system for emergent registering in ip-connectively access network of user equipment | |
WO2009059532A1 (en) | Method and device for bearer operating | |
WO2009117891A1 (en) | A register method and equipment of packet data network connection | |
WO2009097772A1 (en) | Control method, communication system and relative device for resource release | |
US9332426B2 (en) | Communication system, communication method, and communication program | |
WO2010081329A1 (en) | Method and system for controlling network resources during service flow migrating procedure | |
WO2013189217A1 (en) | Method for updating identity information about packet gateway, aaa server and packet gateway | |
WO2010034195A1 (en) | Method for providing ip address of user equipment, diameter routing agent | |
JP2020520602A (en) | Select IP version | |
WO2018059401A1 (en) | Network switching method, device and system, and network access method and device | |
US9860869B2 (en) | Method and apparatus for offloading data traffic in a wireless communication system | |
WO2010124551A1 (en) | Method and system for preserving a packet data network gateway identifier in a multiple access scenario | |
WO2015068732A1 (en) | Communication control method, relay terminal apparatus, terminal apparatus, base station apparatus, control apparatus, server apparatus, and mobile communication system | |
WO2011157189A2 (en) | Method, device and system for reporting location | |
WO2012126302A1 (en) | Method and system supporting simultaneous communication for dual-mode, dual-standby terminal | |
WO2013029245A1 (en) | Bearer processing method, system and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09802434 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09802434 Country of ref document: EP Kind code of ref document: A1 |