Method for enhanced radio link failure recovery

Abstract

The present disclosure relates to methods for enhanced radio link failure recovery. A user equipment (UE) can establish a radio resource control (RRC) connection with a first cell of a cellular network and transmit signaling including an indication of an enhanced radio link failure (RLF) recovery capability. The UE can receive one or more RRC messages including configuration information for RLF recovery on the first cell. The UE detects one or more RLFs corresponding to the first cell and further determines, via a connection reestablishment cell selection procedure, that the first cell is a suitable RLF recovery candidate cell. In response to the detection and determination, the UE can apply the configuration information for the first cell. The UE can then transmit signaling including a trigger indicating RLF recovery to the cellular network and reestablish the RRC connection with the cellular network using the configuration information.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communication, and more particularly, to apparatus, systems, and methods for enhanced radio link failure recovery. BACKGROUND

[0002] The use of wireless communication systems is rapidly increasing. In recent years, wireless devices such as smartphones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated, complex applications that utilize these functions. Additionally, there are numerous different wireless communication technologies and wireless communication standards. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with the WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., lxRTT, lxEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), BLUETOOTH TM , etc.

[0003] The introduction of an ever-increasing number of features and functions in wireless communication devices also creates an ongoing need for improvements in wireless communication, as well as improvements in wireless communication devices. To increase coverage and better serve the growing demand and range of expected uses of wireless communication, more wireless communication technologies are being developed in addition to the communication standards mentioned above.

[0004] The next telecommunication standard proposed beyond the current International Mobile Telecommunication-Advanced (IMT-Advanced) standard is referred to as the 5th Generation Mobile Networks or 5th Generation Wireless Systems, or simply 5G (for 5G New Radio, also referred to as 5G-NR, also simply NR). In comparison to the current LTE standard, 5G-NR proposes higher capacity for higher density of mobile broadband users, while supporting device-to-device, ultra-reliable, and massive machine communications, as well as lower latency and lower battery consumption. In addition, the 5G-NR standard can allow less restrictive UE scheduling in comparison to the current LTE standard. Therefore, efforts are being made to utilize the higher throughput possible at higher frequencies in the ongoing development of 5G-NR. Thus, there is a need for improvements in areas that support such development and design. SUMMARY

[0005] Embodiments relate to wireless communication, and more particularly, to apparatus, systems, and methods for enhanced radio link failure recovery.

[0006] A user equipment (UE) can establish a radio resource control (RRC) connection with a first cell of a cellular network and transmit signaling including an indication of an enhanced radio link failure (RLF) recovery capability. The UE can receive one or more RRC messages including configuration information for RLF recovery on the first cell. The UE detects one or more RLFs corresponding to the first cell and further determines, via a connection reestablishment cell selection procedure, that the first cell is a suitable RLF recovery candidate cell. In response to the detecting and determining, the UE can apply the configuration information for the first cell. The UE can then transmit signaling including a trigger indicating RLF recovery to the cellular network and reestablish the RRC connection with the cellular network using the configuration information.

[0007] In some embodiments, the first cell can include a primary cell (PCell) to which the UE was connected prior to the one or more RLFs and the one or more candidate cells can include one or more neighboring cells. Additionally or alternatively, the signaling including the trigger can further include at least one of a reason for the enhanced RLF recovery, an identifier of the configuration information applied, a cause of the RLF, information data about the RLF, and / or an RLF report, among various possibilities. According to some embodiments, the signaling including the trigger indicating the RLF recovery can be transmitted via medium access control (MAC) layer-2 (L2) signaling.

[0008] In some embodiments, upon successful reception of the trigger, user plane data transmission between the UE and at least one of the serving cell and the one or more candidate cells can be resumed. Additionally or alternatively, the configuration information can include one or more enhanced RLF recovery configurations associated with the serving cell. According to some embodiments, each of the one or more enhanced RLF recovery configurations can correspond to one or more different validity periods configured by the base station.

[0009] In some embodiments, the one or more candidate cells can include a primary cell (PCell) to which the UE had been connected prior to the one or more RLFs and can be further configured by the network as candidate CHO cells. Additionally or alternatively, the one or more candidate cells can be configured by the network as one or more candidate CHO cells. According to some embodiments, the UE or wireless device can be configured to indicate support for an enhanced radio link failure (RLF) recovery capability via non-access stratum (NAS) signaling. Additionally or alternatively, the signaling including the trigger indicating the RLF recovery can be transmitted via dedicated RRC signaling.

[0010] According to further embodiments, the CHO configuration information can include a conditional execution condition. Additionally or alternatively, the conditional execution condition can be configured by the base station in an abstract syntax notation 1 (ASN.1) field.

[0011] In some embodiments, a base station can configure one or more validity periods corresponding to configuration information, and the base station can be configured to dynamically enable or disable the enhanced RLF recovery capability of a UE. Additionally or alternatively, the base station can be configured to indicate whether the enhanced RLF capability is allowed via a system information broadcast (SIB) message.

[0012] The techniques described herein can be implemented in and / or used with a number of different types of devices, including but not limited to unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, cars and / or motor vehicles, and various other computing devices.

[0013] This Summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter as described herein. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following DETAILED DESCRIPTION, Figures, and Claims. BRIEF DESCRIPTION OF DRAWINGS

[0014] A better understanding of the present subject matter will be obtained through consideration of the following detailed description in conjunction with the drawings, in which:

[0015] Figure 1A An exemplary wireless communications system in accordance with some embodiments is shown.

[0016] Figure 1B An example of a base station (BS) and access point in communication with a user equipment (UE) device is shown in accordance with some embodiments.

[0017] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0018] Figure 3A An example block diagram of a BS is shown in accordance with some embodiments.

[0019] Figure 3B An example block diagram of a server is shown in accordance with some embodiments.

[0020] Figure 4 An exemplary block diagram of a UE is shown in accordance with some embodiments.

[0021] Figure 5An example block diagram showing cellular communication circuitry in accordance with some embodiments is shown.

[0022] Figure 6A An example showing connections between an EPC network, an LTE base station (eNB), and a 5G NR base station (gNB) is shown.

[0023] Figure 6B An example of protocol stacks for eNB and gNB is shown.

[0024] Figure 7 An example of a baseband processor architecture for a UE in accordance with some embodiments is shown.

[0025] Figure 8 An example of a typical connection re-establishment procedure in response to a radio link failure (RLF) in accordance with some embodiments is shown.

[0026] Figure 9 Is a high level flow diagram of an enhanced RLF recovery procedure in accordance with some embodiments.

[0027] Figure 10 An example flow diagram of an enhanced RLF recovery procedure using an enhanced RLF recovery radio resource control (RRC) reconfiguration message in accordance with some embodiments is shown.

[0028] Figure 11 An example flow diagram of an enhanced RLF recovery procedure by extending the existing framework for conditional handover (CHO) in accordance with some embodiments is shown.

[0029] While the features described herein can be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the disclosure to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter defined by the appended claims. DETAILED DESCRIPTION

[0030] Acronyms

[0031] Various acronyms are used throughout the present disclosure. Definitions of the most prominent acronyms used throughout the present disclosure can appear as follows:

[0032] • 3GPP: Third Generation Partnership Project

[0033] • TS: Technical Specification

[0034] • RAN: Radio Access Network

[0035] • RAT: Radio Access Technology

[0036] • UE: User Equipment

[0037] • RF: Radio Frequency

[0038] • BS: Base Station

[0039] • DL: Downlink

[0040] • UL: Uplink

[0041] • LTE: Long Term Evolution

[0042] • NR: New Radio

[0043] • 5GS: 5G System

[0044] • 5GMM: 5GS Mobility Management

[0045] • 5GC: 5G Core Network

[0046] • IE: Information Element

[0047] • ITS: Intelligent Transport Systems

[0048] • PCell: Primary Cell

[0049] • SCell: Secondary Cell

[0050] • RLF: Radio Link Failure

[0051] • RRC: Radio Resource Control

[0052] • L1: Layer 1

[0053] • L2: Layer 2

[0054] • MAC: Medium Access Control

[0055] • RLC: Radio Link Control

[0056] • HO: Handover

[0057] • CHO: Conditional Handover

[0058] • ASN.1: Abstract Syntax Notation One

[0059] • NW: Network

[0060] • NAS: Non-Access Stratum

[0061] • SIB: System Information Block

[0062] • PDCP: Packet Data Convergence Protocol

[0063] Terminology

[0064] The following is a glossary of terms used in the disclosure:

[0065] Memory medium— any of various types of memory devices or storage devices. The term "memory medium" is intended to include an installation medium, e.g., CD- ROM, floppy disks, or tapes, a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc., a non-volatile memory such as Flash, magnetic media, e.g., a hard disk drive, or optical storage. The memory medium can also include other types of storage medium or combinations thereof. Moreover, the memory medium can reside in a first computer system's main memory, or in a secondary storage device, e.g., a diskette, or in a computer system's memory, or in a different computer system which can be connected to the first computer system by a network. In the latter instance, the second computer system can provide program instructions for execution by the first computer system. The term "memory medium" can include two or more memory media which can reside in different places, e.g., in different computer systems that are connected to each other by a network. The memory medium can store program instructions that implement programs (e.g., programs that implement methods). The memory medium can also store data generated during the execution of programs.

[0066] Carrier medium— the memory medium described above, as well as a physical transmission medium, such as a bus, network, and / or other physical transmission medium which conveys signals such as electrical, electromagnetic, or digital signals.

[0067] Programmable hardware element— includes various hardware devices including multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Fiel d Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Fiel d Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks can range from fine grained (combinatorial logic elements or lookup tables) to coarse grained (arithmetic logic units or processor cores). Programmable hardware elements can also be referred to as "configurable logic devices".

[0068] Computer system (or computer)— any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0069] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM This includes laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transported by (or with) a user and is capable of wireless communication.

[0070] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0071] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0072] Channel - a medium used to convey information from a transmitter (sender) to a receiver (recipient). It is important to note that the characteristics of the term "channel" can differ depending on the different wireless protocols, and thus the term "channel" as used by the present application can be taken to be used in a manner consistent with the standards of the type of device to which the term usage is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel can be 22 MHz wide, while a Bluetooth channel can be 1 MHz wide. Other protocols and standards can include different definitions of a channel. Also, some standards can define and use multiple types of channels, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0073] Band - the term "band" has the full range of its ordinary meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0074] Wi-Fi - the term "Wi-Fi" has the full range of its ordinary meaning and includes at least a wireless communication network or RAT that is served by wireless LAN (WLAN) access points and provides connectivity to the Internet through those access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standards and marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks are different from cellular networks.

[0075] Automatic - refers to performance of an action or operation by a computer system (e.g., software executing on a computer system) or device (e.g., circuit, programmable hardware element, ASIC, etc.) without user input directly specifying or performing the action or operation. Thus the term "automatic" is in contrast to "manual," where the user directly specifies or performs each individual action or operation. Automatic processes can be initiated by input provided by the user, but the resulting actions are not specified by the user, e.g., in response to the user selecting an option on a graphical user interface of an application program. Such is termed "automatic" in that the action is not specified by the user, but rather initiated by the application program in response to, and as the direct result of, a user input. By contrast, a user would "manually" specify each action or operation that the computer system performs during execution of the application program. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is "manually" filling out the form if the application program requires the user to specify each action. In contrast, a user filling out an electronic form, where the computer system is automatically analyzing the form and filling in the form without any user input specifying answers to form fields (e.g., the computer system is "reading" the form and filling in the form without any user input) is "automatically" filling out the form. As indicated above, a user can invoke the automatic filling of a form, but not be involved in the actual filling of the form (e.g., the user can select a "fill out this form" option that causes the computer system to analyze the form and fill it in automatically without any further user input once the option has been selected).

[0076] Approximately - refers to a value that is close to or exact. For example, approximately can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold (or tolerance) can depend on the application. For example, in some embodiments, "approximately" can mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold can be, e.g., 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0077] Concurrent - refers to execution or performance in parallel, where tasks, processes or procedures are executed in at least partially overlapping fashion. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed in parallel (at least in part) on respective computing elements; or using "weak parallelism," where tasks are executed in interleaved fashion (e.g., via time-multiplexing of execution threads).

[0078] Various components can be described as being "configured to" perform one or more tasks. In such contexts, "configured to" is a broad recitation generally meant to encompass a wide variety of structural arrangements and functions. As such, a component can be configured to perform a task even when the component is not currently on or performing that task (e.g., a group of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" can be a broad recitation meant to encompass a wide variety of structural arrangements and functions. As such, a component can be configured to perform a task even when the component is not currently on or performing that task. Generally, the circuitry forming the structure corresponding to "configured to" can include hardware circuitry.

[0079] For ease of description, various components can be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." A component configured to perform one or more tasks is expressly intended to invoke 35 U.S.C. § 112(f) interpretation.

[0080] Figure 1A and Figure 1B : Communication system

[0081] Figure 1A A simplified exemplary wireless communication system according to some embodiments is shown. Note that Figure 1A The system of FIG. 1 is merely one example of a possible system, and features of the present disclosure can be implemented in any of various systems, as desired.

[0082] As shown, the exemplary wireless communication system includes a base station 102A that communicates over a transmission medium with one or more user devices 106A, 106B through 106N, etc. Each user device can be referred to herein as a "user equipment" (UE). Thus, the user devices 106 are referred to as UEs or UE devices.

[0083] The base station (BS) 102A can be a base transceiver station (BTS) or cell site ("cellular base station"), and can include hardware capable of facilitating wireless communication with the UEs 106A through 106N.

[0084] The communication area (or coverage area) of a base station can be referred to as a "cell." Base station 102A and UEs 106 can be configured to communicate

[0085] As shown, base station 102A can also be equipped to communicate with a network 100 (e.g., with a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and / or the Internet, among various possibilities). As such, base station 102A can facilitate communications between user devices and / or between user devices and the network 100. In particular, cellular base station 102A can provide UEs 106 with various

[0086] Base station 102A and other similar base stations (such as base stations 102B... N) operating according to the same or a different cellular communication standard can thus be provided as a network of cells that together provide continuous or nearly continuous overlap service to UEs 106A-N and similar devices via one or more cellular communication standards over a geographic area.

[0087] As such, while base station 102A can serve as a "serving cell" for UEs 106A-N as shown in FIG. 1, each UE 106 can also be capable of receiving signals from one or more other cells (that can be provided by base stations 102B-N and / or any other base station) that can be referred to as "neighboring cells." Such cells can also be capable of facilitating communication between user devices and / or between user devices and the network 100. Such cells can include "macro" cells, "micro" cells, "pico" cells, and / or any of various other sizes of cells that provide service areas of various granularity. For example, base stations 102A-B shown in FIG. 1 can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0088] In some embodiments, the base station 102A can be a next generation base station, e.g., a 5G New Radio (5G NR) base station or “gNB.” In some embodiments, a gNB can connect to a traditional evolved packet core (EPC) network and / or to a New Radio Communications Core (NRC) network. Further, a gNB cell can include one or more transmission and reception points (TRPs). Further, a UE capable of operating according to 5G NR can connect to one or more TRPs within one or more gNBs.

[0089] Note that the UE 106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, e.g., WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., lxRTT, lxEV-DO, HRPD, eHRPD), etc.), the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0090] Figure 1B A user equipment 106 (e.g., one of devices 106A-106N) in communication with base stations 102 and access points 112 is shown in accordance with some embodiments. The UE 106 can be a device with cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, a handheld device, a computer or tablet, or almost any type of wireless device.

[0091] The UE 106 can include a processor configured to execute program instructions stored in memory. The UE 106 can perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 can include programmable hardware elements, such as a field programmable gate array (FPGA) configured to execute any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0092] The UE 106 can include one or more antennas to communicate using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 can be configured to communicate using, for example, CDMA2000 (lxRTT / lxEV-DO / HRPD / eHRPD), LTE / High-EUTRA, or 5G NR using a single shared radio and / or GSM, LTE, High-EUTRA, or 5G NR using a single shared radio. The shared radio can be coupled to a single antenna, or can be coupled to multiple antennas (e.g., for MIMO) for performing wireless communication. Generally, a radio can include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio can implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 can share one or more portions of receive and / or transmit chains between multiple wireless communication technologies such as those discussed above.

[0093] In some embodiments, the UE 106 can include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 can include one or more radios that are shared between multiple wireless communication protocols, as well as one or more radios that are used exclusively by a single wireless communication protocol. For example, the UE 106 can include a shared radio for communicating using either of LTE or 5G NR (or either of LTE or lxRTT, or either of LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0094] Figure 2 Access point block diagram

