CN118945895A

CN118945895A - Connection recovery processing method, device and equipment

Info

Publication number: CN118945895A
Application number: CN202310535433.6A
Authority: CN
Inventors: 李媛; 张艳霞; 杨晓东
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Filing date: 2023-05-11
Publication date: 2024-11-12

Abstract

The application discloses a connection recovery processing method, a device and equipment, belonging to the technical field of communication, wherein the method provided by the embodiment of the application comprises the following steps: in the case that the timing synchronization state change and the first reason trigger the Radio Resource Control (RRC) connection recovery, the terminal executes a connection recovery strategy corresponding to the highest priority according to the priority sequence of the timing synchronization state change and the first reason; wherein the timing synchronization state change is used for indicating that the timing synchronization state of the access network changes.

Description

Connection recovery processing method, device and equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a connection recovery processing method, device and equipment.

Background

At present, the terminal can reconnect the network due to the timing synchronization state change of the access network, and the terminal can trigger the reconnection of the network by other reasons.

However, when the timing synchronization state of the access network changes and other reasons conflict, how to recover the terminal to connect with the network has become a technical problem to be solved.

Disclosure of Invention

The embodiment of the application provides a connection recovery processing method, a device and equipment, which can solve the problem of how to recover the connection with a network when the timing synchronization state of an access network changes and other reasons conflict.

In a first aspect, a connection recovery processing method is provided, and the method includes:

In the case that the timing synchronization state change and the first reason trigger the Radio Resource Control (RRC) connection recovery, the terminal executes a connection recovery strategy corresponding to the highest priority according to the priority sequence of the timing synchronization state change and the first reason;

wherein the timing synchronization state change is used for indicating that the timing synchronization state of the access network changes.

In a second aspect, there is provided a connection recovery processing device including:

A processing module, configured to execute a connection recovery policy corresponding to a highest priority according to a priority order of a first cause and a timing synchronization state change when the timing synchronization state change and the first cause trigger a radio resource control RRC connection recovery;

In a third aspect, there is provided a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the first aspect.

In a fourth aspect, a terminal is provided, including a processor and a communication interface, where the processor is configured to execute a connection recovery policy corresponding to a highest priority according to a priority order of a first cause and a timing synchronization state change when the timing synchronization state change and the first cause trigger a radio resource control RRC connection recovery;

In a fifth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor realizes the steps of the method according to the first aspect.

In a sixth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, the terminal being operable to perform the steps of the method as described in the first aspect.

In a seventh aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being configured to execute programs or instructions for implementing the method according to the first aspect.

In an eighth aspect, there is provided a computer program/program product stored in a storage medium, the program/program product being executed by at least one processor to carry out the steps of the method according to the first aspect.

In the embodiment of the application, after determining that the triggering reason of the RRC connection recovery includes the timing synchronization state change and the first reason, the terminal executes the connection recovery strategy corresponding to the highest priority according to the priority sequence of the timing synchronization state change and the first reason, thereby completing reconnection with the network.

Drawings

Fig. 1 is a block diagram of a wireless communication system;

FIG. 2 is a flow chart of a connection recovery processing method according to an embodiment of the present application;

Fig. 3 is a schematic block diagram of a connection recovery processing device according to an embodiment of the present application;

Fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms "first," "second," and the like, herein, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, the "or" in the present application means at least one of the connected objects. For example, "a or B" encompasses three schemes, scheme one: including a and excluding B; scheme II: including B and excluding a; scheme III: both a and B. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The term "indication" according to the application may be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). The direct indication may be understood that the sender explicitly informs the specific information of the receiver, the operation to be executed, the request result, and other contents in the sent indication; the indirect indication may be understood as that the receiving side determines corresponding information according to the indication sent by the sending side, or determines and determines an operation or a request result to be executed according to a determination result.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), or other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for exemplary purposes and NR terminology is used in much of the following description, but the techniques may also be applied to systems other than NR systems, such as the 6 th Generation (6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a Mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer), a notebook (Personal DIGITAL ASSISTANT, PDA), a palm Computer, a netbook, an Ultra-Mobile Personal Computer (Ultra-Mobile Personal Computer, UMPC), a Mobile internet device (Mobile INTERNET DEVICE, MID), a Personal Digital Assistant (PDA), Augmented Reality (Augmented Reality, AR), virtual Reality (VR) devices, robots, wearable devices (Wearable Device), aircraft (FLIGHT VEHICLE), in-vehicle devices (Vehicle User Equipment, VUE), on-board equipment, pedestrian terminals (PEDESTRIAN USER EQUIPMENT, PUE), smart home (home appliances having wireless communication function, such as refrigerator, television, washing machine or furniture, etc.), game machine, personal computer (Personal Computer, PC), teller machine or self-service machine, etc. The wearable device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. The in-vehicle apparatus may also be referred to as an in-vehicle terminal, an in-vehicle controller, an in-vehicle module, an in-vehicle component, an in-vehicle chip, an in-vehicle unit, or the like. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may include an access network device or core network device, where the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function, or a radio access network element. The Access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) Access Point (AP), or a wireless fidelity (WIRELESS FIDELITY, WIFI) node, etc. among them, the base station may be called a Node B (NB), an Evolved Node B (eNB), a next generation Node B (the next generation Node B, gNB), a New air interface Node B (New Radio Node B, NR Node B), an access point, a relay station (Relay Base Station, RBS), a serving base station (Serving Base Station, SBS), a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a Basic service set (Basic SERVICE SET, BSS), an Extended service set (Extended SERVICE SET, ESS), a Home Node B (HNB), a home evolved Node B (home evolved Node B), a transmission and reception point (Transmission Reception Point, TRP) or some other suitable terminology in the field, the base station is not limited to a specific technical vocabulary as long as the same technical effect is achieved, In the embodiment of the present application, only the base station in the NR system is described as an example, and the specific type of the base station is not limited.

For ease of understanding, some of the following descriptions are directed to embodiments of the present application:

The decision of the state transition of the radio resource control (Radio Resource Control, RRC) caused by the timing synchronization state change of the Access network by the terminal (also called AS terminal equipment) may be that the Non-Access Stratum (NAS) triggers the registration and service request procedure to Access the network, or that the NAS requests the Access Stratum (AS) to resume the connection with the network.

RRC INACTIVE state (rrc_inactive state):

If the network is supported to be reconnected due to the timing synchronization state change of the access network, and the network is requested to be reconnected by the configuration update command when the timing synchronization state change indication of the access layer is received, and the timing synchronization state change is indicated by the AS layer, the NAS layer of the rrc_inactive state terminal should request the AS layer to trigger the RRC connection recovery procedure so that the terminal enters the rrc_connected state.

RRC IDLE state (rrc_idle state):

If the network reconnection is supported due to the change of the timing synchronization state of the access network, the terminal sets a bit for supporting the network reconnection due to the change of the timing synchronization state in a 5G system mobility management (5GS Mobility Management,5GMM) capability cell of the registration request message, and after the 'request reconnection' in the timing synchronization cell of the access network receiving the registration acceptance message of the network side is indicated by the AS layer, the NAS layer of the RRC_IDLE state terminal triggers a service request flow, namely an RRC connection establishment flow, so that the terminal enters an RRC connection state (RRC_CONNECTED state).

The connection recovery processing method provided by the embodiment of the application is described in detail below through some embodiments and application scenarios thereof with reference to the accompanying drawings.

As shown in fig. 2, a connection recovery processing method according to an embodiment of the present application includes:

Step 201, in the case that the timing synchronization state change and the first cause trigger the radio resource control RRC connection recovery, the terminal executes the connection recovery policy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause;

Here, the timing synchronization state change and the first reason are configured with respective connection recovery policies for guiding the operation flow of RRC connection recovery by the terminal. Also in this embodiment, the timing synchronization status change and the priority order of the first cause are used to indicate the order in which their corresponding connection restoration policies are executed.

