Reconfiguration for lower layer mobility

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, which may be a Layer 1 (L1) / Layer 2 (L2) handover procedure. The UE may receive a second control message indicating a first reset procedure or a second reset procedure, which may each indicate a respective set of operating parameters for a higher layer than L1 / L2 in the protocol stack. The UE may perform the lower layer handover procedure, which may include a handover from a first serving cell to a second serving cell. The UE may perform the first reset procedure or the second reset procedure based on the handover, where the first reset procedure may include maintaining operating parameters of the second serving cell, and the second reset procedure may include handover operating parameters of the second serving cell.

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 045,720, entitled "RECONFIGURATION FOR LOWER LAYER MOBILITY," filed on October 11, 2022, by ZHOU et al., which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communication, including reconfiguration for lower layer mobility. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting reconfigurations for lower layer (e.g., layer 1 (L1) or layer 2 (L2)) mobility. For example, the described techniques provide L1 / L2 mobility procedures that utilize a modified higher layer reconfiguration procedure. A user equipment (UE) may receive a first control message that indicates a set of mobility parameters for a lower layer handover procedure (e.g., an L1 or L2 handover procedure). In some cases, the UE may receive a second control message that indicates a first reset procedure and a second reset procedure, where the first reset procedure and the second reset procedure indicate respective first and second sets of operating parameters for layers higher than L1 and L2 in a protocol stack. The UE may perform the lower layer handover procedure based on the set of mobility parameters and the first or second set of operating parameters. For example, when performing a handover procedure, the UE may switch from a first serving cell to a second serving cell. Based on whether the first serving cell and the second serving cell are associated with the same distributed unit (DU), the UE may then perform the first reset procedure or the second reset procedure. In this way, the UE may communicate with the second serving cell according to the first or second set of operating parameters based on performing one of the lower layer handover procedure and the reset procedure.

[0006] A method for wireless communication at a UE is described. The method may include: receiving a first control message that indicates a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure includes one of an L1 handover procedure or an L2 handover procedure; receiving a second control message that indicates one of a first reset procedure for the lower layer handover procedure or a second reset procedure for the lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers higher than L1 or L2 in a protocol stack, and where the second reset procedure indicates a second set of operating parameters for the higher layer; and performing the lower layer handover procedure based on the set of mobility parameters and one of the first reset procedure or the second reset procedure.

[0007] Describes an apparatus for wireless communication at a UE. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process; receive a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operating parameters for a layer higher than L1 or L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for the higher layer; and perform the lower layer handover process based on the set of mobility parameters and one of the first reset process or the second reset process.

[0008] Describes another apparatus for wireless communication at a UE. The apparatus may include: means for receiving a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process; means for receiving a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operating parameters for a layer higher than L1 or L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for the higher layer; and means for performing the lower layer handover process based on the set of mobility parameters and one of the first reset process or the second reset process.

[0009] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process; receive a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operating parameters for a layer higher than L1 or L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for the higher layer; and perform the lower layer handover process based on the set of mobility parameters and one of the first reset process or the second reset process.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: switching from a first serving cell to a second serving cell based on performing the lower layer handover procedure, where the first serving cell and the second serving cell correspond to the same DU; performing the first reset procedure based on switching to the second serving cell; and communicating with the second serving cell according to the first set of operating parameters.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing the first reset procedure may include operations, features, components, or instructions for: applying the first set of operating parameters to the second serving cell, where the first set of operating parameters was previously applied to the first serving cell.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: applying secondary primary cell (SpCell) configuration to the second serving cell based on switching to the second serving cell.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: switching from a first serving cell associated with a first DU to a second serving cell associated with a second DU based on performing the lower layer handover procedure; performing the second reset procedure based on switching to the second serving cell; and communicating with the second serving cell according to the second set of operating parameters.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing the second reset procedure may include operations, features, components, or instructions for: applying the second set of operating parameters to the second serving cell, where the second set of reset operating parameters was previously applied to the first set of operating parameters of the first serving cell.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing the second reset procedure may include operations, features, components, or instructions for: performing a part of the second reset procedure based on switching to the second serving cell, where the part of the second reset procedure includes resetting the media access control (MAC) layer in the protocol stack.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the second control message may include operations, features, components, or instructions for: receiving an information element indicating that the second reset procedure may be enabled or disabled.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the second control message can include operations, features, components, or instructions for: receiving an L1 signal or an L2 signal that enables one of the first reset procedure or the second reset procedure.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein can further include operations, features, components, or instructions for: performing the first reset procedure or the second reset procedure at least in part based on the set of mobility parameters.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of mobility parameters indicates one or more serving cells of the UE and one or more corresponding DUs.

[0020] A method is described. The method can include: outputting a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure includes one of an L1 handover procedure or an L2 handover procedure; and outputting a second control message indicating one of a first reset procedure for the lower layer handover procedure or a second reset procedure for the lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers higher than L1 and L2 in the protocol stack, and where the second reset procedure indicates a second set of operating parameters for the higher layer.

[0021] An apparatus is described. The apparatus can include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: output a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure includes one of an L1 handover procedure or an L2 handover procedure; and output a second control message indicating one of a first reset procedure for the lower layer handover procedure or a second reset procedure for the lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers higher than L1 and L2 in the protocol stack, and where the second reset procedure indicates a second set of operating parameters for the higher layer.

[0022] Another apparatus is described. The apparatus may include: means for outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process; and means for outputting a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than L1 and L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for the higher layer.

[0023] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: output a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process; and output a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than L1 and L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for the higher layer.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: communicating with a UE via a serving cell according to the first set of operating parameters.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: communicating with a UE via a serving cell according to the second set of operating parameters.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, outputting the second control message may include operations, features, components, or instructions for: outputting an information element indicating that the second reset process may be enabled or disabled.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, outputting the second control message may include operations, features, components, or instructions for: outputting the second control message indicating the first reset process and the second reset process.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of mobility parameters indicates one or more serving cells of a UE and one or more corresponding DUs. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 Illustrates an example of a wireless communication system supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0030] Figure 2 Illustrates an example of a network architecture supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0031] Figure 3 Illustrates an example of a wireless communication system supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0032] Figure 4 Illustrates an example of a process flow supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0033] Figure 5 and Figure 6 Shows a block diagram of a device supporting a reconfiguration process with synchronization functionality for L1 / L2 mobility in accordance with one or more aspects of the present disclosure.

[0034] Figure 7 Shows a block diagram of a communication manager supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0035] Figure 8 Shows a diagram of a system including a device supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0036] Figure 9 and Figure 10 Shows a block diagram of a device supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0037] Figure 11 Shows a block diagram of a communication manager supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0038] Figure 12 Shows a diagram of a system including a device supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure.

[0039] Figures 13 to 17 Shows a flowchart illustrating a method supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. Detailed Description

[0040] In a wireless communication system, a central unit (CU) of a network entity (e.g., a base station) can support one or more distributed units (DUs), and each DU can support a set of cells for communicating with a user equipment (UE). For example, the UE can receive control signaling for a set of cells configured for lower layer mobility, where the lower layer can include layer 1 (L1) or layer 2 (L2) in the protocol stack. As the UE (e.g., a mobile wireless device) moves through an area supported by the wireless communication system, individual cells from the set of cells can be activated or deactivated via L1 / L2 signaling. In this way, the UE can perform a handover process between different cells. During such an L1 / L2 mobility process, and when the UE switches between cells, the L1 / L2 signaling can trigger a secondary cell (SCell) of the UE to switch to a secondary primary cell (SpCell). That is, the SCell can become the primary serving cell of the UE. Switching the SCell to the SpCell can be performed using a radio resource control (RRC) reconfiguration process with a synchronization function, where the UE can reset higher layer entities (e.g., the media access control (MAC) layer or the radio link control layer (RLC)) of the SCell. However, in some scenarios, such as when the SCell and the SpCell are supported by the same DU (and thus share the same higher layer parameters), resetting the higher layer parameters may be redundant, and such a reconfiguration process may increase latency and increase resource consumption of the L1 / L2 mobility process.

[0041] The techniques described herein support a modified reconfiguration for lower layer mobility. The UE can receive a first control message (e.g., RRC signaling) that indicates a set of mobility parameters for a lower layer handover process. The lower layer handover process can include an L1 handover process or an L2 handover process. In some cases, the UE can receive a second control message (e.g., the same or different RRC signaling) that indicates a first reset process and a second reset process, where the first reset process and the second reset process indicate respective first and second sets of operating parameters for higher layers (e.g., the MAC layer, the RLC layer, and any other layer higher than L1 and L2) in the protocol stack.

[0042] The UE may perform a lower layer handover procedure based on a set of mobility parameters and a first or second set of operation parameters. For example, when performing a handover procedure, the UE may switch from a first serving cell to a second serving cell. If the first serving cell and the second serving cell share the same DU, the UE may then perform a first reset procedure from the first serving cell to the second serving cell and maintain the first set of operation parameters. Alternatively, if the first serving cell and the second serving cell are associated with different DUs, the UE may perform a second reset procedure and reconfigure the second serving cell (e.g., the higher layers in the protocol stack of the second serving cell) with the second set of operation parameters. In this way, the UE may communicate with the second serving cell based on the lower layer handover procedure according to the first or second set of operation parameters. By skipping some or all parts of the higher layer RRC reconfiguration procedure, the UE may reduce the interruption to the user plane, improve the quality of service (QoS) and signaling throughput, and reduce the latency of the L1 / L2 mobility procedure.

[0043] Aspects of the present disclosure are first described in the context of a wireless communication system. Then, aspects of the present disclosure are described in the context of a network architecture and a process flow. Aspects of the present disclosure are further illustrated by device diagrams, system diagrams, and flowcharts related to reconfigurations for lower layer mobility and are further described with reference to the device diagrams, system diagrams, and flowcharts.

