CN105517022B - Service restoration method, terminal and system after a kind of failure of establishing initial context - Google Patents

Abstract

Embodiments of the present invention provide a service recovery method, terminal and system after the initial context establishment fails, including: the terminal initiates a NAS message; the mobility management entity instructs the evolved base station to establish the initial context; the evolved base station detects that the initial context establishment fails; the network side Informing the terminal of the context release indication; and the terminal processes the context release indication and initiates an ATTACH request. After the initial context establishment fails, the service recovery method, the terminal and the system add an indication message to the terminal when the initial context establishment fails to notify the UE context information on the MME side and the eNodeB side that the UE context information is deleted, and the terminal then immediately initiates the ATTACH process without having to initiate Processes such as RRC reconstruction or Service Request or TAU are prevented from being rejected by the network, thereby saving signaling resources, quickly restoring services, and optimizing customer experience.

Description

A service recovery method, terminal and system after initial context establishment failure

technical field

The present invention relates to the field of wireless communication, in particular to a service recovery method, terminal and system after an initial context establishment fails.

Background technique

With the development of wireless communication technology, people's demand for data services is increasing day by day. Long Term Resolved (LTE) technology has been vigorously developed due to its characteristics of permanent online, service data rate, and large system capacity. In the prior art, a user equipment (User Equipment, UE) establishes a default enhanced packet service bearer context (EPS BEARERCONTEXT) through an Electronic Support Measures (ESM) process, except for explicit deactivation or implicit network deactivation. In addition to activation, the user experience (User Experience, UE) side and the mobile management entity (Mobile Management Entity, MME) side context will not be released when the S1 connection and the radio resource control module (Radio Resource Control, RRC) connection are released. After release, the user enters ECM-IDLE mode. If the user needs to transmit buffered uplink data or signaling or the network has buffered downlink data to send, it may switch to ECM-CONNECTED mode through the Service Request process or TAU process, and in the Service During the Request process or after the TAU process ends, S1 and the air interface bearer are established through the initial context establishment process, so as to further perform data services.

According to the agreement, if during the initial context establishment process, if the E-UTRAN radio access control or terminal reconfiguration fails or the terminal reconfiguration completion message is not successfully sent to the evolved base station (eNodeB), etc., the initial context establishment process will eventually result Failed, the behavior agreement between eNodeB and MME is not clear, it is acceptable for eNodeB and MME to perform their own implicit release or UE Context Release initiated by MME, as long as the resource release on the eNodeB side is guaranteed.

There are at least the following problems in the prior art:

(1) If the terminal reconfiguration completion message is not sent successfully, the terminal retransmits the message continuously. After reaching the maximum number of retransmissions, it initiates RRC connection re-establishment. Because the UE context on the eNodeB side has been deleted, the re-establishment cannot succeed. After the reconstruction is rejected by the network and leaves the RRC_CONNECTED state, and the underlying RRC release primitive indicating 'RRC connection failure', the terminal continues to initiate the TAU process to restore the NAS signaling connection, and the MME side context has been released, so the TAU Request will also be Network rejects with reason 'Implicitly detached'.

(2) If the radio access control primitive on the network side fails to establish all radio bearers during the Service Request process, the UE does not know that the context on the MME side has been deactivated, and only receives the RRC connection release from the eNodeB for the reason 'other' Message ends the Service Request process. If the subsequent user re-initiates the Service Request to request service recovery, it will be rejected by the network with the reason of "Implicitly detached" because the MME side cannot find the context.

All of the above will increase unnecessary signaling interaction processes, waste signaling resources, and prolong service recovery time.

Contents of the invention

The purpose of the present invention is to provide a service recovery method, terminal and system after initial context establishment failure, which can save signaling resources, quickly restore services, and optimize customer experience.

Specifically, the embodiment of the present invention provides a service recovery method after the initial context establishment fails, including:

The terminal initiates a NAS message;

The mobility management entity instructs the evolved base station to establish an initial context;

The evolved base station detects that the initial context establishment fails;

The network side notifies the terminal of the context release indication; and

The terminal processes the context release indication and initiates an ATTACH request.

