Availability indication for physical random access channel resources

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive configuration information indicating a first physical random access channel (PRACH) configuration indicating one or more PRACH resources, indicating a second PRACH configuration indicating one or more additional PRACH resources, and including an indication of which of the one or more additional PRACH resources can be used for a PRACH transmission. The UE can transmit a PRACH communication in accordance with the configuration information. Numerous other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 573,923, filed April 3, 2024, entitled “AVAILABILITY INDICATION FOR PHYSICAL RANDOM ACCESS CHANNEL RESOURCES,” and U.S. Non-Provisional Patent Application No. 19 / 067,638, filed February 28, 2025, entitled “AVAILABILITY INDICATION FOR PHYSICAL RANDOM ACCESS CHANNEL RESOURCES,” which is assigned to the assignee of this application. The disclosures of these earlier applications are considered part of this patent application and are incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for indicating the availability of physical random access channel resources. Background Technology

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

[0005] 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

[0006] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus 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 individually or in any combination to receive configuration information that: indicates a first Physical Random Access Channel (PRACH) configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The one or more processors may be configured individually or in any combination to transmit PRACH communication according to the configuration information.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus 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 individually or in any combination to transmit configuration information to a UE, the configuration information indicating: a first PRACH configuration indicating one or more PRACH resources; an indication of a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The one or more processors may be configured individually or in any combination to receive PRACH communication according to the configuration information.

[0008] Some aspects described herein relate to a method of wireless communication performed by a device of a UE. The method may include receiving configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The method may include transmitting PRACH communication based on the configuration information.

[0009] Some aspects described herein relate to a method for wireless communication performed by a device of a network node. The method may include transmitting configuration information to a UE, the configuration information indicating: a first PRACH configuration indicating one or more PRACH resources; an indication of a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The method may include receiving PRACH communication based on the configuration information.

[0010] 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 enables the UE to receive configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit PRACH communication according to the configuration information.

[0011] 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 configuration information to a UE, the configuration information indicating: a first PRACH configuration indicating one or more PRACH resources; a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. When executed by one or more processors of the network node, the set of instructions enables the network node to receive PRACH communication according to the configuration information.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The apparatus may include components for transmitting PRACH communication according to the configuration information.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting configuration information to a UE, the configuration information indicating: a first PRACH configuration indicating one or more PRACH resources; a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The apparatus may include components for receiving PRACH communication based on the configuration information.

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

[0015] 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

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

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

[0018] Figure 2 This is an illustration of an example network node communicating with an example user equipment (UE) in a wireless network according to the present disclosure.

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

[0020] Figure 4 This is a diagram illustrating an example of a four-step random access procedure according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example associated with an availability indication for Physical Random Access Channel (PRACH) resources, according to this disclosure.

[0022] Figure 6 This is a diagram illustrating an example of a configuration associated with a PRACH resource according to this disclosure.

[0023] Figure 7 This is a diagram illustrating an example of random access channel timing masking associated with PRACH resources according to this disclosure.

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

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

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

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

[0028] 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 protection 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 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 practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] 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 boxes, 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0030] User equipment (UE) can execute a random access procedure to establish a wireless communication connection to the network. In conjunction with the random access procedure, the UE and network nodes can exchange messages. The random access procedure can begin with the UE sending PRACH communication, including a Physical Random Access Channel (PRACH) preamble. The UE can send PRACH communication within PRACH resources.

[0031] Network nodes may send (e.g., broadcast) configuration information indicating PRACH configurations that specify the PRACH resources available to the UE for transmitting PRACH communications. In some cases, the PRACH configuration indicated by the network node may indicate sparse PRACH resources in the time domain. Therefore, significant delays may exist associated with the UE accessing the network.

[0032] The various aspects collectively involve enhancing the temporal density of PRACH resources. Some aspects more specifically involve UE reception configuration information indicating a first PRACH configuration for a first UE (e.g., a legacy UE) and a second PRACH configuration for a second UE. In some aspects, the first PRACH configuration may indicate PRACH resources, and the second PRACH configuration may indicate PRACH resources and additional PRACH resources in the temporal domain. In some aspects, the configuration information may also include indications of which additional PRACH resources are available to the UE (e.g., a UE supporting the second PRACH configuration). For example, this indication may indicate random access channel (RACH) timing (RO) masking for additional PRACH resources and / or may indicate the activation or deactivation of additional PRACH resources.

[0033] 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, the described techniques can be used to reduce access latency by increasing the temporal density of PRACH resources (e.g., additional PRACH resources indicated by a second PRACH configuration). Additionally, the described techniques can be used to better balance improvements in access latency with network energy efficiency by selectively masking and / or activating / deactivating additional PRACH resources. Furthermore, RO masking for additional PRACH resources can enable RO sharing among multiple RACH processes and / or can support PRACH adaptation in the spatial domain (e.g., by implementing a non-uniform amount of PRACH resources per synchronization signal block (SSB)).

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

[0035] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 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. These 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. Such 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, etc. 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.

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

[0037] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, 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 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 / NR RATs, 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.

[0038] Various operating bands have been defined by frequency range designations: 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 distinct from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are generally referred to as the midband frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into midband frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz that are within FR1 and / or included in midband frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in midband 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, 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 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.

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

[0040] 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 a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0041] 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 geographic 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 compliant with the O-RAN Alliance), 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.

[0042] 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, 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 type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

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

[0044] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. 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 may 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).

[0045] 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 1 In 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. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0046] In some examples, network node 110 may be, may include, or 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. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "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.

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

[0048] 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. In some examples, 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.

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

[0050] 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, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a 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.

[0051] 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 processor group 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 processor group that is configured or configured to perform the set of functions.

[0052] 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 a plurality of 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 be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0053] 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 collectively referred to 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).

[0054] 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 lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, 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 UEs 120 in the first category and UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capacity UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified 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.

[0055] 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 communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly 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.

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

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

[0058] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may receive configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; and transmits PRACH communication according to the configuration information. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0059] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send configuration information to the UE that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; and receives PRACH communication according to the configuration information. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

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

[0061] Figure 2 This is an illustration of an example network node 110 communicating with an example UE 120 in a wireless network according to the present disclosure.

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

[0063] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the 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.

[0064] 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 the same set of processors or can be 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 combined... 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.

[0065] For downlink communication from network node 110 to UE 120, transmit 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, transmit 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) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmit 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)).

[0066] 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 set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

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

[0068] 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 where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), 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.

