CN114390567A - Exception handling method, terminal and storage medium - Google Patents

Abstract

The embodiment of the application provides an exception handling method, a terminal and a storage medium, wherein the method comprises the following steps: when the terminal sends or receives data in an RRC (radio resource control) non-activated state, if the abnormality is detected, performing target processing; wherein the target process comprises any one of: entering into RRC idle state, entering into RRC inactive state, and performing RRC reestablishment. The embodiment of the application avoids the occurrence of a waiting process and a data loss condition.

Description

Exception handling method, terminal and storage medium

technical field

The present application relates to the field of communication technologies, and in particular, to an exception handling method, a terminal, and a storage medium.

Background technique

If the terminal in the Radio Resource Control (RRC) disconnected state is allowed to directly send small data and subsequent small data transmission, the terminal will be prevented from frequently entering the RRC connected state, which can reduce unnecessary signaling overhead. However, in this process, there is currently no relevant discussion on how to detect the occurrence of various anomalies and follow-up processing.

SUMMARY OF THE INVENTION

Embodiments of the present application provide an exception handling method, a terminal, and a storage medium, so as to solve the problem that the prior art cannot check and handle exceptions that occur during small data transmission.

In a first aspect, an embodiment of the present application provides an exception handling method, including:

When the terminal sends or receives data in the RRC inactive state of the radio resource control, if an abnormality is detected, the target processing is performed;

The target processing includes any one of the following: entering an RRC idle state, entering an RRC inactive state, and performing RRC reconstruction.

In a second aspect, an embodiment of the present application provides a terminal, including a memory, a transceiver, and a processor:

a memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; a processor for reading the computer program in the memory and performing the following operations:

When the terminal sends or receives data in the RRC inactive state of the radio resource control, if an abnormality is detected, the target processing is performed;

The target processing includes any one of the following: entering an RRC idle state, entering an RRC inactive state, and performing RRC reconstruction.

In a third aspect, an embodiment of the present application provides an exception processing device, including:

a processing module, configured to perform target processing if an abnormality is detected when the terminal sends or receives data in the RRC inactive state of the radio resource control;

The target processing includes any one of the following: entering an RRC idle state, entering an RRC inactive state, and performing RRC reconstruction.

In the exception handling method, terminal, and storage medium provided by the embodiments of the present application, when data is directly sent or received in the RRC inactive state, if the terminal detects an abnormality, it enters the RRC idle state, enters the RRC inactive state, or performs RRC reconstruction, It avoids unnecessary waiting process and data loss, reduces data transmission time and ensures data lossless.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the accompanying drawings used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

1 is a flowchart of steps of an exception handling method in an embodiment of the present application;

FIG. 2 is a schematic structural diagram of a terminal in an embodiment of the present application;

FIG. 3 is a block diagram of a module of an exception processing apparatus in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The NR system has designed three RRC states: idle (RRC_IDLE) state, connected (RRC_CONNECTED) state and inactive (RRC_INACTIVE) state. In the connected state, the air interface between the terminal and the wireless network is always available; but in the idle state, the air interface between the terminal and the wireless network is disconnected; in the active state, the air interface between the terminal and the wireless network is suspended. Requires recovery to use.

In addition, small data transmission (SDT) means that when the terminal is in the IDLE state or inactive state, when the amount of data is less than a certain threshold, or when the number of data packets is less than a certain amount of data, the terminal can remain in IDLE or inactive state. The inactive state executes SDT without entering the connected state, thereby reducing signaling overhead and data transmission delay. Further, the terminal can maintain the IDLE or inactive state to send multiple uplink (UL) or receive multiple downlink (DL) small data packets.

When discussing small data transmission, it is considered that the resources of a random access channel (Random Access Channel, RACH) or the resources of a CG (Configured grant) can be used to send the first UL small data packet and possibly other signaling.

However, when the inactive state directly performs small data transmission and subsequent small data reception/transmission, this process may be longer than the existing state transition process (transition from IDLE or inactive state to RRC connection state), which may occur Various exceptions. At this time, there is no relevant discussion on how to detect the occurrence of various abnormalities and subsequent processing.

Therefore, the embodiments of the present application provide an exception handling method, a terminal, and a storage medium, so as to solve the problem in the prior art that the exceptions occurring in the small data transmission process cannot be checked and processed.

The method and the device are conceived based on the same application. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and repeated descriptions will not be repeated here.

