System information for assisted access in wireless communications

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a broadcast system information (SI) message from a first cell, wherein the broadcast SI message includes SI for connecting to a second cell. The broadcast SI message may include a synchronization signal block (SSB) message, a system information block (SIB) message, a master information block (MIB) message, or any combination thereof. The UE may then transmit a random access channel (RACH) message to the first cell or the second cell based on receiving the SI included within the broadcast SI message, and perform a random access procedure with the second cell to establish a wireless connection with the second cell based on transmitting the RACH message. The UE may then communicate one or more messages with the second cell based on the random access procedure.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 487,859, filed October 16, 2023, entitled “SYSTEM INFORMATION FOR ASSISTED ACCESS IN WIRELESS COMMUNICATIONS”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following text relates to wireless communication, including system information for auxiliary access in wireless communication. Background Technology

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

[0005] With the development and deployment of future generations of Radio Access Technologies (RATs), many wireless networks will support multiple RATs during "migration periods." For example, as wireless devices gradually "migrate" to sixth-generation (6G) devices, wireless networks will support both 5G and 6G devices. However, several challenges exist when handling migration across RATs. Summary of the Invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting system information for assisted access in wireless communications. Generally, aspects of this disclosure relate to signaling for facilitating connections between wireless devices and network cells, and for facilitating network migration between / across Radio Access Technologies (RATs) (e.g., migration from fifth-generation (5G) to sixth-generation (6G) communications). Specifically, aspects of this disclosure enable a source cell (e.g., a 5G cell) to include an SI for connecting to a target cell (e.g., a 6G cell) within the system information (SI) broadcast by the source cell. By including such an SI within broadcast SI messages (e.g., Master Information Block (MIB), System Information Block (SIB), Synchronization Signal Block (SSB)), the techniques described herein reduce unnecessary signaling performed by the target cell and prevent wireless devices from requiring a full connection with the source cell to communicate with the target cell. Attached Figure Description

[0007] Figure 1 An example of a wireless communication system is shown that supports system information for auxiliary access in wireless communication according to one or more aspects of this disclosure.

[0008] Figure 2 An example of a wireless communication system is shown that supports system information for auxiliary access in wireless communication according to one or more aspects of this disclosure.

[0009] Figure 3 An example of a process flow for supporting system information for assisted access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0010] Figure 4 An example of a process flow for supporting system information for assisted access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0011] Figure 5 and Figure 6 A block diagram of a device for supporting system information for auxiliary access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0012] Figure 7 A block diagram of a communication manager that supports system information for auxiliary access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0013] Figure 8 A diagram of a system including a device for supporting system information for assisted access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0014] Figure 9 and Figure 10A block diagram of a device for supporting system information for auxiliary access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0015] Figure 11 A block diagram of a communication manager that supports system information for auxiliary access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0016] Figure 12 A diagram of a system including a device for supporting system information for assisted access in wireless communication, according to one or more aspects of this disclosure, is shown.

[0017] Figures 13 to 15 A flowchart illustrating a method for supporting system information for assisted access in wireless communication, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0018] With the development and deployment of future generations of Radio Access Technologies (RATs), many wireless networks will support multiple RATs during "migration periods." For example, as wireless devices gradually "migrate" to sixth-generation (6G) devices, wireless networks will support both fifth-generation (5G) and 6G devices. However, several challenges exist when handling migration across RATs. First, power consumption and network energy saving (NES) issues can arise when supporting multiple RATs within a network. For example, there may be situations where a 6G cell does not actually include any 6G devices. In such cases, energy used by the 6G cell to broadcast information targeting the 6G cell may be wasted. Second, previous migration technologies (such as those used for the 4G to 5G / LTE migration) may require devices to first establish connections with older "legacy" RATs so that the older RATs can facilitate connections to the newer RATs. However, requiring devices to establish connections with older RATs to communicate via the newer RATs can lead to increased control signaling overhead and network congestion.

[0019] Therefore, aspects of this disclosure relate to signaling for facilitating connectivity between wireless devices and network cells, as well as for facilitating network migration between / across RATs (e.g., migration from fifth-generation (5G) to sixth-generation (6G) communication). Specifically, aspects of this disclosure enable a source cell (e.g., a 5G cell) to include an SI for connecting to a target cell (e.g., a 6G cell) within the system information (SI) broadcast by the source cell. By including such an SI within broadcast SI messages (e.g., Master Information Block (MIB), System Information Block (SIB), Synchronization Signal Block (SSB)), the techniques described herein reduce unnecessary signaling performed by the target cell and prevent wireless devices from having to establish a full connection with the source cell to communicate with the target cell.

[0020] For example, a UE may receive broadcast SI messages (e.g., SIB, MIB, SSB) from a first cell (such as a 5G cell). The broadcast SI message may include an SI that enables communication with a second cell (such as a 6G cell). Subsequently, and using the received SI, the UE may send a Random Access Channel (RACH) message to establish a connection with the second cell. The UE may send the RACH message directly to the second cell, or it may send the RACH message to the first cell, which relays the RACH message to the second cell. In some cases, the RACH message may "wake up" the second cell, allowing the UE and the second cell to perform the RACH procedure and begin communicating with each other.

[0021] In this example, including the SI within the broadcast SI message sent by the source cell reduces or eliminates the need for the target cell (e.g., a 6G cell) to broadcast the SI, thereby reducing network power consumption at the target cell and allowing the target cell to remain in a low-power state (e.g., sleep state) until the device attempts to connect to the target cell. Furthermore, by including the SI within the broadcast SI message, the UE may not require a full connection with the source cell to receive the SI and connect to the target cell, thus reducing control signaling overhead within the network. Instead, the UE can simply monitor the broadcast SI message within resources pre-configured by the network without performing a full RACH procedure with the source cell.

[0022] The various aspects of this disclosure are first described in the context of a wireless communication system. Additional aspects of this disclosure are described in the context of an example process flow. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to system information for auxiliary access in wireless communication.

[0023] Figure 1 An example of a wireless communication system 100 supporting system information for auxiliary access in wireless communication according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0024] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0025] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

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

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

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

[0029] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0030] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

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

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

[0033] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

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

[0035] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support system information for assisted access in wireless communications as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0037] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

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

[0039] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

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

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

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

[0043] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured using multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0044] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

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

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

[0047] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

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

[0049] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0050] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

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

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

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

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

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

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

[0057] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0058] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technologies in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

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

[0061] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

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

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

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

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

[0066] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0067] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0068] The UE 115 and network entity 105 of the wireless communication system 100 can be configured to support signaling for facilitating connectivity between wireless devices and network cells, as well as for facilitating network migration (e.g., 5G to 6G migration) between RATs. Specifically, aspects of this disclosure enable a source cell (e.g., a 5G cell) to include a SI for connecting to a target cell (e.g., a 6G cell) within the SI broadcast by the source cell. By including such SI within broadcast SI messages (e.g., MIB, SIB, SSB), the techniques described herein reduce unnecessary signaling performed by the target cell and prevent wireless devices from having to establish a full connection with the source cell to communicate with the target cell.

[0069] For example, UE 115 of wireless communication system 100 may receive broadcast SI messages (e.g., SIB, MIB, SSB) from a first cell (such as a 5G cell) supported by wireless communication system 100. The broadcast SI message may include SIs capable of being used to communicate with a second cell (such as a 6G cell). Subsequently, and using the received SIs, UE 115 may send a RACH message to establish a connection with the second cell. UE 115 may send the RACH message directly to the second cell, or it may send the RACH message to the first cell, whereby the first cell relays the RACH message to the second cell. In some cases, the RACH message may "wake up" the second cell, enabling UE 115 and the second cell to perform the RACH procedure and begin communicating with each other.

[0070] In this example, including the SI within the broadcast SI message sent by the source cell reduces or eliminates the need for the target cell (e.g., a 6G cell) to broadcast the SI, thereby reducing network power consumption at the target cell and allowing the target cell to remain in a low-power state (e.g., sleep state) until the device attempts to connect to the target cell. Furthermore, by including the SI within the broadcast SI message, the UE may not require a full connection with the source cell to receive the SI and connect to the target cell, thus reducing control signaling overhead within the network. Instead, the UE can simply monitor the broadcast SI message within resources pre-configured by the network without performing a full RACH procedure with the source cell.

[0071] Figure 2 An example of a wireless communication system 200 supporting system information for auxiliary access in wireless communication, according to one or more aspects of this disclosure, is shown. Aspects of the wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may support signaling and configuration for inter-RAT access, such as signaling for facilitating inter-RAT migration.

[0072] The wireless communication system 200 may include a UE 115-a, a first serving cell 205-a (e.g., a source cell) and a second serving cell 205-b (e.g., a target cell), which may be as shown in the reference. Figure 1Examples of the described UE 115, network entity 105, and other wireless devices. In some cases, serving cell 205 may be associated with (e.g., supported by) one or more network entities 105. For example, in some cases, first serving cell 205-a and second serving cell 205-b may be associated with the same network entity 105 (e.g., supported by the same network entity). In such cases, serving cell 205 may be referred to as co-located (e.g., located in the same geographical location, and / or associated with the same hardware, circuitry, and / or RF components). As another example, in other cases, first serving cell 205-a may be associated with a first network entity 105, and second serving cell 205-b may be associated with a second network entity 105.

[0073] Serving cells 205-a and 205-b can be associated with the same or different Radio Access Technologies (RATs) (e.g., 3G, 4G, LTE, 5G, NR, 6G, etc.) and can be configured to communicate in the same or different frequency bands. For example, in some cases, such as Figure 2 As shown, the first serving cell 205-a may be associated with 5G or NR RAT, and the second serving cell 205-b may be associated with 6G RAT.

[0074] In some respects, UE 115-a may communicate with cell 205 via communication links 210-a and 210-b. In some cases, communication link 210 may include an example of an access link (e.g., a Uu link). Communication link 210 may include a bidirectional link, which may include both uplink and downlink communication. For example, UE 115-a may use communication link 210-a to send uplink transmissions, such as uplink control signals or uplink data signals, to the first serving cell 205-a, and the first serving cell 205-a may use communication link 210-a to send downlink transmissions, such as downlink control signals or downlink data signals, to UE 115-a. Similarly, the first serving cell 205-a and the second serving cell 205-b may communicate with each other via communication link 210-c, which may be an example of an Xn interface.

[0075] In this respect, the wireless communication system 200 can be configured to support multiple RATs, including current and future RATs. As future generations of RATs are developed and deployed, the wireless communication system 200 may experience a "migration period" during which it supports both older (e.g., "legacy") and newer RATs. For example, in the context of 5G and 6G communication, as wireless devices gradually "migrate" to 6G devices, the wireless communication system 200 can support both 5G and 6G devices.

[0076] Several different "migration schemes" exist that can be used for migration between / across RATs. For example, Figure 2 Static configuration 215-a and dynamic configuration 215-b, which can be implemented during the migration process of wireless communication system 200, are illustrated. Configuration 215 illustrates two different specific implementations in which different RATs (e.g., 5G and 6G) ​​can coexist within wireless communication system 200.

[0077] Static configuration 215-a exemplifies a "static reframing" configuration in which resources are statically partitioned across supported RATs in the time and / or frequency domains. Using static reframing (as illustrated via static configuration 215-a), a network provider can dedicate an entire component carrier (or other set of resources) to 6G communication, where there is no coexistence of multiple RATs within or across resources. For example, as shown in static configuration 215-a, resources within a first component carrier 220-a (CC1) (and within a given time slot 225-a) can be allocated to 5G communication, while resources within a second component carrier 220-b (CC2) can be allocated to 6G communication. Static configuration 215-a may be constant across time slot 225 or the set of time slots 225, or it may vary with time slots.

