Random access response differentiation

Abstract

The various formats covered in this case typically involve wireless communication. In some formats, the user equipment (UE) can receive a random access response (RAR). The UE can decode the RAR, at least in part, based on information that distinguishes the RAR according to the UE type. Numerous other formats are described.

Description

[Technical Field]

[0001] In general, the contents of this case relate to wireless communication, and more specifically, the contents of this case relate to techniques and apparatus for distinguishing random access responses. [Previous Technology]

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

[0003] A wireless network may include multiple base stations (BSs), where each BS can support communication between multiple user equipment (UEs). UEs can communicate with the BS via downlinks and uplinks. A "downlink" or "forward link" refers to the communication link from the BS to the UE, while an "uplink" or "backlink" refers to the communication link from the UE to the BS. As described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmitter Receiver Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0004] The above multiplexing access technology has been adopted in various telecommunications standards to provide a universal protocol that enables different user devices to communicate across city limits, countries, regions, and even globally. NR (which can be referred to as 5G) is an enhancement set of the LTE mobile service standard released by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving service, making full use of new spectrum, using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful. [Summary of the Invention]

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

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

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

[0008] 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 a RAR for the UE using information that distinguishes the RAR according to the UE type and at least in part based on the UE type; and send the RAR to the UE.

[0009] In some cases, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a RAR and decode the RAR at least in part based on information that distinguishes the RAR according to the UE type.

[0010] In some cases, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: encode a RAR for the UE using information that distinguishes the RAR according to the UE type and at least in part based on the UE type; and send the RAR to the UE.

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

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

[0013] The general categories of things described herein include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, as fully described with reference to the accompanying drawings and description and as shown in the accompanying drawings and description.

[0014] To better understand the embodiments described below, the features and technical advantages of the examples based on this invention have been generally summarized above. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures to perform the same purpose as the contents of this invention. These equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein (regarding their organization and operation) and the associated advantages will be better understood when the embodiments described below are considered in conjunction with the accompanying drawings. Each of these drawings is provided for illustrative and descriptive purposes only and is not intended to limit the invention.

[0015] Although various embodiments have been described in this document by way of example, those skilled in the art will understand that these embodiments can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some embodiments can be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, or artificial intelligence devices). Embodiments can be implemented using chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices containing the described embodiments and features may also need to include other components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals may include multiple components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or accumulators) for analog and digital purposes. The various forms described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user devices with different sizes, shapes, and constructions.

Implementation Method

[0027] Various forms of the present invention are described more fully below with reference to the accompanying drawings. However, the present invention can be implemented in many different forms and should not be construed as being limited to any particular structure or function provided throughout the present invention. Rather, these forms are provided only to make the present invention thorough and complete and to fully convey the scope of protection of the present invention to those skilled in the art to which it pertains. Based on the present invention, those skilled in the art to which it pertains should understand that the scope of protection of the present invention is intended to cover any form of the disclosed content herein, whether implemented independently or in combination with any other form of the present invention. For example, an apparatus or method may be implemented using any number of the forms set forth herein. Furthermore, the scope of protection of the present invention is intended to cover such apparatus or method that may be implemented by using other structures, functions, or structures and functions other than those of the various forms of the present invention set forth herein, or structures and functions different from those of the various forms of the present invention set forth herein. It should be understood that any form of the disclosure herein may be embodied by one or more components of the present invention.

[0028] Various devices and techniques are now provided for the presentation of some aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated 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 any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0029] It should be noted that although the terms commonly associated with 5G or NR radio access technology (RAT) are used to describe the various forms, the various forms of the present invention may also be applied to other RATs (e.g., 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G)).

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

[0031] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers), allowing UEs with service subscriptions unrestricted access. A picocell can cover a relatively small geographic area, allowing UEs with service subscriptions unrestricted access. A femtocell can cover a relatively small geographic area (e.g., a home), allowing restricted access for UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for a macrocell can be called a macro BS. A BS used for a picocell can be called a pico BS. A BS used for a femtocell can be called a femto BS or a home BS. In the example shown in Figure 1, BS 110a can be a macro BS for macrocell 102a, BS 110b can be a pico BS for picocell 102b, and BS 110c can be a femto BS for femtocell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB” and “cell” may be used interchangeably in this article.

[0032] In some states, the cell does not need to be stationary; the geographical area of ​​the cell can move according to the location of the active BS. In some states, BSs can use any suitable transport network to interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (e.g., direct physical connections or virtual networks).

[0033] In some embodiments, the term "base station" (e.g., base station 110) or "network entity" may refer to an aggregation base station, a decomposition base station, an integrated access and return (IAB) node, a relay node, and / or one or more of its components. For example, in some embodiments, "base station" or "network entity" may represent 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 term "base station" or "network entity" may represent a device configured to perform one or more functions, such as those described herein in conjunction with base station 110. In some embodiments, the term "base station" or "network entity" may represent a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (possibly located in the same or different geographical locations) can be configured to perform at least a portion of a function, or to replicate at least a portion of the execution of a function, and the terms "base station" or "network entity" can represent any one or more of these different devices. In some cases, the terms "base station" or "network entity" can represent one or more virtual base stations and / or one or more virtual base station functions. For example, in some cases, two or more base station functions can be exemplified on a single device. In some cases, the terms "base station" or "network entity" can represent one base station function instead of another. In this way, a single device can include more than one base station.

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

[0035] Wireless network 100 can be a heterogeneous network comprising different types of BSs (e.g., macro BS, pico BS, femto BS, repeater BS, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have higher transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and repeater BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0036] The network controller 130 can be coupled to a group of BSs and provide coordination and control for these BSs. The network controller 130 can communicate with these BSs via backhaul. These BSs can also communicate with each other, for example, directly or indirectly via wireless or wired backhaul communication.

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

[0038] Some UEs can be capacity-reduced (RedCap) UEs capable of decoding Random Access Responses (RARs), where the RAR is part of the Random Access Channel (RACH) procedure used to establish Radio Resource Control (RRC) connections. Different types of UEs may exist, and they can only decode the RAR if it is configured for that UE type. Some UEs can be considered Machine-Type Communication (MTC) UEs or evolved or enhanced Machine-Type Communication (eMTC) UEs. For example, MTC UEs and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, and / or location tags capable of communicating with base stations, another device (e.g., remote devices), or some other entity. Wireless nodes can provide connectivity to or from networks (e.g., wide area networks such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 may be included in a housing that houses the components of UE 120 (e.g., processor components and / or memory components). In some cases, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] Typically, any number of wireless networks can be deployed within a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be called a radio technology, air interface, etc. A frequency can also be called a carrier, frequency channel, etc. Each frequency can 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 can be deployed.

