RANDOM ACCESS RESPONSE DIFFERENTIATION

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a random access response (RAR). The UE may decode the RAR based at least in part on information that differentiates RARs according to UE type. Numerous other aspects are described.

Claims

1. A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: receive a random access channel (RACH) configuration that includes information that differentiates random access responses (RARs) according to UE type; receive a random access response (RAR); and decode the RAR based at least in part on the information that differentiates RARs according to UE type.

2. The UE of claim 1, wherein the one or more processors are configured to, prior to receiving the RAR: obtain an initial bandwidth part (BWP) configuration for random access that indicates an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE; and transmit a random access message within the initial uplink BWP configured for the UE type of the UE.

3. The UE of claim 2, wherein the one or more processors, to receive the RAR, are configured to receive the RAR within the initial downlink BWP configured for the UE type of the UE.

4. The UE of claim 2, wherein the one or more processors, to obtain the configuration, are configured to receive the configuration in a first initial downlink BWP.

5. The UE of claim 4, wherein the first initial downlink BWP is different than the initial downlink BWP configured for the UE type of the UE, and wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on the initial BWP configuration.

6. The UE of claim 1, wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an initial bandwidth part (BWP) configuration.

7. The UE of claim 6, wherein the first UE type shares an initial uplink BWP with the second UE type.

8. The UE of claim 6, wherein an initial uplink BWP for the first UE type is different than an initial uplink BWP for the second UE type.

9. The UE of claim 8, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

10. The UE of claim 8, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type are non-overlapping.

11. The UE of claim 8, wherein an initial downlink BWP for the first UE type is different than an initial downlink BWP for the second UE type.

12. The UE of claim 11, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap or are overlapping.

13. The UE of claim 1, wherein the information includes a cyclic redundancy check (CRC) that is masked with a radio network temporary identifier (RNTI), and wherein the RNTI differentiates between an RAR for a first UE type and an RAR for a second UE type.

14. The UE of claim 13, wherein the one or more processors, to decode the RAR based at least in part on the information, are configured to: extract the RNTI from the CRC; calculate a modified RNTI based at least in part on one or more of an index value of a first symbol of a physical random access channel (PRACH) occasion of the RAR, an index of a first slot of the PRACH occasion in a system frame, and an index of the PRACH occasion in a frequency domain; and decode the RAR if the RNTI extracted from the RNTI is in a set of RNTIs indicated by the modified RNTI.

15. The UE of claim 1, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an interleaving pattern that is applied to the CRC, and wherein the one or more processors, to decode the RAR based at least in part on the information, are configured to: apply one or more of a first interleaving pattern or a second interleaving pattern to the CRC, wherein the first interleaving pattern is associated with the first UE type and the second interleaving pattern is associated with the second UE type; and decode the RAR based at least in part on a result of the applying.

16. The UE of claim 1, wherein the information includes demodulation reference signal (DMRS) sequences that differentiate between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DMRS sequences.

17. The UE of claim 16, wherein the one or more processors, to decode the RAR based at least in part on the information, are configured to: apply one or more of a first scrambling ID set or a second scrambling ID set to the DMRS sequences, wherein the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type; and decode the RAR based at least in part on a result of the applying.

18. The UE of claim 1, wherein the information includes downlink control information (DCI) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DCI.

19. The UE of claim 18, wherein the one or more processors, to decode the RAR based at least in part on the information, are configured to: apply one or more of a first scrambling ID set or a second scrambling ID set to the DCI, wherein the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type; and decode the RAR based at least in part on a result of the applying.

20. The UE of claim 1, wherein the information includes a control resource set (CORESET) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a location of the CORESET.

21. The UE of claim 1, wherein the information includes a precoding that differentiates between an RAR for a first UE type and an RAR for a second UE type.

22. The UE of claim 1, wherein the information includes one or more physical random access channel (PRACH) formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

23. The UE of claim 1, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on being associated with a first set of physical random access channel (PRACH) preambles for the first UE type or a second set of PRACH preambles for the second UE type.

24. A base station for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: transmit a random access channel (RACH) configuration information that includes information that differentiates random access responses (RARs) according to user equipment (UE) type; encode a random access response (RAR) for a UE with the information that differentiates RARs according to UE type and based at least in part on a UE type of the UE; and transmit the RAR to the UE.

25. The base station of claim 24, wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an initial bandwidth part (BWP) configuration.

26. The base station of claim 24, wherein the information includes demodulation reference signal (DMRS) sequences that differentiate between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DMRS sequences.

27. The base station of claim 24, wherein the information includes downlink control information (DCI) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DCI.

28. The base station of claim 24, wherein the one or more processors, to encode the RAR based at least in part on the information, are configured to place a control resource set (CORESET) of the RAR in a location that differentiates between an RAR for a first UE type and an RAR for a second UE type.

29. The base station of claim 24, wherein the information includes one or more physical random access channel (PRACH) formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

30. The base station of claim 24, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on being associated with a first set of physical random access channel (PRACH) preambles for the first UE type or a second set of PRACH preambles for the second UE type.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

[0018] FIG. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0019] FIG. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0020] FIG. 3 is a diagram illustrating types of devices, in accordance with the present disclosure.

[0021] FIG. 4 illustrates an example of configurations for a New Radio reduced capacity (RedCap) UE, in accordance with the present disclosure.

[0022] FIG. 5 is a diagram illustrating an example of differentiating random access responses (RARs), in accordance with the present disclosure.

[0023] FIG. 6 is a diagram illustrating an example of overlapping and non-overlapping bandwidth parts for differentiating RARs, in accordance with the present disclosure.

[0024] FIG. 7 is a diagram illustrating an example of encoding downlink control information for scheduling an RAR, in accordance with the present disclosure.

[0025] FIG. 8 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0026] FIG. 9 is a diagram illustrating an example process performed, for example, by a base station, in accordance with the present disclosure.

[0027] FIGS. 10-11 are block diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.

DETAILED DESCRIPTION

[0028] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than 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 a claim.

[0029] Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses 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, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0030] It should be noted that while aspects may be described herein using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

[0031] FIG. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and/or an LTE network, among other examples. The wireless network 100 may include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and may also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), or the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). ABS for a macro cell may be referred to as a macro BS. ABS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, a BS 110a may be a macro BS for a macro cell 102a, a BS 110b may be a pico BS for a pico cell 102b, and a BS 110c may be a femto BS for a femto cell 102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be used interchangeably herein.

[0033] In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.

