Transmit using an adapted downlink waveform type

Abstract

Apparatus, methods, and systems for transmission using an adapted downlink waveform type are disclosed. One method (3400) includes dynamically or semi-statically adapting (3402) a downlink waveform type at a network element, wherein: the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmission including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. The method (3400) includes transmitting (3404) using a downlink waveform pattern including the downlink waveform type.

Description

[0001] This application claims priority to U.S. Patent Application Serial No. 62 / 928,649, filed October 31, 2019, entitled “Apparatus, Methods, and Systems for Multiwaveform Support at B52.6 GHz,” which is incorporated herein by reference in its entirety. Technical Field

[0002] The topics disclosed in this article generally relate to wireless communication, and more specifically to transmission using adapted downlink waveform types. Background Art

[0003] The following abbreviations are defined herein, and at least some of them are referenced in the following descriptions: Third Generation Partnership Project (“3GPP”), Fifth Generation (“5G”), QoS for NR V2X Communication (“5QI / PQI”), Authentication, Authorization and Accounting (“AAA”), Positive Acknowledgment (“ACK”), Application Function (“AF”), Authentication and Key Protocol (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Server (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Additive White Gaussian Noise (“AWGN”), Background Data (“BD”). Background Data Transmission (“BDT”), Beam Fault Detection (“BFD”), Beam Fault Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Portfolio (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Contention-Based Random Access (“CBRA”), Idle Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Elements (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”) Control Elements (“CE”), Contention-Free Random Access (“CFRA”), Configurable License (“CG”), Closed Loop (“CL”), Cubic Metric (“CM”), Coordinated Multipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Device-to-Device (“D2D”), Discrete Fourier Transform (“DFT”), Discrete Fourier Transform Extension (“DFTS”), Discrete Fourier Transform Extension The following are included: Orthogonal Frequency Division Multiplexing (“DFT-s-OFDM”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Receive (“DRX”), Dedicated Short Range Communication (“DSRC”), Downlink Pilot Time Slots (“DwPTS”), Enhanced Idle Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), and Effective Isotropic Radiated Power (“EIRP”).The European Telecommunications Standards Institute (“ETSI”), Frame-Based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Equalization (“FDE”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Coverage Code (“FD-OCC”), Frequency Range 1–6 GHz and / or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2–24.25 GHz to 52.6 GHz (“FR2”), Common Geographic Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Electricity service (“GPRS”), protection period (“GP”), Global Positioning System (“GPS”), Universal Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”), Hardware (“HW”), Integrated Access and Backhaul (“IAB”), Identifier or identifier (“ID”), Inverse DFT (“IDFT”), Information Element (“…”) IE”), Industrial Internet of Things (“IIoT”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Key Management Function (“KMF”), Key Performance Indicators (“KPI”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load-Based Device (“LBE”), Listen Before Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Priority (“LCP”), Log-Likelihood Ratio (“LL”) R), Line of Sight (“LOS”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Media Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Maximum Bit Rate (“MBR”), Minimum Communication Range (“MCR”), Modulation and Coding Scheme (“MCS”), Master Information Block (“MIB”), Multimedia Internet Keying (“MIKEY”), Multiple Input Multiple Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Mobile Initiation (“MO”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine Type Communication (“MTC”)Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Negative Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Function (“NF”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), License-Free NR (“NR-U”), Network Repository Function (“NRF”), Network Scheduling Mode (“NS Mode”) (e.g., Network Scheduling Mode for V2X Communication Resource Allocation—Mode-1 in NR V2X and LTE) In V2X, the following are considered: Mode 3, Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation, Management and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open Loop (“OL”), Other System Information (“OSI”), Peak-to-Average Power Ratio (“PAPR”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE Interface (“PC5”), Policy and Charging Control (“PCC”), Primary Cell (“PC…”). Physical downlink control channel (“PDCCH”), physical downlink shared channel (“PDSCH”), physical downlink control function (“PCF”), physical cell identifier (“PCI”), physical downlink control channel (“PDCCH”), packet data convergence protocol (“PDCP”), packet data network gateway (“PGW”), physical downlink shared channel (“PDCCH”), pattern division multiple access (“PDMA”), packet data unit (“PDU”), physical hybrid ARQ indicator channel (“PHICH”), power headroom (“PH”), power headroom report (“PHR”), physical layer (“PHY”), path loss (“PL”), public land mobile network (“PLMN”), phase noise (“PN”), PC5 QoS Class Identifier (“PQI”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Proximity Service (“ProSe”), Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Primary Synchronization Signal (“PSS”), Phase Tracking Reference Signal (“PT-RS”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), Quadrature Amplitude Modulation (“QAM”), QoS Class Identifier (“QCI”), Quadrature Co-location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”).Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (serving Uu), Other RAT (“RAT-2”) (no service for Uu), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Block Assignment (“RBA”), Resource Element (“RE”), Resource Element Group (“REG”), Radio Link Control (“RLC”), RLC Acknowledgment Mode (“RLC-AM”), RLC Unacknowledgment Mode / Transparent Mode (“RLC-UM / TM”) Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Residual Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Extended Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Reference Signal Received Quality (“RSRQ”), Received Signal Strength Indicator (“RSSI”), Round Trip Time (“RTT”), Receive (“RX”), Single Carrier (“SC”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”) Single-Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Serving Data Unit (“SDU”), Security Anchor Function (“SEAF”), Sidelink Feedback Content Information (“SFCI”), Serving Gateway (“SGW”), System Information Block (“SIB”), System Information Block Type 1 (“SIB1”), System Information Block Type 2 (“SIB2”), Subscriber Identifier / Identification Module (“SIM”), Signal-to-Interference-plus-Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”). Sidelink Synchronization Signal (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Auxiliary Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSIRS (“S-CSIRS”), Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Auxiliary Synchronization Signal (“SSS”), Subscription Hidden Identifier (“SUCI”)Scheduled User Equipment (“SUE”), Supplemental Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Timing Advance (“TA”), Timing Calibration Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identifier (“TMSI”), Time of Flight (“ToF”), Transmit Power Control (“TPC”), Transmit Receive Point (“TRP”), Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”) (e.g., V2X UE), UE Autonomy Mode (UE autonomously selects V2X communication resources - e.g., Mode 2 in NR V2X and LTE) Mode 4 in V2X. UE autonomy can be based on or not based on resource sensing operations, uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), user plane (“UP”), UP function (“UPF”), uplink pilot slot (“UpPTS”), ultra-reliable low-latency communication (“URLLC”), UE routing strategy (“URSP”), vehicle-to-vehicle (“V2V”), vehicle-to-everything (“V2X”), V2X UE (e.g., a UE capable of vehicular communication using 3GPP protocols), access AMF (“vAMF”), V2X encryption key (“VEK”), V2X group key (“VGK”), V2X MIKEY key (“VMK”), access NSSF (“vNSSF”), access PLMN (“VPLMN”), V2X service key (“VTK”), wide area network (“WAN”), waveform frequency (“WF”), and global microwave access interoperability (“WiMAX”). ,

[0004] Different waveform types may be used in some wireless communication networks. Summary of the Invention

[0005] Methods for transmission using adapted downlink waveform types are disclosed. Apparatus and systems also perform the functions of these methods. One embodiment of a method includes dynamically or semi-statically adapting a downlink waveform type at a network element, wherein: the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmission including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. In some embodiments, the method includes transmitting using a downlink waveform pattern including the downlink waveform type.

[0006] An apparatus for transmission using an adapted downlink waveform type includes a processor that dynamically or semi-statically adapts the downlink waveform type at a network element, wherein: the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmission including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. In various embodiments, the apparatus includes a transmitter that transmits using a downlink waveform pattern including the downlink waveform type.

[0007] Another embodiment of the method for transmission includes transmitting a measurement report to a network unit, wherein: the measurement report includes information indicating phase noise power; the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0008] Another means for transmission includes a transmitter that transmits a measurement report to a network unit, wherein: the measurement report includes information indicating phase noise power; the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0009] Another embodiment of the method for transmission includes transmitting uplink control signaling to a network element, wherein: the uplink control signaling is used to request a change in downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network element, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0010] Another means for transmission includes a transmitter that transmits uplink control signaling to a network element, wherein: the uplink control signaling is used to request a change in the downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network element, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0011] Furthermore, another embodiment of the method includes modifying at least one physical downlink channel structure to support discrete Fourier transform extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combination thereof.

[0012] Furthermore, another device includes a processor that modifies at least one physical downlink channel structure to support discrete Fourier transform extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combination thereof. Attached Figure Description

[0013] A more detailed description of the embodiments briefly described above will be presented by referring to the 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, wherein:

[0014] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for transmission using an adapted downlink waveform type.

[0015] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used for transmission using an adapted downlink waveform type;

