Auxiliary access to serving cell for wireless communication

Abstract

Methods, systems, and devices for wireless communication are described. Techniques described herein provide for assisted access to a serving cell for wireless communications. The UE may receive a broadcast system information message from a first cell. The broadcast system information message may include system information that may be used to communicate with the second cell. Using the received system information, the UE may transmit a random access channel (RACH) preamble message to the first cell to establish a connection with the second cell. The first cell may transmit a wake-up signal to the second cell in response to receiving the RACH preamble message.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 487,748, filed October 16, 2023, entitled “ASSISTED ACCESS TO A SERVING CELL FOR WIRELESS COMMUNICATIONS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communication, including techniques for assisted access to the serving cell for 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). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for assisted access to a serving cell for wireless communication. For example, the described technology provides a first cell for assisted UE access to a second cell that can be in a deep sleep level for power saving. The first cell may exchange signaling with the UE to enable the UE to access the second cell. The first cell may send signaling to the second cell to wake up the target cell, enabling the UE to access the second cell. For example, the UE may receive a broadcast system information message from the first cell. The broadcast system information message may include system information that can be used to communicate with the second cell. Using the received system information, the UE may send a random access channel (RACH) preamble message to the first cell to establish a connection with the second cell. The first cell may send a wake-up signal and a RACH preamble message to the second cell in response to receiving the RACH preamble message. Additional signaling may be exchanged between the UE and the first cell, and additional signaling may be exchanged between the UE and the second cell to grant the UE access to the second cell. Attached Figure Description

[0006] Figure 1 An example of a wireless communication system is shown that supports techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure.

[0007] Figure 2 An example of a wireless communication system is shown that supports techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure.

[0008] Figure 3 An example of a process flow supporting a technique for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown.

[0009] Figure 4 and Figure 5 A block diagram of an apparatus supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown.

[0010] Figure 6 A block diagram of a communication manager supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown.

[0011] Figure 7 A diagram is shown of a system including an apparatus supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure.

[0012] Figure 8 and Figure 9A block diagram of an apparatus supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown.

[0013] Figure 10 A block diagram of a communication manager supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown.

[0014] Figure 11 A diagram is shown of a system including an apparatus supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure.

[0015] Figures 12 to 15 A flowchart illustrating a method for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0016] As future generations of Radio Access Technologies (RATs) are developed and deployed, many wireless networks will support multiple RATs during their "migration cycles." For example, as wireless devices gradually "migrate" to 6G devices, wireless networks will support both 5G and 6G devices. However, several challenges exist when handling migration across RATs. First, power consumption and network energy conservation issues can arise when supporting multiple RATs within a network. For example, there may be situations where a 6G cell does not include any 6G devices. When a 6G cell is not serving user equipment (UE), it can be placed in a deep sleep level for power conservation.

[0017] Techniques for assisted access to a serving cell can provide power savings. For example, a first cell (e.g., a 5G cell) can assist a UE in accessing a second cell (e.g., a 6G cell) that can be in deep sleep mode for power saving. The first cell (e.g., the 5G cell) can exchange signaling with the UE to enable the UE to access the second cell (6G cell). The first cell (e.g., the 5G cell) can send signaling to the second cell (e.g., the 6G cell) to "wake up" the target cell (e.g., the 6G cell) to enable the UE to access the second cell (e.g., the 6G cell). For example, the UE can receive a broadcast system information message from the first cell, such as a 5G cell. The broadcast system information message may include system information that can be used to communicate with the second cell, such as a 6G cell. Using the received system information, the UE can send a random access channel (RACH) preamble message to the first cell to establish a connection with the second cell.

[0018] In some examples, the first cell may send a wake-up signal and a RACH preamble message to the second cell in response to receiving a RACH preamble message. In some cases, the first cell may decide not to wake up the second cell. The UE may receive a random access response message indicating uplink resources based on sending the RACH preamble message. In some cases, the random access response message may be sent by either the first cell or the second cell. The UE may send uplink messages on uplink resources in response to receiving the random access response message, and the uplink resources may be uplink resources of either the first cell or the second cell. The UE may receive downlink messages on downlink resources based on sending the uplink messages, and the downlink resources may be downlink resources of either the first cell or the second cell. After receiving the downlink messages, if access to the second cell has been granted, the UE and the second cell may begin communicating with each other.

[0019] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of timing diagrams and process flows. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to techniques for assisted access to a serving cell for wireless communication.

[0020] Figure 1 An example of a wireless communication system 100 supporting techniques for assisted access to a serving cell for 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.

[0021] 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).

[0022] 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.

[0023] 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.

[0024] 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. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be 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, or may 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 may communicate with the core network 130 via communication link 155.

[0025] 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).

[0026] 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)).

[0027] 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 may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer may be performed by different of CU 160, DU 165, or RU 170). CU 160 may be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 may 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.

[0028] 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.

[0029] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support techniques for assisted access to a serving cell for wireless communication 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).

[0030] 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.

[0031] 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.

[0032] 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 radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling 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, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0033] 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.

[0034] 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).

[0035] 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.

[0036] 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)).

[0037] 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.

[0038] 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, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0039] 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.

[0040] 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)).

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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).

[0046] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating 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 bands may be combined with component carriers operating with licensed 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.

[0047] 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.

[0048] 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).

[0049] As future generations of RATs are developed and deployed, many wireless networks will support multiple RATs during their "migration cycles." For example, as wireless devices gradually migrate to 6G devices, wireless networks will support both 5G and 6G devices. However, several challenges exist when handling migrations across RATs. First, power consumption and network energy conservation issues can arise when supporting multiple RATs within a network. For example, there may be situations where a 6G cell does not include any 6G devices. When a 6G cell is not serving UE 115, it can be placed in a deep sleep level for power conservation.

[0050] Techniques for assisted access to a serving cell can provide power savings. For example, a first cell (e.g., a 5G cell) can assist UE 115 in accessing a second cell (e.g., a 6G cell) that can be in deep sleep mode for power saving. The first cell (e.g., the 5G cell) can exchange signaling with UE 115 to enable UE 115 to access the second cell (6G cell). The first cell (e.g., the 5G cell) can send signaling to the second cell (e.g., the 6G cell) to wake up the target cell (e.g., the 6G cell) to enable UE 115 to access the second cell (e.g., the 6G cell). For example, UE 115 can receive a broadcast system information message from the first cell, such as the 5G cell. The broadcast system information message may include system information that can be used to communicate with the second cell, such as the 6G cell. Using the received system information, UE 115 can send a RACH preamble message to the first cell to establish a connection with the second cell.

[0051] In some examples, the first cell may send a wake-up signal and a RACH preamble message to the second cell in response to receiving a RACH preamble message. In some cases, the first cell may decide not to wake up the second cell. UE 115 may receive a random access response message indicating uplink resources based on sending a RACH preamble message. In some cases, the random access response message may be sent by either the first cell or the second cell. UE 115 may send uplink messages on uplink resources in response to receiving a random access response message, and the uplink resources may be uplink resources of either the first cell or the second cell. UE 115 may receive downlink messages on downlink resources based on sending uplink messages, and the downlink resources may be downlink resources of either the first cell or the second cell. After receiving the downlink message, if access to the second cell has been granted, UE 115 and the second cell may begin communicating with each other.

[0052] Figure 2 An example of a wireless communication system 200 supporting techniques for assisted access to a serving cell for 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 assisted access to a serving cell.

