request waveform variation

Abstract

Apparatus, methods, and systems for requesting waveform changes are disclosed. One method (600) includes receiving (602) first information at a user equipment indicating the configuration of multiple waveforms and an indication that the user equipment is enabled to request a waveform change, a subcarrier spacing change, or a combination thereof. The method (600) includes transmitting (604) a request message to a base station. This request message requests a waveform change, a subcarrier spacing change, or a combination thereof. The method (600) also includes receiving (606) a response message from the base station. This response message indicates whether the request for the waveform change, subcarrier spacing change, or a combination thereof has been approved.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 63 / 044,766, filed June 26, 2020, entitled “Apparatus, Methods, and Systems for Waveform Indication During Initial Access,” which is incorporated herein by reference in its entirety. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically to requesting waveform changes. Background Technology

[0004] In some wireless communication networks, different waveforms can be used for communication. Depending on various criteria, some waveforms may be better than others. Summary of the Invention

[0005] A method for requesting waveform changes is disclosed. Apparatus and systems also perform the functions of this method. One embodiment of the method includes receiving, at a user equipment, first information indicating configuration for multiple waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, the method includes transmitting a request message to a base station. The request message requests waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, the method includes receiving a response message from the base station. The response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0006] An apparatus for requesting waveform changes includes a user equipment. In some embodiments, the apparatus includes a receiver that receives first information indicating the configuration of a plurality of waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In various embodiments, the apparatus includes a transmitter that transmits a request message to a base station. The request message requests waveform changes, subcarrier spacing changes, or combinations thereof. The receiver receives a response message from the base station. The response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0007] Another embodiment of a method for responding to a request for a waveform change includes transmitting from a base station first information indicating the configuration of multiple waveforms and an indication that a user equipment is enabled to request a waveform change, a subcarrier spacing change, or a combination thereof. In some embodiments, the method includes receiving a request message from the user equipment. The request message requests a waveform change, a subcarrier spacing change, or a combination thereof. In some embodiments, the method includes transmitting a response message to the user equipment. The response message indicates whether the request for a waveform change, a subcarrier spacing change, or a combination thereof has been approved.

[0008] Another means for responding to a request for a waveform change includes a base station. In some embodiments, the means includes a transmitter that transmits first information indicating the configuration of a plurality of waveforms and an indication that a user equipment is enabled to request a waveform change, a subcarrier spacing change, or a combination thereof. In various embodiments, the means includes a receiver that receives a request message from the user equipment. The request message requests a waveform change, a subcarrier spacing change, or a combination thereof. The transmitter transmits a response message to the user equipment. The response message indicates whether the request for a waveform change, a subcarrier spacing change, or a combination thereof has been approved. Attached Figure Description

[0009] A more detailed description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are not intended to be limiting of the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for requesting waveform changes;

[0011] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used to request waveform changes;

[0012] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used to respond to a request for a waveform change;

[0013] Figure 4 This is a schematic block diagram illustrating one embodiment of the signaling process for a waveform switching request in response to a 4-step RACH.

[0014] Figure 5 This is a schematic block diagram illustrating one embodiment of the signaling process for a waveform switching request in response to a 2-step RACH.

[0015] Figure 6 This is a flowchart illustrating one embodiment of a method for requesting waveform changes; and

[0016] Figure 7 This is a flowchart illustrating an embodiment of a method for responding to a request for a waveform change. Detailed Implementation

[0017] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein in the form of "circuit," "module," or "system." Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as "code." The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device only uses signals for accessing the code.

[0018] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuits comprising custom-designed very large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0019] Modules can also be implemented in code and / or software for execution by various types of processors. An identified code module may, for example, comprise one or more physical or logical blocks of executable code that can be organized, for example, as objects, procedures, or functions. However, the executable files of the identified modules do not need to be physically located together, but may include unrelated instructions stored in different locations that, when logically connected together, comprise the module and implement the purposes described for the module.

[0020] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data can be identified and illustrated within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0021] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0022] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in connection with an instruction execution system, apparatus, or device.

[0023] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or it can be connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0024] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless explicitly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily all refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless explicitly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless explicitly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless explicitly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0025] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. In the following description, numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0026] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0027] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the boxes or blocks of the schematic flowchart and / or schematic block diagram.

[0028] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the boxes or blocks of the flowchart and / or block diagram.

[0029] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0030] It should also be noted that in some alternative implementations, the functions marked in the boxes may not occur in the order indicated in the figures. For example, depending on the functionality involved, two consecutively shown boxes may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures are conceivable.

[0031] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs a specific function or action.

[0032] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0033] Figure 1 An embodiment of a wireless communication system 100 for requesting waveform changes is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communication system 100.

[0034] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0035] Network units 104 can be distributed across a geographical area. In some embodiments, network element 104 may also be referred to as and / or may include one or more of the following: access point, access terminal, base station, base station, location server, core network (“CN”), radio network entity, node-B, evolved node-B (“eNB”), 5G node-B (“gNB”), home node-B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified data repository (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operation, administration and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, as well as other networks. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0036] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”), and remote unit 102 transmits using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. ZigBee, Sigfoxx, and related protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0037] Network unit 104 can serve multiple remote units 102 within a service area, such as a cell or cell sector, via a wireless communication link. Network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0038] In various embodiments, remote unit 102 may receive at a user equipment first information indicating the configuration of multiple waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, remote unit 102 may transmit a request message to a base station. This request message requests waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, remote unit 102 may receive a response message from the base station. This response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved. Therefore, remote unit 102 can be used to request waveform changes.