[0016] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used for transmission using an adapted downlink waveform type;

[0017] Figure 4 This is a diagram illustrating one embodiment of the SSB structure used in CP-OFDM;

[0018] Figure 5 This is an illustration of an embodiment of an SSB scan with different waveforms for the first SS block of the first burst set;

[0019] Figure 6 This is an illustration of an embodiment of an SSB scan with different waveforms for the second SS block of the first burst set;

[0020] Figure 7 This is an illustration of an embodiment of an SSB scan with different waveforms for the third SS block of the first burst set;

[0021] Figure 8 This is an illustration of an embodiment of an SSB scan with different waveforms for the fourth SS block of the first burst set;

[0022] Figure 9 This is an illustration of an embodiment of an SSB scan with different waveforms for the first SS block of the second burst set;

[0023] Figure 10 This is an illustration of an embodiment of an SSB scan with different waveforms for the second SS block of the second burst set;

[0024] Figure 11 This is an illustration of an embodiment of an SSB scan with different waveforms for the third SS block of the second burst set;

[0025] Figure 12 This is an illustration of an embodiment of an SSB scan with different waveforms for the fourth SS block of the second burst set;

[0026] Figure 13 This is a diagram illustrating one embodiment of a time slot with mixed waveforms;

[0027] Figure 14 It is a diagram. Figure 13 A continuation of the illustration of the embodiments;

[0028] Figure 15 This is a graph illustrating an embodiment of the RF nonlinearity effect with respect to different modulation orders;

[0029] Figure 16 This is a diagram illustrating one embodiment of DL waveform switching;

[0030] Figure 17 It is a diagram. Figure 16 A continuation of the illustration of the embodiments;

[0031] Figure 18 It is a diagram. Figure 16 and Figure 17 A continuation of the illustration of the embodiments;

[0032] Figure 19 This is a diagram illustrating one embodiment of UE rescheduling;

[0033] Figure 20 This is a communication diagram illustrating one embodiment of the signaling process used for waveform selection;

[0034] Figure 21 This is a diagram illustrating one embodiment of an SSB design for DFT-s-OFDM (e.g., Option 1);

[0035] Figure 22 This is an illustration of another embodiment of an SSB design for DFT-s-OFDM (e.g., Option 2);

[0036] Figure 23 This is a diagram illustrating an embodiment of the PDCCH design;

[0037] Figure 24 It is a diagram. Figure 23 A diagram illustrating the continuation of the PDCCH design;

[0038] Figure 25 It is a diagram. Figure 23 and Figure 24 A diagram illustrating the continuation of the PDCCH design;

[0039] Figure 26 It is a diagram. Figure 23 , Figure 24 and Figure 25 A diagram illustrating the continuation of the PDCCH design;

[0040] Figure 27 It is a diagram. Figure 23 , Figure 24 , Figure 25 and Figure 26 A diagram illustrating the continuation of the PDCCH design;

[0041] Figure 28 This is a diagram illustrating one embodiment of a previous DFT PT-RS mapping used for PDCCH;

[0042] Figure 29 It is used for illustration. Figure 28 A diagram illustrating the continuation of the previous DFT PT-RS mapping of the PDCCH;

[0043] Figure 30 The diagram is used for Figure 28 and Figure 29 A diagram illustrating the continuation of the previous DFT PT-RS mapping of the PDCCH;

[0044] Figure 31 The diagram is used for Figure 28 , Figure 29 and Figure 30 A diagram illustrating the continuation of the previous DFT PT-RS mapping of the PDCCH;

[0045] Figure 32 This is a diagram illustrating an embodiment of DFT-s-OFDM based on PDSCH;

[0046] Figure 33 It is a diagram. Figure 32 A continuation diagram of PDSCH-based DFT-s-OFDM;

[0047] Figure 34 This is a flowchart illustrating an embodiment of a method for transmission using an adapted downlink waveform type;

[0048] Figure 35 This is a flowchart illustrating another embodiment of the method for transmission;

[0049] Figure 36 This is a flowchart illustrating yet another embodiment of the method for transmission; and

[0050] Figure 37 This is a flowchart illustrating an embodiment of a method for modifying channel structure. Detailed Implementation

[0051] 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 may generally be referred to herein as "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.

[0052] 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.

[0053] Modules can also be implemented in code and / or software for execution by various types of processors. The identified code module can, for example, comprise one or more physical or logical blocks of executable code, which can, for example, be organized as objects, procedures, or functions. However, the executable files of the identified modules do not need to be physically located together and can include unrelated instructions stored in different locations that, when logically combined, comprise the module and achieve the module's stated purpose.

[0054] 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 spanning 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.

[0055] Any combination of one or more computer-readable media can be used. A computer-readable medium can be a computer-readable storage medium. A computer-readable storage medium can be a storage device for storing code. A storage device can 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.

[0056] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections with one or more cables, 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.

[0057] 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, C++, and common procedural programming languages ​​such as "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, partially on the user's computer as a standalone software package, 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 can be connected to an external computer (e.g., via the Internet through an Internet service provider).

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

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

[0060] The following description of aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the 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 / operations specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0061] 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 that implements the function / operation specified in the schematic flowchart and / or schematic block diagram boxes or blocks.

[0062] 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 for implementing the function / operation specified in the boxes or blocks of the flowchart and / or block diagram.

[0063] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, system, method, 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.

[0064] It should also be noted that in some alternative implementations, the functions annotated in the boxes may occur in a different order than those annotated in the figures. For example, depending on the functions involved, two boxes shown consecutively may actually be performed substantially simultaneously, or these boxes may sometimes be performed in reverse order. It is conceivable that other steps and methods are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures.

[0065] While various arrow and line types may be employed in flowcharts and / or block diagrams, understanding them does not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiments. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumerated steps in a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, as well as combinations of blocks in block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system performing a specific function or operation, or by a combination of dedicated hardware and code.

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

[0067] Figure 1 An embodiment of a wireless communication system 100 for transmission using an adapted downlink waveform type 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.

[0068] 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.

[0069] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as an access point, access terminal, base station, base station, node-B, eNB, gNB, home node-B, relay node, device, core network, air server, wireless access node, AP, NR, network entity, AMF, UDM, UDR, UDM / UDR, PCF, RAN, NSSF, AS, NEF, key management server, KMF, 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, etc. 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.

[0070] In one implementation, the wireless communication system 100 conforms to the standardized NR protocol in 3GPP, wherein network unit 104 transmits over DL using an OFDM modulation scheme, and remote unit 102 transmits over UL using an SC-FDMA scheme or an OFDM scheme. However, more generally, the wireless communication system 100 can implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, etc. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0071] 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 remote units 102 in the time, frequency, and / or spatial domains.

[0072] In various embodiments, network unit 104 can dynamically or semi-statically adapt to a downlink waveform type, wherein the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. In some embodiments, network unit 104 can use a downlink waveform pattern including the downlink waveform type to transmit transmissions. Therefore, network unit 104 can be used for transmissions using the adapted downlink waveform type.

[0073] In some embodiments, remote unit 102 may transmit a measurement report to a network unit (e.g., network unit 104), wherein: the measurement report includes information indicating phase noise power; the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. Therefore, remote unit 102 can be used for transmission.

[0074] In some embodiments, remote unit 102 may transmit uplink control signaling to a network unit (e.g., network unit 104), wherein: the uplink control signaling is used to request a change in the downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. Therefore, remote unit 102 can be used for transmission.

[0075] In various embodiments, remote unit 102 and / or network unit 104 can modify at least one physical downlink channel structure to support discrete Fourier transform extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combinations thereof. Therefore, remote unit 102 and / or network unit 104 can be used to modify the channel structure.

[0076] Figure 2An embodiment of a device 200 that can be used for transmission using an adapted downlink waveform type is depicted. 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.

[0077] 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.

[0078] 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 associated data, such as an operating system or other controller algorithms operating on remote unit 102.

[0079] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, 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, allowing text to be entered 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.

[0080] 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, LCD displays, LED displays, OLED displays, projectors, 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.

[0081] 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 positioned near input device 206.

[0082] In various embodiments, transmitter 210 may transmit a measurement report to a network unit (e.g., network unit 104), wherein: the measurement report includes information indicating phase noise power; the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0083] In some embodiments, transmitter 210 may transmit uplink control signaling to a network element (e.g., network element 104), wherein: the uplink control signaling is used to request a change in the downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network element, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0084] The processor 202 can modify at least one physical downlink channel structure to support discrete Fourier transform extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combinations thereof.

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

[0086] Figure 3 An embodiment of a device 300 that can be used for transmission using an adapted downlink waveform type 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. It will be understood that the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0087] In some embodiments, processor 302 may dynamically or semi-statically adapt the downlink waveform type at a network unit (e.g., network unit 104), wherein the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. In various embodiments, transmitter 310 may use a downlink waveform pattern including the downlink waveform type to transmit transmissions.

