CN102740442B8 - A kind of mthods, systems and devices for realizing static data synchronization - Google Patents

Abstract

The invention discloses a kind of method for realizing static data synchronization, after static data changes, home subscriber data server or attaching position register (HSS/HLR) find out mobility management unit corresponding with the static data of the change or Serving GPRS Support Node (MME/SGSN)；The static data of change is directly pushed to corresponding MME/SGSN by HSS/HLR using node level message, the invention also discloses a kind of method for realizing static data synchronization, system and device, pass through the above method and device, after the content of the static data in HSS/HLR is changed due to a variety of causes, the synchronization of static data in HSS/HLR and MME/SGSN can be realized.

Description

Method, system and device for realizing synchronization of static data

Technical field

[0001] The present invention relates to a user subscription data synchronization technology in the Third Generation Partnership Project (3GPP) system, and in particular to a method, system and device for realizing static data synchronization.

Background technique

[0002] In the field of mobile communications, Evolved Packet System (EPS) networks are gradually developing. Figure 1 is a schematic diagram of the structure of the EPS network. As shown in Figure 1, the non-roaming architecture of the EPS network mainly includes the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and the evolved packet The core network (Evolved Packet Core, EPC) has two parts. The EPC can support terminal access from a GSM EDGE radio access network (GSM EDGE radio access network, GERAN) and a universal terrestrial radio access network (Universal Terrestrial Radio Access Network, UTRAN).

[0003] The EPC includes a home subscriber data server 11 (Home Subscriber Server, HSS), a mobility management unit 12 (Mobility Management Entity, MME), a serving gateway 13 (Serving Gateway, S-GW or SGW), Packet Data Network Gateway 14 (PDNGateway, P-GW or PGW), Serving GPRS Support Node 15 (Serving GPRS Support Node, SGSN), and Policy and Charging Enforcement Function (PCRF) entity 16, in which:

[0004] HSS 11 is a permanent storage location for user subscription data, located in the home network of the user subscription;

[0005] MME12 is the storage location of user subscription data in the current network, and is responsible for terminal-to-network Non-Access Stratum (Non-Access Stratum, NAS layer) signaling management, and is responsible for tracking and locating the user’s terminal in idle mode. Implementation of call management functions and bearer management;

[0006] S-GW13 is the gateway from the core network to the wireless system, responsible for the user plane bearer from the user terminal to the core network, and also responsible for data caching of the terminal in idle mode, and also for the function of initiating service requests on the network side, and Realization of legal eavesdropping and packet data routing and forwarding functions;

[0007] The P-GW14 is a gateway between the EPS and the packet data network, and is responsible for the realization of functions such as terminal IP address allocation, charging functions, packet filtering, and policy application;

[0008] Specifically, the P-GW14 includes all the functions of a GPRS gateway support node (Gateway GPRS Support Node, GGSN), that is, the GGSN is regarded as a sub-function of the P-GW14 and is embedded in the P-GW14. The GGSN can support the edge routing function of the GPRS network, that is, the GGSN is responsible for routing and forwarding the data of the GPRS network, and protects the integrity of the GPRS network data through the firewall and filtering functions. In addition, GGSN also has a charging function. Therefore, the SGSN can directly connect to the P-GW14 and use the Gn/Gp interface.

[0009] The SGSN15 is a service support point for a radio network controller (GERAN/UTRAN) user to access the EPC network. The specific function is similar to that of the MME, and is responsible for user location update, paging management, bearer management and other functions.

[0010] Further, the HSS11 or home location register (HLR) is the main user database supporting calls/sessions. The user subscription data currently stored in the HSS/HLR can be roughly divided into three parts, namely user identification, dynamic data and static data. Among them, dynamic data includes data that will change such as the address information of MME12 and SGSN15, while static data refers to data that can be multiplexed by a large number of users, such as package information.