[0039] In some embodiments, network unit 104 may transmit from a base station first information indicating the configuration of multiple waveforms and an indication that a user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, network unit 104 may receive a request message from the user equipment. This request message requests waveform changes, subcarrier spacing changes, or combinations thereof. In various embodiments, network unit 104 may transmit a response message to the user equipment. This response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved. Therefore, network unit 104 can be used to respond to requests for waveform changes.

[0040] Figure 2 An embodiment of a device 200 that can be used to request waveform changes is depicted. The device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or display 208.

[0041] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0042] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

[0043] In one embodiment, input device 206 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0044] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0045] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a buzzer or beep). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0046] Receiver 212 may receive first information indicating configuration for multiple waveforms and an indication that a user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In various embodiments, transmitter 210 may transmit a request message to a base station, wherein the request message requests waveform changes, subcarrier spacing changes, or combinations thereof; wherein the receiver receives a response message from the base station, wherein the response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0047] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 may be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0048] Figure 3An embodiment of a device 300 that can be used to respond to a request for waveform changes is depicted. Device 300 includes one embodiment of a network unit 104. Furthermore, network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As will be understood, processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0049] In some embodiments, transmitter 310 may be used to transmit the information described herein and / or receiver 312 may be used to receive the information described herein.

[0050] Transmitter 310 may transmit first information indicating the configuration of multiple waveforms and an indication that a user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, receiver 312 may receive a request message from the user equipment. This request message requests waveform changes, subcarrier spacing changes, or combinations thereof. In various embodiments, transmitter 310 transmits a response message to the user equipment. This response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0051] In some embodiments, new radio frequencies (“NR”) exceeding 52.6 GHz may be used. In such embodiments, signal degradation may occur at high frequencies. Furthermore, at such frequencies, in addition to high path loss, the radio frequency (“RF”) components of the transmitter and receiver may exhibit nonlinear transmission characteristics, which may lead to further system degradation.

[0052] In some embodiments, waveforms based on multi-carrier orthogonal frequency division multiplexing (“OFDM”) can be used for the downlink (“DL”) and / or uplink (“UL”). In various embodiments, such as at cell edges, single-carrier discrete Fourier transform (“DFT”) extended OFDM (“DFT-s-OFDM”) can be used in the UL. In some embodiments, cyclic prefix (“CP”) OFDM (“CP-OFDM”) performance degrades at high frequencies (e.g., 52.6 GHz) due to its sensitivity to phase noise and its high peak-to-average power ratio (“PAPR”) or cubic metric (“CM”) that limits cell coverage. It should be noted that the degradation of CP-OFDM at high frequencies can become more severe with increasing modulation order and / or channel bandwidth. Therefore, some physical layer channels may be more affected than others.

[0053] Due to the various embodiments described, single-carrier waveforms may be suitable candidates at high frequencies due to their inherent robustness against phase noise and their low PAPR or CM. In some embodiments, the UL supports single-carrier waveforms (e.g., DFT-s-OFDM and / or single-carrier (“SC”) frequency division multiplexing (“FDM”) (“SC-FDM”)). However, power constraints of the UE, particularly at the cell edge, may also require the use of other single-carrier waveforms for cell edge conditions, such as SC quadrature amplitude modulation (“QAM”) (“SC-QAM”), SC frequency domain equalization (“FDE”) (“SC-FDE”), and, or CP SC (“CP-SC”).

[0054] In various embodiments, single-carrier waveforms such as DFT-s-OFDM waveforms can be used for DL ​​due to their lower PAPR compared to CP-OFDM and their better frequency flexibility compared to pure single-carrier candidates such as SC-QAM. In some embodiments, while using DFT-s-OFDM or other single-carrier candidates for DL ​​can enhance cell coverage, it may limit the system's multiple-input multiple-output (“MIMO”) capabilities and may reduce the flexibility of demodulation reference signal (“DMRS”) mapping. In some embodiments, frequency range 4 (“FR4”) can be used for high data rate applications such as enhanced mobile broadband (“eMBB”) and may require high channel bandwidth for high throughput, where MIMO can also play a significant role. In various embodiments, latency and / or massive access and reliability may be critical, such as in factory automation and / or Industrial Internet of Things (“IoT”) (“IIoT”) applications. In some embodiments, such as backhaul, integrated access backhaul (“IAB”) can operate primarily under line-of-sight (“LOS”) conditions, where fading and power consumption may not be major issues. In some embodiments, mobile data offloading may require coexistence with other systems (e.g., Wi-Fi at 60 GHz). In various embodiments, for short-range high data rate device-to-device (“D2D”) communication, coverage may be limited and PAPR issues may be less critical than other issues. In some embodiments, trade-offs in latency and throughput between cell coverage requirements and quality of service (“QoS”) requirements can be considered to support different configurations. In some embodiments, multi-waveform support for DL ​​and UL is a practical solution for adapting to variant configurations and / or coverage to achieve high system flexibility and optimized performance. In various embodiments, the preferred DL and / or UL waveforms and / or parameter sets for the user equipment (“UE”) can be indicated during the random access channel (“RACH”) procedure.

