Random access response differentiation

Abstract

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

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 201,165, filed April 15, 2021, entitled “RANDOMACCESS RESPONSE DIFFERENTIATION,” and U.S. Non-Provisional Patent Application No. 17 / 652,906, filed February 28, 2022, entitled “RANDOMACCESS RESPONSE DIFFERENTIATION,” which are hereby expressly incorporated by reference.

[0003] open field

[0004] Various aspects of this disclosure generally relate to wireless communications and techniques and apparatus for distinguishing random access responses. Background Technology

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0006] A wireless network may include several base stations (BSs) capable of supporting communication for several user equipments (UEs). UEs may communicate with the BS via downlink and uplink. "Downlink" or "forward link" refers to the communication link from the BS to the UE, while "uplink" or "backlink" refers to the communication link from the UE to the BS. As will be described in more detail herein, the BS may be referred to as a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5G B-node, etc.

[0007] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the city, country, region, and even global levels. NR (which can also be referred to as 5G) is an enhancement set of the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL), and using CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to grow.

[0008] Overview

[0009] In some aspects, a wireless communication method performed by a user equipment (UE) includes: receiving a random access response (RAR) and decoding the RAR based at least in part on information that distinguishes the RAR according to the UE type.

[0010] In some aspects, a wireless communication method performed by a base station includes: encoding a RAR for the UE using information that distinguishes the RAR according to the UE type and at least in part based on the UE type of the UE, and transmitting the RAR to the UE.

[0011] In some aspects, a UE for wireless communication includes: a memory and one or more processors coupled to the memory, the one or more processors being configured to: receive a RAR and decode the RAR at least in part based on information that distinguishes the RAR according to the UE type.

[0012] In some aspects, a base station for wireless communication includes: a memory and one or more processors coupled to the memory, the one or more processors being configured to: encode a RAR for the UE using information that distinguishes RARs according to the UE type and at least in part based on the UE type of the UE, and transmit the RAR to the UE.

[0013] In some aspects, a non-transient computer-readable medium stores a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a UE, cause the UE to perform the following actions: receiving a RAR, and decoding the RAR based at least in part on information that distinguishes the RAR according to the UE type.

[0014] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a base station, cause the base station to perform the following operations: encoding a RAR for the UE based on information distinguishing the RAR according to the UE type and at least in part based on the UE type of the UE, and transmitting the RAR to the UE.

[0015] In some aspects, an apparatus for wireless communication includes: means for receiving a RAR, and means for decoding the RAR at least in part based on information that distinguishes the RAR according to the UE type.

[0016] In some aspects, an apparatus for wireless communication includes: means for encoding a RAR for a UE based at least in part on information that distinguishes the RAR according to the UE type and at least partially based on the UE type of the UE; and means for transmitting the RAR to the UE.

[0017] The aspects generally include, as described herein with reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, as illustrated in the drawings and description.

[0018] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described thereafter. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not for defining limitations on the claims.

[0019] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package layouts. For example, some aspects may be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, or AI-enabled devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include several components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers) for analog and digital purposes. The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user equipment of various sizes, shapes, and configurations. Brief description of the attached diagram

[0021] To gain a more detailed understanding of the features described above in this disclosure, reference can be made to various aspects of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. Identical reference numerals in different drawings may identify the same or similar elements.

[0022] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0023] Figure 2 This is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to this disclosure.

[0024] Figure 3 This is a diagram illustrating the type of equipment according to this disclosure.

[0025] Figure 4 An example of configuration for a new Radio Reduced Capability (RedCap) UE according to this disclosure is explained.

[0026] Figure 5 This is a diagram illustrating an example of distinguishing random access responses (RARs) according to this disclosure.

[0027] Figure 6This is a diagram illustrating an example of distinguishing between overlapping and non-overlapping bandwidth portions of a RAR according to this disclosure.

[0028] Figure 7 This is a diagram illustrating an example of downlink control information used for scheduling RAR according to the coding of this disclosure.

[0029] Figure 8 This is a diagram illustrating an example procedure performed by a UE according to this disclosure.

[0030] Figure 9 This is a diagram illustrating an example process performed by a base station according to this disclosure.

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

[0032] Detailed description

[0033] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as being limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

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

[0035] It should be noted that although the aspects herein may be described using terms commonly associated with 5G or NR radio access technology (RAT), the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0036] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. The wireless network 100 may be a 5G (NR) network and / or an LTE network, etc., or may include elements thereof. The wireless network 100 may include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, B-node, gNB, 5G B-node (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0037] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with a service subscription. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1 In the example shown, BS110a can be a macro BS for macro cell 102a, BS110b can be a pico BS for pico cell 102b, and BS110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” are used interchangeably herein.

[0038] In some respects, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks, using any suitable transport network).

[0039] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to an aggregated base station, a decomposed 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 a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the performance of at least a portion of that function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some respects, 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 respects, two or more base station functions may be instantiated on a single device. In some respects, the term "base station" or "network entity" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

[0040] The wireless network 100 may also include a relay station. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting those data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS110d can communicate with macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay, etc.

[0041] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0042] Network controller 130 can be coupled to a set of Base Stations (BSs) and can provide coordination and control over these BSs. Network controller 130 can communicate with each BS via backhaul. These BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0043] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), entertainment device (e.g., music or video device, or satellite radio), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, Global Positioning System (GPS) device, or any other suitable device configured to communicate via wireless or wired media.

[0044] Some UEs may be RedCap UEs, capable of decoding the Random Access Response (RAR) as part of the Random Access Channel (RACH) procedure for establishing a Radio Resource Control (RRC) connection. Different types of UEs may exist that are capable of decoding the RAR only if the RAR is configured for that UE type. Some UEs may be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes may provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network) via wired or wireless communication links, for example. 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 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 memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0046] In some respects, 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 base station 110 as an intermediary). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this scenario, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as performed by base station 110.

[0047] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1) and / or an operating band with a second frequency range (FR2), where the first frequency range (FR1) spans from 410 MHz to 7.125 GHz and the second frequency range (FR2) spans from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency bands. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to as the "millimeter wave" band. Therefore, unless otherwise stated, it should be understood that, if used herein, the term "sub-6GHz," etc., can broadly refer to frequencies less than 6GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125GHz). Similarly, unless otherwise stated, it should be understood that, if used herein, the term "millimeter wave," etc., can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25GHz). It is conceivable that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] As indicated above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0049] Figure 2 This is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to this disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein generally T≥1 and R≥1.