[0044] Figure 1 An example of a wireless communication system 100 that supports reconfigurations for lower layer mobility in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0045] Network entity 105 can be dispersed throughout a geographic area to form a wireless communication system 100 and can include devices in different forms or with different capabilities. In various examples, network entity 105 can be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 can communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 can support a coverage area 110 (e.g., a geographic coverage area) within which UE 115 and network entity 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographic area within which network entity 105 and UE 115 can support signal communication according to one or more radio access technologies (RATs).

[0046] UE 115 can be dispersed throughout coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile or stationary and mobile at different times. UE 115 can be a device in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated. UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 other UEs 115 or network entity 105 as shown.

[0047] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, a device, an equipment, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As yet another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc. may include the disclosure of UE 115, network entity 105, device, equipment, computing system, etc. as nodes. For example, the disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0048] In some examples, network entity 105 may communicate with core network 130 or with each other or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical link, optical fiber link), one or more wireless links (e.g., radio link, wireless optical link), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155.

[0049] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B or other suitable terms). In some examples, the network entity 105 (e.g., base station 140) may be implemented in an integrated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0050] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., disaggregated base station architecture, disaggregated RAN architecture) that may be configured to utilize a protocol stack physically or logically distributed between two or more network entities 105 (such as an integrated access and backhaul (IAB) network, open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) or virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: CU 160, DU 165, radio unit (RU) 170, RAN intelligent controller (RIC) 175 (e.g., near real-time RIC (near RT RIC), non-real-time RIC (non RT RIC)), service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU) or transmit receive point (TRP). One or more components of the network entity 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0051] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be employed between the CU 160 and DU 165 such that the CU 160 can support one or more layers in the protocol stack and the DU 165 can support one or more different layers in the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), L2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layers, such as L1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., RLC layer, MAC layer) functions and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be employed between the DU 165 and RU 170 such that the DU 165 can support one or more layers in the protocol stack and the RU 170 can support one or more different layers in the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and DU 165 or between the DU 165 and RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers in the protocol stack, which are supported by the respective network entities 105 communicating via such communication links.

[0052] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by each other. One or more IAB nodes 104 can be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via the supported access and backhaul links (e.g., backhaul communication link 120). An IAB node 104 can include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT can include a separate antenna set for relaying communication with a UE 115, or can share the same antenna (e.g., of an RU 170 of the IAB node 104) used for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, an IAB node 104 can include a DU 165 that supports communication links with additional entities (e.g., IAB nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of a split RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) can be configured to operate according to the techniques described herein.

[0053] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor may facilitate the connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and a RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a part of the backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a part of the backhaul link).

[0054] The IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node towards the sub-nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards the parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more sub-nodes (e.g., the IAB donor may relay transmissions for UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or a sub-node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for a sub-IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (e.g., the DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the sub-IAB node 104 or the UE 115.

[0055] For example, the IAB node 104 can be referred to as a parent node that supports communication for sub-IAB nodes or as a sub-node associated with the IAB donor or both. The IAB donor can include the CU 160 having a wired or wireless connection (e.g., the backhaul communication link 120) to the core network 130 and can act as the parent node of the IAB node 104. For example, the DU 165 of the IAB donor can relay transmissions to the UE 115 via the IAB node 104, or can signal transmissions directly to the UE 115, or both. The CU 160 of the IAB donor can signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 can schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data can be relayed to and from the IAB node 104 via signaling over the NR Uu interface to the MT of the IAB node 104. Communication with the IAB node 104 can be scheduled by the DU 165 of the IAB donor, and communication with the IAB node 104 can be scheduled by the DU 165 of the IAB node 104.

[0056] In the case where the techniques described herein are applied in the context of a split RAN architecture, one or more components of the split RAN architecture can be configured to support reconfiguration for lower layer mobility as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) can additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0057] The UE 115 can include or can be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device or some other suitable term, where "device" can also be referred to as a unit, a station, a terminal, or a client, etc. The UE 115 can also include or can be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 can include or can be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which can be implemented in various objects such as appliances or vehicles, meters, etc.

[0058] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 that can sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., asFigure 1 as shown

[0059] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined to support communication link 125. For example, a carrier for communication link 125 may include a portion (e.g., bandwidth part (BWP)) of an RF spectrum band operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may use carrier aggregation (CA) or multi-carrier operation to support communication with UE 115. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a CA configuration. CA may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of network entity 105. For example, the terms "transmit," "receive," or "communicate" when referring to network entity 105 may refer to any part of network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0060] In some examples, such as in a CA configuration, a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in independent mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in non-independent mode, in which case the connection is anchored using a different carrier (e.g., different carriers of the same or different radio access technologies).

[0061] The communication link 125 shown in the wireless communication system 100 may include a downlink transmission (e.g., forward link transmission) from the network entity 105 to the UE 115, an uplink transmission from the UE 115 to the network entity 105 (e.g., reverse link transmission), or other transmission configurations such as both. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink communication and uplink communication (e.g., in TDD mode).

[0062] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth or may be capable of being configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0063] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., during the transmission duration) and a relatively high-order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity for communication with the UE 115.

[0064] One or more parameter sets for a carrier can be supported, and the parameter sets can include subcarrier spacing (Δf) and cyclic prefix. The carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of the UE 115 can be restricted to one or more active BWPs.

[0065] The time intervals available for the network entity 105 or the UE 115 can be expressed as multiples of a basic time unit, and the basic time unit can refer to, for example, the sampling period T s = 1 / (Δf max ·N f ) seconds, where Δf max can represent the supported subcarrier spacing, and N f can represent the supported discrete Fourier transform (DFT) size. The time intervals of the communication resources can be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0066] Each frame can include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot can have the same duration. In some examples, a frame can be divided (e.g., in the time domain) into subframes, and each subframe can be further divided into a certain number of time slots. Alternatively, each frame can include a variable number of time slots, and the number of time slots can depend on the subcarrier spacing. Each time slot can include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, a time slot can be further divided into a plurality of mini - slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period can be associated with one or more (e.g., N f ones) sampling periods. The duration of the symbol period can depend on the subcarrier spacing or the operating frequency band.

[0067] A subframe, time slot, mini - slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain), and can be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0068] According to various techniques, carriers can be used to multiplex physical channels for communication. For example, one or more of time-division multiplexing (TDM) techniques, frequency-division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search a control region for control information according to one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format with a given payload size. The search space set can include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set for transmitting control information to a specific UE 115.

[0069] The network entity 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells or any combination thereof). The term "cell" can refer to a logical communication entity for communicating with the network entity 105 (e.g., using a carrier) and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) for differentiating adjacent cells. In some examples, a cell can also refer to a coverage area 110 or a part of the coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, the scope of such cells can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or can include a building, a subset of a building, or an external space between or overlapping with the coverage areas 110, etc.

[0070] Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access for UEs 115 having a service subscription with the network provider supporting the macro cell. In comparison with macro cells, small cells can be associated with a lower power network entity 105 (e.g., a lower power base station 140), and small cells can operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UEs 115 having a service subscription with the network provider, or can provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The network entity 105 can support one or more cells and can also use one or more component carriers to support communication via the one or more cells.

[0071] In some examples, a carrier can support multiple cells and can be configured with different cells according to different protocol types that can provide access for different types of devices (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)).

[0072] In some examples, the network entity 105 (e.g., base station 140, RU 170) can be movable and thus provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0073] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately aligned in time. For asynchronous operation, the network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 can not be aligned in time. The techniques described herein can be used for synchronous or asynchronous operation.

[0074] Some UEs 115 (such as MTC or IoT devices) can be low-cost or low-complexity devices and can permit automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that permit devices to communicate with each other or a device to communicate with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC can include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 can be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographical event monitoring, formation management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0075] Some UEs 115 can be configured to operate in power consumption-reducing modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include: entering a power-saving deep sleep mode when not participating in active communication, operating using limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0076] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UEs 115 can be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication can include private communication or group communication and can be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency can be used interchangeably herein.

[0077] In some examples, UE 115 may be configured to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 performing D2D communication in a group may be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network entity 105.

[0078] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communication, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0079] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which can include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of the UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets can be passed through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can be connected to the IP services 150 of one or more network operators. The IP services 150 can include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet switched streaming service.

[0080] The wireless communication system 100 can operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because, in terms of length, the wavelength range is from approximately one decimeter to one meter. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clutter), but these waves can be sufficient to penetrate structures so that a macro cell can serve a UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0081] The wireless communication system 100 may also operate using the super high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or using the extremely high frequency (EHF) region of the spectrum (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the network entity 105 (e.g., the base station 140, the RU 170), and the EHF antennas of the corresponding devices may be smaller and closer spaced than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the frequency bands designated across these frequency regions may vary by country or regulatory authority.

[0082] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band) to employ licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, the operation using an unlicensed band may be based on a CA configuration (e.g., LAA) in combination with operating using a licensed band. The operation using unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, etc.

[0083] The network entity 105 (e.g., the base station 140, the RU 170) or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna integration location, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports arranged in multiple rows and columns that the network entity 105 may use to support beamforming for communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays, which may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0084] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., network entity 105, UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via the antenna elements of an antenna array such that some signals propagating along a particular direction relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals communicated via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0085] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for conveyance via logical channels. The MAC layer can perform priority handling and multiplexing from logical channels into transport channels. The MAC layer can also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of an RRC connection that supports the radio bearers for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer can map the transport channels to physical channels.