[0040] In some cases, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more lateral link channels (e.g., without using base station 110 as a relay device to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols) and / or mesh networks. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein that are performed by base station 110.

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

[0042] As indicated above, Figure 1 is provided as an example. Other examples may differ from those described with reference to Figure 1.

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

[0044] At base station 110, transmit processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on the Channel Quality Indicator (CQI) received from each UE, process the data for each UE (e.g., encoding and modulation) based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling), and provide management burden symbols and control symbols. Transmit processor 220 can 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 signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​these data symbols, control symbols, management burden symbols, and / or reference symbols (if any), and provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can also further process the output sample stream (e.g., convert to analog signal, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t respectively.

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

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

[0047] The antenna (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, etc., or may be included in these components. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include a set of coplanar antenna elements and / or a set of non-coplanar antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or multiple antenna elements within housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG. 2.

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

[0049] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if any), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data slot 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule downlink and / or uplink communication for UE 120. In some embodiments, modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some embodiments, base station 110 includes transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220 and / or TX MIMO processor 230. The processor (e.g., controller / processor 240) and memory 242 may be used to perform various forms of any of the methods described herein (e.g., as described with reference to FIG3-11).

[0050] Communication systems such as 5G NR systems can be deployed in various ways with a variety of 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 (e.g., base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, a BS (e.g., node B, evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a decomposed base station.

[0051] Aggregated base stations can be configured to utilize radio protocol stacks that are physically or logically integrated within a single RAN node. Decomposed base stations can be configured to utilize protocol stacks that are physically or logically distributed between two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some cases, the CU can be implemented within a RAN node, and one or more DUs can be located in the same location as the CU, or alternatively, they can be geographically or virtually distributed in one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU).

[0052] The operation or network design of base station types can consider the aggregation characteristics of base station functions. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (e.g., network configurations sponsored by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functions among two or more units in different physical locations, as well as virtually distributing functions to at least one unit, which allows for flexibility in network design. Individual units of a decomposed base station or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless means.

[0053] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may execute one or more technologies associated with RAR as part of the RACH procedure, as further described in detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may execute or direct the operation of, for example, process 800 of FIG. 8, process 900 of FIG. 9, and / or other processes as described herein. Memory 242 and memory 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-transitory computer-readable media 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 of base station 110 and / or UE 120 (e.g., directly or after compilation, translation, and / or interpretation), it may cause one or more processors, UE 120, and / or base station 110 to perform or direct operations such as process 800 of FIG. 8, process 900 of FIG. 9, and / or other processes described herein. In some cases, the execution instructions may include execution instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0054] In some configurations, UE 120 includes: a unit for receiving RAR; and / or a unit for decoding RAR at least in part based on information that distinguishes RAR according to UE type. For example, the unit for UE 120 to perform the operations described herein may include one or more of antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, transmitter processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0055] In some embodiments, the base station includes: a unit for encoding a RAR for a UE using information that distinguishes the RAR according to the UE type and at least partially based on the UE type; and / or a unit for transmitting the RAR to the UE. For example, the unit for the base station to perform the operations described herein may include 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.

[0056] Although the blocks in FIG2 are shown as different components, the functions described above with respect to these blocks can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be executed by the controller / processor 280, or executed under the control of the controller / processor 280.

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

[0058] Figure 3 is a diagram 300 showing the type of equipment according to the contents of this case.

[0059] As shown in Figure 3, Ultra-Reliable Low-Latency Communication (URLLC) devices and Enhanced Mobile Broadband (eMBB) devices can be considered NR Advanced devices (e.g., UEs). Some devices, such as Low-Power Wide-Area (LPWA) devices or Massive Machine-Type Communication (mMTC) devices, can be considered Enhanced LTE devices. Figure 3 shows some wireless communication devices that are not NR Advanced UEs but rather degraded devices. Such degraded devices can include loosely configured IoT devices, smart wearables, sensors, and video surveillance cameras. Degraded devices can be referred to as NR RedCap devices, RedCap devices, Red Cap devices, Red-Cap devices, redcap devices, red cap devices, red-cap devices, and / or NR RedCap UEs. NR RedCap devices are also referred to as NR Light devices or NR Lite devices. For ease of explanation, the term NR RedCap UE may be used in the context described herein.

[0060] In some configurations, the NR RedCap UE may have reduced capabilities due to its ability or configuration to provide less peak throughput, longer latency, lower reliability, higher power efficiency, less system management burden, and / or less resource cost. The NR RedCap UE may be subject to relaxed latency or reliability requirements. In some configurations, the NR RedCap UE may have only one or two transmit or receive antennas.

[0061] In some configurations, an NR RedCap UE may have or be configured to use a subset of features available to an NR Advanced UE or other full-featured NR UEs for personal communications. In some configurations, an NR RedCap UE may have a set of mandatory features and a set of optional features, wherein one or more optional features in the NR RedCap UE are mandatory for NR Advanced UEs. In some configurations, standard charts or feature matrices may be used to specify whether a device is an NR RedCap UE.

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

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

[0064] Figure 4 illustrates an example 400 of the configuration used for NR RedCap UE according to the contents of this case.

[0065] In some configurations, the NR RedCap UE may support reduced bandwidth and a reduced number of transmit and receive antennas. For example, at least for FR1, the NR RedCap UE may support a maximum downlink (DL) or uplink (UL) bandwidth of 20 MHz or 40 MHz. The NR RedCap UE may support maximum bandwidth configured separately for DL ​​and UL. For NR RedCap UEs with reduced bandwidth capabilities (e.g., reduced from 100 MHz for FR1), the maximum bandwidth used for control information or data in UL and DL may be reduced. NR RedCap UEs with reduced bandwidth capabilities may not be expected to support carrier aggregation or dual connectivity that may be required by non-NR RedCap UEs. In some embodiments, the NR RedCap UE may support at most one transmit antenna and at most one or two receive antennas.

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

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

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

[0069] In summary, an NR RedCap UE can have a configuration that is at least partially determined by the type of NR RedCap UE. Therefore, an NR RedCap UE can conserve power, processing resources, and signal transmission resources to support a reduced set of features. In some cases, an NR RedCap UE can support the same power-saving modes, the same set of processing capabilities and isochronous lines, or a set of fallback capabilities as another type of NR UE, where the other type of NR UE may also have reduced capabilities or not. For example, an NR RedCap UE may have a set of reduced capabilities but may also fall back to a further reduced set of capabilities.

[0070] An NR RedCap UE may need to execute a RACH procedure for accessing the channel and establishing a connection. The RACH procedure can be the same for each UE, even if different UEs have different UE capabilities. In some scenarios, the base station may send multiple RACH messages to multiple UEs, such as multiple RARs. UEs with limited capabilities may waste power and processing resources attempting to decode and process RARs that may not be intended for that UE.

[0071] According to the various states described herein, a UE may receive a RAR as part of a RACH procedure and decode the RAR at least in part based on information distinguishing the RAR according to the UE type. That is, if the information indicates that the RAR should be decoded according to the UE type, the UE may decode the RAR. The RAR may be used for a first UE type (e.g., type A) or a second UE type (e.g., type B), but not for both UE types simultaneously. Examples of the first UE type and the second UE type may include: RedCap UE and non-RedCap UE, RedCap UE with one receive antenna branch and RedCap UE with two receive antenna branches, UE supporting coverage enhancement and UE not supporting coverage enhancement, UE supporting small data transmission (SDT) and UE not supporting SDT, or UE supporting RAN slicing and UE not supporting RAN slicing. By distinguishing RARs, the UE can decode RARs intended for the UE (or the UE type) and save power and processing resources by not attempting to decode and process RARs not intended for the UE (or the UE type). The UE can receive information for RAR distinction or retrieve information from stored configuration information. This information can instruct the UE on how to decide whether to decode RARs or other RACH messages.

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

[0073] Figure 5 is a diagram illustrating an example 500 of distinguishing RAR according to the content of this case. As shown in Figure 5, base station 110 and UE 120 can communicate with each other to perform a 4-step RACH procedure.

[0074] As shown in component symbol 505, base station 110 can transmit random access configuration information, and UE 120 can receive it. In some cases, the random access configuration information may be transmitted and / or indicated via system information (e.g., in one or more system information blocks (SIBs), such as in SIB 2) and / or synchronization signal blocks (SSBs), for example, for use in contention-based random access. Alternatively or supplementarily, the random access configuration information may be transmitted in RRC messages that trigger RACH procedures and / or entity downlink control channel (PDCCH) command messages, for example, for contention-free random access. The random access configuration information may include information for receiving RAR and for distinguishing RARs based on UE type.

[0075] As shown in component symbol 510, UE 120 can transmit random access messages (RAM), which may include preamble signals (sometimes referred to as random access preamble signals, physical RACH (PRACH) preamble signals, or RAM preamble signals). In a four-step RACH procedure, the message including the preamble signal may be referred to as message 1, Msg1, msg1, MSG1, first message, or initial message. The RAM may include a random access preamble signal identifier.

[0076] As indicated by component symbol 515, base station 110 may send a RAR as a response to a preamble signal. The message including the RAR may be referred to as message 2, Msg2, msg2, MSG2, or the second message in the four-step RACH procedure. In some cases, the RAR may indicate the detected random access preamble signal identifier (e.g., received from UE 120 in Msg1). Alternatively or supplementarily, the RAR may indicate the uplink grant or resource configuration to be used by UE 120 to send message 3 (msg3).

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

[0078] As shown in component symbol 520, UE 120 can distinguish whether the RAR is for UE 120 or for a specific UE type. In some cases, UE 120 can determine whether the RAR will be decoded by UE 120 based at least in part on the Initial Bandwidth Part (BWP) configuration, which can be configured individually for each UE type. This will be described in more detail with reference to Figure 6. In some cases, UE 120 can determine whether to decode the RAR based at least in part on Cyclic Redundancy Check (CRC). For example, the CRC can be masked with a Radio Network Temporary Identifier (RNTI), and if the RNTI extracted from the CRC belongs to a specific set of RNTIs, then UE 120 can decode the RAR. In some cases, UE 120 can determine whether to decode the RAR based at least in part on the interleaving mode or scrambling identifier (ID) used. These cases are described in more detail with reference to Figure 7.

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

[0080] In some cases, UE 120 may have information about the decoding or quasi-co-location (QCLed) relationship used for scheduling RAR. For example, QCL can be performed on PDCCH using an SSB index reserved for a specific UE type. UE 120 may determine whether to decode RAR based at least in part on the SSB index.

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

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

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

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

[0085] As shown in component symbol 525, if the RAR is intended for UE 120 or the UE type of UE 120, then UE 120 may decode the RAR. If the RAR is not intended for UE 120, then UE 120 may not decode the RAR, thus saving the power and processing resources originally consumed by decoding and processing the RAR.

[0086] The UE can transmit communications at least in part based on communications. As shown in component symbol 530, UE 120 can send an RRC connection request message as a communication. This RRC connection request message can be referred to as message 3, Msg3, msg3, MSG3, or the third message of the four-step RACH procedure. In some cases, the RRC connection request may include the UE identifier, uplink control information (UCI), and / or PUSCH communications (e.g., RRC connection request). Base station 110 can send a Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) for Msg3.

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

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

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

