Random access response distinction

Abstract

Regarding wireless communication, we provide user equipment and a base station that distinguish random access responses (PARs). [Solution] In a wireless communication system, the user equipment (UE) comprises memory and multiple processors, and performs processing that includes the multiple processors receiving random access responses (RARs) from a base station and decoding the RARs based at least partially on information that distinguishes the RARs according to the UE type.

Description

Claim of Priority

[0001] Cross - Reference to Related Applications

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 201,165, filed Apr. 15, 2021, entitled “RANDOM ACCESS RESPONSE DIFFERENTIATION,” and U.S. Non - Provisional Patent Application No. 17 / 652,906, filed Feb. 28, 2022, entitled “RANDOM ACCESS RESPONSE DIFFERENTIATION,” which are hereby incorporated by reference in their entirety.

Technical Field

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatus for differentiating random access responses.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple - access technology that is capable of supporting communication with multiple users by sharing available system resources (such as bandwidth, transmit power, etc.). 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 (R)). LTE / LTE - Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP (R)).

[0004]

[0004] A wireless network may include several base stations (BS) that can support communication for several user equipment (UEs). UEs may communicate with BS via downlink and uplink. "Downlink" or "forward link" refers to the communication link from the BS to the UE, and "uplink" or "reverse link" refers to the communication link from the UE to the BS. As will be described in more detail herein, BS may be called node B, gNB, access point (AP), radio head, transmit / receive point (TRP), new radio (NR) BS, 5G node B, etc.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user devices to communicate at urban, national, regional, and even global levels. NR, sometimes called 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving service, utilizing new spectra, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM), for example) on the uplink (UL), as well as by supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further developments in LTE, NR, and other radio access technologies remain useful. [Overview of the Initiative]

[0006]

[0006] In some embodiments, a method of wireless communication performed by a user device (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 type of UE.

[0007]

[0007] In some embodiments, a method of wireless communication performed by a base station includes encoding a RAR for the UE with information distinguishing the RAR according to the UE type and at least in part on the UE type of the UE, and transmitting the RAR to the UE.

[0008]

[0008] In some embodiments, the 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 RARs and to decode RARs based at least in part on information that distinguishes RARs according to the type of UE.

[0009]

[0009] In some embodiments, 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 RARs for UEs with information distinguishing the RARs according to the UE type and at least partially based on the UE type of the UE, and to transmit the RARs to the UEs.

[0010]

[0010] In some embodiments, a non-temporary computer-readable medium storing a set of instructions for wireless communication includes, when executed by one or more processors of the UE, one or more instructions causing the UE to decode a RAR and a RAR at least in part on information distinguishing the RAR according to the type of UE.

[0011]

[0011] In some embodiments, a non-temporary computer-readable medium storing a set of instructions for wireless communication includes, when executed by one or more processors of a base station, one or more instructions causing the base station to encode a RAR for a UE, with information distinguishing the RAR according to the type of UE, and at least in part on the type of UE, and to transmit the RAR to the UE.

[0012]

[0012] In some embodiments, the device for wireless communication includes means for receiving RARs and means for decoding RARs based at least in part on information distinguishing RARs according to UE types.

[0013]

[0013] In some embodiments, the device for wireless communication includes means for encoding RARs for UEs with information distinguishing the RARs according to the type of UE, and at least in part on the type of UE, and means for transmitting the RARs to the UE.

[0014]

[0014] The embodiments are generally substantially described herein with reference to the drawings and specification and include methods, apparatus, systems, computer program products, non-temporary computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as shown by the drawings and specification.

[0015]

[0015] The above outlines fairly broadly the features and technical advantages of the examples provided in this disclosure so that embodiments for carrying out the following inventions may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may readily be used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent configurations will not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and method of operation, along with the relevant advantages, will be better understood from the following description in relation to the appended figures. Each of the figures is provided for illustrative and explanatory purposes and is not provided as a definition of the limitation of the claims.

[0016]

[0016] While embodiments are described in this disclosure by example to several examples, those skilled in the art will understand that such embodiments can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some embodiments can be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). Embodiments 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 embodiments and features described may include additional components and features for the implementation and practice of the claimed and described embodiments. For example, wireless signal transmission and reception may include several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, (one or more) processors, interleavers, adders, or summers). The embodiments described herein are intended to be applicable to a wide variety of devices, components, systems, distributed configurations, or end-user devices of varying sizes, shapes, and structures.

[0017]

[0017] More specific descriptions than those briefly summarized above can be obtained by referring to embodiments shown in part in the accompanying drawings, so that the features described above can be understood in detail. However, it should be noted that the accompanying drawings show only some typical embodiments of the disclosure and should not be considered to limit the scope of the disclosure, as such descriptions may apply to other equally valid embodiments. The same reference numerals in different drawings may identify the same or similar elements. [Brief explanation of the drawing]

[0018] [Figure 1]

[0018] Diagram showing an example of a wireless network according to the present disclosure. [Figure 2]

[0019] Diagram showing an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure. [Figure 3]

[0020] Diagram showing the type of a device according to the present disclosure. [Figure 4]

[0021] Diagram showing an example of a configuration for a new radio reduced capacity (RedCap) UE according to the present disclosure. [Figure 5]

[0022] Diagram showing an example of distinguishing a random access response (RAR) according to the present disclosure. [Figure 6]

[0023] Diagram showing an example of overlapping and non-overlapping bandwidth parts for distinguishing a RAR according to the present disclosure. [Figure 7]

[0024] Diagram showing an example of encoding downlink control information for scheduling a RAR according to the present disclosure. [Figure 8]

[0025] Diagram showing an exemplary process performed by, for example, a UE according to the present disclosure. [Figure 9]

[0026] Diagram showing an exemplary process performed by, for example, a base station according to the present disclosure. [Figure 10]

[0027] Block diagram of an exemplary apparatus for wireless communication according to the present disclosure. [Figure 11] Block diagram of an exemplary apparatus for wireless communication according to the present disclosure.

Mode for Carrying Out the Invention

[0019]

[0028] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure can be implemented in many different forms and should not be construed as being limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure may be thorough and complete and so as to convey the scope of this disclosure to those skilled in the art. Based on the teachings of this specification, those skilled in the art should understand that the scope of this disclosure covers any aspect of the disclosure disclosed herein, whether implemented independently of other aspects of the disclosure or in combination with other aspects of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of aspects described herein. Furthermore, the scope of this disclosure shall cover any other structure, function, or such apparatus or method practiced using other structures, functions, or structures and functions in addition to or in addition to the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein can be implemented by one or more elements of the claims.

[0020]

[0029] Next, several embodiments of telecommunications systems are presented with reference to various devices and techniques. These devices and techniques are described in the following detailed explanation and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “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.

[0021]

[0030] While embodiments may be described using terminology generally associated with 5G or NR radio access technology (RAT), it should be noted that embodiments of this disclosure may also apply to other RATs, such as 3G RAT, 4G RAT, and / or RATs following 5G (e.g., 6G).

[0022]