[0055] In some embodiments, single-carrier waveforms such as DFT-s-OFDM, SC-FDE, SC-FDM, or CP-SC can have a lower PAPR compared to OFDM and can thereby improve network coverage (e.g., at cell edges and / or at high carrier frequencies). In some embodiments, OFDM can have better support for MIMO and better spectral efficiency, as well as efficient reference signal (“RS”) placement in the time-frequency grid, than SC waveforms. In various embodiments, for simplicity, some UEs may be equipped with only one waveform. In some embodiments, multi-waveform support for DL ​​and UL can be provided to accommodate various configurations and / or coverage areas. In some embodiments, to achieve high system flexibility and optimize performance in terms of coverage and throughput for different configurations, waveform switching schemes can be used during initial access at frequencies above 52.6 GHz for DL. In such embodiments, the gNB can switch between multi-carrier and single-carrier waveforms based on a request from the UE.

[0056] In various embodiments, the existing baseband hardware (“HW”) for the gNB and / or UE can be upgraded to support high frequencies (e.g., frequencies above 52.6 GHz, FR4, frequencies above 52.6 GHz). In such embodiments, the HW can support both multiple and single carrier waveforms for DL ​​and / or UL, and the baseband HW for the UE can support only one waveform. In some embodiments, in addition to semi-statically configuring multiple waveforms for certain data and / or control channels, the UE can request a DL waveform type or a set of waveform parameters based on its measurements of initial access signals (e.g., synchronization signals (“SS”) and / or physical broadcast channel (“PBCH”) blocks).

[0057] In some embodiments, the gNB selects an initial waveform to be used for initial access in different DL channels and transmits a synchronization signal block (“SSB”) with a default DL waveform. The default DL waveform can be single-carrier, multi-carrier, or a combination of both. The default DL waveform and its corresponding parameter set can be selected based on network requirements (e.g., carrier frequency, QoS, etc.).

[0058] In various embodiments, such as for a DL with multiple waveforms, the gNB can select waveforms based on parameters such as the carrier frequency used, UE measurements (e.g., Reference Signal Received Power (“RSRP”), Reference Signal Received Quality (“RSRQ”), Signal-to-Interference-plus-Noise Ratio (“SINR”)), location, UE RF capabilities, gNB RF capabilities, UE power status (e.g., Power Headroom (“PH”) reports), UE auxiliary information (e.g., DL transform precoding recommendations based on path loss (“PL”) estimation), indications of UE battery power status, and so on. In some embodiments, the UE battery can assist the gNB in ​​selecting waveforms because some waveforms may require higher signal processing reception complexity than others, and therefore saving UE power may be important in critical battery power states.

[0059] In some embodiments, the UE may select or recommend a preferred DL or UL waveform or both preferred DL and UL waveforms, and may explicitly or implicitly indicate to the gNB that the waveform will be used during the initial access procedure based on DL SSB measurements for subsequent DL transmissions (e.g., based on DL path loss, peak power of the primary synchronization signal (“PSS”), demodulation reference signal (“DMRS”) of the physical broadcast channel (“PBCH”) (“PBCH-DMRS”) (e.g., RSRP, RSRQ, SINR), or SS-RSRP, RSRQ, and / or SINR), wherein the explicit or implicit indication may be based on the selected RACH preamble or message A (“MsgA”) transmission and a combination of the RACH preamble or both.

[0060] In various embodiments, the gNB may select to transmit a beam-scanning SSB with multiple waveforms having different transmission patterns, and the UE may select a DL waveform with the lowest path loss, a path loss below a threshold, a path loss within a range (e.g., the threshold and / or range may be predefined and / or configured), a path loss above a threshold, and / or the highest SS-RSRP, RSRQ, and / or SINR within a range of SSB measurement results (e.g., the threshold and / or range may be predefined and / or configured), and may indicate this to the gNB in ​​various ways.

[0061] In a first embodiment, a waveform indication for a 4-step RACH may be present. In some embodiments, such as for Type 1 random access (e.g., 4-step RACH), a Physical Random Access Control Channel (“PRACH”) preamble may be generated or selected using a sequence associated with the requested waveform and transmitted to the gNB (e.g., the PRACH preamble sequence is determined based on a preferred DL waveform type). In some embodiments, the PRACH preamble may be used to indicate a preferred DL waveform type and / or a preferred UL waveform type.

[0062] In various embodiments, the UE can implicitly indicate the DL waveform to be used by the gNB in ​​the next subsequent DL transmission (e.g., Msg 2 or Msg 4) by selecting an appropriate preamble identifier (“ID”). In some embodiments, the gNB can configure multiple prach-RootSequenceIndex or multiple msgA-prach-RootSequenceIndex (e.g., via Radio Resource Control (“RRC”) public signaling) in a System Information Block (“SIB”). In such embodiments, each index can be associated with a waveform index.

[0063] In some embodiments, the threshold of the path loss measurement result of the waveform change requested by the UE can be signaled to the UE along with the RACH RRC configuration (e.g., in the SIB).

[0064] In the second embodiment, a waveform indication for a 2-step RACH may be present. In various embodiments, for Type 2 random access (e.g., 2-step RACH), the RACH preamble may be selected or generated and transmitted using a sequence associated with the waveform, or the requested DL waveform indication may be transmitted in the Physical Uplink Shared Channel (“PUSCH”) transmission portion of the MsgA.

[0065] In some embodiments, the MsgA PUSCH payload includes a bit field (or a status within the bit field) indicating the requested DL waveform. In some embodiments, the bit field (or the status within the bit field) may be used to indicate the preferred UL waveform type and / or the preferred DL waveform type.

[0066] In various embodiments, the MsgA PUSCH DMRS can be selected or generated using a sequence associated with the requested waveform. In some embodiments, the DMRS sequence can be used to indicate a preferred UL waveform type and / or a preferred DL waveform type.

