CN116686262A

CN116686262A - Multiple discrete fourier transforms for transmission and reception

Info

Publication number: CN116686262A
Application number: CN202180084185.7A
Authority: CN
Inventors: 安基特·巴姆里; 阿里·拉马丹·阿里; 谢尔·阿里·奇马; 维贾伊·南贾
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2020-12-30
Filing date: 2021-12-30
Publication date: 2023-09-01
Also published as: WO2022144840A1

Abstract

Apparatus, methods, and systems for multiple discrete fourier transforms for transmission and reception are disclosed. An apparatus (800) includes a transceiver (825) to receive a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver, to receive a second configuration for a physical channel from the network, the second configuration including DFT configuration information, and to receive a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration. An apparatus (800) includes a processor (805) that performs multiple DFT-based transmission on time domain symbols transmitted to a network based on a first configuration and a second configuration, and performs multiple IDFT-based reception of time domain symbols received from the network based on an IDFT configuration.

Description

Multiple discrete fourier transforms for transmission and reception

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No.63/132,458 entitled "MULTI DFT-S-OFDM WAVEFORM FOR DOWNLINK (multiple DFT-S-OFDM waveform for downlink)" filed by Ankit Bhamri et al at 12/30 of 2020, which is incorporated herein by reference in its entirety.

Technical Field

The subject matter disclosed herein relates generally to wireless communications, and more particularly to multiple discrete fourier transforms for transmission and reception.

Background

In new radios ("NR") Rel-15, multicarrier-based waveforms (e.g., cyclic prefix orthogonal frequency division multiplexing ("CP-OFDM")) have been employed for the downlink ("DL") as well as the uplink ("UL"), and additionally single carrier-based waveforms (e.g., discrete fourier transform spread OFDM ("DFT-s-OFDM") or CP single carrier frequency division multiplexing ("CP-SC-FDM")) have also been employed for the UL. However, CP-OFDM performance deteriorates at high frequencies (e.g., over 52.6 GHz) due to its sensitivity to phase noise and its peak-to-average power ratio ("PAPR") or cubic metric ("CM") that limits cell coverage, edges of cell performance, and higher UE power consumption.

Disclosure of Invention

A procedure for multiple discrete fourier transforms of transmission and reception is disclosed. The program may be embodied by an apparatus, system, method and/or computer program product.

In one embodiment, a first apparatus includes a transceiver to receive a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver. In one embodiment, a transceiver receives a second configuration for physical channels from a network, the second configuration including a number of DFTs applied at a transmitter to transform one or more time domain signals and/or channels to a frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for time symbols. In one embodiment, the transceiver receives a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration, including a number of IDFTs to apply over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, a first apparatus includes a processor to perform multiple DFT-based transmission on time domain symbols transmitted to a network based on a first configuration and a second configuration, and perform multiple IDFT-based reception of time domain symbols received from the network based on an IDFT configuration.

In one embodiment, a first method includes receiving a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver. In one embodiment, a first method includes receiving, from a network, a second configuration for a physical channel, the second configuration including a number of DFTs to be applied at a transmitter to transform one or more time domain signals and/or channels to a frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for a time symbol. In one embodiment, a first method includes receiving a third configuration from a network for determining an inverse DFT ("IDFT") configuration based on the second configuration, including a number of IDFTs to apply over time symbols to receive one or more signals, a size of each of the IDFTs, and a demapping pattern from subcarriers to the IDFTs. In one embodiment, a first method includes performing a multiple DFT-based transmission on time domain symbols transmitted to a network based on a first configuration and a second configuration; and performing multi-IDFT based reception of the time domain symbols received from the network based on the IDFT configuration.

In one embodiment, the second apparatus includes a processor that determines a first configuration for applying a multiple discrete fourier transform ("DFT") based waveform at the transmitter and/or receiver. In one embodiment, the processor determines a second configuration for the physical channel, the second configuration including a number of DFTs to be applied at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for the time symbols. In one embodiment, the processor determines a third configuration for determining an inverse DFT ("IDFT") configuration that includes a number of IDFTs to apply over time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, the second apparatus includes a transceiver to transmit the determined first configuration, second configuration, and third configuration to a user equipment ("UE") device, and to transmit time domain symbols to the UE, wherein the UE performs multiple IDFT-based reception of the time domain symbols based on the IDFT configuration.

In one embodiment, a second method includes determining a first configuration for applying a multiple discrete fourier transform ("DFT") based waveform at a transmitter and/or receiver. In one embodiment, the second method includes determining a second configuration for the physical channel, the second configuration including a number of DFTs to apply at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for the time symbols. In one embodiment, the second method includes determining a third configuration for determining an inverse DFT ("IDFT") configuration including a number of IDFTs to apply over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, a second method includes transmitting the determined first configuration, second configuration, and third configuration to a user equipment ("UE") device; and transmitting the time domain symbols to the UE, wherein the UE performs multi-IDFT based reception of the time domain symbols based on the IDFT configuration.

Drawings

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for multiple discrete Fourier transforms for transmission and reception;

FIG. 2 depicts an example of multiple DFT-s-OFDM for multiplexing control/data over symbols;

FIG. 3 depicts CDF plots of PAPR comparisons between CP-OFDM, DFT-s-OFDM, and multiple DFT-s-OFDM;

FIG. 4 depicts a new field in a ControlResourceSet information element of multiple DFT-s-OFDM;

FIG. 5A depicts a mapping of DFT output onto a symbol for multiple CORESET subcarriers in a sequential manner; and

FIG. 5B depicts a mapping of DFT output onto a symbol for multiple CORESET subcarriers in a sequential manner;

fig. 6 depicts new fields in a control resource set information element for multiple DFT-s-OFDM for DM-RS and control data;

FIG. 7A depicts a mapping of DFT outputs to subcarriers of a single CORESET for multiplexing DM-RS and control data;

FIG. 7B depicts a mapping of DFT outputs to subcarriers of a single CORESET for multiplexing DM-RS and control data generated in the frequency domain;

FIG. 8 is a block diagram illustrating one embodiment of a user equipment device of multiple discrete Fourier transforms that may be used for transmission and reception;

FIG. 9 is a block diagram illustrating one embodiment of a network equipment apparatus that may be used for transmission and reception of multiple discrete Fourier transforms;

FIG. 10 is a block diagram illustrating one embodiment of a method for multiple discrete Fourier transforms for transmission and reception; and

FIG. 11 is a block diagram illustrating one embodiment of another method for multiple discrete Fourier transforms for transmission and reception.

Detailed Description

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method or program product. Thus, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

For example, the disclosed embodiments may be implemented as hardware circuits comprising custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and/or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and/or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs signals for the access code.

Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for performing operations of embodiments may be any number of rows and may be written in any combination of one or more programming languages, including an object oriented programming language such as Python, ruby, java, smalltalk, C ++ or the like and conventional procedural programming languages, such as the "C" programming language and/or machine languages, such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider ("ISP").

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that the embodiments may be practiced without one or more of the specific details, or with 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.

Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. The listing of enumerated items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a," "an," and "the" also mean "one or more" unless expressly specified otherwise.

As used herein, a list with "and/or" conjunctions includes any single item in the list or a combination of items in the list. For example, the list of A, B and/or C includes a only a, a only B, a only C, A, and B combinations, B and C combinations, a and C combinations, or A, B and C combinations. As used herein, a list using the term "one or more of … …" includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C include a combination of a only, B only, C, A only, and B only, B and C, a and C, or A, B and C. As used herein, a list using the term "one of … …" includes one and only one of any single item in the list. For example, "one of A, B and C" includes only a, only B, or only C and does not include a combination of A, B and C. As used herein, "a member selected from the group consisting of A, B and C" includes one and only one of A, B or C, and does not include the combination of A, B and C. As used herein, "a member selected from the group consisting of A, B and C and combinations thereof" includes a alone, B alone, a combination of C, A and B alone, a combination of B and C, a combination of a and C, or a combination of A, B and C.

Aspects of the embodiments are described below with reference to schematic flow chart diagrams and/or schematic block diagram illustrations of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow diagrams and/or schematic block diagrams, can be implemented by codes. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The code may further be stored in a memory device that is capable of directing a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the memory device produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowcharts and/or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods and program products according to various embodiments. In this regard, each block in the flowchart and/or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, in the illustrated figure.

Although various arrow types and line types may be employed in the flow chart diagrams and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of the elements in each figure may refer to the elements of the preceding figures. Like reference numerals refer to like elements throughout, including alternative embodiments of like elements.

In general, this disclosure describes systems, methods, and apparatuses for multiple discrete fourier transforms for transmission and reception. In some embodiments, the method may be performed using computer code embedded on a computer readable medium. In some embodiments, an apparatus or system may include a computer-readable medium comprising computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

In new radios ("NR") Rel-15, multicarrier-based waveforms (e.g., cyclic prefix orthogonal frequency division multiplexing ("CP-OFDM")) have been employed for the downlink ("DL") as well as the uplink ("UL"), and additionally single carrier-based waveforms (e.g., discrete fourier transform spread OFDM ("DFT-s-OFDM") or CP single carrier frequency division multiplexing ("CP-SC-FDM")) have also been employed for the UL. However, CP-OFDM performance degrades at high frequencies (e.g., over 52.6 GHz) due to its sensitivity to phase noise and its peak-to-average power ratio ("PAPR") or cubic metric ("CM") that limits cell coverage, cell performance margin, and higher UE power consumption.

