Connection recovery processing method, device and equipment
By executing the connection recovery strategy in the terminal according to the priority order, the network reconnection problem of the terminal when the timing synchronization state of the access network changes and other reasons conflicts is solved, and stable network connection recovery is achieved.
Patent Information
- Application Number
- CN202310535433.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-12
AI Technical Summary
When the terminal changes the timing synchronization status of the access network and conflicts with other reasons, how to restore the connection to the network becomes an urgent problem.
By controlling the RRC connection recovery in the case of a radio resource triggered by a timing synchronization state change and a first cause, the terminal executes a connection recovery strategy corresponding to the highest priority according to the order of the timing synchronization state change and the first cause to complete the network Reconnect.
It effectively solves the problem of network reconnection in terminals under multiple causes conflicts, ensuring stable connection and recovery between terminals and networks.
Smart Images

Figure CN118945895A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a connection recovery processing method, device and equipment. Background Art
[0002] Currently, the terminal may reconnect to the network due to a change in the timing synchronization state of the access network. In addition, the terminal may also be triggered to reconnect to the network due to other reasons.
[0003] However, when the access network timing synchronization status changes and other reasons conflict, how the terminal can restore the connection with the network has become a technical problem that needs to be solved urgently. Summary of the invention
[0004] The embodiments of the present application provide a connection recovery processing method, apparatus and device, which can solve the problem of how a terminal recovers its connection with a network when the access network timing synchronization state changes and other reasons conflict.
[0005] In a first aspect, a connection recovery processing method is provided, the method comprising:
[0006] In the case where the timing synchronization state change and the first cause trigger the radio resource control RRC connection recovery, the terminal executes the connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause;
[0007] The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
[0008] In a second aspect, a connection recovery processing device is provided, including:
[0009] A processing module, configured to, when a timing synchronization state change and a first cause trigger a radio resource control RRC connection recovery, execute a connection recovery strategy corresponding to a highest priority according to a priority order of the timing synchronization state change and the first cause;
[0010] The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
[0011] In a third aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.
[0012] In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to, when a timing synchronization state change and a first cause trigger a radio resource control RRC connection recovery, execute a connection recovery strategy corresponding to the highest priority according to a priority order of the timing synchronization state change and the first cause;
[0013] The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
[0014] In a fifth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.
[0015] In a sixth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect.
[0016] In a seventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.
[0017] In an eighth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect.
[0018] In an embodiment of the present application, after the terminal determines that the triggering cause of the RRC connection recovery includes a change in the timing synchronization state and a first cause, it will execute the connection recovery strategy corresponding to the highest priority according to the priority order of the change in the timing synchronization state and the first cause, thereby completing the reconnection with the network. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 is a block diagram of a wireless communication system;
[0020] Figure 2 It is a flowchart of a connection recovery processing method according to an embodiment of the present application;
[0021] Figure 3 It is a schematic diagram of the module structure of the connection recovery processing device in an embodiment of the present application;
[0022] Figure 4 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;
[0023] Figure 5 It is a schematic diagram of the structure of the terminal of an embodiment of the present application. DETAILED DESCRIPTION
[0024] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0025] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0026] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0027] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.
[0028] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. 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 a core network device, wherein 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 unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0029] For ease of understanding, some contents involved in the embodiments of the present application are described below:
[0030] The decision of the terminal (also called terminal equipment) to change the radio resource control (RRC) state due to the change of the access network timing synchronization state can be that the non-access layer (NAS) triggers the registration and service request process to access the network, or NAS requests the access layer (AS) to restore the connection with the network.
[0031] RRC inactive state (RRC_INACTIVE state):
[0032] If reconnecting to the network due to a change in the access network timing synchronization status is supported, and reconnecting to the network is requested upon receiving an indication of a change in the access layer timing synchronization status through a configuration update command, and the AS layer indicates the change in the timing synchronization status, the NAS layer of the terminal in the RRC_INACTIVE state should request the AS layer to trigger the RRC connection recovery process so that the terminal enters the RRC_CONNECTED state.
[0033] RRC idle state (RRC_IDLE state):
[0034] If reconnecting to the network due to changes in the access network timing synchronization state is supported, the terminal sets the "support reconnecting to the network due to changes in the timing synchronization state" bit in the 5G system mobility management (5GS Mobility Management, 5GMM) capability information element of the registration request message. After receiving the "reconnection request" in the access network timing synchronization information element of the registration acceptance message on the network side, and the AS layer indicates the change in the timing synchronization state, the NAS layer of the RRC_IDLE state terminal triggers the service request process, namely the RRC connection establishment process, so that the terminal enters the RRC connected state (RRC_CONNECTED state).
[0035] The connection recovery processing method provided by the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.
[0036] like Figure 2 As shown, a connection recovery processing method in an embodiment of the present application includes:
[0037] Step 201, when the timing synchronization state change and the first cause trigger the radio resource control RRC connection recovery, the terminal executes the connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause;
[0038] The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
[0039] Here, the timing synchronization state change and the first cause are each configured with a respective connection recovery strategy, which is used to guide the terminal to perform an operation process of RRC connection recovery. In addition, in this embodiment, the priority order of the timing synchronization state change and the first cause is used to indicate the order in which the corresponding connection recovery strategies are executed.
[0040] In this way, after the terminal determines that the triggering cause of RRC connection recovery includes the timing synchronization state change and the first cause, it will execute the connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause, thereby completing the reconnection with the network.
[0041] As an implementation mode, the AS layer of the terminal executes the connection recovery strategy corresponding to the highest priority.
[0042] In this embodiment, the connection recovery strategy corresponding to the highest priority is the connection recovery strategy corresponding to the timing synchronization state change or the first cause with the highest priority. For example, if the first cause is cause A, and the priority of the timing synchronization state change is greater than (higher than) the priority of cause A, then the connection recovery strategy corresponding to the timing synchronization state change is executed; if the first cause includes cause A and cause B, and the priority of cause B is the highest priority among the priorities of the timing synchronization state change, cause A, and cause B, then the connection recovery strategy corresponding to cause B is executed.
[0043] As an implementation method, the priority order of the scheduled synchronization state change and the first cause can be predefined or configured by the protocol. Specifically, the protocol predefines or configures the priority of the scheduled synchronization state change and the first cause, and the priority order is indicated by the size of the priority; or, the protocol predefines or configures the execution order of the connection recovery strategy corresponding to the scheduled synchronization state change and the first cause, and the execution order is the priority order.
[0044] Optionally, the first reason includes at least one of the following:
[0045] Respond to RAN paging;
[0046] A high-layer indication, where the high-layer is a non-access NAS layer;
[0047] RAN notification area update.
[0048] That is, the RRC connection recovery may be triggered in response to RAN paging, may be triggered by a NAS layer indication, or may be triggered by a RAN Notification Area (RNA) update.
[0049] Optionally, in this embodiment, the NAS layer of the terminal triggers RRC connection recovery based on the change in the timing synchronization state.
[0050] Optionally, in this embodiment, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0051] The priority of responding to the RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is equal to the priority of the timing synchronization state change, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0052] The priority of responding to the RAN paging is greater than the priority of the RAN notifying the area update, the priority of the RAN notifying the area update is greater than the priority of the high-layer indication, and the priority of the high-layer indication is equal to the priority of the timing synchronization state change;
[0053] The priority of the high-layer indication is equal to the priority of the timing synchronization state change, the priority of the high-layer indication is greater than the priority of the response to RAN paging, and the priority of the response to RAN paging is greater than the priority of the RAN notification area update.
[0054] That is, for the NAS layer triggering RRC connection recovery based on the timing synchronization state change, the timing synchronization state change belongs to the high-level indication. In this way, based on the specific implementation of the first cause, the cause with the highest priority is determined according to the priority order of the above-mentioned first cause. If the priority of the high-level indication is the highest priority, the priority of the timing synchronization state change is also the highest priority; if the priority of the high-level indication is not the highest priority, the priority of the timing synchronization state change is not the highest priority either, and the cause with the highest priority is determined according to the priority order of the above-mentioned first cause.
[0055] Optionally, in this embodiment, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0056] The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0057] The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer 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.
[0058] That is, for the NAS layer triggering 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 high-level layer. In this way, based on the timing synchronization state change and the specific implementation of the first cause, the highest priority is determined according to the above priority order as a certain cause (a certain cause in the first cause) or the timing synchronization state change.
[0059] Optionally, the NAS layer of the terminal triggers a connection recovery strategy corresponding to RRC connection recovery based on the timing synchronization state change, including:
[0060] The NAS layer provides an access category and an access identity based on the timing synchronization state change;
[0061] Use the access category access identity provided by the NAS layer to perform unified access control;
[0062] The access identity provided by the NAS layer includes one or more access identities.
[0063] As an implementation method, for the NAS layer triggering RRC connection recovery based on the change in the timing synchronization status, its connection recovery strategy is similar to the connection recovery strategy corresponding to the NAS layer indication, including: the NAS layer provides an access category and one or more access identities, and unified access control is performed using the access category and access identity provided by the NAS layer; if the access attempt is prohibited, the connection recovery process is stopped.
[0064] Optionally, in this embodiment, the AS layer of the terminal triggers RRC connection recovery based on the change in the timing synchronization state.
[0065] Optionally, in this embodiment, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0066] The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0067] The priority of the timing synchronization state change is greater than the priority of the response to RAN paging, the priority of the response to RAN paging is greater than the priority of the high-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0068] The priority of responding to the 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;
[0069] The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is greater than the priority of the RAN notification area update, and the priority of the RAN notification area update is greater than the priority of the timing synchronization state change.
[0070] That is, for the AS layer triggering RRC connection recovery based on the change in the timing synchronization status, further based on the change in the timing synchronization status and the specific implementation of the first cause, the highest priority is determined in the above-mentioned priority order as a certain cause (a certain cause in the first cause) or a change in the timing synchronization status, and the terminal executes the corresponding connection recovery strategy.
[0071] Optionally, the AS layer of the terminal triggers a connection recovery strategy corresponding to RRC connection recovery based on the change in the timing synchronization state, including:
[0072] Select the access category and connection restoration reason based on whether there is an ongoing emergency service;
[0073] Using the selected access category and connection restoration reason, unified access control is performed.
[0074] That is, the AS layer triggers RRC connection recovery based on the change in the timing synchronization state, and the terminal executes the connection recovery strategy corresponding to the change in the timing synchronization state. It selects the access category and connection recovery reason according to whether there is an ongoing emergency service, and then uses the selected access category and connection recovery reason to perform unified access control.
[0075] Optionally, selecting the access category and the connection restoration reason according to whether there is an ongoing emergency service includes:
[0076] If there is an ongoing emergency service, select the first access category and set the connection restoration reason to emergency;
[0077] If there is no ongoing emergency service, select the second access category and set the connection recovery reason to the protocol preset reason corresponding to the second access category; or select the second access category and set the connection recovery reason to the access network timing synchronization state change.
[0078] As an implementation method, the protocol defines or configures multiple access categories and associated connection recovery reasons as shown in the following table:
[0079]
[0080] According to this, the first access category is the access category "2" defined or configured by the protocol, and the second access category is the access category "3" defined or configured by the protocol. For the second access category, the connection recovery reason defined or configured by the protocol is a protocol preset reason.
[0081] As an implementation, the second access category is access category "8" defined or configured by the protocol, and for the second access category, the connection recovery reason defined or configured by the protocol is a protocol preset reason. Access category "8" corresponds to RNAupdate, which is the AS layer behavior of the terminal.
[0082] Of course, the first access category and the second access category may also be other access categories defined or configured by the protocol, which are not listed here one by one.
[0083] Optionally, in this embodiment, the connection recovery strategy further includes:
[0084] If the access attempt is prohibited, the connection recovery process is stopped.
[0085] Optionally, in this embodiment, the priority order of the timing synchronization state change and the first cause can also be understood as the execution logic of the connection recovery strategy.
[0086] Therefore, for the NAS layer of the terminal triggering the RRC connection recovery based on the timing synchronization state change, the first execution logic of the connection recovery strategy of the terminal includes any one of the following:
[0087] Respond to RAN paging > NAS layer indication > RNA update;
[0088] Respond to RAN paging>RNAupdate>NAS layer indication;
[0089] NAS layer indication > response RAN paging > RNA update;
[0090] At this time, 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), namely, the timing synchronization state change.
[0091] Alternatively, for a connection recovery strategy corresponding to RRC connection recovery triggered by a NAS layer of the terminal based on the timing synchronization state change, the first execution logic of the connection recovery strategy of the terminal includes any one of the following:
[0092] Respond to RAN paging > timing synchronization status change > NAS layer indication > RNA update;
[0093] Respond to RAN paging>NAS layer indication>timing synchronization status change>RNAupdate>NAS layer indication;
[0094] 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 indications.
[0095] In addition, for the AS layer of the terminal triggering RRC connection recovery based on the timing synchronization state change, the second execution logic of the connection recovery strategy of the terminal includes:
[0096] Respond to RAN paging > timing synchronization status change > NAS layer indication > RNA update;
[0097] Timing synchronization status changes > response to RAN paging > NAS layer indication > RNAupdate;
[0098] Respond to RAN paging>NAS layer indication>timing synchronization status change>RNAupdate;
[0099] Response to RAN paging>NAS layer indication>RNA update>NAS layer indication;
[0100] At this time, triggering RRC connection recovery based on the change in the timing synchronization state can be understood as a triggering cause existing at the access layer similar to responding to RANpaging and RNAupdate.
[0101] The following describes the application of the method of the embodiment of the present application in conjunction with specific scenarios:
[0102] Scenario 1: The NAS layer triggers RRC connection recovery based on the change of the timing synchronization status and the AS layer triggers RRC connection recovery conflict:
[0103] The NAS layer of the terminal receives the timing synchronization status indication from the AS layer, determines the access category and access identity used for RRC connection recovery corresponding to the timing synchronization status change, and submits the access category and the access identity to the AS layer. In the case of other triggering reasons at the same time, the RRC connection recovery operation of the terminal follows the connection recovery strategy determined by the first execution logic.
[0104] Exemplarily, the reason why the AS layer triggers RRC connection recovery is in response to 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 to RAN paging>timing synchronization state change>RNAupdate>NAS layer indication (other NAS indication), then the terminal executes the connection recovery strategy corresponding to the timing synchronization state change: if the NAS layer provides an access category and one or more access identities, unified access control is performed according to the access category and access identity provided by the NAS layer; if the access attempt is prohibited, the connection recovery process is stopped.
[0105] Scenario 2: The NAS layer triggers RRC connection recovery based on the timing synchronization status change and conflicts with other NAS layer triggers RRC connection recovery:
[0106] The NAS layer of the terminal receives the timing synchronization status indication from the AS layer, determines the access category and access identity used for RRC connection recovery corresponding to the change of the timing synchronization status, and submits the access category and the access identity to the AS layer. In the case where there are other NAS layers triggering RRC connection recovery at the same time, the RRC connection recovery operation of the terminal follows the connection recovery strategy determined by the first execution logic.
[0107] Exemplarily, the first execution logic is to respond to RAN paging> timing synchronization state change> NAS layer indication (other NAS indications)> RNAupdate, and the terminal executes the connection recovery strategy corresponding to the timing synchronization state change: if the NAS layer provides an access category and one or more access identities corresponding to the timing synchronization state change, unified access control is performed according to the access category and access identity provided by the NAS layer; if the access attempt is prohibited, the connection recovery process is stopped.
[0108] Scenario 3: The AS layer triggers RRC connection recovery based on the change of the timing synchronization state and conflicts with the AS layer triggering RRC connection recovery due to other reasons:
[0109] The AS layer (such as the RRC layer) of the terminal determines that the timing synchronization state of the access network has changed, and determines the access category used for the RRC connection recovery corresponding to the timing synchronization state change, that is, the AS layer triggers the RRC connection recovery based on the timing synchronization state change. In the case of other triggering reasons at the same time, the RRC connection recovery operation of the terminal follows the connection recovery strategy determined by the second logic.
[0110] Assuming that the reason for the AS layer triggering RRC connection recovery for other reasons is RNAupdate, the second logic is to respond to RANpaging>NAS layer indication>timing synchronization state change>RNAupdate, then the terminal executes the connection recovery strategy corresponding to the timing synchronization state change: if there is an ongoing emergency service, select "2" as the first access category, and set the connection recovery reason (resumeCause) to emergency (emergency); if there is no ongoing emergency service, execute:
[0111] Select "3" as the second access category and set resumeCause to the protocol preset reason corresponding to "3";
[0112] Select "8" as the second access category and set resumeCause to the protocol preset reason corresponding to "8";
[0113] Select "3" as the second access category and set resumeCause to the access network timing synchronization status change;
[0114] Select "8" as the second access category and set resumeCause to the access network timing synchronization status change.
[0115] Based on the selected access category and connection restoration reason, unified access control is performed.
[0116] Of course, if the access attempt is prohibited, the connection recovery related operations are stopped.
[0117] It should be noted that, in this embodiment, the connection recovery strategy corresponding to the response to RAN paging includes: selecting a third access category, such as access category "0", performing unified access control according to the third access category; if the access attempt is prohibited, stopping the related operations of connection recovery.
[0118] The connection recovery strategy corresponding to the high-level indication includes: 1. If the high-level layer provides an access category and one or more access identities, unified access control is performed according to the access category and access identity provided by the upper layer; if the access attempt is prohibited, the relevant operations of connection recovery are stopped. 2. If the high-level layer provides network slice access layer grouping (Network Slice As Group, NSAG) information and one or more network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI), in the random access process, the highest NSAG priority is used for NSAG among all NSAGs provided in SIB1 and related to the S-NSSAI that triggered the access attempt. 3. If the connection recovery occurs after the release is redirected using the multimedia priority service mpsPriorityIndication, resumeCause is set to mps-PriorityAccess due to multimedia priority service access. 4. Otherwise (the connection recovery occurs before the release is redirected using mpsPriorityIndication), resumeCause is set according to the information received from the upper layer.
[0119] The connection recovery strategy corresponding to the RNA update includes: if there is an ongoing emergency service, select the first access category, such as access category "2", and set resumeCause to emergency; if there is no ongoing emergency service, select the second access category, such as access category "8", and set resumeCause to the protocol preset reason corresponding to "8"; perform unified access control according to the selected access category and connection recovery reason; if the access attempt is prohibited, set the RNA update variable (pendingRNA-Update) to a true value, and stop the related operations of connection recovery.
[0120] To summarize, the method of the embodiment of the present application takes into account the terminal device triggering RRC connection recovery at the NAS / AS layer and other reasons triggering RRC connection recovery, and performs corresponding access control settings for the RRC connection recovery process in order of priority, that is, executes the connection recovery strategy corresponding to the highest priority, and realizes a reasonable connection recovery process for the terminal when multiple connection recovery reasons conflict.
[0121] The connection recovery processing method provided in the embodiment of the present application can be executed by a connection recovery processing device. In the embodiment of the present application, the connection recovery processing device provided in the embodiment of the present application is described by taking the connection recovery processing method executed by the connection recovery processing device as an example.
[0122] like Figure 3 As shown, a connection recovery processing device in an embodiment of the present application includes:
[0123] The processing module 310 is used to execute a connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause when the timing synchronization state change and the first cause trigger the radio resource control RRC connection recovery;
[0124] The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
[0125] Optionally, the first reason includes at least one of the following:
[0126] Respond to RAN paging;
[0127] A high-layer indication, where the high-layer is a non-access NAS layer;
[0128] RAN notification area update.
[0129] Optionally, the NAS layer of the terminal triggers RRC connection recovery based on the change in the timing synchronization state.
[0130] Optionally, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0131] The priority of responding to the RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is equal to the priority of the timing synchronization state change, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0132] The priority of responding to the RAN paging is greater than the priority of the RAN notifying the area update, the priority of the RAN notifying the area update is greater than the priority of the high-layer indication, and the priority of the high-layer indication is equal to the priority of the timing synchronization state change;
[0133] The priority of the high-layer indication is equal to the priority of the timing synchronization state change, the priority of the high-layer indication is greater than the priority of the response to RAN paging, and the priority of the response to RAN paging is greater than the priority of the RAN notification area update.
[0134] Optionally, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0135] The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0136] The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer 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.
[0137] Optionally, the NAS layer of the terminal triggers a connection recovery strategy corresponding to RRC connection recovery based on the timing synchronization state change, including:
[0138] The NAS layer provides an access category and an access identity based on the timing synchronization state change;
[0139] Use the access category access identity provided by the NAS layer to perform unified access control;
[0140] The access identity provided by the NAS layer includes one or more access identities.
[0141] Optionally, the AS layer of the terminal triggers RRC connection recovery based on the change in the timing synchronization state.
[0142] Optionally, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0143] The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0144] The priority of the timing synchronization state change is greater than the priority of the response to RAN paging, the priority of the response to RAN paging is greater than the priority of the high-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0145] The priority of responding to the 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;
[0146] The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is greater than the priority of the RAN notification area update, and the priority of the RAN notification area update is greater than the priority of the timing synchronization state change.
[0147] Optionally, the AS layer of the terminal triggers a connection recovery strategy corresponding to RRC connection recovery based on the change in the timing synchronization state, including:
[0148] Select the access category and connection restoration reason based on whether there is an ongoing emergency service;
[0149] Using the selected access category and connection restoration reason, unified access control is performed.
[0150] Optionally, selecting the access category and the connection restoration reason according to whether there is an ongoing emergency service includes:
[0151] If there is an ongoing emergency service, select the first access category and set the connection restoration reason to emergency;
[0152] If there is no ongoing emergency service, select the second access category and set the connection recovery reason to the protocol preset reason corresponding to the second access category; or select the second access category and set the connection recovery reason to the access network timing synchronization state change.
[0153] Optionally, the connection recovery strategy further includes:
[0154] If the access attempt is prohibited, the connection recovery process is stopped.
[0155] In this way, after the device determines that the triggering cause of RRC connection recovery includes the timing synchronization state change and the first cause, it will execute the connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause, thereby completing the reconnection with the network.
[0156] It should be noted that the device is a device that applies the above-mentioned connection recovery processing method, and the implementation method of the above-mentioned method embodiment is applicable to the device and can also achieve the same technical effect.
[0157] The connection recovery processing device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0158] The connection recovery processing device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0159] like Figure 4 As shown, an embodiment of the present application also provides a communication device 400, including a processor 401 and a memory 402, and the memory 402 stores programs or instructions that can be executed on the processor 401. For example, when the communication device 400 is a terminal, the program or instructions are executed by the processor 401 to implement the various steps of the above-mentioned connection recovery processing method embodiment and can achieve the same technical effect.
[0160] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 2 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0161] The terminal 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509 and at least some of the components of a processor 510.
[0162] Those skilled in the art will appreciate that the terminal 500 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 510 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 5 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0163] It should be understood that in the embodiment of the present application, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042, and the graphics processor 5041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture 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, etc. The user input unit 507 includes a touch panel 5071 and at least one of other input devices 5072. The touch panel 5071 is also called a touch screen. The 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 (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0164] In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 501 can transmit the data to the processor 510 for processing; in addition, the radio frequency unit 501 can send uplink data to the network side device. Generally, 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, etc.
[0165] The memory 509 can be used to store software programs or instructions and various data. The memory 509 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 509 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 509 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0166] The processor 510 may include one or more processing units; optionally, the processor 510 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 510.
[0167] The processor 510 is configured to, when the timing synchronization state change and the first cause trigger the radio resource control RRC connection recovery, execute a connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause;
[0168] The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
[0169] Optionally, the first reason includes at least one of the following:
[0170] Respond to RAN paging;
[0171] A high-layer indication, where the high-layer is a non-access NAS layer;
[0172] RAN notification area update.
[0173] Optionally, the NAS layer of the terminal triggers RRC connection recovery based on the change in the timing synchronization state.
[0174] Optionally, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0175] The priority of responding to the RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is equal to the priority of the timing synchronization state change, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0176] The priority of responding to the RAN paging is greater than the priority of the RAN notifying the area update, the priority of the RAN notifying the area update is greater than the priority of the high-layer indication, and the priority of the high-layer indication is equal to the priority of the timing synchronization state change;
[0177] The priority of the high-layer indication is equal to the priority of the timing synchronization state change, the priority of the high-layer indication is greater than the priority of the response to RAN paging, and the priority of the response to RAN paging is greater than the priority of the RAN notification area update.
[0178] Optionally, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0179] The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0180] The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer 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.
[0181] Optionally, the NAS layer of the terminal triggers a connection recovery strategy corresponding to RRC connection recovery based on the timing synchronization state change, including:
[0182] The NAS layer provides an access category and an access identity based on the timing synchronization state change;
[0183] Use the access category access identity provided by the NAS layer to perform unified access control;
[0184] The access identity provided by the NAS layer includes one or more access identities.
[0185] Optionally, the AS layer of the terminal triggers RRC connection recovery based on the change in the timing synchronization state.
[0186] Optionally, the priority order of the timing synchronization state change and the first cause includes any one of the following:
[0187] The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0188] The priority of the timing synchronization state change is greater than the priority of the response to RAN paging, the priority of the response to RAN paging is greater than the priority of the high-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update;
[0189] The priority of responding to the 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;
[0190] The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is greater than the priority of the RAN notification area update, and the priority of the RAN notification area update is greater than the priority of the timing synchronization state change.
[0191] Optionally, the AS layer of the terminal triggers a connection recovery strategy corresponding to RRC connection recovery based on the change in the timing synchronization state, including:
[0192] Select the access category and connection restoration reason based on whether there is an ongoing emergency service;
[0193] Using the selected access category and connection restoration reason, unified access control is performed.
[0194] Optionally, selecting the access category and the connection restoration reason according to whether there is an ongoing emergency service includes:
[0195] If there is an ongoing emergency service, select the first access category and set the connection restoration reason to emergency;
[0196] If there is no ongoing emergency service, select the second access category and set the connection recovery reason to the protocol preset reason corresponding to the second access category; or select the second access category and set the connection recovery reason to the access network timing synchronization state change.
[0197] Optionally, the connection recovery strategy further includes:
[0198] If the access attempt is prohibited, the connection recovery process is stopped.
[0199] In this way, after the device determines that the triggering cause of RRC connection recovery includes the change in timing synchronization status and the first cause, the AS layer will execute the connection recovery strategy corresponding to the highest priority according to the priority order of the change in timing synchronization status and the first cause, thereby completing reconnection with the network.
[0200] After the terminal determines that the triggering cause of the RRC connection recovery includes the timing synchronization state change and the first cause, it will execute the connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause, thereby completing the reconnection with the network.
[0201] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.
[0202] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned connection recovery processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0203] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.
[0204] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned connection recovery processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0205] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0206] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned connection recovery processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0207] An embodiment of the present application further provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the connection recovery processing method as described above.
[0208] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0209] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.
[0210] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. A connection recovery processing method, characterized in that: include: In the case where the timing synchronization state change and the first cause trigger the radio resource control RRC connection recovery, the terminal executes the connection recovery strategy corresponding to the highest priority according to the priority order of the timing synchronization state change and the first cause; The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
2. The method according to claim 1, characterized in that The first reason includes at least one of the following: Respond to RAN paging; A high-layer indication, where the high-layer is a non-access NAS layer; RAN notification area update.
3. The method according to claim 2, characterized in that The NAS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.
4. The method according to claim 2 or 3, characterized in that: The priority order of the timing synchronization state change and the first cause includes any one of the following: The priority of responding to the 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 notifying the area update, the priority of the RAN notifying the area update is greater than the priority of the high-layer indication, and the priority of the high-layer indication is equal to the priority of the timing synchronization state change; The priority of the high-layer indication is equal to the priority of the timing synchronization state change, the priority of the high-layer indication is greater than the priority of the response to RAN paging, and the priority of the response to RAN paging is greater than the priority of the RAN notification area update.
5. The method according to any one of claims 2 to 4, characterized in that: The priority order of the timing synchronization state change and the first cause includes any one of the following: The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update; The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer 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.
6. The method according to claim 4 or 5, characterized in that: The NAS layer of the terminal triggers a connection recovery strategy corresponding to the RRC connection recovery based on the change in the timing synchronization state, including: The NAS layer provides an access category and an access identity based on the timing synchronization state change; Use the access category access identity provided by the NAS layer to perform unified access control; The access identity provided by the NAS layer includes one or more access identities.
7. The method according to claim 2, characterized in that The AS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.
8. The method according to claim 2 or 7, characterized in that: The priority order of the timing synchronization state change and the first cause includes any one of the following: The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update; The priority of the timing synchronization state change is greater than the priority of the response to RAN paging, the priority of the response to RAN paging is greater than the priority of the high-layer indication, and the priority of the high-layer 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 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 RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is greater than the priority of the RAN notification area update, and the priority of the RAN notification area update is greater than the priority of the timing synchronization state change.
9. The method according to claim 8, characterized in that The AS layer of the terminal triggers a connection recovery strategy corresponding to the RRC connection recovery based on the change in the timing synchronization state, including: Select the access category and connection restoration reason based on whether there is an ongoing emergency service; Using the selected access category and connection restoration reason, unified access control is performed.
10. The method according to claim 9, characterized in that The selecting of the access category and the connection restoration reason according to whether there is an ongoing emergency service includes: If there is an ongoing emergency service, select the first access category and set the connection restoration reason to emergency; If there is no ongoing emergency service, select the second access category and set the connection recovery reason to the protocol preset reason corresponding to the second access category; or select the second access category and set the connection recovery reason to the access network timing synchronization state change.
11. The method according to claim 6, 9 or 10, characterized in that The connection recovery strategy also includes: If the access attempt is prohibited, the connection recovery process is stopped.
12. A connection recovery processing device, characterized in that: include: A processing module, configured to, when a timing synchronization state change and a first cause trigger a radio resource control RRC connection recovery, execute a connection recovery strategy corresponding to a highest priority according to a priority order of the timing synchronization state change and the first cause; The timing synchronization state change is used to indicate that the timing synchronization state of the access network has changed.
13. The device according to claim 12, characterized in that The first reason includes at least one of the following: Respond to RAN paging; A high-layer indication, where the high-layer is a non-access NAS layer; RAN notification area update.
14. The device according to claim 13, characterized in that The NAS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.
15. The device according to claim 13 or 14, characterized in that The priority order of the timing synchronization state change and the first cause includes any one of the following: The priority of responding to the 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 notifying the area update, the priority of the RAN notifying the area update is greater than the priority of the high-layer indication, and the priority of the high-layer indication is equal to the priority of the timing synchronization state change; The priority of the high-layer indication is equal to the priority of the timing synchronization state change, the priority of the high-layer indication is greater than the priority of the response to RAN paging, and the priority of the response to RAN paging is greater than the priority of the RAN notification area update.
16. The device according to any one of claims 13 to 15, characterized in that The priority order of the timing synchronization state change and the first cause includes any one of the following: The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update; The priority of responding to RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer 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.
17. The device according to claim 15 or 16, characterized in that The NAS layer of the terminal triggers a connection recovery strategy corresponding to the RRC connection recovery based on the change in the timing synchronization state, including: The NAS layer provides an access category and an access identity based on the timing synchronization state change; Use the access category access identity provided by the NAS layer to perform unified access control; The access identity provided by the NAS layer includes one or more access identities.
18. The device according to claim 13, characterized in that The AS layer of the terminal triggers RRC connection recovery based on the timing synchronization state change.
19. The device according to claim 13 or 18, characterized in that The priority order of the timing synchronization state change and the first cause includes any one of the following: The priority of responding to 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-layer indication, and the priority of the high-layer indication is greater than the priority of the RAN notification area update; The priority of the timing synchronization state change is greater than the priority of the response to RAN paging, the priority of the response to RAN paging is greater than the priority of the high-layer indication, and the priority of the high-layer 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 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 RAN paging is greater than the priority of the high-layer indication, the priority of the high-layer indication is greater than the priority of the RAN notification area update, and the priority of the RAN notification area update is greater than the priority of the timing synchronization state change.
20. The device according to claim 19, characterized in that The AS layer of the terminal triggers a connection recovery strategy corresponding to the RRC connection recovery based on the change in the timing synchronization state, including: Select the access category and connection restoration reason based on whether there is an ongoing emergency service; Using the selected access category and connection restoration reason, unified access control is performed.
21. The device according to claim 20, characterized in that The selecting of the access category and the connection restoration reason according to whether there is an ongoing emergency service includes: If there is an ongoing emergency service, select the first access category and set the connection restoration reason to emergency; If there is no ongoing emergency service, select the second access category and set the connection recovery reason to the protocol preset reason corresponding to the second access category; or select the second access category and set the connection recovery reason to the access network timing synchronization state change.
22. The device according to claim 17, 20 or 21, characterized in that The connection recovery strategy also includes: If the access attempt is prohibited, the connection recovery process is stopped.
23. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the connection recovery processing method according to any one of claims 1 to 11 are implemented.
24. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the connection recovery processing method according to any one of claims 1 to 11 are implemented.