[0031] Figure 1 shows an example of a wireless network 100 as described herein. The wireless network 100 may be, or may include, elements of a 5G(NR) network and / or an LTE network, among other things. 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 user equipment (UE) and may also be called an NR BS, node B, gNB, 5G node B(NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage to a specific geographic area. In 3GPP, the term “cell” may refer to the coverage area of ​​a BS and / or BS subsystem that service this coverage area, depending on the context in which the term is used.

[0023]

[0032] A BS can provide communication coverage to macrocells, picocells, femtocells, and / or other types of cells. A macrocell may cover a relatively large geographical area (e.g., a radius of several kilometers) and may enable unrestricted access by UEs subscribing to the service. A picocell may cover a relatively small geographical area and may enable unrestricted access by UEs subscribing to the service. A femtocell may cover a relatively small geographical area (e.g., a home) and may enable limited access by UEs associated with the femtocell (e.g., UEs in a Limited Subscriber Group (CSG)). A BS for a macrocell is sometimes called a macroBS. A BS for a picocell is sometimes called a picoBS. A BS for a femtocell is sometimes called a femtoBS or homeBS. In the example shown in Figure 1, BS110a may be a macroBS for macrocell 102a, BS110b may be a picoBS for picocell 102b, and BS110c may be a femtoBS for femtocell 102c. A BS may support one or more (for example, three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably in this specification.

[0024]

[0033] In some embodiments, cells may not necessarily be fixed, and the geographical area of ​​a cell may move according to the location of the mobile BS. In some embodiments, BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0025]

[0034] In some embodiments, the terms “base station” (e.g., base station 110) or “network entity” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some embodiments, “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 embodiments, the terms “base station” or “network entity” may refer to a single device configured to perform one or more functions, such as the one described herein with respect to base station 110. In some embodiments, the terms “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 several different devices (which may be located in the same 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 a function, and the term “base station” or “network entity” may refer to any one or more of those different devices. In some embodiments, 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 embodiments, two or more base station functions may be instantiated on a single device. In some embodiments, the term “base station” or “network entity” may refer to one of the base station functions and not another. In this way, a single device may contain two or more base stations.

[0026]

[0035] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from upstream stations (e.g., BS or UE) and send those data transmissions to downstream stations (e.g., UE or BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in Figure 1, relay BS110d may communicate with macro BS110a and UE120d to enable communication between BS110a and UE120d. Relay BS may also be called relay stations, relay base stations, or relays.

[0027]

[0036] The wireless network 100 may be a heterogeneous network including different types of BS, such as macro BS, pico BS, femto BS, and relay BS. These different types of BS may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, macro BS may have high transmit power levels (e.g., 5-40 watts), while pico BS, femto BS, and relay BS may have lower transmit power levels (e.g., 0.1-2 watts).

[0028]

[0037] The network controller 130 can be coupled to a set of BSs and perform coordination and control for these BSs. The network controller 130 can communicate with BSs via backhaul. BSs can also communicate with each other, for example, directly or indirectly via wireless backhaul or wireline backhaul.

[0029]

[0038] UE120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UEs may also be called access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or medical equipment, biosensors / biometric devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radios), vehicle components or vehicle sensors, smart meters / smart sensors, industrial manufacturing equipment, Global Positioning System (GPS) devices, or any other suitable devices configured to communicate via wireless or wired media.

[0030]

[0039] Some UEs may be reduced-capacity (RedCap) UEs that can decode Random Access Responses (RARs), which are part of the Random Access Channel (RACH) procedure for establishing a Radio Resource Control (RRC) connection. Different types of UEs may exist, and different types of UEs may only be able to decode RARs if the RAR is configured for that UE type. Some UEs may be considered machine-type communications (MTC) UEs or advanced or enhanced machine-type communications (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with base stations, other devices (e.g., remote devices), or any other entities. Wireless nodes may provide connectivity to or for a network (e.g., a wide area network such as the Internet or a cellular network) via wired or wireless communication links. Some UEs may be considered Internet of Things (IoT) devices and / or implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). The UE120 may be contained within a housing that houses the components of the UE120, such as processor components and / or memory components. In some embodiments, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0031]

[0040] Generally, any number of wireless networks can be deployed within a given geographical area. Each wireless network may support a specific RAT and may operate on one or more frequencies. RATs are sometimes called wireless technologies or air interfaces. Frequencies are sometimes called carriers or frequency channels. Each frequency may support a single RAT within a given geographical area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0032]

[0041] In some embodiments, two or more UE120s (for example, shown as UE120a and UE120e) may communicate directly using one or more sidelink channels (for example, without using base station 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-anything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, UE120s may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by base station 110.

[0033]

[0042] Devices in wireless network 100 may communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., based on frequency or wavelength. For example, devices in wireless network 100 may communicate using an operating band having a first frequency range (FR1) that may span from 410 MHz to 7.125 GHz, and / or using an operating band having a second frequency range (FR2) that may span from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes called midband frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the “sub-6 GHz” band. Similarly, FR2 is often referred to as “millimeter wave” even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified by the International Telecommunication Union (ITU) as the “millimeter wave” band. Therefore, unless otherwise specified, terms such as “sub-6GHz” can broadly refer to frequencies below 6GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125GHz) when used herein. Similarly, unless otherwise specified, terms such as “millimeter wave” can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25GHz) when used herein. Frequencies included in FR1 and FR2 may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0034]

[0043] As stated above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0035]

[0044] Figure 2 shows an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present 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, where generally T≧1 and R≧1.

[0036]

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

[0037]

[0046] In UE120, antennas 252a-252r may receive downlink signals from base station 110 and / or other base stations and provide the received signals to demodulators (DEMOD) 254a-254r, respectively. Each demodulator 254 may adjust the received signal (e.g., filter, amplify, downconvert, and digitize) to acquire an input sample. Each demodulator 254 may further process the input sample (e.g., for OFDM) to acquire a received symbol. A MIMO detector 256 may acquire received symbols from all R demodulators 254a-254r and, where applicable, perform MIMO detection on the received symbols and provide the detected symbols. A receiving processor 258 may process the detected symbols (e.g., demodulate and decode) and provide the decoded data for UE120 to the data sink 260 and the decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may, in some examples, determine the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the CQI parameter. In some embodiments, one or more components of the UE120 may be contained within the housing 284.

[0038]

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

[0039]

[0048] An antenna (for example, antennas 234a-234t and / or antennas 252a-252r) may include, or be contained within, one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include sets of coplanar antenna elements and / or sets of non-coplanar antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include antenna elements in a single housing and / or antenna elements in multiple housings. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements coupled to one or more transmit and / or receive components, such as one or more components in Figure 2.

[0040]

[0049] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information (for reporting, including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may, where applicable, be precoded by TX MIMO processor 266, further processed by modulators 254a-254r (for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some embodiments, the modulator and demodulator of UE120 (e.g., MOD / DEMOD 254) may be included in the modem of UE120. In some embodiments, UE120 includes a transceiver. The transceiver may include any combination of (one or more) antennas 252, a modulator and / or demodulator 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and memory 282 to carry out any aspect of the methods described herein (for example, as described with reference to Figures 3 to 11).

[0041]

[0050] At base station 110, uplink signals from UE 120 and other UEs are received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and may be further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include a communication unit 244, which may communicate with network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some embodiments, the modulator and demodulator of base station 110 (e.g., MOD / DEMOD 232) may be included in the modem of base station 110. In some embodiments, base station 110 includes a transceiver. The transceiver includes (one or more) antennas 234, a modulator and / or demodulator 232, a MIMO detector 236, a receiving processor 238, a transmitting processor 220, and / or TX This may include any combination of MIMO processors 230. Transceivers may be used by a processor (e.g., controller / processor 240) and memory 242 to carry out any aspect of the methods described herein (for example, as described with reference to Figures 3 to 11).

[0042]

[0051] The deployment of communication systems, such as 5G NR systems, can be structured in multiple ways with various components or parts. 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, or one or more units (or one or more components) that perform base station functions, such as base stations, can be implemented in aggregated or disaggregated architectures. For example, a base station (such as a node B, advanced NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell) can be implemented as an aggregated or disaggregated base station (also known as a standalone BS or monolithic BS).

[0043]

[0052] Aggregated base stations may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Disaggregated base stations may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some embodiments, a CU may be implemented within a RAN node, and one or more DUs may be collocated with the CU or, alternatively, geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0044]

[0053] Base station type operation or network design may take into account the aggregation characteristics of base station functions. For example, disaggregated base stations may be used in IAB networks, open radio access networks (such as O-RAN (a network configuration sponsored by the O-RAN Alliance)), or virtualized radio access networks (vRAN, also known as Cloud Radio Access Network (C-RAN)). Disaggregation may involve distributing functions across two or more units in various physical locations, as well as virtually distributing functions for at least one unit, which can enable flexibility in network design. Disaggregated base stations, or various units in a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0045]