[0088] The processor 302 can modify at least one physical downlink channel structure to support discrete Fourier transform extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combinations thereof.

[0089] In some embodiments, transmitter 310 may be used to transmit the information described herein and / or processor 302 may be used to process the information described herein.

[0090] In various embodiments, the system may exhibit high path loss. In such systems, the RF components of the transmitter and / or receiver may exhibit nonlinear transmission characteristics, leading to further system degradation. Certain embodiments described herein can improve upon these shortcomings.

[0091] In some embodiments, multi-carrier (e.g., OFDM) based waveforms can be used for DL ​​and / or UL transmissions. In some embodiments, such as at cell edges, single-carrier (e.g., DFT-s-OFDM) can be used for UL transmissions. In various embodiments, CP-OFDM performance may degrade at high frequencies (e.g., B52.6 GHz) due to its sensitivity to phase noise and its high PAPR or CM, which limits cell coverage. In some embodiments, the high-frequency problems of CP-OFDM may become more severe with increasing modulation order and / or channel bandwidth. In such embodiments, some physical layer channels may be more affected than others.

[0092] In some embodiments, single-carrier waveforms may be suitable candidates at high frequencies due to their natural robustness to phase noise and their low PAPR or CM. In various embodiments, power constraints at the cell edge may necessitate enhancing UL transmission, and employing other single-carrier waveforms such as SC-QAM, SC-FDE, and / or CP-SC for cell edge scenarios.

[0093] In some embodiments, while DFT-s-OFDM or other single-carrier candidates are used for DL ​​enhancement of cell coverage, DFT-s-OFDM or other single-carrier candidates may limit the system's MIMO capabilities and / or reduce the flexibility of DMRS mapping. In some embodiments, such as high data rate eMBB, high throughput may require high channel bandwidth. In such embodiments, MIMO can play a significant role. In various embodiments, such as in factory automation and / or IIoT applications, latency, massive access, and reliability may be key performance indicators (KPIs). In some embodiments, backhaul and / or IAB typically operate under LOS conditions where fading and power consumption are not major concerns. In some embodiments, mobile data offloading may need to coexist with other systems (e.g., Wi-Fi@60GHz). In various embodiments, such as for short-range high data rate D2D communication, coverage may be limited and PAPR issues may not be significant. In some embodiments, trade-offs between cell coverage requirements and QoS requirements in terms of latency and throughput can be considered to support different deployment and use cases.

[0094] In some embodiments, multiple waveforms can be used. In such embodiments, the gNB can be configured via RRC to switch between multi-carrier CP-OFDM and single-carrier DFT-s-OFDM. In such embodiments, the higher-level parameter transformPrecoder in pusch-Config, configuredGrantConfig, or msg3-transformPrecoderin RACH-ConfigCommon can provide indications for enabling and / or disabling the transform precoder for PUSCH. In various embodiments, the UE can consider "enabling" or "disabling" transform precoding based on read messages, and the gNB can apply simultaneous reception from multiple UEs with different waveforms.

[0095] In some embodiments, such as for a DL with multiple waveforms selected by the gNB based on factors such as the carrier frequency used, UE measurements (e.g., RSRP, RSRQ, SINR), location, UE and gNB RF capabilities, UE power status (e.g., PH report), and / or UE auxiliary information (e.g., DL transform precoding recommendation based on PL estimation), the UE battery can help the gNB select the correct WF because some waveforms require higher signal processing reception complexity than others, and thus save some UE power based on the critical battery power status.

[0096] In some embodiments, an SS block includes a PSS, an SSS, and a PBCH, and is transmitted periodically with a period of 5 ms to 160 ms. In various embodiments, beam scanning can be applied to SS block transmission, thus enabling the transmission of SS blocks with different beams via time multiplexing. In some embodiments, the set of SS blocks within a beam scan is referred to as an SS burst set, and the SS block period can be the time between SS block transmissions within a specific beam, which is the periodicity of the SS burst set. In various embodiments, the SS burst set periodicity can be flexible, having a minimum period of 5 ms to a maximum period of 160 ms, and each SS burst set can be limited to a 5 ms time interval.

[0097] In some embodiments, the maximum number of SS blocks within an SS burst set may vary for different frequency ranges. For example, for bands below 3 GHz, an SS burst set may contain up to four SS blocks, thus enabling SS block beam scanning up to four beams. As another example, for bands between 3 GHz and 6 GHz, an SS burst set may contain up to eight SS blocks, allowing SS block beam scanning up to eight beams. In yet another example, for bands above 6 GHz (e.g., FR2), an SS burst set may contain up to 64 SS blocks, allowing SS block beam scanning up to 64 beams.

[0098] In some embodiments, the temporal location of an SS block can depend on the SS block parameter set, and possible candidate locations in a time slot can be the first SS block location corresponding to symbols 2 and 5, and the second possible SS block location can correspond to symbols 8 through 11. In various embodiments, the first and last two symbols in a time slot may not be used for SS block transmission, as they are used to transmit DL and UL control signaling. In some embodiments, the SS block time index identifies the SS block location within an SS burst set, and half-frame bits identify the SS block in the first or second 5ms of a 10ms frame. In such embodiments, the SS block time index is different for different SS blocks in the burst set. Furthermore, SSB blocks do not need to be transmitted at the center frequency of the carrier, and the offset from the PBCH payload can indicate the offset between the SS block and the common resource block grid, while SIB1 indicates the absolute location of the SS block in the carrier.

[0099] Figure 4 This is a diagram illustrating one embodiment of the SSB structure 400 used in CP-OFDM. For example... Figure 4The SSB structure 400 shown occupies a total of 20 RBs and spans 4 OFDM symbols. The first symbol is used for the primary synchronization signal 404, the second and fourth symbols are used for PBCH 408 and DMRS 410, and the third symbol is used for the auxiliary synchronization symbol 406, which is multiplexed with the rest of PBCH 408 and DMRS 410 in the frequency domain. Table 1 shows an example of the correspondence between parameter sets and SSB bandwidths.

[0100] Table 1

[0101] Parameter set (kHz) SSB bandwidth (MHz) 15 3.6 30 7.2 120 28.8 240 57.6

[0102] In some embodiments, to achieve high system flexibility and optimize performance in terms of coverage and throughput for different deployments and use cases, waveform switching schemes at frequencies higher than 52.6 GHz can be used for DL ​​and / or UL transmissions. In such embodiments, based on TA and UE measurement reports, the gNB switches between CP-OFDM and single-carrier waveforms such as DFT-s-OFDM for DL ​​transmissions, and between DFT-s-OFDM, SC-FDE, and / or CP-SC for UL transmissions. As can be understood, single-carrier waveforms such as DFT-s-OFDM and SC-FDE can have lower PAPR compared to OFDM, and thus can improve network coverage. However, OFDM may have better support for MIMO, better spectral efficiency, and more efficient RS placement in the time-frequency grid compared to SC waveforms. On the other hand, for simplicity, some UEs may only be equipped with one waveform. Therefore, multi-waveform support for DL ​​and UL transmissions may be a practical solution to adapt to different deployments, coverage areas, and use cases. In some embodiments, employing DFT-s-OFDM for DL ​​transmission may require modifications to physical layer channels, signals, and / or procedures. Certain embodiments described herein relate to implementations of different DL channels to support DFT-s-OFDM.

[0103] It should be noted that although DFT-s-OFDM is used as an example of a single-carrier waveform to explain different implementations, other single-carrier waveform designs are not excluded.

[0104] In a first embodiment, multiple waveforms (e.g., single-carrier and multi-carrier) can be configured for the BS (e.g., gNB) and UE. In such an embodiment, the UE can perform waveform switching (e.g., the UE can use FDM and / or TDM).

[0105] In the first embodiment, various options for multi-waveform support for the gNB and UE can be used. As an example, the existing baseband HW of the gNB and / or UE can be upgraded to support FR4 and can support both multi-carrier and single-carrier waveforms for DL ​​transmission, while a new baseband HW for the UE may only support one waveform. In the first embodiment, multiple waveforms for certain data channels and / or control channels can be semi-statically configured for the BWP and can be switched by signaling to the UE or dynamically based on measurement reports.

[0106] In the first option corresponding to the first embodiment, the SS burst set can alternatively or use a predetermined pattern to transmit with single-carrier and multi-carrier waveforms to benefit UEs that only support one waveform (e.g., for initial access). As an example, if there are 64 SS blocks in a burst set, the 64 SS blocks in one burst set are first transmitted using a single-carrier waveform, and then the next 64 SS blocks in the burst set are transmitted using a multi-carrier waveform. In the first option, a semi-static DL slot configuration can be used to schedule PDSCHs with one of the waveforms.

