Initial access with downlink carrier sharing

Abstract

Various aspects of this disclosure relate generally to wireless communications. In some aspects, a user equipment (UE) can receive at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of synchronization signal blocks (SSBs) for a set of cells in the cell group. The UE can send an initial access message for a cell in the cell group based on the SSBs in the set of SSBs. Numerous other aspects are described.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 585,281, filed February 23, 2024, entitled “Initial Access with Downlink Carrier Sharing,” which has been assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for initial access with downlink carrier sharing. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0005] Some aspects described herein relate to a method for wireless communication performed by a user equipment (UE). The method may include: receiving at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of synchronization signal blocks (SSBs) for a set of cells in the cell group. The method may also include: for a cell in the cell group, transmitting an initial access message based on the SSBs in the set of SSBs.

[0006] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include: transmitting at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. The method may also include: receiving an initial access message for a cell in the cell group based on the SSBs in that set.

[0007] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions causes the UE to: receive at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. When executed by one or more processors of the UE, the set of instructions causes the UE to: transmit an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0008] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to: transmit at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. When executed by one or more processors of the network node, the set of instructions also enables the network node to: receive an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to: receive at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. The one or more processors may be configured to cause the UE to: transmit an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network node to: transmit at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. The one or more processors may be configured to: receive an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. The apparatus may also include components for transmitting an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. The apparatus may also include components for receiving an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0013] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0014] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0015] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0016] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0017] Figure 2 This is a diagram illustrating communication between an example network node and an example user equipment (UE) in a wireless network according to the present disclosure.

[0018] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0019] Figure 4 This is a diagram illustrating an example of carrier aggregation according to this disclosure.

[0020] Figure 5 This is a diagram illustrating an example of a synchronization signal (SS) hierarchy according to this disclosure.

[0021] Figure 6 This is a diagram illustrating an example of a carrier configuration according to this disclosure.

[0022] Figures 7A to 7C This is a diagram illustrating an example of initial access associated with downlink carrier sharing according to this disclosure.

[0023] Figure 8 This is a diagram illustrating an example process performed, for example, at the UE or at a device of the UE, according to this disclosure.

[0024] Figure 9 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0025] Figure 10 This is a diagram of an example device for wireless communication according to the present disclosure.

[0026] Figure 11 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0027] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0029] In some communication systems, network nodes (or sets of network nodes) can provide multiple overlapping coverage areas to offer network services to user equipment (UEs). For example, a UE may operate in a location associated with a set of uplink-only cells and bidirectional cells (e.g., cells that support both uplink and downlink communication). In this and other examples, a UE may access multiple uplink carriers on multiple uplink cells and multiple downlink carriers on a single bidirectional cell. When multiple downlink carriers are associated with a common set of resources, the multiple downlink carriers may completely overlap. Each cell may broadcast a set of transmissions, such as a Master Information Block (MIB) or System Information Block (SIB) associated with a Synchronization Signal Block (SSB). However, when downlink carriers are shared by multiple cells, the UE may lack information indicating which cell to select for initial access and / or may lack signaling for (e.g., in a group of cells that may already include connected UEs) to perform random access.

[0030] The various aspects generally relate to access communication in multi-cell scenarios with downlink carrier sharing. Some aspects more specifically relate to SSB transmission and selection in communication systems with multiple overlapping downlink cells. For example, a UE may receive a set of SSBs from a single cell, and the set of SSBs may include a MIB and a scheduling SIB with per-cell configurations for multiple cells. Additionally or alternatively, a UE may receive a set of SSBs multiplexed together on a common set of resources from multiple cells, and each SSB may include a corresponding MIB and a corresponding SIB for the corresponding cell. In this case, the UE may receive the set of SSBs, select a cell based on the set of SSBs, and perform access procedures, such as initial access or random access procedures, in the selected cell.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by receiving a set of SSBs from a single cell, a single SIB can provide the UE with information about a group of cells, thereby enabling cell selection from a single SIB. In some examples, by configuring the UE to receive a set of SSBs from multiple cells, network nodes can use silence or punching in one or more time slots to transmit the set of SSBs without modifying the MIB or SIB payload.

[0032] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0033] As the demand for broadband access increases and as the technologies supported by wireless communication networks evolve, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0034] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0035] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless communication networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0036] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0037] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0038] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0039] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations conforming to O-RAN Alliance standards), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0040] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0041] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0042] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell can be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0043] In some contexts (e.g., carrier aggregation scenarios and / or multi-connectivity scenarios), the terms "cell" or "serving cell" may refer to or correspond to a specific carrier frequency (e.g., component carrier) used for wireless communication, and "cell group" may refer to or correspond to multiple carriers used for wireless communication. As an example, in a carrier aggregation scenario, a UE may communicate on multiple component carriers corresponding to multiple (serving) cells within the same cell group, and in a multi-connectivity scenario (e.g., dual-connectivity), a UE may communicate on multiple component carriers corresponding to multiple cell groups.

[0044] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Various types of network nodes 110 can typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100 compared to other types of network nodes 110. For example, macro network nodes can have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0045] In some examples, network node 110 may be, may include, or may operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. "Downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0046] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UE 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0047] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0048] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0049] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, or may be included in the following: access terminal, another terminal, mobile station, or subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0050] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0051] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may include, or may be included in, a housing that accommodates components associated with UE 120, including the processing system.

