Managing group configurations in wireless communication system

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive first control signaling indicating a configuration associated with a target network node in a non-terrestrial network. The configuration may include a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The UE may perform a connection operation based on a trust state of the first UE group configuration.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 838,054, entitled “MANAGING GROUP CONFIGURATIONS IN WIRELESS COMMUNICATIONS SYSTEMS,” filed by Shrestha et al. on June 10, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including managing group configurations in wireless communication systems. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting management of group configurations in wireless communication systems. Various aspects of the present disclosure relate to protecting group configurations (e.g., group radio resource control (RRC) configurations) in wireless communication systems. A satellite or a network entity may send a group RRC configuration to a group of UEs in a wireless communication system. The group RRC configuration may include parameters associated with a target network entity (also referred to as a target cell). In addition, the group RRC configuration may include UE-specific configurations for the group of UEs. In some examples, the satellite or network entity may protect the group RRC configuration using a hash value or a cyclic redundancy check (CRC) value. In some other examples, the satellite or network entity may protect the group RRC configuration based on a radio network temporary identifier (RNTI) value configured for the group of UEs. One or both of the UE and the network entity may determine a trust state of the group RRC configuration and perform a connection procedure (e.g., a handover procedure). The trust state may be an indication of whether the group RRC configuration has been compromised.

[0006] A method for wireless communication at a UE is described. The method may include: receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; determining a trust state of the first UE group configuration; and performing a connection operation based on the trust state of the first UE group configuration.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; determine a trust state of the first UE group configuration; and perform a connection operation based on the trust state of the first UE group configuration.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; means for determining a trust state of the first UE group configuration; and means for performing a connection operation based on the trust state of the first UE group configuration.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; determine a trust state of the first UE group configuration; and perform a connection operation based on the trust state of the first UE group configuration.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing an integrity check of the first UE group configuration to obtain a trust state of the first UE group configuration, and wherein performing a connection operation may be based on the integrity check of the first UE group configuration, and wherein the connection operation includes a handover from a source network node to a target network node in a non-terrestrial network.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing an integrity check of a first UE group configuration may include operations, features, components, or instructions for determining a change in a hash value or a cyclic redundancy check (CRC) associated with the first UE group configuration based on a UE-specific configuration, wherein the integrity information includes the hash value or the CRC.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for performing a post-integrity check operation based on a trust state configured by the first UE group.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing a connection operation may include operations, features, components, or instructions for triggering a reestablishment of a connection operation to a target network node based on a trust state configured by the first UE group.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a second control signaling indicating a trust state of a first UE group configuration; receiving a third control signaling indicating a second UE group configuration based on the trust state of the first UE group configuration according to integrity information, and wherein performing a connection operation may be based on the second UE group configuration.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a hash value or CRC associated with the first UE group configuration and sending a second control signaling indicating the hash value or CRC associated with the first UE group configuration, the second control signaling including a handover complete message.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting one or more parameters associated with the first UE group configuration and sending second control signaling indicating the one or more parameters associated with the first UE group configuration.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a configuration excludes master security key updates.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending second control signaling indicating whether the first UE group configuration includes a common configuration or a default configuration, and wherein performing a connection operation may be based on the second control signaling.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a system information block (SIB) associated with a target network node and a non-terrestrial network-specific SIB associated with a network entity in a non-terrestrial network, and sending a second control signaling indicating that the handover is complete, wherein performing the connection operation may be based on the second control signaling.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI scheduling a physical downlink shared channel (PDSCH), the DCI including a group radio network temporary identifier (G-RNTI) or a system information radio network temporary identifier (SI-RNTI) for integrity information, and wherein receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network can be based on the DCI.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a time interval for receiving a PDCCH based on scheduling information, wherein receiving DCI on the PDCCH includes and receiving the DCI on the PDCCH during the time interval.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a PDCCH search space for receiving a PDCCH based on a search space configuration associated with a group of UEs, wherein receiving DCI on the PDCCH includes and receiving the DCI on the PDCCH based on the PDCCH search space.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring a G-RNTI or a cell radio network temporary identifier (C-RNTI) based on a periodicity, and wherein receiving DCI on a PDCCH may be based on the G-RNTI or the C-RNTI.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first UE group configuration includes one or more cell-specific parameters associated with the target network node.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more cell-specific parameters include one or more broadcast cell-specific parameters of system information associated with the target network node.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a UE-specific configuration includes one or more UE-specific parameters associated with a group of UEs in a non-terrestrial network.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a first UE group configuration in a logical channel associated with an RLC transparent mode or a signaling radio bearer configuration, or both.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first UE group configuration includes a common configuration or a default configuration.

[0029] A method for wireless communication at a network entity is described. The method may include: sending first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; determining a trust state of the first UE group configuration; and performing a connection operation based on the trust state of the first UE group configuration.

[0030] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; determine a trust state of the first UE group configuration; and perform a connection operation based on the trust state of the first UE group configuration.

[0031] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; means for determining a trust state of the first UE group configuration; and means for performing a connection operation based on the trust state of the first UE group configuration.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration; determine a trust state of the first UE group configuration; and perform a connection operation based on the trust state of the first UE group configuration.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing an integrity check of the first UE group configuration to obtain a trust state of the first UE group configuration, and wherein performing a connection operation may be based on the integrity check of the first UE group configuration.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control signaling indicating a change to a hash value or CRC associated with a first UE group configuration and sending third control signaling indicating a second UE group configuration based on a trust status of the first UE group configuration according to the integrity information.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control signaling indicating one or more parameters associated with the first UE group configuration.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a request to verify one or more parameters associated with a first UE group configuration and determining a trust state of the first UE group configuration based on verifying the one or more parameters associated with the first UE group configuration.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a first UE group configuration in a logical channel associated with an RLC transparent mode or a signaling radio bearer configuration, or both.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a DCI on a PDCCH, the DCI scheduling a PDSCH, the DCI including a G-RNTI or a SI-RNTI for integrity information.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending second control signaling indicating that the second UE group configuration may be based on the G-RNTI. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An example of a wireless communication system that supports managing group configuration in a wireless communication system according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 2 An example of a network architecture supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 3 An example of a wireless communication system that supports managing group configuration in a wireless communication system according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 4 An example of a process flow in support of managing group configuration in a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 5 and Figure 6 A block diagram of an apparatus supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown.

[0045] Figure 7 A block diagram of a communication manager that supports managing group configuration in a wireless communication system is shown in accordance with one or more aspects of the present disclosure.

[0046] Figure 8A diagram of a system including a device that supports managing group configuration in a wireless communication system in accordance with one or more aspects of the present disclosure is shown.

[0047] Fig. 9 and Fig.10 A block diagram of an apparatus supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown.