[0067] In a third embodiment, a preferred subcarrier spacing (“SCS”) indication may be present. In some embodiments, the UE may indicate the preferred SCS and preferred DL waveform to the gNB during DL measurements (e.g., measuring DL path loss, SSB, SS-RSRP, RSRQ, and / or SINR), or the UE may indicate an SCS independent of the preferred DL waveform. In various embodiments, the UE may indicate the preferred UL SCS, preferred DL SCS, preferred UL waveform type, and / or preferred DL waveform type to the gNB.

[0068] In some embodiments, the preferred SCS indication can be a threshold based on path loss measurements of SSB, SS-RSRP, RSRQ, and / or SINR transmitted by the gNB. In some embodiments, the threshold can be transmitted by signaling along with the RACH configuration, and the UE can indicate the preferred SCS to the gNB using a PRACH preamble sequence.

[0069] In various embodiments, the PUSCH-DMRS sequence or bit field (or the state in the bit field) in the PUSCH payload of MsgA may indicate the preferred SCS. In some embodiments, the indication may be a relative value representing the increment step size for increasing or decreasing the SCS. In such an embodiment, '1' may indicate a request to increase the SCS by one step (e.g., from 240 kHz to 480 kHz), and '0' may indicate to decrease the SCS by one step (e.g., from 480 kHz to 240 kHz).

[0070] In some embodiments, the UE may indicate the absolute value of the requested SCS using a multi-bit index. In such embodiments, the gNB may acknowledge and indicate the new SCS to the UE using a Random Access Response (“RAR”) message for a 4-step RACH or a Message B (“MsgB”) message for a 2-step RACH.

[0071] In a fourth embodiment, the gNB can provide a response to a waveform change request. In various embodiments, upon detection of a PRACH preamble, the gNB transmits an indication of received waveforms from the PRACH preamble sequence or from the MsgA PUSCH. In response to the UE, the gNB can confirm receipt of the requested waveform using a payload for a 4-step RACH RAR message or MsgB, downlink control information (“DCI”), or a 2-step RACH. In such embodiments, if the requested or indicated waveform type (e.g., as part of the confirmation) would be applicable, the gNB can indicate or configure the application timing (e.g., in terms of the number of symbols and / or slots in the reference subcarrier spacing (e.g., DL SCS, SCS for a 4-step RACH RAR message, or MsgBDCI, or a payload for a 2-step RACH)).

[0072] In some embodiments, the gNB can use the requested waveform for RAR or MsgB transmission. In some embodiments, the gNB can use a default waveform for RAR or MsgB transmission and can indicate the timeslot number of the requested waveform to be used.

[0073] In various embodiments, based on priority or scheduling requirements, the gNB can send an indication to the UE in the DCI that the request can or cannot be fulfilled using a default waveform.

[0074] In the fifth embodiment, a default DL waveform may exist for all DL channels. In some embodiments, the gNB may semi-statically indicate in RRC signaling (e.g., during or after initial access) the default DL waveform to be used for all DL channels (e.g., the Physical Downlink Control Channel (“PDCCH”) and / or the Physical Downlink Shared Channel (“PDSCH”) containing dedicated user data and / or the PDSCH with higher-layer signaling).

[0075] In some embodiments, RRC signaling for PDCCH configuration can indicate DL waveforms, PDSCH-dedicated signaling can indicate DL waveforms to be used for user data, and PDSCH-common signaling can indicate DL waveforms to be used for delivering higher-level signaling.

[0076] In various embodiments, the gNB or network node may indicate that UEs supporting only a first waveform type and / or a first SCS are prohibited or discouraged from accessing the cell. Such information may be indicated in system information (“SI”) such as the Physical Broadcast Channel (“PBCH”) and / or the Master Information Block (“MIB”) or the first SIB (“SIB1”). In some embodiments, the gNB may indicate a set or list of supported waveform types (e.g., for DL ​​and / or UL) and / or a set or list of supported subcarrier spacings (e.g., for DL ​​and / or UL), in which the UE can select a preferred waveform type and / or a preferred SCS. In some embodiments, the first waveform type (or first SCS) in the list may be selected based on a first threshold and the second waveform type (or second SCS) in the list may be selected based on a second threshold. In such embodiments, the first and second thresholds may be the same (e.g., if the DL measurement result is higher than the threshold, the first waveform type (or first SCS) is selected, and if the DL measurement result is lower than the threshold, the second waveform type (or second SCS) is selected).

[0077] Figure 4 This is a schematic block diagram illustrating one embodiment of the signaling procedure 400 for a waveform switching request in response to a 4-step RACH. Communication is illustrated between gNB 402 and UE 404. Each of the communications may include one or more messages.

[0078] In the first communication 406 transmitted from gNB 402 to UE 404, gNB 402 transmits SSB and / or default waveform to UE 404.

[0079] UE 404 measures the path loss of the received signal from 408 (e.g., peak power of PSS, RSRP based on PBCH DMRS).

[0080] In the second communication 412 transmitted from gNB 402 to UE 404, gNB 402 transmits SIBs to UE 404 (e.g., RACH configuration, configuration for waveform-based ID sequence generation, path loss threshold for waveform switching request).

[0081] UE 404 generates a 416PRACH preamble using the requested waveform association.

[0082] In the third communication 420 transmitted from UE 404 to gNB 402, UE 404 transmits a PRACH preamble (e.g., a waveform indicating a request) to gNB 402.

[0083] gNB 404 evaluates 424 requests (e.g., based on QoS requirements and / or priority and scheduling requirements).