[0050] At base station 110, transmit processor 220 can receive data destined for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource allocation 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 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0051] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some respects, one or more components of the UE 120 may be included in the housing 284.

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

[0053] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or be included therein, one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or multiple antenna elements within housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include elements coupled to one or more transmission and / or reception components (such as...). Figure 2 One or more antenna elements (one or more components).

[0054] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-encoded by TX MIMO processor 266 where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, modulators and demodulators (e.g., MOD / DEMOD 254) of UE 120 may be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receiver processors 258, transmitter processors 264, and / or TX MIMO processors 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 (e.g., as referenced). Figure 3-11 (As described).

[0055] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include (such as) antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or any combination of 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 (e.g., as referenced). Figure 3-11 (As described).

[0056] Communication systems (such as 5G NR systems) can be deployed with various components or parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as base stations, or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, a base station (such as a B node, evolved NB (eNB), NRBS, 5G NB, access point (AP), TRP, or cell) can be implemented as an aggregated base station (also known as a self-contained BS or monolithic BS) or a decomposed base station.

[0057] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some respects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU).

[0058] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units across various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Individual units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0059] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more technologies associated with the RAR as part of the RACH protocol, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may execute or direct, for example Figure 8 The process 800 Figure 9The operation of process 900 and / or other processes as described herein. Memory 242 and 282 may store data and program code of 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, when executed by one or more processors of base station 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation), the one or more processors, UE 120, and / or base station 110 may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 8 The process 800 Figure 9 The operation of process 900, and / or other processes described herein. In some aspects, the execution instructions may include run instructions, translate instructions, compile instructions, and / or interpret instructions, etc.

[0060] In some aspects, UE 120 includes: means for receiving a RAR, and / or means for decoding the RAR at least in part based on information that distinguishes the RAR according to the UE type. Means for UE 120 to perform the 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.

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

[0062] although Figure 2 The boxes in the diagram are interpreted as different components, but the functions described above with respect to these boxes can be implemented using a single hardware component, software component, or combination of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0063] As indicated above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0064] Figure 3 This is a diagram 300 illustrating the type of equipment according to this disclosure.

[0065] like Figure 3 As shown, Ultra-Reliable Low Latency Communication (URLLC) devices and Enhanced Mobile Broadband (eMBB) devices can be considered high-end NR devices (e.g., UEs). Some devices (such as Low Power Wide Area (LPWA) devices or Massive Machine-Type Communication (mMTC) devices) can be considered advanced LTE devices. Figure 3 Some wireless communication devices are shown that are not NR high-end UEs, but rather devices with reduced capabilities. Such devices with reduced capabilities can include loose 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, and / or NR RedCap UEs. NR RedCap devices may also be referred to as NR Light devices or NR Lite devices. For illustrative purposes, the term NR RedCap UE may be used in all aspects described herein.

[0066] In some respects, NR RedCap UEs may have reduced capabilities due to their ability or configuration to offer lower peak throughput, longer latency, lower reliability, higher power efficiency, lower system overhead, and / or lower resource costs. NR RedCap UEs can withstand less stringent latency or reliability requirements. In some respects, NR RedCap UEs may have only one or two transmit or receive antennas.

[0067] In some respects, an NR RedCap UE may have or be configured to use a subset of the functions available to an NR high-end UE or other full-featured NR UEs that can be used for personal communications. In some respects, an NR RedCap UE may have a mandatory set of functions and an optional set of functions, wherein one or more optional changes in the NR RedCap UE are mandatory for the NR high-end UE. In some respects, a standard function chart or matrix may be used to explicitly define whether a device is an NR RedCap UE.

[0068] In some respects, NR RedCap UE may include wearable devices such as smartwatches, electronic health-related devices, personal protective equipment, exercise monitors, or medical monitoring devices. NR RedCap UE may include industrial sensors such as pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, or actuators. NR RedCap UE may include surveillance cameras, low-end smartphones, and / or low-end IoT devices.

[0069] As indicated above, Figure 3 This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

[0070] Figure 4 Example 400 of the configuration for NR RedCap UE according to this disclosure is explained.

[0071] In some respects, NR RedCap UEs can support reduced bandwidth and a reduced number of transmit and receive antennas. For example, at least for FR1, an NR RedCap UE can support a maximum bandwidth of 20 MHz or 40 MHz in the downlink (DL) or uplink (UL). NR RedCap UEs can support maximum bandwidths configured separately for DL ​​and UL. For NR RedCap UEs with reduced bandwidth capabilities (e.g., from 100 MHz down for FR1), the maximum bandwidth in UL and DL can be reduced to accommodate control information or data. NR RedCap UEs with reduced bandwidth capabilities are not expected to support carrier aggregation or dual connectivity, which is required for non-NR RedCap UEs. In some embodiments, an NR RedCap UE can support a maximum of one transmit antenna and a maximum of one or two receive antennas.

[0072] Figure 4 This section illustrates other configurations that NR RedCap UEs of various types, at least in part, can support. Different types may have different functionalities or subsets of limitations. For example, an NR RedCap UE as a wearable device may support a DL peak rate of 150 Mbps, a UL peak rate of 50 Mbps, a bandwidth requirement of 20 MHz or 40 MHz, one transmit antenna, and one or two receive antennas. Wearable devices may not support 256-QAM. Wearable devices may have moderate mobility and high power efficiency requirements. Wearable devices may still have latency or reliability requirements similar to eMBB.

[0073] In some aspects, the NR RedCap UE as an industrial sensor can support DL peak rates of less than 2 Mbps, UL peak rates of less than 5 Mbps, bandwidth requirements of 5 MHz or 10 MHz, one transmit antenna, and one receive antenna. The sensor may not support 256-QAM. The sensor may have low mobility and high power efficiency requirements. The sensor may have latency requirements of less than 100 milliseconds (ms), or 5-10 ms for safety-related sensors. The sensor may have a 99.99% reliability requirement.