[0053] The wireless communication system 200 may include a UE 115-a, a first cell 205-a (e.g., a source cell) and a second cell 205-b (e.g., a target cell), which may be as shown in the reference. Figure 1 Examples of the described UE 115, network entity 105, and other radio 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 cell 205-a and second cell 205-b may be associated with the same network entity 105 (e.g., supported by the same network entity). By another example, in other cases, first cell 205-a may be associated with a first network entity 105, and second cell 205-b may be associated with a second network entity 105.

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

[0055] In some respects, UE 115-a may communicate with serving cell 205 via communication links 210-a and 210-b. In some cases, communication links 210-a and 210-b may include examples of access links (e.g., Uu links). Communication links 210-a and 210-b may include bidirectional links, 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 first cell 205-a, and first 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. For example, UE 115-a can use communication link 210-b to send uplink transmissions, such as uplink control signals or uplink data signals, to the second cell 205-b, and the second cell 205-b can use communication link 210-b to send downlink transmissions, such as downlink control signals or downlink data signals, to UE 115-a.

[0056] In some examples, the first cell 205-a may communicate with the second cell 205-b via communication link 210-c. In some cases, communication link 210-c may include examples of an access link (e.g., a Uu link), a backhaul communication link, a midhaul communication link, or a fronthaul communication link, or any combination thereof. Communication link 210-c may include a bidirectional link. For example, the first cell 205-a may use communication link 210-c to send transmissions, such as control signals or data signals, to the second cell 205-b, and the second cell 205-b may use communication link 210-c to send transmissions, such as control signals or data signals, to the first cell 205-a.

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

[0058] Several different "migration schemes" exist that can be used for migration between / across RATs. For example, Figure 2Static 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.