[0069] 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 for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0070] 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 analog signals (such as those used for transmission or reception via an air interface) to 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.

[0071] 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 execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

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

[0073] 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, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may 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 may provide the decoded control information and system information to controller / processor 280.

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

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

[0076] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding 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).

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

[0078] 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, which can be used to independently transmit cross-polarized signals. 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.

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

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

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

[0082] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed 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 decomposed 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 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0083] Each component in the decomposed 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 be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

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

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

[0086] 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 actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0087] 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 can modulate RAN behavior or performance. For example, the non-RT RIC 350 can monitor long-term trends and patterns in performance and can employ AI / ML models to perform corrective actions 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).

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

[0089] 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 an availability indication for PRACH resources, 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 an availability indication for PRACH resources, 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.

[0090] In some aspects, UE 120 includes components for receiving configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; and / or components for transmitting PRACH communication according to the configuration information. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: 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.

[0091] In some aspects, network node 110 includes components for transmitting configuration information to a UE, the configuration information indicating: a first PRACH configuration indicating one or more PRACH resources; a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; and / or components for receiving PRACH communication according to the configuration information. Components enabling 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.

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

[0093] Figure 4 This is a diagram illustrating Example 400 of the four-step random access procedure according to this disclosure. Figure 4 As shown, network node 110 and UE 120 can communicate with each other to perform a four-step random access procedure.

[0094] As shown by reference numeral 405 in the accompanying drawings, network node 110 may send one or more SSBs and random access configuration information, and UE 120 may receive one or more SSBs and random access configuration information. In some aspects, the random access configuration information may be sent and / or indicated by system information (e.g., one or more System Information Blocks (SIBs)) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in RRC messages and / or PDCCH command messages that trigger the RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used during the random access procedure, such as one or more parameters for sending a Random Access Message (RAM) and / or one or more parameters for receiving a Random Access Response (RAR). For example, the random access configuration information may indicate PRACH resources for sending RAM.

[0095] As shown by reference numeral 410 in the attached figure, UE 120 can transmit RAM, which may include a preamble (sometimes referred to as a random access preamble, PRACH preamble, or RAM preamble). The message including the preamble may be referred to as Message 1, msg1, MSG1, First Message, or Initial Message in the four-step random access process. The random access message may include a random access preamble identifier. UE 120 may transmit RAM in PRACH resources.

[0096] As shown by reference numeral 415 in the attached figure, network node 110 may send a RAR as a response to the preamble. The message including the RAR may be referred to as message 2, msg2, MSG2, or the second message in the four-step random access procedure. In some aspects, the RAR may indicate the detected random access preamble identifier (e.g., received from UE 120 in msg1). Additionally or alternatively, the RAR may indicate the resource allocation to be used by UE 120 to send message 3 (msg3).

[0097] In some respects, as part of the second step of the four-step random access procedure, network node 110 may send PDCCH communication for the RAR. This PDCCH communication may schedule PDSCH communication that includes the RAR. For example, the PDCCH communication may indicate resource allocation for the PDSCH communication. Also as part of the second step of the four-step random access procedure, network node 110 may send PDSCH communication for the RAR, as scheduled by the PDCCH communication. The RAR may be included in the MAC Protocol Data Unit (PDU) of the PDSCH communication.

[0098] As shown by reference numeral 420 in the attached figure, UE 120 may send an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or the third message of the four-step random access procedure. In some aspects, the RRC connection request may include the UE identifier, UCI, and / or PUSCH communication (e.g., RRC connection request).

[0099] As shown by reference numeral 425, network node 110 may send an RRC connection establishment message. The RRC connection establishment message may be referred to as message 4, msg4, MSG4, or the fourth message in a four-step random access procedure. In some aspects, the RRC connection establishment message may include the detected UE identifier, timing advance value, and / or contention resolution information. As shown by reference numeral 430, if UE 120 successfully receives the RRC connection establishment message, UE 120 may send a Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK). In some aspects, UE 120 and network node 110 may perform different random access procedures, such as a two-step random access procedure.

[0100] In some examples, various signaling and / or channel transmissions can be adapted, such as those associated with random access. For example, SSB transmissions can be adapted in the time domain, such as by adapting to the periodicity of SSB transmissions. As another example, PRACH can be adapted in the time domain to enhance network energy efficiency (NES). Furthermore, PRACH can be adapted in the spatial domain, such as by using a non-uniform amount of PRACH resources per SSB. As another example, paging timing can be adapted, such as by restricting paging timing to the time domain (e.g., provided there is no increase in paging delay). Generally, signaling and / or channel transmissions can be adapted if there is no negative impact on legacy UEs.

[0101] PRACH adaptation in the time domain can employ one or more mechanisms. For example, this adaptation can be based on configuring additional (e.g., different) PRACH resources for NES-capable UEs, which are in addition to the PRACH resources (if any) used for legacy UEs. Thus, NES-capable UEs can use both the additional PRACH resources and the PRACH resources used for legacy UEs. The additional PRACH resources can be adapted based on PRACH resource periodicity and / or PRACH timing, PRACH configuration, association of time periods and / or association of pattern time periods and / or SSB-to-RO mapping cycles, adaptation by extending cell discontinuous reception (DRX) operation for PRACH, and / or centralizing ROs in the time domain, etc.

[0102] PRACH adaptation in the time domain can be provided by a network node (e.g., a gNB) without UE triggering. Alternatively, PRACH adaptation can be provided with UE triggering. "UE triggering" means that the UE requests PRACH adaptation. PRACH adaptation can be indicated by dynamic signaling and / or semi-static signaling. In some examples, PRACH transmission can be adapted based on specific conditions. PRACH adaptation can be applied to idle, inactive, and / or connected mode UEs. PRACH adaptation can be applied to cells with both legacy UEs and NES-capable UEs, or to cells with only NES-capable UEs.

[0103] Several techniques can be used to configure additional PRACH resources. In some examples, in addition to an old PRACH configuration index indicating the PRACH configuration for legacy UEs (e.g., ...), prach-ConfigurationIndexIn addition to parameters, supplementary PRACH configuration indexes can be configured semi-statically (e.g., in SIB1 or in RRC signaling) to indicate PRACH configurations for NES-capable UEs. Here, PRACH configurations for NES-capable UEs may include PRACH configurations for legacy UEs. In some examples, supplementary PRACH configuration indexes may not be provided to NES-capable UEs. Instead, the periodicity indicated by the legacy PRACH configuration index may be adjusted (e.g., shortened) for NES-capable UEs. Table 6.3.3.2-3 of 3GPP Technical Specification 38.211 provides examples of PRACH configuration indexes and their associated PRACH configurations. "Supplementary PRACH resources" may refer (e.g., in the time domain) to PRACH resources configured for NES-capable UEs that are not (e.g., in the time domain) included in the PRACH configuration for legacy UEs. PRACH resources may correspond to RACH timing (RO) and / or PRACH preamble indexes.