[0107] In the second option corresponding to the first embodiment, SS blocks can be transmitted alternately using single-carrier waveforms and multi-carrier waveforms. For example, odd-numbered SS blocks are transmitted using a single-carrier waveform in a burst set, and even-numbered SS blocks are transmitted using a multi-carrier waveform in a burst set, and the reverse is true for the next burst set, where odd-numbered SS blocks are transmitted using a multi-carrier waveform, and even-numbered SS blocks are transmitted using a single-carrier waveform.

[0108] In both the first and second options, the SSB can carry an indication of a pattern for alternating different burst sets of waveforms. This allows the UE to skip using an SSB or burst set of an unsupported waveform. In one example, a combination of PSS, SSS, and / or PSS / SSS can indicate the periodicity of the pattern, or the payload in the PBCH can indicate the periodicity of the pattern.

[0109] If understandable, one or more of the above options, or parts of the above options, can be combined.

[0110] Figures 5 to 8 The illustration shows an embodiment of the first four SS blocks in the first burst set according to the second option, and Figures 9 to 12 The illustration shows an embodiment of the first four SS blocks in the second burst set according to the second option.

[0111] Figure 5This is a diagram illustrating one embodiment of an SSB scan with different waveforms for the first SS block 500 of the first burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 504, the second and fourth symbols are used for PBCH 508 and DMRS 510, and the third symbol is used for the auxiliary synchronization symbol 506 multiplexed with the remainder of PBCH 508 and DMRS 510. A first beam pattern 512 is used.

[0112] Figure 6 This is a diagram illustrating an embodiment of an SSB scan with different waveforms for a second SS block 600 of a first burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 602, the fourth symbol is used for the secondary synchronization symbol 604, the second and fifth symbols are used for PBCH 606, and the third symbol is used for DMRS 608. A second beam pattern 610 is used.

[0113] Figure 7 This is a diagram illustrating one embodiment of an SSB scan with different waveforms for the third SS block 700 of the first burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 704, the second and fourth symbols are used for PBCH 708 and DMRS 710, and the third symbol is used for the auxiliary synchronization symbol 706 multiplexed with the remainder of PBCH 708 and DMRS 710. A third beam pattern 712 is used.

[0114] Figure 8 This is a diagram illustrating an embodiment of an SSB scan with different waveforms for the fourth SS block 800 of the first burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 802, the fourth symbol is used for the auxiliary synchronization symbol 804, the second and fifth symbols are used for PBCH 806, and the third symbol is used for DMRS 808. A fourth beam pattern 810 is used.

[0115] Figure 9 This is a diagram illustrating an embodiment of an SSB scan with different waveforms for the first SS block 900 of the second burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 902, the fourth symbol is used for the secondary synchronization symbol 904, the second and fifth symbols are used for PBCH 906, and the third symbol is used for DMRS 908. A first beam pattern 910 is used.

[0116] Figure 10This is a diagram illustrating an embodiment of an SSB scan with different waveforms for the second SS block 1000 of the second burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 1002, the second and fourth symbols are used for PBCH 1006 and DMRS 1008, and the third symbol is used for the auxiliary synchronization symbol 1004 multiplexed with the remainder of PBCH 1006 and DMRS 1008. A second beam pattern 1010 is used.

[0117] Figure 11 This is a diagram illustrating an embodiment of an SSB scan with different waveforms for the third SS block 1100 of the second burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 1102, the fourth symbol is used for the auxiliary synchronization symbol 1104, the second and fifth symbols are used for PBCH 1106, and the third symbol is used for DMRS 1108. A third beam pattern 1110 is used.

[0118] Figure 12 This is a diagram illustrating one embodiment of an SSB scan with different waveforms for the fourth SS block 1200 of the second burst set. In the frequency domain, the first symbol is used for the primary synchronization signal 1204, the second and fourth symbols are used for PBCH 1208 and DMRS 1210, and the third symbol is used for the auxiliary synchronization symbol 1206 multiplexed with the remainder of PBCH 1208 and DMRS 1210. A fourth beam pattern 1212 is used.

[0119] In the third option, each DL, UL, or SL BWP in the carrier can be semi-statically configured for mixed waveforms in time slots, radio frames, or subframes. In one implementation, single-carrier or multi-carrier waveforms are used for the DL data channel (e.g., PDSCH), while CP-OFDM is used for SSB, RMSI, and PDCCH, as... Figure 13 and Figure 14 As shown in the diagram. The motivation for doing so is that these channels use low modulation orders and occupy less bandwidth than data channels, and are less affected by RF nonlinearity. In one implementation, in symbols where SSB exists, PDSCH can use CP-OFDM with a low modulation order.

[0120] Figure 13 This is illustration 1300, showing an embodiment of time slots with mixed waveforms. Illustration 1300 illustrates PSS 1304, SSS 1306, PBCH 1308, and DMRS 1310. CP-OFDM PDCCH occupies the first time slot 1312, DFT-s-OFDM PDSCH occupies the second time slot 1314, and CP-OFDM SSB occupies the third time slot 1316.

[0121] Figure 14 It is a diagram. Figure 13 The continuation of the embodiment is illustrated in diagram 1400. DFT-s-OFDM PDSCH occupies... Figure 13 The fourth time period is 1402, following the third time period 1316. Diagram 1400 includes PBCH 1404 and DMRS 1406.

[0122] Figure 15 Simulation results for CP-OFDM with and without RF nonlinearity using a memoryless Rapp model and AWGN channels are shown. As depicted in the figure, the performance degradation level increases with increasing modulation order.

[0123] Figure 15 This is a graph illustrating an embodiment of the RF nonlinear effect for different modulation orders. The first curve 1502 corresponds to QPSK with RF attenuation, the second curve 1504 corresponds to QPSK without RF attenuation, the third curve 1506 corresponds to 16QAM without RF attenuation, the fourth curve 1508 corresponds to 16QAM with RF attenuation, the fifth curve 1510 corresponds to 64QAM without RF impedance, and the sixth curve 1512 corresponds to 64QAM with RF attenuation.

[0124] In some embodiments, the PAPR of CP-OFDM may be independent of the modulation order. Therefore, in such embodiments, to enhance PDCCH performance, a higher AL (e.g., >16) can be applied, and a larger SSB bandwidth can be used.

[0125] In the fourth option of the first embodiment, the BS can signal the selected waveform to the UE. In the fourth option, a bit field can be included in the DCI to indicate the selected waveform for the PDSCH portion used for dynamic waveform selection. In the fourth option, "0" can indicate a single-carrier waveform, and "1" can indicate a multi-carrier waveform, and / or additional bits can indicate one or more types of single-carrier or multi-carrier waveforms, such as SC-QAM and / or SC-FDE. One or more bits can also indicate the time slot or symbol offset at which PDSCH transmission with the new waveform should begin. Multiple waveforms can coexist in the same time slot, radio frame, and / or subframe, or can coexist in different BWPs within a carrier. In some embodiments, if the UE receives a DCI in the same time slot indicating the type of waveform to be used for PDSCH, the UE can be configured with flexible or protected symbols or time slots if additional time is needed for waveform switching.

[0126] In various embodiments, the gNB may indicate a new waveform BWP together with a waveform indicator in the DCI, using a specific DCI format or a combination thereof. In such embodiments, the UE may perform BWP handover and waveform handover for a new active BWP indicated by the gNB in ​​the DCI. As will be understood, while certain embodiments may be described herein for downlink, they may also be applicable to uplink and / or sidelinks.

[0127] In the fifth option, the gNB can select an appropriate waveform (e.g., single-carrier or multi-carrier) for the PDSCH based on one or more of the UE's TA value, UE measurement reports (e.g., RSRP, RSRQ and / or SINR), UE measurement location, UE power state (e.g., PH report), UE auxiliary information (e.g., DL transform precoding recommendations, such as those based on PL estimation), and / or UE capabilities that support single-carrier and multi-carrier waveforms.

[0128] In the sixth option, the semi-static mapping of waveforms for PDSCH to DL BWP, PUSCH to UL BWP, or PSSCH to SL BWP can be signaled in the SIB or via RRC signaling, so that the UE knows the waveform support for PDSCH in each BWP. In the sixth option, based on UE measurements, the UE can use UL control signaling to initiate a request to the gNB for BWP adaptation. In some embodiments, BWP information may include information indicating whether only one waveform is configured for the BWP, a mixed waveform is configured for the BWP, and / or multiple waveforms are configured for the BWP.

