Sending group switch message

Abstract

Methods, apparatus, and computer-readable media are provided for implementing an efficient group handover mechanism with less signaling overhead than single UE handover. An example method at a base station includes sending a group handover request to a target base station for a group of UEs. The method further includes receiving a group handover confirmation from the target base station. The method also includes sending a group handover message to the group of UEs.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application No. 63 / 061,640, filed August 5, 2020, entitled “TRANSMISSION OF GROUP HANDOVER MESSAGE”, and U.S. Patent Application No. 17 / 386,390, filed July 27, 2021, entitled “TRANSMISSION OF GROUP HANDOVER MESSAGE”, which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to a wireless communication system having a handover mechanism. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone communication, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

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

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of them. This overview is not an exhaustive summary of all anticipated aspects, and is neither intended to represent the key or essential elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as an introduction to the more detailed description that follows.

[0007] Satellites can be integrated into 5G communication systems to facilitate communication between base stations and UEs. For example, a transparent satellite performing amplification, spatial filtering, or frequency conversion can relay communication sent from a base station to a UE. When a transparent satellite moves, it may need to switch feeder links because the base station associated with the feeder link may be outside the satellite's coverage area. Therefore, a UE served by the satellite may need to switch to another base station. Existing handover mechanisms that individually switch each UE are inefficient for this type of handover.

[0008] Methods, apparatus, and computer-readable media are provided for implementing an efficient group handover mechanism with less signaling overhead than single user equipment (UE) handover.

[0009] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The base station sends a group handover request for a group of UEs to a target base station and receives a group handover confirmation from the target base station. The base station then sends a group handover message to the group of UEs.

[0010] In another aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a UE are provided. The UE receives a group handover message from a source base station, including an RRC configuration for one or more UEs, the group handover message is sent to a group of UEs including the one or more UEs, and the UE connects to a target base station based on the RRC configuration using the group handover message.

[0011] For the purposes described above and related, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

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

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

[0014] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

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

[0016] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

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

[0018] Figure 4A and Figure 4B An example wireless communication environment with a satellite is shown.

[0019] Figure 5 This is a sample communication stream between a UE and a base station via satellite.

[0020] Figure 6 This is a flowchart of the wireless communication method of a base station.

[0021] Figure 7 This is a flowchart of the UE's wireless communication method.

[0022] Figure 8 This is a diagram illustrating an example of how the hardware implementation of the example device is used.

[0023] Figure 9 This is a flowchart of the UE's wireless communication method.

[0024] Figure 10 This is a flowchart of the UE's wireless communication method.

[0025] Figure 11 This is a diagram illustrating an example of how the hardware implementation of the example device is used. Detailed Implementation

[0026] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations, and not as representations of the only configurations in which the concepts described herein can be practiced. The specific embodiments include detailed information intended to provide a thorough understanding of the various concepts. However, those skilled in the art will understand that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0027] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed embodiments and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the entire system.

[0028] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others.

[0029] Therefore, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or code on a computer-readable medium or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of various types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures.

[0030] While aspects and implementations are described herein by way of examples, those skilled in the art will understand that additional implementations and use cases can be implemented in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations and / or uses can be implemented via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, various applicability of the above-described innovations may occur. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessitate the inclusion of several components (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for both analog and digital purposes. The innovations described herein are intended to be implemented in devices, chip-level components, systems, distributed arrangements, aggregated or deaggregated components, end-user equipment, etc., of various sizes, shapes, and constructions.

[0031] Figure 1 This diagram illustrates an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0032] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, location, and warning message delivery. Base stations 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or core network 190) via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0033] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolution Node B (eNB) (HeNB), which can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE104 can use spectrum with a bandwidth of up to Y MHz per carrier (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.), with each carrier allocated in carrier aggregation for transmission in each direction up to a total of Yx MHz (x component carriers). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric relative to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), while the secondary component carrier may be referred to as the secondary cell (SCell).

[0034] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0035] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0036] Cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Employing NR in unlicensed spectrum can increase coverage and / or capacity of the access network.

[0037] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" band in various documents and articles. Similar naming issues sometimes arise with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this differs from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0038] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands used for these IF bands as the frequency range name FR3 (7.125GHz-24.25GHz). Frequency bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating bands have been designated as the frequency range names FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0039] In light of the foregoing, unless otherwise specifically stated, it should be understood that the terms "below 6 GHz" and the like, as used herein, can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like, as used herein, can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band.

[0040] Base station 102, whether a small cell 102' or a large-area (e.g., macro base station), may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in conventional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near-millimeter wave frequencies in communication with UE 104. When gNB 180 operates in millimeter wave frequencies or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0041] Base station 180 may transmit beamforming signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamforming signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 may receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0042] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. It acts as an entry point for content provider MBMS transmissions, authorizing and initiating MBMS bearer services within a Public Land Mobile Network (PLMN), and scheduling MBMS transmissions. The MBMS gateway 168 distributes MBMS services to base station 102 within a Broadcast-Specific Service Multicast Single Frequency Network (MBSFN) area, and is responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0043] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0044] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or any other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electrical meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart rate monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term. In some scenarios, the term UE may also be applied to one or more companion devices in a device constellation arrangement. One or more of these devices may access the network jointly and / or individually.

[0045] Refer again Figure 1 In some aspects, base station 102 or 180 may include a group handover component 198 configured to perform a group handover of a group of UEs 103, including at least two UEs 104, to another base station 102 or 180. For example, if base station 102 or 180 communicates with a group of UEs 104 via satellite 121, base station 180 may hand over the group of UEs 104 to another base station 102 when satellite 121 moves out of the coverage area of ​​base station 180. The group handover component 198 may be configured to send a group handover request for the group of UEs 103 to a target base station (e.g., base station 102 or 180), receive a group handover confirmation from the target base station, and send a group handover message to the group of UEs 103.

[0046] Each UE 104 served by base station 102 or 180 may include a group handover message component 199 configured to receive from the source base station a group handover message including an RRC configuration for one or more UEs, the group handover message being sent to a group of UEs including the one or more UEs, the UEs connecting to the target base station based on the RRC configuration using the group handover message.

[0047] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD), where for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL; or it can be time division duplex (TDD), where for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL. Figure 2A , Figure 2C In the provided example, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI), or semi-statically / statically via Radio Resource Control (RRC) signaling). It should be noted that the following description also applies to 5G NR frame structures that are TDD.

[0048] Figures 2A-2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, while for extended CP, each time slot may include 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration equal to 1 / SCS.

[0049]

[0050]

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

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

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

[0054] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DCIs within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on the CORESET, where PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and radio frame timing. Based on the Physical Layer Identity and Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides many RBs and System Frame Numbers (SFNs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0055] like Figure 2CAs shown, some REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are also possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a frequency comb structure, and the UE can transmit the SRS on one of the frequency combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0056] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback (i.e., one or more HARQ ACK bits indicate one or more ACKs and / or negative ACKs (NACK)). The PUCCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0057] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority allocation.

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

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

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

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

[0062] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0063] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives a signal via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

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

[0065] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations related to... Figure 1 The group switching message component 199 combines various aspects.

[0066] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The group switching component 198 combines various aspects.

