Waveform support capability signaling during initial access
By sending supported downlink waveform information in the wireless communication system by UE, signal attenuation and blocking problems are solved, data rate and spectrum efficiency of the wireless communication system are improved, and communication performance is enhanced.
Patent Information
- Application Number
- CN202380033225.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-22
- Filing Date
- 2023-03-23
- Publication Date
- 2024-11-19
AI Technical Summary
The existing wireless communication systems have signal attenuation or blocking problems in complex and dynamic environments, resulting in insufficient communication performance, and need to improve communication speed, data carrying capacity, power efficiency and reliability.
User equipment (UE) sends supported downlink waveform information to network entities through random access channel (RACH) messages, and receives downlinks using these waveforms from network entities, supporting a variety of waveforms such as DFT-S-OFDM and CP-OFDM, optimizes initial access procedures to improve data rate and spectrum efficiency.
It improves the data rate and spectrum efficiency of wireless communication systems, enhances communication performance in high energy efficiency scenarios, and is suitable for a variety of wireless communication networks.
Smart Images

Figure CN118985121A_ABST
Abstract
Description
Background Art
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of and priority to U.S. Patent Application No. 17 / 660,368, filed on April 22, 2022, which is incorporated herein by reference in its entirety. Technical Field
[0003] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for signaling downlink waveform support capabilities during an initial access procedure.
[0004] Related technologies
[0005] 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 technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with the multiple users.
[0006] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continuous desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention
[0007] One aspect provides a method of wireless communication by a user equipment (UE). The method includes: sending information indicating one or more downlink waveforms supported by the UE to a network entity via one or more random access channel (RACH) messages; and receiving one or more downlink transmissions using the one or more downlink waveforms supported by the UE from the network entity.
[0008] Another aspect provides a method of wireless communication by a network entity. The method includes: receiving information indicating one or more downlink waveforms supported by the UE from a UE via one or more RACH messages; and sending one or more downlink transmissions using the one or more downlink waveforms supported by the UE to the UE.
[0009] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those 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 / or an apparatus comprising components for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.
[0010] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The accompanying drawings depict certain features of the aspects described herein and should not be considered to limit the scope of the disclosure.
[0012] Figure 1 An example wireless communication network is depicted.
[0013] Figure 2 An example decomposed base station (BS) architecture is depicted.
[0014] Figure 3 Aspects of an example BS and example user equipment (UE) are depicted.
[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.
[0016] Figure 5 An example 5th generation (5G) New Radio (NR) waveform is depicted.
[0017] Figure 6 An example single carrier (SC) waveform is depicted.
[0018] Fig. 7A A four-step random access channel (RACH) procedure is depicted.
[0019] Figure 7B Depicted are RACH messages exchanged between a UE and a network entity during a four-step RACH procedure.
[0020] Fig. 8A A two-step RACH procedure is depicted.
[0021] Figure 8B Depicted are RACH messages exchanged between a UE and a network entity during a two-step RACH procedure.
[0022] 9A to 9C An example process flow for communications in a network between a UE and a network entity is depicted.
[0023] Fig.10 Methods for wireless communications by a UE are described.
[0024] Fig.11 Methods for wireless communications by a network entity are described.
[0025] Fig.12 Aspects of an example communications device are depicted.
[0026] Fig.13 Aspects of an example communications device are depicted. DETAILED DESCRIPTION
[0027] When a user equipment (UE) initially accesses a network entity, a random access procedure (RACH) is performed. The RACH procedure is a multi-step procedure and may be performed using one of a number of waveforms, such as a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-S-OFDM) waveform, a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, and / or other waveforms.
[0028] By default, some UEs may only support CP-OFDM waveforms. Since different waveforms may be used to perform RACH procedures and some UEs may only support CP-OFDM waveforms by default, the UE is required to signal (e.g., via UE capability information) whether a single carrier (SC) waveform (e.g., a DFT-S-OFDM waveform) is also supported by the UE.
[0029] Various aspects of the present disclosure provide mechanisms for signaling a UE's ability to support multiple waveforms. For example, in some cases, a UE may indicate: (i) support for the SC waveform in the downlink (i.e., whether the UE has a transceiver for the DFT-S-OFDM waveform during an initial access procedure), (ii) the switching time between two waveforms (e.g., a DFT-S-OFDM waveform and a CP-OFDM waveform) during an initial access procedure, and / or (iii) a preference for using a specific waveform (e.g., a DFT-S-OFDM waveform or a CP-OFDM waveform) during an initial access procedure.
[0030] In some cases, signaling the UE's ability to support multiple different waveforms (e.g., via a physical RACH (PRACH) preamble, mask, and / or other techniques) may result in higher data rates and spectral efficiency. For example, in some scenarios where higher energy efficiency may be required, the UE capabilities may indicate support and preference for a DFT-S-OFDM waveform (e.g., suitable for power efficient transmission and having a low peak-to-average power ratio (PAPR)) over a CP-OFDM waveform. The lower PAPR of the DFT-S-OFDM waveform translates into higher power added (PA) efficiency and data rates.
[0031] Introduction to wireless communication networks
[0032] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.
[0033] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.
[0034] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and user equipment.
[0035] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interoperate to provide communication services over various communication links (including wired and wireless links).
[0036] Figure 1 Various example UEs 104 are depicted, which may more generally 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 computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.
[0037] BS 102 wirelessly communicates with (e.g., transmits signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.
[0038] BS 102 may generally include: a Node B, an enhanced Node B (eNB), a next generation enhanced Node B (ng-eNB), a next generation Node B (gNB or gNodeB), an access point, a base transceiver, a radio base station, a radio transceiver, a transceiver function, a transmission and reception point, and / or the like. Each of BS 102 may provide communication coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with a coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (a relatively small geographic area (e.g., a home)), and / or other types of cells.
[0039] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functions similar to those of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.
[0040] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.
[0041] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 GHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.
[0042] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various aspects. 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 compared to UL).
[0043] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Therefore, some base stations (e.g. Figure 1 180) can utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels and / or antenna arrays) to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 may also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. It is worth noting that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or different.
[0044] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.
[0045] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).
[0046] The EPC 160 may include various functional components, including: 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 / or a packet data network (PDN) gateway 172, such as in the depicted example. The 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, the MME 162 provides bearer and connection management.
[0047] Typically, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.
[0048] The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0049] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.
[0050] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.
[0051] Internet Protocol (IP) packets are delivered through UPF 195, which connects to IP Services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.
[0052] The wireless communication network 100 also includes a random access channel (RACH) component 198, which can be configured to perform Fig.10 The wireless communication network 100 also includes a RACH component 199, which can be configured to perform Fig.11 Method 1100.
[0053] In various aspects, a network entity or network node may be implemented as a converged BS, a decomposed BS, a component of a BS, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.
[0054] Figure 2 An example decomposed BS 200 architecture is depicted. The decomposed BS 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed BS units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.
[0055] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, a unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.
[0056] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 210. CU210 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.
[0057] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional partition, such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.
[0058] The lower layer functions may be implemented by one or more RUs 240. In some deployments, a RU 240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and the CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0059] The SMO framework 205 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via an O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RU240 via an O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .
[0060] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.
[0061] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0062] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.
[0063] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.
[0064] BS 102 includes a controller / processor 340 that can be configured to perform various functions related to wireless communication. In the depicted example, controller / processor 340 includes a RACH component 341, which can represent Figure 1 RACH component 199 of BS 102. It is worth noting that, although depicted as an aspect of controller / processor 340, in other specific implementations, RACH component 341 can additionally or alternatively be implemented in various other aspects of BS 102.
[0065] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.
[0066] UE 104 includes a controller / processor 380 that can be configured to perform various functions related to wireless communication. In the depicted example, the controller / processor 380 includes a RACH component 381, which can represent Figure 1 The SCI component 198 of the UE 104. It is worth noting that while depicted as an aspect of the controller / processor 380, in other specific implementations, the RACH component 381 can additionally or alternatively be implemented in various other aspects of the UE 104.
[0067] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).
[0068] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 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).
[0069] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-decoding) on data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 332a to 332t. Each modulator in transceivers 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a to 332t may be transmitted via antennas 334a to 334t, respectively.
[0070] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.
[0071] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.
[0072] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.
[0073] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.
[0074] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.
[0075] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.
[0076] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.
[0077] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, and / or other aspects described herein.
[0078] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.
[0079] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).
[0080] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4DFIG480 is a diagram illustrating an example of UL channels within a 5G subframe.
[0081] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.
[0082] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.
[0083] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X can be used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include a micro-time slot, which typically has fewer symbols than a whole time slot. Other wireless communication technologies may have different frame structures and / or different channels.
[0084] In certain aspects, the number of time slots within a subframe is based on the time slot configuration and the parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Thus, for time slot configuration 0 and parameter set μ, there are 14 symbols / time slot and 2μ time slots / subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, while parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.
[0085] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted in , a resource grid can be used to represent a frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending, for example, 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.
[0086] like Figure 4A As illustrated, some of the REs carry data for UEs (eg, Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).
[0087] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.
[0088] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.
[0089] The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.
[0090] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.
[0091] As in Figure 4C As illustrated in , some REs carry DMRS for channel estimation at the base station (indicated as R for one particular configuration, but other DMRS configurations are possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs in the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.
[0092] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0093] Example 5th Generation (5G) New Radio (NR) Waveform
[0094] To improve throughput and increase the amount of data being transferred, user equipment (UE) is equipped to use (eg Figure 5 ) such as a discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM) waveform, a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, and / or other waveforms.
[0095] The CP-OFDM waveform is used for single stream transmission and / or multi-stream (e.g., multiple input multiple output (MIMO)) transmission. The CP-OFDM waveform is supported for higher frequency bands (e.g., FR4 and beyond FR4). The CP-OFDM waveform is backward compatible with the FR1 / FR2 / FR2x waveform. The CP-OFDM waveform provides a high signal-to-noise ratio (SNR) and high-order MIMO. The CP-OFDM waveform is also suitable for achieving high data rates. In some scenarios (e.g., where energy efficiency requirements are more relaxed), the CP-OFDM waveform provides high spectral efficiency.
[0096] The DFT-S-OFDM waveform is a single carrier (SC) waveform and is therefore limited to single stream transmission (e.g., link budget limited situations). The DFT-S-OFDM waveform provides a low peak-to-average power ratio (PAPR). The DFT-S-OFDM waveform is suitable for power efficient transmission, such as coverage / transmit power limited scenarios.
[0097] DFT-S-OFDM waveforms are supported for scenarios requiring high energy efficiency. For example, lower PAPR translates into higher power added (PA) efficiency. High data rates can also be achieved due to large-scale spectrum availability. In some cases, to facilitate frequency domain equalization, a cyclic prefix (CP) is introduced to create OFDM-like blocks or symbols. In addition, the guard interval (GI), which is a known sequence, can be considered as a special case of CP in this context.
[0098] Based on the frequency domain transform pre-coding at the transmitter and the frequency domain equalization at the receiver, the DFT-S-OFDM waveform (e.g., in the frequency domain implementation) has a relatively high complexity. The DFT-S-OFDM waveform has a more efficient bandwidth utilization than SC Quadrature Amplitude Modulation (SC-QAM). The DFT-S-OFDM waveform provides more flexible bandwidth allocation and therefore easily supports large bandwidths.
[0099] SC-QAM (e.g., in a time-domain implementation) has low complexity based on time-domain filtering (e.g., pulse shaping filters at the transmitter and matched filtering / time-domain equalization at the receiver). DFT-S-OFDM waveforms have more bandwidth increase (e.g., through time-domain filtering) and require guard bands (e.g., as Figure 6 The DFT-S-OFDM waveform provides a restricted bandwidth allocation and thus increases the complexity of supporting various different bandwidth allocations.
[0100] Example Random Access Channel (RACH) Procedure
[0101] In order to connect a user equipment (UE) to a 5th generation (5G) network, the UE must be synchronized in the downlink as well as the uplink. Downlink synchronization is obtained after successfully decoding the synchronization signal block (SSB). To establish uplink synchronization and a radio resource control (RRC) connection, the UE performs a random access channel (RACH) procedure.
[0102] The RACH procedure may be performed in certain scenarios including during transition from idle mode to connected mode, intra-system handover, RRC connection re-establishment, and / or when uplink / downlink data arrives while the UE is in an asynchronous state.
[0103] The RACH procedure can be contention-based or non-contention-based. The contention-based RACH procedure involves the UE selecting the physical RACH (PRACH) resources. The non-contention-based RACH procedure involves allocating a narrowband (NB) of resources to the UE.
[0104] The RACH procedure may be a multi-step procedure or have multiple stages. For example, the RACH procedure may include a four-step RACH procedure or a two-step RACH procedure.
[0105] Fig. 7A and Figure 7B An example four-step RACH procedure at a UE is illustrated. Initially, the network entity transmits the SSB to the UE for downlink synchronization. The SSB includes the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and the physical broadcast channel (PBCH). The network entity also transmits the system information block #1 (SIB1) to the UE. SIB1 carries information that is relevant when evaluating whether the UE is allowed to access the cell and defines the scheduling of other system information.
[0106] To establish uplink synchronization, the UE performs a four-step RACH procedure. For example, the UE sends a message 1 (e.g., MSG1) to a network entity. The UE sends the message 1 using a preamble (also known as a RACH preamble, a PRACH preamble, etc.) selected from different RACH preambles. The UE also sends an identity of the UE to the network entity so that the network entity can address the UE in the next operation. The identity used by the UE can be a random access radio network temporary identifier (RA-RNTI) determined according to the time slot number in which the RACH preamble or sequence is transmitted.
[0107] The UE receives a message 2 (e.g., MSG2) from a network entity (e.g., via a physical downlink shared channel (PDSCH)). In response to transmitting message 1 to the network entity, the UE receives message 2. Message 2 may be a random access response (RAR) and is received from the network entity on a downlink shared channel (DL-SCH). The RAR may be addressed to a RA-RNTI calculated by the network entity based on the time slot in which the preamble or sequence is transmitted. Message 2 may also carry the following information: a cell radio network temporary identifier (C-RNTI) that may be used for additional communications between the UE and the network entity; a timing advance value that informs the UE to change the timing of the UE to compensate for a round-trip delay due to a distance between the UE and the network entity; and / or uplink granted resources that may be initial resources assigned to the UE by the network entity so that the UE may use an uplink shared channel (UL-SCH) during operation.
[0108] The UE sends a message 3 (e.g., MSG3) to the network entity (e.g., via a physical uplink shared channel (PUSCH)). In response to receiving message 2 from the network entity, the UE sends message 3, which may be an "RRC connection request message", to the network entity. The RRC connection request message is transmitted to the network entity using the UL-SCH based on the uplink grant resources granted during the previous operation. When transmitting the RRC connection request message, the UE may use the C-RNTI assigned to the UE by the network entity.
[0109] Message 3 or the RRC Connection Request message includes a UE identity, such as a Temporary Mobile Subscriber Identity (TMSI) or a random value. The TMSI is used to identify the UE in the core network and whether the UE has been previously connected to the same core network. A random value is also used if the UE is connecting to a network entity for the first time. Message 3 may include a connection establishment cause indicating the reason why the UE needs to connect to the network entity.
[0110] The UE receives message 4 (e.g., MSG4) from the network entity (e.g., via PDSCH). If the network entity successfully receives and / or decodes message 3 transmitted from the UE, message 4 is a contention resolution message from the network entity. The network entity sends message 4 to the network entity using the TMSI value of the random number described above, but may also include a new C-RNTI to be used for further communications between the UE and the network entity. When establishing a connection, the UE synchronizes with the network entity using the four-step RACH procedure described above.
[0111] Fig. 8A and Figure 8BAn example two-step RACH procedure at a UE is illustrated.After downlink synchronization (eg, via SSB), the UE performs a two-step RACH procedure for uplink synchronization.
[0112] At step 1, the UE sends a message A (e.g., msgA) to a network entity, which message A is also referred to as the first message of the two-step RACH procedure. Fig. 7A The described messages 1 and 3 may be folded (eg, combined) into a first message and transmitted to a network entity.Message 1 may include a sequence that has been selected from possible sequences and may be used as a reference signal (RS) for demodulating data sent in the first message.
[0113] At step 2, the UE receives a message B (e.g., msgB) from the network entity, which message B is also referred to as the second message of the two-step RACH procedure. In response to transmitting the first message to the network entity, the UE receives the second message. Message B may be as described above with reference to Fig. 7A A combination of described messages 2 and 4. Upon successful reception of message B, the UE may transmit a Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) to the network entity.
[0114] Combining message 1 and message 3 into one message A and receiving message B from the network entity in response allows the UE to reduce the RACH procedure setup time to support the low latency requirements of 5G / NR. Although the UE can be configured to support the two-step RACH procedure, the UE still supports the four-step RACH procedure as a backhaul because the UE may not be able to relay on the two-step RACH procedure due to some constraints (such as high transmit power requirements, etc.). Therefore, the UE in 5G / NR can be configured to support both the two-step RACH procedure and the four-step RACH procedure, and determine which RACH procedure to configure based on the RACH configuration information received from the network entity. Some of the use cases of the two-step RACH procedure may include a transition from the RRC IDLE / INACTIVE state to the RRCCONNECTED state, small data transmission in the RRC IDLE / INACTIVE state, and a handover from a source cell to a target cell under RRC CONNECTED and / or RRC CONNECTED (i.e., the UE recovers uplink synchronization loss).
[0115] The RACH procedure described above may be performed using one of a plurality of waveforms, such as a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-S-OFDM) waveform, a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, and / or other waveforms. The CP-OFDM waveform may be used for single-stream transmission and / or multi-stream (e.g., multiple-input multiple-output (MIMO)) transmission, while the DFT-S-OFDM waveform may be limited to single-stream transmission (e.g., link budget-constrained situations).
[0116] By default, some UEs may only support CP-OFDM waveforms. Since different waveforms may be used to perform RACH procedures and some UEs may only support CP-OFDM waveforms by default, the UE is required to signal (e.g., via UE capability information) whether a single carrier (SC) waveform (e.g., a DFT-S-OFDM waveform) is also supported by the UE.
[0117] Aspects related to waveform support capability signaling during initial access
[0118] Various aspects of the present disclosure provide mechanisms for signaling a user equipment (UE) capability to support multiple waveforms. For example, in some cases, the UE may indicate: (i) support for a single carrier (SC) waveform in the downlink (i.e., whether the user equipment (UE) has a transceiver for a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) waveform during an initial access procedure), (ii) a switching time between two waveforms (e.g., a DFT-S-OFDM waveform and a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform) during an initial access procedure, and / or (iii) a preference for using a specific waveform (e.g., a DFT-S-OFDM waveform or a CP-OFDM waveform) during an initial access procedure.
[0119] In some cases, signaling the UE's ability to support different waveforms may result in higher data rates and spectral efficiency. For example, in some scenarios where higher energy efficiency may be required, the UE capabilities may indicate support and preference for a DFT-S-OFDM waveform (e.g., suitable for power-efficient transmission and having a low peak-to-average power ratio (PAPR)) over a CP-OFDM waveform. The lower PAPR of the DFT-S-OFDM waveform translates into higher power added (PA) efficiency and data rates.
[0120] 9A to 9C A process flow for communication in a network between a network entity and a UE is depicted. In some aspects, the network entity may be related to Figure 1 and Figure 3 Describe and describe BS102 or Figure 2 An example of a decomposed BS is depicted and described. Similarly, a UE may be related to Figure 1 and Figure 3 An example of a UE 104 is depicted and described. However, in other aspects, the UE 104 may be another type of wireless communication device and the BS 102 may be another type of network entity or network node, such as those described herein.
[0121] like Fig.9A As illustrated in FIG. 1 , at 902, the UE sends information indicating one or more downlink waveforms supported by the UE to a network entity via one or more random access channel (RACH) messages. The one or more downlink waveforms may include an SC waveform (e.g., a DFT-S-OFDM waveform) and / or a CP-OFDM waveform. The information may also indicate a switching time gap between different downlink waveforms supported by the UE.
[0122] At 904, the network entity sends one or more downlink transmissions to the UE using one or more downlink waveforms supported by the UE.
[0123] In some aspects, the UE sends information to the network entity via a physical RACH (PRACH) message (e.g., MSG 1) of a four-step RACH procedure. Fig. 9B , at 906, the UE initially selects a PRACH preamble and / or a PRACH opportunity to indicate support for a downlink waveform. At 908, the UE sends a PRACH message to a network entity to indicate support for a downlink waveform (e.g., based on the selected PRACH preamble and / or PRACH opportunity). At 910, the network entity sends a downlink transmission to the UE (e.g., using the indicated downlink waveform supported by the UE).
[0124] In one example, the UE selects a PRACH preamble (e.g., for a PRACH message) from different PRACH preamble / sequence sets. The different PRACH preamble sets may include a first PRACH preamble indicating that the UE supports a specific downlink waveform (e.g., a CP-OFDM waveform or an SC waveform) within one or more downlink waveforms. The different PRACH preamble sets may also include a second PRACH preamble indicating that the UE supports all downlink waveforms (e.g., both CP-OFDM waveforms and SC waveforms).
[0125] In another example, the UE selects a PRACH opportunity (e.g., for a PRACH message) from different PRACH opportunity sets. The different PRACH opportunity sets may include a first PRACH opportunity indicating that the UE supports a specific downlink waveform (e.g., an SC waveform) within one or more downlink waveforms. The different PRACH opportunity sets may also include a second PRACH opportunity indicating that the UE supports all downlink waveforms (e.g., both CP-OFDM waveforms and SC waveforms).
[0126] In some cases, the PRACH message includes one or more PRACH preambles, and the PRACH preamble of each PRACH opportunity is associated with a mask. For example, eight PRACH opportunities can be associated with a synchronization signal block (SSB). The PRACH mask index can be indicated (e.g., by ra-ssb-OccasionMaskIndex). The PRACH mask index indicates a PRACH opportunity for PRACH transmission, where the PRACH opportunity is associated with a selected synchronization signal (SS) / physical broadcast channel (PBCH) block index. In some cases, two mask indexes (e.g., a first mask index (e.g., ra-ssb-OccasionMaskIndex for CP-OFDM waveform and SC waveform support) and a second mask index (e.g., ra-ssb-OccasionMaskIndex for CP-OFDM waveform support)) can be defined so that one set is used for UEs that support SC waveforms in the downlink, and if the UE does not support SC waveforms in the downlink, the other set is used for the UE. The network entity may send the first mask index and all other masks to the UE in an SSB (e.g., as part of a master information block (MIB)) or as part of system information block (SIB) 1. In some cases, the masks may be complementary or orthogonal to uniquely identify the waveform capability.
[0127] In some aspects, the UE sends information to the network entity via a scheduled uplink transmission message (e.g., MSG3) of a four-step RACH procedure (rather than MSG1). This will enable downlink waveform configuration for MSG4 and beyond. In such cases, the switching time gap between the two (or more) downlink waveforms (from the first downlink waveform to the second downlink waveform) is signaled in the MSG3 payload.
[0128] In some aspects, the UE sends information to a network entity via a first message of a two-step RACH procedure (e.g., msgA physical uplink shared channel (PUSCH)). For example, the information is sent in a payload or a PUSCH demodulation reference signal (DMRS) configuration message (e.g., using different DMRS sequences / configurations / ports for different types of downlink waveforms supported by the UE).
[0129] like Fig. 9C , the UE sends a downlink waveform recommendation / preference / request for a specific downlink channel or all downlink channels (or supported downlink waveforms for each frequency band and frequency band combination) to a network entity at 912. The UE may signal the downlink waveform request in a msg3 payload (e.g., in the case of a four-step RACH procedure) or in a msgA payload (e.g., in the case of a two-step RACH procedure).
[0130] In one example, the downlink waveform request may indicate the use of an SC waveform for a downlink grant (DG) physical downlink shared channel (PDSCH) transmission. In another example, the downlink waveform request may indicate the use of a CP-OFDM waveform for a semi-persistent scheduling (SPS) PDSCH transmission. In another example, the downlink waveform request may indicate the use of a first downlink waveform for a physical downlink control channel (PDCCH) transmission and a second downlink waveform for a PDSCH transmission. In another example, the downlink waveform request may indicate the use of a first downlink waveform, a second downlink waveform, and / or a third downlink waveform for a first frequency band. In another example, the downlink waveform request may indicate the use of a first downlink waveform and a second downlink waveform for a second frequency band.
[0131] At 914, the network entity sends a PDCCH transmission using a first downlink waveform based on the received downlink waveform request.
[0132] At 916, the network entity sends a PDSCH transmission using a second downlink waveform based on the received downlink waveform request.
[0133] In some cases, different downlink waveform requests may be triggered based on different conditions. For example, a downlink waveform request may be triggered based on downlink reference signal received power (RSRP) which may indicate the geometry / location of the UE. In one example, a downlink waveform request may indicate a CP-OFDM waveform for a cell center UE and an SC waveform for a cell edge UE.
[0134] Example Operation of User Equipment
[0135] Fig.10 The method for use by a UE such as Figure 1 and Figure 3 Method 1000 for wireless communication with a UE 104. Method 1000 may be implemented as a process in which one or more processors (e.g. Figure 3 In addition, the UE may transmit and receive signals in method 1000 by, for example, one or more antennas (e.g., Figure 3 In some aspects, the transmission and / or reception of signals by the UE may be achieved via a bus interface of one or more processors (eg, controller / processor 380) obtaining and / or outputting signals.
[0136] Method 1000 begins at 1005, where information indicating one or more downlink waveforms supported by the UE is sent to a network entity via one or more RACH messages. In some cases, the operation of this step refers to as described in reference to Fig.12 The described capability signaling circuit and / or capability signaling code may be or may be executed by the capability signaling circuit and / or capability signaling code.
[0137] Method 1000 then proceeds to step 1010, where one or more downlink transmissions using one or more downlink waveforms supported by the UE are received from a network entity. In some cases, the operations of this step are referred to as described in reference to Fig.12 The described waveform receiving circuit and / or waveform receiving code may be or may be executed by the waveform receiving circuit and / or waveform receiving code.
[0138] In some aspects, the information further indicates switching time gaps between different downlink waveforms supported by the UE.
[0139] In some aspects, the one or more downlink waveforms include a SC waveform.
[0140] In some aspects, the one or more downlink waveforms comprise a CP-OFDM waveform.
[0141] In some aspects, the sending comprises sending the information via a PRACH message of a four-step RACH procedure.
[0142] In some aspects, the PRACH message includes a PRACH preamble selected from different sets of PRACH preambles, wherein the different sets of PRACH preambles include a first PRACH preamble indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH preamble indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0143] In some aspects, a PRACH message is sent in a PRACH opportunity selected from different PRACH opportunity sets, wherein the different PRACH opportunity sets include a first PRACH opportunity indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH opportunity indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0144] In some aspects, the PRACH message includes one or more PRACH preambles, and wherein the PRACH preamble for each PRACH opportunity is associated with a mask.
[0145] In some aspects, the transmitting comprises transmitting the information via a scheduled uplink transmission message of a four-step RACH procedure.
[0146] In some aspects, the sending includes sending the information via a first message of a two-step RACH procedure.
[0147] In some aspects, the first message corresponds to a PUSCH DMRS configuration message, and wherein the information is indicated using different DMRS sequences for different types of downlink waveforms supported by the UE.
[0148] In some aspects, the information further indicates a preference of the UE in utilizing a particular downlink waveform among the one or more downlink waveforms.
[0149] In some aspects, the preference indicates a downlink waveform request for a particular downlink channel or for all downlink channels.
[0150] In some aspects, the preference indicates one or more downlink waveforms supported by the UE for each frequency band.
[0151] In some aspects, the preference indicates one or more downlink waveforms supported by the UE for the frequency band combination.
[0152] In one aspect, method 1000 or any aspect related thereto may be performed by an apparatus such as Fig.12 The method 1000 is performed by a communication device 1200 that includes various components operable, configured, or adapted to perform the method 1000. The communication device 1200 is described in more detail below.
[0153] It should be noted that Fig.10 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.
[0154] Example Operations of Network Entities
[0155] Fig.11A method for transmitting data to a network entity such as Figure 1 and Figure 3 BS102 or such Figure 2 Method 1100 for wireless communication with a decomposed BS as discussed above. Method 1100 may be implemented as a process in one or more processors (e.g. Figure 3 In addition, the network entity may transmit and receive signals in method 1100 by, for example, one or more antennas (e.g., Figure 3 In some aspects, the sending and / or receiving of signals by the network entity may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 340).
[0156] Method 1100 begins at 1105, where information indicating one or more downlink waveforms supported by the UE is received from the UE via one or more RACH messages. In some cases, the operation of this step refers to as described in reference to Fig.13 The described UE capability processing circuit and / or UE capability processing code may be executed by the UE capability processing circuit and / or UE capability processing code.
[0157] Method 1100 then proceeds to step 1110, where one or more downlink transmissions using one or more downlink waveforms supported by the UE are sent to the UE. In some cases, the operations of this step are referred to as described in reference to Fig.13 The described waveform transmission circuit and / or waveform transmission code may be performed by the waveform transmission circuit and / or waveform transmission code.
[0158] In some aspects, the information further indicates switching time gaps between different downlink waveforms supported by the UE.
[0159] In some aspects, the one or more downlink waveforms include a SC waveform.
[0160] In some aspects, the one or more downlink waveforms comprise a CP-OFDM waveform.
[0161] In some aspects, the receiving comprises receiving information via a PRACH message of a four-step RACH procedure.
[0162] In some aspects, the PRACH message includes a PRACH preamble selected from different sets of PRACH preambles, wherein the different sets of PRACH preambles include a first PRACH preamble indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH preamble indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0163] In some aspects, a PRACH message is received in a PRACH opportunity selected from different sets of PRACH opportunities, wherein the different sets of PRACH opportunities include a first PRACH opportunity indicating that the UE supports a particular downlink waveform within one or more downlink waveforms and a second PRACH opportunity indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0164] In some aspects, the receiving comprises receiving information via a scheduled uplink transmission message of a four-step RACH procedure.
[0165] In some aspects, the receiving comprises receiving information via a first message of a two-step RACH procedure, and wherein the first message corresponds to a PUSCH DMRS configuration message, and wherein the information is indicated using different DMRS sequences for different types of downlink waveforms supported by the UE.
[0166] In some aspects, the information further indicates a preference of the UE in utilizing a particular downlink waveform among the one or more downlink waveforms.
[0167] In some aspects, the preference indicates one or more of: a downlink waveform request for a specific downlink channel or all downlink channels, one or more downlink waveforms supported by the UE for each frequency band, or one or more downlink waveforms supported by the UE for a combination of frequency bands.
[0168] In one aspect, method 1100 or any aspect related thereto may be performed by an apparatus such as Fig.13 The method 1100 is performed by a communication device 1300 that includes various components operable, configured, or adapted to perform the method 1100. The communication device 1300 is described in more detail below.
[0169] It should be noted that Fig.11 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.
[0170] Example Communication Device
[0171] Fig.12 Aspects of an example communications device 1200 are depicted. In some aspects, the communications device 1200 is a user equipment (UE), such as described above with respect to Figure 1 and Figure 3 UE 104 is described.
[0172] The communication device 1200 includes a processing system 1205 coupled to a transceiver 1245 (e.g., a transmitter and / or a receiver). The transceiver 1245 is configured to transmit and receive signals for the communication device 1200, such as various signals as described herein, via an antenna 1250. The processing system 1205 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.
[0173] The processing system 1205 includes one or more processors 1210. In various aspects, the one or more processors 1210 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380, as described with respect to FIG. Figure 3 The one or more processors 1210 are coupled to the computer readable medium / memory 1225 via the bus 1240. In some aspects, the computer readable medium / memory 1225 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1210, cause the one or more processors 1210 to perform operations related to Fig.10 It should be noted that references to a processor performing a function of the communication device 1200 may include one or more processors 1210 performing that function of the communication device 1200.
[0174] In the depicted example, the computer readable medium / memory 1225 stores code (e.g., executable instructions) such as capability signaling code 1230 and waveform reception code 1235. Processing of the capability signaling code 1230 and the waveform reception code 1235 may cause the communication device 1200 to perform operations related to the communication device 1200. Fig.10 The method 1000 described herein or any aspect related thereto.
[0175] The one or more processors 1210 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1225, including circuits such as capability signaling circuit 1215 and waveform receiving circuit 1220. Processing using capability signaling circuit 1215 and waveform receiving circuit 1220 may cause the communication device 1200 to perform operations related to Fig.10 The method 1000 described herein or any aspect related thereto.
[0176] The various components of the communication device 1200 may provide for performing Fig.10 The method 1000 described herein or any aspect thereof may include a component for sending, transmitting, or outputting for sending. Figure 3The transceiver 354 and / or antenna 352 of the UE 104 illustrated in FIG. Fig.12 The transceiver 1245 and antenna 1250 of the communication device 1200 in FIG. 1 may include Figure 3 The transceiver 354 and / or antenna 352 of the UE 104 illustrated in FIG. Fig.12 The transceiver 1245 and antenna 1250 of the communication device 1200.
[0177] Fig.13 Aspects of an example communications device 1300 are depicted. In some aspects, communications device 1300 is a network entity such as Figure 1 and Figure 3 BS102 or such Figure 2 The decomposed BS in question.
[0178] The communication device 1300 includes a processing system 1305 coupled to a transceiver 1345 (e.g., a transmitter and / or a receiver) and / or a network interface 1355. The transceiver 1345 is configured to transmit and receive signals for the communication device 1300 via an antenna 1350, such as various signals as described herein. The network interface 1355 is configured to transmit and receive signals for the communication device 1300 via a communication link (such as various signals as described herein). Figure 2 The processing system 1305 may be configured to perform processing functions for the communication device 1300, including processing signals received by the communication device 1300 and / or to be transmitted.
[0179] The processing system 1305 includes one or more processors 1310. In various aspects, the one or more processors 1310 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. Figure 3 The one or more processors 1310 are coupled to the computer readable medium / memory 1325 via the bus 1340. In some aspects, the computer readable medium / memory 1325 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1310, cause the one or more processors 1310 to perform operations related to Fig.11 The method 1100 described herein or any aspect related thereto. It should be noted that reference to a processor of the communication device 1300 that performs a function may include one or more processors 1310 of the communication device 1300 that perform the function.
[0180] In the depicted example, the computer readable medium / memory 1325 stores code (e.g., executable instructions) such as UE capability processing code 1330 and waveform transmission code 1335. The processing of the UE capability processing code 1330 and the waveform transmission code 1335 may cause the communication device 1300 to perform operations related to the communication device 1300. Fig.11 The method 1100 described herein or any aspect related thereto.
[0181] The one or more processors 1310 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1325, including circuits such as UE capability processing circuit 1315 and waveform transmission circuit 1320. Processing using the UE capability processing circuit 1315 and the waveform transmission circuit 1320 may cause the communication device 1300 to perform the following operations: Fig.11 The described method 1100 or any aspect related thereto.
[0182] The various components of the communication device 1300 may provide for performing Fig.11 The described method 1100 or any aspect thereof may include: Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 and / or Fig.13 The transceiver 1345 and antenna 1350 of the communication device 1300 in FIG. 1344 can include Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 and / or Fig.13 The transceiver 1345 and antenna 1350 of the communication device 1300 in FIG.
[0183] Sample Clauses
[0184] Specific implementation examples are described in the following numbered clauses:
[0185] Clause 1: A method for wireless communications by a UE, comprising: sending information indicating one or more downlink waveforms supported by the UE to a network entity via one or more RACH messages; and receiving one or more downlink transmissions from the network entity using the one or more downlink waveforms supported by the UE.
[0186] Clause 2: The method of clause 1, wherein the information further indicates a switching time gap between different downlink waveforms supported by the UE.
[0187] Clause 3: The method of any of clauses 1 and 2, wherein the one or more downlink waveforms comprise a SC waveform.
[0188] Clause 4: A method as described in any of clauses 1 to 3, wherein the one or more downlink waveforms comprise a CP-OFDM waveform.
[0189] Clause 5: A method as described in any of clauses 1 to 4, wherein the sending comprises sending the information via a PRACH message of a four-step RACH procedure.
[0190] Clause 6: A method according to clause 5, wherein the PRACH message includes a PRACH preamble code selected from different PRACH preamble code sets, wherein the different PRACH preamble code sets include a first PRACH preamble code indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH preamble code indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0191] Clause 7: A method according to clause 5, wherein the PRACH message is sent in a PRACH opportunity selected from different PRACH opportunity sets, wherein the different PRACH opportunity sets include a first PRACH opportunity indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH opportunity indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0192] Clause 8: A method as set forth in clause 5, wherein the PRACH message comprises one or more PRACH preambles, and wherein the PRACH preamble for each PRACH opportunity is associated with a mask.
[0193] Clause 9: A method as described in any of clauses 1 to 8, wherein the sending comprises sending the information via a Scheduled Uplink Send message of a four-step RACH procedure.
[0194] Clause 10: A method as set forth in any one of clauses 1 to 9, wherein said sending comprises sending said information via a first message of a two-step RACH procedure.
[0195] Clause 11: The method of clause 10, wherein the first message corresponds to a PUSCH DMRS configuration message, and wherein the information is indicated using different DMRS sequences for different types of downlink waveforms supported by the UE.
[0196] Clause 12: A method as described in any of clauses 1 to 11, wherein the information further indicates a preference of the UE in using a certain downlink waveform of the one or more downlink waveforms.
[0197] Clause 13: The method of clause 12, wherein the preference indicates a downlink waveform request for a specific downlink channel or all downlink channels.
[0198] Clause 14: The method of clause 12, wherein the preference indicates the one or more downlink waveforms supported by the UE for each frequency band.
[0199] Clause 15: The method of clause 12, wherein the preference indicates the one or more downlink waveforms supported by the UE for a frequency band combination.
[0200] Clause 16: A method for wireless communications by a network entity, comprising: receiving information from a UE via one or more RACH messages indicating one or more downlink waveforms supported by the UE; and sending to the UE one or more downlink transmissions using the one or more downlink waveforms supported by the UE.
[0201] Clause 17: The method of clause 16, wherein the information further indicates a switching time gap between different downlink waveforms supported by the UE.
[0202] Clause 18: The method of any of clauses 16 and 17, wherein the one or more downlink waveforms comprise a SC waveform.
[0203] Clause 19: A method as described in any of clauses 16 to 18, wherein the one or more downlink waveforms comprise a CP-OFDM waveform.
[0204] Clause 20: A method as set forth in any of clauses 16 to 19, wherein said receiving comprises receiving said information via a PRACH message of a four-step RACH procedure.
[0205] Clause 21: A method according to clause 20, wherein the PRACH message includes a PRACH preamble code selected from different PRACH preamble code sets, wherein the different PRACH preamble code sets include a first PRACH preamble code indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH preamble code indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0206] Clause 22: A method according to clause 20, wherein the PRACH message is received in a PRACH opportunity selected from different PRACH opportunity sets, wherein the different PRACH opportunity sets include a first PRACH opportunity indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH opportunity indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
[0207] Clause 23: A method as set out in any of clauses 16 to 22, wherein said receiving comprises receiving said information via a Scheduled Uplink Transmission message of a four-step RACH procedure.
[0208] Clause 24: A method according to any of clauses 16 to 23, wherein the receiving comprises receiving the information via a first message of a two-step RACH procedure, and wherein the first message corresponds to a PUSCH DMRS configuration message, and wherein the information is indicated using different DMRS sequences for different types of downlink waveforms supported by the UE.
[0209] Clause 25: A method as described in any of clauses 16 to 24, wherein the information further indicates a preference of the UE in using a certain downlink waveform of the one or more downlink waveforms.
[0210] Clause 26: A method according to clause 25, wherein the preference indicates one or more of: a downlink waveform request for a specific downlink channel or all downlink channels, the one or more downlink waveforms supported by the UE for each frequency band, or the one or more downlink waveforms supported by the UE for a frequency band combination.
[0211] Clause 27: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method according to any one of clauses 1 to 26.
[0212] Clause 28: An apparatus comprising means for performing the method according to any one of clauses 1 to 26.
[0213] Clause 29: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any of clauses 1 to 26.
[0214] Clause 30: A computer program product embodied on a computer readable storage medium, the computer readable storage medium comprising code for performing the method according to any one of clauses 1 to 26.
[0215] Additional considerations
[0216] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Each example may ignore, replace or add various procedures or components as appropriate. For example, the described method may be performed in a different order than the described order, and various actions may be added, omitted or combined. In addition, the features described for some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions that are supplementary or alternative to the various 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.
[0217] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed using a general purpose processor, a digital signal processor (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 an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.
[0218] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).
[0219] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching 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 a memory), and the like. Additionally, "determining" may include resolving, selecting, choosing, establishing, and the like.
[0220] The method disclosed herein includes one or more actions for implementing the method. The method actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, the various operations of the method described above can be performed by any appropriate component that can perform the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.
[0221] The following claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, references to elements in the singular form are not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "member for...". All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly stated in the claims, anything disclosed herein is not intended to be disclosed to the public.
Claims
1. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: a memory including computer executable instructions; and one or more processors configured to execute the computer executable instructions and cause the UE to: sending information indicating one or more downlink waveforms supported by the UE to a network entity via one or more random access channel (RACH) messages; and One or more downlink transmissions using the one or more downlink waveforms supported by the UE are received from the network entity.
2. The UE of claim 1, wherein the information further indicates a switching time gap between different downlink waveforms supported by the UE.
3. The UE of claim 1, wherein the one or more downlink waveforms comprise a single carrier (SC) waveform.
4. The UE of claim 1, wherein the one or more downlink waveforms comprise a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform.
5. The UE of claim 1, wherein the sending comprises sending the information via a Physical RACH (PRACH) message of a four-step RACH procedure.
6. The UE of claim 5, wherein the PRACH message comprises a PRACH preamble selected from different PRACH preamble sets, wherein the different PRACH preamble sets comprise a first PRACH preamble indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH preamble indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
7. The UE of claim 5, wherein the PRACH message is sent in a PRACH opportunity selected from different PRACH opportunity sets, wherein the different PRACH opportunity sets include a first PRACH opportunity indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH opportunity indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
8. The UE of claim 5, wherein the PRACH message comprises one or more PRACH preambles, and wherein the PRACH preamble of each PRACH opportunity is associated with a mask.
9. The UE of claim 1, wherein the sending comprises sending the information via a scheduled uplink transmission message of a four-step RACH procedure.
10. The UE of claim 1, wherein the sending comprises sending the information via a first message of a two-step RACH procedure.
11. The UE of claim 10, wherein the first message corresponds to a physical uplink shared channel (PUSCH) demodulation reference signal (DMRS) configuration message, and wherein the information is indicated using different DMRS sequences for different types of downlink waveforms supported by the UE.
12. The UE of claim 1, wherein the information further indicates a preference of the UE in using a certain downlink waveform among the one or more downlink waveforms. 13 . The UE of claim 12 , wherein the preference indicates a downlink waveform request for a specific downlink channel or all downlink channels.
14. The UE of claim 12, wherein the preference indicates the one or more downlink waveforms supported by the UE for each frequency band.
15. The UE of claim 12, wherein the preference indicates the one or more downlink waveforms supported by the UE for a frequency band combination.
16. A network entity configured for wireless communication, the network entity comprising: a memory including computer executable instructions; and one or more processors configured to execute the computer executable instructions and cause the network entity to: receiving information from a user equipment (UE) via one or more random access channel (RACH) messages indicating one or more downlink waveforms supported by the UE; and One or more downlink transmissions are transmitted to the UE using the one or more downlink waveforms supported by the UE.
17. The network entity of claim 16, wherein the information further indicates a switching time gap between different downlink waveforms supported by the UE.
18. The network entity of claim 16, wherein the one or more downlink waveforms comprise a single carrier (SC) waveform.
19. The network entity of claim 16, wherein the one or more downlink waveforms comprise a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform.
20. The network entity of claim 16, wherein the receiving comprises receiving the information via a Physical RACH (PRACH) message of a four-step RACH procedure.
21. The network entity of claim 20, wherein the PRACH message comprises a PRACH preamble selected from different sets of PRACH preambles, wherein the different sets of PRACH preambles comprise a first PRACH preamble indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH preamble indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
22. The network entity of claim 20, wherein the PRACH message is received in a PRACH opportunity selected from a set of different PRACH opportunities, wherein the set of different PRACH opportunities includes a first PRACH opportunity indicating that the UE supports a specific downlink waveform within the one or more downlink waveforms, and a second PRACH opportunity indicating that the UE supports all downlink waveforms within the one or more downlink waveforms.
23. The network entity of claim 16, wherein the receiving comprises receiving the information via a Scheduled Uplink Transmission message of a four-step RACH procedure.
24. The network entity of claim 16, wherein the receiving comprises receiving the information via a first message of a two-step RACH procedure, and wherein the first message corresponds to a physical uplink shared channel (PUSCH) demodulation reference signal (DMRS) configuration message, and wherein the information is indicated using different DMRS sequences for different types of downlink waveforms supported by the UE.
25. The network entity of claim 16, wherein the information further indicates a preference of the UE in using a certain downlink waveform among the one or more downlink waveforms.
26. The network entity of claim 25, wherein the preference indicates one or more of: a downlink waveform request for a specific downlink channel or all downlink channels, the one or more downlink waveforms supported by the UE for each frequency band, or the one or more downlink waveforms supported by the UE for a frequency band combination.
27. A method for wireless communication by a user equipment (UE), the method comprising: sending information indicating one or more downlink waveforms supported by the UE to a network entity via one or more random access channel (RACH) messages; as well as One or more downlink transmissions using the one or more downlink waveforms supported by the UE are received from the network entity.
28. The method of claim 27, wherein the information further indicates a switching time gap between different downlink waveforms supported by the UE.
29. A method for wireless communication by a network entity, the method comprising: receiving information from a user equipment (UE) via one or more random access channel (RACH) messages indicating one or more downlink waveforms supported by the UE; as well as One or more downlink transmissions are transmitted to the UE using the one or more downlink waveforms supported by the UE.
30. The method of claim 29, wherein the information further indicates a switching time gap between different downlink waveforms supported by the UE.
Citation Information
Patent Citations
Waveform support capability signaling during initial access
US20230345549A1