[0034] In some aspects, the term “base station” (e.g., the base station 110) or “network entity” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof. For example, in some aspects, “base station” or “network entity” may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term “base station” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station 110. In some aspects, the term “base station” or “network entity” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station” or “network entity” may refer to any one or more of those different devices. In some aspects, the term “base station” or “network entity” may refer to one or more virtual base stations and/or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term “base station” or “network entity” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0035] Wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, a relay BS 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.

[0036] Wireless network 100 may be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0037] A network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

[0038] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, or the like. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system (GPS) device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0039] Some UEs may be reduced capacity (RedCap) UEs that may decode a random access response (RAR) that is part of a random access channel (RACH) procedure for establishing a radio resource control (RRC) connection. There may be UEs of different types that may be able to decode an RAR only if the RAR is configured for the UE type. Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, that may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as processor components and/or memory components. In some aspects, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

[0040] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, or the like. A frequency may also be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0041] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol or a vehicle-to-infrastructure (V2I) protocol), and/or a mesh network. In this case, the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.

[0042] Devices of wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided based on frequency or wavelength into various classes, bands, channels, or the like. For example, devices of wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may span from 410 MHz to 7.125 GHz, and/or may communicate using an operating band having a second frequency range (FR2), which may span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 is often referred to as a “millimeter wave” band despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. Thus, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies less than 6 GHz, frequencies within FR1, and/or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies within the EHF band, frequencies within FR2, and/or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and techniques described herein are applicable to those modified frequency ranges.

[0043] As indicated above, FIG. 1 is provided as an example. Other examples may differ from what is described with regard to FIG. 1.

[0044] FIG. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0045] At base station 110, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0046] At UE 120, antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some aspects, one or more components of UE 120 may be included in a housing 284.

[0047] Network controller 130 may include communication unit 294, controller/processor 290, and memory 292. Network controller 130 may include, for example, one or more devices in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0048] Antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include a set of coplanar antenna elements and/or a set of non-coplanar antenna elements. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include antenna elements within a single housing and/or antenna elements within multiple housings. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of FIG. 2.

[0049] On the uplink, at UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and a demodulator (e.g., MOD/DEMOD 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulators and/or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, as described with reference to FIGS. 3-11).

[0050] At base station 110, the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240. Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244. Base station 110 may include a scheduler 246 to schedule UEs 120 for downlink and/or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD/DEMOD 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modulators and/or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and/or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein (for example, as described with reference to FIGS. 3-11).

[0051] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B, evolved NB (eNB), NR BS, 5G NB, access point (AP), a TRP, or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0052] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0053] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0054] Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component(s) of FIG. 2 may perform one or more techniques associated with differentiating RARs as part of a RACH procedure, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component(s) of FIG. 2 may perform or direct operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, and/or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the base station 110 to perform or direct operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

[0055] In some aspects, the UE 120 includes means for receiving an RAR, and/or means for decoding the RAR based at least in part on information that differentiates RARs according to UE type. The means for the UE 120 to perform operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller/processor 280, or memory 282.

[0056] In some aspects, the base station includes means for encoding an RAR for a UE with information that differentiates RARs according to UE type and based at least in part on a UE type of the UE, and/or means for transmitting the RAR to the UE. The means for the base station to perform operations described herein may include, for example, one or more of transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

[0057] While blocks in FIG. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of controller/processor 280.

[0058] As indicated above, FIG. 2 is provided as an example. Other examples may differ from what is described with regard to FIG. 2.

[0059] FIG. 3 is a diagram 300 illustrating types of devices, in accordance with the present disclosure.

[0060] As shown in FIG. 3, ultra-reliable low-latency communication (URLLC) devices and enhanced mobile broadband (eMBB) devices may be considered NR premium devices (e.g., UEs). Some devices, such as low power wide-area (LPWA) devices or massive machine type communication (mMTC) devices, may be considered enhanced LTE devices. FIG. 3 shows that some wireless communication devices are not NR premium UEs, but rather devices with reduced capabilities. Such devices with reduced capabilities may include relaxed IoT devices, smart wearables, sensors, and video surveillance cameras. Reduced capability devices may be referred to as NR RedCap devices, RedCap devices, Red Cap devices, Red-Cap devices, redcap devices, red cap devices, red-cap devices, and/or NR RedCap UEs. NR RedCap devices have also been referred to as NR Light devices or NR Lite devices. For purposes of explanation, the term NR RedCap UE may be used in the aspects described herein.

[0061] In some aspects, an NR RedCap UE may have reduced capabilities due to a capability or configuration that provides for less peak throughput, longer latency, less reliability, more power consumption efficiency, less system overhead, and/or less resource costs. An NR RedCap UE may be subject to relaxed latency or reliability requirements. In some aspects, an NR RedCap UE may have only one or two transmission or reception antennas.

[0062] In some aspects, an NR RedCap UE may have or be configured to use a subset of features available to NR premium UEs or other full-featured NR UEs that may be used for personal communication. In some aspects, an NR RedCap UE may have a mandatory set of features and an optional set of features, where one or more of the optional features in an NR RedCap UE are mandatory for NR premium UEs. In some aspects, a standard chart or matrix of features may be used to specify whether a device is an NR RedCap UE.

[0063] In some aspects, NR RedCap UEs may include wearable devices, such as smart watches, eHealth related devices, personal protection equipment, exercise monitors, or medical monitoring devices. NR RedCap UEs may include industrial sensors, such as pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, or actuators. NR RedCap UEs may include surveillance cameras, low-end smartphones, and/or low-end IoT devices.

[0064] As indicated above, FIG. 3 is provided as an example. Other examples may differ from what is described with regard to FIG. 3.

[0065] FIG. 4 illustrates an example 400 of configurations for an NR RedCap UE, in accordance with the present disclosure.

[0066] In some aspects, the NR RedCap UE may support reduced bandwidth and a reduced quantity of transmission and reception antennas. For example, at least for FR1, the NR RedCap UE may support a maximum bandwidth in downlink (DL) or uplink (UL) of 20 MHz or 40 MHz. The NR RedCap UE may support a maximum bandwidth that is separately configured for DL and UL. For an NR RedCap UE with reduced bandwidth capability (e.g., down from 100 MHz for FR1), the maximum bandwidth in UL and DL may be reduced for control information or data. An NR RedCap UE with reduced bandwidth capability may not be expected to support carrier aggregation or dual connectivity, which may be required of non-NR RedCap UEs. In some embodiments, an NR RedCap UE may support a maximum of one transmission antenna and a maximum of one or two reception antennas.

