Multiplexing of multiple handover commands

Abstract

The present disclosure provides an apparatus, a method, and a computer program product for handover. An example method may include receiving a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission including a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages including a respective group handover configuration in a set of group handover configurations associated with a respective UE in a set of UEs including UEs, the RRC message set is included in a MAC service data unit (SDU) (MAC SDU) set in a medium access control (MAC) protocol data unit (PDU). The example method may also include processing a first subset of the MAC SDUs associated with the UE and discarding a second subset of the MAC SDUs that are not applicable to the UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 806,457, filed on June 10, 2022, entitled “MULTIPLEXINGOF MULTIPLE HANDOVER COMMANDS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to a wireless communication system having a handover mechanism. Background Art

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

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission including a radio resource control (RRC) message set, each RRC message in the RRC message set including a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in a UE set including the UE, the RRC message set being included in a MAC service data unit (SDU) (MAC SDU) set in a medium access control (MAC) protocol data unit (PDU). The memory and the at least one processor coupled to the memory may also be configured to process a first subset of the MAC SDU associated with the UE and discard a second subset of the MAC SDU that is not applicable to the UE, the first subset of the MAC SDU including a common MAC SDU and at least a UE-specific MAC SDU. The memory and the at least one processor coupled to the memory may also be configured to connect to a target network entity based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may also be configured to send a PDCCH transmission associated with a group RNTI for scheduling a PDSCH transmission for a set of UEs, the group RNTI being associated with each UE in the set of UEs. The memory and the at least one processor coupled to the memory may also be configured to send the PDSCH transmission, the PDSCH transmission including an RRC message set, each RRC message in the RRC message set may include a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in the set of UEs, the RRC message set being included in a MAC SDU set in a MAC PDU, the MAC SDU set including a common MAC SDU for the set of UEs and an SDU subset for each corresponding UE in the set of UEs.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features described in full below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

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

[0016] Figure 4 is a diagram illustrating an example wireless communication environment with a satellite.

[0017] Figure 5 is a diagram illustrating an example wireless communication environment with a satellite.

[0018] Figure 6 is a diagram illustrating an example communication flow between a group of UEs and a network entity communicating via a satellite.

[0019] Figure 7 is a diagram illustrating an example MAC PDU.

[0020] Figure 8 is a diagram illustrating example indexing of SDUs.

[0021] Fig. 9 is a diagram illustrating example indexing of SDUs.

[0022] Fig.10 is a diagram illustrating example indexing of SDUs.

[0023] Fig.11 is a flow chart of a method of wireless communication.

[0024] Fig.12 is a flow chart of a method of wireless communication.

[0025] Fig.13 is a flow chart of a method of wireless communication.

[0026] Fig.14 is a flow chart of a method of wireless communication.

[0027] Fig.15 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0028] Fig.16 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0029] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0030] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

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

[0033] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0034] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0035] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0036] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0037] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0038] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0039] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0040] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

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

[0042] The SMO framework 105 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0043] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0044] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0045] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

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

[0047] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

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

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0050] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0051] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0052] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0053] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity processing, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signal can be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or one or more of other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0055] Reference again Figure 1 In some aspects, the UE 104 may include a handover component 198. In some aspects, the handover component 198 may be configured to receive a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission including a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages including a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in a set of UEs including the UE, the set of RRC messages being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU). In some aspects, the handover component 198 may also be configured to process a first subset of MAC SDUs associated with the UE and discard a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs including a common MAC SDU and at least a UE-specific MAC SDU. In some aspects, the handover component 198 may also be configured to connect to a target network entity based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE.

[0056] In certain aspects, the base station 102 may include a handover component 199. In some aspects, the handover component 199 may be configured to send a PDCCH transmission associated with a group RNTI that schedules a PDSCH transmission for a set of UEs, the group RNTI being associated with each UE in the set of UEs. In some aspects, the handover component 199 may also be configured to send a PDSCH transmission that includes a set of RRC messages, each of the RRC messages in the set of RRC messages may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the set of RRC messages being included in a set of MAC SDUs in a MAC PDU, the set of MAC SDUs including a common MAC SDU for the set of UEs and a subset of SDUs for each corresponding UE in the set of UEs.

[0057] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0058] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. As another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first group of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0059] As described herein, different terms may be used in various aspects to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, send, output, transmit, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, transmitted, or sent by the first network node.

[0060] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling).

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

[0062]

[0063] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0064] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

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

[0067] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb teeth. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0068] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

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

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

[0071] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0073] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0074] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0075] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

[0077] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The handover component 198 is used to perform various aspects.

[0078] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The handover component 199 is used to perform various aspects.

[0079] Figure 4 4 is a diagram illustrating an example wireless communication environment with a satellite. Figure 4 4, satellite 402 may be an intermediary for communication between network entity 404A and UE group 408 including one or more UEs 406A, UE 406B, UE 406C, and UE 406D. Four UEs are shown for illustrative purposes. Network entity 404A may send signal encoding data, such as user data or control data for any UE in UE group 408, to satellite 402. Satellite 402 may relay the data to one or more UEs in UE group 408, such as by performing amplification, spatial filtering, or frequency conversion. Any UE in UE group 408 may communicate with network entity 404A by sending signal encoding data (such as user data of the UE) to satellite 402. Satellite 402 may then relay the data to network entity 404A, such as by performing amplification, spatial filtering, or frequency conversion. The communication (i.e., radio link) between network entity 404A and satellite 402 may be referred to as feeder link A. In some aspects, satellite 402 is a transparent satellite configured to perform amplification, spatial filtering, or frequency conversion. In some aspects, satellite 402 is a regenerative satellite that can additionally perform other signal processing (such as decoding, interference cancellation, signal regeneration) for relaying, but does not have the full functionality of a network entity.

[0080] Figure 5 5 is a diagram illustrating an example wireless communication environment with a satellite. Figure 5 , as satellite 502 moves (e.g., by orbiting the earth), satellite 502 may move out of the coverage area or transmission range of network entity 504A. Thus, network entity 504A may hand over UE group 508 including UE 506A, UE 506B, UE 506C, and UE 506D to another network entity 504B that has satellite 502 in its coverage area. Satellite 502 may hand over the feeder link from network entity 504A to network entity 504B. Network entity 504A and network entity 504B may communicate at 510 via a core network (such as Figure 14B) are connected to each other. The network entity 504A may send a handover request to the network entity 504B, and the network entity 504B may confirm the handover request. The handover request may request that the UE group be handed over to the network entity 504B. In order to signal the handover to the UE group 508, the network entity 504A may send a group handover message 512 to the UE group 508. The group handover message 512 may be sent from the network entity 504A to the UE group 508 via the satellite 502. The UE group 508 may establish a connection with the network entity 504B via the satellite 502 based on the group handover message. Since the UE group 508 has established a connection with the network entity 504B, the satellite 502 switches the feeder link from the network entity 504A to the network entity 504B.