The problem of CP-OFDM at high frequencies becomes severe as the modulation order and/or channel bandwidth increases. The above-mentioned problem makes single carrier waveforms such as DFT-s-OFDM suitable candidates at high frequencies due to their natural robustness to phase noise and their low PAPR or CM. Currently, standardization work is underway in Rel-17 to support NR operation from 52.6GHz to 71 GHz. In the initial discussion, before NR Rel-17 starts, it is proposed to use a single carrier waveform such as a DFT-s-OFDM waveform for DL due to its low PAPR compared to CP-OFDM. But decides to use CP-OFDM only for DL of 52.6GHz to 71GHz and mainly considers higher subcarrier spacing.

However, in future versions of 3GPP NR, discussion related to single carrier waveforms is likely to begin again, especially for potential standardization work beyond 71 GHz. Since NR already supports DFT-s-OFDM for the UL, it is likely to be considered one of the candidate single carrier waveforms for DL as well as for NR B71 GHz. DFT-s-OFDM occurs with limitations in terms of multiplexing over a given time symbol in the frequency domain, and thus, if DFT-s-OFDM were to be applied to the DL, one of the main challenges would be how to apply it with the physical downlink control channel ("PDCCH").

In the present disclosure, signaling aspects for facilitating PDCCH transmission/reception with multiple DFTs for DFT-s-OFDM are discussed by considering the following key issues:

a multiple control resource set ("CORESET") for multiplexing in time and/or frequency of PDCCH with DFT-s-OFDM;

demodulation reference signals ("DM-RS") multiplexed with CORESET in time and/or frequency with DFT-s-OFDM; and

PDCCH and other channels, such as a physical downlink shared channel ("PDSCH") or a synchronization signal block ("SSB"), are multiplexed on symbols with DFT-s-OFDM.

Fig. 1 depicts a wireless communication system 100 for multiple discrete fourier transforms for transmission and reception in accordance with an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a fifth generation radio access network ("5G-RAN") 115, and a mobile core network 140. The 5G-RAN 115 and the mobile core network 140 form a mobile communication network. The 5G-RAN 115 may consist of a third generation partnership project ("3 GPP") access network 120 including at least one cellular base station unit 121 and/or a non-3 GPP access network 130 including at least one access point 131. Remote unit 105 communicates with 3GPP access network 120 using 3GPP communication link 123 and/or with non-3 GPP access network 130 using non-3 GPP communication link 133. Although a particular number of remote units 105, 3GPP access networks 120, cellular base units 121, 3GPP communication links 123, non-3 GPP access networks 130, access points 131, non-3 GPP communication links 133, and mobile core networks 140 are depicted in FIG. 1, one skilled in the art will recognize that any number of remote units 105, 3GPP access networks 120, cellular base units 121, 3GPP communication links 123, non-3 GPP access networks 130, access points 131, non-3 GPP communication links 133, and mobile core networks 140 may be included in wireless communication system 100.

In one embodiment, the RAN 120 conforms to a 5G system specified in the 3GPP specifications. For example, the RAN 120 may be a next generation RAN ("NG-RAN") that implements NR radio access technology ("RAT") and/or long term evolution ("LTE") RATs. In another example, the RAN 120 may include a non-3 GPP RAT (e.g.Or institute of electrical and electronics engineers ("IEEE") 802.11 family compatible WLANs). In another embodiment, the RAN 120 conforms to an LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, such as a worldwide interoperability for microwave access ("WiMAX") or other network of the IEEE 802.16 family of standards. The present disclosure is not intended to be limited to any particular implementation of a wireless communication system architecture or protocol.

In one embodiment, remote unit 105 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart television (e.g., a television connected to the internet), a smart appliance (e.g., an appliance connected to the internet), a set-top box, a gaming machine, a security system (including a security camera), an on-board computer, a network device (e.g., router, switch, modem), and so forth. In some embodiments, remote unit 105 includes a wearable device, such as a smart watch, a fitness band, an optical head mounted display, or the like. Further, remote unit 105 may be referred to as a user equipment ("UE"), subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit/receive unit ("WTRU"), device, or other terminology used in the art. In various embodiments, remote unit 105 includes a subscriber identity and/or identification module ("SIM") and a mobile equipment ("ME") that provides mobile terminal functionality (e.g., radio transmission, handoff, speech coding and decoding, error detection and correction, signaling, and access to the SIM). In some embodiments, remote unit 105 may include a terminal equipment ("TE") and/or be embedded in an appliance or device (e.g., the computing device described above).

Remote unit 105 may communicate directly with one or more cellular base station units 121 in 3GPP access network 120 via UL and DL communication signals. Further, UL and DL communication signals may be carried over 3GPP communication link 123. Similarly, remote unit 105 may communicate with one or more access points 131 in non-3 GPP access network 130 via UL and DL communication signals carried over non-3 GPP communication link 133. Here, access networks 120 and 130 are intermediate networks that provide remote unit 105 with access to mobile core network 140.

In some embodiments, remote unit 105 communicates with a remote host (e.g., in data network 150 or in data network 160) via a network connection with mobile core network 140. For example, an application 107 (e.g., a Web browser, media client, telephone, and/or voice over internet protocol ("VoIP") application) in the remote unit 105 may trigger the remote unit 105 to establish a protocol data unit ("PDU") session (or other data connection) with the mobile core network 140 via the 5G-RAN 115 (e.g., via the 3GPP access network 120 and/or the non-3 GPP network 130). The mobile core network 140 then relays traffic between the remote unit 105 and the remote host using the PDU session. The PDU session represents a logical connection between remote unit 105 and user plane function ("UPF") 141.

In order to establish a PDU session (or packet data network ("PDN") connection), remote unit 105 must register with mobile core network 140 (also referred to as "attach to mobile core network" in the context of a fourth generation ("4G") system). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. In this way, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Additionally or alternatively, remote unit 105 may have at least one PDU session for communicating with packet data network 160. Remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.

In the context of a 5G system ("5 GS"), the term "PDU session" refers to a data connection that provides an end-to-end ("E2E") user plane ("UP") connection between a remote unit 105 and a particular data network ("DN") through UPF 131. A PDU session supports one or more quality of service ("QoS") flows. In some embodiments, there may be a one-to-one mapping between QoS flows and QoS profiles such that all packets belonging to a particular QoS flow have the same 5G QoS identifier ("5 QI").

In the context of a 4G/LTE system, such as an evolved packet system ("EPS"), a PDN connection (also referred to as an EPS session) provides E2E UP connectivity between a remote unit and the PDN. The PDN connection procedure establishes an EPS bearer, e.g., a tunnel between the remote unit 105 and a packet gateway ("PGW"), not shown, in the mobile core network 130. In some embodiments, there is a one-to-one mapping between EPS bearers and QoS profiles such that all packets belonging to a particular EPS bearer have the same QoS class identifier ("QCI").

As described in more detail below, the remote unit 105 may establish a second data connection (e.g., a portion of a second PDU session) with the second mobile core network 140 using the established first data connection (e.g., PDU session) with the first mobile core network 130. When a data connection (e.g., a PDU session) is established with the second mobile core network 140, the remote unit 105 registers with the second mobile core network 140 using the first data connection.

Cellular base station units 121 may be distributed over a geographic area. In certain embodiments, cellular base station unit 121 may also be referred to as an access terminal, access point, base station, node B ("NB"), evolved node B (abbreviated eNodeB or "eNB," also known as evolved universal terrestrial radio access network ("E-UTRAN") node B), 5G/NR node B ("gNB"), home node B, relay node, device, or any other terminology used in the art. The cellular base station units 121 are typically part of a radio access network ("RAN") such as the 3GPP access network 120, which may include one or more controllers communicatively coupled to one or more corresponding cellular base station units 121. These and other elements of the radio access network are not illustrated but are generally well known to those of ordinary skill in the art. The cellular base station unit 121 is connected to the mobile core network 140 via the 3GPP access network 120.

Cellular base unit 121 may serve a plurality of remote units 105 within a service area, such as a cell or cell sector, via 3GPP wireless communication link 123. Cellular base unit 121 may communicate directly with one or more remote units 105 via communication signals. Typically, cellular base unit 121 transmits DL communication signals to serve remote units 105 in the time, frequency, and/or spatial domain. Further, DL communication signals may be carried over 3GPP wireless communication link 123. The 3GPP wireless communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. The 3GPP wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the cellular base units 121. Note that during operation of the NR on the unlicensed spectrum (referred to as "NR-U"), base unit 121 and remote unit 105 communicate over the unlicensed (e.g., shared) radio spectrum.

The non-3 GPP access network 130 may be distributed over a geographic area. Each non-3 GPP access network 130 may serve a plurality of remote units 105 with a service area. Access point 131 in non-3 GPP access network 130 may communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve remote units 105 in the time, frequency, and/or spatial domains. Both UL and DL communication signals are carried over the non-3 GPP communication link 133. The 3GPP communication link 123 and the non-3 GPP communication link 133 can employ different frequencies and/or different communication protocols. In various embodiments, the access point 131 may communicate using unlicensed radio spectrum. Mobile core network 140 may provide services to remote units 105 via non-3 GPP access network 130, as described in more detail herein.