[0078] In contrast, dynamic configuration 215-b exemplifies an example of dynamic multi-RAT spectrum sharing (MRSS). Using dynamic MRSS, component carriers 220 can be dynamically shared among multiple RATs (e.g., 5G and 6G) ​​in the time, frequency, and / or spatial domains. For example, as shown in dynamic configuration 215-b, resources within component carriers 220-c can be partitioned and allocated for both 5G and 6G communications. Furthermore, resource partitioning / allocation across RATs can change over time slots. For example, component carriers 220-c can be partitioned according to a first allocation scheme during a first time slot 225-b, and according to a second allocation scheme during a second time slot 225-c.

[0079] Both static reframing (e.g., static configuration 215-a) and dynamic MRSS (e.g., dynamic configuration 215-b) implementations have advantages and disadvantages. Specifically, static reframing can help improve network power efficiency, thereby incentivizing operators to migrate to new RATs. In contrast, MRSS is expected to deliver resource utilization benefits and features power-aware design for future RATs (e.g., 6G).

[0080] In some cases, wireless communication systems (such as wireless communication system 200) may follow different migration scenarios or paths, specifically implementing a combination of static reframing (e.g., static configuration 215-a) and dynamic MRSS (e.g., dynamic configuration 215-b). For example, some wireless communication systems may utilize only static configuration 215-a. In such cases, the network (e.g., the network provider) may reframe some of its serving cells 205 to provide only 6G service. Thus, the network may consist of 5G-only cells and 6G-only cells.

[0081] In other cases, the network may include 5G-only cells and 5G / 6G MRSS cells. In other words, the network can implement a combination of static configuration 215-a and dynamic configuration 215-b to include some serving cells 205 supporting 5G-only communication, and some cells supporting both 5G and 6G communication (e.g., MRSS cells). In other words, some serving cells 205 of the cell site can remain in 5G operation, while others will dynamically share with the 6G RAT. In practice, MRSS is unlikely to be enabled simultaneously everywhere within the network. Therefore, because the process is gradual, using both static configuration 215-a and dynamic configuration 215-b for the migration process allows some serving cells 205 within the network to remain 5G cells for a longer duration.

[0082] Similarly, in other cases, the network may include 6G-only cells and 5G / 6G MRSS cells. In other words, the network can implement a combination of static configuration 215-a and dynamic configuration 215-b to include some serving cells 205 supporting 6G-only communication, and some cells supporting both 5G and 6G communication (e.g., MRSS cells). In other words, in this specific implementation, some serving cells 205 can be reframed for 6G-only service, while other serving cells 205 will be dynamically shared between 5G and 6G RATs. As more devices within the network become 6G-capable, some MRSS serving cells 205 can be phased out of 5G and converted to 6G-only cells (e.g., gradually shutting down 5G communication / cells as more devices become 6G-capable).

[0083] Finally, in other specific implementations, the network may include all 5G / 6G MRSS serving cells 205. That is, the network may designate all serving cells 205 in the network as dynamic MRCC cells supporting both 5G and 6G communications. Over time, more and more serving cells 205 may support MRSS, assuming that both 5G and 6G have considerable market penetration.

[0084] When considering which of the above migration schemes / implementations to use within the network, several aspects or parameters need to be considered, including the number of radio devices (e.g., UE 115) within the network capable of communicating within the corresponding RAT. Other parameters considered in determining which migration scheme to implement include co-location, frequency ranges of different RATs, and network architecture. Co-location refers to whether different serving cells 205 / network entities 105 are located in the same location (e.g., they are co-located). If two serving cells 205 are co-located, it can be assumed that communication between UE 115-a and the co-located serving cell 205 experiences (substantially) the same channel conditions, path loss (PL), timing advance (TA) values, etc. In other words, for co-located serving cells 205, the difference in TA values ​​and PL across the two cells can be assumed to be negligible. Furthermore, co-location between serving cells 205 can be a factor in determining whether two serving cells 205 are coordinated, which is a key assumption of MRSS. As will be described in further detail in this article, coaddressing is also important in the context of static reframing (e.g., static configuration 215-a).

[0085] The frequency range between serving cell 205 and RAT is another factor in determining which migration scheme to use. Frequency gap refers to the distance (in the frequency domain) between the operating frequency ranges of the two serving cells 205. The frequency gap between the two serving cells 205 is important for the auxiliary operating modes in which the serving cells 205 will "cooperate" with each other, as will be described in further detail herein.

[0086] Finally, network architecture is another factor in determining which migration scheme to use. The term "network architecture" can be used to refer to the circuitry and RF architecture of the corresponding serving cell 205. Specifically, network architecture determines whether serving cell 205 shares the same antenna elements and / or RF chain, which can lead to different migration solutions and power consumption conclusions.

[0087] As previously noted, several challenges exist when handling migrations across RATs. First, power consumption and network energy saving (NES) issues can arise when supporting multiple RATs within a network. NES is a crucial aspect of 6G network design. One process of energy consumption within the network arises from broadcast signals sent by cell / network entity 105 for network access. For example, in a 5G network, cell 205 / network entity 105 may send / broadcast bursts of SSB and SIB to radio devices within the network, where cell 205 / network entity 105 subsequently monitors responsive uplink transmissions from radio devices attempting to access the network (e.g., monitoring approximately 4 ms every 20 milliseconds). The total duration of the SSB / SIB burst can depend on communication parameters used by the respective cell 205 / network entity 105, such as the number of beams, the Remaining Minimum SI (RMSI) multiplexing mode, and the RACH Timing (RO) configuration.

[0088] In some cases, each corresponding serving cell 205 (and / or each corresponding RAT) may broadcast its own SI to allow wireless devices to connect to the corresponding cell 205 / RAT. However, this may result in increased power consumption and / or wasted resources. For example, there may be situations where a 6G cell (e.g., the second serving cell 205-b) does not actually include wireless devices capable of 6G communication. In such cases, the energy used by the 6G cell (e.g., the second serving cell 205-b) to broadcast the SI for the 6G cell may be wasted.

[0089] Therefore, aspects of this disclosure relate to techniques utilizing signaling used by 5G cells to facilitate connections between 6G cells and wireless devices. This assistance provided by the 5G cell can lead to a reduction in the transmission of 6G broadcast communications (e.g., broadcast SI), thereby reducing network energy consumption. In other words, aspects of this disclosure relate to signaling performed by a first serving cell 205-a (e.g., a 5G cell) to facilitate a connection between a second serving cell 205-b (e.g., a 6G cell) and UE 115-a.

[0090] While much of this disclosure is described in the context of signaling used to facilitate communication between serving cells 205 associated with different RATs (e.g., inter-RAT situations), this should not be considered a limitation of the disclosure unless otherwise indicated herein. Specifically, aspects of this disclosure can be used in the context of intra-RAT situations, such as between two 5G serving cells 205, between two 6G serving cells 205, etc. For example, in some cases, Figure 2The serving cells 205-a and 205-b illustrated herein may both be 5G cells. In such cases, aspects of this disclosure may be implemented to facilitate a connection between the second serving cell 205-b (e.g., the second 5G cell) and the UE 115-a using signaling from the first serving cell 205-a (e.g., the first 5G cell).

[0091] Another issue associated with some previous migration technologies, such as those used for the 4G to 5G / LTE migration, may require devices to first establish a connection with an older, "legacy" RAT so that the older RAT can facilitate connectivity to the newer RAT. However, requiring devices to establish a connection with an older RAT in order to communicate via the newer RAT can lead to increased control signaling overhead and network congestion.

[0092] For example, in the context of some previous migration technologies, UE 115-a might be required to connect to a first serving cell 205-a (e.g., a 5G cell) (e.g., to perform a RACH procedure and establish an RRC connection), where a second serving cell 205-b (e.g., a 6G cell) is subsequently woken up by UE 115-a and aggregated as a secondary cell (SCell) or secondary cell group (SCG). However, if UE 115-a is a 6G-capable device, the control signaling used to establish a connection with the 5G cell may be unnecessary and lead to increased network congestion (and delayed connections between UE 115-a and the 6G cell).

[0093] As another example, under some prior migration techniques, UE 115-a might be required to connect to a first serving cell 205-a (e.g., a 5G cell) (e.g., to perform a RACH procedure and establish an RRC connection), whereby the first serving cell 205-a (e.g., the 5G cell) then wakes up a second serving cell 205-b (e.g., a 6G cell) and directs UE 115-a to move to the second serving cell 205-b via a handover procedure. As noted elsewhere, requiring UE 115-a to establish a connection with the 5G cell may be unnecessary and leads to increased network congestion. Furthermore, the handover procedure may take a long time to complete, further delaying communication between UE 115-a and the second serving cell 205-b.

[0094] Therefore, in order to address some of the problems associated with existing migration technologies, aspects of this disclosure relate to signaling and techniques that enable UE115-a to establish a connection with a second serving cell 205-b (e.g., a 6G cell) using signaling from a first serving cell 205-a (e.g., a 5G cell) without fully establishing a connection with the first serving cell 205-a.

[0095] In other words, aspects of this disclosure enable UE 115-a to establish a connection with a 6G cell using signaling from a 5G cell, without performing a RACH procedure or establishing an RRC connection with the 5G cell. In this respect, aspects of this disclosure facilitate a connection with a second serving cell 205-b using signaling from a first serving cell 205-a, without utilizing a handover procedure and / or considering mRAT carrier aggregation or 5G-6G dual connectivity with a 5G primary cell group (MCG). That is, the purpose of this disclosure is to enable a 6G-capable UE 115 to access a 6G cell without connecting to a 5G cell, while still receiving assistance from the 5G cell.

[0096] In some aspects, signaling from the first serving cell 205-a can be used to facilitate a connection between UE 115-a and the second serving cell 205-b using both one-step SI acquisition methods and two-step SI acquisition methods. At a higher level, according to the one-step SI acquisition method, the broadcast SI message 230-a received from the first serving cell 205-a may include all SIs required for UE 115-a to perform a RACH procedure and establish a connection with the second serving cell 205-b. In contrast, according to the two-step SI acquisition method, the broadcast SI message 230-a received from the first serving cell 205-a may include some SIs required for UE 115-a to send a RACH message and / or a wake-up signal (WUS) to wake up the second serving cell 205-b, wherein the additional broadcast SI message 230-b received from the second serving cell 205-b includes the remaining SIs required for UE 115-a to perform a RACH procedure and establish a connection with the second serving cell 205-b.

[0097] This article will refer to Figure 2 This will further describe each of the one-step SI acquisition method and the two-step SI acquisition method in detail. Additionally, refer to... Figure 3 The one-step SI acquisition method is further shown and described, and references are provided. Figure 4 The two-step SI acquisition method is further illustrated and described.

[0098] According to the one-step SI acquisition method, UE 115-a (e.g., UE 115-a with 6G capability) can access a second serving cell 205-b (e.g., a 6G cell) via a first serving cell 205-a (e.g., a 5G cell). For this purpose, the first serving cell 205-a can send / broadcast 6G-related information via broadcast communication. For example, the first serving cell 205-a can send (e.g., broadcast) SI message 230-a. Broadcast SI message 230-a may include MIB, SIB (e.g., SIB1), SSB, or any combination thereof. The first serving cell 205-a can use 5G signaling (e.g., using 5G communication protocols within 5G resources) to send broadcast SI message 230-a.

[0099] In such cases, the broadcast SI message 230-a (e.g., a 5G SIB) may be extended or modified (e.g., a new SIB format) to carry additional 6G-related information. In other words, the 5G broadcast SI message 230-a may include one or more bit fields for conveying 6G-related SIs that can be used by UE 115-a to access the second serving cell 205-b. In some aspects, a UE 115 capable only of 5G communication may be configured to ignore bit fields associated with the 6G-related SI. Furthermore, in cases where a new SIB format is used to convey the broadcast SI message 230-a of the 6G-related SI, a 5G-capable UE 115 (e.g., a UE 115 incapable of 6G communication) may ignore or otherwise avoid reading the new SIB format (e.g., avoid decoding or processing the SIB format with the 6G-related SI).