[0059] Static configuration 215-a illustrates a “static reconfiguration” configuration that statically partitions resources across supported RATs in the time and / or frequency domains. Through static reconfiguration (as shown via static configuration 215-a), a network provider can dedicate an entire component carrier (or another 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. The set of timeslots 225 or timeslots 225 in static configuration 215-a can be constant or can change with time slots.

[0060] In comparison, dynamic configuration 215-b exemplifies an example of dynamic multi-RAT spectrum sharing (MRSS). With 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 carrier 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 carrier 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.

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

[0062] In some cases, wireless communication systems (such as wireless communication system 200) may follow different migration scenarios or paths, utilizing a combination of static reconfiguration (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 reconfigure some of the network's serving cells 205 to provide only 6G service. Therefore, the network may consist of 5G-only cells and 6G-only cells.

[0063] 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 that support only 5G communication, and some cells that support both 5G and 6G communication (e.g., MRSS cells). In other words, some cells in cell site 205 may remain in 5G operation, while others will be dynamically shared with the 6G RAT. In practice, it is unlikely that MRSS will be enabled simultaneously everywhere within the network. Therefore, because the process is gradual, using both static configuration 215-a and dynamic configuration 215-b during the migration process allows some cells 205 within the network to remain 5G cells for a longer duration.

[0064] 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 that only support 6G communication, and some cells that support both 5G and 6G communication (e.g., MRSS cells). In other words, under this specific implementation, some cells 205 can be reconfigured for 6G-only service, while other cells 205 will be dynamically shared between the 5G RAT and the 6G RAT. As more devices within the network become 6G-capable, some MRSS cells in MRSS cells 205 can be phased out of 5G and converted to 6G-only cells (e.g., 5G communication / cells are decommissioned as more devices become 6G-capable).

[0065] Finally, in other specific implementations, the network may include all 5G / 6G MRSS 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, assuming both 5G and 6G have considerable market penetration, more and more cells 205 will support MRSS.

[0066] However, several challenges exist when handling migrations across RATs. First, power consumption and network energy conservation issues can arise when multiple RATs are supported within a network. For example, there may be situations where the second cell 205-b does not actually include any 6G equipment. When the second cell 205-b is not serving a UE, it can be placed in a deep sleep level for power conservation. For example, the second cell 205-b may be idle and not transmit common broadcast (BC) signals. The second cell 205-b can conserve energy by transmitting BC signals when serving a UE instead of periodically transmitting them. In some cases, the first cell 205-a may be active and transmit BC signals. When the second cell 205-b is idle, a UE with second RAT capability (e.g., a UE with 6G capability) may request access to the second cell 205-b. Because the second cell 205-b is in power-saving mode, it may not be usable for directly performing an initial access procedure or RACH procedure with UE 115-a. In some cases, the first cell 205-a can assist UE 115-a in accessing the second cell 205-b. In some examples, the first cell 205-a can exchange signaling with UE 115-a, and the first cell 205-a can send signaling to the second cell 205-b to wake it up. In some examples, the first cell 205-a can decide whether UE 115-a can access the second cell 205-b for load balancing purposes.

[0067] In some examples, when the second cell 205-b is idle and UE 115-a wants to request access to the second cell 205-b, the first cell 205-a may decide to wake up the second cell 205-b. When the second cell 205-b is idle, the second cell 205-b may not send broadcast system information. The first cell 205-a may send a broadcast system information message 230, and UE 115-a may receive the broadcast system information message 230 sent by the first cell 205-a. In some cases, the broadcast system information message 230 sent by the first cell 205-a may include system information for connecting to the first cell 205-a and system information for connecting to the second cell 205-b.

[0068] For example, the broadcast system information message 230 may include a synchronization signal block (SSB) message, a system information block (SIB) message, or any combination thereof. The SSB and SIB may be an SSB and SIB for connecting to a first cell 205-a, with additional information for connecting to a second cell 205-b. In some examples, the SSB and SIB of the first cell 205-a (e.g., 5G) may be extended to deliver additional information for connecting to the second cell 205-b (e.g., 6G), or a new SSB or a new SIB with information for connecting to the second cell 205-b may be added to the broadcast system information message 230. If the SIB for 5G is extended to deliver additional information in a new field for 6G, these new fields may be ignored by UEs with 5G capability. If a new SIB for 6G is included in the broadcast system information message 230, the new SIB for 6G may not be readable by UEs with 5G capability.

[0069] In some cases, additional information added to the SIB or a new SIB of the first cell 205-a may include system information (e.g., 6G system information) for RACH configuration to the second cell 205-b. For example, system information for connecting to the second cell 205-b may include one or more RACH sequences for sending RACH messages, resources associated with RACH timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second cell identifiers, or any combination thereof.

[0070] Subsequently, and using the received system information, UE 115-a may send a RACH preamble message 235 associated with the second cell 205-b to the first cell 205-a. The RACH preamble message 235 may be sent on a carrier or frequency (e.g., a 5G carrier / frequency) associated with the first cell 205-a.

[0071] In some cases, the first cell 205-a may send signaling 240 to the second cell 205-b, at least in part, based on the receipt of the RACH preamble message 235, to forward the RACH preamble message and a wake-up signal 245. The wake-up signal 245, when received by the second cell 205-b, may prompt the second cell 205-b to exit the idle state or deep sleep.

[0072] In some examples, UE 115-a may monitor the Physical Downlink Control Channel (PDCCH) on the frequency (e.g., 5G frequency) of the first cell 205-a. UE 115-a may receive a random access response message 250-a (e.g., msg2 of the RACH procedure) indicating uplink resources for uplink messages (e.g., msg3 of the RACH procedure) based at least in part on the transmission of the RACH preamble message 235. In some cases, the random access response message 250-a may be scheduled to be transmitted on the resources (e.g., 5G frequency / carrier) of the first cell 205-a. UE 115-a may transmit the uplink message 255-a to the first cell 205-a on the uplink resources of the first cell 205-a. In some examples, the random access response message 250-a may be scheduled to be transmitted on the resources (e.g., 6G frequency / carrier) of the second cell 205-b. UE115-a can send uplink message 255-b to the second cell 205-b on the uplink resources of the second cell 205-b.

[0073] In some examples, UE 115-a may monitor the PDCCH on resources (e.g., 6 GHz frequency) of the second cell 205-b after transmitting the RACH preamble message 235. UE 115-a may receive a random access response message 250-b (e.g., msg2) indicating uplink resources for uplink message 255-b, based at least in part on transmitting the RACH preamble message 235. In some cases, the random access response message 250-b may schedule the uplink message 255-b to be transmitted on resources (e.g., 6 GHz frequency / carrier) of the second cell 205-b. UE 115-a may transmit the uplink message 255-b to the second cell 205-b on the uplink resources of the second cell 205-b. In order for UE 115-a to monitor the random access response message 250-b or other messages of the RACH procedure on the resources (e.g., 6G frequency / carrier) of the second cell 205-b, the first cell 205-a may provide CORESET or search space configuration on the resources (e.g., 6G frequency / carrier) of the second cell 205-b via an extended SIB or a new SIB.

[0074] In some cases, UE 115-a may receive downlink messages (e.g., msg4 of the RACH procedure) from first cell 205-a on downlink resources, at least in part, based on sending uplink message 255-a. The downlink resources may be downlink resources of first cell 205-a or downlink resources of second cell 205-b. For example, UE 115-a may receive downlink message 260-a from first cell 205-a on resources of first cell 205-a (e.g., 5G frequency / carrier). In some examples, downlink message 260-a may be used for contention resolution, RRC connection establishment may not be included in downlink message 260-a, and the RRC connection may be transmitted at a later time. In some cases, UE 115-a may receive downlink message 260-b from second cell 205-b on resources of second cell 205-b (e.g., 6G frequency / carrier). In some examples, downlink message 260-b may be used for both contention resolution and RRC connection establishment. Following downlink messages 260-a and 260-b, UE 115-a may be granted access to the second cell 205-b.

[0075] In some examples, after receiving the RACH preamble message 235, the first cell 205-a may decide whether to wake up the second cell 205-b or not. In some cases, the RACH preamble message 235 received by the first cell 205-a may provide an establishment reason as part of an RRC connection request for the second cell 205-b. The first cell 205-a may decide whether to wake up the second cell 205-b by sending signaling 240 to forward the RACH preamble message and wake-up signal 245 based on the establishment reason. The establishment reason (e.g., establishmentCause) may be a field in the RRCSetupRequest information element. The establishment reason field may provide an establishment reason for the RRC setup request based on information received from the upper layer. Enumerated establishment reasons may include emergency, high priority access, MT-access, MO-signaling, MO-data, MO-voice call, MO-video call, MO-SMS, MPS-priority access, or MCS-priority access. In some cases, the establishment reason can be provided in the sequence of RACH preamble message 235 or in the available RACH timing. For example, if the establishment reason indicates an emergency, the first cell 205-a may decide to wake up the second cell 205-b, and if the establishment reason indicates a low-priority item, the first cell 205-a may not wake up the second cell 205-b.

[0076] In another example, the establishment reason may be provided as part of an uplink message 255-a (e.g., msg3). The first cell 205-a may decide whether to wake up the second cell 205-b based on the establishment reason of the uplink message 255-a, and the first cell 205-a may send a wake-up signal 245 and a signaling 240 to forward a RACH preamble message or uplink message (e.g., msg3) to the second cell 205-b in response to receiving the uplink message 255-a with an establishment reason. For an example of an establishment reason as part of uplink message 255-a, UE 115-a requesting access to second cell 205-b (e.g., 6G access) may perform RACH procedure until uplink message 255-a (e.g., msg3) is sent on the resources of first cell 205-a (e.g., a 5G cell using 5G channel / procedure), and UE 115-a may receive downlink message 260-b (e.g., msg4) from second cell 205-b.

[0077] In some examples, the first cell 205-a may decide whether to wake up the second cell 205-b or not after receiving the RACH preamble message 235 or after receiving the uplink message 255-a (e.g., msg3). Downlink messages may be provided on downlink resources based on the wake-up decision. The decision to wake up the second cell 205-b may grant UE 115-a access to the second cell 205-b. The decision not to wake up the second cell 205-b may deny UE 115-a access to the second cell 205-b, and UE 115-a may access the first cell 205-a instead of the second cell 205-b.

[0078] In some cases, UE 115-a may monitor downlink resources (e.g., 5G PDCCH) of the first cell 205-a in response to downlink message 260-a (e.g., msg4). UE 115-a may receive downlink message 260-a on the downlink resources of the first cell 205-a. If access to the second cell 205-b is granted (e.g., 6G access), the downlink message includes an RRC container with RRC information of the second cell 205-b. If access to the second cell 205-b is not granted, UE 115-a may access the first cell 205-a and receive the RRC information of the first cell 205-a as part of the downlink message.

[0079] In some cases, UE 115-a may monitor downlink resources (e.g., 5G PDCCH) of the first cell 205-a in response to downlink message 260-a (e.g., msg4). Indications regarding whether access to the second cell 205-b is permitted (e.g., 6G access) may be provided via physical (PHY) layer signaling. For example, indications regarding access to the second cell 205-b may be provided using different Radio Network Temporary Identifiers (RNTIs), different downlink control information (DCI) formats, different DCI sizes, or indications within the DCI, search space separations, or CORESET separations. For example, UE 115-a may monitor the RNTI or DCI to receive indications of permitted access to the second cell 205-b without receiving or decoding downlink message 260-a (e.g., msg4).

[0080] In some examples, UE 115-a can be configured to monitor downlink resources (e.g., 5G PDCCH) of first cell 205-a and downlink resources (e.g., 6GPDCCH) of second cell 205-b for downlink messages (e.g., msg4). The indication of whether to grant access to second cell 205-b (e.g., 6G access) can be inferred based on the DCI on which the scheduling downlink message (e.g., msg4) is received. If the DCI for the scheduling downlink message is received on the resources of second cell 205-b, access to second cell 205-b (e.g., 6G access) can be granted, and UE 115-a can use MAC-CE or RRC to examine downlink message 260-b on the downlink resources of second cell 205-b. If access to second cell 205-b is granted, UE 115-a can be instructed to fall back to access first cell 205-a in the future. If a DCI scheduling downlink message is received on the resources of the first cell 205-a, access to the second cell 205-b (e.g., 6G access) may be denied, and UE 115-a may examine downlink message 260-a on the downlink resources of the first cell 205-a.

[0081] If the establishment reason is included in the RACH preamble message 235, or when the first cell 205-a may decide to move access to the second cell 205-b for load balancing purposes, the RACH preamble message 235 may be received by UE 115-a from the first cell 205-a. In response to receiving the RACH preamble message 235, UE 115-a may receive a random access response message 250-a from the first cell 205-a on the resources of the first cell 205-a. The random access response message 250-a may indicate the uplink resources of the second cell 205-b for the uplink message 255-b. The permission to receive the uplink message 255-b on the resources of the second cell 205-b may be an indication of permission to access the second cell 205-b, and the downlink message 260-b may be received by UE 115-a on the downlink resources of the second cell 205-b.

[0082] After establishing access to the second cell 205-b, UE 115-a can communicate with the second cell 205-b. If access to the second cell 205-b is not granted, UE 115-a can establish access to the first cell 205-a and communicate with the first cell 205-a.

[0083] Figure 3 Examples of process flow 300 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, are shown. In some examples, process flow 300 may be implemented as described with reference to [references to other documents]. Figure 1 and Figure 2 The described aspects of the wireless communication systems 100 and 200, or those implemented therein. For example, process flow 300 can be implemented by UE 115-b, which can be as described in reference... Figure 1 and Figure 2 An example of the UE described. For instance, process flow 300 may be implemented by a first cell 305-a, which may be as described in the reference. Figure 2 An example of the first cell 205-a described herein. For example, process flow 300 may be implemented by a second cell 405-b, which may be as described in the reference. Figure 2 An example of the first cell 205-a described. In some examples, the first cell 305-a may be associated with a first RAT, and the second cell 305-b may be associated with a second RAT. In some examples, the first RAT may be a 5G RAT or an NR RAT, and the second RAT may be a 6G RAT.

[0084] 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 (e.g., software executed by a processor), 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.

[0085] At 310, UE 115-b can receive broadcast system information messages. In some examples, the first cell 305-a can send broadcast system information messages. The broadcast system information message may include system information for connecting to the second cell 305-b. The broadcast system information message may include SSB messages, SIB messages, or any combination thereof. The system information for connecting to the second cell 305-b may include one or more RACH sequences for sending RACH messages, resources associated with RACH timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

[0086] At 315, UE 115-b may send a RACH preamble message associated with the second cell 305-b to the first cell 305-a, at least in part, based on the receipt of a broadcast system information message. In some examples, the RACH preamble message may indicate the establishment reason associated with UE 115-b's request to connect to the second cell 305-b.

[0087] At 320, the first cell 305-a can send a RACH preamble message and a wake-up signal to the second cell 305-b, at least in part, based on the receipt of the RACH preamble message.

[0088] At 325, UE 115-b may receive a random access response message indicating uplink resources, at least in part, based on the transmission of a RACH preamble message. In some examples, the uplink resources are the uplink resources of the first cell 305-a. In some examples, the uplink resources are the uplink resources of the second cell 305-b. In some cases, the first cell 305-a may send a random access response message indicating uplink resources to UE 115-b in response to receiving the RACH preamble message. In some cases, the second cell 305-b may send a random access response message indicating uplink resources to UE 115-b in response to receiving both the RACH preamble message and a wake-up signal.

[0089] At 330, UE 115-b may send an uplink message on uplink resources in response to receiving a random access response message. In some examples, the uplink resources are the uplink resources of the first cell 305-a. In some examples, the uplink resources are the uplink resources of the second cell 305-b. In some examples, the uplink message may indicate the establishment reason associated with UE 115-b's request to connect to the second cell 305-b. In some examples, the first cell 305-a may send a wake-up signal to the second cell 305-b in response to receiving the uplink message. In some cases, the first cell 305-a may send a RACH preamble message or an uplink message to the second cell 305-b.

[0090] At 335, UE 115-b can receive downlink messages on downlink resources, at least in part, based on sending uplink messages. In some examples, the downlink resources are downlink resources of the first cell 305-a. In some examples, the downlink resources are downlink resources of the second cell 305-b. In some examples, the downlink message includes an RRC container of the first cell 305-a. In some examples, the downlink message includes an RRC container of the second cell 305-b. In some cases, the downlink message is a physical layer message indicating access to the second cell 205-b. In some cases, the downlink message indicates granted access to the second cell 205-b.

[0091] Figure 4 A block diagram 400 illustrates an apparatus 405 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure. Apparatus 405 may be an example of various aspects of UE 115 as described herein. Apparatus 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Apparatus 405, or one or more components of apparatus 405 (e.g., receiver 410, transmitter 415, and communication manager 420), 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).

[0092] Receiver 410 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 technologies for assisted access to a serving cell for wireless communication). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0093] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 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 techniques for assisted access to a serving cell for wireless communication). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0094] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the techniques for assisted access to a serving cell for wireless communication as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0095] In some examples, the communication manager 420, receiver 410, transmitter 415, 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).

