Random access response type differentiation

Abstract

To provide a method for wireless communication.SOLUTION: In some aspects, user equipment may receive configuration information that indicates a transmission parameter associated with a random access response (RAR) type, transmit a random access message associated with the RAR type, use the transmission parameter to obtain a physical downlink control channel (PDCCH) communication that schedules a physical downlink shared channel (PDSCH) communication that includes a RAR in a medium access control protocol data unit of the PDSCH communication, and obtain PDSCH communication or refrain from obtaining the PDSCH communication based at least in part on whether the PDCCH communication is successfully obtained using the transmission parameter. Numerous other aspects are provided.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] Cross - Reference to Related Applications This patent application claims priority to U.S. Provisional Patent Application No. 62 / 923,277, filed on October 18, 2019, entitled "RANDOM ACCESS RESPONSE TYPE DIFFERENTIATION", and U.S. Non - Provisional Patent Application No. 17 / 069,584, filed on October 13, 2020, entitled "RANDOM ACCESS RESPONSE TYPE DIFFERENTIATION", which are hereby incorporated by reference in their entirety.

[0002] Aspects of the present disclosure generally relate to wireless communication, as well as techniques and apparatus for differentiating random access response types.

Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may utilize a multiple - access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple - access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD - SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE - Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP™).

[0004] A wireless communication network may include several base stations (BSs) that can support communication for several user equipments (UEs). The user equipment (UE) can communicate with the base station (BS) via the downlink and the uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, the BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0005] The above-mentioned multi-connection technology has been adopted in various telecommunications standards to provide a common protocol that enables various user equipments to communicate at the urban level, national level, regional level, and even world level. New Radio (NR), which may also be called 5G, is a set of extensions to the LTE mobile standard published by the 3rd Generation Partnership Project (3GPP (registered trademark)). NR is designed to better support mobile broadband Internet access by increasing spectral efficiency, reducing costs, improving services, utilizing new spectra, using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and / or SC-FDM (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM) for example) on the uplink (UL) to better harmonize with other open standards, and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, further improvements to LTE technology and NR technology are needed. Preferably, these improvements should be applicable to other multi-connection technologies and the telecommunications standards that utilize these technologies.

Summary of the Invention

Means for Solving the Problems

[0006] In some aspects, a method of wireless communication performed by a user equipment (UE) may include receiving configuration information indicating transmission parameters associated with a random access response (RAR) type, transmitting a random access message associated with the RAR type, using the transmission parameters to obtain physical downlink control channel (PDCCH) communication for scheduling physical downlink shared channel (PDSCH) communication including the RAR, and obtaining or refraining from obtaining the PDSCH communication based at least in part on whether the PDCCH communication is successfully obtained using the transmission parameters.

[0007] In some aspects, a method of wireless communication performed by a UE may include determining a system frame number (SFN) of a random access channel opportunity to be monitored by the UE, using the least significant bit (LSB) of the SFN to identify the RAR type of an RAR scheduled by PDCCH communication, and obtaining the PDCCH communication or performing early termination of reception of the PDCCH communication based at least in part on the RAR type.

[0008] In some aspects, a method of wireless communication performed by a base station may include transmitting configuration information indicating transmission parameters associated with an RAR type, receiving a random access message associated with the RAR type, and using the transmission parameters to transmit PDCCH communication for scheduling PDSCH communication including the RAR.

[0009] In some aspects, a method of wireless communication performed by a base station may include determining the SFN of a random access channel opportunity, using the LSB of the SFN to indicate the RAR type of an RAR scheduled by PDCCH communication, and transmitting the PDCCH communication.

[0010] In some aspects, a UE for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors are configured to receive configuration information indicating transmission parameters associated with an RAR type, transmit a random access message associated with the RAR type, use the transmission parameters to obtain PDCCH communication for scheduling PDSCH communication including the RAR, and obtain or refrain from obtaining the PDSCH communication based at least in part on whether the PDCCH communication is successfully obtained using the transmission parameters.

[0011] In some aspects, a UE for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors are configured to determine an SFN of a random access channel opportunity to be monitored by the UE, use the LSB of the SFN to identify an RAR type of an RAR scheduled by PDCCH communication, and obtain the PDCCH communication or perform early termination of reception of the PDCCH communication based at least in part on the RAR type.

[0012] In some aspects, a base station for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors are configured to transmit configuration information indicating transmission parameters associated with an RAR type, receive a random access message associated with the RAR type, and use the transmission parameters to transmit PDCCH communication for scheduling PDSCH communication including the RAR.

[0013] In some aspects, a base station for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to determine an SFN of a random access channel opportunity, use the LSB of the SFN to indicate the RAR type of an RAR scheduled by PDCCH communication, and transmit the PDCCH communication.

[0014] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to receive configuration information indicating transmission parameters associated with an RAR type, transmit a random access message associated with the RAR type, use the transmission parameters to obtain PDCCH communication for scheduling PDSCH communication including the RAR, and obtain or refrain from obtaining the PDSCH communication at least partially based on whether the PDCCH communication is successfully obtained using the transmission parameters.

[0015] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to determine an SFN of a random access channel opportunity to be monitored by the UE, use the LSB of the SFN to identify the RAR type of an RAR scheduled by PDCCH communication, and obtain the PDCCH communication or perform an early termination of reception of the PDCCH communication at least partially based on the RAR type.

[0016] In some aspects, the non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to transmit configuration information indicating transmission parameters associated with an RAR type, receive a random access message associated with the RAR type, and use the transmission parameters to transmit PDCCH communication for scheduling PDSCH communication including the RAR.

[0017] In some aspects, the non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to determine the SFN of a random access channel opportunity, use the LSB of the SFN to indicate the RAR type of an RAR scheduled by PDCCH communication, and transmit the PDCCH communication.

[0018] In some aspects, an apparatus for wireless communication may include means for receiving configuration information indicating transmission parameters associated with an RAR type, means for transmitting a random access message associated with the RAR type, means for using the transmission parameters to obtain PDCCH communication for scheduling PDSCH communication including the RAR, and means for obtaining or refraining from obtaining the PDSCH communication based at least in part on whether the PDCCH communication is successfully obtained using the transmission parameters.

[0019] In some aspects, an apparatus for wireless communication may include means for determining the SFN of a random access channel opportunity to be monitored by the apparatus, means for using the LSB of the SFN to identify the RAR type of an RAR scheduled by PDCCH communication, and means for obtaining the PDCCH communication or implementing early termination of reception of the PDCCH communication based at least in part on the RAR type.

[0020] In some aspects, an apparatus for wireless communication may include means for transmitting configuration information indicating transmission parameters associated with a RAR type, means for receiving a random access message associated with the RAR type, and means for using the transmission parameters to transmit PDCCH communication that schedules PDSCH communication including the RAR.

[0021] In some aspects, an apparatus for wireless communication may include means for determining the SFN of a random access channel opportunity, means for using the LSB of the SFN to indicate the RAR type of a RAR scheduled by PDCCH communication, and means for transmitting the PDCCH communication.

[0022] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as sufficiently described herein with reference to the accompanying drawings and the specification, and as shown by the accompanying drawings and the specification.

[0023] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the following Detailed Description of the Invention may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings. Each of the drawings is provided for purposes of illustration and description only, and not as a definition of the limits of the claims.

[0024] To better understand the above-described features of the present disclosure, a more detailed description may be provided for the content briefly summarized above by referring to the embodiments shown in part in the accompanying drawings. However, it should be noted that since this description may admit other equally effective embodiments, the accompanying drawings show only certain exemplary embodiments of the present disclosure and should not be regarded as limiting its scope. The same reference numbers in different drawings may identify the same or similar elements.

Brief Description of the Drawings

[0025]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

[0026] Various aspects of the present disclosure will be described in more detail below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to the specific structures or functions presented throughout the present disclosure. Rather, these aspects are configured so that the present disclosure is thorough and complete and conveys the scope of the present disclosure to those skilled in the art. Based on the teachings herein, the scope of the present disclosure is intended to include any aspect of the present disclosure disclosed herein, whether implemented independently of any other aspect of the present disclosure or in combination with any other aspect of the present disclosure. Those skilled in the art should understand that, for example, an apparatus may be implemented or a method may be practiced using some of the aspects described herein. In addition, the scope of the present disclosure includes apparatuses or methods practiced using other structures, functionality, or structures and functionality in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.

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

[0028] Although aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, it should be noted that aspects of the present disclosure may be applicable in other generation-based communication systems such as 5G and later, including NR technology.

[0029] FIG. 1 is a diagram illustrating a wireless network 100 in which aspects of the present disclosure may be practiced. The wireless network 100 may be any other wireless network such as an LTE network, or a 5G or NR network. The wireless network 100 may include several BSs 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A BS is an entity that communicates with user equipment (UE) and may be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP (registered trademark), the term "cell" can refer to the coverage area of a BS and / or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0030] A BS may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographical area (e.g., several kilometers in radius) and may enable unrestricted access by UEs subscribed to the service. A picocell may cover a relatively small geographical area and may enable unrestricted access by UEs subscribed to the service. A femtocell may cover a relatively small geographical area (e.g., a home) and may enable restricted access by UEs associated with the femtocell (e.g., UEs within a Closed Subscriber Group (CSG)). The BS for a macrocell may sometimes be called a macro BS. The BS for a picocell may sometimes be called a pico BS. The BS for a femtocell may sometimes be called a femto BS or a home BS. In the example shown in FIG. 1, BS110a may be a macro BS for macrocell 102a, BS110b may be a pico BS for picocell 102b, and BS110c may be a femto BS for femtocell 102c. A BS may 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 herein.

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

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

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

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

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