[0081] Figure 6 is a diagram illustrating an example communication flow between a group of UEs and a network entity communicating via a satellite. Figure 6 FIG. 6 is an example communication flow 600 between a group of UEs and a network entity communicating via a satellite. Figure 6 As illustrated in , a UE group 602 including one or more UEs (including UE 602A, UE 602B, and UE 602N) may be in communication 610 with a network entity 604A via a satellite 606. One UE group is illustrated and discussed as an example, but multiple UE groups may exist. For example, UE 602A-502N may have an RRC connection with the network entity 604A. In some aspects, communication 610 between the network entity 604A and the UEs in the UE group 602 may be exchanged via a satellite 606. Communication 610 may include data, control, etc. Communication 610 may include downlink communication and / or uplink communication. The network entity 604A and the network entity 604B may be network nodes. In some aspects, the network entity 604A and the network entity 604B may be base stations, which may be implemented as aggregated base stations, decomposed base stations, integrated access and backhaul (IAB) nodes, relay nodes, side link nodes, etc. The network entity may be implemented in a converged or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of a CU, DU, RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the network entity may be part of a terrestrial or non-terrestrial network, or a combination thereof.

[0082] The network entity 604A may send signal coded data, such as user data or control data for one UE in the UE group 602, to the satellite 606. The satellite 606 may relay the data to one or more UEs in the UE group 602, such as by performing amplification, spatial filtering, or frequency conversion. The UEs in the UE group 602 may communicate with the network entity 604A by sending signal coded data, such as user data of the UE, to the satellite 606. The satellite 606 may then relay the data to the network entity 604A, such as by performing amplification, spatial filtering, or frequency conversion. The communication link (i.e., radio link) between the network entity 604A and the satellite 606 may be referred to as a feeder link A. In some aspects, the satellite 606 is a transparent satellite configured to perform amplification, spatial filtering, or frequency conversion. In some aspects, the satellite 606 is a regenerative satellite that may additionally perform other signal processing (such as decoding, interference cancellation, signal regeneration) for relaying, but does not have the full functionality of a base station.

[0083] Satellite 606 may be mobile (such as by orbiting the earth). As satellite 606 moves at 612, the satellite may move out of the coverage area of ​​network entity 604A. In some aspects, UEs in group 602 of UEs may determine the occurrence of trigger event 614 based on any of a variety of parameters, such as 1) a measurement event related to cell quality or propagation delay (e.g., when the measured quality is below a threshold or the delay is above a threshold), 2) the location of the UE and the satellite, 3) one or more timers configured according to the service time and expected movement of the satellite, or 6) the elevation angle of the source cell and the target cell. UEs in group 602 of UEs may report the occurrence of event 616 (e.g., measurement event) to network entity 604A. In some examples, the occurrence of the event may be determined at a base station, for example, based on measurement information from one or more UEs in group 602 of UEs, one or more timers, the location of the satellite or UE, etc. Network entity 604A may determine to initiate a group handover for group 602 of UEs. At 618, network entity 604A may determine to initiate a group handover for group 602 of UEs. The determination may be based on any of a variety of triggering events. For example, the network entity 604A may determine to initiate a group handover based on a measurement-based trigger, where the cell quality of the UE group 602 has exceeded or fallen below a configured threshold. Alternatively or additionally, the network entity 604A may determine to initiate a group handover based on the location of the UE group 602 and / or the location of the satellite 606. Alternatively or additionally, the network entity 604A may determine to initiate a group handover based on an additional trigger condition based on a timing advance value to the target cell. Alternatively or additionally, the network entity 604A may determine to initiate a group handover based on the elevation angles of the source cell and the target cell. The network entity 604A may determine to initiate a group handover based on measurements from the UE group 602 or independently of measurements performed by the UE group 602.

[0084] After the network entity 604A determines at 618 that the UE group 602 is to be handed over, the network entity 604A may send a handover request 620 to the network entity 604B and receive a handover confirmation 622 from the network entity 604B. The network entity 604A may then send a PDSCH 624 to the UE group 602. Each UE in the UE group processes the PDSCH 624, as illustrated at 625, to determine that the UE is being handed over to the target base station.

[0085] In some aspects, as part of the handover confirmation 622 or PDSCH 624, the network entity 604A may send an RRC reconfiguration with a synchronization message in the PDSCH to the UE group 602, the message including a group handover message or a group handover command. A cell-specific common search space may be configured, and the UE group 602 may monitor the cell-specific common search space to receive a PDSCH indicating a HO command for the UE group. The group handover command may include bits that are scrambled based on a cell-specific group radio network temporary identifier (RNTI). Signaling radio bearer 1 (SRB1) information may provide UE-specific configuration, and UE-specific integrity protection and encryption of the RRC message may be applied to the SRB1 information of each individual UE in the group. SRB-x (such as SRB 3 or SRB 6) may include group-specific configuration information and may be protected using security information known to each UE in the group. For example, access stratum (AS) security information may be sent to the UE group 602, and signaling radio bearer information may be transmitted to the UE group with integrity protection and encryption based on the AS security information of the UE group. When the UE group 602 joins, a common group AS key may be provided to each UE in the group. In some aspects, a set of cell-specific or group-specific parameters may be used to derive a common group AS key. For group handover, the base station may send an RRC message including a list of RRC reconfiguration messages for multiple UEs. The RRC reconfiguration message may include an incremental RRC configuration for each UE based on the current configuration of a specific UE. The incremental RRC configuration may refer to a configuration that includes parameters different from the current configuration of the UE but does not include the same parameters as the current configuration of the UE. In some aspects, the base station may not provide RRC reconfiguration to one or more UEs in the UE group 602. The UE may interpret the absence of RRC reconfiguration or the RRC reconfiguration increment as an indication of continuing to use the current RRC configuration of the UE with the target base station. In such aspects, the UEs in the UE group 602 may continue to 626 to initiate an RRC connection with the target network entity 604B using their corresponding current RRC configuration. The UEs in the UE group 602 may receive a response from the network entity 604B at 628 and may send an RRC reconfiguration completion indication at 630. At 632 , the UEs in UE group 602 may send or receive user data to target network entity 604B. In some aspects, communications (eg, data 632 ) between network entity 604B and the UEs in UE group 602 may be exchanged via satellite 606 .

[0086] In some aspects, the network entity 604A may send a PDSCH 624 including multiple RRC messages to the UE group 602. Multiple RRC messages may be multiplexed at the medium access control (MAC) using one or more identical or different logical channel identifiers (LCIDs). Each UE in the UE group 602 may attempt to decode all RRC messages in the multiplexed RRC messages (such as in SRB1). In some aspects, each UE may attempt to decode multiple RRC messages using the current SRB1 configuration and AS security profile of the specific UE. The UEs in the UE group may decode a single RRC message from the multiplexed RRC messages based on the AS security profile of the UE, for example, one RRC message will pass the integrity protection check for the UE. In some aspects, each UE may use a default SRB1 configuration. After decoding the RRC message, the UEs in the UE group 602 may initiate RRC reconfiguration with the target network entity 604B. The UEs in the UE group 602 may receive a response 628 from the network entity 604B and may send an RRC reconfiguration completion indication 630. After establishing a connection with the target base station, the UEs in the UE group 602 may send or receive user data 632 to the target network entity 604B.

[0087] Each UE may be able to decode one RRC message intended for that UE, and may not be able to decode other RRC messages that are not intended for that UE because the other RRC messages will fail the integrity protection check and may be subsequently discarded. Each RRC reconfiguration may include an incremental configuration based on a default UE configuration for a target. An incremental configuration may refer to a configuration that includes parameters that are different from a default configuration (e.g., a target serving cell configuration) but does not include the same parameters as the default configuration. The size of the group (e.g., the number of UEs in the UE group 602) may be configured by the network to fit the group handover message into a single transport block signal (TBS) size. For example, the number of UEs in the UE group may be based on the amount of group handover information that may be sent in one or more TBSs (e.g., in a single TBS).