[0054] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other components (one or more) of Figure 2 may implement one or more techniques associated with distinguishing RAR as part of the RACH procedure, as will be described in more detail elsewhere in this specification. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other components (one or more) of Figure 2 may implement or direct the operation of, for example, process 800 in Figure 8, process 900 in Figure 9, and / or other processes described herein. Memories 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some embodiments, memory 242 and / or memory 282 may include non-temporary computer-readable media for storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors in the base station 110 and / or UE 120 (for example, directly or after compilation, translation, and / or interpretation), one or more processors, UE 120, and / or base station 110 may be caused to perform or direct the operation of, for example, process 800 in Figure 8, process 900 in Figure 9, and / or other processes described herein. In some embodiments, executing an instruction may include, among other things, running the instruction, translating the instruction, compiling the instruction, and / or interpreting the instruction.

[0046]

[0055] In some embodiments, the UE120 includes means for receiving RARs and / or means for decoding RARs based at least in part on information distinguishing RARs according to the UE type. Means for the UE120 to perform the operations described herein may include, for example, one or more of the following: an antenna 252, a demodulator 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, or a memory 282.

[0047]

[0056] In some embodiments, the base station includes means for encoding the RAR for the UE with information distinguishing the RAR according to the UE type, and at least in part on the UE type of the UE, and / or means for transmitting the RAR to the UE. Means for the base station to carry out the operations described herein may include, for example, one or more of the following: 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.

[0048]

[0057] Although the blocks in Figure 2 are shown as separate components, the functions described above with respect to those blocks can be implemented in a single hardware, software, or combination of components, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be performed by or under the control of the controller / processor 280.

[0049]

[0058] As described above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0050]

[0059] Figure 3 is a 300-type diagram illustrating the device type according to this disclosure.

[0051]

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

[0052]

[0061] In some embodiments, the NR RedCap UE may have reduction capabilities through its ability or configuration to provide lower peak throughput, longer latency, lower reliability, greater power efficiency, lower system overhead, and / or lower resource costs. The NR RedCap UE may comply with mitigation latency or reliability requirements. In some embodiments, the NR RedCap UE may have one or two transmit or receive antennas.

[0053]

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

[0054]

[0063] In some embodiments, NR RedCap UE may include wearable devices such as smartwatches, eHealth-related devices, personal protection devices, 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 also include surveillance cameras, low-end smartphones, and / or low-end IoT devices.

[0055]

[0064] As described above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0056]

[0065] Figure 4 shows an example configuration 400 for NR RedCap UE according to this disclosure.

[0057]

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

[0058]

[0067] Figure 4 shows other configurations that an NR RedCap UE may support, based at least partially on the types of NR RedCap UEs. Different types may have different subsets of features or limitations. For example, an NR RedCap UE that is a wearable device may support a DL peak rate of 150 Mbps, an UL peak rate of 50 Mbps, a bandwidth requirement of 20 MHz or 40 MHz, one transmit antenna, and one or two receive antennas. A wearable device may not support 256QAM. A wearable device may have intermediate mobility and high power saving requirements. A wearable device may still have latency or reliability requirements similar to those of an eMBB.

[0059]

[0068] In some embodiments, the NR RedCap UE, an industrial sensor, may 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 256QAM. The sensor may have low mobility and high power saving requirements. For safety-related sensors, the sensor may have latency requirements of less than 100 milliseconds (ms) or 5-10 ms. The sensor may have a reliability requirement of 99.99%.

[0060]

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

[0061]

[0070] In short, an NR RedCap UE may have a determined configuration based at least partially on the type of NR RedCap UE. As a result, an NR RedCap UE may conserve power, processing resources, and signaling resources and support a reduced set of features. In some embodiments, an NR RedCap UE may 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 also have or may not have reduction capabilities. For example, an NR RedCap UE may have a set of reduction capabilities but may fall back to a further set of reduction capabilities.

[0062]

[0071] An NR RedCap UE may be required to perform a RACH procedure to access the channel and establish a connection. The RACH procedure may be the same for all UEs, although different UEs may have different UE capabilities. In some scenarios, a base station may send multiple RACH messages, such as multiple RARs, to multiple UEs. A UE with limited capabilities may waste power and processing resources attempting to decode and process RARs that may not be intended for that UE.

[0063]

[0072] According to various embodiments described herein, a UE may receive a RAR as part of a RACH procedure and decode the RAR at least in part on information that distinguishes the RAR according to the UE type. That is, a UE may decode the RAR if the information indicates that the RAR should be decoded by the UE type of the UE. A RAR may target a first UE type (e.g., type A) or a second UE type (e.g., type B), but may not target both UE types. Examples of first UE type vs. second UE type may include RedCap UE vs. non-RedCap UE, RedCap UE with one receive antenna branch vs. RedCap UE with two receive antenna branches, UE supporting coverage extensions vs. UE not supporting coverage extensions, UE supporting small data transmission (SDT) vs. UE not supporting SDT, or UE supporting RAN slices vs. UE not supporting RAN slices. By distinguishing RARs, the UE can conserve power and processing resources by decoding RARs intended for the UE (or the UE's UE type) and not attempting to decode and process RARs not intended for the UE (or the UE's UE type). The UE may receive or retrieve information for RAR distinction from stored configuration information. This information may indicate how the UE should decide whether to decode a RAR or other RACH message.

[0064]

[0073] As described above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0065]

[0074] Figure 5 shows an example of distinguishing RARs according to this disclosure. As shown in Figure 5, base station 110 and UE 120 can communicate with each other to perform a 4-step RACH procedure.

[0066]

[0075] As indicated by reference number 505, random access configuration information may be transmitted by base station 110 and received by UE 120. In some embodiments, random access configuration information may be transmitted and / or indicated in system information and / or synchronization signal blocks (SSBs) (e.g., in one or more SIBs, such as system information block (SIB) 2) for contention-based random access. Additional or alternative, random access configuration information may be transmitted in RRC messages and / or physical downlink control channel (PDCCH) sequence messages that trigger a RACH procedure, such as for contention-free random access. Random access configuration information may include information for receiving RARs and distinguishing RARs based on UE type.

[0067]

[0076] As indicated by reference number 510, UE120 may transmit RAM that may contain a preamble (sometimes called a random access preamble, physical RACH (PRACH) preamble, or random access message (RAM) preamble). A message containing a preamble may be called message 1, Msg1, msg1, MSG1, the first message, or initial message in a four-step RACH procedure. RAM may contain a random access preamble identifier.

[0068]

