Patent Grant
12225613
The present application is a U.S. National Stage of International Application No. PCT/CN2019/121035, filed on Nov. 26, 2019, the contents of all of which are incorporated herein by reference in their entireties for all purposes.
The present disclosure relates to a communication technology, in particular to a method and apparatus for processing radio-link failure, and a computer storage medium.
To support direct communication between the user equipment (UE) and UE, Sidelink communication is introduced, and sometimes Sidelink is also referred to as direct link.
After a network transmits a radio resource control (RRC) connection release message, the UE possibly cannot receive the RRC connection release message due to poor signal quality, causing the UE to remain connected, while the network side has released the UE, resulting in a problem of inconsistency between states of the UE and the network. In order to solve the problem that the UE may incorrectly receive the RRC connection release message, an inactivity timer is introduced. The RRC connection of the UE is released in the absence of data transceiving in a period of time.
The present disclosure provides a method and apparatus for processing radio-link failure, and a computer storage medium.
According to a first aspect of examples of the present disclosure, provided is a method for processing radio-link failure, performed by user equipment (UE), The method includes:
recording a reason for a link failure when user equipment (UE) releases a radio resource control (RRC) connection due to expiration of an inactivity timer; and
reporting failure information including the reason for the link failure.
According to a second aspect of examples of the present disclosure, provided is a method for processing radio-link failure, performed by base station. The method includes:
issuing inactivity timer information configured for a UE; and
receiving failure information including a reason for a link failure reported by the UE; where the reason for the link failure is recorded when RRC connection is released due to expiration of the inactivity timer.
According to a third aspect of examples of the present disclosure, provided is an apparatus for processing radio-link failure. The apparatus includes:
a processor, and
a memory configured to store an executable instruction;
where the processor is configured to implement, by executing the executable instruction, any one of the methods for processing radio-link failure applied to a UE-side technical solution.
According to a fourth aspect of examples of the present disclosure, provided is an apparatus for processing radio-link failure. The apparatus includes:
a processor, and
a memory configured to store an executable instruction;
where the processor is configured to implement, by executing the executable instruction, any one of the methods for processing radio-link failure applied to a base station-side technical solution.
According to a fifth aspect of examples of the present disclosure, provided is a non-transitory computer readable storage medium. The computer readable storage medium stores an executable instruction, and after the executable instruction is executed by a processor, any one of the aforementioned methods for processing radio-link failure is applied to a UE-side as a technical solution.
According to an sixth aspect of examples of the present disclosure, provided is a non-transitory computer readable storage medium. The computer readable storage medium stores an executable instruction, and after the executable instruction is executed by a processor, any one of the aforementioned methods for processing radio-link failure is applied to a base station-side as a technical solution.
It is to be understood that both the foregoing general description and the following detailed description are illustrative and explanatory and are not restrictive of the present disclosure.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate examples consistent with the disclosure and, together with the specification, serve to explain the principles of the present disclosure.
Description will herein be made in detail to examples, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different accompanying drawings refer to the same or similar elements unless otherwise instructed. The implementation modes described in the following examples do not represent all implementation modes consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of examples of the present application as described in detail in the appended claims.
The term used in the examples of the present disclosure is for the purpose of describing particular examples merely and is not intended to be restrictive of the examples of the present disclosure. As used in the examples and the appended claims of the present disclosure, singular forms “a”, “an” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. It is to be understood that the term “and/or” as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be employed in the examples of the present disclosure to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish the same type of information from each other. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the examples of the present disclosure. The word “if” and “in case of” as used herein may be construed to mean “upon” or “when” or “in response to determining”, depending on the context.
To support direct communication between the user equipment (UE) and UE, Sidelink communication is introduced, and sometimes Sidelink is also referred to as direct link.
After a network transmits a radio resource control (RRC) connection release message, the UE possibly cannot receive the RRC connection release message due to poor signal quality, causing the UE to remain connected, while the network side has released the UE, resulting in a problem of inconsistency between states of the UE and the network. In order to solve the problem that the UE may incorrectly receive the RRC connection release message, an inactivity timer is introduced. The RRC connection of the UE is released in the absence of data transceiving activity being detected within a period of time. However, when the UE releases the RRC connection to enter an idle state due to expiration of the inactivity timer, it is indicated that the current radio link quality is inferior, which disables receipt of the RRC connection release message of the network.
With reference to
The terminals 11 may be devices that provide speech and/or data connectivity for a user. Each of the terminals 11 may communicate with one or more core networks by means of a radio access network (RAN), and the terminal 11 may be an Internet of Things terminal, for example, a sensor device, a mobile telephone (or referred to as a “cellular” telephone), and a computer having an Internet of Things terminal, for example, may be a stationary, portable, pocket-sized, hand-held, computer-built, or vehicle-mounted device, for example, a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or user equipment (UE). Alternatively, each of the terminal 11 may be a device of an unmanned aerial vehicle. Alternatively, each of the terminal 11 may be an in-vehicle device, for example, a trip computer with a radio communication function, or a radio communication device to which a trip computer is externally connected. Alternatively, each of the terminal 11 may be a roadside device, for example, a street lamp, a signal lamp, another roadside device, etc. with the radio communication function.
Each of the base stations 12 may be a network-side device in the radio communication system. The radio communication system may be the 4th generation mobile communication (4G) system, also referred to as a long term evolution (LTE) system; and alternatively, the radio communication system may also be a 5G system, also referred to as a new radio (NR) system or a 5G NR system. Alternatively, the radio communication system may also be a next generation system consecutive to the 5G system. An access network in the 5G system may be referred to as a new generation-radio access network (NG-RAN). Alternatively, the radio communication system may be a machine-type communication (MTC) system.
Each of the base stations 12 may be an evolved Node B (eNB) used in a 4G system. Alternatively, each of the base stations 12 may also be a next-generation Node B (gNB) using a central distributed architecture in a 5G system. When the base station 12 uses the central distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DU). The central unit is provided with protocol stacks of a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer and a media access control (MAC) layer; and each distributed unit is provided with a protocol stack of a physical (PHY) layer. Examples of the present disclosure are not limited to the specific implementation modes of the base station 12.
A radio connection may be established between the base stations 12 and the terminals 11 by means of radio air interfaces. In different implementation modes, the radio air interface is a radio air interface based on a 4th generation mobile communication network technology (4G) standard; alternatively, the radio air interface is a radio air interface based on a 5th generation mobile communication network technology (5G) standard, for example, the radio air interface is a new radio; and alternatively, the radio air interface may also be a radio air interface based on a 5G-based next generation mobile communication network technology standard.
In some examples, an end to end (E2E) connection may also be established between the terminals 11, for example, vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication, and other scenes in vehicle to everything (V2X).
In some examples, the above radio communication system may further include a network management device 13.
The several base stations 12 are respectively connected to the network management device 13. The network management device 13 may be a core network device in the radio communication system, for example, the network management device 13 may be a mobility management entity (MME) in an evolved packet core (EPC). Alternatively, the network management device may be another core network device, for example, a serving gate way (SGW), a public data network gate way (PGW), a policy and charging rules function (PCRF), a home subscriber server (HSS), etc. The examples of the present disclosure are not limited with respect to an implementation form of the network management device 13.
Various examples of the method of the present disclosure are proposed for reducing the possibility of radio link failure in a network based on the above radio communication system.
In S11, a reason for a link failure is recorded when user equipment (UE) releases a radio resource control (RRC) connection due to expiration of an inactivity timer.
The inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
Data in the data inactivity timer includes media access control (MAC) service data unit (SDU) data.
The reason for the link failure is that the inactivity timer expires.
In this way, when the UE releases the RRC connection due to expiration of the inactivity timer, it is determined that the UE has the radio link failure, and the reason for the link failure is recorded as expiration of the inactivity timer, such that the failure information including the reason for the link failure may be reported to a network subsequently, and the network may optimize the radio link according to the failure information.
In S12, failure information including the reason for the link failure is reported.
In this way, compared with the situation that no processing is carried out when UE releases a RRC connection due to expiration of the inactivity timer, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
In some examples, reporting failure information including the reason for the link failure includes:
In this way, the failure information including the reason for the link failure may be reported in time, such that the base station may know the reason for the link failure and solve the failure link as soon as possible.
In some examples, reporting the failure information including the reason for the link failure after the RRC connection is recovered includes:
In this way, after the report instruction message is received, the failure information including the reason for the link failure is reported, such that the problem that the base station does not successfully receive the failure information reported by the UE due to inappropriate report time is avoided.
In the above solution, the failure information further includes: timing duration information of the inactivity timer.
In the above solution, the failure information further includes: a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
In this way, the base station may conveniently determine the failure link and the reason for the link failure according to the failure information, and determine a measure for optimizing the failure link based on the reason for the link failure.
In the technical solution of the examples of the present disclosure, when UE releases an RRC connection due to expiration of an inactivity timer, a reason for a link failure is recorded; failure information including the reason for the link failure is reported. Compared with the situation that no processing is carried out when UE releases a RRC connection due to expiration of an inactivity timer, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
In S21, inactivity timer information configured for UE is issued.
The inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
The reason for the link failure is that the inactivity timer expires.
As one implementation mode, issuing inactivity timer information configured for UE further includes:
timing duration information of the inactivity timer information configured for UE is issued.
In this way, the UE may release the RRC connection conveniently when the inactivity timer expires, such that resource waste caused by long-time occupation of resources may be reduced.
In S22, failure information including a reason for a link failure reported by the UE is received; where the reason for the link failure is recorded when an RRC connection is released due to expiration of the inactivity timer.
In this way, the base station may be facilitated to optimize a radio link according to the failure information including the reason for the link failure and reported by the UE, such that the possibility that the radio link fails in the network is reduced.
In some examples, before failure information including a reason for a link failure reported by the UE is received, the method further includes:
In this way, the problem that the base station does not successfully receive the failure information reported by the UE due to inappropriate report time of the UE is avoided.
In the above solution, the failure information further includes timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a C-RNTI provided by the serving cell for the UE, and a target cell identifier for handover.
In this way, the base station may conveniently determine the failure link and the reason for the link failure according to the failure information, and determine a measure for optimizing the failure link based on the reason for the link failure.
In the above solution, the method further includes:
Illustratively, the measure for optimizing the failure link includes, but is not limited to:
In this way, the possibility that the radio link fails in the network may be reduced.
According to the technical solution provided in the example of the present disclosure, inactivity timer information configured for UE is issued; and failure information including a reason for a link failure and reported by the UE is received; where the reason for the link failure is recorded when an RRC connection is released due to expiration of an inactivity timer; and in this way, a base station may be facilitated to optimize a radio link according to the failure information including the reason for the link failure and reported by the UE, such that the possibility that the radio link fails in a network is reduced.
Step 401, a base station sends data inactivity timer information configured for UE to the UE, where a timing duration of a data inactivity timer is, for example, 10 s (where s is seconds).
Step 402, after receiving the data inactivity timer information, the UE starts to detect receiving and sending of data.
Step 403, in response to determining that the data inactivity timer expires, an RRC connection is released to enter an idle state, it is recorded that a reason for a link failure is that the data inactivity timer expires, and it is also recorded that the timing duration of the data inactivity timer is 10 s.
Step 404, after the RRC connection is recovered, the UE reports the recorded failure information including the reason for the link failure.
According to the solution of the example, compared with the situation that no processing is carried out when the UE releases an RRC connection due to expiration of an inactivity timer, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
It is to be noted that the flow and the timing duration are a schematic example implementation and these may be set or adjusted according to actual situations or design requirements.
Step 501, a base station sends sidelink inactivity timer information configured for UE to the UE, where a timing duration of a sidelink inactivity timer is 15 s.
Step 502, after receiving the sidelink inactivity timer information, the UE starts to detect receiving and sending of sidelink data.
Step 503, in response to determining that the sidelink inactivity timer expires, an RRC connection is released to enter an idle state, it is recorded that a reason for a link failure is that the sidelink inactivity timer expires, and it is also recorded that the timing duration of the sidelink inactivity timer is 15 s.
Step 504, after the RRC connection is recovered, the UE reports the recorded failure information including the reason for the link failure.
According to the solution of the example, compared with the situation that no processing is carried out when UE releases an RRC connection due to expiration of a sidelink inactivity timer, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
It is to be noted that the flow and the timing duration are schematic and may be set or adjusted according to actual situations or design requirements.
Step 601, a base station sends data inactivity timer information and sidelink inactivity timer information configured for UE to the UE, where a timing duration of a data inactivity timer is 10 s, and a timing duration of a sidelink inactivity timer is 15 s.
Step 602, after receiving the data inactivity timer information and the sidelink inactivity timer information, the UE starts to detect receiving and sending of data.
Step 603, in response to determining that the data inactivity timer and sidelink inactivity timer both expire, an RRC connection is released to enter an idle state, it is recorded that a reason for a link failure is that the data inactivity timer and the sidelink inactivity timer both expire, and it is also recorded that the timing duration of the data inactivity timer is 10 s and the timing duration of the sidelink inactivity timer is 15 s.
Step 604, after the RRC connection is recovered, the UE reports the recorded failure information including the reason for the link failure.
According to the solution of the example, compared with the situation that no processing is carried out when the UE releases the RRC connection due to expiration of the sidelink inactivity timer and the data inactivity timer both, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
It is to be noted that the flow and the timing duration are schematic and may be set or adjusted according to actual situations or design requirements.
The determination unit 10 is configured to record a reason for a link failure when UE releases an RRC connection due to expiration of an inactivity timer; and
In the above solution, the inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
As one implementation mode, the communication unit 20 is configured to
As one implementation mode, the communication unit 20 is configured to
In the above solution, the failure information further includes: timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
With respect to the apparatus in the above example, specific ways in which the various modules perform operations have been described in detail in the examples relating to the method, and will not be described in detail herein.
In practical use, specific structures of the determination unit 10 and the communication unit 20 may be implemented by a central processing unit (CPU), a micro controller unit (MCU), a digital signal processor (DSP), a programmable logic controller (PLC), etc. in an apparatus for processing radio-link failure or UE to which the apparatus for processing radio-link failure belongs.
The apparatus for processing radio-link failure according to the example may be configured to the UE side.
It is to be understood by those skilled in the art that functions of the processing modules in the apparatus for processing radio-link failure in the example of the present disclosure may be understood with reference to the above related description of the method for processing radio-link failure applied to the UE side, and each processing module in the apparatus for processing radio-link failure may be achieved by means of an analog circuit for implementing the functions described in the example of the present disclosure, and may also be achieved by means of running software, executing the functions described in the example of the present disclosure, on a terminal.
According to the apparatus for processing radio-link failure in the example of the present disclosure, compared with the situation that no processing is carried out when UE releases a RRC connection due to expiration of an inactivity timer, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
The sending unit 30 is configured to issue inactivity timer information configured for the UE; and
In the above solution, the inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
In the above solution, the reception unit 40 is configured to receive a prompt message indicating the UE has failure information sent from the UE; and
In the above solution, the failure information further includes timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
In the above solution, the apparatus further includes:
With respect to the apparatus in the above example, specific ways in which the various modules perform operations have been described in detail in the examples relating to the method, and will not be described in detail herein.
In practical use, specific structures of the sending unit 30, the reception unit 40 and the processing unit 50 may be achieved by the apparatus for processing radio-link failure or a CPU, an MCU, a DSP, a PLC, etc. in a base station to which the apparatus for processing radio-link failure belongs.
The apparatus for processing radio-link failure according to the example may be configured for implementation on the base station side.
It is to be understood by those skilled in the art that functions of the processing modules in the apparatus for processing radio-link failure in the example of the present disclosure may be understood with reference to the above related description of the method for processing radio-link failure applied to the base station side, and each processing module in the apparatus for processing radio-link failure may be achieved by means of an analog circuit for implementing the functions described in the example of the present disclosure, and may also be achieved by means of running software, executing the functions described in the example of the present disclosure, on a terminal.
According to the apparatus for processing radio-link failure in the example of the present disclosure, compared with the situation that no processing is carried out when UE releases a RRC connection due to expiration of an inactivity timer, by recording the reason for the link failure and reporting the failure information including the reason for the link failure, a base station may be facilitated to optimize a radio link according to the failure information, such that the possibility that the radio link fails in a network is reduced.
With reference to
The processing assembly 802 generally controls overall operation of the apparatus 800, for example, operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing assembly 802 may include one or more processors 820 to execute an instruction to complete all or part of the steps of the method above. Moreover, the processing assembly 802 may include one or more modules to facilitate interaction between the processing assembly 802 and other assemblies. For example, the processing assembly 802 may include the multimedia module to facilitate interaction between the multimedia assembly 808 and the processing assembly 802.
The memory 804 is configured to store various types of data to support an operation on the apparatus 800. Examples of such data include an instruction, operated on the apparatus 800, for any application or method, contact data, phonebook data, messages, pictures, video, etc. The memory 804 may be implemented by any type of volatile or non-volatile memory device, or their combination, for example, a static random-access memory (SRAM), an electrically-erasable programmable read only memory (EEPROM), an erasable programmable read only memory (EPROM), a programmable read-only memory (PROM), read only memory (ROM), a magnetic memory, a flash memory, a magnetic or an optical disk.
The power assembly 806 provides power for various assemblies of the apparatus 800. The power assembly 806 may include a power management system, one or more power sources, and other assemblies associated with power generating, managing, and distributing for the apparatus 800.
The multimedia assembly 808 includes a screen that provides an output interface between the apparatus 800 and the user. In some examples, the screen may include a liquid crystal display (LCD) and a touch panel (TP). Under the condition that the screen includes the touch panel, the screen may be implemented as a touch screen to receive an input signal from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or slide action, but also detect duration and pressure related to the touch or slide operation. In some examples, the multimedia assembly 808 includes a front-facing camera and/or a rear-facing camera. When the apparatus 800 is in an operational mode, for example, a photographing mode or a video mode, the front-facing camera and/or the rear-facing camera may receive external multimedia data. Each of the front-facing camera and the rear-facing camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio assembly 810 is configured to output and/or input an audio signal. For example, the audio assembly 810 includes a microphone (MIC), configured to receive an external audio signal when the apparatus 800 is in the operational mode, for example, a calling mode, a recording mode, and a speech recognition mode. The received audio signal may be further stored in the memory 804 or transmitted via the communication assembly 816. In some examples, the audio assembly 810 further includes a speaker for outputting the audio signal.
The I/O interface 812 provides an interface between the processing assembly 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include but are not limited to a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing state assessments of various aspects for the apparatus 800. For example, the sensor assembly 814 may detect an on/off state of the apparatus 800 and relative positioning of the assemblies. For example, the assemblies are a display and a keypad of the apparatus 800. The sensor assembly 814 may also detect a change in position of the apparatus 800 or an assembly of the apparatus 800, the presence or absence of contact between the user and the apparatus 800, orientation or acceleration/deceleration of the apparatus 800, and temperature variation of the apparatus 800. The sensor assembly 814 may include a proximity sensor configured to detect presence of nearby objects in the absence of any physical contact. The sensor assembly 814 may also include a light sensor, for example, a complementary metal oxide semiconductor (CMOS) or a charge-coupled device (CCD) image sensor, for use in imaging applications. In some examples, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication assembly 816 is configured to facilitate communications between the apparatus 800 and other device in a wired or wireless mode. The apparatus 800 may access a wireless network based on a communication standard, for example, Wi-Fi, 2G, or 3G, or their combination. In an example, the communication assembly 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an example, the communication assembly 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on a radio frequency identification (RFID) technology, an infrared data association (IrDA) technology, an ultra wide band (UWB) technology, a Bluetooth® (BT) technology, and other technologies.
In an example, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), controllers, microcontrollers, microprocessors, or other electronic elements, and is configured to execute the method for processing radio-link failure applied to the user equipment side.
In the example, further provided is a non-transitory computer-readable storage medium including an executable instruction, for example, a memory 804 including an executable instruction, and the executable instruction may be executed by the processor 820 of the apparatus 800 so as to execute the method above. For example, the non-transitory computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage apparatus, etc.
The apparatus 900 may further include a power supply assembly 926 configured to implement power supply management of the apparatus 900, a wired or radio network interface 950 configured to connect the apparatus 900 to a network, and an input/output (I/O) interface 958. The apparatus 900 may operate an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.
The technical solutions described in the examples of the present disclosure may be combined at will without conflict.
Other examples of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practical disclosure. The present application is intended to cover any variations, uses, or adaptations of the present disclosure, and these variations, uses, or adaptations follow general principles of the present disclosure and include common general knowledge or customary technical means in the technical field not disclosed in the present disclosure. The specification and examples are considered as illustrative merely, and a true scope and spirit of the present disclosure are indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise structure that has been described above and shown in the accompanying drawings, and that various modifications and changes may be made without departing from its scope. The scope of the present disclosure is limited only by the appended claims.
Additional non-limiting examples of the disclosure include the following.
According to a first aspect of examples of the present disclosure, provided is a method for processing radio-link failure, performed by user equipment (UE), The method includes:
In the above solution, the inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
In the above solution, reporting failure information including the reason for the link failure includes:
In the above solution, reporting the failure information including the reason for the link failure after the RRC connection is recovered includes:
In the above solution, the failure information further includes: timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
According to a second aspect of examples of the present disclosure, provided is a method for processing radio-link failure, performed by base station, The method includes:
In the above solution, the inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
In the above solution, before receiving failure information including the reason for a link failure reported by the UE, the method further includes:
In the above solution, the failure information further includes timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
In the above solution, the method further includes:
According to a third aspect of examples of the present disclosure, provided is an apparatus for processing radio-link failure. The apparatus includes:
In the above solution, the inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
In the above solution, the communication unit is configured to:
In the above solution, the communication unit is configured to:
In the above solution, the failure information further includes: timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
According to a fourth aspect of examples of the present disclosure, provided is an apparatus for processing radio-link failure. The apparatus includes:
In the above solution, the inactivity timer includes: a data inactivity timer and/or a sidelink inactivity timer.
In the above solution, the reception unit is configured to receive a prompt message indicating the UE has failure information sent from the UE; and
In the above solution, the failure information further includes timing duration information of the inactivity timer.
In the above solution, the failure information further includes a serving cell identifier of a serving cell connected with the UE before the RRC connection is released, position information of the UE, a cell radio network temporary identifier (C-RNTI) provided by the serving cell for the UE, and a target cell identifier for handover.
In the above solution, the apparatus further includes:
According to a fifth aspect of examples of the present disclosure, provided is an apparatus for processing radio-link failure. The apparatus includes:
According to a sixth aspect of examples of the present disclosure, provided is an apparatus for processing radio-link failure. The apparatus includes:
According to a seventh aspect of examples of the present disclosure, provided is a computer storage medium. The computer storage medium stores an executable instruction, and after the executable instruction is executed by a processor, any one of the aforementioned methods for processing radio-link failure applied to a UE-side technical solution.
According to an eighth aspect of examples of the present disclosure, provided is a computer storage medium. The computer storage medium stores an executable instruction, and after the executable instruction is executed by a processor, any one of the aforementioned methods for processing radio-link failure applied to a base station-side technical solution.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2019/121035 | 11/26/2019 | WO |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2021/102699 | 6/3/2021 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 9730090 | Johansson | Aug 2017 | B2 |
| 10225756 | Reider | Mar 2019 | B2 |
| 20160345351 | Bhattacharjee | Nov 2016 | A1 |
| 20170048898 | Jung | Feb 2017 | A1 |
| 20170265242 | Yang | Sep 2017 | A1 |
| 20200351731 | Kim | Nov 2020 | A1 |
| 20210051539 | Zhang | Feb 2021 | A1 |
| 20210368372 | Chen | Nov 2021 | A1 |
| 20220150730 | Freda | May 2022 | A1 |
| 20220361275 | Da Silva | Nov 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 105265004 | Jan 2016 | CN |
| 107484260 | Dec 2017 | CN |
| 107645738 | Jan 2018 | CN |
| 108990138 | Dec 2018 | CN |
| 110022620 | Jul 2019 | CN |
| 2014007012 | Jan 2014 | WO |
| Entry |
|---|
| Ericsson, “RRC Connection Reestablishment Related Report after Radio Link Failure,” Tdoc R2-1906896, 3GPP TSG-RAN WG2#106 (May 13-17, 2019). |
| MediaTek Inc., “Report of Email Discussion [99#43][NB-IoT] RRC Connection Release,” R2-1710795 (Oct. 2017). |
| Number | Date | Country | |
|---|---|---|---|
| 20220418031 A1 | Dec 2022 | US |