[0067] FIG. 4 shows other configurations that NR RedCap UEs may support, based at least in part on a type of NR RedCap UE. Different types may have different subsets of features or limitations. For example, an NR RedCap UE that is a wearable device may support a DL peak rate of 150 Mbps, an UL peak rate of 50 Mbps, a bandwidth requirement of 20 MHz or 40 MHz, one transmission antenna, and one or two reception antennas. The wearable device may not support 256-QAM. The wearable device may have medium mobility and a high power saving requirement. The wearable device may still have latency or reliability requirements that are similar to eMBB.

[0068] In some aspects, an NR RedCap UE that is an industry sensor may support a DL peak rate of less than 2 Mbps, an UL peak rate of less than 5 Mbps, a bandwidth requirement of 5 MHz or 10 MHz, one transmission antenna, and one reception antenna. The sensor may not support 256-QAM. The sensor may have low mobility and a high power saving requirement. The sensor may have a latency requirement of less than 100 milliseconds (ms) or 5-10 ms for safety-related sensors. The sensor may have a reliability requirement of 99.99%.

[0069] In some aspects, an NR RedCap UE that is a video surveillance camera may support a DL peak rate of less than 5 Mbps, an UL peak rate of less than 25 Mbps, a bandwidth requirement of 10 MHz or 20 MHz, one or two transmission antennas, and one reception antenna. The camera may not support 256-QAM. The camera may have low mobility and a high power saving requirement. The camera may have a latency requirement of less than 500 ms and a reliability requirement of 99%-99.99%.

[0070] In sum, an NR RedCap UE may have a determined configuration based at least in part on a type of the NR RedCap UE. As a result, the NR RedCap UE may save power, processing resources, and signaling resources supporting a reduced set of features. In some aspects, an NR RedCap UE may support a same power saving mode, a same set of processing capabilities and timeline, or a set of fallback capabilities as another type of NR UE, which may also have reduced capabilities or may not have reduced capabilities. For example, an NR RedCap UE may have a set of reduced capabilities, but may fall back to a set of further reduced capabilities.

[0071] An NR RedCap UE may be required to perform a RACH procedure for accessing a channel and establishing a connection. The RACH procedure may be the same procedure for every UE, even though different UEs have different UE capabilities. In some scenarios, a base station may transmit multiple RACH messages, such as multiple RARs, to multiple UEs. A UE with limited capabilities may waste power and processing resources attempting to decode and process an RAR that may not be intended for the UE.

[0072] According to various aspects described herein, a UE may receive an RAR as part of a RACH procedure and decode the RAR based at least in part on information that differentiates RARs according to UE type. That is, the UE may decode the RAR if the information indicates that the RAR is to be decoded by the UE type of the UE. An RAR may be intended for a first UE type (e.g., Type A) or a second UE type (e.g., Type B), but not both UE types. Examples of a first UE type versus a second UE type may include: a RedCap UE vs. a non-RedCap UE, a RedCap UE with one receive antenna branch vs. a RedCap UE with two receive antenna branches, a UE that supports coverage enhancement vs. a UE that does not support coverage enhancement, a UE that supports small data transmissions (SDTs) vs. a UE that does not support SDTs, or a UE that supports RAN slices vs. a UE that does not support RAN slices. By differentiating RARs, the UE may decode RARs intended for the UE (or UE type of the UE) and conserve power and processing resources by not attempting to decode and process RARs that are not intended for the UE (or UE type of the UE). The UE may receive the information for RAR differentiation or obtain the information from stored configuration information. The information may indicate how the UE is to determine whether to decode an RAR or other RACH message.

[0073] As indicated above, FIG. 4 is provided as an example. Other examples may differ from what is described with regard to FIG. 4.

[0074] FIG. 5 is a diagram illustrating an example 500 of differentiating RARs, in accordance with the present disclosure. As shown in FIG. 5, a base station 110 and a UE 120 may communicate with one another to perform a 4-step RACH procedure.

[0075] As shown by reference number 505, the base station 110 may transmit, and the UE 120 may receive, random access configuration information. In some aspects, the random access configuration information may be transmitted in and/or indicated by system information (e.g., in one or more system information blocks (SIBs), such as a SIB 2) and/or a synchronization signal block (SSB), such as for contention-based random access. Additionally, or alternatively, the random access configuration information may be transmitted in an RRC message and/or a physical downlink control channel (PDCCH) order message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include information for receiving an RAR and differentiating RARs based on UE type.

[0076] As shown by reference number 510, the UE 120 may transmit a random access message (RAM), which may include a preamble (sometimes referred to as a random access preamble, a physical RACH (PRACH) preamble, or a RAM preamble). The message that includes the preamble may be referred to as a message 1, Msg1, msg1, MSG1, a first message, or an initial message in a 4-step RACH procedure. The RAM may include a random access preamble identifier.

[0077] As shown by reference number 515, the base station 110 may transmit an RAR as a reply to the preamble. The message that includes the RAR may be referred to as message 2, Msg2, msg2, MSG2, or a second message in a 4-step RACH procedure. In some aspects, the RAR may indicate the detected random access preamble identifier (e.g., received from the UE 120 in Msg1). Additionally, or alternatively, the RAR may indicate an uplink grant or a resource allocation to be used by the UE 120 to transmit message 3 (Msg3).

[0078] In some aspects, as part of the second step of the 4-step random access procedure, the base station 110 may transmit a PDCCH communication for the RAR. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication that includes 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 4-step RACH procedure, the base station 110 may transmit the PDSCH communication for the RAR, as scheduled by the PDCCH communication. The RAR may be included in a MAC protocol data unit (PDU) of the PDSCH communication.

[0079] As shown by reference number 520, the UE 120 may differentiate whether the RAR is intended for the UE 120 or a UE type of the UE 120. In some aspects, the UE 120 may determine if an RAR is to be decoded by the UE 120 based at least in part on an initial bandwidth part (BWP) configuration, which may be separately configured for each UE type. This is described in more detail in connection with FIG. 6. In some aspects, the UE 120 may determine if an RAR is to be decoded based at least in part on a cyclic redundancy check (CRC). For example, the CRC may be masked with a radio network temporary identifier (RNTI) and the UE 120 may decode the RAR if the RNTI that is extracted from the CRC belongs to a particular set of RNTIs. In some aspects, the UE 120 may determine the RAR is to be decoded based at least in part on an interleaving pattern or a scrambling identifier (ID) that is used. These aspects are described in more detail in connection with FIG. 7.

[0080] In some aspects, the UE 120 may have information about different resources that are used for PDCCH scheduling of an RAR. For example, the UE 120 may have information about a control resource set (CORESET) that differentiates between an RAR for a first UE type and an RAR for a second UE type. The RAR may be scheduled with a CORESET, and the UE 120 may determine that the RAR is to be decoded based at least in part on a location of the CORESET. Some CORESET locations may be set aside for UEs of the first UE type and some CORESET locations may be set aside for UEs of the second UE type.

[0081] In some aspects, the UE 120 may have information about a decoding or a quasi-co-located (QCLed) relation that is used for scheduling of an RAR. For example, the PDCCH may be QCLed with an SSB index that is set aside for UEs of a particular UE type. The UE 120 may determine that the RAR is to be decoded based at least in part on the SSB index.

[0082] In some aspects, the information may include one or more reserved bits or spare bits in downlink control information (DCI). For example, for DCI Format 1_0, a CRC may be masked by an RNTI (e.g., random access RNTI, msgB-RNTI, modified RNTI). The masking may use (or repurpose) reserved bits or the spare bits (e.g. most significant bits) to signal a UE type for an RAR. In some aspects, the UE 120 may use any combination of scheduling resources to determine if the UE 120 is to decode the RAR.

[0083] Multiple UE types can be supported in a serving cell or a RAN slice. In some aspects, the information may include one or more PRACH formats associated with each UE type, and the UE 120 may determine if the RAR is to be decoded based at least in part on a PRACH format that is used. One UE type may be mapped to multiple PRACH formats, and different UE types may be mapped to different PRACH formats. For example, UE types may be differentiated by location in a cell. Cell-center UEs (e.g., UEs that satisfy a distance threshold, or a maximum distance, from the cell center) can be mapped to PRACH preambles with a short length, and cell-edge UEs (UEs that do not satisfy a distance threshold, or the maximum distance, from the cell center) can be mapped to PRACH preambles with a longer length. The UE 120 may determine its distance with respect to the base station 110 by using, for example, a GPS and/or measurements.

[0084] In some aspects, PRACH preambles may be grouped into multiple sets characterized by different cyclic shifts. For example, for PRACH preambles sharing the same PRACH occasion, the size of the cyclic shift (e.g., cyclic prefix (CP)) may be scaled proportionally to a downlink RSRP of the UE 120. A CP for a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a sounding reference signal (SRS) may be a normal CP (NCP) or an extended CP (ECP). For example, the UE 120 may perform an RSRP measurement and compare the measurement with thresholds broadcast by the base station 110 to determine which PRACH preamble group to use.

[0085] UEs close to the cell center have a smaller round trip time (RTT), and UEs of this UE type (close UEs) may be mapped to a set of cyclic shifts with dense spacing or may be excluded from the PRACH resource selection by using PRACH-less transmission. UEs close to the cell edge may have a larger RTT, and UEs of this UE type (far UEs) may be mapped to a different set of cyclic shifts with sparse spacing. The UE 120 may determine if the RAR is to be decoded based at least in part on a spacing of the cyclic shift for the RAR.

[0086] As shown by reference number 525, the UE 120 may decode the RAR if the RAR is intended for the UE 120 or the UE type of the UE 120. If the RAR is not intended for the UE 120, the UE 120 may not decode the RAR, and conserve power and processing resources that would have otherwise been consumed by decoding and processing the RAR.

[0087] The UE may transmit a communication based at least in part on the communication. As shown by reference number 530, the UE 120 may transmit an RRC connection request message as the communication. The RRC connection request message may be referred to as message 3, Msg3, msg3, MSG3, or a third message of a 4-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information (UCI), and/or a PUSCH communication (e.g., an RRC connection request). The base station 110 may transmit a hybrid automatic repeat request (HARQ) acknowledgement (ACK) for Msg3.

[0088] As shown by reference number 535, the base station 110 may transmit an RRC connection setup message. The RRC connection setup message may be referred to as message 4, Msg4, msg4, MSG4, or a fourth message of a 4-step RACH procedure. In some aspects, the RRC connection setup message may include the detected UE identifier, a timing advance value, and/or contention resolution information. If the UE 120 successfully receives the RRC connection setup message, the UE 120 may transmit a HARQ ACK. The UE 120 may transmit a HARQ ACK for Msg4. As shown by reference number 540, the base station 110 may transmit DCI with an uplink grant for an RRC connection setup complete message, which indicates that the UE 120 has completed setting up the RRC connection. As shown by reference number 545, the UE 120 may transmit the RRC connection setup complete message.

[0089] If 2-step RACH is to be used, Msg1 and Msg3 may be considered a first step (MsgA), and Msg2 and Msg4 may be considered a second step (MsgB). In this scenario, the UE 120 may transmit a communication based at least in part on differentiating the RAR of MsgB.

[0090] As indicated above, FIG. 5 is provided as an example. Other examples may differ from what is described with regard to FIG. 5.

[0091] FIG. 6 is a diagram illustrating an example 600 of overlapping and non-overlapping BWPs for differentiating RARs, in accordance with the present disclosure.

[0092] The UE 120 may determine to differentiate RARs for UE types based at least in part on an initial BWP configuration. The initial BWP configuration may indicate which BWP is activated for the UL and which BWP is activated for the DL. Configurations for an initial DL BWP and an initial UL BWP may be specified by standardized look-up tables, or indicated by system information. Example 600 shows different UE types, Type A and Type B. Type A may be, for example, UEs with energy harvesting capabilities, which are active during a time interval that is orthogonal to Type B UEs, which may be, for example, powered by non-rechargeable batteries.

[0093] In some aspects, both the initial DL BWP and the initial UL BWP may be shared between UEs with Type A and Type B capabilities. In some aspects, the initial DL BWP may be shared, but the initial UL BWP may be separately configured for Type A and Type B. The initial UL BWP for Type A and for Type B may partially overlap. Example 600 shows overlapping BWPs 602 that are aligned at a reference point that may be a center frequency of initial UE BWPs. Example 600 also shows overlapping BWPs 604 that are aligned at a starting physical resource block. The initial UL BWP for Type A and the initial UL BWP for Type B may be non-overlapping, such as shown by non-overlapping BWPs 606 (e.g., different sub-bands of a same carrier, different carriers (e.g., normal uplink (NUL) and supplementary uplink (SUL))). Non-overlapping BWPs 608 may be separated in time according to time division multiplexing (TDM) and/or have different timer configurations.

[0094] In some aspects, both the initial DL BWP and the initial UL BWP may be separately configured for Type A and for Type B. The initial DL BWPs and/or the initial UL BWPs may be partially overlapping and aligned at a reference point determined by the base station 110. In some aspects, the initial DL and/or UL BWP for Type A and the initial DL and/or UL BWP for Type B may be non-overlapping and mapped to different carriers (e.g., normal downlink (NDL) and supplementary downlink (SDL), NUL and SUL), mapped to different sub-bands of the same carrier, and/or mapped to different TDM time slots or different timer configurations.

[0095] As indicated above, FIG. 6 is provided as an example. Other examples may differ from what is described with regard to FIG. 6.

[0096] FIG. 7 is a diagram illustrating an example 700 of encoding a DCI for scheduling an RAR, in accordance with the present disclosure. Example 700 shows a DCI payload that is used to schedule an RAR and a CRC that may be attached to the DCI. As shown by example 700, an RNTI may be used to mask the CRC (e.g., via a logical exclusive OR (XOR) operation) of DCI that schedules an RAR. The RNTI may belong to a first set of RNTIs that may be applied to mask the CRC of DCI that schedules a Type A RAR or belong to a second set of RNTIs that schedules a Type B RAR. There may be no intersection between the first set of RNTIs and the second set of RNTIs. The first set of RNTIs and the second set of RNTIs may be orthogonal. The RNTI of each set may be constructed according to a formula for a modified RNTI: modified RNTI=mod(1+s_id+S×t_id+S×T×f_id+S×T×F×ul_FDRA_id+Δ.sub.preamble, 2.sup.bitwidth_RNTI−1), where bitwidth_RNTI may denote the number of bits allocated for the modified RNTI (upper bounded by the length of the CRC attached to the DCI), s_id may be the index of the first OFDM symbol of the PRACH occasion (0≤s_id<S, and S is the max number of OFDM symbols per slot which depends on the subcarrier spacing (SCS) and CP length), t_id may be the index of the first slot of the PRACH occasion in a system frame (0≤t_id<T, and t_id depends on the SCS and CP length), f_id may be the index of the PRACH occasion in the frequency domain (0≤f_id<F, F depends on the initial UL BWP configurations of Type A and Type B UEs), and a starting point, a spacing, and a range of f_id (may take different values for Type A and Type B UEs), ul_FDRA_id may be the UL frequency domain resource allocation (FDRA) used for PRACH preamble transmission (e.g., 0 for NUL Carrier or the sub-band index allocated for Type A UE, and 1 for SUL carrier or the sub-band index allocated for Type B UE), and Δ_preamble depends on whether or not a Type A UE and a Type B UE share the same PRACH occasion (Δ_preamble=0 for different PRACH occasions, and Δ_preamble≥S*T*F*2 for a shared PRACH occasion and different preamble groups). The UE 120 may determine if the RAR is to be decoded based at least in part on whether an RNTI extracted from a masked CRC in the information (DCI scheduling the RAR) belongs to a set of RNTIs associated with the UE type of the UE 120. The base station 110 may partition values for the s_id, the t_id, and/or the f_id such that they distinguish UE types when the modified RNTI is calculated. This may save signaling resources (e.g., save a message that may be 16 bits).

[0097] Example 700 also shows that an interleaving pattern may be applied to the CRC portion attached to the DCI scheduling the RAR. Applying the interleaving pattern to the CRC portion may include applying the interleaving pattern to the DCI in addition to the CRC portion. A first interleaving pattern may be applied for Type A UEs, and a second interleaving pattern may be applied for Type B UEs. There may be no intersection between a set of interleaving patterns for Type A and a set of interleaving patterns for Type B. The UE 120 may determine if the RAR is to be decoded based at least in part on the interleaving pattern that is applied. The UE 120 may apply an interleaving pattern associated with the UE type of the UE 120 and if the result indicates a decodable RAR, then the UE 120 may decode the RAR.

[0098] In some aspects, the PDCCH used for scheduling the RAR may be polar coded for the PDCCH. DMRS sequences of the PDCCH may also be scrambled with a sequence associated with a scrambling ID. The UE 120 may determine if the RAR is to be decoded based at least in part on the scrambling ID that is applied to the DMRS sequences. A first set of scrambling IDs may be associated with Type A UEs, and a second (orthogonal or non-intersecting) set of scrambling IDs may be associated with Type B UEs. In some aspects, the DCI may be scrambled with a sequence associated with a scrambling ID. The UE 120 may determine if the RAR is to be decoded based at least in part on the scrambling ID that is applied to the DCI or other coded bits of the PDCCH. By using an interleaving pattern, a scrambling ID, or other encoding feature, the UE 120 may differentiate RARs by UE type to determine if an RAR is to be decoded by the UE 120 or if the UE 120 is to conserve power and processing resources by not decoding the RAR.

[0099] FIG. 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with the present disclosure. Example process 800 is an example where the UE (e.g., UE 120) performs operations associated with differentiating RARs.

[0100] As shown in FIG. 8, in some aspects, process 800 may include receiving an RAR (block 810). For example, the UE (e.g., using reception component 1002 depicted in FIG. 10) may receive an RAR, as described above.

[0101] As further shown in FIG. 8, in some aspects, process 800 may include decoding the RAR based at least in part on information that differentiates RARs according to UE type (block 820). For example, the UE (e.g., using decoding component 1008 depicted in FIG. 10) may decode the RAR based at least in part on information that differentiates RARs according to UE type, as described above.

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

[0103] In a first aspect, decoding the RAR based at least in part on the information includes decoding the RAR if the information indicates that the RAR is to be decoded by the UE type of the UE.

[0104] In a second aspect, alone or in combination with the first aspect, process 800 includes transmitting a communication based at least in part on the RAR.

[0105] In a third aspect, alone or in combination with one or more of the first and second aspects, the RAR is not decoded if the information does not indicate that the RAR is to be decoded by the UE type of the UE.

[0106] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an initial BWP configuration.

[0107] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first UE type shares an initial uplink BWP with the second UE type.

[0108] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, an initial uplink BWP for the first UE type is different than an initial uplink BWP for the second UE type.

[0109] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

[0110] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type are non-overlapping.

[0111] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, an initial downlink BWP for the first UE type is different than an initial downlink BWP for the second UE type.

[0112] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap.

[0113] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

[0114] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the information includes a CRC that is masked with an RNTI, and the RNTI differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0115] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, decoding the RAR based at least in part on the information includes extracting the RNTI from the CRC, calculating a modified RNTI based at least in part on one or more of an index value of a first symbol of a PRACH occasion of the RAR, an index of a first slot of the PRACH occasion in a system frame, and an index of the PRACH occasion in a frequency domain, and decoding the RAR if the RNTI extracted from the RNTI is in a set of RNTIs indicated by the modified RNTI.

[0116] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the information includes a CRC that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an interleaving pattern that is applied to the CRC.

[0117] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, decoding the RAR based at least in part on the information includes applying one or more of a first interleaving pattern or a second interleaving pattern to the CRC, where the first interleaving pattern is associated with the first UE type and the second interleaving pattern is associated with the second UE type, and decoding the RAR based at least in part on a result of the applying.

[0118] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the information includes DMRS sequences that differentiate between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling ID set that is applied to the DMRS sequences.

[0119] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, decoding the RAR based at least in part on the information includes applying one or more of a first scrambling ID set or a second scrambling ID set to the DMRS sequences, where the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type, and decoding the RAR based at least in part on a result of the applying.

[0120] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the information includes DCI that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling ID set that is applied to the DCI.

[0121] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, decoding the RAR based at least in part on the information includes applying one or more of a first scrambling ID set or a second scrambling ID set to the DCI, where the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type, and decoding the RAR based at least in part on a result of the applying.

[0122] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the information includes a CORESET that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a location (e.g., time-frequency resource) of the CORESET.

[0123] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the information includes a precoding or spatial domain that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0124] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the information includes a QCLed relation or spatial relation for scheduling that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0125] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the information includes a reserve bit or a spare bit in DCI (DCI payload) that indicates that the RAR is for a first UE type or for a second UE type.

[0126] In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the information includes one or more PRACH formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0127] In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, the information includes a CRC that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on being associated with a first set of PRACH preambles for the first UE type or a second set of PRACH preambles for the second UE type.

[0128] In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the first UE type includes UEs with a distance from a cell center that satisfies a distance threshold and the second UE type includes UEs with a distance from a cell center that does not satisfy the distance threshold.

[0129] In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, process 800 includes, prior to receiving the RAR: obtaining an initial BWP configuration for random access that indicates an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE, and transmitting a random access message within the initial uplink BWP configured for the UE type of the UE.

[0130] In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, receiving the RAR includes receiving the RAR within the initial downlink BWP configured for the UE type of the UE.

[0131] In a twenty-ninth aspect, alone or in combination with one or more of the first through twenty-eighth aspects, obtaining the configuration includes receiving the configuration in a first initial downlink BWP.

[0132] In a thirtieth aspect, alone or in combination with one or more of the first through twenty-ninth aspects, the first initial downlink BWP is different than the initial downlink BWP configured for the UE type of the UE, and the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on the initial BWP configuration.

[0133] Although FIG. 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0134] FIG. 9 is a diagram illustrating an example process 900 performed, for example, by a base station, in accordance with the present disclosure. Example process 900 is an example where the base station (e.g., base station 110) performs operations associated with differentiating RARs.

[0135] As shown in FIG. 9, in some aspects, process 900 may include encoding an RAR for a UE with information that differentiates RARs according to UE type and based at least in part on a UE type of the UE (block 910). For example, the base station (e.g., using encoding component 1108 depicted in FIG. 11) may encode an RAR for a UE with information that differentiates RARs according to UE type and based at least in part on a UE type of the UE, as described above.

[0136] As further shown in FIG. 9, in some aspects, process 900 may include transmitting the RAR to the UE (block 920). For example, the base station (e.g., using transmission component 1104 depicted in FIG. 11) may transmit the RAR to the UE, as described above.

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

[0138] In a first aspect, process 900 includes receiving a communication based at least in part on the RAR.

[0139] In a second aspect, alone or in combination with the first aspect, the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an initial BWP configuration.

[0140] In a third aspect, alone or in combination with one or more of the first and second aspects, the first UE type shares an initial uplink BWP with the second UE type.

[0141] In a fourth aspect, alone or in combination with one or more of the first through third aspects, an initial uplink BWP for the first UE type is different than an initial uplink BWP for the second UE type.

[0142] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

[0143] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type are non-overlapping.

[0144] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, an initial downlink BWP for the first UE type is different than an initial downlink BWP for the second UE type.

[0145] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap.

[0146] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

[0147] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, encoding the RAR based at least in part on the information includes calculating an RNTI based at least in part on one or more of an index value of a first symbol of a PRACH occasion for the RAR, an index of a first slot of the PRACH occasion in a system frame, and an index of the PRACH occasion in a frequency domain, where the RNTI differentiates between an RAR for a first UE type and an RAR for a second UE type, and masking a CRC of the RAR with the RNTI.

[0148] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the information includes a CRC that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an interleaving pattern that is applied to the CRC.

[0149] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the information includes DMRS sequences that differentiate between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling ID set that is applied to the DMRS sequences.

[0150] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the information includes DCI that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling ID set that is applied to the DCI.

[0151] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, encoding the RAR based at least in part on the information includes placing a CORESET of the RAR in a location that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0152] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the information includes a precoding that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0153] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the information includes a QCLed relation for scheduling that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0154] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the information includes a reserve bit or a spare bit in DCI that indicates that the RAR is for a first UE type or for a second UE type.

[0155] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the information includes one or more PRACH formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0156] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the information includes a CRC that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on being associated with a first set of PRACH preambles for the first UE type or a second set of PRACH preambles for the second UE type.

[0157] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the first UE type includes UEs with a distance from a cell center that satisfies a distance threshold and the second UE type includes UEs with a distance from a cell center that does not satisfy the distance threshold.

[0158] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, process 900 includes, prior to transmitting the RAR: transmitting, to a UE, an initial BWP configuration for random access that indicates an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE; and receiving a random access message within the initial uplink BWP configured for the UE type of the UE.

[0159] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, transmitting the RAR includes transmitting the RAR within the initial downlink BWP configured for the UE type of the UE.

[0160] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, transmitting the configuration includes transmitting the configuration in a first initial downlink BWP.

[0161] In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the first initial downlink BWP is different than the initial downlink BWP configured for the UE type of the UE, and the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on the initial BWP configuration.

[0162] Although FIG. 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0163] FIG. 10 is a block diagram of an example apparatus 1000 for wireless communication. The apparatus 1000 may be a UE, or a UE may include the apparatus 1000. In some aspects, the apparatus 1000 includes a reception component 1002 and a transmission component 1004, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using the reception component 1002 and the transmission component 1004. As further shown, the apparatus 1000 may include a decoding component 1008, among other examples.

[0164] In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein in connection with FIGS. 1-7. Additionally, or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as process 800 of FIG. 8. In some aspects, the apparatus 1000 and/or one or more components shown in FIG. 10 may include one or more components of the UE described above in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 10 may be implemented within one or more components described above in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0165] The reception component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1006. The reception component 1002 may provide received communications to one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with FIG. 2.

[0166] The transmission component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1006. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmission component 1004 for transmission to the apparatus 1006. In some aspects, the transmission component 1004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1006. In some aspects, the transmission component 1004 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with FIG. 2. In some aspects, the transmission component 1004 may be co-located with the reception component 1002 in a transceiver.

[0167] The reception component 1002 may receive an RAR. The decoding component 1008 may decode the RAR based at least in part on information that differentiates RARs according to UE type. The transmission component 1004 may transmit a communication based at least in part on the RAR.

[0168] The number and arrangement of components shown in FIG. 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 10. Furthermore, two or more components shown in FIG. 10 may be implemented within a single component, or a single component shown in FIG. 10 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 10 may perform one or more functions described as being performed by another set of components shown in FIG. 10.

[0169] FIG. 11 is a block diagram of an example apparatus 1100 for wireless communication. The apparatus 1100 may be a base station, or a base station may include the apparatus 1100. In some aspects, the apparatus 1100 includes a reception component 1102 and a transmission component 1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the reception component 1102 and the transmission component 1104. As further shown, the apparatus 1100 may include one or more of an encoding component 1108, among other examples.

[0170] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with FIGS. 1-7. Additionally, or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 900 of FIG. 9. In some aspects, the apparatus 1100 and/or one or more components shown in FIG. 11 may include one or more components of the base station described above in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 11 may be implemented within one or more components described above in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0171] The reception component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106. The reception component 1102 may provide received communications to one or more other components of the apparatus 1100. In some aspects, the reception component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1100. In some aspects, the reception component 1102 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with FIG. 2.

[0172] The transmission component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1106. In some aspects, one or more other components of the apparatus 1100 may generate communications and may provide the generated communications to the transmission component 1104 for transmission to the apparatus 1106. In some aspects, the transmission component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1106. In some aspects, the transmission component 1104 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with FIG. 2. In some aspects, the transmission component 1104 may be co-located with the reception component 1102 in a transceiver.

[0173] The encoding component 1108 may encode an RAR for a UE with information that differentiates RARs according to UE type and based at least in part on a UE type of the UE. The transmission component 1104 may transmit the RAR to the UE. The reception component 1102 may receive a communication based at least in part on the RAR.

[0174] The number and arrangement of components shown in FIG. 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 11. Furthermore, two or more components shown in FIG. 11 may be implemented within a single component, or a single component shown in FIG. 11 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 11 may perform one or more functions described as being performed by another set of components shown in FIG. 11.

[0175] 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 aspects.

[0176] The following provides an overview of some Aspects of the present disclosure:

[0177] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a random access response (RAR); and decoding the RAR based at least in part on information that differentiates RARs according to UE type.

[0178] Aspect 2: The method of Aspect 1, wherein decoding the RAR based at least in part on the information includes decoding the RAR if the information indicates that the RAR is to be decoded by the UE type of the UE.

[0179] Aspect 3: The method of Aspect 2, further comprising transmitting a communication based at least in part on the RAR.

[0180] Aspect 4: The method of any of Aspects 1-3, wherein the RAR is not decoded if the information does not indicate that the RAR is to be decoded by the UE type of the UE.

[0181] Aspect 5: The method of any of Aspects 1-4, wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an initial bandwidth part (BWP) configuration.

[0182] Aspect 6: The method of Aspect 5, wherein the first UE type shares an initial uplink BWP with the second UE type.

[0183] Aspect 7: The method of Aspect 5, wherein an initial uplink BWP for the first UE type is different than an initial uplink BWP for the second UE type.

[0184] Aspect 8: The method of Aspect 7, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

[0185] Aspect 9: The method of Aspect 7, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type are non-overlapping.

[0186] Aspect 10: The method of Aspect 7, wherein an initial downlink BWP for the first UE type is different than an initial downlink BWP for the second UE type.

[0187] Aspect 11: The method of Aspect 10, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap.

[0188] Aspect 12: The method of Aspect 10, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

[0189] Aspect 13: The method of any of Aspects 1-12, wherein the information includes a cyclic redundancy check (CRC) that is masked with a radio network temporary identifier (RNTI), and wherein the RNTI differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0190] Aspect 14: The method of Aspect 13, wherein decoding the RAR based at least in part on the information includes: extracting the RNTI from the CRC; calculating a modified RNTI based at least in part on one or more of an index value of a first symbol of a physical random access channel (PRACH) occasion of the RAR, an index of a first slot of the PRACH occasion in a system frame, and an index of the PRACH occasion in a frequency domain; and decoding the RAR if the RNTI extracted from the RNTI is in a set of RNTIs indicated by the modified RNTI.

[0191] Aspect 15: The method of any of Aspects 1-4, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an interleaving pattern that is applied to the CRC.

[0192] Aspect 16: The method of Aspect 15, wherein decoding the RAR based at least in part on the information includes: applying one or more of a first interleaving pattern or a second interleaving pattern to the CRC, wherein the first interleaving pattern is associated with the first UE type and the second interleaving pattern is associated with the second UE type; and decoding the RAR based at least in part on a result of the applying.

[0193] Aspect 17: The method of any of Aspects 1-16, wherein the information includes demodulation reference signal (DMRS) sequences that differentiate between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DMRS sequences.

[0194] Aspect 18: The method of Aspect 17, wherein decoding the RAR based at least in part on the information includes: applying one or more of a first scrambling ID set or a second scrambling ID set to the DMRS sequences, wherein the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type; and decoding the RAR based at least in part on a result of the applying.

[0195] Aspect 19: The method of any of Aspects 1-18, wherein the information includes downlink control information (DCI) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DCI.