[0100] In some respects, spare and / or additional reserved bits in the MIB and Physical Broadcast Channel (PBCH) of the 5G SSB (e.g., broadcast SI message 230-a) can indicate whether 6G service is being provided. That is, unused or new bits within broadcast SI message 230-a can indicate whether an accessible 6G cell exists within the network or surrounding geographic area. Therefore, previously unused or new bit fields within broadcast SI message 230-a can indicate whether broadcast SI message 230-a includes an SI for accessing such a 6G cell.

[0101] In some respects, bit fields within the broadcast SI message 230-a can be used to indicate whether 6G service is being provided, such as via bit fields within the extended SIB. In such cases, UE 115-a may be able to determine (in advance) whether 6G service is even being provided, allowing it to make an informed decision about whether to attempt to connect to a 6G cell. If this information is included within the extended SIB, UE 115-a may be required to decode the SIB, which could result in higher UE power consumption.

[0102] Additionally or alternatively, the bit fields within the broadcast SI message 230-a can be used to indicate whether a 6G cell (e.g., the second serving cell 205-b) is associated with a 5G cell (e.g., the first serving cell 205-a) via MRSS, or whether the 5G cell is assisting access to a reframed 6G cell. In other words, the bit fields within the broadcast SI message 230-a can indicate whether the resources associated with the second serving cell 205-b (e.g., the 6G cell) are allocated according to static configuration 215-a (e.g., static reframe) or dynamic configuration 215-b (e.g., MRSS). For example, the first serving cell 205-a can set the spare bit in the broadcast SI message 230-a to "0" to indicate that the 5G cell (e.g., the first serving cell 205-a) is not associated with any 6G cell or 6G service. Conversely, the first serving cell 205-a may set the spare bit to "1" and may set one or more additional bits to "0" to indicate that the 5G cell (e.g., the first serving cell 205-a) is associated with the 6G cell (e.g., the second serving cell 205-b) MRSS. Similarly, the first serving cell 205-a may set the spare bit to "1" and may set one or more additional bits to "1" to indicate that the 5G cell (e.g., the first serving cell 205-a) is associated with the reframed 6G cell (e.g., the second serving cell 205-b), wherein the SI for the 6G cell is indicated on the (extended) 5G SIB (e.g., broadcast SI message 230-a).

[0103] In some cases, the first serving cell 205-a can be configured to send / broadcast an SI message 230-a, including an SI for accessing the second serving cell 205-b, on predefined or pre-configured resources. In other words, the resources used by the first serving cell 205-a can be pre-configured and / or hard-coded into the UE 115-a, enabling the UE 115-a to monitor and receive the broadcast SI message 230-a from the first serving cell 205-a without ever establishing a connection with it. That is, the UE 115-a can receive the broadcast SI message 230-a via 5G signaling without actually performing a RACH procedure (or establishing an RRC connection) with the first serving cell 205-a (e.g., a 5G cell).

[0104] Broadcast SI message 230-a may include SIs associated with the second serving cell 205-b (e.g., 6G-related SIs). The SIs included in broadcast SI message 230-a can be used by UE 115-a to access the second serving cell 205-b. SIs may include RACH configuration information (e.g., RACH sequence, RACH timing (RO), resources for ROs in the time / frequency domain, Random Access Response (RAR) search space configuration, etc.), resources for communicating with the second serving cell 205-b (e.g., uplink bandwidth portion (BWP) and / or downlink BWP for communicating with the second serving cell 205-b), control resource set (CORESET) associated with the second serving cell 205-b, etc. In this respect, according to the one-step SI acquisition method, broadcast SI message 230-a received from the first serving cell 205-a may include all SIs required by UE 115-a to perform the RACH procedure and access the second serving cell 205-b.

[0105] Therefore, according to the one-step SI acquisition method, UE 115-a can perform a RACH procedure with a second serving cell 205-b (e.g., a 6G cell) based on (e.g., according to) the SI received via the first serving cell 205-a. That is, after obtaining the SI (e.g., RO, initial DL / UL BWP, etc.) from the first serving cell 205-a, UE 115-a can be configured to initiate and continue the initial access procedure with the second serving cell 205-b (e.g., performing a RACH procedure and an RRC connection procedure on a 6G carrier / frequency). Specifically, UE 115-a can use the SI received from the first serving cell 205-a (via broadcast SI message 230-a) to exchange RACH messages 235-a and 235-b (e.g., physical RACH (PRACH) messages) with the second serving cell 205-b as part of the RACH procedure. In some cases, UE 115-a may send RACH message 235-a, which includes WUS for the second serving cell 205-b to transition from a sleep state to an active state in order to perform the RACH procedure.

[0106] In some cases, such as when serving cell 205 is co-located, UE 115-a may use spatial information, TA value, path loss information, and other information determined based on measurements performed on SSB 240-a received from the first serving cell 205-a to communicate with the second serving cell 205-b. That is, when the cells are co-located, UE 115-a may assume that the measurements / determinations performed on SSB 240-a received from the first serving cell 205-a also apply to the second serving cell 205-b.

[0107] In the context of the one-step SI acquisition method, because the broadcast SI message 230-a from the first serving cell 205-a includes all the SIs required for accessing the second serving cell 205-b, it may not be required or expected that the second serving cell 205-b (e.g., a 6G cell) will periodically transmit SSB, SIB, and / or other broadcast SI messages 230. Therefore, the one-step SI acquisition method allows the second serving cell 205-b to reduce (or eliminate) the energy consumption for sending / broadcasting SI messages 230-b, thereby reducing energy consumption within the network. Furthermore, enabling the second serving cell 205-b to avoid broadcasting SI messages 230-b allows the second serving cell 205-b to remain in a dormant state for a longer period, further reducing energy consumption at the second serving cell 205-b.

[0108] As described herein, in the context of the one-step SI acquisition method, a new and / or extended SIB format can be used to broadcast SI message 230-a to convey the SI associated with the second serving cell 205-b. Using an extended SIB format (and / or a new SIB format with additional bit fields) can result in higher signaling overhead for the periodic transmission of SI message 230-a on the 5G cell. While this leads to reduced power consumption at the second serving cell 205-b (because it reduces / eliminates the need for the second serving cell 205-b to broadcast SI message 230-b), it can potentially result in lower resource utilization and higher network power consumption on the 5G cell.

[0109] Therefore, according to the two-step SI acquisition method, signaling from both the first serving cell 205-a (e.g., a 5G cell) and the second serving cell 205-b (e.g., a 6G cell) can be used to convey SIs for accessing the second serving cell 205-b. That is, instead of conveying all SIs required for accessing the second serving cell 205-b from the first serving cell 205-a, the SIs can be divided across broadcast SI messages 230 received from both serving cells 205. By using broadcast SI messages 230-b from the second serving cell 205-b to convey some SIs for accessing the second serving cell 205-b, the two-step SI acquisition method can be used to reduce power consumption at the 5G cell.

[0110] For example, according to the two-step SI acquisition method, UE 115-a can receive a broadcast SI message 230-a from the first serving cell 205-a, as previously described herein. Compared to the one-step SI acquisition method, where the broadcast SI message 230-a includes all SIs required by UE 115-a to access the second serving cell 205-b, the two-step SI acquisition method allows the broadcast SI message 230-a to include only a subset of SIs that enable UE 115-a to initiate a RACH procedure with the second serving cell 205-b and / or wake up the second serving cell. That is, according to the two-step SI acquisition method, the 5G cell can "outsource" the transmission of most 6G-related SIs to the 6G cell itself. Therefore, according to the two-step SI acquisition method, the SIs required to access the second serving cell 205-b can be divided across the signaling received from the two serving cells 205-a and 205-b.

[0111] For example, in the context of a two-step SI acquisition method, a 5G SIB (e.g., broadcast SI message 230-a) may include bit fields indicating the initial downlink BWP, initial CORESET (CORESET0), and / or search space (e.g., search space 0) for the second serving cell 205-b. In this example, in order to retrieve the remaining SIs to be used for accessing the second serving cell 205-b, UE 115-a (and / or the first serving cell 205-a) may have to wake up the second serving cell 205-b so that the second serving cell 205-b can send / broadcast an SIB (e.g., broadcast SI message 230-b) including the remaining SIs to be used for accessing the second serving cell 205-b. In this regard, UE 115-a may use the SI received in the broadcast SI message 230-a from the first serving cell 205-a to send RACH message 235-a directly to the second serving cell 205-b, and / or send RACH message 235-c (as RACH message 235-d) that will be relayed from the first serving cell 205-a to the second serving cell 205-b.

[0112] For example, in some cases, if an incoming 6G UE 115-a requests complete information (SI) of the 6G cell, it can use the SI received via broadcast SI message 230-b to directly send a RACH message 235-a (e.g., PRACH) to the 6G cell to wake it up. In such cases, the 6G cell (e.g., the second serving cell 205-b) may be expected to periodically "wake up" (e.g., transition from a sleep or inactive state to an active state) to monitor the 6GRACH timing for receiving the RACH message 235-a. The RACH message 235-a may include WUS, or may otherwise request the second serving cell 205-b to wake up. Subsequently, after receiving RACH message 235-a / WUS (and transitioning to an active state), the 6G cell can begin broadcasting its own SIB (e.g., broadcasting SI message 230-b), where the SIB may include the remainder of the SI used for accessing the second serving cell 205-b and not included in the 5G SIB from the 5G cell (e.g., broadcasting SI message 230-a). In this example, UE 115-a can use the additional SI within the broadcast SI message 230-b received from the second serving cell 205-b to perform the RACH procedure and establish a connection with the second serving cell 205-b.

[0113] In additional or alternative scenarios, UE 115-a may send RACH message 235-c and / or WUS to the first serving cell 205-a instead of directly sending RACH message 235-a and / or WUS to the second serving cell 205-b, wherein the first serving cell 205-a is configured to forward or relay information / messages to the second serving cell 205-b. For example, as previously described herein, UE 115-a may receive a broadcast SI message 230-a from the first serving cell 205-a (without establishing a connection with the first serving cell 205-a), wherein the broadcast SI message 230-a includes some SIs for accessing the second serving cell 205-b. UE 115-a may use the SIs included in the broadcast SI message 230-a to send RACH message 235-c (and / or WUS) to the first serving cell 205-a to notify / inform the first serving cell 205-a that UE 115-a wants to access the second serving cell 205-b. In this example, the first serving cell 205-a may forward or relay RACH message 235-d and / or WUS to the second serving cell 205-b to "wake up" the second serving cell 205-b. Subsequently, after receiving RACH message 235-b / WUS from the first serving cell 205-a (and transitioning to an active state), the 6G cell may begin broadcasting its own SIB (e.g., broadcast SI message 230-b), where the SIB may include the remainder of the SI that will be used to access the second serving cell 205-b and is not included in the 5G SIB from the 5G cell (e.g., broadcast SI message 230-a). In this example, UE 115-a may use the additional SI within the broadcast SI message 230-b received from the second serving cell 205-b to perform the RACH procedure and establish a connection with the second serving cell 205-b.

[0114] In both alternative scenarios (e.g., UE 115-a directly sends RACH message 235-a to the second serving cell 205-b, or sends the RACH message to the first serving cell 205-a to relay to the second serving cell 205-b), the first serving cell 205-a consumes less energy compared to the one-step SI acquisition method. Specifically, compared to the broadcast SI message 230-a sent by the first serving cell 205-a according to the one-step SI acquisition method, the broadcast SI message 230-a sent by the first serving cell 205-a according to the two-step SI acquisition method may include fewer SIs (and therefore fewer data / bit fields), thereby reducing the power consumption associated with the first serving cell 205-a. Furthermore, the two-step SI acquisition method can still reduce the power consumption at the second serving cell 205-b, because the second serving cell 205-b can still remain in a sleep state (e.g., idle, inactive, or other low-power state) until it receives WUS from UE 115-a and / or the first serving cell 205-a.