[0067] like Figure 1 As shown, a wireless communication system can integrate one or more satellites 121 to facilitate communication between a base station and a UE. For example, a transparent satellite can relay communications from a base station to a UE to extend the base station's coverage to UEs beyond its transmission range. When relaying communication between a base station and a UE, the satellite can perform amplification, spatial filtering, or frequency conversion. The link between the base station serving the UE and the satellite can be referred to as a feeder link. When the transparent satellite moves, it may need to switch feeder links because the base station associated with the feeder link is no longer within the satellite's coverage area. Therefore, a UE served by the satellite may need to be switched to another base station (which can be referred to as the target base station, while the previous base station can be referred to as the source base station). A switching mechanism that individually switches each UE by sending a dedicated switching message (e.g., a command) to each UE may be inefficient and would involve sending a switching message via the satellite to the entire group of UEs served by the source base station. Additionally, attempting to connect each UE in the group to the target base station using separately stored switching messages could cause congestion at the target base station. If each UE in the group of UEs does not store handover messages but relies on the current serving base station (which may be referred to as the source base station) to send handover messages, then the separate handover message for each UE in the group of UEs increases system overhead.

[0068] Figure 4A and Figure 4B Example wireless communication environments 400 and 450 with satellites are shown. Figure 4AAs shown, satellite 402 can be a medium for communication between base station 404A and a group of UEs 408, including one or more UEs 406A, 406B, 406C, and 406D. Four UEs are shown for illustrative purposes. Base station 404A can transmit signal-coded data, such as user data or control data for any of the UEs in the group of UEs 408, to satellite 402. Satellite 402 can relay the data to one or more of the UEs in the group of UEs 408, such as by performing amplification, spatial filtering, or frequency conversion. Any UE in the group of UEs 408 can communicate with base station 404A by transmitting signal-coded data (such as user data) to satellite 402. Satellite 402 can then relay the data to base station 404A, such as by performing amplification, spatial filtering, or frequency conversion. The communication between base station 404A and satellite 402 (i.e., the radio link) can be referred to as feeder link A. In some aspects, satellite 402 is a transparent satellite configured to perform amplification, spatial filtering, or frequency conversion. In some respects, Satellite 402 is a regenerable satellite that can perform additional signal processing for relay, such as decoding, interference cancellation, and signal regeneration, but it does not have all the functionality of a base station.

[0069] like Figure 4B As shown, as satellite 402 moves (e.g., by orbiting the Earth), it may move out of the coverage area or transmission range of base station 404A. Therefore, base station 404A can switch the group of UEs 408 to another base station 404B that will have satellite 402 in its coverage area. Satellite 402 can switch the feeder link from base station 404A to base station 404B. Base stations 404A and 404B can communicate via a core network (such as...) Figure 1 The core network 190 (or EPC 160) shown is interconnected at 410. Base station 404A can send a handover request to base station 404B, and base station 404B can acknowledge the handover request. The handover request may request that the group of UEs be handed over to base station 404B. In order to signal the handover to the group of UEs 408, base station 404A may send a group handover message 412 to the group of UEs 408. The group handover message 412 may be sent from base station 404A to the group of UEs 408 via satellite 402. The group of UEs 408 may establish a connection with base station 404B via satellite 402 based on the group handover message. Because the group of UEs 408 has established a connection with base station 404B, satellite 402 switches the feeder link from base station 404A to base station 404B.

[0070] Figure 5 This is an example communication stream 500 between a UE and a base station via satellite. (Example:) Figure 5As shown, a group of UEs 502, including one or more UEs 502A, 502B, and 502N, communicate 510 with base station 504A via satellite 506. For example, UEs 502A-502N may have RRC connections with base station 504A. In some aspects, the communication 510 between base station 504A and the UEs in the group of UEs 502 may be exchanged via satellite 506. Communication 510 may include data, control, etc. Communication 510 may include downlink communication and / or uplink communication.

[0071] Base station 504A can transmit signal-coded data, such as user data or control data for any of the UEs in the group of UEs 502, to satellite 506. Satellite 506 can relay the data to one or more UEs in the group of UEs 502, such as by performing amplification, spatial filtering, or frequency conversion. UEs in the group of UEs 502 can communicate with base station 504A by transmitting signal-coded data (such as UE user data) to satellite 506. Satellite 506 can then relay the data to base station 504A, such as by performing amplification, spatial filtering, or frequency conversion. The communication link (i.e., radio link) between base station 504A and satellite 506 can be referred to as feeder link A. In some aspects, satellite 506 is a transparent satellite configured to perform amplification, spatial filtering, or frequency conversion. In some aspects, satellite 506 is a regenerable satellite that can additionally perform other signal processing for relay, such as decoding, interference cancellation, and signal regeneration, but does not have all the functionality of a base station.

[0072] Satellite 506 can move (e.g., by orbiting the Earth). As satellite 506 moves at 512, it can move out of the coverage area of ​​base station 504A. In some aspects, the UEs in the group of UEs 502 can determine the occurrence of triggering event 514 based on any of a variety of parameters such as: 1) a measurement event related to cell quality or propagation delay (e.g., when measurement quality is below a threshold or delay is above a threshold), 2) the position of the UE and the satellite, 3) one or more timers configured according to the service time and the expected movement of the satellite, or 4) the elevation angle of the source cell and the target cell. The UEs in the group of UEs 502 can report the occurrence of event 516 (e.g., a measurement event) to base station 504A. In some examples, the occurrence of the event can be determined at the base station, for example, based on measurement information from one or more UEs in the group of UEs 502, one or more timers, the satellite, or the position of the UE. Base station 504A can determine to initiate a group handover for the group of UEs 502. At 518, base station 504A can determine to initiate a group handover for the group of UEs 502. This determination can be based on any of a variety of triggering events. For example, base station 504A can determine to initiate a group handover based on a measurement-based trigger, wherein the cell quality of the group of UEs 502 has exceeded or fallen below a configured threshold. Alternatively or additionally, base station 504A can determine to initiate a group handover based on the location of the group of UEs 502 and / or the location of satellite 506. Alternatively or additionally, base station 504A can determine to initiate a group handover based on additional triggering conditions based on a timing advance value to the target cell. Alternatively or additionally, base station 504A can determine to initiate a group handover based on the elevation angle of the source cell and the target cell. Base station 504A can determine to initiate a group handover based on measurements from the group of UEs 502 or independently of measurements performed by the group of UEs 502.

[0073] After base station 504A determines at 518 that it is switching the group of UEs 502, base station 504A may send a handover request 520 to base station 504B and receive a handover confirmation 522 from base station 504B. Base station 504A may then send one or more group handover messages 524 to the group of UEs 502. Each UE in the group processes the group handover message 524, as shown at 525, to determine that the UE is switching to the target base station.

[0074] In some aspects, as part of a handover confirmation 522 or group handover message 524, base station 504A may send an RRC reconfiguration with a synchronization message to the group of UEs 502 in a PDSCH that includes a group handover message or group handover command. A cell-specific common search space can be configured, and the group of UEs 502 may monitor the cell-specific common search space to receive a PDSCH indicating a HO command for the group of UEs. The group handover command may include bits scrambled based on a cell-specific group radio network temporary identifier (RNTI). Signaling radio bearer 1 (SRB1) information may provide UE-specific configuration, and UE-specific integrity protection and encryption of the RRC message may be applied to the SRB1 information of each individual UE in the group. SRB-x (such as SRB3 or SRB4) may include group-specific configuration information and may be protected with known security information for each UE in the group. For example, access stratum (AS) security information may be sent to the group of UEs 502, and signaling radio bearer information with integrity protection and encryption based on AS security information for the group of UEs may be sent to the group of UEs. A common group AS key can be provided to each UE in the group of UEs 502 upon joining the group. In some aspects, the common group AS key can be derived using a cell-specific or group-specific set of parameters. For group handover, the base station can send an RRC message including a list of RRC reconfiguration messages for multiple UEs. The RRC reconfiguration message can include an incremental RRC configuration for each UE based on the current configuration of the specific UE. The incremental RRC configuration can refer to a configuration that includes parameters different from the UE's current configuration but excludes parameters identical to the UE's current configuration. In some aspects, one or more UEs in the group of UEs 502 may not be provided with RRC reconfiguration by the base station. The UE may interpret the absence of RRC reconfiguration or the RRC reconfiguration increment as an indication to continue using the UE's current RRC configuration with the target base station. In such aspects, UEs in the group of UEs 502 can continue to 526 to initiate an RRC connection with the target base station 504B using their respective current RRC configurations. The UEs in the group of UEs 502 can receive a response from base station 504B at 528 and can send an RRC reconfiguration completion indication at 530. At 532, the UEs in the group of UEs 502 can send or receive user data with the target base station 504B. In some aspects, communication between base station 504B and the UEs in the group of UEs 502 (e.g., data 532) can be exchanged via satellite 506.