[0086] In some wireless communication systems 100, the UE 115 can communicate via one or more lower layers such as L1 and L2. In some cases, the UE 115 can use procedures based on L1 / L2 inter-cell mobility to reduce mobility latency. For example, the network entity 105 (e.g., which can include one or more CUs 160, DUs 165, RUs 170, and other components) can configure and maintain multiple candidate cells such that the UE 115-a can more quickly apply the configurations for the candidate cells. Additionally or alternatively, the network entity 105 can configure a dynamic handover mechanism between candidate serving cells (e.g., including SpCell and SCell) for potentially applicable scenarios based on L1 / L2 signaling.

[0087] L1 / L2-based inter-cell mobility can be applicable to various scenarios. For example, UE 115-a can perform such mobility procedures for standalone, CA, and NR-DC scenarios with serving cell changes within a cell group (CG), intra-DU and inter-DU within CU scenarios (e.g., applicable to standalone and CA configurations), intra-frequency and inter-frequency scenarios, frequency range 1 (FR1) and frequency range 2 (FR2) operations, scenarios where the source cell and the target cell are synchronous or asynchronous, or any combination thereof.

[0088] In some cases, during the L1 / L2 mobility procedure, network entity 105 can use lower layer signaling (which can include L1 signaling and L2 signaling) to prepare one or more cells to become the PCell or SpCell. The L1 / L2 mobility procedure can depend on the configuration of one or more cells such that they can become the PCell or SpCell. For example, UE 115 can receive RRC signaling that configures a set of cells for L1 / L2 mobility (referred to herein as the set of cells for L1 / L2 mobility configuration). In some cases, the set of cells activated for L1 / L2 mobility can be the set of cells in the configured set that are activated and can be readily used for data and control transfer. The set of cells deactivated for L1 / L2 mobility can be the set of cells in the configured set that are deactivated and can be readily activated via L1 / L2 signaling.

[0089] UE 115 can consider various parameters of wireless communication system 100 when performing the L1 / L2 mobility procedure. For example, the mobility management of the activated set can be based on L1 / L2 signaling that is used to activate or deactivate cells in the set and to select beams within the activated cells, which can provide seamless mobility within the activated cells in the set. As UE 115-a moves throughout wireless communication system 100, cells from the set can be deactivated or activated via L1 / L2 signaling. For example, cells can be deactivated or activated based on signal quality measurements, load times, or other factors. To fully perform L1 / L2 mobility, the set of cells can include a certain number of cells that support communication within a given coverage area such that the L1 / L2 mobility procedure can be performed as the device moves throughout the coverage area.

[0090] In some examples of CA, SpCell management can be based on all cells in the wireless communication system 100 that are configured for L1 / L2 mobility with an active SpCell and SCell configuration (e.g., all cells in a set of cells with an L1 / L2 configuration). In some cases, RRC signaling (e.g., layer 3 (L3) signaling) can update the set of cells with an L1 / L2 configuration for L1 / L2 mobility. The UE 115 can use L1 / L2 signaling to set the SpCell from pre-configured options within the set of active cells. The UE 115 can use L1 / L2 signaling instead of using L3 signaling or RRC reconfiguration with synchronization capabilities to switch an SCell to an SpCell, where the UE 115 performs a random access procedure to the target new SpCell. For example, if a cell is an SCell and is promoted to become an SpCell, the UE 115 can apply the SpCell configuration. In this way, the previous SpCell can become an SCell to which the UE 115 can apply the SCell configuration.

[0091] Using L3 signaling or RRC reconfiguration with synchronization capabilities may increase the latency of the L1 / L2 mobility process. RRC reconfiguration with synchronization capabilities can be associated with information elements included in the SpCell configuration (e.g., the ReconfigurationWithSync information element included in SpCellConfig), and can list the actions that the UE 115 performs when the UE 115 receives L3 signaling to update the SpCell. Some of the actions can be based on the reset of the MAC entity for the CG. Alternatively, some of the actions can be based on an L3 handover process that includes higher layer resets (including the RLC layer and the PDCP layer). However, L1 / L2 mobility may not perform such resets, especially when all cells in the cell are supported by the MAC entity, the same DU, or both. Even if the DUs are different and the MACs in the DUs are different, the UE 115 can avoid MAC and higher layer resets, which can reduce the latency. That is, for L1 / L2 mobility, whether activated or deactivated, the cell may already be a configured serving cell. In such cases, the UE 115 can avoid changing the C-RNTI or any other credentials or parameters, and thus, performing reconfiguration with synchronization capabilities may be redundant and waste resources.

[0092] The wireless communication system 100 may utilize a modified higher layer reconfiguration procedure to support L1 / L2 mobility procedures. The UE 115 may receive a first control message that indicates a set of mobility parameters for a lower layer handover procedure (e.g., an L1 or L2 handover procedure). In some cases, the UE 115 may receive a second control message that indicates a first reset procedure and a second reset procedure, where the first reset procedure and the second reset procedure indicate respective first and second sets of operating parameters for layers higher than L1 and L2 in the protocol stack. The UE 115 may perform a lower layer handover procedure based on the set of mobility parameters and the first or second set of operating parameters. For example, when performing a handover procedure, the UE 115 may switch from a first serving cell to a second serving cell. Based on whether the first serving cell and the second serving cell are associated with the same DU, the UE 115 may then perform the first reset procedure or the second reset procedure. In this way, the UE 115 may communicate with the second serving cell according to the first or second set of operating parameters based on performing one of the lower layer handover procedure and the reset procedure.

[0093] Figure 2 An example of a network architecture 200 (e.g., a split base station architecture, a split RAN architecture) that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with the core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a through one or more split network entities 105 (e.g., a near RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework) or both). The CU 160-a may communicate with one or more DUs 165-a via a respective midhaul communication link 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via a respective fronthaul communication link 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0094] Each network entity 105 in the network entity 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) providing instructions to the interfaces of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, these network entities 105 may include a wired interface configured to receive signals on a wired transmission medium or transmit signals to one or more of the other network entities 105 on the wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver), configured to receive signals on a wireless transmission medium, transmit signals to one or more of the other network entities 105 on the wireless transmission medium, or both.

[0095] In some examples, the CU 160-a may host one or more higher-layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 160-a. The CU 160-a may be configured to handle user-plane functionality (e.g., CU-UP), control-plane functionality (e.g., CU-CP), or a combination thereof. In some examples, the CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bi-directionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 160-a may be implemented to communicate with the DU 165-a for network control and signaling.

[0096] The DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, the DU 165-a may host at least in part one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation, and demodulation, etc.), at least in part depending on the functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, the DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by the DU 165-a or with control functions hosted by the CU 160-a.

[0097] In some examples, the lower layer functionality may be implemented by one or more RUs 170-a. For example, an RU 170-a controlled by the DU 165-a may correspond to a logical node that hosts at least in part an RF processing function or a low PHY layer function (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both, at least in part based on the functional split (such as a lower layer functional split). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communication with one or more UEs 115-a. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0098] The SMO 180-a can be configured to support the RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., the O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate the virtualized network entity 105). Such virtualized network entities 105 can include, but are not limited to, the CU 160-a, the DU 165-a, the RU 170-a, and the near-RTRIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some specific implementations, the SMO 180-a can communicate directly with one or more RUs 170-a via the O1 interface. The SMO 180-a can also include a non-RT RIC 175-a, which is configured to support the functionality of the SMO 180-a.

[0099] The non-RT RIC 175-a can be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based steering of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via the A1 interface). The near-RT RIC 175-b can be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) that connects one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b.

[0100] In some examples, to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received at the SMO 180-a or the non-RT RIC 175-a from non-network data sources or from network functions. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or an ML model to perform corrective actions via the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of RAN management policies such as A1 policies.

[0101] The network architecture 200 may utilize a modified higher-layer reconfiguration procedure to support L1 / L2 mobility procedures. The UE 115-a may receive (e.g., from the CU 160-a, DU 165-a, RU 170-a) a first control message that indicates a set of mobility parameters for a lower-layer handover procedure (e.g., an L1 or L2 handover procedure). In some cases, the UE 115-a may receive (e.g., from the CU 160-a, DU 165-a, RU 170-a) a second control message that indicates a first reset procedure and a second reset procedure, where the first reset procedure and the second reset procedure indicate respective first and second sets of operating parameters for layers higher than L1 and L2 in the protocol stack. The UE 115-a may perform the lower-layer handover procedure based on the set of mobility parameters and the first or second set of operating parameters. For example, when performing a handover procedure, the UE 115-a may switch from a first serving cell to a second serving cell. Based on whether the first serving cell and the second serving cell are associated with the same DU 165-a, the UE 115-a may then perform the first reset procedure or the second reset procedure. In this way, the UE 115-a may communicate with the second serving cell according to the first or second set of operating parameters based on performing one of the lower-layer handover procedure and the reset procedure.

[0102] Figure 3Illustrated is an example of a wireless communication system 300 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. In some examples, the wireless communication system 300 may implement aspects of the wireless communication system 100 and the network architecture 200, or may be implemented by aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include a UE 115-b, a CU 160-b, a DU 165-b, and a DU 165-c, which may be examples of the corresponding devices described herein. The CU 160-b and the DU 165 may be components of the network entity 105, a base station, or some other network device as described herein. In some examples, the UE 115-a may perform a lower layer handover procedure between cells of the wireless communication system 300, where the cells may correspond to the DU 165-b or the DU 165-c.