[0077] As indicated by reference number 515, base station 110 may send a RAR in response to the preamble. The message containing the RAR may be referred to as message 2, Msg2, msg2, MSG2, or second message in the 4-step RACH procedure. In some embodiments, the RAR may indicate a discovered random access preamble identifier (for example, received from UE120 in Msg1). Additionally or alternatively, the RAR may indicate an uplink permission or resource allocation to be used by UE120 to send message 3 (Msg3).

[0069]

[0078] In some embodiments, as part of the second step of a four-step random access procedure, base station 110 may transmit a PDCCH communication for RAR. The PDCCH communication may schedule a Physical Downlink Shared Channel (PDSCH) communication that includes RAR. For example, the PDCCH communication may indicate a resource allocation for PDSCH communication. Alternatively, as part of the second step of a four-step RACH procedure, base station 110 may transmit a PDSCH communication for RAR as scheduled by the PDCCH communication. RAR may be contained within the MAC protocol data unit (PDU) of the PDSCH communication.

[0070]

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

[0071]

[0080] In some embodiments, UE120 may have information about different resources used for PDCCH scheduling of RARs. For example, UE120 may have information about a control resource set (CORESET) that distinguishes between RARs for a first type of UE and RARs for a second type of UE. RARs may be scheduled by the CORESET, and UE120 may determine that a RAR should be decoded based at least partially on the location of the CORESET. Some CORESET locations may be reserved for UEs of the first type of UE, and some CORESET locations may be reserved for UEs of the second type of UE.

[0072]

[0081] In some embodiments, UE120 may have information regarding decryption or quasi-co-located (QCLed) relationships used for scheduling RARs. For example, PDCCH may be QCLed with an SSB index reserved for a particular type of UE. UE120 may determine that a RAR should be decrypted based at least partially on the SSB index.

[0073]

[0082] In some embodiments, the information may include one or more reserved or spare bits in the Downlink Control Information (DCI). For example, in DCI format 1_0, the CRC may be masked by an RNTI (e.g., Random Access RNTI, msgB-RNTI, Modified RNTI). The masking may use (or reuse) a reserved or spare bit (e.g., the most significant bit) to signal the UE type for the RAR. In some embodiments, UE120 may use any combination of scheduling resources to determine whether UE120 should decode the RAR.

[0074]

[0083] Multiple UE types may be supported in a serving cell or RAN slice. In some embodiments, the information may include one or more PRACH formats associated with each UE type, and UE120 may determine whether the RAR should be decoded based at least partially on the PRACH format used. One UE type may be mapped to multiple PRACH formats, and different UE types may be mapped to different PRACH formats. For example, UE types may be 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 of shorter 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 of longer length. UE120 may determine its distance to base station 110, for example, by using GPS and / or measurements.

[0075]

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

[0076]

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

[0077]

[0086] As indicated by reference number 525, UE120 may decode the RAR if the RAR targets UE120 or a UE type of UE120. If the RAR does not target UE120, UE120 may not decode the RAR, thus conserving the power and processing resources that would normally be consumed by decoding and processing the RAR.

[0078]

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

[0079]

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

[0080]

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

[0081]

[0090] As described above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0082]

[0091] Figure 6 shows examples of overlapping and non-overlapping BWPs for distinguishing RARs as described herein.

[0083]

[0092] UE120 may decide to distinguish RAR for UE type based at least partially on the initial BWP configuration. The initial BWP configuration may indicate which BWPs are activated for UL and which BWPs are activated for DL. Configurations for BWP and initial UL BWP may be specified by standardized lookup tables or indicated by system information. Example 600 illustrates different UE types, Type A and Type B. Type A may be, for example, UEs with energy harvesting capabilities, and these UEs are active during time intervals orthogonal to Type B UEs, which may be powered, for example, by non-rechargeable batteries.

[0084]

[0093] In some embodiments, both the initial DL BWP and the initial UL BWP may be shared between a Type A capable UE and a Type B capable UE. In some embodiments, the initial DL BWP may be shared, but the initial UL BWP may be configured separately for Type A and Type B. The initial UL BWP for Type A and the initial UL BWP for Type B may partially overlap. Example 600 shows an overlapping BWP 602 matched at a reference point that may be the center frequency of the initial UE BWP. Example 600 also shows an overlapping BWP 604 matched at the initial physical resource block. The initial UL BWP for Type A and the initial UL BWP for Type B may not overlap, as shown by the non-overlapping BWP 606 (e.g., different subbands of the same carrier, different carriers (e.g., normal uplink (NUL) and auxiliary uplink (SUL))). The non-overlapping BWP 608 may be temporally separated according to time-division multiplexing (TDM) and / or have different timer configurations.

[0085]

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

[0086]

[0095] As described above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0087]

[0096] Figure 7 shows an example 700 of encoding a DCI for scheduling a RAR according to the present disclosure. Example 700 shows a DCI payload used to schedule a RAR and a CRC that may be attached to the DCI. As shown by Example 700, an RNTI may be used to mask the CRC of a DCI scheduling a RAR (e.g., via a logical exclusive OR (XOR) operation). An RNTI may belong to a first set of RNTIs that can be applied to mask the CRC of a DCI scheduling a type A RAR, or to a second set of RNTIs that schedule a type B RAR. There may be no intersection between the first set of RNTIs and the second set of RNTIs. The first set of RNTIs and the second set of RNTIs may be orthogonal. The RNTI of each set is given by the formula for modified RNTI, i.e., 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 a modified RNTI (whose upper limit is determined by the length of the CRC attached to the DCI), s_id may be the index of the first OFDM symbol of the PRACH occasion (0 ≦ s_id < S and S is the maximum number of OFDM symbols per slot depending on the subcarrier spacing (SCS) and the 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 the CP length), f_id may be the index of the PRACH occasion in the frequency domain (0 ≦ f_id < F and F depends on the initial UL BWP configuration of type A UEs and type B UEs), 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) used for PRACH preamble transmission (e.g., 0 for the NUL carrier or the subband index allocated for type A UEs, and 1 for the SUL carrier or the 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). UE120 may determine whether the RAR should be decoded at least partially 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 UE120. The base station 110 may partition the values for s_id, t_id, and / or f_id such that they distinguish the UE type when the modified RNTI is calculated. This may save signaling resources (e.g., save a message that may be 16 bits).

[0088]

[0097] Example 700 also shows that an interleaving pattern may be applied to the CRC portion attached to the DCI that schedules the RAR. Applying an interleaving pattern to the CRC portion may include applying an interleaving pattern to the DCI in addition to the CRC portion. A first interleaving pattern may be applied for a type A UE, and a second interleaving pattern may be applied for a type B UE. There may be no intersection between the set of interleaving patterns for type A and the set of interleaving patterns for type B. UE120 may determine whether the RAR should be decoded based at least partially on the interleaving pattern to be applied. UE120 may apply the interleaving pattern associated with the UE type of UE120, and if the result indicates a decodeable RAR, UE120 may decode the RAR.

[0089]

[0098] In some embodiments, the PDCCH used to schedule the RAR may be polar coded. Additionally, the DMRS sequence of the PDCCH may be scrambled using a sequence associated with a scrambling ID. UE120 may determine whether the RAR should be decoded based at least partially on the scrambling ID applied to the DMRS sequence. A first set of scrambling IDs may be associated with a type A UE, and a second (orthogonal or non-intersecting) set of scrambling IDs may be associated with a type B UE. In some embodiments, the DCI may be scrambled using a sequence associated with a scrambling ID. UE120 may determine whether the RAR should be decoded based at least partially on the scrambling ID applied to the DCI or other coded bits of the PDCCH. By using interleaving patterns, scrambling IDs, or other coding features, UE120 may distinguish RARs by UE type to determine whether the RAR should be decoded by UE120 or whether power and processing resources should be conserved by UE120 not decoding the RAR.