[0090] Figure 6 is a diagram illustrating an example 600 for distinguishing overlapping and non-overlapping BWPs of RAR, according to the contents of this case.

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

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

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

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

[0095] Figure 7 is a diagram illustrating an example 700 of encoding a DCI for scheduling a RAR, according to the content of this case. Example 700 illustrates the DCI payload for scheduling the RAR and the CRC that can be attached to the DCI. As shown in Example 700, the CRC of the DCI for scheduling the RAR can be masked using RNTI (e.g., via a logical XOR operation). The RNTI can belong to a first group of RNTIs or a second group of RNTIs, wherein the first group of RNTIs can be applied to mask the CRC of the DCI for scheduling a type A RAR, while the second group of RNTIs is used for scheduling a type B RAR. There may be no overlap between the first group of RNTIs and the second group of RNTIs. The first group of RNTIs and the second group of RNTIs can be orthogonal. The RNTI for each set can be constructed according to the modified RNTI formula: Modified RNTI = mod(1 + s_id + S × t_id + S × T × f_id + S × T × F × ul_FDRA_id + , - 1), where s_id can be represented as the number of bits allocated in the modified RNTI (upper limit is the length of the CRC appended to the DCI), s_id can be the index of the first OFDM symbol of the PRACH timing (0 ≦ s_id < S, where S is the maximum number of OFDM symbols per slot, which depends on the subcarrier spacing (SCS) and CP length), t_id can be the index of the first slot of the PRACH timing in the system frame (0 ≦ t_id < T, and t_id depends on the SCS and CP length), and f_id can be the index of the PRACH timing in the frequency domain (0 ≦ t_id < T, and t_id depends on the SCS and CP length). ≦f_id<F, where F depends on the initial UL BWP configuration of Type A and Type B UEs), and the start point, spacing, and range of f_id (Type A and Type B UEs can take different values), ul_FDRA_id can be the UL frequency domain resource configuration (FDRA) for PRACH preamble signal transmission (e.g., 0 for NUL carriers or subband indices allocated to Type A UEs, and 1 for SUL carriers or subband indices allocated to Type B UEs), and ∆_F_F_D depends on whether Type A and Type B UEs share the same PRACH timing (for different PRACH timings, ∆_F_F_D = 0). 0, for shared PRACH timing and different preceding signal groups, ∆_ ...Base station 110 can partition the values ​​of s_id, t_id, and / or f_id so that they can distinguish the UE type when calculating the modified RNTI. This can save signal transmission resources (e.g., potentially saving 16 bits of message).