[0196] Aspect 20: The method of Aspect 19, wherein decoding the RAR based at least in part on the information includes: applying one or more of a first scrambling ID set or a second scrambling ID set to the DCI, wherein the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type; and decoding the RAR based at least in part on a result of the applying.

[0197] Aspect 21: The method of any of Aspects 1-20, wherein the information includes a control resource set (CORESET) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a location of the CORESET.

[0198] Aspect 22: The method of any of Aspects 1-21, wherein the information includes a precoding that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0199] Aspect 23: The method of any of Aspects 1-22, wherein the information includes a quasi-co-located relation for scheduling that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0200] Aspect 24: The method of any of Aspects 1-23, wherein the information includes a reserve bit or a spare bit in downlink control information that indicates that the RAR is for a first UE type or for a second UE type.

[0201] Aspect 25: The method of any of Aspects 1-24, wherein the information includes one or more physical random access channel (PRACH) formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0202] Aspect 26: The method of any of Aspects 1-25, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on being associated with a first set of physical random access channel (PRACH) preambles for the first UE type or a second set of PRACH preambles for the second UE type.

[0203] Aspect 27: The method of Aspect 26, wherein the first UE type includes UEs with a distance from a cell center that satisfies a distance threshold and the second UE type includes UEs with a distance from a cell center that does not satisfy the distance threshold.

[0204] Aspect 28: The method of any of Aspects 1-24, further comprising, prior to receiving the RAR: obtaining an initial bandwidth part (BWP) configuration for random access that indicates an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE; and transmitting a random access message within the initial uplink BWP configured for the UE type of the UE.

[0205] Aspect 29: The method of Aspect 28, wherein receiving the RAR includes receiving the RAR within the initial downlink BWP configured for the UE type of the UE.

[0206] Aspect 30: The method of Aspect 28 or 29, wherein obtaining the configuration includes receiving the configuration in a first initial downlink BWP.

[0207] Aspect 31: The method of Aspect 30, wherein the first initial downlink BWP is different than the initial downlink BWP configured for the UE type of the UE, and wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on the initial BWP configuration.

[0208] Aspect 32: A method of wireless communication performed by a base station, comprising: encoding a random access response (RAR) for a user equipment (UE) with information that differentiates RARs according to UE type and based at least in part on a UE type of the UE; and transmitting the RAR to the UE.

[0209] Aspect 33: The method of Aspect 32, further comprising receiving a communication based at least in part on the RAR.

[0210] Aspect 34: The method of Aspect 32 or 33, wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an initial bandwidth part (BWP) configuration.

[0211] Aspect 35: The method of Aspect 34, wherein the first UE type shares an initial uplink BWP with the second UE type.

[0212] Aspect 36: The method of Aspect 34, wherein an initial uplink BWP for the first UE type is different than an initial uplink BWP for the second UE type.

[0213] Aspect 37: The method of Aspect 36, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

[0214] Aspect 38: The method of Aspect 36, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type are non-overlapping.

[0215] Aspect 39: The method of Aspect 36, wherein an initial downlink BWP for the first UE type is different than an initial downlink BWP for the second UE type.

[0216] Aspect 40: The method of Aspect 39, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap.

[0217] Aspect 41: The method of Aspect 39, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

[0218] Aspect 42: The method of any of Aspects 32-41, wherein encoding the RAR based at least in part on the information includes: calculating a radio network temporary identifier (RNTI) based at least in part on one or more of an index value of a first symbol of a physical random access channel (PRACH) occasion for the RAR, an index of a first slot of the PRACH occasion in a system frame, and an index of the PRACH occasion in a frequency domain, wherein the RNTI differentiates between an RAR for a first UE type and an RAR for a second UE type; and masking a cyclic redundancy check (CRC) of the RAR with the RNTI.

[0219] Aspect 43: The method of any of Aspects 32-42, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on an interleaving pattern that is applied to the CRC.

[0220] Aspect 44: The method of any of Aspects 32-43, wherein the information includes demodulation reference signal (DMRS) sequences that differentiate between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DMRS sequences.

[0221] Aspect 45: The method of any of Aspects 32-44, wherein the information includes downlink control information (DCI) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on a scrambling identifier (ID) set that is applied to the DCI.

[0222] Aspect 46: The method of any of Aspects 32-45, wherein encoding the RAR based at least in part on the information includes placing a control resource set (CORESET) of the RAR in a location that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0223] Aspect 47: The method of any of Aspects 32-46, wherein the information includes a precoding that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0224] Aspect 48: The method of any of Aspects 32-47, wherein the information includes a quasi-co-located relation for scheduling that differentiates between an RAR for a first UE type and an RAR for a second UE type.

[0225] Aspect 49: The method of any of Aspects 32-48, wherein the information includes a reserve bit or a spare bit in downlink control information that indicates that the RAR is for a first UE type or for a second UE type.

[0226] Aspect 50: The method of any of Aspects 32-49, wherein the information includes one or more physical random access channel (PRACH) formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0227] Aspect 51: The method of any of Aspects 32-50, wherein the information includes a cyclic redundancy check (CRC) that differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on being associated with a first set of physical random access channel (PRACH) preambles for the first UE type or a second set of PRACH preambles for the second UE type.

[0228] Aspect 52: The method of Aspect 51, wherein the first UE type includes UEs with a distance from a cell center that satisfies a distance threshold and the second UE type includes UEs with a distance from a cell center that does not satisfy the distance threshold.

[0229] Aspect 53: The method of any of Aspects 32-52, further comprising, prior to transmitting the RAR: transmitting, to a UE, an initial bandwidth part (BWP) configuration for random access that indicates an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE; and receiving a random access message within the initial uplink BWP configured for the UE type of the UE.

[0230] Aspect 54: The method of Aspect 53, wherein transmitting the RAR includes transmitting the RAR within the initial downlink BWP configured for the UE type of the UE.

[0231] Aspect 55: The method of Aspect 52 or 53, wherein transmitting the configuration includes transmitting the configuration in a first initial downlink BWP.

[0232] Aspect 56: The method of Aspect 55, wherein the first initial downlink BWP is different than the initial downlink BWP configured for the UE type of the UE, and wherein the information differentiates between an RAR for a first UE type and an RAR for a second UE type based at least in part on the initial BWP configuration.

[0233] Aspect 57: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-56.

[0234] Aspect 58: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more of Aspects 1-56.

[0235] Aspect 59: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-56.

[0236] Aspect 60: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-56.

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

[0238] As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a processor is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

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

[0240] Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. 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, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

[0241] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).