In this way, after determining that the trigger cause of RRC connection recovery includes the timing synchronization state change and the first cause, the terminal executes the connection recovery policy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause, thereby completing reconnection with the network.

AS an embodiment, the AS layer of the terminal performs a connection recovery policy corresponding to the highest priority.

In this embodiment, the connection recovery policy corresponding to the highest priority, i.e., the connection recovery policy corresponding to the timing synchronization state change or the first cause having the highest priority. For example, if the first cause is cause a and the priority of the timing synchronization state change is higher (higher) than the priority of cause a, then a connection recovery policy corresponding to the timing synchronization state change is executed; the first cause includes a cause a and a cause B, and the priority of the cause B is the highest priority among the priority of the timing synchronization status change, the cause a, and the cause B, and then the connection recovery policy corresponding to the cause B is executed.

As an embodiment, the timing synchronization state change and the priority order of the first cause may be predefined or configured by the protocol. Specifically, the protocol predefines or configures the timing synchronization status change and the priority of the first cause, and the priority order is indicated by the size of the priority; or the protocol predefines or configures the execution sequence of the connection recovery strategy corresponding to the timing synchronization state change and the first reason, wherein the execution sequence is the priority sequence.

Optionally, the first cause includes at least one of:

responding to Radio Access Network (RAN) paging;

a high layer indicates, wherein the high layer is a non-access NAS layer;

The RAN informs of the area update.

That is, RRC connection recovery may be triggered in response to a RAN page, may be triggered by a NAS layer indication, may be triggered by a RAN announcement region (RAN Notification Area, RNA) update.

Optionally, in this embodiment, the NAS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.

Optionally, in this embodiment, the timing synchronization status change and the priority order of the first cause include any one of the following:

The priority of the response RAN paging is greater than the priority of the high-level indication, the priority of the high-level indication is equal to the priority of the timing synchronization state change, and the priority of the high-level indication is greater than the priority of the RAN notification area update;

The priority of responding to the RAN paging is greater than the priority of the RAN notification area update, the priority of the RAN notification area update is greater than the priority of the high-level indication, and the priority of the high-level indication is equal to the priority of the timing synchronization state change;

The priority of the high-level instruction is equal to the priority of the timing synchronization state change, the priority of the high-level instruction is larger than the priority of the response RAN paging, and the priority of the response RAN paging is larger than the priority of the RAN notification area update.

That is, the RRC connection recovery is triggered for the NAS layer based on the timing synchronization state change, which belongs to a higher layer indication. In this way, based on the specific implementation of the first reason, determining the reason of the highest priority according to the priority order of the first reason, if the priority indicated by the higher layer is the highest priority, the priority of the timing synchronization state change is also the highest priority; if the priority of the higher layer instruction is not the highest priority, the priority of the timing synchronization state change is not the highest priority, and the reason of the highest priority is determined according to the priority order of the first reason.

the priority of the response RAN paging is greater than the priority of the timing synchronization state change, the priority of the timing synchronization state change is greater than the priority of the high-level indication, and the priority of the high-level indication is greater than the priority of the RAN notification area update;

The priority of responding to the RAN paging is larger than the priority of the high-layer indication, the priority of the high-layer indication is larger than the priority of the timing synchronization state change, and the priority of the timing synchronization state change is larger than the priority of the RAN notification area update.

That is, for the NAS layer to trigger RRC connection recovery based on the timing synchronization state change, the priority of the timing synchronization state change is not equal to the priority indicated by the higher layer. In this way, the highest priority is determined as a certain cause (a certain cause among the first causes) or a timing synchronization state change in accordance with the priority order based on the timing synchronization state change and the specific implementation of the first cause.

Optionally, the NAS layer of the terminal triggers, based on the timing synchronization state change, a connection recovery policy corresponding to RRC connection recovery, including:

the NAS layer provides an access category and an access identity based on the timing synchronization state change;