[0088] In some aspects, the PDSCH 624 may be sent in a broadcast or multicast message received by the UE group. In some aspects, a public security key for the UE group 602 may be used to protect the broadcast or multicast message. The public security key may be provided to the UE group 602 using dedicated RRC signaling. In some aspects, based on time and / or location, each UE in the UE group 602 may check the broadcast or multicast message to determine whether to provide PDSCH 624 for the target cell of the target network entity 604B. In some aspects, the network entity 604A may (e.g., in communication 610) send a group-specific or UE-specific indication to each UE in the UE group 602 to check the broadcast or multicast message to schedule the time when the PDSCH 624 is sent as a broadcast message. In some aspects, the scheduling information may be provided to the UE group in a group handover message. In some aspects, the scheduling information may be provided to the UE group using RRC reconfiguration when the UE moves to the RRC connected state, or the scheduling information may be broadcast in system information such as SIB1. In some aspects, each UE in the UE group 602 may acquire a broadcast or multicast PDSCH before accessing the target cell at 626. A common security key for the UE group may be used to protect the broadcast or multicast message. The common security key may be provided to the UE group in dedicated signaling for the UE group, or to each UE in the UE group. If a group handover message is not configured or received, each UE in the UE group 602 may initiate an RRC reestablishment procedure at 626, such as based on a pre-configured time / location. The UEs in the UE group 602 may receive a response 628 from the network entity 604B, and may send an RRC reconfiguration complete indication 630. The UEs in the UE group 602 may then send or receive user data 632 to the target network entity 604B.

[0089] The RRC reconfiguration may include an incremental configuration. The incremental configuration may be based on a source configuration or a current configuration of each UE. The incremental configuration may indicate parameters of a configuration different from the source configuration or the default configuration of the UE, without indicating parameters that will remain unchanged. In some aspects, the incremental configuration of each UE in the UE group 602 may be based on a default UE configuration for the target network entity 604B. The default UE configuration for the target network entity 604B may be a complete configuration of parameters for communicating with the target base station. In some aspects, the default UE configuration for the target network entity 604B may be provided before the handover decision at 618. In some aspects, the group handover message may provide a common target serving cell configuration for each UE in the UE group. The list of RRC reconfigurations may include an incremental configuration that individually indicates one or more parameters that will be changed for each UE.

[0090] In some aspects, the group handover message may include an indication to continue using the current source cell configuration. In some aspects, the target network entity 604B may accept the same UE radio configuration as used in the source network entity 604A. The cell-specific / carrier-specific configuration for the UE may be the same. The security keys may be different between the source base station and the target base station, and the UE may receive a next hop chain counter (NCC) and / or a cell radio network temporary identifier (C-RNTI) for the target base station in the group handover message.

[0091] The new feeder link to the new base station may result in a different time delay for the communication. In some aspects, the group handover message may include a new round trip delay (RTD) value between the satellite and the gateway (i.e., the target network entity 604B). The new RTD value may be used by each UE in the UE group 602 for uplink pre-compensation in uplink transmissions such as in 626, 630, and 632. The new RTD value may be included in a system information block (SIB).

[0092] In some aspects, if the timing advance (TA) is different for the target network entity 604B compared to the network entity 604A, the network entity 604A may provide an adjustment to the TA using a UE-specific or group-specific indication (e.g., a DCI using a group RNTI) to adjust the feeder link propagation delay common to each UE in the UE group 602. The precompensation applied to the UE-to-satellite link may remain the same. The UEs in the UE group 602 may use the same TA for the target network entity 604B without receiving an indication of the TA adjustment. In some aspects, the UEs in the UE group 602 may read the system information to receive the latest common configuration that may include paging, random access, and an initial precompensated TA value for initial access before initiating RRC access with the network entity 604B at 626. In such aspects, the group handover message may not include common configuration or system information for reducing the size of the handover message, and at 626, the UEs in the UE group 602 may initiate RRC access with the network entity 604B based on pre-configured execution conditions (such as, time, location, etc.).

[0093] In some aspects, after the feeder link is changed from network entity 604A to network entity 604B, the SIB in the cell is considered unchanged. Information about SIBs may be transparent to UEs in IDLE mode or RRC_INACTIVE mode. For such UEs, a change in RTD may not trigger an SI update procedure.

[0094] In aspects where each UE in the UE group 602 attempts to decode all of the multiple RRC messages in the multiplexed RRC messages (such as in SRB1), each of the multiple RRC messages in the PDSCH 624 may include a target serving cell configuration (which may be common to each UE) (e.g., an RRC configuration associated with a target serving cell of the network entity 604B). As a result, the PDSCH 624 may include multiple copies of the common configuration. Some aspects provided herein may improve the efficiency of group handover procedures by reducing signaling overhead (e.g., associated with the PDSCH 624).

[0095] In some aspects, before sending the PDSCH 624 to the UE group 602, a group RNTI may be configured for the UE group 602. As used herein, the term "group RNTI" may refer to an RNTI configured for the UE group. In such aspects, the PDSCH 624 may be sent to the UE group 602 based on the group RNTI. In some aspects, the group RNTI may be configured in a PDCCH 623 sent from the network entity 604A to the UE group 602. In some aspects, the PDCCH 623 may schedule the PDSCH 624. In addition to the group RNTI, an index may also be configured to indicate an association between multiple RRC messages and corresponding UEs in the UE group 602. For example, if the index configured for UE 602B is 2, the second RRC message in the PDSCH may be associated with UE 602B.

[0096] In some aspects, upon receiving the PDCCH 623, each UE in the UE group 602 may indicate (e.g., in the ACK 670) a HARQ process ID to receive the PDSCH 624. In some aspects, the HARQ process ID=0 may be used independently of the HARQ process ID field. In some aspects, a multi-bit (e.g., 4-bit / 5-bit) HARQ process ID field may be reused for other purposes. In some aspects, the HARQ process ID may be reserved for the PDCCH 623. In some aspects, the new data indicator (NDI) field may be switched. In some aspects, feedback of another schedule in the reserved HARQ process ID may be canceled. In some aspects, the HARQ process ID (e.g., in the ACK 670) for receiving the PDSCH 624 may be independent of the feedback enable / disable configuration (e.g., HARQ process ID) for the HARQ process.

[0097] In some aspects, the target serving cell configuration may be provided in a separate common MAC SDU (e.g., included in a separate RRC message carried by the common MAC SDU), rather than including the target serving cell configuration in each of the multiple RRC messages. As used herein, the term "MAC SDU" may refer to a service data unit that may be received from a logical link control sublayer located above the MAC sublayer in the protocol stack. The logical link control sublayer and the MAC sublayer may be collectively referred to as a data link layer. In some aspects, the common MAC SDU may be provided in a SIB or a broadcast PDSCH 680 and may be broadcast by the network entity 604A. In some aspects, the SIB or broadcast PDSCH 680 is readable for all UEs (including the UE group 602) communicating with the network entity 604A. In some aspects, the common MAC SDU may be included in the PDSCH 624.

