CN117981453A - Random access radio network temporary identifier for higher subcarrier spacing - Google Patents

Abstract

Certain aspects of the present disclosure provide techniques for wireless communication by a user equipment, comprising: transmitting a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot; generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds ROs of one or more configured RACH slots defined within a reference slot; and processing a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble using the RA-RNTI.

Description

Random access radio network temporary identifier for higher subcarrier spacing

Cross Reference to Related Applications

The present application claims priority from U.S. patent application Ser. No. 17/957,099, filed on 30 th 9 of 2022, which claims the benefit and priority from U.S. patent application Ser. No. 63/251,535, filed on 1 th 10 of 2021, and U.S. patent application Ser. No. 63/251,540, filed on 1 of 2021, all of which are assigned to the assignee of the present application and hereby incorporated by reference as if fully set forth below and expressly incorporated herein for all purposes of its entirety.

Background

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for generating a Random Access (RA) radio network temporary identifier (RA-RNTI) for a higher frequency subcarrier spacing (SCS).

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, or other similar types of services. These wireless communication systems may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, or other resources) with the users. The multiple access technique may rely on any of code division, time division, frequency division, orthogonal frequency division, single carrier frequency division, or time division synchronous code division, to name a few examples. These and other multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels.

Despite the tremendous technological advances made over the years in wireless communication systems, challenges remain. For example, complex and dynamic environments may still attenuate or block signals between the wireless transmitter and the wireless receiver, disrupting the various wireless channel measurement and reporting mechanisms established for managing and optimizing the use of limited wireless channel resources. Accordingly, there is a need for further improvements in wireless communication systems to overcome various challenges.

Disclosure of Invention

One aspect provides a method for wireless communication by a User Equipment (UE), comprising: transmitting a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot; generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and processing a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble using the RA-RNTI.

One aspect provides a method for wireless communication by a network entity, comprising: receiving a PRACH preamble from the UE in an RO within the RACH slot; generating an RA-RNTI based at least in part on the RO in which the PRACH is transmitted and the number of RACH slots in the frame; and processing the RAR message transmitted from the network entity to the UE in response to the PRACH preamble using the RA-RNTI.

One aspect provides a method for wireless communication by a User Equipment (UE), comprising: receiving a Random Access Channel (RACH) configuration configuring a plurality of RACH Occasions (ROs) for the UE; identifying one or more additional RACH slots within the reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and transmitting a Physical RACH (PRACH) preamble in the RO in one of the configured RACH slot or the additional RACH slot.

One aspect provides a method for wireless communication by a network entity, comprising: transmitting to the UE RACH configuration configuring the UE with a plurality of ROs; identifying one or more additional RACH slots within the reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and monitoring ROs in the configured RACH slot and the additional RACH slot for a Physical RACH (PRACH) preamble from the UE.

Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform the foregoing methods and those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the foregoing methods and those described elsewhere herein; and an apparatus comprising means for performing the foregoing methods, as well as those methods described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or a processing system cooperating over one or more networks.

For purposes of illustration, the following description and the annexed drawings set forth certain features.

Drawings

The drawings depict certain features of the aspects described herein and are not intended to limit the scope of the disclosure.

Fig. 1 is a block diagram conceptually illustrating an example wireless communication network.

Fig. 2 is a block diagram conceptually illustrating aspects of an example of a base station and user equipment.

Fig. 3A, 3B, 3C, and 3D depict various example aspects of a data structure for a wireless communication network.

Fig. 4 illustrates how different Synchronization Signal Blocks (SSBs) may be transmitted using different beams in accordance with aspects of the present disclosure.

FIG. 5 illustrates an example resource mapping in accordance with aspects of the present disclosure.

Fig. 6A and 6B are call flow diagrams illustrating example four-step and two-step Random Access Channel (RACH) procedures in accordance with certain aspects of the present disclosure.

Fig. 7 shows an example association of SSBs with RACH Occasions (ROs).

Fig. 8 is an example of ROs within a slot for a given subcarrier spacing (SCS).

Figure 9 illustrates an example RO pattern for different SCS in accordance with certain aspects of the present disclosure.

Fig. 10A, 10B, and 10C illustrate example RO slot expansion modes for different SCSs according to certain aspects of the present disclosure.

Fig. 11 illustrates example operations for wireless communication by a network entity in accordance with some aspects of the present disclosure.

Fig. 12 illustrates example operations for wireless communication by a User Equipment (UE) in accordance with some aspects of the present disclosure.

Fig. 13 illustrates example operations for wireless communication by a network entity in accordance with some aspects of the present disclosure.

Fig. 14 illustrates example operations for wireless communication by a User Equipment (UE) in accordance with some aspects of the present disclosure.

Fig. 15 depicts aspects of an example communication device.

Fig. 16 depicts aspects of an example communication device.

Fig. 17 depicts aspects of an example communication device.

Fig. 18 depicts aspects of an example communication device.

Detailed Description

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for generating Random Access (RA) radio network temporary identifiers (RA-RNTIs) for higher frequency subcarrier spacings (SCS), such as 480kHz and 960 kHz.

In wireless networks, communications are made using time and frequency resources, which are typically divided into subcarriers or tones in the frequency domain and symbols in the time domain. The subcarrier spacing is typically equal to the inverse of the symbol time. The subcarrier spacing and symbol length are collectively referred to as a parameter set.

The downlink and uplink transmissions are organized into frames (e.g., having a 10ms duration), each frame consisting of a set of subframes (e.g., 10 x 1ms subframes). Each subframe may be further divided into slots. The slots tend to have the same number of symbols. The slot length varies according to the subcarrier spacing such that generally the slot length becomes shorter as the subcarrier spacing becomes wider (due to shorter symbols).

The reduction in slot length resulting from the wider subcarrier spacing can affect various processes such as beam sweep. Beam sweep generally refers to transmitting signals at regular intervals in a predetermined direction. During initial access (e.g., when the mobile phone is first turned on), the UE searches for a Synchronization Signal Block (SSB) transmitted in a different direction (beam sweep) to attempt to synchronize with the network and obtain system information.

Typically, the UE is designed to support a relatively large number of SSB beams (e.g., up to 64). While larger SCS (and thus shorter symbols) may result in reduced beam sweep time, downlink-to-uplink (DL/UL) handoff delays for utilizing uplink segments within SSB bursts may present challenges at the UE. The reduction in slot duration may also affect the Random Access Channel (RACH) procedure, involving physical RACH preamble transmission in RACH Occasions (ROs) determined based on SSB detection.

After receiving the RACH preamble transmitted by the UE, the network transmits a Random Access Response (RAR) involving a random access RNTI (RA-RNTI). The RA-RNTI is used to scramble a checksum of a Physical Downlink Control Channel (PDCCH) used to schedule a Physical Downlink Shared Channel (PDSCH) carrying the RAR. The RA-RNTI helps the UE identify that the RAR corresponds to its RACH preamble transmission. This is because the RA-RNTI is generated using parameters of the RACH preamble in a manner that explicitly identifies which time-frequency resource is used by the UE to transmit the RACH preamble.

The current RA-RNTI equation assumes that the index of the first slot of the RACH occasion is less than 80. However, for higher SCS, this assumption may not hold because the RACH slot number may be greater than 80.

Aspects of the present disclosure may help address these issues. For example, certain aspects of the present disclosure introduce modifications to the equations used to generate RA-RNTIs, which may depend on the actual RO configuration designed to accommodate the higher SCS.

Wireless communication network introduction

Fig. 1 depicts an example of a wireless communication system 100 in which aspects described herein may be implemented.

In general, the wireless communication network 100 includes a Base Station (BS) 102, a User Equipment (UE) 104, one or more core networks, such as an Evolved Packet Core (EPC) 160 and a 5G core (5 GC) network 190, that interoperate to provide wireless communication services.

The base station 102 may provide an access point for the user equipment 104 to the EPC 160 and/or 5gc 190 and may perform one or more of the following functions: user data delivery, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, delivery of warning messages, and other functions. In various contexts, a base station may include and/or be referred to as a gNB, a node B, an eNB, a ng-eNB (e.g., an eNB that has been enhanced to provide connectivity to both EPC 160 and 5GC 190), an access point, a transceiver base station, a radio transceiver, or a transceiver function, or a transmission receiving point.

The base station 102 communicates wirelessly with the UE 104 via a communication link 120. Each base station 102 may provide communication coverage for a respective geographic coverage area 110 that may overlap in some cases. For example, a small cell 102 '(e.g., a low power base station) may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro cells (e.g., high power base stations).

The communication link 120 between the base station 102 and the UE 104 may include Uplink (UL) (also known as reverse link) transmissions from the user equipment 104 to the base station 102 and/or Downlink (DL) (also known as forward link) transmissions from the base station 102 to the user equipment 104. In various aspects, communication link 120 may employ multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity.

Examples of UEs 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electricity meter, an air pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or other similar devices. Some of the UEs 104 may be internet of things (IoT) devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, or other IoT devices), always-on (AON) devices, or edge processing devices. The UE 104 may also be more generally referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or client.

Communications using higher frequency bands may have higher path loss and shorter distances than lower frequency communications. Thus, some base stations (e.g., 180 in fig. 1) may utilize beamforming 182 with the UE 104 to improve path loss and distance. For example, the base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming.

In some cases, the base station 180 may transmit the beamformed signals to the UE 104 in one or more transmission directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals to the base station 180 in one or more transmission directions 182 ". The base station 180 may also receive beamformed signals from the UEs 104 in one or more receive directions 182'. The base station 180 and the UE 104 may then perform beam training to determine the best receive direction and transmit direction for each of the base station 180 and the UE 104. It is noted that the transmission direction and the reception direction of the base station 180 may be the same or may be different. Similarly, the transmit direction and the receive direction of the UE 104 may or may not be the same.