[0011] When a large number of users access the network for some reason and need to interact with HSS/HLR through MME/SGSN and obtain user subscription data, HSS/HLR needs to deliver complete user subscription data to MME/SGSN , Which may lead to overloading of each network in the network, and further cause no response to service requests, which greatly reduces the user's experience of using the service. In order to solve the above problems, a possible solution is to correspond the static data with the static data identifier. When the first user terminal on the MME/SGSN that contains the user subscription data of the static data accesses, the HSS/HLR will complete the user The subscription data is sent to the MME/SGSN, and for subsequent user terminals that access from this MME/SGSN, if this static data is also needed, only the corresponding static data identifier is issued, and the MME/SGSN generates the complete data locally. Of user subscription data. However, when the content of the static data in the HSS/HLR changes due to various reasons, under the premise that the static data identifier in the user subscription data remains unchanged, the content of the specific static data will become asynchronous, so that the MME /SGSN will generate incorrect complete user subscription data.

Summary of the invention

[0012] In view of this, the main purpose of the present invention is to provide a method, system and device for realizing static data synchronization, which can solve the problem of static data synchronization in HSS/HLR and MME/SGSN.

[0013] In order to achieve the above objective, the technical solution of the present invention is achieved as follows:

[00 M] The present invention provides a method for realizing static data synchronization, the method includes:

[0015] After the static data is changed, the HSS/HLR finds out the MME/SGSN corresponding to the changed static data; [0016] The HSS/HLR uses node-level messages to directly push the changed static data to the corresponding dirty/SGSN .

[0017] The present invention also provides a method for realizing static data synchronization, the method including:

[0018] After the static data is changed, the HSS/HUMME/SGSN sends a reset message, and the reset message carries the changed static data identifier;

[0019] The MME/SGSN sets the static data corresponding to the static data identifier as untrustworthy;

[0020] After the MME/SGSN receives the trigger message sent by the terminal, if the HSS/HLR queries that the subscription data contains a changed static data identifier, or the MME/SGSN queries that the subscription data contains a changed static data identifier, and If the corresponding static data is not credible, the HSS/HLR will synchronize the changed static data to the MME/SGSN.

[0021] Wherein, the HSS/HLR sending a reset message to the MME/SGSN includes:

[0022] The HSS/HLR sends a reset message to all connected MMEs/SGSNs; or the HSS/HLR finds the MME/SGSN related to the changed static data, and sends a reset message to it.

[0023] Wherein, the MME/SGSN inquires that the subscription data contains a changed static data identifier, and the corresponding static data is not credible, the HSS/HLR synchronizes the changed static data to the MME/SGSN, specifically:

[0024] MME/SGSN sends a location update request message to inform HSS/HLR that it supports static data identification; HSS/HLR returns user subscription data and static data identification to MME/SGSN; static data if changed in MME/SGSN The identifier is the same as the static data identifier of the current user, and the corresponding static data is in an untrusted state. The MME/SGSN obtains the changed static data from the HSS/HLR through the interaction of signaling, updates its own static data, and sets the status to available. letter;

[0025] Or the MME/SGSN queries the locally stored user subscription data and finds that it contains the changed static data identifier, and the corresponding static data is in an untrusted state, then the changed static data is obtained from the HSS/HLR through signaling interaction , And set the status to trusted after updating its own static data.

[0026] Wherein, the MME/SGSN obtains the changed static data from the HSS/HLR through signaling interaction, specifically:

[0027] This is achieved by using a subscription information request message and a subscription information response message, or an update location request message and an update location response message, or a new message is constructed.

[0028] Wherein, the HSS/HLR inquires that the subscription data contains a changed static data identifier, and then the Yang synchronizes the changed static data to the MME/SGSN with this ruler, specifically:

[0029] The MME/SGSN sends a location update request message to inform the HSS/HLR that it supports the static data identification function. The HSS/HLR query finds that the subscription data contains the changed static data identification, and the corresponding static data is not sent to the HSS/HLR. ^/ SGSN, the HSS/HLR sends the changed static data to the MME/SGSN, and the MME/SGSN updates its own static data and sets the status to be trusted.

[0030] The present invention also provides a device for realizing static data synchronization, and the device is specifically:

[0031] The HSS/HLR is used to find the MNE/SGSN corresponding to the changed static data after the static data is changed, and use node-level messages to directly push the changed static data to the corresponding mme/SGSN.

[0032] The present invention also provides a system for realizing static data synchronization. The system includes: HSS/HLR and MN E/SGSN, wherein,

[0033] The HSS/HLR is used to sense that the local static data changes and send a reset message to mme/SGSN. The reset message carries the changed static data identifier. After receiving the trigger message sent by the terminal, if you query When the contract data contains the changed static data identifier, the changed static data will be synchronized to mme/sgsn;

[0034] The MME/SGSN is used to set the static data corresponding to the static data identifier as untrustworthy after receiving the reset message, if the query data contains the changed static data identifier and its corresponding static data If it is not trustworthy, the changed static data synchronized by HSS/HLR is received.

[0035] Wherein, the HSS/HLR sending a reset message to the MME/SGSN includes:

[0036] The HSS/HLR sends a reset message to all connected MMEs/SGSNs; or the HSS/HLR finds the MME/SGSN related to the changed static data and sends a reset message to it.

[0037] Wherein, the MME/SGSN inquires that the subscription data contains a changed static data identifier, and the corresponding static data is not credible, then the changed static data synchronized by the HSS/HLR is received, specifically:

[0038] MME/SGSN sends a location update request message to inform HSS/HLR that it supports static data identification; HSS/HL responds to MME/SGSN to return user subscription data and static data identification; static data if changed in MME/SGSN The identifier is the same as the static data identifier of the current user, and the corresponding static data is in an untrusted state. mme/sgsn obtains the changed static data from the HSS/HLR through the interaction of signaling, and sets the status to be available after updating its own static data. letter;

[0039] Or the MME/SGSN queries the locally stored user subscription data and finds that it contains the changed static data identifier, and the corresponding static data is in an untrusted state, then the changed static data is obtained from the HSS/HLR through signaling interaction , And set the status to trusted after updating its own static data.

[0040] Wherein, the HSS/HLR inquires that the subscription data contains a changed static data identifier, and then receives the changed static data synchronized by the HSS/HLR, specifically:

[0041] The MME/SGSN sends a location update request message to inform the HSS/HLR that it supports the static data identification function. The HSS/HLR query finds that the subscription data contains the changed static data identification, and the corresponding static data is not sent to the HSS/HLR. ^/ SGSN, the HSS/HLR sends the changed static data to the MME/SGSN, and the MME/SGSN updates its own static data and sets the status to be trusted.

[0042] In the method, system and device for realizing static data synchronization provided by the present invention, after static data is changed, HSS/HLR finds out the MME/SGSN corresponding to the changed static data; HSS/HLR uses node level The message directly pushes the changed static data to the corresponding MME/SGSN. After the content of the static data in the HSS/HLR is changed due to various reasons, the static data in the HSS/HLR and MME/SGSN can be synchronized, so that after the MME/SGSN receives the trigger message, it generates the synchronized data. Complete user subscription data.

Description of the drawings

[0043] FIG. 1 is a schematic diagram of the structure of an EPS network;

[0044] FIG. 2 is a schematic flowchart of a method for realizing static data synchronization according to the present invention;

[0045] FIG. 3 is a schematic flowchart of an embodiment of the present invention for pushing static data through node-level messages;

[0046] FIG. 4 is a schematic flowchart of a method for realizing static data synchronization according to the present invention;

[0047] FIG. 5 is a schematic flowchart of Embodiment 1 of a method for synchronization of sending a static data identifier that is changed through a reset message according to the present invention;

[0048] FIG. 6 is a schematic flowchart of Embodiment 2 of a method for synchronization of sending static data identifiers that are changed through a reset message according to the present invention;

[0049] FIG. 7 is a schematic flowchart of Embodiment 3 of the synchronization method for sending a static data identifier that is changed by a reset message according to the present invention;