[0098] In some aspects, the target serving cell configuration may not be present in the reconfigurationWithSync information element (IE), which represents the parameters for synchronous reconfiguration of the target specific cell (SpCell). In some aspects, the SS / PBCH block measurement timing configuration (SMTC) may be provided to the UE group 602 based on the format of the reconfigurationWithSync IE. In some aspects, the target serving cell configuration may be carried in a separate RRC message (e.g., separated from the SMTC). In some aspects, the DLInformationTransfer message representing the transfer of the non-access stratum (NAS) may include the target serving cell configuration. In some aspects, the RRC transaction identifier (ID) associated with the common MAC SDU may not be used. In some aspects, the UE group 602 may or may not send an ACK associated with the common MAC SDU. In some aspects, the common MAC SDU may also include the frequency or cell ID of the target serving cell.

[0099] In some aspects, the PDSCH 624 may be a MAC PDU that includes multiple RRC messages (also referred to as an "RRC message group") for the UE group 602. As used herein, the term "MAC PDU" may refer to a protocol data unit that may include one or more subheaders, each subheader providing information for decoding a corresponding MAC sub-PDU. A single MAC PDU may be encapsulated as a transport block (TB) and may be sent to the physical layer via a transport channel. A single MAC PDU may include multiple MAD SDUs and CEs. In some aspects, an LCID or an extended LCID (eLCID) may identify a common MAC SDU and an RRC message carrying a target serving cell configuration. Figure 7 FIG. 7 is a diagram illustrating an example MAC PDU. Figure 7 As illustrated in , the MAC PDU may include a set of MAC sub-PDUs, some of which may be MAC sub-PDUs including MAC SDUs. In some aspects, the MAC PDU may also include a MAB sub-PDU containing padding. In some aspects, each MAC SDU 706 in the MAC sub-PDU set 710 may carry one RRC message among multiple RRC messages associated with the UE group 602. In some aspects, each RRC message carried by the MAC SDU in the MAC sub-PDU 710 may include a corresponding group handover configuration for one UE in the UE group 602. As used herein, the term "group handover configuration" may refer to a configuration for a UE to be connected to a target network entity, which may be bundled with other group handover configurations of other UEs in the group. In some aspects, the MAC PDU may include a MAC sub-PDU 708, which includes a common MAC SDU 704 carrying an RRC message, which carries a target serving cell configuration. In some aspects, each MAC sub-PDU including the MAC SDU may also include a MAC sub-header.

[0100] As used herein, the term "target serving cell configuration" may refer to a configuration associated with a target serving cell (e.g., of network entity 604B). In some aspects, the target serving cell configuration may be represented by an incremental configuration relative to a default target cell configuration or a source cell configuration. As an example, the target serving cell configuration may include a physical cell ID, a downlink configuration, an uplink configuration, a DM-RS configuration, a rate matching mode configuration, a transmit power configuration, an SSB subcarrier configuration, a timing advance offset configuration, etc. In some aspects, as Figure 7As illustrated in , if the MAC PDU begins with a common MAC SDU (which may have an LCID) that includes a default target cell configuration (e.g., associated with network entity 604B) or a source cell configuration (which may be common to UE group 602), then other MAC subheaders 702 associated with each MAC SDU 706 (each MAC subheader carries one of a plurality of RRC messages associated with UE group 602, each RRC message may include a corresponding group handover configuration for one of UEs in UE group 602) may include an index associated with a corresponding UE in the UE group. In some aspects, the index may be configured to the corresponding UE via a dedicated RRC message. As an example, if UE 602B is configured with index 2, then after UE 602B discards the first common MAC SDU and other MAC SDUs 706, UE 602B may decode the second MAC SDU 706. In some aspects, each MAC SDU 706 may be configured with a priority (e.g., high priority) logical channel for SRB. Other MAC SDUs 706 may be discarded based on high priority while lower priority SDUs may be decoded.

[0101] In some aspects, a bitmap sub-header (such as an 8x bitmap sub-header) may be introduced for the LCID associated with a common MAC SDU. Figure 8 FIG. 8 is a diagram illustrating an example indexing of an SDU. Figure 8 As illustrated in , the MAC PDU may include a set of MAC sub-PDUs, some of which may be MAC sub-PDUs including MAC SDUs. In some aspects, the MAC PDU may also include a MAB sub-PDU including padding. In some aspects, each MAC SDU 806 in the MAC sub-PDU set 810 may carry one RRC message among multiple RRC messages associated with the UE group 602. In some aspects, each RRC message carried by the MAC SDU in the MAC sub-PDU 810 may include a corresponding group handover configuration for one UE in the UE group 602. In some aspects, the MAC PDU may include a MAC sub-PDU 808, which includes a common MAC SDU 804 carrying an RRC message, which carries a default target cell configuration or a source cell configuration. In some aspects, each MAC sub-PDU including the MAC SDU may also include a MAC sub-header. As Figure 8As illustrated in the figure, the bitmap 850 may include one or more octets representing an index bitmap of the location of a MAC SDU associated with each UE in the UE set 602 (each MAC SDU carries one of multiple RRC messages associated with the UE group 602, and each RRC message may include a corresponding group handover configuration for one of the UEs in the UE group 602).

[0102] In some aspects, a common MAC SDU follows a MAC subheader (eg, 1 byte) indicating a C-RNTI MAC CE list, which is used to indicate to the UE which RRC messages (which MAC SDUs) of the UE are included in the MAC PDU. Fig. 9 FIG. 9 is a diagram illustrating an example index of an SDU. Fig. 9 As illustrated in the figure, a common MAC SDU 904 may follow a MAC subheader 902 indicating a list of C-RNTI MAC CEs 920, for indicating an association between each UE in the UE group 602 and a MAC SDU 910 for the corresponding UE (each MAC SDU carries one of multiple RRC messages associated with the UE group 602, and each RRC message may include a corresponding group handover configuration for one of the UEs in the UE group 602).

[0103] In some aspects, if the MAC PDU includes N RRC messages associated with a set of UEs 602 including N UEs, the MAC PDU may start with a set of N (N is a positive integer) C-RNTI MAC CEs. Fig.10 FIG. 1000 is a diagram illustrating an example indexing of an SDU. Fig.10 As illustrated in , if a MAC PDU includes N RRC messages in N corresponding MAC SDUs 1010 associated with a set of UEs 602 including N UEs (e.g., each RRC message may include a corresponding group handover configuration for one UE in the UE group 602), the MAC PDU may start with a set of N (N is a positive integer) C-RNTI MAC CEs 1020. In some aspects, the C-RNTI may be associated with a C-RNTI LCID code point (e.g., a reserved normal or eLCID) having a length of multiple bytes (e.g., which may be fixed, such as two bytes).

[0104] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, a UE in UE group 602; device 1504).

[0105] At 1102, the UE may receive a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission including a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages including a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in a set of UEs including the UE, the set of RRC messages being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU). For example, a UE in a group of UEs 602 may receive a physical downlink shared channel (PDSCH) transmission (e.g., 624) from a network entity 604A, the PDSCH transmission including a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages including a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in a set of UEs including the UE, the set of RRC messages being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU). In some aspects, 1102 may be performed by handover component 198 .

[0106] At 1104, the UE may process a first subset of MAC SDUs associated with the UE and discard a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs including a common MAC SDU and at least a UE-specific MAC SDU. For example, the UEs in the UE group 602 may receive a first subset of MAC SDUs associated with the UE and discard a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs including a common MAC SDU and at least a UE-specific MAC SDU. In some aspects, 1104 may be performed by the handover component 198. In some aspects, the UE-specific MAC SDU may include one RRC message in the message set.