[0115] In some respects, the information within the broadcast SI message 230-a sent by the first serving cell 205-a may be interpreted differently depending on whether the information is to be applied to communication with the first serving cell 205-a (e.g., 5G communication) or with the second serving cell 205-b (e.g., 6G communication). In other words, a 5G-capable UE 115 that will use SI to communicate with the first serving cell 205-a for 5G will interpret the bit fields differently than a 6G-capable UE 115 that will use SI to communicate with the second serving cell 205-b for 6G. When a 6G-capable UE 115 knows that a 5G cell (e.g., the first serving cell 205-a) is associated with a 6G cell (e.g., the second serving cell 205-b), it may be useful to use separate interpretations for the same bit fields within the broadcast SI message 230, regardless of whether the 5G cell is associated with a 6G cell MRSS or with a reframed 6G cell.

[0116] For example, broadcast SI message 230-a may include one or more bit fields associated with a PDCCH or SIB configuration (e.g., pdcch-ConfigSIB1). In this example, 5G UE 115 may interpret the bit fields of pdcch-ConfigSIB1 according to a first interpretation used for 5G communication with the first serving cell 205-a. In contrast, 6G UE 115 may interpret the bit fields of pdcch-ConfigSIB1 according to a second interpretation used for 6G communication with the second serving cell 205-b. Utilizing this new interpretation of the bit fields of pdcch-ConfigSIB1 for the 6G cell, it may not be expected that a 6G-capable UE 115 will detect and decode the 5GSIB1 message to obtain the information required to acquire the 6G SIB. Instead, a 6G-capable UE 115 can directly detect and decode the 6G SIB. In this respect, allowing different interpretations of the same bit fields within the broadcast SI message 230-a, compared to some previous methods, can result in lower latency and lower power consumption for UE 115 with 6G capability, and can also result in lower 5G network overhead and power consumption.

[0117] Both the one-step SI acquisition method and the two-step SI acquisition method are well-suited for migration scenarios with the following conditions: (1) 5G and 6G cells are co-located, (2) the frequency gap between 5G and 6G cells is relatively small, and (3) RF and antenna components are shared between 5G and 6G cells. When 5G and 6G cells are co-located, serving cell 205 can coordinate with each other and thus cooperate with each other (e.g., communicate) with negligible timing inaccuracies. Furthermore, when serving cell 205 is co-located, UE 115-a can rely on timing information obtained / determined based on communication with the 5G cell when initiating access to the 6G cell. Additionally, when the frequency gap between cells is relatively small (e.g., less than a threshold), UE 115-a can rely on measurements performed on signals received from the first serving cell 205-a when initiating access to the second serving cell 205-b. The frequency gap condition can be satisfied in the case of MRSS between the first serving cell 205-a (e.g., a 5G cell) and the second serving cell 205-b (e.g., a 6G cell). Finally, if RF and antenna components are shared between serving cells 205, UE 115-a can rely on the spatial information it obtains / determines from the first serving cell 205-a when initiating access to the second serving cell 205-b.

[0118] When serving cell 205 is co-located, it can be referred to as "coordinated" because the schedulers at serving cell 205 communicate with each other, and the differences in TA values ​​and path losses from the two serving cells 205 implemented by UE 115-a are negligible. However, the assumptions / conditions described above may not hold if the first serving cell 205-a and the second serving cell 205-b are not co-located (e.g., not supported by the same network entity 105). In such cases, the second serving cell 205-b (e.g., a 6G cell) can be configured to send / broadcast SSB 240-b upon its wake-up.

[0119] For example, in some cases, the first serving cell 205-a and the second serving cell 205-b may not be co-located. When serving cell 205 is not co-located, UE 115-a may not be able to directly send RACH message 235-a (e.g., PRACH) to the second serving cell 205-b. Therefore, in the context of both a one-step SI acquisition method and / or a two-step SI acquisition method, the second serving cell 205-b may receive RACH message 235-d and / or WUS relayed / forwarded by the first serving cell 205-a and can be "wake up" by transitioning to an active state. In this example, and when serving cells 205-a and 205-b are not co-located, the second serving cell 205-b may send / broadcast its own SSB 240-b after being woken up. In this regard, because UE 115-a cannot rely on the spatial information, TA value, and path loss associated with the first serving cell 205-a (since the cells are not co-located), UE 115-a can utilize SSB 240-b received from the second serving cell 205-b to determine the individual spatial information, TA value, path loss, and other information associated with the second serving cell 205-b. Subsequently, UE 115-a can perform a RACH procedure with the second serving cell 205-b (as described previously herein) based on the information determined / obtained from SSB 240-b.

[0120] In this regard, in some cases, such as when the cells are co-located, UE 115-a may rely on measurements of the first serving cell 205-a (e.g., a 5G cell) to access the second serving cell 205-b (e.g., a 6G cell). In other cases, such as when the cells are not co-located (e.g., co-location conditions are not met), measurements performed on signals from the first serving cell 205-a (e.g., SSB 240-a) may not be useful for accessing the second serving cell 205-b. Therefore, in some cases, a 5G cell (e.g., the first serving cell 205-a) may be associated with a set of 6G cells (e.g., the set of serving cells 205 including the second serving cell 205-b), rather than with only one 6G cell.

[0121] In some cases, a 5G cell (e.g., the first serving cell 205-a) can be configured to "wake up" more than one 6G cell, such that the notified 6G cell can begin transmitting SSB 240-b to enable UE 115-a to access the corresponding 6G cell. In this example, the woken-up 6G cells may include all 6G cells associated with the 5G cell, or only a subset of the 6G cells associated with the 5G cell. The 5G cell may also indicate to UE 115-a information associated with the SSB 240-b of the 6G cell (e.g., time / frequency resources for SSB 240-b) to enable UE 115-a to perform measurements on the SSB 240-b received from the 6G cell. In such cases, UE 115-a may have various options (among the 6G cells) to access the 6G network and may perform cell selection across the indicated 6G cells. Once a 6G cell is selected, other 6G cells that are woken up can fall back to or otherwise return to a sleep state (e.g., idle state, inactive state, other low-power state).

[0122] When UE 115-a accesses a second serving cell 205-b using SSB 240-a from a first serving cell 205-a (e.g., a 5G cell) (in either the one-step SI acquisition method or the two-step SI acquisition method), UE 115-a may determine the cell ID of the second serving cell 205-b (e.g., a 6G cell) according to various specific implementations. According to a first implementation, the cell ID of the second serving cell 205-b (e.g., a 6G cell) may be the same as (equal to) the cell ID of the first serving cell 205-a (e.g., a 5G cell). However, this implementation may restrict network operation to always selecting the same ID for the 5G cell and the 6G cell. According to a second implementation, the second serving cell 205-b (e.g., a 6G cell) may transmit its own SSB 240-b to UE 115-b after wake-up, wherein SSB 240-b indicates the cell ID of the second serving cell 205-b. However, as discussed earlier herein, requiring the second serving cell 205-b to send SSB 240-b after wake-up may increase network power consumption at the second serving cell 205-b. According to a third embodiment, the first serving cell 205-a (e.g., a 5G cell) may be configured to indicate to UE 115-a the cell ID associated with the second serving cell 205-b (e.g., a 6G cell) via broadcast SI message 230-a (e.g., via extended 5G SIB). In such cases, it may not be required or expected that the second serving cell 205-b (e.g., a 6G cell) broadcast its own SSB 240-b to UE 115-a, resulting in reduced power consumption and more flexible network operation.

[0123] Figure 3 An example of a process flow 300 supporting system information for auxiliary access in wireless communications, according to one or more aspects of this disclosure, is shown. Aspects of process flow 300 may implement aspects of wireless communication system 100, wireless communication system 200, or both, or be implemented by them. For example, process flow 300 exemplifies signaling and configuration that enables UE 115-b to access another serving cell using signaling from a first serving cell without ever being fully connected to the first serving cell, as described previously herein. Specifically, Figure 3 The signaling shown illustrates an example of the one-step SI acquisition method described in this paper.

[0124] Process flow 300 includes UE 115-b, first serving cell 305-a, and second serving cell 305-b, which can be examples of UE 115, network entity 105, serving cell 205, and other radio devices as described herein. For example, Figure 3The UE 115-b, the first serving cell 305-a, and the second serving cell 305-b illustrated herein may respectively include, as follows: Figure 2 Examples of UE115-a, first serving cell 205-a, and second serving cell 205-b are illustrated. In this regard, first serving cell 305-a and second serving cell 305-b may be associated with the same or different network entities 105 (e.g., supported by these same or different network entities) and may be configured to communicate using the same or different frequency bands / RATs. For example, in some cases, first serving cell 305-a may include a 5G cell, and second serving cell 305-b may include a 6G cell.

[0125] In some examples, the operations illustrated in process flow 300 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0126] At 310, UE 115-b may receive one or more broadcast SI messages from the first serving cell 305-a. Broadcast SI messages may include MIBs, SIBs (e.g., SIB1), SSBs, or any combination thereof. For example, in some cases, UE 115-b may perform measurements on SSBs received from the first serving cell 305-a. As previously described herein, in the case of co-location of serving cells 305-a and 305-b, UE 115-b may be able to access the second serving cell 305-b using measurements and assumptions (e.g., path loss, spatial information, TA value) based on SSBs received from the first serving cell 305-a. The first serving cell 205-a may use 5G signaling (e.g., using 5G communication protocols within 5G resources) to send broadcast SI messages 230-a.

[0127] In some aspects, the broadcast SI message at 310 (e.g., a 5G SIB) may be extended or modified (e.g., a new SIB format) to carry additional 6G-related information. In other words, the 5G broadcast SI message may include one or more bit fields for conveying a 6G-related SI that can be used by UE 115-a to access the second serving cell 305-b. In some aspects, a UE 115 capable only of 5G communication may be configured to ignore bit fields associated with the 6G-related SI. Furthermore, in cases where a new SIB format is used to convey broadcast SI messages of the 6G-related SI, a 5G-capable UE 115 (e.g., a UE 115 incapable of 6G communication) may ignore or otherwise avoid reading the new SIB format (e.g., avoid decoding or processing the SIB format with the 6G-related SI).

[0128] In some cases, the first serving cell 305-a can be configured at 310 to send / broadcast SI messages, including SIs for accessing the second serving cell 305-b, on predefined or pre-configured resources. In other words, the resources used by the first serving cell 305-a can be pre-configured and / or hard-coded into the UE 115-b, enabling the UE 115-b to monitor and receive broadcast SI messages from the first serving cell 305-a without ever establishing a connection with it. That is, the UE 115-b can receive broadcast SI messages via 5G signaling without actually performing a RACH procedure (or establishing an RRC connection) with the first serving cell 305-a (e.g., a 5G cell).

[0129] The broadcast SI message at 310 may include SIs associated with the second serving cell 305-b (e.g., 6G-related SIs). The SIs included in the broadcast SI message 230-a can be used by UE 115-b to access the second serving cell 305-b. The SIs may include RACH configuration information (e.g., RACH sequence, RACH timing (RO), resources for ROs in the time / frequency domain, Random Access Response (RAR) search space configuration, etc.), resources for communicating with the second serving cell 305-b (e.g., uplink bandwidth portion (BWP) and / or downlink BWP for communicating with the second serving cell 305-b), control resource sets (CORESET) associated with the second serving cell 305-b, etc. In this respect, according to the one-step SI acquisition method, the broadcast SI message received from the first serving cell 305-a may include all SIs required by UE 115-b to perform the RACH procedure and access the second serving cell 305-b.