[0096] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, 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 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

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

[0098] Communication manager 420 may support wireless communications according to examples disclosed herein. For example, communication manager 420 may be capable of, configured to, or operable to support components for receiving 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, or any combination thereof. Communication manager 420 may be capable of, configured to, or operable to support components for sending a RACH preamble message associated with the second serving cell to the first serving cell based on the receipt of the broadcast system information message. Communication manager 420 may be capable of, configured to, or operable to support components for receiving a random access response message indicating uplink resources from the first serving cell based on the transmission of the RACH preamble message. Communication manager 420 may be capable of, configured to, or operable to support components for sending an uplink message on uplink resources to the first serving cell in response to the receipt of the random access response message.

[0099] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption and utilizing communication resources more efficiently.

[0100] Figure 5 A block diagram 500 of an apparatus 505 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown. Apparatus 505 may be an example of aspects of apparatus 405 or UE 115 as described herein. Apparatus 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Apparatus 505, or one or more components of apparatus 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 support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0101] 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 technologies for assisted access to a serving cell for wireless communication). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0102] 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 techniques for assisted access to a serving cell for 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.

[0103] Device 505 or its various components may be examples of components for performing various aspects of techniques for assisted access to a serving cell for wireless communication as described herein. For example, communication manager 520 may include broadcast system information message manager 525, RACH preamble message manager 530, random access response message manager 535, uplink message manager 540, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use or otherwise cooperate with receiver 510, transmitter 515, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0104] Communication manager 520 can support wireless communication according to the examples disclosed herein. Broadcast system information message manager 525 is capable of, configured to, or operable to support components for receiving broadcast system information messages from a first serving cell, wherein the broadcast system information messages include system information for connecting to a second serving cell, and wherein the broadcast system information messages include synchronization signal block messages, system information block messages, or any combination thereof. RACH preamble message manager 530 is capable of, configured to, or operable to support components for sending a RACH preamble message associated with a second serving cell to the first serving cell based on the receipt of a broadcast system information message. Random access response message manager 535 is capable of, configured to, or operable to support components for receiving a random access response message indicating uplink resources from the first serving cell based on the transmission of a RACH preamble message. Uplink message manager 540 is capable of, configured to, or operable to support components for sending uplink messages on uplink resources to the first serving cell in response to the receipt of a random access response message.

[0105] Figure 6 A block diagram 600 of a communication manager 620 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown. The communication manager 620 may be an example of aspects of the communication manager 420, communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of components for performing various aspects of the techniques for assisted access to a serving cell for wireless communication as described herein. For example, the communication manager 620 may include a broadcast system information message manager 625, a RACH preamble message manager 630, a random access response message manager 635, an uplink message manager 640, a downlink message manager 645, 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).

[0106] Communication manager 620 can support wireless communication according to the examples disclosed herein. Broadcast system information message manager 625 is capable of, configured to, or operable to support components for receiving broadcast system information messages from a first serving cell, wherein the broadcast system information messages include system information for connecting to a second serving cell, and wherein the broadcast system information messages include synchronization signal block messages, system information block messages, or any combination thereof. RACH preamble message manager 630 is capable of, configured to, or operable to support components for sending a RACH preamble message associated with a second serving cell to the first serving cell based on the receipt of a broadcast system information message. Random access response message manager 635 is capable of, configured to, or operable to support components for receiving a random access response message indicating uplink resources from the first serving cell based on the transmission of a RACH preamble message. Uplink message manager 640 is capable of, configured to, or operable to support components for sending uplink messages on uplink resources to the first serving cell in response to the receipt of a random access response message.