The technical solutions provided in the embodiments of the present application can be applied to various systems, especially 5G systems. For example, applicable systems may be global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) general packet radio Service (general packet radio service, GPRS) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, advanced long-term Evolution (long term evolution advanced, LTE-A) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G New Radio (New Radio, NR) system, etc. . These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (Evloved Packet System, EPS), a 5G system (5GS), and the like.

The terminal device involved in the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem. In different systems, the names of the terminal equipment may be different. For example, in a 5G system, the terminal equipment may be called user equipment (User Equipment, UE). Wireless terminal equipment can communicate with one or more core networks (Core Network, CN) via a radio access network (Radio Access Network, RAN). "telephone) and computers with mobile terminal equipment, eg portable, pocket-sized, hand-held, computer-built or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants, PDA) and other devices. A wireless terminal device may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, A remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), and a user device (user device) are not limited in the embodiments of the present application. Since the terminal equipment and other network equipment (eg, core network equipment, access network equipment (ie base station)) together form a network that can support communication, in the present invention, the terminal equipment is also regarded as a kind of network equipment.

The network device involved in the embodiments of the present application may be a base station, and the base station may include a plurality of cells providing services for the terminal. Depending on the specific application, the base station may also be called an access point, or may be a device in the access network that communicates with wireless terminal equipment through one or more sectors on the air interface, or other names. The network equipment can be used to exchange received air frames with Internet Protocol (IP) packets, and act as a router between the wireless terminal equipment and the rest of the access network, where the rest of the access network can include the Internet. Protocol (IP) communication network. The network devices may also coordinate attribute management for the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in a Global System for Mobile Communications (GSM) or a Code Division Multiple Access (Code Division Multiple Access, CDMA). ), or a network device (NodeB) in a Wide-band Code Division Multiple Access (WCDMA), or an evolved network device in a long term evolution (LTE) system (evolutional Node B, eNB or e-NodeB), a 5G base station (gNB) in a 5G network architecture (next generation system), or a Home evolved Node B (HeNB), a relay node (relay node), A home base station (femto), a pico base station (pico), etc., are not limited in the embodiments of the present application. In some network structures, network devices may include centralized unit (CU) nodes and distributed unit (DU) nodes, which may also be geographically separated.

Furthermore, it is to be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic associated with the embodiment is included in at least one embodiment of the present application. Thus, appearances of "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

The present application will be specifically described below.

As shown in FIG. 1, it is a flowchart of the steps of an exception handling method in an embodiment of the present application, and the method includes the following steps:

Step 101: When the terminal transmits or receives data in the RRC inactive state, if an abnormality is detected, target processing is performed.

Specifically, the data in this embodiment may be small data, that is, data whose amount of data is less than a preset value or the number of data packets is less than a preset number.

Specifically, the target processing includes any one of the following: entering an RRC idle state, entering an RRC inactive state, and performing RRC reconstruction.

That is, when the terminal sends or receives data in the RRC inactive state, if an abnormality is detected, it can enter the RRC idle state, or perform RRC reconstruction, or maintain the RRC inactive state.

In this way, when the present embodiment directly transmits or receives data in the RRC inactive state, if the terminal detects an abnormality, it enters the RRC idle state, enters the RRC inactive state, or performs RRC reconstruction, thereby avoiding unnecessary waiting processes and data loss. Data transmission time is reduced and data lossless is guaranteed.

Optionally, in this embodiment, if at least one of the following is detected, it is determined that an abnormality is detected:

First, if the terminal receives the indication information, it is determined that an abnormality is detected.

The indication information is used to indicate that the number of data retransmissions reaches the maximum number of times.

That is, in the process of sending or receiving data in the RRC inactive state, when the terminal receives an indication that the number of data retransmissions reaches the maximum number, it is determined that an abnormality is detected.

In addition, specifically, the indication information may be delivered by the radio link control RLC layer.

Second, if the terminal detects that a beam failure occurs, it is determined that an abnormality is detected.

Specifically, in the process of sending or receiving data in the inactive state of the RRC, if a beam failure is detected, it is determined that an abnormality is detected.

Third, if the terminal detects that a beam recovery failure has occurred, it is determined that an abnormality is detected.

Specifically, in the process of sending or receiving data in the inactive state of the RRC, if it is detected that the beam recovery fails, it can also be determined that an abnormality is detected.

Fourth, if the terminal detects that cell reselection occurs, it is determined that an abnormality is detected.

Specifically, in the process of sending or receiving data in the RRC inactive state, if it is detected that a cell reselection process occurs, it is determined that an abnormality is detected.

That is, in this embodiment, the detected abnormality may include any one or more of the maximum number of data retransmissions, beam failure, beam recovery failure, and cell reselection.