[0095] Figure 2 An exemplary block diagram of an access point (AP) 112 is shown. Note that Figure 2 The block diagram of the AP is merely one example of a possible system. As shown, the AP 112 can include a processor 204 that can execute program instructions for the AP 112. The processor 204 can also be (directly or indirectly) coupled to memory management unit (MMU) 240, or other circuitry or devices, that can be configured to receive addresses from the processor 204 and translate those addresses to locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0096] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 270 (or additional network ports) may be configured to couple to a local network, such as a home network or a corporate network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks such as the Internet.

[0097] AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with UE 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in the case of a small cell where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, LTE, LTE-A Advanced, GSM, WCDMA, CDMA2000, etc.

[0098] In some implementations, as further described below, AP 112 can be configured to perform overhead reduction methods for multicarrier beam selection and power control as further described herein.

[0099] Figure 3A Block diagram of a base station

[0100] Figure 3A An example block diagram of a base station 102 according to some implementation schemes is shown. It should be noted that... Figure 3A The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include processor 304, which executes program instructions for base station 102. Processor 304 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 304 and translate these addresses into locations in memory (e.g., memory 360 and read-only memory (ROM) 350), or into other circuitry or devices.

[0101] Base station 102 may include at least one network port 370. Network port 370 may be configured to be coupled to a telephone network and provide access to the telephone network to multiple devices (e.g., UE device 106), as shown above in Figure 1 and... Figure 2as described in the middle.

[0102] The network port 370 (or an additional network port) can also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network can provide mobility related services and / or other services to a plurality of devices, such as the UE devices 106. In some cases, the network port 370 can couple to a telephone network via the core network, and / or the core network can provide a telephone network (e.g., between other UE devices served by the cellular service provider).

[0103] In some embodiments, the base station 102 can be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB.” In such embodiments, the base station 102 can connect to a traditional evolved packet core (EPC) network and / or to a NR core (NRC) network. Further, the base station 102 can be considered a 5G NR cell and can include one or more transition and reception points (TRPs). Moreover, a UE capable of operating according to 5G NR can connect to one or more TRPs within one or more gNBs.

[0104] The base station 102 can include at least one antenna 334, and possibly a plurality of antennas. The at least one antenna 334 can be configured to operate as a wireless transceiver and can be further configured to communicate with UE devices 106 via the radio 330. The antenna 334 is in communication with the radio 330 through a communication link 332. The communication link 332 can be a receive chain, a transmit chain, or both. The radio 330 can be configured to communicate via a variety of wireless communication standards including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0105] The base station 102 can be configured to communicate wirelessly using multiple wireless communication standards. In some cases, the base station 102 can include multiple radios that can enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 can include an LTE radio for performing communications according to LTE and a 5G NR radio for performing communications according to 5G NR. In this case, the base station 102 can be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 can include a multi-mode radio capable of performing communications according to any of a plurality of wireless communication technologies, e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.

[0106] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. Processor 304 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 304 may be configured as a programmable hardware element, such as a FPGA (Field-Programmable Gate Array), or an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Optionally (or additionally), processor 304 of BS 102, together with one or more other components 330, 332, 334, 340, 350, 360, 370, may be configured to implement or support some or all of the features described herein.

[0107] Furthermore, as described herein, processor 304 may include one or more processing elements. In other words, one or more processing elements may be included in processor 304. Therefore, processor 304 may include one or more integrated circuits (ICs) configured to perform the functions of processor 304. In addition, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 304.

[0108] Furthermore, as described herein, radio component 330 may include one or more processing elements. In other words, radio component 330 may include one or more processing elements. Therefore, radio component 330 may include one or more integrated circuits (ICs) configured to perform the functions of radio component 330. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio component 330.

[0109] Figure 3B Server block diagram

[0110] Figure 3B An example block diagram of server 104 according to some implementation schemes is shown. Note that... Figure 3B The server described is merely one example of a possible server. As shown, server 104 may include processor 344 capable of executing program instructions specific to server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuitry or devices.

[0111] Server 104 can be configured to provide network access functionality to multiple devices, such as base station 102, UE device 106, and / or UTM 108, for example, as further described herein.

[0112] In some embodiments, the server 104 can be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some embodiments, the server 104 can be connected to a traditional Evolved Packet Core (EPC) network and / or to an NR Core (NRC) network.

[0113] As further described later herein, the server 104 can include hardware and software components for implementing or supporting implementation of the features described herein. The processor 344 of the server 104 can be configured to implement or support implementation of some or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 can be configured as a programmable hardware element(s), such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or some combination thereof. Alternatively (or additionally) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and / or 374 can be configured to implement or support implementation of some or all of the features described herein.

[0114] Further, as described herein, the processor 344 can be composed of one or more processing elements. In other words, one or more processing elements can be included in the processor 344. Thus, the processor 344 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 344. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the processor 344.

[0115] Figure 4 Block diagram of a UE

[0116] Figure 4 An exemplary simplified block diagram of the communication device 106 is shown in accordance with some embodiments. Note that Figure 4The block diagram of the communication device is merely one example of a possible communication device. The communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or combinations of devices, among other devices, in accordance with embodiments. As shown, the communication device 106 can include a set of components 400 configured to perform core functions. The set of components can be implemented as, for example, a system on a chip (SoC), which can include portions for various purposes. Alternatively, the set of components 400 can be implemented to be separate components or groups of components for various purposes. This set of components 400 can be coupled (e.g., communicatively; directly or indirectly) to various other circuitry of the communication device 106.

[0117] For example, the communication device 106 can include various types of memory, such as NAND flash 410, input / output interfaces such as connector I / F 420 (e.g., for connecting to a computer system; a dock; a charging station; an input device, such as a microphone, camera, keyboard; an output device, such as a speaker; and the like), a display 460 that can be integrated with or external to the communication device 106, and cellular communication circuitry 430, such as for 5G NR, LTE, GSM, and the like, and short-to-medium range wireless communication circuitry 429 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 can include wired communication circuitry (not shown), such as, for example, an Ethernet network interface card.

[0118] The cellular communication circuitry 430 can be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as the antennas 435 and 436 shown. The short-to-medium range wireless communication circuitry 429 can also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as the antennas 437 and 438 shown. Alternatively, the short-to-medium range wireless communication circuitry 429 can be (e.g., communicatively; directly or indirectly) coupled to the antennas 435 and 436 in addition to, or instead of, being coupled to the antennas 437 and 438. The short-to-medium range wireless communication circuitry 429 and / or the cellular communication circuitry 430 can include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input-multiple-output (MIMO) configuration.

[0119] In some embodiments, cellular communication circuitry 430 can include a dedicated receive chain for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) a dedicated processor and / or radio) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR), as further described below. Further, in some embodiments, cellular communication circuitry 430 can include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain as well as a transmit chain shared with additional radio components, such as a second radio component that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain as well as the shared transmit chain.

[0120] Communication device 106 can also include and / or be configured for use with one or more user interface elements. User interface elements can include any of a variety of elements such as a display 460 (which can be a touch screen display), a keyboard (which can be a discrete keyboard or can be implemented as part of a touch screen display), a mouse, a microphone, and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0121] The communication devices 106 can also include one or more smart cards 445 having SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (Universal Integrated Circuit Card) 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 can include at least two SIMs. Each SIM can execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM can be a single smart card that can be embedded, e.g., soldered onto a circuit board in the UE 106, or each SIM can be implemented as a removable smart card. Thus, a SIM can be one or more removable smart cards, such as a UICC card sometimes referred to as a “SIM card,” and / or a SIM 410 can be one or more embedded cards, such as an embedded UICC (eUICC) sometimes referred to as an “eSIM” or “eSIM card.” In some embodiments, such as when a SIM includes an eUICC, one or more of the SIMs can implement embedded SIM (eSIM) functionality; in such embodiments, a single one of the SIMs can execute multiple SIM applications. Each SIM can include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality can be stored in the memory and executed by the processor. In some embodiments, the UE 106 can include a combination of removable and fixed / non-removable smart cards, such as one or more eUICC cards implementing eSIM functionality, as needed. For example, the UE 106 can include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also contemplated.

[0122] As described above, in some embodiments, the UE 106 can include two or more SIMs. Including two or more SIMs in the UE 106 can allow the UE 106 to support two different phone numbers, and can allow the UE 106 to communicate on two or more corresponding respective networks. For example, a first SIM can support a first RAT, such as LTE, while a second SIM supports a second RAT, such as 5G NR. Of course, other implementations and RATs are possible. In some embodiments, when the UE 106 includes two SIMs, the UE 106 can support dual- card dual-active (DSDA) functionality. DSDA functionality can allow the UE 106 to simultaneously connect to two networks (and use two different RATs), or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. DSDA functionality can also allow the UE 106 to simultaneously receive a voice call or data traffic on either phone number. In certain embodiments, the voice call can be a packet-switched communication. In other words, the voice call can be received using Voice over LTE (VoLTE) technology and / or Voice over NR (VoNR) technology. In some embodiments, the UE 106 can support dual-card dual- standby (DSDS) functionality. DSDS functionality can allow either of the two SIMs in the UE 106 to standby for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, the DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that executes multiple SIM applications for different carriers and / or RATs.