[0130] At 315, UE 115-b and the second serving cell 305-b can perform a RACH procedure (and / or an RRC connection procedure) to establish a connection between UE 115-b and the second serving cell 305-b. UE 115-b can perform the RACH procedure with the second serving cell 305-b (e.g., a 6G cell) based on (e.g., according to) the SI received at 310 via the first serving cell 305-a. That is, after obtaining the SI (e.g., RO, initial DL / UL BWP, etc.) from the first serving cell 305-a, UE 115-b can be configured to initiate and continue the initial access procedure with the second serving cell 305-b (e.g., performing the RACH procedure and the RRC connection procedure on the 6G carrier / frequency). That is, as part of the RACH process, UE 115-b can use the SI received from the first serving cell 305-a (via the broadcast SI message at 310) to exchange RACH messages (e.g., PRACH messages) with the second serving cell 305-b.

[0131] In some cases, UE 115-b may send a RACH message 235-a, which includes a WUS for the second serving cell 305-b to transition from a sleep state to an active state in order to perform the RACH procedure. In this respect, the second serving cell 305-b may be configured to transition from a sleep state (e.g., idle state, inactive state, low power state) to an active state when it receives a RACH message and / or WUS from UE 115-b at 315.

[0132] In some cases, such as when serving cell 305 is co-located, UE 115-b may use spatial information, TA value, path loss information, and other information determined based on measurements performed on SSBs received from the first serving cell 305-a to communicate with the second serving cell 305-b. That is, when the cells are co-located, UE 115-b may assume that the measurements / determinations performed on SSBs received from the first serving cell 305-a also apply to the second serving cell 305-b.

[0133] In the context of the one-step SI acquisition method, because the broadcast SI message from the first serving cell 305-a includes all the SIs required for accessing the second serving cell 305-b, it may not be required or expected that the second serving cell 305-b (e.g., a 6G cell) will periodically transmit SSB, SIB, and / or other SI messages. Therefore, the one-step SI acquisition method allows the second serving cell 305-b to reduce (or eliminate) the energy consumption for sending / broadcasting SI messages, thereby reducing energy consumption within the network. Furthermore, enabling the second serving cell 305-b to avoid broadcasting SI messages allows it to remain in a dormant state for extended periods, further reducing energy consumption at the second serving cell 305-b.

[0134] At 320, UE 115-b and the second serving cell 305-b can communicate one or more messages to each other. UE 115-b and the second serving cell 305-b can communicate messages to each other at 320 based on receiving a broadcast SI message at 310, performing a RACH procedure at 315, or both.

[0135] Figure 4 An example of a process flow 400 supporting system information for auxiliary access in wireless communications, according to one or more aspects of this disclosure, is shown. Aspects of process flow 400 may implement aspects of wireless communication system 100, wireless communication system 200, process flow 300, or any combination thereof, or be implemented by these aspects. For example, process flow 400 exemplifies signaling and configuration that enables UE 115-c to access another serving cell using signaling from a first serving cell without ever being fully connected to the first serving cell, as previously described herein. Specifically, Figure 4 The signaling shown illustrates an example of the two-step SI acquisition method described in this paper.

[0136] Process flow 400 includes UE 115-c, first serving cell 405-a, and second serving cell 405-b, which can be examples of UE 115, network entity 105, serving cells 205, 305, and other radio devices as described herein. For example, Figure 4 The UE 115-c, the first serving cell 405-a, and the second serving cell 405-b illustrated herein may respectively include, as follows: Figure 2 Examples of UE 115-a, first serving cell 205-a, and second serving cell 205-b are illustrated. Similarly, Figure 4 The UE115-c, the first serving cell 405-a, and the second serving cell 405-b illustrated herein may respectively include, as follows: Figure 3Examples of UE 115-b, first serving cell 305-a, and second serving cell 305-b are illustrated. In this regard, first serving cell 405-a and second serving cell 405-b may be associated with the same or different network entities 105 (e.g., supported by these same or different network entities) and may be configured to communicate using the same or different frequency bands / RATs. For example, in some cases, first serving cell 405-a may include a 5G cell, and second serving cell 405-b may include a 6G cell.

[0137] In some examples, the operations illustrated in process flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0138] At 410, UE 115-c may receive one or more broadcast SI messages from the first serving cell 405-a. Broadcast SI messages may include MIBs, SIBs (e.g., SIB1), SSBs, or any combination thereof. For example, in some cases, UE 115-c may perform measurements on SSBs received from the first serving cell 405-a. As previously described herein, in the case of co-location of serving cells 405-a and 405-b, UE 115-c may be able to access the second serving cell 405-b using measurements and assumptions (e.g., path loss, spatial information, TA value) based on SSBs received from the first serving cell 405-a. The first serving cell 205-a may use 5G signaling (e.g., using 5G communication protocols within 5G resources) to send broadcast SI messages 230-a.

[0139] The broadcast SI messages at 310 locations include a one-step SI acquisition method for all SIs required by UE 115-b to access the second serving cell 05-b (in Figure 3 Compared to the example in the text, the two-step SI acquisition method (in...) Figure 4 (As illustrated in the example), the broadcast SI message at 410 may only include a subset of SIs that enable UE 115-c to initiate a RACH procedure with the second serving cell 405-b and / or wake up the second serving cell. That is, according to the two-step SI acquisition method, the 5G cell can "outsource" the transmission of most 6G-related SIs to the 6G cell itself. Therefore, according to the two-step SI acquisition method, the SIs required to access the second serving cell 405-b can be divided across the signaling received from the two serving cells 405-a and 405-b.

[0140] For example, in the context of a two-step SI acquisition method, a 5G SIB (e.g., a broadcast SI message) may include bit fields indicating the initial downlink BWP, initial CORESET (CORESET0), and / or search space (e.g., search space 0) for the second serving cell 405-b. In this example, in order to retrieve the remaining SIs to be used for accessing the second serving cell 405-b, UE 115-c (and / or the first serving cell 405-a) may have to wake up the second serving cell 405-b so that the second serving cell 405-b can send / broadcast an SIB (e.g., a broadcast SI message) including the remaining SIs to be used for accessing the second serving cell 405-b. In this regard, UE 115-c may use the SI received at 410 in the broadcast SI message from the first serving cell 405-a to directly send a RACH message to the second serving cell 405-b, and / or send a RACH message that will be relayed from the first serving cell 405-a to the second serving cell 405-b.

[0141] In some respects, the information within the broadcast SI message sent by the first serving cell 405-a at 410 may be interpreted differently depending on whether the information is to be applied to communication with the first serving cell 405-a (e.g., 5G communication) or with the second serving cell 405-b (e.g., 6G communication). In other words, a 5G-capable UE 115 that will use SI to communicate with the first serving cell 405-a for 5G will interpret the bit fields differently than a 6G-capable UE 115 that will use SI to communicate with the second serving cell 405-b for 6G. When a 6G-capable UE 115 knows that a 5G cell (e.g., the first serving cell 405-a) is associated with a 6G cell (e.g., the second serving cell 405-b), it may be useful to use separate interpretations for the same bit fields within the broadcast SI message at 410, regardless of whether the 5G cell is associated with a 6G cell MRSS or with a reframed 6G cell.

[0142] For example, the broadcast SI message at 410 may include one or more bit fields associated with a PDCCH or SIB configuration (e.g., pdcch-ConfigSIB1). In this example, the 5G UE 115 may interpret the bit fields of pdcch-ConfigSIB1 according to a first interpretation used for 5G communication with the first serving cell 405-a. In contrast, the 6G UE 115 may interpret the bit fields of pdcch-ConfigSIB1 according to a second interpretation used for 6G communication with the second serving cell 405-b. Utilizing this new interpretation of the bit fields of pdcch-ConfigSIB1 for the 6G cell, it may not be expected that the 6G-capable UE 115 will detect and decode the 5GSIB1 message to obtain the information required to acquire the 6G SIB. Instead, the 6G-capable UE 115 can directly detect and decode the 6G SIB. In this respect, allowing different interpretations of the same bit fields within the broadcast SI message 230-a, compared to some previous methods, can result in lower latency and lower power consumption for UE 115 with 6G capability, and can also result in lower 5G network overhead and power consumption.

[0143] At 415, UE 115-c may send RACH messages and / or WUS to the first serving cell 405-a. In such a case, at 420, the first serving cell 405-a may be configured to forward or relay information / messages to the second serving cell 405-b.

[0144] For example, as previously described herein, UE 115-c may receive a broadcast SI message from first serving cell 405-a at 410 (without establishing a connection with first serving cell 405-a), wherein the broadcast SI message includes some SIs for accessing second serving cell 405-b. UE 115-c may use the SIs included in the broadcast SI message at 410 to send a RACH message (and / or WUS) to first serving cell 405-a to notify / inform first serving cell 405-a that UE 115-c wants to access second serving cell 405-b. In this example, first serving cell 405-a may forward or relay the RACH message and / or WUS to second serving cell 405-b to "wake up" second serving cell 405-b.

[0145] In an additional or alternative implementation, UE 115-c may directly send RACH messages (and / or WUS) to the second serving cell 405-b, as shown and described in step 425.

[0146] At 425, UE 115-c may directly send RACH messages and / or WUS to the second serving cell 405-c. In this respect, step 425 can be considered an alternative to the steps shown and described in steps 415 and 420.

[0147] At 430, the second serving cell 405-b can transition from a sleep state to an active state. In other words, the second serving cell 405-b can be "wake up" based on receiving a RACH message and / or WUS from the first serving cell 405-a at 420 and / or from UE 115-c at 425.

[0148] As previously noted herein, in the case where the second serving cell 405-b is co-located with the first serving cell 405-a, the UE 115-c may be able to apply measurements and / or assumptions (e.g., TA values, path loss information, spatial information) associated with the first serving cell 405-a to its communications with the second serving cell 405-b. Therefore, in the case of cell co-location, the second serving cell 405-b may not need to transmit its own SSB, and process flow 400 may proceed directly to step 440.

[0149] However, in other cases where the second serving cell 405-b is not co-located with the first serving cell 405-a, the measurements / assumptions performed on the SSB received from the first serving cell 405-a may not apply (e.g., cannot be used) to communication with the second serving cell 405-b. Therefore, in cases where the serving cells are not co-located, the second serving cell 405-b may be expected to send its own SSB, allowing the UE 115-c to perform measurements and determine TA values, path loss information, spatial information, etc. Therefore, in cases where the cells are not co-located, process flow 400 may proceed to step 435.

[0150] At 435, the second serving cell 405-b may send / broadcast one or more SSBs. Specifically, when the cells are not co-located, the second serving cell 405-b may send an SSB, allowing the UE 115-c to perform measurements on the SSB to determine information for communicating with the second serving cell 405-b, such as TA value, path loss information, spatial information, etc.

[0151] At 440, the second serving cell 405-b may send / broadcast one or more additional broadcast SI messages (e.g., SIB, MIB), wherein the additional broadcast SI messages may include the remainder of the SI used for accessing the second serving cell 405-b and not included in the broadcast SI message received from the first serving cell 405-a at 410. In this example, UE 115-c may use the additional SI within the broadcast SI message received from the second serving cell 405-b at 440 to perform the RACH procedure and establish a connection with the second serving cell 405-b.

[0152] At 445, UE 115-c and the second serving cell 405-b can perform a RACH procedure (and / or an RRC connection procedure) to establish a connection between UE 115-c and the second serving cell 405-b. UE 115-c can perform the RACH procedure with the second serving cell 405-b (e.g., a 6G cell) based on (e.g., according to) the SI received at 410 via the first serving cell 405-a and an additional SI received at 435 via the second serving cell 405-b. That is, after obtaining the SI from the second serving cell 405-b, UE 115-c can be configured to initiate and continue the initial access procedure with the second serving cell 405-b (e.g., performing the RACH procedure and the RRC connection procedure on a 6G carrier / frequency). That is, as part of the RACH process, UE 115-c can use the SI received from the second serving cell 405-b (via the broadcast SI message at 440) to exchange RACH messages (e.g., PRACH messages) with the second serving cell 405-b.

[0153] At 450, UE 115-c and the second serving cell 405-b can communicate one or more messages to each other. UE 115-c and the second serving cell 405-b can communicate messages to each other at 420 based on receiving a broadcast SI message at 410, sending / relaying RACH messages and / or WUS at 415, 420 and 425, transitioning to an active state at 430, receiving an SSB at 435, receiving an additional broadcast SI message at 440, performing a RACH procedure at 445 or any combination thereof.

[0154] Figure 5A block diagram 500 illustrates a device 505 supporting system information for assisted access in wireless communication according to one or more aspects of this disclosure. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0155] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to system information for auxiliary access in wireless communications). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

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