The beam failure and the beam recovery failure will be specifically described below.

Specifically, the terminal detects that a beam failure occurs, which may include any of the following:

(1) The terminal detects that the signal quality of all synchronization signal blocks (SSB for short) under the current serving cell is lower than the first preset quality threshold.

Specifically, if the terminal detects that the signal quality of all SSBs under the current serving cell of the terminal is lower than the first preset quality threshold, it may determine that a beam failure has occurred.

For example, it is assumed that the current serving cell transmits SSBs in a beam scanning manner, and one beam scanning period includes 4 SSBs. At this time, if the terminal directly transmits or receives small data in the RRC inactive state, and finds that the signal quality of the detected SSB (for example, the received power of the reference signal) is all lower than a preset threshold, the terminal considers that the beam has failed to be detected. .

(2) The terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold.

Specifically, if the terminal detects that the signal quality of the current serving beam of the terminal is lowered and falls below the second preset quality threshold, it is determined that the occurrence of beam failure is detected.

For example, the terminal determines the current serving beam based on the random access (RACH for short) process in the small data transmission process or the DL beam information in the CG resource. At this time, in the process of directly sending or receiving small data in the inactive state of RRC, if the signal quality of the current serving beam is degraded, for example, lower than a preset threshold, it is considered that a beam failure is detected.

(3) The terminal detects that the current serving beam is changed.

Specifically, if the terminal detects that the current serving beam of the terminal is changed, it is determined that the occurrence of beam failure is detected.

For example, the terminal determines the current serving beam based on the random access RACH process in the small data transmission process or the DL beam information in the CG resource, and it is assumed that the determined serving beam is SSB1 at this time. In the process of directly sending or receiving small data in the RRC inactive state, if the current serving beam of the terminal is changed, for example, changed to SSB2, it is considered that a beam failure is detected.

That is, when the terminal detects any one of the above (1), (2) and (3), it considers that the occurrence of beam failure is detected, and then it can be determined that an abnormality is detected.

In addition, specifically, the terminal detects that a beam recovery failure occurs, which may include any one of the following:

(1) The terminal detects that the signal quality of all SSBs under the current serving cell is lower than the first preset quality threshold, and the duration of the lower than the first preset quality threshold is greater than the first preset value.

Specifically, if the terminal detects that the signal quality of all SSBs under the current serving cell of the terminal is lower than the first preset quality threshold, and the duration of the lower than the first preset quality threshold is greater than the first preset value, it is considered that A beam recovery failure has occurred.

Specifically, the first preset value may be determined by a timer, that is, if the duration of time lower than the first preset quality threshold exceeds the timing time of the timer, it is considered that beam recovery fails.

For example, it is assumed that the current serving cell of the terminal transmits the SSB in a beam scanning manner, and one beam scanning period includes 4 SSBs. At this time, if the terminal directly transmits or receives small data in the RRC inactive state and finds that the signal quality of the detected SSB is lower than a preset threshold, the terminal starts a timer T1 at this time. Before the T1 timeout, if the signal quality of the SSB of the serving cell that the terminal can detect is still lower than the preset threshold (ie, has not recovered), after the T1 timeout, the terminal considers that beam recovery failure is detected.

(2), the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, and the duration of being lower than the second preset quality threshold is greater than the second preset value.

Specifically, if the terminal detects that the signal quality of the current serving beam of the terminal decreases, and the duration of the decrease to below the second preset quality threshold is greater than the second preset value, it is considered that beam recovery failure has occurred.

The second preset value may also be determined by the timer timing, that is, if the duration of the degradation of the signal quality exceeds the timing time of the timer, it is considered that the beam recovery fails.

For example, the terminal determines the current serving beam based on the RACH process in the small data transmission process or the DL beam information in the CG resource. At this time, in the process of directly sending or receiving small data in the RRC inactive state, if the signal quality of the current serving beam decreases, for example, when the signal quality drops below a preset threshold, the terminal starts a timer T2. During the operation of T2, regardless of whether the terminal has changed the current serving beam, if the signal quality of the current serving beam has not recovered (that is, has not exceeded the set preset threshold), after T2 times out, the terminal will consider that a beam has been detected. Recovery failed.

(3), when the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, sends a beam recovery report to the network side, and does not receive a beam recovery report sent by the network side within the first preset period of time. Feedback.

Specifically, when the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold and sends a beam restoration report to the network side, but does not receive the beam restoration feedback from the network side within the first preset period, it is considered that the A beam recovery failure has occurred.

In addition, the beam recovery report may include information about the beam selected by the terminal to recover.

