CN101247255B - Method and system for processing fault - Google Patents
Method and system for processing fault Download PDFInfo
- Publication number
- CN101247255B CN101247255B CN2007100792477A CN200710079247A CN101247255B CN 101247255 B CN101247255 B CN 101247255B CN 2007100792477 A CN2007100792477 A CN 2007100792477A CN 200710079247 A CN200710079247 A CN 200710079247A CN 101247255 B CN101247255 B CN 101247255B
- Authority
- CN
- China
- Prior art keywords
- network node
- user terminal
- communication device
- information
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 238000012545 processing Methods 0.000 title claims abstract description 39
- 238000004891 communication Methods 0.000 claims abstract description 144
- 238000012546 transfer Methods 0.000 claims abstract description 16
- 238000005516 engineering process Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 10
- 230000008569 process Effects 0.000 abstract description 12
- 238000010586 diagram Methods 0.000 description 5
- 244000287680 Garcinia dulcis Species 0.000 description 4
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- POXUQBFHDHCZAD-MHTLYPKNSA-N (2r)-2-[(4s)-2,2-dimethyl-1,3-dioxolan-4-yl]-3,4-dihydroxy-2h-furan-5-one Chemical compound O1C(C)(C)OC[C@H]1[C@@H]1C(O)=C(O)C(=O)O1 POXUQBFHDHCZAD-MHTLYPKNSA-N 0.000 description 1
- 101100490659 Arabidopsis thaliana AGP17 gene Proteins 0.000 description 1
- 101100049938 Neurospora crassa (strain ATCC 24698 / 74-OR23-1A / CBS 708.71 / DSM 1257 / FGSC 987) exr-1 gene Proteins 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 101150101384 rat1 gene Proteins 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention discloses a processing damage method which is: first network node determines second network node faults occur; the first network node executes corresponding process according to wireless access system of second network node, the user terminal of user surface context established on the second network node separates from the second network node by the process flow, or the user terminal is transferred to other network node. When network node goes wrong, this can transfer communicating context of corresponding user terminal effectually, and make other network node take-over said user terminal automatically, so the user terminal can initiate service process flow normally. The present invention also discloses a communication apparatus and communicating system.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for handling a failure in an evolved network.
Background
In an existing Evolved Network Architecture, a plurality of Radio Access systems (RAT systems) with different Radio Access technologies coexist, and as shown in fig. 1, the Evolved Network Architecture includes an Evolved Radio Access Network (Evolved RAN, E-RAN) belonging to a Long-term Evolution (Long-term Evolution, LTE) Network, an Evolved Packet Core (EPC) belonging to a System Architecture Evolution (SAE) Network, a GPRS Core (GPRS Core) belonging to a legacy universal Radio communication System/universal Packet Radio service (UMTS/GPRS) Network, a GSM EDGE Radio Access Network (GSM EDGE Radio Access Network, GERAN) Network, and a UMTS (Terrestrial Radio Access Network UMTS Terrestrial Radio Access Network, UTRAN).
As shown in fig. 1, a Mobility Management Entity (MME) in the EPC has a function of storing a user plane context of a User Equipment (UE), such as an identifier of a user, a Mobility Management state, tracking area information, and the like, and authenticating the UE; the User Plane Entity (UPE) has the function of terminating the downlink data of the UE in idle state, triggering paging, and storing the User Plane context of the UE, such as the IP address and routing information of the UE. The user plane Anchor (IASA) is a user plane Anchor for a user to access a packet data network, has functions of routing and forwarding packets, and completes Policy and Charging Enforcement Function (PCEF), collects Charging information, and the like. A Home Subscriber Server (HSS) is used to store Subscriber subscription information.
Based on the above evolved network architecture, when the UE moves between different RAT systems (e.g. 2G/3G UTRAN/GERAN network and LTE/SAE evolved network), the UE may cause ping-pong effect of frequent network registration procedures due to camping on different networks, thereby resulting in waste of air interface resources. For this phenomenon, referring to fig. 2, in the prior art, when the UE moves to RAT2 after being registered in RAT1 and performs network registration again, an association context of the UE is established between corresponding network nodes of two RAT systems, where the association context includes a UE user identifier, a temporary user identifier, a UE registered location area, network node information, and the like, so that the UE does not need to initiate any registration process when moving between registration areas (routing area RA or tracking area TA, and the like) corresponding to the two network nodes.
In the evolved network system, when a network node fails, an adjacent network node discovers the failed network node through a heartbeat message (e.g., an echo detection message in a user plane tunnel between two network nodes, or a heartbeat-beat message in an SCTP connection, etc.); wherein, the adjacent network node and the fault network node belong to the same RAT system or belong to two different RAT systems.
When a faulty network node is discovered in an evolved network, the prior art addresses the problem by following two approaches to handling faults in a UMTS network.
The first method comprises the following steps: although the UE can be effectively transferred by using this method, the related flow can only be triggered by the UE actively sending a request message, if downlink data of the UE arrives before the UE actively sending the request message, the downlink data will be discarded, which may result in that the UE cannot be paged normally, i.e. cannot receive traffic.
The second method is as follows: dividing N working network nodes into a backup group, carrying out static backup on data of the group by one (or more) backup devices for disaster recovery, and loading the data of a fault network node by the backup devices to take over the work of the network node when a certain network node fails; although the normal paging of the UE is not affected by using the method, certain network resources need to be reserved due to the need of data backup, and a certain amount of network equipment is occupied, so that the resource waste is caused.
It can be seen that the method for handling faults in the UMTS network is not suitable for the evolved network, and therefore, the problem to be solved currently is to provide a method for handling faults suitable for the evolved network.
Disclosure of Invention
The embodiment of the invention provides a method, a device and a system for processing faults, which are used for solving the problem that in the prior art, no method suitable for processing the faults per se exists in an evolution network.
A method of handling a fault comprising the steps of:
the first network node determines that the second network node fails;
the first network node carries out corresponding processing flow according to a wireless access system where a second network node is located, and the user terminal establishing the user plane context on the second network node is logged off from the second network node through the processing flow; wherein,
when the first network node determines that a second network node with a user terminal association context between the first network node and the node has a fault, the first network node sends a message for deleting the second network node information to the corresponding user terminal according to the user terminal association context; wherein the first network node and the second network node belong to wireless access systems of different wireless access technologies, respectively.
A method of handling a fault comprising the steps of:
the first network node determines that the second network node fails;
the first network node carries out corresponding processing flow according to a wireless access system where a second network node is located, and the user terminal establishing the user plane context on the second network node is logged off from the second network node through the processing flow;
wherein, if the first network node and the second network node belong to wireless access systems of different wireless access technologies, the processing flow includes the steps of:
the first network node sends the related information of the user terminal to a third network node, wherein the first network node and the second network node have the associated context of the user terminal, and the third network node and the second network node belong to the same wireless access system;
and the third network node performs network registration according to the received related information of the user terminal, and the user terminal records the information of the third network node and deletes the information of the second network node.
A method of handling a fault comprising the steps of:
the first network node determines that the second network node fails;
the first network node carries out corresponding processing flow according to a wireless access system where a second network node is located, and the user terminal establishing the user plane context on the second network node is logged off from the second network node through the processing flow; wherein,
if the first network node and the second network node belong to the same wireless access system, the processing flow comprises the following steps:
when receiving downlink data, the user plane anchor point sends a paging request message to the first network node, wherein the paging request message carries relevant information of the user terminal;
and the first network node acquires the information of the user terminal from the user terminal according to the relevant information of the user terminal and performs network registration.
And after the first network node finishes the registration, the user terminal is instructed to delete the information of the second network node locally, and the information of the first network node is recorded.
A communication system, comprising:
the user terminal is used for establishing connection with the corresponding communication device so as to complete data communication;
the communication device comprises a plurality of communication devices and a control module, wherein when a first communication device determines that a second communication device has a fault, the first communication device carries out corresponding processing flow according to a wireless access system where the second communication device is located, and the user terminal establishing a user plane context on the second communication device is logged off from the second communication device through the processing flow;
when the first communication device determines that a second communication device with a user terminal association context between the first communication device and the second communication device has a fault, the first communication device sends a message for deleting information of the second communication device to a corresponding user terminal according to the association context of the user terminal; the first communication device and the second communication device belong to wireless access systems of different wireless access technologies respectively.
A communication system, comprising:
the user terminal is used for establishing connection with the corresponding communication device so as to complete data communication;
the communication device comprises a plurality of communication devices and a control module, wherein when a first communication device determines that a second communication device has a fault, the first communication device carries out corresponding processing flow according to a wireless access system where the second communication device is located, and the user terminal establishing a user plane context on the second communication device is logged off from the second communication device through the processing flow;
if the first communication device and the second communication device belong to wireless access systems of different wireless access technologies respectively, the first communication device sends related information of a user terminal to a third communication device, wherein the first communication device and the second communication device have an associated context of the user terminal, and the third communication device and the second communication device belong to the same wireless access system; and the third communication device performs network registration according to the received related information of the user terminal, and the user terminal records the information of the third communication device and deletes the information of the second communication device.
A communication system, comprising:
the user terminal is used for establishing connection with the corresponding communication device so as to complete data communication;
the communication device comprises a plurality of communication devices and a control module, wherein when a first communication device determines that a second communication device has a fault, the first communication device carries out corresponding processing flow according to a wireless access system where the second communication device is located, and the user terminal establishing a user plane context on the second communication device is logged off from the second communication device through the processing flow;
if the first communication device and the second communication device belong to the same wireless access system, the user plane anchor point sends a paging request message to the first communication device when receiving downlink data, wherein the paging request message carries relevant information of the user terminal; the first communication device acquires the information of the user terminal from the user terminal according to the relevant information of the user terminal and carries out network registration; and after the first communication device finishes the registration, the first communication device instructs the user terminal to delete the information of the second communication device locally, and records the information of the first communication device.
In the embodiment of the invention, after the user terminal is registered in the network, if the adjacent network node finds that the network node registered by the user is in fault, the adjacent network node separates the user terminal from the fault network node or transfers the user terminal from the fault network node to another network node, so that the communication context of the user terminal can be effectively transferred, other network nodes automatically take over the user terminal, the user terminal can normally initiate a service process, the continuity of user services is maintained, and the use experience of the user is improved.
Drawings
FIG. 1 is a diagram of an evolved network architecture in the prior art;
FIG. 2 is a diagram illustrating an evolved network architecture in the prior art;
FIG. 3A is a diagram illustrating an evolved network architecture according to an embodiment of the present invention;
FIG. 3B is a functional block diagram of a network node according to an embodiment of the present invention;
FIG. 4 is a flow chart of a detached user terminal in an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a re-registration process of a UE according to an embodiment of the present invention;
FIGS. 6 and 7 are flow diagrams of a transfer user terminal in the practice of the present invention;
FIG. 8 is a flowchart of a user plane anchor point triggered transfer user terminal according to an embodiment of the present invention;
fig. 9 is a flowchart of an access node triggering transfer of a ue in an embodiment of the present invention.
Detailed Description
In the embodiment of the invention, when a first network node in an evolution network determines that a second network node has a fault, the first network node performs a corresponding processing flow according to a wireless access system where the second network node is located, and a user terminal establishing a user plane context on the second network node is cancelled from the second network node through the processing flow, wherein the cancellation comprises the step of separating the user terminal from the second network node or transferring the user terminal from the second network node to other network nodes.
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
Referring to fig. 3A, in the embodiment of the present invention, the communication system includes two Radio Access Technology (RAT) systems, namely, a 2G/3G network and an LTE/SAE network, which are referred to as RAT a and RAT B, respectively. Access network nodes in RAT a are referred to as access node a1 and access node a2.. said.., core network nodes in RATA are referred to as network node a1 and network node a2.. said.., and similarly, access network nodes in RAT B are referred to as access node B1 and access node b2... said., core network nodes in RAT B are referred to as network node B1 and network node B2.. said.., and there is a common user plane anchor point in RAT a and RAT B, which may be the same physical entity as a certain network node or an independent physical entity.
Referring to fig. 3B, a network node (which may be the network node a1 or the network node B1) in the communication system includes a communication unit, a determination unit, and a processing unit. The communication unit is used for carrying out information interaction with other network nodes or user terminals; the judging unit is used for determining that another network node has a fault according to the heartbeat detection message; the processing unit is configured to perform a corresponding processing procedure according to a wireless access system in which a failed network node is located, delete information of the network node by a user equipment that establishes a user plane context on the failed network node through the processing procedure, separate the user equipment from the failed network node, or transfer the user equipment to another network node.
Based on the above network architecture, in this embodiment, an association context of a certain User Equipment (UE) has been established between the network node a1 and the network node B1, and when the network node a1 detects that the network node B1 fails through a heartbeat message, the network node a1 obtains a network address of the UE according to the association context of the UE, and initiates a Detach (Detach) procedure for the UE, so as to force the UE to Detach from the radio access system RAT B in which the network node B1 is located, that is, instruct the UE to locally delete all information related to the network node B1.
Referring to fig. 4, the detailed procedure of the network node a1 for initiating the detach procedure for the UE is as follows:
step 400: network node a1 initiates a detach request message to the UE indicating that the UE is detached from RAT B.
In general, the network node a1 cannot know that the radio access system where the UE is currently located is RAT a or RATB, so the network node a1 directly sends a detach request message to the UE in RATA; and simultaneously, selecting a network node B2 from the RATB, and forwarding a separation request message to the UE by the network node B2, wherein the separation request message contains the information of the UE, including the user identifier, the temporary user identifier, other UE characteristic identifiers (such as IP addresses) of the UE, the location area information of the UE in the RAT B and the like. Of course, if the network node a1 can know in advance whether the radio access system where the UE is located is RATA or RATB, the network node a1 may select one of the two manners to send the detach request message.
If the user plane anchor receives downlink data sent to the UE and initiates a data notification request message to network node a1 before network node a1 sends a detach request message, network node a1 also notifies the UE that downlink data is coming when sending the detach request message.
Step 401: network node a1 initiates the UE's user plane context update procedure to the user plane anchor.
In this process, the user plane anchor activates the user plane context of the UE locally associated with network node B1 and locally deletes the UE information associated with network node B1.
Step 402: the network node a1 sends a detach indication message to a Home Subscriber Server (HSS), where the message carries information related to RAT B, and the HSS server deletes locally stored association information between the network node B1 and the UE.
On the other hand, network node a1 also deletes the information of network node B1 locally.
Step 403: after receiving the detach request message sent by network node a1, the UE detaches the UE from network node B1, deletes the information about network node B1 locally, and returns a detach accept message to network node a1 after the operation is completed.
The UE may send the detach accept message directly to network node a1 or first to network node B2 and forwarded by network node B2 to network node a 1.
Step 404: if the wireless access system where the UE is currently located is RAT A, the UE locally deletes the information of the network node B1, updates the communication context of the UE and receives downlink data when the downlink data are found; if the wireless access system where the UE is currently located is RAT B, the UE deletes the information of the network node B1, re-registers to a new network node in RAT B, updates its communication context, and receives downlink data if the downlink data is found.
Unlike the above embodiments, network node A1 may also initiate a Re-registration (Re-RAU/TAU, Re-attach) procedure to request the UE to Re-register with another network node in RAT B when discovering that network node B1 has failed. Referring to fig. 5, the detailed procedure for the network node a1 to instruct the UE to re-register is as follows:
step 500: network node a1 sends a Re-registration request message (Re-RAU/Re-TAU, Re-attach) to the UE requesting the UE to Re-register with another new network node in RAT B. Similarly, the network node a1 directly sends the re-registration request message to the UE, and forwards the re-registration request message through the network node B2 in the RAT B, where the re-registration request message includes the UE's UE user identity, temporary user identity and other UE feature identities (such as IP addresses), and the location area information of the UE registered in the RAT system.
Step 501: if the UE is camping on RAT a, the UE replies a re-registration response message to network node a1 after receiving the re-registration request message, and then sends a registration request message to the corresponding network node B, where the re-registration response message includes information about whether the UE is registered to the RATB (e.g., will initiate re-registration in RAT B or not initiate re-registration temporarily, etc.).
If the UE is camped on RAT B, the UE directly initiates a registration request to the network, and the network node to which the UE is registered may be network node B2 or other network nodes, i.e., the network node forwarding the re-registration response message and the network node to which the UE is re-registered may be the same network node or different network nodes. In this embodiment, a case where the UE is registered in the network node B2 will be described as an example.
Step 502: the network node B2 acquires the UE's communication context (including one or more of the UE's mobility management context, user plane context, and association context) from the network node a1, and performs network registration with the HSS; during registration, the HSS locally deletes the association information of the UE with network node B1 and sends the user subscription information of the UE to network node B2.
Step 503: the network node B2 replies to the UE with a registration receipt message carrying the temporary user identity assigned by the network node B2.
Step 504: the UE replies to network node B2 with a registration complete message.
Step 505: the UE initiates a user plane context update procedure between network node a1, network node B2, and the user plane anchor. In this process, the UE, network node a1 and the user plane anchor locally delete the UE's associated information with network node B1 while recording the network node B2's associated information, while network node B2 locally records the UE's associated information.
When the UE discovers downlink data, the downlink data may be received by network node a1 or network node B2 regardless of whether the UE is in RAT a or RAT B.
In addition, network node a1 may also transfer the UE to another network node in RAT B upon discovering that network node B1 failed. In this embodiment, the network node a1 may transfer the UE by two methods.
The first method comprises the following steps: network node a1 selects another network node B2 in RAT B, initiates a temporary user identity reallocation procedure by network node B2, sends the new temporary user identity to the UE for UE transfer. Referring to fig. 6, the detailed flow of the first method is as follows:
step 600: network node a1 selects another new network node B2 in RAT B and sends a user transfer request message to network node B2 for transferring UEs, which contains information such as user identity (IMSI) and temporary user identity (P-TMSI, S-TMSI). The user transfer request message may be initiated by network node a1 actively, or when network a1 needs to forward the UE's downlink data to network node B1.
Step 601: the network node B1 obtains the UE communication context from the network node a1, then the network node B1 and the network node a1 establish the UE association context, and the network node B1 registers with the HSS, during the registration process, the HSS locally deletes the association information between the UE and the network node B1, and sends the UE user subscription information to the network node B1.
Step 602: the network node B2 returns a user transfer response message to network node a 1.
Step 603: the network node B2 initiates a temporary user identity reallocation procedure in which the network node B2 sends the new temporary user identity to the UE.
Step 604: the UE, network node A1, network node B2 and the user anchor initiate an update flow of the UE's user plane context. In this update procedure, the UE, network node a1 and the user plane anchor locally delete the association information of the UE with network node B1 while recording the association information of network node B2, while network node B2 locally records the association information of the UE.
When the UE discovers that there is downlink data, whether the UE is in RATA or RAT B, the downlink data may be received through network node a1 or network node B2.
The second method is as follows: the network node a1 resolves the temporary mobile user identity of the UE, transfers the UE to a new network node B2, the network node B2 allocates a new feature identity to the UE and informs the access node B1 of the corresponding location area (TA/RA) in the RATB, the access node B1 establishes a correlation between the feature identity allocated by the network node B1 and the feature identity allocated by the network node B2, if the configuration capability of the access node B1 cannot establish a correlation between the two feature identities, the access node B1 informs the network node B2 that the network node B2 instructs the UE to re-register in the RAT B.
Referring to fig. 7, in the present embodiment, the detailed flow of the second method is as follows:
step 700: network node a1 sends the UE's communication context to network node B2.
In the process, network node a1 first resolves the UE's temporary mobile subscriber identity, then selects a new network node B2 in RAT B, and sends the UE's communication context to network node B2.
Step 701: the network node B2 assigns a new signature (called B2) to the UE and informs the access node B1 of the corresponding location area in the RATB; the association between the signature assigned by network node B1, referred to as B1, and B2 was established by access node B1.
Step 702: the network node B2 informs the network node A1 that the UE's communication context has been received, and then the network node B2 and the network node A1 establish the UE's association context.
Step 703: the network node B2, network node A1 and the user plane anchor initiate an update procedure of the UE user plane context. In this update procedure, network node a1 and the user plane anchor locally delete the UE's association information with network node B1 while recording the network node B2's association information, while network node B2 locally records the UE's association information.
Step 704: the network node B2 performs network registration with the HSS to obtain user subscription information for the UE, which locally deletes association information between the UE and the network node B1.
If the UE is currently in RAT a, the UE initiates an access request message to network node a, and updates the local user plane context after the network node a1 returns an access accept message, at this time, the UE may have actively requested a service or received corresponding downlink data.
If the UE is currently in RAT B, the UE sends an access request message to access node B1, after access node B1 parses the temporary mobile subscriber identity of the UE, the access request message is forwarded to network node B2 according to the association information between B1 and B2, and after receiving an access accept message returned by network node B2, the UE updates the local user plane context, and at this time, the UE may have actively requested a service or received corresponding downlink data.
In the above embodiments, the network node a1 and the network node B1 are in different radio access systems (RAT a and RAT B), respectively, and when another network node a2 in RAT a with the network node a1 fails, if a UE currently camps on a location area corresponding to the network node a2 (i.e., the network node a2 has the user plane context of the UE), the network node a1 transfers the UE to the local network node, instead of the network node a2, to provide service for the UE.
Referring to fig. 8, when downlink data arrives, the detailed flow of the network node a1 transferring the UE is as follows:
step 800: the user plane anchor point receives the downlink data of the UE,
step 801: the user-plane anchor sends a data notification to network node a2 and determines that network node a2 cannot reply to the response message.
Step 802: the user plane anchor sends a paging request message to network node a1, which includes the UE's subscriber identity (IMSI and/or P-TMSI, etc.) and location area information, etc.
Step 803: the network node a1 sends a paging request message to the UE in the location area where the UE is located, where the message carries the user identifier (IMSI and/or P-TMSI, etc.) of the UE, and if the network node a1 cannot know the registration area where the UE is located, the network node a1 pages the UE in all location areas corresponding to the network node pool where the network node a2 is located or all location areas governed by the network node a2, and carries the identity identifier (IMSI) of the UE, the temporary user identifier allocated by the network node a1, and the like.
Step 804: after receiving the paging request message, the UE updates the local temporary user identifier, and replies a paging response message to the network node a1, where the message carries information of the UE itself.
Step 805: the network node a1 initiates a security authentication procedure for the UE, i.e. determines whether the UE has the right to use the corresponding traffic service.
Step 806: after receiving the paging response message, the network node a1 performs network registration with the HSS, and during the registration, the network node a1 sends a location update location request message to the HSS, where the message carries the identification information of the UE and the identification information of the network node a 1.
Step 807: the HSS replies to network node a1 with an update location response message, which carries the user subscription information of the UE.
Step 808: network node a1 initiates an update procedure for the UE user plane context between the UE, network node a1, and the user plane anchor, in which the UE and the user plane anchor delete locally the association information of the UE with network node a2, record the relevant information of network node a1, and network node a1 records locally the relevant information of the UE.
Step 809: and the user plane anchor point forwards the received downlink data to the UE.
Referring to fig. 9, when the UE actively sends the service request message, the detailed flow of the network node a1 transferring the UE is as follows:
step 900: the UE initiates a traffic request message to network device a2 via access node b 1.
Step 901: access node b1 is unable to send a service request message to network node a2, access node b1 forwards the service request message to the newly selected network node a 1.
Step 902: network node a1 obtains the UE's identity (IMSI, etc.) from the UE.
Step 903: network node a1 initiates a secure authentication procedure for the UE.
Step 904: the network node A1 carries out network registration to HSS, when registering, the network node A1 sends a location updating request message to HSS, and the message carries the identification information of UE and the identification information of the network node A1; and the HSS replies to network node a1 with an update location response message, sending the user subscription information of the UE to network node a 1.
Step 905: after registering to the HSS, the network node a1 replies to the UE with a service accept message, where the message carries the temporary user identity of the network node a 1.
Step 906: the UE initiates an updating process of the communication context, in the updating process, the network node A1 obtains the user plane context of the UE from the user plane anchor point, and the UE, the access node b1 and the user plane anchor point delete the associated information of the UE and the network node A2 locally, record the associated information of the network node A1, and the network node A1 records the associated information of the UE locally.
In summary, in the embodiments of the present invention, after the user terminal is registered in the network, if the neighboring network node finds that the network node registered by the user is faulty, the neighboring network node separates the user terminal from the faulty network node, or transfers the user terminal from the faulty network node to another network node, so that the communication context of the user terminal can be effectively transferred, and other network nodes automatically take over the user terminal, so that the user terminal can normally initiate a service flow, thereby maintaining continuity of a user service and further improving user experience.
It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present invention without departing from the spirit and scope of the invention. Thus, provided that such modifications and variations in the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the embodiments of the present invention are intended to include such modifications and variations as well.
Claims (22)
1. A method of handling a fault, comprising the steps of:
the first network node determines that the second network node fails;
the first network node carries out corresponding processing flow according to a wireless access system where a second network node is located, and the user terminal establishing the user plane context on the second network node is logged off from the second network node through the processing flow; wherein,
when the first network node determines that a second network node with a user terminal association context between the first network node and the node has a fault, the first network node sends a message for deleting the second network node information to the corresponding user terminal according to the user terminal association context; wherein the first network node and the second network node belong to wireless access systems of different wireless access technologies, respectively.
2. The method according to claim 1, wherein the first network node sends the message for deleting the second network node information directly to the user terminal or/and to a third network node belonging to the same radio access system as the second network node, which forwards the message for deleting the second network node information to the user terminal.
3. The method according to any of claims 1 and 2, wherein if the ue is in the same radio access system as the first network node, the ue deletes the information of the second network node and updates its communication context, and receives downlink data when it is found that there is the downlink data;
if the user terminal and the second network node are in the same wireless access system at present, the user terminal deletes the information of the second network node, re-registers to a third network node which belongs to the same wireless access system with the second network node, updates the communication context of the user terminal, and receives downlink data if the user terminal finds the downlink data.
4. A method of handling a fault, comprising the steps of:
the first network node determines that the second network node fails;
the first network node carries out corresponding processing flow according to a wireless access system where a second network node is located, and the user terminal establishing the user plane context on the second network node is logged off from the second network node through the processing flow;
wherein, if the first network node and the second network node belong to wireless access systems of different wireless access technologies, the processing flow includes the steps of:
the first network node sends the related information of the user terminal to a third network node, wherein the first network node and the second network node have the associated context of the user terminal, and the third network node and the second network node belong to the same wireless access system;
and the third network node performs network registration according to the received related information of the user terminal, and the user terminal records the information of the third network node and deletes the information of the second network node.
5. The method according to claim 4, wherein the first network node sends a message for instructing the ue to re-register to the third network node, where the message carries information of the ue itself, the third network node obtains the communication context of the ue according to the information of the ue itself and performs network registration, and the third network node forwards the message for instructing the ue to re-register to the ue.
6. The method of claim 5, wherein the first network node further sends a message directly to the user terminal instructing the user terminal to re-register.
7. The method of claim 4, comprising the steps of: the first network node sends a message for indicating the transfer of the user terminal to the third network node, wherein the message carries the information of the user terminal, and the third network node acquires the communication context of the user terminal according to the information of the user terminal and performs network registration.
8. The method of claim 7, wherein the third network node returns a response message to the first network node after network registration with a home subscriber server and sends a temporary subscriber identity to the user terminal.
9. The method of claim 4, wherein the first network node sends the communication context of the user terminal to the third network node, and the third network node performs network registration according to the communication context of the user terminal.
10. The method of claim 9, wherein the third network node sends its own signature to the corresponding access node, which establishes association information between the signature of the third network node and the signature of the second network node.
11. The method of claim 10, wherein if the access node fails to establish the association information, the access node notifies the third network node that the user terminal is re-registered with the corresponding other network node.
12. The method according to any of claims 4-11, wherein during the handover of the user terminal, the user plane anchor point and the home subscriber server record information of the third network node and delete the association information of the user terminal with the second network node.
13. The method according to claim 12, wherein when the third network node performs network registration, the third network node and the first network node establish an association context of the user terminal, and the home subscriber server locally deletes association information of the second network node and the user terminal, and records related information of the third network node.
14. The method of claim 13, wherein the ue updates its user plane context after transferring to the third network node, and receives downlink data when the ue finds the downlink data.
15. A method of handling a fault, comprising the steps of:
the first network node determines that the second network node fails;
the first network node carries out corresponding processing flow according to a wireless access system where a second network node is located, and the user terminal establishing the user plane context on the second network node is logged off from the second network node through the processing flow; wherein,
if the first network node and the second network node belong to the same wireless access system, the processing flow comprises the following steps:
when receiving downlink data, the user plane anchor point sends a paging request message to the first network node, wherein the paging request message carries relevant information of the user terminal;
the first network node acquires the information of the user terminal from the user terminal according to the relevant information of the user terminal and carries out network registration;
and after the first network node finishes the registration, the user terminal is instructed to delete the information of the second network node locally, and the information of the first network node is recorded.
16. The method of claim 15, wherein an access node forwards a service request message to the first network node when receiving the service request message sent by a user terminal, where the service request message carries relevant information of the user terminal, and the first network node obtains information of the user terminal from the user terminal according to the relevant information of the user terminal and performs network registration.
17. The method according to claim 15 or 16, wherein the updating of the communication context of the user terminal is performed between the first network node, the user terminal and a user plane anchor after the first network node has completed registration.
18. The method of claim 17, wherein during the handover of the user terminal, a user plane anchor and a home subscriber server record information of the first network node and delete association information of the user terminal with the second network node.
19. The method of claim 18, wherein the first network node sends a temporary subscriber identity to the user terminal during the handover of the user terminal.
20. A communication system, comprising:
the user terminal is used for establishing connection with the corresponding communication device so as to complete data communication;
the communication device comprises a plurality of communication devices and a control module, wherein when a first communication device determines that a second communication device has a fault, the first communication device carries out corresponding processing flow according to a wireless access system where the second communication device is located, and the user terminal establishing a user plane context on the second communication device is logged off from the second communication device through the processing flow;
when the first communication device determines that a second communication device with a user terminal association context between the first communication device and the second communication device has a fault, the first communication device sends a message for deleting information of the second communication device to a corresponding user terminal according to the association context of the user terminal; the first communication device and the second communication device belong to wireless access systems of different wireless access technologies respectively.
21. A communication system, comprising:
the user terminal is used for establishing connection with the corresponding communication device so as to complete data communication;
the communication device comprises a plurality of communication devices and a control module, wherein when a first communication device determines that a second communication device has a fault, the first communication device carries out corresponding processing flow according to a wireless access system where the second communication device is located, and the user terminal establishing a user plane context on the second communication device is logged off from the second communication device through the processing flow;
if the first communication device and the second communication device belong to wireless access systems of different wireless access technologies respectively, the first communication device sends related information of a user terminal to a third communication device, wherein the first communication device and the second communication device have an associated context of the user terminal, and the third communication device and the second communication device belong to the same wireless access system; and the third communication device performs network registration according to the received related information of the user terminal, and the user terminal records the information of the third communication device and deletes the information of the second communication device.
22. A communication system, comprising:
the user terminal is used for establishing connection with the corresponding communication device so as to complete data communication;
the communication device comprises a plurality of communication devices and a control module, wherein when a first communication device determines that a second communication device has a fault, the first communication device carries out corresponding processing flow according to a wireless access system where the second communication device is located, and the user terminal establishing a user plane context on the second communication device is logged off from the second communication device through the processing flow;
if the first communication device and the second communication device belong to the same wireless access system, the user plane anchor point sends a paging request message to the first communication device when receiving downlink data, wherein the paging request message carries relevant information of the user terminal; the first communication device acquires the information of the user terminal from the user terminal according to the relevant information of the user terminal and carries out network registration; and after the first communication device finishes the registration, the first communication device instructs the user terminal to delete the information of the second communication device locally, and records the information of the first communication device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100792477A CN101247255B (en) | 2007-02-13 | 2007-02-13 | Method and system for processing fault |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100792477A CN101247255B (en) | 2007-02-13 | 2007-02-13 | Method and system for processing fault |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101247255A CN101247255A (en) | 2008-08-20 |
| CN101247255B true CN101247255B (en) | 2010-09-15 |
Family
ID=39947484
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007100792477A Expired - Fee Related CN101247255B (en) | 2007-02-13 | 2007-02-13 | Method and system for processing fault |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101247255B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103238345A (en) * | 2012-10-31 | 2013-08-07 | 华为技术有限公司 | Communication method, device and system all based on mobile management entity pool (MME Pool) |
| CN104284451B (en) * | 2014-09-22 | 2018-03-27 | 大唐移动通信设备有限公司 | The method for releasing and equipment of a kind of user resources |
| US9992240B2 (en) * | 2015-02-13 | 2018-06-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Preserving S1-AP UE contexts on SCTP failover |
| CN105933884B (en) * | 2016-06-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Network registering method, device and the mobile terminal of mobile terminal |
| CN114339910A (en) | 2017-07-31 | 2022-04-12 | 华为技术有限公司 | Communication method, device and system |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1561648A (en) * | 2001-10-05 | 2005-01-05 | 艾利森电话股份有限公司 | Optimization of handover procedures in GPRS |
-
2007
- 2007-02-13 CN CN2007100792477A patent/CN101247255B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1561648A (en) * | 2001-10-05 | 2005-01-05 | 艾利森电话股份有限公司 | Optimization of handover procedures in GPRS |
Non-Patent Citations (2)
| Title |
|---|
| 3GPP System Architecture Evolution:Report onTechnicalOptions and Conclusions (Release 7).3GPP TR 23.882V1.6.1.2006,V1.6.1第75-78页. * |
| CN 1561648 A,全文. |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101247255A (en) | 2008-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11979938B2 (en) | Communication method and apparatus | |
| US10021728B2 (en) | Mobile terminated call improvements | |
| US8428625B2 (en) | Paging heuristics in packet based networks | |
| CN101610504B (en) | Method and device for accessing and obtaining user equipment context and user equipment identification | |
| CN102098655B (en) | Method and system for controlling activation of ISR (Idle mode Signaling Reduction) and UE (user equipment) | |
| US8606264B2 (en) | Method and device for processing information given idle-mode signaling reduction | |
| US8582503B2 (en) | Method for indicating the bearer management of a serving gateway | |
| US20100120427A1 (en) | Method and system for dual registration processing | |
| US20040266438A1 (en) | Methods involving a core network node that is handling a mobile subscriber and initiates a request to a second core network node to handle said mobile subscriber | |
| CN101247255B (en) | Method and system for processing fault | |
| US20110300861A1 (en) | Mobility management entity information deleting method and device | |
| CN101505474B (en) | Network side processing method in subscriber handover process, network element equipment and network system | |
| CN102761855B (en) | Access, obtain customer equipment context and the method and apparatus of customer equipment identification | |
| CN102378208A (en) | Processing method for VLR fault and system thereof | |
| CN102905369B (en) | User equipment calling method and system when mobile management unit fails or restarts | |
| CN104519538B (en) | User equipment, request message method of reseptance, device and its system | |
| CN102595388B (en) | The method and apparatus of processing user equipment context | |
| CN104380771B (en) | A kind of information processing method of MSC pool, apparatus and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100915 Termination date: 20140213 |