In some embodiments, the non-3 GPP access network 130 is connected to the mobile core network 140 via an interworking entity 135. Interworking entity 135 provides interworking between non-3 GPP access network 130 and mobile core network 140. Interworking entity 135 supports connections via "N2" and "N3" interfaces. As depicted, both 3GPP access network 120 and interworking entity 135 communicate with access and mobility management function ("AMF") 143 using an "N2" interface. The 3GPP access network 120 and interworking entity 135 also communicate with the UPF 141 using an "N3" interface. Although depicted as being external to the mobile core network 140, in other embodiments, the interworking entity 135 may be part of the core network. Although depicted as being outside of non-3 GPP RAN 130, in other embodiments interworking entity 135 may be part of non-3 GPP RAN 130.

In some embodiments, the non-3 GPP access network 130 can be controlled by an operator of the mobile core network 140 and can directly access the mobile core network 140. Such non-3 GPP AN deployments are referred to as "trusted non-3 GPP access networks". When the non-3 GPP access network 130 is operated by a 3GPP operator or trusted partner, it is considered "trusted" and supports certain security features, such as strong air interface encryption. Conversely, non-3 GPP AN deployments that are not under the control of the operator (or trusted partner) of the mobile core network 140, do not directly access the mobile core network 140, or do not support certain security features are referred to as "untrusted" non-3 GPP access networks. Interworking entity 135 deployed in trusted non-3 GPP access network 130 can be referred to herein as a trusted network gateway function ("TNGF"). Interworking entity 135 deployed in untrusted non-3 GPP access network 130 may be referred to herein as a non-3 GPP interworking function ("N3 IWF"). Although depicted as part of non-3 GPP access network 130, in some embodiments the N3IWF may be part of mobile core network 140 or may be located in data network 150.

In one embodiment, the mobile core network 140 is a 5G core ("5 GC") or evolved packet core ("EPC") that may be coupled to a data network 150, such as the internet and private data networks, among other data networks. Remote unit 105 may have a subscription or other account with mobile core network 140. Each mobile core network 140 belongs to a single public land mobile network ("PLMN"). The present disclosure is not intended to be limited to any particular implementation of a wireless communication system architecture or protocol.

The mobile core network 140 includes several network functions ("NFs"). As depicted, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes a plurality of control plane functions including, but not limited to, an AMF 143 serving the 5G-RAN 115, a session management function ("SMF") 145, a policy control function ("PCF") 147, an authentication server function ("AUSF") 148, a unified data management ("UDM") and a unified data repository function ("UDR").

In the 5G architecture, UPF(s) 141 are responsible for packet routing and forwarding, packet inspection, qoS handling, and external PDU sessions for an interconnect data network ("DN"). The AMF 143 is responsible for terminating non-access stratum ("NAS") signaling, NAS ciphering and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. The SMF 145 is responsible for session management (e.g., session establishment, modification, release), remote unit (e.g., UE) IP address assignment and management, DL data notification, and traffic steering configuration of the UPF to enable proper traffic routing.

PCF 147 is responsible for unifying policy frameworks to provide policy rules for control plane ("CP") functions to access subscription information for policy decisions in UDR. The AUSF 148 acts as an authentication server.

The UDM is responsible for generating authentication and key agreement ("AKA") credentials, user identification handling, access authorization, subscription management. UDR is a repository of subscriber information and can be used to serve multiple network functions. For example, the UDR may store subscription data, policy related data, subscriber related data that allows for opening to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as a combined entity "UDM/UDR"149.

In various embodiments, the mobile core network 140 may also include a network open function ("NEF") (responsible for making network data and resources readily accessible to clients and network partners, e.g., via one or more APIs), a network repository function ("NRF") (providing NF service registration and discovery, enabling NFs to identify appropriate services to each other and communicate with each other through an application programming interface ("API"), or other NFs defined for 5 GC. In some embodiments, mobile core network 140 may include an authentication, authorization, and accounting ("AAA") server.

In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, with each mobile data connection utilizing a particular network slice. Here, "network slice" refers to a portion of the mobile core network 140 that is optimized for a particular traffic type or communication service. The network instance may be identified by a single network slice selection assistance information ("S-nsai") while the set of network slices for which the remote unit 105 is authorized to use is identified by the nsai. In some embodiments, the various network tiles may include separate instances of network functions, such as SMF and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For ease of illustration, different network slices are not shown in fig. 1, but they are assumed to support different network slices.

Although a particular number and type of network functions are depicted in fig. 1, those skilled in the art will recognize that any number and type of network functions may be included in the mobile core network 140. Furthermore, where mobile core network 140 includes EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a mobility management entity ("MME"), a serving gateway ("S-GW"), an MME, an S-GW, a P-GW, a home subscriber server ("HSS"), and so forth.

Although fig. 1 depicts components of a 5G RAN and 5G core network, the described embodiments for access authentication using pseudonyms (pseudonyms) over non-3 GPP accesses are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, bluetooth, zigBee, sigfox, and the like. For example, in a 4G/LTE variant involving EPC, AMF 143 may be mapped to MME, SMF to control plane portion of P-GW and/or MME, UPF 141 may be mapped to S-GW and user plane portion of P-GW, UDM/UDR 149 may be mapped to HSS, etc.

As depicted, remote unit 105 (e.g., UE) may connect to a mobile core network (e.g., to a 5G mobile communication network) via two types of access: (1) Via a 3GPP access network 120, and (2) via a non-3 GPP access network 130. A first type of access (e.g., 3GPP access network 120) uses a 3GPP defined type of wireless communication (e.g., NG-RAN), and a second type of access (e.g., non-3 GPP access network 130) uses a non-3 GPP defined type of wireless communication (e.g., WLAN). The 5G-RAN 115 refers to any type of 5G access network capable of providing access to a mobile core network 140, including a 3GPP access network 120 and a non-3 GPP access network 130.

By way of background, regarding PDCCH in NR, according to part 7.3.2 in 3gpp TS 38.211, PDCCH consists of the following main components for transmission with CP-OFDM.

1. Control channel element ("CCE")

The physical downlink control channel consists of one or more CCEs, as shown in table 1.

Aggregation level	Number of CCEs
		1	1
2	2
		4	4
8	8
		16	16

Table 1: supported PDCCH aggregation level

2.CORESET

Control resource set is defined by the frequency domainIndividual resource blocks and +.>A symbol composition.

The control channel element consists of 6 resource element groups ("REGs"), where the resource element groups are equal to one resource block during one OFDM symbol. The resource element groups within the control resource set are numbered in ascending order in a time-prioritized manner, starting with 0 for the first OFDM symbol and the lowest numbered resource block in the control resource set.

The UE can be configured with multiple sets of control resources. Each control resource set is associated with only one CCE-to-REG mapping.

The CCE-to-REG mapping for the control resource set can be interleaved or non-interleaved and described by REG bundling:

REG bundle i is defined as REG { iL, il+1,., il+l-1}, where L is the REG bundle size,and->Is the number of REGs in CORESET;

CCE j consists of REG bundles { f (6 j/L), f (6 j/l+1),. F (6 j/l+6/L-1) }, where f (·) is the interleaver.

For non-interleaved CCE-to-REG mapping, l=6 and f (x) =x.

For mapping of interleaved CCEs to REGs, forAnd for the followingThe interleaver is defined by:

x＝cR+r

r＝0，1，...，R-1

c＝0，1，...，C-1

wherein R.epsilon. {2,3,6}.

The UE processing is not expected to result in a configuration where the number C is not integer.

For CORESET configured by ControlResourceSet IE:

given by higher layer parameters frequence domainresourcesDischarging;

given by the higher layer parameter duration, wherein +.>

The interleaving or non-interleaving mapping is given by the higher layer parameter cce-REG-MappingType;

for non-interleaving mappings, L is equal to 6 and is given by the higher layer parameter reg-BundleSize for the mapping of interleaving;

r is given by the higher layer parameter interaversize;

if provided, n _shift E {0,1,.,. 274} is given by the higher layer parameter shiftIndex; otherwise

For both interleaving and non-interleaving mappings, the UE may assume that

If the higher layer parameter pre-coding granularity is equal to the sameaassreg-bundle, then the same pre-coding is used within REG bundles;

if the higher parameter pre-coding granularity is equal to the allconfou rb, the same pre-coding is used across all resource element groups within the set of consecutive resource blocks in CORESET, and no resource elements in CORESET overlap with SSB or LTE cell-specific reference signals, as indicated by the higher layer parameter it-CRS-to-match around or additionalLTE-CRS-to-match around list.

For CORESET 0 configured by ControlResourceSetZero IE:

and->From [5, TS 38.213]Clause 13 of (a);

the UE may assume an interlace mapping

L＝6；

R＝2；

When CORESET 0 is configured by MIB or SIB1, the UE may assume a normal cyclic prefix;

the UE may assume that the same precoding is used within the REG bundle.

3. Scrambling

The UE should assume that the bit block b (0) before modulation _bit -1) scrambling, wherein M _bit Is the number of bits transmitted on the physical channel, resulting in a block of scrambled bits according to

Wherein the scrambling sequence c (i) is given in clause 5.2.1. The scrambling sequence generator should be initialized to:

c _init ＝(n _RNTI ·2 ¹⁶ +n _ID )mod 2 ³¹

wherein the method comprises the steps of