[0052] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0053] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR-Lite UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0054] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communication through a network node 110 acting as an intermediary). As an example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0055] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0056] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0057] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group; and send an initial access message for a cell in the cell group based on the SSBs in the set of SSBs. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may: transmit at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group; and receive an initial access message for a cell in the cell group based on the SSBs in the set of SSBs. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0059] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0060] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0061] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0062] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “processor,” “controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0063] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be from the same set of processors or can be from different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0064] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0065] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the downlink signal set (e.g., ...) together via the corresponding set of antennas 234. T (One downlink signal).

[0066] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0067] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 (e.g., receive (Rx) MIMO processor) where applicable, and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0068] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0069] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting between analog signals (such as those used for transmission or reception via an air interface) and digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0070] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0071] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0072] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and provide the decoded control information and system information to controller / processor 280.

[0073] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0074] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0075] Modems 254a to 254u can transmit uplink signal sets (e.g., via corresponding sets of antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0076] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0077] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit the cross-polarized signal. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0078] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0079] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0080] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0081] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110), may include, or may be included in one or more network nodes. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0082] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0083] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0084] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0085] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0086] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may perform corrective actions using AI / ML models via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0087] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0088] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with initial access with downlink carrier sharing, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with initial access with downlink carrier sharing, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 8 The process 800 Figure 9The operation of process 900 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 8 The process 800 Figure 9 The process 900 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0089] In some aspects, UE 120 includes components for: receiving at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group; and / or components for: sending an initial access message for a cell in the cell group based on the SSBs in the set of SSBs. Components for UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0090] In some aspects, network node 110 includes components for: transmitting at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group; and / or components for: receiving an initial access message for a cell in the cell group based on the SSBs in the set of SSBs. Components for network node 110 to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0091] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0092] Figure 4 This is a diagram illustrating example 400 of carrier aggregation according to this disclosure.

[0093] Carrier aggregation (CA) is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. As shown, carriers can be combined in the same or different frequency bands. Additionally or alternatively, contiguous or discontinuous carriers can be combined. Network node 110 can configure carrier aggregation for UE 120, such as in RRC messages, DCI messages, and / or other signaling messages.

[0094] As shown by reference numeral 405, in some examples, carrier aggregation can be configured as an intra-band continuous mode, in which the aggregated carriers are continuous with each other and in the same frequency band. As shown by reference numeral 410, in some examples, carrier aggregation can be configured as an intra-band discontinuous mode, in which the aggregated carriers are discontinuous with each other and in the same frequency band. As shown by reference numeral 415, in some examples, carrier aggregation can be configured as an inter-band discontinuous mode, in which the aggregated carriers are discontinuous with each other and in different frequency bands.

[0095] In carrier aggregation, UE 120 can be configured using a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some examples, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers; this scheduling may be referred to as cross-carrier scheduling. In some examples, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on that carrier; this scheduling may be referred to as self-carrier scheduling or carrier self-scheduling.

[0096] Similar to carrier aggregation, Supplemental Uplink (SUL) is a technique where a UE can be scheduled to transmit on either a first (non-supplemental) uplink or a second (supplemental) uplink, but not simultaneously on both. Supplemental uplink can be provided to extend uplink coverage. In enhanced supplemental uplink (eSUL) or enhanced uplink carrier aggregation (eUL-CA), some features of carrier aggregation and supplemental uplink can be provided together to further enhance UE operation (e.g., by enhancing data capacity and / or uplink coverage). For example, in eSUL, the UE can be configured using a set of bidirectional cells (e.g., for downlink and uplink coverage) and unidirectional cells (e.g., for extended uplink coverage).

[0097] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0098] Figure 5 This is a diagram illustrating example 500 of the synchronization signal (SS) hierarchy according to this disclosure. Figure 5 As shown, the SS hierarchy may include an SS burst set 505, which may include multiple SS bursts 510, shown as SS burst 0 to SS burst N-1, where N is the maximum number of repetitions of the SS burst 510 that can be transmitted by one or more network nodes. As further shown, each SS burst 510 may include one or more SSBs 515, shown as SSB 0 to SSB M-1, where M is the maximum number of SSBs 515 that can be carried by the SS burst 510. In some examples, different SSBs 515 may be beamformed in different ways (e.g., transmitted using different beams) and may be used for cell search, cell acquisition, beam management and / or beam selection (e.g., as part of the initial network access procedure). The SS burst set 505 may be transmitted periodically (e.g., every X milliseconds) by a radio node (e.g., network node 110). Figure 5As shown. In some examples, the SS burst set 505 may have a fixed or dynamic length (its length is...). Figure 5 (This is represented as Y milliseconds). In some cases, SS burst set 505 or SS burst 510 may be referred to as the Discovery Reference Signal (DRS) transmission window or the SSB Measurement Time Configuration (SMTC) window.