[0123] As shown, the SOC 400 can include a processor 402 that can execute program instructions for the communication device 106 and a display circuit 404 that can perform graphics processing and provide a display signal to the display 460. The processor 402 can also be coupled to a memory management unit (MMU) 440 that can be configured to receive addresses from the processor 402 and translate those addresses to locations in memory (e.g., a memory 406, a read-only memory (ROM) 450, a NAND flash memory 410) and / or to other circuits or devices, such as the display circuit 404, the short-to-medium range wireless communication circuit 429, the cellular communication circuit 430, the connector I / F 420, and / or the display 460. The MMU 440 can be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 can be included as a part of the processor 402.

[0124] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 can be configured to perform methods for beam failure recovery based on a unified TCI framework (e.g., in 5G NR systems and beyond), as described further herein.

[0125] As described herein, the communication device 106 can include hardware and software components for implementing the above-described features of the communication device 106 to transmit scheduling profiles for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 402 of the communication device 106 can be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 402 can be configured as programmable hardware elements, such as an FPGA (field programmable gate array) or ASIC (application-specific integrated circuit). Alternatively (or in addition) in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, the processor 402 of the communication device 106 can be configured to implement part or all of the features described herein.

[0126] Further, as described herein, the processor 402 can include one or more processing elements. Thus, the processor 402 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 402. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the processor 402.

[0127] Further, as described herein, the cellular communication circuitry 430 and the short- to medium-range wireless communication circuitry 429 can each include one or more processing elements. In other words, one or more processing elements can be included in the cellular communication circuitry 430 and, similarly, one or more processing elements can be included in the short- to medium-range wireless communication circuitry 429. Thus, the cellular communication circuitry 430 can include one or more integrated circuits (ICs) that are configured to perform the functions of the cellular communication circuitry 430. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the cellular communication circuitry 430. Similarly, the short- to medium-range wireless communication circuitry 429 can include one or more ICs that are configured to perform the functions of the short- to medium-range wireless communication circuitry 429. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the short- to medium-range wireless communication circuitry 429.

[0128] Figure 5 Block diagram of cellular communication circuitry

[0129] Figure 5 An example simplified block diagram of a cellular communication circuit is shown in accordance with some embodiments. Note that Figure 5 The block diagram of the cellular communication circuit of FIG. 5 is merely one example of one possible cellular communication circuit. The cellular communication circuit 530, which can be the cellular communication circuit 430, can be included in a communication device, such as the communication device 106 described above, in accordance with embodiments. As described above, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop or computing device, a mobile computing device (e.g., laptop, notebook, or portable computing device), a tablet, and / or combinations of devices, among other devices.

[0130] The cellular communication circuit 530 can be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as the antennas 435a-435b and 436 shown in FIG. 5. Figure 4 In some embodiments, the cellular communication circuit 530 can include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as shown in FIG. 5, the cellular communication circuit 530 can include a modem 510 and a modem 520. The modem 510 can be configured for communication in accordance with a first RAT, such as LTE or LTE-A, and the modem 520 can be configured for communication in accordance with a second RAT, such as 5G NR. Figure 5

[0131] As shown, the modem 510 can include one or more processors 512 and a memory 516 in communication with the processors 512. The modem 510 can be in communication with a radio frequency (RF) front end 530. The RF front end 530 can include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 can include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 can be in communication with a downlink (DL) front end 550, which can include circuitry for receiving radio signals via the antenna 335a.

[0132] Similarly, the modem 520 can include one or more processors 522 and a memory 526 in communication with the processors 522. The modem 520 can be in communication with an RF front end 540. The RF front end 540 can include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 can include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 can be in communication with a DL front end 560, which can include circuitry for receiving radio signals via the antenna 335b.​

[0133] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. In addition, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported via the modem 510), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported via the modem 520), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0134] In some embodiments, the cellular communication circuitry 530 can be configured to perform a method of beam failure recovery based on a unified TCI framework (e.g., in 5G NR systems and beyond), as further described herein.

[0135] As described herein, the modem 510 can include hardware and software components for implementing the features described above or for time-division multiplexing UL data for NSA NR operation and various other techniques described herein. For example, the processor 512 can be configured to implement part or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 512 can be configured as a programmable hardware element(s) such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512 can be configured, together with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, to implement some or all of the features described herein.

[0136] In addition, as described herein, the processor 512 can include one or more processing elements. Thus, the processor 512 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 512. In addition, each integrated circuit can include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor 512.

[0137] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0138] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0139] Figure 6A and Figure 6B 5G NR architecture with LTE

[0140] In some specific implementations, fifth-generation (5G) wireless communication will initially be deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been designated as part of the initial NR deployment. Therefore, as... Figure 6A to Figure 6B As shown, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). Furthermore, eNB 602 can communicate with the 5G NR base station (e.g., gNB 604) and can transfer data between the core network 600 and gNB 604. Therefore, the EPC network 600 can be used (or reused), and gNB 604 can serve as additional capacity for user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Therefore, LTE can be used to establish connections to the network, and NR can be used for data services.

[0141] Figure 6BThe proposed protocol stacks for eNB 602 and gNB 604 are shown. As shown, eNB 602 can include a medium access control (MAC) layer 632 that interfaces with radio link control (RLC) layers 622a-622b. RLC layer 622a can also interface with a packet data convergence protocol (PDCP) layer 612a, and RLC layer 622b can interface with PDCP layer 612b. Similar to dual connectivity specified in LTE-Advanced Release 12, PDCP layer 612a can interface with EPC network 600 via a master cell group (MCG) bearer, and PDCP layer 612b can interface with EPC network 600 via a split bearer.

[0142] In addition, as shown, gNB 604 can include a MAC layer 634 that interfaces with RLC layers 624a-624b. RLC layer 624a can interface with PDCP layer 612b of eNB 602 via an X2 interface for information exchange and / or coordination (e.g., scheduling UEs) between eNB 602 and gNB 604. Further, RLC layer 624b can interface with PDCP layer 614. Similar to dual connectivity specified in LTE-Advanced Release 12, PDCP layer 614 can interface with EPC network 600 via a secondary cell group (SCG) bearer. Thus, eNB 602 can be considered a master node (MeNB), and gNB 604 can be considered a secondary node (SgNB). In some cases, a UE can be required to maintain connectivity with both the MeNB and the SgNB. In such scenarios, the MeNB can be used to maintain a radio resource control (RRC) connection with the EPC, and the SgNB can be used for capacity (e.g., additional downlink and / or uplink throughput).

[0143] Figure 7 UE baseband processor architecture

[0144] Figure 7 An example of a baseband processor architecture for a UE (e.g., such as UE 106) is shown, in accordance with some embodiments. Figure 7The baseband processor architecture 700 described in the middle can be implemented on one or more radios (e.g., the radio 329 and / or the radio 330 described above) or modems (e.g., the modem 510 and / or the modem 520) as described above. As shown, the non-access stratum (NAS) 710 can include a 5G NAS 720 and a legacy NAS 750. The legacy NAS 750 can include a communication connection with a legacy access stratum (AS) 770. The 5G NAS 720 can include a communication connection with a 5G AS 740 and a non-3GPP AS 730 as well as a Wi-Fi AS 732. The 5G NAS 720 can include functional entities associated with two access strata. Thus, the 5G NAS 720 can include multiple 5G MM entities 726 and 728 as well as 5G session management (SM) entities 722 and 724. The legacy NAS 750 can include functional entities such as a short message service (SMS) entity 752, an evolved packet system (EPS) session management (ESM) entity 754, a session management (SM) entity 756, an EPS mobility management (EMM) entity 758, and a mobility management (MM) / GPRS mobility management (GMM) entity 760. Further, the legacy AS 770 can include functional entities such as an LTE AS 772, a UMTS AS 774, and / or a GSM / GPRS AS 776.