[0090]

[0099] Figure 8 shows an exemplary process 800 performed by, for example, a UE according to the present disclosure. The exemplary process 800 is an example in which a UE (e.g., UE120) performs an operation associated with distinguishing RARs.

[0091]

[0100] As shown in Figure 8, in some embodiments, process 800 may include receiving the RAR (block 810). For example, the UE may receive the RAR (for example, using the receiving component 1002 shown in Figure 10) as described above.

[0092]

[0101] As further shown in Figure 8, in some embodiments, process 800 may include decoding the RAR based at least partially on information that distinguishes the RAR according to the UE type (block 820). For example, the UE may decode the RAR (for example, using the decoding component 1008 shown in Figure 10) based at least partially on information that distinguishes the RAR according to the UE type, as described above.

[0093]

[0102] Process 800 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below and / or elsewhere in this specification.

[0094]

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

[0095]

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

[0096]

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

[0097]

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

[0098]

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

[0099]

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

[0100]

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

[0101]

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

[0102]

[0111] 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 is different from the initial downlink BWP for the second UE type.

[0103]

[0112] In the tenth embodiment, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap, either alone or in combination with one or more of the first to ninth embodiments.

[0104]

[0113] In the eleventh embodiment, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type do not overlap, either alone or in combination with one or more of the first to tenth embodiments.

[0105]

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

[0106]

[0115] In the 13th aspect, decoding a RAR on information, either alone or in combination with one or more of the first to 12 aspects, includes: extracting an RNTI from a CRC; calculating a modified RNTI on at least partly one or more of the index values ​​of the first symbols of the PRACH occasions in the RAR, the index of the first slot of the PRACH occasions in the system frame, and the index of the PRACH occasions in the frequency domain; and decoding the RAR if the RNTI extracted from the RNTI is in the set of RNTIs indicated by the modified RNTI.

[0107]

[0116] In the 14th aspect, either alone or in combination with one or more of the first to 13th aspects, the information includes a CRC, the CRC distinguishing between a RAR for a first UE type and a RAR for a second UE type based at least in part on the interleaving pattern applied to the CRC.

[0108]

[0117] In the 15th aspect, decoding a RAR on information at least partially, either alone or in combination with one or more of the 1st to 14th aspects, includes applying one or more of the first interleaving patterns or the second interleaving patterns to the CRC, wherein the first interleaving pattern is associated with a first UE type and the second interleaving pattern is associated with a second UE type, and decoding a RAR on information at least partially as a result of the application.

[0109]

[0118] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the information includes a DMRS sequence, the DMRS sequence distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on a scrambling ID set applied to the DMRS sequence.

[0110]

[0119] In the 17th aspect, decoding a RAR on information at least partially, either alone or in combination with one or more of the first to 16th aspects, includes 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 a RAR on information at least partially as a result of such application.

[0111]

[0120] In the 18th aspect, either alone or in combination with one or more of the 1st to 17th aspects, the information includes a DCI, which distinguishes between a RAR for a first UE type and a RAR for a second UE type based at least in part on the scrambling ID set applied to the DCI.

[0112]

[0121] In the 19th aspect, decoding a RAR on information at least partially, either alone or in combination with one or more of the first to 18 aspects, includes applying one or more of the first or second scrambling ID sets 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 a RAR on information at least partially as a result of such application.

[0113]

[0122] In the 20th aspect, either alone or in combination with one or more of the first to 19 aspects, the information includes a CORESET, which distinguishes between RARs for a first type of UE and RARs for a second type of UE, at least in part, based on the location of the CORESET (e.g., a time-frequency resource).

[0114]

[0123] In the 21st aspect, either alone or in combination with one or more of the 1st to 20th aspects, the information includes a precoding or spatial region that distinguishes RAR for a first UE type from RAR for a second UE type.

[0115]

[0124] In the 22nd aspect, either alone or in combination with one or more of the 1st to 21st aspects, the information includes a QCLed relationship or spatial relationship for scheduling that distinguishes between RARs for a first UE type and RARs for a second UE type.

[0116]

[0125] In the 23rd aspect, either alone or in combination with one or more of the first to 22 aspects, the information includes reserve bits or spare bits in the DCI (DCI payload) indicating that the RAR is for a first type of UE or for a second type of UE.

[0117]

[0126] In the 24th aspect, the information includes, either alone or in combination with one or more of the first to 23 aspects, one or more PRACH formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0118]

[0127] In the 25th aspect, either alone or in combination with one or more of the 1st to 24th aspects, the information includes a CRC, which distinguishes between a RAR for a first UE type and a RAR for a second UE type, at least in part on the basis that the CRC is associated with a first set of PRACH preambles for a first UE type or a second set of PRACH preambles for a second UE type.

[0119]

[0128] In the 26th aspect, either alone or in combination with one or more of the first to 25 aspects, the first UE type includes UEs with distances from cell centers that satisfy a distance threshold, and the second UE type includes UEs with distances from cell centers that do not satisfy a distance threshold.

[0120]

[0129] In the 27th aspect, either alone or in combination with one or more of the first to 26 aspects, process 800 includes, prior to receiving a RAR, obtaining an initial BWP configuration for random access, which indicates 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.

[0121]

[0130] In the 28th aspect, receiving a RAR, either alone or in combination with one or more of the first to 27 aspects, includes receiving a RAR within an initial downlink BWP configured for the UE type of the UE.

[0122]

[0131] In the 29th aspect, obtaining a configuration, either alone or in combination with one or more of the first to 28 aspects, includes receiving a configuration in the first initial downlink BWP.

[0123]

[0132] In the 30th aspect, either alone or in combination with one or more of the first to 29 aspects, the first initial downlink BWP differs from the initial downlink BWP configured for the UE type of the UE, and 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.

[0124]

[0133] Figure 8 shows an exemplary block of process 800, but in some embodiments, process 800 may include additional blocks, fewer blocks, different blocks, or blocks configured differently, in addition to those shown in Figure 8. Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.

[0125]

[0134] Figure 9 shows an exemplary process 900 performed, for example, by a base station, according to the present disclosure. The exemplary process 900 is an example of an operation performed by a base station (e.g., base station 110) that is associated with distinguishing RARs.

[0126]

[0135] As shown in Figure 9, in some embodiments, process 900 may include encoding the RAR for the UE with information distinguishing the RAR according to the UE type and at least partially based on the UE type of the UE (block 910). For example, a base station (for example, using the encoding component 1108 shown in Figure 11) may encode the RAR for the UE with information distinguishing the RAR according to the UE type and at least partially based on the UE type of the UE, as described above.

[0127]

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

[0128]

[0137] Process 900 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below and / or elsewhere in this specification.

[0129]

[0138] In the first aspect, process 900 includes receiving communications at least in part to RAR.

[0130]

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

[0131]

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

[0132]

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

[0133]

[0142] In the fifth embodiment, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap, either alone or in combination with one or more of the first to fourth embodiments.

[0134]

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

[0135]

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

[0136]

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

[0137]

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

[0138]

[0147] In the tenth aspect, encoding a RAR on information, either alone or in combination with one or more of the first to ninth aspects, includes calculating an RNTI on at least part of one or more of the index values ​​of the first symbols of the PRACH occasions for the RAR, the index of the first slot of the PRACH occasions in the system frame, and the index of the PRACH occasions in the frequency domain, wherein the RNTI distinguishes between RARs for a first UE type and RARs for a second UE type, and masking the CRC of the RAR with the RNTI.