[0075] In some aspects, base station 504A can send a group handover message 524 comprising multiple RRC messages to the group of UEs 502. Multiple RRC messages can be multiplexed at the Media Access Control (MAC) using one or more identical or different Logical Channel Identifiers (LCIDs). Each UE in the group of UEs 502 can attempt to decode all RRC messages (such as those in SRB1) within the multiplexed RRC messages. In some aspects, each UE can utilize its current SRB1 configuration and AS security profile to attempt to decode multiple RRC messages. UEs in the group can decode a single RRC message within the multiplexed RRC messages based on their AS security profile; for example, an RRC message might convey an integrity protection check for the UE. In some aspects, each UE can use a default SRB1 configuration. After decoding the RRC messages, the UEs in the group of UEs 502 can initiate an RRC reconfiguration with the target base station 504B. The UEs in the group of UEs 502 can receive a response 528 from the base station 504B and can send an RRC reconfiguration completion indication 530. After establishing a connection with the target base station, the UEs in the group of UEs 502 can send or receive user data 532 with the target base station 504B.

[0076] Each UE may be able to decode one RRC message intended for that UE, but may not be able to decode other RRC messages not intended for that UE, as these other RRC messages would fail the integrity protection check and may subsequently be discarded. Each RRC reconfiguration may include an incremental configuration based on the default UE configuration for the target. An incremental configuration may refer to a configuration that includes parameters different from the default configuration but excludes parameters identical to the default configuration. The group size (e.g., the number of UEs in the group 502) may be configured by the network to fit group handover messages in a single Transport Block Signal (TBS) size. For example, the number of UEs in the group may be based on the amount of group handover information that can be sent in one or more TBSs (e.g., a single TBS).

[0077] In some aspects, the group handover message 524 may be sent in a broadcast or multicast message received by the group of UEs. In some aspects, a public security key of the group of UEs 502 may be used to protect the broadcast or multicast message. The public security key may be provided to the group of UEs 502 using dedicated RRC signaling. In some aspects, each UE in the group of UEs 502 may check the broadcast or multicast message based on time and / or location to determine whether a group handover message 524 has been provided for the target cell of the target base station 504B. In some aspects, base station 504A may (e.g., in communication 510) send a group-specific or UE-specific indication to each UE in the group of UEs 502 to check the broadcast or multicast message to schedule the time for sending the group handover message 524 as a broadcast message. In some aspects, scheduling information may be provided to the group of UEs in the group handover message. In some aspects, the scheduling information may be provided to the group of UEs using RRC reconfiguration when a UE moves to an RRC connected state, or it may be broadcast in system information such as SIB1. In some aspects, each UE in the group of UEs 502 can acquire a broadcast or multicast PDSCH at 526 before accessing the target cell. The broadcast or multicast messages can be protected using a public security key of the group of UEs. The public security key can be provided to the group of UEs or to each UE in the group in dedicated signaling used for the group of UEs. If no group handover message is configured or received, each UE in the group of UEs 502 can initiate an RRC reconfiguration procedure at 526, such as based on a pre-configured time / location. The UEs in the group of UEs 502 can receive a response 528 from base station 504B and can send an RRC reconfiguration completion indication 530. The UEs in the group of UEs 502 can then send or receive user data 532 with the target base station 504B.

[0078] RRC reconfiguration may include incremental configuration. Incremental configuration may be based on the source configuration or current configuration of each UE. Incremental configuration may indicate parameters that differ from the UE's source configuration or default configuration, but not parameters that will remain unchanged. In some aspects, the incremental configuration of each UE in the group of UEs 502 may be based on the default UE configuration of the target base station 504B. The default UE configuration of the target base station 504B may be a complete configuration of parameters used for communication with the target base station. In some aspects, the default UE configuration of the target base station 504B may be provided prior to the handover decision at 518. In some aspects, the group handover message may provide a common target configuration for each UE in the group of UEs. The RRC reconfiguration list may include incremental configurations that individually indicate one or more parameters that will be changed for each UE.

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

[0080] A new feeder link to the new base station may result in different communication time delays. In some aspects, the group handover message may include a new round-trip delay (RTD) value between the satellite and the gateway (i.e., the target base station 504B). The new RTD value may be used by each of the group of UEs 502 for uplink pre-compensation, such as in uplink transmissions in 526, 530, and 532. The new RTD value may be included in the System Information Block (SIB).

[0081] In some aspects, if the timing advance (TA) of the target base station 504B will differ from that of base station 504A, base station 504A may use UE-specific or group-specific indications (e.g., using the DCI of the group RNTI) to provide adjustments to the TA to compensate for the feeder link propagation delay common to each of the group of UEs 502. The pre-compensation applied to the UE-to-satellite link may remain unchanged. UEs in the group of UEs 502 may use the same TA for the target base station 504B without receiving indications for TA adjustment. In some aspects, UEs in the group of UEs 502 may read system information to receive the latest common configuration, which may include paging, random access, and an initial pre-compensated TA value for initial access, and then initiate RRC access with base station 504B at 526. In such aspects, the group handover message may not include common configuration or system information to reduce the size of the handover message, and UEs in the group of UEs 502 may initiate RRC access with base station 504B at 526 based on pre-configured execution conditions (such as time, location, etc.).

[0082] In some respects, the SIB in the cell is considered unchanged after the feeder link is changed from base station 504A to base station 504B. Information about the SIB can be transparent to UEs in IDLE or RRC_INACTIVE mode. For such UEs, changes to the RTD may not trigger the SI update process.

[0083] Figure 6This is a flowchart 600 of a wireless communication method. This method can be performed by a base station (e.g., base station 102 / 180; base station 310; base station 504A, base station 404A, device 802). This method helps provide more efficient handover for a group of UEs and reduces the signaling overhead of handing each UE to the target base station.

[0084] At 604, the base station sends a group handover request for the group of UEs to the target base station. For example, base station 504A may send handover request 520 to target base station 504B. For example, sending 604 may be performed by group handover request component 842. Sending 604 may include combining... Figure 5 The handover request 520 describes various aspects. In some aspects, the base station sends a group handover request to check with the target base station whether the target base station has the resources to process the handover.

[0085] At 606, the base station receives a handover acknowledgment from the target base station. For example, base station 504A can receive a handover acknowledgment 522 from base station 504B. For example, receiving 606 can be performed by receiving component 830. Receiving 606 may include... Figure 5 The handover confirmation 522 describes various aspects. In some aspects, the target base station may send a handover confirmation to indicate that the target base station can be used as a target for handover.