[0107] At 1106, the UE may connect to the target network entity based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE. For example, the UEs in the UE group 602 may connect to the target network entity 604B based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE. In some aspects, 1106 may be performed by the handover component 198.

[0108] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, a UE in UE group 602; device 1504).

[0109] At 1202, a UE may receive a PDCCH transmission associated with a group RNTI for scheduling a PDSCH transmission for a set of UEs including the UE, the PDCCH transmission being received from a network entity, the group RNTI being associated with each UE in the set of UEs. For example, a UE in the UE group 602 may receive a PDCCH transmission (e.g., 623) associated with a group RNTI for scheduling a PDSCH transmission (e.g., 624) for the set of UEs 602 including the UE, the PDCCH transmission being received from a network entity 604A, the group RNTI being associated with each UE in the set of UEs. In some aspects, 1202 may be performed by handover component 198.

[0110] At 1203, the UE may send a HARQ response associated with the PDCCH transmission. For example, the UEs in the UE group 602 may send a HARQ response associated with the PDCCH transmission (e.g., ACK 670). In some aspects, 1203 may be performed by the handover component 198. In some aspects, the HARQ response may be independent of the feedback enable or disable configuration.

[0111] At 1204, the UE may receive a PDSCH transmission from a network entity, the PDSCH transmission including a set of RRC messages, each of which may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the set of RRC messages being included in a set of MAC SDUs in the MAC PDU. For example, a UE in the set of UEs 602 may receive a PDSCH transmission (e.g., 624) from a network entity 604A, the PDSCH transmission including a set of RRC messages, each of which may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs 602, the set of RRC messages being included in a set of MAC SDUs in the MAC PDU. In some aspects, 1204 may be performed by the handover component 198. In some aspects, the MAC PDU may include a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the target serving cell configuration may be associated with a target network entity. In some aspects, each RRC message in the RRC message set may be associated with a priority associated with a high priority logical channel for SRBs. In some aspects, a common MAC SDU may be associated with an LCID, and wherein the LCID may be associated with a bitmap subheader representing an index, the index representing an association between the RRC message set and the UE set. In some aspects, the common MAC SDU may be followed by a MAC subheader in a MAC PDU, wherein the MAC subheader indicates a C-RNTI list representing an index, the index representing an association between the RRC message set and the UE set. In some aspects, the MAC PDU may include a C-RNTI MAC CE set associated with the RRC message set and the UE set.

[0112] In some aspects, at 1240, the UE may process a first subset of MAC SDUs associated with the UE and discard a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs including a common MAC SDU and at least a UE-specific MAC SDU. For example, the UEs in the UE group 602 may process a first subset of MAC SDUs associated with the UE and discard a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs including a common MAC SDU and at least a UE-specific MAC SDU. As an example, the UE may process one MAC SDU in the MAC SDU 706 associated with the UE and discard other MAC SDUs 706 that are not associated with the UE. As an example, the UE may process one MAC SDU in the MAC SDU 806 associated with the UE and discard other MAC SDUs that are not associated with the UE. As an example, the UE may process one MAC SDU in the MAC SDU 910 associated with the UE and discard other MAC SDUs. As an example, the UE may process one MAC SDU in the MAC SDU 1010 associated with the UE and discard other MAC SDUs. In some aspects, 1240 may be performed by handover component 198. In some aspects, the UE-specific MAC SDU may include one RRC message in a set of messages.

[0113] At 1205, the UE may receive a target serving cell configuration associated with each UE in the set of UEs, wherein a common MAC SDU may be received in a SIB or a broadcast PDSCH (e.g., 680), wherein the target serving cell configuration may be associated with the target network entity 604B, and wherein the common MAC SDU may be separate from the set of MAC SDUs. For example, the UEs in the UE group 602 may receive a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the common MAC SDU may be received in a SIB or a broadcast PDSCH, wherein the target serving cell configuration may be associated with the target network entity, and wherein the common MAC SDU may be separate from the set of MAC SDUs. In some aspects, 1205 may be performed by handover component 198.

[0114] In some aspects, the common MAC SDU may include incremental configuration regarding a default target cell configuration or source cell configuration for each UE in the set of UEs. In some aspects, the common MAC SDU may include a frequency or cell ID associated with a target cell associated with a target network entity. In some aspects, the PDCCH transmission may include an index representing an association between a set of RRC messages and a set of UEs.

[0115] At 1206, the UE may connect to the target network entity based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE. For example, the UEs in the UE group 602 may connect to the target network entity 604B based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE. In some aspects, 1206 may be performed by the handover component 198.

[0116] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 604A, network entity 1502, network entity 1602).

[0117] At 1306, the network entity may transmit a PDCCH transmission associated with a group RNTI that schedules PDSCH transmissions for the set of UEs, the group RNTI being associated with each UE in the set of UEs. For example, network entity 604A may transmit a PDCCH transmission associated with a group RNTI that schedules PDSCH transmissions for the set of UEs (e.g., 623), the group RNTI being associated with each UE in the set of UEs. In some aspects, 1306 may be performed by handover component 199.

[0118] At 1308, the network entity may send a PDSCH transmission, the PDSCH transmission including a set of RRC messages, each RRC message in the set of RRC messages may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the RRC message set being included in a set of MAC SDUs in a MAC PDU, the MAC SDU set including a common MAC SDU for the set of UEs and a subset of SDUs for each corresponding UE in the set of UEs. For example, the network entity 604A may send a PDSCH transmission (e.g., 624), the PDSCH transmission including a set of RRC messages, each RRC message in the set of RRC messages may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the RRC message set being included in a set of MAC SDUs in the MAC PDU. In some aspects, 1308 may be performed by handover component 199.

[0119] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 604A, network entity 1502, network entity 1602).

[0120] At 1406, the network entity may send a PDCCH transmission associated with a group RNTI that schedules PDSCH transmissions for the set of UEs, the group RNTI being associated with each UE in the set of UEs. For example, the network entity 604A may send a PDCCH transmission (e.g., 623) associated with a group RNTI that schedules PDSCH transmissions for the set of UEs, the group RNTI being associated with each UE in the set of UEs. In some aspects, 1406 may be performed by handover component 199. In some aspects, the PDCCH transmission may include an index indicating an association between a set of RRC messages and a set of UEs.

[0121] At 1407, the network entity may receive a HARQ response associated with the PDCCH transmission. For example, the network entity 604A may receive a HARQ response associated with the PDCCH transmission (e.g., 670). In some aspects, 1407 may be performed by handover component 199. In some aspects, the HARQ response may be independent of the feedback enable or disable configuration.