[0096] Example 700 also illustrates that an interleaving mode can be applied to the CRC portion of the DCI appended to the scheduled RAR. Applying an interleaving mode to the CRC portion may include applying the interleaving mode to the DCI other than the CRC portion. A first interleaving mode may be applied to a type A UE, and a second interleaving mode may be applied to a type B UE. There may be no overlap between a set of interleaving modes for type A and a set of interleaving modes for type B. UE 120 may determine whether to decode the RAR based at least in part on the applied interleaving mode. UE 120 may apply an interleaving mode associated with the UE type of UE 120, and if the result indicates that the RAR is decodeable, then UE 120 may decode the RAR.

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

[0098] Figure 8 is a diagram illustrating, for example, an instance process 800 performed by a UE, according to the content of this case. Instance process 800 is an instance of a UE (e.g., UE 120) performing an operation associated with distinguishing RAR.

[0099] As shown in FIG8, in some cases, processing 800 may include receiving RAR (block 810). For example, the UE may (e.g., using the receiving component 1002 illustrated in FIG10) receive RAR as described above.

[0100] As further shown in FIG8, in some cases, processing 800 may include decoding the RAR at least in part based on information that distinguishes the RAR according to the UE type (block 820). For example, the UE may (e.g., using the decoding component 1008 illustrated in FIG10) decode the RAR at least in part based on information that distinguishes the RAR according to the UE type, as described above.

[0101] Process 800 may include additional patterns, such as any single pattern or any combination of patterns described below and / or patterns of one or more other processes described elsewhere herein.

[0102] In the first state, decoding the RAR at least in part based on the information includes: if the information indicates that the RAR will be decoded by the UE type of the UE, then the RAR is decoded.

[0103] In the second state, either alone or in combination with the first state, processing 800 includes: sending communications at least in part based on the RAR.

[0104] In the third state sample, either alone or in combination with one or more of the first and second state samples, if the information indicates that the RAR will not be decoded by the UE type of the UE, then the RAR will not be decoded.

[0105] In the fourth state, either alone or in combination with one or more of the first to third states, the information is based at least in part on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

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

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

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

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

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

[0111] In the tenth state, 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 state types.

[0112] In the eleventh state, either alone or in combination with one or more of the first to tenth state states, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

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

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

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

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

[0117] In the sixteenth state sample, alone or in combination with one or more of the first to fifteenth state samples, the information includes a DMRS sequence, which distinguishes between a RAR for a first UE type and a RAR for a second UE type based at least in part on a set of scrambling IDs applied to the DMRS sequence.

[0118] In the seventeenth state sample, decoding the RAR, either alone or in combination with one or more of the first to sixteenth state samples, at least in part based on the information, includes: applying one or more of a first scrambling ID set or a 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; and decoding the RAR at least in part based on the result of the application.

[0119] In the eighteenth state sample, alone or in combination with one or more of the first to seventeenth state samples, 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 a set of scrambling IDs applied to the DCI.

[0120] In the nineteenth state sample, decoding the RAR, either alone or in combination with one or more of the first to eighteenth states, at least in part based on the information, includes: applying one or more of a first scrambling ID set or a second scrambling ID set to the DCI, wherein the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type; and decoding the RAR at least in part based on the result of the application.

[0121] In the twentieth state, alone or in combination with one or more of the first to nineteenth states, the information includes a CORESET, 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 location of the CORESET (e.g., time and frequency resources).

[0122] In the 21st state sample, alone or in combination with one or more of the first to 20th state samples, the information includes precoding or spatial domains that distinguish between RAR for the first UE type and RAR for the second UE type.

[0123] In the 22nd state, alone or in combination with one or more of the first to 21st states, the information includes QCLed relationships or spatial relationships for scheduling, which distinguish between RARs for the first UE type and RARs for the second UE type.

[0124] In the 23rd state sample, alone or in combination with one or more of the first to 22nd state samples, the information includes reserved or spare bits in the DCI (DCI payload) indicating whether the RAR is for a first UE type or for a second UE type.

[0125] In the 24th state sample, either alone or in combination with one or more of the first to 23rd state samples, the information includes one or more PRACH formats associated with the first UE type or one or more PRACH formats associated with the second UE type.

[0126] In the 25th state sample, either alone or in combination with one or more of the 1st to 24th state samples, the information includes a CRC, which distinguishes between the RAR for the first UE type and the RAR for the second UE type based at least in part on whether it is associated with a first set of PRACH preamble signals for the first UE type or with a second set of PRACH preamble signals for the second UE type.

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

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

[0129] In the twenty-eighth state, receiving the RAR alone or in combination with one or more of the first to twenty-seventh states includes receiving the RAR within the initial downlink BWP configured for the UE type of the UE.

[0130] In the twenty-ninth state sample, obtaining the configuration alone or in combination with one or more of the first to twenty-eighth state samples includes: receiving the configuration in the first initial downlink BWP.

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

[0132] Although FIG8 illustrates an exemplary block of process 800, in some cases, process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those described in FIG8. Alternatively or supplementarily, two or more blocks of process 800 may be performed in parallel.

[0133] Figure 9 is a diagram illustrating, for example, an exemplary process 900 performed by a base station, according to the content of this case. The exemplary process 900 is an example of an operation performed by a base station (e.g., base station 110) associated with distinguishing RARs.

[0134] As shown in FIG9, in some cases, processing 900 may include: encoding the RAR for the UE using information that distinguishes the RAR according to the UE type and at least partially based on the UE type (block 910). For example, the base station may (e.g., using the encoding component 1108 illustrated in FIG11) encode the RAR for the UE using information that distinguishes the RAR according to the UE type and at least partially based on the UE type, as described above.

[0135] As further shown in FIG9, in some cases, process 900 may include sending the RAR to the UE (block 920). For example, the base station may send the RAR to the UE (e.g., using the transmission component 1104 illustrated in FIG11), as described above.

[0136] Process 900 may include additional patterns, such as any single pattern or any combination of patterns described below and / or patterns of one or more other processes described elsewhere herein.

[0137] In the first state, processing 900 includes: receiving communications at least in part based on the RAR.

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

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

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

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

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

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

