WO2010012241A1 - Procédé de réalisation d'interaction d'informations et nœud de stockage de données souscrites par utilisateur - Google Patents

Procédé de réalisation d'interaction d'informations et nœud de stockage de données souscrites par utilisateur Download PDF

Info

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
Application number
PCT/CN2009/073015
Other languages
English (en)
Chinese (zh)
Inventor
时书锋
闫学霞
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010012241A1 publication Critical patent/WO2010012241A1/fr

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

L'invention porte sur un procédé de réalisation d'interaction d'informations avec un nœud ayant une fonction de gestion de mobilité dans une procédure de mise à jour de localisation. Le procédé comprend : la réception d'une requête de mise à jour de localisation envoyée par le nœud ayant la fonction de gestion de mobilité, la requête de mise à jour de localisation étant superposée au type de données souscrites par l'utilisateur demandées ; l'envoi des données souscrites par l'utilisateur au nœud à fonction de gestion de mobilité selon le type de données souscrites par l'utilisateur demandées. L'invention porte également sur un autre procédé de réalisation d'interaction d'informations avec un nœud ayant une fonction de gestion de mobilité dans une procédure de mise à jour de localisation et sur un nœud pour stocker des données souscrites par l'utilisateur.
PCT/CN2009/073015 2008-08-01 2009-07-31 Procédé de réalisation d'interaction d'informations et nœud de stockage de données souscrites par utilisateur WO2010012241A1 (fr)

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 (zh) 2008-08-01 2009-05-18 进行信息交互的方法及存储用户签约数据的节点

Publications (1)

Publication Number Publication Date
WO2010012241A1 true WO2010012241A1 (fr) 2010-02-04

Family

ID=41609975

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073015 WO2010012241A1 (fr) 2008-08-01 2009-07-31 Procédé de réalisation d'interaction d'informations et nœud de stockage de données souscrites par utilisateur

Country Status (2)

Country Link
CN (1) CN101909274A (fr)
WO (1) WO2010012241A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2682856C1 (ru) * 2015-04-03 2019-03-21 Хуавэй Текнолоджиз Ко., Лтд. Способ доступа в сети беспроводной связи, соответствующие устройство и система

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642083A (zh) * 2004-09-23 2005-07-20 华为技术有限公司 网络侧选择鉴权方式的方法
CN1798140A (zh) * 2004-12-28 2006-07-05 上海贝尔阿尔卡特股份有限公司 支持不同类型网络协议信令的通用归属位置寄存器及其查询方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642083A (zh) * 2004-09-23 2005-07-20 华为技术有限公司 网络侧选择鉴权方式的方法
CN1798140A (zh) * 2004-12-28 2006-07-05 上海贝尔阿尔卡特股份有限公司 支持不同类型网络协议信令的通用归属位置寄存器及其查询方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2682856C1 (ru) * 2015-04-03 2019-03-21 Хуавэй Текнолоджиз Ко., Лтд. Способ доступа в сети беспроводной связи, соответствующие устройство и система
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 (zh) 2010-12-08

Similar Documents

Publication Publication Date Title
US9763077B2 (en) Method and system for implementing data routing of roaming user
JP5044020B2 (ja) Ｌｔｅシステムにおいて、ユーザ静的ｉｐアドレスのアドレッシングをサポートする方法、システムおよび装置
US9560048B2 (en) Method for updating identity information about packet gateway, AAA server and packet gateway
WO2013047822A1 (fr) Système, procédé et appareil de communication
WO2016107161A1 (fr) Procédé de communication, équipement d'utilisateur et dispositif de communication
WO2009000197A1 (fr) Procédé et équipement réseau pour établir et effacer des ressources
US20110287785A1 (en) Method, device and system for obtaining user equipment location information
WO2014056445A1 (fr) Procédé, système et contrôleur pour transfert de routage
WO2009149669A1 (fr) Procédé de communication de données, son système de communication et dispositif s'y rapportant
WO2009121251A1 (fr) Procédé, système et appareil permettant de mettre en œuvre l’optimisation du routage
WO2008131681A1 (fr) Procédé, système et appareil de mise en œuvre d'un service de sous-système multimédia ip dans un réseau visité
WO2008086754A1 (fr) Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur
WO2009059532A1 (fr) Procédé et dispositif pour exploitation de support
WO2009117891A1 (fr) Procédé d'enregistrement et équipement de connexion à un réseau de données par paquet
WO2009097772A1 (fr) Procédé de commande, système de communication et dispositif correspondant pour une libération de ressource
US9332426B2 (en) Communication system, communication method, and communication program
WO2010081329A1 (fr) Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services
WO2010034195A1 (fr) Procédé pour obtenir l'adresse ip d'un équipement d'utilisateur, d'un agent de routage diameter
WO2011015140A1 (fr) Procédé, système et appareil pour radiomessagerie de télécommunication mobile
JP2020520602A (ja) Ｉｐバージョンの選択
WO2018059401A1 (fr) Procédé, dispositif et système de commutation de réseau, et procédé et dispositif d'accès au réseau
US9860869B2 (en) Method and apparatus for offloading data traffic in a wireless communication system
WO2010124551A1 (fr) Procédé et système pour préserver un identifiant de passerelle de réseau par paquets dans un scénario d'accès multiples
WO2015068732A1 (fr) Procédé de commande de communication, appareil terminal de relais, appareil terminal, appareil de station de base, appareil de commande, appareil serveur, et système de communications mobiles
WO2011157189A2 (fr) Procédé, dispositif et système de compte rendu de position

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