WO2024007186A1

WO2024007186A1 - Techniques to facilitate avoiding rrc re-establishment

Info

Publication number: WO2024007186A1
Application number: PCT/CN2022/104071
Authority: WO
Inventors: Feng Chen; Chunxia LI; Yuyu YAN
Original assignee: Qualcomm Incorporated
Priority date: 2022-07-06
Filing date: 2022-07-06
Publication date: 2024-01-11

Abstract

Apparatus, methods, and computer-readable media for facilitating avoiding performing an RRC connection re-establishment procedure based on a partial failure associated with an RRC reconfiguration message are disclosed herein. The partial failure may be based on a sidelink configuration associated with the RRC reconfiguration message. An example method for wireless communication at a UE includes receiving an RRC reconfiguration message including a sidelink configuration. The example method also includes initiating a sidelink configuration procedure based on the sidelink configuration. The example method also includes transmitting an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The example method also includes skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

Description

TECHNIQUES TO FACILITATE AVOIDING RRC RE-ESTABLISHMENT

INTRODUCTION

The present disclosure relates generally to communication systems, and more particularly, to wireless communications utilizing radio resource control (RRC) reconfiguration procedures.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method of wireless communication at a user equipment (UE) is provided. The method may include receiving a radio resource control (RRC) reconfiguration message including a sidelink configuration. The example method may also include initiating a sidelink configuration procedure based on the sidelink configuration. Additionally, the example method may include transmitting an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The example method may also include skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another aspect of the disclosure, an apparatus for wireless communication is provided. The apparatus may be a UE that includes a memory and at least one processor coupled to the memory, the memory and the at least one processor configured to receive an RRC reconfiguration message including a sidelink configuration. The memory and the at least one processor may also be configured to initiate a sidelink configuration procedure based on the sidelink configuration. Additionally, the memory and the at least one processor may be configured to transmit an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The memory and the at least one processor may also be configured to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another aspect of the disclosure, an apparatus for wireless communication at a UE is provided. The apparatus may include means for receiving an RRC reconfiguration message including a sidelink configuration. The example apparatus may also include means for initiating a sidelink configuration procedure based on the sidelink configuration. Additionally, the example apparatus may include means for transmitting an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The example apparatus may also include means for skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another aspect of the disclosure, a non-transitory computer-readable storage medium storing computer executable code for wireless communication at a UE is provided. The code, when executed, may cause a processor to receive an RRC reconfiguration message including a sidelink configuration. The example code, when executed, may also cause the processor to initiate a sidelink configuration procedure based on the sidelink configuration. Additionally, the example code, when executed, may cause the processor to transmit an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The example code, when executed, may also cause the processor to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In an aspect of the disclosure, a method of wireless communication at a network entity is provided. The method may include outputting an RRC reconfiguration message including a first sidelink configuration. The example method may also include obtaining an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. Additionally, the example method may include outputting a second sidelink configuration based on the indication of the sidelink configuration failure. The example method may also include skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another aspect of the disclosure, an apparatus for wireless communication is provided. The apparatus may be a network entity that includes a memory and at least one processor coupled to the memory, the memory and the at least one processor configured to output an RRC reconfiguration message including a first sidelink configuration. The memory and the at least one processor may also be configured to obtain an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. Additionally, the memory and the at least one processor may be configured to output a second sidelink configuration based on the indication of the sidelink configuration failure. The memory and the at least one processor may also be configured to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another aspect of the disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus may include means for outputting an RRC reconfiguration message including a first sidelink configuration. The example apparatus may also include means for obtaining an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. Additionally, the example apparatus may include means for outputting a second sidelink configuration based on the indication of the sidelink configuration failure. The example apparatus may also include means for skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another aspect of the disclosure, a non-transitory computer-readable storage medium storing computer executable code for wireless communication at a network entity is provided. The code, when executed, may cause a processor to output an RRC reconfiguration message including a first sidelink configuration. The example code, when executed, may also cause the processor to obtain an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. Additionally, the example code, when executed, may cause the processor to output a second sidelink configuration based on the indication of the sidelink configuration failure. The example code, when executed, may also cause the processor to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 is a diagram illustrating an example disaggregated base station architecture, in accordance with the teachings disclosed herein.

FIG. 5 is an example communication flow between a network entity and a UE, in accordance with the teachings disclosed herein.

FIG. 6 is an example communication flow between a network entity and a UE, in accordance with the teachings disclosed herein.

FIG. 7 is a flowchart of a method of wireless communication at a UE, in accordance with the teachings disclosed herein.

FIG. 8 is a flowchart of a method of wireless communication at a UE, in accordance with the teachings disclosed herein.

FIG. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus and/or network entity.

FIG. 10 is a flowchart of a method of wireless communication at a network entity, in accordance with the teachings disclosed herein.

FIG. 11 is a flowchart of a method of wireless communication at a network entity, in accordance with the teachings disclosed herein.

FIG. 12 is a diagram illustrating an example of a hardware implementation for an example network entity.

DETAILED DESCRIPTION

A UE in communication with a network entity (e.g., via an RRC connection) may perform a connection reconfiguration procedure. For example, the network entity may output (e.g., transmit) a connection reconfiguration message to modify a connection at the UE. The connection reconfiguration message may provide information regarding measurements, mobility control, radio resource configurations, and/or Access Stratum security configurations.

After receiving the connection reconfiguration message, the UE may perform one or more procedures based on the information provided by the connection reconfiguration message. In some examples, the UE may fail to comply, e.g., may not be able to comply, with the connection reconfiguration message and a connection reconfiguration failure may occur. In some such examples, the UE may transmit a connection re-establishment request to perform a connection re-establishment procedure with the network entity. The connection re-establishment procedure may facilitate re-establishing a connection, for example, with the network entity. However, when the UE is performing the connection re-establishment procedure, ongoing services at the UE may be interrupted. For example, the UE may pause or hold data in a transmission queue while performing the connection re-establishment procedure. In such examples, ongoing services may be interrupted and/or throughput may be reduced.

Aspects disclosed herein facilitate skipping the initiating of a connection re-establishment procedure based on a partial failure associated with a connection reconfiguration procedure. For example, a connection reconfiguration message may indicate one or more configurations that cause the UE to perform one or more corresponding procedures. In some examples, when the UE determines an inability to comply with the connection reconfiguration procedure (e.g., determine that the connection reconfiguration procedure is unsuccessful) due to the one or more procedures, the UE may output an indication of a partial failure based on the corresponding configuration.

For example, the connection reconfiguration message may indicate sidelink-related parameters that cause the UE to perform a corresponding procedure. In examples in which the UE is unable to complete the corresponding procedure, the UE may output an indication of the sidelink configuration failure that is obtained by the network entity. The UE may output the indication of the sidelink configuration failure via an uplink message and/or RRC signaling. In some examples, the sidelink configuration failure may be indicated via an information element (IE) of the uplink message and/or the RRC signaling. The indication of the sidelink configuration failure may also indicate a partial failure associated with the corresponding connection reconfiguration message.

The UE may also skip initiating the connection re-establishment procedure with the network entity. Additionally, by skipping the initiating of the connection re- establishment procedure, ongoing services at the UE may be uninterrupted. Moreover, throughput at the UE may be unaffected due to the partial failure of the connection reconfiguration message.

Thus, it may be appreciated that the aspects presented herein may enable a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure, which may facilitate improving communication performance, for example, by avoiding interruption of ongoing services and maintaining throughput.