[0099] In some examples, SSB 515 may include resources carrying PSS 520, SSS 525, and / or Physical Broadcast Channel (PBCH) 530. In some examples, multiple SSBs 515 are included in SS burst 510 (e.g., using transmissions on different beams), and PSS 520, SSS 525, and / or PBCH 530 may be identical for each SSB 515 across SS burst 510. In some examples, a single SSB 515 may be included in SS burst 510. In some examples, the length of SSB 515 may be at least four symbols (e.g., OFDM symbols), where each symbol carries one or more of the following: PSS 520 (e.g., occupying one symbol), SSS 525 (e.g., occupying one symbol), and / or PBCH 530 (e.g., occupying two symbols). In some examples, SSB 515 may be referred to as an SS / PBCH block.

[0100] In some examples, the symbols for SSB 515 are consecutive, such as... Figure 5 As shown. In some examples, the symbols of SSB 515 are discontinuous. Similarly, in some examples, one or more SSBs 515 of SS burst 510 may be transmitted in continuous radio resources (e.g., continuous symbols) during one or more time slots. Additionally or alternatively, one or more SSBs 515 of SS burst 510 may be transmitted in discontinuous radio resources.

[0101] In some examples, SS burst 510 may have a burst period, and the SSB 515 of SS burst 510 may be transmitted by a wireless node (e.g., network node 110) according to the burst period. In this case, SSB 515 may repeat during each SS burst 510. In some examples, SS burst set 505 may have a burst set periodicity, whereby the wireless node transmits SS burst 510 in SS burst set 505 according to a fixed burst set periodicity. In other words, SS burst 510 may repeat during each SS burst set 505.

[0102] In some examples, SSB 515 may include an SSB index that corresponds to a beam used to carry SSB 515. UE 120 may use different receive (Rx) beams to monitor and / or measure SSB 515 during initial network access procedures and / or cell search procedures, etc. Based at least in part on monitoring and / or measurement, UE 120 may (e.g., directly or via one or more other network nodes) indicate to network node 110 one or more SSBs 515 with optimal signal parameters (e.g., RSRP parameters). Network node 110 and UE 120 may use the indicated one or more SSBs 515 to select one or more beams to be used for communication between network node 110 and UE 120 (e.g., for a random access channel (RACH) procedure). Additionally or alternatively, UE 120 may use SSB 515 and / or the SSB index to determine cell timing for the cell (e.g., serving cell) through which it receives SSB 515.

[0103] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0104] Figure 6 This is a diagram illustrating an example 600 / 600' of a carrier configuration according to this disclosure.

[0105] like Figure 6 As shown, in Example 600 (e.g., a non-eSUL example), the set of cells can be configured as downlink and uplink cells. For example, the UE can obtain coverage from a first cell 605 (cell 1), a second cell 610 (cell 2), or a third cell 615 (cell 3), and each cell can provide both downlink and uplink carriers. Network nodes can broadcast MIBs and / or System Information Block Type 1 (SIB1) for each cell. For example, a network node can send a first MIB and SIB1 for the first cell 605 (e.g., on a first downlink carrier), a second MIB and SIB1 for the second cell 610 (e.g., on a second downlink carrier), and a third MIB and SIB1 for the third cell 615 (e.g., on a third carrier).

[0106] In Example 600' (e.g., the eSUL example), cells may share a common downlink carrier. For example, a first cell 605' (cell 1), a second cell 610' (cell 2), and a third cell 615' (cell 3) may each provide their respective uplink carriers but may share a single downlink carrier. As shown, the single downlink carrier is divided into three shared portions for cells 1 through 3. In this case, the UE can receive downlink control information or downlink data from the same carrier shared across cells and scheduled to transmit on any available uplink carrier. However, when network nodes are configured to broadcast control information (such as SSB, MIB, or SIB1) for access procedures (e.g., initial access or random access) on each downlink carrier in each cell, network nodes may experience communication conflicts when multiple cells share a single downlink carrier. Furthermore, when a UE is tuned to a single downlink carrier to receive broadcast control information, the UE may lack information for selecting an uplink cell to send an initial access message or for performing random access on a cell group in which UEs may already have connections.

[0107] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0108] The various aspects generally relate to access communication in multi-cell scenarios with downlink carrier sharing. Some aspects more specifically relate to SSB transmission and selection in communication systems with multiple overlapping downlink cells. For example, a UE may receive a set of SSBs from a single cell, and the set of SSBs may include a MIB and a scheduling SIB with per-cell configurations for multiple cells. Additionally or alternatively, a UE may receive a set of SSBs multiplexed together on a common set of resources from multiple cells, and each SSB may include a corresponding MIB and a corresponding SIB for the corresponding cell. In this case, the UE may receive the set of SSBs, select a cell based on the set of SSBs, and perform access procedures, such as initial access or random access procedures, in the selected cell.

[0109] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by receiving a set of SSBs from a single cell, a single SIB can provide the UE with information about a group of cells, thereby enabling cell selection from a single SIB. In some examples, by configuring the UE to receive a set of SSBs from multiple cells, network nodes can use silence or punching in one or more time slots to transmit the set of SSBs without modifying the MIB or SIB payload.

[0110] Figures 7A to 7C This is a diagram illustrating example 700 associated with initial access having downlink carrier sharing according to this disclosure. Figure 7A As shown, Example 700 includes communication between network node 110 and UE 120.