[0104] The various aspects collectively involve enhancing the temporal density of PRACH resources. Some aspects more specifically involve UE reception configuration information indicating a first PRACH configuration for a first UE (e.g., a legacy UE) and a second PRACH configuration for a second UE. In some aspects, the first PRACH configuration may indicate PRACH resources, and the second PRACH configuration may indicate PRACH resources and additional PRACH resources in the temporal domain. In some aspects, the configuration information may also include indications of which additional PRACH resources are available to the UE (e.g., a UE supporting the second PRACH configuration). For example, the indication may indicate RO masking for additional PRACH resources and / or indicate the activation or deactivation of additional PRACH resources.

[0105] 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, the described techniques can be used to reduce access latency by increasing the temporal density of PRACH resources (e.g., additional PRACH resources indicated by a second PRACH configuration). Additionally, the described techniques can be used to better balance improvements in access latency with network energy efficiency by selectively masking and / or activating / deactivating additional PRACH resources. Furthermore, RO masking for additional PRACH resources can enable RO sharing among multiple RACH procedures and / or can support PRACH adaptation in the spatial domain (e.g., by implementing a non-uniform amount of PRACH resources per SSB).

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

[0107] Figure 5 This is a diagram of Example 500 associated with an availability indication for PRACH resources according to this disclosure. Figure 5 As shown, network nodes (e.g., network nodes 110, CU, DU, and / or RU) can communicate with a UE (e.g., UE 120). In some aspects, the network nodes and the UE can be part of a wireless network (e.g., wireless network 100). In some aspects, the UE can be an NES-capable UE, which can refer to a UE having the ability to perform NES operations associated with 3GPP NR Release 19 or later. For example, an NES-capable UE can be configured with PRACH resources not configured for legacy UEs. In some examples, a PRACH configuration index table can be provided to an NES-capable UE, which includes indices not included in the PRACH configuration index table provided for legacy UEs.

[0108] As shown by reference numeral 505 in the attached figure, a network node can transmit SSBs and a UE can receive SSBs. For example, a network node can use different beams to transmit SSBs. A UE can use SSBs to synchronize with a network node.

[0109] As shown by reference numeral 510 in the attached figure, a network node can send configuration information, and a UE can receive this configuration information. In some aspects, the UE can receive the configuration information via one or more of the following: system information (e.g., Master Information Block (MIB) and / or SIB, RRC signaling, one or more MAC-CEs and / or DCIs, etc.

[0110] In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, these one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, a subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as one or more MAC-CE and / or one or more DCI messages, etc.

[0111] In some aspects, configuration information may include random access configuration information, such as combined with Figure 4As described. In some aspects, configuration information may indicate one or more legacy PRACH resources and one or more supplementary PRACH resources. For example, configuration information may indicate: a first PRACH configuration indicating legacy PRACH resources and a second PRACH configuration indicating supplementary PRACH resources. The second PRACH configuration may also indicate legacy PRACH resources or a subset of legacy PRACH resources. The first PRACH configuration may be used by a first UE (e.g., a legacy UE), and the second PRACH configuration may be used by a second UE (e.g., a UE with NES capability). The first UE (e.g., a legacy UE) may use legacy PRACH resources, and the second UE (e.g., a UE with NES capability) may use both supplementary PRACH resources and legacy PRACH resources (e.g., all legacy PRACH resources in the first PRACH configuration and the second PRACH configuration, or the union of legacy PRACH resources). Supplementary PRACH resources may include any PRACH resources not included in legacy PRACH resources. For example, each PRACH resource may correspond to a RACH timing (e.g., time and frequency resources) in which the UE may transmit PRACH communications. In some respects, the configuration information indicating the first and second PRACH configurations can be semi-static configuration information, such as in SIB1 or RRC messages. The PRACH configuration may indicate the preamble format, the periodicity of the PRACH resource indicated by the PRACH configuration, one or more subframe numbers including the PRACH resource, and / or the start symbol for the PRACH resource, etc.

[0112] In some aspects, the configuration information may include a first PRACH configuration index (e.g., an old PRACH configuration index) for indicating a first PRACH configuration with legacy PRACH resources, and a second PRACH configuration index (e.g., the second PRACH configuration may include the first PRACH configuration) for indicating a second PRACH configuration with any legacy PRACH resources and additional PRACH resources. Alternatively, the configuration information may include a first PRACH configuration index for indicating the first PRACH configuration, but the second PRACH configuration index may be omitted. Here, the configuration information may further indicate an adaptation (e.g., modification) to the first PRACH configuration that produces the second PRACH configuration. For example, this adaptation may increase the periodicity of the first PRACH configuration to achieve the second PRACH configuration.

[0113] The configuration information may also include an indication of which additional PRACH resources are available for PRACH transmission. For example, available PRACH resources may be used by the UE as RO, for SSB-to-RO mapping, and / or for RACH preambles, etc.

[0114] In some aspects, an indication of which additional PRACH resources are available among the additional PRACH resources can indicate a masking (e.g., RO masking) to be applied to the additional PRACH resources. For example, masking can indicate one or more additional PRACH resources among those that are muted (e.g., these muted PRACH resources may not be ROs used to transmit PRACH communications). Masking for additional PRACH resources enables RO sharing between multiple RACH procedures. Additionally or alternatively, masking for additional PRACH resources can (e.g., by implementing a non-uniform amount of PRACH resources per SSB) support PRACH adaptation in the spatial domain. Masking for additional PRACH resources can be in addition to any masking indicated for legacy PRACH resources.

[0115] In some examples, SSBs sent by the network node (each SSB associated with a different beam) may have a mapping to ROs (e.g., to enable the network node to identify which SSB beam the UE has selected for PRACH communication based on which RO the UE uses). In some examples, not all defined SSBs are actually sent by the network node. Configuration information (e.g., in SIB1 or RRC messages) may (e.g., using parameters) ssb-PositionsInBurst (In the bitmap) indicates the set of SSBs that are actually sent. For the purpose of SSB-to-RO mapping, additional PRACH resources can be provided to all SSBs that are actually sent or to a subset of the SSBs that are actually sent.

[0116] In some aspects, in addition to the actual set of SSBs sent, configuration information (e.g., in SIB1 or RRC messages) may indicate a subset of the actual set of SSBs sent for SSB-to-RO mapping for additional PRACH resources. For example, the configuration information may include a first-order diagram indicating the set of actual SSBs sent (e.g., using parameters). ssb- PositionsInBurst ) and a second bitmap of a subset of the set used to indicate the actual SSB sent (e.g., using parameters) ssb-PositionsInBurst-r19 ).