Preferably, the terminal processes the context release indication and initiates an ATTACH request, specifically including:

After receiving the RRC link release message from the network side, the RRC layer of the terminal judges the reason for the release;

If the above-mentioned release reason indicates that the network context is released, then the RRC layer of the terminal judges whether there is currently an RLC retransmission and whether to initiate an RRC re-establishment process, and if so, stops the process and releases resources to enter the IDLE state;

After the release of resources, the RRC layer instructs the NAS layer to release the radio link, carries a special cause value, and instructs the network side to release the context;

After the NAS layer receives the above wireless link release message, it judges the cause value, if it is a context release instruction, it performs local de-registration, and initiates an ATTACH request after the local de-registration is completed, requesting the network to reattach.

Preferably, the NAS message is a TAU message or a Service Request message.

Preferably, the indicated message is a parameter in an existing message, a newly added parameter or some fields in an existing parameter.

The embodiment of the present invention also provides a service recovery terminal after the initial context establishment fails, including:

The NAS module is used for the terminal to initiate a NAS message;

The RRC module is used for the mobility management entity to instruct the evolved base station to establish an initial context;

The initial context failure detection module is used for the evolved base station to detect the failure to establish the initial context;

The initial context release indication module is used for the network side to notify the terminal of the context release indication; and

The service failure recovery module is used for the terminal to process the context release indication and initiate an ATTACH request.

Preferably, the business failure recovery module specifically includes:

The first judging module, after the RRC layer of the terminal receives the RRC link release message from the network side, judges the reason for the release;

The second judging module, if the above-mentioned release reason indicates that the network context is released, then the RRC layer of the terminal judges whether there is RLC retransmission and whether to initiate the RRC reconstruction process, if there is, stop the process, and release resources to enter the IDLE state;

Release module, the RRC layer instructs the NAS layer to release the radio link after releasing the resources, carries a special cause value, and instructs the network side to release the context;

The third judging module, after the NAS layer receives the above-mentioned wireless link release message, judges the cause value therein, if it is a context release instruction, then performs local de-registration, and initiates an ATTACH request after the local de-registration is completed, requesting the network to re-register attached.

Preferably, the NAS message is a TAU message or a Service Request message.

Preferably, the indicated message is a parameter in an existing message, a newly added parameter or some fields in an existing parameter.

On this basis, an embodiment of the present invention further provides a service recovery system after initial context establishment failure, specifically including the above-mentioned service recovery terminal after initial context establishment failure provided by the embodiment of the present invention.

Because the service recovery method, terminal and system provided by the embodiment of the present invention after the network initial context establishment fails, when the initial context establishment fails, an indication message is added to the terminal to notify the UE context information on the MME side and the eNodeB side to be deleted, The terminal then immediately initiates the ATTACH process without initiating RRC re-establishment or Service Request or TAU processes to avoid being rejected by the network, thereby saving signaling resources, quickly restoring services, and optimizing customer experience.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the following preferred embodiments are specifically cited below, and are described in detail as follows in conjunction with the accompanying drawings.

Description of drawings

Fig. 1 is a schematic flow chart of a method for recovering a service that fails to establish an initial context according to the first embodiment of the present invention.

FIG. 2 is a schematic flow chart of service restoration in step S105 shown in FIG. 1 .

Fig. 3 is a schematic flow chart of a method for recovering a service that fails to establish an initial context according to a second embodiment of the present invention.

Fig. 4 is a schematic structural diagram of a terminal for service recovery after an initial context establishment failure provided by a third embodiment of the present invention.

FIG. 5 is a schematic structural diagram of the service failure recovery module shown in FIG. 4 .

Detailed ways

In order to further explain the technical means and effects adopted by the present invention to achieve the intended purpose of the invention, the following, in conjunction with the accompanying drawings and preferred embodiments, will describe a method, terminal, system and service recovery method, terminal and system proposed according to the present invention after failure to establish an initial context. Its specific implementation, methods, steps, structures, features and effects are described in detail below.

The foregoing and other technical contents, features and effects of the present invention will be clearly presented in the following detailed description of preferred embodiments with reference to the drawings. Through the description of specific implementation methods, the technical means and effects of the present invention to achieve the intended purpose can be understood more deeply and specifically, but the attached drawings are only for reference and description, and are not used to explain the present invention limit.