Using the access category access identity provided by the NAS layer to execute unified access control;

Wherein the access identities provided by the NAS layer include one or more access identities.

As an implementation, triggering RRC connection recovery based on the timing synchronization state change for the NAS layer, the connection recovery policy of which is similar to the connection recovery policy corresponding to the NAS layer indication, includes: the NAS layer provides an access class and one or more access identities, and performs unified access control (unified access control) using the access class and the access identities provided by the NAS layer; if the access attempt is disabled, the flow of connection recovery is stopped.

Optionally, in this embodiment, the AS layer of the terminal triggers RRC connection restoration based on the timing synchronization state change.

The priority of the timing synchronization state change is greater than the priority of the response RAN paging, the priority of the response RAN paging is greater than the priority of the high-level indication, and the priority of the high-level indication is greater than the priority of the RAN notification area update;

the priority of the response RAN paging is greater than the priority of the high-level indication, the priority of the high-level indication is greater than the priority of the timing synchronization state change, and the priority of the timing synchronization state change is greater than the priority of the RAN notification area update;

The priority of responding to the RAN paging is larger than the priority of the high-layer indication, the priority of the high-layer indication is larger than the priority of the RAN notification area update, and the priority of the RAN notification area update is larger than the priority of the timing synchronization state change.

That is, for the AS layer to trigger RRC connection recovery based on the timing synchronization state change, further based on the timing synchronization state change and the specific implementation of the first cause, the highest priority is determined to be a certain cause (a certain cause of the first causes) or the timing synchronization state change according to the priority order, and the terminal executes the connection recovery policy corresponding to the highest priority.

Optionally, the AS layer of the terminal triggers an RRC connection restoration policy corresponding to the RRC connection restoration based on the timing synchronization state change, including:

Selecting an access category and a connection restoration reason according to whether an ongoing emergency service exists;

And performing unified access control using the selected access category and the connection restoration reason.

That is, the AS layer triggers RRC connection restoration based on the timing synchronization state change, and the terminal executes a connection restoration policy corresponding to the timing synchronization state change, selects an access category and a connection restoration reason according to whether or not there is an ongoing emergency service, and then performs unified access control using the selected access category and connection restoration reason.

Optionally, the selecting an access category and a connection recovery reason according to whether an ongoing emergency service exists includes:

if an ongoing emergency service exists, selecting a first access category and setting a connection restoration reason as emergency;

If no ongoing emergency service exists, selecting a second access category, and setting a connection recovery reason as a protocol preset reason corresponding to the second access category; or selecting the second access category, and setting the connection restoration reason as the access network timing synchronization state change.

As one implementation, the protocol defines or configures a plurality of access categories and associated connection recovery reasons as shown in the following table:

accordingly, the first access category is an access category "2" defined or configured by the protocol, and the second access category is an access category "3" defined or configured by the protocol. Wherein for the second access class, the protocol defines or configures connection restoration bits for a protocol preset reason.

As an implementation, the second access class is an access class "8" defined or configured by the protocol, for which the protocol defines or configures connection recovery bits for a protocol preset reason. The access category "8" corresponds to RNAupdate, which is the AS layer behavior of the terminal.

Of course, the first access category and the second access category may also be other access categories defined or configured by a protocol, which are not listed here.

Optionally, in this embodiment, the connection recovery policy further includes:

if the access attempt is disabled, the flow of connection recovery is stopped.

Alternatively, in this embodiment, the timing synchronization state change and the priority order of the first cause may also be understood as the execution logic of the connection recovery policy.

Thus, for the NAS layer of the terminal to trigger RRC connection recovery based on the timing synchronization state change, the first execution logic of the connection recovery policy of the terminal includes any one of the following:

responding to RAN paging (paging) > NAS layer indication > RNA update (update);

responding RAN PAGING > RNAupdate > NAS layer indication;

NAS layer indicates > response RAN PAGING > RNA update;