[0117] In some aspects, the second bitmap may indicate whether each SSB in the defined SSBs is included in a subset (e.g., the first and second bitmaps may have the same length). In some aspects, the second bitmap may be a short bitmap based on the first bitmap (e.g., the length of the second bitmap is less than the length of the first bitmap). For example, the bits of the second bitmap may correspond to the SSBs indicated as actually transmitted by the first bitmap, and the second bitmap may not include bits corresponding to SSBs indicated as not transmitted by the first bitmap. As an example, if the first bitmap is [1 1 1 0] (indicating that SSB 0, SSB 1, and SSB 2 were actually transmitted), the second bitmap may include three bits corresponding to the three actually transmitted SSBs respectively (e.g., [1 0 0], which indicates that SSB 0 is in the subset and SSB 1 and SSB 2 are not in the subset).

[0118] In some aspects, an indication of which additional PRACH resources are available among the additional PRACH resources can indicate the activation or deactivation of one or more additional PRACH resources. For example, the indication can indicate masking and / or activation / deactivation. Activation / deactivation can be related to the availability of PRACH resources resulting from masking (e.g., masking is a first indication of the availability of additional PRACH resources, and activation / deactivation is a second indication of the availability of additional PRACH resources). Activation / deactivation of additional PRACH resources can apply to any RRC state of the UE. The signaling used for activation / deactivation can adopt a common framework used for all RRC states. Furthermore, the activation / deactivation signaling can use existing DCI formats, thus not introducing new DCI formats. In some aspects, activation / deactivation indicated during a system information modification period can be applied to the next system information modification period.

[0119] Various channels and / or signals can be used to activate / deactivate signaling. In some aspects, the activation / deactivation of additional PRACH resources can be indicated in SIB1 and / or RRC messages. In some aspects, the activation / deactivation of additional PRACH resources can be indicated in paging DCIs (e.g., DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a paging radio network temporary identifier (P-RNTI), DCI format 2_7 with a CRC scrambled by a paging early indication (PEI)-RNTI, and / or DCI format 2_6 with a CRC scrambled by a power saving (PS)-RNTI, etc.

[0120] If a Tracking Reference Signal (TRS) availability indication is provided in the paging DCI, the paging DCI may not have reserved bits. For example, the TRS availability indication can be 1, 2, 3, 4, 5, or 6 bits. If configured, the number of bits can be equal to one plus the number configured in the TRS resource set (e.g., using...). trs-ResourceSetConfig One or more parameters provided in indBitID Parameters (where) indBitID The parameter is the highest value for the index of the associated bit in the TRS Resource Set Indicator TRS Availability Indicator field, otherwise it is zero. Furthermore, the number of reserved bits can be (8-) for operation in cells with shared spectrum channel access in FR1 or for operation in cells in FR2-2. M ) bits, or (6-) bits used for operation in cells without shared spectrum channel access. M ) position, of which M This is the number of bits used in the TRS availability indicator field.