[0129] In one implementation of the sixth option, the UE may have different SR configurations for different waveforms (e.g., single-carrier or multi-carrier), and the UE may initiate a request to change the waveform used to transmit a specific SR. In another implementation of the sixth option, a BSR transmission or MAC CE transmission from the UE may indicate a request for the sixth option. L1-PUCCH signaling may be used to indicate this request, and / or a UE measurement report may also be used to indicate this request.

[0130] Based on the selection decision, the gNB can change the waveform of a specific UE on its current BWP. An indication to switch the WF to the next time slot can be sent in the current BWP with the current WF, such as... Figures 16 to 18 As shown in the diagram, or the UE can be rescheduled to a different BWP that has been configured with the appropriate waveform, such as... Figure 19 As shown in the image.

[0131] Figure 16This is illustration 1600, showing one embodiment of DL waveform switching. In the frequency domain, the first symbol is used for the primary synchronization signal 1604, the second and fourth symbols are used for PBCH 1608 and DMRS 1610, and the third symbol is used for the auxiliary synchronization symbol 1606, multiplexed with the remainder of PBCH 1608 and DMRS 1610. Illustration 1600 illustrates the SSB using the waveform CP-OFDM. The first indicator 1612 and / or the second indicator 1614 can be used to indicate the waveform for switching the next time slot.

[0132] Figure 17 It is a diagram. Figure 16 A continuation of the embodiment is illustrated in Figure 1700. Figure 1700 illustrates DMRS 1702 and 1706, and PBCH 1704 and 1708, transmitting PDCCH 1710 and PDSCH 1712 using DFT-s-OFDM waveforms. A second indication 1614 can be used to indicate switching the waveform from the previous time slot to the current time slot, and / or a third indication 1714 can be used to indicate switching the waveform for the next time slot.

[0133] Figure 18 It is a diagram. Figure 16 and Figure 17 The illustration continues from the embodiment in diagram 1800. In the frequency domain, the first symbol is used for the primary synchronization signal 1802, the fourth symbol is used for the auxiliary synchronization symbol 1804, the second and fifth symbols are used for PBCH 1806, and the third symbol is used for DMRS 1808. The fourth indicator 1810 can be used to indicate the waveform for the next time slot switching.

[0134] Figure 19 This is illustration 1900, depicting an embodiment of UE rescheduling. A first BWP 1902 can be used to transmit a CP-OFDM 1904 waveform, while a second BWP 1906 can be used to transmit a DFT-s-OFDM 1908 waveform. Signal 1910 can be used to transmit an indication of switching from the CP-OFDM 1904 waveform of the first BWP 1902 to the DFT-s-OFDM 1908 waveform of the second BWP 1906.

[0135] The second embodiment can be used for waveform selection and / or indication. In the second embodiment, the gNB selects the initial waveform for initial access for different DL channels based on carrier frequency, cell size, deployment, and usage scenario.

[0136] In a second embodiment, the PSS sequence carries information about the waveform used for the PBCH, or the sequence can be encoded with a waveform indicator. In such an embodiment, after decoding the PSS or SSS, the UE begins demodulating and decoding the PBCH with the corresponding waveform indicator. This indicator can also implicitly inform the UE about the location of DMRS and PBCH resources (e.g., waveform-related pre-configuration).

[0137] In the second embodiment, the PBCH-DMRS or PBCH payload carries indications of waveforms for CORESET_type0 and SIB. Based on RACH TA, the gNB indicates the waveforms that will be used by the individual UEs for PUSCH Msg3 and subsequent DL and / or UL messages.

[0138] In the second embodiment, UEs with different RF front-ends may observe different phase noise powers, and temperature variations in the RF model may also cause PN to change over time. Therefore, the UE needs to monitor PT-RS and report the phase noise power to the gNB. Furthermore, other common parameters reported by the UE, such as RSRP, CSI, and battery status, can help the gNB perform waveform selection.

[0139] Based on the UE measurement report, the gNB selects the appropriate waveform for the control and data of both UL and DL. The selection criteria can be based on the following parameters: PN, CSI, QoS requirements, UE power consumption (e.g., battery state), and / or location.

[0140] Figure 20The diagram illustrates a signaling procedure 2000 for waveform switching between the gNB and the UE. Signaling procedure 2000 includes communications transmitted between the gNB 2002 and the UE 2004. A first communication 2006 can be used to transmit a PSS from the gNB 2002 to the UE 2004, where the PSS sequence indicates the PBCH waveform. A second communication 2008 can be used to transmit an SSS and / or PBCH from the gNB 2002 to the UE 2004. The PBCH DMRS can indicate the CORESET_type0 and / or SIB waveform. A third communication 2010 can be used to transmit an SIB from the gNB 2002 to the UE 2004. A fourth communication 2012 can be used to transmit a RACH from the UE 2004 to the gNB 2002. The gNB 2002 can then select 2014 based on the initial WFTA. A fifth communication 2016 can be used to transmit a RAR from the gNB 2002 to the UE 2004. The sixth communication, 2018, can be used to transmit an attachment between UE 2004 and gNB 2002. The seventh communication, 2020, can be used to transmit CSI-RS and / or PT-RS from gNB 2002 to UE 2004. UE 2004 can perform 2022PN measurements, whereby the UE monitors PT-RS, CSI-RS, reporting capabilities, PN, and / or power status. The eighth communication, 2024, can be used to transmit PUCCH (e.g., PN reporting, CQI) from UE 2004 to gNB 2002. gNB 2002 can perform 2026WF reselection. Selection criteria can be: PN, CSI, QoS requirements, UE power consumption (e.g., battery status), and / or location. The ninth communication, 2028, can be used to transmit WF or BWP handover information from gNB 2002 to UE 2004.

[0141] The third embodiment can be used to perform Uu and / or sidelink waveform switching. In the third embodiment, the UE can be configured with single-carrier or multi-carrier waveforms in the uplink, while SL only supports multi-carrier waveforms. The third embodiment can be described with respect to ULBWP and SL BWP and can also be applied to DL BWP and SL BWP.

[0142] In one implementation of the third embodiment, if the UE switches the waveform from a single-carrier UL BWP to a multi-carrier SL BWP on the same carrier, the UE may need additional handover delay. In the example, the UE can switch to the SL waveform autonomously in the configured side link time slot.

[0143] In another implementation of the third embodiment, based on the priority of UL and / or SL services, if different waveforms are configured, the UE can disable the UL BWP or SL BWP. Disabling the SL BWP can be understood as disabling SL communication on the corresponding carrier and / or serving cell (e.g., the UE cannot transmit or receive SL communication on the configured resource pool). Once the UL BWP and SLBWP support the same waveform, the UE will automatically activate the SL BWP. If the waveform of the currently activated UL BWP is different from that of the SL BWP, the UE will automatically switch to the configured UL BWP, which has the same waveform as the SL BWP. The UE can use L1 signaling to activate and / or disable the SL BWP and / or UL BWP. If the UE supports multiple waveforms for SL communication, the UE can autonomously switch the SL BWP to match the UL or DL ​​waveform. It is permissible for the UE to communicate on an active UL BWP with a different waveform than the SL BWP in a time slot reserved for NR UL, NR SL, or flexible symbols and which is at least a predefined time (e.g., x ms) before the next time slot configured for SL communication (e.g., there may be a gap of at least x ms between NR UL operation and NR SL communication).

[0144] To allow sufficient time for waveform switching, the UE can stop UL transmissions on the active UL BWP for a predefined time (e.g., x ms) before the next SL time slot (e.g., a time slot and / or subframe belonging to the SL resource pool). After UL transmissions have stopped (e.g., the UL BWP is deactivated), the UE automatically switches its waveform to the waveform of the SL BWP to enable SL communication in the next SL time slot and / or subframe. The predefined time for waveform switching can be derived based on RAN4 requirements regarding BWP handover delay. Similarly, the UE stops SL communication (e.g., deactivates the SLBWP) for a predefined time before the next UL time slot to facilitate waveform switching to the active UL BWP. For example, handover delays may introduce UE behavior such as dropping UL and / or SL transmissions, and can be based on the priority of UL and / or SL services, the priority of HARQ-ACK and / or NACK in the PUCCH during UL and SL data transmission, as configured for the UE or in the cell.

[0145] The fourth embodiment may include PBCH-DMRS TDM and / or FDM designs for DFT-s-OFDM.

[0146] In the fourth embodiment, a single-carrier SSB design for the downlink can be used. For example... Figure 21 and Figure 22As shown, the SSB structure for single-carrier waveforms such as DFT-s-OFDM can be designed as PBCH-DMRS with different options. In idle mode, the PBCH waveform can be implicitly indicated using the PSS sequence or its position.