[0111] like Figure 7A Furthermore, as shown by reference numerals 710 and 720, UE 120 can receive at least one downlink communication that delivers a set of SSBs for a set of cells in a cell group, and UE 120 can select a cell to connect to based on the set of SSBs. For example, when UE 120 operates in a network comprising multiple cells sharing a single downlink carrier (e.g., as shown in Example 600', as described above), network node 110 can broadcast multiple SSBs from a single cell. In this case, the multiple SSBs may include MIB communication with per-cell configuration and a single scheduling SIB1 communication. Additionally or alternatively, network node 110 may use multiplexing techniques to broadcast multiple SSBs from multiple cells. In this case, each of the multiple SSBs may include a corresponding MIB communication and scheduling SIB1 communication for each cell.

[0112] In some aspects, the SIB1 included in the SSB may include one or more serving cell configuration common information elements. For example, when network node 110 is configured to transmit the SSB via a single cell, network node 110 may transmit the SSB via a single SIB1. ServingCellConfigCommonSIB The information element includes per-cell information to identify configuration information used for multiple cells. Additionally or alternatively, network node 110 may include this information in a single SIB1 transmission. ServingCellConfigCommonSIB The information element list identifies configuration information for multiple cells. In some aspects, network node 110 may include frequency information in the SIB1 message. For example, when each cell in a cell group shares a common downlink frequency (e.g., associated with a common downlink carrier), network node 110 may include a single FrequencyInfoDL-SIB The information element conveys frequency information for multiple cells within a cell group. In some aspects, network node 110 may include information identifying the bandwidth portion in the SIB1 message. For example, the cell group may have a single shared initial downlink bandwidth portion or may be configured with a per-cell initial downlink bandwidth portion, and network node 110 may include... BWP-DownlinkCommmonSIB A list or a single information element Aggregated-BWP-DownlinkCommonSIB The information element transmits information identifying one or more initial downlink bandwidth portions.

[0113] In some respects, multiple cells in a cell group can be associated with a specific ordering for cell selection. For example, UE 120 can determine the ordering for cell selection based on the E-UTRA Absolute Radio Channel Number (EARFCN) of multiple cells. Additionally or alternatively, UE 120 can determine the cell ordering based on the frequency of the minimum resource block index in the uplink bandwidth portion of the cell. For example, UE 120 can order the cells from the lowest frequency to the highest frequency (or use another order). In some respects, network node 110 can send information to indicate the cell offset of a cell. For example, when UE 120 is in connected mode, network node 110 can send RRC configuration information (such as...) Aggregated-BWP-DownlinkCommonSIB Information elements Aggregated-BWP-Downlink-Common Information elements ServingCellConfigCommonSIB Information elements or searchSpace Information elements) to indicate the cell offset. Additionally or alternatively, UE 120 may use a default offset (e.g., an initial offset of zero). In some respects, UE 120 may receive information identifying the offset in the SIB1 message, such as via... Serv ingCellConfigurationCommonSIB Information element.

[0114] In some aspects, UE 120 may determine the uplink carrier-to-cell mapping based on SSB broadcasts received from network node 110 in a single cell, including a MIB with per-cell configuration and a single scheduling SIB1. For example, UE 120 may parse SIB1 to determine a set of UE parameters or measurements, and may determine the uplink carrier-to-cell mapping based on the set of UE parameters or measurements. In this case, UE 120 may receive a single Aggregated- UplinkConfigCommonSIB Information element, the information element has FrequencyInfoUL-SIB List of information elements BWP-UplinkCommon A list of information elements (e.g., a configuration indicating the portion of the uplink bandwidth used for each uplink carrier) and TimeAlignmentTimer Information elements. Therefore, UE 120 can use the frequency information and cell identification information included in the received information elements to map the uplink carrier to a cell. Additionally or alternatively, UE 120 can use a set of measurements (such as a set of RSRP or RSRQ measurements) to select the cell to connect to. In some aspects, SIB1 may not include supplementary uplink configurations, such as those identifying the supplementary uplink configuration. UplinkConfigCommonSIB Information element.

[0115] In some respects, network node 110 can time-division multiplex multiple SSBs broadcast via multiple cells in a cell group. For example, such as Figure 7BAs shown, in an example where an SSB is transmitted every 20 milliseconds (ms) and there are 3 cells in the cell group, two of every three SSB bursts are punctured. When an SSB burst is punctured, network node 110 determines that there are conflicting transmissions and interrupts, abandons, or cancels some of the transmissions to avoid interfering with the selected transmissions. For example, in a first instance, network node 110 transmits an SSB in the first cell (and punctures the SSB in the second and third cells); in a second instance, network node 110 transmits an SSB in the second cell (and punctures the SSB in the first and third cells); in a third instance, network node 110 transmits an SSB in the third cell (and punctures the SSB in the first and second cells). In this example, where network node 110 uses puncturing to time-division multiplex multiple SSBs, each SSB may include a MIB and a scheduling SIB1 for the corresponding cell. Therefore, UE 120 receives SSBs from multiple cells (e.g., by monitoring multiple SSB instances) and sorts the SSBs based on sorting criteria (e.g., the lowest frequency of the minimum resource block index of the uplink bandwidth portion). UE 120 may select cells based on RSRP or RSRQ measurements or based on indications received via RRC or SSB SIB1.