[0144] In the eighth state, 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 state types.

[0145] In the ninth state, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping, either alone or in combination with one or more of the first to eighth states.

[0146] In the tenth state sample, encoding the RAR, either alone or in combination with one or more of the first to ninth state samples, at least partially based on the information, includes calculating the RNTI based at least partially on one or more of the following: the index value of the first symbol of the PRACH timing of the RAR, the index of the first time slot of the PRACH timing in the system frame, and the index of the PRACH timing in the frequency domain, wherein the RNTI distinguishes between RARs for a first UE type and RARs for a second UE type, and uses the RNTI to mask the CRC of the RAR.

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

[0148] In the twelfth state sample, alone or in combination with one or more of the first to eleventh state samples, the information includes a DMRS sequence, which is at least partially based on a set of scrambling IDs applied to the DMRS sequence to distinguish between a RAR for a first UE type and a RAR for a second UE type.

[0149] In the thirteenth state sample, alone or in combination with one or more of the first to twelfth state samples, 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 a set of scrambling IDs applied to the DCI.

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

[0151] In the fifteenth state sample, alone or in combination with one or more of the first to fourteenth state samples, the information includes precoding that distinguishes between RAR for the first UE type and RAR for the second UE type.

[0152] In the sixteenth state sample, alone or in combination with one or more of the first to fifteenth state samples, the information includes a QCLed relationship for scheduling, which distinguishes between RAR for the first UE type and RAR for the second UE type.

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

[0154] The eighteenth state sample, alone or in combination with one or more of the first to seventeenth state samples, includes one or more PRACH formats associated with the first UE type or one or more PRACH formats associated with the second UE type.

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

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

[0157] In the 21st state, either alone or in combination with one or more of the first to 20th states, the process 900 includes: before sending the RAR: sending an initial BWP configuration for random access to the UE, the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for the UE type of the UE; and receiving random access messages within the initial uplink BWP configured for the UE type of the UE.

[0158] In the 22nd state sample, either alone or in combination with one or more of the 1st to 21st state samples, sending the RAR includes sending the RAR within the initial downlink BWP configured for the UE type of the UE.

[0159] In the 23rd state sample, the configuration is sent alone or in combination with one or more of the first to 22nd state samples, including sending the configuration in the first initial downlink BWP.

[0160] In the 24th state, either alone or in combination with one or more of the first to 23rd states, the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of the UE, and the information is based at least in part on the initial BWP configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

[0161] Although FIG9 illustrates an exemplary block of process 900, in some cases, process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those described in FIG9. Alternatively or supplementarily, two or more of the blocks in process 900 may be performed in parallel.

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

[0163] In some embodiments, device 1000 may be configured to perform one or more operations described herein in conjunction with Figures 1-7. Alternatively or additionally, device 1000 may be configured to perform one or more processes described herein, such as process 800 of Figure 8. In some embodiments, device 1000 and / or one or more components shown in Figure 10 may include one or more components of the UE described above in conjunction with Figure 2. Alternatively or additionally, one or more components shown in Figure 10 may be implemented within one or more components described above in conjunction with Figure 2. Alternatively or additionally, one or more of these components may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0164] The receiving unit 1002 may receive communications (e.g., reference signals, control information, data communications, or combinations thereof) from the device 1006. The receiving unit 1002 may provide the received communications to one or more other components of the device 1000. In some cases, the receiving unit 1002 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other instances thereof), and may provide the processed signal to one or more other components of the device 1000. In some cases, the receiving unit 1002 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the UE described above in conjunction with FIG. 2.

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

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

[0167] The number and arrangement of components shown in Figure 10 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 10. Furthermore, two or more components shown in Figure 10 may be implemented in a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Supplementally or alternatively, a group of components shown in Figure 10 (e.g., one or more components) may perform one or more functions described as being performed by another group of components shown in Figure 10.

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

[0169] In some embodiments, device 1100 may be configured to perform one or more operations described herein in conjunction with Figures 1-7. Alternatively or additionally, device 1100 may be configured to perform one or more processes described herein, such as process 900 of Figure 9. In some embodiments, device 1100 and / or one or more components shown in Figure 11 may include one or more components of the base station described above in conjunction with Figure 2. Alternatively or additionally, one or more components shown in Figure 11 may be implemented within one or more components described above in conjunction with Figure 2. Alternatively or additionally, one or more of these components may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0170] The receiving unit 1102 may receive communications (e.g., reference signals, control information, data communications, or combinations thereof) from the device 1106. The receiving unit 1102 may provide the received communications to one or more other components of the device 1100. In some embodiments, the receiving unit 1102 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other instances thereof), and may provide the processed signal to one or more other components of the device 1100. In some embodiments, the receiving unit 1102 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof from the base station described above in conjunction with FIG2.

[0171] Transmission component 1104 can send communications (e.g., reference signals, control information, data communications, or combinations thereof) to device 1106. In some cases, one or more other components of device 1100 can generate communications and provide the generated communications to transmission component 1104 for transmission to device 1106. In some cases, transmission component 1104 can perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other instances thereof), and can send the processed signals to device 1106. In some cases, transmission component 1104 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof from the base station described above in conjunction with FIG2. In some cases, transmission component 1104 may be co-located with receiver component 1102 in a transceiver.

[0172] The encoding component 1108 can encode the RAR for the UE using information that distinguishes the RAR according to the UE type and at least partially based on the UE type. The transmission component 1104 can send the RAR to the UE. The receiving component 1102 can receive communications that are at least partially based on the RAR.

[0173] The number and arrangement of components shown in Figure 11 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented in a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Supplementally or alternatively, a group of components shown in Figure 11 (e.g., one or more components) may perform one or more functions described as being performed by another group of components shown in Figure 11.

[0174] The foregoing disclosure provides explanation and description, but is not exhaustive, nor does it limit these states to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or modifications and variations can be derived from the practice of these states.

[0175] The following provides an overview of some aspects of the case:

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

[0177] State 2: According to the method of State 1, wherein decoding the RAR based at least in part on the information includes: if the information indicates that the RAR will be decoded by the UE type of the UE, then the RAR is decoded.

[0178] State 3: The method according to State 2 also includes: sending communications at least in part based on the RAR.

[0179] State 4: According to any one of the states 1-3, if the information indicates that the RAR will not be decoded by the UE type of the UE, then the RAR will not be decoded.

[0180] State 5: According to the method of States 1-4, wherein the information is at least partially based on the Initial Bandwidth Part (BWP) configuration to distinguish between RAR for the first UE type and RAR for the second UE type.

[0181] State 6: According to the method of State 5, wherein the first UE type and the second UE type share the initial uplink BWP.