[0048] Fig.11 A block diagram of a communication manager that supports managing group configuration in a wireless communication system is shown in accordance with one or more aspects of the present disclosure.

[0049] Fig.12 A diagram of a system including a device that supports managing group configuration in a wireless communication system in accordance with one or more aspects of the present disclosure is shown.

[0050] Fig.13 and Fig.14 A flow chart illustrating a method of supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] A wireless communication system may include communication devices, such as UEs or network entities (e.g., evolved Node Bs (eNBs), next generation Node Bs, or Gigabit Node Bs (any of which may be referred to as gNBs), or some other base station) that support wireless communication using one or more radio access technologies. Examples of radio access technologies include 4G systems such as LTE systems, 5G systems that may be referred to as NR systems, or other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein (e.g., sixth generation (6G) systems). The wireless communication system may be a terrestrial communication system or a non-terrestrial communication system or a combination thereof. A non-terrestrial communication system may be an example of a wireless communication system that includes non-terrestrial communication devices such as a satellite. In an example of a non-terrestrial communication system, a satellite may support wireless communication with communication devices in a terrestrial communication system (e.g., at or relatively close to the ground plane).

[0052] A satellite may support wireless communications with a network entity (e.g., a base station) and a group of UEs using a communication link (also referred to as a feeder link) from a terrestrial gateway such as a network entity to the satellite. In some cases, because the satellite may be moving at high speed relative to communication equipment operating within a terrestrial communication system, the satellite may have to switch feeder links (e.g., from a terrestrial gateway such as a network entity to the satellite) to continue supporting wireless communications with the group of UEs in the terrestrial communication system. For example, a network entity for a group of UEs (such as a serving base station) may become out of coverage for the satellite, and therefore, the satellite may have to connect to another network entity (such as another base station) to hand over the group of UEs to continue supporting wireless communications with the group of UEs. Since signaling is dedicated to each UE individually, some techniques for handover of the group of UEs may be inefficient, which may be inefficient for handovers in non-terrestrial networks.

[0053] Various aspects of the present disclosure relate to protecting a group configuration (e.g., a group radio resource control (RRC) configuration) in a wireless communication system. A satellite or a network entity may send a group RRC configuration (also referred to as a common configuration) to a group of UEs in a wireless communication system. The group RRC configuration may include parameters associated with a target network entity (also referred to as a target cell). In addition, the group RRC configuration may include a UE-specific configuration for the group of UEs. In some examples, the satellite or network entity may protect the group RRC configuration using a hash value or a cyclic redundancy check (CRC) value. In some other examples, the satellite or network entity may protect the group RRC configuration based on a radio network temporary identifier (RNTI) value configured for the group of UEs as described herein.

[0054] One or both of the UE and the network entity may determine the trust state of the group RRC configuration and perform a connection procedure (e.g., a handover procedure). The trust state may be an indication of whether the group RRC configuration has been compromised. The target network entity (e.g., a target cell) may receive a handover completion message from the group of UEs and determine whether the group RRC configuration has been compromised, for example based on a hash value, a CRC value, a parameter provided by the group of UEs, etc. If the target network entity determines that the group RRC configuration has been compromised, the target network entity may send a new RRC configuration to the group of UEs. Otherwise, the target network entity may complete the handover for the group of UEs. Additionally or alternatively, one or more UEs in the group of UEs may determine whether the group RRC configuration has been compromised and perform operations as described herein.

[0055] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to managing group configurations in a wireless communication system.

[0056] Figure 1 An example of a wireless communication system 100 that supports managing group configuration in a wireless communication system according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be an LTE network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0057] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other names. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area, and the network entity 105 and the UE 115 may support signal communications over the geographic area according to one or more radio access technologies (RATs).

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

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

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

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

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

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

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

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

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

[0067] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child node associated with the IAB host, or both. The IAB host may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay transmissions to the UE 115 via the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0068] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support managing group configuration in a wireless communication system as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

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

[0072] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

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

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

[0076] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

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

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

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

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

[0081] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or other examples such as an external space between coverage areas 110 or overlapping with a coverage area.

[0082] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) compared to macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

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

[0084] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

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

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

[0087] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

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

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

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

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

[0092] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0093] The wireless communication system 100 may also operate in an ultra-high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (also known as a millimeter band) that uses a spectrum (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0094] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include other examples such as downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions.

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

[0096] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

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

[0098] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0099] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0100] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0101] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

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

[0103] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0104] The wireless communication system 100 may be a terrestrial communication system or a non-terrestrial communication system or a combination thereof. For example, the wireless communication system 100 may include one or more of a network entity 105, a UE 115, and a satellite 161. The satellite 161 may communicate with the network entity 105 (also referred to as a gateway in a non-terrestrial network) and the UE 115. The satellite 161 may be any suitable type of communication satellite configured to communicate with one or more of the network entity 105 or the UE 115 in the wireless communication system 100.

[0105] Satellite 161 may be configured to provide wireless communication services in a predefined geographic service area 110. Satellite 161 may be at any distance from the surface of the earth. In some examples, satellite 161 may be in one or more of a geosynchronous equatorial orbit (GEO), a medium earth orbit (MEO), or a low earth orbit (LEO). A GEO may be a circular and equatorial orbit around the earth at an altitude of, for example, 35,786 km. The orbital period of a GEO may be equal to the rotation period of the earth. A MEO may be a circular orbit around the earth at an altitude of, for example, between 7,000 km and 25,000 km. A LEO may be a circular orbit around the earth and be at an altitude of, for example, between 300 km and 1500 km.

[0106] In the example of a non-terrestrial communication system, the satellite 161 may be moving at high speed relative to one or more of the network entities 105 or UEs 115 operating within the terrestrial communication system (e.g., at or relatively close to the ground level). In some cases, because the satellite 161 may be moving at high speed relative to one or more of the network entities 105 or UEs 115 operating within the terrestrial communication system, the satellite 161 may have to switch the communication link 125 (e.g., from a terrestrial gateway such as the network entity 105 to the satellite) to continue to support wireless communications with the group of UEs 115 in the terrestrial communication system. For example, the network entity 105 for the group of UEs 115 may become out of coverage for the satellite 161, and therefore, the satellite 161 may have to connect to another network entity 105 and hand over the group of UEs 115 to the other network entity 105 and continue to support wireless communications with the group of UEs 115.

[0107] In some cases, as part of the handover, the network entity 105 or the satellite 161 may provide a dedicated handover command to each UE 115 in the group of UEs 115. However, this handover method for the group of UEs 115 may be inefficient. In some other cases, in order to reduce overhead signaling in the wireless communication system 100, the network entity 105 or the satellite 161 may broadcast a message including a default RRC configuration or a group RRC configuration for the target network entity 105 (e.g., a target cell). Alternatively, the network entity 105 or the satellite 161 may send a group RRC message including a default RRC configuration or a group RRC configuration for the target network entity 105. The network entity 105 or the satellite 161 may protect the group RRC message by encrypting the group RRC message with a security key. Each UE 115 in the group of UEs 115 may be associated with a separate (e.g., different) security key for decrypting the RRC message. However, this handover method for the group of UEs 115 may also be inefficient.