[0107] In some examples, the system information used to connect to the second serving cell includes one or more random access channel sequences for sending random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

[0108] In some examples, the uplink resource is the uplink resource of the first serving cell, and the downlink message manager 645 is capable of, configured to, or operable to support components for receiving downlink messages on the downlink resource based on sending uplink messages, wherein the downlink resource is the downlink resource of the first serving cell or the downlink resource of the second serving cell.

[0109] In some examples, the uplink resource is the uplink resource of the second serving cell, and the downlink message manager 645 is capable of, configured to, or operable to support components for receiving downlink messages on the downlink resource based on sending uplink messages, wherein the downlink resource is the downlink resource of the second serving cell.

[0110] In some examples, the RACH preamble message or uplink message indicates the establishment reason associated with the UE's request to connect to the second serving cell.

[0111] In some examples, the downlink message manager 645 is capable of, configured to, or operable to support components for receiving downlink messages on downlink resources based on sending uplink messages, wherein the downlink resources are downlink resources of the first serving cell.

[0112] In some examples, the downlink message includes the RRC container of the second serving cell.

[0113] In some examples, the downlink message includes the RRC container of the first serving cell.

[0114] In some examples, downlink messages are physical layer messages indicating access to a second serving cell.

[0115] In some examples, the RACH preamble message or uplink message indicates the establishment reason associated with the UE's request to connect to the second serving cell, and the downlink message manager 645 is capable of, configured to, or operable to support components for receiving downlink messages on the downlink resources of the second serving cell indicating permission to access the second serving cell based on the receipt of a random access response message.

[0116] In some examples, the RACH preamble message indicates the establishment reason associated with the UE's request to connect to the second serving cell, and the downlink message manager 645 is capable of, configured to, or operable to support components for receiving downlink messages indicating permission to access the second serving cell on downlink resources of the second serving cell based on the receipt of a random access response message.

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

[0118] In some examples, the first serving cell is associated with a first radio access technology. In some examples, the second serving cell is associated with a second radio access technology.

[0119] In some examples, the first radio access technology includes fifth-generation radio access technology, new radio access technology, or both. In some examples, the second radio access technology includes sixth-generation radio access technology.

[0120] Figure 7A diagram of a system 700 including device 705 supporting assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or a component including such devices. Device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 745).

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

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

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

[0124] At least one processor 740 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 740 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 740. At least one processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting techniques for assisted access to a serving cell for wireless communication). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 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 740 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 740) and memory circuitry (which may include at least one memory 730)) 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 740 or a processing system including at least one processor 740 may be configured, configurable, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” 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 730 or otherwise.

[0125] The communication manager 720 can support wireless communications according to examples disclosed herein. For example, the communication manager 720 can be configured or operable to support components for receiving 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, or any combination thereof. The communication manager 720 can be configured or operable to support components for sending a RACH preamble message associated with the second serving cell to the first serving cell based on the receipt of the broadcast system information message. The communication manager 720 can be configured or operable to support components for receiving a random access response message indicating uplink resources from the first serving cell based on the transmission of the RACH preamble message. The communication manager 720 can be configured or operable to support components for sending an uplink message on uplink resources to the first serving cell in response to the receipt of the random access response message.

[0126] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for reducing power consumption, utilizing communication resources more efficiently, and improving coordination between devices.

[0127] In some examples, the communication manager 720 may be configured to use or otherwise coordinate with the transceiver 715, one or more antennas 725, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of the techniques for assisted access to a serving cell for wireless communication as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0128] Figure 8A block diagram 800 illustrates an apparatus 805 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure. Apparatus 805 may be an example of aspects of network entity 105 as described herein. Apparatus 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Apparatus 805, or one or more components of apparatus 805 (e.g., receiver 810, transmitter 815, and communication manager 820), 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).

[0129] Receiver 810 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 805. In some examples, receiver 810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0130] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 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 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 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 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0131] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the techniques for assisted access to a serving cell for wireless communication as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0132] In some examples, the communication manager 820, receiver 810, transmitter 815, 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 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).

[0133] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, 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 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described herein).

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

[0135] The communication manager 820 can support wireless communications according to examples disclosed herein. For example, the communication manager 820 is capable of, configured to, or operable to support components for transmitting broadcast system information messages, wherein the broadcast system information messages include system information for connecting to a second serving cell, wherein the broadcast system information messages include synchronization signal block messages, system information block messages, or any combination thereof. The communication manager 820 is capable of, configured to, or operable to support components for receiving a RACH preamble message associated with a second serving cell from the UE based on transmitting the broadcast system information message. The communication manager 820 is capable of, configured to, or operable to support components for transmitting a random access response message indicating uplink resources to the UE in response to receiving the RACH preamble message.

[0136] Additionally or alternatively, the communication manager 820 may support wireless communications according to the examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving a wake-up signal from a first serving cell instructing a second serving cell to wake from a sleep state. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a RACH preamble message associated with the UE and associated with the wake-up signal from the first serving cell. The communication manager 820 may be capable of, configured to, or operable to support components for communicating with the UE or the first serving cell based on the receipt of the RACH preamble message and the wake-up signal.

[0137] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption and utilizing communication resources more efficiently.

[0138] Figure 9 A block diagram 900 illustrates an apparatus 905 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure. Apparatus 905 may be an example of aspects of apparatus 805 or network entity 105 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Apparatus 905, or one or more components of apparatus 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 support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0139] 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.

[0140] 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.

[0141] Device 905 or its various components may be examples of components for performing various aspects of techniques for assisted access to a serving cell for wireless communication as described herein. For example, communication manager 920 may include broadcast system information message manager 925, RACH preamble message manager 930, random access response message manager 935, wake-up manager 940, access grant manager 945, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0142] Communication Manager 920 can support wireless communication according to the examples disclosed herein. Broadcast System Information Message Manager 925 is capable of, configured to, or operable to support components for transmitting broadcast system information messages, wherein the broadcast system information messages include system information for connecting to a second serving cell, wherein the broadcast system information messages include synchronization signal block messages, system information block messages, or any combination thereof. RACH Preamble Message Manager 930 is capable of, configured to, or operable to support components for receiving a RACH preamble message associated with a second serving cell from the UE based on the transmission of the broadcast system information message. Random Access Response Message Manager 935 is capable of, configured to, or operable to support components for sending a random access response message indicating uplink resources to the UE in response to receiving a RACH preamble message.

[0143] Additionally or alternatively, the communication manager 920 may support wireless communication according to the examples disclosed herein. The wake-up manager 940 is capable of, configured to, or operable to support components for receiving a wake-up signal from a first serving cell instructing a second serving cell to wake from a sleep state. The RACH preamble message manager 930 is capable of, configured to, or operable to support components for receiving a RACH preamble message associated with the UE and associated with the wake-up signal from the first serving cell. The access grant manager 945 is capable of, configured to, or operable to support components for communicating with the UE or the first serving cell based on the receipt of the RACH preamble message and the wake-up signal.