[0086] At 608, the base station sends a group handover message to the group of UEs. For example, sending 608 can be performed by sending component 834. For example, base station 504A can send group handover message 524 to the group of UEs 502. In some aspects, the group handover message is sent to each UE in the group of UEs in a synchronized RRC reconfiguration. In some aspects, the group handover message is sent to the group of UEs based on a cell-specific common search space. In some aspects, at least a portion of the group handover message is scrambled with a cell-specific group RNTI. In some aspects, the RRC reconfiguration includes RRC messages that include a list of RRC reconfiguration messages for each UE in the group of UEs. In some aspects, the RRC reconfiguration messages in the RRC reconfiguration message list indicate differences in the current configuration of the respective UE.

[0087] Figure 7 This is a flowchart 700 of a wireless communication method. This method can be performed by a base station (e.g., base station 102 / 180; base station 310; base station 504A, base station 404A, device 802). This method helps provide more efficient handover for a group of UEs and reduces the signaling overhead of handing each UE to the target base station.

[0088] In some aspects, at 701, the base station provides a public AS key and a group-specific or default signaling radio bearer configuration to a group of UEs. For example, base station 504A may provide a public AS key and a group-specific or default signaling radio bearer configuration to a group of UEs. In some aspects, the base station issues new SRB information to the group of UEs, the new SRB information having integrity protection and encryption based on the public AS key and the group-specific new SRB configuration. In some aspects, providing 701 may be performed by AS key and configuration component 848.

[0089] At 702, the base station determines to perform a group handover for the group of UEs. For example, determination 702 can be performed by determination component 840. For example, base station 504A can determine to perform a group handover at 518. In some aspects, the base station communicates with the group of UEs via a transparent satellite, such as satellite 506 / 402. The base station can determine to perform a group handover for the group of UEs based on various triggers that may be triggered due to satellite movement. For example, the base station can determine to perform a group handover based on a measurement-based trigger, where the cell quality change of the group of UEs exceeds a pre-configured threshold. Alternatively or additionally, the base station can determine to perform a group handover based on the positions of the group of UEs and the satellite. Alternatively or additionally, the base station can determine to perform a group handover based on additional triggering conditions based on timing advance values ​​to the target cell. Alternatively or additionally, the base station can determine to perform a group handover based on the elevation angles of the source cell and the target cell. Base station 504A can determine to perform a group handover based on measurements performed by the group of UEs or independently of such measurements.

[0090] At 704, the base station sends a group handover request for the group of UEs to the target base station. For example, base station 504A may send handover request 520 to target base station 504B. For example, sending 704 may be performed by group handover request component 842. Sending 704 may include combining... Figure 5 The handover request 520 describes various aspects. In some aspects, the base station sends a group handover request to check with the target base station whether the target base station has the resources to process the handover.

[0091] At 706, the base station receives a handover acknowledgment from the target base station. For example, base station 504A can receive a handover acknowledgment 522 from base station 504B. For example, receiving 706 can be performed by receiving component 830. Receiving 706 may include... Figure 5 The handover confirmation 522 describes various aspects. In some aspects, the target base station may send a handover confirmation to indicate that the target base station can be used as a target for handover.

[0092] In some aspects, at 707, the base station provides configuration information for each UE in the group of UEs. For example, base station 504A may provide configuration information for each UE in the group of UEs 502. For example, providing 707 may be performed by an AS key and configuration component 848. The configuration information for each UE in the group of UEs may indicate changes to one or more configuration parameters for that UE relative to a common configuration for the target base station. In some aspects, the common configuration includes a default configuration for the target base station applicable to all UEs (each UE in the group of UEs) or a complete configuration for the target base station. In some aspects, the configuration information is provided to the group of UEs in the group handover message or in a downlink message prior to the handover decision. In some aspects, providing 707 may be part of sending 708 or may occur before determining 702.

[0093] At 708, the base station sends a group handover message to the group of UEs. For example, sending 708 can be performed by a sending component 834. For example, base station 504A can send a group handover message 524 to the group of UEs 502. In some aspects, the group handover message is sent to each UE in the group of UEs in a synchronized RRC reconfiguration. In some aspects, the group handover message is sent to the group of UEs based on a cell-specific common search space. In some aspects, at least a portion of the group handover message is scrambled with a cell-specific group RNTI. In some aspects, the RRC reconfiguration includes RRC messages that include a list of RRC reconfiguration messages for each UE in the group of UEs. In some aspects, the RRC reconfiguration messages in the RRC reconfiguration message list indicate differences in the current configuration of the respective UE.

[0094] In some aspects, the group handover message includes a MAC message that comprises multiplexed Radio Resource Control (RRC) messages using one or more Logical Channel Identifiers (LCIDs). In some aspects, each RRC message in the multiplexed RRC messages is based on the SRB configuration and AS key of the UEs in the group. In some aspects, the SRB configuration is UE-specific or includes a default radio bearer configuration. In some aspects, each RRC message in the multiplexed RRC messages includes an incremental configuration based on the default UE configuration for the target base station. In some aspects, the size of the group of UEs is based on the number of multiplexed RRC messages allowed in a single TBS.

[0095] In some aspects, group handover messages are sent in multicast messages. Multicast messages may be sent at a specified or predefined time or at the location of the group of UEs. The base station may send an indication to one or more UEs in the group of UEs when to check the multicast message. In some aspects, the multicast message includes scheduling information. In some aspects, the multicast message is encrypted using a group public security key for the group of UEs.

[0096] In some aspects, the handover message includes an indication to continue using the current source cell configuration with the target base station. The handover message may include a new security key for communicating with the target base station. In some aspects, the handover message includes the NCC and C-RNTI for the target base station. In some aspects, the handover message includes a new RTD value for the target base station. In some aspects, the handover message includes a new TA for the target base station.

[0097] Figure 8 Figure 800 illustrates an example of a hardware implementation for device 802. Device 802 is a BS and includes a baseband unit 804. Baseband unit 804 can communicate with UE 104 via a cellular RF transceiver. Baseband unit 804 may include computer-readable medium / memory. Baseband unit 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by baseband unit 804, causes baseband unit 804 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 804 during software execution. Baseband unit 804 also includes a receiving component 830, a communication manager 832, and a transmitting component 834. Communication manager 832 includes one or more of the components shown. Components within communication manager 832 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 804. The baseband unit 804 may be a component of the BS 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0098] Communication manager 832 includes a determining component 840 configured to determine a group handover to be performed on a group of UEs, for example, as in combination Figure 7 The determination described in 702.

[0099] Communication manager 832 includes group handover request component 842, which sends a group handover request for the group of UEs to a target base station, for example, as in combination with Figure 6 Sending 604 and Figure 7 The 704 error message is described.

[0100] Communication manager 832 includes group handover confirmation component 844, which receives group handover confirmation from target base station, for example, as in combination with Figure 6 Receive 606 and Figure 6 As described in Receive 706.

[0101] Communication manager 832 includes group handover message component 846, which sends group handover messages to the group of UEs, for example, as in combination with Figure 6 Sending 608 and Figure 7 As described in the 708 message.

[0102] Communication manager 832 includes AS key and configuration component 848, which provides configuration information for each UE in the group of UEs and provides the group of UEs with a public AS key and group-specific or default signaling radio bearer configuration, for example, as combined with Figure 7 The provisions described in 701 and 707 are provided.

[0103] The device may include execution Figure 6 and Figure 7 Each of the algorithm boxes in the aforementioned flowchart is an additional component. Therefore, Figure 6 and Figure 7 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or a combination thereof.