[0084] In the fourth communication 428 transmitted from gNB 402 to UE 404, gNB 402 transmits a RAR (e.g., indicating a response to a waveform request) to UE 404.

[0085] Figure 5 This is a schematic block diagram illustrating one embodiment of a signaling procedure 500 for a waveform switching request in response to a 2-step RACH. Communication is illustrated between gNB 502 and UE 504. Each of the communications may include one or more messages.

[0086] In the first communication 506 transmitted from gNB 502 to UE 504, gNB 502 transmits SSB and / or default waveform to UE 504.

[0087] UE 504 measures the path loss of the received signal from 508 (e.g., peak power of PSS, RSRP based on PBCH DMRS).

[0088] In the second communication 512 transmitted from gNB 502 to UE 504, gNB 502 transmits SIBs to UE 504 (e.g., RACH configuration, configuration for waveform-based ID sequence generation, path loss threshold for waveform switching request).

[0089] UE 504 generates 516MsgA using the requested waveform association.

[0090] In the third communication 520 transmitted from UE 504 to gNB 502, UE 504 transmits MsgA (e.g., indicating the requested waveform) to gNB 502.

[0091] gNB 504 evaluates 524 requests (e.g., based on QoS requirements and / or priority and scheduling requirements).

[0092] In the fourth communication 528 transmitted from gNB 502 to UE 504, gNB 502 transmits MsgB to UE 504 (e.g., indicating a response to a waveform request).

[0093] Figure 6 This is a flowchart illustrating one embodiment of a method 600 for requesting waveform changes. In some embodiments, method 600 is executed by a device such as remote unit 102. In some embodiments, method 600 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0094] In various embodiments, method 600 includes receiving at a user equipment 602 first information indicating configuration for multiple waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, method 600 includes transmitting a request message 604 to a base station, wherein the request message requests waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, method 600 includes receiving a response message 606 from a base station, wherein the response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0095] In some embodiments, the multiple waveforms include uplink waveforms, downlink waveforms, multi-carrier waveforms, single-carrier waveforms, or combinations thereof. In some embodiments, method 600 further includes receiving second information indicating at least one waveform type that is unavailable in the serving cell. In various embodiments, method 600 further includes receiving a system information block random access channel configuration comprising multiple random access channel preambles and mappings between the multiple waveforms.

[0096] In one embodiment, method 600 further includes receiving a plurality of random access channel root sequence indices, wherein each sequence index of the plurality of random access channel root sequence indices corresponds to a waveform in a plurality of waveforms. In some embodiments, method 600 further includes receiving path loss information corresponding to a synchronization block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio (SINR) threshold, or a combination thereof. In some embodiments, method 600 further includes triggering a request message based on the synchronization block threshold, the reference signal received power threshold, the reference signal received quality threshold, the SINR threshold, or a combination thereof.

[0097] In various embodiments, the request message includes a selected random access channel preamble belonging to a root sequence index or preamble identifier group corresponding to waveform variation, subcarrier spacing variation, or a combination thereof. In one embodiment, in response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload. In some embodiments, the request message includes an implicit request to use the demodulation reference signal sequence of the physical uplink shared channel of message A.

[0098] In some embodiments, the request message includes a request to change the subcarrier spacing. In various embodiments, the request to change the subcarrier spacing includes multiple bits indicating an absolute subcarrier spacing value. In one embodiment, the request to change the subcarrier spacing includes a single bit indicating an incremental change in the default subcarrier spacing.

[0099] In some embodiments, a single bit including a "1" indicates that the default subcarrier spacing will be changed upwards by one value, and a "0" indicates that the default subcarrier spacing will be changed downwards by one value. In some embodiments, the response message is received as a random access response or message B. In various embodiments, the response message is determined based on the base station's scheduling and priority.

[0100] In one embodiment, the response message indicates the application of a waveform change, subcarrier spacing change, or a combination thereof, with a symbol offset or slot offset. In some embodiments, the response message indicates that a request for a waveform change, subcarrier spacing change, or a combination thereof has been approved, or that a default waveform should be used.

[0101] Figure 7 This is a flowchart illustrating one embodiment of a method 700 for responding to a request for a waveform change. In some embodiments, method 700 is executed by a device such as network unit 104. In some embodiments, method 700 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0102] In various embodiments, method 700 includes transmitting from a base station 702 first information indicating configuration for multiple waveforms and an indication that a user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, method 700 includes receiving from the user equipment 704 a request message, wherein the request message requests waveform changes, subcarrier spacing changes, or combinations thereof. In some embodiments, method 700 includes transmitting to the user equipment 706 a response message, wherein the response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0103] In some embodiments, the multiple waveforms include uplink waveforms, downlink waveforms, multi-carrier waveforms, single-carrier waveforms, or combinations thereof. In some embodiments, method 700 further includes transmitting second information indicating at least one waveform type that is unavailable in the serving cell. In various embodiments, method 700 further includes transmitting a system information block random access channel configuration comprising multiple random access channel preambles and a mapping between multiple waveforms.

[0104] In one embodiment, method 700 further includes transmitting a plurality of random access channel root sequence indices, wherein each sequence index of the plurality of random access channel root sequence indices corresponds to a waveform in a plurality of waveforms. In some embodiments, method 700 further includes transmitting path loss information corresponding to a synchronization block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio (SINR) threshold, or a combination thereof. In some embodiments, a request message is triggered based on the synchronization block threshold, the reference signal received power threshold, the reference signal received quality threshold, the SINR threshold, or a combination thereof.

[0105] In various embodiments, the request message includes a selected random access channel preamble belonging to a root sequence index or preamble identifier group corresponding to waveform variation, subcarrier spacing variation, or a combination thereof. In one embodiment, in response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload. In some embodiments, the request message includes an implicit request to use the demodulation reference signal sequence of the physical uplink shared channel of message A.

[0106] In some embodiments, the request message includes a request to change the subcarrier spacing. In various embodiments, the request to change the subcarrier spacing includes multiple bits indicating an absolute subcarrier spacing value. In one embodiment, the request to change the subcarrier spacing includes a single bit indicating an incremental change in the default subcarrier spacing.

[0107] In some embodiments, a single bit including a "1" indicates that the default subcarrier spacing will be changed upwards by one value, and a "0" indicates that the default subcarrier spacing will be changed downwards by one value. In some embodiments, the response message is received as a random access response or message B. In various embodiments, the response message is determined based on the base station's scheduling and priority.

[0108] In one embodiment, the response message indicates the application of a waveform change, subcarrier spacing change, or a combination thereof, with a symbol offset or slot offset. In some embodiments, the response message indicates that a request for a waveform change, subcarrier spacing change, or a combination thereof has been approved, or that a default waveform should be used.

[0109] In one embodiment, a method includes: receiving at a user equipment the first information indicating configuration for a plurality of waveforms and an indication indicating that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof; transmitting a request message to a base station, wherein the request message requests waveform changes, subcarrier spacing changes, or combinations thereof; and receiving from the base station the response message, wherein the response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0110] In some embodiments, the multiple waveforms include uplink waveforms, downlink waveforms, multicarrier waveforms, single-carrier waveforms, or combinations thereof.

[0111] In some embodiments, the method further includes receiving second information indicating at least one waveform type that is not available in the serving cell.

[0112] In various embodiments, the method further includes receiving a system information block random access channel configuration comprising a plurality of random access channel preambles and a mapping between a plurality of waveforms.

[0113] In one embodiment, the method further includes receiving a plurality of random access channel root sequence indices, wherein each sequence index of the plurality of random access channel root sequence indices corresponds to a waveform in a plurality of waveforms.

[0114] In some embodiments, the method further includes receiving path loss information corresponding to a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0115] In some embodiments, the method further includes triggering a request message based on a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0116] In various embodiments, the request message includes a selected random access channel preamble belonging to a root sequence index or preamble identifier group corresponding to waveform variation, subcarrier spacing variation, or a combination thereof.

[0117] In one embodiment, in response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload.

[0118] In some embodiments, the request message includes an implicit request for a demodulation reference signal sequence using the physical uplink shared channel of message A.

[0119] In some embodiments, the request message includes a request to change the subcarrier spacing.

[0120] In various embodiments, a request to change the subcarrier spacing includes multiple bits indicating the absolute subcarrier spacing value.

[0121] In one embodiment, a request to change the subcarrier spacing includes a bit indicating an incremental change in the default subcarrier spacing.

[0122] In some embodiments, a bit including "1" indicates that the default subcarrier spacing will be changed upward by one value and "0" indicates that the default subcarrier spacing will be changed downward by one value.

[0123] In some embodiments, the response message is received as a random access response or message B.

[0124] In various embodiments, the response message is determined based on the base station's scheduling and priority.

[0125] In one embodiment, the response message indicates a symbol offset or time slot offset for applying waveform changes, subcarrier spacing changes, or combinations thereof.

[0126] In some embodiments, the response message indicates that a request for waveform change, subcarrier spacing change, or a combination thereof has been approved or that a default waveform should be used.

[0127] In one embodiment, an apparatus includes a user equipment, the apparatus further comprising: a receiver receiving first information indicating configuration for a plurality of waveforms and an indication indicating that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof; and a transmitter transmitting a request message to a base station, wherein the request message requests waveform changes, subcarrier spacing changes, or combinations thereof; wherein the receiver receives a response message from the base station, wherein the response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof is approved.

[0128] In some embodiments, the multiple waveforms include uplink waveforms, downlink waveforms, multicarrier waveforms, single-carrier waveforms, or combinations thereof.

[0129] In some embodiments, the receiver receives second information indicating that at least one waveform type is not available in the serving cell.

[0130] In various embodiments, the receiver receives a system information block random access channel configuration that includes multiple random access channel preambles and mappings between multiple waveforms.

[0131] In one embodiment, the receiver receives a plurality of random access channel root sequence indices, and each sequence index of the plurality of random access channel root sequence indices corresponds to one of a plurality of waveforms.

[0132] In some embodiments, the receiver receives path loss information corresponding to a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0133] In some embodiments, the method further includes a processor that triggers a request message based on a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0134] In various embodiments, the request message includes a selected random access channel preamble belonging to a root sequence index or preamble identifier group corresponding to waveform variation, subcarrier spacing variation, or a combination thereof.

[0135] In one embodiment, in response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload.

[0136] In some embodiments, the request message includes an implicit request for a demodulation reference signal sequence using the physical uplink shared channel of message A.

[0137] In some embodiments, the request message includes a request to change the subcarrier spacing.

[0138] In various embodiments, a request to change the subcarrier spacing includes multiple bits indicating the absolute subcarrier spacing value.

[0139] In one embodiment, a request to change the subcarrier spacing includes a bit indicating an incremental change in the default subcarrier spacing.

[0140] In some embodiments, a bit including "1" indicates that the default subcarrier spacing will be changed upward by one value and "0" indicates that the default subcarrier spacing will be changed downward by one value.

[0141] In some embodiments, the response message is received as a random access response or message B.

