Supports cross-TAG scheduling and 2-step RACH payload transmission for PDCCH ordered contention-free random access procedure
By introducing a cross TAG scheduling mechanism into the DCI of PDCCH, the inefficiency problem of the orderly and uncontested random access process of PDCCH in wireless communication systems is solved, network throughput and reliability are improved, and it is suitable for carrier aggregation and dual connection scenarios.
Patent Information
- Application Number
- CN202080050581.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-07-15
- Filing Date
- 2020-07-16
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-07-16
AI Technical Summary
Existing wireless communication systems are used in the physical downlink control channel (PDCCH) to support cross-time advance group (TAG) scheduling and 2-step random access channel (RACH) payload transmission for orderly and non-contested random access processes. There is a problem of inefficiency, especially in carrier aggregation and dual connection scenarios, resulting in insufficient network throughput and reliability.
By introducing a cross TAG scheduling mechanism in DCI format 1_0 of PDCCH, the carrier of the first cell allows the timing advance group and related parameters of the second cell to ensure that the UE can send random access messages according to the indicated parameters, improving network efficiency and reliability sex.
It improves network throughput, reduces waiting time, improves system performance, is suitable for carrier aggregation and dual connection scenarios, and enhances system reliability and efficiency.
Smart Images

Figure CN114175831B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. patent application No. 62 / 875,768, filed on July 18, 2019, entitled “SUPPORTING CROSS-TAG SCHEDULING AND 2-STEP RACH PAYLOAD TRANSMISSION FOR APDCCH-ORDERED CONTENTION-FREE RANDOM ACCESS PROCEDURE,” and U.S. patent application No. 16 / 929,925, filed on July 15, 2020, entitled “SUPPORTING CROSS-TAG SCHEDULING AND 2-STEP RACH PAYLOAD TRANSMISSION FOR APDCCH-ORDERED CONTENTION-FREE RANDOM ACCESS PROCEDURE,” which are hereby expressly incorporated herein by reference. Technical Field
[0003] Aspects of the present disclosure generally relate to wireless communications and techniques and apparatus for supporting cross-timing advance group (TAG) scheduling and 2-step random access channel (RACH) payload transmission for a physical downlink control channel (PDCCH) ordered contention-free random access procedure. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies 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 standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless communication network may include multiple base stations (BS) that can support communications for multiple user equipment (UE). User equipment (UE) can communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, while an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a 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.
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global level. New Radio (NR) (also referred to as 5G) is an enhancement set of the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to use orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL) to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards, as well as support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation, and better support mobile broadband Internet access. However, as the demand for mobile broadband access continues to grow, there is a need to further improve LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention
[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) may include: receiving downlink control information for ordered contention-free random access to a physical downlink control channel via a first cell, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; and sending a random access message via the second cell based on the one or more parameters and a timing advance value determined at least in part based on the timing advance group of the second cell.
[0008] In some aspects, a method of wireless communication performed by a UE may include: receiving downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure; and sending a random access message for the two-step random access procedure based on the one or more parameters.
[0009] In some aspects, a UE for wireless communication may include: a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive downlink control information for ordered contention-free random access of a physical downlink control channel via a first cell, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; and send a random access message via the second cell according to the one or more parameters and a timing advance value determined at least in part based on the timing advance group of the second cell.
[0010] In some aspects, a UE for wireless communication may include: a memory and one or more processors coupled to the memory. The memory and the one or more processors are configured to: receive downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure; and send a random access message for the two-step random access procedure based on the one or more parameters.
[0011] 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 downlink control information for ordered contention-free random access of a physical downlink control channel via a first cell, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; and send a random access message via the second cell according to the one or more parameters and a timing advance value determined at least in part based on the timing advance group of the second cell.
[0012] 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 downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure; and send a random access message for the two-step random access procedure based on the one or more parameters.
[0013] In some aspects, an apparatus for wireless communication may include: a component for receiving downlink control information for ordered contention-free random access of a physical downlink control channel via a first cell, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by a UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; and a component for sending a random access message via the second cell based on the one or more parameters and a timing advance value determined at least in part based on the timing advance group of the second cell.
[0014] In some aspects, an apparatus for wireless communication may include: a component for receiving downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by the apparatus as part of a two-step random access procedure; and a component for sending a random access message for the two-step random access procedure based on the one or more parameters.
[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as generally described herein with reference to and illustrated by the figures and description.
[0016] The foregoing has outlined rather extensively the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for achieving the same purpose 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 methods of operation, together with the associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to be able to understand the above features of the present disclosure in detail, the above brief summary may be described in more detail by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and should not be considered as limiting the scope thereof, as the description may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0018] Figure 1 is a block diagram illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.
[0019] Figure 2 is a block diagram illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of the present disclosure.
[0020] Figure 3 is a diagram illustrating an example of a two-step random access channel (RACH) procedure using PDCCH ordered contention-free random access (CFRA).
[0021] Figure 4 is a diagram illustrating an example of a random access message including a random access message preamble and a random access message payload.
[0022] Figure 5 is a diagram illustrating an example of a four-step RACH procedure using PDCCH ordered CFRA.
[0023] Figure 6-8 is a diagram illustrating an example of supporting cross-timing advance group (TAG) scheduling and 2-step random access channel (RACH) payload transmission for a physical downlink control channel (PDCCH) ordered contention-free random access procedure in accordance with various aspects of the present disclosure.
[0024] Fig. 9 and 10 is a diagram illustrating example processing performed (eg, by a user device) according to various aspects of the present disclosure. DETAILED DESCRIPTION
[0025] The various aspects of the present disclosure will be described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms, and the present disclosure should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will become comprehensive and complete, and these aspects will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings of this article, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is realized independently of any other aspect of the present disclosure or realized in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to realize a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claim.
[0026] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, 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 application and the design constraints imposed on the overall system.
[0027] It should be noted that although various aspects may be described herein using terminology generally associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G and later generations, including NR technology.
[0028] Figure 1 1 is a diagram illustrating a wireless network 100 in which various aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include a plurality of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and it may also 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 specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of a BS and / or a BS subsystem serving this coverage area, depending on the context in which the term is used.
[0029] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). The BS of a macro cell may be referred to as a macro BS. The BS of a pico cell may be referred to as a pico BS. The BS of a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS of macro cell 102a, BS 110b may be a pico BS of pico cell 102b, and BS 110c may be a femto BS of femto cell 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.
[0030] In some aspects, the cells are not necessarily fixed, and the geographic area of the cells may move depending on 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 via various types of backhaul interfaces, such as direct physical connections, virtual networks, and / or similar interfaces using any suitable transport networks.
[0031] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and transmit transmissions of data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay station 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.
[0032] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).
[0033] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other (eg, directly or indirectly via a wireless or wired backhaul).
[0034] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smart book, an ultrabook, a medical device or equipment, a biosensor or device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, 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, a sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.
[0035] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include robots, drones, remote devices (such as sensors, meters, monitors, location tags), etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide connectivity for a network or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premise equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).
[0036] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, channel, etc. In a given geographic area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.
[0037] 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 (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0038] As mentioned above, Figure 1 Provided as an example. Other examples can be found in relation to Figure 1 The content described is different.
[0039] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown. BS 110 and UE 120 may be Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.
[0040] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the (multiple) MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (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 may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may also process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.
[0041] At UE 120, antennas 252a to 252r may receive downlink signals from BS 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may also process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The channel processor may determine 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 UE 120 may be included in a housing.
[0042] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide decoded data to a data sink 239 and decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and 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.
[0043] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other (multiple) components of the may perform one or more techniques associated with cross-timing advance group (TAG) scheduling and 2-step random access channel (RACH) payload transmission for a physical downlink control channel (PDCCH) ordered contention-free random access procedure, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component(s) may perform or direct e.g. Fig. 9 Processing 900, Fig.10 1000, and / or other processes described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120, the one or more instructions may perform or direct, for example, Fig. 9 Processing 900, Fig.10 The scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.
[0044] In some aspects, the UE 120 may include components for receiving downlink control information for ordered contention-free random access of a physical downlink control channel via a first cell, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; components for sending a random access message via the second cell based on the one or more parameters and a timing advance value determined at least in part based on the timing advance group of the second cell; and the like. Additionally, or alternatively, the UE 120 may include components for receiving downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure; components for sending a random access message for a two-step random access procedure based on the one or more parameters; and the like. In some aspects, such components may include in combination Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.
[0045] As mentioned above, Figure 2 Provided as an example. Other examples can be found in relation to Figure 2 The content described is different.
[0046] Figure 3 is a diagram illustrating an example 300 of a two-step random access channel (RACH) procedure using a physical downlink control channel (PDCCH) ordered contention-free random access (CFRA). Figure 3 As shown, base station 110 and UE 120 may communicate with each other to perform a two-step RACH procedure.
[0047] As shown in reference numeral 305, the base station 110 may send and the UE 120 may receive downlink control information (DCI) for a PDCCH ordered CFRA (sometimes referred to as a PDCCH order). In some aspects, the base station 110 may trigger the PDCCH ordered CFRA to synchronize the transmission timing of the UE 120 that has lost synchronization (e.g., desynchronized). For example, the base station 110 may trigger the PDCCH ordered CFRA when the time alignment timer expires due to a lack of transmission of uplink data or downlink data between the base station 110 and the UE 120. The base station 110 may send a PDCCH order (e.g., a DCI for a PDCCH ordered CFRA) to the UE 120 based at least in part on triggering the PDCCH ordered CFRA. The DCI for the PDCCH ordered CFRA in the new radio (NR) may have a DCI format 1_0. The DCI may indicate one or more parameters for performing a random access procedure, such as a random access preamble to be sent by the UE 120.
[0048] As shown in reference numeral 310, UE 120 may send a random access (RA) preamble. As shown in reference numeral 315, UE 120 may send a random access payload. As shown, as part of the first step of a two-step RACH process, UE 120 may send a random access preamble and a random access payload. A random access message (e.g., including a random access preamble and a random access payload) is sometimes referred to as message A, msgA, or the first message in a two-step RACH process. A random access preamble is sometimes referred to as a message A preamble, msgA preamble, or preamble. A random access payload is sometimes referred to as a message A payload, msgA payload, or payload. A random access message may include some or all of the contents of message 1 (msg1) and message 3 (msg3) of a four-step RACH process. For example, a random access preamble may include some or all of the contents of message 1 (such as a RACH preamble). For PDCCH ordered CFRA, UE 120 may use a random access preamble indicated by a DCI for PDCCH ordered CFRA (e.g., with DCI format 1_0). The random access payload may include some or all of the contents of message 3 (such as a UE identifier, uplink control information, physical uplink shared channel (PUSCH) communications, etc.). Additionally, or alternatively, the random access payload may include a channel state information (CSI) report, a position measurement, a buffer status report (BSR), a power headroom (PHR) report, beam failure recovery (BFR) information, etc.
[0049] As shown in reference numeral 320, the base station 110 may receive a random access preamble sent by the UE 120. If the base station 110 successfully receives and decodes the random access preamble, the base station 110 may receive and decode the random access payload. As shown in reference numeral 325, the base station 110 may send a random access response (sometimes referred to as a random access response message). As shown, the base station 110 may send a random access response as part of the second step of the two-step RACH process. The random access response is sometimes referred to as message B, msgB, or the second message in the two-step RACH process. The random access response may include some or all of the contents of message 2 (msg2) and message 4 (msg4) of the four-step RACH process. For example, the random access response may include a detected RACH preamble identifier, a detected UE identifier, a timing advance value, contention resolution information, etc.
[0050] As mentioned above, Figure 3 Provided as an example. Other examples can be found in relation to Figure 3 The content described is different.
[0051] Figure 44 is a diagram illustrating an example of a random access message including a random access message preamble and a random access message payload. As shown, a random access message sent by a UE 120 as part of a two-step RACH procedure may include a random access (RA) preamble and a random access payload, as described above. The random access preamble may include a physical random access channel (PRACH) preamble signal and may use a guard time (shown as GT, with T G The random access payload may include a demodulation reference signal (DMRS) and / or a physical uplink shared channel (PUSCH) communication, and a guard time (also shown as GT, with T G As further shown, the transmission of the random access preamble and the transmission of the random access payload can be separated from other signals by a transmission protection time (shown as TxG, with T G duration) to separate them in time.
[0052] As further shown, the random access preamble may be sent in a RACH opportunity (RO), which may correspond to a synchronization signal block (SSB) in contention-based random access (CBRA). As also shown, the random access payload may be sent in a PUSCH resource unit (PRU) group, which may correspond to an SSB in a CBRA. In a CBRA, the UE 120 may determine resources (e.g., RO and / or PRU groups) for sending a random access message based at least in part on the SSB. For example, the SSB index of the best SSB measured by the UE 120 may correspond to a set of uplink resources for sending a random access message in a CBRA. For CBRA, the UE 120 may randomly select a preamble (e.g., a sequence) for sending in a random access preamble. By associating RACH resources with SSBs, the signaling overhead that would otherwise be used to indicate RACH resources may be reduced.
[0053] In CFRA, the 2-step RACH process is DCI-based rather than SSB-based. In this case, in order to support CFRA, the DCI for PDCCH ordered CFRA indicates the preamble (e.g., sequence) to be sent by UE 120 in the random access preamble. However, DCI format 1_0 for PDCCH ordered CFRA can be mainly used to provide control information for downlink transmission, such as physical downlink shared channel (PDSCH) transmission, RA response transmission (e.g., msgB, msg2, msg4, etc.), system information (e.g., one or more system information blocks (SIBs)), etc. Therefore, the DCI for PDCCH ordered RACH may not include sufficient information for UE 120 to send a random access message. For example, DCI format 1_0 may not include resource allocations and / or other parameters for random access messages to be sent by UE 120 for sending random access messages (e.g., random access preambles and / or random access payloads). Some techniques and devices described herein enable PDCCH ordered CFRA.
[0054] In addition, in some scenarios, such as dual connectivity and / or carrier aggregation, different cells or uplink carriers may be configured in different timing advance groups (TAGs). For example, a first uplink carrier and a second uplink carrier may have different propagation delays between a user equipment 120 and a corresponding base station 110 that may not be co-located. For example, a first service cell of a first uplink carrier may be provided by a first base station 110 (e.g., a first TRP, a first antenna array of the base station 110, etc.), and a second service cell of a second uplink carrier may be provided by a second base station 110 that is not co-located with the first base station 110 (e.g., a second TRP, a second antenna array of the base station 110, etc.), resulting in different propagation delays for uplink transmissions to reach the corresponding base station 110 on different uplink carriers. Therefore, the first uplink carrier and the second uplink carrier may have different timing advance values for uplink transmissions and may belong to different timing advance groups. A timing advance group may refer to a set of uplink carriers having the same (or similar within a threshold) timing advance values. UE 120 may use the timing advance value of the uplink carrier to transmit uplink communications on the uplink carrier at a timing that results in synchronization with the transmission time interval of base station 110 to reduce inter-TTI interference.
[0055] In some cases (e.g., in dual connectivity and / or carrier aggregation), cross-carrier scheduling may be supported, where a first carrier (e.g., on a first cell) carries control information to schedule communications on a second carrier (e.g., on a second cell). When the first carrier and the second carrier belong to different TAGs, such cross-carrier scheduling may be referred to as cross-TAG scheduling. For cross-TAG scheduling, it may be necessary to indicate the TAG of a second carrier (e.g., a secondary TAG or sTAG) scheduled by a first carrier (which is included in a primary TAG or pTAG) via the first carrier. However, DCI format 1_0 for PDCCH ordered RACH may not include such information. Some techniques and apparatus described herein enable cross-TAG scheduling for PDCCH ordered CFRA.
[0056] As mentioned above, Figure 4 Provided as an example. Other examples can be found in relation to Figure 4 The content described is different.
[0057] Figure 5 5 is a diagram illustrating an example 500 of a four-step RACH procedure using PDCCH ordered CFRA. Figure 5 As shown, base station 110 and UE 120 may communicate with each other to perform a four-step RACH procedure.
[0058] As indicated by reference numeral 505, base station 110 may send and UE 120 may receive DCI for PDCCH ordered CFRA (sometimes referred to as PDCCH order). Figure 3 As described, the base station 110 may trigger a PDCCH ordered CFRA to synchronize the transmission timing of the UE 120 that has lost synchronization (e.g., desynchronized). The DCI for the PDCCH ordered CFRA in the NR may have a DCI format 1_0. The DCI may indicate one or more parameters for performing a random access procedure, such as a random access preamble to be sent by the UE 120.
[0059] As indicated by reference numeral 510, UE 120 may send a random access (RA) preamble (sometimes referred to as a RACH preamble, a PRACH preamble, etc.). The message including the random access preamble may be referred to as message 1, msg1, MSG1, or the first message of a four-step RACH procedure. For PDCCH ordered CFRA, UE 120 may use a random access preamble indicated by a DCI for PDCCH ordered CFRA (e.g., having DCI format 1_0).
[0060] As indicated by reference numeral 515, the base station 110 may send a reply to the preamble. The message including the preamble reply may be referred to as message 2, msg2, MSG2, or the second message of the four-step RACH procedure. In some aspects, the preamble reply may indicate a detected RACH preamble identifier (e.g., received from the UE 120 in MSG1). Additionally, or alternatively, the preamble reply may indicate a resource allocation to be used by the UE 120 to send message 3 (msg3).
[0061] As indicated by reference numeral 520, UE 120 may send 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 four-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information, PUSCH communication (e.g., RRC connection request), etc.
[0062] As indicated by reference numeral 525, base station 110 may send an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or a fourth message of a four-step RACH procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, and the like.
[0063] As described above, NR may not support cross-TAG scheduling in PDCCH ordered CFRA because DCI format 1_0 of PDCCH ordered RACH may not include information that allows UE 120 to determine the sTAG of the carrier being scheduled. Some techniques and apparatus described herein enable cross-TAG scheduling for PDCCH ordered CFRA (e.g., for two-step RACH and four-step RACH) in NR.
[0064] As mentioned above, Figure 5 Provided as an example. Other examples can be found in relation to Figure 5 The content described is different.
[0065] Figure 6 is a diagram illustrating an example 600 supporting cross-TAG scheduling and 2-step RACH payload transmission for a PDCCH ordered CFRA procedure in accordance with various aspects of the present disclosure.
[0066] like Figure 6As shown, UE 120 can communicate with base station 110 using a first cell (shown as cell 1) included in a first TAG (shown as TAG 1). The first cell may be a primary cell (PCell), and the first TAG may be a pTAG. The first cell may schedule communication for a second cell (shown as cell 2) included in a second TAG (shown as TAG 2) different from the first TAG. Therefore, the first cell and the second cell may belong to different TAGs. The second cell may be a secondary cell (SCell), and the second TAG may be an sTAG. The first cell and the second cell may be provided by the same base station 110 or by different base stations 110.
[0067] In some aspects, the sTAG of the second cell is not configured with a scheduling cell (e.g., a scheduling SCell). In some aspects, all other sTAGs associated with the UE 120, except for the second cell, are configured with a scheduling cell (e.g., according to an RRC configuration). In this case, a single DCI may be used to support cross-TAG scheduling for the sTAG of the second cell (e.g., using a set of reserved bits included in a DCI with format 1_0 for PDCCH ordered CFRA). Due to size limitations of the DCI (e.g., limitations on the number of bits included in the DCI), if multiple sTAGs are not configured with scheduling cells (e.g., scheduling SCells), then a single DCI may not have enough available bits to support cross-TAG scheduling for multiple sTAGs. Figure 6 The details of cross-TAG scheduling for a single sTAG are shown below. Figure 7 Details of cross-TAG scheduling for multiple sTAGs are shown.
[0068] As shown in reference numeral 605, the base station 110 may send a DCI for a PDCCH ordered CFRA to the UE 120 and via the first cell. In some aspects, the DCI has a DCI format 1_0. In some aspects, the DCI may support cross-TAG scheduling. For example, the DCI may indicate a TAG of the second cell (e.g., an sTAG of the SCell). Additionally, or alternatively, the DCI may include one or more parameters associated with a random access message to be sent by the UE 120 via the second cell. For example, the one or more parameters may be related to a random access payload to be sent by the UE 120 (e.g., may include one or more payload parameters that instruct the UE 120 how to generate and / or send a RA payload).
[0069] As described above, the DCI may indicate the TAG of the second cell. For example, the DCI may indicate the TAG of the second cell in a field that explicitly identifies the TAG (e.g., using a TAG ID). In this case, the UE 120 may use a default SCell configuration for the identified TAG, such as the default SCell configuration indicated in the RRC message. Additionally, or alternatively, the DCI may indicate the TAG using a carrier indicator field (CIF), which indicates an index of an uplink carrier included in the TAG. In this case, the SCell configuration of the indicated uplink carrier may be the same as the default SCell configuration indicated in the RRC message, or may be different from the SCell configuration indicated in the RRC message. In some aspects, the SCell configuration of the indicated uplink carrier may override the default SCell configuration indicated in the RRC message.
[0070] In some aspects, a field indicating a TAG (e.g., a TAG ID field or CIF) may have a configurable bit width (e.g., 0 bits, 1 bit, 2 bits, etc.). For example, the bit width of the field may depend on the number of TAGs configured for the UE 120. The bit width may refer to the number of bits included in the field. In some aspects, the bit width of the field may be indicated (e.g., explicitly) or inferred (e.g., based at least in part on the number of TAGs configured for the UE 120) based at least in part on the TAG configuration and / or SCell configuration in the RRC message. For example, if the UE 120 does not support multiple TAGs and / or is not configured with multiple TAGs, the field may have a zero bit width or may be excluded from the DCI. As another example, if the UE 120 supports two TAGs, the field may have a bit width of 1, if the UE 120 supports three TAGs or four TAGs, the field may have a bit width of 2, and so on. In some aspects, a particular value of this field (eg, all bits of this field set to zero) may indicate that an uplink carrier (eg, to be used to send RA messages) and a downlink carrier (eg, used to carry DCI) belong to the same TAG.
[0071] Additionally, or alternatively, the DCI may indicate whether the random access message is to be sent as part of a two-step random access procedure or as part of a four-step random access procedure. For example, the DCI may include a field that identifies the RACH type as a two-step RACH or a four-step RACH. In some aspects, the field may include a single bit. A first value of the bit (e.g., zero) may indicate a four-step RACH, and a second value of the bit (e.g., one) may indicate a two-step RACH.
[0072] Additionally, or alternatively, the DCI may indicate a frequency domain resource allocation (FDRA) for sending the RA message on the second cell. The FDRA may indicate a set of frequency domain resources to be used by the UE 120 to send the RA message on the second cell. For example, a frequency domain resource indication value (RIV) may be used to indicate the FDRA. In some aspects, the field indicating the FDRA (e.g., the frequency domain RIV) may have a maximum bit width of in Indicates the size of the initial uplink bandwidth portion configured for the uplink carrier in the sTAG. In some aspects, if the DCI indicates that the RA message is for a four-step RACH, the UE 120 may ignore the FDRA field, and / or the FDRA field may be set to a specific value (e.g., all ones) to indicate that the FDRA field is to be ignored because the FDRA is used for RA payloads, which are not sent by the UE 120 in a four-step RACH. If the DCI indicates that the RA message is for a two-step RACH, the UE 120 may use the value of the FDRA field (e.g., frequency domain RIV) to identify the set of frequency domain resources on which the RA payload is to be sent on the second carrier.
[0073] Because DCI format 1_0 has a limited number of reserved bits (e.g., 10 reserved bits), the number of bits available for the FDRA field may be limited. If the number of bits in the FDRA field is greater than or equal to the frequency domain RIV, the base station 110 may include the entire frequency domain RIV in the FDRA field. In this case, the value of the FDRA field may be set according to the type 1 resource allocation of the PRU for msgA to indicate a set of frequency domain resources to be used to send msgA. If the number of bits in the FDRA field is less than the frequency domain RIV, one or more bits (e.g., one or more most significant bits) of the frequency domain RIV may be truncated so that the remaining bits of the frequency domain RIV may be indicated in the FDRA field. Additionally, or alternatively, if the number of bits in the FDRA field is less than the frequency domain RIV, the granularity of the frequency domain RIV may be modified (e.g., increased from a granularity of 1 resource block (RB) to 2 RBs, etc.). In this way, a limited number of bits in the DCI may be used to indicate the FDRA.
[0074] Additionally, or alternatively, the DCI may indicate a time domain resource allocation (TDRA) for sending an RA message on the second cell. TDRA may indicate a set of time domain resources to be used by UE 120 to send an RA message on the second cell. TDRA may be indicated in the TDRA field. In some aspects, the TDRA field may have a configurable bit width. For example, the bit width of the TDRA field may be indicated in an RRC message. In some aspects, if the DCI indicates that the RA message is used for a four-step RACH, the UE 120 may ignore the TDRA field and / or the TDRA field may be set to a specific value (e.g., all one) to indicate that the TDRA field will be ignored because the TDRA is used for RA payload, which is not sent by the UE 120 in the four-step RACH. If the DCI indicates that the RA message is used for a two-step RACH, the UE 120 may use the value of the TDRA field to identify a set of time domain resources on which the RA payload will be sent on the second carrier. The value of the TDRA field may be set according to the time domain resource allocation of the PRU for msgA to indicate the set of time domain resources to be used for sending msgA. Thus, in some aspects, the value of the FDRA field and / or the TDRA field may be set according to the RACH type indicated by the DCI.
[0075] Additionally, or alternatively, the DCI may indicate a payload size for an RA message (e.g., for an RA payload), a modulation and coding scheme (MCS) to be used for the RA message (e.g., for an RA payload), a rate matching scheme to be used for the RA message (e.g., for an RA payload), and / or a redundancy version to be used for the RA message (e.g., for an RA payload). This information may be indicated in one or more fields of the DCI. One or more fields may have a configurable bit width (e.g., which may be indicated in an RRC message). In some aspects, the payload size may be explicitly indicated in the DCI. Additionally, or alternatively, the DCI may indicate an MCS and / or resource allocation, and the UE 120 may infer the payload size based at least in part on the MCS and / or resource allocation. In some aspects, if the DCI indicates that the RA message is for a four-step RACH, the UE 120 may ignore one or more fields and / or one or more fields may be set to a specific value, as shown above. If the DCI indicates that the RA message is for two-step RACH, the UE 120 may use the value(s) of the one or more fields to identify the payload size, MCS, rate matching scheme, redundancy version, etc. for the RA message. In some aspects, the one or more fields may include an index that maps to a corresponding value of the payload size, MCS, rate matching scheme, redundancy version, etc.
[0076] Additionally, or alternatively, the DCI may indicate a demodulation reference signal (DMRS) configuration for the RA message. The DMRS configuration may indicate, for example, one or more DMRS ports, a DMRS sequence, one or more resources to be used for the DMRS, and the like. In some aspects, the DMRS configuration for msgA on the sTAG may reuse the CFRA configuration (e.g., DMRS configuration) of the pTAG. Additionally, or alternatively, the DMRS configuration for msgA on the sTAG may be based at least in part on the msgA preamble configuration for CFRA. The msgA preamble configuration for CFRA may be indicated in system information, an RRC message, and the like. Additionally, or alternatively, the UE 120 may receive (e.g., in system information, an RRC message, and the like) information identifying a table for mapping between msgA preambles and corresponding msgA DMRS configurations.
[0077] In some aspects, the DCI may indicate a random access preamble index, an SSB index (or SS / PBCH index), a PRACH mask index, and the like. The random access preamble index may indicate a preamble index for msgA for two-step RACH or a preamble index for MSG1 for four-step RACH. The SSB index may indicate an SSB index to be used to determine the RACH timing of msgA or MSG1. The PRACH mask index may indicate an index of a RACH timing of an sTAG uplink carrier associated with the SSB index. In some aspects, by adding one or more of the above fields, the fields of the random access preamble index, the SSB index, and / or the PRACH mask index may be maintained at the same size as in a conventional DCI having format 1_0 for backward compatibility. Alternatively, the field size of the random access preamble index, the SSB index, and / or the PRACH mask index may be configurable (e.g., using an RRC message). For example, the bit width of the random access preamble index may be maintained at 6 bits for backward compatibility, or may be modified based at least in part on the pool size of the preamble sequence associated with the CFRA. In some aspects, a particular value of the random access preamble index may indicate a CBRA. As another example, the bit width of the SSB index field may remain at 6 bits for backward compatibility, or may be modified based at least in part on the SSB-to-PRU association rule for two-step RACH. As another example, the bit width of the PRACH mask index field may remain at 4 bits for backward compatibility, or may be modified based at least in part on the RACH opportunity configuration for two-step RACH and / or four-step RACH.
[0078] In some aspects, due to the number of available (eg, reserved) bits in the DCI, the information used for cross-TAG scheduling may be limited to 10 bits. In some aspects, the interpretation of the bits used for cross-TAG scheduling may be indicated in the RRC message.
[0079] As shown by reference numeral 610, a set of cyclic redundancy check (CRC) bits of the DCI may be scrambled. In some aspects, the CRC bits may be scrambled using a cell radio network temporary identifier (C-RNTI), such as a C-RNTI associated with the first cell. In some aspects, the CRC bits may be scrambled using a UE identifier associated with the UE 120. For example, the UE identifier may be a function of the C-RNTI and a TAG index or identifier (e.g., of an sTAG). In some aspects, the UE identifier may be indicated in an RRC message (e.g., on the first cell).
[0080] As indicated by reference numeral 615, UE 120 may determine a timing advance value for the RA message based at least in part on the DCI. Additionally, or alternatively, UE 120 may generate the RA message based at least in part on one or more parameters indicated in the DCI. For example, UE 120 may generate the RA payload based at least in part on one or more payload parameters indicated in the DCI.
[0081] As indicated by reference numeral 620, UE 120 may send an RA message (which may include an RA preamble and / or an RA payload) via the second cell. UE 120 may send the RA message with a timing based at least in part on a timing advance value determined from the DCI (e.g., an indicated sTAG for the second cell). Additionally, or alternatively, UE 120 may send the RA message based on one or more parameters indicated in the DCI for sending the RA message via the second cell. For example, UE 120 may send the RA payload based at least in part on one or more payload parameters indicated in the DCI for sending the RA message via the second cell. In some aspects, the RA message is msgA of a two-step RACH procedure, as described above in conjunction with Figure 3 In some aspects, the RA message is MSG1 and / or MSG3 of a four-step RACH procedure.
[0082] By indicating information for cross-TAG scheduling in the DCI for PDCCH ordered CFRA, the base station 110 can enable the UE 120 to perform cross-TAG scheduling of PDCCH ordered CFRA, thereby improving network throughput (e.g., by using carrier aggregation and / or dual connectivity), improving reliability, reducing latency, and improving performance.
[0083] As mentioned above, Figure 6 Provided as an example. Other examples can be found in relation to Figure 6 The content described is different.
[0084] Figure 7is a diagram illustrating another example 700 supporting cross-TAG scheduling and 2-step RACH payload transmission for a PDCCH ordered CFRA procedure in accordance with various aspects of the present disclosure.
[0085] like Figure 7 As shown, UE 120 can communicate with base station 110 using a first cell (shown as cell 1) included in a first TAG (shown as TAG 1). The first cell may be a primary cell (PCell), and the first TAG may be a pTAG. The first cell may schedule communications for a second cell (shown as cell 2) included in a second TAG (shown as TAG 2) and a third cell (shown as cell 3) included in a third TAG (shown as TAG). The first TAG, the second TAG, and the third TAG may all be different. For example, the first TAG may be a pTAG and the second and third TAGs may be different sTAGs. The second cell and the third cell may be different SCells. The first cell, the second cell, and the third cell may be provided by the same base station 110 or by a plurality of base stations 110.
[0086] In some aspects, the sTAG of the second cell is not configured with a scheduling cell (e.g., a scheduling SCell), and the sTAG of the third cell is not configured with a scheduling cell (e.g., a scheduling SCell). Therefore, in this case, at least two sTAGs are not configured with a scheduling cell. In this case, a single DCI with format 1_0 cannot be used to support cross-TAG scheduling for the sTAG of the second cell and the sTAG of the third cell. Figure 7 Details of cross-TAG scheduling for multiple sTAGs are shown.
[0087] As shown by reference numeral 705, the base station 110 may send a first DCI (shown as DCI A) for PDCCH ordered CFRA on the second cell to the UE 120 via the first cell. The first DCI may include the above combined Figure 6 The first DCI may carry the information for cross-TAG scheduling of the second cell. For example, the first DCI may indicate a TAG (e.g., sTAG) of the second cell, may indicate one or more parameters associated with a random access message to be sent by UE 120 via the second cell, and the like, as described above in conjunction with Figure 6 described.
[0088] As shown by reference numeral 710, the base station 110 may send a second DCI (shown as DCI B) for PDCCH ordered CFRA on the third cell to the UE 120 via the first cell. The second DCI may include the above combined Figure 6The second DCI may carry the information for cross-TAG scheduling of the third cell. For example, the second DCI may indicate a TAG (e.g., sTAG) of the third cell, may indicate one or more parameters associated with a random access message to be sent by UE 120 via the third cell, and the like, as described above in conjunction with Figure 6 described.
[0089] As shown in reference numeral 715, in some aspects, a first set of CRC bits of a first DCI may be scrambled using a first identifier, and a second set of CRC bits of a second DCI may be scrambled using a second identifier. In this case, the CRC overhead for sending the first DCI and the second DCI may be more, but the first DCI and the second DCI may both have DCI format 1_0, so that there is no need to create a new DCI format. Figure 6 As described above, the identifier used to scramble the CRC bits may be a C-RNTI, a UE identifier (eg, a function of the C-RNTI and a sTAG identifier or a sTAG index), or the like.
[0090] As shown in reference numeral 720, in some aspects, the joint CRC bits of the first DCI and the second DCI may be scrambled using an identifier. In this case, the CRC overhead for sending the first DCI and the second DCI may be less, but a new DCI format may be required. Figure 6 As described above, the identifier used to scramble the CRC bits may be a C-RNTI, a UE identifier (eg, a function of the C-RNTI and a sTAG identifier or a sTAG index), or the like.
[0091] As shown in reference numeral 725, UE 120 may be combined with the above Figure 6 In a similar manner as described above, the timing advance value of the first RA message to be sent on the second cell is determined based at least in part on the first DCI. Additionally or alternatively, the UE 120 may be configured to perform the following steps in conjunction with the above. Figure 6 In a similar manner as described above, a first RA message for the second cell may be generated based at least in part on one or more parameters indicated in the first DCI. For example, UE 120 may generate a first RA payload for the second cell based at least in part on one or more payload parameters indicated in the first DCI. Similarly, UE 120 may determine a timing advance value for a second RA message to be sent on a third cell based at least in part on the second DCI and / or may generate a second RA message (e.g., a second RA payload) for the third cell.
[0092] As indicated by reference numeral 730, UE 120 may send a first RA message (which may include a first RA preamble and / or a first RA payload) via the second cell. UE 120 may send the first RA message with a timing based at least in part on a timing advance value determined from the first DCI (e.g., an indicated sTAG for the second cell). Additionally, or alternatively, UE 120 may send the first RA message based on one or more parameters indicated in the first DCI for sending the first RA message via the second cell. For example, UE 120 may send the first RA payload based at least in part on one or more payload parameters indicated in the first DCI for sending the RA message via the second cell. In some aspects, the first RA message is msgA of a two-step RACH procedure, as described above in conjunction with Figure 3 In some aspects, the first RA message is MSG1 and / or MSG3 of the four-step RACH procedure.
[0093] As indicated by reference numeral 735, UE 120 may send a second RA message (which may include a second RA preamble and / or a second RA payload) via the third cell. UE 120 may send the second RA message with a timing based at least in part on a timing advance value determined from the second DCI (e.g., an indicated sTAG for the third cell). Additionally, or alternatively, UE 120 may send the second RA message based on one or more parameters indicated in the second DCI for sending the second RA message via the third cell. For example, UE 120 may send the second RA payload based at least in part on one or more payload parameters indicated in the second DCI for sending the RA message via the third cell. In some aspects, the second RA message is msgA of a two-step RACH procedure, as described above in conjunction with Figure 3 In some aspects, the second RA message is MSG1 and / or MSG3 of the four-step RACH procedure.
[0094] By indicating information for cross-TAG scheduling in the DCI for PDCCH ordered CFRA, the base station 110 can enable the UE 120 to perform cross-TAG scheduling for PDCCH ordered CFRA, thereby improving network throughput (e.g., by using carrier aggregation and / or dual connectivity), improving reliability, reducing latency, and improving performance.
[0095] As mentioned above, Figure 7 Provided as an example. Other examples can be found in relation to Figure 7 The content described is different.
[0096] Figure 8is a diagram illustrating another example 800 supporting cross-TAG scheduling and 2-step RACH payload transmission for a PDCCH ordered CFRA procedure in accordance with various aspects of the present disclosure.
[0097] like Figure 8 As shown, UE 120 can communicate with base station 110 using a first cell (shown as cell 1) included in a first TAG (shown as TAG 1). The first cell may be a primary cell (PCell), and the first TAG may be a pTAG. The first cell may schedule communication of a second cell (shown as cell 2) also included in the first TAG (shown as TAG 1). Therefore, in this scenario, the first cell and the second cell may belong to the same TAG. The second cell may be a secondary cell (SCell), and the second TAG may be an sTAG. The first cell and the second cell may be provided by the same base station 110 or different base stations 110.
[0098] In example 800, the sTAG of the second cell is configured with a scheduling cell. In this case, the DCI does not need to support cross-TAG scheduling because the first cell and the second cell are in the same TAG. However, as part of the two-step RACH procedure performed on the second cell, the DCI may still need to support resource allocation and other configuration for msgA payload transmission on the second cell.
[0099] As indicated by reference numeral 805, the base station 110 may send a DCI for a PDCCH ordered CFRA to the UE 120 and via the first cell. In some aspects, the DCI has a DCI format 1_0. The DCI may include one or more parameters associated with the RA message (e.g., RA preamble, RA payload, msgA, etc.), as described above in conjunction with Figure 6 As described. For example, the DCI may indicate whether the random access message will be sent as part of a two-step random access procedure or as part of a four-step random access procedure, frequency domain resource allocation for the random access message, time domain resource allocation for the random access message, payload size for the random access message, modulation and coding scheme for the random access message, rate matching scheme for the random access message, redundant version for the random access message, demodulation reference signal resource configuration for the random access message, etc. In some aspects, a set of reserved bits in the DCI that do not indicate a random access preamble index, a synchronization signal block index, a physical random access channel mask index, etc. may be used to indicate one or more parameters.
[0100] In some aspects, the DCI may indicate a TAG (e.g., sTAG) of the second cell. For example, the DCI may indicate that the TAG of the second cell in which the RA message is to be sent is the same as the TAG of the first cell in which the DCI is received. For example, a field in the DCI indicating the TAG of the second cell (e.g., a TAG ID field, a CIF field, etc.) may be set to a value indicating that the TAG of the second cell is the same as the TAG of the first cell.
[0101] Additionally, or alternatively, DCI for same TAG scheduling may use a different CRC mask than DCI from cross TAG scheduling. In this case, the base station 110 may apply a different CRC mask to the DCI for cross TAG scheduling compared to the DCI for same TAG scheduling, and the UE 120 may determine whether the DCI is for cross TAG scheduling or same TAG scheduling based at least in part on the CRC mask. In some aspects, a different identifier for scrambling CRC bits may be used for DCI for cross TAG scheduling compared to DCI for same TAG scheduling. For example, the base station 110 may use C-RNTI to scramble DCI for same TAG scheduling, and may use an identifier other than C-RNTI (e.g., such as by using a UE identifier that is a function of C-RNTI and sTAG identifier or index) to scramble DCI for cross TAG scheduling.
[0102] Additionally, or alternatively, the base station 110 may use an indication in the RRC message to indicate that the DCI is for same TAG scheduling. Additionally, or alternatively, the base station 110 may allocate different preambles to the UE 120 for PDCCH ordered CFRA depending on whether the DCI is for same TAG scheduling or cross-TAG scheduling. For example, a first preamble set may be used for same TAG scheduling, and a second (e.g., mutually exclusive) preamble set may be used for cross-TAG scheduling. The base station 110 may select from the first preamble set or the second preamble set based at least in part on whether the DCI is for same TAG scheduling or cross-TAG scheduling, and may indicate the selected preamble in the DCI. The UE 120 may determine whether the DCI is for same TAG scheduling or cross-TAG scheduling based at least in part on the preamble indicated in the DCI.
[0103] As indicated by reference numeral 810, UE 120 may determine a timing advance value for an RA message based at least in part on the DCI. For example, UE 120 may determine the timing advance value based at least in part on determining that the first cell and the second cell are included in the same TAG. Additionally or alternatively, UE 120 may generate the RA message based at least in part on one or more parameters indicated in the DCI. For example, UE 120 may generate the RA payload based at least in part on one or more payload parameters indicated in the DCI.
[0104] As indicated by reference numeral 815, UE 120 may send an RA message (which may include an RA preamble and / or an RA payload) via the second cell. UE 120 may send the RA message with a timing based at least in part on a timing advance value determined from the DCI (e.g., an indication of same TAG scheduling). Additionally, or alternatively, UE 120 may send the RA message based on one or more parameters indicated in the DCI for sending the RA message via the second cell. For example, UE 120 may send the RA payload based at least in part on one or more payload parameters indicated in the DCI for sending the RA message via the second cell. In some aspects, the RA message is msgA of a two-step RACH procedure, as described above in conjunction with Figure 3 as described.
[0105] By indicating information for transmitting msgA in the DCI for PDCCH ordered CFRA, the base station 110 may enable the UE 120 to perform a two-step RACH procedure for PDCCH ordered CFRA, thereby reducing latency and improving performance.
[0106] As mentioned above, Figure 8 Provided as an example. Other examples can be found in relation to Figure 8 The content described is different.
[0107] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a UE in accordance with various aspects of the present disclosure. Example process 900 is an example of operations in which a UE (e.g., UE 120, etc.) performs operations associated with supporting cross-TAG scheduling and 2-step RACH payload transmission for a PDCCH ordered contention-free random access procedure.
[0108] like Fig. 9As shown, in some aspects, processing 900 may include receiving downlink control information for ordered contention-free random access of a physical downlink control channel via a first cell, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups (box 910). For example, the UE (e.g., using the receiving processor 258, the controller / processor 280, the memory 282, etc.) may receive downlink control information for ordered contention-free random access of a physical downlink control channel via the first cell, as described above. In some aspects, the downlink control information indicates a timing advance group of the second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell. In some aspects, the first cell and the second cell belong to different timing advance groups.
[0109] like Fig. 9 As further shown, in some aspects, process 900 may include sending a random access message via the second cell based on one or more parameters and a timing advance value determined based at least in part on a timing advance group for the second cell (block 920). For example, the UE (e.g., using transmit processor 264, controller / processor 280, memory 282, etc.) may send a random access message via the second cell based on one or more parameters and a timing advance value determined based at least in part on a timing advance group for the second cell, as described above.
[0110] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0111] In a first aspect, a random access message includes at least one of a random access preamble, a random access payload, or a combination thereof.
[0112] In a second aspect, alone or in combination with the first aspect, the timing advance group of the second cell is not configured with a scheduled secondary cell, and all other timing advance groups associated with the UE are configured with a scheduled cell.
[0113] In a third aspect, alone or in combination with one or more of the first and second aspects, the downlink control information indicates whether the random access message is to be sent as part of a two-step random access procedure or a four-step random access procedure.
[0114] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the downlink control information indicates the timing advance group of the second cell in a field including a timing advance group identifier or a carrier indicator identifying an index of an uplink carrier in the timing advance group.
[0115] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a bit width of a field is indicated in a radio resource control message.
[0116] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, one or more parameters indicate a frequency domain resource allocation for a random access message.
[0117] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, one or more parameters indicate a time domain resource allocation for a random access message.
[0118] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, one or more parameters indicate at least one of a payload size, a modulation and coding scheme, a rate matching scheme, or a redundancy version associated with a random access message.
[0119] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, one or more parameters indicate a demodulation reference signal resource configuration for a random access message.
[0120] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the downlink control information includes a field for indicating a random access preamble index, a field for indicating a synchronization signal block index, a field for indicating a physical random access channel mask index, and a set of reserved bits for indicating at least one of the following: whether the random access message will be sent as part of a two-step random access procedure or as part of a four-step random access procedure, a timing advance group of the second cell, a frequency domain resource allocation for the random access message, a time domain resource allocation for the random access message, a payload size associated with the random access message, a modulation and coding scheme for the random access message, a rate matching scheme for the random access message, a redundant version for the random access message, a demodulation reference signal resource configuration for the random access message, or a combination thereof.
[0121] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the cyclic redundancy check bits of the downlink control information are scrambled using at least one of: a cell radio network temporary identifier, or a UE identifier that is a function of the cell radio network temporary identifier and a timing advance group index.
[0122] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the timing advance group of the second cell is not configured with a scheduled secondary cell, and at least one other timing advance group associated with the UE is not configured with a scheduled cell.
[0123] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, processing 900 includes receiving second downlink control information for ordered contention-free random access to a physical downlink control channel via the first cell, and the second downlink control information indicates a second timing advance group of a third cell and one or more second parameters associated with a second random access message to be sent by the UE via the third cell, and the third cell belongs to a different timing advance group from the first cell and the second cell; and sending a second random access message via the third cell based on one or more second parameters and a second timing advance value determined at least in part based on the second timing advance group of the third cell.
[0124] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, a first cyclic redundancy check bit of downlink control information is scrambled using a first identifier, and a second cyclic redundancy check bit of a second downlink control information is scrambled using a second identifier.
[0125] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, joint cyclic redundancy check bits of the downlink control information and the second downlink control information are scrambled using an identifier.
[0126] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 900 may be used. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.
[0127] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with various aspects of the present disclosure. Example process 1000 is an example of operations in which a UE (e.g., UE 120, etc.) performs operations associated with supporting cross-TAG scheduling and 2-step RACH payload transmission for a PDCCH ordered contention-free random access procedure.
[0128] like Fig.10As shown, in some aspects, the process 1000 may include receiving downlink control information for a physical downlink control channel ordered contention-free random access (block 1010), wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure. For example, the UE (e.g., using the receive processor 258, the controller / processor 280, the memory 282, etc.) may receive downlink control information for a physical downlink control channel ordered contention-free random access, as described above. In some aspects, the downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure.
[0129] like Fig.10 As further shown, in some aspects, process 1000 may include sending a random access message for a two-step random access procedure based on one or more parameters (block 1020). For example, the UE (e.g., using the transmit processor 264, the controller / processor 280, the memory 282, etc.) may send a random access message for a two-step random access procedure based on one or more parameters, as described above.
[0130] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0131] In a first aspect, a random access message includes at least one of a random access preamble, a random access payload, or a combination thereof.
[0132] In a second aspect, alone or in combination with the first aspect, one or more parameters indicate at least one of: whether the random access message is sent as part of a two-step random access procedure or as part of a four-step random access procedure, frequency domain resource allocation for the random access message, time domain resource allocation for the random access message, payload size for the random access message, modulation and coding scheme for the random access message, rate matching scheme for the random access message, redundant version for the random access message, demodulation reference signal resource configuration for the random access message, or a combination thereof.
[0133] In a third aspect, either alone or in combination with one or more of the first and second aspects, the downlink control information includes a field for indicating a random access preamble index, a field for indicating a synchronization signal block index, a field for indicating a physical random access channel mask index, and a set of reserved bits for indicating one or more parameters.
[0134] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1000 comprises receiving an indication that a timing advance group associated with transmission of a random access message is the same as a timing advance group associated with a cell via which downlink control information is received.
[0135] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication is included in at least one of the fields in the radio resource control message or the downlink control information.
[0136] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the indication is based at least in part on at least one of: a preamble indicated in the downlink control information, a demodulation reference signal configuration indicated in the downlink control information, a cyclic redundancy check mask applied to the downlink control information, an identifier for scrambling the cyclic redundancy check bits of the downlink control information, or a combination thereof.
[0137] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1000 may be used. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
[0138] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.
[0139] The term "component" as used herein is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.
[0140] As used herein, satisfying a threshold may 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., depending on the context.
[0141] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in these respects. Therefore, 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 may be designed to implement the systems and / or methods based at least in part on the description herein.
[0142] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, multiple features in these features can be combined in a manner that is not specifically set forth in the claims and / or is not specifically disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes the combination of each dependent claim and each other claim in the claim set. The phrase "at least one" related to the list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc and any combination with multiple identical elements (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc or any other arrangement of a, b, and c).
[0143] Unless explicitly described, any element, action, or instruction used herein should not be interpreted as critical or necessary. In addition, the articles "a" and "an" used herein are intended to include one or more items and can be used interchangeably with "one or more". In addition, the terms "set" and "group" used herein are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". In the case of only intending to include one item, the phrase "only one" or similar language is used. In addition, the terms "has", "have", "having", etc. used herein are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to represent "based at least in part on".
Claims
1. A method of wireless communication performed by a user equipment UE, comprising: receiving, via a first cell, downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups, wherein the downlink control information comprises a field identifying the RACH type as a two-step RACH or a four-step RACH, the field comprising one or more bits indicating whether the random access message is to be sent as part of a two-step random access procedure or a four-step random access procedure; and Based on receiving the downlink control information, the random access message is sent via the second cell according to the one or more parameters and a timing advance value determined based at least in part on the timing advance group of the second cell.
2. The method of claim 1, wherein: The random access message includes at least one of a random access preamble, a random access payload, or a combination thereof.
3. The method of claim 1, wherein: The timing advance group of the second cell is not configured with a scheduled secondary cell, and all other timing advance groups associated with the UE are configured with a scheduled cell.
4. The method of claim 1, wherein: The downlink control information indicates the timing advance group of the second cell in a field including a timing advance group identifier or a carrier indicator identifying an index of an uplink carrier in the timing advance group.
5. The method of claim 4, wherein: The bit width of the field is indicated in the radio resource control message.
6. The method of claim 1, wherein: The one or more parameters indicate frequency domain resource allocation for the random access message.
7. The method of claim 1, wherein: The one or more parameters indicate a time domain resource allocation for the random access message.
8. The method of claim 1, wherein: The one or more parameters indicate at least one of a payload size, a modulation and coding scheme, a rate matching scheme, or a redundancy version associated with the random access message.
9. The method of claim 1, wherein: The one or more parameters indicate a demodulation reference signal resource configuration for the random access message.
10. The method of claim 1, wherein: The downlink control information includes a field for indicating a random access preamble index, a field for indicating a synchronization signal block index, a field for indicating a physical random access channel mask index, and a set of reserved bits including the one or more bits, wherein the set of reserved bits is used to indicate at least one of the following: whether the random access message is to be sent as part of the two-step random access procedure or as part of the four-step random access procedure, the timing advance group of the second cell, frequency domain resource allocation for the random access message, time domain resource allocation for the random access message, a payload size associated with the random access message, a modulation and coding scheme for said random access message, a rate matching scheme for said random access message, a redundancy version for the random access message, a demodulation reference signal resource configuration for the random access message, or A combination of them.
11. The method of claim 1, wherein: The cyclic redundancy check bits of the downlink control information are scrambled using at least one of the following: Cell Radio Network Temporary Identifier, or A UE identifier that is a function of the cell radio network temporary identifier and a timing advance group index.
12. The method of claim 1, wherein: The timing advance group of the second cell is not configured with a scheduled secondary cell, and at least one other timing advance group associated with the UE is not configured with a scheduled cell.
13. The method of claim 1, further comprising: receiving, via the first cell, second downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the second downlink control information indicates a second timing advance group of a third cell and one or more second parameters associated with a second random access message to be sent by the UE via the third cell, wherein the third cell belongs to a different timing advance group than the first cell and the second cell; and The second random access message is sent via the third cell according to the one or more second parameters and a second timing advance value determined based at least in part on the second timing advance group of the third cell.
14. The method of claim 13, wherein: A first cyclic redundancy check bit of the downlink control information is scrambled using a first identifier, and a second cyclic redundancy check bit of the second downlink control information is scrambled using a second identifier.
15. The method of claim 13, wherein: Joint cyclic redundancy check bits of the downlink control information and the second downlink control information are scrambled using an identifier.
16. A method of wireless communication performed by a user equipment UE, comprising: receiving downlink control information for a physical downlink control channel ordered contention-free random access, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by a UE as part of a two-step random access procedure; The downlink control information includes a field identifying the RACH type as a two-step RACH, the field including one or more bits indicating that the random access message is to be sent as part of a two-step random access procedure; and Based on receiving the downlink control information, the random access message for the two-step random access procedure is sent according to one or more parameters.
17. The method of claim 16, wherein: The random access message includes at least one of a random access preamble, a random access payload, or a combination thereof.
18. The method of claim 16, wherein: The one or more parameters indicate at least one of the following: whether the random access message is sent as part of the two-step random access procedure or as part of a four-step random access procedure, frequency domain resource allocation for the random access message, time domain resource allocation for the random access message, The payload size of the random access message, a modulation and coding scheme for said random access message, a rate matching scheme for said random access message, a redundancy version for the random access message, a demodulation reference signal resource configuration for the random access message, or A combination of them.
19. The method of claim 16, wherein: The downlink control information includes a field for indicating a random access preamble index, a field for indicating a synchronization signal block index, a field for indicating a physical random access channel mask index, and a set of reserved bits including the one or more bits for indicating the one or more parameters.
20. The method of claim 16, further comprising receiving an indication that a timing advance group associated with the transmission of the random access message is the same as a timing advance group associated with a cell via which the downlink control information is received.
21. The method of claim 20, wherein: The indication is included in at least one of a field in a radio resource control message or the downlink control information.
22. The method of claim 20, wherein: The indication is based at least in part on at least one of: a preamble indicated in the downlink control information, a demodulation reference signal configuration indicated in the downlink control information, a cyclic redundancy check mask applied to the downlink control information, an identifier for scrambling cyclic redundancy check bits of the downlink control information, or a combination thereof.
23. A user equipment UE for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving, via a first cell, downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; wherein the downlink control information comprises a field identifying the RACH type as a two-step RACH or a four-step RACH, the field comprising one or more bits indicating whether the random access message is to be sent as part of a two-step random access procedure or a four-step random access procedure; and Based on receiving the downlink control information, the random access message is sent via the second cell according to the one or more parameters and a timing advance value determined based at least in part on the timing advance group of the second cell.
24. The UE according to claim 23, wherein: The timing advance group of the second cell is not configured with a scheduled secondary cell, and all other timing advance groups associated with the UE are configured with a scheduled cell.
25. The UE according to claim 23, wherein: The one or more bits include a set of reserved bits.
26. The UE according to claim 23, wherein: The downlink control information indicates the timing advance group of the second cell in a field including a timing advance group identifier or a carrier indicator identifying an index of an uplink carrier in the timing advance group.
27. The UE according to claim 23, wherein: The timing advance group of the second cell is not configured with a scheduled secondary cell, and at least one other timing advance group associated with the UE is not configured with a scheduled cell.
28. The UE according to claim 23, wherein: The one or more processors are further configured to: receiving, via the first cell, second downlink control information for ordered contention-free random access of a physical downlink control channel, wherein the second downlink control information indicates a second timing advance group of a third cell and one or more second parameters associated with a second random access message to be sent by the UE via the third cell, wherein the third cell belongs to a different timing advance group than the first cell and the second cell; and The second random access message is sent via the third cell according to the one or more second parameters and a second timing advance value determined based at least in part on the second timing advance group of the third cell.
29. A user equipment UE for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving downlink control information for a physical downlink control channel ordered contention-free random access, wherein the downlink control information indicates one or more parameters associated with a random access message to be sent by a UE as part of a two-step random access procedure; The downlink control information includes a field identifying the RACH type as a two-step RACH, the field including one or more bits indicating that the random access message is to be sent as part of a two-step random access procedure; and Based on receiving the downlink control information, the random access message for the two-step random access procedure is sent according to one or more parameters.
30. The UE according to claim 29, wherein: The downlink control information includes a field for indicating a random access preamble index, a field for indicating a synchronization signal block index, a field for indicating a physical random access channel mask index, and a set of reserved bits for indicating the one or more parameters.
31. A non-transitory computer-readable medium storing one or more instructions for wireless communication, which when executed by one or more processors of a UE, cause the one or more processors to: receiving downlink control information for ordered contention-free random access of a physical downlink control channel via a first cell, wherein: The downlink control information indicates a timing advance group of a second cell and one or more parameters associated with a random access message to be sent by the UE via the second cell, wherein the first cell and the second cell belong to different timing advance groups; and wherein the downlink control information comprises a field identifying the RACH type as a two-step RACH or a four-step RACH, the field comprising one or more bits indicating whether the random access message is to be sent as part of a two-step random access procedure or a four-step random access procedure; and Based on receiving the downlink control information, the random access message is sent via the second cell according to the one or more parameters and a timing advance value determined based at least in part on the timing advance group of the second cell.
32. A non-transitory computer-readable medium storing one or more instructions for wireless communication, which when executed by one or more processors of a UE cause the one or more processors to: receiving downlink control information for ordered contention-free random access of a physical downlink control channel, wherein: The downlink control information indicates one or more parameters associated with a random access message to be sent by the UE as part of a two-step random access procedure; and The downlink control information includes a field identifying the RACH type as a two-step RACH, the field including one or more bits indicating that the random access message is to be sent as part of a two-step random access procedure; and Based on receiving the downlink control information, the random access message for the two-step random access procedure is sent according to one or more parameters.