[0074] In some aspects, the NR RedCap UE as a video surveillance camera can support DL peak rates of less than 5 Mbps, UL peak rates of less than 25 Mbps, bandwidth requirements of 10 MHz or 20 MHz, one or two transmit antennas, and one receive antenna. The camera may not support 256-QAM. The camera may have low mobility and high power efficiency requirements. The camera may have latency requirements of less than 500 ms and reliability requirements of 99%-99.99%.

[0075] In summary, NR RedCap UEs can have a defined configuration, at least in part, based on their type. As a result, NR RedCap UEs can conserve power, processing resources, and signaling resources, and support a reduced set of functions. In some respects, NR RedCap UEs can support the same power-saving modes, the same set of processing capabilities and timelines, or the same set of fallback capabilities as another type of NR UE, which may or may not have reduced capabilities. For example, an NR RedCap UE may have a set of reduced capabilities but can fall back to a set of further reduced capabilities.

[0076] NR RedCap UEs may be required to execute RACH procedures for accessing channels and establishing connections. The RACH procedure can be the same for each UE, even if different UEs have different UE capabilities. In some scenarios, the base station may transmit multiple RACH messages to multiple UEs, such as multiple RARs. UEs with limited capabilities may waste power and processing resources attempting to decode and process RARs that may not be intended for that UE.

[0077] As described herein, a UE can receive a RAR as part of a RACH procedure and decode the RAR based at least in part on information that distinguishes the RAR according to the UE type. That is, a UE can decode a RAR if the information indicates that the RAR should be decoded by the UE's UE type. A RAR may be designed for a first UE type (e.g., Type A) or a second UE type (e.g., Type B), but not for either. Examples of a first UE type relative to a second UE type may include: a RedCap UE relative to a non-RedCap UE, a RedCap UE with one receive antenna branch relative to a RedCap UE with two receive antenna branches, a UE supporting coverage enhancement relative to a UE not supporting coverage enhancement, a UE supporting small data transmission (SDT) relative to a UE not supporting SDT, and a UE supporting RAN slicing relative to a UE not supporting RAN slicing. By distinguishing RARs, a UE can decode RARs designed for that UE (or that UE's UE type) and save power and processing resources by not attempting to decode and process RARs not designed for that UE (or that UE's UE type). The UE can receive information for RAR differentiation or obtain information from stored configuration information. This information instructs the UE on how to determine whether to decode RAR or other RACH messages.

[0078] As indicated above, Figure 4 This is provided as an example. Other examples may differ from the one provided. Figure 4 The example described.

[0079] Figure 5 This is an illustration of Example 500, explaining the differentiation of RARs according to this disclosure. For example... Figure 5 As shown, base station 110 and UE 120 can communicate with each other to perform the 4-step RACH procedure.

[0080] As indicated by reference numeral 505, base station 110 can transmit, and UE 120 can receive, random access configuration information. In some aspects, the random access configuration information may be transmitted and / or indicated by system information (e.g., in one or more System Information Blocks (SIBs) (such as SIB 2)) and / or Synchronization Signal Blocks (SSBs), such as for contention-based random access. Additionally or alternatively, the random access configuration information may be transmitted in RRC messages that trigger RACH procedures and / or Physical Downlink Control Channel (PDCCH) command messages, such as for contention-free random access. The random access configuration information may include information for receiving RARs and for distinguishing RARs based on UE type.

[0081] As shown by reference numeral 510 in the attached figure, UE 120 may transmit a random access message (RAM), which may include a preamble (sometimes referred to as a random access preamble, physical RACH (PRACH) preamble, or RAM preamble). A message including a preamble may be referred to as Message 1, Msg1, msg1, MSG1, First Message, or Initial Message in a four-step RACH procedure. The RAM may include a random access preamble identifier.

[0082] As indicated by reference numeral 515, base station 110 may transmit a RAR as a response to a preamble. The message including the RAR may be referred to as message 2, Msg2, msg2, MSG2, or a second message in the four-step RACH procedure. In some respects, the RAR may indicate the detected random access preamble identifier (e.g., received from UE 120 in Msg1). Additionally or alternatively, the RAR may indicate uplink permission or resource allocation to be used by UE 120 for transmitting message 3 (Msg3).

[0083] In some respects, as part of the second step of the four-step random access procedure, base station 110 may transmit PDCCH communications for the RAR. The PDCCH communications may schedule Physical Downlink Shared Channel (PDSCH) communications that include the RAR. For example, the PDCCH communications may indicate resource allocation for the PDSCH communications. Similarly, as part of the second step of the four-step RACH procedure, base station 110 may transmit PDSCH communications for the RAR, as scheduled by the PDCCH communications. The RAR may be included in the MAC Protocol Data Unit (PDU) of the PDSCH communications.

[0084] As shown by reference numeral 520 in the attached figure, UE 120 can distinguish whether the RAR is for UE 120 or the UE type of UE 120. In some aspects, UE 120 can determine whether the RAR should be decoded by UE 120 based at least in part on the Initial Bandwidth Part (BWP) configuration (which can be configured separately for each UE type). This is combined with Figure 6 A more detailed description follows. In some aspects, UE 120 may determine whether a RAR should be decoded based at least in part on Cyclic Redundancy Check (CRC). For example, the CRC may be masked with a Radio Network Temporary Identifier (RNTI), and UE 120 may decode the RAR if the RNTI extracted from the CRC belongs to a specific set of RNTIs. In some aspects, UE 120 may determine whether a RAR should be decoded based at least in part on the interleaving mode or scrambling identifier (ID) used. Combined Figure 7 Let's describe these aspects in more detail.

[0085] In some respects, UE 120 may have information about different resources for PDCCH scheduling used for RAR. For example, UE 120 may have information about control resource sets (CORESETs) that differentiate between RARs for a first UE type and RARs for a second UE type. RARs can be scheduled via CORESETs, and UE 120 may determine the RAR to be decoded based at least in part on the location of the CORESET. Some CORESET locations may be reserved for UEs of the first UE type, and some CORESET locations may be reserved for UEs of the second UE type.

[0086] In some respects, UE 120 may have information about the decoding or quasi-co-location (QCL) relationship used for RAR scheduling. For example, the PDCCH may have a QCL with the SSB index reserved for UEs of a specific UE type. UE 120 may determine the RAR to be decoded based at least in part on the SSB index.

[0087] In some aspects, this information may include one or more reserved or spare bits in the downlink control information (DCI). For example, for DCI format 1_0, the CRC may be masked by the RNTI (e.g., random access RNTI, msgB-RNTI, modified RNTI). The mask may use (or reuse) reserved or spare bits (e.g., the most significant bit) to signal the UE type of the RAR. In some aspects, UE 120 may use any combination of scheduling resources to determine whether UE 120 should decode the RAR.

[0088] Multiple UE types can be supported in the serving cell or RAN slice. In some aspects, this information may include one or more PRACH formats associated with each UE type, and UE 120 may determine whether RAR should be decoded based at least in part on the PRACH format used. A UE type may be mapped to multiple PRACH formats, and different UE types may be mapped to different PRACH formats. For example, UE types can be distinguished by their location within the cell. Cell center UEs (e.g., UEs that meet a distance threshold or maximum distance from the cell center) may be mapped to a PRACH preamble with a short length, and cell edge UEs (UEs that do not meet a distance threshold or maximum distance from the cell center) may be mapped to a PRACH preamble with a longer length. UE 120 may determine its distance relative to base station 110 using, for example, GPS and / or measurements.

[0089] In some respects, PRACH preambles can be grouped into multiple sets characterized by different cyclic shifts. For example, for PRACH preambles sharing the same PRACH timing, the size of the cyclic shift (e.g., the cyclic prefix (CP)) can be scaled proportionally to the downlink RSRP of UE120. The CP used for the Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), or Probe Reference Signal (SRS) can be a normal CP (NCP) or an extended CP (ECP). For example, UE120 can perform an RSRP measurement and compare it with a threshold broadcast by base station 110 to determine which PRACH preamble group to use.

[0090] UEs located near the cell center have shorter round-trip times (RTTs), and this type of UE (near UE) can be mapped to a set of cyclic shifts with dense intervals, or excluded from PRACH resource selection using PRACH-free transmission. UEs located near the cell edge may have longer RTTs, and this type of UE (far UE) can be mapped to different sets of cyclic shifts with sparse intervals. UE 120 can determine whether the RAR should be decoded based at least in part on the interval of the cyclic shifts of the RAR.

[0091] As shown by reference numeral 525, UE 120 may decode the RAR if the RAR is intended for UE 120 or the UE type of UE 120. If the RAR is not intended for UE 120, UE 120 may not decode the RAR, thus saving the power and processing resources that would otherwise be consumed by decoding and processing the RAR.

[0092] The UE may transmit communications at least in part based on communications. As indicated by reference numeral 530, the UE 120 may transmit an RRC connection request message as a communication. The RRC connection request message may be referred to as message 3, Msg3, msg3, MSG3, or a third message in the four-step RACH procedure. In some aspects, the RRC connection request may include the UE identifier, uplink control information (UCI), and / or PUSCH communications (e.g., the RRC connection request). The base station 110 may transmit a Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) for Msg3.

[0093] As indicated by reference numeral 535, base station 110 may transmit an RRC connection establishment message. The RRC connection establishment message may be referred to as message 4, Msg4, msg4, MSG4, or the fourth message in the four-step RACH procedure. In some aspects, the RRC connection establishment message may include a detected UE identifier, a timing advance value, and / or contention resolution information. If UE 120 successfully receives the RRC connection establishment message, UE 120 may transmit a HARQ ACK. UE 120 may transmit a HARQ ACK for Msg4. As indicated by reference numeral 540, base station 110 may transmit a DCI with uplink permission for an RRC connection establishment completion message, indicating that UE 120 has completed establishing the RRC connection. As indicated by reference numeral 545, UE 120 may transmit the RRC connection establishment completion message.

[0094] If a two-step RACH is to be used, Msg1 and Msg3 can be considered as the first step (MsgA), and Msg2 and Msg4 can be considered as the second step (MsgB). In this scenario, UE 120 can transmit communication based at least in part on the RAR that distinguishes MsgB.

[0095] As indicated above, Figure 5 This is provided as an example. Other examples may differ from the one provided. Figure 5 The example described.

[0096] Figure 6 This is an illustration of Example 600, which explains how overlapping BWPs and non-overlapping BWPs are used to distinguish RARs according to this disclosure.

[0097] UE 120 can determine the RAR to differentiate for each UE type based at least in part on the initial BWP configuration. The initial BWP configuration can indicate which BWP is activated for UL and which BWP is activated for DL. The configurations for the initial DL BWP and initial UL BWP can be specified by a standardized lookup table or indicated by system information. Example 600 illustrates different UE types, Type A and Type B. Type A can be, for example, a UE with energy harvesting capabilities that is active during time intervals orthogonal to those of Type B UEs, and Type B UEs can be, for example, powered by non-rechargeable batteries.

[0098] In some respects, the initial DL BWP and the initial UL BWP can be shared between UEs with both Type A and Type B capabilities. In other respects, the initial DL BWP can be shared, but the initial UL BWP can be configured separately for Type A and Type B. The initial UL BWPs for Type A and Type B can partially overlap. Example 600 shows an overlapping BWP 602 aligned at a reference point, which can be the center frequency of the initial UE BWP. Example 600 also shows an overlapping BWP 604 aligned at the starting physical resource block. The initial UL BWP for Type A and the initial UL BWP for Type B can not overlap, as shown by a non-overlapping BWP 606 (e.g., different subbands of the same carrier, different carriers (e.g., Normal Uplink (NUL) and Supplementary Uplink (SUL))). A non-overlapping BWP 608 can be time-separated and / or configured with different timers according to Time Division Multiplexing (TDM).

[0099] In some respects, the initial DL BWP and initial UL BWP can be configured separately for Type A and Type B. The initial DL BWP and / or initial UL BWP can partially overlap and be aligned at a reference point determined by base station 110. In some respects, the initial DL and / or UL BWP for Type A and the initial DL and / or UL BWP for Type B can not overlap and can be mapped to different carriers (e.g., normal downlink (NDL) and supplementary downlink (SDL), NUL and SUL), mapped to different subbands of the same carrier, and / or mapped to different TDM slots or different timer configurations.

[0100] As indicated above, Figure 6 This is provided as an example. Other examples may differ from the one provided. Figure 6 The example described.

[0101] Figure 7This is a diagram illustrating Example 700 of a DCI used for scheduling RAR according to the encoding of this disclosure. Example 700 shows the DCI payload used for scheduling RAR and the CRC that can be attached to the DCI. As shown by Example 700, an RNTI can be used to mask the CRC of the DCI for scheduling RAR (e.g., via a logical XOR operation). An RNTI can belong to a first set of RNTIs that can be applied to mask the CRC of the DCI for scheduling type A RAR, or to a second set of RNTIs for scheduling 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 can be constructed according to the formula for the modified RNTI: Modified RNTI = mod(1 + s_id + S×t_id + S×T×f_id + S×T×F×ul_FDRA_id + Δ preamble ,2 bitwidth_RNTI-1), where bitwidth_RNTI may indicate the number of bits allocated for the modified RNTI (the upper limit is defined 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, where S is the maximum 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 the 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, where F depends on the initial UL BWP configuration for type A UEs and type B UEs), and the starting point, interval and range of f_id (which may take different values for type A UEs and type B UEs), ul_FDRA_id may be the UL frequency domain resource allocation (FDRA) for PRACH preamble transmission (e.g., 0 for the NUL carrier or subband index allocated for type A UEs, and 1 for the SUL carrier or subband index allocated for type B UEs), and Δ_preamble depends on whether type A UEs and type B UEs share the same PRACH occasion (Δ_preamble=0 for different PRACH occasions, and Δ_preamble≥S*T*F*2 for shared PRACH occasions and different preamble groups). The UE 120 may determine whether an RAR is to be decoded at least in part based on whether the RNTI extracted from the masked CRC in the information (the DCI scheduling the RAR) belongs to the set of RNTIs associated with the UE type of the UE 120. The base station 110 may divide the values of s_id, t_id and / or f_id such that they distinguish between UE types when calculating the modified RNTI. This may save signaling resources (e.g., save a message that may be 16 bits).

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

[0103] In some aspects, the PDCCH used for scheduling the RAR can be polar-coded for the PDCCH. The DMRS sequence of the PDCCH can also be scrambled with a sequence associated with a scrambling ID. UE 120 can determine whether the RAR should be decoded based at least in part on the scrambling ID applied to the DMRS sequence. A first set of scrambling IDs can be associated with type A UEs, and a second (orthogonal or disjoint) set of scrambling IDs can be associated with type B UEs. In some aspects, the DCI can be scrambled with a sequence associated with a scrambling ID. UE 120 can determine whether the RAR should be decoded based at least in part on the scrambling IDs applied to other coded bits of the DCI or PDCCH. By using interleaving modes, scrambling IDs, or other coding features, UE 120 can distinguish the RAR according to the UE type to determine whether the RAR should be decoded by UE 120, or whether UE 120 should save power and processing resources by not decoding the RAR.

[0104] Figure 8 This is a diagram illustrating an example procedure 800 performed by a UE according to this disclosure. Example procedure 800 is an example in which a UE (e.g., UE 120) performs operations associated with distinguishing RARs.

[0105] like Figure 8 As shown, in some aspects, process 800 may include receiving RAR (block 810). For example, the UE (e.g., using...) Figure 10 The receiving component 1002 depicted herein can receive RAR, as described above.

[0106] like Figure 8 As further illustrated, in some aspects, process 800 may include decoding the RAR (box 820) based at least in part on information that distinguishes the RAR according to the UE type. For example, the UE (e.g., using...) Figure 10 The decoding component 1008 described herein can decode the RAR at least in part based on information that distinguishes the RAR according to the UE type, as described above.

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

[0108] In the 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.

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

[0110] In a third aspect, either 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.

[0111] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the information distinguishes between the RAR for the first UE type and the RAR for the second UE type based at least in part on the initial BWP configuration.

[0112] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first UE type shares the initial uplink BWP with the second UE type.

[0113] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0114] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the initial uplink BWP for the first UE type partially overlaps with the initial uplink BWP for the second UE type.

[0115] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the initial uplink BWP for the first UE type does not overlap with the initial uplink BWP for the second UE type.

[0116] In the ninth aspect, the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type, either alone or in combination with one or more of the first to eighth aspects.

[0117] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the initial downlink BWP for the first UE type partially overlaps with the initial downlink BWP for the second UE type.

[0118] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the initial downlink BWP for the first UE type does not overlap with the initial downlink BWP for the second UE type.

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

[0120] In the thirteenth aspect, decoding the RAR, either alone or in combination with one or more of the first to twelfth aspects, at least in part based on the information, comprises: extracting the RNTI from the CRC; calculating the modified RNTI based at least in part on one or more of the index value of the first symbol of the PRACH timing of the RAR, the index of the first time slot of the PRACH timing in the system frame, and the index of the PRACH timing in the frequency domain; and decoding the RAR if the RNTI extracted from the CRC is in the set of RNTIs indicated by the modified RNTI.

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

[0122] In the fifteenth aspect, decoding the RAR, either alone or in combination with one or more of the first to fourteenth aspects, at least in part based on the information, comprises: applying one or more of a first interleaving mode or a second interleaving mode to a CRC, wherein the first interleaving mode is associated with a first UE type and the second interleaving mode is associated with a second UE type; and decoding the RAR at least in part based on the result of the application.

[0123] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the information includes a DMRS sequence that is at least partially distinguishable between a RAR for a first UE type and a RAR for a second UE type based on a scrambling ID applied to the DMRS sequence.

[0124] In the seventeenth aspect, decoding the RAR, either alone or in combination with one or more of the first to sixteenth aspects, at least in part based on the information, comprises: applying one or more of a first scrambling ID set or a second scrambling ID set to a DMRS sequence, wherein the first scrambling ID set is associated with a first UE type and the second scrambling ID set is associated with a second UE type; and decoding the RAR at least in part based on the result of the application.

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

[0126] In the nineteenth aspect, decoding the RAR, either alone or in combination with one or more of the first to eighteenth aspects, at least in part based on the information, comprises: 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 a first UE type and the second scrambling ID set is associated with a second UE type; and decoding the RAR at least in part based on the result of the application.

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

[0128] In the twentieth aspect, alone or in combination with one or more of the first to twentieth aspects, the information includes a precoding or spatial domain that distinguishes between a RAR for a first UE type and a RAR for a second UE type.

[0129] In the twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the information includes QCL relationships or spatial relationships for scheduling, which distinguish between RARs for a first UE type and RARs for a second UE type.

[0130] In the twentieth aspect, alone or in combination with one or more of the first to twenty-two aspects, the information includes reserved or spare bits in the DCI (DCI payload) indicating whether the RAR is for a first UE type or a second UE type.

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

[0132] In the twentieth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, the information includes a CRC that distinguishes between the RAR for the first UE type and the RAR for the second UE type, based at least in part on whether it is associated with a first PRACH preamble set for the first UE type or with a second PRACH preamble set for the second UE type.

[0133] In the twenty-sixth aspect, either alone or in combination with one or more of the first to twenty-fifth aspects, the first UE type includes UEs whose distance from the cell center meets a distance threshold, and the second UE type includes UEs whose distance from the cell center does not meet a distance threshold.

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

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

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

[0137] In the thirtieth aspect, either alone or in combination with one or more of the first to twenty-ninth aspects, the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of the UE, and this information is at least partially based on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

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

[0139] Figure 9 This is a diagram illustrating an example process 900 performed by a base station according to this disclosure. Example process 900 is an example in which a base station (e.g., base station 110) performs operations associated with distinguishing RARs.

[0140] like Figure 9 As shown, in some aspects, process 900 may include encoding a RAR for the UE based on information distinguishing the RAR according to the UE type and at least in part on the UE type (box 910). For example, a base station (e.g., using...) Figure 11The encoding component 1108 described herein can use information to distinguish the RAR based on the UE type and encode the RAR for the UE based at least in part on the UE type of the UE, as described above.

[0141] like Figure 9 As further illustrated, in some aspects, process 900 may include transmitting the RAR to the UE (box 920). For example, a base station (e.g., using...) Figure 11 The transmission component 1104 depicted in the figure can transmit the RAR to the UE, as described above.

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

[0143] In the first aspect, process 900 includes receiving communications based at least in part on the RAR.

[0144] In the second aspect, either alone or in combination with the first aspect, this information is at least partially based on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

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

[0146] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0147] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the initial uplink BWP for the first UE type partially overlaps with the initial uplink BWP for the second UE type.

[0148] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the initial uplink BWP for the first UE type does not overlap with the initial uplink BWP for the second UE type.

[0149] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type.

[0150] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the initial downlink BWP for the first UE type partially overlaps with the initial downlink BWP for the second UE type.

[0151] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the initial downlink BWP for the first UE type does not overlap with the initial downlink BWP for the second UE type.

[0152] In the tenth aspect, encoding the RAR based at least in part on the information, either alone or in combination with one or more of the first to ninth aspects, comprises: calculating the RNTI based at least in part on one or more of the index value of the first symbol of the PRACH timing for the RAR, the index of the first time slot of the PRACH timing in the system frame, and the index of the PRACH timing in the frequency domain, wherein the RNTI distinguishes between the RAR for the first UE type and the RAR for the second UE type; and masking the CRC of the RAR with the RNTI.

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

[0154] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the information includes a DMRS sequence that is at least partially distinguishable between a RAR for a first UE type and a RAR for a second UE type based on a scrambling ID applied to the DMRS sequence.

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

[0156] In the fourteenth aspect, encoding the RAR, either alone or in combination with one or more of the first to thirteenth aspects, at least in part, based on the information includes: placing the CORESET of the RAR in a position that distinguishes it from the RAR for the first UE type.

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

[0158] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the information includes a QCL relationship for scheduling that distinguishes between a RAR for a first UE type and a RAR for a second UE type.

[0159] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the information includes reserved or spare bits in the DCI indicating whether the RAR is for a first UE type or for a second UE type.

[0160] In the eighteenth aspect, alone or in combination with one or more of the first to 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.

[0161] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the information includes a CRC that distinguishes between the RAR for the first UE type and the RAR for the second UE type based at least in part on whether it is associated with a first PRACH preamble set for the first UE type or with a second PRACH preamble set for the second UE type.

[0162] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the first UE type includes UEs whose distance from the cell center meets a distance threshold, and the second UE type includes UEs whose distance from the cell center does not meet a distance threshold.

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

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

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

[0166] In the twentieth aspect, either alone or in combination with one or more of the first to twenty-third aspects, the first initial downlink BWP is different from the initial downlink BWP configured for the UE type, and this information is at least partially based on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

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

[0168] Figure 10 This is a block diagram of an example device 1000 for wireless communication. Device 1000 may be a UE, or a UE may include device 1000. In some aspects, device 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 may use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, a base station, or another wireless communication device). As further shown, device 1000 may include a decoding component 1008 and other examples.

[0169] In some respects, device 1000 can be configured to perform the functions described herein. Figure 1-7 The described one or more operations. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, the device 1000 and / or Figure 10 One or more components shown may include the above combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 10 One or more components shown can be combined as described above. Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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 may be executed by a controller or processor to perform the function or operation of that component.

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

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

[0172] The receiving component 1002 can receive the RAR. The decoding component 1008 can decode the RAR at least in part based on information that distinguishes the RAR according to the UE type. The transmitting component 1004 can transmit communication at least in part based on the RAR.

[0173] Figure 10 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 10 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The collection of components shown (e.g., one or more components) can be executed as described by Figure 10 The other set of components shown in the diagram performs one or more functions.

[0174] Figure 11 This is a block diagram of an example device 1100 for wireless communication. Device 1100 may be a base station, or a base station may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a transmitting component 1104, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 may use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, device 1100 may include one or more of the following: an encoding component 1108, etc.

[0175] In some respects, device 1100 can be configured to perform the functions described herein. Figure 1-7 The described one or more operations. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 9 The process 900. In some aspects, the apparatus 1100 and / or Figure 11 One or more components shown may include the above combination Figure 2 One or more components of the described base station. Additional or alternative. Figure 11 One or more components shown can be combined as described above. Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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 may be executed by a controller or processor to perform the function or operation of that component.

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

[0177] Transmission component 1104 can transmit communications (such as reference signals, control information, data communications, or combinations thereof) to device 1106. In some aspects, one or more other components of device 1100 can generate communications and provide the generated communications to transmission component 1104 for transmission to device 1106. In some aspects, transmission component 1104 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and can transmit the processed signals to device 1106. In some aspects, transmission component 1104 can include combinations of the above. Figure 2 The described base station includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1104 may be co-located with the receive component 1102 in a transceiver.