[0145] Thus, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, the 5G MM can maintain separate connection management and registration management state machines for each connection. Additionally, a device (e.g., the UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular access as well as non-cellular access. Further, the device can be in a connected state in one access and an idle state in the other access, or vice versa. Finally, there can be common 5G-MM procedures (e.g., registration, de-registration, identity, authentication, etc.) for both accesses.

[0146] Note that, in various embodiments, one or more of the above-described functional entities of the 5G NAS and / or 5G AS can be configured to perform the overhead reduction methods for multi-carrier beam selection and power control, e.g., as further described herein.

[0147] Figure 8 Connection re-establishment procedure in response to radio link failure

[0148] In the case where a user equipment (UE) has established a connection with a network (e.g., a base station or an evolved node-B (eNB) / next generation node-B (gNB)), the UE can be considered to be in a radio resource control (RRC) connected mode. However, if the UE experiences a radio link failure (RLF), the UE can perform a connection reestablishment procedure. More specifically, if a suitable cell is found during connection reestablishment cell selection, the UE can exchange a sequence of over-the-air messages with the cellular network to resume the connection. For example, Figure 8 A connection reestablishment procedure in response to a radio link failure (RLF) is shown in accordance with some embodiments.

[0149] A UE can experience an RLF due to various physical layer issues, expiration of one or more timers (e.g., a T310 timer), or if the UE has reached a maximum number of random access reconnection attempts. More specifically, some UEs can experience a radio link failure due to the UE can enter a temporary out-of-coverage situation of an area with minimal cellular coverage. Thus, the minimal cellular coverage (e.g., minimal carrier signal strength) can cause a loss of a primary serving cell “Pcell” during this time. For example, in addition to other examples, some UEs can experience such a loss of a Pcell due to entering an elevator, entering a house basement, or entering a tunnel. During this connection reestablishment period, UE user plane data transmission with the network can be suspended.

[0150] Once the temporary out-of-coverage situation has been resolved (e.g., the user and / or UE has exited the house basement, elevator, or tunnel), the UE can attempt to reconnect to the network. During the connection reestablishment cell selection procedure, the UE can reselect the same primary serving cell “Pcell” that it was previously using or camped on prior to experiencing the RLF. However, the UE can also have to perform an appropriate connection reestablishment procedure, which can unnecessarily consume time.

[0151] For example, as Figure 8As shown, the cellular device 802 (e.g., UE) can establish a connection with a first serving cell (e.g., a primary cell (PCell)) corresponding to the cellular network 804. Thus, the UE can be considered to be in an RRC connected state 806 and can further experience or detect a radio link failure (RLF) 808 corresponding to the issues discussed above. In 810, the UE can attempt to initiate a connection reestablishment with the network and further release some connected mode configurations (e.g., release secondary cells (scells)). Further, after the UE has performed cell selection in 812, the UE can prepare to transmit a reestablishment request to the network by applying layer-1 (L1) and medium access control (MAC) default configurations in 814. Thus, the UE and the network can exchange RRC messages such as RRC reestablishment request 816 messages, RRC reestablishment 818 messages, RRC reestablishment complete 820 messages, RRC reconfiguration 822 messages, and RRC reconfiguration complete 824 messages as part of corresponding operations as defined in the appropriate 3GPP specifications and standards.

[0152] Additionally, the RRC reconfiguration over-the-air message can provide and / or include full or partial PCell and Scell configurations. Further, radio link control (RLC) and packet data convergence protocol (PDCP) radio bearer reestablishment can be required to complete the connection reestablishment procedure. In New Radio (NR), these operations can take up to 29 ms. For example, operations involving the UE releasing its configuration and applying default configurations can take up to 3 ms, RRC processing delay requirements for the RRC reestablishment complete 820 message can take up to 10 ms, and RRC processing delay requirements for the RRC reconfiguration complete 824 message can take up to 16 ms, for a total of approximately 29 ms.

[0153] In Long Term Evolution (LTE), these operations can take up to 38 ms. For example, operations involving the UE releasing its configuration and applying default configurations can take up to 3 ms, RRC processing delay requirements for the RRC reestablishment complete 820 message can take up to 15 ms, and RRC processing delay requirements for the RRC reconfiguration complete 824 message can take up to 20 ms, for a total of approximately 38 ms. Thus, by performing operations similar to those discussed above, the UE can experience unnecessary time in which UE user plane data transmission with the network can be suspended.

[0154] Method for enhanced radio link failure recovery

[0155] Embodiments described herein provide mechanisms for enhanced radio link failure recovery. For example, some embodiments can involve a UE performing a connection reestablishment cell selection procedure in which the UE selects the same primary serving cell "Pcell" to which it was connected or camped prior to detecting or experiencing an RLF. Further, as an alternative to re-executing the connection reestablishment procedure described above, the UE can stop the connection reestablishment procedure and send a special trigger to the network. According to some embodiments, the trigger can be an RRC dedicated signaling over-the-air message or a layer-2 (L2) medium access control (MAC) layer signaling. Additionally or alternatively, once the network successfully receives the special trigger and causes a successful random access procedure, the connection can be considered to be reestablished. Thus, the suspension of user plane data transmission that occurs upon experiencing an RLF and losing Pcell connection can be immediately resumed with the enhanced RLF recovery special trigger received at the network. In other words, it can be possible to resume user plane data transmission at some point within the random access procedure corresponding to the UE applying layer-1 (LI) and medium access control (MAC) default configurations in 814. Thus, the UE can be able to reestablish its user plane data transmission with the network without experiencing the 29 ms delay and 38 ms delay associated with the full connection reestablishment procedure associated with 814-824 in Figure 8 Figure 8

[0156] Figure 9 - Enhanced RLF recovery procedure

[0157] Figure 9 A high level flow diagram illustrating an enhanced RLF recovery procedure according to some embodiments is shown.

[0158] Figure 9 ​​Aspects of the method of FIG. 10 can be implemented by a wireless device such as one or more UEs 106 communicating with one or more base stations (e.g., BS 102) as shown in the figures and as described in relation to the figures, or more generally in relation to any of the computer systems or devices shown in the figures and other circuitry, systems, devices, elements, or components shown in the figures and other devices as desired. For example, one or more processors (or processing elements) of a UE (e.g., one or more processors 402, one or more baseband processors, one or more processors associated with communication circuitry, etc.) can cause the UE to perform some or all of the illustrated method elements. Note that while at least some elements of the method are described using terminology associated with communication techniques and / or features associated with 3GPP specification documents, such description is not intended to limit the present disclosure and aspects of the method can be used in any suitable wireless communication system as desired. In various embodiments, some of the illustrated method elements can be performed simultaneously, in a different order than illustrated, can be omitted, or can be substituted for other method elements as desired. Additional method elements can also be performed as desired. As shown, the method can operate as follows.

[0159] For example, as shown, according to some embodiments, a cellular device 902 (e.g., a UE) can establish a connection with a cellular network cell (e.g., a first cell or PCell) 904 such that the UE is considered to be in an RRC connected state 906. Figure 9

[0160] At 908, the UE 902 can indicate its capabilities with respect to enhanced RLF recovery to the network 904. For example, according to some embodiments, the UE can transmit a radio resource control (RRC) message to the network indicating support for its enhanced RLF recovery feature. In some embodiments, the UE can indicate support for this feature to the network through UE capability information (e.g., through non-access stratum (NAS) or RRC layer UE capability dedicated signaling over-the-air messages).

[0161] ​At 910, the network can enable, through secure dedicated signaling (e.g., over-the-air download RRC message), an enhanced RLF recovery feature in which a connection mode configuration can be applied after RLF recovery on the Pcell (e.g., first cell). Additionally or alternatively, the network can determine how the application scope of the connection mode configuration (e.g., common or dedicated) prior to RLF, such that the UE can re-use the configuration after RLF recovery. Thus, user plane data transmission can be resumed immediately (e.g., at least on the Pcell / first cell) whether a partial set of the configuration has been applied (e.g., the network can send another RRC reconfiguration over-the-air download message after RLF recovery) or the entire set of the configuration has been applied. According to some embodiments, the network can dynamically enable and disable this enhanced RLF recovery feature in the UE within the RRC connection through dedicated signaling over-the-air messages (e.g., RRC dedicated signaling over-the-air messages).

[0162] According to some embodiments in which the feature is enabled, the network can configure the UE with a validity period for the enhanced RLF recovery configuration. More specifically, the validity period for the enhanced RLF recovery configuration can correspond to a time period in which the UE considers the corresponding configuration to be a valid configuration. In other words, only if the validity period has not exceeded a threshold, the corresponding configuration can be effectively applied by the UE. According to some embodiments, the network can associate more than one enhanced RLF recovery configuration within the same Pcell, such that each configuration can correspond to a different and distinct validity period. According to some embodiments, the network cell can indicate whether this validity period feature is supported or not supported through a system information broadcast message parameter (e.g., SIB1 parameter).

[0163] In some embodiments, if the UE does not fully re-use the RRC connection mode configuration configured prior to RLF after RLF recovery, the network can configure the UE with a difference or delta of the configuration (e.g., partial configuration) such that the current Pcell configuration or the full (e.g., complete) connection mode configuration (common or dedicated) can be applied by the UE after enhanced RLF recovery.

[0164] At 912, the UE can detect a radio link failure (RLF) that can correspond to the UE having entered a temporary out-of-coverage situation with minimal cellular coverage. Thus, this can result in the loss of the primary serving cell "Pcell" at this time and prior to re-establishing a connection, possibly suspending UE user plane data transmission with the network.

[0165] At 914, the UE can initiate a connection reestablishment procedure by performing cell selection 916. More specifically, the UE can select a suitable cell (e.g., a cell in which the UE can obtain normal service) based on idle mode measurements and certain cell selection criteria. For example, the cell can be part of a selected or registered public land mobile network (PLMN), and the UE can scan radio frequency (RF) channels in an NR or LTE radio interface (e.g., evolved universal terrestrial radio access (E-UTRA)). According to some embodiments, the UE can only search for the strongest cell on each carrier frequency, and once a suitable cell is found, the UE can select this cell. In other words, the UE can determine, via a connection reestablishment cell selection procedure, that a first cell (e.g., a Pcell in which the UE was camped prior to the RLF) is a suitable RLF recovery candidate cell. According to some embodiments, the UE can then apply configuration information for the first cell in response to detecting one or more RLFs and determining that the first cell is a suitable RLF recovery candidate cell.

[0166] According to some embodiments, at 918, if the selected Pcell is the first cell that the UE was previously connected to or camped on, the UE can transmit a special trigger (e.g., via an RRC signaling over-the-air download message) to the network. Thus, upon successful reception of the special trigger at the network, user plane data transmission can be resumed and data can be exchanged between the network and the UE again. Additionally or alternatively, the connection reestablishment special trigger transmitted from the UE to the network can provide additional information to the network. For example, the trigger can include an indication that the reason for the transmission of the special trigger is related to the enhanced RLF recovery procedure. In some embodiments, in the case that more than one enhanced RLF recovery configuration is configured, the trigger can include an identifier for the applied enhanced RLF recovery configuration. Additionally or alternatively, the trigger can contain information about the RLF cause and any additional data (e.g., signal strength measurements) that can be associated with the RLF and / or any other information defined by 3GPP.

[0167] Accordingly, during connection reestablishment, if the selected cell is the previous Pcell that the UE was camped on prior to the RLF occurrence (which is typical in the temporary out-of-coverage case) and most of the RRC connected mode configuration has already been applied (and can be reused) prior to the RLF, the NR and LTE connection reestablishment operations can be reduced from 29ms and 38ms, respectively, to about 2ms, which can correspond to the time needed to initiate and transmit the enhanced RLF recovery trigger to the network. Moreover, this technique can be applied to different cellular technologies other than LTE and NR or any future cellular technology.

[0168] Figure 10- Methods of enhanced RLF recovery by utilizing enhanced RRC reconfiguration messages

[0169] Figure 10 An exemplary flow diagram of an enhanced RLF recovery procedure using enhanced radio resource control (RRC) reconfiguration messages is shown in accordance with some embodiments. More specifically, Figure 10 Methods are shown in which a network can configure a UE with one or more enhanced RLF recovery RRC reconfiguration encoded over-the-air messages associated with a candidate Pcell, such as a current Pcell (e.g., previously connected to and / or camped on) or other candidate Pcell (e.g., a neighboring cell) through a RRC reconfiguration procedure.

[0170] Figure 10 Aspects of the methods of FIG. 10 can be implemented by a wireless device such as UE 106, which communicates with one or more base stations (e.g., BS 102) as shown in the figures and as described with respect to the figures, or more generally, in conjunction with any of the computer systems or devices shown in the figures and other circuitry, systems, devices, elements, or components shown in the figures and other devices as desired. For example, one or more processors (or processing elements) of the UE (e.g., one or more processors 402, one or more baseband processors, one or more processors associated with communication circuitry, etc.) can cause the UE to perform some or all of the illustrated method elements. Note that while at least some elements of the method are described using terminology related to using communication techniques and / or features associated with 3GPP specification documents, such description is not intended to limit the present disclosure, and aspects of the method can be used in any suitable wireless communication system as desired. In various embodiments, some of the illustrated method elements can be performed concurrently, in different orders, or can be omitted, replaced, or supplemented with other method elements as desired. Additionally, method elements can be performed in any suitable order, as can be readily determined by those of skill in the art. As shown, the method can operate as follows.

[0171] Similar to 902 discussed above with respect to Figure 9 In 1002, a cellular device 1002 (e.g., a UE) can establish a connection with a cellular network cell (e.g., a PCell / first cell) 1004 such that the UE is considered to be in an RRC connected state 1006 in accordance with some embodiments.

[0172] In 1008, the network can transmit a query to the UE regarding the UE’s capabilities or support for the enhanced RLF recovery procedure. In other words, the network can request information from the UE if it encounters an RLF such that the network can assist the UE in performing the enhanced RLF recovery procedure if the UE indicates that it is capable.

[0173] In 1010, the UE can transmit a response to the network in response to receiving the query from the network in 1008, which can include information about the UE's capabilities or support for the enhanced RLF recovery procedure. More specifically, the UE can indicate support for this feature through the RRC UE Capability Information over-the-air message.

[0174] Further, an example code block for the UE's capability information in 1010 can correspond to:

[0175] SEQUENCE{

[0176] …

[0177] enhancedRlfRecovery-ReconfiogSupport

[0178] {supported}, optional Need N,

[0179] …

[0180] }

[0181] At 1012, the network can transmit one or more RRC reconfiguration messages to the UE in response to receiving the UE's capability information in order to assist or prepare the UE for an enhanced recovery procedure upon encountering an RLF. For example, one or more enhanced RLF recovery RRC reconfiguration messages transmitted from the network to the UE can include a difference or delta with respect to a current UE RRC connected mode common or dedicated configuration (e.g., partial configuration). Further, the network can determine the content of the enhanced RLF recovery RRC reconfiguration. For example, the network can need the UE to re-use a majority of the RRC connected mode configuration (e.g., common or dedicated) that was applied prior to the occurrence of the RLF. Thus, due to the re-use of the configuration and / or information elements (IE), such as the MobilityControlInformation IE in LTE or the ReconfigurationWithSync IE in NR, the message content can have minimal information. Further, the enhanced RLF recovery RRC reconfiguration message for the current Pcell can not need information about candidate enhanced RLF recovery Pcells, such as frequencies and physical cell identities. In other words, the UE can already know this information and thus including this information in the message can not be useful to the UE. Additionally or alternatively, the network can include other configurations up to a full connected mode configuration. In some embodiments, a normal (e.g., non-enhanced RLF recovery RRC reconfiguration message) RRC reconfiguration message can be received at any point in time during the RRC connected state. According to some embodiments, an exemplary code block for the RRC reconfiguration message can correspond to:

[0182] SEQUENCE{

[0183] …

[0184] enhancedRlfRecoveryAddModList::=SEQUENCE(SIZE(1..

[0185] maxenhancedRlfecoveryCells))OF

[0186] enhancedRlfRecoveryToAddMod

[0187] enhancedRlfRecoveryAddMod::=SEQUENCE{

[0188] enhancedRlfRecoveryId enhancedRlfRecoveryid.

[0189] enhancedRlfRecoveryReconfig OCTET

[0190] STRING(CONTAINING RRCReconfiguration)OPTIONAL,--Cond

[0191] validity enhancedRlfRecoveryValidityperiod

[0192] OPTIONAL,--Cond enhancedRlfRecoveryAdd

[0193] …

[0194] }

[0195] …

[0196] }

[0197] In 1014, the UE may transmit an RRC reconfiguration completion message upon successful completion of the random access procedure in response to receiving an RRC reconfiguration message from the network.

[0198] In 1016, the UE can detect a radio link failure (RLF) that may correspond to a temporary out-of-coverage situation where the UE has entered an area with minimal cellular coverage. Therefore, this may result in the loss of the primary serving cell "Pcell" at this time and before the connection is re-established, potentially suspending UE user plane data transmission with the network.

[0199] In version 1018, the UE can initiate the connection reconstruction process. However, compared to... Figure 8 Compared to the typical connection rebuild shown, the UE may not release the connection mode configuration (e.g., Scell) and proceed directly to a process that may involve something similar to... Figure 9 The process of selecting 1020 communities in the 916 process.

[0200] In 1022, if the cell selected for connection re-establishment is one of the candidate enhanced RLF recovery primary serving cells (e.g., the same Pcell that the UE was connected to or camped on prior to the RLF) the UE can stop the connection re-establishment procedure as indicated in 1024, apply the associated stored enhanced RLF recovery RRC reconfiguration message in 1026, and send the RRC reconfiguration complete message accordingly in 1028. Thus, at the point in time when the random access procedure has been successful and the RRC reconfiguration complete message has been sent to the network, the user plane data can be resumed. According to some embodiments, this procedure can be similar to an intra-RAT handover. In some embodiments, the random access configuration can be provided within the associated enhanced RLF recovery RRC reconfiguration message. Additionally or alternatively, if the random access configuration is not provided, the UE can use the random access configuration broadcasted in the selected Pcell system information block (SIB).

[0201] In some embodiments, the network can be able to dynamically enable and / or disable the enhanced RLF recovery feature through a new Abstract Syntax Notation One (ASN.1) field in a dedicated RRC reconfiguration over-the-air message (e.g., an “enhancedRlfReconveryReconfigAddList” ASN.1 field). Further, according to some embodiments, an entry in the list of candidate enhanced RLF recovery Pcells can include information such as an identifier (ID) for the enhanced RLF recovery configuration entry. Additionally or alternatively, an entry in the list of candidate enhanced RLF recovery Pcells can include an EnhancedRlfRecoveryReconfig, which can be an encoded RRC reconfiguration message, that can be applied if the cell selected for connection re-establishment is included in the message. In some embodiments, an entry in the list of candidate enhanced RLF recovery Pcells can include cell information such as a frequency and a physical cell ID that can be part of the message. For example, in NR, this cell information can be part of the ReconfigurationWithSync ASN.1 information element.

[0202] According to some embodiments, an entry in the list of candidate enhanced RLF recovery Pcells can include a validity period corresponding to a time period regarding configuration validity. More specifically, this validity period can be initiated or launched after the UE detects an RLF. If this period elapses or expires (e.g., exceeds a threshold), there can be different configuration options that can be configured by the network. For example, as one option, the UE can remove this configuration entry. Additionally or alternatively, the UE can apply certain and / or minimum configuration set defined by 3GPP specifications. For example, if the time elapsed since the UE detected the RLF is greater than the ValidityPeriod value but less than a certain threshold, the UE can release one or more corresponding Scells and apply specific and / or default values for other configurations. One advantage of this can be that user plane data transmission can be resumed immediately after sending the RRC reconfiguration complete message, instead of having to wait for receiving the next RRC reconfiguration message from the network (e.g., as in the case of normal connection reestablishment procedure).

[0203] According to some embodiments, the network can configure the UE with multiple entries for the same candidate enhanced RLF recovery Pcell with different validity periods and contents. This can be advantageous, for example, if a value less than a certain threshold exceeds the ValidityPeriod, the network can require the UE to apply a different configuration if the UE cannot apply the configuration. In other words, according to some embodiments, the UE can be able to apply a configuration with a smaller validity period first and subsequently apply a configuration with a larger validity period.

[0204] In some embodiments, if the enhanced RLF recovery feature is supported / allowed, the network can indicate whether the enhanced RLF recovery feature is supported / allowed through a system information broadcast message (e.g., SIB1 parameter). Further, in the RRC reconfiguration complete message sent by the UE to the network for enhanced RLF recovery, the UE can include information such as a reason or indication regarding performing the enhanced RLF recovery procedure. Additionally or alternatively, the UE can include information regarding the ID of the applied enhanced RLF recovery configuration, which can be needed if the UE is configured with more than one enhanced RLF recovery configuration for the same Pcell.

[0205] In some embodiments, the UE can include information of the cause of the RLF and any information or data about the RLF. Additionally or alternatively, the UE can include other information that can be defined by 3GPP specifications, such as the parameter ue-measurmentsAvailable and the parameter rlf-InfoAvailable. More specifically, the UE can indicate rlf-InfoAvailable in the RRC reconfiguration complete message. In response, the network can trigger a UEInformationRequest or UEInformationResponse to retrieve the RLF report that can include the cause of the RLF and / or other RLF related information. Once the network receives the RRC reconfiguration complete message, the connection can be considered to be re-established and the user plane data transmission can be resumed at a certain point within the random access procedure corresponding to the UE application layer-1 (LI) and medium access control (MAC) default configuration in 814. Thus, the UE is able to re-establish its user plane data transmission with the network without experiencing the 29 ms delay and 38 ms delay associated with the full connection re-establishment procedure associated with 814-824 in Figure 8 Figure 8

[0206] Figure 11 - Method for enhanced RLF recovery by extending the existing framework for conditional handover (CHO)

[0207] Figure 11 An exemplary flowchart of an enhanced RLF recovery procedure by extending the existing framework for conditional handover (CHO) is shown in accordance with some embodiments.

[0208] Figure 11 ​​Aspects of the method may be implemented by a wireless device such as UE 106, which communicates with one or more base stations (e.g., BS 102) as shown in the figures and as described with respect to the figures, or more generally, in conjunction with any of the computer systems or devices shown in the figures, as well as other circuits, systems, devices, elements or components and other devices shown in the figures, as needed. For example, one or more processors (or processing elements) of the UE (e.g., one or more processors 402, one or more baseband processors, one or more processors associated with communication circuitry, etc.) may cause the UE to perform some or all of the illustrated method elements. It should be noted that although at least some elements of the method have been described in a manner involving the use of communication technologies and / or features associated with 3GPP specification documents, this description is not intended to limit the disclosure, and aspects of the method may be used in any suitable wireless communication system as needed. In various embodiments, some elements of the illustrated method may be performed simultaneously in a different order than shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown, the method may operate as follows.

[0209] like Figure 11 The example shown is similar to the one discussed above regarding... Figure 9 According to some implementation schemes, cellular device 1102 (e.g., UE) can establish a connection with cellular network cell (e.g., PCell / first cell) 1104, such that the UE is considered to be in RRC connection state 1106.

[0210] In 1108, the network can transmit one or more RRC reconfiguration messages to the UE to assist or prepare the UE for an enhanced recovery procedure in the event of an RLF. According to some implementations, the network can configure the UE with a list of candidate CHO PCells, which the UE can use to trigger a CHO if certain configured conditions (e.g., conditional execution conditions) are met. Additionally or alternatively, the network can trigger CHO execution if the cell selected during the connection re-establishment cell selection procedure is one of the configured candidate CHO PCells. In some implementations, the conditional execution conditions can be configured by the `condExecutionCond ASN.1` field in the NR. However, this may not be applicable if the CHO candidate Pcell is the current Pcell, because meeting the conditional execution conditions as described above may not apply to the current Pcell. Therefore, fast re-camping via CHO execution on a previous Pcell may not be possible during the connection re-establishment procedure.

[0211] According to some embodiments, the conditional execution condition can correspond to a new event (e.g., event A2) that the signal quality of a feature similar to a serving cell becomes worse than a threshold. This new event can be utilized instead of considering the signal quality offset of a neighbor cell becomes better than the signal quality of the SpCell (e.g., event A3) and / or the signal quality of the SpCell becomes worse than a first threshold and the neighbor cell signal quality becomes better than a second threshold (e.g., event A5). Thus, satisfying certain conditional execution conditions such as these can result in triggering the RLF recovery procedure early.

[0212] Additionally or alternatively, the network can configure the current Pcell (e.g., the first cell to which the UE can be connected or camped) such that it is one of the conditional reconfiguration candidate Pcells. In other words, the current Pcell can also be configured by the network as a CHO candidate Pcell. In some embodiments, a normal (e.g., non-enhanced) RLF recovery RRC reconfiguration message can be received at any point in time during the RRC connected state. More specifically, an exemplary code block of the RRC reconfiguration message can correspond to:

[0213] SEQUENCE{

[0214] …

[0215] CondReconfigToAddMod-r16::= SEQUENCE{

[0216] condReconfigId-r16. CondReconfigId-r16,

[0217] condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Cond

[0218] condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, - Cond

[0219] …

[0220] }

[0221] According to some embodiments, the condReconfigAddPcell field can be needed when adding a conditional reconfiguration ID with respect to a master cell group (MCG) candidate Pcell other than the current Pcell or with respect to a secondary cell group (SCG) candidate Pscell. In some embodiments, M is needed if the condReconfigAddPcell segment is optional. Additionally or alternatively, the condReconfigAddPcell field can not be present if the MCG candidate Pcell is equivalent to the current Pcell.

[0222] In 1110, the UE can transmit an RRC reconfiguration complete message in response to receiving the RRC reconfiguration message from the network upon successful completion of the random access procedure.

[0223] In 1112, the UE can detect a radio link failure (RLF) that can correspond to the UE having entered a temporary out-of-coverage situation with minimal cellular coverage. As a result, this can cause the loss of the primary serving cell “Pcell” at this time and before the connection is reestablished, possibly suspending UE user plane data transmission with the network.

[0224] In 1114, the UE can initiate a connection reestablishment procedure. However, unlike a typical connection reestablishment as shown in Figure 8 the UE can not release the connected mode configuration (e.g., Scell) and proceed directly to cell selection 1116 that can involve a procedure similar to that from 916 of Figure 9

[0225] In 1118, if the connection reestablishment is initiated and the cell selected during the connection reestablishment is one of the configured candidate CHO Pcells, the UE can stop the connection reestablishment procedure in 1120 and apply the stored conditional reconfiguration message to the Pcell (e.g., the UE connects to the first cell). Similar to a typical CHO execution, this can initiate a CHO procedure on the selected Pcell. Thus, the corresponding CHO can utilize a normal intra-RAT handover procedure in which the applied RRC reconfiguration message is the one stored in the UE for the corresponding selected conditional reconfiguration candidate Pcell (e.g., the Pcell the UE was camping on or connected to prior to the RLF) previously configured by the network. In some embodiments, a UE with NR capability can initiate the CHO execution by applying the associated CHO RRC reconfiguration message set in the condReconfig ASN.1 field associated with the previous Pcell CHO conditional reconfiguration entry.

[0226] ​In 1124, having successfully performed the CHO, the UE can transmit an RRC reconfiguration complete message to the network. Additionally or alternatively, the UE can include in the RRC reconfiguration complete message to the network information about whether the enhanced RLF recovery procedure was successful or implemented, the cause of the RLF, and / or other information about the RLF or defined by 3GPP specifications (e.g., ue-measurmentsAvailable, rlf-InfoAvailable). In some embodiments and similar to other CHO RRC reconfiguration messages, the RRC reconfiguration message can include a mobility IE (e.g., MobilityControlInformation IE in LTE or reconfigurationWithSync IE in NR). Thus, the normal intra-RAT handover procedure can be followed for reestablishing the connection that re-enters the cell in which the random access procedure is applied. Moreover, once the network receives the RRC reconfiguration complete message, the connection can be considered reestablished. In other words, it can be possible to resume user plane data transmission at a certain point within the random access procedure corresponding to the UE application layer-1 (LI) and medium access control (MAC) default configuration in 814. Figure 8 As such, the UE is able to reestablish its user plane data transmission with the network without experiencing the 29ms and 38ms delay associated with performing the complete connection reestablishment procedure associated with 814-824.

[0227] It is well understood that, by using personally identifiable information, one must follow the privacy policies and practices that are generally recognized as satisfying or exceeding industry- or government-recognized requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risks it faces from unauthorized or illegal access or use, and battery shall be clearly indicated to users what personally identifiable information is being collected, how it is to be used, and how it should be maintained and secured.

[0228] Embodiments of the disclosure can be realized in any of various forms. For example, some embodiments can be realized as computer-implemented methods, computer-readable memory media, or computer systems. Other embodiments can be realized using one or more custom-designed hardware devices, such as ASICs. Still other embodiments can be realized using one or more programmable hardware elements, such as FPGAs.

[0229] In some embodiments, a non-transitory computer-readable memory medium can be configured such that it stores program instructions and / or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, such as any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets.

[0230] In some embodiments, a device (e.g., UE 106) can be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device can be implemented in any of a variety of forms.

[0231] Any of the methods described herein for operating a user equipment (UE) can be the basis for a corresponding method for operating a base station, by interpreting each message / signal X received by the UE in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station.

[0232] While the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be construed to include all such variations and modifications as falling within the true spirit and scope of the present disclosure.

Claims

1. A method for wireless communication, comprising: Establish a Radio Resource Control (RRC) connection with the first cell of the cellular network; The cellular network is transmitted signaling including an indication of support for enhanced radio link failure (RLF) recovery capability, wherein the enhanced RLF recovery capability includes applying a connection mode configuration after RLF recovery on the first cell; Receive one or more RRC messages from the cellular network, including configuration information for RLF recovery on the first cell; Detect one or more RLFs corresponding to the first cell; The first cell is determined to be a suitable RLF recovery candidate cell from one or more candidate cells through the connection reconstruction cell selection process; In response to detecting the one or more RLFs and determining that the first cell is a suitable RLF recovery candidate cell, the configuration information for RLF recovery on the first cell is applied; In response to the application of the configuration information, signaling including an indication of RLF recovery is transmitted to the cellular network; as well as When the trigger is successfully received at the cellular network, the configuration information is used to rebuild the RRC connection with the cellular network without exchanging additional signaling with the cellular network as part of the complete RRC connection rebuilding process.

2. The method according to claim 1, The first cell includes the primary cell PCell to which the UE was connected before the one or more RLFs.

3. The method according to claim 1, The candidate cells mentioned above include neighboring cells.

4. The method according to claim 1, This includes the triggered signaling further comprising at least one of the following: Regarding the rationale for the enhanced RLF recovery, Identifiers for application configuration information. The reason for the one or more RLFs Information data regarding the one or more RLFs, and RLF report.

5. The method according to claim 1, The signaling transmitted via Media Access Control Layer-2 (MAC L2) includes the triggering signaling indicating RLF recovery.

6. The method according to claim 1, Upon successful receipt of the trigger, user plane data transmission between the UE and the cellular network is resumed.

7. The method according to claim 1, The configuration information includes one or more enhanced RLF recovery configurations associated with the one or more candidate cells.

8. The method according to claim 7, Each of the one or more enhanced RLF recovery configurations corresponds to one or more different validity periods configured by the cellular network.

9. An apparatus for wireless communication, comprising: A processor configured to perform the method according to any one of claims 1 to 8 when executing instructions stored in memory.

10. The apparatus according to claim 9, further comprising: A radio component, which is operatively coupled to the processor.

11. A non-transitory computer-readable storage medium storing program instructions that are executed by one or more processors to cause a user equipment (UE) to perform operations according to any one of claims 1 to 8.

12. A method for wireless communication, comprising: Establish a Radio Resource Control (RRC) connection with the User Equipment (UE) in the first cell of the cellular network; Transmit a capability request message to the UE; In response to the capability request message, the UE receives signaling including an indication of support for enhanced radio link failure (RLF) recovery capability, wherein the enhanced RLF recovery capability includes applying a connection mode configuration after RLF recovery on the first cell; Transmit one or more RRC messages, including configuration information, to the UE; Receive signaling from the UE including a trigger indicating RLF recovery; When the trigger is successfully received at the cellular network, the configuration information is used to rebuild the RRC connection with the UE without performing additional signaling exchange with the cellular network as part of the complete RRC connection rebuilding process.

13. The method of claim 12, further comprising: The configuration corresponds to one or more validity periods of the configuration information.

14. The method of claim 12, further comprising: Dynamically enable or disable the enhanced RLF recovery capability of the UE.

15. The method of claim 12, further comprising: The enhanced RLF capability is indicated via a System Information Broadcast (SIB) message.

16. The method of claim 12, wherein the first cell comprises the primary cell PCell to which the UE was connected before the RLF.

17. The method of claim 12, wherein the triggered signaling further comprises at least one of the following: Regarding the rationale for the aforementioned RLF recovery Identifiers for application configuration information. One or more RLF causes, Information data regarding the one or more RLFs, and RLF report.

18. The method according to claim 12, The signaling transmitted via Media Access Control Layer-2 (MAC L2) includes the triggering signaling indicating RLF recovery.

19. An apparatus for wireless communication, comprising: A processor configured to perform the operation of any one of claims 12 to 18 when executing instructions stored in memory.

20. A non-transitory computer-readable storage medium storing program instructions that are executed by one or more processors to cause a cellular base station (BS) to perform the operation of the method according to any one of claims 12 to 18.

Images