Method for recovering business after initial context is unsuccessfully built, terminal and system

Abstract

The embodiment of the invention provides a method for recovering business after initial context is unsuccessfully built, a terminal and a system, which comprise steps: the terminal launches network attached storage (NAS) information, a mobile managenment entity indicates an evolutionary base station to built initial context, the evolutionary base station detects that the initial context is unsuccessfully built, a network side notices a terminal context to release indication, and a terminal processes the context to release indication, and launches an attach (ATTACH) request. The method for recovering business after initial context is unsuccessfully built, the terminal and the system notices user experience (UE) context information on mobile managenment entity (MME) sides and enode B sides to be deleted through the indication information which is added on the terminal, the terminal further launches an ATTACH process at once, does not have to launch radio resource control (RRC) reestablishment or Service Request or tracking area update (TAU) process and the like to avoid being refused by network, thereby saving a signalling resource, rapidly recovering business, and optimizing user experience.

Description

technical field [0001] 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 [0002] With the development of wireless communication technology, people's demand for data services is increasing day by day. The 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, the user equipment (UserEquipment, UE) establishes a default enhanced packet service bearer context (EPSBEARERCONTEXT) through the Electronic Support Measures (ESM) process. In addition to the explicit deactivation or network implicit deactivation of the bearer context, When the S1 connection and the RadioResourceControl (RRC) connection are released, the user experience (UserExperience, UE) side and the mobile management entity (MobileManagenmentE...

AI Technical Summary

Problems solved by technology

[0006] (2) If the radio access control primitive on the network side during the ServiceRequest process causes all radio bearers to fail to be established, the UE does not know that the context on the MME side has been deactivated, and only receives the RRC connection release message from the eNodeB whose reason is 'other' After the current ServiceRequest process is completed, if the subsequent user initiates a ServiceRequest to request service recovery again, it will be rejected by the network with the reason "Implicitly detached" because the context cannot be found on the MME side.

[0007] All of the above will increase unnecessary signaling interaction process, waste signaling resources, and prolong service recovery time

Images