[0108] In other cases, the network entity 105 or the satellite 161 may establish a configured signaling radio bearer (SRB) for exchanging RRC configurations to support handover for the group of UEs 115. The RRC configuration may be a group-specific RRC configuration. The network entity 105 or the satellite 161 may send an RRC message including an RRC reconfiguration list for the group of UEs 115 to the group of UEs 115. In some cases, based on the current RRC configuration of each UE 115 in the group of UEs 115, there may be a change (e.g., Δ) in the RRC configuration. The network entity 105 or the satellite 161 may support the use of access stratum (AS) security to protect the RRC configuration. For example, the network entity 105 or the satellite 161 may support the use of a group AS key, which may be provided to each UE 115 in the group of UEs 115 and other UEs 115 joining the group of UEs 115. If no other RRC reconfiguration is provided for the UE 115, the UE 115 may continue to use the RRC configuration. One or more of the network entity 105, UE 115, or satellite 161 may derive the AS key based on a set of parameters (eg, cell-specific parameters or group-specific parameters). However, this method of handing over the group of UEs 115 using the configured SRBs may also be inefficient.

[0109] Various aspects of the present disclosure relate to handover of a group of UEs 115 in a wireless communication system 100, the wireless communication system including a satellite 161 and a network entity 105 supporting secure communication of a set of RRC configurations for the group of UEs 115, as described herein. The network entity 105 or the satellite 161 or both may include a communication manager 101, which may support managing group configurations in the wireless communication system 100 according to examples as disclosed herein. The communication manager 101 may be a reference Figures 5 to 8 Examples of various aspects of the communication manager described herein. The UE 115 may include a communication manager 102 that can support managing group configurations in the wireless communication system 100 according to examples as disclosed herein. The communication manager 102 can be reference Figures 9 to 12 Examples of aspects of the described communications manager. The wireless communications system 100 can facilitate high reliability and low latency wireless communications for network entities 105, UEs 115, and satellites 161.

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

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

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

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