[0103] The wireless communication system 300 may support communication between the UE 115-b and the CU 160-b. For example, the CU 160-b may output control signaling (e.g., RRC signaling) for reception by the UE 115-b. In some examples, the CU 160-b may correspond to multiple DUs 165, including the DU 165-b and the DU 165-c. Additionally, each DU 165 may control, operate, or otherwise support one or more cells. For example, the DU 165-b (e.g., the first DU) may correspond to cell 1, cell 2, and cell 3, and the DU 165-c (e.g., the second DU) may correspond to cell 4, cell 5, cell 6, and cell 7. Additionally, cell 2 may include cell 2', cell 3 may include cell 3', cell 4 may include cell 4', and cell 5 may include cell 5', which may represent the CA deployment of the corresponding cells. In some cases, a given set of cells in a CA deployment (e.g., cell 5 and 5') may include a certain number (N) of component carriers.

[0104] In some cases, a cell (e.g., serving cell), DU 165, and CU 160 may be configured for L1 / L2 mobility such that UE 115-b (mobile radio device) can perform a handover process as UE 115-b moves throughout the coverage area or zone supported by wireless communication system 300. For example, CU 160-b may output RRC signaling to UE 115-b configuring a set of cells (e.g., cell 1, cell 2 and 2', cell 3 and 3', cell 4 and 4', cell 5 and 5', cell 6 and cell 7) for L1 / L2 mobility, and the set of cells may be referred to as L1 / L2 configured cell set 305. In some examples, wireless communication system 300 may include an active cell set 310-a supported by DU 165-a and an active cell set 310-b supported by DU 165-b. Each active cell set 310 may include a group of cells that are activated for communication with UE 115-b and managed via L1 / L2 signaling. For example, cells 2, 2', 3, and 3' in active cell set 310-a may be used for control and data communication between UE 115-b and CU 160-b via DU 165-b, and cells 4, 4', 5, 5', and 6 in active cell set 310-b may be used for control and data communication between UE 115-b and CU 160-b via DU 165-c. Either active cell set 310-a or active cell set 310-b may be activated at any given time.

[0105] In some examples, UE 115-b may use a set of mobility parameters to perform a lower layer (e.g., L1 or L2) handover process in wireless communication system 300. UE 115-b may receive a first control message that indicates a set of mobility parameters associated with the L1 or L2 handover process. For example, the first control message may include RRC signaling. That is, UE 115-b may receive an indication of some form of configuration for L1 / L2 mobility. In some examples, the set of mobility parameters may indicate one or more serving cells of UE 115-b (e.g., cells 1 to 7) and one or more corresponding DUs (e.g., DU 165-b and DU 165-c).

[0106] In addition, UE 115-b may receive a second control message that indicates one of a first reset procedure for a lower layer handover procedure or a second reset procedure for a lower layer handover procedure. In some cases, the second control message may be the same or different RRC signaling as the first control message. The first reset procedure may indicate a first set of operating parameters for layers in the protocol stack of the cell that are higher than L1 or L2, and the second reset procedure may indicate a second set of operating parameters for the higher layers. For example, the higher layers may include the MAC layer, the RLC layer, the PDCP layer, or any other layer in the protocol stack that is higher than L1 or L2. In some examples, the first reset procedure and the second reset procedure may correspond to some form of RRC reconfiguration procedure with a synchronization function and may reconfigure (e.g., reset) one or more higher layers of the serving cell during the L1 / L2 mobility procedure.

[0107] UE 115-b may be connected to a serving cell in the set of active cells 310-a. For example, UE 115-b may communicate with cell 2 and cell 2' in a CA scenario. In some cases, UE 115-b may perform a lower layer handover procedure based on a set of mobility parameters and one of the first reset procedure or the second reset procedure. Based on performing the handover procedure, UE 115-b may switch from a first serving cell to a second serving cell during the L1 / L2 mobility procedure within the DU. For example, UE115-b may switch from cell 2 to cell 3. Since cell 2 and cell 3 correspond to the same DU 165 (e.g., DU 165-b) and thus correspond to the same higher layers, UE 115-b may perform the first reset procedure after switching to cell 2.

[0108] In some examples, the first reset procedure may include applying a first set of operation parameters to cell 3 (e.g., the second serving cell), where UE 115-b may have previously applied the first set of operation parameters to the first serving cell. That is, based on receiving second control signaling indicating the first reset procedure, UE 115-b may avoid performing any MAC reset or other reconfiguration procedures with synchronization functions on higher layers in the protocol stack of the second serving cell. In this way, UE 115-b can communicate with the second serving cell (e.g., cell 3) according to the first set of operation parameters without resetting the higher layers in the protocol stack. UE 115-b may avoid applying any RRC reconfiguration procedures with synchronization functions to the second serving cell and may communicate with the second serving cell according to the first set of operation parameters and using the original L1 / L2 mobility configuration (e.g., a set of mobility parameters) indicated in the first control message. In some cases, if the second serving cell (e.g., cell 2) is the SpCell of UE 115-b, UE 115-b may still apply the SpCell configuration to the second serving cell based on switching to the second serving cell without reconfiguring the higher layers.

[0109] Alternatively, UE 115-b may perform a lower layer handover procedure and handover from the first serving cell (cell 2) to a second serving cell in a different set of active cells 310. For example, UE 115-b may handover from cell 2 in the set of active cells 310-a to cell 4 in the set of active cells 310-b, where cell 2 corresponds to DU 165-b and cell 4 corresponds to DU 165-c (e.g., an inter-DU L1 / L2 mobility procedure). Based on the first serving cell and the second serving cell corresponding to different DUs 165 and thus corresponding to different protocol stacks, UE 115-b may perform a second reset procedure after performing the lower layer handover procedure.

[0110] In some examples, the second reset procedure may include performing an RRC reconfiguration procedure with a synchronization function (e.g., soft MAC reset, skipped MAC reset) on one or more higher layers in the protocol stack of the second serving cell. For example, UE 115-b may perform an RRC reconfiguration procedure with a synchronization function for the MAC layer, RLC layer, PDCP layer, or any other layer in the protocol stack higher than L1 or L2. In some cases, the RRC reconfiguration procedure with a synchronization function may include applying a second set of operating parameters to the second serving cell, where the second set of parameters resets a first set of parameters that UE 115-b may have previously applied to the first serving cell. Thus, UE 115-b may communicate with the second serving cell according to the second set of operating parameters, and the second set of operating parameters resets the higher layers in the protocol stack based on the second serving cell corresponding to DU 165-c.

[0111] UE 115-b may use the described techniques in various scenarios. For example, if CU 160-b updates an existing SCell to a target SpCell, UE 115-b may perform the second reset procedure when there is a change in the SpCell at the higher layers in the protocol stack. In some cases, UE 115-b may perform the reset procedure based on a set of mobility parameters, and the set of mobility parameters indicates a set of serving cells and the corresponding DUs 165. For example, UE 115-b may apply the first reset procedure to L1 / L2 mobility within a DU, where there may be only one MAC entity (e.g., the case where UE 115-b switches between serving cells of the same DU 165). Alternatively, UE 115-b may apply the second reset procedure to L1 / L2 mobility between DUs, where there may be multiple MAC entities (e.g., the case where UE 115-b switches between serving cells of different DUs 165). In some examples, UE 115-b may use such reset procedures when connected to multiple TRPs and performing a handover procedure between the multiple TRPs or in any other scenario of L1 / L2 mobility.

[0112] In some cases, UE 115-b may perform a modified (e.g., soft) second reset procedure. For example, UE 115-b may perform a part of the second reset procedure based on switching to a second serving cell associated with a different DU 165 (e.g., switching to cell 4 corresponding to DU 165-c), where this part of the second reset procedure may include resetting the MAC layer in the protocol stack (and maintaining other higher layers). In other cases, UE 115-b may perform a full second reset procedure (e.g., for inter-DU L1 / L2 mobility as described herein), or may avoid performing the second reset procedure and perform the first reset procedure (e.g., for intra-DU L1 / L2 mobility as described herein). In some examples, UE 115-b may implicitly determine whether to perform the first reset procedure or the second reset procedure based on a set of mobility parameters (e.g., L1 / L2 mobility configuration). For example, if the set of mobility parameters indicates that UE 115-b is to switch from a first serving cell associated with DU 165-b to a second serving cell also associated with DU 165-b, then UE 115-b may determine to use the first reset procedure, and if the set of mobility parameters indicates that UE 115-b is the second serving cell associated with DU 165-c, then UE 115-b may determine to use the second reset procedure.

[0113] In some examples, the second control message may include an explicit indication of whether the second reset procedure (e.g., an RRC reconfiguration procedure with a synchronization function) is enabled or disabled. For example, the second control message may be an RRC configuration message including an information element (e.g., soft / skip MAC reset) that may have a value of "enabled" or "disabled" (e.g., ENUMERATED{enabled,disabled}). If the information element is enabled, then UE 115-b may perform the second reset procedure and apply a second set of operation parameters to reset the second serving cell. If the information element is disabled, then UE 115-b may perform the first reset procedure and avoid resetting the operation parameters of the second serving cell. Alternatively, UE 115-b may receive L1 / L2 signaling that explicitly indicates whether UE 115-b is to use the first reset procedure or the second reset procedure. That is, UE 115-b may receive an L1 signal or an L2 signal that enables one of the first reset procedure or the second reset procedure.

[0114] As described herein, UE 115-b can support improved communication with CU 160-b by applying a first reset procedure or a second reset procedure after a lower layer handover procedure. For example, by resetting higher layer operating parameters when UE 115-b switches to a serving cell of the same DU 165, UE 115-b can reduce the interruption to the user plane by skipping some or all of the parts of the MAC reset procedure. In addition, due to continuous data transmission and reduced interruption during the lower layer handover procedure, this can result in improved QoS and increased signaling throughput. In some cases, UE 115-b can improve latency based on a faster SpCell update (compared to an L3 handover that utilizes a full reconfiguration and synchronization procedure) because UE 115-b can avoid resetting the entire protocol stack.

[0115] Figure 4 An example of a process flow 400 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure is illustrated. Process flow 400 may implement aspects of wireless communication system 100 and network architecture 200, or may be implemented by aspects of wireless communication system 100 and network architecture 200. For example, process flow 400 may illustrate operations between UE 115-c and CU 160-c (which may be examples of corresponding devices described herein). In the following description of process flow 400, operations between UE 115-c and CU 160-c may be sent in an order different from the order of the illustrated examples, or operations performed by UE 115-c and CU 160-c may be performed in a different order or at different times. Some operations may also be omitted from process flow 400 and other operations may be added to process flow 400.

[0116] At 405, UE 115-c may receive a first control message (e.g., RRC signaling) that indicates a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure may include one of an L1 handover procedure or an L2 handover procedure. UE 115-c may use the set of mobility parameters to handover between serving cells as it moves throughout the wireless communication system.

[0117] At 410, the UE 115-c may receive a second control message (e.g., RRC signaling) that indicates a first reset procedure for a lower layer handover procedure or a second reset procedure for a lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers in the protocol stack that are higher than L1 or L2, and where the second reset procedure indicates a second set of operating parameters for higher layers. For example, higher layers may include the MAC layer, the RLC layer, or any other layer in the protocol stack that is higher than L1 and L2. In some cases, the first control message and the second control message may be included in the same or different transmissions. In some examples, the second control message may include an information element that indicates whether the second reset procedure is enabled or disabled.

[0118] At 415, the UE 115-c may perform a lower layer handover procedure based on a set of mobility parameters and one of the first reset procedure or the second reset procedure. For example, the UE 115-c may hand over from a first serving cell to a second serving cell as it moves throughout the wireless communication system.

[0119] At 420, the UE 115-c may switch from a first serving cell to a second serving cell based on performing the lower layer handover procedure. In some examples, the first serving cell and the second serving cell may be associated with the same DU, or the first serving cell and the second serving cell may be associated with different DUs. The second serving cell may become the SpCell of the UE 115-c based on the handover.

[0120] At 425, based on switching to a second serving cell that is associated with the same DU as the first serving cell, the UE 115-c may perform the first reset procedure. That is, because the first serving cell and the second serving cell are associated with the same DU and thus with the same protocol stack, the UE 115-c may apply the first set of operating parameters to the second serving cell, where the first set of operating parameters was previously applied to the first serving cell (e.g., the UE 115-c may maintain the same operating parameters for the higher layers in the protocol stack of the second serving cell). In this way, the UE 115-c may communicate with the second serving cell according to the first set of operating parameters.

[0121] At 430, based on a handover to a second serving cell associated with a different DU than the first serving cell, UE 115-c may perform a second reset procedure. That is, because the first serving cell and the second serving cell are associated with different DUs and thus with different protocol stacks, UE 115-c may use a second set of operating parameters to reset the second serving cell as a serving cell, where the first set of operating parameters was previously applied to the first serving cell (e.g., UE 115-c may use different operating parameters to reset the second serving cell). In this way, UE 115-c may communicate with the second serving cell according to the second set of operating parameters.

[0122] Figure 5 FIG. 500 is a block diagram showing a device 505 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. Device 505 may be an example of aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0123] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reconfiguration for lower layer mobility). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or an array of multiple antennas.