The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmit receive point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) . In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .

Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) (e.g., an EPC 160) , and another core network 190 (e.g., a 5G Core (5GC) ) . The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) . The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with the core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or the core network 190) with each other over third backhaul links 134 (e.g., an X2 interface) . The first backhaul links 132, the second backhaul links 184 (e.g., an Xn interface) , and the third backhaul links 134 may be wired or wireless.

In some aspects, a base station (e.g., one of the base stations 102 or one of base stations 180) may be referred to as a RAN and may include aggregated or disaggregated components. As an example of a disaggregated RAN, a base station may include a central unit (CU) (e.g. a CU 106) , one or more distributed units (DU) (e.g., a DU 105) , and/or one or more remote units (RU) (e.g., an RU 109) , as illustrated in FIG. 1. A RAN may be disaggregated with a split between the RU 109 and an aggregated CU/DU. A RAN may be disaggregated with a split between the CU 106, the DU 105, and the RU 109. A RAN may be disaggregated with a split between the CU 106 and an aggregated DU/RU. The CU 106 and the one or more DUs may be connected via an F 1 interface. A DU 105 and an RU 109 may be connected via a fronthaul interface. A connection between the CU 106 and a DU 105 may be referred to as a midhaul, and a connection between a DU 105 and the RU 109 may be referred to as a fronthaul. The connection between the CU 106 and the core network 190 may be referred to as the backhaul.

The RAN may be based on a functional split between various components of the RAN, e.g., between the CU 106, the DU 105, or the RU 109. The CU 106 may be configured to perform one or more aspects of a wireless communication protocol, e.g., handling one or more layers of a protocol stack, and the one or more DUs may be configured to handle other aspects of the wireless communication protocol, e.g., other layers of the protocol stack. In different implementations, the split between the layers handled by the CU and the layers handled by the DU may occur at different layers of a protocol stack. As one, non-limiting example, a DU 105 may provide a logical node to host a radio link control (RLC) layer, a medium access control (MAC) layer, and at least a portion of a physical (PHY) layer based on the functional split. An RU may provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing. The CU 106 may host higher layer functions, e.g., above the RLC layer, such as a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and/or an upper layer. In other implementations, the split between the layer functions provided by the CU, the DU, or the RU may be different.

An access network may include one or more integrated access and backhaul (IAB) nodes (e.g., the IAB nodes 111) that exchange wireless communication with a UE (e.g., one of the UEs 104) or another IAB node to provide access and backhaul to a core network. In an IAB network of multiple IAB nodes, an anchor node may be referred to as an IAB donor. The IAB donor may be a base station (e.g., one of the base stations 102 or one of the base stations 180) that provides access to the core network 190 or the EPC 160 and/or control to one or more of the IAB nodes 111. The IAB donor may include a CU 106 and a DU 105. The IAB nodes 111 may include a DU 105 and a mobile termination (MT) . The DU 105 of an IAB node may operate as a parent node, and the MT may operate as a child node.

As described above, deployment of communication systems, such as 5G new radio (NR) systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmit receive point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) . In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .

Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

As an example, FIG. 4 shows a diagram illustrating architecture of an example disaggregated base station 400. The disaggregated base station 400 architecture may include one or more CUs (e.g., a CU 410) that can communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC 425) via an E2 link, or a Non-Real Time (Non-RT) RIC (e.g. a Non-RT RIC 415) associated with a Service Management and Orchestration (SMO) Framework (e.g., an SMO Framework 405) , or both) . The CU 410 (e.g., the CU 106 of FIG. 1) may communicate with one or more DUs (e.g., a DU 430) via respective midhaul links, such as an F1 interface. A DU 430 (e.g., the DU 105 of FIG. 1) may communicate with one or more RUs (e.g., an RU 440) via respective fronthaul links. An RU 440 (e.g., the RU 109 of FIG. 1) may communicate with respective UEs (e.g., the UEs 104 of FIG. 1) via one or more radio frequency (RF) access links. In some implementations, a UE may be simultaneously served by multiple RUs.

Each of the units, i.e., the CU 410, the DU 430, the RU 440, as well as the Near-RT RIC 425, the Non-RT RIC 415, and the SMO Framework 405, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 410 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 410. The CU 410 may be configured to handle user plane functionality (i.e., Central Unit -User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit -Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 410 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 410 can be implemented to communicate with the DU 430, as necessary, for network control and signaling.

The DU 430 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs. In some aspects, the DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some aspects, the DU 430 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 430, or with the control functions hosted by the CU 410.

Lower-layer functionality can be implemented by one or more RUs. In some deployments, an RU 440, controlled by a DU 430, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) can be implemented to handle over the air (OTA) communication with one or more of the UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) can be controlled by the corresponding DU. In some scenarios, this configuration can enable the DU (s) and the CU 410 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 405 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 405 may be configured to interact with a cloud computing platform (such as an open cloud 490 (O-Cloud) ) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, the CU 410, the DU 430, the RU 440 and the Near-RT RIC 425. In some implementations, the SMO Framework 405 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) (e.g., an O-eNB 411) , via an O1 interface. Additionally, in some implementations, the SMO Framework 405 can communicate directly with one or more RUs via an O1 interface. The SMO Framework 405 also may include a Non-RT RIC 415 configured to support functionality of the SMO Framework 405.

The Non-RT RIC 415 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 425. The Non-RT RIC 415 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 425. The Near-RT RIC 425 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs, one or more DUs, or both, as well as an O-eNB, with the Near-RT RIC 425.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 425, the Non-RT RIC 415 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 425 and may be received at the SMO Framework 405 or the Non-RT RIC 415 from non-network data sources or from network functions. In some examples, the Non-RT RIC 415 or the Near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 415 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 405 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .

Referring again to FIG. 1, the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area (e.g., a coverage area 110) . There may be overlapping geographic coverage areas. For example, a small cell 102a may have a coverage area 110a that overlaps the coverage area 110 of one or more of the base stations 102 (e.g., one or more macro base stations) . A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE to a base station and/or downlink (DL) (also referred to as forward link) transmissions from a base station to a UE. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc. ) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Some of the UEs 104 may communicate with each other using device-to-device (D2D) communication link (e.g., a D2D communication link 158) . The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) (e.g., STAs 152) via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102a may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102a may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102a, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz -7.125 GHz) and FR2 (24.25 GHz -52.6 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz -300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz -24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz -71 GHz) , FR4 (71 GHz -114.25 GHz) , and FR5 (114.25 GHz -300 GHz) . Each of these higher frequency bands falls within the EHF band.

With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

A base station, whether a small cell 102a or a large cell (e.g., a macro base station) , may include and/or be referred to as an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as a gNB (e.g., one of the base stations 180) may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UEs 104. When the gNB operates in millimeter wave or near millimeter wave frequencies, the gNB may be referred to as a millimeter wave base station. The millimeter wave base station may utilize beamforming 182 with one or more of the UEs 104 to compensate for path loss and short range. The base stations 180 and the UEs 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