[0116] In some respects, UE 120 can use cell identifiers for cell detection and map SSBs to cells. For example, UE 120 can determine the association between an SSB and a cell number based on the PHY cell identifier included in the SSB. In some respects, when UE 120 is decoding a PSS or SSS in an SSB, the UE can use different physical cell identifiers instead of (e.g., using EARFCN or frequency) to determine cell ordering. In some respects, when SSBs (e.g., multiple cells across a cell group) have the same physical cell identifier, UE 120 can use cell ordering.

[0117] like Figure 7A As further illustrated by reference numerals 730 and 740, based on the SSB, UE 120 can send, and network node 110 can receive, access messages 730 of access procedure 740, such as initial access messages or random access messages. For example, UE 120 may use a cell selected based on information included in scheduling SIB1 to send the initial access message. In this case, UE 120 may use a cell selected (e.g., based on one or more selection criteria, such as received indications, a set of measurements, cell ordering, or another criterion) to send the access message. Based on sending the initial access message and completing access procedure 740, UE 120 may obtain access to network services via one or more cells in the cell group.

[0118] In some respects, UE 120 may perform a (four-step) random access procedure in the selected cell. In some respects, UE 120 may use a set of RRC parameters identifying the PRACH acknowledgment to send an initial random access message, such as message 1 (msg1) PRACH message. In this case, network node 110 may determine which cell UE 120 has selected based on the uplink carrier that carried the PRACH message or based on which cell network node 110 has already indicated to UE 120 in, for example, a SIB1 message. Network node 110 may send a response message, such as a random access response (RAR) message 2 (msg2) message, via PDCCH (e.g., where the control resource set (CORESET) for PDCCH is shared by the cell group) or PDSCH. UE 120 may receive the RAR message based on having already obtained the cell order and cell offset from SIB1, as described above. The core set used by UE 120 to receive RARmsg2 messages can be shared with other connected UEs and / or can be a dedicated core set (e.g., a separate core set for random access). Therefore, UE 120 can perform random access procedures and coexist within the same core set with other UEs. Figure 7C As shown, a UE (e.g., UE 120) can monitor a common shared CORESET and use a control channel element (CCE) to cell mapping to determine which messages are associated with which cells. For example, the CCE to cell mapping may indicate that some CCEs in the common shared CORESET are allocated for RAR msg2 PDCCH transmission (which is used for initial access for each cell), and other CCEs in the common shared CORESET are allocated for other types of PDCCH transmission.

[0119] Based on receiving RAR msg2 and decoding DCI, UE 120 can transmit RACH message 3 (msg3) in the selected cell. In this case, the selected cell for transmitting RACH msg3 can be the same selected cell for which UE 120 transmitted PRACH msg 1. Based on transmitting RACH msg3 to network node 10, UE 120 can receive RACH message 4 (msg4) from network node 110. In this case, UE 120 can receive the PDCCH carrying DCI and / or receive the scheduling MAC-CE PDSCH in the shared common CORESET used by the cell group. Based on receiving msg4 from network node 110, UE 120 can transmit a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) message on the uplink carrier of the selected cell.

[0120] As indicated above, Figures 7A to 7C This is provided as an example. Other examples are available with reference to [the relevant information]. Figures 7A to 7C The examples described are different.

[0121] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120) performs operations associated with initial access having downlink carrier sharing.

[0122] like Figure 8 As shown, in some aspects, process 800 may include: receiving at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group (block 810). For example, a UE (e.g., using...) Figure 10 The receiving component 1002 and / or communication manager 1006 described herein can receive at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group, as described above.

[0123] like Figure 8 As further shown, in some aspects, process 800 may include: sending an initial access message (block 820) for a cell in a cell group based on an SSB in a set of SSBs. For example, the UE (e.g., using...) Figure 10 The transmitting component 1004 and / or communication manager 1006 described above can transmit initial access messages for cells in a cell group based on SSBs in a set of SSBs.

[0124] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0125] In the first aspect, the set of SSBs is received from individual cells in a cell group and includes a MIB with a per-cell configuration for the set of cells and a scheduling SIB.

[0126] In the second aspect, either alone or in combination with the first aspect, the set of SSBs is received from multiple cells in a cell group, a first SSB in the set of SSBs is multiplexed with a second SSB in the set of SSBs, and each SSB includes a corresponding MIB and a corresponding scheduling SIB for the corresponding cell in the cell group.

[0127] In the third aspect, either alone or in combination with one or more of the first and second aspects, the first SSB and the second SSB are perforated to reuse the set of SSBs across a set of public resources.

[0128] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the SIB of the set of SSBs includes information identifying at least one serving cell configuration.

[0129] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the set of SSBs includes information identifying a single downlink frequency configuration.

[0130] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the set of SSBs includes information identifying at least one initial downlink bandwidth portion configured for a group of UEs.

[0131] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the cell sorting used for random access response or connection mode operation is based on the value of the channel number indicator or the frequency of the minimum resource block index in the uplink bandwidth portion.

[0132] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the offset value used for random access response or connection mode operation is based on at least one of the following: radio resource control configuration, received information element, or default value.

[0133] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the mapping of the uplink carrier to a cell in the cell group is based on received information identifying a set of configured UE parameters or measurements.

[0134] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the uplink configuration of the UE is at least partially based on a single aggregate set of configuration parameters or multiple individual sets of configuration parameters.