[0157] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of system information for auxiliary access in wireless communication as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof or components thereof may be able to perform one or more of the functions described herein.

[0158] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0159] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0160] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated in combination with the receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0161] For example, the communication manager 520 can be configured or operated to support components for receiving a broadcast SI message from a first serving cell, wherein the broadcast SI message includes an SI for connecting to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. The communication manager 520 can be configured or operated to support components for sending a RACH message to the first serving cell or the second serving cell based on the SI included in the received broadcast SI message. The communication manager 520 can be configured or operated to support components for performing a random access procedure with the second serving cell to establish a radio connection with the second serving cell based on sending the RACH message. The communication manager 520 can be configured or operated to support components for communicating one or more messages with the second serving cell based on the random access procedure.

[0162] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., control receiver 510, transmitter 515, communication manager 520, or a combination thereof, or at least one processor otherwise coupled thereto) can support techniques that enable UE 115 to access a second serving cell (and / or a second RAT) using broadcast SI messages received from a first serving cell (and / or a first RAT) without a full connection to the first serving cell. Therefore, the techniques described herein can reduce control signaling overhead (by reducing or eliminating signaling used to establish a connection between UE 115 and the first cell). Furthermore, the techniques described herein can reduce communication latency at UE 115 by reducing the amount of time spent establishing a connection between UE 115 and the second serving cell.

[0163] Figure 6 A block diagram 600 illustrates a device 605 supporting system information for assisted access in wireless communication according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to system information for auxiliary access in wireless communications). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

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

[0166] Device 605 or its various components may be examples of parts used to perform various aspects of system information for assisted access in wireless communications as described herein. For example, communication manager 620 may include SI message receiving manager 625, RACH message sending manager 630, RACH process manager 635, serving cell manager 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0167] SI message receiving manager 625 is capable of, configured to, or operable to support components for receiving broadcast SI messages from a first serving cell, wherein the broadcast SI message includes an SI for connecting to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. RACH message sending manager 630 is capable of, configured to, or operable to support components for sending RACH messages to the first or second serving cell based on the received SI included in the broadcast SI message. RACH procedure manager 635 is capable of, configured to, or operable to support components for performing a random access procedure with the second serving cell to establish a radio connection with the second serving cell based on sending the RACH message. Serving cell manager 640 is capable of, configured to, or operable to support components for communicating one or more messages with the second serving cell based on the random access procedure.

[0168] Figure 7 A block diagram 700 of a communication manager 720 supporting system information for auxiliary access in wireless communications, according to one or more aspects of this disclosure, is shown. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of system information for auxiliary access in wireless communications as described herein. For example, the communication manager 720 may include an SI message receiving manager 725, a RACH message sending manager 730, a RACH process manager 735, a serving cell manager 740, an SSB receiving manager 745, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0169] SI message receiving manager 725 is capable of, configured to, or operable to support components for receiving broadcast SI messages from a first serving cell, wherein the broadcast SI message includes an SI for connecting to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. RACH message sending manager 730 is capable of, configured to, or operable to support components for sending RACH messages to the first or second serving cell based on the received SI included in the broadcast SI message. RACH procedure manager 735 is capable of, configured to, or operable to support components for performing a random access procedure with the second serving cell to establish a radio connection with the second serving cell based on sending the RACH message. Serving cell manager 740 is capable of, configured to, or operable to support components for communicating one or more messages with the second serving cell based on the random access procedure.

[0170] In some examples, the broadcast SI message includes one or more bit fields indicating whether the broadcast SI message includes an SI for connecting to a second serving cell.

[0171] In some examples, the SI used to connect to the second serving cell includes one or more RACH sequences for sending the RACH message, resources associated with the RACH timing, one or more RAR search space configurations, one or more BWPs for communicating with the second serving cell, a CORESET associated with the second serving cell, or any combination thereof.

[0172] In some examples, the SI included in the broadcast SI message indicates whether a first set of resources for communicating with the first serving cell is located on a separate component carrier relative to a second set of resources for communicating with the second serving cell, or whether the first set of resources for communicating with the first serving cell is located on the same component carrier as the second set of resources for communicating with the second serving cell.

[0173] In some examples, in order to support the transmission of RACH messages, the RACH message transmission manager 730 is capable of, configured to, or able to operate to support components for transmitting RACH messages to a second serving cell based on the SI included in the broadcast SI message.

[0174] In some examples, the SI message receiving manager 725 is capable of, configured to, or able to operate to support components for receiving a second broadcast SI message from the second serving cell based on the transmission of the RACH message, wherein the second broadcast SI message includes an additional SI for connecting to the second serving cell, wherein a random access procedure is performed with the second serving cell based on the SI and the additional SI.

[0175] In some examples, in order to support the transmission of RACH messages, the RACH message transmission manager 730 is capable of, configured to, or able to operate to support components for transmitting RACH messages to a second serving cell, wherein the RACH message includes a wake-up indication for the second serving cell, and wherein a second broadcast SI message is received based on the wake-up indication.

[0176] In some examples, in order to support the transmission of RACH messages, the RACH message transmission manager 730 is capable of, configured to, or able to operate to support components for transmitting RACH messages to a first serving cell, wherein the RACH message includes a wake-up indication for a second serving cell and a request to the first serving cell to relay the RACH message and the wake-up indication to the second serving cell, and wherein a second broadcast SI message is received based on the wake-up indication.

[0177] In some examples, the second broadcast SI message includes a SIB message.

[0178] In some examples, the SI included in the broadcast SI message comprises one or more bit fields associated with the SIB configuration. In some examples, if the SIB configuration is applied to a first serving cell, one or more bit fields are associated with a first interpretation. In some examples, if the SIB configuration is applied to a second serving cell, one or more bit fields are associated with a second interpretation.

[0179] In some examples, the SSB receive manager 745 is capable of, configured to, or able to operate to support components for receiving one or more SSB messages from a second serving cell based on the transmission of RACH messages, wherein a random access procedure is performed based on the reception of one or more SSB messages.

[0180] In some examples, the first serving cell and the second serving cell are supported by the same network entity.

[0181] In some examples, the first serving cell is associated with the first RAT. In some examples, the second serving cell is associated with the second RAT.

[0182] In some examples, the first RAT includes a 5G RAT, NR access technology, or both. In some examples, the second RAT includes a 6G RAT.

[0183] Figure 8A diagram of a system 800 including device 805 supporting assisted access in wireless communication, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0184] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

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

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

[0187] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting system information for assisted access in wireless communications). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0188] For example, the communication manager 820 can be configured or operated to support components for receiving a broadcast SI message from a first serving cell, wherein the broadcast SI message includes an SI for connecting to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. The communication manager 820 can be configured or operated to support components for sending a RACH message to the first serving cell or the second serving cell based on the SI included in the received broadcast SI message. The communication manager 820 can be configured or operated to support components for performing a random access procedure with the second serving cell to establish a radio connection with the second serving cell based on sending the RACH message. The communication manager 820 can be configured or operated to support components for communicating one or more messages with the second serving cell based on the random access procedure.

[0189] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support a technique that enables UE 115 to access a second serving cell (and / or a second RAT) using broadcast SI messages received from a first serving cell (and / or a first RAT) without a full connection to the first serving cell. Therefore, the technique described herein reduces control signaling overhead (by reducing or eliminating signaling used to establish a connection between UE 115 and the first cell). Furthermore, the technique described herein reduces communication latency at UE 115 by reducing the amount of time spent establishing a connection between UE 115 and the second serving cell.

[0190] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 815, one or more antennas 825, or any combination thereof, or otherwise cooperating with them. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions executable by at least one processor 840 to cause device 805 to perform various aspects of system information for assisted access in wireless communications as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0191] Figure 9A block diagram 900 illustrates a device 905 supporting system information for assisted access in wireless communication according to one or more aspects of this disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0194] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of system information for auxiliary access in wireless communication as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof or components thereof may be able to perform one or more of the functions described herein.

[0195] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

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

[0197] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in combination with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0198] For example, the communication manager 920 can be configured or operated to support components for sending a broadcast SI message to the UE, wherein the broadcast SI message includes an SI that the UE can use to connect to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. The communication manager 920 can be configured or operated to support components for receiving a RACH message from the UE based on the SI included within the broadcast SI message. The communication manager 920 can be configured or operated to support components for relaying RACH messages to the second serving cell to facilitate a random access procedure between the UE and the second serving cell.

[0199] For example, the communication manager 920 can be configured or operated to support components for receiving a wake-up signal from a first serving cell or the UE, instructing a second serving cell to wake up from a sleep state to an active state. The communication manager 920 can be configured or operated to support components for performing a random access procedure with the UE based on the received wake-up signal. The communication manager 920 can be configured or operated to support components for communicating one or more messages with the UE based on the random access procedure.

[0200] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., control receiver 910, transmitter 915, communication manager 920, or a combination thereof, or at least one processor otherwise coupled thereto) can support techniques that enable UE 115 to access a second serving cell (and / or a second RAT) using broadcast SI messages received from a first serving cell (and / or a first RAT) without a full connection to the first serving cell. Therefore, the techniques described herein can reduce control signaling overhead (by reducing or eliminating signaling used to establish a connection between UE 115 and the first cell). Furthermore, the techniques described herein can reduce communication latency at UE 115 by reducing the amount of time spent establishing a connection between UE 115 and the second serving cell.

[0201] Figure 10 A block diagram 1000 of a device 1005 supporting system information for assisted access in wireless communication, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0204] Device 1005 or its various components may be examples of parts used to perform various aspects of system information for assisted access in wireless communications as described herein. For example, communication manager 1020 may include SI message sending manager 1025, RACH message receiving manager 1030, cell relay manager 1035, WUS receiving manager 1040, RACH process manager 1045, UE communication manager 1050, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0205] SI message sending manager 1025 is capable of, configured to, or operable to support components for sending broadcast SI messages to a UE, wherein the broadcast SI message includes SIs that the UE can use to connect to a second serving cell, and wherein the broadcast SI message includes SSB messages, SIB messages, MIB messages, or any combination thereof. RACH message receiving manager 1030 is capable of, configured to, or operable to support components for receiving RACH messages from a UE based on the SIs included within the broadcast SI message. Cell relay manager 1035 is capable of, configured to, or operable to support components for relaying RACH messages to a second serving cell to facilitate a random access procedure between the UE and the second serving cell.

[0206] The WUS Receive Manager 1040 is capable of, configured to, or operable to support components for receiving a wake-up signal from a first serving cell or the UE, instructing a second serving cell to wake up from a sleep state to an active state. The RACH Procedure Manager 1045 is capable of, configured to, or operable to support components for performing a random access procedure with the UE based on the received wake-up signal. The UE Communication Manager 1050 is capable of, configured to, or operable to support components for communicating one or more messages with the UE based on the random access procedure.

[0207] Figure 11 A block diagram 1100 of a communication manager 1120 supporting system information for assisted access in wireless communications, according to one or more aspects of this disclosure, is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of system information for assisted access in wireless communications as described herein. For example, the communication manager 1120 may include an SI message sending manager 1125, a RACH message receiving manager 1130, a cell relay manager 1135, a WUS receiving manager 1140, a RACH procedure manager 1145, a UE communication manager 1150, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0208] SI message sending manager 1125 is capable of, configured to, or operable to support components for sending broadcast SI messages to the UE, wherein the broadcast SI message includes SIs that the UE can use to connect to a second serving cell, and wherein the broadcast SI message includes SSB messages, SIB messages, MIB messages, or any combination thereof. RACH message receiving manager 1130 is capable of, configured to, or operable to support components for receiving RACH messages from the UE based on the SIs included in the broadcast SI message. Cell relay manager 1135 is capable of, configured to, or operable to support components for relaying RACH messages to the second serving cell to facilitate a random access procedure between the UE and the second serving cell.

