CN114390567A - Exception handling method, terminal and storage medium - Google Patents
Exception handling method, terminal and storage medium Download PDFInfo
- Publication number
- CN114390567A CN114390567A CN202011142087.8A CN202011142087A CN114390567A CN 114390567 A CN114390567 A CN 114390567A CN 202011142087 A CN202011142087 A CN 202011142087A CN 114390567 A CN114390567 A CN 114390567A
- Authority
- CN
- China
- Prior art keywords
- terminal
- rrc
- data
- state
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
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
Technical Field
The present application relates to the field of communications technologies, and in particular, to an exception handling method, a terminal, and a storage medium.
Background
If the terminal in the Radio Resource Control (RRC) non-connected state allows direct small data transmission and subsequent small data transmission, the terminal will be prevented from frequently entering the RRC connected state, and unnecessary signaling overhead can be reduced. However, how to detect the occurrence of various exceptions and subsequent processing in this process is not currently discussed.
Disclosure of Invention
The embodiment of the application provides an exception handling method, a terminal and a storage medium, which are used for solving the problem that in the prior art, an exception occurring in a small data transmission process cannot be checked and handled.
In a first aspect, an embodiment of the present application provides an exception handling method, including:
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.
In a second aspect, an embodiment of the present application provides a terminal, including 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.
In a third aspect, an embodiment of the present application provides an exception handling apparatus, including:
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.
According to the abnormity processing method, the terminal and the storage medium provided by the embodiment of the application, when the RRC non-activated state directly transmits or receives data, if the terminal detects an abnormity, the terminal enters the RRC idle state, enters the RRC non-activated state or carries out RRC reconstruction, so that unnecessary waiting processes and data loss are avoided, the data transmission time is shortened, and the data is ensured to be lossless.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart of the 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 an exception handling apparatus according to an embodiment of the present application.
Detailed Description
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, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The NR system has 3 RRC states designed: an IDLE (RRC _ IDLE) state, a CONNECTED (RRC _ CONNECTED) state, and an INACTIVE (RRC _ INACTIVE) state. When in the connection state, the air interface between the terminal and the wireless network is available at any time; but the air interface between the idle terminal and the wireless network is disconnected; in the active state, the air interface between the terminal and the wireless network is suspended and needs to be recovered for use.
In addition, Small Data Transmission (SDT) refers to that when the terminal is in an IDLE state or an inactive state, and when the data amount is less than a certain threshold, or the number of data packets is less than a certain data amount, the terminal can maintain the IDLE state or the inactive state to execute the SDT without entering a connection state, thereby reducing signaling overhead and reducing data transmission delay. Further, the terminal may transmit a plurality of Uplink (UL) packets or receive a plurality of Downlink (DL) small packets while maintaining an IDLE or inactive state.
When small data transmission is currently discussed, it is considered that the first UL small data packet and possibly other signaling may be transmitted using resources of a Random Access Channel (RACH) or resources of a cg (configured grant).
However, when the inactive state directly performs the small data transmission and the subsequent small data reception/transmission, the procedure may be longer than the existing state transition procedure (transition from IDLE or inactive state to RRC connected state), and various exceptions may occur in the procedure. How to detect the occurrence of various exceptions and subsequent processing at this time is not currently discussed.
Therefore, an embodiment of the present application provides an exception handling method, a terminal, and a storage medium, so as to solve the problem that in the prior art, an exception occurring in a small data transmission process cannot be checked and handled.
The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.
The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a long term evolution (long term evolution, LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an LTE-a (long term evolution) system, a universal mobile system (universal mobile telecommunications system, UMTS), a Worldwide Interoperability for Mobile Access (WiMAX) system, a New Radio network (NR 5) system, etc. These various systems include terminal devices and network devices. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5GS), and the like.
The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. In different systems, the names of the terminal devices may be different, for example, in a 5G system, the terminal device may be called a User Equipment (UE). A wireless terminal device, which may be a mobile terminal device such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal device, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application. Since the terminal device forms a network capable of supporting communication with other network devices (e.g., a core network device, an access network device (i.e., a base station)), the terminal device is also considered as a network device in the present invention.
The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells for providing services to a terminal. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be configured to exchange received air frames with Internet Protocol (IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA), may be a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), may be an evolved Node B (eNB or e-NodeB) in a Long Term Evolution (LTE) System, may be a 5G Base Station (gbb) in a 5G network architecture (next evolution System), may be a Home evolved Node B (HeNB), a relay Node (relay Node), a Home Base Station (femto), a pico Base Station (pico Base Station), and the like, which are not limited in the embodiments of the present application. In some network architectures, a network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.
Furthermore, it should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all 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 is explained in detail below.
As shown in fig. 1, a flowchart of the steps of an exception handling method in the embodiment of the present application is shown, where the method includes the following steps:
step 101: when the terminal sends or receives data in an RRC inactive state, if the abnormality is detected, target processing is performed.
Specifically, the data in this embodiment may be small data, that is, data with a data amount smaller than a preset value or data with a data packet number smaller than a preset number.
Specifically, the target process includes any one of: entering into RRC idle state, entering into RRC inactive state, and performing RRC reestablishment.
That is, when the terminal sends or receives data in the RRC inactive state, if an abnormality is detected, the terminal may enter the RRC idle state, perform RRC reestablishment, or maintain the RRC inactive state.
In this way, when the RRC inactive state directly transmits or receives data, if the terminal detects an abnormality, the terminal enters the RRC idle state, enters the RRC inactive state, or performs RRC reestablishment, thereby avoiding unnecessary waiting procedures and data loss, reducing data transmission time, and ensuring lossless data.
Optionally, in this embodiment, it is determined that an abnormality is detected if at least one of the following is detected:
firstly, if the terminal receives the indication information, the abnormality is determined to be detected.
The indication information is used for indicating that the retransmission times of the data reach the maximum times.
That is, in the process of transmitting or receiving data in the RRC inactive state, when the terminal receives an indication that the number of retransmissions of the data reaches the maximum number, it is determined that an abnormality is detected.
In addition, specifically, the indication information may be issued by the RLC layer.
Secondly, if the terminal detects that the beam fails to occur, it is determined that the abnormality is detected.
Specifically, in the process of transmitting or receiving data in the RRC inactive state, if a beam failure is detected, it is determined that an abnormality is detected.
And thirdly, if the terminal detects that the beam recovery fails, determining that the abnormality is detected.
Specifically, in the process of transmitting or receiving data in the RRC inactive state, if a failure of beam recovery is detected, it may also be determined that an abnormality is detected.
And fourthly, if the terminal detects that the cell reselection occurs, determining that the abnormality is detected.
Specifically, in the process of transmitting 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 retransmissions of data, a beam failure, a beam recovery failure, and a cell reselection.
The beam failure and the beam recovery failure are specifically described below.
Specifically, the detecting of the beam failure by the terminal may include any one of the following:
(1) the terminal detects that the signal quality of all synchronous signal blocks (SSB for short) in the current service cell is lower than a first preset quality threshold.
Specifically, if the terminal detects that the signal quality of all SSBs in the current serving cell of the terminal is lower than the first preset quality threshold, it may be determined that the occurrence of beam failure is detected.
For example, assume that the current serving cell transmits the SSBs in a beam scanning manner, and each beam scanning period includes 4 SSBs. At this time, if the terminal directly performs small data transmission or reception in the RRC inactive state, and finds that the detected signal quality (for example, the reference signal received power) of the SSB is lower than a preset threshold, the terminal considers that the beam failure is detected.
(2) And the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold.
Specifically, if the terminal detects that the signal quality of the current serving beam of the terminal is reduced and is lower than the second preset quality threshold, it is determined that the beam failure occurs.
For example, the terminal determines the current serving beam based on a Random Access (RACH) procedure in a small data transmission procedure or DL beam information in a CG resource. At this time, in the process of directly transmitting or receiving small data in the RRC inactive state, if the signal quality of the current serving beam is reduced, for example, below a certain 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 service beam of the terminal is changed, it is determined that the beam failure is detected.
For example, the terminal determines the current service beam based on the random access RACH procedure in the small data transmission procedure or the DL beam information in the CG resource, and it is assumed that the determined service beam is the SSB 1. In the process of directly transmitting or receiving small data in an RRC inactive state, if a current serving beam of the terminal is changed, for example, to SSB2, it is considered that a beam failure is detected.
That is, the terminal detects any one of the above (1), (2) and (3), and determines that the beam failure is detected, and further determines that the abnormality is detected.
In addition, specifically, the detection of the occurrence of the beam recovery failure by the terminal may include any one of the following:
(1) and the terminal detects that the signal quality of all SSBs in the current serving 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.
Specifically, if the terminal detects that the signal quality of all SSBs in the current serving cell of the terminal is lower than a first preset quality threshold, and the duration time lower than the first preset quality threshold is greater than a first preset value, it is determined that the beam recovery fails.
Specifically, the first preset value may be determined by a timer, that is, if the duration time below the first preset quality threshold exceeds the timing time of the timer, the beam recovery is considered to be failed.
For example, assume that the current serving cell of the terminal transmits the SSBs in a beam scanning manner, and each beam scanning period includes 4 SSBs. At this time, if the terminal directly performs small data transmission or reception in the RRC inactive state and finds that the detected signal quality of the SSB is lower than a preset threshold, the terminal starts a timer T1. Before the time-out of T1, if the signal quality of the SSB of the serving cell that can be detected by the terminal is still lower than the preset threshold (i.e., not recovered yet), after the time-out of T1, the terminal considers that the beam recovery failure is detected.
(2) And 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 greater than a second preset value.
Specifically, if the terminal detects that the signal quality of the current serving beam of the terminal is reduced and the duration time of the signal quality reduced to be lower than the second preset quality threshold is greater than the second preset value, it is determined that the beam recovery failure occurs.
The second preset value can also be determined by the timer timing, that is, if the duration of the signal quality degradation exceeds the timing time of the timer, the beam recovery is considered to be failed.
For example, the terminal determines the current service beam based on the RACH procedure in the small data transmission procedure or the DL beam information in the CG resource. At this time, in the process of directly transmitting or receiving small data in the RRC inactive state, if the signal quality of the current serving beam is reduced, for example, the signal quality is reduced to be lower than a certain preset threshold, the terminal starts the timer T2. During the operation of T2, regardless of whether the terminal changes the current service beam, if the signal quality of the current service beam is not recovered (i.e. the signal quality of the current service beam still does not exceed the preset threshold), the terminal considers that the beam recovery failure is detected after the timeout of T2.
(3) And when the terminal detects that the signal quality of the current service beam is lower than a second preset quality threshold, the terminal sends a beam recovery report to the network side, and does not receive feedback information that the beam sent by the network side recovers to be normal in a first preset time period.
Specifically, when detecting that the signal quality of the current service beam is lower than a second preset quality threshold, the terminal sends a beam recovery report to the network side, but does not receive beam recovery feedback from the network side within a first preset time period, which is considered to be a beam recovery failure.
In addition, information that the terminal selects a recovered beam may be included in the beam recovery report.
For example, the terminal determines the current service beam based on the RACH procedure in the small data transmission procedure or the DL beam information in the CG resource. At this time, in the process of directly transmitting or receiving small data in the RRC inactive state, if the signal quality of the current serving beam is reduced, for example, the signal quality is reduced to be lower than a certain preset threshold, the terminal starts a timer T3, and sends a beam recovery report to the network side, and optionally, the beam recovery report includes a beam selected for recovery. 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 has failed to be detected.
(4) 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.
Specifically, after detecting that the signal quality of the current service beam is lower than a second preset quality threshold, if the downlink scheduling or data is not successfully received within a second preset time period, the terminal determines that the beam recovery fails.
For example, the terminal determines the current service beam based on the RACH procedure in the small data transmission procedure or the DL beam information in the CG resource. At this time, in the process of directly transmitting or receiving small data in the RRC inactive state, if the signal quality of the current serving beam is reduced, for example, the signal quality is reduced to be lower than a certain preset threshold, the terminal starts the timer T4, and during the operation period of T4, the terminal does not successfully receive DL scheduling or data, and after T4 times out, the terminal considers that the beam recovery failure is detected.
That is, when the terminal detects any one of the above items (1), (2), (3), and (4), it is considered that the beam recovery failure has been detected, and it can be determined that an abnormality has been detected.
In addition, optionally, in this embodiment, for different target processing manners, the terminal needs to perform other operations correspondingly, which is 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 needs to perform the following operations at the same time:
stopping transmitting or receiving data in an RRC inactive state; and/or sending a failure reason to a terminal side higher layer, wherein the failure reason is that the terminal fails to send or receive data in an RRC (radio resource control) inactive state.
Therefore, the terminal stops sending or receiving data when entering an RRC idle state, and data loss is avoided; in addition, the reason for the failure is sent to the higher layer of the terminal side, so that the higher layer of the terminal side can know the specific reason for the failure of data transmission, namely the failure of data transmission or data reception in the RRC inactive state, and unnecessary waiting process is avoided.
In addition, optionally, when the target processing mode is to enter the RRC inactive state, the terminal further needs to perform at least one of the following operations at the same time:
first, data transmission or reception in the RRC inactive state is stopped.
Specifically, if the terminal detects that the abnormal target processing mode is to enter the RRC inactive state, i.e., to continue to maintain the RRC inactive state, the terminal stops sending or receiving data in the RRC inactive state, so as to avoid unnecessary data loss.
And secondly, sending the failure reason to the terminal side high layer.
Specifically, the failure reason is that the terminal fails to transmit or receive data in the RRC inactive state.
The terminal sends the failure reason to the high layer of the terminal side, so that the high layer of the terminal side can timely acquire the reason of the data transmission failure, and unnecessary waiting process is avoided.
And thirdly, if the terminal is updated in the process of sending or receiving data in the RRC non-activated state, the state is recovered to the state when the data is not updated before the data is sent or received in the RRC non-activated state.
Specifically, if the terminal is updated in the process of sending or receiving data in the RRC inactive state, the terminal is restored to the state when the data is not updated before sending or receiving data in the RRC inactive state, so that smooth transmission of subsequent data is ensured.
For example, assuming that the terminal updates the key according to the next hop link count (NCC for short) in the RRC release message during the RRC inactive state transmitting or receiving data, the terminal deletes the updated key at this time, and recovers the key before continuing use; for example, the packet data convergence protocol sequence number (PDCP SN) is reset to 0, or the PDCP SN is recovered to the PDCP SN stored in the RRC inactive state.
Thus, by any mode, unnecessary waiting processes and data loss are avoided.
In addition, optionally, when the target processing mode is RRC reestablishment, the RRC reestablishment process includes:
the terminal carries out RRC reconstruction in the current service cell; and/or if the terminal is updated in the process of sending or receiving data in the RRC non-activated state, the state is recovered to the state when the data is not updated before the data is sent or received in the RRC non-activated state.
Specifically, when the terminal detects an abnormal situation and performs RRC re-establishment, in some cases, for example, abnormal situations such as cell reselection or beam failure occur, the terminal may perform an RRC re-establishment procedure in the current serving cell without performing cell reselection again. In addition, if the terminal is updated in the process of transmitting or receiving data in the RRC inactive state, the terminal is restored to the state when the data is not updated before being transmitted or received in the RRC inactive state, so as to ensure smooth transmission of subsequent data.
In addition, specifically, when the target processing mode is RRC reestablishment, the terminal sends an RRC reestablishment request message to the network side, where the RRC reestablishment request message may include at least one of the following information:
a cell radio network temporary identifier (C-RNTI for short) stored when the terminal enters an RRC (radio resource control) inactive state;
a source physical cell (PCell for short) when a 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;
RRC reestablishment reason, the RRC reestablishment reason is as follows: the terminal fails to transmit or receive data in the RRC inactive state, or fails to transmit small data.
That is, the terminal may include the at least one item of information in the RRC reestablishment request message and send the RRC reestablishment request message to the network side device, so that the network side device can perform RRC reestablishment based on the RRC reestablishment request message.
It should be noted that, after the terminal sends the RRC reestablishment request message to the network side, the network side may find a radio access network (RAN for short) 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, and after the verification is passed, the network side sends an RRC reestablishment message to the terminal and reestablishes related data transmission.
Therefore, after the abnormity is detected, the RRC reestablishment process is executed, so that the connection can be recovered in time, and the data can be ensured to be lossless.
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 reestablishment if an abnormality is detected, thereby avoiding an unnecessary waiting process and avoiding data loss.
Fig. 2 is a schematic structural diagram of a terminal according to an embodiment of the present application, which includes a memory 220, a transceiver 200, and a processor 210.
Where in fig. 2, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 210, and various circuits, represented by memory 220, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 200 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium 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 Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.
A memory 220 for storing a computer program; a transceiver 200 for transceiving data under the control of the processor; a processor 210 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.
Optionally, the detecting an 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.
Optionally, the terminal detects that a beam failure occurs, including 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.
Optionally, the terminal detects that a beam recovery failure occurs, including 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.
Optionally, when the target process is to enter an RRC idle state, the method further includes:
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.
Optionally, when the target process is to enter an RRC inactive state, at least one of the following is further included:
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.
Optionally, the performing RRC reestablishment includes:
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.
Optionally, when the target processing mode is RRC reestablishment, the terminal sends an RRC reestablishment request message to the 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.
As can be seen from the above embodiments, 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 reestablishment, thereby avoiding an unnecessary waiting process and avoiding data loss.
Fig. 3 is a block diagram of an exception handling apparatus according to an embodiment of the present application, where the apparatus includes:
a processing module 301, configured to perform target processing if an abnormality is detected when the terminal sends or receives data in an RRC inactive state;
wherein the target process comprises any one of: entering into RRC idle state, entering into RRC inactive state, and performing RRC reestablishment.
Optionally, the detecting an 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.
Optionally, the terminal detects that a beam failure occurs, including 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.
Optionally, the terminal detects that a beam recovery failure occurs, including 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.
Optionally, when the target process is to enter an RRC idle state, the method further includes:
the first stop data processing module is used for stopping sending or receiving data in an RRC (radio resource control) inactive state; and/or the presence of a gas in the gas,
the first sending module is used for 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.
Optionally, when the target process is to enter an RRC inactive state, at least one of the following is further included:
the second stop data processing module is used for stopping sending or receiving data in an RRC (radio resource control) inactive state;
a second sending module, configured to send a failure reason to a terminal-side higher layer, where the failure reason is that the terminal fails to send or receive data in an RRC inactive state;
and the recovery module is used for recovering to the state when the data is not updated before the data is sent or received in the RRC non-activated state if the terminal is updated in the process of sending or receiving the data in the RRC non-activated state.
Optionally, the performing RRC reestablishment includes:
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.
Optionally, when the target processing mode is RRC reestablishment, the terminal sends an RRC reestablishment request message to the 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.
It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It should be noted that the apparatus provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.
On the other hand, the embodiment of the present application further provides a processor-readable storage medium, where a computer program is stored, and the computer program is used to enable the processor to execute the method described in the foregoing embodiment.
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 memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.
As seen from the above embodiments, a processor-readable storage medium stores a computer program for causing a processor to execute the exception handling method according to the above embodiments.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or 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 (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
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 application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such 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 intended to include such modifications and variations as well.
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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011142087.8A CN114390567A (en) | 2020-10-22 | 2020-10-22 | Exception handling method, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011142087.8A CN114390567A (en) | 2020-10-22 | 2020-10-22 | Exception handling method, terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114390567A true CN114390567A (en) | 2022-04-22 |
Family
ID=81194515
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011142087.8A Pending CN114390567A (en) | 2020-10-22 | 2020-10-22 | Exception handling method, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114390567A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023207984A1 (en) * | 2022-04-27 | 2023-11-02 | 维沃移动通信有限公司 | Behavior processing method and apparatus, and terminal, network-side device and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180220369A1 (en) * | 2017-02-02 | 2018-08-02 | Htc Corporation | Device and Method of Handling an Inactive State in a Wireless Communication System |
| CN110022567A (en) * | 2018-01-08 | 2019-07-16 | 维沃移动通信有限公司 | A kind of data transmission method and user terminal |
| US20200045669A1 (en) * | 2018-08-06 | 2020-02-06 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting or receiving signal in mobile communication system |
-
2020
- 2020-10-22 CN CN202011142087.8A patent/CN114390567A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180220369A1 (en) * | 2017-02-02 | 2018-08-02 | Htc Corporation | Device and Method of Handling an Inactive State in a Wireless Communication System |
| CN110022567A (en) * | 2018-01-08 | 2019-07-16 | 维沃移动通信有限公司 | A kind of data transmission method and user terminal |
| US20200045669A1 (en) * | 2018-08-06 | 2020-02-06 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting or receiving signal in mobile communication system |
Non-Patent Citations (1)
| Title |
|---|
| ERICSSON: "S2-2002779 \"Transfer Failure Notification Address handling\"", 3GPP TSG_SA\\WG2_ARCH, no. 2 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023207984A1 (en) * | 2022-04-27 | 2023-11-02 | 维沃移动通信有限公司 | Behavior processing method and apparatus, and terminal, network-side device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11071158B2 (en) | Communication method, communications device, and communications system thereof | |
| WO2018210176A1 (en) | Beam failure processing method, auxiliary base station failure processing method and terminal | |
| US11425784B2 (en) | Radio link failure handling method and related product | |
| WO2018090910A1 (en) | Method and device for recovering radio downlink failure | |
| KR20140006789A (en) | Network based control of report messages in a wireless communications network | |
| CN108781376B (en) | Data transmission method, user equipment and access network equipment | |
| US20210251032A1 (en) | Communication method, apparatus, and system | |
| WO2019096274A1 (en) | Signal transmission method and device | |
| CN112399454B (en) | Information transmission method and device | |
| WO2022083484A1 (en) | Data transmission control method, apparatus, and storage medium | |
| CN116017557A (en) | Data transmission method, device and storage medium | |
| US20230354136A1 (en) | Integrated access and backhaul communication method and apparatus | |
| CN114339925A (en) | Switching method, device, terminal equipment, network equipment and storage medium | |
| CN114390567A (en) | Exception handling method, terminal and storage medium | |
| US20160234089A1 (en) | Wireless communication system | |
| WO2022083469A1 (en) | Method and apparatus for determining mro critical scenario, and device | |
| WO2022083411A1 (en) | Method and device for determining error type of secondary cell switching | |
| WO2020164510A1 (en) | Communication method, communication apparatus, and computer-readable storage medium | |
| CN104521275A (en) | Method, apparatus and computer program for a wireless device | |
| US20230388873A1 (en) | Method and apparatus for determining daps handover failure type | |
| WO2023143285A1 (en) | Method and apparatus for processing state information of scg | |
| WO2022222915A1 (en) | Signaling sending method and apparatus, and storage medium | |
| CN115134948A (en) | Method and device for recovering load, core network element and storage medium | |
| WO2023045436A1 (en) | Information sending method and apparatus | |
| CN115134949A (en) | Information sending method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |