Early termination of random access response decoding

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an indication of whether a random access response (RAR) is for a first UE type, a second UE type, or both the first UE type and the second UE type. The UE may decode the RAR or skip decoding of the RAR according to the indication and based at least in part on whether the UE is associated with the first UE type or the second UE type. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for early termination of random access response (RAR) decoding. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0003] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continued desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0004] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication of whether a random access response (RAR) is for a first UE type, a second UE type, or both the first UE type and the second UE type. The method may include decoding the RAR or skipping decoding the RAR based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type.

[0005] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include outputting an indication of whether a RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type. The method may include outputting a RAR associated with a UE based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type.

[0006] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those methods described herein with reference to the accompanying drawings and as illustrated in the accompanying drawings; a non-transitory computer-readable medium comprising processor-executable instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those methods described herein with reference to the accompanying drawings and as illustrated in the accompanying drawings; a computer program product embodied on a computer-readable storage medium, the computer-readable storage medium comprising code for performing the foregoing methods and those methods described herein with reference to the accompanying drawings and as illustrated in the accompanying drawings; and / or an apparatus comprising components for performing the foregoing methods and those methods described herein with reference to the accompanying drawings and as illustrated in the accompanying drawings. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0007] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily utilized as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0008] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0010] Figure 1 An example of a wireless communication network in accordance with the present disclosure is depicted.

[0011] Figure 2 Aspects of example base stations and user equipment (UE) according to the present disclosure are depicted.

[0012] Figure 3 An example disaggregated base station architecture is depicted.

[0013] Figure 4A , Figure 4B , Figure 4C and Figure 4D

[0013] Aspects of a data structure for a wireless communication network according to the present disclosure are depicted.

[0014] Figure 5 is a diagram illustrating an example of a two-step random access procedure according to the present disclosure.

[0015] Figure 6is a diagram illustrating an example of a four-step random access procedure according to the present disclosure.

[0016] Figure 7 is a diagram illustrating an example of physical downlink control channel (PDCCH) communication scheduling a physical downlink shared channel (PDSCH) communication carrying a random access response (RAR) according to the present disclosure.

[0017] Figure 8 is a diagram of an example of signaling for indicating whether the RAR is for the first UE type or the second UE type according to the present disclosure.

[0018] Fig. 9 is a diagram illustrating an example of indicating a UE type of a RAR via a Radio Network Temporary Identifier (RNTI) distinction according to the present disclosure.

[0019] Fig.10 is a diagram illustrating an example of indicating a UE type of RAR through RAR window differentiation according to the present disclosure.

[0020] Fig.11 A method of wireless communication by a UE according to the present disclosure is shown.

[0021] Fig.12 A method of wireless communication by a network entity according to the present disclosure is shown.

[0022] Fig.13 Aspects of an example communication device according to the present disclosure are depicted.

[0023] Fig.14 Aspects of an example communication device according to the present disclosure are depicted. DETAILED DESCRIPTION

[0024] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for early termination of random access response (RAR) decoding.

[0025] Different devices may have different capabilities and / or features. For example, different user equipment (UE) using 5G radio access technology (RAT) may have different capabilities and / or feature sets. A UE with a specific capability and / or feature set may be considered to have a specific UE type. Different UEs may have different UE types. For example, a UE with a first UE type may have a first capability, such as a first capability for a radio frequency (RF) bandwidth and / or a baseband (BB) bandwidth, and a UE with a second UE type may have a second capability, such as a second capability for an RF bandwidth and / or a BB bandwidth. In some aspects, a UE with a first UE type may be referred to as an enhanced mobile broadband (eMBB) UE or a reduced capability (RedCap) UE, and a UE with a second UE type may be referred to as an enhanced RedCap (eRedCap) UE. Distinguishing UEs by UE type may enable the deployment of different categories of UEs, such as UEs that provide support for more complex features of NR (such as user-oriented smartphones) and UEs that provide relatively low cost, energy consumption, and data rate requirements (such as industrial wireless sensors, wearable devices, monitoring equipment, etc.).

[0026] There is a situation where a UE of a first UE type may be able to decode a communication while a UE of a second UE type cannot decode the communication. For example, the communication may have a bandwidth that exceeds the capabilities of the second UE type and is within the capabilities of the first UE type. In addition, if a UE of a first UE type decodes a communication for a UE of a second UE type (so that the communication complies with the less complex capabilities of the second UE type), the power and decoding resources of the UE of the first type may be inefficiently utilized. An example of such a communication is RAR. The RAR may be scheduled by downlink control information (DCI) received via a physical downlink control channel (PDCCH). The UE may first receive the DCI and then may receive the RAR. However, in some configurations, there may be ambiguity as to whether the RAR is for a UE of a first UE type or a UE of a second UE type. If the bandwidth of the RAR exceeds the bandwidth capabilities of the second UE type, the UE of the second UE type may not be able to decode the RAR, and therefore may use power and decoding resources. If the bandwidth of the RAR is within the bandwidth capabilities of the second UE type and for a UE of the second UE type, the UE of the first UE type may use power and decoding resources to incorrectly decode the RAR.

[0027] Some techniques described herein provide early termination of decoding of a RAR. As used herein, "early termination" may refer to skipping (e.g., canceling, ending) decoding of a RAR or information provided in a RAR before decoding of the RAR is completed. For example, a UE may terminate decoding of a RAR based on an indication of whether the RAR is associated with a UE type of the UE. The indication may take various forms, as described elsewhere herein. The indication may allow the UE to skip decoding of the RAR entirely, or terminate decoding of the RAR before decoding of the RAR is completed. Thus, power and decoding resources of the UE are saved (such as when the RAR exceeds the capabilities of the UE or when the RAR is not intended for the UE).

[0028] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functionality, or structure and functionality other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) RATs, various aspects of the present disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or post-5G RATs (e.g., 6G).

[0031] Figure 1 An example of a wireless communication network 100 according to the present disclosure is depicted.

[0032] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., a UE, a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 110), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) that can communicate with other network elements (e.g., ground BSs) and user equipment.

[0033] In the depicted example, the wireless communication network 100 includes a BS 110, a UE 120, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0034] Figure 1 Various example UEs 120 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or another similar device. UE 120 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, or a handset, etc.

[0035] BS 110 may wirelessly communicate with (e.g., send signals to or receive signals from) UE 120 via communication link 170. Communication link 170 between BS 110 and UE 120 may carry uplink (UL) (also referred to as a reverse link) transmissions from UE 120 to BS 110 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 110 to UE 120. In various aspects, communication link 170 may employ multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0036] BS 110 may generally include, for example, a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a transmission reception point, and / or the like. BS 110 may provide communication coverage for a corresponding geographic coverage area 112, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell provided by BS 110a may have a coverage area 112' that overlaps with a coverage area 112 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0037] Although BS110 is depicted as a single communication device in various aspects, BS110 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS110) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functions similar to those of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 3 An example decomposed base station architecture is depicted and described.

[0038] Different BSs 110 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 110 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 110 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 110 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0039] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, the Third Generation Partnership Project (3GPP) currently defines frequency range 1 (FR1) as including 410 MHz to 7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS110b) configured to communicate using mmWave or near mmWave radio bands may utilize beamforming (e.g., as shown by 182) with a UE (e.g., 120) to improve path loss and range.

[0040] The communication link 170 between the BS 110 and, for example, the UE 120 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other bandwidths) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. In some examples, the allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0041] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Accordingly, some base stations (e.g., Figure 1182 ′. The base station 110b in the example embodiment may utilize beamforming with the UE 120 to improve path loss and range, as shown at 182. For example, the BS 110b and the UE 120 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 110b may transmit beamformed signals to the UE 120 in one or more transmit directions 182′. The UE 120 may receive the beamformed signals from the BS 110b in one or more receive directions 182″. The UE 120 may also transmit beamformed signals to the BS 110b in one or more transmit directions 182″. The BS 110b may also receive beamformed signals from the UE 120 in one or more receive directions 182′. The BS 110b and the UE 120 may then perform beam training to determine the best receive and transmit directions for each of the BS 110b and the UE 120. It is noteworthy that the transmit direction and receive direction of the BS 110b may be the same or may not be the same. Similarly, the transmit direction and receive direction of UE 120 may or may not be the same.

[0042] The wireless communication network 100 further includes a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0043] Certain UEs 120 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0044] The EPC 160 may include various functional components, including: a mobility management entity (MME) 161, other MMEs 162, a serving gateway 163, a multimedia broadcast multicast service (MBMS) gateway 164, a broadcast multicast service center (BM-SC) 165, and / or a packet data network (PDN) gateway 166, such as in the depicted example. The MME 161 may communicate with a home subscriber server (HSS) 167. The MME 161 is a control node that handles signaling between the UE 120 and the EPC 160. In general, the MME 161 provides bearer and connection management.

[0045] Generally, user Internet Protocol (IP) packets are delivered through a Serving Gateway 163, which itself is connected to a PDN Gateway 166. The PDN Gateway 166 provides UE IP address allocation and other functions. The PDN Gateway 166 and the BM-SC 165 are connected to IP Services 168, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0046] The BM-SC 165 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 165 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 164 may be used to distribute MBMS services to BSs 110 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0047] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 191, other AMFs 192, session management functions (SMF) 193, and user plane functions (UPF) 194. AMF 191 may communicate with unified data management (UDM) 195.

[0048] AMF 191 is a control node that processes signaling between UE 120 and 5GC 190. AMF 191 provides, for example, Quality of Service (QoS) flow and session management.

[0049] IP packets are delivered through UPF 194, which is connected to IP services 196 and provides UE IP address allocation and other functions for 5GC 190. IP services 196 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0050] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, or a transmit receive point (TRP), to name a few examples.

[0051] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0052] Figure 2 Aspects of an example BS 110 and UE 120 according to the present disclosure are depicted.

[0053] In general, BS 110 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a-234t (collectively 234), transceivers 232a-232t (collectively 232) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data sink 239). For example, BS 110 can transmit and receive data between BS 110 and UE 120. BS 110 includes controller / processor 240 that can be configured to implement various functions described herein related to wireless communication.

[0054] Generally speaking, the UE 120 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-252r (collectively, 252), transceivers 254a-254r (collectively, 254) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 262) and wireless reception of data (e.g., provided to a data sink 260). The UE 120 includes a controller / processor 280 that may be configured to implement various functions described herein related to wireless communications.

[0055] Regarding example downlink transmissions, BS 110 includes a transmit processor 220 that can receive data from a data source 212 and control information from a controller / processor 240. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a PDCCH, a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0056] The transmit processor 220 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS)).

[0057] The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in the transceiver 232a-232t. Each modulator in the transceiver 232a-232t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0058] To receive downlink transmissions, UE 120 includes antennas 252a-252r that can receive downlink signals from BS 110 and can provide received signals to demodulators (DEMODs) in transceivers 254a-254r, respectively. Each demodulator in transceivers 254a-254r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0059] A MIMO detector 256 may obtain received symbols from all demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0060] For example uplink transmissions, the UE 120 also includes a transmit processor 264 that can receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 can also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modulators in the transceivers 254a-254r (e.g., for SC-FDM), and transmitted to the BS 110.

[0061] At BS 110, uplink signals from UE 120 may be received by antennas 234a-234t, processed by demodulators in transceivers 232a-232t, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. Memory 242 and memory 282 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0062] In various aspects, the BS 110 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 212, a scheduler 244, a memory 242, a transmit processor 220, a controller / processor 240, a TX MIMO processor 230, a transceiver 232a-232t, an antenna 234a-234t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 234a-234t, a transceiver 232a-232t, a RX MIMO detector 236, a controller / processor 240, a receive processor 238, a scheduler 244, a memory 242, and / or other aspects described herein.

[0063] In various aspects, the UE 120 may also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from a data source 262, a memory 282, a transmit processor 264, a controller / processor 280, a TX MIMO processor 266, a transceiver 254a-254t, an antenna 252a-252t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 252a-252t, a transceiver 254a-254t, a RX MIMO detector 256, a controller / processor 280, a receive processor 258, a memory 282, and / or other aspects described herein.

[0064] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0065] Although Figure 2The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0066] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0067] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an AP, a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0068] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0069] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0070] Figure 3 An example disaggregated base station 300 architecture is depicted. The disaggregated base station 300 architecture may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units, such as a near real-time (near RT) RIC 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0071] Each of the units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides processor-executable instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0072] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0073] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, DU 330 may host one or more of the following: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split (such as that defined by 3GPP). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0074] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0075] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0076] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0077] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0078] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0079] Figure 4A , Figure 4B , Figure 4C and Figure 4D Described is a method for use in a wireless communication network (such as Figure 1 Various aspects of the data structure of the wireless communication network 100). Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0080] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) will (for example, Figure 4B and Figure 4D The system bandwidth (as depicted in FIG. 1 ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0081] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also use TDD, where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0082] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and F is used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DCI or semi-statically / statically configured by RRC signaling) through a received time slot format indicator (SFI). In the depicted example, a 10ms frame is divided into 10 1ms subframes of equal size. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. A subframe may also include a micro-time slot, which typically has fewer symbols than a whole time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0083] In certain aspects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ × 15kHz, where μ is the parameter set index, which can be selected from values ​​0 to 5. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=5 is 480kHz. Other parameter sets and subcarrier spacings can be used. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0084] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted in , a resource grid may be used to represent a frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending, for example, over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0085] like Figure 4AAs illustrated, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 120). The RS may include a DMRS and / or a CSI-RS for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0086] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The PDCCH carries DCI within one or more control channel elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0087] The PSS may be within symbol 2 of a particular subframe of a frame. The PSS is used by a UE (eg, UE 120) to determine subframe / symbol timing and physical layer identification.

[0088] The SSS may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0089] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The PBCH carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system bandwidth and the number of RBs in the system frame number (SFN). The PDSCH carries user data, broadcast system information (such as a system information block (SIB)) that is not sent via the PBCH, and / or paging messages.

[0090] like Figure 4C As illustrated, some of the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. The UE 120 may send an SRS. The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0091] Figure 4DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK or negative acknowledgement (NACK) (ACK / NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0092] Figure 5 5 is a diagram illustrating an example 500 of a two-step random access procedure according to the present disclosure. Figure 5 As shown, BS 110 and UE 120 may communicate with each other to perform a two-step random access procedure.

[0093] As shown by reference numeral 505, BS 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 in system information (e.g., one or more SIBs) and / or SSBs and / or indicated by the system information and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or a PDCCH command message that triggers a random access channel (RACH) procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in a two-step random access procedure, such as one or more parameters for sending a random access message (RAM) and / or receiving a RAR to a RAM.

[0094] As shown in reference numeral 510, UE 120 may send a RAM preamble, and network entity 110 may receive the RAM preamble. As shown in reference numeral 515, UE 120 may send a RAM payload, and BS 110 may receive the RAM payload. As shown, as part of the initial (or first) step of the two-step random access process, UE 120 may send a RAM preamble and a RAM payload to BS 110. In some aspects, RAM may be referred to as message A, msgA, a first message, or an initial message in the two-step random access process. In addition, in some aspects, the RAM preamble may be referred to as a message A preamble, a msgA preamble, a preamble, or a PRACH preamble, and the RAM payload may be referred to as a message A payload, a msgA payload, or a payload. In some aspects, RAM may include some or all of the contents of message 1 (msg1) and message 3 (msg3) of the four-step random access process described in more detail elsewhere herein. For example, the RAM preamble may include some or all of the contents of message 1 (e.g., the PRACH preamble), and the RAM payload may include some or all of the contents of message 3 (e.g., the UE identifier, UCI, and / or PUSCH transmission).

[0095] As indicated by reference numeral 520, the BS 110 may receive the RAM preamble transmitted by the UE 120. If the BS 110 successfully receives and decodes the RAM preamble, the BS 110 may then receive and decode the RAM payload.

[0096] As shown by reference numeral 525, BS 110 may send a RAR (sometimes referred to as a RAR message). As shown, BS 110 may send a RAR message as part of the second step of a two-step random access procedure. In some aspects, the RAR message may be referred to as message B, msgB, or a second message in a two-step random access procedure. The RAR message may include some or all of the contents of message 2 (msg2) and message 4 (msg4) of a four-step random access procedure. For example, the RAR message may include a detected PRACH preamble identifier, a detected UE identifier, a timing advance value, and / or contention resolution information.

[0097] As shown by reference numeral 530, as part of the second step of the two-step random access procedure, BS 110 may send a PDCCH communication for the RAR. The PDCCH communication may schedule a PDSCH communication including the RAR. For example, the PDCCH communication may indicate a resource allocation (e.g., in a DCI) for the PDSCH communication.

[0098] As part of the second step of the two-step random access procedure, BS 110 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication, as shown by reference numeral 535. The RAR may be included in a MAC protocol data unit (PDU) of the PDSCH communication. As shown by reference numeral 540, if UE 120 successfully receives the RAR, UE 120 may send a HARQ acknowledgement (ACK).

[0099] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0100] Figure 6 is a diagram illustrating an example of a four-step random access procedure according to the present disclosure. Figure 6 As shown, BS 110 and UE 120 may communicate with each other to perform a four-step random access procedure.

[0101] As shown by reference numeral 605, BS 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 in system information (e.g., one or more SIBs) and / or SSBs and / or indicated by the system information and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or a PDCCH command message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in the random access process, such as one or more parameters for sending a RAM and / or one or more parameters for receiving a RAR.

[0102] As shown by reference numeral 610, UE 120 may send a RAM, which may include a preamble (sometimes referred to as a random access preamble, a PRACH preamble, or a RAM preamble). The message including the preamble may be referred to as message 1, msg1, MSG1, a first message, or an initial message in the four-step random access procedure. The random access message may include a random access preamble identifier.

[0103] As shown by reference numeral 615, BS 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 a second message in the four-step random access procedure. In some aspects, the RAR may indicate a detected random access preamble identifier (e.g., received from UE 120 in msg1). Additionally or alternatively, the RAR may indicate a resource allocation to be used by UE 120 to send message 3 (msg3).

[0104] In some aspects, as part of the second step of the four-step random access procedure, BS 110 may send a PDCCH communication for the RAR. The PDCCH communication may schedule a PDSCH communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. Also as part of the second step of the four-step random access procedure, BS 110 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in the MAC PDU of the PDSCH communication.

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

[0106] As shown by reference numeral 625, BS 110 may send an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or a fourth message of the four-step random access procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, and / or contention resolution information. As shown by reference numeral 630, if UE 120 successfully receives the RRC connection setup message, UE 120 may send a HARQ ACK.

[0107] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0108] Figure 7 700 is a diagram illustrating an example of a PDCCH communication 710 for scheduling a PDSCH communication carrying a RAR 720 according to the present disclosure. As shown, the PDCCH communication may include a DMRS. The DMRS is a reference signal for demodulating the PDCCH communication. As further shown, the PDCCH communication may carry a DCI. The DCI may include scheduling information for scheduling the PDSCH communication carrying the RAR 720. The DCI may be encoded using a cyclic redundancy check (CRC). The CRC is a value generated using an error detection code (e.g., a cyclic code). The CRC may be generated based at least in part on the content of a data block (e.g., a DCI, an encoded version of the DCI) and may be appended to the data block. The RAR 720 may include, for example, a RACH msg2 (in combination with Figure 5 Description) or RACH msgB (combined Figure 6Description). In some aspects, UEs of the first UE type and the second UE type may be configured with overlapping or partially overlapping initial bandwidth part (BWP) resources (e.g., downlink and uplink BWP resources) and random access resources (including PRACH opportunities, CORESET and / or common search space) in the time domain and / or frequency domain.

[0109] The present disclosure describes UEs of a first UE type and a second UE type. A UE of the first UE type may have a first capability (e.g., a first bandwidth capability, etc.), and a UE of the second UE type may have a second capability (e.g., a second bandwidth capability, etc.). In some aspects, the first UE type may include an eMBB UE and / or a RedCap UE. In some aspects, the second UE type may include an eRedCap UE. In some aspects, the first UE type may have an RF bandwidth capability of at least 20 MHz for uplink and downlink communications. The RF bandwidth capability may indicate the maximum bandwidth (e.g., the maximum configurable initial bandwidth) of a BWP or a carrier of the first UE type. In some aspects, a RedCap UE (of the first UE type) or an eRedCap UE (of the second UE type) may be configured with an initial RF bandwidth of up to 20 MHz. In some aspects, the second UE type may have a BB bandwidth capability of 5 MHz for PDSCH (e.g., for unicast and broadcast) and for PUSCH. The BB bandwidth capability may indicate the maximum bandwidth or supported bandwidth for a specific channel or communication at the baseband. In some aspects, for physical channels and signals other than PDSCH and PUSCH, the second UE type may have a BB bandwidth capability equal to the RF bandwidth capability.In some examples, the first UE type may be referred to as a legacy UE type, and the second UE type may be referred to as an eRedCap UE type.

[0110] In some aspects, the UE of the first UE type and the UE of the second UE type may share a cell definition SSB (CD-SSB) and a control resource set #0 (CORESET#0) with each other. For example, the UE of the first UE type and the UE of the second UE type may both use the same CD-SSB to identify system information block 1 (SIB1), and may receive PDCCH communications defined for PDSCH communications carrying SIB1 by monitoring the same CORESET#0.

[0111] RACH opportunity (RO) is a set of time and frequency positions that can be used for UE to send RACH preamble. In some aspects, a UE of a first UE type may share a RACH opportunity with a UE of a second UE type, so that both the UE of the first UE type and the UE of the second UE type can monitor DCI (scheduled for PDSCH communication of RAR) addressed to the same random access radio network temporary identifier (RNTI) (RA-RNTI) or the same message B RNTI. For example, RA-RNTI or message B RNTI can be a function of RACH opportunity and / or one or more other factors. In this example, different UE types may be configured with different preamble sequence groups. Therefore, for the purpose of providing RAR in response to RAM, different UE types can be distinguished via orthogonal preamble sequence resources (e.g., code division multiplexing). However, since the UE of the first UE type and the UE of the second UE type share the RACH opportunity, it may be difficult to distinguish the RAR for the UE of the first UE type from the RAR for the UE of the second type until decoding. If the bandwidth of the RAR exceeds the capabilities of the second UE type, the RAR may be decoded only by the first UE type, which uses the decoding resources of the second UE type without benefit. If the RAR is within the capabilities of the first UE type and the second UE type, the RAR may still not be distinguished as being targeted at the first UE type or the second UE type. For example, a UE of the first UE type may use power to decode a RAR that is targeted only at UEs of the second UE type, or a UE of the second UE type may use power to decode a RAR that is targeted only at UEs of the first UE type. Some of the techniques described herein provide an indication of whether the RAR is for the first UE type or the second UE type, such as associated with PDCCH communication 710 or another form of signaling. The indication may enable the UE to selectively decode the RAR or skip decoding the RAR depending on whether the UE is a first UE type, a second UE type, or both.

[0112] Although the techniques described herein apply to RACH, these techniques may be applied to procedures involving random access, such as random access-based procedures (such as small data transfers).

[0113] In some aspects, the indication may be a PDCCH communication 710, may be associated with the PDCCH communication, or may be included in the PDCCH communication. For example, the PDCCH communication 710 may be addressed to a RA-RNTI and / or a messageB-RNTI. In some aspects, the indication may include a DMRS of a PDCCH communication 710 associated with the RAR. For example, the DMRS may be generated (and / or configured with a scrambling identifier) ​​using a scrambling identifier (e.g., via system information) that indicates the UE type of the RAR. As another example, the DMRS may be generated (and / or configured with a pseudo-sequence) using a pseudo-sequence (i.e., a pseudo-random sequence) that may be indicated by system information or a wireless communication specification indicating the UE type of the RAR. As another example, the DMRS may be mapped to a resource element pattern indicating the UE type of the RAR (e.g., transmitted and received on the resource element pattern), wherein the resource element pattern is indicated by system information or a wireless communication specification.

[0114] The PDCCH communication 710 may be considered "associated" with the RAR because the PDCCH communication 710 carries the DCI that schedules the RAR. The DCI may be considered "associated" with the RAR because the DCI schedules the PDSCH communication that carries the RAR.

[0115] In some aspects, the indication may include a CRC of the DCI. For example, a CRC attachment to the DCI may use a pattern indicating the UE type of the RAR, where the pattern may be indicated by system information or a wireless communication specification.

[0116] In some aspects, the indication may include a field of the DCI. For example, one or more fields in the DCI may be scrambled or interleaved with a sequence indicating the UE type of the RAR (e.g., indicated by system information or a wireless communication specification). As another example, one or more fields in the DCI may be configured with (or may include) a bit width indicating the UE type of the RAR (e.g., a range of transport block scaling, a start and length indicator (SLIV) table indication, a range of time domain resource assignments, a range of modulation and coding schemes), where the bit width is indicated by the system information or the wireless communication specification.

[0117] In some aspects, the indication may be or include a bit. For example, the bit may indicate the UE type of the RAR. In some aspects, the bit may be a bit that is a reserved bit, such as a bit reserved for operation in a shared spectrum or a bit reserved for operation in an unlicensed spectrum.

[0118] In some aspects, if the UE monitors a DCI addressed to a common RNTI (common between UEs of the first UE type and the second UE type) (such as a RA-RNTI and / or messageB-RNTI), then if the DCI can be decoded but one or more fields in the DCI are invalid for the corresponding UE capabilities (e.g., if the frequency-domain resource allocation for the PDSCH spans a bandwidth wider than the bandwidth supported by UEs of the second UE type), the UE may skip decoding of the RAR scheduled by the DCI. In some aspects, if the UE monitors a DCI addressed to a common RNTI (common between UEs of the first UE type and the second UE type) (e.g., a RA-RNTI and / or messageB-RNTI), then if the DCI cannot be decoded by the UE (e.g., if there is a mismatch of CHEST, CRC, etc.), the UE may skip decoding of the RAR scheduled by the DCI.

[0119] In some aspects, the indication includes a PDCCH communication 710 in a CORESET indicating whether the RAR is for a first UE type, a second UE type, or both. For example, a first CORESET or a first common search space may be configured for UEs of a first UE type, and a second CORESET or a second common search space may be configured for UEs of a second UE type. In this example, the first CORESET or the first common search space may have a first configuration (e.g., indicating the first CORESET or the first common search space as being associated with a first UE type), and the second CORESET or the second common search space may have a second configuration (e.g., indicating the second CORESET or the second common search space as being associated with a second UE type). For example, the first CORESET may be mapped to a first frequency domain resource (e.g., one or more contiguous or non-contiguous RBs or RB groups), and the second CORESET may be mapped to a second frequency domain resource (e.g., one or more contiguous or non-contiguous RBs or RB groups), wherein the first frequency domain resource is associated with a first UE type and the second frequency domain resource is associated with a second UE type. As another example, a first CORESET may be quasi-co-located with a first SSB index and / or burst set, such as a CD-SSB or a non-CD-SSB (NCD-SSB), and a second CORESET may be quasi-co-located with a second SSB index and / or burst set.

[0120] In some aspects, the indication includes a PDCCH communication 710 in a search space or a search space set (e.g., a common search space (CSS) set) indicating whether the RAR is for a first UE type, a second UE type, or both. For example, a first CSS set associated with a first UE type may be configured with a first set of parameters (e.g., aggregation level, time offset, periodicity, a combination thereof, and / or another parameter), and a second CSS set associated with a second UE type may be configured with a second set of parameters different from the first set of parameters (e.g., aggregation level, time offset, periodicity, a combination thereof, and / or another parameter). These configurations may be indicated via system information. Thus, the UE may distinguish whether the PDCCH communication 710 is associated with the first UE type, the second UE type, or both, based on whether the PDCCH communication 710 is received in the first CSS set or in the second CSS set, and the UE may decode the corresponding RAR or skip decoding of the corresponding RAR.

[0121] By providing an indication in or associated with PDCCH communication 710, the UE can determine whether the RAR is for a UE of the UE type of the UE before determining whether to decode the RAR. Therefore, the UE can selectively decode the RAR or skip decoding the RAR, which improves the power utilization of the UE.

[0122] Figure 8 800 is a diagram of an example of signaling for indicating whether a RAR is for a first UE type or a second UE type according to the present disclosure. As shown, example 800 includes a UE (e.g., UE 120) and a network entity (e.g., base station 110, one or more network entities of a decomposed base station). The UE may have a UE type, such as a first UE type or a second UE type as described elsewhere herein. In example 800, the UE type is a second UE type (e.g., for an eRedCap UE).