[0050] FIG. 8 is a schematic flowchart of Embodiment 4 of the synchronization method for sending a static data identifier that is changed by a reset message according to the present invention;

[0051] FIG. 9 is a schematic flowchart of Embodiment 5 of the synchronization method for sending a static data identifier that is changed through a reset message according to the present invention;

[0052] FIG. 10 is a schematic diagram of a system structure for realizing static data synchronization according to the present invention.

Detailed ways

[0053] The basic idea of ​​the present invention is that after static data changes, HSS/HLR finds out the MME/SGSN corresponding to the changed static data; HSS/HLR uses node-level messages to directly push the changed static data to the corresponding MME/SGSN〇

[0054] The technical solution of the present invention will be further elaborated below in conjunction with the drawings and specific embodiments.

[0055] FIG. 2 is a schematic flowchart of a method for realizing static data synchronization according to the present invention. As shown in FIG. 2, the method includes:

[0056] Step 201: After the static data is changed, the HSS/HLR searches for the MME/SGSN corresponding to the changed static data;

[0057] Specifically, the MN E/SGSN corresponding to the changed static data is specifically: a user whose user subscription data includes the changed static data accesses the HSS/HLR through the MME/SGSN.

[0058] Step 202: The HSS/HLR uses node-level messages to directly push the changed static data to the corresponding MME/SGSN.

[0059] Further, after receiving the changed static data, the MME/SGSN locally updates the user subscription data attached to it.

[0060] FIG. 3 is a schematic flowchart of an embodiment of the present invention for pushing static data through node-level messages. As shown in FIG. 3, the specific implementation steps of the embodiment are as follows:

[0061] Step 301, the HSS/HLR senses that the local static data has changed;

[0062] Step 302, HSS/HLR queries local records to find out the MME/SGSN related to this static data, that is, users whose subscription data contains this static data access the HSS/HLR through this MME/SGSN;

[0063] Step 3〇3, HSS/HLR uses node-level messages to directly push static data to the relevant MME/SGSN;

[00M] In step 304, the MME/SGSN locally uses the received static data to update the user subscription data attached to it.

[0065] FIG. 4 is a schematic flowchart of a method for realizing static data synchronization according to the present invention. As shown in FIG. 4, the method includes:

[0066] Step 401: After the static data is changed, the HSS/HLR sends a reset message to the MME/SGSN, and the reset message carries the changed static data identifier;

[0067] Specifically, the HSS/HLR sends a reset message to the MME/SGSN, including: the HSS/HLR sends a reset message to all connected MMEs/SGSNs; or the HSS/HLR finds the MME/s related to the changed static data. The SGSN sends a reset message to it.

[0068] Step 402, the MME/SGSN sets the static data corresponding to the static data identifier as untrustworthy;

[0069] Step 403, after the MME/SGSN receives the trigger message sent by the terminal, if the HSS/HLR inquires that the subscription data contains a changed static data identifier, or the MME/SGSN inquires that the subscription data contains changed static data If the corresponding static data is not credible, the HSS/HLR will synchronize the changed static data to the MME/SGSN.

[0070] Specifically, the trigger message includes: service request, tracking area update, or attachment messages. If the leg E/SGSN inquires that the subscription data contains the changed static data identifier, and the corresponding static data is not credible, the HSS/HLR will synchronize the changed static data to the leg E/SGSN, specifically: MME/SGSN Send a location update request message to inform HSS/HLR that it supports static data identification; HSS/HLR returns user subscription data and static data identification to MME/SGSN; if the static data identification is changed in MME/SGSN, the static data identification of the current user If the data identifier is the same, and the corresponding static data is in an untrusted state, the MME/SGSN obtains the changed static data from the HSS/HLR through the interaction of signaling, and sets the state to be trusted after updating its own static data; or MME/SGSN Query the locally stored user subscription data, and find that it contains the changed static data identifier, and the corresponding static data is in an untrusted state, then obtain the changed static data from the HSS/HLR through signaling interaction, and update its own static data Set the status to trusted. Wherein, the MME/SGSN obtains the changed static data from the HSS/HLR through the interaction of signaling, including: using a subscription information request message and a subscription information response message, or updating a location request message and updating a location response message, or constructing a new one Message to achieve.