[0104] In one configuration, device 802, particularly baseband unit 804, includes components for determining to perform group handover to a group of UEs. Baseband unit 804 may also include components for sending a group handover request to a target base station for the group of UEs. Baseband unit 804 may further include components for receiving group handover confirmation from the target base station. Baseband unit 804 may also include components for sending a group handover message to the group of UEs. The aforementioned components may be one or more of the aforementioned components of device 802, configured to perform the functions described above. As described above, device 802 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the aforementioned components may be TX processor 316, RX processor 370, and controller / processor 375, configured to perform the functions described above.

[0105] Figure 9This is a flowchart 900 of a wireless communication method. The method can be performed by a UE served by a source base station (e.g., UE 94; UEs in the group of UEs 408; UEs in the group of UEs 502; device 802). In some aspects, the size of the group of UEs is based on the amount of RRC messages allowed in a single TBS. This method helps provide more efficient handover of a group of UEs and reduces the signaling overhead of handing each UE to the target base station.

[0106] At 908, the UE can receive a group handover message from the source base station, including RRC configurations for one or more UEs, which is sent to a group of UEs including the one or more UEs. For example, the UE in UE 502 can receive group handover message 524 from base station 504A. For example, receiving at 908 can be performed by group handover message receiving component 1140. In some aspects, the source base station communicates with the group of UEs via satellite. In some aspects, the group handover message is received for the group of UEs in a synchronized RRC reconfiguration. In some aspects, the UE receives the group handover message in a cell-specific common search space. In some aspects, at least a portion of the group handover message is scrambled with a cell-specific group RNTI.

[0107] At point 910, the UE uses the RRC configuration to connect to the target base station based on the group handover message. For example, the UE in UE 502 can establish a connection with base station 504B based on the group handover message. For example, connection 910 can be performed by group handover connection component 1142. In some aspects, in order to connect to the target base station, the UE decodes an RRC message in the multiplexed RRC message that points to the UE.

[0108] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be performed by a UE served by a source base station (e.g., UE 104; UEs in the group of UEs 408; UEs in the group of UEs 502; device 802). In some aspects, the size of the group of UEs is based on the amount of RRC messages allowed in a single TBS. This method helps provide more efficient handover of a group of UEs and reduces the signaling overhead of handing each UE to the target base station.

[0109] At 1006, the UE receives a public AS key and a group-specific or default SRB configuration common to the group of UEs from the source base station. For example, the UE in UE 502 can receive the public AS key and group-specific or default SRB configuration from base station 504A. For example, receiving at 1006 can be performed by AS key component 1148. In some aspects, the new SRB information in the group handover message includes integrity protection and encryption based on the public AS key and the new group-specific SRB configuration.

[0110] At 1008, the UE receives a group handover message from the source base station, including RRC configurations for one or more UEs, which is sent to a group of UEs including the one or more UEs. For example, the UE in UE 502 can receive group handover message 524 from base station 504A. For example, receiving 1008 can be performed by group handover message receiving component 1140. In some aspects, the source base station communicates with the group of UEs via satellite. In some aspects, the group handover message is received for the group of UEs in a synchronized RRC reconfiguration. In some aspects, the UE receives the group handover message in a cell-specific common search space. In some aspects, at least a portion of the group handover message is scrambled with a cell-specific group RNTI.

[0111] In some aspects, RRC reconfiguration includes RRC messages comprising a list of RRC reconfiguration messages for each UE in the group of UEs. In some aspects, the RRC reconfiguration messages for a UE in the list indicate one or more different parameters regarding the current configuration of the UE. In some aspects, the group handover message includes a MAC message comprising multiplexed RRC messages using one or more LCIDs.

[0112] In some aspects, the UE receives the group handover message in a multicast message. As part of 1008, at 1009, the UE can check the multicast message for the group handover message based on a specified or predefined time or location, and can receive an indication about the multicast message from the source base station. In response to receiving the indication, the UE can receive the group handover message in a multicast message. The indication can be specific to the UE or can be for a group of UEs. In some aspects, the UE acquires the multicast message in the PDSCH before accessing the target cell of the target base station.

[0113] In some aspects, the multicast message includes scheduling information. In some aspects, the multicast message is encrypted using a group public security key provided for the group of UEs. In some aspects, the group handover message includes an indication to continue using the current source cell configuration with the target base station. In some aspects, the group handover message includes a new security key for communicating with the target base station. In some aspects, the group handover message includes the NCC and C-RNTI for the target base station. In some aspects, the group handover message includes a new RTD value. In some aspects, the group handover message includes a new TA.

[0114] In some aspects, system information including common configuration and pre-compensation values ​​for the target base station may be included in the group handover message. In some aspects, system information including common configuration and pre-compensation values ​​for the target base station is not included in the group handover message. In such aspects, the UE may receive system information including common configuration and pre-compensation values ​​for the target base station at 1002 before connecting to the target base station. In some aspects, the common configuration for the target base station includes a default configuration or a full configuration for the target base station applicable to each UE in the group of UEs. In some aspects, this configuration information is received in the group handover message or in a downlink message prior to the handover decision. In some aspects, at 1004, the UE may receive configuration information from the source base station indicating changes to one or more configuration parameters for the UE relative to the common configuration for the target base station.

[0115] At 1010, the UE uses RRC configuration to connect to the target base station based on the group handover message. For example, the UE in UE 502 can establish a connection with base station 504B based on the group handover message. For example, connection 1010 can be performed by group handover connection component 1142. In some aspects, in order to connect to the target base station, the UE decodes an RRC message in a multiplexed RRC message that is directed to the UE. In some aspects, the UE uses the current UE-specific SRB 1 and AS security key / profile received at reception 1006 to attempt to decode the multiplexed RRC message to determine the RRC message intended for it. In some aspects, the UE uses a default SRB1 (such as the SRB1 received at reception 1002 or 1006) to attempt to decode the multiplexed message. In some aspects, the UE may be able to decode the RRC message intended for the UE and may not be able to decode other RRC messages.

[0116] In some respects, an RRC message directed to the UE from a multiplexed RRC message includes an incremental configuration based on the default UE configuration for the target base station.

[0117] In some aspects, group handover messages are sent in synchronization messages, which are sent to each UE in the group of UEs during RRC reconfiguration.

[0118] In some aspects, each UE in the group of UEs is configured with a cell-specific group RNTI. In some aspects, RRC reconfiguration includes RRC messages comprising a list of RRC reconfiguration messages for each UE in the group of UEs. In some aspects, each UE in the group of UEs receives a public AS key and group-specific configuration. In some aspects, each UE in the group of UEs is configured with a UE-specific SRB1.

[0119] In some aspects, group handover messages are sent in multiple RRC messages multiplexed at the MAC using one or more LCID or Cell Radio Network Temporary Identifier (C-RNTI) MAC control elements.

[0120] Figure 11 Figure 1100 illustrates an example of a hardware implementation for device 1102. Device 1102 is a UE and includes a cellular baseband processor 1104 (also referred to as a modem) coupled to a cellular RF transceiver 1122 and one or more Subscriber Identity Module (SIM) cards 1120, an application processor 1106 coupled to a Secure Digital (SD) card 1108 and a screen 1110, a Bluetooth module 1112, a Wireless Local Area Network (WLAN) module 1114, a Global Positioning System (GPS) module 1116, and a power supply 1118. The cellular baseband processor 1104 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1122. The cellular baseband processor 1104 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1104 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1104, the software causes the cellular baseband processor 1104 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1104 during software execution. The cellular baseband processor 1104 also includes a receiving component 1130, a communication manager 1132, and a transmitting component 1134. The communication manager 1132 includes one or more of the components shown. The components within the communication manager 1132 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1104. The cellular baseband processor 1104 can be a component of the UE 350 and can include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1102 can be a modem chip and only include the baseband processor 1104, and in another configuration, the device 1102 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1102.