[0124] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reconfiguration for lower layer mobility). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or an array of multiple antennas.

[0125] Communication manager 520, receiver 510, transmitter 515, or various combinations thereof or their various components may be examples of components for performing various aspects of reconfiguration for lower layer mobility as described herein. For example, communication manager 520, receiver 510, transmitter 515, or various combinations thereof or components may support methods for performing one or more of the functions described herein.

[0126] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in this disclosure. In some examples, the processor and the memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0127] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices that is configured to or otherwise supports components for performing the functions described in this disclosure.

[0128] In some examples, the communication manager 520 may be configured to use the receiver 510, the transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 520 may receive information from the receiver 510, convey information to the transmitter 515, or integrate with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0129] The communication manager 520 may support wireless communication at a UE in accordance with examples disclosed herein. For example, the communication manager 520 may be configured to or otherwise support components for receiving a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The communication manager 520 may be configured to or otherwise support components for receiving a second control message indicating one of a first reset process for a lower layer handover process or a second reset process for a lower layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than L1 or L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for higher layers. The communication manager 520 may be configured to or otherwise support components for performing a lower layer handover process based on the set of mobility parameters and one of the first reset process or the second reset process.

[0130] By including or configuring a communication manager 520 in accordance with examples described herein, a device 505 (e.g., a processor that controls or otherwise couples to a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for a modified higher layer reconfiguration process for L1 / L2 mobility that may improve QoS, increase signaling throughput, reduce interruptions to the user plane, and reduce latency.

[0131] Figure 6 Block diagram 600 illustrates a device 605 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of the device 505 or UE 115 described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0132] The receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reconfiguration for lower layer mobility). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0133] The transmitter 615 can provide components for transmitting signals generated by other components of the device 605. For example, the transmitter 615 can transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to reconfiguration for lower-layer mobility). In some examples, the transmitter 615 can be co-located with the receiver 610 in a transceiver module. The transmitter 615 can utilize a single antenna or an array of multiple antennas.

[0134] The device 605 or its various components can be examples of components for performing various aspects of reconfiguration for lower-layer mobility as described herein. For example, the communication manager 620 can include a mobility parameter component 625, a reset process component 630, a handover component 635, or any combination thereof. The communication manager 620 can be an example of aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using the receiver 610, the transmitter 615, or both, or otherwise cooperate with them. For example, the communication manager 620 can receive information from the receiver 610, convey information to the transmitter 615, or integrate with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0135] The communication manager 620 can support wireless communication at the UE according to the examples disclosed herein. The mobility parameter component 625 can be configured to or otherwise support a component for receiving a first control message indicating a set of mobility parameters associated with a lower-layer handover process, where the lower-layer handover process includes one of an L1 handover process or an L2 handover process. The reset process component 630 can be configured to or otherwise support a component for receiving a second control message indicating one of a first reset process for a lower-layer handover process or a second reset process for a lower-layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than L1 or L2 in the protocol stack, and where the second reset process indicates a second set of operating parameters for higher layers. The handover component 635 can be configured to or otherwise support a component for performing a lower-layer handover process based on the set of mobility parameters and one of the first reset process or the second reset process.

[0136] Figure 7FIG. 700 is a block diagram illustrating a communication manager 720 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The communication manager 720 may be an example of the communication manager 520, the communication manager 620, or aspects of both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of reconfiguration for lower layer mobility as described herein. For example, the communication manager 720 may include a mobility parameter component 725, a reset procedure component 730, a handover component 735, a handoff component 740, a communication component 745, a reset component 750, a parameter component 755, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0137] The communication manager 720 may support wireless communication at a UE in accordance with examples disclosed herein. The mobility parameter component 725 may be configured to or otherwise support a component for receiving a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure includes one of an L1 handover procedure or an L2 handover procedure. The reset procedure component 730 may be configured to or otherwise support a component for receiving a second control message indicating one of a first reset procedure for a lower layer handover procedure or a second reset procedure for a lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers higher than L1 or L2 in a protocol stack, and where the second reset procedure indicates a second set of operating parameters for higher layers. The handover component 735 may be configured to or otherwise support a component for performing a lower layer handover procedure based on the set of mobility parameters and one of the first reset procedure or the second reset procedure.

[0138] In some examples, the handoff component 740 may be configured to or otherwise support a component for handing off from a first serving cell to a second serving cell based on performing a lower layer handover procedure, where the first serving cell and the second serving cell correspond to the same DU. In some examples, the reset procedure component 730 may be configured to or otherwise support a component for performing the first reset procedure based on handing off to the second serving cell. In some examples, the communication component 745 may be configured to or otherwise support a component for communicating with the second serving cell in accordance with the first set of operating parameters.

[0139] In some examples, to support performing the first reset procedure, the parameter component 755 may be configured to or otherwise support a component for applying the first set of operating parameters to the second serving cell, where the first set of operating parameters was previously applied to the first serving cell.

[0140] In some examples, the parameter component 755 may be configured to or otherwise support components for applying the SpCell configuration to the second serving cell based on a handover to the second serving cell.

[0141] In some examples, the handover component 740 may be configured to or otherwise support components for handing over from a first serving cell associated with a first DU to a second serving cell associated with a second DU based on performing a lower layer handover procedure. In some examples, the reset procedure component 730 may be configured to or otherwise support components for performing a second reset procedure based on a handover to the second serving cell. In some examples, the communication component 745 may be configured to or otherwise support components for communicating with the second serving cell according to a second set of operating parameters.

[0142] In some examples, to support performing the second reset procedure, the parameter component 755 may be configured to or otherwise support components for applying a second set of operating parameters to the second serving cell, where the second set of operating parameters resets a first set of operating parameters previously applied to the first serving cell.

[0143] In some examples, to support performing the second reset procedure, the reset procedure component 730 may be configured to or otherwise support components for performing a part of the second reset procedure based on a handover to the second serving cell, where the part of the second reset procedure includes resetting the MAC layer in the protocol stack.

[0144] In some examples, to support receiving a second control message, the reset procedure component 730 may be configured to or otherwise support components for receiving an information element indicating that the second reset procedure is enabled or disabled.

[0145] In some examples, to support receiving a second control message, the reset procedure component 730 may be configured to or otherwise support components for receiving an L1 signal or an L2 signal enabling one of the first reset procedure or the second reset procedure.

[0146] In some examples, the reset component 750 may be configured to or otherwise support components for performing the first reset procedure or the second reset procedure at least partially based on a set of mobility parameters. In some examples, the set of mobility parameters indicates one or more serving cells of the UE and one or more corresponding DUs.