[0139]

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

[0140]

[0149] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the information includes a DMRS sequence, the DMRS sequence distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on a scrambling ID set applied to the DMRS sequence.

[0141]

[0150] In the 13th aspect, either alone or in combination with one or more of the first to 12 aspects, the information includes a DCI, which distinguishes between a RAR for a first UE type and a RAR for a second UE type based at least in part on the scrambling ID set applied to the DCI.

[0142]

[0151] In the 14th aspect, encoding a RAR based at least partially on information, either alone or in combination with one or more of the first to 13th aspects, includes placing the CORESET of the RAR in a location that distinguishes the RAR for a first UE type from the RAR for a second UE type.

[0143]

[0152] In the 15th aspect, the information includes, either alone or in combination with one or more of the 1st to 14th aspects, a precoding that distinguishes between RARs for a first UE type and RARs for a second UE type.

[0144]

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

[0145]

[0154] In the 17th aspect, the information includes, either alone or in combination with one or more of the 1st to 16th aspects, a reserve bit or spare bit in the DCI indicating that the RAR is for a first type of UE or for a second type of UE.

[0146]

[0155] In the 18th aspect, the information includes, either alone or in combination with one or more of the first to 17th aspects, one or more PRACH formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0147]

[0156] In the 19th aspect, either alone or in combination with one or more of the 1st to 18th aspects, the information includes a CRC, which distinguishes between a RAR for a first UE type and a RAR for a second UE type, at least in part on the basis that the CRC is associated with a first set of PRACH preambles for a first UE type or a second set of PRACH preambles for a second UE type.

[0148]

[0157] In the 20th aspect, either alone or in combination with one or more of the first to 19 aspects, the first UE type includes UEs with distances from cell centers that satisfy a distance threshold, and the second UE type includes UEs with distances from cell centers that do not satisfy a distance threshold.

[0149]

[0158] In the 21st aspect, either alone or in combination with one or more of the first to 20 aspects, process 900 includes sending an initial BWP configuration for random access to the UE, indicating an initial downlink BWP and an initial uplink BWP configured for the UE type of the UE, prior to sending a RAR, and receiving random access messages within the initial uplink BWP configured for the UE type of the UE.

[0150]

[0159] In the 22nd aspect, transmitting a RAR, either alone or in combination with one or more of the 1st to 21st aspects, includes transmitting a RAR within an initial downlink BWP configured for the UE type of the UE.

[0151]

[0160] In the 23rd aspect, transmitting a configuration, either alone or in combination with one or more of the first to 22 aspects, includes transmitting a configuration in the first initial downlink BWP.

[0152]

[0161] In the 24th aspect, either alone or in combination with one or more of the first to 23 aspects, the first initial downlink BWP differs from the initial downlink BWP configured for the UE type of the UE, and 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.

[0153]

[0162] Figure 9 shows an exemplary block of process 900, but in some embodiments, process 900 may include additional blocks, fewer blocks, different blocks, or blocks configured differently, in addition to those shown in Figure 9. Additionally or alternatively, two or more blocks of process 900 may be executed in parallel.

[0154]