Please refer to FIG. 1 . FIG. 1 is a schematic flowchart of a method for recovering a service that fails to establish an initial context according to the first embodiment of the present invention. As shown in Figure 1, the initial context establishment failure service recovery method specifically includes the following steps:

Step S101: the terminal initiates a NAS message.

The terminal in ECM-IDLE mode initiates a NAS message to trigger the initial context establishment process, and the NAS message is a TAU message or a Service Request message.

Among them, the TAU message triggering scenarios include two types: the active flag bit is set in the TAU request, or the active flag bit is not set in the TAU request but the network has downlink data cache.

Step S102: the MME instructs the eNodeB to establish an initial context.

After receiving the NAS message, the MME triggers the initial context establishment process and sends an initial context establishment request to the eNodeB.

The initial context establishment request triggered by the TAU process is after the MME sends the TAU Accept message.

Step S103: the eNodeB detects that the initial context establishment fails;

After receiving the initial context establishment request message from the MME, the eNodeB performs related wireless access admission and establishment of user plane resources. If the eNodeB detects that the initial context establishment process fails, it notifies the MME.

Step S104: the network side notifies the terminal of the context release instruction.

The eNodeB side and the MME side perform subsequent processing after the initial context establishment fails, and finally instruct the terminal network side to release the context. The indication message is a parameter in an existing message, a newly added parameter, or some fields in an existing parameter.

Step S105: the terminal processes the context release indication and initiates an ATTACH request.

After the terminal receives the context release indication message from the network side, it terminates the existing process, including the existing Service Request process of the NAS module and the related processes of the RRC module such as reconstruction and retransmission. Activate the context on the UE side and enter the EMM-DEREGISTERED state. Finally, the terminal initiates an ATTACH request to reattach.

For the network-side context release indication processing in the above method, there are multiple implementation schemes: the eNodeB suspends the release of the link, and the MME instructs the terminal through the existing NAS message; the eNodeB side adds a new IE or release reason IE to the RRC release message A new field is extended to indicate the terminal.

Please refer to FIG. 2 . FIG. 2 is a schematic flow chart of the service restoration in step S105 shown in FIG. 1 . As shown in Figure 2, the specific steps of the step S105 service recovery include:

Step S1051: After receiving the RRC link release message from the network side, the RRC layer of the terminal judges the reason for the release;

Step S1052: If the above-mentioned release reason indicates that the network context is released, the RRC layer of the terminal judges whether there is currently an RLC retransmission and whether to initiate an RRC re-establishment process, and if so, stops the process and releases resources to enter the IDLE state;

Step S1053: After the release of resources, the RRC layer instructs the NAS layer to release the radio link, carries a special cause value, and instructs the network side to release the context;

Step S1054: After receiving the wireless link release message, the NAS layer judges the cause value, if it is a context release instruction, performs local de-registration, and initiates an ATTACH request after the local de-registration is completed, requesting network re-attachment.

The embodiment of the present invention provides a service recovery method after the initial context establishment fails, which mainly includes: the terminal receives a Service Request message or a TAU request message in the ECM-IDLE state and the activation flag is set or a TAU request message and the activation flag is not set bit but the network has downlink data to send, the network side detects that the initial context establishment fails, and needs to instruct the terminal network side to deactivate the context, the terminal RRC layer does not retransmit RLC data and does not initiate the RRC reconstruction process, and the NAS layer terminates the current process And directly initiate the ATTACH request.

Please refer to FIG. 3 . FIG. 3 is a schematic flowchart of a method for recovering a service that fails to establish an initial context according to a second embodiment of the present invention. As shown in Figure 3, the network side context release indication method specifically includes:

Steps S201 , S202 , and S203 are similar to step S101 in the above-mentioned first embodiment, and steps S210 and S211 are similar to steps S102 and S103 in the above-mentioned first embodiment, so details are not repeated here.

Step S212: the eNodeB instructs the MME to fail to establish the initial context.

Step S213: optional step, applicable to the scenario where the MME initiates an explicit S1 connection release, then send a UE context release instruction message to the eNodeB, and carry a suitable reason in the message, which needs to be indicated to the terminal in the RRC release message, similar to Handle the cause of "Load Balancing TAU Required".

Step S214: If the release indication message from the MME is received and the reason is a specific release reason, or the instruction from the MME is not received, the eNodeB releases the wireless signaling connection, and carries a specific context release indication cause in the RRC release message.

Step S215: The terminal processes the context release indication on the network side, including terminating the existing process, entering the idle state and de-registering state.

Step S216: the terminal initiates an ATTACH request to request the network to attach.

Step S217: attach successfully.

Please refer to FIG. 4 . FIG. 4 is a schematic structural diagram of a service recovery terminal that fails to establish an initial context according to a third embodiment of the present invention. The initial context establishment failure service recovery terminal 410 includes:

The NAS module 411 is used for the terminal to initiate a NAS message;

Wherein, the NAS module 411 judges the cause of the release after receiving the wireless link release instruction from the RRC module, and if the network context is deactivated, performs local de-registration and re-initiates the ATTCH process.

The RRC module 412 is used for the mobility management entity to instruct the evolved base station to establish an initial context;

Wherein, the RRC module 412 receives the RRC release message sent by the eNodeB, and judges the reason for the release. If the network side context is released, the local release resource terminates the process of retransmission and reconstruction, and instructs the NAS module to release the wireless link.

The initial context failure detection module 421 is used for the evolved base station to detect the failure to establish the initial context;

Wherein, the initial context failure detection module 421 detects the final initial context establishment failure caused by various failures in the initial context establishment process of the eNodeB, and sends an initial context establishment failure message to the MEM.

The initial context release indication module 422 is used for the network side to notify the terminal of the context release indication;

Wherein, the context release instruction module 422 detects that the initial context failure detection module 421 fails to establish the initial context, releases the user resources and releases the RRC connection, and if the MME explicitly initiates the UE context release, then judges whether the MME release command carries a specific context Release reason, if carried, set the RRC release reason as the context release reason, if it is an implicit release process, the eNodeB directly carries the release reason in the RRC release message as the context release.

The service failure recovery module 431 is used for the terminal to process the context release indication and initiate an ATTACH request.

Among them, the service failure recovery module 431 is used to carry a specific cause value in the S1UE Context Release Command message in the S1 connection release indication initiated by the MME to indicate the context release, and agree that the eNodeB needs to include the cause in the RRC release message carried to the terminal.

For different implementations of context release instructions on the network side, terminals also have different implementations:

If the network indicates the context release through an RRC message such as an RRC release message, the RRC module does not need to continue RLC retransmission after receiving the network side context deactivation indication message. Release the message to the NAS, and indicate that the reason for the release is "context deactivation". After receiving the RRC layer signaling connection release message, the NAS module determines whether the cause is the context deactivation indication. If it is the indication, terminate the current process, and then initiate an ATTACH request ;

If the network indicates context release through a NAS message such as a Detach Req or Service reject message, the NAS module first performs a de-registration process after receiving the network-side context deactivation indication message, and then initiates an ATTACH request after the de-registration process is completed.

Please refer to FIG. 5 , which is a schematic structural diagram of the service failure recovery module shown in FIG. 4 . As shown in Figure 5, the business failure recovery module 431 specifically includes:

The first judging module 4311, after the unlimited resource control module layer of the terminal receives the link release message of the unlimited resource control module on the network side, judges the reason for the release;

The second judging module 4312, if the above-mentioned release reason indicates that the network context is released, then the terminal's unlimited resource control module layer judges whether there is currently RLC retransmission and whether to initiate the unlimited resource control module reconstruction process, and if so, stop the process and release The resource enters the IDLE state;

The release module 4313, after the unlimited resource control module layer releases resources, instructs the NAS layer to release the wireless link, carries a special cause value, and instructs the network side to release the context;

The third judging module 4314, after the NAS layer receives the wireless link release message, judges the cause value therein, if it is a context release instruction, then performs local de-registration, and initiates an ATTACH request after the local de-registration is completed, requesting the network Reattach.