[0144] Figure 10A block diagram 1000 of a communication manager 1020 supporting techniques for assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of the techniques for assisted access to a serving cell for wireless communication as described herein. For example, the communication manager 1020 may include a broadcast system information message manager 1025, a RACH preamble message manager 1030, a random access response message manager 1035, a wake-up manager 1040, an access grant manager 1045, an uplink message manager 1050, a downlink message manager 1055, 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.

[0145] Communication manager 1020 can support wireless communication according to the examples disclosed herein. Broadcast system information message manager 1025 is capable of, configured to, or operable to support components for transmitting broadcast system information messages, wherein the broadcast system information messages include system information for connecting to a second serving cell, wherein the broadcast system information messages include synchronization signal block messages, system information block messages, or any combination thereof. RACH preamble message manager 1030 is capable of, configured to, or operable to support components for receiving a RACH preamble message associated with a second serving cell from the UE based on transmitting a broadcast system information message. Random access response message manager 1035 is capable of, configured to, or operable to support components for sending a random access response message indicating uplink resources to the UE in response to receiving a RACH preamble message.

[0146] In some examples, the system information used to connect to the second serving cell includes one or more random access channel sequences for sending random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

[0147] In some examples, the wake-up manager 1040 is capable of, configured to, or operable to support components for sending RACH preamble messages to a second serving cell and wake-up signals for the second serving cell based on the received RACH preamble message.

[0148] In some examples, the uplink resource is the uplink resource of the first serving cell, and the uplink message manager 1050 is capable of, configured to, or operable to support components for receiving uplink messages on the uplink resource based on sending random access response messages.

[0149] In some examples, the downlink message manager 1055 is capable of, configured to, or operable to support components for sending downlink messages on downlink resources of the first serving cell based on received uplink messages.

[0150] In some examples, the downlink message includes the RRC container of the second serving cell.

[0151] In some examples, the downlink message includes the RRC container of the first serving cell.

[0152] In some examples, the downlink message is a physical layer message indicating access to a second serving cell.

[0153] In some examples, the RACH preamble message indicates the reason for establishing a connection to the second serving cell, or the uplink message indicates the reason for establishing a connection to the second serving cell, and the random access response message indicates the downlink resources of the first serving cell and the downlink resources of the second serving cell.

[0154] In some examples, the RACH preamble message or uplink message indicates the establishment reason associated with the UE's request to connect to the second serving cell, and the wake-up manager 1040 is capable of, configured to, or operable to support components for sending a wake-up signal and RACH preamble message to the second serving cell based on the received establishment reason.

[0155] Additionally or alternatively, the communication manager 1020 may support wireless communications according to examples disclosed herein. The wake-up manager 1040 is capable of, configured to, or operable to support components for receiving a wake-up signal from a first serving cell instructing a second serving cell to wake from a sleep state. In some examples, the RACH preamble message manager 1030 is capable of, configured to, or operable to support components for receiving a RACH preamble message associated with the UE and associated with the wake-up signal from the first serving cell. The access grant manager 1045 is capable of, configured to, or operable to support components for communicating with the UE or the first serving cell based on the receipt of the RACH preamble message and the wake-up signal.

[0156] In some examples, the random access response message manager 1035 is capable of, configured to, or operable to support components for sending a random access response message to the UE indicating uplink resources of a second serving cell based on the receipt of a RACH preamble message.

[0157] In some examples, the uplink message manager 1050 is capable of, configured to, or operable to support components for receiving uplink messages from the UE on uplink resources of the second serving cell.

[0158] In some examples, the downlink message manager 1055 is capable of, configured to, or operable to support components for sending downlink messages to the UE on downlink resources of the second serving cell.

[0159] Figure 11 A diagram of a system 1100 including a device 1105 supporting assisted access to a serving cell for wireless communication, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and acquisition of communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically via one or more buses (e.g., bus 1140) or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

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

[0161] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by one or more processors of at least one processor 1135, cause device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by a processor of at least one processor 1135, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, at least one memory 1125 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 1135 may include multiple processors, and at least one memory 1125 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).

[0162] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 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 processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks supporting techniques for assisted access to a serving cell for wireless communication). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 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 host functions for performing the functions of device 1105 (e.g., by executing code 1130). At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 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 1135 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 1135) and memory circuitry (which may include at least one memory 1125)) 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 1135 or a processing system including at least one processor 1135 may be configured, configurable, or operable to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configurable to,” “configurable to,” 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 1125 or otherwise.

[0163] In some examples, bus 1140 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 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 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

[0164] In some examples, the communication manager 1120 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 1120 may manage the delivery of data communications by client devices such as one or more UEs 115. In some examples, the communication manager 1120 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 1120 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0165] Communication manager 1120 may support wireless communications according to examples disclosed herein. For example, communication manager 1120 may be capable of, configured to, or operable to support components for transmitting broadcast system information messages, wherein the broadcast system information messages include system information for connecting to a second serving cell, wherein the broadcast system information messages include synchronization signal block messages, system information block messages, or any combination thereof. Communication manager 1120 may be capable of, configured to, or operable to support components for receiving a RACH preamble message associated with a second serving cell from a UE based on transmitting the broadcast system information message. Communication manager 1120 may be capable of, configured to, or operable to support components for transmitting a random access response message indicating uplink resources to a UE in response to receiving a RACH preamble message.

[0166] Additionally or alternatively, the communication manager 1120 may support wireless communications according to the examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving a wake-up signal from a first serving cell instructing a second serving cell to wake from a sleep state. The communication manager 1120 may be capable of, configured to, or operable to support components for receiving a RACH preamble message associated with the UE and associated with the wake-up signal from the first serving cell. The communication manager 1120 may be capable of, configured to, or operable to support components for communicating with the UE or the first serving cell based on the receipt of the RACH preamble message and the wake-up signal.

[0167] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for reducing power consumption, utilizing communication resources more efficiently, and improving coordination between devices.

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

[0169] Figure 12 A flowchart illustrating a method 1200 for assisted access to a serving cell for wireless communication, according to various aspects of this disclosure, is shown. Operation of method 1200 can be implemented by a UE or its components as described herein. For example, operation of method 1200 can be implemented by, as referenced... Figures 1 to 7The 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.

[0170] At 1205, the method may include: receiving 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, or any combination thereof. The operation of block 1205 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1205 may be as described in references... Figure 6 The broadcast system information message manager 625 described herein is used for execution.

[0171] At 1210, the method may include: sending a RACH preamble message associated with the second serving cell to the first serving cell based on the received broadcast system information message. The operation of block 1210 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1210 may be derived from, as referenced... Figure 6 The RACH preamble message manager 630 described is used for execution.

[0172] At 1215, the method may include: receiving a random access response message indicating uplink resources from a first serving cell based on sending a RACH preamble message. The operation of block 1215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1215 may be derived from, as referenced... Figure 6 The random access response message manager 635 described is used for execution.

[0173] At 1220, the method may include: sending an uplink message to the first serving cell on uplink resources in response to receiving a random access response message. The operation of block 1220 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1220 may be as described in the references... Figure 6 The uplink message manager 640 described is used for execution.

[0174] Figure 13 A flowchart illustrating a method 1300 for assisted access to a serving cell for wireless communication, according to various aspects of this disclosure, is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be implemented by, as referenced... Figures 1 to 7The 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.

[0175] At 1305, the method may include: receiving 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, 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 6 The broadcast system information message manager 625 described herein is used for execution.