[0163] Figure 10 is a block diagram of an exemplary device 1000 for wireless communication. Device 1000 may be a UE, or a UE may include device 1000. In some embodiments, device 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (for example, 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 also include a decoding component 1008, among other examples.

[0155]

[0164] In some embodiments, the apparatus 1000 may be configured to perform one or more operations described herein with respect to Figures 1 to 7. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as process 800 in Figure 8. In some embodiments, the apparatus 1000 and / or one or more components shown in Figure 10 may include one or more components of the UE described above with respect to Figure 2. Additionally or alternatively, one or more components shown in Figure 10 may be implemented within one or more components described above with respect to Figure 2. Additionally or alternatively, one or more components of a 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 that can be stored in a non-temporary computer-readable medium and executed by a controller or processor to perform the function or operation of the component.

[0156]

[0165] The receiving component 1002 may receive communications from the device 1006, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may perform signal processing on the received communications (among examples being filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof of the UE described above with respect to Figure 2.

[0157]

[0166] The transmitting component 1004 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1006. In some embodiments, one or more other components of the device 1000 may generate communications and provide the transmitted component 1004 with the generated communications for transmission to the device 1006. In some embodiments, the transmitting component 1004 may perform signal processing on the generated communications (among examples being filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1006. In some embodiments, the transmitting component 1004 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the UE described above with respect to Figure 2. In some embodiments, the transmitting component 1004 may be collated with the receiving component 1002 in the transceiver.

[0158]

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

[0159]

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

[0160]

[0169] Figure 11 is a block diagram of an exemplary device 1100 for wireless communication. Device 1100 may be a base station, or a base station may include device 1100. In some embodiments, device 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (for example, 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 also include one or more coding components 1108, among other examples.

[0161]

[0170] In some embodiments, the device 1100 may be configured to perform one or more operations described herein with respect to Figures 1 to 7. Additionally or alternatively, the device 1100 may be configured to perform one or more processes described herein, such as process 900 in Figure 9. In some embodiments, the device 1100 and / or one or more components shown in Figure 11 may include one or more components of the base station described above with respect to Figure 2. Additionally or alternatively, one or more components shown in Figure 11 may be implemented within one or more components described above with respect to Figure 2. Additionally or alternatively, one or more components of a 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 that can be stored in a non-temporary computer-readable medium and executed by a controller or processor to perform the function or operation of the component.

[0162]

[0171] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some embodiments, the receiving component 1102 may perform signal processing on the received communications (among examples being filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 1100. In some embodiments, the receiving component 1102 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the base station described above with respect to Figure 2.

[0163]

[0172] The transmitting component 1104 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1106. In some embodiments, one or more other components of the device 1100 may generate communications and provide the transmitted component 1104 with the generated communications for transmission to the device 1106. In some embodiments, the transmitting component 1104 may perform signal processing on the generated communications (among examples being filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1106. In some embodiments, the transmitting component 1104 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the base station described above with respect to Figure 2. In some embodiments, the transmitting component 1104 may be collated with the receiving component 1102 in the transceiver.

[0164]

[0173] The encoding component 1108 can encode the RAR for the UE with information that distinguishes the RAR according to the UE type, and at least partially based on the UE type of the UE. The transmitting component 1104 can transmit the RAR to the UE. The receiving component 1102 can receive the communication at least partially based on the RAR.

[0165]

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

[0166]

[0175] The above disclosures are illustrative and explanatory, and are not exhaustive, nor do they limit the embodiments to the exact forms disclosed. Modifications and variations may be made in light of the above disclosures or derived from the practice of the embodiments.

[0167]

[0176] The following provides an overview of some aspects of this disclosure.

[0168]

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

[0169]

[0178] Embodiment 2: The method according to Embodiment 1, wherein decoding a RAR based at least partially on information includes decoding a RAR if the information indicates that the RAR should be decoded by the UE type of the UE.

[0170]

[0179] Embodiment 3: The method of Embodiment 2, further comprising transmitting communications to RAR at least in part.

[0171]

[0180] Embodiment 4: The method of any one of Embodiments 1 to 3, wherein the RAR is not decrypted if the information does not indicate that the RAR should be decrypted by the UE type of the UE.

[0172]

[0181] Embodiment 5: The method according to any one of embodiments 1 to 4, wherein the information distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on the initial bandwidth portion (BWP) configuration.

[0173]

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

[0174]

[0183] Embodiment 7: The method according to Embodiment 5, wherein the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0175]

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

[0176]

[0185] Embodiment 9: The method according to Embodiment 7, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type do not overlap.

[0177]

[0186] Embodiment 10: The method according to Embodiment 7, wherein the initial downlink BWP for a first UE type is different from the initial downlink BWP for a second UE type.

[0178]

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

[0179]

[0188] Embodiment 12: The method according to Embodiment 10, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type do not overlap.

[0180]

[0189] Embodiment 13: The method according to any one of embodiments 1 to 12, wherein the information includes a cyclic redundancy check (CRC) masked using a wireless network temporary identifier (RNTI), wherein the RNTI distinguishes between RARs for a first type of UE and RARs for a second type of UE.

[0181]

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

[0182]

[0191] Embodiment 15: The method according to any one of embodiments 1 to 4, wherein the information includes a cyclic redundancy check (CRC), and the CRC distinguishes between RARs for a first type of UE and RARs for a second type of UE based at least in part on an interleaving pattern applied to the CRC.

[0183]

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

[0184]

[0193] Embodiment 17: The method according to any one of embodiments 1 to 16, wherein the information includes a demodulated reference signal (DMRS) sequence, and the DMRS sequence distinguishes RARs for a first type of UE and RARs for a second type of UE based at least in part on a set of scrambling identifiers (IDs) applied to the DMRS sequence.

[0185]

[0194] Embodiment 18: The method of Embodiment 17, wherein decoding a RAR on at least partially 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.

[0186]

[0195] Embodiment 19: The method according to any one of embodiments 1 to 18, wherein the information includes downlink control information (DCI), and the DCI distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on a set of scrambling identifiers (IDs) applied to the DCI.

[0187]

[0196] Embodiment 20: The method according to Embodiment 19, wherein decrypting a RAR based at least in part on information includes applying one or more of a first scrambling ID set or a second scrambling ID set to a 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.

[0188]

[0197] Embodiment 21: The method according to any one of Embodiments 1 to 20, wherein the information includes a control resource set (CORESET), and the CORESET distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on the location of the CORESET.

[0189]

[0198] Embodiment 22: The method according to any one of embodiments 1 to 21, wherein the information includes precoding to distinguish between RARs for a first UE type and RARs for a second UE type.

[0190]

[0199] Embodiment 23: The method according to any one of embodiments 1 to 22, wherein the information includes a pseudo-colocation relationship for scheduling that distinguishes between RARs for a first UE type and RARs for a second UE type.

[0191]

[0200] Embodiment 24: The method according to any one of embodiments 1 to 23, wherein the information includes a reserve bit or a spare bit in the downlink control information indicating that the RAR is for a first type of UE or for a second type of UE.

[0192]

[0201] Embodiment 25: The method according to any one of Embodiments 1 to 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.

[0193]

[0202] Embodiment 26: The method according to any one of embodiments 1 to 25, wherein the information includes a cyclic redundancy check (CRC), and distinguishes between a RAR for a first UE type and a RAR for a second UE type, at least in part on the basis that the CRC is associated with a first set of physical random access channel (PRACH) preambles for a first UE type or a second set of PRACH preambles for a second UE type.

[0194]

[0203] Embodiment 27: The method according to Embodiment 26, wherein the first UE type includes a UE having a distance from the cell center that satisfies a distance threshold, and the second UE type includes a UE having a distance from the cell center that does not satisfy a distance threshold.

[0195]

[0204] Embodiment 28: The method of any one embodiment 1 to 24, further comprising obtaining an initial BWP configuration for random access, which indicates an initial downlink bandwidth portion (BWP) and an initial uplink BWP configured for the UE type of the UE, prior to receiving a RAR, and transmitting a random access message within the initial uplink BWP configured for the UE type of the UE.

[0196]

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

[0197]

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

[0198]

[0207] Embodiment 31: The method of Embodiment 30, wherein the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of UE, wherein 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.

[0199]

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

[0200]

[0209] Embodiment 33: The method of Embodiment 32, further comprising receiving communications at least partially based on RAR.

[0201]

[0210] Embodiment 34: The method according to Embodiment 32 or 33, wherein the information distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on the initial bandwidth portion (BWP) configuration.

[0202]

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

[0203]

[0212] Embodiment 36: The method according to Embodiment 34, wherein the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0204]

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

[0205]

[0214] Embodiment 38: The method according to Embodiment 36, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type do not overlap.

[0206]

[0215] Embodiment 39: The method according to Embodiment 36, wherein the initial downlink BWP for a first UE type is different from the initial downlink BWP for a second UE type.

[0207]

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

[0208]

[0217] Embodiment 41: The method according to Embodiment 39, wherein the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type do not overlap.

[0209]

[0218] Embodiment 42: The method according to any one embodiment 32 to 41, wherein encoding the RAR on information at least in part comprises calculating a Radio Network Temporary Identifier (RNTI) on at least part in part one or more of the following: the index value of a first symbol of a physical random access channel (PRACH) occasion for the RAR, the index of a first slot of a PRACH occasion in a system frame, and the index of a PRACH occasion in the frequency domain, wherein the RNTI is used to mask the cyclic redundancy check (CRC) of the RAR, distinguishing between RARs for a first UE type and RARs for a second UE type.

[0210]

[0219] Embodiment 43: The method according to any one of embodiments 32 to 42, wherein the information includes a cyclic redundancy check (CRC), and the CRC distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on an interleaving pattern applied to the CRC.

[0211]

[0220] Embodiment 44: The method according to any one of embodiments 32 to 43, wherein the information includes a demodulated reference signal (DMRS) sequence, and the DMRS sequence distinguishes RARs for a first type of UE and RARs for a second type of UE based at least in part on a set of scrambling identifiers (IDs) applied to the DMRS sequence.

[0212]

[0221] Embodiment 45: The method according to any one of embodiments 32 to 44, wherein the information includes downlink control information (DCI), and the DCI distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on a set of scrambling identifiers (IDs) applied to the DCI.

[0213]

[0222] Embodiment 46: The method according to any one of embodiments 32 to 45, wherein encoding the RAR based at least in part on the information includes locating the control resource set (CORESET) of the RAR in a location that distinguishes the RAR for a first type of UE from the RAR for a second type of UE.

[0214]

[0223] Embodiment 47: The method according to any one of embodiments 32 to 46, wherein the information includes precoding to distinguish between RARs for a first UE type and RARs for a second UE type.

[0215]

[0224] Embodiment 48: The method according to any one of embodiments 32 to 47, wherein the information includes a pseudo-colocation relationship for scheduling that distinguishes between RARs for a first UE type and RARs for a second UE type.

[0216]

[0225] Embodiment 49: The method according to any one of embodiments 32 to 48, wherein the information includes a reserve bit or a spare bit in the downlink control information indicating that the RAR is for a first type of UE or for a second type of UE.

[0217]

[0226] Embodiment 50: The method according to any one of embodiments 32 to 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.

[0218]

[0227] Embodiment 51: The method according to any one of embodiments 32 to 50, wherein the information includes a cyclic redundancy check (CRC), and distinguishes between a RAR for a first UE type and a RAR for a second UE type, at least in part on the basis that the CRC is associated with a first set of physical random access channel (PRACH) preambles for a first UE type or a second set of PRACH preambles for a second UE type.

[0219]

[0228] Embodiment 52: The method according to Embodiment 51, wherein the first UE type includes a UE having a distance from a cell center that satisfies a distance threshold, and the second UE type includes a UE having a distance from a cell center that does not satisfy a distance threshold.

[0220]

[0229] Embodiment 53: The method of any one embodiment 32 to 52, further comprising transmitting to the UE an initial bandwidth portion (BWP) configuration for random access, which indicates an initial downlink BWP and an initial uplink BWP configured for the UE's UE type, prior to transmitting a RAR, and receiving random access messages within the initial uplink BWP configured for the UE's UE type.

[0221]

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

[0222]

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

[0223]

[0232] Embodiment 56: The method of Embodiment 55, wherein the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of the UE, wherein 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.

[0224]

[0233] Embodiment 57: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform one or more methods of Embodiments 1 to 56.

[0225]

[0234] Embodiment 58: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein the memory and one or more processors are configured to implement one or more methods of Embodiments 1 to 56.

[0226]

[0235] Embodiment 59: An apparatus for wireless communication, comprising at least one means for carrying out a method according to one or more of embodiments 1 to 56.

[0227]

[0236] Embodiment 60: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code comprises instructions that can be executed by a processor to carry out the method according to one or more embodiments 1 to 56.

[0228]

[0237] Embodiment 61: A non-temporary computer-readable medium for storing a set of instructions for wireless communication, wherein the set of instructions comprises one or more instructions that cause the device to perform one or more of the methods described in Embodiments 1 to 56 when executed by one or more processors of the device.

[0229]

[0238] As used herein, the term “Components” shall be broadly interpreted as hardware, and / or combinations of hardware and software. “Software” shall be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, regardless of the names such as software, firmware, middleware, microcode, and hardware description languages, among others. The processors used herein are implemented as hardware, and / or combinations of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, and / or combinations of hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods is not limited to their embodiments. Therefore, the operation and behavior of the systems and / or methods are described herein independently of any specific software code, and it is understood that software and hardware may be designed to implement the systems and / or methods based at least in part on the descriptions herein.

[0230]

[0239] As used herein, meeting a threshold can mean, depending on the context, that a value is 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, or not equal to the threshold.

[0231]

[0240] While certain combinations of features are expressed in the claims and / or disclosed herein, these combinations do not limit the disclosure of various embodiments. In fact, many of these features can be combined in ways not expressed in the claims and / or disclosed herein in detail. Each dependent claim described below may depend directly on only one claim, but the disclosure of various embodiments includes each dependent claim combined with any other claims in the claims. As used herein, the phrase “at least one of” the list of items refers to any combination of those items, each containing a single member. For example, “at least one of a, b, or c” shall include 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 order of a, b, and c).

[0232]

[0241] No element, action, or command used herein should be construed as important or essential unless expressly described as such. Furthermore, the articles “a” and “an” as used herein include one or more items and may be used interchangeably with “one or more.” Additionally, the article “the” as used herein includes one or more items being referred to in relation to the article “the” and may be used interchangeably with “one or more.” Furthermore, the terms “set” and “group” as used herein 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.” When only one item is intended, the phrase “only one” or a similar expression is used. Also, terms such as “has,” “have,” and “having” as used herein are open-ended terms. Furthermore, the phrase “based on” means “at least partially based on” unless otherwise specified. Furthermore, the term “or” as used herein is inclusive when used consecutively and may be used interchangeably with “and / or” unless otherwise specified (for example, when used in combination with “either” or “only one of”).

Claims

1. User equipment (UE) for wireless communication, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors are Receiving a Random Access Response (RAR) and Decoding the RAR based at least partially on information that distinguishes the RAR according to the UE type, User equipment (UE) configured to perform the following actions.

2. The one or more processors, prior to receiving the RAR, Obtain an initial BWP configuration for random access, which shows the initial downlink bandwidth portion (BWP) and initial uplink BWP configured for the UE type of the aforementioned UE, Sending random access messages within the initial uplink BWP configured for the UE type of the UE, The UE according to claim 1, configured to perform the following actions.

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

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

5. The first initial downlink BWP differs from the initial downlink BWP configured for the UE type of the UE, The information distinguishes between a RAR for a first UE type and a RAR for a second UE type, based at least in part on the initial BWP configuration. The UE according to claim 4.

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

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

8. The UE according to claim 6, wherein the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

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

10. The UE according to claim 8, wherein the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type do not overlap.

11. The UE according to claim 8, wherein the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type.

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

13. The aforementioned information includes a cyclic redundancy check (CRC) masked using a wireless network temporary identifier (RNTI), The aforementioned RNTI distinguishes between RAR for a first UE type and RAR for a second UE type. The UE according to claim 1.

14. The one or more processors, in order to decode the RAR based at least partially on the information, Extracting the RNTI from the CRC, Calculating a modified RNTI based at least partially on one or more of the following: the index value of the first symbol of the physical random access channel (PRACH) occasion of the RAR, the index of the first slot of the PRACH occasion in the system frame, and the index of the PRACH occasion in the frequency domain; If the RNTI extracted from the RNTI is in the set of RNTIs indicated by the modified RNTI, the RAR is decoded. The UE according to claim 13, configured to perform the following.

15. The information includes a cyclic redundancy check (CRC), the CRC distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on the interleaving pattern applied to the CRC, The one or more processors, in order to decode the RAR based at least partially on the information, Applying one or more of the first interleaving pattern or the second interleaving pattern to the CRC, wherein the first interleaving pattern is associated with the first UE type, and the second interleaving pattern is associated with the second UE type. Based at least in part on the results of the above application, the RAR is decoded, The UE according to claim 1, configured to perform the following actions.

16. The UE according to claim 1, wherein the information includes a demodulated reference signal (DMRS) sequence, the DMRS sequence 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 identifiers (IDs) applied to the DMRS sequence.

17. The one or more processors, in order to decode the RAR based at least partially on the information, Applying one or more of the first scrambling ID set or the second scrambling ID set to the DMRS sequence, wherein the first scrambling ID set is associated with the first UE type, and the second scrambling ID set is associated with the second UE type. Based at least in part on the results of the above application, the RAR is decoded, The UE according to claim 16, configured to perform the following.

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

19. The one or more processors, in order to decode the RAR based at least partially on the information, Applying one or more of the first scrambling ID set or the second scrambling ID set to the DCI, wherein the first scrambling ID set is associated with the first UE type, and the second scrambling ID set is associated with the second UE type. Based at least in part on the results of the above application, the RAR is decoded, The UE according to claim 18, configured to perform the following actions.

20. The UE according to claim 1, wherein the information includes a control resource set (CORESET), and the CORESET distinguishes between RARs for a first UE type and RARs for a second UE type, at least partially based on the location of the CORESET.

21. The UE according to claim 1, wherein the information includes precoding to distinguish between RARs for a first UE type and RARs for a second UE type.

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

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

24. A base station for wireless communications, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors are Encoding Random Access Responses (RARs) for User Equipment (UE) with information that distinguishes RARs according to the UE type, and at least partially based on the UE type of the UE, The RAR is transmitted to the UE, A base station configured to perform the following actions.

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

26. The base station according to claim 24, wherein the information includes a demodulation reference signal (DMRS) sequence, the DMRS sequence distinguishes between a RAR for a first UE type and a RAR for a second UE type, at least in part on a set of scrambling identifiers (IDs) applied to the DMRS sequence.

27. The base station according to claim 24, wherein the information includes downlink control information (DCI), and the DCI distinguishes between RARs for a first UE type and RARs for a second UE type based at least in part on a set of scrambling identifiers (IDs) applied to the DCI.

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

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

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

Images