[0114] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., 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 this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0115] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a 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 (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

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

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

[0118] Figure 3 An example of a wireless communication system 300 that supports managing group configuration in a wireless communication system according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may implement aspects of the wireless communication system 100 or be implemented by these aspects. For example, the wireless communication system 300 may include a network entity 105-a, a network entity 105-b, a group of UEs 115 (such as UE 115-a, UE 115-b, and UE 115-c), and a satellite 161-a, which may be as described in reference Figure 1 The examples of network entities 105, UE 115, and satellite 161 are described. Additionally or alternatively, the wireless communication system 300 may implement the Figure 2 Aspects of the described network architecture 200 may be implemented by or in accordance with these aspects. The wireless communication system 300 may support a variety of radio access technologies, including 4G systems (such as LTE systems, LTE-A systems, or LTE-A Pro systems), 5G systems, or other systems and radio technologies, including future systems and radio technologies (e.g., 6G systems) not explicitly mentioned herein. The wireless communication system 300 may provide power savings and, in some examples, may facilitate wireless communications with higher reliability and lower latency.

[0119] Satellite 161-a may support wireless communications with network entity 105-a and the set of UEs 115 via communication link 125-a (eg, a feeder link), which may be as described with reference to Figure 1 Alternatively, satellite 161-a may support wireless communications with network entity 105-b and the group of UEs 115 via communication link 125-b (e.g., a feeder link), which may be as described in reference Figure 1 An example of the communication link 125 is shown. Figure 3, the satellite 161-a may be moving at a high speed relative to the network entity 105-a operating within the wireless communication system 300. In some cases, because the satellite 161-a may be moving at a high speed relative to the network entity 105-a operating within the wireless communication system 300, the satellite 161-a may have to switch the communication link 125 (e.g., from a ground gateway such as the network entity 105-a to the satellite 161-a) to continue supporting wireless communications with the set of UEs 115 in the wireless communication system 300. For example, the network entity 105-a for the set of UEs 115 may become out of coverage for the satellite 161-a, and therefore, the satellite 161-a may have to connect to the network entity 105-b and hand over the set of UEs 115 to the network entity 105-b and continue supporting wireless communications with the set of UEs 115.

[0120] The network entity 105-a or the satellite 161-a may send (or output) an RRC configuration 305 to one or more UEs 115 in the group of UEs 115. The RRC configuration 305 may be a group RRC configuration, which may include group cell-specific parameters associated with the network entity 105-b (e.g., a target cell). In addition, the group RRC configuration may include UE-specific configurations associated with one or more UEs in the group of UEs 115, such as discontinuous reception (DRX) parameters, hybrid automatic repeat request (HARQ) parameters (e.g., packet data convergence protocol (PDCP) parameters, radio link control (RLC) parameters, medium access control (MAC) parameters, etc.), among other examples. In some examples, the first UE group configuration may be received in a logical channel configured with an RLC transparent mode or a default signaling radio bearer configuration, or both.

[0121] The network entity 105-a may send (or output) an RRC configuration 305 to one or more UEs 115 in the group of UEs 115 in a downlink data channel scheduled by a downlink control channel. For example, the network entity 105-a may send (or output) a group RRC configuration to one or more UEs 115 in the group of UEs 115 in a physical downlink shared channel (PDSCH) scheduled by a physical downlink control channel (PDCCH). In some examples, the RRC configuration 305 may be associated with a group radio network temporary identifier (RNTI). The RNTI may be a multi-bit identifier used by the network entity 105-a to identify the group of UEs 115. In some other examples, the RRC configuration 305 may be associated with a system information RNTI (SI-RNTI) or other pre-configured scheduling information. The network entity 105-a and the group of UEs 115 may process (e.g., receive and send) the RRC configuration 305 using a transparent mode (TM).

[0122] The network entity 105-b (e.g., the target cell) may broadcast system information, which may include one or more of the above-described example parameters. In some examples, the RRC configuration 305 (e.g., the group RRC configuration) may uniquely include the same parameters broadcast by the network entity 105-b (e.g., the target cell) in the system information (e.g., cell-specific and ephemeris). In this example, no protection may be required for the RRC configuration 305.

[0123] In some examples, one or more UEs 115 in the group of UEs 115 may receive a hash value or a cyclic redundancy check (CRC) associated with a default RRC configuration via a UE-specific RRC configuration (e.g., a handover command). If there is any change or the CRC check fails after receiving the UE-specific RRC configuration, one or more UEs 115 in the group of UEs 115 may determine that the RRC configuration 305 is compromised (e.g., incompatible).

[0124] The network entity 105-a or the satellite 161-a may configure an RNTI value for the group of UEs 115. For example, the configured RNTI value may be used to send and receive an RRC configuration 305 using a downlink data channel (e.g., PDSCH) scheduled by a downlink control channel (e.g., PDCCH). The network entity 105-a or the satellite 161-a may send a broadcast message based on scheduling information or a scheduling time window provided to the group of UEs 115. In some examples, the network entity 105-a or the satellite 161-a may configure a search space (e.g., a PDCCH search space) to the group of UEs 115, which the group of UEs 115 may use to receive and decode the PDCCH together with the group RNTI. The group of UEs 115 may monitor the group RNTI together with the C-RNTI or with a pre-configured periodicity.

[0125] In some examples, one or more UEs 115 in the group of UEs 115 may generate a hash value or perform a CRC check of the received RRC configuration 305 (e.g., the group RRC configuration). One or more UEs 115 in the group of UEs 115 may include an indication of the result of the generated hash value or CRC check in a handover complete message to the network entity 105-b (e.g., the target cell). If the network entity 105-b (e.g., the target cell) determines that the RRC configuration 305 (e.g., the group RRC configuration) may have been compromised, the network entity 105-b may provide a new RRC reconfiguration message to one or more UEs 115 in the group of UEs 115.

[0126] In some examples, one or more UEs 115 in the group of UEs 115 may randomly select parameters from the received RRC configuration 305 (e.g., the group RRC configuration) and include the selected parameters in a handover complete message to the network entity 105-b (e.g., the target cell) for verification. If there is a mismatch in parameter values ​​reported from at least one UE 115 or multiple UEs 115 in the group of UEs 115, the network entity 105-b may determine that the RRC configuration 305 (e.g., the group RRC configuration) may have been compromised and reconfigure the UE 115 or multiple UEs 115 in the group of UEs 115.

[0127] One or more UEs 115 in the group of UEs 115 (including one or more of UE 115-a, UE 115-b, or UE 115-c) may receive the RRC configuration 305 from the network entity 105-a, the network entity 105-b, or the satellite 161-a. For example, one or more of the network entity 105-a, the network entity 105-b, or the satellite 161-a may send or broadcast the RRC configuration 305 to one or more UEs 115 in the group of UEs 115 in the wireless communication system 300. One or more UEs 115 in the group of UEs 115 may determine a trust state associated with the received RRC configuration 305 for the group of UEs 115. For example, one or more UEs 115 in the group of UEs 115 may perform an integrity protection operation (e.g., an integrity protection check failure operation) for the received RRC configuration 305. One or more UEs 115 in the group of UEs 115 may detect that the received RRC configuration 305 has been compromised based on the integrity protection operations performed.

[0128] In some examples, based on the determination, one or more UEs 115 in the group of UEs 115 may be reconfigured with a new RRC configuration by the network entity 105-a, the network entity 105-b, or the satellite 161-a. In other examples, based on the determination, one or more UEs 115 in the group of UEs 115 may send an indication to the network entity 105-a, the network entity 105-b, or the satellite 161-a indicating a trust state associated with the received RRC configuration 305. For example, one or more UEs 115 in the group of UEs 115 may indicate to the network entity 105-a, the network entity 105-b, or the satellite 161-a that the received RRC configuration 305 has been compromised. Accordingly, one or more of the network entity 105-a, the network entity 105-b, or the satellite 161-a may send a new RRC configuration to the group of UEs 115. Additionally or alternatively, in some other examples, based on the determination, one or more UEs 115 in the group of UEs 115 initiate an RRC re-establishment procedure with the network entity 105 - b (e.g., a target cell).

[0129] One or more UEs in the group of UEs 115 may perform a handover from network entity 105-a to network entity 105-b. In some examples, one or more UEs in the group of UEs 115 may perform a handover based on a received RRC configuration 305, which may be a default RRC configuration or a group RRC configuration. One or more UEs in the group of UEs 115 may complete the handover to network entity 105-b (e.g., a target cell) using a default RRC configuration or a group RRC configuration. In some cases, the received RRC configuration 305 may not contain an indication of a modification of one or more security keys (such as an AS security key) (e.g., a master key update). In some cases, the handover command may reset one or more security configurations (e.g., security keys) for one or more UEs in the group of UEs 115 based on the handover.

[0130] One or more of the UEs 115 in the group of UEs 115 may include in the handover complete message an indication of whether the UE 115 uses a default RRC configuration or a group RRC configuration. If the default RRC configuration is used, the network entity 105-b (e.g., the target cell) may send a correct RRC reconfiguration to the one or more of the UEs 115 in the group of UEs 115. The network entity 105-b may refresh security keys (e.g., master key update) and perform wireless communications with the one or more of the UEs 115 in the group of UEs 115. Alternatively, if the group RRC configuration is used, the one or more of the UEs 115 in the group of UEs 115 may obtain a system information block (SIB) (e.g., SIB1) from the network entity 105-b (e.g., the target cell). In some examples, the one or more of the UEs 115 in the group of UEs 115 may also obtain a non-terrestrial network-specific SIB, for example, from the satellite 161-a, and send a handover complete message to the network entity 105-b. In some cases, for the provided UE-specific parameters, one or more of the UEs 115 in the group of UEs 115 may use default parameters or determine that these parameters are not configured. One or more of the UEs 115 in the group of UEs 115 may indicate this to the network entity 105-b in the handover complete message.

[0131] The network entity 105-b or the satellite 161-a may receive (or obtain) a message including one or more parameters of the group RRC configuration from one or more of the UEs 115 in the group of UEs 115. For example, the network entity 105-b or the satellite 161-a may receive (or obtain) a handover complete message including a report of the one or more parameters of the group RRC configuration from one or more of the UEs 115 in the group of UEs 115. In some examples, before the handover (e.g., during handover preparation), the network entity 105-b or the satellite 161-a may receive (or obtain) a message including one or more parameters of the group RRC configuration from the network entity 105-a. The network entity 105-b or the satellite 161-a may request the network entity 105-a to verify the one or more parameters (e.g., HARQ or CRC check) after receiving the message from one or more of the UEs 115 in the group of UEs 115. The network entity 105-b may use the group RNTI to provide the correct group RRC reconfiguration message to one or more of the UEs 115 in the group of UEs 115. One or more of the UEs 115 in the group of UEs 115 may be requested to read the system information to obtain the group RRC configuration, and other correct UE-specific configurations may be provided via RRC messaging.

[0132] Figure 4 An example of a process flow 400 for supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 may be implemented as described in reference Figure 1 and Figure 3 Aspects of the described wireless communication system 100 and the wireless communication system 300 may be implemented by aspects of these two wireless communication systems. For example, the process flow 400 may be implemented by the network entity 105-c, the network entity 105-d, the satellite 161-b, and the UE 115-d, which may be as described in reference Figure 1 and Figure 3 The examples of network entity 105, satellite 161 and UE 115 are described. In addition, process flow 400 can be implemented as described in reference Figure 2 Aspects of the described network architecture 200 may be implemented by or as such.

[0133] In the following description of process flow 400, operations between network entity 105-c, network entity 105-d, satellite 161-b, and UE 115-d may be sent in a different order than the example order shown, or operations performed by network entity 105-c, network entity 105-d, satellite 161-b, and UE 115-d may be performed in a different order or at a different time. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.

[0134] At 405, the network entity 105-c or the satellite 161-b may send a UE group configuration associated with a target network node (e.g., network entity 105-d). For example, the network entity 105-c or the satellite 161-b may broadcast an RRC message including the UE group configuration associated with the network entity 105-d. In some examples, the RRC message may also include a UE-specific configuration including integrity information for the UE group configuration.

[0135] At 410-a, UE 115-d may determine a trust state of the UE group configuration. For example, UE 115-d may perform an integrity check of the UE group configuration to obtain the trust state of the UE group configuration. In some examples, UE 115-d may determine a change in a hash value or CRC associated with the UE group configuration based on the UE-specific configuration. The integrity information may include a hash value or a CRC. Optionally, at 410-b, network entity 105-c or satellite 161-b may also determine a trust state of the UE group configuration as described herein.

[0136] At 415, UE 115-d may optionally send an indication of a trust status of the UE group configuration to network entity 105-c or satellite 161-b. For example, UE 115-d may indicate that the UE group configuration has been compromised. At 420, network entity 105-c or satellite 161-b may optionally send a new UE group configuration associated with a target network node (e.g., network entity 105-d), e.g., based on the indication that the previous UE group configuration has been compromised.

[0137] At 425, the network entity 105-c, the satellite 161-b, the UE 115-d, or the network entity 105-d, or any combination thereof, may perform a handover procedure, such as a handover from the network entity 105-c to the network entity 105-d.

[0138] Figure 5 A block diagram 500 of a device 505 supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The device 505 can be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0139] Receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to managing group configuration in a wireless communication system). The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a group of multiple antennas.