[0182] State 7: According to the method of State 5, wherein the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0183] State 8: According to the method of State 7, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

[0184] State 9: According to the method of State 7, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type do not overlap.

[0185] State 10: According to the method of State 7, wherein the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type.

[0186] State 11: According to the method of State 10, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap.

[0187] State 12: According to the method of State 10, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

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

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

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

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

[0192] State 17: The method according to any one of States 1-16, wherein the information includes a demodulation reference signal (DMRS) sequence, the DMRS sequence being at least partially based on a set of scrambling identifiers (IDs) applied to the DMRS sequence to distinguish between a RAR for a first UE type and a RAR for a second UE type.

[0193] State 18: According to the method of State 17, decoding the RAR at least in part based on the information includes: applying one or more of a first scrambling ID set or a 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; and decoding the RAR at least in part based on the result of the application.

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

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

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

[0197] State 22: The method according to any one of states 1-21, wherein the information includes precoding that distinguishes between RAR for a first UE type and RAR for a second UE type.

[0198] State 23: The method according to any one of states 1-22, wherein the information includes a quasi-colocation relationship for scheduling, which distinguishes between RAR for a first UE type and RAR for a second UE type.

[0199] State 24: The method according to any one of states 1-23, wherein the information includes reserved or spare bits in downlink control information indicating whether the RAR is for a first UE type or for a second UE type.

[0200] State 25: The method according to any one of States 1-24, wherein the information includes one or more entity random access channel (PRACH) formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

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

[0202] State 27: According to the method of State 26, the first UE type includes UEs whose distance from the cell center meets the distance threshold, and the second UE type includes UEs whose distance from the cell center does not meet the distance threshold.

[0203] State 28: The method according to any one of States 1-24, wherein before receiving the RAR: an initial bandwidth portion (BWP) configuration for random access is obtained, the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for the UE type of the UE; and a random access message is sent within the initial uplink BWP configured for the UE type of the UE.

[0204] State 29: According to the method of State 28, receiving the RAR includes: receiving the RAR within the initial downlink BWP configured for the UE type of the UE.

[0205] State 30: According to the method of state 28 or 29, wherein obtaining the configuration includes: receiving the configuration in the first initial downlink BWP.

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

[0207] Sample 32: A method of wireless communication performed by a base station includes: encoding a RAR for a user equipment (UE) using information that distinguishes a random access response (RAR) according to the UE type and at least in part based on the UE type of the user equipment (UE); and sending the RAR to the UE.

[0208] State 33: The method according to state 32 also includes: receiving communications at least in part based on the RAR.

[0209] Style 34: According to the method of style 32 or 33, wherein the information is at least partially based on the initial bandwidth portion (BWP) configuration to distinguish between the RAR for the first UE type and the RAR for the second UE type.

[0210] State 35: According to the method of State 34, wherein the first UE type and the second UE type share the initial uplink BWP.

[0211] State 36: According to the method of State 34, the initial uplink BWP for the first UE type is different from the initial uplink BWP for the second UE type.

[0212] State 37: According to the method of State 36, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type partially overlap.

[0213] State 38: According to the method of State 36, the initial uplink BWP for the first UE type and the initial uplink BWP for the second UE type do not overlap.

[0214] State 39: According to the method of State 36, the initial downlink BWP for the first UE type is different from the initial downlink BWP for the second UE type.

[0215] State 40: According to the method of State 39, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type partially overlap.

[0216] State 41: According to the method of State 39, the initial downlink BWP for the first UE type and the initial downlink BWP for the second UE type are non-overlapping.

[0217] State 42: The method according to any one of states 32-41, wherein encoding the RAR based at least in part on the information includes calculating a Radio Network Temporary Identifier (RNTI) based at least in part on one or more of the following: the index value of a first symbol of the physical random access channel (PRACH) timing of the RAR, the index of a first time slot of the PRACH timing in the system frame, and the index of the PRACH timing in the frequency domain, wherein the RNTI distinguishes between RARs for a first UE type and RARs for a second UE type; and using the RNTI to mask the cyclic redundancy check (CRC) of the RAR.

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

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

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

[0221] State 46: The method according to any one of states 32-45, wherein encoding the RAR based at least in part on the information includes: placing the control resource set (CORESET) of the RAR in a location that distinguishes between the RAR for the first UE type and the RAR for the second UE type.

[0222] State 47: The method according to any one of states 32-46, wherein the information includes precoding that distinguishes between RAR for a first UE type and RAR for a second UE type.

[0223] State 48: The method according to any one of states 32-47, wherein the information includes a quasi-colocation relationship for scheduling, which distinguishes between RAR for a first UE type and RAR for a second UE type.

[0224] State 49: The method according to any one of states 32-48, wherein the information includes reserved or spare bits in downlink control information indicating whether the RAR is for a first UE type or for a second UE type.

[0225] State 50: The method according to any one of states 32-49, wherein the information includes one or more entity random access channel (PRACH) formats associated with a first UE type or one or more PRACH formats associated with a second UE type.

[0226] State 51: The method according to any one of states 32-50, wherein the information includes a cyclic redundancy check (CRC) that distinguishes between a RAR for the first UE type and a RAR for the second UE type based at least in part on whether it is associated with a first set of entity random access channel (PRACH) preamble signals for the first UE type or with a second set of PRACH preamble signals for the second UE type.

[0227] State 52: According to the method of state 51, the first UE type includes UEs whose distance from the cell center meets the distance threshold, and the second UE type includes UEs whose distance from the cell center does not meet the distance threshold.

[0228] State 53: The method according to any one of states 32-52 also includes: before sending the RAR: sending an initial bandwidth portion (BWP) configuration for random access to the UE, the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for the UE type of the UE; and receiving random access messages within the initial uplink BWP configured for the UE type of the UE.

[0229] State 54: According to the method of State 53, sending the RAR includes: sending the RAR within the initial downlink BWP configured for the UE type of the UE.

[0230] State 55: According to the method of state 52 or 53, wherein sending the configuration includes: sending the configuration in the first initial downlink BWP.

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

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

[0233] Form 58: A device for wireless communication includes: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more of Forms 1-56.

[0234] Format 59: An apparatus for wireless communication, comprising: at least one unit for performing the method according to one or more of Formats 1-56.

[0235] Sample 60: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described in one or more of Samples 1-56.

[0236] Session 61: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of scenarios 1-56.

[0237] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. "Software" should be interpreted broadly as instructions, instruction sets, code, code fragments, code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, programs, and / or functions, regardless of whether they are referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented using hardware and / or a combination of hardware and software. It is apparent that the systems and / or methods described herein can be implemented using various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to these forms. Therefore, since the operation and performance of these systems and / or methods are described without reference to specific software code, it should be understood that software and hardware for implementing these systems and / or methods can be designed, at least in part, based on the description herein.

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