[0209] In some examples, the broadcast SI message includes one or more bit fields indicating whether the broadcast SI message includes an SI for connecting to a second serving cell.

[0210] In some examples, the SI used to connect to the second serving cell includes one or more RACH sequences for sending the RACH message, resources associated with the RACH timing, one or more RAR search space configurations, one or more BWPs for communicating with the second serving cell, a CORESET associated with the second serving cell, or any combination thereof.

[0211] In some examples, the SI included in the broadcast SI message indicates whether a first set of resources for communicating with the first serving cell is located on a separate component carrier relative to a second set of resources for communicating with the second serving cell, or whether the first set of resources for communicating with the first serving cell is located on the same component carrier as the second set of resources for communicating with the second serving cell.

[0212] In some examples, the RACH message includes a wake-up indication for the second serving cell and a request for the first serving cell to relay the RACH message and the wake-up indication to the second serving cell. In some examples, the relaying of the RACH message is based on receiving the wake-up indication and the request.

[0213] In some examples, the SI included in the broadcast SI message comprises one or more bit fields associated with the SIB configuration. In some examples, if the SIB configuration is applied to a first serving cell, one or more bit fields are associated with a first interpretation. In some examples, if the SIB configuration is applied to a second serving cell, one or more bit fields are associated with a second interpretation.

[0214] In some examples, in order to support relaying RACH messages, the cell relay manager 1135 is capable of, configured to, or able to operate to support components for relaying RACH messages to a set of multiple additional serving cells, including a second serving cell.

[0215] In some examples, the first serving cell and the second serving cell are supported by the same network entity.

[0216] In some examples, the first serving cell is associated with the first RAT. In some examples, the second serving cell is associated with the second RAT.

[0217] In some examples, the first RAT includes a 5G RAT, NR access technology, or both. In some examples, the second RAT includes a 6G RAT.

[0218] The WUS Receive Manager 1140 is capable of, configured to, or operable to support components for receiving a wake-up signal from a first serving cell or the UE, instructing a second serving cell to wake up from a sleep state to an active state. The RACH Procedure Manager 1145 is capable of, configured to, or operable to support components for performing a random access procedure with the UE based on the received wake-up signal. The UE Communication Manager 1150 is capable of, configured to, or operable to support components for communicating one or more messages with the UE based on the random access procedure.

[0219] In some examples, the SI message sending manager 1125 is capable of, configured to, or able to operate to support components for sending an SI message to the UE based on a received wake-up signal, wherein the SI message includes an SI that the UE can use to connect to a second serving cell.

[0220] In some examples, the RACH message reception manager 1130 is capable of, configured to, or able to operate to support components for receiving RACH messages from the UE, wherein a wake-up signal is received via a RACH message, and wherein a random access procedure is performed based on the receipt of the RACH message.

[0221] In some examples, the RACH message reception manager 1130 is capable of, configured to, or able to operate to support components for receiving RACH messages relayed in association with the UE from a first serving cell, wherein a wake-up signal is received via the RACH message, and wherein a random access procedure is performed based on the reception of the RACH message.

[0222] Figure 12A diagram of a system 1200 including device 1205 supporting assisted access in wireless communication, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or a component including such devices or network entities. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and obtaining communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0223] As described herein, transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, transceiver 1210 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1210 may also include a modem for modulating signals to provide modulated signals for transmission (e.g., via one or more antennas 1215, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components or configured to be coupled to said one or more processors or one or more memory components, said one or more processors or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0224] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by one of the at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0225] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting system information for assisted access in wireless communications). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1230) host functions for performing the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operated to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

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

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

[0228] For example, the communication manager 1220 can be configured or operated to support components for sending a broadcast SI message to the UE, wherein the broadcast SI message includes an SI that the UE can use to connect to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. The communication manager 1220 can be configured or operated to support components for receiving a RACH message from the UE based on the SI included in the broadcast SI message. The communication manager 1220 can be configured or operated to support components for relaying RACH messages to the second serving cell to facilitate a random access procedure between the UE and the second serving cell.

[0229] For example, the communication manager 1220 can be configured or operated to support components for receiving a wake-up signal from a first serving cell or a UE, instructing a second serving cell to wake up from a sleep state to an active state. The communication manager 1220 can be configured or operated to support components for performing a random access procedure with the UE based on the received wake-up signal. The communication manager 1220 can be configured or operated to support components for communicating one or more messages with the UE based on the random access procedure.

[0230] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support a technique that enables UE 115 to access a second serving cell (and / or a second RAT) using broadcast SI messages received from a first serving cell (and / or a first RAT) without a full connection to the first serving cell. Therefore, the technique described herein reduces control signaling overhead (by reducing or eliminating signaling used to establish a connection between UE 115 and the first cell). Furthermore, the technique described herein reduces communication latency at UE 115 by reducing the amount of time spent establishing a connection between UE 115 and the second serving cell.

[0231] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors in at least one processor 1235 to cause the device 1205 to perform various aspects of system information for assisted access in wireless communications as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0232] Figure 13 A flowchart illustrating a method 1300 for supporting system information for assisted access in wireless communication, according to various aspects of this disclosure, is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the functions. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0233] At 1305, the method may include receiving a broadcast SI message from a first serving cell, wherein the broadcast SI message includes an SI for connecting to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. The operation of block 1305 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1305 may be as described in references... Figure 7 The SI message receiving manager 725 described is used to perform this.

[0234] At 1310, the method may include sending a RACH message to a first serving cell or a second serving cell based on the SI included in the received broadcast SI message. The operation of block 1310 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1310 may be as described in the references... Figure 7 The RACH message sending manager 730 described is used to perform this.

[0235] At 1315, the method may include performing a random access procedure with a second serving cell to establish a radio connection based on sending a RACH message. The operation of block 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1315 may be derived from, as referenced... Figure 7 The RACH process manager 735 described is used for execution.

[0236] At 1320, the method may include communicating one or more messages with the second serving cell based on a random access procedure. The operation of block 1320 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1320 may be derived from, as referenced... Figure 7 The described service is executed by the Cell Manager 740.

[0237] Figure 14 A flowchart illustrating a method 1400 for supporting system information for assisted access in wireless communication, according to various aspects of this disclosure, is shown. The operation of method 1400 may be implemented by a network entity or its components as described herein. For example, the operation of method 1400 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12The network entity described performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0238] At 1405, the method may include sending a broadcast SI message to the UE, wherein the broadcast SI message includes an SI that the UE can use to connect to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SIB message, a MIB message, or any combination thereof. The operation of block 1405 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1405 may be as described in references... Figure 11 The SI message sending manager 1125 described herein is used to perform this.

[0239] At 1410, the method may include receiving a RACH message from the UE based on the SI included within the broadcast SI message. The operation of block 1410 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1410 may be derived from, as referenced... Figure 11 The RACH message receiving manager 1130 described herein is used for execution.

[0240] At 1415, the method may include relaying a RACH message to a second serving cell to facilitate a random access procedure between the UE and the second serving cell. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 11 The described cell relay manager 1135 performs this function.

[0241] Figure 15 A flowchart illustrating a method 1500 for supporting system information for assisted access in wireless communication, according to various aspects of this disclosure, is shown. The operation of method 1500 can be implemented by a network entity or its components as described herein. For example, the operation of method 1500 can be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The network entity described performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0242] At 1505, the method may include receiving a wake-up signal from a first serving cell or a UE instructing a second serving cell to wake up from a sleep state to an active state. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be as described in references... Figure 11The WUS receiver manager 1140 described herein is used to perform this.

[0243] At 1510, the method may include performing a random access procedure with the UE based on receiving a wake-up signal. The operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 11 The RACH process manager 1145 described above is used to execute this.

[0244] At 1515, the method may include communicating one or more messages to the UE based on a random access procedure. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from, as referenced... Figure 11 The UE communication manager 1150 described is executed by this.

[0245] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a broadcast SI message from a first serving cell, wherein the broadcast SI message includes an SI for connecting to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SI block message, a MIB message, or any combination thereof; transmitting a RACH message to the first serving cell or the second serving cell based at least in part on receiving the SI included in the broadcast SI message; performing a random access procedure with the second serving cell to establish a radio connection with the second serving cell based at least in part on transmitting the RACH message; and communicating one or more messages with the second serving cell based at least in part on the random access procedure.

[0246] Aspect 2: According to the method of aspect 1, the broadcast SI message includes one or more bit fields indicating whether the broadcast SI message includes the SI for connecting to the second serving cell.

[0247] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the SI for connecting to the second serving cell includes one or more RACH sequences for sending the RACH message, resources associated with RACH timing, one or more RAR search space configurations, one or more BWPs for communicating with the second serving cell, a CORESET associated with the second serving cell, or any combination thereof.

[0248] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the SI included in the broadcast SI message indicates whether a first set of resources for communicating with the first serving cell is located on a separate component carrier relative to a second set of resources for communicating with the second serving cell, or whether the first set of resources for communicating with the first serving cell is located on the same component carrier as the second set of resources for communicating with the second serving cell.

[0249] Aspect 5: The method according to any one of Aspects 1 to 4, wherein sending the RACH message comprises: sending the RACH message to the second serving cell according to the SI included in the broadcast SI message.

[0250] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: receiving a second broadcast SI message from the second serving cell based at least in part on sending the RACH message, wherein the second broadcast SI message includes an additional SI for connecting to the second serving cell, wherein the random access procedure is performed with the second serving cell based on the SI and the additional SI.

[0251] Aspect 7: According to the method of aspect 6, sending the RACH message includes: sending the RACH message to the second serving cell, wherein the RACH message includes a wake-up indication for the second serving cell, and wherein the second broadcast SI message is received at least in part based on the wake-up indication.

[0252] Aspect 8: The method according to any one of Aspects 6 to 7, wherein sending the RACH message comprises: sending the RACH message to the first serving cell, wherein the RACH message includes a wake-up indication for the second serving cell and a request for the first serving cell to relay the RACH message and the wake-up indication to the second serving cell, and wherein the second broadcast SI message is received at least in part based on the wake-up indication.

[0253] Aspect 9: The method according to any one of Aspects 6 to 8, wherein the second broadcast SI message includes an SI block message.

[0254] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the SI included in the broadcast SI message includes one or more bit fields associated with an SI block configuration, wherein the one or more bit fields are associated with a first interpretation when the SI block configuration is applied to the first serving cell, and wherein the one or more bit fields are associated with a second interpretation when the SI block configuration is applied to the second serving cell.

[0255] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: receiving one or more SSB messages from the second serving cell at least in part based on sending the RACH message, wherein the random access procedure is performed at least in part based on receiving the one or more SSB messages.

[0256] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the first serving cell and the second serving cell are supported by the same network entity.

[0257] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the first serving cell is associated with a first RAT and the second serving cell is associated with a second RAT.

[0258] Aspect 14: The method according to aspect 13, wherein the first RAT includes a 5G RAT, a new radio access technology, or both, and the second RAT includes a 6G RAT.

[0259] Aspect 15: A method for wireless communication at a first serving cell, the method comprising: sending a broadcast SI message to a UE, wherein the broadcast SI message includes an SI that the UE can use to connect to a second serving cell, and wherein the broadcast SI message includes an SSB message, an SI block message, a MIB message, or any combination thereof; receiving a RACH message from the UE based at least in part on the SI included in the broadcast SI message; and relaying the RACH message to the second serving cell to facilitate a random access procedure between the UE and the second serving cell.