[0140] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to managing group configuration in a wireless communication system). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a group of multiple antennas.

[0141] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of managing group configuration in a wireless communication system as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0144] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0145] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a device 505 (e.g., a UE). For example, the communication manager 520 may be configured to or otherwise support a means for receiving a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The communication manager 520 may be configured to or otherwise support a means for performing a connection operation based on a trust state of the first UE group configuration.

[0146] By including or configuring a communication manager 520 according to examples as described herein, a device 505 (eg, a processor controlling or otherwise coupled with a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for reduced power consumption.

[0147] Figure 6 A block diagram 600 of a device 605 supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to managing group configuration in a wireless communication system). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a group of multiple antennas.

[0149] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to managing group configuration in a wireless communication system). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a group of multiple antennas.

[0150] Device 605 or its various components may be examples of components for performing various aspects of managing group configuration in a wireless communication system as described herein. For example, communication manager 620 may include configuration component 625, connection component 635, or any combination thereof. Communication manager 620 may be an example of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0151] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a device 605 (e.g., a UE). The configuration component 625 may be configured to or otherwise support means for receiving a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The connection component 635 may be configured to or otherwise support means for performing a connection operation based on a trust state of the first UE group configuration.

[0152] Figure 7 A block diagram 700 of a communication manager 720 that supports managing group configuration in a wireless communication system in accordance with one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of means for performing various aspects of managing group configuration in a wireless communication system as described herein. For example, the communication manager 720 may include a configuration component 725, a trust component 730, a connection component 735, an integrity component 740, a system information component 745, a downlink component 750, an identifier component 755, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0153] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. The configuration component 725 may be configured to or otherwise support means for receiving a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The connection component 735 may be configured to or otherwise support means for performing a connection operation based on a trust state of the first UE group configuration.

[0154] In some examples, integrity component 740 can be configured as or otherwise support means for performing an integrity check of the first UE group configuration to obtain a trust state of the first UE group configuration. In some examples, connection component 735 can be configured as or otherwise support means for performing an integrity check where the connection operation is based on the first UE group configuration, and where the connection operation includes a handover from a source network node to a target network node in a non-terrestrial network.

[0155] In some examples, to support performing an integrity check of the first UE group configuration, integrity component 740 may be configured as or otherwise support a component for determining a change in a hash value or CRC associated with the first UE group configuration based on a UE-specific configuration, wherein the integrity information includes a hash value or CRC.

[0156] In some examples, integrity component 740 may be configured as or otherwise support means for performing a post-integrity check operation based on a trust state configured by the first UE group.

[0157] In some examples, to support performing a connection operation, connection component 735 may be configured or otherwise support means for triggering a reestablishment of a connection operation to a target network node based on a trust state configured by the first UE group.

[0158] In some examples, the trust component 730 may be configured or otherwise support means for sending a second control signaling indicating a trust state of the first UE group configuration. In some examples, the configuration component 725 may be configured or otherwise support means for receiving a third control signaling indicating a second UE group configuration based on the trust state of the first UE group configuration according to the integrity information. In some examples, the connection component 735 may be configured or otherwise support means for performing a connection operation based on the second UE group configuration.

[0159] In some examples, integrity component 740 may be configured or otherwise support means for generating a hash value or CRC associated with the first UE group configuration. In some examples, integrity component 740 may be configured or otherwise support means for sending a second control signaling indicating a hash value or CRC associated with the first UE group configuration, the second control signaling comprising a handover complete message.

[0160] In some examples, configuration component 725 may be configured or otherwise support means for selecting one or more parameters associated with the first UE group configuration. In some examples, configuration component 725 may be configured or otherwise support means for sending second control signaling indicating one or more parameters associated with the first UE group configuration.

[0161] In some examples, this configuration excludes master security key updates.

[0162] In some examples, the configuration component 725 may be configured or otherwise support a means for sending a second control signaling indicating whether the first UE group configuration includes a common configuration or a default configuration. In some examples, the connection component 735 may be configured or otherwise support a means for performing a connection operation based on the second control signaling.

[0163] In some examples, system information component 745 can be configured to or otherwise support means for receiving a SIB associated with a target network node and a non-terrestrial network-specific SIB associated with a network entity in a non-terrestrial network. In some examples, connection component 735 can be configured to or otherwise support means for sending a second control signaling indicating completion of the handover, wherein performing the connection operation is based on the second control signaling.