For example in [5, TS 38.213]UE-specific search space defined in clause 10, if configured, n _ID E {0,1,.,. 65535} is equal to the higher layer parameter pdcch-DMRS-ScramblingID,

otherwise

And wherein

If the higher layer parameter PDCCH-DMRS-scramblingID is configured, n is given by the C-RNTI for PDCCH in the UE-specific search space _RNTI And (2) and

n _RNTI =0, otherwise.

PDCCH modulation

The UE shall assume a block of bitsIs QPSK modulated as described in clause 5.1.3 resulting in a complex-valued modulation symbol block d (0),. The term d (M) _symb -1)。/>

5. Mapping to physical resources

The UE should assume a block d (0) of complex-valued symbols _symb -1) to be by a factor of beta _PDCCH Scaling and mapping to resource elements (k, l) for monitored PDCCH and not for associated PDCCH DMRS in ascending order of k first, then l _p，μ . Antenna port p=2000.

In the present disclosure, configuration and/or signaling of multiple DFTs is proposed in DL and/or UL to allow multiplexing of one or more channels, CORESET, RS, etc. in different frequency resources within the same time symbol. In one embodiment, to apply multiple DFT-s-OFDM as waveforms for downlink channels, where multiple DFTs can be applied at the transmitter prior to inverse fast fourier transform ("IFFT") or inverse discrete fourier transform ("IDFT") to allow multiplexing of different downlink channels on the same time symbol, and/or multiplexing of different CORESET for the UE on the same time symbol, and/or multiplexing of control data with DM-RS for CORESET on the same time symbol, a corresponding mapping configured with multiple DFT configuration and DFT output to subcarriers is proposed.

Fig. 2 depicts one example of multiplexing two CORESETs with two DFTs, wherein corresponding CORESET configuration enhancements are implemented, as set forth in the embodiments below. In particular, fig. 2 illustrates one embodiment of applying multiple DFTs at the transmitter side. As shown in fig. 2, one M1-point DFT 206 for CORESET 1 202 spreading and one M2-point DFT 208 for CORESET 2 204 spreading are applied (after application of constellation mapping 205 from serial-to-parallel converters 201, 203), followed by a centralized or distributed mapping 210 to N subcarriers, and then by an N-point IFFT 212 or IDFT, such that m1+m2< = N. In one embodiment, a CP is added 214 and an application 216 is parallel to serial converter.

In one embodiment, applying multiple DFT-s-OFDM provides better performance in terms of PAPR than CP-OFDM while at the same time providing more flexibility in multiplexing multiple CORESETs of the same or different sizes over time symbols, and provides flexibility in power/energy per resource element ("EPRE") ratio between different channels and/or signals than the single DFT-s-OFDM currently applied in NR UL transmissions.

In one embodiment, multiple DFT-s-OFDM can provide multiplexing capability for both control of CORESET and DM-RS over symbols, but with better PAPR than CP-OFDM. Furthermore, in one embodiment, such waveforms allow PDCCH CORESET 0 to be multiplexed with SSB using two DFTs prior to IFFT or IDFT. PAPR comparisons between multiple DFT-s-OFDM, CP-OFDM, and DFT-s-OFDM are shown in FIG. 3 (n represents the number of DFT operations). Fig. 3 depicts the benefits of using multiple DFTs. Basically, with respect to PAPR, CP-OFDM is the worst and a single DFT-s-OFDM is the best. The use of multiple DFTs provides better than CP-OFDM but worse than single DFT-s-OFDM but with better multiplexing capability. Thus, in one embodiment, using multiple DFTs for DFT-s-OFDM can provide a good tradeoff. In fig. 3, the results for the 2048 IFFT or IDFT size are shown. As is apparent from fig. 3, the PAPR of the multiple DFT-s-OFDM reaches CP-OFDM as the number of DFT operations increases, which provides a PAPR tradeoff between CP-OFDM and DFT-s-OFDM, but on the other hand provides more frequency domain multiplexing flexibility.

In a first embodiment, for multiple DFT-s-OFDM for multiple CORESET multiplexing over symbols, K DFTs are applied at the transmitter for multiplexing K CORESETs over a bandwidth portion ("BWP") of the UE, where each of the K DFTs has a length equal to the CORESET length in frequency (e.g., the number of resource elements). In one embodiment, the UE is configured by the network (e.g., the gNB) with a controlresource information element, as shown in fig. 4, in which a DFT field is introduced that can indicate the number of DFTs 402, the size of each of the DFTs 404, and the location/offset applicable to the corresponding CORESET. In some embodiments, only multiple DFTs of the same size are configured for CORESET. In some embodiments, only one DFT is associated with one CORESET and only the corresponding length is configured. In some embodiments, only one DFT is associated with one CORESET and the DFT size is equal to the number of resource elements in the CORESET's symbol.

In some embodiments, the maximum size of the bit field frequencydomain resource 406 in the ControlResourceSet information element is equal to the maximum number of DFTs allowed on symbols within BWP, where each bit field corresponds to a group of a consecutive number of resource elements (e.g., 6 resource blocks ("RBs") in BWP) equal to the DFT length. The number of bits set to "1" corresponds to the number of DFTs associated with a single CORESET. In some embodiments, only one DFT can be associated with CORESET, and for the frequencydomain resource field 406, only one of the bit values may be set to "1".

Based on which field is set to "1", the output of the DFT is mapped to the corresponding resource element (subcarrier) in the frequency domain. In some embodiments, the explicit field for DFT is not included in the controlresource information element and the number of DFTs for CORESET can be inferred from the number of bits in the frequencydomain resource field 406 set to "1". In this case, the size of the DFT is equal to the number of resource elements (subcarriers) indicated by a single bit of the frequencydomain resource field 406. For example, if the number of subcarriers indicated by a single bit of the frequencydomalnresource field 406 is 480 subcarriers, the DFT size to be used for CORESET transmission at the gNB and at the UE for receiving CORESET is 480.

In some embodiments, the number of DFTs and the size of each of the DFTs are determined based on (e.g., implicitly) the frequencydomain resource field 406. In one example, the frequencydomain resource field 406 includes a plurality of disjoint sets of consecutive bits, each having a value set to "1" (having at least one bit in a bit value of "0" between any two sets), a first set of consecutive bits having a first size/length set to "1", a second set of consecutive bits having a second size/length set to "1", the number of DFTs being equal to the number of disjoint sets, the size of the first DFT being equal to the number of resource elements in the symbol corresponding to the first set based on the first size/length, and the size of the second DFT being equal to the number of resource elements in the symbol corresponding to the second set based on the second size/length.

In some embodiments, one of the number of DFTs and the size of the DFT higher layer parameters is indicated, where the other parameter is determined based on the frequencydomain resource field 406. For example, if the number of DFT parameters is indicated, bits in the frequencydomain resource field 406 having a value set to "1" are grouped into groups of numberofDFT 402, where at least the groups of numberofDFT-1 are equally sized groups (e.g., having the same number of bits having a value of "1"), where the last group may have a smaller number of bits having a value of "1" than the equally sized groups. The size of the DFT of each group is determined based on (e.g., equal to) the number of resource elements in the symbol corresponding to the resource associated with each group. In another example, if the size of the DFT parameter is indicated, it is assumed that each DFT corresponds to sizeoff 404, and the number of DFTs is determined by dividing the resources corresponding to bits in the frequencydomain resource 406 field having a value set to "1" by sizeoff 404, where the UE assumes or expects an integer number of DFTs.

The number of DFTs and the mapping on frequency (based on the frequencydomain resource field 406 with a value set to "1") may be configured by the network based on the intended frequency selectivity and the PAPR/CM required for transmission.

Fig. 5A provides an illustration of how multiple CORESETs can be mapped onto subcarriers in a symbol, where each CORESET is mapped to a contiguous frequency resource. In fig. 5A, 2 CORESETs 502, 504 are configured to the UE, and in principle, two DFTs 512, 514 can be used, each DFT having a size M (typically, the size of each DFT corresponding to each DFT can be different) for mapping the two CORESETs in frequency (after applying the serial-to-parallel converters 506, 508 and constellation mapping 510). Depending on how the bits in the frequencydomalnresource field are set, the exact mapping is determined. Further, the number of subcarriers corresponding to each bit is equal to the size of DFT, for example, the size of M.

In the depicted example, after DFT 512, 514 and subcarrier mapping 516 are applied, only bit fields of size 2 are used, with bit 1 518 (e.g., the rightmost or least significant bit) indicating the upper half of the frequency resource and bit 2 520 (e.g., the leftmost or most significant bit) indicating the lower half of the frequency resource. For CORESET1 502, only the most significant bits are set to "1" and thus CORESET1 502 is mapped to the lower half of the frequency resource, and for CORESET2 504, only the least significant bits are set to "1" and thus CORESET2 504 is mapped to the upper half of the frequency resource. In some examples, only a single CORESET can be configured to the UE in a symbol, and only a single DFT can be applied.

Fig. 5B provides an illustration of how multiple CORESETs can be mapped onto subcarriers in a symbol, where each of the CORESETs is mapped in an interleaved or distributed manner over frequency (in general, CORESETs can be mapped in a centralized manner over frequency, and signaling as described in this example can also apply). In fig. 5B, 2 CORESETs 502, 504 are configured to the UE, and DFT sizes M512, 514 are used to map the two CORESETs in frequency. Depending on how the bits in the frequencydomalnresource field are set, the exact mapping is determined.