[0176] At 1310, the method may include: sending a RACH preamble message associated with the second serving cell to the first serving cell based on the received broadcast system information 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 derived from, as referenced... Figure 6 The RACH preamble message manager 630 described is used for execution.

[0177] At 1315, the method may include: receiving a random access response message indicating uplink resources from a first serving cell based on sending a RACH preamble 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 6 The random access response message manager 635 described is used for execution.

[0178] At 1320, the method may include: sending an uplink message to the first serving cell on uplink resources in response to receiving a random access response message. 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 as described in the references... Figure 6 The uplink message manager 640 described is used for execution.

[0179] At 1325, the method may include: receiving a downlink message on a downlink resource based on sending an uplink message. The operation of block 1325 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1325 may be derived from references... Figure 6 The downlink message manager 645 described is used for execution.

[0180] Figure 14A flowchart illustrating a method 1400 for assisted access to a serving cell for wireless communication, according to various aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a network entity or component thereof as described herein (e.g., a network entity or component thereof associated with a first serving cell, such as a 5G serving cell). For example, operation of method 1400 may be implemented by, as described in reference... Figures 1 to 3 as well as Figures 8 to 11 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.

[0181] At 1405, the method may include: transmitting a broadcast system information message, wherein the broadcast system information message includes system information for connecting to the second serving cell, wherein the broadcast system information message includes a synchronization signal block message, a system information block 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 10 The broadcast system information message manager 1025 is used to perform this function.

[0182] At 1410, the method may include: receiving a RACH preamble message associated with a second serving cell from the UE based on transmitting a broadcast system information message. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be derived from references... Figure 10 The RACH preamble message manager 1030 described is used for execution.

[0183] At 1415, the method may include: sending a random access response message indicating uplink resources to the UE in response to receiving a RACH preamble message. 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 as described in references... Figure 10 The random access response message manager 1035 described herein is used for execution.

[0184] Figure 15 A flowchart illustrating a method 1500 for assisted access to a serving cell for wireless communication, according to various aspects of this disclosure, is shown. Operation of method 1500 may be implemented by a network entity or component thereof as described herein (e.g., a network entity or component thereof associated with a second serving cell, such as a 6G serving cell). For example, operation of method 1500 may be implemented by, as described in reference... Figures 1 to 3 as well as Figures 8 to 11The 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.

[0185] At 1505, the method may include: receiving a wake-up signal from a first serving cell instructing a second serving cell to wake up from a sleep state. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be as described in references... Figure 10 The wake-up manager 1040 described is used to perform this.

[0186] At 1510, the method may include: receiving a RACH preamble message associated with the UE and associated with a wake-up signal from a first serving cell. 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 10 The RACH preamble message manager 1030 described is used for execution.

[0187] At 1515, the method may include: communicating with the UE or a first serving cell based on receiving a RACH preamble message and a wake-up signal. 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 references... Figure 10 The access grant manager 1045 described herein shall be executed.

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

[0189] Aspect 1: A method for wireless communication by a UE, the method comprising: receiving 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, or any combination thereof; transmitting a RACH preamble message associated with the second serving cell to the first serving cell based at least in part on receiving the broadcast system information message; receiving a random access response message indicating uplink resources based at least in part on transmitting the RACH preamble message; and transmitting an uplink message on the uplink resources in response to receiving the random access response message.

[0190] Aspect 2: According to the method of aspect 1, wherein the system information for connecting to the second serving cell includes one or more random access channel sequences for sending random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

[0191] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the uplink resource is the uplink resource of the first serving cell, the method further comprising: receiving a downlink message on a downlink resource at least in part based on sending the uplink message, wherein the downlink resource is the downlink resource of the first serving cell or the downlink resource of the second serving cell.

[0192] Aspect 4: The method according to any one of Aspects 1 to 2, wherein the uplink resource is the uplink resource of the second serving cell, the method further comprising: receiving a downlink message on a downlink resource at least in part based on sending the uplink message, wherein the downlink resource is the downlink resource of the second serving cell.

[0193] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the RACH preamble message or the uplink message indicates the establishment reason associated with the UE requesting to connect to the second serving cell.

[0194] Aspect 6: According to the method of aspect 5, the method further includes: receiving downlink messages on downlink resources at least in part based on sending the uplink messages, wherein the downlink resources are downlink resources of the first serving cell.

[0195] Aspect 7: According to the method of aspect 6, the downlink message includes the RRC container of the second serving cell.

[0196] Aspect 8: The method according to any one of Aspect 6, wherein the downlink message includes the RRC container of the first serving cell.

[0197] Aspect 9: The method according to any one of Aspect 6, wherein the downlink message is a physical layer message indicating access to the second serving cell.

[0198] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the RACH preamble message or the uplink message indicates an establishment reason associated with the UE requesting to connect to the second serving cell, and wherein the random access response message indicates downlink resources of the first serving cell and downlink resources of the second serving cell, the method further comprising: receiving, at least in part, a downlink message on the downlink resources of the second serving cell indicating permission to access the second serving cell based on receiving the random access response message.

[0199] Aspect 11: The method according to any one of Aspects 1 to 9, wherein the RACH preamble message indicates an establishment reason associated with the UE requesting to connect to the second serving cell, and wherein the random access response message indicates downlink resources of the first serving cell or downlink resources of the second serving cell, the method further comprising: receiving, at least in part, a downlink message indicating granted access to the second serving cell on the downlink resources of the second serving cell based on receiving the random access response message.

[0200] 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.

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

[0202] Aspect 14: According to the method of aspect 13, wherein the first radio access technology includes fifth-generation radio access technology, new radio access technology or both, and the second radio access technology includes sixth-generation radio access technology.

[0203] Aspect 15: A method for wireless communication by a first serving cell, the method comprising: transmitting a broadcast system information message, wherein the broadcast system information message includes system information for connecting to a second serving cell, wherein the broadcast system information message includes a synchronization signal block message, a system information block message, or any combination thereof; receiving, at least in part, a RACH preamble message associated with the second serving cell from a UE based on transmitting the broadcast system information message; and transmitting a random access response message indicating uplink resources to the UE in response to receiving the RACH preamble message.

[0204] Aspect 16: According to the method of aspect 15, the system information for connecting to the second serving cell includes one or more random access channel sequences for sending random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

[0205] Aspect 17: The method according to any one of Aspects 15 to 16, the method further comprising: sending the RACH preamble message and a wake-up signal for the second serving cell to the second serving cell based at least in part on receiving the RACH preamble message.

[0206] Aspect 18: The method according to any one of Aspects 15 to 17, wherein the uplink resource is the uplink resource of the first serving cell, the method further comprising: receiving uplink messages on the uplink resource at least in part based on sending the random access response message.

[0207] Aspect 19: The method according to aspect 18, the method further comprising: sending a downlink message on the downlink resources of the first serving cell, at least in part based on receiving the uplink message.

[0208] Aspect 20: The method according to aspect 19, wherein the downlink message includes the RRC container of the second serving cell.

[0209] Aspect 21: The method according to any one of Aspects 19 to 20, wherein the downlink message includes the RRC container of the first serving cell.

[0210] Aspect 22: The method according to any one of Aspects 19 to 21, wherein the downlink message is a physical layer message indicating access to the second serving cell.

[0211] Aspect 23: The method according to aspect 22, wherein the RACH preamble message indicates the reason for establishing a connection to the second serving cell, or the uplink message indicates the reason for establishing a connection to the second serving cell, and the random access response message indicates the downlink resources of the first serving cell and the downlink resources of the second serving cell.