[0122] At 1408, the network entity may send a PDSCH transmission, the PDSCH transmission including a set of RRC messages, each RRC message in the set of RRC messages may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the RRC message set being included in a set of MAC SDUs in a MAC PDU, the MAC SDU set including a common MAC SDU for the set of UEs and a subset of SDUs for each corresponding UE in the set of UEs. For example, the network entity 604A may send a PDSCH transmission (e.g., 624), the PDSCH transmission including a set of RRC messages, each RRC message in the set of RRC messages may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the RRC message set being included in a set of MAC SDUs in the MAC PDU. In some aspects, 1408 may be performed by the handover component 199. In some aspects, the MAC PDU may include a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the target serving cell configuration may be associated with a target network entity. In some aspects, a common MAC SDU corresponds to the beginning of a MAC PDU, and wherein the MAC PDU may include a MAC subheader including an index indicating an association between a set of RRC messages and a set of UEs. In some aspects, each RRC message in the set of RRC messages may be associated with a priority associated with a high priority logical channel for SRBs. In some aspects, a common MAC SDU may be associated with an LCID, and wherein the LCID may be associated with a bitmap subheader indicating an index indicating an association between a set of RRC messages and a set of UEs. In some aspects, a common MAC SDU may be after a MAC subheader in a MAC PDU, wherein the MAC subheader indicates a C-RNTI list indicating an index indicating an association between a set of RRC messages and a set of UEs. In some aspects, a MAC PDU may include a set of C-RNTI MAC CEs associated with a set of RRC messages and a set of UEs.

[0123] At 1410, the network entity may send a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the common MAC SDU may be sent in a SIB or a broadcast PDSCH, wherein the target serving cell configuration may be associated with the target network entity, and wherein the common MAC SDU may be separate from the set of MAC SDUs. For example, the network entity 604A may send a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the common MAC SDU may be sent in a SIB or a broadcast PDSCH (e.g., 680), wherein the target serving cell configuration may be associated with the target network entity, and wherein the common MAC SDU may be separate from the set of MAC SDUs. In some aspects, 1410 may be performed by the handover component 199. In some aspects, the common MAC SDU may include an incremental configuration for a default target cell configuration or a source cell configuration for each UE in the set of UEs. In some aspects, the common MAC SDU may include a frequency or cell ID associated with a target cell associated with the target network entity.

[0124] Fig.151500 is a diagram illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the apparatus 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, a satellite system module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the satellite system module 1516 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1524 communicates with the UE 104 and / or with a RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1524 / application processor 1506 to perform various functions described herein when executed by the cellular baseband processor 1524 / application processor 1506. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software. The cellular baseband processor 1524 / application processor 1506 may be a component of the UE350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359.In one configuration, the device 1504 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1524 and / or the application processor 1506, while in another configuration, the device 1504 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1504.

[0125] As discussed herein, the handover component 198 may be configured to receive a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission comprising a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages comprising a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in a set of UEs including the UE, the RRC message set being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU). In some aspects, the handover component 198 may also be configured to process a first subset of MAC SDUs associated with the UE and discard a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs comprising a common MAC SDU and at least a UE-specific MAC SDU. In some aspects, the handover component 198 may also be configured to connect to a target network entity based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE. The handover component 198 may be within the cellular baseband processor 1524, the application processor 1506, or both the cellular baseband processor 1524 and the application processor 1506. The handover component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1504 may include a variety of components configured for various functions. In one configuration, the device 1504 (and specifically, the cellular baseband processor 1524 and / or the application processor 1506) includes a component for receiving a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission including a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages including a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in a set of UEs including the UE, the set of RRC messages being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU). In some aspects, the device 1504 may also include a component for processing a first subset of MAC SDUs associated with the UE and discarding a second subset of MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs including a common MAC SDU and at least a UE-specific MAC SDU. In some aspects, the device 1504 may also include a component for connecting to a target network entity based on a group handover configuration in the set of group handover configurations, the group handover configuration being associated with the UE.In some aspects, the device 1504 may also include a component for receiving a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the common MAC SDU is received in a system information block (SIB), a broadcast PDSCH, a group PDSCH, or a unicast PDSCH, wherein the target serving cell configuration is associated with a target network entity, and wherein the common MAC SDU is separated from the MAC SDU set. In some aspects, the device 1504 may also include a component for sending a HARQ response associated with a PDCCH transmission. The component may be a handover component 198 of the device 1504 configured to perform the functions recorded by the component. As described herein, the device 1504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recorded by the component.

[0126] Fig.161600 is a diagram illustrating an example of a hardware implementation for a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality handled by the component 199, the network entity 1602 may include a CU 1610; both a CU 1610 and a DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both a DU 1630 and a RU 1640; or a RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1612'. In some aspects, the CU 1610 may also include an additional memory module 1614 and a communication interface 1618. CU 1610 communicates with DU 1630 via a midhaul link, such as an F1 interface. DU 1630 may include a DU processor 1632. DU processor 1632 may include on-chip memory 1632'. In some aspects, DU 1630 may also include additional memory modules 1634 and a communication interface 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include a RU processor 1642. RU processor 1642 may include on-chip memory 1642'. In some aspects, RU 1640 may also include additional memory modules 1644, one or more transceivers 1646, antenna 1680, and communication interface 1648. RU 1640 communicates with UE 104. On-chip memory 1612', 1632', 1642' and additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each processor in processors 1612, 1632, 1642 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0127] As discussed herein, the handover component 199 may be configured to send a group handover request for a set of UEs to a target network entity. In some aspects, the handover component 199 may also be configured to receive a group handover confirmation (ACK) from the target network entity based on the group handover request. In some aspects, the handover component 199 may also be configured to send a PDCCH transmission associated with a group RNTI for scheduling a PDSCH transmission for a set of UEs, the group RNTI being associated with each UE in the set of UEs. In some aspects, the handover component 199 may also be configured to send a PDSCH transmission, the PDSCH transmission comprising an RRC message set, each RRC message in the RRC message set may include a corresponding group handover configuration in a set of group handover configurations associated with a corresponding UE in the set of UEs, the RRC message set being included in a MAC SDU set in a MAC PDU, the MAC SDU set comprising a common MAC SDU for the set of UEs and an SDU subset for each corresponding UE in the set of UEs.

[0128] The handover component 199 may be within one or more processors of one or more of the CU 1610, the DU 1630, and the RU 1640. The handover component 199 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 1602 may include a variety of components configured for various functions. In one configuration, the network entity 1602 includes a component for sending a PDCCH transmission associated with a group RNTI for scheduling a PDSCH transmission for a set of UEs, the group RNTI being associated with each UE in the set of UEs. In some aspects, the network entity 1602 may also include a component for sending a PDSCH transmission, the PDSCH transmission including an RRC message set, each RRC message in the RRC message set may include a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in the set of UEs, the RRC message set being included in a MAC SDU set in a MAC PDU. In some aspects, the network entity 1602 may also include a component for sending a common MAC SDU associated with a target serving cell configuration or a source cell configuration associated with each UE in a set of UEs, wherein the common MAC SDU may be sent in a SIB, a broadcast PDSCH, a group PDSCH, or a unicast PDSCH, wherein the target serving cell configuration may be associated with a target network entity, and wherein the common MAC SDU may be separated from the MAC SDU set. In some aspects, the network entity 1602 may also include a component for receiving a HARQ response associated with a PDCCH transmission. The component may be a handover component 199 of the network entity 1602 configured to perform the functions recorded by the component. As described herein, the network entity 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recorded by the component.

[0129] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0130] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ......" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases (such as "when ......") do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly recorded using the phrase "component for..."

[0131] As used in this disclosure outside of the claims, the phrase "based on" includes all interpretations and should not be limited to any single interpretation unless specifically recorded or indicated as such. For example, the phrase "based on A" (where "A" may be information, a condition, a factor, etc.) may be interpreted as: "at least based on A", "partially based on A", "at least partially based on A", "only based on A" or "based on A alone". Therefore, as disclosed herein, in one aspect, "based on A" may refer to "at least based on A". In another aspect, "based on A" may refer to "partially based on A". In another aspect, "based on A" may refer to "at least partially based on A". In another aspect, "based on A" may refer to "only based on A". In another aspect, "based on A" may refer to "based on A alone". In another aspect, "based on A" may refer to any combination of alternative interpretations. As used in the claims, the phrase "based on A" should be interpreted as "at least based on A", unless otherwise specifically stated.