[0121] Communication manager 1132 includes group handover message receiving component 1140, which is configured to receive from a source base station a group handover message including RRC configurations for one or more UEs, the group handover message being sent to a group of UEs including the one or more UEs, for example, as in combination Figure 9 908 and Figure 10 The 1008 in the text describes.

[0122] Communication manager 1132 also includes group handover connection component 1142, which is configured to connect to the target base station using RRC configuration based on group handover messages, for example, as in combination with Figure 9 910 and Figure 10 The 1010 in the text describes.

[0123] Communication manager 1132 may also include SI receiving component 1144, which is configured to receive system information from the source base station, including common configuration and pre-compensation values, for example, as combined with Figure 10 As described in 1002.

[0124] Communication manager 1132 may also include SI change receiving component 1146, configured to receive configuration information from source base station indicating changes to one or more configuration parameters of the UE relative to the common configuration of the target base station, for example, as in combination with Figure 10 As described in 1004.

[0125] Communication manager 1132 may also include AS key component 1148, which is configured to receive a public AS key and group-specific or default SRB configuration from the source base station, for example, as combined with Figure 10 As described in 1006.

[0126] Communication manager 1132 may also include indication receiving component 1150, which is configured to check for group handover messages in the multicast message based on a specified or predefined time or location and receive indications about the multicast message from the source base station, for example, as in combination with Figure 10 As described in 1009.

[0127] The device may include execution Figure 9 and Figure 10 Each of the algorithm boxes in the aforementioned flowchart is an additional component. Therefore, Figure 9 and Figure 10 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or a combination thereof.

[0128] In one configuration, apparatus 1102, particularly cellular baseband processor 1104, includes components for receiving group handover messages from a source base station to a group of UEs and components for connecting to a target base station based on the group handover messages. The aforementioned components may be one or more of the aforementioned components of apparatus 1102, configured to perform the functions described above. As described above, apparatus 1102 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned components may be TX processor 368, RX processor 356, and controller / processor 359, configured to perform the functions described above.

[0129] It should be understood that the specific order or hierarchy of boxes in the disclosed process / flowchart is illustrative of the exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of boxes in the process / flowchart may be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the individual boxes in a sample order, but this does not imply limitation to the specific order or hierarchy presented.

[0130] The above description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein elements referenced in the singular are not intended to mean “one and only one” (unless specifically stated so), but rather “one or more”. Terms such as “if,” “when,” and “while” should be interpreted as “in the case of,” rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply a direct action in response to the occurrence of an action or during the occurrence of an action, but merely imply that an action will occur if the condition is met, without imposing a specific or direct time limit on the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as being preferred or more advantageous than other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of one or more A, B, or C. Elements of the various aspects described throughout this disclosure that are known to those skilled in the art or subsequently known all structural and functional equivalents are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be intended for public use, whether or not such disclosure is expressly recited in the claims. Terms such as “module,” “mechanism,” “component,” and “equipment” may not be substitutes for the term “part.” Therefore, unless an element is explicitly described using the phrase “part for…”, no claim element should be interpreted as a part plus a function.

[0131] The following examples are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein, without limitation.

[0132] Aspect 1 is an apparatus for wireless communication for a base station, comprising: a memory; and at least one processor coupled to the memory and configured to: send a group handover request to a group of UEs to a target base station; receive a group handover confirmation from the target base station; and send a group handover message to the group of UEs.

[0133] Aspect 2 is the apparatus described in aspect 1, wherein the base station communicates with the group of UEs via a satellite, and wherein the group handover message is sent to each of the group of UEs in a synchronized RRC reconfiguration.

[0134] Aspect 3 is the apparatus of any one of Aspects 1-2, wherein the group handover message is sent to the group of UEs based on a cell-specific common search space, and wherein at least a portion of the group handover message is scrambled with a cell-specific group RNTI.

[0135] Aspect 4 is the apparatus of any one of Aspects 1-3, wherein at least one processor coupled to the memory is further configured to: provide a public AS key and a group-specific or default signaling radio bearer configuration to the group of UEs; wherein the base station issues new SRB information to the group of UEs, the new SRB information having integrity protection and encryption based on the public AS key and the group-specific new SRB configuration.

[0136] Aspect 5 is the apparatus of any one of Aspects 1-4, wherein the group handover message includes an RRC message, the RRC message including a list of RRC reconfiguration messages for each UE in the group of UEs, and wherein the RRC reconfiguration messages in the list of RRC reconfiguration messages indicate differences in the current configuration of the respective UE.

[0137] Aspect 6 is the apparatus of any one of Aspects 1-5, wherein the group switching message includes a MAC message that multiplexes an RRC message using one or more LCID or C-RNTI MAC control elements.

[0138] Aspect 7 is the apparatus of any one of Aspects 1-6, wherein each RRC message in the multiplexed RRC messages is based on the SRB configuration and AS key of the UE in the set of UEs, and wherein the SRB configuration is specific to the UE or includes a default radio bearer configuration.

[0139] Aspect 8 is the apparatus of any one of Aspects 1-7, wherein each RRC message in the multiplexed RRC message includes an incremental configuration based on the default UE configuration for the target base station.

[0140] Aspect 9 is the apparatus of any one of Aspects 1-8, wherein the size of the group of UEs is based on the amount of multiplexed RRC messages allowed in a single TBS.

[0141] Aspect 10 is the apparatus of any one of Aspects 1-9, wherein the group switching message is sent in a multicast message, and wherein the multicast message is sent at a specified or predefined time or location for the group of UEs.

[0142] Aspect 11 is the apparatus of any one of Aspects 1-10, wherein at least one processor coupled to the memory is further configured to send an indication to one or more of the group of UEs of when to inspect the multicast message.

[0143] Aspect 12 is the apparatus of any one of Aspects 1-11, wherein the multicast message is encrypted using a group public security key for the group of UEs.

[0144] Aspect 13 is the apparatus of any one of Aspects 1-12, wherein at least one processor coupled to the memory is further configured to: provide configuration information for each of the group of UEs, wherein the configuration information of the UEs in the group of UEs indicates a change in one or more configuration parameters of the UE relative to a common configuration of the target base station, wherein the common configuration of the target base station includes a default configuration of the target base station applicable to each of the group of UEs or a full configuration of the target base station, wherein the configuration information is provided to the group of UEs in the group handover message or in a downlink message prior to the handover decision.

[0145] Aspect 14 is an apparatus according to any one of Aspects 1-13, wherein the group handover message includes one or more of the following: an indication to continue using the current source cell configuration with the target base station, a new security key for communicating with the target base station, the NCC and the C-RNTI of the target base station, a new RTD value of the target base station, or a new TA of the target base station.

[0146] Aspect 15 is an apparatus for wireless communication at a UE served by a source base station, comprising: a memory; and at least one processor coupled to the memory and configured to: receive from the source base station a group handover message including an RRC configuration for one or more UEs, the group handover message being sent to a group of UEs including the one or more UEs; and connect to a target base station based on the group handover message using the RRC configuration.

[0147] Aspect 16 is the apparatus described in aspect 15, wherein the source base station communicates with the group of UEs via a satellite.

[0148] Aspect 17 is an apparatus according to any one of Aspects 15-16, wherein the group handover message is received for the group of UEs in a synchronized RRC reconfiguration, wherein the UEs receive the group handover message in a cell-specific common search space, and wherein at least a portion of the group handover message is scrambled with a cell-specific group RNTI.