[0135] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the uplink carrier information for cell selection or random access is based on the frequency information type of the information element, and the cell selection from the cell group is based on a set of received cell selection parameters or measurements.

[0136] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 800 includes: communicating with a network node to complete a random access procedure for a physical random access channel in a specific cell selected from a cell group based on an SSB set.

[0137] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the control resource set of the physical downlink control channel is shared by the set of cells in the cell group.

[0138] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the set of control resources for random access performed by the UE is a shared set of control resources.

[0139] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0140] Figure 9 This is a diagram illustrating an example process 900 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 900 is an example in which a device or network node (e.g., network node 110) performs operations associated with initial access having downlink carrier sharing.

[0141] like Figure 9 As shown, in some aspects, process 900 may include: transmitting at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group (box 910). For example, a network node (e.g., using...) Figure 11 The transmitting component 1104 and / or communication manager 1106 described herein can transmit at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group, as described above.

[0142] like Figure 9 As further shown, in some aspects, process 900 may include: receiving an initial access message for a cell in a cell group based on an SSB in a set of SSBs (box 920). For example, a network node (e.g., using...) Figure 11 The receiving component 1102 and / or communication manager 1106 described herein can receive initial access messages for cells in a cell group based on SSBs in a set of SSBs, as described above.

[0143] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0144] In the first aspect, the set of SSBs is sent from individual cells in the cell group and includes a MIB with a per-cell configuration for the set of cells and a scheduling SIB.

[0145] In the second aspect, either alone or in combination with the first aspect, the set of SSBs is sent from multiple cells in a cell group, the first SSB in the set of SSBs is multiplexed with the second SSB in the set of SSBs, and each SSB includes a corresponding MIB and a corresponding scheduling SIB for the corresponding cell in the cell group.

[0146] In the third aspect, either alone or in combination with one or more of the first and second aspects, the first SSB and the second SSB are perforated to reuse the set of SSBs across a set of public resources.

[0147] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the SIB of the set of SSBs includes information identifying at least one serving cell configuration.

[0148] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the set of SSBs includes information identifying a single downlink frequency configuration.

[0149] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the set of SSBs includes information identifying at least one initial downlink bandwidth portion.

[0150] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the cell sorting used for random access response or connection mode operation is based on the value of the channel number indicator or the frequency of the minimum resource block index in the uplink bandwidth portion.

[0151] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the offset value used for random access response or connection mode operation is based on at least one of the following: radio resource control configuration, received information element, or default value.

[0152] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the mapping of the uplink carrier to a cell in a cell group is based on received information identifying a set of configured device parameters or measurements.

[0153] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the uplink configuration is at least partially based on a single aggregate set of configuration parameters or multiple individual sets of configuration parameters.

[0154] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the uplink carrier information for cell selection or random access is based on the frequency information type of the information element, and the cell selection from the cell group is based on a set of transmitted cell selection parameters or measurements.

[0155] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 900 includes: communicating with the UE node to complete a random access procedure for a physical random access channel in a specific cell selected from a cell group based on an SSB set.

[0156] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the control resource set of the physical downlink control channel is shared by the set of cells in the cell group.

[0157] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the set of control resources for random access is a shared set of control resources.

[0158] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0159] Figure 10 This is a diagram of an example device 1000 for wireless communication according to the present disclosure. Device 1000 may be a UE, or a UE may include device 1000. In some aspects, device 1000 includes a receiving component 1002, a transmitting component 1004, and / or a communication manager 1006 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1006 is combined with... Figure 1 The described communication manager 140. As shown, device 1000 can communicate with another device 1008 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1002 and transmitting component 1004.

[0160] In some respects, device 1000 can be configured to perform the functions described herein. Figures 7A to 7C One or more operations described herein. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process is 800. In some respects, Figure 10 The illustrated device 1000 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 10 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0161] Receiver 1002 may receive communications from device 1008, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 1000. In some aspects, receiver 1002 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0162] Transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1008. In some aspects, one or more other components of device 1000 may generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1008. In some aspects, transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1008. In some aspects, transmitting component 1004 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1004 may co-located with the receive component 1002 in one or more transceivers.

[0163] The communication manager 1006 may support the operation of the receiving component 1002 and / or the transmitting component 1004. For example, the communication manager 1006 may receive information associated with configuring the reception of communications by the receiving component 1002 and / or the transmission of communications by the transmitting component 1004. Additionally or alternatively, the communication manager 1006 may generate control information and / or provide control information to the receiving component 1002 and / or the transmitting component 1004 to control the reception and / or transmission of communications.

[0164] The receiving component 1002 can receive at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. The transmitting component 1004 can transmit an initial access message for a cell in the cell group, based on the SSBs in the set of SSBs. The communication manager 1006, the receiving component 1002, and / or the transmitting component 1004 can communicate with network nodes to complete a random access procedure for a physical random access channel in a specific cell selected from the cell group based on the set of SSBs.

[0165] Figure 10 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 10 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The collection of (one or more) components shown is executable and described as being composed of Figure 10 Another set of components shown performs one or more functions.

[0166] Figure 11 This is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a network node, or a network node may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... Figure 1 The described communication manager 150. As shown, device 1100 can communicate with another device 1108 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1102 and transmitting component 1104.