[0132] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0133] Aspect 1 is a method for performing wireless communication at a UE, the method comprising: receiving a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission comprising a radio resource control (RRC) message set, each RRC message in the RRC message set comprising a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in a UE set including the UE, the RRC message set being included in a MAC service data unit (SDU) (MAC SDU) set in a medium access control (MAC) protocol data unit (PDU); processing a first subset of the MAC SDU associated with the UE and discarding a second subset of the MAC SDU that is not applicable to the UE, the first subset of the MAC SDU comprising a common MAC SDU and at least a UE-specific MAC SDU; and connecting to a target network entity based on a group handover configuration in the group handover configuration set, the group handover configuration being associated with the UE.

[0134] Aspect 2 is a method according to Aspect 1, and the method also includes: receiving a common MAC SDU associated with a target service cell configuration or a source cell configuration associated with each UE in the UE set, wherein the common MAC SDU may be received in a SIB, a broadcast PDSCH, a group PDSCH, or a unicast PDSCH, wherein the target service cell configuration may be associated with the target network entity, and wherein the common MAC SDU may be separated from the MAC SDU set.

[0135] Aspect 3 is a method according to any one of aspects 1 to 2, wherein the common MAC SDU may include an incremental configuration regarding a default target cell configuration or a source cell configuration for each UE in the set of UEs.

[0136] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the common MAC SDU may include a frequency or cell ID associated with a target cell associated with the target network entity.

[0137] Aspect 5 is a method according to any one of Aspects 1 to 4, the method also including receiving a physical downlink control channel (PDCCH) transmission associated with a group radio network temporary identifier (RNTI) for scheduling the PDSCH transmission for the set of UEs including the UE, the PDCCH transmission being received from the network entity, the group RNTI being associated with each UE in the set of UEs.

[0138] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein the MAC PDU may include a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the target serving cell configuration may be associated with the target network entity.

[0139] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein the common MAC SDU corresponds to the beginning of the MAC PDU, and wherein the MAC PDU may include a MAC subheader, and the MAC subheader includes an index representing the association between the RRC message set and the UE set.

[0140] Aspect 8 is a method according to any one of aspects 1 to 7, wherein each RRC message in the RRC message set may be associated with a priority associated with a high priority logical channel for SRBs.

[0141] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein the common MAC SDU can be associated with an LCID, and wherein the LCID can be associated with a bitmap subheader representing an index, wherein the index represents the association between the RRC message set and the UE set.

[0142] Aspect 10 is a method according to any one of Aspects 1 to 9, wherein the common MAC SDU may be after a MAC subheader in the MAC PDU, wherein the MAC subheader indicates a C-RNTI list representing an index, wherein the index represents an association between the RRC message set and the UE set.

[0143] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the MAC PDU may include a C-RNTI MAC CE set associated with the RRC message set and the UE set.

[0144] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: sending a HARQ response associated with the PDCCH transmission.

[0145] Aspect 13 is a method according to any one of aspects 1 to 12, wherein the HARQ response may be independent of feedback enabling or disabling configuration.

[0146] Aspect 14 is a method according to any one of Aspects 1 to 13, wherein the method is performed at an apparatus comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna can be configured to receive the PDSCH transmission.

[0147] Aspect 15 is a method for performing wireless communication at a network entity, the method comprising: sending a PDCCH transmission associated with a group RNTI for scheduling a PDSCH transmission for a UE set, the group RNTI being associated with each UE in the UE set; and sending the PDSCH transmission, the PDSCH transmission comprising an RRC message set, each RRC message in the RRC message set comprising a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in the UE set, the RRC message set being included in a MAC SDU set in a MAC PDU, the MAC SDU set comprising a common MAC SDU for the UE set and an SDU subset for each corresponding UE in the UE set.

[0148] Aspect 16 is a method according to Aspect 15, the method further comprising: sending a common MAC SDU associated with the target service cell configuration to each UE in the UE set, wherein the common MAC SDU may be sent in a SIB, a broadcast PDSCH, a group PDSCH, a unicast PDSCH or a group handover configuration, wherein the target service cell configuration may be associated with the target network entity, and wherein the common MAC SDU may be separated from the MAC SDU set.

[0149] Aspect 17 is a method according to any one of aspects 15 to 16, wherein the common MAC SDU may include an incremental configuration regarding a default target cell configuration or a source cell configuration for each UE in the set of UEs.

[0150] Aspect 18 is a method according to any one of aspects 15 to 17, wherein the common MAC SDU may include a frequency or cell ID associated with a target cell associated with the target network entity.

[0151] Aspect 19 is a method according to any one of aspects 15 to 18, wherein the PDCCH transmission may include an index indicating an association between the set of RRC messages and the set of UEs.

[0152] Aspect 20 is a method according to any one of Aspects 15 to 19, wherein the MAC PDU may include a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the target serving cell configuration may be associated with the target network entity.

[0153] Aspect 21 is a method according to any one of Aspects 15 to 20, wherein the common MAC SDU corresponds to the beginning of the MAC PDU, and wherein the MAC PDU may include a MAC subheader, the MAC subheader including an index representing the association between the RRC message set and the UE set.

[0154] Aspect 22 is a method according to any one of aspects 15 to 21, wherein each RRC message in the set of RRC messages may be associated with a priority associated with a high priority logical channel for SRBs.

[0155] Aspect 23 is a method according to any one of Aspects 15 to 22, wherein the common MAC SDU can be associated with an LCID, and wherein the LCID can be associated with a bitmap subheader representing an index, wherein the index represents the association between the RRC message set and the UE set.

[0156] Aspect 24 is a method according to any one of Aspects 15 to 23, wherein the common MAC SDU may be after a MAC subheader in the MAC PDU, wherein the MAC subheader indicates a C-RNTI list representing an index, and the index represents an association between the RRC message set and the UE set.

[0157] Aspect 25 is a method according to any one of aspects 15 to 24, wherein the MAC PDU may include a set of C-RNTI MAC CEs associated with the set of RRC messages and the set of UEs.

[0158] Aspect 26 is a method according to any one of aspects 15 to 25, the method further comprising: receiving a HARQ response associated with the PDCCH transmission.

[0159] Aspect 27 is a method according to any one of aspects 15 to 26, wherein the HARQ response may be independent of feedback enabling or disabling configuration.

[0160] Aspect 28 is a method according to any one of aspects 15 to 27, wherein the method is performed at an apparatus comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna can be configured to transmit the PDSCH transmission.

[0161] Aspect 29 is an apparatus for wireless communication at a device, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 14 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0162] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 1 to 14.

[0163] Aspect 31 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 1 to 14.

[0164] Aspect 32 is an apparatus for wireless communication at a device, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 15 to 28 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0165] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 15 to 28.