In this example, the number of bits indicated by each bit and the number of frequency resources are not directly related to the DFT size. The number of frequency resources indicated by each bit is equal to the number of consecutive resources in the frequency resources. In this example, the frequencydomain resource field has a size of 4 bits, where bit 1 518 (e.g., the least significant bit) represents the first M/2 subcarriers of CORESET2 504 at the top of the frequency region, followed by bit 2 520 representing the first M/2 subcarriers of CORESET1 502, followed by bit 3 522 representing the last M/2 subcarriers of CORESET2 504, and followed by bit 4 524 (e.g., the most significant bit) representing the last M/2 subcarriers of CORESET1 502 at the bottom of the frequency region. For CORESET1 502, bit 2 520 and bit 4 524 are set to "1" and for CORESET2 504, bit 1 518 and bit 3 522 are set to "1".

In an alternative embodiment, a multiple DFT operation is applied to each CORESET 502, 504. CCEs of CORESET in the time domain are grouped into multiple groups Mg and DFT operations of the same or different sizes, e.g., size M/Mg is applied over each CCE group, where M is the CORESET size. The resulting contiguous frequency resources of each DFT 512, 514 are flexibly mapped 516 to configured subcarriers according to frequencydomalnresource.

In a second embodiment, for multiple DFT-s-OFDM for multiplexing control data of CORESET and DM-RS, one or more DFTs can be applied for a single CORESET on a symbol. In some embodiments, 2 DFTs are applied for a single CORESET, with DFT1 being used to spread DM-RS associated with CORESET for channel estimation and DFT2 being used to spread control information to be transmitted in CORESET. The outputs of the two DFTs may be mapped onto subcarriers of the same symbol and the mapping can be indicated by a frequencydomalnresource field in a ControlResourceSet information element, e.g., as depicted in fig. 4.

In some embodiments, separate fields for DM-RS 602 and control information 604 are included to indicate DFT size and also map to frequency resources, as illustrated in fig. 6. In some embodiments, some of the DFT related fields may be common to the DM-RS and control. To perform frequency domain channel estimation at the receiver, a DFT spreading is applied to the generated DM-RS sequence at the UE, where the same DFT size is used at the gNB. In some embodiments, the number of DFTs and the size of the DFTs for DM-RS may be determined similarly to the number and size for CORESET described above in the first embodiment. This will allow different multiplexing modes of DM-RS resources and control data resources within a symbol.

Fig. 7A provides an illustration of how DM-RS 702 and control data 704 for CORESET can be mapped 716 in an interleaved manner over frequency onto subcarriers in a symbol. In fig. 7A, DM-RS 702 is generated in the time domain and then a separate DFT 712 is used for DM-RS 702 and then the DFT output is multiplexed with control data 704 in a distributed manner. In this example, two DFTs 712, 714 are applied (after serial-to-parallel converters 706, 708 and constellation mapping 710 are applied), with DFT1 714 of size M being used to spread control data and DFT2 712 of size M/3 being used to spread DM-RS 702. The ratio of the DFT size may correspond to a ratio between DM-RS overhead and control data in a symbol. The interleaving pattern is determined based on the bit values in the frequencydomalnresource field for both DM-RS 702 and control 704. Further, the ratio of overheads can depend on how many resources are indicated by a single bit of the field for each of the DM-RS 702 and the control 704.

In an alternative embodiment, a multiple DFT operation is applied to the DM-RS 702. In one embodiment, the time domain DM-RS resources are grouped into multiple groups/bundles of the same or different sizes, and a DFT operation is applied on each bundle. The resulting contiguous frequency resources of each DFT 712, 714 are flexibly mapped/distributed 716 in the frequency grid to cover the control symbols over the frequency. The number of DMRS bundles and the mapping interval in frequency 716 can be configured by the network based on the desired frequency selection and the PAPR/CM required for transmission.

In some embodiments, DM-RS 702 is generated in the frequency domain and need not be spread by DFT 714, and only control data 704 is spread by DFT 714, as illustrated in fig. 7B. Then, the output of the DFT 714 for the control data 704 and frequency domain DM-RS 702 sequence is mapped 716 to subcarriers and then followed by IFFT or IDFT.

In some embodiments, when only one DFT 714 is applied for one CORESET in a symbol, then only control data 704 or DM-RS 702 for CORESET can be transmitted over the symbol. In some embodiments, the DM-RS 702 is transmitted over at least a first symbol of a plurality of symbol lengths CORESET.

In a third embodiment, two DL channels or signals are multiplexed on the same time symbol by using multiple DFTs. In some embodiments, the PDCCH with CORESET0 is multiplexed with SSBs in frequency, e.g., multiplexing modes 2 and 3, where at least one DFT is applied to spread CORESET0 and at least one DFT is applied to spread SSBs. In some embodiments, a common or UE-specific PDCCH and PDSCH are multiplexed in symbols by applying multiple DFTs, with at least one DFT applied to spread PDCCH CORESET and at least one DFT applied to spread PDSCH. In some embodiments, the same subcarrier spacing is configured for PDCCH CORESET0 and SSB, and therefore, only a single IFFT or IDFT is applied at the transmitter for generating the time domain signal. In some embodiments, different subcarrier spacings are configured for PDCCH CORESET0 and SSB, and thus, two different IFFTs or IDFTs are applied at the transmitter for generating the time domain signals.

Fig. 8 depicts a user equipment device 800 of a plurality of discrete fourier transforms that may be used for transmission and reception in accordance with an embodiment of the present disclosure. In various embodiments, user equipment device 800 is used to implement one or more of the solutions described above. User equipment device 800 may be one embodiment of remote unit 105 and/or UE described above. Further, user equipment apparatus 800 may include a processor 805, a memory 810, an input device 815, an output device 820, and a transceiver 825.

In some embodiments, the input device 815 and the output device 820 are combined into a single device, such as a touch screen. In some embodiments, user equipment device 800 may not include any input devices 815 and/or output devices 820. In various embodiments, user equipment device 800 may include one or more of the following: the processor 805, the memory 810, and the transceiver 825, and may not include the input device 815 and/or the output device 820.

As depicted, transceiver 825 includes at least one transmitter 830 and at least one receiver 835. In some embodiments, transceiver 825 communicates with one or more cells (or wireless coverage areas) supported by one or more base station units 121. In various embodiments, transceiver 825 is capable of operating over unlicensed spectrum. Further, the transceiver 825 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 825 may support at least one network interface 840 and/or application interface 845. The application interface(s) 845 may support one or more APIs. The network interface(s) 840 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 840 may be supported as will be appreciated by those of ordinary skill in the art.

In one embodiment, the processor 805 may comprise any known controller capable of executing computer-readable instructions and/or capable of performing logic operations. For example, the processor 805 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, the processor 805 executes instructions stored in the memory 810 to perform the methods and routines described herein. The processor 805 is communicatively coupled to the memory 810, the input device 815, the output device 820, and the transceiver 825. In some embodiments, the processor 805 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

In various embodiments, the processor 805 and transceiver 825 control the user equipment device 800 to implement the UE behavior described above. In one embodiment, the transceiver 825 receives a first configuration from the network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of the transmitter and receiver. In one embodiment, transceiver 825 receives a second configuration for physical channels from the network, the second configuration comprising a number of DFTs applied at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for time symbols.

In some alternative embodiments, only the first configuration is signaled and other configurations for multiple DFT-S-OFDM waveforms are preconfigured or fixed in the specification. In one embodiment, based on the first configuration, multiple DFT-s-OFDM are applied to the DL and UL. In alternative embodiments, the first configuration is separate for UL and DL, and this would allow multiple DFT-s-OFDM applications for UL or DL or both. In some embodiments, multiple DFT-s-OFDM is applied only in certain cases where multiplexing in the frequency domain is required for different physical channels or signals, otherwise, multiple DFT-s-OFDM is not applied even if configured. Such constraints can be fixed or preconfigured.

In one embodiment, transceiver 825 receives a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration, comprising a number of IDFTs applied over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, processor 805 performs multiple DFT-based transmission on time domain symbols transmitted to a network based on a first configuration and a second configuration, and performs multiple IDFT-based reception of time domain symbols received from the network based on an IDFT configuration.

In one embodiment, the first configuration, the second configuration, and the third configuration each form part of a single configuration. In one embodiment, the one or more transforms performed on the physical channel time domain symbols comprise at least one transform selected from the group of: the method includes removing a cyclic prefix portion corresponding to a signal on a transmitter side, passing the signal from a serial to parallel converter, performing a fast fourier transform ("FFT") to convert the signal to frequency domain subcarriers, and demapping the subcarriers.

In one embodiment, transceiver 825 receives a configuration for at least one control resource set ("CORESET") comprising an indication of: the number of DFTs for generating control data and corresponding demodulation reference signals ("DM-RS"), the length of each of the DFTs for determining the length of CORESET in the frequency domain, and the mapping pattern for multiplexing the control data and/or corresponding DM-RS over time symbols.

In one embodiment, the processor 805 applies a first DFT to CORESET to transform the time domain control data to the frequency domain and applies a second DFT to CORESET to transform the time domain DM-RS sequence to the frequency domain, wherein the total length of the CORESET in the frequency domain is equal to the sum of the lengths of the outputs of the first DFT and the second DFT.