[0121] DCI format 2_7 can be used for paging early indication and / or TRS availability indication for one or more UEs. For example, the DCI in DCI format 2_7 may include a paging indication field and a TRS availability indication (e.g., having 1, 2, 3, 4, 5, or 6 bits, as described herein). The size of DCI format 2_7 may be determined by higher-layer parameters (e.g., payloadSizeDCI-2-7 (Parameters) Indicator. The number of information bits in DCI format 2_7 can be equal to or less than the payload size of DCI format 2_7. If the number of information bits is less than the payload size, the remaining bits can be reserved.

[0122] In some respects, as described herein, indications for activation / deactivation of additional PRACH resources can be semi-statically indicated, such as in SIBs (e.g., SIB1) and / or RRC messages. For example, an indication for activation or deactivation of one or more additional PRACH resources may be in an SIB (e.g., SIB1) or RRC message. If the indication is in an SIB (e.g., SIB1), paging for the UE for an SIB update that only indicates an update for activation or deactivation of additional PRACH resources is suppressed (e.g., not sent, skipped, discarded, etc.). As an example, a network node may avoid sending paging messages to the UE for SIB (e.g., SIB1) updates that only indicate an update for activation or deactivation of additional PRACH resources. For example, if the indication is in SIB1, the UE does not expect to receive paging if the SIB1 update is only for updating additional PRACH resources (e.g., the network node does not send a paging request for the UE to obtain a new SIB1 if the SIB1 update is only for updating additional PRACH resources).

[0123] In some aspects, as described herein, an indication of activation / deactivation of an additional PRACH resource may be indicated in a DCI message (e.g., in DCI format 2_7) used for paging early indication and / or TRS availability indication. In some aspects, the indication of activation / deactivation of an additional PRACH resource may include a first indication in a SIB (e.g., SIB1) or RRC message, and a second indication in a DCI message (e.g., in DCI format 2_7) used for paging early indication and / or TRS availability indication. For example, in addition to SIB1 and / or RRC-based activation / deactivation, the activation / deactivation of an additional PRACH resource may be additionally indicated in a DCI message (e.g., in DCI format 2_7). The first and second indications may be the same, or the second indication may provide an update to the first indication (e.g., the second indication may differ from the first indication). In some aspects, the DCI may include fields (e.g., newly introduced fields) for indicating the activation or deactivation of an additional PRACH resource (e.g., for PRACH timing and / or resource availability indication). For example, the field may be located in DCI format 2_7. The indication of activation / deactivation of additional PRACH resources in the DCI (e.g., in the field) may apply to all paging times and / or paging frames, or to a subset of paging times and / or paging frames (e.g., the subset may be indicated in the DCI or elsewhere).

[0124] In some respects, an indication of the activation or deactivation of one or more additional PRACH resources may be included in the paging DCI message. For example, if the paging DCI message lacks a TRS availability indication (e.g., no TRS availability indication is provided, for example, no TRS is configured for the UE),... trs-ResourceSetConfig If the parameter is specified, the indication can be indicated in the paging DCI message. Alternatively, if the paging DCI message includes a TRS availability indication using a number of indication bits that meet a threshold (e.g., a TRS availability indication is provided, but the number of indication bits is less than or equal to the threshold, such as 3), the indication can be indicated in the paging DCI message.

[0125] A set of additional PRACH resources can be defined for the purpose of activating / deactivating additional PRACH resources (e.g., the set indicates which additional PRACH resources are activated or deactivated by an indication of activation / deactivation of additional PRACH resources). In some aspects, the number of bits used for additional PRACH resources is based on the number of ROs or PRACH slots for additional PRACH resources within a PRACH period defined by a first PRACH configuration (e.g., a PRACH period defined by a PRACH periodicity configured for legacy UEs) (e.g., a PRACH configuration period, a PRACH association period, or a PRACH association pattern period). In some aspects, the number of bits used for additional PRACH resources is based on the number of ROs or PRACH slots for additional PRACH resources within a PRACH period defined by a second PRACH configuration (e.g., a PRACH period defined by a PRACH periodicity configured for NES-capable UEs) (e.g., a PRACH configuration period, a PRACH association period, or a PRACH association pattern period).

[0126] For example, for the purpose of activating / deactivating additional PRACH resources, the number of bits for additional PRACH resources can be determined by the first PRACH configuration index (e.g., the legacy PRACH configuration index for legacy UEs, such as using...). prach- ConfigurationIndex The number of ROs or PRACH slots used to attach PRACH resources within the PRACH configuration periodicity (or PRACH associated periodicity or PRACH associated pattern periodicity) configured by the parameters. As an example, if the first PRACH configuration index indicates one PRACH resource for a 20ms periodicity (e.g., PRACH configuration index 3), and the second PRACH configuration index indicates two PRACH resources for a 10ms periodicity (e.g., PRACH configuration index 17), then there will be 3 bits available for attaching PRACH resources in the 20ms period (e.g., assuming no RO masking is applied).

[0127] Alternatively, for the purpose of activating / deactivating additional PRACH resources, the number of bits for additional PRACH resources can be the PRACH configuration periodicity (or PRACH-associated periodicity or PRACH-associated pattern periodicity) configured by a second PRACH configuration index (e.g., a new PRACH configuration index for NES-capable UEs) or the number of ROs or PRACH slots for additional PRACH resources within an indicated PRACH configuration periodicity for NES-capable UEs. As an example, if the second PRACH configuration index or the indicated PRACH configuration periodicity indicates a 10ms periodicity with two PRACH resources in a time period, then there will be 2 bits for additional PRACH resources in the 10ms time period (e.g., assuming no RO masking is applied).

[0128] The PRACH association period may include the minimum number of PRACH configuration periods required to achieve a complete mapping between the SSB and RO. The PRACH association pattern period may include the minimum number of PRACH association periods that can be repeated every 160ms (e.g., SSB periodicity).

[0129] In some aspects, if an additional PRACH resource indicated by the second PRACH configuration is activated, the configuration information may additionally indicate whether one or more legacy PRACH resources indicated by the first PRACH configuration are available for PRACH transmission. For example, the configuration information may include a single bit indicating whether a UE with NES capability wants to use a legacy PRACH resource. As another example, if an additional PRACH resource is activated, the configuration information may (e.g., using a bitmap) indicate the masking to be applied to the legacy PRACH resource (e.g., RO masking). If an additional PRACH resource indicated by the second PRACH configuration is activated, the indication of whether one or more legacy PRACH resources indicated by the first PRACH configuration are available for PRACH transmission may be in an SIB (e.g., SIB1), in an RRC message, or included in an indication indicating the activation or deactivation of the additional PRACH resource. If the PRACH resource is available for PRACH transmission, the PRACH resource (e.g., RO) may be "activated".

[0130] The UE can configure itself, at least in part, based on configuration information. In some respects, the UE can be configured to perform one or more of the operations described herein, at least in part, based on configuration information.

[0131] As shown by reference numeral 515 in the attached figure, the UE can send PRACH communications according to the configuration information, and the network node can receive PRACH communications. For example, the UE can send PRACH communications in a PRACH resource (sometimes also referred to as a "RACH resource"). The PRACH resource may correspond to a legacy PRACH resource or to an additional PRACH resource available as indicated by the configuration information (e.g., based on masking and / or activation / deactivation). In some examples, the PRACH communications may include a PRACH preamble. The PRACH communications may be part of a random access procedure (such as combining...). Figure 4 This is part of the described random access procedure. For example, PRACH communication may include RAM.

[0132] In some respects (e.g., after the UE has established a connection with the network node using a random access procedure), the UE may send a capability report, and the network node may receive the capability report. The capability report may indicate whether the UE supports a feature and / or one or more parameters associated with that feature. For example, capability information may indicate capabilities and / or parameters associated with NES, with the use of additional PRACH resources, or with the activation or deactivation of additional PRACH resources. One or more operations described herein may be based on the capability information in the capability report. For example, the UE may perform communication based on the capability information, or may receive configuration information based on the capability information.

[0133] In some aspects, the configuration information and / or capability report described in conjunction with reference to reference numeral 510 may include information transmitted via multiple communications. Additionally or alternatively, the network node may transmit the configuration information or communications including at least a portion of the configuration information before and / or after the UE transmits the capability report. For example, the network node may transmit a first portion of the configuration information before the capability report, the UE may transmit at least a portion of the capability report, and the network node may transmit a second portion of the configuration information after receiving the capability report.

[0134] By increasing the temporal density of PRACH resources through the use of additional PRACH resources, the described technique can be used to reduce access latency. Furthermore, by selectively masking and / or activating / deactivating additional PRACH resources, the described technique can be used to balance access latency with NES (Network Escalation and Retrieval).

[0135] As indicated above, Figure 5 This is provided as an example. Other examples are available relative to... Figure 5 The examples described are different.

[0136] Figure 6This is an illustration of example 600 associated with a configuration of PRACH resources according to this disclosure. As described herein, the UE may be configured with a PRACH configuration index table that includes PRACH configuration indexes corresponding to PRACH configurations. Figure 6 PRACH configurations 605 and 610 in the time domain are shown. PRACH configurations 605 and 610 are shown in relation to radio frames divided into multiple subframes (numbered 0 to 9), where the duration of each subframe can be 1 ms.

[0137] PRACH configuration 605 can be configured for legacy UEs. For example, PRACH configuration 605 may correspond to a PRACH configuration index configured for a legacy UE (e.g., TDD PRACH configuration index "3"). PRACH configuration 605 is shown as having a 20ms PRACH configuration periodicity and RO 606 in the PRACH resources in subframe 9. PRACH configuration 605 also shows SSB 607 (e.g., 8 SSBs) transmitted in subframes 0 and 1 and SIB1 608 (e.g., 8 SIB1 608 corresponding to the 8 SSBs 607) transmitted in subframes 5 through 8.

[0138] PRACH configuration 610 can be configured for a UE with NES capability. For example, PRACH configuration 610 may correspond to a PRACH configuration index (e.g., TDD PRACH configuration index "17") configured for a UE with NES capability. PRACH configuration 610 is shown as having a 10ms PRACH configuration periodicity and RO 611 in the PRACH resources in subframes 4 and 9. PRACH configuration 610 also shows SSB 612 (e.g., 8 SSBs) transmitted in subframes 0 and 1 and SIB1613 (e.g., 8 SIB1 613 corresponding to the 8 SSBs 612) transmitted in subframes 5 through 8. As shown, PRACH configuration 610 includes the PRACH resources of PRACH configuration 605 (shown in striped shading) and includes additional PRACH resources (shown in solid line shading).

[0139] As indicated above, Figure 6 This is provided as an example. Other examples are available relative to... Figure 6 The examples described are different.

[0140] Figure 7 This is an illustration of example 700 associated with RO masking of PRACH resources according to this disclosure. Figure 7 The PRACH configuration 610 is shown. (As combined with...) Figure 6As described, PRACH configuration 610 includes the PRACH resources of PRACH configuration 605 (shown in striped shading) and includes additional PRACH resources (shown in solid line shading). Figure 7 A RO masking 705 applied to a PRACH configuration 610 is shown. As described herein, the RO masking 705 can be applied to additional PRACH resources. Thus, for example, with the RO masking 705 applied, RO 611 in a first and second (temporally) additional PRACH resource can be unmuteed, and RO 611 in a third (temporally) additional PRACH resource can be muted.

[0141] As indicated above, Figure 7 This is provided as an example. Other examples are available relative to... Figure 7 The examples described are different.

[0142] 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 an availability indication for PRACH resources.

[0143] like Figure 8 As shown, in some aspects, process 800 may include receiving configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission (block 810). For example, the UE (e.g., using...) Figure 10 The receiving component 1002 and / or communication manager 1006 depicted herein may receive configuration information that: indicates a first PRACH configuration indicating one or more PRACH resources; indicates a second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission, as described above.

[0144] like Figure 8 As further shown, in some aspects, process 800 may include sending PRACH communication based on configuration information (block 820). For example, the UE (e.g., using...) Figure 10 The transmitting component 1004 and / or the communication manager 1006 described above can transmit PRACH communication according to configuration information.

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

[0146] In the first aspect, the first PRACH configuration is used for the first UE, and the second PRACH configuration is used for the second UE.

[0147] In the second aspect, either alone or in combination with the first aspect, the first PRACH configuration is used for legacy UEs, and the second PRACH configuration is used for UEs with NES capability.

[0148] In the third aspect, either alone or in combination with one or more of the first and second aspects, the instruction indicates that it is to be applied to the masking of one or more additional PRACH resources.

[0149] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the configuration information further indicates the set of SSBs actually transmitted, and a subset of the set of SSBs actually transmitted for SSB-to-RO mapping for additional PRACH resources.

[0150] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the instruction indicates the activation or deactivation of one or more additional PRACH resources.

[0151] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the instruction is in the SIB or RRC message.

[0152] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indication in the SIB, and for the UE, is that paging for SIB updates indicating only the activation or deactivation of one or more additional PRACH resources is suppressed.

[0153] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the indication is in a DCI message for at least one of the paging early indication or TRS availability indication.

[0154] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication includes a first indication in an SIB or RRC message and a second indication in a DCI message for at least one of a paging early indication or a TRS availability indication.

[0155] In the tenth aspect, the instruction is given alone or in combination with one or more of the first to ninth aspects in the paging DCI message.

[0156] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the paging DCI message lacks a TRS availability indication, or includes a TRS availability indication using a number of indication bits that meet a threshold.

[0157] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the number of bits for one or more additional PRACH resources is based on the number of ROs or PRACH slots for one or more additional PRACH resources within a PRACH period defined by the first PRACH configuration.

[0158] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the number of bits for one or more additional PRACH resources is based on the number of ROs or PRACH slots for one or more additional PRACH resources within a PRACH period defined by the second PRACH configuration.

[0159] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, if one or more additional PRACH resources indicated by the second PRACH configuration are activated, the configuration information additionally indicates whether one or more PRACH resources indicated by the first PRACH configuration can be used for PRACH transmission.

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

[0161] 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 this disclosure. Example process 900 is an example in which a device or network node (e.g., network node 110) performs operations associated with an availability indication for a PRACH resource.

[0162] like Figure 9As shown, in some aspects, process 900 may include sending configuration information to the UE, the configuration information indicating: a first PRACH configuration indicating one or more PRACH resources; an indication of a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission (box 910). For example, a network node (e.g., using...) Figure 11 The transmitting component 1104 and / or communication manager 1106 depicted herein can transmit configuration information to the UE, the configuration information indicating a first PRACH configuration that indicates one or more PRACH resources; indicating a second PRACH configuration that indicates one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission, as described above.

[0163] like Figure 9 As further shown, in some aspects, process 900 may include receiving PRACH communication based on configuration information (box 920). For example, a network node (e.g., using...) Figure 11 The receiving component 1102 and / or communication manager 1106 depicted herein can receive PRACH communication according to configuration information, as described above.

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

[0165] In the first aspect, the first PRACH configuration is used for the first UE, and the second PRACH configuration is used for the second UE.

[0166] In the second aspect, either alone or in combination with the first aspect, the first PRACH configuration is used for legacy UEs, and the second PRACH configuration is used for UEs with NES capability.

[0167] In the third aspect, either alone or in combination with one or more of the first and second aspects, the instruction indicates that it is to be applied to the masking of one or more additional PRACH resources.

[0168] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the configuration information further indicates the set of SSBs actually transmitted, and a subset of the set of SSBs actually transmitted for SSB-to-RO mapping for additional PRACH resources.

[0169] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the instruction indicates the activation or deactivation of one or more additional PRACH resources.

[0170] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the instruction is in the SIB or RRC message.

[0171] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indication in the SIB, and for the UE, is that paging for SIB updates indicating only the activation or deactivation of one or more additional PRACH resources is suppressed.

[0172] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the indication is in a downlink control information message for at least one of the paging early indication or the tracking reference signal availability indication.

[0173] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication includes a first indication in an SIB or RRC message and a second indication in a DCI message for at least one of a paging early indication or a TRS availability indication.

[0174] In the tenth aspect, the instruction is given alone or in combination with one or more of the first to ninth aspects in the paging DCI message.

[0175] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the paging DCI message lacks a TRS availability indication, or includes a TRS availability indication using a number of indication bits that meet a threshold.

[0176] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the number of bits for one or more additional PRACH resources is based on the number of ROs or PRACH slots for one or more additional PRACH resources within a PRACH period defined by the first PRACH configuration.

[0177] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the number of bits for one or more additional PRACH resources is based on the number of ROs or PRACH slots for one or more additional PRACH resources within a PRACH period defined by the second PRACH configuration.

[0178] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, if one or more additional PRACH resources indicated by the second PRACH configuration are activated, the configuration information additionally indicates whether one or more PRACH resources indicated by the first PRACH configuration can be used for PRACH transmission.

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

[0180] 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 use receiving component 1002 and transmitting component 1004 to communicate with another device 1008 (such as UE or network node (such as CU, DU, RU or base station)).

[0181] In some respects, device 1000 can be configured to perform the functions described herein. Figures 5 to 7 One or more operations as 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 800) or a combination thereof. 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.