[0036] Some UEs may be regarded as machine type communication (MTC) UEs, or enhanced or extended machine type communication (eMTC) UEs. MTC UEs and eMTC UEs can communicate with, for example, a base station, another device (such as a remote device), or some other entity, including robots, drones, remote devices, sensors, meters, monitors, location tags, etc. A wireless node can provide connectivity for a network (such as a wide area network like the Internet or a cellular network) or connectivity to the network via, for example, a wired or wireless communication link. Some UEs may be regarded as Internet of Things (IoT) devices and / or may be implemented as narrowband Internet of Things (NB-IoT) devices. Some UEs may be regarded as customer premise equipment (CPE). UE120 may be included within a housing that stores components of UE120, such as processor components, memory components, etc.

[0037] Generally, any number of wireless networks can be deployed within a given geographical area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may sometimes be referred to as a wireless technology, air interface, etc. Frequencies may sometimes be referred to as carriers, frequency channels, etc. Each frequency may support a single RAT within a given geographical area to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network may be deployed.

[0038] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communicating 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 (which may include, for example, vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, and the like. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by base station 110.

[0039] As shown above, FIG. 1 is given as an example. Other examples may be different from those described with respect to FIG. 1.

[0040] FIG. 2 shows a block diagram of a design 200 of base station 110 and UE 120, which may be one of the base stations and one of the UEs in FIG. 1. Base station 110 may be equipped with T antennas 234a - 234t, and UE 120 may be equipped with R antennas 252a - 252r, where generally T ≧ 1 and R ≧ 1.

[0041] At base station 110, transmission processor 220 receives data for one or more UEs from data source 212, selects one or more modulation and coding schemes (MCSs) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, processes (e.g., encodes and modulates) the data for each UE based at least in part on the MCS selected for the UE, and may provide data symbols to all UEs. Transmission processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, higher layer signaling, etc.) and provide overhead symbols and control symbols. Transmission processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRSs)) as well as synchronization signals (e.g., primary synchronization signals (PSSs) and secondary synchronization signals (SSSs)). Transmission (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and provide T output symbol streams to T modulators (MODs) 232a - 232t. Each modulator 232 may process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a - 232t may be transmitted via T antennas 234a - 234t, respectively. According to various aspects described in more detail below, the synchronization signals may be generated using location coding to convey additional information.

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

[0043] On the uplink, at the UE 120, the transmission processor 264 may receive and process data from the data source 262 and control information (such as for reporting including RSRP, RSSI, RSRQ, CQI, etc.) from the controller / processor 280. The transmission processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmission processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the modulators 254a - 254r (such as for DFT - s - OFDM, CP - OFDM, etc.) and transmitted to the base station 110. At the base station 110, the uplink signals from the UE 120 and other UEs are received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the reception processor 238 to obtain the decoded data and control information sent by the UE 120. The reception processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 includes a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0044] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component of FIG. 2 may implement one or more techniques associated with distinguishing random access response types, as described in more detail elsewhere in this specification. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component of FIG. 2 may perform or direct the operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, process 1100 of FIG. 11, and / or other processes described herein. Memories 242 and 282 may store data and program code for the base station 110 and the UE 120, respectively. In some aspects, memory 242 and / or memory 282 may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, when executed by one or more processors of the base station 110 and / or the UE 120, the one or more instructions may perform or direct the operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, process 1100 of FIG. 11, and / or other processes described herein. Scheduler 246 may schedule the UE for data transmission on the downlink and / or uplink.

[0045] In some aspects, UE120 may include means for receiving configuration information indicating transmission parameters associated with a random access response (RAR) type, means for transmitting a random access message associated with the RAR type, means for using the transmission parameters to obtain physical downlink control channel (PDCCH) communications for scheduling physical downlink shared channel (PDSCH) communications including the RAR, means for obtaining or refraining from obtaining the PDSCH communications based at least in part on whether the PDCCH communications are successfully obtained using the transmission parameters, and the like. Additionally or alternatively, UE120 may include means for determining a system frame number (SFN) of a random access channel opportunity to be monitored by UE120, means for using the least significant bit (LSB) of the SFN to identify the RAR type of the RAR scheduled by the PDCCH communications, means for obtaining the PDCCH communications or performing early termination of reception of the PDCCH communications based at least in part on the RAR type, and the like. In some aspects, such means may include one or more components of UE120 described in connection with FIG. 2, such as controller / processor 280, transmission processor 264, TX MIMO processor 266, MOD254, antenna 252, DEMOD254, MIMO detector 256, reception processor 258, and the like.

[0046] In some aspects, the base station 110 may include means for transmitting configuration information indicating transmission parameters associated with the RAR type, means for receiving a random access message associated with the RAR type, means for using the transmission parameters to transmit PDCCH communication for scheduling PDSCH communication including the RAR, and the like. Additionally or alternatively, the base station 110 may include means for determining the SFN of the random access channel opportunity, means for using the LSB of the SFN to indicate the RAR type of the RAR scheduled by the PDCCH communication, means for transmitting the PDCCH communication, and the like. In some aspects, such means may include one or more components of the base station 110 described with respect to FIG. 2, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0047] As shown above, FIG. 2 is provided by way of example. Other examples may differ from those described with respect to FIG. 2.

[0048] FIG. 3 is a diagram illustrating an example 300 of a two-step random access channel (RACH) procedure. As shown in FIG. 3, the base station 110 and the UE 120 may communicate with each other to perform a two-step RACH procedure.

[0049] As indicated by reference numeral 305, one or more synchronization signal blocks (SSBs) and RACH configuration information may be transmitted by base station 110 and received by UE 120. In some aspects, the RACH configuration information is transmitted in and / or indicated by system information (such as in one or more system information blocks (SIBs)) and / or the SSB. Additionally or alternatively, the RACH configuration information may be transmitted in a radio resource control (RRC) message. The RACH configuration information may include one or more parameters to be used in the RACH procedure, such as one or more parameters for transmitting a random access message (RAM), one or more parameters for receiving a RAR, etc.

[0050] As indicated by reference numeral 310, UE 120 may transmit a RAM preamble. As indicated by reference numeral 315, UE 120 may transmit a RAM payload. As illustrated, UE 120 may transmit a RAM preamble and a RAM payload as part of the first step of a two-step RACH procedure. The RAM may be referred to as message A, msgA, or the first message in a two-step RACH procedure. The RAM preamble may be referred to as a message A preamble, msgA preamble, or preamble. The RAM payload may be referred to as a message A payload, msgA payload, or payload. The RAM may include some or all of the content of message 1 (msg1) and message 3 (msg3) in a four-step RACH procedure. For example, the RAM preamble may include some or all of the content of message 1 (such as a RACH preamble). The RAM payload may include some or all of the content of message 3 (such as a UE identifier, uplink control information, physical uplink shared channel (PUSCH) communication, etc.).

[0051] As indicated by reference numeral 320, the base station 110 may receive the RAM preamble transmitted by the UE 120. If the base station 110 successfully receives and decodes the RAM preamble, the base station 110 can receive and decode the RAM payload.

[0052] As indicated by reference numeral 325, the base station 110 may transmit a RAR (which may be referred to as a RAR message). As shown in the figure, the base station 110 may transmit a RAR message as part of the second step of the two-step RACH procedure. The RAR message may be referred to as message B, msgB, or the second message in the two-step RACH procedure. The RAR message may include some or all of the content of message 2 (msg2) and message 4 (msg4) in the four-step RACH procedure. For example, the RAR message may include a detected RACH preamble identifier, a detected UE identifier, a timing advance value, contention resolution information, etc.

[0053] As indicated by reference numeral 330, as part of the second step of the two-step RACH procedure, the base station 110 may transmit physical downlink control channel (PDCCH) communication for the RAR. The PDCCH communication may schedule physical downlink shared channel (PDSCH) communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication (e.g., in the downlink control information (DCI)).

[0054] As indicated by reference numeral 335, as part of the second step of the two-step RACH procedure, the base station 110 may transmit PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in the medium access control (MAC) protocol data unit (PDU) of the PDSCH communication. As indicated by reference numeral 340, if the UE 120 successfully receives the RAR, the UE 120 may transmit a hybrid automatic repeat request (HARQ) positive acknowledgment (ACK).

[0055] As shown above, FIG. 3 is given as an example. Other examples may be different from those described with respect to FIG. 3.

[0056] FIG. 4 is a diagram showing an example 400 of a 4-step RACH procedure. As shown in FIG. 4, the base station 110 and the UE 120 may communicate with each other to perform a 4-step RACH procedure.

[0057] As indicated by reference numeral 405, the base station 110 may transmit one or more SSBs and RACH configuration information, and the UE 120 may receive them. In some aspects, the RACH configuration information is transmitted in and / or indicated by system information (such as in one or more SIBs, etc.) and / or the SSB. Additionally or alternatively, the RACH configuration information may be transmitted in an RRC message. The RACH configuration information may include one or more parameters to be used in the RACH procedure, such as one or more parameters for transmitting the RAM, one or more parameters for receiving the RAR, etc.

[0058] As indicated by reference numeral 410, the UE 120 may transmit a random access message such as a random access (RA) preamble (sometimes called a RACH preamble, PRACH preamble, RAM preamble, etc.). A message including a random access preamble may be called message 1, msg1, MSG1, or the first message of the 4-step RACH procedure. The random access message may include a RACH preamble identifier.

[0059] As indicated by reference numeral 415, the base station 110 may transmit a random access response (RAR), such as a response to a preamble. A message including a preamble response may be referred to as message 2, msg2, MSG2, or the second message of the 4-step RACH procedure. In some aspects, the preamble response may indicate the detected RACH preamble identifier (e.g., received from UE 120 in MSG1). Additionally or alternatively, the preamble response may indicate the resource allocation to be used by UE 120 to transmit message 3 (msg3).