In one embodiment, the processor 805 multiplexes the output of the first DFT applied to the time domain control data and the output of the second DFT applied to the DM-RS sequence onto subcarriers in the frequency domain according to a mapping pattern.

In one embodiment, the processor 805 applies one DFT to CORESET to transform time domain control data to the frequency domain and does not apply DFT to the corresponding DM-RS sequence, where the DM-RS sequence is generated in the frequency domain and the total length of CORESET in the frequency domain is equal to the sum of the length of DFT output of the control data and the number of DM-RS frequency domain symbols.

In one embodiment, the processor 805 directly multiplexes the output of the DFT applied to the control data with the frequency domain DM-RS sequence onto subcarriers in the frequency domain according to a mapping pattern.

In one embodiment, in response to the CORESET duration being more than one symbol, the processor 805 applies a different configuration for each symbol in terms of the number of DFTs, the length of each of the DFTs, and the mapping of the DFT outputs to subcarriers in the frequency domain.

In one embodiment, the processor 805 configures CORESET mapping in the frequency domain across different symbols to allow frequency hopping across different symbols. In one embodiment, in response to the CORESET duration being more than one symbol, the processor 805 applies the same configuration for each symbol.

In one embodiment, the processor 805 configures a plurality of CORESETs for UEs having independent configurations in terms of the number of DFTs, the length of each of the DFTs, and the mapping of the DFT outputs to subcarriers in the frequency domain.

In one embodiment, the processor 805 configures the plurality of CORESETs for the UE such that the plurality of CORESETs do not overlap in the frequency domain. In one embodiment, the processor 805 applies a single DFT for CORESET in one symbol and applies time domain multiplexing between control data and a corresponding DM-RS for CORESET in response to CORESET duration of at least two symbols.

In one embodiment, the transceiver 825 transmits the DM-RS symbols before the control data symbols for CORESET. In one embodiment, transceiver 825 receives a configuration for CORESET comprising at least one selected from the group consisting of: the method includes generating a number of DFTs of control data and/or a corresponding DM-RS, a length of each of the DFTs for determining a length of CORESET in a frequency domain, a configuration of a synchronization signal block ("SSB") for including a number of DFTs for generating a corresponding signal, a length of each of the DFTs for determining a length of the signal in a frequency domain, and an indication of a frequency domain multiplexing mode that multiplexes an output of the DFT for CORESET and an output of the DFT for SSB.

In one embodiment, memory 810 is a computer-readable storage medium. In some embodiments, memory 810 includes a volatile computer storage medium. For example, memory 810 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 810 includes a non-volatile computer storage medium. For example, memory 810 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 810 includes both volatile and nonvolatile computer storage media.

In some embodiments, memory 810 stores data related to a plurality of fourier variations for transmission and reception. For example, memory 810 may store various parameters, panel/beam configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 810 also stores program code and related data, such as an operating system or other controller algorithms running on user equipment device 800.

In one embodiment, the input device 815 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, and the like. In some embodiments, the input device 815 may be integrated with the output device 820, for example, as a touch-screen or similar touch-sensitive display. In some embodiments, the input device 815 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, the input device 815 includes two or more different devices, such as a keyboard and a touch panel.

In one embodiment, the output device 820 is designed to output visual, audible, and/or tactile signals. In some embodiments, output device 820 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output devices 820 may include, but are not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 820 may include a wearable display, such as a smart watch, smart glasses, head-up display, or the like, separate from but communicatively coupled to the rest of the user equipment device 800. Further, the output device 820 may be a component of a smart phone, personal digital assistant, television, desktop computer, notebook (laptop) computer, personal computer, vehicle dashboard, or the like.

In some embodiments, output device 820 includes one or more speakers for producing sound. For example, the output device 820 may generate an audible alarm or notification (e.g., a beep or bell). In some embodiments, output device 820 includes one or more haptic devices for generating vibrations, motion, or other haptic feedback. In some embodiments, all or part of the output device 820 may be integrated with the input device 815. For example, input device 815 and output device 820 may form a touch screen or similar touch-sensitive display. In other embodiments, the output device 820 may be located near the input device 815.

The transceiver 825 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 825 operates under the control of the processor 805 to transmit and also receive messages, data, and other signals. For example, the processor 805 may selectively activate the transceiver 825 (or portions thereof) at particular times in order to transmit and receive messages.

The transceiver 825 includes at least a transmitter 830 and at least one receiver 835. One or more transmitters 830 may be used to provide UL communication signals, such as UL transmissions described herein, to base unit 121. Similarly, one or more receivers 835 may be used to receive DL communication signals from base station unit 121 as described herein. Although only one transmitter 830 and one receiver 835 are illustrated, user equipment device 800 may have any suitable number of transmitters 830 and receivers 835. Further, the transmitter(s) 830 and receiver(s) 835 may be any suitable type of transmitter and receiver. In one embodiment, the transceiver 825 includes a first transmitter/receiver pair for communicating with a mobile communication network on an licensed radio spectrum and a second transmitter/receiver pair for communicating with the mobile communication network on an unlicensed radio spectrum.

In some embodiments, a first transmitter/receiver pair for communicating with a mobile communication network on an licensed radio spectrum and a second transmitter/receiver pair for communicating with a mobile communication network on an unlicensed radio spectrum may be combined into a single transceiver unit, e.g., a single chip, that performs the functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, some transceivers 825, transmitters 830, and receivers 835 may be implemented as physically separate components accessing shared hardware resources and/or software resources (such as, for example, network interface 840).

In various embodiments, one or more transmitters 830 and/or one or more receivers 835 may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, system-on-a-chip, ASIC, or other type of hardware component. In some embodiments, one or more transmitters 830 and/or one or more receivers 835 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components, such as the network interface 840 or other hardware components/circuitry, may be integrated into a single chip with any number of transmitters 830 and/or receivers 835. In such embodiments, the transmitter 830 and receiver 835 may be logically configured as a transceiver 825 using one or more common control signals, or as a modular transmitter 830 and receiver 835 implemented in the same hardware chip or in a multi-chip module.

Fig. 9 depicts a network apparatus 900 of multiple discrete fourier transforms that may be used for transmission and reception in accordance with an embodiment of the present disclosure. In one embodiment, network apparatus 900 may be an implementation of a RAN node, such as base station unit 121, RAN node 210, or a gNB as described above. Further, the base network apparatus 900 may include a processor 905, a memory 910, an input device 915, an output device 920, and a transceiver 925.

In some embodiments, the input device 915 and the output device 920 are combined into a single device, such as a touch screen. In some embodiments, network apparatus 900 may not include any input devices 915 and/or output devices 920. In various embodiments, the network device 900 may include one or more of the following: the processor 905, the memory 910, and the transceiver 925, and may not include an input device 915 and/or an output device 920.

As depicted, transceiver 925 includes at least one transmitter 930 and at least one receiver 935. Here, transceiver 925 communicates with one or more remote units 105. In addition, the transceiver 925 may support at least one network interface 940 and/or application interface 945. The application interface(s) 945 may support one or more APIs. Network interface(s) 940 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 940 may be supported as will be appreciated by those of ordinary skill in the art.

In one embodiment, the processor 905 may comprise any known controller capable of executing computer-readable instructions and/or capable of performing logic operations. For example, the processor 905 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, the processor 905 executes instructions stored in the memory 910 to perform the methods and routines described herein. The processor 905 is communicatively coupled to the memory 910, the input device 915, the output device 920, and the transceiver 925. In some embodiments, the processor 905 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

In various embodiments, the network device 900 is a RAN node (e.g., a gNB) that includes a processor 905 and a transceiver 925. In one embodiment, the transceiver 925 transmits an indication to a user equipment ("UE") device that includes at least a beta offset value and multiplexing of multiple repetitions of uplink control information ("UCI") over a single transmission occasion of a physical uplink shared channel ("PUSCH"). In one embodiment, the transceiver 925 transmits a configuration to the UE device to determine a starting symbol index and a maximum number of symbols for each of a plurality of repetitions of UCI on PUSCH. In one embodiment, the transceiver 925 receives UCI from the UE device on PUSCH, the UCI being multiplexed based on the starting symbol index and the maximum number of symbols for each of the multiple repetitions according to the indicated beta offset value.

In one embodiment, memory 910 is a computer-readable storage medium. In some embodiments, memory 910 includes a volatile computer storage medium. For example, memory 910 may include RAM including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 910 includes a non-volatile computer storage medium. For example, memory 910 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 910 includes both volatile and nonvolatile computer storage media.

In some embodiments, the memory 910 stores data related to a plurality of discrete fourier transforms for transmission and reception. For example, memory 910 can store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory 910 also stores program codes and related data, such as an operating system or other controller algorithms running on the network device 900.

In one embodiment, the input device 915 may include any known computer input device including a touch panel, buttons, keyboard, stylus, microphone, and the like. In some embodiments, the input device 915 may be integrated with the output device 920, for example, as a touch screen or similar touch sensitive display. In some embodiments, the input device 915 includes a touch screen such that text can be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, the input device 915 includes two or more different devices, such as a keyboard and a touch panel.

In one embodiment, the output device 920 is designed to output visual, audible, and/or tactile signals. In some embodiments, the output device 920 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 920 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 920 may include a wearable display, such as a smart watch, smart glasses, head-up display, etc., separate from but communicatively coupled to the rest of the network apparatus 900. Further, the output device 920 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