[0167] In some respects, device 1100 can be configured to perform the functions described herein. Figures 7A to 7C One or more operations described herein. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 9 The process is 900. In some respects, Figure 11 The illustrated device 1100 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 11 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0168] Receiver 1102 may receive communications from device 1108, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... Figure 2 The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1102 and / or transmitter component 1104 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1100 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0169] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1108. In some aspects, transmitting component 1104 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

[0170] The communication manager 1106 may support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 may receive information associated with configuring the reception of communications by the receiving component 1102 and / or the transmission of communications by the transmitting component 1104. Additionally or alternatively, the communication manager 1106 may generate control information and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 to control the reception and / or transmission of communications.

[0171] Transmitting component 1104 can transmit at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of SSBs for a set of cells in the cell group. Receiving component 1102 can receive an initial access message for a cell in the cell group based on the SSBs in the set of SSBs. Communication manager 1106, transmitting component 1104, and / or receiving component 1102 can communicate with the UE to complete a random access procedure for a physical random access channel in a specific cell selected from the cell group based on the set of SSBs.

[0172] Figure 11 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The collection of (one or more) components shown is executable and described as being composed of Figure 11Another set of components shown performs one or more functions.

[0173] The following provides an overview of some aspects of this disclosure:

[0174] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of synchronization signal blocks (SSBs) for a set of cells in the cell group; and sending an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0175] Aspect 2: According to the method of aspect 1, wherein the set of SSBs is received from individual cells in the cell group and includes a Master Information Block (MIB) having per-cell configuration for the set of cells and a Scheduled Single System Information Block (SIB).

[0176] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the set of SSBs is received from a plurality of cells in the cell group, wherein a first SSB in the set of SSBs is multiplexed with a second SSB in the set of SSBs, and wherein each SSB includes a corresponding Master Information Block (MIB) and a corresponding Scheduling System Information Block (SIB) for the corresponding cell in the cell group.

[0177] Aspect 4: According to the method of aspect 3, wherein the first SSB and the second SSB are punched to reuse the set of SSBs across a set of public resources.

[0178] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the System Information Block (SIB) of the set of SSBs includes information identifying at least one serving cell configuration.

[0179] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the set of SSBs includes information identifying a single downlink frequency configuration.

[0180] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the set of SSBs includes information identifying at least one initial downlink bandwidth portion configured for a group of UEs.

[0181] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the cell sorting for random access response or connection mode operation is based on the value of the channel number indicator or the frequency value of the minimum resource block index in the uplink bandwidth portion.

[0182] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the offset value for random access response or connection mode operation is based on at least one of: radio resource control configuration, received information element, or default value.

[0183] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the mapping of the uplink carrier to the cells in the cell group is based on received information identifying a set of configured UE parameters or measurements.

[0184] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the uplink configuration of the UE is based at least in part on a single aggregated set of configuration parameters or multiple individual sets of configuration parameters.

[0185] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the uplink carrier information for cell selection or random access is based on the frequency information type of the information element, and wherein the cell selection from the cell group is based on a set of received cell selection parameters or measurements.

[0186] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: communicating with a network node to complete a random access procedure for a physical random access channel in a specific cell selected from the cell group based on the SSB set.

[0187] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the control resource set of the physical downlink control channel is shared by the set of cells in the cell group.

[0188] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the set of control resources for random access performed by the UE is a shared set of control resources.

[0189] Aspect 16: A method of wireless communication performed by a network node, the method comprising: transmitting at least one downlink communication for a cell group having a shared downlink carrier, the at least one downlink communication delivering a set of synchronization signal blocks (SSBs) for a set of cells in the cell group; and receiving an initial access message for a cell in the cell group based on the SSBs in the set of SSBs.

[0190] Aspect 17: The method according to aspect 16, wherein the set of SSBs is sent from a single cell in the cell group and includes a Master Information Block (MIB) having a per-cell configuration for the set of cells and a Scheduled Single System Information Block (SIB).

[0191] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the set of SSBs is transmitted from a plurality of cells in the cell group, wherein a first SSB in the set of SSBs is multiplexed with a second SSB in the set of SSBs, and wherein each SSB includes a corresponding Master Information Block (MIB) and a corresponding Scheduling System Information Block (SIB) for the corresponding cell in the cell group.

[0192] Aspect 19: According to the method of aspect 18, wherein the first SSB and the second SSB are punched to reuse the set of SSBs across a set of public resources.

[0193] Aspect 20: The method according to any one of aspects 16 to 19, wherein the system information block (SIB) of the set of SSBs includes information identifying at least one serving cell configuration.

[0194] Aspect 21: The method according to any one of Aspects 16 to 20, wherein the set of SSBs includes information identifying a single downlink frequency configuration.

[0195] Aspect 22: The method according to any one of Aspects 16 to 21, wherein the set of SSBs includes information identifying at least one initial downlink bandwidth portion.

[0196] Aspect 23: The method according to any one of Aspects 16 to 22, wherein the cell sorting for random access response or connection mode operation is based on the value of the channel number indicator or the value of the frequency of the minimum resource block index in the uplink bandwidth portion.

[0197] Aspect 24: The method according to any one of Aspects 16 to 23, wherein the offset value for random access response or connection mode operation is based on at least one of: radio resource control configuration, received information element, or default value.