[0147] exist Figure 21 In the first option shown, the minimum PAPR design (e.g., this may depend on the presence of other signals and / or channels on other RBs of the SS and / or PBCH symbols) may require additional symbols for DMRS to perform channel estimation. These additional symbols can be used for TDM with other SSB symbols. Although this may result in lower spectral efficiency compared to CP-OFDM due to the additional DMRS symbols, the PBCH may have a larger payload size and occupy the entire subcarrier compared to a multicarrier waveform, and the SSS may have better frequency protection with a larger frequency guard band. Figure 22 In the second option illustrated, the DMRS can be split into two symbols multiplexed with the PBCH and SSS in the frequency domain, with a small number of RBs used for the DMRS. To ensure adequate channel estimation, the DMRS can be mapped to the middle of the first PBCH symbol and the edge of the SSS symbol. This design avoids additional DMRS symbols; however, it may increase the PAPR of the PBCH compared to DMRS used for TDM.

[0148] Figure 21 This is a diagram 2100 illustrating one embodiment of an SSB design for DFT-s-OFDM (e.g., Option 1). Diagram 2100 illustrates PSS 2102, SSS 2104, PBCH 2106, and DMRS 2108. Figure 22 This is illustration 2200, which illustrates another embodiment (e.g., option 2) of an SSB design for DFT-s-OFDM. Illustration 2200 illustrates PSS2202, SSS2204, PBCH2206, and DMRS2208.

[0149] In the fifth embodiment, a PDDCH with a previous DFT PT-RS can be used for a DFT-s-OFDM waveform.

[0150] In the fifth embodiment, a DFT-s-OFDM waveform for the PDCCH can be used. In such an embodiment, the DL channel design can consider that the single-carrier waveform may be related to the PDCCH CORESET and CCE mapping. For low PAPR transmissions, DMRS cannot be FDMed with data; therefore, additional DMRS symbols can be used before or after the PDCCH.

[0151] Figures 23 to 27 An embodiment of the PDCCH design is shown.

[0152] Figure 23 This is illustration 2300, which illustrates an embodiment of the PDCCH design. Illustration 2300 shows a DCI 2302 received by a CORESET 2304. The CORESET 2304 includes a first CCE 2306, a second CCE 2308, a third CCE 2310, and a fourth CCE 2312.

[0153] Figure 24 It is a diagram. Figure 23 The diagram 2400 is a continuation of the PDCCH design. A DFT can be performed on the CORESET 2304 to produce a CORESET 2402 spanning the frequency 2404.

[0154] Figure 25 It is a diagram. Figure 23 and Figure 24 The PDCCH design is a continuation of diagram 2500. Diagram 2500 is illustrated at time 2502. Diagram 2500 includes CORESET 2506 (e.g., CORESET 2402), PDSCH_1 2510 (multiplexed PDSCH), PDSCH_1 2512, PDSCH_2 2514, DMRS2516, DMRS2518, and DMRS2520.

[0155] Figure 26 It is a diagram. Figure 23 , Figure 24 and Figure 25 The PDCCH design is a continuation of diagram 2600. CORESET 2602 (e.g., CORESET 2506) spanning frequency 2604 can be extracted from the transmission of diagram 2500.

[0156] Figure 27 It is a diagram. Figure 23 , Figure 24 , Figure 25 and Figure 26 The diagram 2700 shows a continuation of the PDCCH design. IDFT can be performed on CORESET 2602 to produce a first CCE 2706, a second CCE 2708, a third CCE 2710, and a fourth CCE 2712. A blind search 2716 can be performed on the first CCE 2706, the second CCE 2708, the third CCE 2710, and the fourth CCE 2712.

[0157] In some embodiments, a DFT operation can be applied to each configured CORESET. To enhance PDCCH performance, the time-domain PT-RS can be mapped to the time-domain RE before the DFT. The PT-RS can be located on a time-domain RE similar to the PDCCH-DMRS frequency spacing used for CP-OFDM, such that the mapping from DCI size to CCE remains unchanged. In one example, the time-domain PTRS REs within the CCE can be bundled (e.g., 2 REs in size), and these bundles can be distributed and / or interleaved within the CCE. In another example, the time-domain PTRS REs within the CCE can be grouped together and placed coherently and / or continuously (e.g., in the middle, at the beginning, and / or near the end of the CCE). High time-density PT-RS tones can be used for PN compensation to enhance PDCCH decoding performance. The UE can begin phase correction based on the PT-RS and channel estimation.

[0158] Figure 28 This is illustration 2800, showing one embodiment of a prior DFT PT-RS mapping for a PDCCH. Illustration 2800 is illustrated at time 2802 (e.g., OFDM symbol) and frequency 2804 (e.g., subcarrier). PDCCH 2806, PDCCH DMRS 2808, PDSCH 2810, PDSCH DMRS 2812, and PDSCH CSI-RS 2814 are illustrated using waveform CP-OFDM.

[0159] Figure 29 It is a diagram. Figure 28 The PDCCH is a continuation of the previous DFT PT-RS mapping in diagram 2900. In diagram 2900, the OFDM symbols of diagram 2800 can be converted to CCEs. DCI 2902 is used to obtain CORESET 2904. CORESET 2904 includes a first CCE 2906, a second CCE 2908, a third CCE 2910, and a fourth CCE 2912 using DFT-s-OFDM waveforms.

[0160] Figure 30 It is a diagram. Figure 28 and Figure 29 The continuation of the previous DFT PT-RS mapping of the PDCCH in Diagram 3000. Diagram 3000 illustration. Figure 29 An embodiment of the first CCE 2906. The first CCE 2906 includes data 3002 and PT-RS 3004 that follow the same PDCCH-DMRS mapping as in illustration 2800.

[0161] Figure 31 It is a diagram. Figure 28 , Figure 29 and Figure 30 A continuation diagram of the previous DFT PT-RS mapping of the PDCCH is shown in diagram 3100. DTF can be performed on CORESET 2904 to generate CORESET 3102 at frequency 3104.

[0162] In the sixth embodiment, PDCCH and / or PDSCHFDM can be used in the downlink for DFT-s-OFDM.

[0163] The sixth embodiment addresses the frequency domain multiplexing of PDCCH and PDSCH considering a single-carrier waveform design for the downlink. CORESET can span a bandwidth smaller than the carrier bandwidth, allowing PDSCH to be multiplexed with PDCCH in the same symbol. To achieve efficient PDSCH mapping in the time-frequency grid, the time-domain RE of PDSCH can be split and grouped with different lengths to perform multiple DFT operations on each symbol in the time slot. In one example, the time-domain symbol shared by CORESET and PDSCH may have a DFT size for PDSCH compared to the remaining symbols in the same time slot where no CORESET exists, and this operation is performed before frame mapping, such as... Figure 32 and Figure 33 As shown in the figure. The number and size of these portions used for PDSCH may depend on the size and location of the PDCCH resource in the time-domain symbol. The number of PDSCH portions and the DFT size of each portion can be transmitted via DCI signaling. In one embodiment of the sixth embodiment, a CORESET spanning the entire time-domain symbol can be used to avoid overlapping PDSCH and PDCCH in the same time-domain symbol.

[0164] Figure 32 This is a diagram 3200 illustrating an embodiment of PDSCH-based DFT-s-OFDM. Diagram 3200 includes a module 3202 (e.g., a modulator block that generates QAM and / or QPSK symbols) that outputs data 3204 to an SPL 3206 (e.g., a splitter). A CORESET configuration 3207 is also provided to the SPL 3206. The SPL 3206 provides a first output 3208 to a first DFT 3210 and a second output 3212 to a second DFT 3214. A map 3216 receives the outputs 3214 from the first DFT 3210 and the second DFT. The map 3216 provides an output to an IDFT 3218. The IDFT 3218 receives first information 3220 from a first symbol cycle (e.g., N1 symbols) and second information 3222 from a second symbol cycle (e.g., N2 symbols). Mapping 3216 also receives other UE PDSCH 3224, DMRS 3226, and PDCCH 3228. IDFT 3218 outputs data 3230.

[0165] Figure 33 The diagram shows the output data 3230. Figure 32 The diagram 3300 is a continuation of the PDSCH-based DFT-s-OFDM. Diagram 3300 includes N1 symbols 3306 and N2 symbols 3308. Diagram 3300 includes CORESET 3310, PDSCH_1 3312 (multiplexed PDSCH), PDSCH_1 3314, PDSCH_2 3316, DMRS 3318, DMRS 3320, and DMRS 3322. Figure 33 This shows how based on frequency and / or time grids Figure 32 The functionality described in [the document] splits the modulation symbols of PDSCH_1 into two parts, PDSCH_1 3312 and PDSCH_1 3314. The size and number of parts can be based on [the following]. Figure 32 The CORESET configuration 3207 gives the CORESET 3310 (e.g., size and / or resources).