The embodiment of the present invention provides a service recovery terminal after the initial context establishment fails, mainly including: the terminal receives a Service Request message or a TAU request message in the ECM-IDLE state and the activation flag is set or a TAU request message and the activation flag is not set bit but the network has downlink data to send, the network side detects that the initial context establishment fails, and needs to instruct the terminal network side to deactivate the context, the terminal RRC layer does not retransmit RLC data and does not initiate the RRC reconstruction process, and the NAS layer terminates the current process And directly initiate the ATTACH request.

On this basis, an embodiment of the present invention further provides a service recovery system after initial context establishment failure. The service recovery system after initial context establishment failure includes the above-mentioned service recovery terminal after initial context establishment failure.

According to the disclosure and teaching of the above-mentioned specification, those skilled in the art to which the present invention belongs can also make changes and modifications to the above-mentioned embodiment. Therefore, the present invention is not limited to the specific embodiments disclosed and described above, and some modifications and changes to the present invention should also fall within the protection scope of the claims of the present invention. In addition, although some specific terms are used in this specification, these terms are only for convenience of description and do not constitute any limitation to the present invention.

Claims (7)

1. A business recovery method after initial context establishment failure, is characterized in that, comprises: The terminal initiates a NAS message; The mobility management entity instructs the evolved base station to establish an initial context; The evolved base station detects that the initial context establishment fails; The network side notifies the terminal of the context release indication; and The terminal processes the context release indication and initiates an ATTACH request; Wherein, the terminal processes the context release indication and initiates an ATTACH request, specifically including: After receiving the link release message from the radio resource control module on the network side, the radio resource control module layer of the terminal judges the cause of the release; If the above-mentioned release reason indicates that the network context is released, the radio resource control module layer of the terminal judges whether there is RLC retransmission and whether to initiate a radio resource control module reconstruction process, and if so, stops the process and releases resources to enter the IDLE state; After the release of resources, the radio resource control module layer instructs the NAS layer to release the radio link, carries a special cause value, and instructs the network side to release the context; After the NAS layer receives the above wireless link release message, it judges the cause value, if it is a context release instruction, it performs local de-registration, and initiates an ATTACH request after the local de-registration is completed, requesting the network to reattach. 2. The service recovery method after initial context establishment failure according to claim 1, characterized in that: the NAS message is a TAU message or a Service Request message. 3. The service recovery method after initial context establishment failure according to claim 1, characterized in that: the indicated message is a parameter in an existing message, a newly added parameter or some fields in an existing parameter. 4. A service recovery terminal after initial context establishment failure, characterized in that: comprising: The NAS module is used for the terminal to initiate a NAS message; The radio resource control module is used for the mobility management entity to instruct the evolved base station to establish an initial context; The initial context failure detection module is used for the evolved base station to detect the failure to establish the initial context; The initial context release indication module is used for the network side to notify the terminal of the context release indication; and The service failure recovery module is used for the terminal to process the context release indication and initiate an ATTACH request; wherein, the service failure recovery module specifically includes: The first judging module, after the radio resource control module layer of the terminal receives the link release message of the radio resource control module on the network side, judges the reason for the release; The second judging module, if the above-mentioned release reason indicates that the network context is released, then the radio resource control module layer of the terminal judges whether there is currently RLC retransmission and whether to initiate a radio resource control module reconstruction process, and if so, stop the process and release resources Enter the IDLE state; In the release module, the radio resource control module layer instructs the NAS layer to release the radio link after releasing the resource, carries a special cause value, and instructs the network side to release the context; The third judging module, after the NAS layer receives the above wireless link release message, judges the cause value therein, if it is a context release instruction, then performs local de-registration, and initiates an ATTACH request after the local de-registration is completed, requesting the network to re-register attached. 5. The service recovery terminal after initial context establishment failure according to claim 4, wherein the NAS message is a TAU message or a Service Request message. 6. The service recovery terminal after initial context establishment failure according to claim 4, characterized in that: the indicated message is a parameter in an existing message, a newly added parameter, or some fields in an existing parameter . 7. A service recovery system after initial context establishment failure, characterized by comprising the service recovery terminal after initial context establishment failure according to any one of claims 4-6.