[0198] Aspect 25: The method according to any one of Aspects 16 to 24, wherein the mapping of the uplink carrier to a cell in the cell group is based on received information identifying a set of configured device parameters or measurements.

[0199] Aspect 26: The method according to any one of Aspects 16 to 25, wherein the uplink configuration is at least partially based on a single aggregate set of configuration parameters or a plurality of separate sets of configuration parameters.

[0200] Aspect 27: The method according to any one of Aspects 16 to 26, wherein the uplink carrier information for cell selection or random access is based on the frequency information type of the information element, and wherein the cell selection from the cell group is based on a set of transmitted cell selection parameters or measurements.

[0201] Aspect 28: The method according to any one of Aspects 16 to 27, the method further comprising: communicating with a user equipment (UE) to complete a random access procedure for a physical random access channel in a specific cell selected from the cell group based on the set of SSBs.

[0202] Aspect 29: The method according to any one of Aspects 16 to 28, wherein the control resource set of the physical downlink control channel is shared by the set of cells in the cell group.

[0203] Aspect 30: The method according to any one of aspects 16 to 29, wherein the set of control resources for random access is a shared set of control resources.

[0204] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 30.

[0205] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0206] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 30.

[0207] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 30.

[0208] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 30.

[0209] Aspect 36: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0210] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0211] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0212] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0213] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0214] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0215] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0216] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the UE to: For a cell group having a shared downlink carrier, at least one downlink communication is received, the at least one downlink communication delivering a set of synchronization signal blocks (SSBs) for a set of cells in the cell group; as well as For each cell in the cell group, an initial access message is sent based on the SSBs in the set of SSBs.

2. The UE of claim 1, wherein the set of SSBs is received from a single cell in the cell group and includes a Master Information Block (MIB) having a per-cell configuration for the set of cells and a Scheduled Single System Information Block (SIB).

3. The UE according to claim 1, wherein the set of SSBs is received from multiple cells in the cell group, wherein a first SSB in the set of SSBs is multiplexed with a second SSB in the set of SSBs, and wherein each SSB includes a corresponding Master Information Block (MIB) and a corresponding Scheduling System Information Block (SIB) for the corresponding cell in the cell group.

4. The UE of claim 3, wherein the first SSB and the second SSB are punctured to reuse the set of SSBs across a set of common resources.

5. The UE according to claim 1, wherein the System Information Block (SIB) of the set of SSBs includes information identifying at least one serving cell configuration.

6. The UE of claim 1, wherein the set of SSBs includes information identifying a single downlink frequency configuration.

7. The UE of claim 1, wherein the set of SSBs includes information identifying at least one initial downlink bandwidth portion configured for a group of UEs.

8. The UE of claim 1, wherein the cell sorting for random access response or connection mode operation is based on the value of the channel number indicator or the frequency of the minimum resource block index in the uplink bandwidth portion.

9. The UE of claim 1, wherein the offset value for random access response or connection mode operation is based on at least one of the following: Radio resource control configuration, Received information element, or default value.

10. The UE of claim 1, wherein the mapping of the uplink carrier to a cell in the cell group is based on received information identifying a set of configured UE parameters or measurements.

11. The UE of claim 1, wherein the uplink configuration of the UE is at least partially based on a single aggregate set of configuration parameters or multiple individual sets of configuration parameters.

12. The UE of claim 1, wherein the uplink carrier information for cell selection or random access is based on the frequency information type of the information element, and The cell selection performed from the cell group is based on a set of received cell selection parameters or measurements.

13. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: Communicate with network nodes to complete a random access procedure for a physical random access channel in a specific cell selected from the cell group based on the SSB set.

14. The UE of claim 1, wherein the control resource set of the physical downlink control channel is shared by the set of cells in the cell group.

15. The UE of claim 1, wherein the control resource set for random access performed by the UE is a shared control resource set.

16. A network node for wireless communication, the network node comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: At least one downlink communication is transmitted for a cell group having a shared downlink carrier, the at least one downlink communication transmitting a set of synchronization signal blocks (SSBs) for a set of cells in the cell group; as well as For each cell in the cell group, the initial access message is received based on the SSBs in the set of SSBs.

17. The network node of claim 16, wherein the set of SSBs is sent from a single cell in the cell group and includes a Master Information Block (MIB) with per-cell configuration for the set of cells and a Scheduled Single System Information Block (SIB).

18. The network node of claim 16, wherein the set of SSBs is sent from a plurality of cells in the cell group, wherein a first SSB in the set of SSBs is multiplexed with a second SSB in the set of SSBs, and wherein each SSB includes a corresponding Master Information Block (MIB) and a corresponding Scheduling System Information Block (SIB) for the corresponding cell in the cell group.

19. The network node of claim 18, wherein the first SSB and the second SSB are punctured to reuse the set of SSBs across a set of public resources.

20. A method for wireless communication performed by a user equipment (UE), the method comprising: For a cell group having a shared downlink carrier, at least one downlink communication is received, the at least one downlink communication delivering a set of synchronization signal blocks (SSBs) for a set of cells in the cell group; as well as For each cell in the cell group, an initial access message is sent based on the SSBs in the set of SSBs.

Images