[0147] Figure 8FIG. 800 shows a system 800 including a device 805 that supports reconfiguration for lower layer mobility, in accordance with one or more aspects of the present disclosure. Device 805 may be an example of, or include components of, device 505, device 605, or UE 115 as described herein. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for two-way voice and data communication, including components for sending and receiving communications, such as communication manager 820, input / output (I / O) controller 810, transceiver 815, antenna 825, memory 830, code 835, and processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0148] I / O controller 810 may manage input and output signals of device 805. I / O controller 810 may also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent, or interact with, a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor (such as processor 840). In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0149] In some cases, device 805 may include a single antenna 825. However, in some other cases, device 805 may have more than one antenna 825, which may be capable of concurrently sending or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links, as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be examples of, or include components of, transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof as described herein.

[0150] The memory 830 may include a random access memory (RAM) and a read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform the various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as the system memory or another type of memory. In some cases, the code 835 may not be directly executable by the processor 840 but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 830 may also contain a basic input / output system (BIOS) that may control basic hardware or software operations such as interactions with peripheral components or devices.

[0151] The processor 840 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., support functions or tasks for reconfiguration for lower-layer mobility). For example, the device 805 or components of the device 805 may include the processor 840 and the memory 830 coupled or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0152] The communication manager 820 may support wireless communication at the UE according to the examples disclosed herein. For example, the communication manager 820 may be configured as or otherwise support a component for receiving a first control message indicating a set of mobility parameters associated with a lower-layer handover process, where the lower-layer handover process includes one of an L1 handover process or an L2 handover process. The communication manager 820 may be configured as or otherwise support a component for receiving a second control message indicating one of a first reset process for a lower-layer handover process or a second reset process for a lower-layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than L1 or L2 in the protocol stack, and where the second reset process indicates a second set of operating parameters for higher layers. The communication manager 820 may be configured as or otherwise support a component for performing a lower-layer handover process based on the set of mobility parameters and one of the first reset process or the second reset process.

[0153] By including or configuring a communication manager 820 according to an example as described herein, the device 805 may support techniques for a modified higher layer reconfiguration process for L1 / L2 mobility, which may improve QoS, increase signaling throughput, reduce interruption to the user plane, and reduce latency.

[0154] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in conjunction with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that, when executed by the processor 840, cause the device 805 to perform various aspects of reconfiguration for lower layer mobility as described herein, or the processor 840 and the memory 830 may otherwise be configured to perform or support such operations.

[0155] Figure 9 A block diagram 900 of a device 905 supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a CU as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0156] The receiver 910 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0157] The transmitter 915 can provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 905. For example, the transmitter 915 can output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 can support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 915 can support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 can be co-located in a transceiver, which can include a modem or be coupled to a modem.

[0158] The communication manager 920, the receiver 910, the transmitter 915, or various combinations or various components thereof can be examples of components for performing aspects of the reconfiguration for lower layer mobility as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can support methods for performing one or more of the functions described herein.

[0159] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA, or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and the memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0160] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices configured to or otherwise supporting components for performing the functions described in this disclosure.

[0161] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 920 may receive information from the receiver 910, convey information to the transmitter 915, or integrate with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0162] For example, the communication manager 920 may be configured to or otherwise support a component for outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The communication manager 920 may be configured to or otherwise support a component for outputting a second control message indicating one of a first reset process for a lower layer handover process or a second reset process for a lower layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than L1 and L2 in a protocol stack, and where the second reset process indicates a second set of operating parameters for higher layers.

[0163] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (e.g., a processor that controls or otherwise couples with the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) may support techniques for a modified higher layer reconfiguration process for L1 / L2 mobility that may improve QoS, increase signaling throughput, reduce interruptions to the user plane, and reduce latency.

[0164] Figure 10 Block diagram 1000 illustrates a device 1005 supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the device 905 or the CU 160 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0165] The receiver 1010 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0166] The transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0167] The device 1005 or its various components may be examples of components for performing various aspects of the reconfiguration for lower layer mobility as described herein. For example, the communication manager 1020 may include a handover process component 1025, an operating parameter component 1030, or any combination thereof. The communication manager 1020 may be an example of aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, convey information to the transmitter 1015, or integrate with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0168] The handover process component 1025 can be configured to or otherwise support a component for outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The operation parameter component 1030 can be configured to or otherwise support a component for outputting a second control message indicating one of a first reset process for a lower layer handover process or a second reset process for a lower layer handover process, where the first reset process indicates a first set of operation parameters for layers higher than L1 and L2 in a protocol stack, and where the second reset process indicates a second set of operation parameters for higher layers.

[0169] Figure 11 FIG. 1100 is a block diagram showing a communication manager 1120 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The communication manager 1120 can be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components can be examples of components for performing various aspects of reconfiguration for lower layer mobility as described herein. For example, the communication manager 1120 can include a handover process component 1125, an operation parameter component 1130, a serving cell component 1135, an information element component 1140, or any combination thereof. Each of these components can communicate directly or indirectly with each other (e.g., via one or more buses).

[0170] The handover process component 1125 can be configured to or otherwise support a component for outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The operation parameter component 1130 can be configured to or otherwise support a component for outputting a second control message indicating one of a first reset process for a lower layer handover process or a second reset process for a lower layer handover process, where the first reset process indicates a first set of operation parameters for layers higher than L1 and L2 in a protocol stack, and where the second reset process indicates a second set of operation parameters for higher layers.

[0171] In some examples, the serving cell component 1135 can be configured to or otherwise support a component for communicating with a UE via a serving cell according to a first set of operation parameters.

[0172] In some examples, the serving cell component 1135 can be configured to or otherwise support a component for communicating with a UE via a serving cell according to a second set of operation parameters.

[0173] In some examples, to support outputting a second control message, the information element component 1140 may be configured to or otherwise support a component for outputting an information element indicating that a second reset process is enabled or disabled.

[0174] In some examples, to support outputting a second control message, the operation parameter component 1130 may be configured to or otherwise support a component for outputting a second control message indicating a first reset process and a second reset process. In some examples, a set of mobility parameters indicates one or more serving cells of a UE and one or more corresponding DUs.

[0175] Figure 12 A diagram of a system 1200 including a device 1205 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure is shown. The device 1205 may be an example of or include components of the device 905, the device 1005, or the CU as described herein. The device 1205 may include components for two-way voice and data communication, which include components for sending and receiving communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may be electronically communicated or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled via one or more buses (e.g., bus 1240).

[0176] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmitting operations or output operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components that are operable to perform the following operations: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235, or memory 1225, or both) may be included in a chip or chip component installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0177] The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform the various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by the processor 1235 but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1225 may contain a BIOS and the like, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0178] Processor 1235 may include intelligent hardware devices (e.g., general-purpose processor, DSP, ASIC, CPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., support functions or tasks for reconfiguration for lower-layer mobility). For example, device 1205 or components of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and processor 1235 and memory 1225 are configured to perform the various functions described herein. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functions (e.g., by executing code 1230) to perform the functions of device 1205. Processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within memory 1225). In some specific implementations, processor 1235 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process these inputs to produce outputs (which may be passed to other systems or components such as device 1205, for example). For example, the processing system of device 1205 may refer to a system that includes various other components or sub-components of device 1205, such as processor 1235, or transceiver 1210, or communication manager 1220, or a combination of other components or components of device 1205. The processing system of device 1205 may interface with other components of device 1205 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, and other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter such that device 1205 may transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver such that the device 1205 may obtain information or signal inputs and the information may be passed to the processing system. Those of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal inputs and the second interface may also output information or signal outputs.

[0179] In some examples, the bus 1240 may support communication within a protocol layer (e.g., within a protocol layer) in a protocol stack. In some examples, the bus 1240 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers in a protocol stack), which may include communication performed within components of the device 1205 or between different components of the device 1205 that may be co-located or located at different locations (e.g., where the device 1205 may refer to a system in which one or more of the communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one component or divided among different components).

[0180] In some examples, the communication manager 1220 may manage (e.g., via one or more wired or wireless backhaul links) aspects of communication with the core network 130. For example, the communication manager 1220 may manage the delivery of data communication for client devices such as one or more UEs 115. In some examples, the communication manager 1220 may manage communication with other network entities 105 and may include a controller or scheduler for collaboratively controlling communication with the UEs 115 with other network entities 105. In some examples, the communication manager 1220 may support the X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0181] For example, the communication manager 1220 may be configured or otherwise support a component for outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The communication manager 1220 may be configured or otherwise support a component for outputting a second control message indicating one of a first reset process for a lower layer handover process or a second reset process for a lower layer handover process, where the first reset process indicates a first set of operating parameters for layers in the protocol stack higher than L1 and L2, and where the second reset process indicates a second set of operating parameters for higher layers.

[0182] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 may support techniques for a modified higher layer reconfiguration process for L1 / L2 mobility, which may improve QoS, increase signaling throughput, reduce interruptions to the user plane, and reduce latency.

[0183] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof or otherwise in cooperation with them. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transmitter 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions that can be executed by the processor 1235 to cause the device 1205 to perform various aspects of reconfiguration for lower layer mobility as described herein, or the processor 1235 and the memory 1225 may otherwise be configured to perform or support such operations.

[0184] Figure 13 A flowchart illustrating a method 1300 that supports reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure is shown. Operations of the method 1300 may be implemented by a UE or components thereof as described herein. For example, operations of the method 1300 may be performed by a UE 115 as described with reference to Figures 1 to 8 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0185] At 1305, the method may include: receiving a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The operation of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1305 may be performed by a mobility parameter component 725 as described with reference to Figure 7 described.