[0166] Figure 34 This is a flowchart illustrating one embodiment of a method 3400 for transmission using an adapted downlink waveform type. In some embodiments, method 3400 is executed by a device such as network unit 104. In some embodiments, method 3400 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0167] In various embodiments, method 3400 includes dynamically or semi-statically adapting a downlink waveform type 3402 at a network element, wherein: the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof. In some embodiments, method 3400 includes transmitting 3404 a transmission using a downlink waveform pattern including the downlink waveform type.

[0168] In some embodiments, a downlink waveform pattern is used for synchronization block scanning, such that different synchronization block transmissions use different waveforms, and the downlink waveform pattern includes a variable waveform pattern for each of a plurality of synchronization burst sets. In some embodiments, method 3400 further includes indicating a downlink waveform type to the user equipment. In various embodiments, method 3400 further includes transmitting synchronization blocks to the user equipment to indicate the downlink waveform pattern to the user equipment.

[0169] In one embodiment, method 3400 further includes transmitting a master synchronization signal sequence to the user equipment to indicate a downlink waveform type, wherein the downlink waveform type includes a waveform of the physical broadcast channel. In some embodiments, method 3400 further includes transmitting a physical broadcast channel payload or a physical broadcast channel demodulation reference signal to the user equipment to indicate a downlink waveform type, wherein the downlink waveform type includes a waveform of a system information block and a common resource set. In some embodiments, method 3400 further includes transmitting a random access response message to the user equipment during the initial access procedure to indicate the downlink waveform type.

[0170] In various embodiments, method 3400 further includes transmitting downlink control information or media access control elements to the user equipment to indicate a downlink waveform type to the user equipment, wherein the downlink waveform type includes a waveform for a data channel.

[0171] Figure 35 This is a flowchart illustrating another embodiment of the method 3500 for transmission. In some embodiments, method 3500 is executed by a device such as remote unit 102. In some embodiments, method 3500 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0172] In various embodiments, method 3500 includes transmitting a measurement report 3502 to a network unit, wherein: the measurement report includes information indicating phase noise power; and the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0173] Figure 36 This is a flowchart illustrating another embodiment of the method 3600 for transmission. In some embodiments, method 3600 is executed by a device such as remote unit 102. In some embodiments, method 3600 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0174] In various embodiments, method 3600 includes transmitting uplink control signaling 3602 to a network element, wherein: the uplink control signaling is used to request a change in downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network element, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0175] In some embodiments, method 3600 further includes transmitting a scheduling request to a network element, wherein the scheduling request includes information indicating a requested waveform for a downlink waveform type. In some embodiments, method 3600 further includes transmitting an indicative media access control element to the network element, wherein the media access control element includes information indicating a requested waveform for a downlink waveform type.

[0176] Figure 37 This is a flowchart illustrating one embodiment of a method 3700 for modifying channel structure. In some embodiments, method 3700 is performed by means such as remote unit 102 and / or network unit 104. In some embodiments, method 3700 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0177] In various embodiments, method 3700 includes modifying 3702 at least one physical downlink channel structure to support discrete Fourier transform extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combinations thereof.

[0178] In some embodiments, the synchronization signal block channel structure is modified such that the demodulation reference symbols are time-division multiplexed with the physical broadcast channel before or after the physical broadcast channel symbols for channel estimation, and the physical broadcast channel symbols contain only physical broadcast channel resource elements. In some embodiments, the demodulation reference signal structure includes a demodulation reference signal in the frequency domain split into two symbols multiplexed with the physical broadcast channel and an auxiliary synchronization signal, such that each of the two symbols is in a different physical broadcast channel resource block group and a discrete Fourier transform is performed on each physical broadcast channel resource block group. In various embodiments, the physical downlink control channel structure is modified such that the demodulation reference signal symbols are time-division multiplexed with the physical downlink control channel resource elements.

[0179] In one embodiment, the phase tracking reference signal symbol structure includes phase tracking reference signal symbols inserted in the time domain before the discrete Fourier transform. In some embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within control channel elements, which are grouped into bundles, and these bundles are interleaved within the control channel elements. In some embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within control channel elements, which are grouped together and placed consecutively in the middle or near the control channel elements. In various embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within control channel elements that are grouped together and placed consecutively at or near the beginning or end of the control channel elements.

[0180] In one embodiment, a method includes: dynamically or semi-statically adapting a downlink waveform type at a network element, wherein: the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmission including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof; and transmitting using a downlink waveform pattern including the downlink waveform type.

[0181] In some embodiments, the downlink waveform pattern is used for synchronization block scanning such that different synchronization block transmissions use different waveforms, and the downlink waveform pattern includes a variable waveform pattern for each of the multiple synchronization burst sets.

[0182] In some embodiments, the method further includes instructing the user equipment on the downlink waveform type.

[0183] In various embodiments, the method further includes transmitting a synchronization signal block to the user equipment to indicate the downlink waveform pattern to the user equipment.

[0184] In one embodiment, the method further includes transmitting a sequence of primary synchronization signals to the user equipment to indicate the downlink waveform type to the user equipment, wherein the downlink waveform type includes a waveform of a physical broadcast channel.

[0185] In some embodiments, the method further includes transmitting a physical broadcast channel payload or a physical broadcast channel demodulation reference signal to the user equipment to indicate the downlink waveform type to the user equipment, wherein the downlink waveform type includes a waveform of a system information block and a common resource set.

[0186] In some embodiments, the method further includes transmitting a random access response message to the user equipment during the initial access procedure to indicate the downlink waveform type to the user equipment.

[0187] In various embodiments, the method further includes transmitting downlink control information or media access control elements to the user equipment to indicate the downlink waveform type to the user equipment, wherein the downlink waveform type includes waveforms for a data channel.

[0188] In one embodiment, an apparatus includes: a processor that dynamically or semi-statically adapts a downlink waveform type at a network unit, wherein: the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmission including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof; and a transmitter that uses a downlink waveform pattern including the downlink waveform type to transmit the transmission.

[0189] In some embodiments, the downlink waveform pattern is used for synchronization block scanning such that different synchronization block transmissions use different waveforms, and the downlink waveform pattern includes a variable waveform pattern for each of the multiple synchronization burst sets.

[0190] In some embodiments, the transmitter transmits information to the user equipment indicating the downlink waveform type.

[0191] In various embodiments, the transmitter transmits a synchronization signal block to the user equipment to indicate the downlink waveform pattern to the user equipment.

[0192] In one embodiment, the transmitter transmits a sequence of primary synchronization signals to the user equipment to indicate the downlink waveform type to the user equipment, and the downlink waveform type includes the waveform of the physical broadcast channel.

[0193] In some embodiments, the transmitter transmits a physical broadcast channel payload or a physical broadcast channel demodulation reference signal to the user equipment to indicate the downlink waveform type to the user equipment, and the downlink waveform type includes the waveform of a system information block and a common resource set.

[0194] In some embodiments, the transmitter transmits a random access response message to the user equipment during the initial access process to indicate the downlink waveform type to the user equipment.

[0195] In various embodiments, the transmitter transmits downlink control information or media access control elements to the user equipment to indicate the downlink waveform type to the user equipment, and the downlink waveform type includes waveforms for the data channel.

[0196] In one embodiment, a method includes transmitting a measurement report to a network unit, wherein: the measurement report includes information indicating phase noise power; the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0197] In one embodiment, an apparatus includes: a transmitter that transmits a measurement report to a network unit, wherein: the measurement report includes information indicating phase noise power; the phase noise power is used by the network unit to select a downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network unit, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0198] In one embodiment, a method includes: transmitting uplink control signaling to a network element, wherein: the uplink control signaling is used to request a change in downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network element, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0199] In some embodiments, the method further includes sending a scheduling request to the network element, wherein the scheduling request includes information indicating a waveform for a request of the downlink waveform type.

[0200] In some embodiments, the method further includes transmitting an indicative media access control element to the network unit, wherein the media access control element includes information indicating a waveform for a request for the downlink waveform type.

[0201] In one embodiment, an apparatus includes: a transmitter that transmits uplink control signaling to the network element, wherein: the uplink control signaling is used to request a change in downlink waveform type; the downlink waveform type includes a multi-carrier waveform, a single-carrier waveform, or a combination thereof; and the downlink waveform type is used for transmissions from the network element, including synchronization block transmission, physical downlink scheduling channel transmission, or a combination thereof.

[0202] In some embodiments, the transmitter sends a scheduling request to the network unit, and the scheduling request includes information indicating a waveform for the request used for the downlink waveform type.

[0203] In some embodiments, the transmitter transmits a media access control element to the network unit, and the media access control element includes information indicating a waveform for a request for the downlink waveform type.