The wireless communication network 100 includes a Random Access (RA) radio network temporary identifier (RA-RNTI) manager component 199 that may be configured to transmit RA-RNTIs for a subcarrier spacing (SCS). The radio network 100 also includes an RA-RNTI manager component 198 that may be configured to receive the RA-RNTI for the SCS.

Fig. 2 depicts aspects of an example Base Station (BS) 102 and User Equipment (UE) 104.

In general, base station 102 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a-t (collectively 234), transceivers 232a-t (collectively 232) including modulators and demodulators, and other aspects, that enable wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data sink 239). For example, the base station 102 may send and receive data between itself and the user equipment 104.

The base station 102 includes a controller/processor 240 that may be configured to implement various functions related to wireless communications. In the depicted example, the controller/processor 240 includes an RA-RNTI management component 241, which may represent the RA-RNTI management component 199 of fig. 1. Notably, while depicted as an aspect of the controller/processor 240, in other implementations, the RA-RNTI management component 241 may additionally or alternatively be implemented in various other aspects of the base station 102.

In general, the user equipment 104 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-r (collectively 252), transceivers 254a-r (collectively 254) including modulators and demodulators, and other aspects, that enable wireless transmission of data (e.g., data source 262) and wireless reception of data (e.g., data sink 260).

The user equipment 104 includes a controller/processor 280 that may be configured to implement various functions related to wireless communications. In the depicted example, controller/processor 280 includes RA-RNTI management component 281, which may represent RA-RNTI management component 198 of fig. 1. Notably, while depicted as an aspect of the controller/processor 280, in other implementations, the RA-RNTI management component 281 may additionally or alternatively be implemented in various other aspects of the user equipment 104.

Fig. 3A-3D depict aspects of a data structure for a wireless communication network, such as wireless communication network 100 of fig. 1. Specifically, fig. 3A is a diagram 300 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, fig. 3B is a diagram 330 illustrating an example of a DL channel within a 5G subframe, fig. 3C is a diagram 350 illustrating an example of a second subframe within a 5G frame structure, and fig. 3D is a diagram 380 illustrating an example of a UL channel within a 5G subframe.

Further discussion regarding fig. 1, 2, and 3A-3D is provided later in this disclosure.

Example Signal synchronization Block Transmission

In NR, a Synchronization Signal Block (SSB) is transmitted. In certain aspects, SSBs may be transmitted in bursts, where each SSB in a burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and/or beam refinement). SSB includes PSS, SSS and two symbols PBCH. SSBs may be transmitted in fixed slot positions, such as symbols 0 through 3 shown in fig. 3. PSS and SSS may be used by the UE for cell search and cell acquisition. The PSS may provide half frame timing and the SS may provide CP length and frame timing. PSS and SSS may provide cell identity. The PBCH carries some basic system information such as downlink system bandwidth, timing information within the radio frame, SS burst set periodicity, system frame number, etc. SSBs may be organized into SS bursts to support beam sweep. Additional system information such as Remaining Minimum System Information (RMSI), system Information Blocks (SIBs), other System Information (OSI) may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes. For millimeter waves, SSBs may be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions. Multiple transmissions of SSBs are referred to as SS burst sets. SSBs in SS burst sets may be transmitted in the same frequency region, while SSBs in different SS burst sets may be transmitted in different frequency regions.

Additional system information such as Remaining Minimum System Information (RMSI), system Information Blocks (SIBs), other System Information (OSI) may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes.

As shown in fig. 4, SS blocks may be organized into SS burst sets to support beam sweep. As shown, each SSB within a burst set may be transmitted using a different beam, which may help the UE quickly acquire both a transmit (Tx) beam and a receive (Rx) beam (e.g., in certain mmW applications). The Physical Cell Identity (PCI) can still be decoded from the PSS and SSS of the SSB.

A particular deployment scenario may include one or two NR deployment options. Some option may be configured for non-self-standing (NSA) and/or self-Standing (SA) options. The independent cell may need to broadcast both SSB and the Remaining Minimum System Information (RMSI), e.g., using SIB1 and SIB 2. A non-standalone cell may only need to broadcast SSB and not RMSI. In a single carrier in the NR, multiple SSBs may be transmitted in different frequencies and may include different types of SSBs.

Fig. 5 illustrates an example transmission resource map 500 in accordance with aspects of the present disclosure. In an exemplary mapping, a BS (e.g., BS110a shown in fig. 1) transmits SS/PBCH block 502. The SS/PBCH block includes a Master Information Block (MIB) that conveys an index to a table that correlates CORESET time and frequency resources with those of the SS/PBCH block. The BS may also transmit control signaling. In some scenarios, the BS may also transmit PDCCH (e.g., schedule PDSCH 506) to the UE within the time/frequency resources of CORESET 504,504.

Example RACH procedure

The Random Access Channel (RACH) is so named because it refers to a radio channel (medium) that can be shared by multiple UEs and used by those UEs to (randomly) access the network for communication. For example, RACH may be used for call setup and access to a network for data transmission. In some cases, RACH may be used for initial access to the network when the UE switches from a Radio Resource Control (RRC) connected idle mode to an active mode, or when switching in an RRC connected mode. Furthermore, RACH may be used for Downlink (DL) and/or Uplink (UL) data arrival when the UE is in RRC idle or RRC inactive mode, and when reestablishing a connection with the network.

Fig. 6A is a timing diagram (or "call flow diagram") 600 illustrating an example four-step RACH procedure in accordance with certain aspects of the present disclosure. The first message (MSG 1) may be transmitted from the UE 120 to the BS110 on a Physical Random Access Channel (PRACH). In this case, MSG1 may include only RACH preamble. BS110 may respond with a Random Access Response (RAR) message (MSG 2) that may include an Identifier (ID) of the RACH preamble, a Timing Advance (TA), an uplink grant, a cell radio network temporary identifier (C-RNTI), and a back-off indicator. MSG2 may include PDCCH communications including control information regarding subsequent communications on PDSCH, as shown. In response to MSG2, MSG3 is transmitted from UE 120 to BS110 on PUSCH. MSG3 may include one or more of an RRC connection request, a tracking area update request, a system information request, a location lock or location signal request, or a scheduling request. BS110 then responds with MSG 4, which may include a contention resolution message.

In some cases, to speed up access, a two-step RACH procedure may be supported. As the name suggests, the two-step RACH procedure can effectively "collapse" the four messages of the four-step RACH procedure into two messages.

Fig. 6B is a timing diagram 650 illustrating an example two-step RACH procedure in accordance with certain aspects of the present disclosure. A first enhanced message may be sent from UE 120 to BS110 (msgA). In certain aspects msgA includes some or all of the information from MSG1 and MSG3 of the four-step RACH procedure (effectively combining MSG1 and MSG 3). For example, msgA may include MSG1 and MSG3 multiplexed together, such as using one of time division multiplexing or frequency division multiplexing. In certain aspects, msgA comprises a RACH preamble and a payload for random access. For example, msgA payload may include a UE-ID and other signaling information (e.g., buffer Status Report (BSR)) or Scheduling Request (SR). BS110 may respond with a Random Access Response (RAR) message (msgB) that may effectively combine MSG2 and MSG4 described above. For example, msgB may include an ID of RACH preamble, timing Advance (TA), back-off indicator, contention resolution message, UL/DL grant, and Transmit Power Control (TPC) command.

In a two-step RACH procedure msgA may include a RACH preamble and a payload. In some cases, RACH preambles and payloads may be sent in msgA transmission occasions.

The random access message (msgA) transmission occasions generally include msgA preamble occasions (for transmitting preamble signals) and msgA payload occasions for transmitting PUSCH. msgA preamble transmission generally involves:

(1) A preamble sequence is selected; and

(2) Selection of preamble occasions (for transmission of the selected preamble sequence) in the time/frequency domain.

MsgA payload transmission generally involves:

(1) Construction of random access message payload (DMRS/PUSCH); and

(2) Selection of one or more PUSCH Resource Units (PRUs) to transmit the message (payload) in the time/frequency domain.

In some cases, the UE monitors SSB transmissions sent (by the gNB using different beams) and associated with a limited set of time/frequency resources defining RACH Occasions (ROs) and PRUs. As will be described in more detail below, upon detecting an SSB, the UE may select an RO and one or more PRUs associated with the SSB for msgA transmissions. The limited set of ROs and PRUs may help reduce the monitoring overhead (blind decoding) of the base station.

There are several benefits to the two-step RACH procedure, such as access speed and the ability to send relatively small amounts of data without the overhead of establishing a connection for the entire four-step RACH procedure (when the four-step RACH message may be larger than the payload).

The two-step RACH procedure may operate in any RRC state and with any supported cell size. A network using a two-step RACH procedure may generally support contention-based random access (CBRA) message (e.g., msgA) transmissions within a limited payload size range and with a limited number of MCS levels.

Overview of SSB association with RACH occasion

After the UE has selected an SSB (beam), there are predefined one or more RACH Opportunities (ROs) with specific time and frequency offset and direction (e.g., specific to the selected SSB) for the SS block. Fig. 7 shows an example association (mapping) between SSBs and ROs.

The SSB is associated with the RO for the gNB to know what beam the UE has acquired/is using (commonly referred to as beam setup). One SSB may be associated with one or more ROs, or more than one SSB may be associated with one RO. The association is typically performed first in the frequency domain, then in the time domain within the RACH slot, then in the time domain across the RACH slot (e.g., starting from a lower SSB index). The association period is typically defined as the minimum number of RACH configuration periods such that all (configured) SSB beams are mapped into ROs.