[0164] In some examples, downlink component 750 may be configured to or otherwise support means for receiving a DCI on a PDCCH that schedules a physical downlink shared channel, the DCI including a G-RNTI or SI-RNTI for integrity information. In some examples, configuration component 725 may be configured to or otherwise support means for receiving a first control signaling indicating a configuration based on the DCI associated with a target network node in a non-terrestrial network.

[0165] In some examples, downlink component 750 may be configured or otherwise support means for determining a time interval for receiving PDCCH based on scheduling information. In some examples, downlink component 750 may be configured or otherwise support means for receiving DCI on PDCCH during the time interval.

[0166] In some examples, downlink component 750 may be configured to or otherwise support components for determining a PDCCH search space for receiving a PDCCH based on a search space configuration associated with the group of UEs. In some examples, downlink component 750 may be configured to or otherwise support components for receiving DCI on a PDCCH based on the PDCCH search space.

[0167] In some examples, identifier component 755 can be configured or otherwise support means for monitoring G-RNTI or C-RNTI based on periodicity. In some examples, downlink component 750 can be configured or otherwise support means for receiving DCI on PDCCH based on G-RNTI or C-RNTI.

[0168] In some examples, the first UE group configuration includes one or more cell-specific parameters associated with the target network node.

[0169] In some examples, the one or more cell-specific parameters include one or more broadcast cell-specific parameters of system information associated with the target network node.

[0170] In some examples, the UE-specific configuration includes one or more UE-specific parameters associated with a group of UEs in a non-terrestrial network.

[0171] In some examples, the one or more UE-specific parameters include DRX parameters, HARQ parameters, PDCP parameters, RLC parameters, or MAC parameters, or a combination thereof.

[0172] In some examples, configuration component 725 may be configured to or otherwise support means for receiving a first UE group configuration in a logical channel associated with an RLC transparent mode or a signaling radio bearer configuration, or both.

[0173] In some examples, the first UE group configuration includes a common configuration or a default configuration.

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

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

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

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

[0178] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to enable the device 805 to perform various functions (e.g., functions or tasks that support management of group configurations in a wireless communication system). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0179] According to examples as disclosed herein, the communication manager 820 may support wireless communication at a device 805 (e.g., a UE). For example, the communication manager 820 may be configured to or otherwise support a means for receiving a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The communication manager 820 may be configured to or otherwise support a means for performing a connection operation based on a trust state of the first UE group configuration.

[0180] By including or configuring the communication manager 820 according to examples as described herein, the device 805 can support techniques for improving communication reliability.

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

[0182] Fig. 9 A block diagram 900 of a device 905 supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0185] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of managing group configuration in a wireless communication system as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

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

[0188] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0189] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the device 905 (e.g., a network entity). For example, the communication manager 920 may be configured to or otherwise support means for sending a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The communication manager 920 may be configured to or otherwise support means for performing a connection operation based on a trust state of the first UE group configuration.

[0190] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (e.g., a processor controlling or otherwise coupled with a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for reduced power consumption.

[0191] Fig.10 A block diagram 1000 of a device 1005 supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0194] Device 1005 or its various components may be examples of components for performing various aspects of managing group configuration in a wireless communication system as described herein. For example, communication manager 1020 may include configuration component 1025, connection component 1035, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0195] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at the device 1005 (e.g., a network entity). The configuration component 1025 may be configured to or otherwise support means for sending a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The connection component 1035 may be configured to or otherwise support means for performing a connection operation based on a trust state of the first UE group configuration.

[0196] Fig.11 A block diagram 1100 of a communication manager 1120 supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of means for performing various aspects of managing group configuration in a wireless communication system as described herein. For example, the communication manager 1120 may include a configuration component 1125, a trust component 1130, a connection component 1135, an integrity component 1140, a downlink component 1145, a verification component 1150, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0197] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The configuration component 1125 may be configured to or otherwise support means for sending a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The connection component 1135 may be configured to or otherwise support means for performing a connection operation based on a trust state of the first UE group configuration.

[0198] In some examples, integrity component 1140 may be configured as or otherwise support means for performing an integrity check of the first UE group configuration to obtain a trust state of the first UE group configuration. In some examples, connection component 1135 may be configured as or otherwise support means for an integrity check where the connection operation is based on the first UE group configuration.

[0199] In some examples, integrity component 1140 may be configured or otherwise support means for receiving a second control signaling indicating a change to a hash value or CRC associated with the first UE group configuration. In some examples, configuration component 1125 may be configured or otherwise support means for sending a third control signaling indicating a second UE group configuration based on a trust state of the first UE group configuration according to the integrity information.

[0200] In some examples, configuration component 1125 may be configured as or otherwise support means for receiving second control signaling indicating one or more parameters associated with the first UE group configuration.

[0201] In some examples, verification component 1150 may be configured or otherwise support a means for receiving a request to verify one or more parameters associated with the first UE group configuration. In some examples, trust component 1130 may be configured or otherwise support a means for determining a trust state of the first UE group configuration based on verifying one or more parameters associated with the first UE group configuration.

[0202] In some examples, the one or more parameters include DRX parameters, HARQ parameters, PDCP parameters, RLC parameters, or MAC parameters, or a combination thereof.

[0203] In some examples, configuration component 1125 may be configured to or otherwise support means for sending a first UE group configuration in a logical channel associated with an RLC transparent mode or a signaling radio bearer configuration, or both.

[0204] In some examples, downlink component 1145 may be configured or otherwise support means for sending a DCI on a PDCCH scheduling a physical downlink shared channel, the DCI including a G-RNTI or SI-RNTI for integrity information.

[0205] In some examples, sending the second control signaling indicating the second UE group configuration is based on the G-RNTI.

[0206] Fig.12A diagram of a system 1200 including a device 1205 supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components of these devices. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0207] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating a signal. Where applicable, transceiver 1210 or transceiver 1210 and one or more antennas 1215 or wired interfaces may be examples of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0209] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1225) to enable the device 1205 to perform various functions (e.g., functions or tasks that support management of group configurations in a wireless communication system). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, and the processor 1235 and the memory 1225 are configured to perform various functions described herein. The processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 1230) to perform the functions of the device 1205.

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

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

[0212] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at the device 1205 (e.g., a network entity). For example, the communication manager 1220 may be configured to or otherwise support means for sending a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The communication manager 1220 may be configured to or otherwise support means for performing a connection operation based on a trust state of the first UE group configuration.

[0213] By including or configuring the communication manager 1220 according to examples as described herein, the device 1205 can support techniques for improving communication reliability.

[0214] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions that are executable by the processor 1235 to cause the device 1205 to perform various aspects of managing group configuration in a wireless communication system as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0215] Fig.13 A flowchart illustrating a method 1300 for supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0216] At 1305, the method may include receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described configuration component 725 is executed.