The base stations 180 may transmit a bearnformed signal to one or more of the UEs 104 in one or more transmit directions 182′. A UE may receive the beamformed signal from the base station in one or more receive directions 182". The UE may also transmit a beamformed signal to the base station in one or more transmit directions. The base stations 180 may receive the beamformed signal from the UE in one or more receive directions. The base stations 180/the UEs 104 may perform beam training to determine the best receive and transmit directions for each of the base station/the UE. The transmit and receive directions for the base station may or may not be the same. The transmit and receive directions for the UE may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) (e.g., an MME 162) , other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway (e.g., an MBMS Gateway 168) , a Broadcast Multicast Service Center (BM-SC) (e.g., a BM-SC 170) , and a Packet Data Network (PDN) Gateway (e.g., a PDN Gateway 172) . The MME 162 may be in communication with a Home Subscriber Server (HSS) (e.g., an HSS 174) . The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include an Access and Mobility Management Function (AMF) (e.g., an AMF 192) , other AMFs 193, a Session Management Function (SMF) (e.g., an SMF 194) , and a User Plane Function (UPF) (e.g., a UPF 195) . The AMF 192 may be in communication with a Unified Data Management (UDM) (e.g., a UDM 196) . The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base stations 102 provide an access point to the EPC 160 or the core network 190 for the UEs 104. Examples of the UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UEs 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.

Referring again to FIG. 1, in certain aspects, a device in communication with a network entity, such as one of the UEs 104 in communication with one of the base stations 102 or a component of a base station (e.g., a CU 106, a DU 105, and/or an RU 109) , may be configured to manage one or more aspects of wireless communication. For example, one or more of the UEs 104 may include a partial failure component 198 configured to facilitate avoiding triggering an RRC re-establishment due to a partial failure associated with a sidelink configuration. In certain aspects, the partial failure component 198 may be configured to receive an RRC reconfiguration message including a sidelink configuration. The example partial failure component 198 may also be configured to initiate a sidelink configuration procedure based on the sidelink configuration. Additionally, the example partial failure component 198 may be configured to transmit an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The example partial failure component 198 may also be configured to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another configuration, a network entity, such as one of the base stations 102 or a component of a base station (e.g., a CU 106, a DU 105, and/or an RU 109) , may be configured to manage or more aspects of wireless communication. For example, one or more of the base stations 102 may include a network reconfiguration component 199 configured to facilitate avoiding triggering an RRC re-establishment due to a partial failure associated with a sidelink configuration. In certain aspects, the network reconfiguration component 199 may be configured to output an RRC reconfiguration message including a first sidelink configuration. The example network reconfiguration component 199 may also be configured to obtain an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. Additionally, the example network reconfiguration component 199 may be configured to output a second sidelink configuration based on the indication of the sidelink configuration failure. The example network reconfiguration component 199 may also be configured to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

The aspects presented herein may enable a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure, which may facilitate improving communication performance, for example, by avoiding interruption of ongoing services and maintaining throughput.

Although the following description provides examples directed to 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and/or other wireless technologies.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While

subframes

3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi- statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infira applies also to a 5G NR frame structure that is TDD.

FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length/duration, which is equal to 1/SCS.

Table 1