[0178] Encoding component 1108 can use information from the RAR to distinguish it according to the UE type and encode the RAR for the UE at least in part based on the UE type. Transmission component 1104 can transmit the RAR to the UE. Receiving component 1102 can receive communication at least in part based on the RAR.

[0179] Figure 11 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The collection of components shown (e.g., one or more components) can be executed as described by Figure 11 The other set of components shown in the diagram performs one or more functions.

[0180] The foregoing disclosure provides explanations and descriptions, 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 foregoing disclosure or may be obtained through practice.

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

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

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

[0184] Aspect 3: The method of aspect 2 further includes: transmitting communications at least in part based on the RAR.

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

[0186] Aspect 5: The method of any of Aspects 1-4, wherein the information is configured, at least in part, based on the initial bandwidth portion (BWP), to distinguish between the RAR for the first UE type and the RAR for the second UE type.

[0187] Aspect 6: The method of aspect 5, wherein the first UE type and the second UE type share the initial uplink BWP.

[0188] Aspect 7: The method of aspect 5, wherein the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0189] Aspect 8: The method of aspect 7, wherein the initial uplink BWP for the first UE type partially overlaps with the initial uplink BWP for the second UE type.

[0190] Aspect 9: The method of aspect 7, wherein the initial uplink BWP for the first UE type does not overlap with the initial uplink BWP for the second UE type.

[0191] Aspect 10: The method of aspect 7, wherein the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type.

[0192] Aspect 11: The method of aspect 10, wherein the initial downlink BWP for the first UE type partially overlaps with the initial downlink BWP for the second UE type.

[0193] Aspect 12: The method of aspect 10, wherein the initial downlink BWP for the first UE type does not overlap with the initial downlink BWP for the second UE type.

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

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

[0196] Aspect 15: The method of any of Aspects 1-4, wherein the information includes Cyclic Redundancy Check (CRC), which distinguishes between RAR for a first UE type and RAR for a second UE type based at least in part on an interleaving mode applied to the CRC.

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

[0198] Aspect 17: The method of any of Aspects 1-16, wherein the information includes a demodulation reference signal (DMRS) sequence, which is at least partially distinguished between a RAR for a first UE type and a RAR for a second UE type based on a set of scrambling identifiers (IDs) applied to the DMRS sequence.

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

[0200] Aspect 19: The method of any of Aspects 1-18, wherein the information includes downlink control information (DCI), which is distinguished at least in part from a set of scrambling identifiers (IDs) applied to the DCI between a RAR for a first UE type and a RAR for a second UE type.

[0201] Aspect 20: The method of aspect 19, wherein decoding the RAR based at least in part on the information comprises: 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 a first UE type and the second scrambling ID set is associated with a second UE type; and decoding the RAR based at least in part on the result of the application.

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

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

[0204] Aspect 23: The method of any of Aspects 1-22, wherein the information includes a quasi-co-location relationship for scheduling, which distinguishes between a RAR for a first UE type and a RAR for a second UE type.

[0205] Aspect 24: The method of any of Aspects 1-23, wherein the information includes reserved or spare bits in downlink control information indicating whether the RAR is for a first UE type or a second UE type.

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

[0207] Aspect 26: The method of any of Aspects 1-25, wherein the information includes Cyclic Redundancy Check (CRC), which distinguishes between the RAR for the first UE type and the RAR for the second UE type based at least in part on whether it is associated with a first Physical Random Access Channel (PRACH) preamble set for the first UE type or with a second PRACH preamble set for the second UE type.

[0208] Aspect 27: The method of aspect 26, wherein the first UE type includes UEs whose distance from the cell center meets a distance threshold, and the second UE type includes UEs whose distance from the cell center does not meet a distance threshold.

[0209] Aspect 28: The method of any of Aspects 1-24 further includes: obtaining an initial bandwidth portion (BWP) configuration for random access before receiving the RAR, the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for the UE type of the UE; and transmitting a random access message within the initial uplink BWP configured for the UE type of the UE.

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

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

[0212] Aspect 31: The method of aspect 30, wherein the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of the UE, and wherein the information is at least partially based on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

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

[0214] Aspect 33: The method of aspect 32 further includes: receiving communications at least in part based on the RAR.

[0215] Aspect 34: The method of aspect 32 or 33, wherein the information is configured, at least in part, based on the initial bandwidth portion (BWP), to distinguish between the RAR for the first UE type and the RAR for the second UE type.

[0216] Aspect 35: The method of aspect 34, wherein the first UE type and the second UE type share the initial uplink BWP.

[0217] Aspect 36: The method of aspect 34, wherein the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0218] Aspect 37: The method of aspect 36, wherein the initial uplink BWP for the first UE type partially overlaps with the initial uplink BWP for the second UE type.

[0219] Aspect 38: The method of aspect 36, wherein the initial uplink BWP for the first UE type does not overlap with the initial uplink BWP for the second UE type.

[0220] Aspect 39: The method of aspect 36, wherein the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type.

[0221] Aspect 40: The method of aspect 39, wherein the initial downlink BWP for the first UE type partially overlaps with the initial downlink BWP for the second UE type.

[0222] Aspect 41: The method of aspect 39, wherein the initial downlink BWP for the first UE type does not overlap with the initial downlink BWP for the second UE type.

[0223] Aspect 42: The method of any of Aspects 32-41, wherein encoding the RAR based at least in part on the information comprises: calculating a Radio Network Temporary Identifier (RNTI) based at least in part on one or more of the index value of a first symbol of the Physical Random Access Channel (PRACH) timing for the RAR, the index of a first time slot of the PRACH timing in a system frame, and the index of the PRACH timing in the frequency domain, wherein the RNTI distinguishes between a RAR for a first UE type and a RAR for a second UE type; and masking the Cyclic Redundancy Check (CRC) of the RAR with the RNTI.

[0224] Aspect 43: The method of any of Aspects 32-42, wherein the information includes Cyclic Redundancy Check (CRC), which distinguishes between RAR for a first UE type and RAR for a second UE type based at least in part on an interleaving mode applied to the CRC.