[0142] In various embodiments, the response message is determined based on the base station's scheduling and priority.

[0143] In one embodiment, the response message indicates a symbol offset or time slot offset for applying waveform changes, subcarrier spacing changes, or combinations thereof.

[0144] In some embodiments, the response message indicates that a request for waveform change, subcarrier spacing change, or a combination thereof has been approved or that a default waveform should be used.

[0145] In one embodiment, a method includes: transmitting from a base station first information indicating configuration for multiple waveforms and an indication indicating that a user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof; receiving from the user equipment a request message, wherein the request message requests waveform changes, subcarrier spacing changes, or combinations thereof; and transmitting to the user equipment a response message, wherein the response message indicates whether the request for waveform changes, subcarrier spacing changes, or combinations thereof has been approved.

[0146] In some embodiments, the multiple waveforms include uplink waveforms, downlink waveforms, multicarrier waveforms, single-carrier waveforms, or combinations thereof.

[0147] In some embodiments, the method further includes transmitting second information indicating at least one waveform type that is not available in the serving cell.

[0148] In various embodiments, the method further includes transmitting a system information block random access channel configuration comprising a plurality of random access channel preambles and a mapping between a plurality of waveforms.

[0149] In one embodiment, the method further includes transmitting a plurality of random access channel root sequence indices, wherein each sequence index of the plurality of random access channel root sequence indices corresponds to a waveform in a plurality of waveforms.

[0150] In some embodiments, the method further includes transmitting path loss information corresponding to a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0151] In some embodiments, a request message is triggered based on a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0152] In various embodiments, the request message includes a selected random access channel preamble belonging to a root sequence index or preamble identifier group corresponding to waveform variation, subcarrier spacing variation, or a combination thereof.

[0153] In one embodiment, in response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload.

[0154] In some embodiments, the request message includes an implicit request for a demodulation reference signal sequence using the physical uplink shared channel of message A.

[0155] In some embodiments, the request message includes a request to change the subcarrier spacing.

[0156] In various embodiments, a request to change the subcarrier spacing includes multiple bits indicating the absolute subcarrier spacing value.

[0157] In one embodiment, a request to change the subcarrier spacing includes a bit indicating an incremental change in the default subcarrier spacing.

[0158] In some embodiments, a bit including "1" indicates that the default subcarrier spacing will be changed upward by one value and "0" indicates that the default subcarrier spacing will be changed downward by one value.

[0159] In some embodiments, the response message is received as a random access response or message B.

[0160] In various embodiments, the response message is determined based on the base station's scheduling and priority.

[0161] In one embodiment, the response message indicates a symbol offset or time slot offset for applying waveform changes, subcarrier spacing changes, or combinations thereof.

[0162] In some embodiments, the response message indicates that a request for waveform change, subcarrier spacing change, or a combination thereof has been approved or that a default waveform should be used.

[0163] In one embodiment, an apparatus includes a base station, the apparatus further comprising: a transmitter transmitting first information indicating the configuration of a plurality of waveforms and an indication indicating that a user equipment is enabled to request a waveform change, a subcarrier spacing change, or a combination thereof; and a receiver receiving a request message from the user equipment, wherein the request message requests a waveform change, a subcarrier spacing change, or a combination thereof; wherein the transmitter transmits a response message to the user equipment, wherein the response message indicates whether the request for the waveform change, the subcarrier spacing change, or the combination thereof is approved.

[0164] In some embodiments, the multiple waveforms include uplink waveforms, downlink waveforms, multicarrier waveforms, single-carrier waveforms, or combinations thereof.

[0165] In some embodiments, the transmitter transmits second information indicating at least one waveform type that is not available in the serving cell.

[0166] In various embodiments, the transmitter transmits a system information block random access channel configuration that includes multiple random access channel preambles and mappings between multiple waveforms.

[0167] In one embodiment, the transmitter transmits a plurality of random access channel root sequence indices, wherein each sequence index of the plurality of random access channel root sequence indices corresponds to a waveform in a plurality of waveforms.

[0168] In some embodiments, the transmitter transmits path loss information corresponding to a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0169] In some embodiments, a request message is triggered based on a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof.

[0170] In various embodiments, the request message includes a selected random access channel preamble belonging to a root sequence index or preamble identifier group corresponding to waveform variation, subcarrier spacing variation, or a combination thereof.

[0171] In one embodiment, in response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload.

[0172] In some embodiments, the request message includes an implicit request for a demodulation reference signal sequence using the physical uplink shared channel of message A.

[0173] In some embodiments, the request message includes a request to change the subcarrier spacing.

[0174] In various embodiments, a request to change the subcarrier spacing includes multiple bits indicating the absolute subcarrier spacing value.

[0175] In one embodiment, a request to change the subcarrier spacing includes a bit indicating an incremental change in the default subcarrier spacing.

[0176] In some embodiments, a bit including "1" indicates that the default subcarrier spacing will be changed upward by one value and "0" indicates that the default subcarrier spacing will be changed downward by one value.

[0177] In some embodiments, the response message is received as a random access response or message B.

[0178] In various embodiments, the response message is determined based on the base station's scheduling and priority.

[0179] In one embodiment, the response message indicates a symbol offset or time slot offset for applying waveform changes, subcarrier spacing changes, or combinations thereof.

[0180] In some embodiments, the response message indicates that a request for waveform change, subcarrier spacing change, or a combination thereof has been approved or that a default waveform should be used.

[0181] The embodiments may be practiced in other specific forms. The described embodiments are to be regarded in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All variations within the meaning and equivalents of the claims are included within their scope.