[0260] Aspect 16: According to the method of aspect 15, the broadcast SI message includes one or more bit fields indicating whether the broadcast SI message includes the SI for connecting to the second serving cell.

[0261] Aspect 17: The method according to any one of Aspects 15 to 16, wherein the SI for connecting to the second serving cell includes one or more RACH sequences for sending the RACH message, resources associated with RACH timing, one or more RAR search space configurations, one or more BWPs for communicating with the second serving cell, a CORESET associated with the second serving cell, or any combination thereof.

[0262] Aspect 18: The method according to any one of Aspects 15 to 17, wherein the SI included in the broadcast SI message indicates whether a first set of resources for communicating with the first serving cell is located on a separate component carrier relative to a second set of resources for communicating with the second serving cell, or whether the first set of resources for communicating with the first serving cell is located on the same component carrier as the second set of resources for communicating with the second serving cell.

[0263] Aspect 19: The method according to any one of Aspects 15 to 18, wherein the RACH message includes a wake-up indication for the second serving cell and a request for the first serving cell to relay the RACH message and the wake-up indication to the second serving cell, and the relaying of the RACH message is based at least in part on receiving the wake-up indication and the request.

[0264] Aspect 20: The method according to any one of Aspects 15 to 19, wherein the SI included in the broadcast SI message includes one or more bit fields associated with an SI block configuration, wherein the one or more bit fields are associated with a first interpretation when the SI block configuration is applied to the first serving cell, and wherein the one or more bit fields are associated with a second interpretation when the SI block configuration is applied to the second serving cell.

[0265] Aspect 21: The method according to any one of Aspects 15 to 20, wherein relaying the RACH message includes: relaying the RACH message to a plurality of additional serving cells including the second serving cell.

[0266] Aspect 22: The method according to any one of Aspects 15 to 21, wherein the first serving cell and the second serving cell are supported by the same network entity.

[0267] Aspect 23: The method according to any one of Aspects 15 to 22, wherein the first serving cell is associated with a first RAT and the second serving cell is associated with a second RAT.

[0268] Aspect 24: According to the method of aspect 23, the first RAT includes a 5G RAT, a new radio access technology, or both, and the second RAT includes a 6G RAT.

[0269] Aspect 25: A method for wireless communication at a second serving cell, the method comprising: receiving from a first serving cell or a UE a wake-up signal instructing the second serving cell to wake up from a sleep state to an active state; performing a random access procedure with the UE based at least in part on the receipt of the wake-up signal; and communicating one or more messages with the UE based at least in part on the random access procedure.

[0270] Aspect 26: The method according to aspect 25, the method further comprising: sending an SI message to the UE at least in part based on receiving the wake-up signal, wherein the SI message includes an SI that the UE can use to connect to the second serving cell.

[0271] Aspect 27: The method according to any one of Aspects 25 to 26, the method further comprising: receiving a RACH message from the UE, wherein the wake-up signal is received via the RACH message, and wherein the random access procedure is performed at least in part based on the receipt of the RACH message.

[0272] Aspect 28: The method according to any one of Aspects 25 to 27, the method further comprising: receiving a RACH message relayed in association with the UE from the first serving cell, wherein the wake-up signal is received via the RACH message, and wherein the random access procedure is performed at least in part based on the receipt of the RACH message.

[0273] Aspect 29: A UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 1 to 14.

[0274] Aspect 30: A UE comprising at least one component for performing the method according to any one of aspects 1 to 14.

[0275] Aspect 31: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 14.

[0276] Aspect 32: A network entity associated with a first serving cell for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs the method according to any one of Aspects 15 to 24 via the first serving cell.

[0277] Aspect 33: A network entity associated with a first serving cell for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 15 to 24.

[0278] Aspect 34: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 15 to 24.

[0279] Aspect 35: A network entity associated with a second serving cell for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs the method according to any one of Aspects 25 to 28 via the second serving cell.

[0280] Aspect 36: A network entity associated with a second serving cell for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 25 to 28.

[0281] Aspect 37: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 25 to 28.

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

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

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

[0285] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

[0287] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

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

[0289] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0290] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0291] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0292] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a broadcast system information message from a first serving cell, wherein the broadcast system information message includes system information for connecting to a second serving cell, and wherein the broadcast system information message includes a synchronization signal block message, a system information block message, a master information block message, or any combination thereof; At least in part, a random access channel message is sent to the first serving cell or the second serving cell based on the system information included in the received broadcast system information message; At least in part, a random access procedure is performed with the second serving cell to establish a radio connection with the second serving cell based on sending the random access channel message; as well as One or more messages are communicated with the second serving cell, at least in part, based on the random access procedure.

2. The UE according to claim 1, wherein the broadcast system information message includes one or more bit fields, the one or more bit fields indicating whether the broadcast system information message includes system information for connecting to the second serving cell.

3. The UE of claim 1, wherein the system information for connecting to the second serving cell includes one or more random access channel sequences for transmitting the random access channel message, resources associated with random access channel timing, one or more random access response search space configurations, one or more bandwidth portions for communicating with the second serving cell, a set of control resources associated with the second serving cell, or any combination thereof.

4. The UE of claim 1, wherein the system information included in the broadcast system information message indicates whether a first set of resources for communicating with the first serving cell is located on a separate component carrier relative to a second set of resources for communicating with the second serving cell, or whether the first set of resources for communicating with the first serving cell is located on the same component carrier as the second set of resources for communicating with the second serving cell.

5. The UE according to claim 1, wherein, In order to send the random access channel message, the one or more processors can operate individually or jointly to execute the code to cause the UE to: The random access channel message is sent to the second serving cell based on the system information included in the broadcast system information message.

6. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The second broadcast system information message is received from the second serving cell at least in part based on the transmission of the random access channel message, wherein the second broadcast system information message includes additional system information for connecting to the second serving cell, and wherein the random access procedure is performed with the second serving cell based on the system information and the additional system information.

7. The UE according to claim 6, wherein, In order to send the random access channel message, the one or more processors can operate individually or jointly to execute the code to cause the UE to: The random access channel message is sent to the second serving cell, wherein the random access channel message includes a wake-up indication for the second serving cell, and wherein the second broadcast system information message is received at least in part based on the wake-up indication.

8. The UE according to claim 6, wherein, In order to send the random access channel message, the one or more processors can operate individually or jointly to execute the code to cause the UE to: The random access channel message is sent to the first serving cell, wherein the random access channel message includes a wake-up indication for the second serving cell and a request for the first serving cell to relay the random access channel message and the wake-up indication to the second serving cell, and wherein the second broadcast system information message is received at least in part based on the wake-up indication.

9. The UE according to claim 6, wherein the second broadcast system information message includes a system information block message.

10. The UE of claim 1, wherein the system information included in the broadcast system information message includes one or more bit fields associated with a system information block configuration, wherein when the system information block configuration is applied to the first serving cell, the one or more bit fields are associated with a first interpretation, and wherein when the system information block configuration is applied to the second serving cell, the one or more bit fields are associated with a second interpretation.

11. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The random access procedure is performed at least in part based on receiving one or more synchronization block messages from the second serving cell, wherein the random access procedure is performed at least in part based on receiving the one or more synchronization block messages.

12. The UE of claim 1, wherein the first serving cell and the second serving cell are supported by the same network entity.

13. The UE of claim 1, wherein the first serving cell is associated with a first radio access technology, and wherein the second serving cell is associated with a second radio access technology.

14. The UE of claim 13, wherein the first radio access technology includes fifth-generation radio access technology, new radio access technology, or both, and wherein the second radio access technology includes sixth-generation radio access technology.

15. A network entity associated with a first serving cell, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the network entity to transit the first serving cell: Sending a broadcast system information message to a user equipment (UE), wherein the broadcast system information message includes system information that the UE can use to connect to a second serving cell, and wherein the broadcast system information message includes a synchronization signal block message, a system information block message, a main information block message, or any combination thereof; The random access channel message is received from the UE based at least in part on the system information included in the broadcast system information message. as well as The random access channel message is relayed to the second serving cell to facilitate the random access process between the UE and the second serving cell.

16. The network entity of claim 15, wherein the broadcast system information message includes one or more bit fields, the one or more bit fields indicating whether the broadcast system information message includes the system information for connecting to the second serving cell.

17. The network entity of claim 15, wherein the system information for connecting to the second serving cell includes one or more random access channel sequences for transmitting the random access channel message, resources associated with random access channel timing, one or more random access response search space configurations, one or more bandwidth portions for communicating with the second serving cell, a set of control resources associated with the second serving cell, or any combination thereof.

18. The network entity of claim 15, wherein the system information included in the broadcast system information message indicates whether a first set of resources for communicating with the first serving cell is located on a separate component carrier relative to a second set of resources for communicating with the second serving cell, or whether the first set of resources for communicating with the first serving cell is within the same component carrier as the second set of resources for communicating with the second serving cell.

19. The network entity of claim 15, wherein the random access channel message includes a wake-up indication for the second serving cell and a request for the first serving cell to relay the random access channel message and the wake-up indication to the second serving cell, and wherein relaying the random access channel message is based at least in part on receiving the wake-up indication and the request.

20. The network entity of claim 15, wherein the system information included in the broadcast system information message includes one or more bit fields associated with a system information block configuration, wherein when the system information block configuration is applied to the first serving cell, the one or more bit fields are associated with a first interpretation, and wherein when the system information block configuration is applied to the second serving cell, the one or more bit fields are associated with a second interpretation.

21. The network entity according to claim 15, wherein, In order to relay the random access channel messages, the one or more processors can operate individually or jointly to execute the code to cause the network entity to transit through the first serving cell: The random access channel message is relayed to multiple additional serving cells, including the second serving cell.

22. The network entity of claim 15, wherein both the first serving cell and the second serving cell are supported by the network entity.

23. The network entity of claim 15, wherein the first serving cell is associated with a first radio access technology, and wherein the second serving cell is associated with a second radio access technology.

24. The network entity of claim 23, wherein the first radio access technology includes fifth-generation radio access technology, new radio access technology, or both, and wherein the second radio access technology includes sixth-generation radio access technology.

25. A network entity associated with a second serving cell, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the network entity to transit the second serving cell: Receive a wake-up signal from the first serving cell or user equipment (UE) instructing the second serving cell to wake up from a sleep state to an active state; At least in part based on receiving the wake-up signal, perform a random access procedure with the UE; and One or more messages are communicated to the UE, at least in part, based on the random access procedure.

26. The network entity of claim 25, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to transit via the second serving cell: The system information message is sent to the UE at least in part based on the receipt of the wake-up signal, wherein the system information message includes system information that the UE can use to connect to the second serving cell.

27. The network entity of claim 25, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to transit via the second serving cell: The UE receives a random access channel message, wherein the wake-up signal is received via the random access channel message, and wherein the random access procedure is performed at least in part based on the receipt of the random access channel message.

28. The network entity of claim 25, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to transit via the second serving cell: The UE receives a random access channel message relayed in association with the UE from the first serving cell, wherein the wake-up signal is received via the random access channel message, and wherein the random access procedure is performed at least in part based on the receipt of the random access channel message.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a broadcast system information message from a first serving cell, wherein the broadcast system information message includes system information for connecting to a second serving cell, and wherein the broadcast system information message includes a synchronization signal block message, a system information block message, a master information block message, or any combination thereof; At least in part, a random access channel message is sent to the first serving cell or the second serving cell based on the system information included in the received broadcast system information message; At least in part, a random access procedure is performed with the second serving cell to establish a radio connection with the second serving cell based on sending the random access channel message; as well as One or more messages are communicated with the second serving cell, at least in part, based on the random access procedure.

30. The method of claim 29, wherein the broadcast system information message includes one or more bit fields, the one or more bit fields indicating whether the broadcast system information message includes system information for connecting to the second serving cell.

Images