[0071] The HSS/HLR inquires that the subscription data contains the changed static data identifier, and the HSS/HLR synchronizes the changed static data to the MME/SGSN, specifically: the MME/SGSN sends a location update request message to the HSS /HLR informs it to support the static data identification function. HSS/HLR finds that the subscription data contains changed static data identification, and the corresponding static data is not sent to the MME/SGSN, then HSS/HLR sends the changed static data to MME/SGSN, MME/SGSN updates its own static data and sets the status to be trusted.

[0072] FIG. 5 is a flowchart of Embodiment 1 of the synchronization method for sending a static data identifier that is changed through a reset message according to the present invention. As shown in FIG. 5, the specific implementation steps of the embodiment are as follows:

[0073] In step 51, the HSS/HLR senses that the local static data has changed;

[0074] In step 502, the HSS/HLR sends a reset message to all connected MME/SGSNs, and the reset message includes the identifier of the changed static data;

[0075] Step 503: The static data corresponding to the changed static data identifier set locally by the MME/SGSN is not trusted;

[0076] In step 504, the MME/SGSN receives a trigger message sent from the terminal. The trigger message may be a tracking area update or attach message, etc.;

[0077] Step 5〇5, MME/SGSN sends a location update request message to HSS/HLR, and informs HSS/HLR of its ability to support static data identification;

[0078] Step 506, if the MME/SGSN supports static data identification, the HSS/HLR will include the user subscription data and static data identification in the location update response message and send it to the MME/SGSN;

[0079] Specifically, if the MME/SGSN does not support static data identification, the HSS/HLR needs to deliver the complete user subscription data to the MME/SGSN. This situation is the same as the existing process processing, and will not be repeated here.

[0080] Step 507, if the changed static data identifier is the same as the static data identifier of the current user, and the local corresponding static data is still in an untrusted state, the MME/SGSN needs to initiate a subscription information request to change the static data identifier Send to HSS/HLR;

[0081] Step 508, HSS/HLR responds to the subscription information request and sends the static data corresponding to the changed static data identifier to the MME/SGSN;

[0082] Specifically, for the subscription information request or response, the message name is not limited to the subscription information request or response, and can be implemented by extending the existing update location request message or by adding a new message.

[0083] In step 509, the MME/SGSN updates the corresponding static data, and sets the status of the static data to be trusted, thereby allowing other users to subscribe data to be multiplexed.

[0084] FIG. 6 is a schematic flowchart of Embodiment 2 of the synchronization method for sending a static data identifier that is changed by a reset message according to the present invention. As shown in FIG. 6, the specific implementation steps of the embodiment are as follows:

[0085] Step 61: HSS/HLR senses that the local static data has changed;

[0086] Step 602, the HSS/HLR sends a reset message to all connected MME/SGSN, and the reset message includes the changed static data identifier;

[0087] Step 603, the static data corresponding to the changed static data identifier set locally by the MME/SGSN is not trusted;

[0088] Step 604: The MME/SGSN receives a trigger message sent from the terminal. The trigger message may be a tracking area update or attach message, etc.;

[0089] Step 605, MME/SGSN sends a location update request message to HSS/HLR, and informs HSS/HLR of its ability to support static data identification;

[0090] Step 606: If the HSS/HLR local query finds that the current user subscription data contains a changed static data identifier, and no new static data corresponding to this static data identifier is delivered to the MME/SGSN, then the HSS /HLR will send user subscription data and new dynamic data to MME/SGSN;

[0091] In step 607, the surface E/SGSN updates the corresponding static data, and sets the status of the static data to be trusted, thereby allowing other users to subscribe data to be multiplexed.