In some embodiments, the output device 920 includes one or more speakers for producing sound. For example, the output device 920 may generate an audible alarm or notification (e.g., a beep or bell). In some embodiments, output device 920 includes one or more haptic devices for generating vibrations, motion, or other haptic feedback. In some embodiments, all or part of the output device 920 may be integrated with the input device 915. For example, the input device 915 and the output device 920 may form a touch screen or similar touch-sensitive display. In other embodiments, the output device 920 may be located near the input device 915.

The transceiver 925 includes at least a transmitter 930 and at least one receiver 935. One or more transmitters 930 may be used to communicate with UEs, as described herein. Similarly, one or more receivers 935 may be used to communicate with network functions in a non-public network ("NPN"), PLMN, and/or RAN, as described herein. Although only one transmitter 930 and one receiver 935 are illustrated, the network apparatus 900 may have any suitable number of transmitters 930 and receivers 935. Further, the transmitter(s) 930 and receiver(s) 935 may be any suitable type of transmitter and receiver.

In one embodiment, the processor 905 determines a first configuration for applying a multiple discrete fourier transform ("DFT") based waveform at the transmitter and/or receiver. In one embodiment, the processor 905 determines a second configuration for the physical channel comprising a number of DFTs to apply at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for the time symbols.

In one embodiment, processor 905 determines a third configuration for determining an inverse DFT ("IDFT") configuration that includes a number of IDFTs applied over time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, the transceiver 925 transmits the determined first, second, and third configurations to a user equipment ("UE") device and transmits time domain symbols to the UE, wherein the UE performs multi-IDFT based reception of the time domain symbols based on the IDFT configuration.

Fig. 10 is a flow chart of a method 1000 for multiple discrete fourier transforms of transmission and reception. The method 1000 may be performed by a UE, such as remote unit 105, UE, and/or user equipment device 800, as described herein. In some embodiments, the method 1000 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

In one embodiment, the method 1000 includes receiving 1005 a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver. In one embodiment, the method 1000 includes receiving 1010 a second configuration for a physical channel from a network, the second configuration including a number of DFTs to be applied at a transmitter to transform one or more time domain signals and/or channels to a frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for a time symbol.

In one embodiment, the method 1000 includes receiving 1015 a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration, including a number of IDFTs applied over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, the method 100 includes performing 1020 a multiple DFT-based transmission on time domain symbols transmitted to a network based on the first configuration and the second configuration. In one embodiment, the method 1000 includes performing 1025 multi-IDFT based reception of time domain symbols received from the network based on the IDFT configuration, and the method 1000 ends.

Fig. 11 is a flow chart of a method 1100 for multiple discrete fourier transforms of transmission and reception. The method 1100 may be performed by a network entity, such as a base node, a gNB, and/or a network equipment apparatus 900. In some embodiments, the method 1100 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

In one embodiment, the method 1100 includes determining 1105 a first configuration for applying a plurality of discrete fourier transform ("DFT") based waveforms at a transmitter and/or receiver. In one embodiment, the method 1100 includes determining 1110 a second configuration for a physical channel, the second configuration including a number of DFTs to apply at a transmitter to transform one or more time domain signals and/or channels to a frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for a time symbol.

In one embodiment, the method 1100 includes determining 1115 a third configuration for determining an inverse DFT ("IDFT") configuration including a number of IDFTs to apply over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, the method 1100 includes transmitting 1120 the determined first configuration, second configuration, and third configuration to a user equipment ("UE") device. In one embodiment, the method 1100 includes transmitting 1125 time domain symbols to a UE, wherein the UE performs multi-IDFT based reception of the time domain symbols based on an IDFT configuration, and the method 1100 ends.

A first apparatus for multiple discrete fourier transforms of transmission and reception is disclosed. The first apparatus may include a UE, e.g., remote unit 105, UE, and/or user equipment apparatus 800, as described herein. In some embodiments, the first apparatus may include a processor, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc., that executes program code.

In one embodiment, a first apparatus includes a transceiver to receive a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver. In one embodiment, a transceiver receives a second configuration for a physical channel from a network, the second configuration including a number of DFTs applied at a transmitter to transform one or more time domain signals and/or channels to a frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for a time symbol.

In one embodiment, the transceiver receives a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration, including a number of IDFTs applied over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, a first apparatus includes a processor to perform multiple DFT-based transmission on time domain symbols transmitted to a network based on a first configuration and a second configuration, and perform multiple IDFT-based reception of time domain symbols received from the network based on an IDFT configuration.

In one embodiment, a transceiver receives a configuration for at least one control resource set ("CORESET") comprising an indication of: the number of DFTs for generating control data and corresponding demodulation reference signals ("DM-RS"), the length of each of the DFTs for determining the length of CORESET in the frequency domain, and the mapping pattern for multiplexing the control data and/or corresponding DM-RS over time symbols.

In one embodiment, the processor applies a first DFT to CORESET to transform the time domain control data to the frequency domain and applies a second DFT to CORESET to transform the time domain DM-RS sequence to the frequency domain, wherein the total length of the CORESET in the frequency domain is equal to the sum of the lengths of the outputs of the first DFT and the second DFT.

In one embodiment, the processor multiplexes an output of a first DFT applied to the time domain control data and an output of a second DFT applied to the DM-RS sequence onto subcarriers in the frequency domain according to a mapping pattern.

In one embodiment, the processor applies one DFT for CORESET to transform the time domain control data to the frequency domain and does not apply the DFT to the corresponding DM-RS sequence, wherein the DM-RS sequence is generated in the frequency domain and the total length of the CORESET in the frequency domain is equal to the sum of the length of the DFT output of the control data and the number of DM-RS frequency domain symbols.

In one embodiment, the processor directly multiplexes the output of the DFT applied to the control data with the frequency domain DM-RS sequence onto subcarriers in the frequency domain according to a mapping pattern.

In one embodiment, in response to the CORESET duration being more than one symbol, the processor applies a different configuration for each symbol in terms of the number of DFTs, the length of each of the DFTs, and the mapping of the DFT outputs to subcarriers in the frequency domain.

In one embodiment, the processor configures CORESET mapping in the frequency domain across different symbols to allow frequency hopping across different symbols. In one embodiment, in response to the CORESET duration being more than one symbol, the processor applies the same configuration for each symbol.

In one embodiment, a processor configures a plurality of CORESETs for a UE having an independent configuration in terms of the number of DFTs, the length of each of the DFTs, and the mapping of the DFT outputs to subcarriers in the frequency domain.

In one embodiment, the processor configures the plurality of CORESETs for the UE such that the plurality of CORESETs do not overlap in the frequency domain. In one embodiment, the processor applies a single DFT for CORESET in one symbol and applies time domain multiplexing between control data and a corresponding DM-RS for CORESET in response to CORESET duration of at least two symbols.

In one embodiment, the transceiver transmits the DM-RS symbols before the control data symbols for CORESET. In one embodiment, the transceiver receives a configuration for CORESET comprising at least one selected from the group of: the method includes generating control data and/or a number of DFTs of a corresponding DM-RS, determining a length of each of the DFTs of the CORESET in a frequency domain, configuring a synchronization signal block ("SSB") including the number of DFTs for generating a corresponding signal, determining a length of each of the DFTs of the signal in the frequency domain, and multiplexing an output of the DFT for the CORESET and an output of the DFT for the SSB.

A first method of a plurality of discrete fourier transforms for transmission and reception is disclosed. The first method may be performed by a UE as described herein, e.g., remote unit 105, UE, and/or user equipment device 800. In some embodiments, the first method may be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

In one embodiment, a first method includes receiving a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver. In one embodiment, a first method includes receiving, from a network, a second configuration for a physical channel, the second configuration including a number of DFTs applied at a transmitter to transform one or more time domain signals and/or channels to a frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for a time symbol.

In one embodiment, a first method includes receiving a third configuration from a network for determining an inverse DFT ("IDFT") configuration based on the second configuration, including a number of IDFTs applied over a time symbol to receive one or more signals, a size of each of the IDFTs, and a demapping pattern from subcarriers to the IDFTs. In one embodiment, a first method includes performing a multiple DFT-based transmission on time domain symbols transmitted to a network based on a first configuration and a second configuration; and performing multi-IDFT based reception of the time domain symbols received from the network based on the IDFT configuration.

In one embodiment, a first method includes receiving a configuration for at least one control resource set ("CORESET") including an indication of: the number of DFTs for generating control data and corresponding demodulation reference signals ("DM-RS"), the length of each of the DFTs for determining the length of CORESET in the frequency domain, and the mapping pattern for multiplexing the control data and/or corresponding DM-RS over time symbols.

In one embodiment, the first method includes applying a first DFT to CORESET to transform time domain control data to the frequency domain and applying a second DFT to CORESET to transform the time domain DM-RS sequence to the frequency domain, wherein a total length of the CORESET in the frequency domain is equal to a sum of lengths of outputs of the first DFT and the second DFT.

In one embodiment, a first method includes multiplexing an output of a first DFT applied to time domain control data and an output of a second DFT applied to a DM-RS sequence onto subcarriers in a frequency domain according to a mapping pattern.

In one embodiment, the first method includes applying one DFT to the CORESET to transform the time domain control data to the frequency domain and not applying the DFT to a corresponding DM-RS sequence, wherein the DM-RS sequence is generated in the frequency domain and a total length of the CORESET in the frequency domain is equal to a sum of a length of a DFT output of the control data and a number of DM-RS frequency domain symbols.