[0123] As shown by reference numeral 810, the network entity may output an indication of whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type, and the UE may receive the indication. In some aspects, the indication may be included in a PDCCH communication (such as a communication regarding the scheduling of the RAR) Figure 7 In some aspects, the indication may be or may be included in the configuration of the RACH opportunity, such as with respect to Fig. 9 In some aspects, the indication may be included in the configuration of the RAR window, such as in Fig.10As described in Example 1000 of . In Example 800, the indication indicates that the corresponding RAR (e.g., a RAR scheduled by a PDCCH communication or DCI carrying the indication or associated with the indication, a RAR on a downlink bandwidth portion whose configuration includes the indication, a RAR with an RNTI indicating a UE type for the RAR, a RAR responding to a RACH opportunity indicating a UE type for the RAR, etc.) is for a second UE type. For example, the indication may indicate that a UE of the second UE type is to decode the RAR.

[0124] In some aspects, the indication may include one or more parameters of a downlink BWP configuration for random access. For example, a network entity may provide an RRC configuration or a DCI or MAC selection for an RRC configuration, indicating a downlink BWP configuration for random access. The downlink BWP configuration for random access may be a configuration of a BWP received for a RAM and / or PDCCH communication for a RACH process. In some aspects, one or more parameters may include bandwidth. For example, a bandwidth parameter may indicate whether the downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may indicate a starting PRB of a downlink PRB. For example, a starting PRB may indicate whether the downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may include a scheduling offset (e.g., k0). For example, a scheduling offset may indicate whether the downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may include a DCI format size for a PDCCH communication for a scheduling RAM, as indicated by a downlink BWP configuration for random access. For example, a range including a DCI format size may indicate whether a downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may include an aggregation level for PDCCH monitoring in a downlink BWP configuration for random access. For example, a range in which an aggregation level occurs may indicate whether a downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may include a time offset for PDCCH monitoring in a downlink BWP configuration for random access. For example, a range in which a time offset occurs may indicate whether a downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may include a periodicity for PDCCH monitoring in a downlink BWP configuration for random access. For example, a range in which a periodicity occurs may indicate whether a downlink BWP configuration for random access is for a first UE type or a second UE type. In some aspects, one or more parameters may include an indication of a BWP for narrowband PDSCH communication. For example, the BWP for narrowband PDSCH communication can be considered as a partial BWP for narrowband PDSCH communication (e.g., a part of the downlink BWP for random access) or a virtual BWP (e.g., a region of the downlink BWP for random access configured for a specific purpose via another BWP configuration).

[0125] As shown in reference numeral 820, the network entity may output the RAR, and the UE may receive the RAR. In some aspects, the RAR may include or be associated with the indication. For example, the RNTI of the RAR (e.g., messageB-RNTI or RA-RNTI) may include the indication. As shown by reference numeral 830, the UE may decode the RAR. For example, the UE may determine that the RAR is for a second UE type, and may decode the RAR in response to determining that the RAR is for a second UE type. In some aspects, the UE may determine that the RAR is for a first UE type. In such aspects, the UE may skip decoding the RAR. For example, the UE may skip receiving the RAR. As another example, the UE may determine that the RNTI of the RAR indicates a first UE type, and may skip or stop decoding the RAR in response to determining that the RNTI of the RAR indicates a first UE type. In this way, resources of the UE are saved relative to attempting to decode the RAR, regardless of whether the RAR is for the UE type of the UE or compatible with the UE type of the UE. In some aspects, the UE may perform an action based at least in part on decoding the RAR. For example, the UE may perform beam failure recovery. As another example, the UE may perform small data transfer. As another example, the UE may perform initial access.

[0126] Fig. 9 are diagrams illustrating examples 900 and 905 of indication of UE type of RAR differentiated via RNTI according to the present disclosure.

[0127] As described elsewhere herein, the UE may receive an indication of whether the RAR is for a first UE type or for a second UE type. In example 900, the indication is or is included in the configuration of the RACH opportunity. For example, the UE may receive configuration information indicating one or more first ROs shown by reference numeral 910 and one or more second ROs shown by reference numeral 915. The one or more first ROs may be for a RAR of a first UE type, and the one or more second ROs may be for a RAR of a second UE type. In this example, the UE of the first UE type and the UE of the second UE type may use the same formula to determine the RA-RNTI and messageB-RNTI of the RAR. In addition, the RAR in response to the RAM on one or more first ROs may use the first RA-RNTI and / or messageB-RNTI of the one or more first ROs, and the RAR in response to the RAM on one or more second ROs may use the second RA-RNTI and / or messageB-RNTI of the one or more second ROs. Therefore, the UE may determine whether the RAR is for the first UE type or the second UE type (according to the RA-RNTI or messageB-RNTI of the RAR) before decoding the RAR, and may therefore continue decoding the RAR or skip decoding of the RAR.

[0128] In example 905, the indication is or is included in the configuration of the RACH opportunity. For example, a RA-RNTI or messageB-RNTI for a first UE type may be configured using a first formula, and a RA-RNTI or messageB-RNTI for a second UE type may be configured using a second formula different from the first formula. Thus, the RAR may be configured with a RA-RNTI or messageB-RNTI that is distinguishable for the first UE type or for the second UE type. In this example, the first UE type may have a first RNTI set 920 (e.g., a first RNTI space, a non-overlapping RNTI set), the second UE type may have a second RNTI set 925 (e.g., a second RNTI space, a non-overlapping RNTI set), and a third RNTI set 930 (e.g., a shared RNTI space) may be used for the first UE type and the second UE type. Thus, by addressing the RAR to an RNTI belonging to one of the first RNTI set 920, the second RNTI set 925, or the third RNTI set 930, the network node may indicate whether the RAR is to be decoded by a UE of the first UE type, a UE of the second UE type, or both. For example, if the RAR is only for the second UE type or only for the first UE type, the RA-RNTI and messageB-RNTI of the RAR may be selected from a non-overlapping RNTI space (e.g., the first RNTI set 920 or the second RNTI set 925), while if the RAR is for both the first UE type and the second UE type, the RA-RNTI and messageB-RNTI may be selected from the third RNTI set 930. In this way, if the RACH opportunity of the RAR belongs to (e.g., is associated with an RNTI derived from the RACH opportunity and belongs to) a shared RNTI space, the indication may indicate that the RAR is for both the first UE type and the second UE type. In this way, if the RACH opportunity of the RAR belongs to (eg, is associated with an RNTI derived from the RACH opportunity and belongs to) the first RNTI set 920 or the second RNTI set 925, the indication may indicate that the RAR is for one of the first UE type and the second UE type.

[0129] Fig.101 is a diagram illustrating an example 1000 of indicating a UE type of RAR by RAR window differentiation according to the present disclosure. Example 1000 illustrates a first RAR window 1005 and a second RAR window 1010. The start time and / or duration L1 of the first RAR window 1005 may be different from the start time and / or duration L2 of the second RAR window 1010. The RAR window is a window in which a PDCCH communication that schedules a PDSCH communication carrying a RAR may arrive. The UE may receive configuration information indicating the RAR window of the UE, and the network node may output the configuration information. For example, the network node may configure a UE of a first UE type to use the first RAR window 1005, and / or may configure a UE of a second UE type to use the second RAR window 1010. Thus, a UE monitoring the first RAR window 1005 may only receive PDCCH communications that schedule RARs for the UE type of the first RAR window 1005, and a UE monitoring the second RAR window 1010 may only receive PDCCH communications that schedule RARs for the UE type of the second RAR window 1010. In some aspects, if the RAR windows 1005 and 1010 (corresponding to different UE types) overlap with each other, as at reference numeral 1015, then the PDCCH communications within the overlap interval may schedule RARs for only the first UE type. In some aspects, if the RAR windows 1005 and 1010 (corresponding to different UE types) overlap with each other, as at reference numeral 1015, then the PDCCH communications within the overlap interval may schedule RARs for only the second UE type. In some aspects, if the RAR windows 1005 and 1010 (corresponding to different UE types) overlap with each other, as at reference numeral 1015, then the PDCCH communications within the overlap interval may schedule RARs for both the first UE type and the second UE type.