Overview of frequency ranges

In 5G, two initial operating bands have been identified as frequency range names FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" band in various documents and articles. Similar naming problems sometimes occur with respect to FR2, which is often (interchangeably) referred to in various documents and articles as the "millimeter wave" band, although it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" (mmW "or" mmWave ") band, because the wavelengths at these frequencies are between 1 and 10 millimeters. The radio waves in this band may be referred to as millimeter waves. Near mmWave can extend down to a frequency of 3GHz with a wavelength of 100 mm. The ultra-high frequency (SHF) band extends between 3GHz and 30GHz, which is also known as a centimeter wave.

In view of the above, unless specifically stated otherwise, it is to be understood that, if used herein, the term "below 6GHz" and the like may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" or the like is used herein, it may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

Aspects related to RACH slot extended mode for high frequency SCS

In some systems (e.g., according to NR), NR operation (referred to as "FR 2-2") in a frequency range between 52.6GHz and 71GHz may be deployed. In such systems, a new SCS may be used. For example, in addition to 120kHz SCS, 480kHz and 960kHz SCS may also be used for operation of data and control channels and reference signals in this frequency range together with a newly defined maximum bandwidth.

As described above, the increased SCS may lead to various timing related challenges, for example, when supporting up to 64 SSB beams for licensed and unlicensed operation in this frequency range. In some cases, it may be desirable for the UE to support 120kHz SCS for SSB and 120kHz SCS for initial access related signals/channels in the initial bandwidth part (BWP), and possibly additional higher SCS (240 kHz, 480kHz, 960 kHz) for SSB and additional SCS (480 kHz, 960 kHz) for initial access related signals/channels in the initial BWP. Additional SCS (480 kHz, 960 kHz) of SSB for the case other than initial access was studied and specified if necessary. Various PRACH sequence lengths (e.g., l=139, l=571, and l=1151) may be supported, and in some cases, RO configurations for non-contiguous RACH Occasions (ROs) in the time domain may be supported for operation in the shared spectrum.

In NR Rel-15/16, the PRACH preamble is sent from the UE to the gNB in a RACH Occasion (RO). As described above, referring to fig. 7, ro generally refers to a set of time/frequency resources. The specific RO selected by the UE for transmitting the RACH preamble is determined by association with the corresponding SSB (beam) selected by the UE. For some PRACH formats (e.g., format A, B, C), the RO may carry a duplicate PRACH preamble.

As shown in fig. 8, in some cases, a slot for the first SCS (e.g., a 60kHz slot) may be used as the reference PRACH slot 800. Due to the lower SCS, multiple PRACH slots of the higher SCS may fit within the reference PRACH slot 800. For example, as shown in fig. 8, for FR2, two 120kHz SCS PRACH slots may fit within a 60kHz reference PRACH slot 800.

As shown in fig. 8, a plurality of ROs may be configured in a single RACH slot. In the example shown, a 120kHz PRACH slot has 6 ROs, each RO occupying two symbols. A set of RACH slots may be repeated every RACH configuration period.

As described above, with reference to fig. 7, ssb and RO association is used for the gNB to know what beam the UE has acquired/is using (beam setup). One SSB may be associated with one or more ROs, or more than one SSB may be associated with one RO. The association is made in the frequency domain, then within the RACH slot in the time domain, then across the RACH slot in the time domain. The association period is defined as the minimum number of RACH configuration periods such that all SSB beams are mapped into ROs.

In some cases, at least the same RO density in the time domain (e.g., the number of specified ROs per reference slot according to the PRACH configuration index) may be supported for 480kHz and 960kHz PRACH, such as for 120kHz PRACH in FR 2. In some cases, gaps between consecutive ROs in the time domain may also be supported.

For 480kHz and 960kHz PRACH, when a PRACH slot can contain all time domain PRACH opportunities (including gaps between consecutive PRACH opportunities if supported) corresponding to a PRACH configuration index, the PRACH slot index may be determined to consider LBT and/or beam switching when the number of PRACH slots in the reference slot is 1, as follows:

For a PRACH at 480kHz, And for 960kHz PRACH,/>

And when the number of PRACH slots in the reference slot is 2,

For a PRACH at 480kHz,And for a PRACH of 960kHz,

When the PRACH slot cannot contain all time domain PRACH occasions corresponding to the PRACH configuration (including gaps between consecutive PRACH occasions if supported), a determination may be provided forA mechanism of values to account for LBT and/or beam switching. In some cases, for example, if the maximum value that can be configured for the number of FD ROs is less than 8 (e.g., due to bandwidth limitations), then additional/>, may be allowedValues.

In some cases, the reference slot duration may correspond to 60kHz SCS for 480kHz and 960kHz PRACH. PRACH slot indexMay correspond to one of the starting 480/960kHz PRACH slots within the reference slot.

NR Rel-16 allows for back-to-back multiplexing of ROs because the gNB beam switching delay can be absorbed by the CP (i.e., the CP can be long enough to absorb the beam switching delay). However, in higher frequency bands and SCS (e.g., scs=480 kHz and 960 kHz), the CP length may not be long enough to absorb the beam switching delay requirement. In addition, listen Before Talk (LBT) gaps may be required, which may be as long as one or more ROs.

To alleviate this problem, gaps between ROs (of different beams) may be included to accommodate beam switching. Without including explicit gaps, some PRACH symbol repetition may be lost and may be left to the gNB embodiment to determine how to handle any duplicate preamble loss. Thus, in some cases, at least one PRACH symbol-level gap may be included between ROs. In other cases, longer gaps (e.g., RO-stage gaps) may be included between ROs.

Fig. 9 shows examples of various options for introducing gaps between ROs of different beams. As shown, four 480kHz slots may be suitable for a 120kHz slot, and each RO spans two symbols.

According to a first option, referred to (and labeled in fig. 9) option a, ROs and slots are Time Division Multiplexed (TDM) until all required number of ROs are satisfied (e.g., based on the association with the corresponding SSB set), even though ROs extend to additional timeslots. For example, as shown, a two symbol length gap placed between each RO in a 480kHz RACH slot causes the ROs to extend into additional slots. For option a, four slots are located in the RACH slot, while the remaining two slots are extended into the extra slot.

According to a second option, referred to (and labeled in fig. 9) option B, the total number of ROs may be evenly divided among the plurality of slots such that the resulting gap pattern is the same for all slots. For example, in the illustrated example with six ROs, three ROs occupy the first slot, and the remaining three ROs may occupy additional slots.

Because ROs may overflow into extra slots, for higher RACH SCS (480 kHz and 960 kHz), more than 2 RACH slots (extra slots) per RACH reference slot may be required due to gap and/or coverage enhancement requirements.

Aspects related to RA-RNTI generation for high frequency SCS

As described above, after receiving the RACH preamble transmitted by the UE in the RO, the network transmits a Random Access Response (RAR). The RAR is transmitted in PDSCH scheduled by PDCCH with a checksum scrambled by RA-RNTI. The RA-RNTI is intended to explicitly identify which time frequency resource is used by the UE to transmit the RACH preamble and in doing so to assist the UE in identifying that the RAR corresponds to its RACH preamble transmission.

However, the current equation for generating RA-RNTI is based on the assumption that may not be true for higher SCS. The current equation for calculating the RA-RNTI associated with the PRACH occasion in which the preamble is transmitted is:

RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id；

wherein:

s_id is the index of the first OFDM symbol of the PRACH occasion (0.ltoreq.s_id < 14);

t_id is the index of the first slot of the PRACH occasion in the system frame (0.ltoreq.t_id < 80),

F_id is the index of PRACH occasion in frequency domain (0.ltoreq.f_id < 8); and

Ul_carrier_id is the UL carrier for preamble transmission (0 for NUL carrier and 1 for SUL carrier).

As shown, the calculation uses t_id <80, which assumes a 10ms RAR window (a window in which the UE monitors RAR after transmitting RACH preamble) and a maximum SCS of 120kHz (80 slots in frame). However, as described above, for higher frequency bands and higher SCS (480 kHz and 960 kHz), an additional RACH slot may be used in some cases.

In the case where no additional slots are required, the number of RACH slots in the frame may be limited (e.g., =80) and there may be no problem of calculating RA-RNTI according to the above equation. However, the number of RACH slots in a frame may exceed the assumed number (e.g., greater than 80) for the various scenarios described above. Thus, keeping the equation unchanged in this case (assuming t_id <80 slots) means that the maximum RAR window will be less than 10ms. This reduced maximum RAR window may be limiting (e.g., if 2 additional slots are used, there are 160 RACH slots in a frame, and the maximum RAR window would be halved to 5 ms).

In addition, in NR Rel-16, the RAR window (or MSGB window for 2-step RACH) and the NR unlicensed (NR-U) RAR window are extended to 40ms by including 2-bit LSBs of a System Frame Number (SFN) corresponding to a PRACH occasion for transmitting MSGA preamble in the RAR PDCCH.

Aspects of the present disclosure introduce modifications to the equations used to generate the RA-RNTI, which may depend on the actual RO design. The mechanism presented herein addresses various scenarios, such as (case 1) when no additional RACH slots are used (needed/configured), (case 2) when additional RACH slots are used but the same number of ROs per reference slot, and (case 3) when additional RACH slots are used and there are more ROs per reference slot.

For the first case, the number of 480/960kHz RACH slots per frame may be the same as the number of 120kHz (e.g., 1 or 2 slots per reference slot) when no additional RACH slots are needed or configured. Thus, the above equation can be reused by redefining the t_id parameter as:

t_id is the index (0.ltoreq.t_id < 80) of the first slot (based on the 120kHz parameter set) of the PRACH occasion in the system frame.

The second scenario that is addressed is when an additional RACH slot is needed or configured (but where there are the same number of ROs per reference slot). This situation is shown in fig. 9, for example, and may be due to the required gap and RO overflowing into more slots than configured. In this case, modifications to the s_id term of the RA-RNTI equation may be considered, as the RO will now span more than one slot (i.e., more than 14 symbols of one slot). However, if the number of ROs is the same, the total number of actual symbols used by all ROs (although spanning more than one slot) may remain within 14 (by not counting the symbols of the gap between them). Thus, the s_id parameter can be redefined as:

s_id is the index of the first OFDM symbol of the PRACH occasion within one or more slots spanned by RO, excluding any gap (0.ltoreq.s_id < 14).

The effect of this redefinition can be seen with reference to fig. 10A. In this example, (6) ROs extend into the extra time slot. Without this redefinition, ROs starting at the same symbol in each slot will produce the same s_id. However, by excluding the gap in determining s_id, s_id of the second RO occurring in symbol 4 of the configured slot has a value of 2 instead of a value of 4. Similarly, the s_id of the third RO occurring in symbol 4 of the configured slot has a value of 4 instead of a value of 8. In the extra slot, ambiguity is eliminated because s_id of the fourth RO occurring in symbol 0 of the extra slot has a value of 6 instead of 0. Similarly, the s_id of the fifth RO occurring in the symbol 4 of the extra slot has a value of 8 instead of the value of 4, and the s_id of the sixth RO occurring in the symbol 8 of the extra slot has a value of 10 instead of the value of 8. For t_id, a method similar to the previous case (case 1) can be adopted:

t_id is the index (0.ltoreq.t_id < 80) of the first slot (based on the 120kHz parameter set) of the PRACH occasion in the system frame.

The third case is when an additional RACH slot is required or is configured with more ROs than in the reference slot. This case may be configured to, for example, implement additional capacity to enhance coverage (e.g., with longer ROs). In this case, the s_id term of the equation can be reconsidered again, as the RO will again span more than one slot (i.e., >14 symbols). Accordingly, aspects of the present disclosure provide various options for using the scope of the extension s_id.

According to the first option (option a), s_id can be extended to be greater than 14 by introducing a new parameter S, and the equation can be modified as follows:

RA-RNTI＝(1+s_id+S×t_id+S×80×f_id+S×80×8×ul_carrier_id)mod 2¹⁶；

wherein:

s_id is the index of the first OFDM symbol of PRACH occasion within one or more slots spanned by RO excluding any gap (0 +.s_id < S);

s may take a value greater than 14 (S > 14); and

T_id is the index (0.ltoreq.t_id < 80) of the first slot (based on the 120kHz parameter set) of the PRACH occasion in the system frame.

Fig. 10B shows an example in which S has a value of 16 for the case of 8 ROs, including 4 ROs that extend into the extra slot. The s_id of the second RO occurring in symbol 3 of the configured slot has a value of 2 instead of a value of 3, extending the range of s_id based on s=16 and by excluding the gap in determining s_id. Similarly, the s_id of the third RO occurring in symbol 6 of the configured slot has a value of 4 instead of the value of 6, and the fourth RO occurring in symbol 9 of the configured slot has a value of 6 instead of the value of 9. In the extra slot, ambiguity is eliminated because the s_id of the fifth RO occurring in the symbol 0 of the extra slot has a value of 8 instead of the value of 0, the sixth RO occurring in the symbol 3 of the extra slot has a value of 10 instead of the value of 3, the s_id of the seventh RO occurring in the symbol 9 of the extra slot has a value of 12 instead of the value of 9, and the s_id of the eighth RO occurring in the symbol 12 of the extra slot has a value of 14 instead of the value of 9.

With this option, the RA-RNTI may be larger than the FFFF, and thus modulo arithmetic may be applied. Due to modulo arithmetic, there is a possibility that some ROs will have the same RA-RNTI and may collide with certain reserved or pre-allocated values (e.g. FFF0 to FFFD) or values reserved for paging RNTIs (P-RNTIs, FFFEs) or system information RNTIs (SI-RNTIs, FFFFs). In this case, an RO having RA-RNTI that collides with the pre-allocated RNTI should not be used. When a plurality of ROs have the same RA-RNTI but do not collide with the pre-allocated RNTI, only one of the ROs (e.g., the first RO among those having the same RA-RNTI) may be used or an existing contention resolution mechanism may be applied.

According to a second option (option B), when an additional RACH slot is required or is configured with more ROs than in the reference slot, the existing NR RA-RNTI equation may be reused while additional system timing information is conveyed. For example, additional system timing information may be conveyed in DL DCI of scheduling MSG 2/MSGB. This can be done using the same Rel-15/16 equation, but based on the following equation:

t_id is the index (0.ltoreq.t_id < 80) of the first slot (based on the 120kHz parameter set) of the PRACH occasion in the system frame; and

480/960KHz slot index within 120kHz slots is signaled in DL DCI of scheduling MSG 2/MSGB.

As described herein, aspects of the present disclosure provide various mechanisms for generating RA-RNTIs, which may depend on the actual RO configuration designed to accommodate higher SCS.

Because ROs may overflow into extra slots, for higher RACH SCS (480 kHz and 960 kHz), more than 2 RACH slots (extra slots) per RACH reference slot may be required due to gap and/or coverage enhancement requirements.

Aspects of the present disclosure provide mechanisms that can help determine where these additional slots should be placed within a reference slot.

Figure 10C depicts an example RO slot expansion mode for different SCS in accordance with certain aspects of the present disclosure. If additional slots are needed (e.g., RO requires more RACH slots in the reference slots due to gap and/or coverage enhancement requirements or any other requirement), one or more additional slots may be added in a designated area within the RACH reference slots.

According to a first option, called (and marked as) Alt 1 in fig. 10C, additional time slots are added such that these time slots are distributed within the RACH reference time slots according to a predefined pattern. For example, as shown, the slots may be evenly distributed within the RACH reference slots.

As shown, for the case of 480kHz SCS, there is one configured RACH slot at slot 7, and when one additional slot is used, the additional slot may be located at slot 3. When two additional time slots are needed, these additional time slots may be located at time slots 1 and 4.

For the case of 960kHz SCS, with two configured RACH slots at slots 7 and 15, when one additional slot (per configured RACH slot) is used, one additional slot may be located at slot 11 and the other slot may be located at slot 3. When two additional time slots (per configured RACH time slot) are used, the additional time slots may be located at time slots 9, 12, 4 and 1.

This first option may have the advantage of distributing RACH detection load over the gNB. This may be important, for example, in the case where there are a large number of UEs.

According to a second option, referred to as (and marked as) Alt 2 in fig. 10C, an additional time slot may be added in the time slot immediately adjacent to the original (configured) RACH time slot. A potential advantage of this second option is that it may result in fewer UL segments, which may allow for more flexible uplink scheduling.

As shown, for the case of 480kHz SCS, there is one configured RACH slot at slot 7, when one additional slot is used, the additional slot may be located at adjacent slot 6. When two additional time slots are needed, these additional time slots may be located at adjacent time slots 5 and 6.

For the case of 960kHz SCS, with two configured RACH slots at slots 7 and 15, when one additional slot (per configured RACH slot) is used, one additional slot may be located at adjacent slot 14 and the other slot may be located at slot 6. When two additional slots (per configured RACH slot) are used, the additional slots may be located at adjacent slots 14, 13, 6 and 5.

In some cases, the gNB may configure a slot expansion mode (e.g., alt 1 or Alt 2) for the UE to use.

The additional time slots may be used in different ways. For example, additional time slots may be used for new or additional ROs or beams to maintain or increase RACH capacity. In some cases, additional time slots may be used for repetition of existing ROs or beams for coverage enhancement. In some cases, a combination of these options may be used. For example, in this case, some extra time slots may be used for new or additional ROs or beams, while other extra time slots are used for repetition.

Example method

Fig. 11 illustrates example operations 1100 for wireless communication by a User Equipment (UE) in accordance with some aspects of the disclosure. For example, the UE 104 of fig. 1 may perform example operation 1100.

At 1110, the UE transmits a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot.

At 1120, the UE generates a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the number of ROs configured exceeds the RO capacity of one or more configured RACH slots defined within the reference slot.

At 1130, the UE uses the RA-RNTI to process a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble.

Fig. 12 illustrates example operations 1200 for wireless communication by a network entity in accordance with some aspects of the disclosure. For example, the base station 102 (e.g., a gNB) may perform the example operation 1200.

At 1210, the network entity receives a PRACH preamble from the UE in an RO within a RACH slot.

At 1220, the network entity generates an RA-RNTI based at least in part on the RO in which the PRACH was transmitted and the number of RACH slots in the frame.

At 1230, the network entity uses the RA-RNTI to process a RAR message transmitted from the network entity to the UE in response to the PRACH preamble.

Fig. 13 illustrates example operations 1300 for wireless communication by a User Equipment (UE) in accordance with some aspects of the disclosure. For example, the UE 104 of fig. 1 may perform the example operations 1300.

At 1310, the UE receives a Random Access Channel (RACH) configuration configuring a plurality of RACH Occasions (ROs) for the UE. For example, the UE 104 may receive RACH configurations that configure the UE 104 with multiple ROs.

At 1320, when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot, the UE identifies one or more additional RACH slots within the reference slot. For example, when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot, the UE 104 may identify one or more additional RACH slots within the reference slot (e.g., RACH slots 0-7 or 0-15 in fig. 10C).

At 1330, the UE transmits a Physical RACH (PRACH) preamble in the RO in one of the configured RACH slot or the additional RACH slot. For example, the UE 104 may transmit a PRACH preamble (e.g., according to Alt 1 or Alt 2 in fig. 10C) in an RO in one of the configured RACH slots or the additional RACH slots.

Fig. 14 illustrates example operations for wireless communication by a network entity in accordance with some aspects of the present disclosure. For example, the base station 102 (e.g., a gNB) may perform the example operation 1400.

At 1410, the network entity transmits to the user equipment UE RACH configuration configuring a plurality of ROs for the UE. For example, BS102/180 may transmit to UE 104 a RACH configuration that configures multiple ROs for UE 104.

At 1420, when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot, the network entity identifies one or more additional RACH slots within the reference slot. For example, when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot, BS102/180 may identify one or more additional RACH slots within the reference slot (e.g., additional RACH slots in fig. 10C).

At 1430, the network entity monitors the configured RACH slots and ROs in the additional RACH slots for a PRACH preamble from the UE. For example, BS102/180 may monitor ROs in the configured RACH slot and the additional RACH slot for PRACH preambles from UE 104.

Example Wireless communication device

Fig. 15 depicts an example communication device 1500 that includes various components capable of operating, configured, or adapted to perform operations for the techniques disclosed herein, such as the operations depicted and described with respect to fig. 11. In some examples, the communication device 1500 may be the user equipment 104 described, for example, with respect to fig. 1 and 2.

The communication device 1500 includes a processing system 1502 that is coupled to a transceiver 1508 (e.g., a transmitter and/or receiver). The transceiver 1508 is configured to transmit (or send) and receive signals of the communication device 1500, such as the various signals described herein, via the antenna 1510. The processing system 1502 may be configured to perform processing functions for the communication device 1500, including processing signals received by and/or to be transmitted by the communication device 1500.

The processing system 1502 includes one or more processors 1520 coupled to a computer-readable medium/memory 1530 via a bus 1506. In certain aspects, the computer-readable medium/memory 1530 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1520, cause the one or more processors 1520 to perform the operations shown in fig. 11 or to perform other operations discussed herein for transmitting various techniques with SSBs for SCS mode.

In the depicted example, computer-readable medium/memory 1530 stores code 1531 for transmitting a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot; code 1532 for generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds the RO capacity of the one or more configured RACH slots defined within the reference slot; and code 1533 for processing a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble using the RA-RNTI.

In the depicted example, the one or more processors 1520 include circuitry configured to implement code stored in a computer-readable medium/memory 1530 including circuitry 1521 for transmitting a PRACH preamble in an RO within a RACH slot to a network entity. Circuitry 1522 for generating an RA-RNTI based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and circuitry 1523 for processing the RAR message transmitted from the network entity in response to the PRACH preamble using the RA-RNTI.

The various components of the communications device 1500 may provide means for performing the methods described herein (including with respect to fig. 11).

In some examples, the means for transmitting or sending (or means for outputting for transmission) may include the transceiver 254 and/or antenna 252 of the user equipment 104 shown in fig. 2 and/or the transceiver 1508 and antenna 1510 of the communication device 1500 in fig. 15.

In some examples, the means for receiving (or means for obtaining) may include the transceiver 254 and/or the antenna 252 of the user equipment 104 shown in fig. 2 and/or the transceiver 1508 and the antenna 1510 of the communication device 1500 in fig. 15.

In some examples, the means for transmitting, generating, or using may include various processing system components, such as: one or more processors 1520 in fig. 15, or aspects of user equipment 104 depicted in fig. 2, include a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and/or a controller/processor 280 (including a RA-RNTI management component 281).

It is noted that fig. 15 is an example, and that many other examples and configurations of communication device 1500 are possible.

Fig. 16 depicts an example communication device 1600 that includes various components operable, configured, or adapted to perform operations for the techniques disclosed herein, such as the operations depicted and described with respect to fig. 12. In some examples, the communication device 1600 may be, for example, the base station 102 described with respect to fig. 1 and 2.

The communication device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and/or receiver). The transceiver 1608 is configured to transmit (or send) and receive signals of the communication device 1600, such as the various signals described herein, via the antenna 1610. The processing system 1602 may be configured to perform processing functions for the communication device 1600, including processing signals received by and/or to be transmitted by the communication device 1600.