In one embodiment, the first method includes directly multiplexing an output of a DFT applied to control data with a frequency domain DM-RS sequence onto subcarriers in a frequency domain according to a mapping pattern.

In one embodiment, the first method includes, in response to the CORESET duration being more than one symbol, applying a different configuration for each symbol in terms of a number of DFTs, a length of each of the DFTs, and a mapping of DFT outputs to subcarriers in the frequency domain.

In one embodiment, the first method includes configuring CORESET mapping in the frequency domain across different symbols to allow frequency hopping across different symbols. In one embodiment, the first method includes, in response to the CORESET duration being more than one symbol, applying the same configuration for each symbol.

In one embodiment, a first method includes configuring a plurality of CORESETs for a UE having independent configurations in terms of a number of DFTs, a length of each of the DFTs, and a mapping of DFT outputs to subcarriers in a frequency domain.

In one embodiment, a first method includes configuring a plurality of CORESETs for a UE such that the plurality of CORESETs do not overlap in the frequency domain. In one embodiment, a first method includes applying a single DFT for CORESET in one symbol and, in response to CORESET duration being at least two symbols, applying time domain multiplexing between control data and a corresponding DM-RS for CORESET.

In one embodiment, the first method includes transmitting DM-RS symbols prior to control data symbols for CORESET. In one embodiment, a first method includes receiving a configuration for CORESET comprising at least one selected from the group consisting of: the method includes generating control data and/or a number of DFTs of a corresponding DM-RS, determining a length of each of the DFTs of the CORESET in a frequency domain, configuring a synchronization signal block ("SSB") including the number of DFTs for generating a corresponding signal, determining a length of each of the DFTs of the signal in the frequency domain, and multiplexing an output of the DFT for the CORESET and an output of the DFT for the SSB.

A second apparatus for multiple discrete fourier transforms of transmission and reception is disclosed. The second apparatus may include a network entity, such as a base node, a gNB, and/or a network device apparatus 900. In some embodiments, the second device comprises a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

In one embodiment, the second apparatus includes a processor that determines a first configuration for applying a multiple discrete fourier transform ("DFT") based waveform at the transmitter and/or receiver. In one embodiment, the processor determines a second configuration for the physical channel, the second configuration including a number of DFTs to be applied at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for the time symbols.

In one embodiment, the processor determines a third configuration for determining an inverse DFT ("IDFT") configuration that includes a number of IDFTs applied over time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, the second apparatus includes a transceiver to transmit the determined first configuration, second configuration, and third configuration to a user equipment ("UE") device, and to transmit time domain symbols to the UE, wherein the UE performs multi-IDFT based reception of the time domain symbols based on the IDFT configuration.

A second method of multiple discrete fourier transforms for transmission and reception is disclosed. The second method may be performed by a network entity such as a base node, a gNB, and/or a network equipment apparatus 900. In some embodiments, the second method may be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

In one embodiment, a second method includes determining a first configuration for applying a multiple discrete fourier transform ("DFT") based waveform at a transmitter and/or receiver. In one embodiment, the second method includes determining a second configuration for the physical channel, the second configuration including a number of DFTs to be applied at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for the time symbols.

In one embodiment, the second method includes determining a third configuration for determining an inverse DFT ("IDFT") configuration including a number of IDFTs applied over the time symbols to receive the one or more signals, a size of each of the IDFTs, and a demapping pattern from the subcarriers to the IDFTs. In one embodiment, a second method includes transmitting the determined first configuration, second configuration, and third configuration to a user equipment ("UE") device; and transmitting the time domain symbols to the UE, wherein the UE performs multi-IDFT based reception of the time domain symbols based on the IDFT configuration.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A user equipment ("UE") device apparatus, the apparatus comprising:

a transceiver, the transceiver:

receiving a first configuration from a network to apply a multiple discrete fourier transform ("DFT") based waveform at one or more of a transmitter and a receiver;

receiving a second configuration for physical channels from the network, the second configuration comprising a number of DFTs for application at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for time symbols; and is also provided with

Receiving a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration, the IDFT configuration comprising a number of IDFTs applied over time symbols to receive one or more signals, a size of each of the IDFTs, and a demapping pattern from subcarriers to the IDFTs; and

A processor, the processor:

performing a multiple DFT-based transmission on time domain symbols transmitted to the network based on the first configuration and the second configuration; and is also provided with

Based on the IDFT configuration, multi-IDFT-based reception of time domain symbols received from the network is performed.

2. The apparatus of claim 1, wherein the first configuration, the second configuration, and the third configuration each form part of a single configuration.

3. The apparatus of claim 1, wherein the transceiver receives a configuration for at least one control resource set ("CORESET") comprising an indication of: the method includes generating a number of DFTs for generating control data and corresponding demodulation reference signals ("DM-RS"), a length of each of the DFTs for determining a length of the CORESET in a frequency domain, and a mapping pattern for multiplexing the control data and/or the corresponding DM-RS over time symbols.

4. The apparatus of claim 3, wherein the processor:

applying a first DFT to the CORESET to transform time domain control data to the frequency domain; and is also provided with

A second DFT is applied to the CORESET to transform the time domain DM-RS sequence to the frequency domain,

Wherein the total length of the CORESET in the frequency domain is equal to the sum of the lengths of the outputs of the first DFT and the second DFT.

5. The apparatus of claim 4, wherein the processor multiplexes an output of the first DFT applied to the time domain control data and an output of the second DFT applied to the DM-RS sequence onto subcarriers in a frequency domain according to the mapping pattern.

6. The apparatus of claim 3, wherein the processor:

applying a DFT to the CORESET to transform the time domain control data to the frequency domain; and is also provided with

The DFT is not applied to the corresponding DM-RS sequence,

wherein the DM-RS sequence is generated in the frequency domain and the total length of the CORESET in the frequency domain is equal to the sum of the length of the DFT output of the control data and the number of DM-RS frequency domain symbols.

7. The apparatus of claim 6, wherein the processor multiplexes the output of the DFT applied to the control data with a frequency domain DM-RS sequence directly onto subcarriers in a frequency domain according to the mapping pattern.

8. The apparatus of claim 7, wherein the processor, in response to a CORESET duration of more than one symbol:

Applying a different configuration for each of the symbols in terms of the number of DFTs, the length of each of the DFTs, and the mapping of the DFT outputs to the subcarriers in the frequency domain; and is also provided with

CORESET mapping in the frequency domain is configured across different symbols to allow frequency hopping across the different symbols.

9. The apparatus of claim 8, wherein the processor configures a plurality of CORESETs for UEs having independent configurations in terms of a number of DFTs, a length of each of the DFTs, and a mapping of DFT outputs to subcarriers in a frequency domain.

10. The apparatus of claim 9, wherein the processor configures a plurality of CORESETs for a UE such that the plurality of CORESETs do not overlap in the frequency domain.

11. The apparatus of claim 10, wherein the processor:

applying a single DFT for CORESET in one symbol; and is also provided with

In response to the CORESET duration being at least two symbols, time domain multiplexing is applied between the control data and the corresponding DM-RS for CORESET.

12. The apparatus of claim 11, wherein the transceiver transmits DM-RS symbols before control data symbols for the CORESET.

13. The apparatus of claim 1, wherein the transceiver receives a configuration for CORESET, the configuration comprising at least one selected from the group of: the apparatus may include means for generating a number of DFTs of control data and/or a corresponding DM-RS, means for determining a length of each of the DFTs of the CORESET in a frequency domain, means for configuring a synchronization signal block ("SSB") including the number of DFTs for generating a corresponding signal, means for determining a length of each of the DFTs of the signal in the frequency domain, and means for multiplexing an output of the DFT of the CORESET and an output of the DFT of the SSB in a frequency domain multiplexing mode.

14. A method at a user equipment ("UE") device, the method comprising:

receiving a second configuration for physical channels from the network, the second configuration comprising a number of DFTs for application at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for time symbols;

receiving a third configuration from the network for determining an inverse DFT ("IDFT") configuration based on the second configuration, the third configuration comprising a number of IDFTs applied over time symbols to receive one or more signals, a size of each of the IDFTs, and a demapping pattern from subcarriers to the IDFTs;

performing a multiple DFT-based transmission on time domain symbols transmitted to the network based on the first configuration and the second configuration; and

15. A network node apparatus, the apparatus comprising:

a processor, the processor:

determining a first configuration for applying a multiple discrete fourier transform ("DFT") based waveform at the transmitter and/or receiver;

determining a second configuration for physical channels, the second configuration comprising a number of DFTs to be applied at the transmitter to transform one or more time domain signals and/or channels to the frequency domain, a size of each of the DFTs, and a mapping pattern for mapping an output of each of the DFTs onto subcarriers in the frequency domain for time symbols; and is also provided with

Determining a third configuration for determining an inverse DFT ("IDFT") configuration, the third configuration comprising a number of IDFTs applied over time symbols to receive one or more signals, a size of each of the IDFTs, and a demapping pattern from subcarriers to the IDFTs; and

a transceiver, the transceiver:

transmitting the determined first configuration, second configuration, and third configuration to a user equipment ("UE") device; and is also provided with

Transmitting a time domain symbol to the UE, wherein the UE performs multi-IDFT based reception of the time domain symbol based on the IDFT configuration.