[0060] In some aspects, as part of the second step of the 4-step RACH procedure, the base station 110 may transmit PDCCH communication for the RAR. The PDCCH communication may schedule PDSCH communication including the RAR. For example, the PDCCH communication may indicate the resource allocation for the PDSCH communication. Also as part of the second step of the 4-step RACH procedure, the base station 110 may transmit PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in the MAC PDU of the PDSCH communication.

[0061] As indicated by reference numeral 420, UE 120 may transmit a radio resource control (RRC) connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or the third message of the 4-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information, PUSCH communication (e.g., the RRC connection request), etc.

[0062] As indicated by reference numeral 425, the base station 110 may transmit an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or the fourth message of the 4-step RACH procedure. In some embodiments, the RRC connection setup message may include a detected UE identifier, a timing advance value, contention resolution information, and the like. As indicated by reference numeral 430, if the UE 120 successfully receives the RRC connection setup message, the UE 120 may transmit a HARQ ACK.

[0063] RACH procedures, such as the 2-step RACH procedure of FIG. 3 and / or the 4-step RACH procedure of FIG. 4, may be triggered by various events and / or may be used in various scenarios. For example, the RACH procedure may be used for initial network access (e.g., from the RRC idle state), may be used for RRC connection re-establishment, may be used to indicate or obtain on-demand system information, may be used for beam failure recovery procedures, may be used for synchronization configuration, may be used for scheduling request failure, may be used for handover, and so on. These different RACH use cases may be associated with different priorities. In some cases, different random access modes, such as 2-step RACH or 4-step RACH, may be used. Further, different UEs 120 may have different capabilities for performing the RACH procedure.

[0064] As a result, there are various different RAR types (e.g., different types of RAR) that can be used in the RACH procedure, such as for different random access modes, different UE capabilities, different priorities, different lengths of the RAR window, etc. In some cases, different types of RAR can be transmitted simultaneously (e.g., using unicast or multicast transmission) in the same time resource (e.g., overlapping time resources or the same time resource), the same symbol, the same slot, the same subframe, the same radio frame, within the same RACH opportunity, etc. When UE120 shares a RACH opportunity with one or more other UEs120 (e.g., when multiple RARs are transmitted simultaneously), UE120 may need to decode multiple PDCCHs and / or multiple PDSCHs corresponding to the multiple RARs in order to obtain the RAR directed to UE120. This requires UE120 to perform excessive blind decoding, thereby consuming the resources of UE120 (e.g., memory resources, processing resources, battery power, etc.). This also increases latency due to the time required to decode each PDCCH and each PDSCH. Some of the techniques and apparatuses described herein enable UE120 to distinguish different RAR types without fully decoding all PDCCHs and / or all PDSCHs in the RACH opportunity. By doing so, the resources of UE120 are saved and latency is reduced.

[0065] As shown above, FIG. 4 is given as an example. Other examples may be different from those described with respect to FIG. 4.

[0066] FIG. 5 is a diagram showing an example 500 of distinguishing random access response types according to various aspects of the present disclosure. As shown in FIG. 5, UE120 and base station 110 may communicate with each other to perform a RACH procedure.

[0067] As indicated by reference numeral 505, the base station 110 may transmit RACH configuration information to the UE 120. The RACH configuration information may indicate transmission parameters associated with the RAR type. The transmission parameters may be associated with a transmission method for distinguishing different RAR types. In some aspects, the RACH configuration may indicate the transmission parameters and / or the transmission method. As an example, for a first transmission method (shown as Tx method 1), the RACH configuration information may indicate a first transmission parameter (shown as Tx parameter 1) corresponding to a first RAR type (shown as RAR type 1), a second transmission parameter (shown as Tx parameter 2) corresponding to a second RAR type (shown as RAR type 2), etc.

[0068] The transmission method may refer to a method used to distinguish different RAR types. In some cases, the transmission method may be referred to as an RAR type indication method, an RAR type discrimination method, etc. For example, a demodulation reference signal (DMRS)-based RAR type indication method may use different DMRS scrambling identifiers (or different sets of DMRS scrambling identifiers) to distinguish the RAR type. As another example, a radio network temporary identifier (RNTI)-based RAR type indication method may use different RNTIs (or different sets of RNTIs) to distinguish the RAR type. Different transmission parameters of the transmission method may indicate different RAR types. Other examples are given below.

[0069] Transmission parameters can be used to indicate the RAR type. In some aspects, the transmission parameters can refer to parameters used to prepare PDCCH communication for transmission and / or parameters used to recover the transmission of PDCCH communication transmitted using the transmission parameters. For example, the transmission parameters can include a DMRS scrambling identifier, an antenna port mapping identifier, a DCI scrambling identifier, a CRC mask, an interleaving pattern, a control resource set (CORESET) configuration, a search space configuration, spatial parameters, an RNTI, etc. Further details and examples are given below.

[0070] The RAR type can indicate, for example, the random access mode for the RACH procedure (e.g., 2-step RACH mode, 4-step RACH mode, etc.), the UE capabilities associated with the RACH procedure, the priority of the RACH procedure, the length of the RAR window associated with the RACH procedure, etc. Thus, different RAR types can be associated with different random access modes, different UE capabilities, different priorities, different lengths of the RAR window, etc. In some aspects, the UE capabilities for the RACH procedure can indicate the bandwidth supported by the UE120 (e.g., narrowband UE capabilities, wideband UE capabilities, one or more bandwidth parts supported by the UE120, etc.), the power class of the UE120, the layer of the UE120 (e.g., low layer, high layer, etc.), whether the UE120 supports specific requirements (e.g., low latency requirements, high reliability requirements, ultra-reliable low latency communication (URLLC) requirements, etc.), etc. In some aspects, the priority of the RACH procedure can indicate whether the RACH procedure is associated with time-constrained traffic (e.g., URLLC traffic), whether the RACH procedure is associated with best-effort traffic, the quality of service (QoS) requirements and / or parameters (or a set of parameters) for the RACH procedure, etc.

[0071] As indicated by reference numeral 510, the UE 120 may transmit a Random Access Message (RAM) to the base station 110. The RAM may include, for example, a RAM preamble and / or a RAM payload, as described above in connection with FIGS. 3 and 4. In a two-step RACH procedure, the RAM may be msgA. In a four-step RACH procedure, the RAM may be msg1. As shown, the RAM may be associated with a first RAR type, shown as RAR type 1. In some aspects, the UE 120 may determine the RAR type based at least in part on an event that triggers the RACH procedure, the priority of the RACH procedure, the UE capabilities, the random access mode of the RACH procedure (e.g., two-step RACH or four-step RACH), etc.

[0072] As indicated by reference numeral 515, the base station 110 may transmit a PDCCH communication (e.g., a first PDCCH communication) associated with a second RAR type. For example, the PDCCH communication may schedule a PDSCH communication (e.g., a first PDSCH communication) that includes a RAR having the second RAR type (e.g., msgB, msg2, etc.). When transmitting a PDCCH communication associated with the second RAR type, the base station 110 may transmit the PDCCH communication using a second set of transmission parameters (e.g., those indicated as being associated with the second RAR type in the RACH configuration information). As indicated by reference numeral 520, the base station 110 may transmit a PDSCH communication that includes a RAR having the second RAR type according to the scheduling information indicated in the PDCCH communication. The PDSCH communication may include the RAR in the MAC PDU (or MAC sub-PDU) of the PDSCH communication.

[0073] As indicated by reference number 525, the UE 120 may use a first transmission parameter to acquire (e.g., acquire, attempt to acquire, monitor, receive, decode, demodulate, descramble, etc.) PDCCH communication. In example 500, the UE 120 uses a first transmission parameter to acquire PDCCH communication because the UE 120 transmitted RAM for a first RAR type, which corresponds to the first transmission parameter according to the RACH configuration information. In this case, the UE 120 fails to acquire (e.g., fails to receive, decode, demodulate, descramble, etc.) the PDCCH communication because the PDCCH communication is transmitted using a second transmission parameter instead of the first transmission parameter. Due to the failure to successfully acquire the PDCCH communication, the UE 120 determines that the PDSCH communication scheduled by the PDCCH communication does not include a RAR having a first RAR type.

[0074] As indicated by reference number 530, due to the failure of the UE 120 to successfully acquire the PDCCH communication, the UE 120 may refrain from acquiring the PDSCH communication. In some aspects, when a transmission parameter is required to read the PDCCH communication (e.g., in the case of a scrambling identifier, etc.), the UE 120 may perform an early termination of the reception of the PDCCH communication.

[0075] As indicated by reference number 535, the base station 110 may transmit PDCCH communication associated with a first RAR type (e.g., a second PDCCH communication). For example, the PDCCH communication may schedule PDSCH communication (e.g., a second PDSCH communication) including a RAR having the first RAR type (e.g., msgB, msg2, etc.). When transmitting PDCCH communication associated with the first RAR type, the base station 110 may transmit the PDCCH communication using first transmission parameters (e.g., those indicated as being associated with the first RAR type in the RACH configuration information). As indicated by reference number 540, the base station 110 may transmit PDSCH communication including a RAR having the first RAR type according to the scheduling information indicated in the PDCCH communication. The PDSCH communication may include the RAR in the MAC PDU (or MAC sub-PDU) of the PDSCH communication.

[0076] In some aspects, the base station 110 may transmit a first PDSCH communication (having a RAR with a second RAR type) and a second PDSCH communication (having a RAR with the first RAR type) simultaneously (e.g., using unicast or multicast transmission). For example, the base station 110 may transmit the first PDSCH communication and the second PDSCH communication within the same time resource (e.g., overlapping time resources or the same time resource), the same symbol, the same slot, the same subframe, the same radio frame, the same RACH opportunity, etc.