The processing system 1602 includes one or more processors 1620 coupled to a computer-readable medium/memory 1630 via a bus 1606. In certain aspects, the computer-readable medium/memory 1630 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1620, cause the one or more processors 1620 to perform the operations shown in fig. 12 or other operations for performing various techniques for generating Random Access (RA) radio network temporary identifiers (RA-RNTIs) for higher frequency subcarrier spacing (SCS) as discussed herein.

In the depicted example, the computer-readable medium/memory 1630 stores code 1631 for receiving a PRACH preamble from a UE in an RO within a RACH slot; code 1632 for generating an RA-RNTI based at least in part on the RO in which the PRACH is transmitted and the number of RACH slots in the frame; and code 1633 for using the RA-RNTI to process an RAR message transmitted from the network entity to the UE in response to the PRACH preamble.

In the depicted example, the one or more processors 1620 include circuitry configured to implement code stored in the computer-readable medium/memory 1630, including circuitry 1621 for receiving a PRACH preamble in an RO within a RACH slot from a UE. Circuitry 1622 to generate an RA-RNTI based at least in part on the RO in which the PRACH was transmitted and the number of RACH slots in the frame; and circuitry 1623 for using the RA-RNTI to process a RAR message transmitted from the network entity to the UE in response to the PRACH preamble.