[0166] Aspect 34 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 15 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission comprising a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages comprising a respective one of a set of group handover configurations associated with a respective one of a set of UEs including the UE, the set of RRC messages being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU); processing a first subset of the MAC SDUs associated with the UE and discarding a second subset of the MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs comprising a common MAC SDU and at least a UE-specific MAC SDU; as well as Connecting to a target network entity based on a group handover configuration in the group handover configuration set, the group handover configuration being associated with the UE.

2. The apparatus of claim 1 , wherein the at least one processor is configured to: Receive the common MAC SDU associated with the target service cell configuration associated with each UE in the UE set, wherein the common MAC SDU is received in a system information block (SIB), a broadcast PDSCH, a group PDSCH or a unicast PDSCH, wherein the target service cell configuration is associated with the target network entity, and wherein the common MAC SDU is separated from the MAC SDU set.

3. The apparatus of claim 2, wherein the common MAC SDU comprises an incremental configuration regarding a default target cell configuration or a source cell configuration for each UE in the set of UEs.

4. The apparatus of claim 2, wherein the common MAC SDU comprises a frequency or cell identifier (ID) associated with a target cell associated with the target network entity.

5. The apparatus of claim 1, wherein the MAC PDU comprises a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the target serving cell configuration is associated with the target network entity.

6. The apparatus according to claim 5, wherein the common MAC SDU corresponds to the beginning of the MAC PDU, and wherein the MAC PDU includes a MAC subheader, the MAC subheader including an index indicating an association between the RRC message set and the UE set.

7. The apparatus of claim 6, wherein each RRC message in the set of RRC messages is associated with a priority associated with a high priority logical channel for a signaling radio bearer (SRB).

8. The apparatus of claim 5, wherein the common MAC SDU is associated with a logical channel identifier (LCID), and wherein the LCID is associated with a bitmap subheader representing an index, the index representing an association between the RRC message set and the UE set.

9. The apparatus according to claim 5, wherein the common MAC SDU is after a MAC subheader in the MAC PDU, wherein the MAC subheader indicates a cell RNTI (C-RNTI) list representing an index, wherein the index represents an association between the RRC message set and the UE set.

10. The apparatus of claim 5, wherein the MAC PDU further comprises a set of cell-RNTI (C-RNTI) MAC control elements (MAC CEs) associated with the set of RRC messages and the set of UEs.

11. The apparatus according to claim 1, wherein the UE is configured to: Receiving a physical downlink control channel (PDCCH) transmission associated with a group radio network temporary identifier (RNTI) that schedules the PDSCH transmission for the set of UEs including the UE, the PDCCH transmission being received from the network entity, the group RNTI being associated with each UE in the set of UEs.

12. The apparatus of claim 11, wherein the at least one processor is configured to: A hybrid automatic repeat request (HARQ) response associated with a HARQ process configured for the PDCCH transmission is transmitted.

13. The apparatus of claim 12, wherein the HARQ response is independent of a feedback enable or disable configuration.

14. The apparatus of claim 1, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the PDSCH transmission.

15. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: transmitting a physical downlink control channel (PDCCH) transmission associated with a group radio network temporary identifier (RNTI) that schedules a physical downlink shared channel (PDSCH) transmission for a set of user equipment (UEs), the group RNTI being associated with each UE in the set of UEs; as well as The PDSCH transmission is sent, wherein the PDSCH transmission includes a radio resource control (RRC) message set, each RRC message in the RRC message set includes a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in the UE set, and the RRC message set is included in a MAC service data unit (SDU) (MAC SDU) set in a medium access control (MAC) protocol data unit (PDU), and the MAC SDU set includes a common SDU for the UE set and a subset of the SDU for each corresponding UE in the UE set.

16. The apparatus of claim 15, wherein the at least one processor is configured to: The common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs is sent in a system information block (SIB), a broadcast PDSCH, a group PDSCH, a unicast PDSCH, or a group handover configuration, wherein the target serving cell configuration is associated with a target network entity, and wherein the common MAC SDU is separated from the set of MAC SDUs.

17. The apparatus of claim 16, wherein the common MAC SDU comprises an incremental configuration regarding a default target cell configuration or a source cell configuration for each UE in the set of UEs.

18. The apparatus of claim 16, wherein the common MAC SDU comprises a frequency or cell identifier (ID) associated with a target cell associated with the target network entity.

19. The apparatus of claim 15, wherein the group RNTI is associated with an index representing an association between the set of RRC messages and the set of UEs.

20. The apparatus of claim 15, wherein the MAC PDU comprises a common MAC SDU associated with a target serving cell configuration associated with each UE in the set of UEs, wherein the target serving cell configuration is associated with a target network entity.

21. The apparatus of claim 20, wherein the common MAC SDU corresponds to the beginning of the MAC PDU, and wherein the MAC PDU comprises a MAC subheader comprising an index representing an association between the RRC message set and the UE set.

22. The apparatus of claim 21, wherein each RRC message in the set of RRC messages is associated with a priority associated with a high priority logical channel for a signaling radio bearer (SRB).

23. The apparatus of claim 20, wherein the common MAC SDU is associated with a logical channel identifier (LCID), and wherein the LCID is associated with a bitmap subheader representing an index representing an association between the RRC message set and the UE set.

24. The apparatus of claim 20, wherein the common MAC SDU follows a MAC subheader in the MAC PDU, wherein the MAC subheader indicates a cell RNTI (C-RNTI) list representing an index representing an association between the RRC message set and the UE set.

25. The apparatus of claim 20, wherein the MAC PDU further comprises a set of cell-RNTI (C-RNTI) MAC control elements (MAC CEs) associated with the set of RRC messages and the set of UEs.

26. The apparatus of claim 15, wherein the at least one processor is configured to: A hybrid automatic repeat request (HARQ) response associated with a HARQ process configured for the PDCCH transmission is received.

27. The apparatus of claim 26, wherein the HARQ response is independent of a feedback enable or disable configuration.

28. The apparatus of claim 15, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the PDSCH transmission.

29. A method of wireless communication at a user equipment (UE), the method comprising: receiving a physical downlink shared channel (PDSCH) transmission from a network entity, the PDSCH transmission comprising a set of radio resource control (RRC) messages, each RRC message in the set of RRC messages comprising a respective one of a set of group handover configurations associated with a respective one of a set of UEs including the UE, the set of RRC messages being included in a set of MAC service data units (SDUs) (MAC SDUs) in a medium access control (MAC) protocol data unit (PDU); processing a first subset of the MAC SDUs associated with the UE and discarding a second subset of the MAC SDUs that are not applicable to the UE, the first subset of MAC SDUs comprising a common MAC SDU and at least a UE-specific MAC SDU; as well as Connecting to a target network entity based on a group handover configuration in the group handover configuration set, the group handover configuration being associated with the UE.

30. A method for wireless communication at a network entity, the method comprising: transmitting a physical downlink control channel (PDCCH) transmission associated with a group radio network temporary identifier (RNTI) that schedules a physical downlink shared channel (PDSCH) transmission for a set of UEs, the group RNTI being associated with each UE in the set of UEs; as well as The PDSCH transmission is sent, wherein the PDSCH transmission includes a radio resource control (RRC) message set, each RRC message in the RRC message set includes a corresponding group handover configuration in a group handover configuration set associated with a corresponding UE in the UE set, and the RRC message set is included in a MAC service data unit (SDU) (MAC SDU) set in a medium access control (MAC) protocol data unit (PDU), and the MAC SDU set includes a common SDU for the UE set and a subset of the SDU for each corresponding UE in the UE set.

Images