[0149] Aspect 18 is the apparatus of any one of Aspects 15-17, wherein at least one processor coupled to the memory is further configured to receive a public AS key and a group-specific or default SRB configuration shared by the group of UEs from the source base station.

[0150] Aspect 19 is the apparatus of any one of Aspects 15-18, wherein the new SRB information in the group switching message includes integrity protection and encryption based on the public AS key and the group-specific new SRB configuration.

[0151] Aspect 20 is the apparatus of any one of Aspects 15-19, wherein the RRC reconfiguration includes RRC messages, the RRC messages including a list of RRC reconfiguration messages for each of the group of UEs, and wherein the RRC reconfiguration messages for the UE in the list of RRC reconfiguration messages indicate one or more different parameters regarding the current configuration of the UE.

[0152] Aspect 21 is the apparatus of any one of Aspects 15-20, wherein the group switching message includes a MAC message that multiplexes an RRC message using one or more LCID or C-RNTI MAC control elements.

[0153] Aspect 22 is the apparatus of any one of Aspects 15-21, wherein the UE decodes an RRC message in a multiplexed RRC message that is directed to the UE.

[0154] Aspect 23 is the apparatus of any one of Aspects 15-22, wherein the UE uses a current UE-specific SRB1 and AS security profile to attempt to decode a multiplexed RRC message to determine an RRC message intended for use by the UE.

[0155] Aspect 24 is the apparatus of any one of Aspects 15-22, wherein the UE uses default SRB1 to attempt to decode multiplexed RRC messages.

[0156] Aspect 25 is the apparatus of any one of Aspects 15-25, wherein an RRC message directed to the UE from a multiplexed RRC message includes an incremental configuration based on the default UE configuration of the target base station.

[0157] Aspect 26 is the apparatus of any one of Aspects 15-25, wherein the UE receives the group handover message in a multicast message.

[0158] Aspect 27 is the apparatus of any one of Aspects 15-26, wherein at least one processor coupled to the memory is further configured to: examine the multicast message for the group switching message based on a specified or predefined time or position.

[0159] Aspect 28 is the apparatus of any one of Aspects 15-26, wherein at least one processor coupled to the memory is further configured to: receive an indication from the source base station regarding the multicast message, wherein the UE receives the group handover message in the multicast message in response to receiving the indication.

[0160] Aspect 29 is the apparatus of any one of Aspects 15-28, wherein the group handover message includes an indication to continue using the current source cell configuration with the target base station, and wherein at least one processor coupled to the memory is further configured to receive information prior to connecting to the target base station if system information including the common configuration and pre-compensation value of the target base station is not provided in the handover message.

[0161] Aspect 30 is the apparatus described in any one of aspects 15-29, and further includes a transceiver.

Claims

1. An apparatus for wireless communication for a base station, comprising: At least one memory containing instructions; as well as At least one processor is configured to execute the instructions to cause the device to: Send a group handover request for a group of user equipment (UEs) to the target base station; Confirmation of switchover from the target base station receiving group; Provide the group of UEs with a common access stratum AS key and a group-specific or default signaling radio bearer (SRB) configuration; Send new SRB information to the group of UEs, the new SRB information having integrity protection and encryption based on the public AS key and group-specific new SRB configuration; and Send a group handover message to the group of UEs.

2. The apparatus of claim 1, wherein the base station communicates with the group of UEs via a satellite, and wherein the group handover message is sent to each of the group of UEs in a synchronized Radio Resource Control (RRC) reconfiguration.

3. The apparatus of claim 1, wherein the group handover message is sent to the group of UEs based on a cell-specific public search space, and wherein at least a portion of the group handover message is scrambled with a cell-specific group radio network temporary identifier (RNTI).

4. The apparatus of claim 1, wherein the group handover message includes an RRC message, the RRC message including a list of RRC reconfiguration messages for each UE in the group of UEs, and wherein the RRC reconfiguration messages in the list of RRC reconfiguration messages indicate differences in the current configuration of the respective UE.

5. The apparatus of claim 1, wherein the group handover message includes a Medium Access Control (MAC) message, the MAC message multiplexing a Radio Resource Control (RRC) message by using one or more Logical Channel Identifier (LCID) MAC control elements or Cell Radio Network Temporary Identifier (C-RNTI) MAC control elements.

6. The apparatus of claim 5, wherein each RRC message in the multiplexed RRC messages is based on the signaling radio bearer SRB configuration and access stratum AS key of the UE in the group of UEs, and wherein the SRB configuration is specific to the UE or includes a default radio bearer configuration.

7. The apparatus of claim 5, wherein each RRC message in the multiplexed RRC messages includes an incremental configuration based on the default UE configuration for the target base station.

8. The apparatus of claim 5, wherein the size of the group of UEs is based on the amount of multiplexed RRC messages allowed in a single transport block signal TBS.

9. The apparatus of claim 1, wherein the group switching message is sent in a multicast message, and wherein the multicast message is sent at a specified or predefined time or location for the group of UEs.

10. The apparatus of claim 9, wherein the at least one processor is further configured to cause the apparatus to: Send an indication to one or more UEs in the group of UEs when to check the multicast message.

11. The apparatus of claim 9, wherein the multicast message is encrypted using a group public security key for the group of UEs.

12. The apparatus of claim 1, wherein the at least one processor is further configured to cause the apparatus to: Provide configuration information for each UE in the group of UEs. The configuration information for a UE in the group of UEs indicates a change in one or more configuration parameters for that UE relative to a common configuration for the target base station. The common configuration for the target base station includes either a default configuration for the target base station applicable to each of the group of UEs or a complete configuration for the target base station. The configuration information is provided to the group of UEs in the group handover message or in the downlink message prior to the handover decision.

13. The apparatus of claim 1, wherein the group handover message includes one or more of the following: an indication to continue using the current source cell configuration with the target base station, a new security key for communicating with the target base station, a cell radio network temporary identifier (C-RNTI) and a next-hop link counter (NCC) for the target base station, a new round-trip delay (RTD) value for the target base station, or a new timing advance (TA) for the target base station.

14. An apparatus for performing wireless communication at a user equipment (UE) served by a source base station, comprising: At least one memory containing instructions; as well as At least one processor is configured to execute the instructions to cause the device to: The source base station receives a group handover message including radio resource control (RRC) configuration for one or more UEs, the group handover message being sent to a group of UEs including the one or more UEs; The system receives a common access stratum (AS) key from the source base station and a group-specific or default signaling radio bearer (SRB) configuration common to the group of UEs; wherein the new SRB information in the group handover message includes integrity protection and encryption based on the common AS key and the group-specific new SRB configuration; and Based on the group handover message, connect to the target base station using the RRC configuration.

15. The apparatus of claim 14, wherein the source base station communicates with the group of UEs via a satellite.

16. The apparatus of claim 14, wherein the group handover message is received for the group of UEs in a synchronized Radio Resource Control (RRC) reconfiguration, wherein the UEs receive the group handover message in a cell-specific common search space, and wherein at least a portion of the group handover message is scrambled with a cell-specific group radio network temporary identifier (RNTI).

17. The apparatus of claim 16, wherein the RRC reconfiguration includes RRC messages, the RRC messages including a list of RRC reconfiguration messages for each of the group of UEs, and wherein the RRC reconfiguration messages for the UE in the list of RRC reconfiguration messages indicate one or more different parameters regarding the current configuration for the UE.

18. The apparatus of claim 14, wherein the group handover message includes a Media Access Control (MAC) message, the MAC message multiplexing a Radio Resource Control (RRC) message by using one or more Logical Channel Identifier (LCID) MAC control elements or Cell Radio Network Temporary Identifier (C-RNTI) MAC control elements.