The various components of the communication device 1600 may provide means for performing the methods described herein (including with respect to fig. 12).

In some examples, the means for transmitting or sending (or means for outputting for transmission) may include the transceiver 232 and/or the antenna 234 of the base station 102 shown in fig. 2 and/or the transceiver 1608 and the antenna 1610 of the communication device 1600 in fig. 16.

In some examples, the means for receiving (or means for obtaining) may include the transceiver 232 and/or the antenna 234 of the base station 102 shown in fig. 2 and/or the transceiver 1608 and the antenna 1610 of the communication device 1600 in fig. 16.

In some examples, the means for receiving, generating, or using may include various processing system components, such as: one or more processors 1620 in fig. 16, or aspects of base station 102 depicted in fig. 2, include receive processor 238, transmit processor 220, TX MIMO processor 230, and/or controller/processor 240 (including RA-RNTI management component 241).

It is noted that fig. 16 is an example, and that many other examples and configurations of communication device 1600 are possible.

Fig. 17 depicts an example communication device 1700 that includes various components capable of operating, configured, or adapted to perform operations for the techniques disclosed herein, such as the operations depicted and described with respect to fig. 13. In some examples, the communication device 1700 may be the user equipment 104 described, for example, with respect to fig. 1 and 2.

The communication device 1700 includes a processing system 1702 coupled to a transceiver 1708 (e.g., a transmitter and/or receiver). The transceiver 1708 is configured to transmit (or send) and receive signals of the communication device 1700, such as various signals as described herein, via the antenna 1710. The processing system 1702 may be configured to perform processing functions for the communication device 1700, including processing signals received by and/or to be transmitted by the communication device 1700.

The processing system 1702 includes one or more processors 1720 coupled to a computer-readable medium/memory 1730 via a bus 1706. In certain aspects, the computer-readable medium/memory 1730 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1720, cause the one or more processors 1720 to perform the operations shown in fig. 13 or other operations for performing the various techniques for transmitting SSBs with SCS modes discussed herein.

In the depicted example, computer-readable medium/memory 1730 stores code 1731 for receiving a Random Access Channel (RACH) configuration configuring a plurality of RACH Occasions (ROs) for a UE; code 1732 for identifying one or more additional RACH slots within the reference slot when the number of configured ROs exceeds the RO capacity of the one or more configured RACH slots defined within the reference slot; and code 1733 for transmitting a Physical RACH (PRACH) preamble in the RO in one of the configured RACH slot or the additional RACH slot.

In the depicted example, the one or more processors 1720 include circuitry configured to implement code stored in a computer-readable medium/memory 1730, including circuitry 1721 for receiving RACH configurations to configure a plurality of ROs for a UE. Circuitry 1722 for identifying one or more additional RACH slots within the reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and circuitry 1723 to transmit the PRACH preamble in the RO in one of the configured RACH slot or the additional RACH slot.

The various components of communication device 1700 may provide means for performing the methods described herein (including with respect to fig. 13).

In some examples, the means for transmitting or sending (or means for outputting for transmission) may include the transceiver 254 and/or antenna 252 of the user equipment 104 shown in fig. 2 and/or the transceiver 1708 and antenna 1710 of the communication device 1700 in fig. 17.

In some examples, the means for receiving (or means for obtaining) may include the transceiver 254 and/or antenna 252 of the user equipment 104 shown in fig. 2 and/or the transceiver 1708 and antenna 1710 of the communication device 1700 in fig. 17.

In some examples, the means for receiving, identifying, or transmitting may include various processing system components, such as: one or more processors 1720 in fig. 17, or aspects of user equipment 104 depicted in fig. 2, include a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and/or a controller/processor 280 (including RA-RNTI management component 281).

It is noted that fig. 17 is an example, and that many other examples and configurations of communication device 1700 are possible.

Fig. 18 depicts an example communication device 1800 that includes various components capable of operating, configured, or adapted to perform operations for the techniques disclosed herein, such as the operations depicted and described with respect to fig. 14. In some examples, the communication device 1800 may be, for example, the base station 102 described with respect to fig. 1 and 2.