For example, the terminal determines the current serving beam based on the RACH process in the small data transmission process or the DL beam information in the CG resource. At this time, in the process of directly sending or receiving small data in the RRC inactive state, if the signal quality of the current serving beam decreases, for example, when the signal quality drops below a preset threshold, the terminal starts a timer T3 and sends a message to the network side. A beam restoration report, optionally, the beam restoration report includes the selected beams to be restored. When T3 times out, if the terminal does not receive the beam recovery feedback from the network side, the terminal considers that the beam recovery failure is detected.

(4) When the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, it fails to receive downlink scheduling or data within the second preset time period.

Specifically, after the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, if the downlink scheduling or data is not successfully received within the second preset time period, it is considered that beam recovery failure has occurred.

For example, the terminal determines the current serving beam based on the RACH process in the small data transmission process or the DL beam information in the CG resource. At this time, in the process of directly sending or receiving small data in the RRC inactive state, if the signal quality of the current serving beam decreases, for example, when the signal quality drops below a preset threshold, the terminal starts the timer T4. During the operation of T4, the terminal starts the timer T4. If the terminal does not successfully receive the DL scheduling or data, after T4 times out, the terminal considers that beam recovery failure has been detected.

That is, when the terminal detects any one of the above (1), (2), (3) and (4), it considers that a beam recovery failure has occurred, and further can determine that an abnormality has been detected.

In addition, optionally, in this embodiment, for different target processing modes, the terminal also needs to perform other operations correspondingly, which will be described below.

Optionally, when the target processing mode is to enter the RRC idle state, that is, if the terminal detects an abnormality and enters the RRC idle state, the terminal also needs to perform the following operations at the same time:

Stop sending or receiving data in the RRC inactive state; and/or, send a failure cause to the upper layer of the terminal side, wherein the failure cause is that the terminal fails to send or receive data in the RRC inactive state.

In this way, when the terminal enters the RRC idle state, it stops sending or receiving data, thereby avoiding data loss; in addition, by sending the failure reason to the upper layer of the terminal side, the higher layer of the terminal side can know the specific reason for the failure of data transmission. Inactive state fails to send or receive data, avoiding unnecessary waiting process.

In addition, optionally, when the target processing mode is to enter the RRC inactive state, the terminal also needs to perform at least one of the following operations at the same time:

First, stop sending or receiving data in the RRC inactive state.

Specifically, if the terminal detects that the abnormal target processing method is to enter the RRC inactive state, that is, continue to maintain the RRC inactive state, it stops sending or receiving data in the RRC inactive state to avoid unnecessary data loss.

Second, the failure reason is sent to the upper layer on the terminal side.

Specifically, the failure reason is that the terminal fails to send or receive data in the RRC inactive state.

The terminal sends the failure reason to the upper layer of the terminal side, so that the upper layer of the terminal side can know the reason for the failure of data transmission in time, avoiding unnecessary waiting process.

Third, if the terminal is updated in the process of sending or receiving data in the RRC inactive state, it will return to the state when the RRC inactive state has not been updated before sending or receiving data.

Specifically, if the terminal is updated in the process of sending or receiving data in the RRC inactive state, the terminal returns to the state when the data was not updated before the RRC inactive state sent or received data, thereby ensuring the smooth transmission of subsequent data.

For example, suppose that during the process of sending or receiving data in the RRC inactive state, the terminal updates the key according to the next hop link count (NCC for short) in the RRC release message. At this time, the terminal deletes the updated key and restores the key. The previous key is used; for example, the Packet Data Convergence Protocol Sequence Number (PDCP SN for short) is reset to 0, or the PDCP SN is restored to the PDCP SN stored in the RRC inactive state.

In this way, by any of the above methods, unnecessary waiting processes and data loss are avoided.

In addition, optionally, when the target processing mode is to perform RRC reconstruction, the process of RRC reconstruction includes:

The terminal performs RRC re-establishment in the current serving cell; and/or, if the terminal is updated in the process of sending or receiving data in the RRC inactive state, restore to the state when the data was not updated before sending or receiving the data in the RRC inactive state.

Specifically, when the terminal detects an abnormal situation and performs RRC re-establishment, in some cases, such as abnormal situations such as cell reselection or beam failure, the terminal can perform the RRC re-establishment process in the current serving cell without needing to perform the RRC re-establishment process again. Perform cell reselection. In addition, if the terminal is updated in the process of sending or receiving data in the RRC inactive state, it will return to the state when the RRC inactive state has not been updated before sending or receiving data, so as to ensure the smooth transmission of subsequent data.