in this case, the NAS layer indication may be an indication other than the NAS layer indication corresponding to the access network timing synchronization state change, or may be a special NAS layer indication (NAS layer indication corresponding to the access network timing synchronization state change), that is, the timing synchronization state change.

Or triggering a connection recovery strategy corresponding to RRC connection recovery by the NAS layer of the terminal based on the timing synchronization state change, wherein the first execution logic of the connection recovery strategy of the terminal comprises any one of the following steps:

Responding RAN PAGING > timing synchronization state change > NAS layer indication > RNA update;

responding RAN PAGING to the NAS layer indication > timing synchronization state change > RNAupdate to the NAS layer indication;

At this time, the NAS layer indication is an indication other than the NAS layer indication corresponding to the access network timing synchronization state change, and may be referred to as a NAS layer indication not corresponding to the access network timing synchronization state change, or other NAS layer indication.

In addition, for the AS layer of the terminal triggering RRC connection restoration based on the timing synchronization state change, the second execution logic of the connection restoration policy of the terminal includes:

Timing synchronization state change > response RAN PAGING > NAS layer indication > RNAupdate;

response RAN PAGING > NAS layer indicates > timing synchronization state change > RNAupdate;

responding RAN PAGING to the > NAS layer indication > RNA update > NAS layer indication;

at this point, triggering RRC connection restoration based on timing synchronization state change can be understood as a trigger cause existing at the access stratum similar to responses RAN PAGING and RNAupdate.

The application of the method according to the embodiment of the present application is described below in conjunction with a specific scenario:

Scene one, NAS layer triggers RRC connection recovery and AS layer triggers RRC connection recovery conflict based on timing synchronization state change:

The NAS layer of the terminal receives the timing synchronization state indication from the AS layer, decides an access category and an access identity used by RRC connection recovery corresponding to the timing synchronization state change, and delivers the access category and the access identity to the AS layer. In the case where other trigger causes exist at the same time, the RRC connection recovery operation of the terminal follows the connection recovery policy determined by the first execution logic.

Illustratively, the reason why the AS layer triggers RRC connection recovery is that in response RAN PAGING, the priority of the timing synchronization state change is not equal to the priority of the NAS layer indication (other NAS layer indication), and the first execution logic is in response RAN PAGING > timing synchronization state change > RNAupdate > NAS layer indication (other NAS indication), then the terminal executes the connection recovery policy corresponding to the timing synchronization state change: if the NAS layer provides an access category and one or more access identities, performing unified access control according to the access category and the access identities provided by the NAS layer; if the access attempt is disabled, the flow of connection recovery is stopped.

Scene two, NAS layer triggers RRC connection to resume and triggers RRC connection to resume conflict with other NAS layers based on timing synchronization state change:

The NAS layer of the terminal receives the timing synchronization state indication from the AS layer, decides an access category and an access identity used by RRC connection recovery corresponding to the timing synchronization state change, and delivers the access category and the access identity to the AS layer. In case that other NAS layers trigger RRC connection restoration at the same time, the RRC connection restoration operation of the terminal follows the connection restoration policy determined by the first execution logic.

Illustratively, the first execution logic is responsive RAN PAGING > timing synchronization state change > NAS layer indication (other NAS indication) > RNAupdate, then the terminal executes a connection recovery policy corresponding to the timing synchronization state change: if the NAS layer provides one access category and one or more access identities corresponding to the timing synchronization state change, performing unified access control according to the access category and the access identities provided by the NAS layer; if the access attempt is disabled, the flow of connection recovery is stopped.

Scene three, AS layer triggers RRC connection recovery based on timing synchronization state change and AS layer triggers RRC connection recovery conflict with other reasons:

the AS layer (e.g., RRC layer) of the terminal determines that the timing synchronization state of the access network changes, and determines an access class used for RRC connection recovery corresponding to the timing synchronization state change, i.e., the AS layer triggers RRC connection recovery based on the timing synchronization state change. In the case where other trigger causes exist at the same time, the RRC connection recovery operation of the terminal follows the connection recovery policy determined by the second logic.