[0182] 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 (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the 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.

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

[0184] 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 receiving component 1002 to receive communication and / or the transmitting component 1004 to transmit communication. 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 receiving and / or transmitting of communication.

[0185] The receiving component 1002 can receive configuration information that: indicates a first PRACH configuration, which indicates one or more PRACH resources; indicates a second PRACH configuration, which indicates one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission. The transmitting component 1004 can transmit PRACH communication according to the configuration information.

[0186] Figure 10 The number and arrangement of components shown are provided as an example. In reality, with... Figure 10 Compared to the components shown, there may be 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.

[0187] 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 use receiving component 1102 and transmitting component 1104 to communicate with another device 1108 (such as UE or network node (such as CU, DU, RU or base station)).

[0188] In some respects, device 1100 can be configured to perform the functions described herein. Figures 5 to 7 One or more operations described herein. Additionally or alternatively, device 1100 may be configured to perform one or more processes described herein (such as...). Figure 9 The process 900) or a combination thereof. 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 2Implementation 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.

[0189] 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 (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... Figure 2 The described network node 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. 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.

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

[0191] 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 receiving component 1102 to receive communication and / or the transmitting component 1104 to transmit communication. 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 receiving and / or transmitting of communication.

[0192] The transmitting component 1104 can transmit configuration information to the UE, which includes: indicating a first PRACH configuration that indicates one or more PRACH resources; indicating a second PRACH configuration that indicates one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for transmission. The receiving component 1102 can receive PRACH communication according to the configuration information.

[0193] Figure 11 The number and arrangement of components shown are provided as an example. In reality, with... Figure 11 Compared to the components shown, there may be 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 11 Another set of components shown performs one or more functions.

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

[0195] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving configuration information, the configuration information indicating a first physical random access channel (PRACH) configuration, the first physical random access channel (PRACH) configuration indicating one or more PRACH resources; indicating a second PRACH configuration, the second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; and transmitting PRACH communication according to the configuration information.

[0196] Aspect 2: According to the method of aspect 1, wherein the first PRACH configuration is used for the first UE, and the second PRACH configuration is used for the second UE.

[0197] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the first PRACH configuration is for a legacy UE and the second PRACH configuration is for a UE with Network Energy Saving (NES) capability.

[0198] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the indication indicates to be applied to the masking of the one or more additional PRACH resources.

[0199] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the configuration information further indicates: a set of actual transmitted synchronization signal blocks (SSBs), and a subset of the set of actual transmitted SSBs for SSB-to-random access channel timing (RO) mapping for the additional PRACH resources.

[0200] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the indication indicates the activation or deactivation of the one or more additional PRACH resources.

[0201] Aspect 7: The method according to aspect 6, wherein the indication is in a System Information Block (SIB) or Radio Resource Control message.

[0202] Aspect 8: The method according to aspect 7, wherein the indication is in the SIB, and wherein, for the UE, paging for SIB updates indicating only the activation or deactivation of the one or more additional PRACH resources is suppressed.

[0203] Aspect 9: The method according to any one of Aspects 6 to 8, wherein the indication is in a downlink control information message for at least one of paging early indication or tracking reference signal availability indication.

[0204] Aspect 10: The method according to any one of Aspects 6 to 9, wherein the indication includes a first indication in a System Information Block (SIB) or Radio Resource Control message, and a second indication in a Downlink Control Information message for at least one of Paging Early Indication or Tracking Reference Signal Availability Indication.

[0205] Aspect 11: The method according to any one of Aspects 6 to 10, wherein the indication is in the paging downlink control information (DCI) message.

[0206] Aspect 12: According to the method of aspect 11, the paging DCI message lacks a tracking reference signal (TRS) availability indication, or includes a TRS availability indication using a number of indication bits that meet a threshold.

[0207] Aspect 13: The method according to any one of Aspects 6 to 12, wherein the number of bits for the one or more additional PRACH resources is the number of ROs or the number of PRACH slots for the one or more additional PRACH resources within a PRACH period defined by the first PRACH configuration.

[0208] Aspect 14: The method according to any one of Aspects 6 to 12, wherein the number of bits for the one or more additional PRACH resources is the number of ROs or the number of PRACH slots for the one or more additional PRACH resources within a PRACH period defined by the second PRACH configuration.

[0209] Aspect 15: The method according to any one of Aspects 1 to 14, wherein, when the one or more additional PRACH resources indicated by the second PRACH configuration are activated, the configuration information additionally indicates whether the one or more PRACH resources indicated by the first PRACH configuration can be used for PRACH transmission.

[0210] Aspect 16: A method for wireless communication performed by a network node, the method comprising: transmitting configuration information to a user equipment (UE), the configuration information indicating: a first physical random access channel (PRACH) configuration indicating one or more PRACH resources; indicating a second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; and receiving PRACH communication according to the configuration information.

[0211] Aspect 17: The method according to aspect 16, wherein the first PRACH configuration is used for the first UE, and the second PRACH configuration is used for the second UE.

[0212] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the first PRACH configuration is for a legacy UE and the second PRACH configuration is for a UE with Network Energy Saving (NES) capability.

[0213] Aspect 19: The method according to any one of Aspects 16 to 18, wherein the indication indicates a mask to be applied to the one or more additional PRACH resources.

[0214] Aspect 20: The method according to any one of Aspects 16 to 19, wherein the configuration information further indicates: a set of actual transmitted synchronization signal blocks (SSBs), and a subset of the set of actual transmitted SSBs for SSB-to-random access channel timing (RO) mapping for the additional PRACH resources.

[0215] Aspect 21: The method according to any one of Aspects 16 to 20, wherein the indication indicates the activation or deactivation of the one or more additional PRACH resources.

[0216] Aspect 22: The method according to aspect 21, wherein the indication is in a System Information Block (SIB) or Radio Resource Control message.

[0217] Aspect 23: The method according to aspect 22, wherein the indication is in the SIB, and wherein, for the UE, paging for SIB updates indicating only the activation or deactivation of the one or more additional PRACH resources is suppressed.

[0218] Aspect 24: The method according to any one of Aspects 21 to 23, wherein the indication is in a downlink control information message for at least one of paging early indication or tracking reference signal availability indication.

[0219] Aspect 25: The method according to any one of Aspects 21 to 24, wherein the indication includes a first indication in a System Information Block (SIB) or Radio Resource Control message, and a second indication in a Downlink Control Information message for at least one of Paging Early Indication or Tracking Reference Signal Availability Indication.

[0220] Aspect 26: The method according to any one of Aspects 21 to 25, wherein the indication is in a paging downlink control information (DCI) message.

[0221] Aspect 27: According to the method of aspect 26, the paging DCI message lacks a tracking reference signal (TRS) availability indication, or includes a TRS availability indication using a number of indication bits that meet a threshold.

[0222] Aspect 28: The method according to any one of Aspects 21 to 27, wherein the number of bits for the one or more additional PRACH resources is the number of ROs or the number of PRACH slots for the one or more additional PRACH resources within a PRACH period defined by the first PRACH configuration.

[0223] Aspect 29: The method according to any one of Aspects 21 to 27, wherein the number of bits for the one or more additional PRACH resources is the number of ROs or the number of PRACH slots for the one or more additional PRACH resources within a PRACH period defined by the second PRACH configuration.

[0224] Aspect 30: The method according to any one of aspects 16 to 29, wherein, when the one or more additional PRACH resources indicated by the second PRACH configuration are activated, the configuration information additionally indicates whether the one or more PRACH resources indicated by the first PRACH configuration can be used for PRACH transmission.

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

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

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

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

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

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

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

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

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

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

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

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

[0237] 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured individually or in any combination to: Receive configuration information, wherein the configuration information: indicates a first physical random access channel (PRACH) configuration, the first physical random access channel (PRACH) configuration indicating one or more PRACH resources; indicates a second PRACH configuration, the second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; as well as Send PRACH communication according to the configuration information.

2. The apparatus of claim 1, wherein the first PRACH is configured for the first UE, and the second PRACH is configured for the second UE.

3. The apparatus of claim 1, wherein the first PRACH configuration is for a legacy UE, and the second PRACH configuration is for a UE with Network Energy Saving (NES) capability.

4. The apparatus of claim 1, wherein the indication indicates to be applied to the masking of the one or more additional PRACH resources.

5. The apparatus of claim 1, wherein, when the one or more additional PRACH resources indicated by the second PRACH configuration are activated, the configuration information additionally indicates whether the one or more PRACH resources indicated by the first PRACH configuration can be used for PRACH transmission.

6. The apparatus of claim 1, wherein the configuration information further indicates: The actual set of transmitted synchronization signal blocks (SSBs), and The subset of the set of SSBs actually transmitted for the SSB-to-Random Access Channel Timing (RO) mapping for the additional PRACH resources.

7. The apparatus of claim 1, wherein the indication indicates the activation or deactivation of the one or more additional PRACH resources.

8. The apparatus of claim 7, wherein the indication is in a System Information Block (SIB) or Radio Resource Control message.

9. The apparatus of claim 8, wherein the indication is in the SIB, and For the UE, paging for SIB updates that only indicate the activation or deactivation of the one or more additional PRACH resources is suppressed.

10. The apparatus of claim 7, wherein the indication is in a downlink control information message for at least one of paging early indication or tracking reference signal availability indication.

11. The apparatus of claim 7, wherein the indication comprises a first indication in a System Information Block (SIB) or Radio Resource Control message, and a second indication in a downlink control information message for at least one of Paging Early Indication or Tracking Reference Signal Availability Indication.

12. The apparatus of claim 7, wherein the indication is in a paging downlink control information (DCI) message.

13. The apparatus of claim 12, wherein the paging DCI message lacks a Tracking Reference Signal (TRS) availability indication, or includes a TRS availability indication using a number of indication bits that meet a threshold.

14. The apparatus of claim 7, wherein the number of bits for the one or more additional PRACH resources is based on the number of random access channel opportunities (ROs) or the number of PRACH slots for the one or more additional PRACH resources within a PRACH period defined by the first PRACH configuration.

15. The apparatus of claim 7, wherein the number of bits for the one or more additional PRACH resources is the number of random access channel opportunities (ROs) or the number of PRACH slots for the one or more additional PRACH resources within a PRACH period defined by the second PRACH configuration.

16. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive configuration information, wherein the configuration information: indicates a first physical random access channel (PRACH) configuration, the first physical random access channel (PRACH) configuration indicating one or more PRACH resources; indicates a second PRACH configuration, the second PRACH configuration indicating one or more additional PRACH resources; and includes an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; as well as Send PRACH communication according to the configuration information.

17. The method of claim 16, wherein the indication indicates a mask to be applied to the one or more additional PRACH resources.

18. The method of claim 16, wherein the indication indicates the activation or deactivation of the one or more additional PRACH resources.

19. An apparatus for wireless communication, the apparatus comprising: A component for receiving configuration information, the configuration information including: an indication of a first physical random access channel (PRACH) configuration, the first physical random access channel (PRACH) configuration indicating one or more PRACH resources; an indication of a second PRACH configuration, the second PRACH configuration indicating one or more additional PRACH resources; and including an indication of which of the one or more additional PRACH resources can be used for PRACH transmission; as well as A component used to send PRACH communications based on the configuration information.

20. The apparatus of claim 19, wherein the indication indicates to be applied to the masking of the one or more additional PRACH resources.

Images