In addition, specifically, when the target processing mode is to perform RRC reconstruction, the terminal sends an RRC reconstruction request message to the network side, and the RRC reconstruction request message may include at least one of the following information:

The cell radio network temporary identifier (C-RNTI for short) that is stored when the terminal enters the RRC inactive state;

The source physical cell (PCell for short) when the terminal enters the RRC inactive state;

Truncated integrity-protected message authentication code (ShortMAC-I for short) input, where the ShortMAC-I input includes: the physical layer cell identity of the source physical cell when the terminal enters the RRC inactive state, the cell identity of the reconstructed serving cell, and C-RNTI when the terminal enters the RRC inactive state;

RRC re-establishment reason, the RRC re-establishment reason is: the terminal fails to send or receive data in the RRC inactive state, or fails to send small data.

That is, the terminal may include the above at least one item of information in the RRC re-establishment request message and send it to the network-side device, so that the network-side device can perform RRC re-establishment based on this.

It should be noted here that after the terminal sends the RRC reestablishment request message to the network side, the network side can find the radio access network (RAN) node when the terminal enters the RRC inactive state according to the RRC reestablishment request message; specifically, The RAN side node performs security verification on the terminal according to the stored terminal context. After the verification is passed, the network side sends an RRC reconstruction message to the terminal and reconstructs the relevant data transmission.

In this way, after an abnormality is detected, the RRC reconstruction process is performed, so that the connection can be restored in time, and the loss of data is ensured.

In the process of sending or receiving data in the RRC inactive state, the terminal in this embodiment enters the RRC idle state, performs the RRC inactive state, or performs the RRC reconstruction if an abnormality is detected, which avoids the unnecessary waiting process and avoids the data lost.

FIG. 2 is a schematic structural diagram of a terminal provided by an embodiment of the present application, including a memory 220 , a transceiver 200 , and a processor 210 .

2, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 210 and various circuits of memory represented by memory 220 are linked together. The bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein. The bus interface provides the interface. Transceiver 200 may be multiple elements, ie, including a transmitter and a receiver, providing means for communicating with various other devices over transmission media including wireless channels, wired channels, fiber optic cables, and the like. The processor 210 is responsible for managing the bus architecture and general processing, and the memory 220 may store data used by the processor 210 in performing operations.