Assuming that the reason why the AS layer for other reasons triggers RRC connection recovery is RNAupdate and the second logic is that the response RAN PAGING > NAS layer indicates > timing synchronization state change > RNAupdate, the terminal performs a connection recovery policy corresponding to the timing synchronization state change: if there is an ongoing emergency service, selecting "2" as a first access category, and setting a connection restoration cause (resumeCause) as emergency (emergency); if there is no ongoing emergency service, performing:

Selecting '3' as a second access category, and setting resumeCause as a protocol preset reason corresponding to '3';

Selecting 8 as a second access category, and setting resumeCause as a protocol preset reason corresponding to 8;

selecting '3' as a second access category, and setting resumeCause as access network timing synchronization state change;

An "8" is selected as the second access category and resumeCause is set to access network timing synchronization state change.

And executing unified access control according to the selected access category and the connection recovery reason.

Of course, if the access attempt is disabled, the relevant operation of connection restoration is stopped.

It should be noted that in this embodiment, the connection recovery policy corresponding to the response RAN PAGING includes: selecting a third access category, such as access category "0", and performing unified access control according to the third access category; if the access attempt is disabled, the associated operation of connection restoration is stopped.

The connection recovery policy corresponding to the high-level indication includes: 1. if the higher layer provides an access category (access category) and one or more access identities (ACCESS IDENTITY), performing unified access control according to the access category and the access identity provided by the upper layer; if the access attempt is disabled, the associated operation of connection restoration is stopped. 2. If the higher layer provides network slice access layer packet (Network Slice As Group, NSAG) information and one or more network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI), the highest NSAG priority is used for NSAG in the random access procedure among all NSAG provided in SIB1 and related to S-NSSAI that triggered the access attempt. 3. If connection recovery occurs after a redirect release using the multimedia priority service mpsPriorityIndication, resumeCause is set to access mps-PriorityAccess for the multimedia priority service. 4. Otherwise (connection recovery occurs before using mpsPriorityIndication redirect release), resumeCause is set according to the information received from the upper layer.

The connection recovery strategy corresponding to the RNA update includes: if there is an ongoing emergency service, selecting a first access category, such as access category "2", and setting resumeCause to emergency; if no ongoing emergency service exists, selecting a second access category, such as an access category "8", and setting resumeCause as a protocol preset reason corresponding to "8"; according to the selected access category and the connection recovery reason, executing unified access control; if the access attempt is disabled, the RNA Update variable (PENDINGRNA-Update) is set to true and the associated operation of connection recovery is stopped.

In summary, in the method of the embodiment of the present application, the terminal device is considered to trigger RRC connection recovery at the NAS/AS layer and trigger RRC connection recovery for other reasons, and the corresponding access control setting is performed on the RRC connection recovery procedure through the priority order, that is, the connection recovery policy corresponding to the highest priority is executed, so AS to implement a reasonable connection recovery procedure of the terminal when multiple connection recovery reasons collide.

According to the connection recovery processing method provided by the embodiment of the application, the execution main body can be the connection recovery processing device. In the embodiment of the present application, a connection recovery processing device executes a connection recovery processing method by using a connection recovery processing device as an example, and the connection recovery processing device provided in the embodiment of the present application is described.

As shown in fig. 3, a connection recovery processing device according to an embodiment of the present application includes:

A processing module 310, configured to execute a connection recovery policy corresponding to a highest priority according to a priority order of a first cause and a timing synchronization state change in a case where the timing synchronization state change and the first cause trigger a radio resource control RRC connection recovery;

Optionally, the first cause includes at least one of:

responding to Radio Access Network (RAN) paging;

a high layer indicates, wherein the high layer is a non-access NAS layer;

The RAN informs of the area update.

Optionally, the NAS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.

Optionally, the timing synchronization status change and the priority order of the first cause include any one of:

Optionally, the AS layer of the terminal triggers RRC connection restoration based on the timing synchronization state change.