Claims

1. A method executed by a user equipment, comprising: Receive first information indicating the configuration of multiple waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof; Receive a system information block random access channel configuration including multiple random access channel preambles and mappings between the multiple waveforms; A request message is transmitted to the base station, wherein the request message includes a random access channel preamble among the plurality of random access channel preambles, and wherein the random access channel preamble corresponds to a waveform among the plurality of waveforms according to the mapping included in the random access channel configuration of the system information block, and wherein the request message requests a change in the waveform, a change in the subcarrier spacing, or a combination thereof; and A response message is received from the base station, wherein the response message indicates whether the request for the waveform change, the subcarrier spacing change, or a combination thereof has been approved.

2. The method according to claim 1, further comprising receiving a plurality of random access channel root sequence indices, wherein, Each sequence index in the plurality of random access channel root sequence indices corresponds to a corresponding waveform in the plurality of waveforms.

3. The method of claim 1, further comprising receiving path loss information corresponding to a synchronization block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio (SINNR) threshold, or a combination thereof, and triggering the request message based on the synchronization block threshold, the reference signal received power threshold, the reference signal received quality threshold, the SINNR threshold, or a combination thereof.

4. The method according to claim 1, wherein, The request message includes the random access channel preamble belonging to the root sequence index or preamble identifier group corresponding to the waveform change, the subcarrier spacing change, or a combination thereof.

5. The method according to claim 1, wherein, In response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload.

6. The method according to claim 1, wherein, The request message includes an implicit request for the demodulation reference signal sequence of the physical uplink shared channel of message A.

7. The method according to claim 1, wherein, The request message includes a request to change the subcarrier spacing, and the request message includes multiple bits indicating the absolute subcarrier spacing value.

8. The method according to claim 1, wherein, The request message includes a request to change the subcarrier spacing, and the request message includes a bit indicating an incremental change in the default subcarrier spacing.

9. The method according to claim 1, wherein, The response message is received as a random access response or message B.

10. The method according to claim 1, wherein, The response message indicates the application of the waveform change, the subcarrier spacing change, or a combination thereof, as a symbol offset or time slot offset.

11. The method according to claim 1, wherein, The response message indicates that the request for the waveform change, the subcarrier spacing change, or a combination thereof is approved or that the default waveform should be used.

12. A communication device, comprising a user equipment, the communication device further comprising: The receiver receives first information indicating the configuration of multiple waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof, and receives a system information block random access channel configuration including multiple random access channel preambles and mappings between the multiple waveforms; as well as A transmitter transmits a request message to a base station, wherein the request message includes a random access channel preamble among the plurality of random access channel preambles, and wherein the random access channel preamble corresponds to a waveform among the plurality of waveforms according to the mapping included in the random access channel configuration of the system information block, and wherein the request message requests a change in the waveform, a change in the subcarrier spacing, or a combination thereof; The receiver receives a response message from the base station, wherein the response message indicates whether the request for the waveform change, the subcarrier spacing change, or a combination thereof has been approved.

13. A method at a base station, comprising: The transmission indication provides first information for configuring multiple waveforms and an indication that the user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof; The transmission includes a system information block random access channel configuration comprising multiple random access channel preambles and mappings between the multiple waveforms; A request message is received from the user equipment, wherein the request message includes a random access channel preamble among the plurality of random access channel preambles, and wherein the random access channel preamble corresponds to a waveform among the plurality of waveforms according to the mapping included in the system information block random access channel configuration, and wherein the request message requests a waveform change, a subcarrier spacing change, or a combination thereof; and A response message is transmitted to the user equipment, wherein the response message indicates whether the request for the waveform change, the subcarrier spacing change, or a combination thereof is approved.

14. The method of claim 13, further comprising transmitting a plurality of random access channel root sequence indices, wherein, Each sequence index in the plurality of random access channel root sequence indices corresponds to a corresponding waveform in the plurality of waveforms.

15. The method of claim 13, further comprising transmitting path loss information corresponding to a synchronization signal block threshold, a reference signal received power threshold, a reference signal received quality threshold, a signal-to-interference-plus-noise ratio threshold, or a combination thereof, wherein, The request message is triggered based on the synchronization signal block threshold, the reference signal received power threshold, the reference signal received quality threshold, the signal-to-interference-plus-noise ratio threshold, or a combination thereof.

16. The method according to claim 13, wherein, The request message includes the random access channel preamble belonging to the root sequence index or preamble identifier group corresponding to the waveform change, the subcarrier spacing change, or a combination thereof.

17. The method according to claim 13, wherein, In response to the use of a two-step random access control channel procedure, the request message includes an explicit request to use the physical uplink shared channel message payload.

18. A communication device, comprising a base station, the communication device further comprising: The transmitter transmits first information indicating the configuration of multiple waveforms and an indication that a user equipment is enabled to request waveform changes, subcarrier spacing changes, or combinations thereof, and transmits a system information block random access channel configuration including multiple random access channel preambles and a mapping between the multiple waveforms. as well as A receiver receives a request message from the user equipment, wherein the request message includes a random access channel preamble among the plurality of random access channel preambles, and wherein the random access channel preamble corresponds to a waveform among the plurality of waveforms according to the mapping included in the random access channel configuration of the system information block, and wherein the request message requests a change in the waveform, a change in the subcarrier spacing, or a combination thereof; The transmitter transmits a response message to the user equipment, wherein the response message indicates whether the request for the waveform change, the subcarrier spacing change, or a combination thereof has been approved.

Images