[0212] Aspect 24: The method according to any one of Aspects 18 to 23, wherein the RACH preamble message or the uplink message indicates an establishment reason associated with the UE requesting to connect to the second serving cell, the method further comprising: sending a wake-up signal and the RACH preamble message to the second serving cell at least in part based on receiving the establishment reason.

[0213] Aspect 25: A method for wireless communication by a second serving cell, the method comprising: receiving from a first serving cell a wake-up signal instructing the second serving cell to wake from a sleep state; and receiving from the first serving cell a RACH preamble message associated with a UE and associated with the wake-up signal; and communicating with the UE or the first serving cell at least in part based on receiving the RACH preamble message and the wake-up signal.

[0214] Aspect 26: The method according to aspect 25, wherein communicating with the UE or the first serving cell further comprises: sending a random access response message to the UE, at least in part based on receiving the RACH preamble message, indicating uplink resources of the second serving cell.

[0215] Aspect 27: The method according to any one of Aspects 25 to 26, wherein communicating with the UE or the first serving cell further comprises: receiving an uplink message from the UE on uplink resources of the second serving cell.

[0216] Aspect 28: The method according to any one of Aspects 25 to 27, wherein communicating with the UE or the first serving cell further comprises: sending a downlink message to the UE on downlink resources of the second serving cell.

[0217] Aspect 29: A UE for wireless communication, the 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.

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

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

[0220] 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 a method according to any one of Aspects 15 to 24 via the first serving cell.

[0221] 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.

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

[0223] 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 a method according to any one of Aspects 25 to 28 via the second serving cell.

[0224] 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.

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

[0226] 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.

[0227] 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 outside of 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.

[0228] 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.

[0229] 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 unit, 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 can be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

[0231] 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.

[0232] 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".

[0233] 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".

[0234] 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.

[0235] 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.

[0236] 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.

[0237] 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, or any combination thereof; At least in part, based on receiving the broadcast system information message, a RACH preamble message associated with the second serving cell is sent to the first serving cell; Receiving a random access response message indicating uplink resources is based at least in part on sending the RACH preamble message; as well as In response to receiving the random access response message, an uplink message is sent on the uplink resource.

2. 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 random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

3. The UE of claim 1, wherein the uplink resource is the uplink resource of the first serving cell, and wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receiving downlink messages on downlink resources is based at least in part on sending the uplink messages, wherein the downlink resources are downlink resources of the first serving cell or downlink resources of the second serving cell.

4. The UE of claim 1, wherein the uplink resource is the uplink resource of the second serving cell, and wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receiving downlink messages on downlink resources is based at least in part on sending the uplink messages, wherein the downlink resources are the downlink resources of the second serving cell.

5. The UE of claim 1, wherein the RACH preamble message or the uplink message indicates an establishment reason associated with the UE's request to connect to the second serving cell.

6. The UE of claim 5, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receiving downlink messages on downlink resources is based at least in part on sending the uplink messages, wherein the downlink resources are the downlink resources of the first serving cell.

7. The UE according to claim 6, wherein the downlink message includes the RRC container of the second serving cell.

8. The UE according to claim 6, wherein the downlink message includes the RRC container of the first serving cell.

9. The UE according to claim 6, wherein the downlink message is a physical layer message indicating access to the second serving cell.

10. The UE of claim 1, wherein the RACH preamble message or the uplink message indicates an establishment reason associated with the UE requesting to connect to the second serving cell, and wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: At least in part, based on receiving the random access response message, a downlink message indicating permission to access the second serving cell is received on the downlink resources of the second serving cell.

11. The UE of claim 1, wherein the RACH preamble message indicates an establishment reason associated with the UE requesting to connect to the second serving cell, and wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: At least in part, based on receiving the random access response message, a downlink message indicating permission to access the second serving cell is received on the downlink resources of the second serving cell.

12. 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.

13. The UE of claim 12, 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.

14. 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, wherein the broadcast system information message includes system information for connecting to the second serving cell, wherein the broadcast system information message includes a synchronization signal block message, a system information block message, or any combination thereof; The RACH preamble message associated with the second serving cell is received from the user equipment (UE) at least in part based on the transmission of the broadcast system information message; as well as In response to receiving the RACH preamble message, a random access response message indicating uplink resources is sent to the UE.

15. The network entity of claim 14, wherein the system information for connecting to the second serving cell includes one or more random access channel sequences for sending random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

16. The network entity of claim 14, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to transit via the first serving cell: The RACH preamble message and the wake-up signal for the second serving cell are sent to the second serving cell based at least in part on the receipt of the RACH preamble message.

17. The network entity of claim 14, wherein the uplink resource is the uplink resource of the first serving cell, and wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to travel via the first serving cell: Receiving uplink messages on the uplink resources is based at least in part on sending the random access response message.

18. The network entity of claim 17, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to transit the first serving cell: The downlink message is sent on the downlink resources of the first serving cell, at least in part based on the receipt of the uplink message.

19. The network entity of claim 18, wherein the downlink message includes the RRC container of the second serving cell.

20. The network entity of claim 18, wherein the downlink message includes the RRC container of the first serving cell.

21. The network entity of claim 18, wherein the downlink message is a physical layer message indicating access to the second serving cell.

22. The network entity according to claim 21, wherein: The RACH preamble message indicates the reason for establishing a connection to the second serving cell; or The uplink message indicates the reason for establishing a connection to the second serving cell, and the random access response message indicates the downlink resources of the first serving cell and the downlink resources of the second serving cell.

23. The network entity of claim 17, wherein the RACH preamble message or the uplink message indicates an establishment reason associated with the UE requesting to connect to the second serving cell, and wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to connect via the first serving cell: The wake-up signal and the RACH preamble message are sent to the second serving cell, at least in part, based on the receipt of the establishment reason.

24. 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 instructing the second serving cell to wake up from sleep; Receive a RACH preamble message associated with the user equipment (UE) and the wake-up signal from the first serving cell; as well as The communication with the UE or the first serving cell is based at least in part on receiving the RACH preamble message and the wake-up signal.

25. The network entity of claim 24, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to transit via the second serving cell: At least in part, a random access response message indicative of uplink resources of the second serving cell is sent to the UE based on the receipt of the RACH preamble message.

26. The network entity of claim 24, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to transit via the second serving cell: The UE receives uplink messages on the uplink resources of the second serving cell.

27. The network entity of claim 24, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to transit via the second serving cell: Send downlink messages to the UE on the downlink resources of the second serving cell.

28. A method for wireless communication by 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, or any combination thereof; At least in part, based on receiving the broadcast system information message, a RACH preamble message associated with the second serving cell is sent to the first serving cell; Receiving a random access response message indicating uplink resources is based at least in part on sending the RACH preamble message; as well as In response to receiving the random access response message, an uplink message is sent on the uplink resource.

29. The method of claim 28, wherein the system information for connecting to the second serving cell includes one or more random access channel sequences for sending random access channel messages, resources associated with random access channel timings, one or more random access response search space configurations, the number of resource timings in the frequency, one or more second serving cell identifiers, or any combination thereof.

30. The method of claim 28, wherein the uplink resource is the uplink resource of the first serving cell, the method further comprising: Receiving downlink messages on downlink resources is based at least in part on sending the uplink messages, wherein the downlink resources are downlink resources of the first serving cell or downlink resources of the second serving cell.

Images