[0130] Fig.11 A method 1100 of wireless communications by a UE, such as UE 120, according to the present disclosure is shown.

[0131] The method 1100 begins, at 1110, by receiving an indication of whether the RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type.

[0132] Then, the method 1100 proceeds to step 1120, and the RAR is decoded or the decoding of the RAR is skipped according to the indication and based at least in part on whether the UE is associated with the first UE type or the second UE type. As used herein, "decoding" includes extracting coded information from a received signal (such as a received PDSCH communication carrying the RAR).

[0133] In a first aspect, the indication comprises a demodulation reference signal of a physical downlink control channel associated with the RAR.

[0134] In a second aspect, alone or in combination with the first aspect, the indication comprises a cyclic redundancy check of a downlink control information message associated with the RAR.

[0135] In a third aspect, alone or in combination with one or more of the first and second aspects, an indication includes a field of a downlink control information message associated with a RAR.

[0136] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication is a bit of a downlink control information message associated with a RAR.

[0137] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a field that is invalid for a UE type of a UE of a downlink control information message associated with an RAR is indicated.

[0138] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a configuration including a downlink control information message associated with a RAR that is not decodable by a UE type of a UE is indicated.

[0139] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, configuration of a RACH opportunity including a RACH preamble corresponding to a RAR is indicated.

[0140] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, indicating that the RAR is for both the first UE type and the second UE type based at least in part on a RACH opportunity belonging to a shared RNTI set.

[0141] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication indicates that the RAR is for one of the first UE type or the second UE type based at least in part on RACH opportunities belonging to a non-overlapping RNTI set.

[0142] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, configuration of an RAR window including an RAR is indicated.

[0143] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the indication includes a physical downlink control channel communication in a control resource set, which physical downlink control channel communication indicates whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

[0144] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the indication includes a physical downlink control channel communication in a search space concentration, which physical downlink control channel communication indicates whether the RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type.

[0145] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, one or more parameters including a downlink bandwidth portion configuration for random access are indicated.

[0146] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the first UE type has a first bandwidth capability for receiving RAR, and the second UE type has a second bandwidth capability for receiving RAR.

[0147] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the first UE type is an enhanced mobile broadband (eMBB) or reduced capability (RedCap) UE type, and the second UE type is an enhanced RedCap (eRedCap) UE type.

[0148] In one aspect, method 1100 or any aspect related thereto may be performed by an apparatus such as Fig.13 The method 1100 is performed by a communication device 1300, which includes various components operable to, configured to, or adapted to perform the method 1100. The communication device 1300 is described in more detail below.

[0149] Please note that Fig.11 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in accordance with the present disclosure.

[0150] Fig.12 1. The present disclosure shows a method for a network entity (such as BS110, or as shown in FIG. Figure 3 A method 1200 for performing wireless communications using a decomposed base station) as discussed above.

[0151] The method 1200 begins at 1210 by outputting an indication of whether the RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type.

[0152] The method 1200 then proceeds to step 1220, where the RAR is outputted based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type. Outputting the RAR based at least in part on whether the UE is associated with the first UE type or the second UE type may include, for example, outputting a RAR consistent with capabilities of the first UE type if the UE is associated with the first UE type, or outputting a RAR consistent with capabilities of the second UE type if the UE is associated with the second UE type.

[0153] In a first aspect, the indication comprises a demodulation reference signal of a physical downlink control channel associated with the RAR.

[0154] In a second aspect, alone or in combination with the first aspect, the indication comprises a cyclic redundancy check of a downlink control information message associated with the RAR.

[0155] In a third aspect, alone or in combination with one or more of the first and second aspects, an indication includes a field of a downlink control information message associated with a RAR.

[0156] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication is a bit of a downlink control information message associated with a RAR.

[0157] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a field that is invalid for a UE type of a UE of a downlink control information message associated with an RAR is indicated.

[0158] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a configuration including a downlink control information message associated with a RAR that is not decodable by a UE type of a UE is indicated.

[0159] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, configuration of a RACH opportunity including a RACH preamble corresponding to a RAR is indicated.

[0160] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, indicating that the RAR is for both the first UE type and the second UE type based at least in part on a RACH opportunity belonging to a shared RNTI set.

[0161] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication indicates that the RAR is for one of the first UE type or the second UE type based at least in part on RACH opportunities belonging to a non-overlapping RNTI set.

[0162] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, configuration of an RAR window including an RAR is indicated.

[0163] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the indication includes a physical downlink control channel communication in a control resource set, which physical downlink control channel communication indicates whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

[0164] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the indication includes a physical downlink control channel communication in a search space concentration, which physical downlink control channel communication indicates whether the RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type.

[0165] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, one or more parameters including a downlink bandwidth portion configuration for random access are indicated.

[0166] In one aspect, method 1200 or any aspect related thereto may be performed by an apparatus such as Fig.14 The method 1200 is performed by a communication device 1400, which includes various components operable, configured, or adapted to perform the method 1200. The communication device 1400 is described in more detail below.

[0167] Please note that Fig.12 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in accordance with the present disclosure.

[0168] Fig.13 Aspects of an example communications device 1300 are depicted in accordance with the present disclosure. In some aspects, communications device 1300 is user equipment, such as UE 120.

[0169] The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or a receiver). The transceiver 1308 is configured to transmit and receive signals for the communication device 1300, such as the various signals described herein, via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received by the communication device 1300 and / or to be transmitted by the communication device.

[0170] The processing system 1302 includes one or more processors 1320. In various aspects, the one or more processors 1320 may represent one or more of the receive processor 258, the transmit processor 264, the TX MIMO processor 266, and / or the controller / processor 280, as described with respect to FIG. Figure 2 The one or more processors 1320 are coupled to the computer readable medium / memory 1330 via the bus 1306. In some aspects, the computer readable medium / memory 1330 is configured to store instructions (e.g., computer executable code, processor executable instructions) that, when executed by the one or more processors 1320, cause the one or more processors 1320 to perform operations with respect to Fig.11 The method 1100 or any aspect related thereto is described. Note that reference to a processor performing a function of the communication device 1300 may include one or more processors performing that function of the communication device 1300.

[0171] In the depicted example, the computer-readable medium / memory 1330 stores code (e.g., executable instructions) 1331 for receiving an indication of whether the RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type, and code 1332 for decoding the RAR or skipping decoding the RAR based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type. The processing of the codes 1331-1332 may cause the communication device 1300 to perform operations relative to Fig.11 The method 1100 or any aspect related thereto is described.