[0077] As indicated by reference number 545, the UE 120 may use a first transmission parameter to obtain (e.g., obtain, attempt to obtain, monitor, receive, decode, demodulate, descramble, etc.) PDCCH communication. In example 500, the UE 120 uses a first transmission parameter to obtain PDCCH communication because the UE 120 has transmitted RAM for a first RAR type, which corresponds to the first transmission parameter according to the RACH configuration information. In this case, the UE 120 obtains (e.g., receives, decodes, demodulates, descrambles, etc.) PDCCH communication because the PDCCH communication is transmitted using the first transmission parameter. By successfully obtaining the PDCCH communication, the UE 120 determines that the PDSCH communication scheduled by the PDCCH communication includes a RAR having a first RAR type. As indicated by reference number 550, the UE 120 can obtain the PDSCH communication by successfully obtaining the PDCCH communication.

[0078] In some aspects, the transmission method is a DMRS-based RAR type indication method. The DMRS-based RAR type indication method may use different sets of (e.g., one or more) DMRS scrambling identifiers and / or different sets of (e.g., one or more) antenna port mapping identifiers to distinguish RAR types. In this case, the transmission parameter may include a DMRS scrambling identifier for PDCCH communication (e.g., a scrambling identifier for a DMRS sequence associated with the PDCCH communication) and / or a DMRS antenna port mapping identifier for PDCCH communication (e.g., an antenna port mapping identifier for a DMRS sequence associated with the PDCCH communication).