The processor 210 may be a central processor (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also use a multi-core architecture.

The memory 220 is used to store computer programs; the transceiver 200 is used to send and receive data under the control of the processor; the processor 210 is used to read the computer program in the memory and perform the following operations:

When the terminal sends or receives data in the RRC inactive state of the radio resource control, if an abnormality is detected, the target processing is performed;

The target processing includes any one of the following: entering an RRC idle state, entering an RRC inactive state, and performing RRC reconstruction.

Optionally, the detected abnormality includes at least one of the following:

If the terminal receives the indication information, it is determined that an abnormality is detected, wherein the indication information is used to indicate that the number of retransmissions of the data reaches the maximum number of times;

If the terminal detects that a beam failure occurs, it is determined that an abnormality is detected;

If the terminal detects that a beam recovery failure occurs, it is determined that an abnormality is detected;

If the terminal detects that cell reselection occurs, it is determined that an abnormality is detected.

Optionally, the terminal detects that a beam failure occurs, including any of the following:

The terminal detects that the signal quality of all synchronization signal blocks SSB under the current serving cell is lower than the first preset quality threshold;

The terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold;

The terminal detects that the current serving beam is changed.

Optionally, the terminal detects that a beam recovery failure occurs, including any of the following:

The terminal detects that the signal quality of all SSBs under the current serving cell is lower than the first preset quality threshold, and the duration of being lower than the first preset quality threshold is greater than the first preset value;

The terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, and the duration of being lower than the second preset quality threshold is greater than the second preset value;

When the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, a beam restoration report is sent to the network side, and no feedback information sent by the network side that the beam returns to normal is received within the first preset time period ;

After the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, it fails to receive downlink scheduling or data within the second preset time period.

Optionally, when the target process is to enter the RRC idle state, it further includes:

stop sending or receiving data in the RRC inactive state; and/or,

Send the failure cause to the upper layer on the terminal side, where the failure cause is that the terminal fails to send or receive data in the RRC inactive state.

Optionally, when the target processing is to enter the RRC inactive state, it also includes at least one of the following:

Stop sending or receiving data in the RRC inactive state;

Send the failure cause to the terminal side upper layer, wherein the failure cause is that the terminal fails to send or receive data in the RRC inactive state;

If the terminal is updated in the process of sending or receiving data in the RRC inactive state, it returns to the state when the data was not updated before the RRC inactive state sent or received data.

Optionally, the performing RRC reconstruction includes:

the terminal performs RRC re-establishment in the current serving cell; and/or,

If the terminal is updated in the process of sending or receiving data in the RRC inactive state, it returns to the state when the data was not updated before the RRC inactive state sent or received data.

Optionally, when the target processing mode is to perform RRC reconstruction, the terminal sends an RRC reconstruction request message to the network side;

The RRC re-establishment request message includes at least one of the following information:

The cell radio network temporary identity C-RNTI stored when the terminal enters the RRC inactive state;

The source physical cell when the terminal enters the RRC inactive state;

Truncated integrity-protected message authentication code ShortMAC-I input, where the ShortMAC-I input includes: the physical layer cell identity of the source physical cell when the terminal enters the RRC inactive state, the cell identity of the rebuilt serving cell, and the terminal C-RNTI when entering the RRC inactive state;

RRC re-establishment reason, the RRC re-establishment reason is that the terminal fails to send or receive data in the RRC inactive state, or fails to send small data.

It can be seen from the above embodiment that, in the process of sending or receiving data in the RRC inactive state, if an abnormality is detected, the terminal enters the RRC idle state, performs the RRC inactive state or performs the RRC reconstruction, which avoids the unnecessary waiting process and avoids. data lost.

FIG. 3 is a block diagram of a module of an exception processing apparatus provided by an embodiment of the present application, and the apparatus includes:

The processing module 301 is configured to perform target processing if an abnormality is detected when the terminal transmits or receives data in the RRC inactive state of the radio resource control;

The target processing includes any one of the following: entering an RRC idle state, entering an RRC inactive state, and performing RRC reconstruction.

Optionally, the detected abnormality includes at least one of the following:

If the terminal receives the indication information, it is determined that an abnormality is detected, wherein the indication information is used to indicate that the number of retransmissions of the data reaches the maximum number of times;

If the terminal detects that a beam failure occurs, it is determined that an abnormality is detected;

If the terminal detects that a beam recovery failure occurs, it is determined that an abnormality is detected;

If the terminal detects that cell reselection occurs, it is determined that an abnormality is detected.

Optionally, the terminal detects that a beam failure occurs, including any of the following:

The terminal detects that the signal quality of all synchronization signal blocks SSB under the current serving cell is lower than the first preset quality threshold;

The terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold;

The terminal detects that the current serving beam is changed.

Optionally, the terminal detects that a beam recovery failure occurs, including any of the following:

The terminal detects that the signal quality of all SSBs under the current serving cell is lower than the first preset quality threshold, and the duration of being lower than the first preset quality threshold is greater than the first preset value;

The terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, and the duration of being lower than the second preset quality threshold is greater than the second preset value;

When the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, a beam restoration report is sent to the network side, and no feedback information sent by the network side that the beam returns to normal is received within the first preset time period ;

After the terminal detects that the signal quality of the current serving beam is lower than the second preset quality threshold, it fails to receive downlink scheduling or data within the second preset time period.

Optionally, when the target process is to enter the RRC idle state, it further includes:

a first stop data processing module, configured to stop sending or receiving data in the RRC inactive state; and/or,

The first sending module is configured to send a failure cause to a higher layer on the terminal side, wherein the failure cause is that the terminal fails to send or receive data in an RRC inactive state.

Optionally, when the target processing is to enter the RRC inactive state, it also includes at least one of the following:

The second stop data processing module is used to stop sending or receiving data in the RRC inactive state;

a second sending module, configured to send a failure cause to the terminal side high layer, wherein the failure cause is that the terminal fails to send or receive data in the RRC inactive state;

A recovery module, configured to restore to the state when the terminal is not updated before sending or receiving data in the RRC inactive state if the terminal is updated in the process of sending or receiving data in the RRC inactive state.

Optionally, the performing RRC reconstruction includes:

the terminal performs RRC re-establishment in the current serving cell; and/or,

If the terminal is updated in the process of sending or receiving data in the RRC inactive state, it returns to the state when the data was not updated before the RRC inactive state sent or received data.

Optionally, when the target processing mode is to perform RRC reconstruction, the terminal sends an RRC reconstruction request message to the network side;

The RRC re-establishment request message includes at least one of the following information:

The cell radio network temporary identity C-RNTI stored when the terminal enters the RRC inactive state;

The source physical cell when the terminal enters the RRC inactive state;

Truncated integrity-protected message authentication code ShortMAC-I input, where the ShortMAC-I input includes: the physical layer cell identity of the source physical cell when the terminal enters the RRC inactive state, the cell identity of the rebuilt serving cell, and the terminal C-RNTI when entering the RRC inactive state;

RRC re-establishment reason, the RRC re-establishment reason is that the terminal fails to send or receive data in the RRC inactive state, or fails to send small data.

It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division methods may be used in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a processor-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

It should be noted here that the above-mentioned device provided by the embodiment of the present application can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the same as the method embodiment in this embodiment is not repeated here. The parts and beneficial effects will be described in detail.

On the other hand, an embodiment of the present application further provides a processor-readable storage medium, where a computer program is stored in the processor-readable storage medium, and the computer program is used to cause the processor to execute the processes described in the foregoing embodiments. Methods.

The processor-readable storage medium can be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (eg, floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (eg, CD, DVD, BD, HVD, etc.), and semiconductor memory (eg, ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state disk (SSD)), and the like.

It can be seen from the foregoing embodiments that a processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the exception handling method described in the foregoing embodiments.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media having computer-usable program code embodied therein, including but not limited to disk storage, optical storage, and the like.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowcharts and/or block diagrams, and combinations of flows and/or blocks in the flowcharts and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These processor-executable instructions may also be stored in a processor-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory result in the manufacture of means comprising the instructions product, the instruction means implements the functions specified in the flow or flow of the flowchart and/or the block or blocks of the block diagram.

These processor-executable instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process that Execution of the instructions provides steps for implementing the functions specified in the flowchart or blocks and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (18)

1. An exception handling method, comprising:

when the terminal sends or receives data in a Radio Resource Control (RRC) non-activated state, if the abnormality is detected, performing target processing;

wherein the target process comprises any one of: entering into RRC idle state, entering into RRC inactive state, and performing RRC reestablishment.

2. The exception handling method according to claim 1, wherein said detecting an exception comprises at least one of:

if the terminal receives indication information, determining that the abnormality is detected, wherein the indication information is used for indicating that the retransmission times of the data reach the maximum times;

if the terminal detects that the beam fails to occur, determining that the abnormality is detected;

if the terminal detects that the beam recovery fails, determining that the abnormality is detected;

and if the terminal detects that the cell reselection occurs, determining that the abnormality is detected.

3. The exception handling method according to claim 2, wherein the terminal detecting that the beam failure occurs includes any one of:

the terminal detects that the signal quality of all synchronous signal blocks SSB in the current service cell is lower than a first preset quality threshold;

the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold;

the terminal detects that the current service beam is changed.

4. The exception handling method according to claim 2, wherein the terminal detects that a beam recovery failure occurs, and includes any one of:

the terminal detects that the signal quality of all SSBs in the current service cell is lower than a first preset quality threshold value, and the duration time of the signal quality lower than the first preset quality threshold value is longer than a first preset value;

the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold value, and the duration time of the signal quality lower than the second preset quality threshold value is longer than a second preset value;

when the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold value, a beam recovery report is sent to a network side, and feedback information that the beam sent by the network side recovers to be normal is not received in a first preset time period;

and when the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold value, the downlink scheduling or data is not successfully received in a second preset time period.

5. The exception handling method according to claim 1, wherein when the target process is entering an RRC idle state, further comprising:

stopping transmitting or receiving data in an RRC inactive state; and/or the presence of a gas in the gas,

and sending a failure reason to a terminal side high layer, wherein the failure reason is that the terminal fails to send or receive data in an RRC (radio resource control) inactive state.

6. The exception handling method according to claim 1, wherein when the target process is entering an RRC inactive state, the method further comprises at least one of:

stopping transmitting or receiving data in an RRC inactive state;

sending a failure reason to a terminal side high layer, wherein the failure reason is that the terminal fails to send or receive data in an RRC (radio resource control) inactive state;

and if the terminal is updated in the process of sending or receiving data in the RRC non-activated state, restoring to the state when the data is not updated before the data is sent or received in the RRC non-activated state.

7. The exception handling method according to claim 1, wherein said performing RRC reestablishment comprises:

the terminal carries out RRC reconstruction in the current serving cell; and/or the presence of a gas in the gas,

and if the terminal is updated in the process of sending or receiving data in the RRC non-activated state, restoring to the state when the data is not updated before the data is sent or received in the RRC non-activated state.

8. The exception handling method according to claim 1, wherein when the target processing mode is RRC reestablishment, the terminal sends an RRC reestablishment request message to a network side;

wherein the RRC reestablishment request message comprises at least one of the following information:

the terminal enters a cell radio network temporary identifier C-RNTI stored when the RRC is in an inactive state;

a source physical cell when the terminal enters an RRC (radio resource control) inactive state;

a truncated integrity protected message authentication code ShortMAC-I input, wherein the ShortMAC-I input comprises: the physical layer cell identification of a source physical cell when the terminal enters an RRC non-activated state, the cell identification of a reconstructed service cell and the C-RNTI when the terminal enters the RRC non-activated state;

and the RRC reestablishment reason is that the terminal fails to send or receive data in an RRC non-activated state or fails to send small data.

9. A terminal, comprising a memory, a transceiver, a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

when the terminal sends or receives data in a Radio Resource Control (RRC) non-activated state, if the abnormality is detected, performing target processing;

wherein the target process comprises any one of: entering into RRC idle state, entering into RRC inactive state, and performing RRC reestablishment.

10. The terminal of claim 9, wherein the detected anomaly comprises at least one of:

if the terminal receives indication information, determining that the abnormality is detected, wherein the indication information is used for indicating that the retransmission times of the data reach the maximum times;

if the terminal detects that the beam fails to occur, determining that the abnormality is detected;

if the terminal detects that the beam recovery fails, determining that the abnormality is detected;

and if the terminal detects that the cell reselection occurs, determining that the abnormality is detected.

11. The terminal of claim 10, wherein the terminal detects the occurrence of the beam failure, and comprises any one of:

the terminal detects that the signal quality of all synchronous signal blocks SSB in the current service cell is lower than a first preset quality threshold;

the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold;

the terminal detects that the current service beam is changed.

12. The terminal of claim 10, wherein the terminal detects that a beam recovery failure occurs, and comprises any one of:

the terminal detects that the signal quality of all SSBs in the current service cell is lower than a first preset quality threshold value, and the duration time of the signal quality lower than the first preset quality threshold value is longer than a first preset value;

the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold value, and the duration time of the signal quality lower than the second preset quality threshold value is longer than a second preset value;

when the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold value, a beam recovery report is sent to a network side, and feedback information that the beam sent by the network side recovers to be normal is not received in a first preset time period;

and when the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold value, the downlink scheduling or data is not successfully received in a second preset time period.

13. The terminal of claim 9, wherein when the target process is entering an RRC idle state, further comprising:

stopping transmitting or receiving data in an RRC inactive state; and/or the presence of a gas in the gas,

and sending a failure reason to a terminal side high layer, wherein the failure reason is that the terminal fails to send or receive data in an RRC (radio resource control) inactive state.

14. The terminal of claim 9, wherein when the target process is entering an RRC inactive state, further comprising at least one of:

stopping transmitting or receiving data in an RRC inactive state;

sending a failure reason to a terminal side high layer, wherein the failure reason is that the terminal fails to send or receive data in an RRC (radio resource control) inactive state;

and if the terminal is updated in the process of sending or receiving data in the RRC non-activated state, restoring to the state when the data is not updated before the data is sent or received in the RRC non-activated state.

15. The terminal of claim 9, wherein the performing RRC reestablishment comprises:

the terminal carries out RRC reconstruction in the current serving cell; and/or the presence of a gas in the gas,

and if the terminal is updated in the process of sending or receiving data in the RRC non-activated state, restoring to the state when the data is not updated before the data is sent or received in the RRC non-activated state.

16. The terminal according to claim 9, wherein when the target processing mode is RRC reestablishment, the terminal sends an RRC reestablishment request message to a network side;

wherein the RRC reestablishment request message comprises at least one of the following information:

the terminal enters a cell radio network temporary identifier C-RNTI stored when the RRC is in an inactive state;

a source physical cell when the terminal enters an RRC (radio resource control) inactive state;

a truncated integrity protected message authentication code ShortMAC-I input, wherein the ShortMAC-I input comprises: the physical layer cell identification of a source physical cell when the terminal enters an RRC non-activated state, the cell identification of a reconstructed service cell and the C-RNTI when the terminal enters the RRC non-activated state;

and the RRC reestablishment reason is that the terminal fails to send or receive data in an RRC non-activated state or fails to send small data.

17. An exception handling apparatus, comprising:

the processing module is used for carrying out target processing if abnormality is detected when the terminal sends or receives data in a Radio Resource Control (RRC) non-activated state;

wherein the target process comprises any one of: entering into RRC idle state, entering into RRC inactive state, and performing RRC reestablishment.

18. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing a processor to perform the method of any one of claims 1 to 8.

Images