[0217] At 1310, the method may include performing a connection operation based on a trust state configured for the first UE group. The operations of 1310 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The described connection component 735 is performed.

[0218] Fig.14 A flowchart illustrating a method 1400 for supporting management of group configuration in a wireless communication system according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 4 as well as Figures 9 to 12 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0219] At 1405, the method may include sending first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration including a first UE group configuration and a UE-specific configuration, the UE-specific configuration including integrity information for the first UE group configuration. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.11 The described configuration component 1125 is executed.

[0220] At 1410, the method may include performing a connection operation based on a trust state configured by the first UE group. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.11 The described connection component 1135 is executed.

[0221] The following provides an overview of various aspects of the disclosure:

[0222] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration comprising a first UE group configuration and a UE-specific configuration, the UE-specific configuration comprising integrity information for the first UE group configuration; determining a trust status of the first UE group configuration; and performing a connection operation based at least in part on the trust status of the first UE group configuration.

[0223] Aspect 2: According to the method described in Aspect 1, the method also includes: performing an integrity check of the first UE group configuration to obtain the trust state of the first UE group configuration, wherein performing the connection operation is at least partially based on the integrity check of the first UE group configuration, and wherein the connection operation includes a handover from a source network node in the non-terrestrial network to the target network node.

[0224] Aspect 3: A method according to Aspect 2, wherein performing the integrity check of the first UE group configuration includes: determining a change in a hash value or CRC associated with the first UE group configuration based at least in part on the UE-specific configuration, wherein the integrity information includes the hash value or the CRC.

[0225] Aspect 4: According to any one of aspects 2 to 3, the method also includes: performing a post-integrity check operation based at least in part on the trust state of the first UE group configuration.

[0226] Aspect 5: The method according to any one of aspects 2 to 4, wherein performing the connection operation includes: triggering a re-establishment connection operation to the target network node based at least in part on the trust state configured by the first UE group.

[0227] Aspect 6: According to the method described in any one of Aspects 2 to 5, the method further includes: sending a second control signaling indicating the trust status of the first UE group configuration; and receiving a third control signaling indicating the second UE group configuration based at least in part on the trust status of the first UE group configuration according to the integrity information, wherein performing the connection operation is at least in part based on the second UE group configuration.

[0228] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: generating a hash value or CRC associated with the first UE group configuration; and sending a second control signaling indicating the hash value or the CRC associated with the first UE group configuration, the second control signaling including a handover completion message.

[0229] Aspect 8: According to the method according to any one of Aspects 1 to 7, the method also includes: selecting one or more parameters associated with the first UE group configuration; and sending a second control signaling indicating the one or more parameters associated with the first UE group configuration.

[0230] Aspect 9: The method according to any one of aspects 1 to 8, wherein the configuration excludes master security key update.

[0231] Aspect 10: According to any one of aspects 1 to 9, the method further includes: sending a second control signaling indicating whether the first UE group configuration includes a common configuration or a default configuration, wherein performing the connection operation is at least partially based on the second control signaling.

[0232] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a SIB associated with the target network node and a non-terrestrial network-specific SIB associated with a network entity in the non-terrestrial network; and sending a second control signaling indicating the completion of the handover, wherein performing the connection operation is at least partially based on the second control signaling.

[0233] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: receiving DCI on PDCCH, the DCI scheduling PDSCH, the DCI including a G-RNTI or SI-RNTI for the integrity information, wherein receiving the first control signaling indicating the configuration associated with the target network node in the non-terrestrial network is at least partially based on the DCI.

[0234] Aspect 13: According to the method according to Aspect 12, the method also includes: determining a time interval for receiving the PDCCH based at least in part on scheduling information, wherein receiving the DCI on the PDCCH includes: receiving the DCI on the PDCCH during the time interval.

[0235] Aspect 14: According to the method described in any one of Aspects 12 to 13, the method also includes: determining a PDCCH search space for receiving the PDCCH based at least in part on a search space configuration associated with a group of UEs, wherein receiving the DCI on the PDCCH includes: receiving the DCI on the PDCCH based at least in part on the PDCCH search space.

[0236] Aspect 15: According to any one of Aspects 12 to 14, the method also includes: monitoring the G-RNTI or C-RNTI based at least in part on periodicity, wherein receiving the DCI on the PDCCH is based at least in part on the G-RNTI or the C-RNTI.

[0237] Aspect 16: The method according to any one of aspects 1 to 15, wherein the first UE group configuration comprises one or more cell-specific parameters associated with the target network node.

[0238] Aspect 17: The method according to aspect 16, wherein the one or more cell-specific parameters include one or more broadcast cell-specific parameters of system information associated with the target network node.

[0239] Aspect 18: The method according to any one of aspects 1 to 17, wherein the UE-specific configuration comprises one or more UE-specific parameters associated with a group of UEs in the non-terrestrial network.

[0240] Aspect 19: The method according to aspect 18, wherein receiving the first control signaling includes: receiving the first UE group configuration in a logical channel associated with a radio link control transparent mode or a signaling radio bearer configuration or both.

[0241] Aspect 20: The method according to any one of aspects 1 to 19, wherein the first UE group configuration comprises a common configuration or a default configuration.

[0242] Aspect 21: A method for performing wireless communications at a network entity, the method comprising: sending a first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration comprising a first UE group configuration and a UE-specific configuration, the UE-specific configuration comprising integrity information for the first UE group configuration; determining a trust status of the first UE group configuration; and performing a connection operation based at least in part on the trust status of the first UE group configuration.

[0243] Aspect 22: According to the method according to Aspect 21, the method also includes: performing an integrity check of the first UE group configuration to obtain the trust state of the first UE group configuration, wherein performing the connection operation is at least partially based on the integrity check of the first UE group configuration.

[0244] Aspect 23: According to the method described in any one of Aspects 21 to 22, the method also includes: receiving a second control signaling indicating a change to a hash value or CRC associated with the first UE group configuration; and sending a third control signaling indicating a second UE group configuration based at least in part on the trust status of the first UE group configuration based on the integrity information.

[0245] Aspect 24: According to any one of aspects 21 to 23, the method further includes: receiving second control signaling indicating one or more parameters associated with the first UE group configuration.

[0246] Aspect 25: According to the method according to Aspect 24, the method also includes: receiving a request to verify the one or more parameters associated with the first UE group configuration; and determining the trust status of the first UE group configuration based at least in part on verifying the one or more parameters associated with the first UE group configuration.

[0247] Aspect 26: The method according to any one of aspects 24 to 25, wherein sending the first control signaling includes: sending the first UE group configuration in a logical channel associated with a radio link control transparent mode or a signaling radio bearer configuration or both.

[0248] Aspect 27: According to the method according to any one of Aspects 21 to 26, the method further includes: sending DCI on the PDCCH, the DCI scheduling the PDSCH, and the DCI including the G-RNTI or SI-RNTI for the integrity information.