[0204] In one embodiment, a method includes: modifying at least one physical downlink channel structure to support a discrete Fourier transform extended orthogonal frequency demodulation waveform, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combinations thereof.

[0205] In some embodiments, the synchronization signal block channel structure is modified such that the demodulation reference symbol is time-division multiplexed with the physical broadcast channel before or after the physical broadcast channel symbol for channel estimation, and the physical broadcast channel symbol contains only physical broadcast channel resource elements.

[0206] In some embodiments, the demodulation reference signal structure includes a demodulation reference signal in the frequency domain that is split into two symbols multiplexed with a physical broadcast channel and an auxiliary synchronization signal, such that each of the two symbols is in a different physical broadcast channel resource block group and a discrete Fourier transform is performed on each physical broadcast channel resource block group.

[0207] In various embodiments, the physical downlink control channel structure is modified to time-division multiplex demodulation reference symbols with physical downlink control channel resource elements.

[0208] In one embodiment, the phase tracking reference signal symbol structure includes a phase tracking reference signal symbol inserted in the time domain before the discrete Fourier transform.

[0209] In some embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within control channel elements grouped into bundles, and the bundles are interleaved within the control channel elements.

[0210] In some embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within a control channel element, wherein the time-domain phase tracking reference signal resource elements are grouped together and continuously placed in the middle or near the control channel element.

[0211] In various embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within a control channel element, the time-domain phase tracking reference signal resource elements being grouped together and placed consecutively at or near the beginning or end of the control channel element.

[0212] In one embodiment, an apparatus includes: a processor that modifies at least one physical downlink channel structure to support a discrete Fourier transform extended orthogonal frequency demodulation waveform, wherein the at least one physical downlink channel structure includes: a synchronization signal block channel structure; a demodulation reference signal structure; a physical downlink control channel structure; a phase tracking reference signal symbol structure; a time-domain phase tracking reference signal resource element structure; or some combinations thereof.

[0213] In some embodiments, the synchronization signal block channel structure is modified such that the demodulation reference symbol is time-division multiplexed with the physical broadcast channel before or after the physical broadcast channel symbol for channel estimation, and the physical broadcast channel symbol contains only physical broadcast channel resource elements.

[0214] In some embodiments, the demodulation reference signal structure includes a demodulation reference signal in the frequency domain that is split into two symbols multiplexed with a physical broadcast channel and an auxiliary synchronization signal, such that each of the two symbols is in a different physical broadcast channel resource block group and a discrete Fourier transform is performed on each physical broadcast channel resource block group.

[0215] In various embodiments, the physical downlink control channel structure is modified to time-division multiplex demodulation reference symbols with physical downlink control channel resource elements.

[0216] In one embodiment, the phase tracking reference signal symbol structure includes a phase tracking reference signal symbol inserted in the time domain before the discrete Fourier transform.

[0217] In some embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements within control channel elements grouped into bundles, and the bundles are interleaved within the control channel elements.

[0218] In some embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements that are grouped together and placed consecutively in the middle or near the control channel elements.

[0219] In various embodiments, the time-domain phase tracking reference signal resource element structure includes time-domain phase tracking reference signal resource elements that are grouped together and placed consecutively within the control channel elements at or near the beginning or end of the control channel elements.

[0220] 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 performed by a network element (NE), the method comprising: Based on the user equipment (UE) timing advance value and the UE's ability to support both single-carrier and multi-carrier waveforms, the downlink waveform type is dynamically or semi-statically adapted, wherein: The downlink waveform type includes multi-carrier waveforms, single-carrier waveforms, or combinations thereof; and The downlink waveform type is used for transmissions including Synchronization Signal Block (SSB) transmissions, Physical Downlink Shared Channel (PDSCH) transmissions, or combinations thereof; and for transmitting the transmissions using a downlink waveform pattern including the downlink waveform type.

2. The method according to claim 1, wherein, The downlink waveform pattern is used for SSB scanning, so that different SSB transmissions use different waveforms, and the downlink waveform pattern includes a variable waveform pattern for each SSB burst set of multiple SSB burst sets.

3. The method according to claim 1, further comprising: Indicate the downlink waveform type to the UE.

4. The method according to claim 1, further comprising: The SSB is transmitted to the UE to indicate the downlink waveform pattern to the UE.

5. The method of claim 1, further comprising: A sequence of primary synchronization signals (PSS) is transmitted to the UE to indicate the downlink waveform type to the UE, wherein the downlink waveform type includes the waveform of the physical broadcast channel (PBCH).

6. The method of claim 1, further comprising: Transmit a Physical Broadcast Channel (PBCH) payload or a PBCH Demodulation Reference Signal (DMRS) to the UE to indicate the downlink waveform type to the UE, wherein the downlink waveform type includes the waveform of the System Information Block (SIB) and the Common Resource Set.

7. The method of claim 1, further comprising: During the initial access process, a random access response message is transmitted to the UE to indicate the downlink waveform type to the UE.

8. The method of claim 1, further comprising: The downlink control information (DCI) or media access control element (MAC-CE) is transmitted to the UE to indicate the downlink waveform type to the UE, wherein the downlink waveform type includes a waveform for the data channel.

9. The method of claim 1, further comprising: Modify at least one physical downlink channel structure to support Discrete Fourier Transform (DFT) extended orthogonal frequency demodulation waveforms, wherein the at least one physical downlink channel structure includes: SSB channel structure; Demodulation Reference Signal (DMRS) structure; Physical downlink control channel (PDCCH) structure; Phase Tracking Reference Signal (PTRS) symbol structure; Time-domain phase tracking reference signal (PTRS) resource element structure; or Its combination.

10. The method according to claim 9, wherein, The SSB channel structure is modified such that DMRS symbols are time-division multiplexed (TDM) with PBCH before or after Physical Broadcast Channel (PBCH) symbols for channel estimation, and the PBCH symbols contain only PBCH resource elements.

11. The method according to claim 9, wherein, The DMRS structure includes a frequency domain DMRS that is split into two symbols multiplexed with the Physical Broadcast Channel (PBCH) and the Supplemental Synchronization Signal (SSS), such that each of the two symbols is in a different PBCH Resource Block Group (RBG), and a Discrete Fourier Transform (DFT) is performed on each PBCH RBG.

12. The method according to claim 9, wherein, The PDCCH structure was modified to enable time-division multiplexing (TDM) of DMRS symbols and PBCH resource elements.

13. The method according to claim 9, wherein, The PTRS symbol structure includes PTRS symbols in the time domain inserted before the Discrete Fourier Transform (DFT).

14. The method according to claim 9, wherein, The time-domain PTRS resource element structure includes time-domain PTRS resource elements within control channel elements grouped into bundles, and the bundles are interleaved within the control channel elements.

15. The method according to claim 9, wherein, The time-domain PTRS resource element structure includes time-domain PTRS resource elements within the control channel element, which are grouped together and placed consecutively in the middle or near the control channel element.

16. The method according to claim 9, wherein, The time-domain PTRS resource element structure includes time-domain PTRS resource elements within the control channel element. These time-domain PTRS resource elements are grouped together and placed consecutively at or near the beginning or end of the control channel element.

17. A network element (NE), comprising: At least one memory; and At least one processor, said at least one processor being coupled to said at least one memory and configured to cause the NE: Based on the user equipment (UE) timing advance value and the UE's ability to support both single-carrier and multi-carrier waveforms, the downlink waveform type is dynamically or semi-statically adapted, wherein: The downlink waveform types include multi-carrier waveforms, single-carrier waveforms, or combinations thereof; and The downlink waveform type is used for transmissions including Synchronization Signal Block (SSB) transmissions, Physical Downlink Shared Channel (PDSCH) transmissions, or combinations thereof; and for transmitting the transmissions using a downlink waveform pattern including the downlink waveform type.

18. A method performed by a user equipment (UE), comprising: Receive transmissions based on downlink waveform patterns, including downlink waveform types. The downlink waveform type is dynamically or semi-statically adapted based on the UE's timing advance value and the UE's ability to support both single-carrier and multi-carrier waveforms. The downlink waveform type includes multi-carrier waveforms, single-carrier waveforms, or combinations thereof; and The transmission includes synchronization signal block (SSB) transmission, physical downlink shared channel (PDSCH) transmission, or a combination thereof.

19. A user equipment (UE), comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to cause the UE to: Receive transmissions based on downlink waveform patterns, including downlink waveform types. The downlink waveform type is dynamically or semi-statically adapted based on the UE's timing advance value and the UE's ability to support both single-carrier and multi-carrier waveforms. The downlink waveform type includes multi-carrier waveforms, single-carrier waveforms, or combinations thereof; and The transmission includes synchronization signal block (SSB) transmission, physical downlink shared channel (PDSCH) transmission, or a combination thereof.

Images