19. The apparatus of claim 18, wherein the UE decodes an RRC message in a multiplexed RRC message that points to the UE.

20. The apparatus of claim 19, wherein the UE uses the current UE-specific signaling radio bearer 1SRB1 and access layer AS security profile to attempt to decode the multiplexed RRC message to determine the RRC message intended for use by the UE.

21. The apparatus of claim 19, wherein the UE uses the default signaling radio bearer 1SRB1 to attempt to decode the multiplexed RRC message.

22. The apparatus of claim 19, wherein the one RRC message directed to the UE from the multiplexed RRC message includes an incremental configuration based on the default UE configuration for the target base station.

23. The apparatus of claim 14, wherein the UE receives the group handover message in a multicast message.

24. The apparatus of claim 23, wherein the at least one processor is further configured to cause the apparatus to: The multicast message for the group switching message is checked based on a specified or predefined time or location.

25. The apparatus of claim 23, wherein the at least one processor is further configured to cause the apparatus to: The UE receives an indication regarding the multicast message from the source base station, wherein the UE receives the group handover message in the multicast message in response to receiving the indication.

26. The apparatus of claim 14, wherein the group handover message includes an indication to continue using the current source cell configuration with the target base station, and wherein the at least one processor is further configured to cause the apparatus to: If the handover message does not provide system information including common configuration and pre-compensation values ​​for the target base station, then the information is received before connecting to the target base station.

27. The apparatus of claim 14, further comprising a transceiver.

28. A method for wireless communication for a base station, comprising: Send a group handover request for a group of user equipment (UEs) to the target base station; Confirmation of switchover from the target base station receiving group; Provide the group of UEs with a common access stratum AS key and a group-specific or default signaling radio bearer (SRB) configuration; Send new SRB information to the group of UEs, the new SRB information having integrity protection and encryption based on the public AS key and group-specific new SRB configuration; and Send a group handover message to the group of UEs.

29. The method of claim 28, wherein the base station communicates with the group of UEs via a satellite, and wherein the group handover message is sent to each of the group of UEs in a synchronized Radio Resource Control (RRC) reconfiguration.

30. The method of claim 28, wherein the group handover message is sent to the group of UEs based on a cell-specific public search space, and wherein at least a portion of the group handover message is scrambled with a cell-specific group radio network temporary identifier (RNTI).

31. The method of claim 28, wherein the group handover message includes an RRC message, the RRC message including a list of RRC reconfiguration messages for each UE in the group of UEs, and wherein the RRC reconfiguration messages in the list of RRC reconfiguration messages indicate differences in the current configuration of the respective UE.

32. The method of claim 28, wherein the group handover message includes a Media Access Control (MAC) message, the MAC message multiplexing a Radio Resource Control (RRC) message by using one or more Logical Channel Identifier (LCID) MAC control elements or Cell Radio Network Temporary Identifier (C-RNTI) MAC control elements.

33. The method of claim 32, wherein each RRC message in the multiplexed RRC messages is based on the signaling radio bearer SRB configuration and access stratum AS key of the UE in the set of UEs, and wherein the SRB configuration is specific to the UE or includes a default radio bearer configuration.

34. The method of claim 32, wherein each RRC message in the multiplexed RRC messages includes an incremental configuration based on the default UE configuration for the target base station.

35. The method of claim 32, wherein the size of the group of UEs is based on the amount of multiplexed RRC messages allowed in a single transport block signal TBS.

36. The method of claim 28, wherein the group switching message is sent in a multicast message, and wherein the multicast message is sent at a specified or predefined time or location for the group of UEs.

37. The method of claim 36, further comprising: Send an indication to one or more UEs in the group of UEs when to check the multicast message.

38. The method of claim 36, wherein the multicast message is encrypted using a group public security key for the group of UEs.

39. The method of claim 28, further comprising: Provide configuration information for each UE in the group of UEs. The configuration information for a UE in the group of UEs indicates a change in one or more configuration parameters for that UE relative to a common configuration for the target base station. The common configuration for the target base station includes either a default configuration for the target base station applicable to each of the group of UEs or a complete configuration for the target base station. The configuration information is provided to the group of UEs in the group handover message or in the downlink message prior to the handover decision.

40. The method of claim 28, wherein the group handover message includes one or more of the following: an indication to continue using the current source cell configuration with the target base station, a new security key for communicating with the target base station, a cell radio network temporary identifier (C-RNTI) and a next-hop link counter (NCC) for the target base station, a new round-trip delay (RTD) value for the target base station, or a new timing advance (TA) for the target base station.

41. A method for conducting wireless communication at a user equipment (UE) served by a source base station, comprising: The source base station receives a group handover message including radio resource control (RRC) configuration for one or more UEs, the group handover message being sent to a group of UEs including the one or more UEs; The system receives a common access stratum (AS) key from the source base station and a group-specific or default signaling radio bearer (SRB) configuration common to the group of UEs; wherein the new SRB information in the group handover message includes integrity protection and encryption based on the common AS key and the group-specific new SRB configuration; and Based on the group handover message, connect to the target base station using the RRC configuration.

42. The method of claim 41, wherein the source base station communicates with the group of UEs via a satellite.

43. The method of claim 41, wherein the group handover message is received for the group of UEs in a synchronized Radio Resource Control (RRC) reconfiguration, wherein the UEs receive the group handover message in a cell-specific common search space, and wherein at least a portion of the group handover message is scrambled with a cell-specific group radio network temporary identifier (RNTI).

44. The method of claim 43, wherein the RRC reconfiguration includes RRC messages, the RRC messages including a list of RRC reconfiguration messages for each of the group of UEs, and wherein the RRC reconfiguration messages for the UE in the list of RRC reconfiguration messages indicate one or more different parameters regarding the current configuration for the UE.

45. The method of claim 41, wherein the group handover message includes a Media Access Control (MAC) message, the MAC message multiplexing a Radio Resource Control (RRC) message by using one or more Logical Channel Identifier (LCID) MAC control elements or Cell Radio Network Temporary Identifier (C-RNTI) MAC control elements.

46. ​​The method of claim 45, wherein the UE decodes an RRC message in a multiplexed RRC message that points to the UE.

47. The method of claim 46, wherein the UE uses the current UE-specific signaling radio bearer 1SRB1 and access layer AS security profile to attempt to decode the multiplexed RRC message to determine the RRC message intended for use by the UE.

48. The method of claim 46, wherein the UE uses Default Signaling Radio Bearer 1 SRB1 to attempt to decode the multiplexed RRC message.

49. The method of claim 46, wherein the one RRC message directed to the UE from the multiplexed RRC message includes an incremental configuration based on the default UE configuration for the target base station.

50. The method of claim 41, wherein the UE receives the group handover message in a multicast message.

51. The method of claim 50, further comprising: The multicast message for the group switching message is checked based on a specified or predefined time or location.

52. The method of claim 50, further comprising: The UE receives an indication regarding the multicast message from the source base station, wherein the UE receives the group handover message in the multicast message in response to receiving the indication.

53. The method of claim 41, wherein the group handover message includes an indication to continue using the current source cell configuration with the target base station, and the method further includes: If the handover message does not provide system information including common configuration and pre-compensation values ​​for the target base station, then the information is received before connecting to the target base station.

54. An apparatus for wireless communication at a base station, comprising: Components for performing the method according to any one of claims 28 to 40.

55. An apparatus for wireless communication at a user equipment, comprising: Components for performing the method according to any one of claims 41 to 53.

56. A computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 28 to 40.

57. A computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 41 to 53.

Images