The communication device 1800 includes a processing system 1802 coupled to a transceiver 1808 (e.g., transmitter and/or receiver). The transceiver 1808 is configured to transmit (or send) and receive signals of the communication device 1800, such as the various signals as described herein, via the antenna 1810. The processing system 1802 may be configured to perform processing functions for the communication device 1800, including processing signals received by and/or to be transmitted by the communication device 1800.

The processing system 1802 includes one or more processors 1820 coupled to a computer-readable medium/memory 1830 via a bus 1806. In certain aspects, the computer-readable medium/memory 1830 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1820, cause the one or more processors 1820 to perform the operations shown in fig. 14 or to perform other operations for receiving SSBs having the various techniques for SCS mode discussed herein.

In the depicted example, computer-readable medium/memory 1830 stores code 1831 for transmitting RACH configuration to a UE to configure a plurality of ROs for the UE; code 1832 for identifying one or more additional RACH slots within the reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and code 1833 for monitoring ROs in the configured RACH slot and the additional RACH slot for a PRACH preamble from the UE.

In the depicted example, the one or more processors 1820 include circuitry configured to implement code stored in the computer-readable medium/memory 1830 including circuitry 1821 for transmitting to the UE RACH configuration configuring a plurality of ROs for the UE. Circuitry 1822 for identifying one or more additional RACH slots within the reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and circuitry 1823 for monitoring ROs in the configured RACH slot and the additional RACH slot for PRACH preambles from the UE.

The various components of the communication device 1800 may provide means for performing the methods described herein (including with respect to fig. 14).

In some examples, the means for transmitting or sending (or means for outputting for transmission) may include the transceiver 232 and/or antenna 234 of the base station 102 shown in fig. 2 and/or the transceiver 1808 and antenna 1810 of the communication device 1800 in fig. 18.

In some examples, the means for receiving (or means for obtaining) may include the transceiver 232 and/or the antenna 234 of the base station shown in fig. 2 and/or the transceiver 1808 and the antenna 1810 of the communication device 1800 in fig. 18.

In some examples, the means for transmitting, identifying, or monitoring may include various processing system components, such as: one or more processors 1820 in fig. 18, or aspects of base station 102 depicted in fig. 2, include receive processor 238, transmit processor 220, TX MIMO processor 230, and/or controller/processor 240 (including RA-RNTI management component 241).

It is noted that fig. 18 is an example, and that many other examples and configurations of the communication device 1800 are possible.

Example clauses

Specific examples of implementations are described in the following numbered clauses:

Clause 1: a method for wireless communication by a User Equipment (UE), comprising: transmitting a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot; generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds the RO capacity of one or more configured RACH slots defined within a reference slot; and processing a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble using the RA-RNTI.

Clause 2: the method of clause 1, wherein the RACH slots have a duration based on a first subcarrier spacing (SCS) and the number of RACH slots is the same as the number of RACH slots corresponding to a second SCS.

Clause 3: the method of clause 2, wherein the RA-RNTI is generated using an equation with parameters corresponding to a first time slot based on a parameter set of the second SCS of the RO in which the PRACH preamble is transmitted.

Clause 4. The method of any of clauses 1 to 3, wherein the number of ROs configured exceeds the RO capacity of one or more configured RACH slots defined within a reference slot, and the UE identifies one or more additional RACH slots within the reference slot.

Clause 5: the method of clause 4, wherein the RA-RNTI is generated using an equation involving parameters corresponding to an index of a first symbol of the RO in which the PRACH preamble is transmitted within a configured or additional RACH slot.

Clause 6: the method of any one of clauses 4 and 5, wherein the RA-RNTI is generated using an equation with parameters corresponding to a first time slot based on a set of parameters of the second SCS of the RO in which the PRACH preamble is transmitted.

Clause 7: the method of any one of clauses 4-6, wherein the PRACH preamble is transmitted in an RO selected from a set of ROs spanning multiple slots corresponding to a first subcarrier spacing (SCS), and the RA-RNTI is generated using an equation involving parameters of an index corresponding to a first symbol of the RO, wherein the PRACH preamble is transmitted within one or more slots spanned by the set of ROs.

Clause 8: the method of clause 7, wherein a value of the parameter corresponding to the index of the first symbol can be greater than a number of symbols within a slot.

Clause 9: the method of any one of clauses 7 and 8, wherein the equation further relates to a parameter corresponding to a first time slot based on a parameter set of a second SCS of the RO in which the PRACH preamble is transmitted.

Clause 10: the method of any of clauses 7-9, further comprising: the RO in which the PRACH preamble is transmitted is selected to avoid generating RA-RNTI with a reserved value.

Clause 11: the method of any of clauses 7-10, further comprising: receiving Downlink Control Information (DCI) scheduling the RAR message; and using information obtained via the DCI when generating the RA-RNTI with the equation.

Clause 12: a method for wireless communication by a network entity, comprising: receiving a Physical Random Access Channel (PRACH) preamble from a User Equipment (UE) in a Random Access Channel (RACH) occasion (RO) within a RACH slot; generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH was transmitted and a plurality of RACH slots in a frame; and processing a Random Access Response (RAR) message transmitted from the network entity to the UE in response to the PRACH preamble using the RA-RNTI.

Clause 13: the method of clause 12, wherein the RACH slots have a duration based on a first subcarrier spacing (SCS) and the number of RACH slots is the same as the number of RACH slots corresponding to a second SCS.

Clause 14: the method of clause 13, wherein the RA-RNTI is generated using an equation with parameters corresponding to a first time slot based on a parameter set of the second SCS of the RO in which the PRACH preamble is transmitted.

Clause 15: the method of any of clauses 12-14, wherein the number of ROs configured exceeds the RO capacity of one or more configured RACH slots defined within a reference slot, and the UE identifies one or more additional RACH slots within the reference slot.

Clause 16: the method of clause 15, wherein the RA-RNTI is generated using an equation involving parameters corresponding to an index of a first symbol of the RO in which the PRACH preamble is transmitted within the configured or additional RACH slot.

Clause 17: the method of any one of clauses 15 and 16, wherein the PRACH preamble is transmitted in an RO selected from a set of ROs spanning multiple slots corresponding to a first subcarrier spacing (SCS), and the RA-RNTI is generated using an equation involving parameters of an index corresponding to a first symbol of the RO, wherein the PRACH preamble is transmitted within one or more slots spanned by the set of ROs.

Clause 18: the method of clause 17, wherein a value of the parameter corresponding to the index of the first symbol can be greater than a number of symbols within a slot.

Clause 19: the method of any one of clauses 17 and 18, wherein the equation further relates to a parameter corresponding to a first time slot based on a parameter set of a second SCS of the RO in which the PRACH preamble is transmitted.

Clause 20: the method of any of clauses 17-19, further comprising: transmitting Downlink Control Information (DCI) scheduling the RAR message; and using information transmitted via the DCI when generating the RA-RNTI with the equation.

Clause 21: an apparatus, comprising: a memory, the memory comprising executable instructions; one or more processors configured to execute the executable instructions and cause the apparatus to perform the method according to any one of clauses 1-20.

Clause 22: an apparatus comprising means for performing the method of any one of clauses 1 to 20.

Clause 23: a non-transitory computer-readable medium comprising: executable instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method according to any one of clauses 1 to 20.

Clause 24: a computer program product embodied on a computer readable storage medium, comprising code for performing the method of any of clauses 1 to 20.

Clause 25: a method for wireless communication by a User Equipment (UE), comprising: receiving a Random Access Channel (RACH) configuration configuring a plurality of RACH Occasions (ROs) for the UE; identifying one or more additional RACH slots within a reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and transmitting a Physical RACH (PRACH) preamble in the RO in one of the configured RACH slots or the additional RACH slots.

Clause 26: the method of clause 25, wherein the duration of the reference time slot is defined by a first subcarrier spacing and the duration of each of the configured RACH time slot and the additional RACH time slot is defined by a second subcarrier spacing.

Clause 27: the method of any of clauses 25 and 26, wherein the RACH configuration indicates a location of the additional RACH slot within the reference slot.

Clause 28: the method of any of clauses 25-27, wherein the location of the additional RACH slots results in the configured and additional RACH slots being distributed according to a predefined pattern within the reference slots.

Clause 29: the method of any of clauses 25-28, wherein the location of each additional RACH slot is adjacent to the configured RACH slot.

Clause 30: the method of any of clauses 25-29, wherein the additional RACH slots are used for additional ROs or beams in addition to the ROs or beams associated with the configured RACH slots.

Clause 31: the method of any of clauses 25 to 30, wherein the additional RACH slot is used for repetition of an existing RO or beam associated with the configured RACH slot.

Clause 32: the method of clause 31, wherein the additional RACH slots are used for additional ROs or beams in addition to the ROs or beams associated with the configured RACH slots.

Clause 33: a method for wireless communication by a network entity, comprising: transmitting, to a User Equipment (UE), a Random Access Channel (RACH) configuration configuring a plurality of RACH Occasions (ROs) for the UE; identifying one or more additional RACH slots within a reference slot when the number of configured ROs exceeds the RO capacity of one or more configured RACH slots defined within the reference slot; and monitoring the configured RACH slots and ROs in the additional RACH slots for a Physical RACH (PRACH) preamble from the UE.

Clause 34: the method of clause 33, wherein the duration of the reference slot is defined by a first subcarrier spacing and the duration of each of the configured RACH slot and the additional RACH slot is defined by a second subcarrier spacing.

Clause 35: the method of any of clauses 33 and 34, wherein the RACH configuration indicates a location of the additional RACH slot within the reference slot.

Clause 36: the method of any of clauses 33 to 35, wherein the location of the additional RACH slots results in the configured and additional RACH slots being distributed according to a predefined pattern within the reference slots.