[0239] Although combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each variant. In fact, many of these features can be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. Although each dependent claim listed below may directly depend on a claim, the disclosure of each variant includes each dependent claim in combination with the other claims in each of the claim groups. As used herein, the phrase "at least one of" for a list item represents any combination of these items (including a single member). For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0240] No element, action, or instruction used in this case should be construed as essential or fundamental unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items) and may be used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “containing,” “having,” “including,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and / or" unless otherwise expressly stated (e.g., when used in conjunction with "any" or "only one of"). [Simplified Explanation of the Diagram]

[0016] To gain a detailed understanding of the features described above, this invention provides a more specific description of some embodiments, some of which are illustrated in the accompanying drawings. However, it should be noted that since the description of this invention allows for other equivalent and effective embodiments, these drawings merely illustrate certain typical embodiments of this invention and should not be considered as limiting the scope of protection of this invention. Identical element symbols in different drawings may identify the same or similar components.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the contents of this case.

[0018] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network, according to the contents of this case.

[0019] Figure 3 is a diagram showing the types of equipment according to the contents of this case.

[0020] Figure 4 illustrates an example of the configuration for a new Radio Capacity Reduction (RedCap) UE, based on the contents of this case.

[0021] Figure 5 is a diagram illustrating instances of distinguishing random access responses (RAR) based on the content of this case.

[0022] Figure 6 is a diagram illustrating an example of distinguishing overlapping and non-overlapping bandwidth portions of a RAR, according to the contents of this case.

[0023] Figure 7 is a diagram illustrating an example of encoding downlink control information to schedule RAR, according to the contents of this case.

[0024] Figure 8 is a diagram illustrating, for example, an exemplary process performed by a UE, according to the contents of this case.

[0025] Figure 9 is a diagram illustrating, for example, an exemplary process performed by a base station, according to the content of this case.

[0026] Figures 10-11 are diagrams of an example device for wireless communication according to the contents of this case. [Biomaterial Storage]

[0242] Domestic storage information (please note in order of storage institution, date, and number) None Foreign storage information (please note in order of storage country, institution, date, and number) None

Claims

1. A user equipment (UE) for wireless communication, comprising: One or more memory modules; and one or more processors coupled to the one or more memories, the one or more processors being individually or jointly configured to perform the following operations: receiving a Random Access Channel (RACH) configuration, the RACH configuration including information distinguishing a Random Access Response (RAR) based on UE type, the information distinguishing the RAR based on UE type indicating an initial bandwidth portion (BWP) configuration for receiving a RAR and a location of a control resource set (CORESET), the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE, the initial uplink BWP configured for the UE type being different from another initial uplink BWP configured for another UE type, the other initial uplink BWP configured for the other UE type being greater than a maximum uplink BWP supported by the UE, the information indicating a Cyclic Redundancy Check (CRC), the CRC being at least partially based on an RNTI masked by a modified radio network temporary identifier (RNTI), the modified The modified RNTI is at least partially based on association with a first entity random access channel (PRACH) resource configuration for a first UE type or a second PRACH resource configuration for a second UE type to distinguish between a RAR for the first UE type and a RAR for the second UE type. This information indicates a set of scrambling identifiers (IDs) for demodulation reference signals (DMRS) used for PDCCH transmissions, which are scheduled for both the RAR for the first UE type and the RAR for the second UE type. A first scrambling ID from a first subset of this set of scrambling IDs is applied to a DMRS scheduled for PDCCH transmissions of the RAR for the first UE type, and a second scrambling ID from a second subset of this set of scrambling IDs is applied to a DMRS scheduled for PDCCH transmissions of the RAR for the second UE type. One or more of the following conditions are met: The UE type of the UE corresponds to a UE that supports coverage enhancement, and the other UE type corresponds to a UE that does not support coverage enhancement; the UE type of the UE corresponds to a UE that supports small data transmission (SDT), and the other UE type corresponds to a UE that does not support SDT; or the UE type of the UE corresponds to a UE that supports radio access network (RAN) slicing, and the other UE type corresponds to a UE that does not support RAN slicing; receive the RAR; and decode the RAR at least in part based on information that distinguishes the RAR according to the UE type.

2. According to request item 1, the UE, wherein the one or more processors are configured to perform the following operation before receiving the RAR: send a random access message within the initial uplink BWP configured for the UE type of the UE.

3. According to request item 2, the one or more processors used to receive the RAR are configured to receive the RAR within the initial downlink BWP configured for the UE type of the UE.

4. According to Request Item 2, the one or more processors used to obtain the initial BWP configuration are configured to receive the initial BWP configuration in a first initial downlink BWP.

5. The UE according to request item 4, wherein the first initial downlink BWP is different from the initial downlink BWP configured for the UE type of the UE, and wherein the information is based at least in part on the initial BWP configuration to distinguish the RAR for the first UE type and the RAR for the second UE type.

6. According to the UE of request item 1, wherein the information is based at least in part on the initial BWP configuration to distinguish the RAR for the first UE type and the RAR for the second UE type.

7. According to request item 6, the UE type of the first UE type shares an initial uplink BWP with the UE type of the second UE type.

8. According to request item 6, the UE wherein an initial uplink BWP for the first UE type is different from an initial uplink BWP for the second UE type.

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

10. According to request item 8, 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 request item 8, wherein an initial downlink BWP for the first UE type is different from an initial downlink BWP for the second UE type.

12. The UE according to request item 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 UE according to request item 1, wherein the one or more processors for decoding the RAR at least in part based on the information are configured to perform the following operations: extract an RNTI from the CRC; calculate the modified RNTI at least in part based on one or more of the following: an index value of a first symbol of a PRACH timing of the RAR, an index of a first time slot of the PRACH timing in a system frame, and an index of the PRACH timing in a frequency domain; and decode the RAR if the RNTI extracted from the RNTI is in a set of RNTIs indicated by the modified RNTI.

14. The UE according to request item 13, wherein the CRC distinguishes the RAR for the first UE type and the RAR for the second UE type based at least in part on an interleaving mode applied to the CRC, and wherein the one or more processors for decoding the RAR at least in part based on the information are configured to: apply one or more of a first interleaving mode or a second interleaving mode to the CRC, wherein the first interleaving mode is associated with the first UE type and the second interleaving mode is associated with the second UE type; and decode the RAR at least in part based on a result of the application.

15. The UE according to request item 1, wherein the information includes downlink control information (DCI), the DCI being at least partially based on a set of scrambling identifiers (IDs) applied to the DCI to distinguish the RAR for the first UE type and the RAR for the second UE type.

