WO2010012241A1

WO2010012241A1 - Method for performing information interaction and node for storing user subscribed data

Info

Publication number: WO2010012241A1
Application number: PCT/CN2009/073015
Authority: WO
Inventors: 时书锋; 闫学霞
Original assignee: 华为技术有限公司
Priority date: 2008-08-01
Filing date: 2009-07-31
Publication date: 2010-02-04
Also published as: CN101909274A

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

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 (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.

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.

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 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;

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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) 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) 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) 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.

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

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) 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) 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) 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.

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:

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:

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:

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

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;

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.

Sixth embodiment

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:

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. 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 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.

Seventh embodiment

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:

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. 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:

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

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.

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

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.

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 (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;

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.

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

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匕

dagger.

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.

The specific process is shown in Figure 18.

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;

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.

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.

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.

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

Rights request

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. 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. 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. 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.

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.

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.

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.

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.

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.

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.

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.

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.