Optionally, the connection recovery policy further includes:

if the access attempt is disabled, the flow of connection recovery is stopped.

In this way, after determining that the trigger cause of RRC connection recovery includes a timing synchronization state change and a first cause, the apparatus performs a connection recovery policy corresponding to a highest priority according to the priority order of the timing synchronization state change and the first cause, thereby completing reconnection with the network.

It should be noted that, the device is a device to which the connection recovery processing method is applied, and the implementation manner of the embodiment of the method is applicable to the device, so that the same technical effects can be achieved.

The connection recovery processing device in the embodiment of the application can be an electronic device, for example, an electronic device with an operating system, or can be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, the terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the present application are not limited in detail.

The connection recovery processing device provided by the embodiment of the present application can implement each process implemented by the method embodiment of fig. 2, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.

As shown in fig. 4, the embodiment of the present application further provides a communication device 400, including a processor 401 and a memory 402, where the memory 402 stores a program or an instruction that can be executed on the processor 401, for example, when the communication device 400 is a terminal, the program or the instruction is executed by the processor 401 to implement the steps of the above-mentioned connection recovery processing method embodiment, and the same technical effects can be achieved.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the steps in the embodiment of the method shown in fig. 2. The terminal embodiment corresponds to the terminal-side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved. Specifically, fig. 5 is a schematic hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 500 includes, but is not limited to: at least some of the components of the radio frequency unit 501, the network module 502, the audio output unit 503, the input unit 504, the sensor 505, the display unit 506, the user input unit 507, the interface unit 508, the memory 509, and the processor 510.

Those skilled in the art will appreciate that the terminal 500 may further include a power source (e.g., a battery) for powering the various components, and the power source may be logically coupled to the processor 510 via a power management system so as to perform functions such as managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 5 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine certain components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 504 may include a graphics processing unit (Graphics Processing Unit, GPU) 5041 and a microphone 5042, with the graphics processor 5041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 507 includes at least one of a touch panel 5071 and other input devices 5072. Touch panel 5071, also referred to as a touch screen. Touch panel 5071 may include two parts, a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving downlink data from a network side device, the radio frequency unit 501 may transmit the downlink data to the processor 510 for processing; in addition, the radio frequency unit 501 may send uplink data to the network side device. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 509 may be used to store software programs or instructions as well as various data. The memory 509 may mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 509 may include volatile memory or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDRSDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCH LINK DRAM, SLDRAM), and Direct random access memory (DRRAM). Memory 509 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

Processor 510 may include one or more processing units; optionally, the processor 510 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, etc., and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 510.

Wherein, the processor 510 is configured to execute, in a case where a timing synchronization state change and a first cause trigger a radio resource control RRC connection recovery, a connection recovery policy corresponding to a highest priority according to a priority order of the timing synchronization state change and the first cause;

Optionally, the first cause includes at least one of:

responding to Radio Access Network (RAN) paging;

a high layer indicates, wherein the high layer is a non-access NAS layer;

The RAN informs of the area update.

Optionally, the connection recovery policy further includes:

if the access attempt is disabled, the flow of connection recovery is stopped.

In this way, after determining that the trigger cause of RRC connection recovery includes a timing synchronization state change and a first cause, the AS layer performs a connection recovery policy corresponding to a highest priority according to the priority order of the timing synchronization state change and the first cause, thereby completing reconnection with the network.

After determining that the triggering reason of the RRC connection recovery includes the timing synchronization status change and the first reason, the terminal executes a connection recovery policy corresponding to the highest priority according to the priority order of the timing synchronization status change and the first reason, thereby completing reconnection with the network.

It can be appreciated that the implementation process of each implementation manner mentioned in this embodiment may refer to the related description of the method embodiment, and achieve the same or corresponding technical effects, so that repetition is avoided and detailed description is omitted herein.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above-mentioned connection recovery processing method embodiment, and can achieve the same technical effects, and in order to avoid repetition, the description is omitted here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