[0172] The one or more processors 1320 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1330, including circuits 1321 for receiving an indication of whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type, and circuits 1322 for decoding the RAR or skipping decoding the RAR based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type. Processing using the circuits 1321-1322 may cause the communication device 1300 to perform operations relative to Fig.11 The method 1100 or any aspect related thereto is described.

[0173] The various components of the communication device 1300 may provide for performing Fig.11 The components of the method 1100 or any aspect related thereto. For example, the components for sending, transmitting, or outputting for sending may include the transceiver 254 and / or the antenna 252 of the UE 120, and / or Fig.13The transceiver 1308 and antenna 1310 of the communication device 1300 in the UE 120. The means for receiving or obtaining may include the transceiver 254 and / or the antenna 252 and / or Fig.13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG.

[0174] Fig.14 Depicted are aspects of an example communication device 1400 according to the present disclosure. In some aspects, the communication device 1400 is a network entity, such as a BS 110 or a Figure 3 The decomposed base station in question.

[0175] The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or a receiver) and / or a network interface 1412. The transceiver 1408 is configured to transmit and receive signals for the communication device 1400 via an antenna 1410, such as the various signals described herein. The network interface 1412 is configured to transmit and receive signals for the communication device 1400 via a communication link (such as the various signals described herein). Figure 3 The processing system 1402 may be configured to obtain and transmit signals for the communication device 1400 using the backhaul link, midhaul link, and / or fronthaul link described herein. The processing system 1402 may be configured to perform processing functions of the communication device 1400, including processing signals received by the communication device 1400 and / or to be transmitted by the communication device.

[0176] The processing system 1402 includes one or more processors 1420. In various aspects, the one or more processors 1420 may represent one or more of the receive processor 238, the transmit processor 220, the TX MIMO processor 230, and / or the controller / processor 240, as described with respect to FIG. Figure 2 The one or more processors 1420 are coupled to the computer readable medium / memory 1430 via the bus 1406. In some aspects, the computer readable medium / memory 1430 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1420, cause the one or more processors 1420 to perform operations related to Fig.12 The method 1200 or any aspect related thereto is described. Note that reference to a processor of the communication device 1400 performing a function may include one or more processors of the communication device 1400 performing the function.

[0177] In the depicted example, the computer-readable medium / memory 1430 stores code (e.g., executable instructions) 1431 for outputting an indication of whether the RAR is for a first UE type, a second UE type, or both the first UE type and the second UE type, and code 1432 for outputting a RAR associated with a UE based at least in part on whether the UE is associated with the first UE type or the second UE type. The processing of the codes 1431-1432 may cause the communication device 1400 to perform operations relative to Fig.12 The method 1200 described herein or any aspect related thereto.

[0178] The one or more processors 1420 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1430, including circuits 1421 for outputting an indication of whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type, and circuits 1422 for outputting the RAR associated with the UE based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type. Processing using circuits 1421-1422 may cause the communication device 1400 to perform as described with respect to Fig.12 The method 1200 described herein or any aspect related thereto.

[0179] The various components of the communication device 1400 may be provided for performing Fig.12 Means for sending, transmitting, or outputting for sending may include transceiver 232 and / or antenna 234 of BS 110, and / or Fig.14 The transceiver 1408 and antenna 1410 of the communication device 1400 in the embodiment. The means for receiving or obtaining may include the transceiver 232 and / or antenna 234 and / or Fig.14 The transceiver 1408 and antenna 1410 of the communication device 1400 in FIG.

[0180] The following provides an overview of some aspects of the disclosure:

[0181] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication of whether a random access response (RAR) is for a first UE type, a second UE type, or both the first UE type and the second UE type; and decoding the RAR or skipping decoding the RAR based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type.

[0182] Aspect 2: The method according to aspect 1, wherein the indication includes a demodulation reference signal of a physical downlink control channel associated with the RAR.

[0183] Aspect 3: The method according to any one of aspects 1 to 2, wherein the indication comprises a cyclic redundancy check of a downlink control information message associated with the RAR.

[0184] Aspect 4: The method according to any one of aspects 1 to 3, wherein the indication comprises a field of a downlink control information message associated with the RAR.

[0185] Aspect 5: The method according to any one of aspects 1 to 4, wherein the indication is a bit of a downlink control information message associated with the RAR.

[0186] Aspect 6: The method according to any one of aspects 1 to 5, wherein the indication comprises a field of a downlink control information message associated with the RAR that is invalid for the UE type of the UE.

[0187] Aspect 7: The method according to any one of aspects 1 to 6, wherein the indication includes a configuration of a downlink control information message associated with the RAR that is not decodable by a UE type of the UE.

[0188] Aspect 8: The method according to any one of aspects 1 to 7, wherein the indication comprises a configuration of a random access channel (RACH) opportunity corresponding to a RACH preamble of the RAR.

[0189] Aspect 9: The method of aspect 8, wherein the indication indicates that the RAR is for both the first UE type and the second UE type based at least in part on the RACH occasion belonging to a shared radio network temporary identifier (RNTI) set.

[0190] Aspect 10: The method of aspect 8, wherein the indication indicates that the RAR is for one of the first UE type or the second UE type based at least in part on the RACH occasion belonging to a set of non-overlapping radio network temporary identifiers (RNTIs).

[0191] Aspect 11: The method according to any one of aspects 1 to 11, wherein the indication comprises a configuration of a RAR window of the RAR.

[0192] Aspect 12: A method according to any one of Aspects 1 to 12, wherein the indication includes a physical downlink control channel communication in a control resource set, and the physical downlink control channel communication indicates whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

[0193] Aspect 13: A method according to any one of Aspects 1 to 13, wherein the indication includes a physical downlink control channel communication in a search space set, and the physical downlink control channel communication indicates whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

[0194] Aspect 14: The method according to any one of aspects 1 to 14, wherein the indication comprises one or more parameters of a downlink bandwidth portion configuration for random access.

[0195] Aspect 15: The method according to any one of aspects 1 to 15, wherein the first UE type has a first bandwidth capability for receiving the RAR, and the second UE type has a second bandwidth capability for receiving the RAR.

[0196] Aspect 16: The method according to aspect 15, wherein the first UE type is an enhanced mobile broadband (eMBB) or reduced capability (RedCap) UE type, and the second UE type is an enhanced RedCap (eRedCap) UE type.

[0197] Aspect 17: A method of wireless communication performed by a network entity, the method comprising: outputting an indication of whether a random access response (RAR) is for a first user equipment (UE) type, a second UE type, or both the first UE type and the second UE type; and outputting the RAR associated with the UE based on the indication and at least in part on whether the UE is associated with the first UE type or the second UE type.

[0198] Aspect 18: The method according to aspect 17, wherein the indication comprises a demodulation reference signal of a physical downlink control channel associated with the RAR.

[0199] Aspect 19: The method according to any one of aspects 17 to 18, wherein the indication comprises a cyclic redundancy check on a downlink control information message associated with the RAR.

[0200] Aspect 20: A method according to any one of aspects 17 to 19, wherein the indication comprises a field of a downlink control information message associated with the RAR.

[0201] Aspect 21: The method according to any one of aspects 17 to 20, wherein the indication is a bit of a downlink control information message associated with the RAR.

[0202] Aspect 22: A method according to any one of aspects 17 to 21, wherein the indication comprises a field of a downlink control information message associated with the RAR that is invalid for the UE type of the UE.