Clause 37: the method of any of clauses 33-36, wherein the location of each additional RACH slot is adjacent to the configured RACH slot.

Clause 38: the method of any of clauses 33 to 37, wherein the additional RACH slots are used for additional ROs or beams in addition to the ROs or beams associated with the configured RACH slots.

Clause 39: the method of any of clauses 33 to 38, wherein the additional RACH slot is used for repetition of an existing RO or beam associated with the configured RACH slot.

Clause 40: the method of clause 39, wherein the additional RACH slots are used for additional ROs or beams in addition to the ROs or beams associated with the configured RACH slots.

Clause 41: an apparatus, comprising: a memory, the memory comprising executable instructions; one or more processors configured to execute the executable instructions and cause the apparatus to perform the method according to any one of clauses 25-40.

Clause 42: an apparatus comprising means for performing the method of any one of clauses 25 to 40.

Clause 43: a non-transitory computer-readable medium comprising: executable instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method according to any one of clauses 25 to 40.

Clause 44: a computer program product embodied on a computer-readable storage medium, comprising code for performing the method of any of clauses 25-40.

Additional wireless communication network considerations

The techniques and methods described herein may be used for various wireless communication networks (or Wireless Wide Area Networks (WWANs)) and Radio Access Technologies (RATs). Although aspects may be described herein using terms commonly associated with 3G, 4G, and/or 5G (e.g., 5G new air interface (NR)) wireless technologies, aspects of the present disclosure may be equally applicable to other communication systems and standards not explicitly mentioned herein.

The 5G wireless communication network may support various advanced wireless communication services, such as enhanced mobile broadband (eMBB), millimeter wave (mmWave), machine Type Communication (MTC), and/or mission critical ultra-reliable, low latency communication (URLLC). These services and other services may include latency and reliability requirements.

Returning to fig. 1, aspects of the present disclosure may be performed within an example wireless communication network 100.

In 3GPP, the term "cell" can refer to a coverage area of a node B and/or a narrowband subsystem serving the coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and BS, next generation node B (gNB or gNodeB), access Point (AP), distributed Unit (DU), carrier wave or transmission-reception point may be used interchangeably. The BS may provide communication coverage for macro cells, pico cells, femto cells, and/or other types of cells.

A macro cell may typically cover a relatively large geographical area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. The pico cell may cover a relatively small geographic area (e.g., a gym) and may allow unrestricted access by UEs with service subscription. 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) and UEs of users in the home). The BS for the macro cell may be referred to as a macro BS. The BS for the pico cell may be referred to as a pico BS. The BS for the femto cell may be referred to as a femto BS, a home BS, or a home node B.

A base station 102 configured for 4G LTE, collectively referred to as an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with the EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G (e.g., 5G NR or next generation RAN (NG-RAN)) may interface with the 5gc 190 over the second backhaul link 184. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC 160 or 5gc 190) over a third backhaul link 134 (e.g., an X2 interface). The third backhaul link 134 may be generally wired or wireless.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same 5GHz unlicensed spectrum as used by the Wi-Fi AP 150. The use of NR small cells 102' in the unlicensed spectrum may improve coverage to the access network and/or increase the capacity of the access network.

Some base stations, such as the gNB 180, may operate in a conventional below 6GHz spectrum, millimeter wave (mmWave) frequencies, and/or frequencies near mmWave to communicate with the UE 104. When the gNB 180 operates in mmWave or frequencies near mmWave, the gNB 180 may be referred to as a mmWave base station.

The communication link 120 between the base station 102 and, for example, the UE 104 may be over one or more carriers. For example, for each carrier allocated in carrier aggregation up to yxmhz (x component carriers) in total for transmission in each direction, base station 102 and UE 104 may use a spectrum up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, and other MHz) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

The wireless communication system 100 further includes a Wi-Fi Access Point (AP) 150 that communicates with Wi-Fi Stations (STAs) 152 via a communication link 154 in, for example, the 2.4GHz and/or 5GHz unlicensed spectrum. When communicating in the unlicensed spectrum, STA 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communication to determine whether a channel is available.

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems such as, for example, FLASHLINQ, WIMEDIA, bluetooth, zigBee, wi-Fi based on the IEEE 802.11 standard, 4G (e.g., LTE), or 5G (e.g., NR), just to name a few options.

EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172.MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, MME 162 provides bearer and connection management.

In general, user Internet Protocol (IP) packets are communicated through a serving gateway 166, which itself is connected to a PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services.

The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may be used as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The 5gc 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196.

The AMF 192 is typically a control node that handles signaling between the UE 104 and the 5gc 190. In general, AMF 192 provides QoS flows and session management.

All user Internet Protocol (IP) packets are delivered through the UPF 195, which connects to the IP service 197 and provides IP address assignment for the UE as well as other functions for the 5gc 190. The IP services 197 may include, for example, the internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming media services, and/or other IP services.

Returning to fig. 2, various example components of BS102 and UE 104 (e.g., wireless communication network 100 of fig. 1) that may be used to implement aspects of the present disclosure are depicted.

At BS102, a transmit processor 220 may receive data from a data source 212 and control information from a controller/processor 240. The control information may be for a Physical Broadcast Channel (PBCH), a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a Physical Downlink Control Channel (PDCCH), a group common PDCCH (GC PDCCH), and so on. In some examples, the data may be for a Physical Downlink Shared Channel (PDSCH).

A Medium Access Control (MAC) -control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes. The MAC-CE may be carried in a shared channel, such as a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Shared Channel (PUSCH), or a physical side link shared channel (PSSCH).

Processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmission processor 220 may also generate reference symbols, such as for a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to Modulators (MODs) of transceivers 232a through 232 t. Each modulator in transceivers 232a through 232t may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators in transceivers 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

At the UE 104, antennas 252a through 252r may receive the downlink signals from BS102 and may provide the received signals to demodulators (DEMODs) in transceivers 254a through 254r, respectively. Each demodulator in transceivers 254 a-254 r may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM) to obtain received symbols.

MIMO detector 256 may obtain received symbols from all of the demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 260, and provide decoded control information to a controller/processor 280.

On the uplink, at the UE 104, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a Physical Uplink Shared Channel (PUSCH)) and control information from a controller/processor 280 (e.g., for a Physical Uplink Control Channel (PUCCH)). The transmission processor 264 may also generate reference symbols for a reference signal (e.g., a Sounding Reference Signal (SRS)). The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators in transceivers 254a through 254r (e.g., for SC-FDM), and transmitted to BS102.

At BS102, uplink signals from UE 104 may be received by antennas 234a-t, processed by demodulators in transceivers 232a through 232t, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 104. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240.

Memory 242 and memory 282 may store data and program codes for BS102 and UE 104, respectively.

The scheduler 244 may schedule UEs for data transmission on the downlink and/or uplink.

The 5G may utilize Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on uplink and downlink. 5G may also support half duplex operation using Time Division Duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones and bins. Each subcarrier may be modulated with data. The modulation symbols may be transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The interval between adjacent subcarriers may be fixed and the total number of subcarriers may depend on the system bandwidth. In some examples, the minimum resource allocation, referred to as a Resource Block (RB), may be 12 consecutive subcarriers. The system bandwidth may also be divided into a plurality of sub-bands. For example, one subband may cover multiple RBs. NR may support a 15KHz base subcarrier spacing (SCS) and other SCSs may be defined relative to the base SCS (e.g., 30KHz, 60KHz, 120KHz, 240KHz, etc.).

As described above, fig. 3A-3D depict various example aspects of a data structure for a wireless communication network, such as wireless communication network 100 of fig. 1.

In various aspects, the 5G frame structure may be Frequency Division Duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to DL or UL. The 5G frame structure may also be Time Division Duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to both DL and UL. In the example provided by fig. 3A and 3C, the 5G frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (mostly DL) and subframe 3 configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is flexible for use between DL/UL. Although subframes 3,4 are shown in slot formats 34, 28, respectively, any particular subframe may be configured with any of a variety of available slot formats 0-61. The slot formats 0, 1 are DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with a slot format (dynamically configured by DL Control Information (DCI) or semi-statically/statically configured by Radio Resource Control (RRC) signaling) through a received Slot Format Indicator (SFI). Note that the following description also applies to a 5G frame structure that is TDD.

Other wireless communication technologies may have different frame structures and/or different channels. One frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. In some examples, each slot may include 7 or 14 symbols, depending on the slot configuration.

For example, for slot configuration 0, each slot may include 14 symbols, while for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) -spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to single stream transmission).

The number of slots within a subframe is based on a slot configuration and a parameter set. For slot configuration 0, different parameter sets (μ) 0 through 5 allow 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols/slot and 2 μ slots/subframe. The subcarrier spacing and symbol length/duration are a function of the parameter set. The subcarrier spacing may be equal to 2 ^μ x 15kHz, where μ is the parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, while parameter set μ=5 has a subcarrier spacing of 480 kHz. The symbol length/duration is inversely related to the subcarrier spacing. Fig. 3A to 3D provide examples of a slot configuration 0 having 14 symbols per slot and a parameter set μ=2 having 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67 mus.

The resource grid may be used to represent a frame structure. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As shown in fig. 3A, some REs carry reference (pilot) signals (RSs) for UEs (e.g., UE 104 of fig. 1 and 2). The RSs may include demodulation RSs (DM-RSs) (indicated as Rx for one particular configuration, where 100x is a port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

Fig. 3B shows an example of various DL channels within a subframe of a frame. A Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol.

The Primary Synchronization Signal (PSS) may be within symbol 2 of a particular subframe of a frame. PSS is used by UEs (e.g., 104 of fig. 1 and 2) to determine subframe/symbol timing and physical layer identity.

The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block. The MIB provides the number of RBs in the system bandwidth and a System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) that are not transmitted over the PBCH, and paging messages.