[0249] Aspect 28: The method according to any one of aspects 21 to 27, wherein sending the second control signaling indicating the second UE group configuration is at least partially based on a G-RNTI.

[0250] Aspect 29: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 20.

[0251] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 20.

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

[0253] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 21 to 28.

[0254] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 21 to 28.

[0255] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 21 to 28.

[0256] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined in a method.

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

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

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

[0260] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using the one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0261] Computer-readable medium includes both non-transient computer storage medium and communication medium, including any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.In a manner of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used to carry or store desired program code components and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0263] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0264] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0265] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0266] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration comprising a first UE group configuration and a UE-specific configuration, the UE-specific configuration comprising integrity information for the first UE group configuration; and A connection operation is performed based at least in part on the trust state of the first UE group configuration.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: performing an integrity check of the first UE group configuration to obtain the trust state of the first UE group configuration, Wherein performing the attach operation is based at least in part on the integrity check of the first UE group configuration, and wherein the attach operation comprises a handover from a source network node to the target network node in the non-terrestrial network.

3. The apparatus of claim 2, wherein the instructions to perform the integrity check of the first UE group configuration are executable by the processor to cause the apparatus to: A change in a hash value or a cyclic redundancy check associated with the first UE group configuration is determined based at least in part on the UE-specific configuration, wherein the integrity information includes the hash value or the cyclic redundancy check.

4. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: A post integrity check operation is performed based at least in part on the trust state of the first UE group configuration.

5. The apparatus of claim 2, wherein the instructions for performing the connection operation are executable by the processor to cause the apparatus to: A re-establishment of a connection to the target network node is triggered based at least in part on the trust state of the first UE group configuration.

6. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: sending second control signaling indicating the trust state configured by the first UE group; and receiving third control signaling indicating a second UE group configuration based at least in part on the trust status of the first UE group configuration according to the integrity information, Wherein performing the connection operation is based at least in part on the second UE group configuration.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: generating a hash value or a cyclic redundancy check associated with the first UE group configuration; and Second control signaling indicating the hash value or the cyclic redundancy check associated with the first UE group configuration is sent, the second control signaling including a handover complete message.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: selecting one or more parameters associated with the first UE group configuration; and Second control signaling is sent indicating the one or more parameters associated with the first UE group configuration.

9. The apparatus of claim 1, wherein the configuration excludes master security key updates.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: sending a second control signaling indicating whether the first UE group configuration includes a common configuration or a default configuration, Wherein performing the connection operation is at least partially based on the second control signaling.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving a system information block associated with the target network node and a non-terrestrial network specific system information block associated with a network entity in the non-terrestrial network; and Second control signaling is sent indicating that the handover is complete, wherein performing the connecting operation is based at least in part on the second control signaling.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving downlink control information on a physical downlink control channel, the downlink control information scheduling a physical downlink shared channel, the downlink control information including a group radio network temporary identifier or a system information radio network temporary identifier for the integrity information, Wherein receiving the first control signaling indicating the configuration associated with the target network node in the non-terrestrial network is based at least in part on the downlink control information.

13. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: determining a time interval for receiving the physical downlink control channel based at least in part on the scheduling information, wherein the instructions for receiving the downlink control information on the physical downlink control channel are further executable by the processor to cause the apparatus to: The downlink control information is received on the physical downlink control channel during the time interval.

14. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: determining a physical downlink control channel search space for receiving the physical downlink control channel based at least in part on a search space configuration associated with a group of UEs, wherein the instructions for receiving the downlink control information on the physical downlink control channel are further executable by the processor to cause the apparatus to: The downlink control information is received on the physical downlink control channel based at least in part on the physical downlink control channel search space.

15. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: monitoring the set radio network temporary identifier or the cell radio network temporary identifier based at least in part on a periodicity, Wherein receiving the downlink control information on the physical downlink control channel is based at least in part on the group radio network temporary identifier or the cell radio network temporary identifier.

16. The apparatus of claim 1, wherein the first UE group configuration comprises one or more cell-specific parameters associated with the target network node.

17. The apparatus of claim 16, wherein the one or more cell-specific parameters comprise one or more broadcast cell-specific parameters of system information associated with the target network node.

18. The apparatus of claim 1, wherein the UE-specific configuration comprises one or more UE-specific parameters associated with a group of UEs in the non-terrestrial network.

19. The apparatus of claim 18, wherein the instructions for receiving the first control signaling are further executable by the processor to cause the apparatus to: The first UE group configuration is received in a logical channel associated with a radio link control transparent mode or a signaling radio bearer configuration or both.

20. The apparatus of claim 1, wherein the first UE group configuration comprises a common configuration or a default configuration.

21. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration comprising a first user equipment (UE) group configuration and a UE-specific configuration, the UE-specific configuration comprising integrity information for the first UE group configuration; as well as A connection operation is performed based at least in part on the trust state of the first UE group configuration.

22. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: performing an integrity check of the first UE group configuration to obtain the trust state of the first UE group configuration, Wherein performing the connection operation is at least partially based on the integrity check of the first UE group configuration.

23. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: receiving second control signaling indicating a change to a hash value or a cyclic redundancy check associated with the first UE group configuration; and Third control signaling indicating a second UE group configuration is sent based at least in part on the trust status of the first UE group configuration according to the integrity information.

24. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is received indicating one or more parameters associated with the first UE group configuration.

25. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a request to verify the one or more parameters associated with the first UE group configuration; and The trust status of the first UE group configuration is determined based at least in part on verifying the one or more parameters associated with the first UE group configuration.

26. The apparatus of claim 24, wherein the instructions for sending the first control signaling are further executable by the processor to cause the apparatus to: The first UE group configuration is sent in a logical channel associated with a radio link control transparent mode or a signaling radio bearer configuration or both.

27. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: Downlink control information is sent on a physical downlink control channel, the downlink control information scheduling a physical downlink shared channel, the downlink control information including a group radio network temporary identifier or a system information radio network temporary identifier for the integrity information.

28. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling indicating a second UE group configuration is sent based at least in part on the group radio network temporary identifier.

29. A method for wireless communication at a user equipment (UE), the method comprising: receiving first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration comprising a first UE group configuration and a UE-specific configuration, the UE-specific configuration comprising integrity information for the first UE group configuration; and A connection operation is performed based at least in part on the trust state of the first UE group configuration.

30. A method for wireless communication at a network entity, the method comprising: sending first control signaling indicating a configuration associated with a target network node in a non-terrestrial network, the configuration comprising a first user equipment (UE) group configuration and a UE-specific configuration, the UE-specific configuration comprising integrity information for the first UE group configuration; as well as A connection operation is performed based at least in part on the trust state of the first UE group configuration.

Images