[0203] Aspect 23: A method according to any one of aspects 17 to 22, wherein the indication comprises a configuration of a downlink control information message associated with the RAR that is not decodable by a UE type of the UE.

[0204] Aspect 24: The method according to any one of aspects 17 to 23, wherein the indication comprises a configuration of a random access channel (RACH) opportunity corresponding to a RACH preamble of the RAR.

[0205] Aspect 25: The method of aspect 24, wherein the indication indicates that the RAR is for both the first UE type and the second UE type based at least in part on the RACH occasion belonging to a shared radio network temporary identifier (RNTI) set.

[0206] Aspect 26: The method of aspect 24, wherein the indication indicates that the RAR is for one of the first UE type or the second UE type based at least in part on the RACH occasion belonging to a set of non-overlapping radio network temporary identifiers (RNTIs).

[0207] Aspect 27: The method according to any one of aspects 17 to 26, wherein the indication comprises a configuration of a RAR window of the RAR.

[0208] Aspect 28: A method according to any one of Aspects 17 to 27, wherein the indication includes a physical downlink control channel communication in a control resource set, and the physical downlink control channel communication indicates whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

[0209] Aspect 29: A method according to any one of Aspects 17 to 28, wherein the indication includes a physical downlink control channel communication in a search space set, and the physical downlink control channel communication indicates whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

[0210] Aspect 30: A method according to any one of aspects 17 to 29, wherein the indication comprises one or more parameters of a downlink bandwidth portion configuration for random access.

[0211] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 30.

[0212] Aspect 32: A device for wireless communication, the device comprising a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 30.

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

[0214] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.

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

[0216] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0217] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method at least in part based on the description herein.

[0218] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0219] Although the specific combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically stated in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, 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 sorting of a, b and c).

[0220] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

[0221] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited to the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may omit, replace or add various procedures or components as appropriate. For example, the described methods may be performed in an order different from the order described, and various actions may be added, omitted or combined. In addition, the features described for some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality or structures and functionality that are supplementary or alternative to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0222] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration).

[0223] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, etc. In addition, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determine" may include resolving, selecting, choosing, establishing, etc.

[0224] The method disclosed herein includes one or more actions for implementing the method. The method actions are interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. In addition, the various operations of the method described above may be performed by any appropriate component capable of performing the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0225] The following claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication of whether a random access response (RAR) is for a first UE type, a second UE type, or both the first UE type and the second UE type; as well as The RAR is decoded or decoding of the RAR is skipped according to the indication and based at least in part on whether the UE is associated with the first UE type or the second UE type.

2. The method of claim 1, wherein the indication comprises a demodulation reference signal of a physical downlink control channel associated with the RAR.

3. The method of claim 1, wherein the indication comprises a cyclic redundancy check on a downlink control information message associated with the RAR.

4. The method of claim 1, wherein the indication comprises a field of a downlink control information message associated with the RAR.

5. The method of claim 1, wherein the indication is a bit of a downlink control information message associated with the RAR.

6. The method of claim 1, wherein the indication comprises a field of a downlink control information message associated with the RAR that is invalid for a UE type of the UE.

7. The method of claim 1, wherein the indication comprises a configuration of a downlink control information message associated with the RAR that is not decodable by a UE type of the UE.

8. The method of claim 1, wherein the indication comprises a configuration of a random access channel (RACH) opportunity corresponding to a RACH preamble of the RAR.

9. The method of claim 8, wherein the indication indicates that the RAR is for both the first UE type and the second UE type based at least in part on the RACH occasion belonging to a shared Radio Network Temporary Identifier (RNTI) set.

10. The method of claim 8, wherein the indication indicates that the RAR is for one of the first UE type or the second UE type based at least in part on the RACH occasion belonging to a non-overlapping set of radio network temporary identifiers (RNTIs).

11. The method of claim 1, wherein the indication comprises a configuration of a RAR window of the RAR.

12. The method of claim 1, wherein the indication comprises a physical downlink control channel communication in a control resource set, the physical downlink control channel communication indicating whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

13. The method of claim 1, wherein the indication comprises a physical downlink control channel communication in a search space set, the physical downlink control channel communication indicating whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

14. The method of claim 1, wherein the indication comprises one or more parameters of a downlink bandwidth portion configuration for random access.

15. The method of claim 1, wherein the first UE type has a first bandwidth capability for receiving the RAR, and the second UE type has a second bandwidth capability for receiving the RAR.

16. The method of claim 15, wherein the first UE type is an enhanced mobile broadband (eMBB) or reduced capability (RedCap) UE type, and the second UE type is an enhanced RedCap (eRedCap) UE type.

17. A method of wireless communication performed by a network entity, the method comprising: outputting an indication of whether a random access response (RAR) is for a first user equipment (UE) type, a second UE type, or both the first UE type and the second UE type; as well as The RAR associated with the UE is outputted in accordance with the indication and based at least in part on whether the UE is associated with the first UE type or the second UE type.

18. The method of claim 17, wherein the indication comprises a demodulation reference signal of a physical downlink control channel associated with the RAR.

19. The method of claim 17, wherein the indication comprises a cyclic redundancy check on a downlink control information message associated with the RAR.

20. The method of claim 17, wherein the indication comprises a field of a downlink control information message associated with the RAR.

21. The method of claim 17, wherein the indication is a bit of a downlink control information message associated with the RAR.

22. The method of claim 17, wherein the indication comprises a field of a downlink control information message associated with the RAR that is invalid for a UE type of the UE.

23. The method of claim 17, wherein the indication comprises a configuration of a downlink control information message associated with the RAR that is not decodable by a UE type of the UE.

24. The method of claim 17, wherein the indication comprises a configuration of a random access channel (RACH) opportunity corresponding to a RACH preamble of the RAR.

25. The method of claim 24, wherein the indication indicates that the RAR is for both the first UE type and the second UE type based at least in part on the RACH occasion belonging to a shared Radio Network Temporary Identifier (RNTI) set.

26. The method of claim 24, wherein the indication indicates that the RAR is for one of the first UE type or the second UE type based at least in part on the RACH occasion belonging to a non-overlapping set of radio network temporary identifiers (RNTIs).

27. The method of claim 17, wherein the indication comprises a configuration of a RAR window of the RAR.

28. The method of claim 17, wherein the indication comprises a physical downlink control channel communication in a control resource set, the physical downlink control channel communication indicating whether the RAR is for the first UE type, the second UE type, or both the first UE type and the second UE type.

29. A user equipment (UE), the user equipment (UE) comprising: a memory including processor-executable instructions; and a processor configured to execute the processor-executable instructions and cause the UE to: receiving an indication of whether a random access response (RAR) is for a first UE type, a second UE type, or both the first UE type and the second UE type; as well as The RAR is decoded or decoding of the RAR is skipped according to the indication and based at least in part on whether the UE is associated with the first UE type or the second UE type.

30. A network entity, comprising: a memory including processor-executable instructions; and a processor configured to execute the processor-executable instructions and cause the network entity to: outputting an indication of whether a random access response (RAR) is for a first user equipment (UE) type, a second UE type, or both the first UE type and the second UE type; as well as The RAR associated with the UE is outputted in accordance with the indication and based at least in part on whether the UE is associated with the first UE type or the second UE type.

Images