[0186] At 1310, the method may include: receiving a second control message indicating one of a first reset procedure for a lower layer handover procedure or a second reset procedure for a lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers in the protocol stack higher than L1 or L2, and where the second reset procedure indicates a second set of operating parameters for higher layers. The operations at 1310 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1310 may be performed by a reset procedure component 730 as described with reference to Figure 7 The reset procedure component 730 described.

[0187] At 1315, the method may include: performing a lower layer handover procedure based on a set of mobility parameters and one of the first reset procedure or the second reset procedure. The operations at 1315 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1315 may be performed by a handover component 735 as described with reference to Figure 7 The handover component 735 described.

[0188] Figure 14 FIG. shows a flow diagram of a method 1400 supporting reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The operations of method 1400 may be implemented by a UE or its components as described herein. For example, the operations of method 1400 may be performed by a UE 115 as described with reference to Figures 1 to 8 The UE 115 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0189] At 1405, the method may include: receiving a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure includes one of an L1 handover procedure or an L2 handover procedure. The operations at 1405 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1405 may be performed by a mobility parameter component 725 as described with reference to Figure 7 The mobility parameter component 725 described.

[0190] At 1410, the method may include: receiving a second control message indicating one of a first reset procedure for a lower layer handover procedure or a second reset procedure for a lower layer handover procedure, where the first reset procedure indicates a first set of operating parameters for layers in the protocol stack higher than L1 or L2, and where the second reset procedure indicates a second set of operating parameters for higher layers. The operations at 1410 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1410 may be performed by a reset procedure component 730 as described with reference to Figure 7 The reset procedure component 730 described.

[0191] At 1415, the method may include: performing a lower layer handover procedure based on a set of mobility parameters and one of a first reset procedure or a second reset procedure. The operations at 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1415 may be performed by a handover component 735 as described in reference Figure 7 described.

[0192] At 1420, the method may include: switching from a first serving cell to a second serving cell based on performing the lower layer handover procedure, where the first serving cell and the second serving cell correspond to the same DU. The operations at 1420 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1420 may be performed by a handover component 740 as described in reference Figure 7 described.

[0193] At 1425, the method may include: performing a first reset procedure based on switching to the second serving cell. The operations at 1425 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1425 may be performed by a reset procedure component 730 as described in reference Figure 7 described.

[0194] At 1430, the method may include: applying a first set of operating parameters to the second serving cell, where the first set of operating parameters was previously applied to the first serving cell. The operations at 1430 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1430 may be performed by a parameter component 755 as described in reference Figure 7 described.

[0195] At 1435, the method may include: communicating with the second serving cell according to the first set of operating parameters. The operations at 1435 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1435 may be performed by a communication component 745 as described in reference Figure 7 described.

[0196] Figure 15 FIG. shows a flowchart of a method 1500 that illustrates support for reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The operations of method 1500 may be implemented by a UE or its components as described herein. For example, the operations of method 1500 may be performed by a UE 115 as described in reference Figures 1 to 8 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0197] At 1505, the method may include: receiving a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, where the lower layer handover procedure includes one of an L1 handover procedure or an L2 handover procedure. The operation at 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1505 may be performed by a mobility parameter component 725 as described with reference to Figure 7 described.

[0198] At 1510, the method may include: receiving a second control message indicating one of a first reset procedure for a lower layer handover procedure or a second reset procedure for a lower layer handover procedure, where the first reset procedure indicates a first set of operation parameters for layers higher than L1 or L2 in a protocol stack, and where the second reset procedure indicates a second set of operation parameters for higher layers. The operation at 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1510 may be performed by a reset procedure component 730 as described with reference to Figure 7 described.

[0199] At 1515, the method may include: performing a lower layer handover procedure based on the set of mobility parameters and one of the first reset procedure or the second reset procedure. The operation at 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1515 may be performed by a handover component 735 as described with reference to Figure 7 described.

[0200] At 1520, the method may include: switching from a first serving cell associated with a first DU to a second serving cell associated with a second DU based on performing the lower layer handover procedure. The operation at 1520 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1520 may be performed by a handover component 740 as described with reference to Figure 7 described.

[0201] At 1525, the method may include: performing a second reset procedure based on switching to the second serving cell. The operation at 1525 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1525 may be performed by a reset procedure component 730 as described with reference to Figure 7 described.

[0202] At 1530, the method may include: applying a second set of operation parameters to the second serving cell, where the second set of operation parameters resets a first set of operation parameters previously applied to the first serving cell. The operation at 1530 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1530 may be performed by a parameter component 755 as described with reference to Figure 7 described.

[0203] At 1535, the method may include: communicating with a second serving cell based on a second set of operation parameters. The operation at 1535 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1535 may be performed by a communication component 745 as described with reference to Figure 7 the description.

[0204] Figure 16 FIG. shows a flowchart of a method 1600 that illustrates support for reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The operations of method 1600 may be implemented by a CU or its components as described herein. For example, the operations of method 1600 may be performed by a CU as described with reference to Figures 1 to 4 and Figures 9 to 12 the description. In some examples, the CU may execute an instruction set to control the functional elements of the CU to perform the described functions. Additionally or alternatively, the CU may use dedicated hardware to perform aspects of the described functions.

[0205] At 1605, the method may include: outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The operation at 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1605 may be performed by a handover process component 1125 as described with reference to Figure 11 the description.

[0206] At 1610, the method may include: outputting a second control message indicating one of a first reset process for a lower layer handover process or a second reset process for a lower layer handover process, where the first reset process indicates a first set of operation parameters for layers higher than L1 and L2 in a protocol stack, and where the second reset process indicates a second set of operation parameters for higher layers. The operation at 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1610 may be performed by an operation parameter component 1130 as described with reference to Figure 11 the description.

[0207] Figure 17 FIG. shows a flowchart of a method 1700 that illustrates support for reconfiguration for lower layer mobility in accordance with one or more aspects of the present disclosure. The operations of method 1700 may be implemented by a CU or its components as described herein. For example, the operations of method 1700 may be performed by a CU as described with reference to Figures 1 to 4 and Figures 9 to 12Described CU execution. In some examples, the CU may execute an instruction set to control the functional elements of the CU to perform the described functions. Additionally or alternatively, the CU may use dedicated hardware to perform aspects of the described functions.

[0208] At 1705, the method may include: outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process. The operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1705 may be performed by the handover process component 1125 as described with reference to Figure 11 the described handover process component 1125.

[0209] At 1710, the method may include: outputting an information element indicating that a second reset process for a lower layer handover process is enabled or disabled, where the second reset process indicates a second set of operation parameters for layers higher than L1 and L2 in the protocol stack. The operation of 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be performed by the information element component 1140 as described with reference to Figure 11 the described information element component 1140.

[0210] An overview of aspects of the present disclosure is provided below:

[0211] Aspect 1: A method for wireless communication at a UE, the method including: receiving a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of an L1 handover process or an L2 handover process; receiving a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operation parameters for layers higher than L1 or L2 in the protocol stack, where the second reset process indicates a second set of operation parameters for the higher layers; and performing the lower layer handover process at least in part based on the set of mobility parameters and one of the first reset process or the second reset process.

[0212] Aspect 2: The method according to aspect 1, the method further including: switching from a first serving cell to a second serving cell at least in part based on performing the lower layer handover process, where the first serving cell and the second serving cell correspond to the same DU; performing the first reset process at least in part based on switching to the second serving cell; and communicating with the second serving cell according to the first set of operation parameters.

[0213] Aspect 3: The method according to aspect 2, wherein performing the first reset process includes: applying the first set of operating parameters to the second serving cell, wherein the first set of operating parameters was previously applied to the first serving cell.

[0214] Aspect 4: The method according to any one of aspects 2 to 3, the method further comprising: applying SpCell configuration to the second serving cell at least in part based on a handover to the second serving cell.

[0215] Aspect 5: The method according to any one of aspects 1 to 4, the method further comprising: switching from a first serving cell associated with a first DU to a second serving cell associated with a second DU at least in part based on performing the lower layer handover process; performing the second reset process at least in part based on a handover to the second serving cell; and communicating with the second serving cell according to the second set of operating parameters.

[0216] Aspect 6: The method according to aspect 5, wherein performing the second reset process includes: applying the second set of operating parameters to the second serving cell, wherein the second set of operating parameters resets the first set of operating parameters previously applied to the first serving cell.

[0217] Aspect 7: The method according to any one of aspects 5 to 6, wherein performing the second reset process includes: performing a part of the second reset process at least in part based on a handover to the second serving cell, wherein the part of the second reset process includes resetting the MAC layer in the protocol stack.

[0218] Aspect 8: The method according to any one of aspects 1 to 7, wherein receiving the second control message includes: receiving an information element indicating that the second reset process is enabled or disabled.

[0219] Aspect 9: The method according to any one of aspects 1 to 8, wherein receiving the second control message includes: receiving an L1 signal or an L2 signal enabling one of the first reset process or the second reset process.

[0220] Aspect 10: The method according to any one of aspects 1 to 9, the method further comprising: performing the first reset process or the second reset process at least in part based on the set of mobility parameters.

[0221] Aspect 11: The method according to aspect 10, wherein the set of mobility parameters indicates one or more serving cells of the UE and one or more corresponding DUs.

[0222] Aspect 12: A method for wireless communication at a Central Unit (CU), the method comprising: outputting a first control message indicating a set of mobility parameters associated with a lower layer handover process, wherein the lower layer handover process includes one of an L1 handover process or an L2 handover process; and outputting a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, wherein the first reset process indicates a first set of operating parameters for L1 and higher layers in a protocol stack, and wherein the second reset process indicates a second set of operating parameters for the higher layers.

[0223] Aspect 13: The method according to aspect 12, the method further comprising: communicating with a UE via a serving cell according to the first set of operating parameters.