The embodiment of the application further provides a chip, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the processes of the connection recovery processing method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and the description is omitted here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the above-mentioned embodiments of the connection recovery processing method, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated here.

The embodiment of the application also provides a wireless communication system, which comprises: the terminal and the network side device, the terminal can be used for executing the steps of the connection recovery processing method.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the description of the embodiments above, it will be apparent to those skilled in the art that the above-described example methods may be implemented by means of a computer software product plus a necessary general purpose hardware platform, but may also be implemented by hardware. The computer software product is stored on a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes instructions for causing a terminal or network side device to perform the methods according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms of embodiments may be made by those of ordinary skill in the art without departing from the spirit of the application and the scope of the claims, which fall within the protection of the present application.

Claims

1. A connection recovery processing method, characterized by comprising:

2. The method of claim 1, wherein the first cause comprises at least one of:

responding to Radio Access Network (RAN) paging;

a high layer indicates, wherein the high layer is a non-access NAS layer;

The RAN informs of the area update.

3. The method of claim 2, wherein the NAS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.

4. A method according to claim 2 or 3, wherein the timing synchronisation state change and the priority order of the first cause comprises any one of:

5. The method of any of claims 2 to 4, wherein the timing synchronization state change and the priority order of the first cause comprises any of:

6. The method according to claim 4 or 5, wherein the NAS layer of the terminal triggers an RRC connection restoration corresponding connection restoration policy based on the timing synchronization state change, comprising:

7. The method of claim 2, wherein the AS layer of the terminal triggers RRC connection restoration based on the timing synchronization state change.

8. The method of claim 2 or 7, wherein the timing synchronization state change and the priority order of the first cause comprise any one of:

9. The method of claim 8, wherein the AS layer of the terminal triggers an RRC connection restoration corresponding connection restoration policy based on the timing synchronization state change, comprising:

10. The method of claim 9, wherein the selecting an access category and a connection restoration reason based on whether an ongoing emergency service exists comprises:

11. The method of claim 6, 9 or 10, wherein the connection recovery policy further comprises:

if the access attempt is disabled, the flow of connection recovery is stopped.

12. A connection restoration processing apparatus, comprising:

13. The apparatus of claim 12, wherein the first cause comprises at least one of:

responding to Radio Access Network (RAN) paging;

a high layer indicates, wherein the high layer is a non-access NAS layer;

The RAN informs of the area update.

14. The apparatus of claim 13, wherein a NAS layer of a terminal triggers RRC connection recovery based on the timing synchronization state change.

15. The apparatus of claim 13 or 14, wherein the timing synchronization state change and the priority order of the first cause comprise any one of:

The priority of the high-level instruction is equal to the priority of the timing synchronization state change, the priority of the high-level instruction is greater than the priority of the response RAN paging, and the priority of the response RAN paging is greater than the priority of the RAN notification area update.

16. The apparatus of any of claims 13 to 15, wherein the timing synchronization state change and the priority order of the first cause comprise any of:

17. The apparatus according to claim 15 or 16, wherein the NAS layer of the terminal triggers an RRC connection restoration corresponding connection restoration policy based on the timing synchronization state change, comprising:

18. The apparatus of claim 13, wherein an AS layer of the terminal triggers RRC connection restoration based on the timing synchronization state change.

19. The apparatus of claim 13 or 18, wherein the timing synchronization state change and the priority order of the first cause comprise any one of:

20. The apparatus of claim 19, wherein the AS layer of the terminal triggers an RRC connection restoration corresponding connection restoration policy based on the timing synchronization state change, comprising:

21. The apparatus of claim 20, wherein the selecting the access category and the connection restoration reason based on whether there is an ongoing emergency service comprises:

22. The apparatus of claim 17, 20 or 21, wherein the connection recovery policy further comprises:

if the access attempt is disabled, the flow of connection recovery is stopped.

23. A terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the connection recovery processing method of any one of claims 1 to 11.

24. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the connection restoration processing method according to any one of claims 1 to 11.