16. The UE according to request item 15, wherein the one or more processors for decoding the RAR at least in part based on the information are configured to: apply one or more of a first scrambling ID set or a second scrambling ID set to the DCI, wherein the first scrambling ID set is associated with the first UE type and the second scrambling ID set is associated with the second UE type; and decode the RAR at least in part based on a result of the application.

17. The UE according to request item 1, wherein the CORESET distinguishes the RAR for the first UE type and the RAR for the second UE type based at least in part on the location of the CORESET.

18. The UE according to request item 1, wherein the information includes a precode that distinguishes the RAR used for the first UE type and the RAR used for the second UE type.

19. The UE according to request item 1, wherein the information includes one or more PRACH formats associated with the first UE type or one or more PRACH formats associated with the second UE type.

20. The UE according to request item 1, wherein the CRC distinguishes the RAR for the first UE type and the RAR for the second UE type based at least in part on an interleaving mode applied to the CRC, and wherein the one or more processors are configured to: apply a first interleaving mode or a second interleaving mode to the CRC, wherein the first interleaving mode indicates that the RAR is for the first UE type and the second interleaving mode indicates that the RAR is for the second UE type; and decode the RAR based at least in part on a result of the application.

21. A base station for wireless communication, comprising: One or more memory modules; and one or more processors coupled to the one or more memories, the one or more processors being individually or jointly configured to perform the following operations: Sending Random Access Channel (RACH) configuration information, the RACH configuration information including information distinguishing Random Access Responses (RARs) according to User Equipment (UE) type, the information distinguishing RARs according to UE type indicating an initial bandwidth portion (BWP) configuration for receiving a RAR and a location of a control resource set (CORESET), the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for a UE type of a UE, the initial uplink BWP configured for that UE type being different from another initial uplink BWP configured for another UE type, the other initial uplink BWP configured for the other UE type being greater than a maximum uplink BWP supported by the UE, the information indicating a Cyclic Redundancy Check (CRC), the CRC being at least partially based on an RNTI associated with a modified Radio Network Temporary Identifier (RNTI) that is masked. The modified RNTI, at least in part, is based on association with a first entity random access channel (PRACH) resource configuration for a first UE type or a second PRACH resource configuration for a second UE type to distinguish between a RAR for the first UE type and a RAR for the second UE type. The information indicates a set of scrambling identifiers (IDs) for demodulation reference signals (DMRS) used for PDCCH transmissions, which are scheduled for both the RAR for the first UE type and the RAR for the second UE type. A first scrambling ID from a first subset of the set of scrambling identifiers is applied to a DMRS scheduled for PDCCH transmissions of the RAR for the first UE type, and a second scrambling ID from a second subset of the set of scrambling IDs is applied to a DMRS scheduled for PDCCH transmissions of the RAR for the second UE type. One or more of the following conditions are met: The UE type of the UE corresponds to a UE that supports coverage enhancement, and the other UE type corresponds to a UE that does not support coverage enhancement; the UE type of the UE corresponds to a UE that supports small data transmission (SDT), and the other UE type corresponds to a UE that does not support SDT; or the UE type of the UE corresponds to a UE that supports radio access network (RAN) slicing, and the other UE type corresponds to a UE that does not support RAN slicing; using the information that distinguishes the RAR according to the UE type and at least in part based on the UE type of the UE, the RAR for the UE is encoded; and the RAR is sent to the UE.

22. The base station according to request item 21, wherein the information is based at least in part on the initial BWP configuration to distinguish the RAR for the first UE type and the RAR for the second UE type.

23. The base station according to request item 21, wherein the information includes downlink control information (DCI), the DCI being at least partially based on a set of scrambling identifiers (IDs) applied to the DCI to distinguish the RAR for the first UE type and the RAR for the second UE type.

24. The base station according to request item 21, wherein the one or more processors for encoding the RAR at least in part based on the information are configured to place the CORESET in the location for receiving the RAR, wherein the location distinguishes between the RAR for the first UE type and the RAR for the second UE type.

25. The base station according to request item 21, wherein the information includes one or more PRACH formats associated with the first UE type or one or more PRACH formats associated with the second UE type.

26. The base station according to request item 21, wherein the one or more processors are configured to: receive a random access message within the initial uplink BWP configured for the UE type of the UE before sending the RAR.

27. A wireless communication method performed by a user equipment (UE), comprising the steps of: receiving a random access channel (RACH) configuration, the RACH configuration including information for distinguishing random access responses (RARs) according to UE type, the information for distinguishing RARs according to UE type indicating an initial bandwidth portion (BWP) configuration for receiving a RAR and a location of a control resource set (CORESET), the initial BWP configuration indicating an initial downlink BWP and an initial uplink BWP configured for a UE type of the UE, the initial uplink BWP configured for the UE type being different from another initial uplink BWP configured for another UE type, the other initial uplink BWP configured for the other UE type being greater than a maximum uplink BWP supported by the UE, the information indicating a cyclic redundancy check (CRC), the CRC being at least partially based on an RNTI masked by a modified radio network temporary identifier (RNTI), the modified The modified RNTI is at least partially based on association with a first entity random access channel (PRACH) resource configuration for a first UE type or a second PRACH resource configuration for a second UE type to distinguish between a RAR for the first UE type and a RAR for the second UE type. This information indicates a set of scrambling identifiers (IDs) for demodulation reference signals (DMRS) used for PDCCH transmissions, which are scheduled for both the RAR for the first UE type and the RAR for the second UE type. A first scrambling ID from a first subset of this set of scrambling IDs is applied to a DMRS scheduled for PDCCH transmissions of the RAR for the first UE type, and a second scrambling ID from a second subset of this set of scrambling IDs is applied to a DMRS scheduled for PDCCH transmissions of the RAR for the second UE type. One or more of the following conditions are met: The UE type of the UE corresponds to a UE that supports coverage enhancement, and the other UE type corresponds to a UE that does not support coverage enhancement; the UE type of the UE corresponds to a UE that supports Small Data Transmission (SDT), and the other UE type corresponds to a UE that does not support SDT; or the UE type of the UE corresponds to a UE that supports Radio Access Network (RAN) slicing, and the other UE type corresponds to a UE that does not support RAN slicing; receive the RAR; and decode the RAR at least in part based on the information that distinguishes the RAR according to the UE type.

28. The method according to request item 27 further includes performing the following steps before receiving the RAR: sending a random access message within the initial uplink BWP configured for the UE type of the UE.

29. Receiving the RAR according to the method of request item 28 includes receiving the RAR within the initial downlink BWP configured for the UE type of the UE.

30. The method according to request item 28, wherein obtaining the configuration includes receiving the configuration in a first initial downlink BWP.

Images