[0225] Aspect 44: The method of any of Aspects 32-43, wherein the information includes a demodulation reference signal (DMRS) sequence, which is at least partially based on a set of scrambling identifiers (IDs) applied to the DMRS sequence to distinguish between a RAR for a first UE type and a RAR for a second UE type.

[0226] Aspect 45: The method of any of Aspects 32-44, wherein the information includes downlink control information (DCI), which is at least partially based on a set of scrambling identifiers (IDs) applied to the DCI to distinguish between a RAR for a first UE type and a RAR for a second UE type.

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

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

[0229] Aspect 48: The method of any of Aspects 32-47, wherein the information includes a quasi-co-location relationship for scheduling, which distinguishes between a RAR for a first UE type and a RAR for a second UE type.

[0230] Aspect 49: The method of any of Aspects 32-48, wherein the information includes reserved or spare bits in downlink control information indicating whether the RAR is for a first UE type or a second UE type.

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

[0232] Aspect 51: The method of any of Aspects 32-50, wherein the information includes Cyclic Redundancy Check (CRC), which distinguishes between the RAR for the first UE type and the RAR for the second UE type based at least in part on whether it is associated with a first Physical Random Access Channel (PRACH) preamble set for the first UE type or with a second PRACH preamble set for the second UE type.

[0233] Aspect 52: The method of aspect 51, wherein the first UE type includes UEs whose distance from the cell center meets a distance threshold, and the second UE type includes UEs whose distance from the cell center does not meet a distance threshold.

[0234] Aspect 53: The method of any of Aspects 32-52 further includes: transmitting an initial bandwidth portion (BWP) configuration for random access to the UE before transmitting the RAR, the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for the UE type of the UE; and receiving a random access message within the initial uplink BWP configured for the UE type of the UE.

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

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

[0237] Aspect 56: The method of aspect 55, wherein the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of the UE, and wherein the information is at least partially based on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

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

[0239] Aspect 58: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform one or more of the methods of aspects 1-56.

[0240] Aspect 59: An apparatus for wireless communication, comprising at least one means for performing one or more methods as described in aspects 1-56.

[0241] Aspect 60: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 1-56.

[0242] Aspect 61: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 1-56.

[0243] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, processors are implemented using hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in any way. Thus, the operation and behavior of these systems and / or methods are described herein without reference to any specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on the descriptions herein.

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

[0245] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below may be directly subordinated to only one claim, the disclosure of aspects includes each dependent claim being combined with each other claim in this set of claims. As used herein, the phrase “at least one of” refers to any combination of these items, including single members. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0246] The elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “a certain” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “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. Moreover, as used herein, the terms “have,” “contain,” “include,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Moreover, as used herein, the term “or” is intended to be inclusive when used in a sequence and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., in combination with “either of” or “only one of”).

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors are coupled to the memory and configured to: Receive Random Access Response (RAR); as well as The RAR is decoded at least in part based on information that distinguishes it according to the UE type. The information includes a demodulation reference signal (DMRS) sequence, which is at least partially based on a set of scrambling identifiers (IDs) applied to the DMRS sequence to distinguish between a RAR for a first UE type and a RAR for a second UE type.

2. The UE of claim 1, wherein the one or more processors are configured to: before receiving the RAR, Obtain the initial bandwidth portion (BWP) configuration for random access, the initial BWP configuration indicating the initial downlink BWP and initial uplink BWP configured for the UE type of the UE; and Random access messages are transmitted within the initial uplink BWP of the UE type configured for the UE.

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

4. The UE of claim 2, wherein, in order to obtain the configuration, the one or more processors 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 from the initial downlink BWP configured for the UE type of the UE, and wherein the information is configured at least in part based on the initial BWP to distinguish between the RAR for the first UE type and the RAR for the second UE type.

6. The UE of claim 1, wherein the information is configured, at least in part, based on the initial bandwidth portion BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

7. The UE of claim 1, wherein, for decoding the RAR based at least in part on the information, the one or more processors are configured to: Extract the Radio Temporary Identifier (RNTI) from the Cyclic Redundancy Check (CRC). The modified RNTI is calculated at least in part based on one or more of the index value of the first symbol of the physical random access channel (PRACH) timing of the RAR, the index of the first time slot of the PRACH timing in the system frame, and the index of the PRACH timing in the frequency domain. as well as The RAR is decoded using the RNTI extracted from the RNTI within the set of RNTIs indicated by the modified RNTI.

8. The UE of claim 7, wherein the CRC distinguishes between a RAR for a first UE type and a RAR for a second UE type based at least in part on an interleaving pattern applied to the CRC, and wherein, in order to decode the RAR based at least in part on the information, the one or more processors are configured to: One or more of a first interleaving mode or a second interleaving mode are applied to the CRC, wherein the first interleaving mode is associated with the first UE type and the second interleaving mode is associated with the second UE type; and The RAR is decoded based at least in part on the results of the application.

9. The UE of claim 1, wherein the information includes downlink control information (DCI), the DCI being distinguished between a RAR for a first UE type and a RAR for a second UE type based at least in part on a set of scrambling identifiers (IDs) applied to the DCI.

10. The UE of claim 1, wherein the information includes a CORESET, the CORESET being distinguished between a RAR for a first UE type and a RAR for a second UE type based at least in part on the location of the CORESET.

11. The UE of claim 1, wherein the information includes precoding, the precoding distinguishing between RAR for a first UE type and RAR for a second UE type.

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

13. The UE of claim 1, wherein the information includes a Cyclic Redundancy Check (CRC), the CRC distinguishing between a RAR for the first UE type and a RAR for the second UE type based at least in part on whether it is associated with a first Physical Random Access Channel (PRACH) preamble set for the first UE type or with a second PRACH preamble set for the second UE type.

14. A network entity for wireless communication, comprising: Memory; as well as One or more processors are coupled to the memory and configured to: Information is used to distinguish random access response (RAR) based on the user equipment (UE) type and the RAR for the UE is encoded based at least in part on the UE type. as well as The RAR is transmitted to the UE. The information used to distinguish RARs based on UE type includes a demodulation reference signal (DMRS) sequence, which is at least partially based on a set of scrambling identifiers (IDs) applied to the DMRS sequence to distinguish between RARs for a first UE type and RARs for a second UE type.

Images