[0224] Aspect 14: The method according to any one of aspects 12 to 13, the method further comprising: communicating with a UE via a serving cell according to the second set of operating parameters.

[0225] Aspect 15: The method according to any one of aspects 12 to 14, wherein outputting the second control message comprises: outputting an information element indicating that the second reset process is enabled or disabled.

[0226] Aspect 16: The method according to any one of aspects 12 to 15, wherein outputting the second control message comprises: outputting the second control message indicating the first reset process and the second reset process.

[0227] Aspect 17: The method according to any one of aspects 12 to 16, wherein the set of mobility parameters indicates one or more serving cells of a UE and one or more corresponding DUs.

[0228] Aspect 18: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 11.

[0229] Aspect 19: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 11.

[0230] Aspect 20: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0231] Aspect 21: An apparatus, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 12 to 17.

[0232] Aspect 22: An apparatus, the apparatus comprising: at least one component for performing the method according to any one of Aspects 12 to 17.

[0233] Aspect 23: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of Aspects 12 to 17.

[0234] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified and other specific implementations are also possible. In addition, aspects from two or more methods can be combined.

[0235] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques can be applied to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0236] The information and signals described herein can be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0237] The various illustrative blocks and components described in this disclosure can be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0238] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software, hardware, firmware, hardwiring, or any combination of these. The features implementing the functions can also be physically located at different positions, including being distributed such that different portions of the functions are implemented at different physical locations.

[0239] Computer-readable media includes both non-transitory computer storage media and communication media, which includes any medium that facilitates transfer of a computer program from one location to another. Non-transitory storage media can be any available media that can be accessed by a general or special purpose computer. By way of example and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general or special purpose computer or a general or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks can reproduce data magnetically, while discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0240] As used herein, including in the claims, the "or" used in a list of items (e.g., a list of items accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0241] The term "determine" encompasses a variety of actions, and thus, "determine" can include operations such as calculating, computing, processing, deriving, researching, looking up (such as looking up in a table, database, or other data structure), ascertaining, and similar actions. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Further, "determine" can include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0242] In the figures, similar components or features may have the same reference numeral. Additionally, various components of the same type can be distinguished by adding a dash and a second label used to differentiate between similar components after the reference numeral. If only the first reference numeral is used in the specification, the description can apply to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0243] The description set forth herein in conjunction with the figures describes example configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". The detailed description includes specific details for providing an understanding of the described techniques. However, the techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0244] The description provided herein enables a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure are apparent to a person of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a User Equipment (UE), the method comprising: Receiving a first control message indicating a set of mobility parameters associated with a lower layer handover process, wherein the lower layer handover process includes one of a layer 1 handover process or a layer 2 handover process; Receiving a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, wherein the first reset process indicates a first set of operating parameters for layers higher than layer 1 or layer 2 in a protocol stack, and wherein the second reset process indicates a second set of operating parameters for the higher layer; And Performing the lower layer handover process at least in part based on the set of mobility parameters and one of the first reset process or the second reset process.

2. The method according to claim 1, the method further comprising: Switching from a first serving cell to a second serving cell at least in part based on performing the lower layer handover process, wherein the first serving cell and the second serving cell correspond to the same distributed unit; Performing the first reset process at least in part based on switching to the second serving cell; And Communicating with the second serving cell according to the first set of operating parameters.

3. The method according to claim 2, wherein performing the first reset process comprises: Applying the first set of operating parameters to the second serving cell, wherein the first set of operating parameters was previously applied to the first serving cell.

4. The method according to claim 2, the method further comprising: Applying a secondary primary cell configuration to the second serving cell at least in part based on switching to the second serving cell.

5. The method according to claim 1, the method further comprising: Switching from a first serving cell associated with a first distributed unit to a second serving cell associated with a second distributed unit at least in part based on performing the lower layer handover process; Performing the second reset process at least in part based on switching to the second serving cell; And Communicating with the second serving cell according to the second set of operating parameters.

6. The method according to claim 5, wherein performing the second reset process comprises: Applying the second set of operating parameters to the second serving cell, wherein the second set of operating parameters resets the first set of operating parameters previously applied to the first serving cell.

7. The method according to claim 5, wherein performing the second reset process comprises: Performing a part of the second reset process at least in part based on switching to the second serving cell, wherein the part of the second reset process includes resetting a medium access control layer in the protocol stack.

8. The method according to claim 1, wherein receiving the second control message comprises: Receiving an information element indicating that the second reset process is enabled or disabled.

9. The method according to claim 1, wherein receiving the second control message comprises: Receive a layer 1 signal or a layer 2 signal enabling one of the first reset procedure or the second reset procedure.

10. The method according to claim 1, the method further comprising: Performing the first reset procedure or the second reset procedure at least in part based on the set of mobility parameters.

11. The method according to claim 10, wherein the set of mobility parameters indicates one or more serving cells of the UE and one or more corresponding distributed units.

12. A method for wireless communication at a central unit (CU), the method comprising: Outputting a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, wherein the lower layer handover procedure comprises one of a layer 1 handover procedure or a layer 2 handover procedure; And Outputting a second control message indicating one of a first reset procedure for the lower layer handover procedure or a second reset procedure for the lower layer handover procedure, wherein the first reset procedure indicates a first set of operating parameters for layers higher than layer 1 and layer 2 in the protocol stack, and wherein the second reset procedure indicates a second set of operating parameters for the higher layers.

13. The method according to claim 12, the method further comprising: Communicating with a user equipment (UE) via a serving cell according to the first set of operating parameters.

14. The method according to claim 12, the method further comprising: Communicating with the UE via the serving cell according to the second set of operating parameters.

15. The method according to claim 12, wherein outputting the second control message comprises: Outputting an information element indicating that the second reset procedure is enabled or disabled.

16. The method according to claim 12, wherein outputting the second control message comprises: Outputting the second control message indicating the first reset procedure and the second reset procedure.

17. The method according to claim 12, wherein the set of mobility parameters indicates one or more serving cells of the UE and one or more corresponding distributed units.

18. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: A processor; A memory coupled to the processor; And Instructions stored in the memory and executable by the processor to cause the apparatus to: Receive a first control message indicating a set of mobility parameters associated with a lower layer handover procedure, wherein the lower layer handover procedure comprises one of a layer 1 handover procedure or a layer 2 handover procedure; Receive a second control message indicating one of a first reset procedure for the lower layer handover procedure or a second reset procedure for the lower layer handover procedure, wherein the first reset procedure indicates a first set of operating parameters for layers higher than layer 1 or layer 2 in the protocol stack, wherein the second reset procedure indicates a second set of operating parameters for the higher layers; And Perform the lower layer handover procedure at least partially based on the set of mobility parameters and one of the first reset procedure or the second reset procedure.

19. The apparatus according to claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: Switch from a first serving cell to a second serving cell at least partially based on performing the lower layer handover procedure, wherein the first serving cell and the second serving cell correspond to the same distributed unit; Perform the first reset procedure at least partially based on switching to the second serving cell; And Communicate with the second serving cell according to the first set of operation parameters.

20. The apparatus according to claim 19, wherein the instructions for performing the first reset procedure are executable by the processor to cause the apparatus to: Apply the first set of operation parameters to the second serving cell, wherein the first set of operation parameters was previously applied to the first serving cell.

21. The apparatus according to claim 19, wherein the instructions are further executable by the processor to cause the apparatus to: Apply a secondary primary cell configuration to the second serving cell at least partially based on switching to the second serving cell.

22. The apparatus according to claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: Switch from a first serving cell associated with a first distributed unit to a second serving cell associated with a second distributed unit at least partially based on performing the lower layer handover procedure; Perform the second reset procedure at least partially based on switching to the second serving cell; And Communicate with the second serving cell according to the second set of operation parameters.

23. The apparatus according to claim 22, wherein the instructions for performing the second reset procedure are executable by the processor to cause the apparatus to: Apply the second set of operation parameters to the second serving cell, wherein the second set of operation parameters resets the first set of operation parameters previously applied to the first serving cell.

24. The apparatus according to claim 22, wherein the instructions for performing the second reset procedure are executable by the processor to cause the apparatus to: Perform a part of the second reset procedure at least partially based on switching to the second serving cell, wherein the part of the second reset procedure includes resetting the media access control layer in the protocol stack.

25. The apparatus according to claim 18, wherein the instructions for receiving the second control message are executable by the processor to cause the apparatus to: Receive an information element indicating that the second reset procedure is enabled or disabled.

26. The apparatus according to claim 18, wherein the instructions for receiving the second control message are executable by the processor to cause the apparatus to: Receive a layer 1 signal or a layer 2 signal enabling one of the first reset procedure or the second reset procedure.

27. An apparatus, the apparatus comprising: A processor; A memory coupled to the processor; and Instructions stored in the memory and executable by the processor to cause the device to: Output a first control message indicating a set of mobility parameters associated with a lower layer handover process, where the lower layer handover process includes one of a layer 1 handover process or a layer 2 handover process; and Output a second control message indicating one of a first reset process for the lower layer handover process or a second reset process for the lower layer handover process, where the first reset process indicates a first set of operating parameters for layers higher than layer 1 and layer 2 in the protocol stack, and where the second reset process indicates a second set of operating parameters for the higher layers.

28. The device according to claim 27, wherein the instructions are further executable by the processor to cause the device to: Communicate with a user equipment (UE) via a serving cell according to the first set of operating parameters.

29. The device according to claim 27, wherein the instructions are further executable by the processor to cause the device to: Communicate with the UE via the serving cell according to the second set of operating parameters.

30. The device according to claim 27, wherein the instructions for outputting the second control message are executable by the processor to cause the device to: Output an information element indicating that the second reset process is enabled or disabled.

Images