As shown in fig. 3C, some REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for a Physical Uplink Control Channel (PUCCH) and DM-RS for a Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous or the previous two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations according to whether the short PUCCH or the long PUCCH is transmitted and according to a specific PUCCH format used. The UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency dependent scheduling of the UL.

Fig. 3D illustrates examples of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and HARQ ACK/NACK feedback. PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.

Additional considerations

The foregoing description provides an example of transmitting a Random Access (RA) radio network temporary identifier (RA-RNTI) for a higher frequency subcarrier spacing (SCS), such as 480kHz and 960 kHz. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited in scope, applicability, or aspect to the description set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, replace, or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or both in addition to or instead of the aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

The techniques described herein may be used for various wireless communication techniques such as 5G (e.g., 5 GNR), 3GPP Long Term Evolution (LTE), LTE-advanced (LTE-a), code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. TDMA networks may implement radio technologies such as global system for mobile communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5 GRA), evolved UTRA (E-UTRA), ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and LTE-a are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-a and GSM are described in documents from an organization named "third generation partnership project" (3 GPP). Cdma2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3 GPP 2). NR is an emerging wireless communication technology being developed.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including processors, machine-readable media, and bus interfaces. The bus interface may be used to connect a network adapter or the like to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user equipment (see fig. 1), a user interface (e.g. keypad, display, mouse, joystick, touch screen, biometric sensor, proximity sensor, light emitting element, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. A processor may be implemented using one or more general-purpose processors and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality of the processing system depending on the particular application and the overall design constraints imposed on the overall system.

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general-purpose processing, including the execution of software modules stored on a machine-readable storage medium. A computer readable storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, machine-readable media may comprise a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium having instructions stored thereon, separate from the wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or in addition, the machine-readable medium or any portion thereof may be integrated into the processor, such as in the case of having a cache and/or general purpose register file. By way of example, a machine-readable storage medium may comprise RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, a magnetic disk, an optical disk, a hard disk drive, or any other suitable storage medium or any combination thereof. The machine-readable medium may be embodied by a computer program product.

A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer readable medium may include several software modules. The software modules include instructions that, when executed by an apparatus, such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a reception module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, when a trigger event occurs, the software module may be loaded from the hard disk drive into RAM. During execution of the software module, the processor may load some of the instructions into the cache to increase access speed. One or more cache lines may then be loaded into a general purpose register file for execution by the processor. When reference is made below to the functionality of a software module, it will be understood that such functionality is implemented by the processor when executing instructions from the software module.

As used herein, the term "exemplary" means "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.

As used herein, a phrase referring to "at least one item in a list of items" refers to any combination of these items (which includes a single member). As an example, at least one of "a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple identical elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so forth. Further, "determining" may include parsing, selecting, choosing, establishing, and so forth.

The methods disclosed herein comprise one or more steps or actions for achieving the method. The steps and/or actions of the methods may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. The component may include various hardware and/or software components and/or modules including, but not limited to, a circuit, an Application Specific Integrated Circuit (ASIC), or a processor. Generally, where there are operations shown in the figures, those operations may have corresponding elements plus features with like numbers.

The following claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims. Within the claims, reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more. The term "some" means one or more unless specifically stated otherwise. No claim element should be construed in accordance with the specification of 35u.s.c. ≡112 (f) unless the element is explicitly recited using the phrase "means for..once again, or in the case of method claims, the phrase" step for..once again. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims (22)

1. A User Equipment (UE) configured for wireless communication, comprising:

A memory including computer-executable instructions; and

A processor configured to execute the computer-executable instructions and cause the UE to:

Transmitting a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot;

Generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds the RO capacity of one or more configured RACH slots defined within a reference slot; and

The RA-RNTI is used to process a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble.

2. The UE of claim 1, wherein:

The RACH slot having a duration based on a first subcarrier spacing (SCS); and

The number of RACH slots is the same as the number of RACH slots corresponding to the second SCS.

3. The UE of claim 2, wherein the processor configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI using an equation having parameters corresponding to a first time slot based upon a parameter set of the second SCS of the RO in which the PRACH preamble is transmitted.

4. The UE of claim 1, wherein:

The number of ROs configured exceeds the RO capacity of one or more configured RACH slots defined within a reference slot; and

The processor is configured to execute the computer-executable instructions and further cause the UE to identify one or more additional RACH slots within the reference slot.

5. The UE of claim 4, wherein the processor configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI using an equation involving a parameter corresponding to an index of a first symbol of the RO within a configured or additional RACH slot in which the PRACH preamble is transmitted.

6. The UE of claim 4, wherein the processor configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI using an equation having parameters corresponding to a first time slot based upon a parameter set of a second SCS of the RO in which the PRACH preamble is transmitted.

7. The UE of claim 4, wherein:

the processor configured to execute the computer-executable instructions to cause the UE to transmit the PRACH preamble comprises: the processor is configured to execute the computer-executable instructions to cause the UE to transmit the PRACH preamble in an RO selected from a group of ROs spanning a plurality of slots corresponding to a first subcarrier spacing (SCS); and

The processor configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the UE to generate the RA-RNTI using an equation involving a parameter corresponding to an index of a first symbol of the RO in which the PRACH preamble is transmitted within one or more slots spanned by the set of ROs.

8. The UE of claim 7, wherein a value of the parameter corresponding to the index of the first symbol can be greater than a number of symbols within a slot.

9. The UE of claim 7, wherein the equation further relates to a parameter corresponding to a first time slot based on a parameter set of a second SCS of the RO in which the PRACH preamble is transmitted.

10. The UE of claim 7, wherein the processor is configured to execute the computer-executable instructions and further cause the UE to select the RO in which the PRACH preamble is transmitted to avoid generating RA-RNTI with a reserved value.

11. The UE of claim 7, wherein the processor is configured to execute the computer-executable instructions and further cause the UE to:

receiving Downlink Control Information (DCI) scheduling the RAR message; and

When the RA-RNTI is generated with the equation, information obtained via the DCI is used.

12. A network entity configured for wireless communication, comprising:

A memory including computer-executable instructions; and

A processor configured to execute the computer-executable instructions and cause the network entity to:

Receiving a Physical Random Access Channel (PRACH) preamble from a User Equipment (UE) in a Random Access Channel (RACH) occasion (RO) within a RACH slot;

Generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH was transmitted and a number of RACH slots in a frame; and

A Random Access Response (RAR) message transmitted from the network entity to the UE in response to the PRACH preamble is processed using the RA-RNTI.

13. The network entity of claim 12, wherein:

The RACH slot having a duration based on a first subcarrier spacing (SCS); and

The number of RACH slots is the same as the number of RACH slots corresponding to the second SCS.

14. The network entity of claim 13, wherein the processor configured to execute the computer-executable instructions to cause the network entity to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the network entity to generate the RA-RNTI using an equation having parameters corresponding to a first time slot based upon a set of parameters of the second SCS of the RO in which the PRACH preamble is transmitted.

15. The network entity of claim 12, wherein:

the number of ROs configured exceeds the RO capacity of one or more RACH slots configured as defined within the reference slot; and

The UE identifies one or more additional RACH slots within the reference slot.

16. The network entity of claim 15, wherein the processor configured to execute the computer-executable instructions to cause the network entity to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the network entity to generate the RA-RNTI using an equation involving a parameter corresponding to an index of a first symbol of the RO within a configured or additional RACH slot in which the PRACH preamble is transmitted.

17. The network entity of claim 15, wherein:

transmitting the PRACH preamble in an RO selected from a group of ROs spanning a plurality of slots corresponding to a first subcarrier spacing (SCS); and

The processor configured to execute the computer-executable instructions to cause the network entity to generate the RA-RNTI comprises: the processor is configured to execute the computer-executable instructions to cause the network entity to generate the RA-RNTI using an equation involving a parameter corresponding to an index of a first symbol of the RO in which the PRACH preamble is transmitted within one or more slots spanned by the set of ROs.

18. The network entity of claim 17, wherein a value of the parameter corresponding to the index of the first symbol can be greater than a number of symbols within a slot.

19. The network entity of claim 17, wherein the equation further relates to a parameter corresponding to a first time slot based on a parameter set of a second SCS of the RO in which the PRACH preamble is transmitted.

20. The network entity of claim 17, wherein the processor is configured to execute the computer-executable instructions and further cause the network entity to:

transmitting Downlink Control Information (DCI) scheduling the RAR message; and

When generating the RA-RNTI with the equation, information transmitted via the DCI is used.

21. A method for wireless communication by a User Equipment (UE), comprising:

Transmitting a Physical Random Access Channel (PRACH) preamble to a network entity in a Random Access Channel (RACH) occasion (RO) within a RACH slot;

Generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH is transmitted and whether the configured number of ROs exceeds the RO capacity of one or more configured RACH slots defined within a reference slot; and

The RA-RNTI is used to process a Random Access Response (RAR) message transmitted from the network entity in response to the PRACH preamble.

22. A method for wireless communication by a network entity, comprising:

Receiving a Physical Random Access Channel (PRACH) preamble from a User Equipment (UE) in a Random Access Channel (RACH) occasion (RO) within a RACH slot;

Generating a random access radio network temporary identifier (RA-RNTI) based at least in part on the RO in which the PRACH was transmitted and a number of RACH slots in a frame; and

A Random Access Response (RAR) message transmitted from the network entity to the UE in response to the PRACH preamble is processed using the RA-RNTI.