[0092^ FIG. 7 is a schematic flowchart of Embodiment 3 of the synchronization method for sending a static data identifier that is changed by a reset message according to the present invention. As shown in FIG. 7, the specific implementation steps of the embodiment are as follows:

[0093] Step 701, the HSS/HLR senses that the local static data has changed;

[0094] Step 702, the HSS/HLR queries the MME/SGSN related to the static data to send a reset message, and includes the changed static data identifier in the reset message. The static data corresponding to the static data identifier changed locally by the MME/SGSN is not trusted;

[0095] Step 703: The MME/SGSN receives a trigger message sent from the terminal. The trigger message may be a tracking area update or attach message, etc.;

[00%] Step 704, MME/SGSN sends a location update request message to HSS/HLR, and informs HSS/HLR of its ability to support static data identification;

[OO97] Step 705, if the MME/SGSN supports static data identification, the HSS/HLR will include the user subscription data and static data identification in the location update response message and send it to the MME/SGSN;

[0098] Step 706, if the changed static data identifier is the same as the static data identifier of the current user, and the static data of the local response is still untrusted, the MME/SGSN needs to initiate a subscription information request to change the static data identifier Send to HSS/HLR;

[00"] Step 707, the HSS/HLR responds to the subscription information request and sends the static data corresponding to the changed static data identifier to the MME/SGSN;

[0100] In step 708, the MN E/SGSN updates the corresponding static data, and sets the status of the static data to be trusted, thereby allowing other users to subscribe data to be multiplexed.

[0101] FIG. 8 is a schematic flowchart of Embodiment 4 of the synchronization method for sending a static data identifier that is changed by a reset message according to the present invention. As shown in FIG. 8, the specific implementation steps of the embodiment are as follows:

[0102] Step 801, the HSS/HLR senses that the local static data has changed;

[0103] Step 802, the HSS/HLR queries the MME/SGSN related to the static data to send a reset message, and includes the changed static data identifier in the reset message, and the E/SGSN locally sets the static data corresponding to the changed static data identifier Untrustworthy

[0104] Step 803: MME/SGSN receives the trigger message sent from the terminal;

[0105] Specifically, the trigger message may be a tracking area update or attachment message.

[0106] Step 804, MME/SGSN sends a location update request message to HSS/HLR, and informs HSS/HLR of its ability to support static data identification;

[0107] Step 805, if the HSS/HLR local query finds that the current user subscription data contains a changed static data identifier, and the changed static data corresponding to the changed static data identifier is not delivered to this MME/SGSN, then the HSS / HLR will send user subscription data and changed dynamic data to MME/SGSN;

[010S] Step 806, the MME/SGSN updates the corresponding static data, and sets the status of this static data to be trusted, thereby allowing other users to subscribe data to be multiplexed.

[0109] FIG. 9 is a schematic flowchart of Embodiment 5 of a synchronization method for sending a static data identifier that is changed through a reset message according to the present invention. As shown in FIG. 9, the specific implementation steps of the embodiment are as follows:

[0110] Step 901, the HSS/HLR senses that the local static data has changed;

[0111] Step 902, the HSS/HLR locally queries the MME/SGSN related to the changed static data, and then only sends a reset message to the related MME/SGSN, and the MME/SGSN locally sets the static data corresponding to the changed static data identifier Untrustworthy

[0112] Step 903: The MME/SGSN receives a trigger message sent from the terminal. The trigger message may be a tracking area update or a service request message, etc.;

[0113] Step 904, Xinjiang E/SGSN queries the locally stored user subscription data, and finds that it contains a changed static data identifier, and the corresponding static data is currently untrustworthy;

[01 M] Step 905, the MME/SGSN sends a location update request to the HSS/HLR and carries the changed static data identifier;

[0115] Step 906, the HSS/HLR returns the new static data to the MME/SGSN in the location update response message;

[0116] Step 907, the MN E/SGSN updates the corresponding static data, and sets the status of the static data to be trusted, thereby allowing other users to subscribe data to be multiplexed.

[0117] FIG. 10 is a schematic structural diagram of a system for realizing static data synchronization according to the present invention. As shown in FIG. 10, the system includes: HSS/HLR101 and MME/SGSN102, wherein,

[0118] The HSS/HLR101 is used to sense that the local static data has changed and send a reset message to mmE/sgsn1〇2, the reset message carries the changed static data identifier, and after receiving the trigger message sent by the terminal, If it is queried that the subscription data contains a changed static data identifier, the changed static data will be synchronized to the MME/SGSN102;

[0119] Specifically, the HSS/HLR101 sends a reset message to the MME/SGSN102, including: HSS/HLR101 sends a reset message to all connected MME/SGSN102; or HSS/HLR101 inquires about the MME/ SGSN102, send a reset message to it. The trigger message includes: service request, tracking area update, or attachment messages. [0120] The HSS/HLR101 inquires that the subscription data contains the changed static data identifier, and the HSS/HLR101 synchronizes the changed static data to the MME/SGSN102, specifically: the MME/SGSN102 sends a location update request message to HSS/HLR101 informs it to support static data identification function, HSS/HLR101 finds that the subscription data contains changed static data identification, and the corresponding static data is not sent to MME/SGSN102, then HSS/HLR101 will send the changed static data To the MME/SGSN 102, the MME/SGSN 102 updates its own static data and sets the status to be trusted.

[0121] The MME/SGSN 102 is used to set the static data corresponding to the static data identifier as untrusted after receiving the reset message, if the query data contains the changed static data identifier and its corresponding static data If it is not trustworthy, the changed static data synchronized by HSS/HLR101 is received.

[0122] Specifically, if the MME/SGSN 102 finds that the subscription data contains a changed static data identifier, and the corresponding static data is not credible, it receives the changed static data synchronized by the HSS/HLR 101, which is specifically: MME/SGSN102 sends a location update request message to inform HSS/HLR101 that it supports the static data identification function; HSS/HLR101 returns user subscription data and static data identification to MME/SGSN102; if the static data identification is changed in MME/SGSN102 and the current The static data identifier of the user is the same, and the corresponding static data is in an untrusted state, MME/SGSN102 obtains the changed static data from HSS/HLR101 through signaling interaction, and sets the state to be trusted after updating its own static data; or MME/SGSN102 queries the locally stored user subscription data, and finds that it contains the changed static data identifier, and the corresponding static data is in an untrusted state, it obtains the changed static data from HSS/HLR101 through signaling interaction, and updates its own Set the status to trusted after the static data. Wherein, the MN E/SGSN 102 obtains the changed static data from the HSS/HLR 101 through the interaction of signaling, including: using a subscription information request message and a subscription information response message, or updating a location request message and an update location response message, or constructing a new Message to achieve.

[0123] The present invention also discloses a device for realizing static data synchronization. As shown in FIG. 10, the HSS/HLR 101 in the system is used to find out the static data with the change after the static data is changed. The corresponding MME/SGSN 102 uses node-level messages to directly push the changed static data to the corresponding Xinjiang E/SGSN 102.

[0124] Specifically, the MME/SGSN 102 corresponding to the changed static data is specifically: a user whose user subscription data includes the changed static data accesses the HSS/HLR 101 through the MME/SGSN 102.

[0125] Further, after receiving the changed static data, the MME/SGSN 102 locally updates the user subscription data attached to it.

[0126] The above are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (9)

1. A method for realizing static data synchronization, characterized in that the method comprises: After the static data is changed, the HSS/HLR sends a reset message to the MME/SGSN, and the reset message carries the changed static data identifier; MME/ The SGSN sets the static data corresponding to the static data identifier as untrustworthy; after the MME/SGSN receives the trigger message sent by the terminal, if the HSS/HLR finds that the subscription data contains a changed static data identifier, or the MME/SGSN finds the subscription If the data contains a changed static data identifier, and the corresponding static data is not credible, the HSS/HLR will synchronize the changed static data to the MME/SGSN. 2. The method according to claim 1, wherein the HSS/HLR sends a reset message to the MME/SGSN, comprising: HSS/HLR sends a reset message to all connected MME/SGSN; or HSS/HLR finds The MME/SGSN related to the changed static data sends a reset message to it. 3. The method according to claim 1 or 2, wherein the MME/SGSN queries that the subscription data contains a changed static data identifier, and the corresponding static data is not credible, the HSS/HLR will change The static data is synchronized to the MME/SGSN, specifically: MME/SGSN sends a location update request message to inform HSS/HLR that it supports the static data identification function; HSS/HLR returns user subscription data and static data identification to MME/SGSN; If the changed static data identifier in the MME/SGSN is the same as the static data identifier of the current user, and the corresponding static data is in an untrusted state, the MME/SGSN obtains the changed static data from the HSS/HLR through signaling interaction, and updates itself Set the state to be trusted; or MME/SGSN inquires the locally stored user subscription data and finds that it contains the changed static data identifier, and the corresponding static data is in an untrusted state, then through the interaction of signaling The HSS/HLR obtains the changed static data, updates its own static data, and sets the status to be trusted. 4. The method according to claim 3, wherein the MME/SGSN obtains the changed static data from the HSS/HLR through signaling interaction, specifically: using a subscription information request message and a subscription information response message, or Update the location request message and update the location response message, or construct a new message to achieve. 5. The method according to claim 1 or 2, wherein the HSS/HLR finds that the subscription data contains a changed static data identifier, and the HSS/HLR synchronizes the changed static data to the MME/SGSN, Specifically: MME/SGSN sends a location update request message to inform HSS/HLR that it supports static data identification function, HSS/HLR query finds that the subscription data contains changed static data identification, and the corresponding static data is not sent to MME /SGSN, the HSS/HLR sends the changed static data to the MME/SGSN, and the MME/SGSN updates its own static data and sets the status to be trusted. 6. A system for realizing static data synchronization, characterized in that the system includes: HSS/HLR and MME/SGSN, where the HSS/HLR is used to sense the change of local static data, and then to /SGSN sends a reset message. The reset message carries the changed static data identifier. After receiving the trigger message sent by the terminal, if the contract data contains the changed static data identifier, the changed static data will be synchronized to the MME/ SGSN; the MME/SGSN is used to set the static data corresponding to the static data identifier as untrusted after receiving the reset message, if the query data contains the changed static data identifier, and the corresponding static data is not If the data is received, the changed static data synchronized by the HSS/HLR is received. 7. The system according to claim 6, wherein the HSS/HLR sends a reset message to the MME/SGSN, comprising: HSS/HLR sends a reset message to all connected MME/SGSN; or HSS/HLR finds The MME/SGSN related to the changed static data sends a reset message to it. 8. The system according to claim 6 or 7, wherein the MME/SGSN inquires that the subscription data contains a changed static data identifier, and the corresponding static data is not credible, then the HSS/HLR is received The synchronized changed static data is specifically: MME/SGSN sends a location update request message to inform HSS/HLR that it supports the static data identification function; HSS/HLR returns user subscription data and static data identification to MME/SGSN; in MME If the changed static data ID in the /SGSN is the same as the current user's static data ID, and the corresponding static data is not trusted, the MME/SGSN obtains the changed static data from the HSS/HLR through signaling interaction, and updates its own Set the status to trusted after the static data; or the MN E/SGSN queries the locally stored user subscription data and finds that it contains the changed static data identifier, and the corresponding static data is in an untrusted state, then through the signaling interaction The HSS/HLR obtains the changed static data, updates its own static data, and sets the status to be trusted. 9. The system according to claim 6 or 7, wherein the HSS/HLR queries that the subscription data contains a changed static data identifier, and then receives the changed static data synchronized by the HSS/HLR, specifically It is: MME/SGSN sends a location update request message to inform HSS/HLR that it supports static data identification function, HSS/HLR query finds that the subscription data contains changed static data identification, and the corresponding static data is not sent to MME/HLR. SGSN, the HSS/HLR sends the changed static data to the MME/SGSN, and the MME/SGSN updates its own static data and sets the status to be trusted.