For normal CP (14 symbols/slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. As shown in Table 1, the subcarrier spacing may be equal to 2 ^μ*15 kHz, whereμ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE.The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram that illustrates an example of a first wireless device that is configured to exchange wireless communication with a second wireless device. In the illustrated example of FIG. 3, the first wireless device may include a base station 310, the second wireless device may include a UE 350, and the base station 310 may be in communication with the UE 350 in an access network. As shown in FIG. 3, the base station 310 includes a transmit processor (TX processor 316) , a transmitter 318Tx, a receiver 318Rx, antennas 320, a receive processor (RX processor 370) , a channel estimator 374, a controller/processor 375, and memory 376. The example UE 350 includes antennas 352, a transmitter 354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, a controller/processor 359, memory 360, and a TX processor 368. In other examples, the base station 310 and/or the UE 350 may include additional or alternative components.

In the DL, Internet protocol (IP) packets may be provided to the controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The TX processor 316 and the RX processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M- PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna of the antennas 320 via a separate transmitter (e.g., the transmitter 318Tx) . Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna of the antennas 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, two or more of the multiple spatial streams may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with the memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna of the antennas 352 via separate transmitters (e.g., the transmitter 354Tx) . Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna of the antennas 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

The controller/processor 375 can be associated with the memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the partial failure component 198 of FIG. 1.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the network reconfiguration component 199 of FIG. 1.

FIG. 5 illustrates an example communication flow 500 between a network entity 502 and a UE 504, as presented herein. One or more aspects described for the network entity 502 may be performed by a component of a base station, such as a CU, a DU, and/or an RU. In the illustrated example, the communication flow 500 facilitates the UE 504 performing a connection reconfiguration procedure and/or initiating a connection re-establishment procedure. Aspects of the network entity 502 may be implemented by at least one of the base stations 102 of FIG. 1 and/or the base station 310 of FIG. 3. Aspects of the UE 504 may be implemented by at least one of the UEs 104 of FIG. 1 and/or the UE 350 of FIG. 3. Although not shown in the illustrated example of FIG. 5, it may be appreciated that in additional or alternative examples, the network entity 502 may be in communication with one or more other network entities or UEs, and/or the UE 504 may be in communication with one or more other network entities or UEs.

In the illustrated example of FIG. 5, the UE 504 and the network entity 502 establish a connection. For example, the UE 504 and the network entity 502 may perform a connection establishment procedure 510 that establishes a connection between the UE 504 and the network entity 502. The connection establishment procedure 510 may be based on an RRC connection establishment procedure. For example, the UE 504 may transmit a connection setup request message, which may be referred to as an “RRCSetupRequest” message or by any other name, and the UE 504 may receive a setup message, which may be referred to as an “RRCSetup” message or by any other name, in response to the connection setup request message.

The connection between the UE 504 and the network entity 502 may facilitate standalone operation or place the UE 504 in a dual connectivity (DC) state.

In some examples, the connection with the network entity 502 may be via NR (e.g., NR standalone, NR E-UTRA Dual Connectivity (NE-DC) , or NR-NR Dual Connectivity (NR-DC) ) . In some examples, the connection with the network entity 502 may place the UE 504 in a DC state with E-UTRA. For example, the UE 504 may be in E-UTRA NR Dual Connectivity ( (NG) EN-DC) , which may include E-UTRA NR Dual Connectivity with E-UTRA connected to EPC (EN-DC) or E-UTRA NR Dual Connectivity with E-UTRA connected to 5GC (NGEN-DC) .

In some examples, the connection establishment procedure 510 may facilitate establishing signaling radio bearers (SRBs) between the UE 504 and the network entity 502. The UE 504 and the network entity 502 may use SRBs to communicate RRC messages and/or Non-Access Stratum (NAS) messages. Examples of SRBs include an “SRB0” that facilitates communicating RRC messages, an “SRB1” that facilitates communicating RRC messages and/or NAS messages prior to SRB2 establishment, an “SRB2” that facilitates communicating NAS messages and/or RRC messages that include logged measurement information, and an “SRB3” that facilitates communicating specific RRC messages when the UE is in (NG) EN-DC or NR-DC. Communications using the SRB0 may use a common control channel (CCCH) logical channel, and communications using the SRB1, the SRB2, and the SRB3 may use a dedicated control channel (DCCH) logical channel.

As shown in FIG. 5, the network entity 502 may output (e.g., transmit) a connection reconfiguration message 512 that is received by the UE 504. The connection reconfiguration message 512 may be referred to as an “RRCReconfiguration” message or by any other name. The network entity 502 may use the SRB1 or the SRB3 to communicate the connection reconfiguration message 512 to the UE 504.

The network entity 502 may output the connection reconfiguration message 512 to modify a connection (e.g., an RRC connection) . The connection reconfiguration message 512 may provide information regarding measurements (e.g., a measurement configuration) , mobility control, radio resource configuration (e.g., radio bearers, MAC main configuration, and/or physical channel configurations) , and/or Access Stratum (AS) security configuration. For example, the network entity 502 may output the connection reconfiguration message 512 modify the connection established with the UE 504 via the connection establishment procedure 510. The network entity 502 may output the connection reconfiguration message 512 to establish/modify/release radio bearers (RBs) and/or backhaul RLC channels, to perform reconfiguration with respect to a sync procedure, to setup/modify/release measurements, to add/modify/release secondary cells (SCells) or cell groups, to add/modify/release a conditional handover configuration, to add/modify/release a conditional primary secondary cell group (SCG) cell (PSCell) change configuration, etc.

After receiving the connection reconfiguration message 512, the UE 504 may perform a procedure 514 to determine whether the connection reconfiguration is successful or unsuccessful. For example, the connection reconfiguration message 512 may include one or more configurations and the UE 504 may attempt to apply the one or more configurations and/or perform one or more procedures related to the one or more configurations.

In examples in which the UE 504 determines that the connection reconfiguration is successful (e.g., a connection reconfiguration failure is not detected) , the UE 504 may transmit (e.g., output) a connection reconfiguration complete message 516 that is obtained by the network entity 502. The connection reconfiguration complete message 516 may be referred to as an “RRCReconfigurationComplete” message or by any other name. The UE 504 may output the connection reconfiguration complete message 516 to confirm the successful completion of a connection reconfiguration (e.g., an RRC connection reconfiguration) . The UE 504 may use the SRB1 or the SRB3 to communicate the connection reconfiguration complete message 516.

In other examples in which the UE 504 determines that the connection reconfiguration is unsuccessful (e.g., a connection reconfiguration failure is detected) , the UE 504 and the network entity 502 may perform a connection re-establishment procedure 518. The connection re-establishment procedure 518 may facilitate re-establishing a connection (e.g., an RRC connection) . For example, the UE 504 and the network entity 502 may perform the connection re-establishment procedure 518 to re-establish the connection established via the connection establishment procedure 510.

In some examples, the UE 504 may transmit a connection re-establishment request 520 that is obtained by the network entity 502. The connection re-establishment request 520 may be referred to as an “RRCReestablishmentRequest” message or by any other name. The UE 504 may use the SRB0 to communicate the connection re-establishment request 520. The UE 504 may transmit the connection re-establishment request 520 to request the re-establishment of a connection (e.g., an RRC connection) . In some examples, the UE 504 may transmit a re-establishment cause indication 522 that is obtained by the network entity 502. The re-establishment cause indication 522 may be referred to as a “reestablishmentCause” field or by any other name. The re-establishment cause indication 522 may indicate the cause of the connection reconfiguration failure that triggered performing the connection re-establishment procedure 518. The re-establishment cause indication 522 may indicate that the failure cause is due to the connection reconfiguration, due to a handover failure, or another reason. In some examples, the re-establishment cause indication 522 may be included with the connection re-establishment request 520. For example, the re-establishment cause indication 522 may be a field of the connection re-establishment request 520.

In examples in which the UE 504 and the network entity 502 perform the connection re-establishment procedure 518, the connection reconfiguration procedure associated with the connection reconfiguration message 512 ends. Additionally, performing the connection re-establishment procedure 518 may interrupt one or more ongoing services at the UE 504 and/or may reduce throughput. For example, when performing the connection re-establishment procedure 518, data in queue for transmitting may be held (e.g. not sent) and, thus, ongoing services may be interrupted. Examples of ongoing services that may be interrupted include Voice-over NR (VoNR) , data transfer, etc.

The UE may also skip initiating the connection re-establishment procedure with the network entity. Additionally, by skipping the initiating of the connection re-establishment procedure, ongoing services at the UE are uninterrupted. Moreover, throughput at the UE may be unaffected due to the partial failure of the connection reconfiguration message.

FIG. 6 illustrates an example communication flow 600 between a network entity 602 and a UE 604, as presented herein. Aspects of the network entity 602 and the UE 604 may be implemented by the network entity 502 and the UE 504, respectively. Although not shown in the illustrated example of FIG. 6, it may be appreciated that in additional or alternative examples, the network entity 602 may be in communication with one or more other network entities or UEs, and/or the UE 604 may be in communication with one or more other network entities or UEs.

In the illustrated example, the communication flow 600 facilitates the UE 604 indicating that a connection reconfiguration failure is due to sidelink-related parameters and abstain from triggering a connection re-establishment procedure because of the connection reconfiguration failure. That is, if the UE 604 determines that a connection reconfiguration indicates a sidelink configuration and that a partial failure of the connection reconfiguration occurs due to the sidelink configuration, the UE 604 may output an indication of the sidelink configuration failure. The UE 604 may also skip initiating the connection re-establishment procedure.

In the illustrated example of FIG. 6, the UE 604 and the network entity 602 have established a connection, for example, an RRC connection. Aspects of establishing the connection are described in connection with the connection establishment procedure 510 of FIG. 5. The connection may place the UE 604 in standalone operation (e.g., NR standalone) or in a dual connectivity state (e.g., in (NG) EN-DC) .

As shown in FIG. 6, the network entity 602 may output (e.g., transmit) a connection reconfiguration message 610 that is obtained (e.g., received) by the UE 604. The network entity 602 may output the connection reconfiguration message 610 over SRB1 or SRB3. The UE 604 may receive the connection reconfiguration message 610 in (NG) EN-DC or via NR (e.g., NR standalone, NE-DC, or NR-DC) .

The connection reconfiguration message 610 may be a command to modify an RRC connection between the UE 604 and the network entity 602. For example, the connection reconfiguration message 610 may convey information for measurement configuration, mobility control, radio resource configuration, and/or AS security configuration. The connection reconfiguration message 610 may include one or more information elements (IEs) that indicate one or more configurations related to the connection reconfiguration message 610.

In the illustrated example of FIG. 6, the connection reconfiguration message 610 indicates a sidelink configuration 612 ( “SL configuration” ) . The sidelink configuration 612 may be indicated via an IE of the connection reconfiguration message 610. For example, the connection reconfiguration message 610 may include reconfiguration Ies, which may be referred to as “RRCReconfiguration-v1 61 0-IEs” or by any other name, that indicate one or more sidelink-related parameters. Examples of sidelink-related parameters include a sidelink NR configuration, which may be referred to as a “sl-ConfigDedicatedNR-r16” field or by any other name, and a sidelink E-UTRA configuration, which may be referred to as a “sl-ConfigDedicatedEUTRA-Info-r16” or by any other name. The sidelink NR configuration may provide dedicated configurations for NR sidelink communication. The sidelink E-UTRA configuration may provide information related to vehicle-to-everything (V2X) sidelink communication.

The UE 604 may initiate one or more procedures based on corresponding configurations indicated by the connection reconfiguration message 610. For example, the UE 604 may initiate a sidelink configuration procedure 614 based on the sidelink configuration 612 indicated by the connection reconfiguration message 610. The sidelink configuration procedure 614 may be include a sidelink dedicated configuration procedure (e.g., based on a sidelink NR configuration) and/or may include procedure (s) for V2X sidelink communication (e.g., based on a sidelink E-UTRA configuration) .

Although the example of FIG. 6 describes initiating the sidelink configuration procedure 614 based on the sidelink configuration 612, in other examples, the UE 604 may initiate additional or alternate configuration procedures based on the connection reconfiguration message 610.

As shown in FIG. 6, the UE 604 may perform a procedure 616 to determine whether the connection reconfiguration is successful or unsuccessful. Aspects of the procedure 616 may be similar to the procedure 514 of FIG. 5.

In examples in which the UE 604 determines that the connection reconfiguration is successful (e.g., a connection reconfiguration failure is not detected) , the UE 604 may transmit a connection reconfiguration complete message 618 that is obtained by the network entity 602. The connection reconfiguration complete message 618 may be referred to as an “RRCReconfigurationComplete” message or by any other name. The UE 604 may output the connection reconfiguration complete message 618 to confirm the successful completion of the connection reconfiguration message 610. The UE 604 may communicate the connection reconfiguration complete message 618 over SRB1 or over SRB3.

In examples in which the UE 604 determines that the connection reconfiguration is unsuccessful (e.g., a connection reconfiguration failure is detected) , the UE 604 may perform a procedure 620 to determine whether the connection reconfiguration failure is based on sidelink-related parameters (e.g., the sidelink configuration 612) . For example, the UE 604 may include the sidelink configuration 612 and one or more other configurations. In such examples, the UE 604 may have the ability to comply with the one or more other configurations, but may fail to comply with the sidelink configuration 612. In examples in which the UE 604 determines that the connection reconfiguration failure is not due to the sidelink configuration 612, then the UE 604 and the network entity 602 may initiate a connection re-establishment procedure 622. Aspects of the connection re-establishment procedure 622 may be similar to the connection re-establishment procedure 518 of FIG. 5. For example, the UE 604 may transmit a connection re-establishment request to request the re-establishment of a connection (e.g., an RRC connection) .

However, if the UE 604 determines, based on the procedure 620, that the connection reconfiguration failure is based on the sidelink-related parameters of the connection reconfiguration message 610, the UE 604 may provide an indication to the network entity 602 that the connection reconfiguration failure is due to the sidelink-related parameters (e.g., the sidelink configuration 612) . The network entity 602 may also skip (e.g., abstain from) triggering a connection re-establishment procedure, such as the connection re-establishment procedure 622.

In some examples, the UE 604 may provide the indication of the sidelink configuration failure via an uplink message. For example, the UE 604 may output a sidelink configuration failure message 630 that indicates that that the UE 604 is unable to comply with the connection reconfiguration message 610 based on a sidelink configuration failure associated with the sidelink configuration 612.

In some examples, the UE 604 may reuse an existing message between the UE 604 and the network entity 602 to provide the indication of the sidelink configuration failure. For example, the UE 604 may output a UE assistance information message 632. The UE assistance information message 632 may also be referred to as a “UEAssistanceInformation” message or by any other name. The UE 604 may output the UE assistance information message 632 over SRB1 or SRB3. The UE 604 may output the UE assistance information message 632 to provide UE assistance information to the network (e.g., the network entity 602) . Examples of information that the UE assistance information message 632 may indicate include information related to overheating assistance information, parameters and/or preferences for power saving, reference time information, etc. In the example of FIG. 6, the UE assistance information message 632 includes a sidelink configuration failure indication 634. The sidelink configuration failure indication 634 may indicate that the connection reconfiguration failure (e.g., at the procedure 616) is due to the sidelink-related parameters. In some examples, the UE assistance information message 632 may be configured to include an information element to include the sidelink configuration failure indication 634. In some examples, the sidelink configuration failure indication 634 may include a flag that is set to a first value when a sidelink configuration failure is present and is set to a second value when a sidelink failure is not present.

In some examples, the UE 604 may output a sidelink UE information message 636 to provide the indication of the sidelink configuration failure. The sidelink UE information message 636 may also be referred to as a “SidelinkUEInformationNR” message or by any other name. The UE 604 may output the sidelink UE information message 636 over SRB1. The UE 604 may output the sidelink UE information message 636 to provide NR sidelink UE information to the network (e.g., the network entity 602) . Examples of information that the sidelink UE information message 636 may indicate include information the index of frequency on which the UE 604 is interested to receive NR sidelink communication, parameters to request transmission resources for NR sidelink communication, etc. In the example of FIG. 6, the sidelink UE information message 636 includes a sidelink configuration failure indication 638. The sidelink configuration failure indication 638 may indicate that the connection reconfiguration failure (e.g., at the procedure 616) is due to the sidelink-related parameters. In some examples, the sidelink UE information message 636 may be configured to include an information element to include the sidelink configuration failure indication 638. In some examples, the sidelink configuration failure indication 638 may include a flag that is set to a first value when a sidelink configuration failure is present and is set to a second value when a sidelink failure is not present.

In some examples, the UE 604 may output a connection reconfiguration complete message 640 that is configured to indicate the partial failure associated with the connection reconfiguration message 610. For example, the connection reconfiguration complete message 640 may include a sidelink configuration failure indication 642 that indicates that the connection reconfiguration failure (e.g., at the procedure 616) is due to the sidelink-related parameters. In some examples, the connection reconfiguration complete message 640 may be configured to include an information element to include the sidelink configuration failure indication 642. In some examples, the sidelink configuration failure indication 642 may include a flag that is set to a first value when a sidelink configuration failure is present and is set to a second value when a sidelink failure is not present.

As shown in FIG. 6, the UE 604 and the network entity 602 may skip triggering a connection re-establishment procedure, such as the connection re-establishment procedure 622. For example, at 650, the UE 604 may skip initiating a connection re-establishment procedure. The UE 604 may skip initiating the connection re-establishment procedure based on the determination that the connection reconfiguration failure is a partial failure due to the sidelink configuration 612 (e.g., at the procedure 620) . In a similar manner, at 652, the network entity 602 may skip initiating a connection re-establishment procedure. The network entity 602 may skip initiating the connection re-establishment procedure based on obtaining an indication of the sidelink configuration failure (e.g., the sidelink configuration failure message 630, the sidelink configuration failure indication 634, the sidelink configuration failure indication 638, or the sidelink configuration failure indication 642) .

In examples in which the UE 604 and the network entity 602 skip initiating a connection re-establishment procedure, the connection (e.g., the RRC connection) between the UE 604 and the network entity 602 is maintained. For example, when performing a connection re-establishment procedure, data in queue for transmitting may be held (e.g. not sent) and, thus, ongoing services may be interrupted. However, by skipping initiating the connection re-establishment procedure, the UE 604 may continue transmitting data in the queue and, thus, ongoing services at the UE 604 may continue without interruption. Additionally, reductions in throughput that may occur based on performing a connection re-establishment procedure due to the partial failure (e.g., that is attributable to the sidelink configuration 612) may also be avoided, which may facilitate improving communication performance.

In some examples, the network entity 602 may output a subsequent sidelink configuration 654 that is received by the UE 604. The network entity 602 may output the subsequent sidelink configuration 654 based on obtaining the indication of the sidelink configuration failure. The subsequent sidelink configuration 654 may provide information for another sidelink configuration. As shown in FIG. 6, the UE 604 may initiate a sidelink configuration procedure 656 based on the subsequent sidelink configuration 654. In some examples, the UE 604 may transmit another indication of a sidelink configuration failure when the sidelink configuration procedure 656 is unsuccessful. In some examples, the UE 604 may initiate a connection re-establishment procedure, such as the connection re-establishment procedure 622 when the sidelink configuration procedure 656 based on the subsequent sidelink configuration 654 is unsuccessful.

FIG. 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a UE (e.g., at least one of the UEs 104, and/or an apparatus 904 of FIG. 9) . The method may facilitate improving communication performance by enabling a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure associated with a sidelink configuration and, thus, maintaining throughput and avoiding interruption of ongoing services.

At 702, the UE receives an RRC reconfiguration message including a sidelink configuration, as described in connection with the connection reconfiguration message 610 and the sidelink configuration 612 of FIG. 6. The receiving of the RRC reconfiguration message, at 702, may be performed by a cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 704, the UE initiates a sidelink configuration procedure based on the sidelink configuration, as described in connection with the sidelink configuration procedure 614 of FIG. 6. The initiating of the sidelink configuration procedure, at 704, may be performed by the partial failure component 198 of the apparatus 904 of FIG. 9.

At 706, the UE transmits an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful, as described in connection with the sidelink configuration failure message 630, the sidelink configuration failure indication 634, the sidelink configuration failure indication 638, and/or the sidelink configuration failure indication 642 of FIG. 6. The transmitting of the indication of the sidelink configuration failure, at 706, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 708, the UE skips initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure, as described in connection with 650 of FIG. 6. The skipping initiating of the RRC connection re-establishment procedure, at 708, may be performed by the partial failure component 198 of the apparatus 904 of FIG. 9.

FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a UE (e.g., at least one of the UEs 104, and/or an apparatus 904 of FIG. 9) . The method may facilitate improving communication performance by enabling a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure associated with a sidelink configuration and, thus, maintaining throughput and avoiding interruption of ongoing services.

At 802, the UE receives an RRC reconfiguration message including a sidelink configuration, as described in connection with the connection reconfiguration message 610 and the sidelink configuration 612 of FIG. 6. The receiving of the RRC reconfiguration message, at 802, may be performed by a cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 804, the UE initiates a sidelink configuration procedure based on the sidelink configuration, as described in connection with the sidelink configuration procedure 614 of FIG. 6. The initiating of the sidelink configuration procedure, at 804, may be performed by the partial failure component 198 of the apparatus 904 of FIG. 9.

At 806, the UE transmits an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful, as described in connection with the sidelink configuration failure message 630, the sidelink configuration failure indication 634, the sidelink configuration failure indication 638, and/or the sidelink configuration failure indication 642 of FIG. 6. The transmitting of the indication of the sidelink configuration failure, at 806, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 808, the UE may transmit an uplink message including the indication of the sidelink configuration failure, as described in connection with the sidelink configuration failure message 630 of FIG. 6. The transmitting of the uplink message, at 808, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 810, the UE may transmit a UE assistance information message including the indication of the sidelink configuration failure, as described in connection with the UE assistance information message 632 and the sidelink configuration failure indication 634 of FIG. 6. The transmitting of the UE assistance information message, at 810, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 812, the UE may transmit a sidelink UE information message including the indication of the sidelink configuration failure, as described in connection with the sidelink UE information message 636 and the sidelink configuration failure indication 638 of FIG. 6. The transmitting of the sidelink UE information message, at 812, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 814, the UE may transmit an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, as described in connection with the connection reconfiguration complete message 640 and the sidelink configuration failure indication 642 of FIG. 6. The RRC reconfiguration complete message may be configured with an information element including the indication of the sidelink configuration failure. In some examples, the RRC reconfiguration complete message may indicate a partial failure associated with the RRC reconfiguration message. The transmitting of the RRC reconfiguration complete message, at 814, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 816, the UE skips initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure, as described in connection with 650 of FIG. 6. The skipping initiating of the RRC connection re-establishment procedure, at 816, may be performed by the partial failure component 198 of the apparatus 904 of FIG. 9.

At 818, the UE may receive a subsequent sidelink configuration based on the indication of the sidelink configuration failure, as described in connection with the subsequent sidelink configuration 654 of FIG. 6. The receiving of the subsequent sidelink configuration, at 818, may be performed by the cellular RF transceiver 922 and/or the partial failure component 198 of the apparatus 904 of FIG. 9.

At 820, the UE may initiate a subsequent sidelink configuration procedure based on the subsequent sidelink configuration, as described in connection with the sidelink configuration procedure 656 of FIG. 6. The initiating of the subsequent sidelink configuration procedure, at 820, may be performed by the partial failure component 198 of the apparatus 904 of FIG. 9.

FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 904. The apparatus 904 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 904 may include a cellular baseband processor 924 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 922) . The cellular baseband processor 924 may include on-chip memory 924′. In some aspects, the apparatus 904 may further include one or more subscriber identity modules (SIM) cards 920 and an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910. The application processor 906 may include on-chip memory 906′. In some aspects, the apparatus 904 may further include a Bluetooth module 912, a WLAN module 914, an SPS module 916 (e.g., GNSS module) , one or more sensor modules 918 (e.g., barometric pressure sensor/altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 926, a power supply 930, and/or a camera 932. The Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include their own dedicated antennas and/or utilize one or more antennas 980 for communication. The cellular baseband processor 924 communicates through transceiver (s) (e.g., the cellular RF transceiver 922) via one or more antennas 980 with at least one of the UEs 104 and/or with an RU associated with a network entity 902. The cellular baseband processor 924 and the application processor 906 may each include a computer-readable medium/memory, such as the on-chip memory 924′, and the on-chip memory 906′, respectively. The additional memory modules 926 may also be considered a computer-readable medium/memory. Each computer-readable medium/memory (e.g., the on-chip memory 924′, the on-chip memory 906′, and/or the additional memory modules 926) may be non-transitory. The cellular baseband processor 924 and the application processor 906 are each responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor 924/application processor 906, causes the cellular baseband processor 924/application processor 906 to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor 924/application processor 906 when executing software. The cellular baseband processor 924/application processor 906 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 904 may be a processor chip (modem and/or application) and include just the cellular baseband processor 924 and/or the application processor 906, and in another configuration, the apparatus 904 may be the entire UE (e.g., see the UE 350 of FIG. 3) and include the additional modules of the apparatus 904.

As discussed supra, the partial failure component 198 is configured to receive an RRC reconfiguration message including a sidelink configuration. The partial failure component 198 is also configured to initiate a sidelink configuration procedure based on the sidelink configuration. Additionally, the partial failure component 198 is configured to transmit an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The partial failure component 198 is also configured to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

The partial failure component 198 may be within the cellular baseband processor 924, the application processor 906, or both the cellular baseband processor 924 and the application processor 906. The partial failure component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.

As shown, the apparatus 904 may include a variety of components configured for various functions. For example, the partial failure component 198 may include one or more hardware components that perform each of the blocks of the algorithm in the flowcharts of FIGs. 7 and/or 8.

In one configuration, the apparatus 904, and in particular the cellular baseband processor 924 and/or the application processor 906, includes means for receiving an RRC reconfiguration message including a sidelink configuration. The example apparatus 904 also includes means for initiating a sidelink configuration procedure based on the sidelink configuration. The example apparatus 904 also includes means for transmitting an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful. The example apparatus 904 also includes means for skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another configuration, the example apparatus 904 also includes means for transmitting an uplink message including the indication of the sidelink configuration failure.

In another configuration, the example apparatus 904 also includes means for transmitting a UE assistance information message including the indication of the sidelink configuration failure.

In another configuration, the example apparatus 904 also includes means for transmitting a sidelink UE information message including the indication of the sidelink configuration failure.

In another configuration, the example apparatus 904 also includes means for transmitting an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.

In another configuration, the example apparatus 904 also includes means for receiving a subsequent sidelink configuration based on the indication of the sidelink configuration failure. The example apparatus 904 also includes means for initiating a subsequent sidelink configuration procedure based on the subsequent sidelink configuration.

The means may be the partial failure component 198 of the apparatus 904 configured to perform the functions recited by the means. As described supra, the apparatus 904 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means.

FIG. 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a network entity (e.g., one of the base stations 102 or a component of a base station, and/or a network entity 1202 of FIG. 12) . The method may facilitate improving communication performance by enabling a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure associated with a sidelink configuration and, thus, maintaining throughput and avoiding interruption of ongoing services.

At 1002, the network entity outputs an RRC reconfiguration message including a first sidelink configuration, as described in connection with the connection reconfiguration message 610 and the sidelink configuration 612 of FIG. 6. The outputting of the RRC reconfiguration message, at 1002, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1004, the network entity obtains an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration, as described in connection with the sidelink configuration failure message 630, the sidelink configuration failure indication 634, the sidelink configuration failure indication 638, and/or the sidelink configuration failure indication 642 of FIG. 6. The obtaining of the indication of the sidelink configuration failure, at 1004, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1006, the network entity outputs a second sidelink configuration based on the indication of the sidelink configuration failure, as described in connection with the subsequent sidelink configuration 654 of FIG. 6. The outputting of the second sidelink configuration, at 1006, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1008, the network entity skips initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure, as described in connection with 652 of FIG. 6. The skipping initiating of the RRC connection re-establishment procedure, at 1008, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

FIG. 11 is a flowchart 1100 of a method of wireless communication. The method may be performed by a network entity (e.g., one of the base stations 102 or a component of a base station, and/or a network entity 1202 of FIG. 12) . The method may facilitate improving communication performance by enabling a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure associated with a sidelink configuration and, thus, maintaining throughput and avoiding interruption of ongoing services.

At 1102, the network entity outputs an RRC reconfiguration message including a first sidelink configuration, as described in connection with the connection reconfiguration message 610 and the sidelink configuration 612 of FIG. 6. The outputting of the RRC reconfiguration message, at 1102, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1104, the network entity obtains an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration, as described in connection with the sidelink configuration failure message 630, the sidelink configuration failure indication 634, the sidelink configuration failure indication 638, and/or the sidelink configuration failure indication 642 of FIG. 6. The obtaining of the indication of the sidelink configuration failure, at 1104, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1106, the network entity may obtain an uplink message including the indication of the sidelink configuration failure, as described in connection with the sidelink configuration failure message 630 of FIG. 6. The obtaining of the uplink message, at 1106, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1108, the network entity may obtain a UE assistance information message including the indication of the sidelink configuration failure, as described in connection with the UE assistance information message 632 and the sidelink configuration failure indication 634 of FIG. 6. The obtaining of the UE assistance information message, at 1108, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1110, the network entity may obtain a sidelink UE information message including the indication of the sidelink configuration failure, as described in connection with the sidelink UE information message 636 and the sidelink configuration failure indication 638 of FIG. 6. The obtaining of the sidelink UE information message, at 1110, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1112, the network entity may obtain an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, as described in connection with the connection reconfiguration complete message 640 and the sidelink configuration failure indication 642 of FIG. 6. The RRC reconfiguration complete message may be configured with an information element including the indication of the sidelink configuration failure. In some examples, the RRC reconfiguration complete message may indicate a partial failure associated with the RRC reconfiguration message. The obtaining of the RRC reconfiguration complete message, at 1112, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1114, the network entity outputs a second sidelink configuration based on the indication of the sidelink configuration failure, as described in connection with the subsequent sidelink configuration 654 of FIG. 6. The outputting of the second sidelink configuration, at 1114, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

At 1116, the network entity skips initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure, as described in connection with 652 of FIG. 6. The skipping initiating of the RRC connection re-establishment procedure, at 1116, may be performed by the network reconfiguration component 199 of the network entity 1202 of FIG. 12.

FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or an RU 1240. For example, depending on the layer functionality handled by the network reconfiguration component 199, the network entity 1202 may include the CU 1210; both the CU 1210 and the DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both the DU 1230 and the RU 1240; or the RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include on-chip memory 1212′. In some aspects, may further include additional memory modules 1214 and a communications interface 1218. The CU 1210 communicates with the DU 1230 through a midhaul link, such as an F1 interface. The DU 1230 may include a DU processor 1232. The DU processor 1232 may include on-chip memory 1232′. In some aspects, the DU 1230 may further include additional memory modules 1234 and a communications interface 1238. The DU 1230 communicates with the RU 1240 through a fronthaul link. The RU 1240 may include an RU processor 1242. The RU processor 1242 may include on-chip memory 1242′. In some aspects, the RU 1240 may further include additional memory modules 1244, one or more transceivers 1246, antennas 1280, and a communications interface 1248. The RU 1240 communicates with at least one of the UEs 104. The on-chip memories (e.g., the on-chip memory 1212′, the on-chip memory 1232′, and/or the on-chip memory 1242′) and/or the additional memory modules (e.g., the additional memory modules 1214, the additional memory modules 1234, and/or the additional memory modules 1244) may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the CU processor 1212, the DU processor 1232, the RU processor 1242 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor (s) when executing software.

As discussed supra, the network reconfiguration component 199 is configured to output an RRC reconfiguration message including a first sidelink configuration. The network reconfiguration component 199 is also configured to obtain an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. Additionally, the network reconfiguration component 199 is configured to output a second sidelink configuration based on the indication of the sidelink configuration failure. The network reconfiguration component 199 is also configured to skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

The network reconfiguration component 199 may be within one or more processors of one or more of the CU 1210, DU 1230, and the RU 1240. The network reconfiguration component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.

The network entity 1202 may include a variety of components configured for various functions. For example, the network reconfiguration component 199 may include one or more hardware components that perform each of the blocks of the algorithm in the flowcharts of FIGs. 10 and/or 11.

In one configuration, the network entity 1202 includes means for outputting an RRC reconfiguration message including a first sidelink configuration. The example network entity 1202 also includes means for obtaining an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration. The example network entity 1202 also includes means for outputting a second sidelink configuration based on the indication of the sidelink configuration failure. The example network entity 1202 also includes means for skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

In another configuration, the example network entity 1202 also includes means for obtaining an uplink message including the indication of the sidelink configuration failure.

In another configuration, the example network entity 1202 also includes means for obtaining a UE assistance information message including the indication of the sidelink configuration failure.

In another configuration, the example network entity 1202 also includes means for obtaining a sidelink UE information message including the indication of the sidelink configuration failure.

In another configuration, the example network entity 1202 also includes means for obtaining an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.

The means may be the network reconfiguration component 199 of the network entity 1202 configured to perform the functions recited by the means. As described supra, the network entity 1202 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.

The aspects presented herein may enable a UE to avoid triggering an RRC connection re-establishment procedure due to a partial failure, which may facilitate improving communication performance, for example, by avoiding interruption of ongoing services and avoiding reduction in throughput due to the partial failure. For example, disclosed techniques facilitate the UE indicating that a connection reconfiguration failure is due to a sidelink-related configuration and abstaining from triggering a connection re-establishment procedure because of the connection reconfiguration failure. That is, if the UE determines that a connection reconfiguration indicates a sidelink-related configuration and that a partial failure of the connection reconfiguration occurs due to the sidelink-related configuration, the UE may output an indication of the sidelink configuration failure. The UE may also skip initiating the connection re-establishment procedure, thereby allowing ongoing services at the UE to be uninterrupted and throughput at the UE due to the partial failure of the connection reconfiguration may be unaffected.

It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

Aspect 1 is a method of wireless communication at a UE, including: receiving a radio resource control (RRC) reconfiguration message including a sidelink configuration; initiating a sidelink configuration procedure based on the sidelink configuration; transmitting an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful; and skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

Aspect 2 is the method of aspect 1, further including: transmitting an uplink message including the indication of the sidelink configuration failure.

Aspect 3 is the method of any of

aspects

1 and 2, further including: transmitting a UE assistance information message including the indication of the sidelink configuration failure.

Aspect 4 is the method of any of aspects 1 to 3, further including: transmitting a sidelink UE information message including the indication of the sidelink configuration failure.

Aspect 5 is the method of any of aspects 1 to 4, further including: transmitting an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.

Aspect 6 is the method of any of aspects 1 to 5, further including that the RRC reconfiguration complete message indicates a partial failure associated with the RRC reconfiguration message.

Aspect 7 is the method of any of aspects 1 to 6, further including: receiving a subsequent sidelink configuration based on the indication of the sidelink configuration failure; and initiating a subsequent sidelink configuration procedure based on the subsequent sidelink configuration.

Aspect 8 is an apparatus for wireless communication at a UE including at least one processor coupled to a memory and configured to implement any of aspects 1 to 7.

In aspect 9, the apparatus of aspect 8 further includes at least one antenna coupled to the at least one processor.

In aspect 10, the apparatus of

aspect

8 or 9 further includes a transceiver coupled to the at least one processor.

Aspect 11 is an apparatus for wireless communication including means for implementing any of aspects 1 to 7.

In aspect 12, the apparatus of aspect 11 further includes at least one antenna coupled to the means to perform the method of any of aspects 1 to 7.

In aspect 13, the apparatus of

aspect

11 or 12 further includes a transceiver coupled to the means to perform the method of any of aspects 1 to 7.

Aspect 14 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 1 to 7.

Aspect 15 is a method of wireless communication at a network entity, including outputting a radio resource control (RRC) reconfiguration message including a first sidelink configuration; obtaining an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration; outputting a second sidelink configuration based on the indication of the sidelink configuration failure; and skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.

Aspect 16 is the method of aspect 15, further including: obtaining an uplink message including the indication of the sidelink configuration failure.

Aspect 17 is the method of any of aspects 15 and 16, further including: obtaining a UE assistance information message including the indication of the sidelink configuration failure.

Aspect 18 is the method of any of aspects 15 to 17, further including: obtaining a sidelink UE information message including the indication of the sidelink configuration failure.

Aspect 19 is the method of any of aspects 15 to 18, further including: obtaining an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.

Aspect 20 is the method of any of aspects 15 to 19, further including that the RRC reconfiguration complete message indicates a partial failure associated with the RRC reconfiguration message.

Aspect 21 is an apparatus for wireless communication at a network entity including at least one processor coupled to a memory and configured to implement any of aspects 15 to 20.

In aspect 22, the apparatus of aspect 21 further includes at least one antenna coupled to the at least one processor.

In aspect 23, the apparatus of aspect 21 or 22 further includes a transceiver coupled to the at least one processor.

Aspect 24 is an apparatus for wireless communication including means for implementing any of aspects 15 to 20.

In aspect 25, the apparatus of aspect 24 further includes at least one antenna coupled to the means to perform the method of any of aspects 15 to 20.

In aspect 26, the apparatus of aspect 24 or 25 further includes a transceiver coupled to the means to perform the method of any of aspects 15 to 20.

Aspect 27 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 15 to 20.

Claims

An apparatus for wireless communication at a user equipment (UE) , comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receive a radio resource control (RRC) reconfiguration message including a sidelink configuration;

initiate a sidelink configuration procedure based on the sidelink configuration;

transmit an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful; and

skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.
The apparatus of claim 1, further comprising:

at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to:

transmit an uplink message including the indication of the sidelink configuration failure.
The apparatus of claim 1, wherein the at least one processor is further configured to:

transmit a UE assistance information message including the indication of the sidelink configuration failure.
The apparatus of claim 1, wherein the at least one processor is further configured to:

transmit a sidelink UE information message including the indication of the sidelink configuration failure.
The apparatus of claim 1, wherein the at least one processor is further configured to:

transmit an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.
The apparatus of claim 5, wherein the RRC reconfiguration complete message indicates a partial failure associated with the RRC reconfiguration message.
The apparatus of claim 1, wherein the at least one processor is further configured to:

receive a subsequent sidelink configuration based on the indication of the sidelink configuration failure; and

initiate a subsequent sidelink configuration procedure based on the subsequent sidelink configuration.
A method of wireless communication at a user equipment (UE) , comprising:

receiving a radio resource control (RRC) reconfiguration message including a sidelink configuration;

initiating a sidelink configuration procedure based on the sidelink configuration;

transmitting an indication of a sidelink configuration failure in response to the sidelink configuration procedure being unsuccessful; and

skipping initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.
The method of claim 8, further comprising:

transmitting an uplink message including the indication of the sidelink configuration failure.
The method of claim 8, further comprising:

transmitting a UE assistance information message including the indication of the sidelink configuration failure.
The method of claim 8, further comprising:

transmitting a sidelink UE information message including the indication of the sidelink configuration failure.
The method of claim 8, further comprising:

transmitting an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.
The method of claim 12, wherein the RRC reconfiguration complete message indicates a partial failure associated with the RRC reconfiguration message.
The method of claim 8, further comprising:

receiving a subsequent sidelink configuration based on the indication of the sidelink configuration failure; and

initiating a subsequent sidelink configuration procedure based on the subsequent sidelink configuration.
An apparatus for wireless communication at a network entity, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

output a radio resource control (RRC) reconfiguration message including a first sidelink configuration;

obtain an indication of a sidelink configuration failure associated with a sidelink configuration procedure based on the first sidelink configuration;

output a second sidelink configuration based on the indication of the sidelink configuration failure; and

skip initiating an RRC connection re-establishment procedure based on the indication of the sidelink configuration failure.
The apparatus of claim 15, further comprising:

at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to:

obtain an uplink message including the indication of the sidelink configuration failure.
The apparatus of claim 15, wherein the at least one processor is further configured to:

obtain a UE assistance information message including the indication of the sidelink configuration failure.
The apparatus of claim 15, wherein the at least one processor is further configured to:

obtain a sidelink UE information message including the indication of the sidelink configuration failure.
The apparatus of claim 15, wherein the at least one processor is further configured to:

obtain an RRC reconfiguration complete message in response to the sidelink configuration procedure being unsuccessful, the RRC reconfiguration complete message configured with an information element including the indication of the sidelink configuration failure.
The apparatus of claim 19, wherein the RRC reconfiguration complete message indicates a partial failure associated with the RRC reconfiguration message.