[0079] For the DMRS-based RAR type indication method, the RACH configuration information is a first set of DMRS scrambling identifiers for PDCCH communication that schedules a RAR having a first RAR type (e.g., C init,Xor a first set of DMRS antenna port mapping identifiers (e.g., P init,X ), a second set of DMRS scrambling identifiers for PDCCH communications scheduling a RAR having a second RAR type (e.g., C init,Y ) or a second set of DMRS antenna port mapping identifiers (e.g., P init,Y ), etc. may be indicated. The first set of DMRS scrambling identifiers and the second set of DMRS scrambling identifiers may be mutually exclusive (e.g., the sets may not overlap). Similarly, the first set of DMRS antenna port mapping identifiers and the second set of DMRS antenna port mapping identifiers may be mutually exclusive.

[0080] For a DMRS-based RAR type indication method, the UE 120 may attempt to obtain PDCCH communications by using a DMRS scrambling identifier to descramble a DMRS sequence associated with the PDCCH communications. Additionally or alternatively, the UE 120 may attempt to obtain PDCCH communications by using a DMRS antenna port mapping identifier to demap resource elements occupied by the DMRS sequence.

[0081] In some aspects, the transmission method is a DCI-based RAR type indication method. The DCI-based RAR type indication method may use different sets of DCI scrambling identifiers to distinguish RAR types. In this case, the transmission parameters may include a DCI scrambling identifier for PDCCH communications (e.g., a scrambling identifier for the DCI carried in the PDCCH communications). For a DCI-based RAR type indication method, the RACH configuration information is a first set of DCI scrambling identifiers for PDCCH communications scheduling a RAR having a first RAR type (e.g., D init,X ), a second set of DCI scrambling identifiers for PDCCH communications scheduling a RAR having a second RAR type (e.g., Dinit,Y ) etc. can be indicated. The first set of DCI scrambling identifiers and the second set of DCI scrambling identifiers may be mutually exclusive. For the DCI-based RAR type indication method, UE120 may attempt to obtain PDCCH communication by using a DCI scrambling identifier to descramble the DCI carried in the PDCCH communication.

[0082] In some aspects, the transmission method is a cyclic redundancy check (CRC)-based RAR type indication method. The CRC-based RAR type indication method may use different sets of CRC masks to distinguish RAR types. In this case, the transmission parameters may include a CRC mask for the DCI carried in the PDCCH communication. For the CRC-based RAR type indication method, the RACH configuration information includes a first set of CRC masks (e.g., M X ) for the PDCCH communication scheduling the RAR having the first RAR type (e.g., M Y ) etc. can be indicated. The first set of CRC masks and the second set of CRC masks may be mutually exclusive. For the CRC-based RAR type indication method, UE120 may attempt to obtain PDCCH communication by using a CRC mask to perform a cyclic redundancy check for the DCI carried in the PDCCH communication.

[0083] In some aspects, the transmission method is an interleaver-based RAR type indication method. The interleaver-based RAR type indication method can use different sets of interleaving patterns to distinguish RAR types. In this case, the transmission parameter may include the interleaving pattern associated with the DCI carried in the PDCCH communication. The interleaving pattern may be applied to the CRC of the DCI (e.g., to the CRC bits rather than the DCI payload bits), or may be applied to both the CRC and the DCI (e.g., to both the CRC and DCI payload bits). For the interleaver-based RAR type indication method, the RACH configuration information is the first set of interleaving patterns for the PDCCH communication scheduling the RAR having the first RAR type (e.g., I X ), the second set of interleaving patterns for the PDCCH communication scheduling the RAR having the second RAR type (e.g., I Y ), etc. The first set of interleaving patterns and the second set of interleaving patterns may be mutually exclusive. For the interleaver-based RAR type indication method, the UE 120 may attempt to obtain the PDCCH communication by using the interleaving pattern for performing the deinterleaving of the CRC of the DCI (e.g., the deinterleaving of the CRC bits rather than the DCI payload bits), or for performing the deinterleaving of both the CRC and the DCI (e.g., the deinterleaving of the CRC bits and the DCI payload bits).

[0084] In some aspects, the transmission method is a control resource set (CORESET)-based RAR type indication method. The CORESET-based RAR type indication method can use different CORESETs (or CORESET configurations) and / or different search spaces (SSs) (or SS configurations) to distinguish RAR types. In this case, the transmission parameters may include the CORESET configuration and / or SS configuration associated with PDCCH communication. For the CORESET-based RAR type indication method, the RACH configuration information can indicate the first CORESET configuration and / or the first SS configuration for PDCCH communication scheduling an RAR having a first RAR type, the second CORESET configuration and / or the second SS configuration for PDCCH communication scheduling an RAR having a second RAR type, and so on. The first CORESET configuration and / or SS configuration may be different from the second CORESET configuration and / or SS configuration. For the CORESET-based RAR type indication method, UE120 may attempt to obtain PDCCH communication by monitoring PDCCH communication in a CORESET (e.g., defined or configured according to the CORESET configuration) and / or an SS (e.g., defined or configured according to the SS configuration).

[0085] In some aspects, the transmission method is a spatial-based RAR type indication method. The spatial-based RAR type indication method may use different spatial parameters to distinguish RAR types. In this case, the transmission parameters may include the spatial parameters associated with PDCCH communication. The spatial parameters may include, for example, a precoder, a quasi-collocation (QCL) relationship, a transmission configuration indication (TCI) state, etc. associated with PDCCH communication. For the spatial-based RAR type indication method, the RACH configuration information may indicate a first spatial parameter for PDCCH communication scheduling an RAR having a first RAR type, a second spatial parameter for PDCCH communication scheduling an RAR having a second RAR type, and so on. The first spatial parameter may be different from the second spatial parameter. For the spatial-based RAR type indication method, the UE 120 may attempt to obtain PDCCH communication by monitoring PDCCH communication using spatial parameters (e.g., using a precoder, a QCL relationship, a TCI state, etc.).

[0086] In some aspects, the transmission method is an RNTI-based RAR type indication method. The RNTI-based RAR type indication method may use different RNTIs to distinguish RAR types. In this case, the transmission parameters may include RNTIs associated with PDCCH communication, such as a random access RNTI (RA-RNTI). For the RNTI-based RAR type indication method, the RACH configuration information may indicate a first RNTI for PDCCH communication scheduling an RAR having a first RAR type, a second RNTI for PDCCH communication scheduling an RAR having a second RAR type, and so on. The first RNTI may be different from the second RNTI. For the RNTI-based RAR type indication method, the UE 120 may attempt to obtain PDCCH communication by descrambling PDCCH communication using an RNTI.

[0087] In some aspects, the base station 110 may apply multiple transmission schemes and / or transmission parameters to enable the UE 120 to use PDCCH communication to distinguish different RAR types. For example, the base station 110 may apply one or more of a DMRS-based RAR type indication scheme, a DCI-based RAR type indication scheme, a CRC-based RAR type indication scheme, an interleaver-based RAR type indication scheme, a CORESET-based RAR type indication scheme, a spatial-based RAR type indication scheme, and / or an RNTI-based RAR type indication scheme. In some aspects, the set of transmission schemes used to enable RAR type differentiation is indicated in the RACH configuration information. Additionally or alternatively, the RACH configuration information may indicate a plurality of transmission parameters (e.g., of different transmission schemes) associated with a particular RAR type. The UE 120 may use these multiple transmission schemes and / or transmission parameters to attempt to obtain PDCCH communication and to determine whether the RAR type of the PDSCH communication scheduled by the PDCCH communication is the same as the RAR type associated with the random access message transmitted by the UE 120.

[0088] By enabling the UE 120 to distinguish different RAR types without fully decoding all PDCCH and / or all PDSCH in a RACH opportunity, some of the techniques and apparatuses described herein perform functions such as saving resources of the UE 120 and reducing latency.

[0089] As shown above, FIG. 5 is given as an example. Other examples may be different from those described with respect to FIG. 5.

[0090] FIG. 6 is a diagram illustrating an example 600 of differentiating random access response types according to various aspects of the present disclosure. FIG. 6 shows the process for DMRS and / or PDCCH transmission by the base station 110 and how the base station 110 may apply different transmission schemes (described above in relation to FIG. 5) to enable the UE 120 to differentiate between different RAR types.

[0091] As shown, the base station 110 may construct a DCI payload in block 605. In some aspects, the base station 110 may include information in the DCI to indicate the RAR type (and / or the LSB of the SFN, as will be described in more detail below in relation to FIG. 7). The base station 110 may then perform CRC addition in block 610. In some aspects, the base station 110 may apply an interleaving pattern to the CRC bits to indicate the RAR type. The base station 110 may then perform CRC masking in block 615. In some aspects, the base station 110 may apply a CRC mask indicating the RAR type. Additionally or alternatively, the base station 110 may scramble the CRC bits using an RNTI indicating the RAR type.

[0092] The base station 110 may then perform channel coding in block 620. In some embodiments, the base station 110 may apply an interleaving pattern to the coded bits (e.g., DCI bits with CRC bits added) to indicate the RAR type. The base station 110 may then perform PDCCH bit scrambling in block 625. In some embodiments, the base station 110 may use a DCI scrambling identifier to scramble the PDCCH bits (e.g., the coded bits) to indicate the RAR type. The base station 110 may then perform linear modulation in block 630, may apply an inverse fast Fourier transform (IFFT) in block 635, and may perform multiplexing (MUX) in block 640 using the DMRS generated in block 645. In some embodiments, the base station 110 may apply a DMRS scrambling identifier to the DMRS sequence of the DMRS to indicate the RAR type.

[0093] The base station 110 may then perform resource element (RE) mapping in block 650. In some embodiments, the base station 110 may map the REs to the CORESET and / or the SS to indicate the RAR type. The base station 110 may then perform precoding in block 655. In some embodiments, the base station 110 may apply a precoder and / or another spatial parameter to indicate the RAR type. The base station 110 may then transmit the PDCCH (and the accompanying DMRS).

[0094] By enabling the UE 120 to distinguish different RAR types without fully decoding all PDCCH and / or all PDSCH in a RACH opportunity, some of the techniques and apparatuses described herein perform functions such as saving resources of the UE 120 and reducing latency.

[0095] As shown above, FIG. 6 is given as an example. Other examples may be different from those described with respect to FIG. 6.

[0096] FIG. 7 is a diagram showing an example 700 of differentiating random access response types according to various aspects of the present disclosure. As shown in FIG. 7, the UE 120 and the base station 110 may communicate with each other to perform a RACH procedure.

[0097] As indicated by reference numeral 705, the base station 110 may transmit RACH configuration information to the UE 120 in the same manner as described elsewhere in this specification. As indicated by reference numeral 710, the UE 120 may transmit a RAM to the base station 110. The RAM may include, for example, a RAM preamble and / or a RAM payload as described above in connection with FIGS. 3 and 4. In a two-step RACH procedure, the RAM may be msgA. In a four-step RACH procedure, the RAM may be msg1. As shown, the RAM may be associated with a first RAR type indicated as RAR type 1. In some aspects, the UE 120 may determine the RAR type based at least in part on an event that triggers the RACH procedure, the priority of the RACH procedure, the UE capabilities, the random access mode of the RACH procedure (e.g., two-step RACH or four-step RACH), etc. In some aspects, the RAR type may be message B of a two-step RACH procedure (e.g., with an extended RAR window or a reduced RAR window).

[0098] As indicated by reference numeral 715, the UE 120 may determine the SFN of a RACH opportunity to be monitored by the UE. In some aspects, the UE 120 may determine the SFN based at least in part on the RACH configuration information, the resource or set of resources in which the UE 120 transmits the RAM, etc. As further shown, the UE 120 may determine the LSB of the SFN, sometimes referred to as the first LSB. In example 700, the LSB (first LSB) of the SFN determined by the UE 120 is zero (0).

[0099] As indicated by reference number 720, the base station 110 may transmit PDCCH communication (e.g., the first PDCCH communication) associated with the second RAR type. For example, the PDCCH communication may schedule PDSCH communication (e.g., the first PDSCH communication) including a RAR having the second RAR type (e.g., msgB, msg2, etc.). As shown in the figure, the base station 110 may transmit the PDCCH communication among SFNs having LSBs different from the LSB of the SFN determined by the UE 120. In Example 700, the LSB of the SFN in which the PDCCH communication is transmitted is 1. The LSB of the SFN in which the PDCCH communication is transmitted may be referred to as the second LSB.

[0100] As indicated by reference number 725, the base station 110 may transmit PDSCH communication including a RAR having the second RAR type according to the scheduling information indicated in the PDCCH communication. The PDSCH communication may include the RAR in the MAC PDU (or MAC sub-PDU) of the PDSCH communication.

[0101] As indicated by reference number 730, the UE 120 may use the first LSB to identify the RAR type of the RAR scheduled by the PDCCH communication. For example, the UE 120 may use the first LSB to determine whether the RAR type of the RAR scheduled by the PDCCH communication is the same as the RAR type associated with the RAM transmitted by the UE 120 (in Example 700, RAR type 1).

[0102] In some aspects, the UE 120 may generate a RNTI (e.g., RA-RNTI) at least partially based on the first LSB. The UE 120 may use the generated RNTI to descramble the PDCCH communication. In some aspects, the UE 120 may generate a RNTI (e.g., extended RA-RNTI or eRA-RNTI) using one of the following equations (1) or (2).

[0103]

Equation

[0104] In the above formula, s_id is the index of the first OFDM symbol of the specified PRACH (0 ≤ s_id < 14), t_id is the index of the first slot of the specified PRACH in the system frame (0 ≤ t_id < 80), f_id is the index of the specified PRACH in the frequency domain (0 ≤ f_id < 8), ul_carrier_id is the UL carrier used for transmitting the PRACH preamble (0 for the NUL carrier and 1 for the SUL carrier), and LSB_SFN is the LSB of the SFN in which the RACH opportunity occurs.

[0105] Additionally or alternatively, UE120 may compare the first LSB and the second LSB indicated by the base station 110. For example, the second LSB may be indicated in the DCI carried by the PDCCH (e.g., in one or more DCI fields, in unused fields, using one or more reserved bits). In some aspects, the PDCCH is a group common PDCCH (GC-PDCCH) having DCI format 1_0.

[0106] Additionally or alternatively, UE120 may compare the first LSB with a value indicated by a DMRS scrambling identifier associated with the PDCCH communication, a DCI scrambling identifier associated with the PDCCH communication, an interleaving pattern associated with the PDCCH communication, etc. In some aspects, the RACH configuration information may indicate the LSB value corresponding to the DMRS scrambling identifier (or a set of DMRS scrambling identifiers), the DCI scrambling identifier (or a set of DMRS scrambling identifiers), and / or the interleaving pattern (or a set of interleaving patterns). UE120 may compare the first LSB with the LSB value.

[0107] As indicated by reference numeral 735, the UE 120 may refrain from obtaining PDSCH communication and / or may perform early termination of PDCCH reception, at least partially based on the RAR type of the PDCCH communication. For example, the UE 120 may refrain from obtaining PDSCH communication and / or may perform early termination of PDCCH reception, at least partially based on whether the RAR type of the RAR scheduled by the PDCCH communication is the same as the RAR type associated with the RAM transmitted by the UE 120. For example, if the UE 120 fails to successfully descramble the PDCCH communication using an RNTI generated at least partially based on a first LSB, the UE 120 may refrain from obtaining PDSCH communication and / or may perform early termination of PDCCH reception. Additionally or alternatively, if the first LSB does not match a second LSB indicated in the DCI of the PDCCH communication, the UE 120 may refrain from obtaining PDSCH communication and / or may perform early termination of PDCCH reception. Additionally or alternatively, if the first LSB does not match an LSB value indicated by a DMRS scrambling identifier associated with the PDCCH communication, a DCI scrambling identifier associated with the PDCCH communication, an interleaving pattern associated with the PDCCH communication, etc., the UE 120 may refrain from obtaining PDSCH communication and / or may perform early termination of PDCCH reception.

[0108] As indicated by reference numeral 740, the base station 110 may transmit PDCCH communication (e.g., a second PDCCH communication) associated with a first RAR type. For example, the PDCCH communication may schedule PDSCH communication (e.g., a second PDSCH communication) including an RAR having a first RAR type (e.g., msgB, msg2, etc.). As illustrated, the base station 110 may transmit the PDCCH communication within an SFN having an LSB (a second LSB having a value of 1) that is the same as the LSB (a first LSB having a value of 1) of the SFN determined by the UE 120.

[0109] As indicated by reference numeral 745, the base station 110 may transmit PDSCH communication including a RAR having a first RAR type according to scheduling information indicated in PDCCH communication. The PDSCH communication may include the RAR in a MAC PDU (or MAC sub-PDU) of the PDSCH communication.

[0110] As indicated by reference numeral 750, the UE 120 may use the first LSB to identify the RAR type of the RAR scheduled by PDCCH communication in the same manner as described above. For example, the UE 120 may use the first LSB to determine whether the RAR type of the RAR scheduled by PDCCH communication is the same as the RAR type associated with the RAM transmitted by the UE 120 (in Example 700, RAR type 1).

[0111] As indicated by reference number 755, the UE 120 may acquire PDCCH communication and / or may acquire PDSCH communication, at least partially based on the RAR type of the PDCCH communication. For example, the UE 120 may acquire PDCCH communication and / or PDSCH communication, at least partially based on whether the RAR type of the RAR scheduled by the PDCCH communication is the same as the RAR type associated with the RAM transmitted by the UE 120. For example, if the UE 120 successfully descrambles the PDCCH communication using an RNTI generated at least partially based on a first LSB, the UE 120 may acquire the PDCCH communication and / or the PDSCH communication. Additionally or alternatively, if the first LSB matches a second LSB indicated in the DCI of the PDCCH communication, the UE 120 may acquire the PDCCH communication and / or the PDSCH communication. Additionally or alternatively, if the first LSB matches an LSB value indicated by a DMRS scrambling identifier associated with the PDCCH communication, a DCI scrambling identifier associated with the PDCCH communication, an interleaving pattern associated with the PDCCH communication, etc., the UE 120 may acquire the PDCCH communication and / or the PDSCH communication.

[0112] By enabling the UE 120 to distinguish different RAR types without fully decoding all PDCCH and / or all PDSCH in a RACH opportunity, some of the techniques and apparatuses described herein perform things such as saving resources of the UE 120, reducing latency, and preventing RACH collisions.

[0113] As shown above, FIG. 7 is given as an example. Other examples may be different from those described with respect to FIG. 7.

[0114] FIG. 8 is a diagram illustrating an exemplary process 800, for example, implemented by a UE, according to various aspects of the present disclosure. The exemplary process 800 is an example where a UE (e.g., UE 120, etc.) performs operations associated with differentiating random access response types.

[0115] As shown in FIG. 8, in some aspects, process 800 may include receiving configuration information indicating transmission parameters associated with an RAR type (block 810). For example, a UE (e.g., using receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may receive configuration information indicating transmission parameters associated with an RAR type as described above.

[0116] As further shown in FIG. 8, in some aspects, process 800 may include transmitting a random access message associated with an RAR type (block 820). For example, a UE (e.g., using receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may transmit a random access message associated with an RAR type as described above.

[0117] As further shown in FIG. 8, in some aspects, process 800 may include using transmission parameters to obtain PDCCH communication for scheduling PDSCH communication including an RAR (block 830). For example, a UE (e.g., using receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may use transmission parameters to obtain PDCCH communication for scheduling PDSCH communication including an RAR as described above.

[0118] As further shown in FIG. 8, in some aspects, process 800 may include obtaining or refraining from obtaining PDSCH communication (block 840) at least in part based on whether PDCCH communication is successfully obtained using transmission parameters. For example, a UE (using, e.g., receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may obtain or refrain from obtaining PDSCH communication at least in part based on whether PDCCH communication is successfully obtained using transmission parameters as described above.

[0119] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described with respect to one or more other processes described below and / or elsewhere in this specification.

[0120] In a first aspect, obtaining or refraining from obtaining PDSCH communication includes obtaining PDSCH communication if PDCCH communication is successfully received using transmission parameters, or refraining from obtaining PDSCH communication if PDCCH communication is not successfully received using transmission parameters.

[0121] In a second aspect, alone or in combination with the first aspect, different RAR types are associated with at least one of different random access modes, different UE capabilities, different priorities, different lengths of the RAR window, or combinations thereof.

[0122] In a third aspect, alone or in combination with one or more of the first and second aspects, the transmission parameters include a scrambling identifier or a unique antenna port mapping identifier for a demodulation reference signal (DMRS) sequence associated with PDCCH communication.

[0123] In a fourth aspect, using transmission parameters to obtain PDCCH communication, alone or in combination with one or more of the first to third aspects, includes using a scrambling identifier to descramble a DMRS sequence associated with the PDCCH communication, or using an antenna port mapping identifier to demap resource elements occupied by the DMRS sequence.

[0124] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the configuration information indicates a first set of DMRS scrambling identifiers or a first set of DMRS antenna port mapping identifiers for PDCCH communication that schedules an RAR having a first RAR type, and a second set of DMRS scrambling identifiers or a second set of DMRS antenna port mapping identifiers for PDCCH communication that schedules an RAR having a second RAR type.

[0125] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first set of DMRS scrambling identifiers and the second set of DMRS scrambling identifiers are mutually exclusive, or the first set of DMRS antenna port mapping identifiers and the second set of DMRS antenna port mapping identifiers are mutually exclusive.

[0126] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the transmission parameters include a scrambling identifier for downlink control information (DCI) carried in the PDCCH communication.

[0127] In an eighth aspect, using transmission parameters to obtain PDCCH communication, alone or in combination with one or more of the first to seventh aspects, includes using a scrambling identifier to descramble the DCI carried in the PDCCH communication.

[0128] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configuration information indicates a first set of DCI scrambling identifiers for PDCCH communication that schedules an RAR having a first RAR type, and a second set of DCI scrambling identifiers for PDCCH communication that schedules an RAR having a second RAR type.

[0129] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first set of DCI scrambling identifiers and the second set of DCI scrambling identifiers are mutually exclusive.

[0130] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the transmission parameters include a cyclic redundancy check (CRC) mask for DCI carried in PDCCH communication.

[0131] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, using the transmission parameters to obtain PDCCH communication includes using the CRC mask to perform a CRC for DCI carried in the PDCCH communication.

[0132] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the configuration information indicates a first set of CRC masks for DCI carried in PDCCH communication that schedules an RAR having a first RAR type, and a second set of CRC masks for DCI carried in PDCCH communication that schedules an RAR having a second RAR type.

[0133] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the first set of CRC masks and the second set of CRC masks are mutually exclusive.

[0134] In a 15th aspect, alone or in combination with one or more of the 1st to 14th aspects, the transmission parameter includes an interleaving pattern associated with DCI carried in PDCCH communication.

[0135] In a 16th aspect, alone or in combination with one or more of the 1st to 15th aspects, the interleaving pattern is applied to the CRC of the DCI or is applied to the CRC and the DCI.

[0136] In a 17th aspect, alone or in combination with one or more of the 1st to 16th aspects, using the transmission parameter to obtain PDCCH communication includes using the interleaving pattern to perform de-interleaving of the CRC of the DCI or the CRC and the DCI.

[0137] In an 18th aspect, alone or in combination with one or more of the 1st to 17th aspects, the configuration information indicates a first set of interleaving patterns for DCI carried in PDCCH communication that schedules a RAR having a first RAR type, and a second set of interleaving patterns for DCI carried in PDCCH communication that schedules a RAR having a second RAR type.

[0138] In a 19th aspect, alone or in combination with one or more of the 1st to 18th aspects, the first set of interleaving patterns and the second set of interleaving patterns are mutually exclusive.

[0139] In a 20th aspect, alone or in combination with one or more of the 1st to 19th aspects, the transmission parameter includes a control resource set (CORESET) configuration associated with the PDCCH communication, a search space (SS) configuration associated with the PDCCH communication, or a combination thereof.

[0140] In a 21st aspect, using transmission parameters to obtain PDCCH communication, either alone or in combination with one or more of the 1st to 20th aspects, includes monitoring at least one of a CORESET configured according to a CORESET configuration or an SS configured according to an SS configuration for PDCCH communication associated with an RAR type.

[0141] In a 22nd aspect, either alone or in combination with one or more of the 1st to 21st aspects, configuration information indicates a first CORESET configuration or a first search space configuration for PDCCH communication that schedules an RAR having a first RAR type and a second CORESET configuration or a second search space configuration for PDCCH communication that schedules an RAR having a second RAR type.

[0142] In a 23rd aspect, either alone or in combination with one or more of the 1st to 22nd aspects, transmission parameters include spatial parameters associated with PDCCH communication.

[0143] In a 24th aspect, either alone or in combination with one or more of the 1st to 23rd aspects, spatial parameters include at least one of a precoder, a quasi - co - location (QCL) relationship, a transmission configuration indicator (TCI) state, or a combination thereof.

[0144] In a 25th aspect, using transmission parameters to obtain PDCCH communication, either alone or in combination with one or more of the 1st to 24th aspects, includes monitoring PDCCH communication using spatial parameters.

[0145] In a 26th aspect, either alone or in combination with one or more of the 1st to 25th aspects, configuration information indicates a first spatial parameter for PDCCH communication that schedules an RAR having a first RAR type and a second spatial parameter for PDCCH communication that schedules an RAR having a second RAR type.

[0146] In the 27th aspect, alone or in combination with one or more of the 1st to 26th aspects, the transmission parameter is associated with a transmission scheme for distinguishing different RAR types.

[0147] In the 28th aspect, alone or in combination with one or more of the 1st to 27th aspects, the RAR is one of a plurality of RARs having different RAR types, which are simultaneously transmitted using different RAR type discrimination methods based on random access messages.

[0148] FIG. 8 shows exemplary blocks of process 800. In some aspects, however, process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks illustrated in FIG. 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0149] FIG. 9 is a diagram showing an exemplary process 900, such as may be performed by a UE, according to various aspects of the present disclosure. The exemplary process 900 is an example where a UE (e.g., UE 120, etc.) performs operations associated with distinguishing random access response types.

[0150] As shown in FIG. 9, in some aspects, process 900 may include determining (block 910) the SFN of a random access channel opportunity to be monitored by the UE. For example, a UE (using, e.g., receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may determine the SFN of a random access channel opportunity to be monitored by the UE as described above.

[0151] As further shown in FIG. 9, in some aspects, process 900 may include using the least significant bit (LSB) of the system frame number (SFN) to identify the RAR type of a RAR scheduled by PDCCH communication (block 920). For example, a user equipment (UE) (e.g., using receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may use the LSB of the SFN to identify the RAR type of a RAR scheduled by PDCCH communication as described above.

[0152] As further shown in FIG. 9, in some aspects, process 900 may include obtaining PDCCH communication or performing early termination of reception of PDCCH communication (block 930) based at least in part on the RAR type. For example, a UE (e.g., using receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) may obtain PDCCH communication or perform early termination of reception of PDCCH communication based at least in part on the RAR type as described above.

[0153] Process 900 may include additional aspects such as any single aspect or any combination of aspects described with respect to one or more other processes described below and / or elsewhere in this specification.

[0154] In a first aspect, the RAR type is Message B of a two-step RACH procedure.

[0155] In a second aspect, alone or in combination with the first aspect, using the LSB of the SFN to identify the RAR type includes descrambling PDCCH communication using a random access radio network temporary identifier generated at least in part based on the LSB of the SFN and identifying the RAR type based at least in part on whether the descrambling is successful.

[0156] In a third aspect, using the LSB of the SFN, alone or in combination with one or more of the first and second aspects, to identify the RAR type includes comparing the LSB of the SFN with a field included in the DCI of the PDCCH communication and identifying the RAR type based at least in part on the comparison.

[0157] In a fourth aspect, using the LSB of the SFN, alone or in combination with one or more of the first to third aspects, to identify the RAR type includes comparing the LSB of the SFN with a value indicated by at least one of a DMRS scrambling identifier used for PDCCH communication, a DCI scrambling identifier used for PDCCH communication, or an interleaving pattern used for PDCCH communication and identifying the RAR type based at least in part on the comparison.

[0158] FIG. 9 shows exemplary blocks of process 900, but in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks illustrated in FIG. 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0159] FIG. 10 is a diagram showing an exemplary process 1000 performed, for example, by a base station according to various aspects of the present disclosure. The exemplary process 1000 is an example in which a base station (e.g., base station 110, etc.) performs operations related to differentiating random access response types.

[0160] As shown in FIG. 10, in some aspects, process 1000 may include transmitting configuration information indicating transmission parameters associated with the RAR type (block 1010). For example, a base station (e.g., using transmission processor 220, reception processor 238, controller / processor 240, memory 242, etc.) may transmit configuration information indicating transmission parameters associated with the RAR type as described above.

[0161] As further shown in FIG. 10, in some aspects, process 1000 may include receiving a random access message associated with an RAR type (block 1020). For example, a base station (e.g., using a transmission processor 220, a reception processor 238, a controller / processor 240, a memory 242, etc.) may receive a random access message associated with an RAR type as described above.

[0162] As further shown in FIG. 10, in some aspects, process 1000 may include using transmission parameters to transmit PDCCH communications for scheduling PDSCH communications including an RAR (block 1030). For example, a base station (e.g., using a transmission processor 220, a reception processor 238, a controller / processor 240, a memory 242, etc.) may use transmission parameters to transmit PDCCH communications for scheduling PDSCH communications including an RAR as described above.

[0163] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described with respect to one or more other processes described below and / or elsewhere in this specification.

[0164] In a first aspect, different RAR types are associated with at least one of different random access modes, different UE capabilities, different priorities, different lengths of RAR windows, or combinations thereof.

[0165] In a second aspect, alone or in combination with the first aspect, the transmission parameters include a scrambling identifier or a unique antenna port mapping identifier for a DMRS sequence associated with the PDCCH communication.

[0166] In a third aspect, using transmission parameters to transmit PDCCH communication, either alone or in combination with one or more of the first and second aspects, includes using a scrambling identifier to scramble the DMRS sequence associated with the PDCCH communication, or using an antenna port mapping identifier to map the resource elements occupied by the DMRS sequence.

[0167] In a fourth aspect, the configuration information, either alone or in combination with one or more of the first to third aspects, indicates a first set of DMRS scrambling identifiers or a first set of DMRS antenna port mapping identifiers for PDCCH communication that schedules a RAR having a first RAR type, and a second set of DMRS scrambling identifiers or a second set of DMRS antenna port mapping identifiers for PDCCH communication that schedules a RAR having a second RAR type.

[0168] In a fifth aspect, the first set of DMRS scrambling identifiers and the second set of DMRS scrambling identifiers are mutually exclusive, or the first set of DMRS antenna port mapping identifiers and the second set of DMRS antenna port mapping identifiers are mutually exclusive, either alone or in combination with one or more of the first to fourth aspects.

[0169] In a sixth aspect, the transmission parameters, either alone or in combination with one or more of the first to fifth aspects, include a scrambling identifier for DCI carried in the PDCCH communication.

[0170] In a seventh aspect, using transmission parameters to transmit PDCCH communication, either alone or in combination with one or more of the first to sixth aspects, includes using a scrambling identifier to scramble the DCI carried in the PDCCH communication.

[0171] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration information indicates a first set of DCI scrambling identifiers for PDCCH communication scheduling an RAR having a first RAR type and a second set of DCI scrambling identifiers for PDCCH communication scheduling an RAR having a second RAR type.

[0172] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the first set of DCI scrambling identifiers and the second set of DCI scrambling identifiers are mutually exclusive.

[0173] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the transmission parameters include a CRC mask for DCI carried in PDCCH communication.

[0174] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, using the transmission parameters to transmit PDCCH communication includes using the CRC mask to perform CRC masking of the CRC for DCI carried in the PDCCH communication.

[0175] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the configuration information indicates a first set of CRC masks for DCI carried in PDCCH communication scheduling an RAR having a first RAR type and a second set of CRC masks for DCI carried in PDCCH communication scheduling an RAR having a second RAR type.

[0176] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the first set of CRC masks and the second set of CRC masks are mutually exclusive.

[0177] In a 14th aspect, alone or in combination with one or more of the 1st to 13th aspects, the transmission parameter includes an interleaving pattern associated with DCI carried in PDCCH communication.

[0178] In a 15th aspect, alone or in combination with one or more of the 1st to 14th aspects, the interleaving pattern is applied to the CRC of the DCI or is applied to the CRC and the DCI.

[0179] In a 16th aspect, alone or in combination with one or more of the 1st to 15th aspects, using the transmission parameter to transmit PDCCH communication includes using the interleaving pattern to perform interleaving of the CRC of the DCI or the CRC and the DCI.

[0180] In a 17th aspect, alone or in combination with one or more of the 1st to 16th aspects, the configuration information indicates a first set of interleaving patterns for DCI carried in PDCCH communication that schedules an RAR having a first RAR type and a second set of interleaving patterns for DCI carried in PDCCH communication that schedules an RAR having a second RAR type.

[0181] In an 18th aspect, alone or in combination with one or more of the 1st to 17th aspects, the first set of interleaving patterns and the second set of interleaving patterns are mutually exclusive.

[0182] In a 19th aspect, alone or in combination with one or more of the 1st to 18th aspects, the transmission parameter includes a control resource set (CORESET) configuration associated with the PDCCH communication, a search space (SS) configuration associated with the PDCCH communication, or a combination thereof.

[0183] In the 20th aspect, using transmission parameters to transmit PDCCH communication, either alone or in combination with one or more of the 1st to 19th aspects, includes transmitting PDCCH communication associated with an RAR type in at least one of a CORESET configured according to a CORESET configuration or an SS configured according to an SS configuration.

[0184] In the 21st aspect, the configuration information, either alone or in combination with one or more of the 1st to 20th aspects, indicates a first CORESET configuration or a first search space configuration for PDCCH communication that schedules an RAR having a first RAR type and a second CORESET configuration or a second search space configuration for PDCCH communication that schedules an RAR having a second RAR type.

[0185] In the 22nd aspect, the transmission parameters, either alone or in combination with one or more of the 1st to 21st aspects, include spatial parameters associated with PDCCH communication.

[0186] In the 23rd aspect, the spatial parameters, either alone or in combination with one or more of the 1st to 22nd aspects, include at least one of a precoder, a quasi - co - location (QCL) relationship, a transmission configuration indicator (TCI) state, or a combination thereof.

[0187] In the 24th aspect, using transmission parameters to transmit PDCCH communication, either alone or in combination with one or more of the 1st to 23rd aspects, includes transmitting PDCCH communication using the spatial parameters.

[0188] In the 25th aspect, the configuration information, either alone or in combination with one or more of the 1st to 24th aspects, indicates a first spatial parameter for PDCCH communication that schedules an RAR having a first RAR type and a second spatial parameter for PDCCH communication that schedules an RAR having a second RAR type.

[0189] In the 26th aspect, alone or in combination with one or more of the 1st to 25th aspects, the transmission parameter is associated with a transmission method for distinguishing different RAR types.

[0190] In the 27th aspect, alone or in combination with one or more of the 1st to 26th aspects, a plurality of RAR type discrimination methods are simultaneously used for RAR transmission based on a random access message.

[0191] FIG. 10 shows an exemplary block of process 1000. In some aspects, however, process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks illustrated in FIG. 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0192] FIG. 11 is a diagram showing an exemplary process 1100 performed, for example, by a base station according to various aspects of the present disclosure. The exemplary process 1100 is an example in which a base station (such as base station 110, etc.) performs operations associated with the discrimination of random access response types.

[0193] As shown in FIG. 11, in some aspects, process 1100 may include determining the SFN of a random access channel opportunity (block 1110). For example, a base station (using, for example, transmission processor 220, reception processor 238, controller / processor 240, memory 242, etc.) may determine the SFN of a random access channel opportunity as described above.

[0194] As further shown in FIG. 11, in some aspects, process 1100 may include using the LSB of the SFN (block 1120) to indicate the RAR type of the RAR scheduled by PDCCH communication. For example, a base station (using, e.g., transmission processor 220, reception processor 238, controller / processor 240, memory 242, etc.) may use the LSB of the SFN to indicate the RAR type of the RAR scheduled by PDCCH communication as described above.

[0195] As further shown in FIG. 11, in some aspects, process 1100 may include transmitting PDCCH communication (block 1130). For example, a base station (using, e.g., transmission processor 220, reception processor 238, controller / processor 240, memory 242, etc.) may transmit PDCCH communication as described above.

[0196] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described with respect to one or more other processes described below and / or elsewhere in this specification.

[0197] In a first aspect, the RAR type is Message B of a two-step RACH procedure.

[0198] In a second aspect, alone or in combination with the first aspect, using the LSB of the SFN to indicate the RAR type includes scrambling the PDCCH communication using a random access radio network temporary identifier generated at least in part based on the LSB of the SFN.

[0199] In a third aspect, alone or in combination with one or more of the first and second aspects, using the LSB of the SFN to indicate the RAR type includes including the LSB of the SFN in a field included in the DCI of the PDCCH communication.

[0200] In a fourth aspect, using the LSB of the SFN alone or in combination with one or more of the first to third aspects to indicate the RAR type includes indicating the value of the LSB of the SFN using at least one of a DMRS scrambling identifier used for PDCCH communication, a DCI scrambling identifier used for PDCCH communication, an interleaving pattern used for PDCCH communication, or a combination thereof.

[0201] FIG. 11 shows exemplary blocks of process 1100, but in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks illustrated in FIG. 11. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0202] The above disclosure provides examples and explanations and is not exhaustive or limiting to the exact forms disclosed. Modifications and variations may be made in light of the above disclosure or obtained from practice of the aspects.

[0203] As used herein, the term "component" is to be broadly construed as hardware, firmware, and / or a combination of hardware and software. A processor as used herein is implemented in hardware, firmware, and / or a combination of hardware and software.

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

[0205] The systems and / or methods described herein will be apparent to one skilled in the art that they may be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. It will be apparent that the actual specific control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Accordingly, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It should be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0206] Even if specific combinations of features are recited in the claims and / or disclosed herein, these combinations are not limiting of the various aspects disclosed. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. Each of the dependent claims listed below may depend directly on only one claim, but the various aspects disclosed include each dependent claim combined with any of the other claims in the claim set. The phrase referring to an enumeration of items "at least one of" refers to any combination of those items including a single member. By way of example, "at least one of a, b, or c" includes a, b, c, a - b, a - c, b - c, and a - b - c, as well as combinations having multiple of the same element (e.g., a - a, a - a - a, a - a - b, a - a - c, a - b - b, a - c - c, b - b, b - b - b, b - b - c, c - c, and c - c - c, or any other order of a, b, and c).

[0207] None of the elements, acts, or instructions used in this specification should be construed as important or essential unless explicitly described. Also, as used in this specification, the articles "a" and "an" include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the terms "set" and "group" include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with "one or more". If only one item is intended, the phrase "only one" or similar words are used. Also, as used in this specification, terms such as "has", "having", etc. shall be considered open-ended terms. Further, the phrase "based on" shall mean "at least partially based on" unless explicitly stated otherwise.

Description of Reference Numerals

[0208] 100 Wireless Network 102a Macrocell 102b Picocell 102c Femtocell 110 BS, Base Station 110a BS, Macro BS 110b BS 110c BS 110d BS, Relay Station 120 UE 120a UE 120b UE 120c UE 120d UE 120e UE 130 Network Controller 212 Data Source 220 Transmission Processor 230 Transmission (TX) Multiple-Input Multiple-Output (MIMO) Processor 232 Modulator (MOD), Demodulator 232a~232t Modulator (MOD) 234 Antenna 236 MIMO Detector 238 Receiver Processor 239 Data Sink 240 Controller / Processor 242 Memory 244 Communication Unit 246 Scheduler 252 Antenna 254 Demodulator (DEMOD), Modulator 254a~254r Demodulator (DEMOD) 256 MIMO Detector 258 Receiver Processor 260 Data Sink 262 Data Source 264 Transmitter Processor 266 TX MIMO Processor 280 Controller / Processor 282 Memory 290 Controller / Processor 292 Memory 294 Communication Unit

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: receiving configuration information indicating transmission parameters associated with a random access response (RAR) type; transmitting a random access message associated with the RAR type; using the transmission parameters to obtain physical downlink control channel (PDCCH) communication for scheduling physical downlink shared channel (PDSCH) communication including an RAR; obtaining or refraining from obtaining the PDSCH communication based at least in part on whether the PDCCH communication is successfully obtained using the transmission parameters. The method according to claim 1, further comprising:

2. The step of obtaining or refraining from obtaining the PDSCH communication includes obtaining the PDSCH communication if the PDCCH communication is successfully received using the transmission parameters, or refraining from obtaining the PDSCH communication if the PDCCH communication is not successfully received using the transmission parameters. The method according to claim 1.

3. The method according to claim 1, wherein different RAR types are associated with at least one of different random access modes, different UE capabilities, different priorities, different lengths of RAR windows, or combinations thereof.

4. The method according to claim 1, wherein the RAR is one of a plurality of RARs having different RAR types, and is transmitted simultaneously using different RAR type discrimination methods based on the random access message.

5. The method according to claim 1, wherein the transmission parameters include a cyclic redundancy check (CRC) mask for downlink control information (DCI) carried in the PDCCH communication.

6. The method according to claim 5, wherein the step of using the transmission parameters to obtain the PDCCH communication includes using the CRC mask to perform a CRC on the DCI carried in the PDCCH communication.

7. The method according to claim 1, wherein the configuration information indicates a first set of cyclic redundancy check (CRC) masks for downlink control information (DCI) carried in PDCCH communication scheduling a RAR having a first RAR type, and a second set of CRC masks for DCI carried in PDCCH communication scheduling a RAR having a second RAR type.

8. The method according to claim 7, wherein the first set of CRC masks and the second set of CRC masks are mutually exclusive.

9. The method according to claim 1, wherein the transmission parameters include a control resource set (CORESET) configuration associated with the PDCCH communication, a search space (SS) configuration associated with the PDCCH communication, or a combination thereof.

10. The method according to claim 9, wherein the step of using the transmission parameters to obtain the PDCCH communication includes monitoring at least one of a CORESET configured according to the CORESET configuration or an SS configured according to the SS configuration for the PDCCH communication associated with the RAR type.

11. The method according to claim 1, wherein the configuration information indicates a first control resource set (CORESET) configuration or a first search space configuration for PDCCH communication scheduling a RAR having a first RAR type, and a second CORESET configuration or a second search space configuration for PDCCH communication scheduling a RAR having a second RAR type.

12. The method according to claim 1, wherein the transmission parameters are associated with a transmission scheme for distinguishing different RAR types.

13. A method of wireless communication performed by a user equipment (UE), comprising: determining a system frame number (SFN) of a random access channel opportunity to be monitored by the UE; using the least significant bit (LSB) of the SFN to identify a RAR type of a random access response (RAR) scheduled by physical downlink control channel (PDCCH) communication; acquiring the PDCCH communication or performing early termination of reception of the PDCCH communication at least partially based on the RAR type and including the method.

14. The method according to claim 13, wherein the RAR type is Message B of a two-step RACH procedure.

15. The step of using the LSB of the SFN to identify the RAR type comprises: descrambling the PDCCH communication using a random access radio network temporary identifier generated at least partially based on the LSB of the SFN; and identifying the RAR type at least partially based on whether the descrambling is successful. The method according to claim 13.

16. The step of using the LSB of the SFN to identify the RAR type comprises: comparing the LSB of the SFN with a field included in downlink control information (DCI) of the PDCCH communication; and identifying the RAR type at least partially based on the comparison. The method according to claim 13.

17. A method of wireless communication performed by a base station, the method comprising: transmitting configuration information indicating transmission parameters associated with a random access response (RAR) type; receiving a random access message associated with the RAR type; and using the transmission parameters to transmit physical downlink control channel (PDCCH) communication for scheduling physical downlink shared channel (PDSCH) communication including the RAR. The method.

18. The method according to claim 17, wherein different RAR types are associated with at least one of different random access modes, different UE capabilities, different priorities, different lengths of the RAR window, or combinations thereof.

19. The method according to claim 17, wherein based on the random access message, a plurality of RAR type discrimination methods are simultaneously used for RAR transmission.

20. The method according to claim 17, wherein the transmission parameters include a cyclic redundancy check (CRC) mask for downlink control information (DCI) carried in the PDCCH communication.

21. The step of using the transmission parameters to transmit the PDCCH communication includes using the CRC mask to perform CRC masking of the CRC for the DCI carried in the PDCCH communication, according to the method of claim 20.

22. The method according to claim 17, wherein the configuration information indicates a first set of cyclic redundancy check (CRC) masks for downlink control information (DCI) carried in physical downlink control channel (PDCCH) communication scheduling a RAR having a first RAR type, and a second set of CRC masks for DCI carried in PDCCH communication scheduling a RAR having a second RAR type.

23. The method according to claim 22, wherein the first set of CRC masks and the second set of CRC masks are mutually exclusive.

24. The method according to claim 17, wherein the transmission parameters include a control resource set (CORESET) configuration associated with the PDCCH communication, a search space (SS) configuration associated with the PDCCH communication, or a combination thereof.

25. The method according to claim 24, wherein the step of using the transmission parameters to transmit the PDCCH communication includes transmitting the PDCCH communication associated with the RAR type in at least one of a CORESET configured according to the CORESET configuration or an SS configured according to the SS configuration.

26. The method according to claim 17, wherein the configuration information indicates a first CORESET configuration or a first search space configuration for PDCCH communication scheduling a RAR having a first RAR type, and a second CORESET configuration or a second search space configuration for PDCCH communication scheduling a RAR having a second RAR type.

27. The method according to claim 17, wherein the transmission parameters are associated with a transmission method for distinguishing different RAR types.

28. A method of wireless communication performed by a base station, comprising: determining a system frame number (SFN) of a random access channel opportunity; using the least significant bit (LSB) of the SFN to indicate a RAR type of a random access response (RAR) scheduled by physical downlink control channel (PDCCH) communication; transmitting the PDCCH communication.

29. The method according to claim 28, wherein the RAR type is message B of a two-step RACH procedure.

30. The step of using the LSB of the SFN to indicate the RAR type comprises: scrambling the PDCCH communication using a random access radio network temporary identifier generated at least partially based on the LSB of the SFN, or including the LSB of the SFN in a field included in the downlink control information (DCI) of the PDCCH communication The method according to claim 28, comprising at least one of the above.

Images