Control signal configures waveform type

Abstract

Apparatuses, methods, and systems for associating control signaling configurations with waveform types are disclosed. An apparatus (500) in a mobile communication network includes a processor (505) and a transceiver (525) that receives (705) a configuration for control signaling. The processor (505) associates (710) the control signaling configuration with a waveform type, where at least two different waveform types are associated with different control signaling configurations. The transceiver (525) receives (715) a control signal transmission from a radio access network using the associated waveform type.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 044,454, filed June 26, 2020, entitled “Apparatus, Methods, and Systems for Detecting and Switching Multiple Waveforms,” by Ankit Bhamri, Ali Ramadan Ali, Karthikeyan Ganesan, Alexander Golitschek, and Vijay Nangia, which is incorporated herein by reference. Technical Field

[0003] The subject matter disclosed herein generally relates to wireless communication, and more specifically to apparatus, methods and systems for multiple waveform indication and / or switching. Background Technology

[0004] In some wireless communication systems, radio access networks support NR-based operation at frequencies between 52.6 GHz and 71 GHz. Due to anticipated performance degradation at higher frequencies, additional design requirements for NR above 52.6 GHz have been considered. In addition to high path loss, the RF components of the transmitter and receiver exhibit nonlinear transmission characteristics, leading to further system degradation. Summary of the Invention

[0005] A process for associating control signaling configuration with waveform type is disclosed. This process can be implemented by an apparatus, system, method, or computer program product.

[0006] A method for a user equipment (“UE”) includes receiving a configuration for control signaling and associating the control signaling configuration with waveform types, wherein at least two different waveform types are associated with different control signaling configurations. The method includes receiving control signal transmissions from a radio access network using the associated waveform types.

[0007] A method for a radio access network (“RAN”) node includes configuring a UE using a set of control signaling configurations and transmitting control signal transmissions using associated waveform types, wherein at least two different waveform types are associated with different control signaling configurations. Attached Figure Description

[0008] 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 to be limiting of the scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

[0009] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for associating control signaling configurations with waveform types;

[0010] Figure 2 is a block diagram illustrating one embodiment of a 5G New Radio (“NR”) protocol stack;

[0011] Figure 3 is a diagram illustrating one embodiment of an example RRC configuration of a CORESET IE that can be used for multiple waveform indications and / or switching;

[0012] Figure 4A is a diagram illustrating one embodiment of a control resource set (“CORESET”) region;

[0013] Figure 4B is a diagram illustrating one embodiment of a CORESET region that is localized by bandwidth part (“BWP”);

[0014] Figure 5 is a diagram showing one embodiment of a user equipment device that can be used to associate control signaling configurations with waveform types;

[0015] Figure 6 is a diagram illustrating one embodiment of a network device that can be used to associate control signaling configurations with waveform types;

[0016] Figure 7 is a flow diagram illustrating one embodiment of a first method for associating control signaling configurations with waveform types; and

[0017] Figure 8 is a flow diagram illustrating one embodiment of a second method for associating control signaling configurations with waveform types. DETAILED DESCRIPTION

[0018] As those skilled in the art will appreciate, the various aspects of the embodiments can be embodied as a system, device, method or program product. Accordingly, the embodiments can 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 that can all generally be referred to herein as a “module,” “system,” “device” or “apparatus.” Furthermore, the embodiments can take the form of program product embodied in one or more computer readable mediums having computer readable program code embodied thereon.

[0019] For example, disclosed embodiments can be implemented in hardware circuitry, including custom very-large-scale integration ("VLSI") or gate array circuitry, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Disclosed embodiments can 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, disclosed embodiments can include one or more physical or logical blocks of executable code, which may, for example, be organized as an object, procedure, or function.

[0020] Furthermore, embodiments can 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 also referred to as code. The storage devices can be tangible, non-transitory, and / or non-transmission. The storage devices can not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0021] Any combination of one or more computer readable medium can be utilized. The computer readable medium can be a computer readable storage medium. The computer readable storage medium can be a storage device storing the code. The storage device can 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.

[0022] 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 can 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.

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

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

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

[0026] As used herein, a list with a conjunction of “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the terminology “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 includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the terminology “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 excludes combinations 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 excludes combinations of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C.

[0027] Various aspects of embodiments are described in further detail below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart and / or schematic block diagrams, and combinations of blocks in the schematic flowchart and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the code, which executes via the processor of the computer or other programmable data processing apparatus, creates means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0028] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0029] The code can 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 execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0030] The diagrams in the drawings are intended to facilitate understanding of implementations of the present disclosure and, in that regard, are not intended to be limiting of the scope of the disclosure. In particular, the exercises depicted in the drawings are intended to show the architecture, functionality, and operation of some implementations of various embodiments. In this regard, each block in the flowchart diagrams and / or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions.

[0031] It should also be noted that in some alternative implementations, the functions noted in the blocks can 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 can sometimes be executed in the reverse order, depending upon the functionality involved. Such variation, and other variations, will depend from the functionality involved, and such orderings are within the scope of the present disclosure. Other steps and methods can be conceived that are equivalent in function, logic, or effect to those illustrated, with the scope of the present disclosure included therein.

[0032] Although various arrow types and line types can be employed in the flowchart diagrams and / or block diagrams, they are used in these diagrams to reflect different conceptual aspects.

[0033] The description of elements in each figure can refer to elements of previous figures. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0034] Generally, the present disclosure describes systems, methods, and apparatuses for associating control signaling configurations with waveform types and corresponding scheduled transmissions for downlink and uplink. In certain embodiments, methods can be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system can include a computer-readable medium containing computer readable code, which, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0035] Due to the performance degradation expected at high frequencies, additional design requirements for new radio (“NR”) beyond 52.6 GHz have been considered for further investigation. In addition to high path loss, the radio frequency (“RF”) components of the transmitter and receiver exhibit non-linear transmission characteristics, which lead to further system degradation.

[0036] In NR Release 15 (“Rel-15”), a multi-carrier (e.g., orthogonal frequency division multiplexing (“OFDM”)) based waveform has been adopted for downlink (“DL”) as well as for uplink (“UL”). For some cases, especially at cell edge, a single carrier (e.g., discrete Fourier transform (“DFT”) spread OFDM (“DFT-s-OFDM”)) is also used as an option for uplink (“UL”). However, due to its sensitivity to phase noise and its high peak-to-average power ratio (“PAPR”) or cubic metric (“CM”) that limits cell coverage, cyclic prefix OFDM (“CP-OFDM”) performance degrades at high frequencies (e.g., 52.6 GHz and beyond). The problem of CP-OFDM at high frequencies becomes severe with an increase in modulation order and / or channel bandwidth. Thus, some physical layer channels will be more impacted than others.

[0037] The above issues make single carrier waveforms a suitable candidate at high frequencies due to their natural robustness to phase noise and their low PAPR or CM. In NR Rel-15 / 16, UL has supported single carrier (DFT-s-OFDM and / or single carrier frequency division multiple access (“SC-FDMA”)). However, power constraints of the UE, especially at cell edge, make it necessary to also enhance UL by adopting other single carrier waveforms, such as single carrier quadrature amplitude modulation (“SC-QAM”) or single carrier frequency domain equalization (“SC-FDE”) / cyclic prefix single carrier (“CP-SC”) for cell edge scenarios.

[0038] One candidate waveform type for use at high frequencies (e.g., 52.6 GHz and beyond) is a single carrier waveform based on OFDM, such as a DFT-s-OFDM waveform. Single carrier waveforms can be used for downlink (“DL”) due to their low PAPR compared to CP-OFDM and their better frequency flexibility compared to pure single carrier candidates such as SC-QAM. On the other hand, while using DFT-s-OFDM or other single carrier candidates for DL enhances cell coverage, it limits the multiple-in-multiple-out (“MIMO”) capability of the system and reduces the flexibility of demodulation reference signal (“DMRS”) mapping. Some FR4 use cases described in 3GPP TR 38.807, such as enhanced mobile broadband (“eMBB”) for high data rates, require high channel bandwidth for high throughput, where MIMO can also play an important role.

[0039] On the other hand, in factory automation / industrial internet of things ("IIoT") applications, latency, massive access, and reliability are the main key performance indicators ("KPIs"). Other use cases, such as backhaul, integrated access and backhaul ("IAB"), mainly work in line of sight ("LOS") conditions, where fading and power consumption are not the main issues. Mobile data offloading requires coexistence with other systems, e.g., 60GHz Wi-Fi (i.e., "WiGig"). For short-range high-data-rate device-to-device ("D2D") communication, coverage is limited, and the PAPR issue is not the main issue to be solved. Trade-offs in latency and throughput between cell coverage requirements and quality of service ("QoS") requirements need to be considered to support different deployment and use case scenarios. Therefore, multi-waveform support for downlink ("DL") and uplink ("UL") is a practical solution to accommodate different deployment, coverage, and use case scenarios, enabling high system flexibility, and optimizing the performance of the solution for DL waveform semi-static switching for data transmission.

[0040] In this disclosure, the problem of configuring (or indicating or switching) multiple waveforms, and multi-beam (or multiple transmission and reception point ("multi-TRP") transmission / reception of physical downlink control channel ("PDCCH") and corresponding scheduled physical downlink shared channel ("PDSCH"), physical uplink shared channel ("PUSCH"), and / or physical uplink control channel ("PUCCH") transmissions and repetitions is addressed.

[0041] Figure 1 A wireless communication system 100 for associating control signaling configuration with waveform type according to embodiments of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network ("RAN") 120, and a mobile core network 140. The RAN 120 and mobile core network 140 form a mobile communication network. The RAN 120 can be composed of a base unit 121 with which the remote unit 105 communicates using wireless communication links 123. Although a certain number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 are depicted in the figure, those skilled in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 can be included in the wireless communication system 100. Figure 1 Although a certain number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 are depicted in the figure, those skilled in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 can be included in the wireless communication system 100.

[0042] In one implementation, the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 can be a Next Generation Radio Access Network (“NG-RAN”), implementing the New Radio (“NR”) Radio Access Technology (“RAT”) and / or the Long Term Evolution (“LTE”) RAT. In another example, the RAN 120 can include a non-3GPP RAT (e.g., Wi-Fi® compatible to the Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 family of standards). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 can implement some other open or proprietary communication network protocol, for example, Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16 standards, among others. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0043] In one embodiment, the remote units 105 can include computing devices, such as desktop, laptop, personal digital assistant (“PDA”), tablet, smart phone, smart television (e.g., television connected to the Internet), smart appliance (e.g., appliance connected to the Internet), set-top box, game console, security system (including security camera), vehicle

[0044] ​The remote units 105 can directly communicate with one or more base units 121 of the RAN 120 via uplink ("UL") and downlink ("DL") communication signals. The UL and DL communication signals can be carried over the wireless communication links 123. Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140. As described in more detail below, the base unit 121 can provide a cell that operates using a first carrier frequency and / or a cell that operates using a second frequency. The cell using the first carrier frequency can form a first frequency layer, while the cell using the second carrier frequency can form a second frequency layer.

[0045] In some embodiments, the remote units 105 communicate with the application server 151 via a network connection with the mobile core network 140. For example, an application 107 (e.g., a web browser, a messaging client, a telephone application, and / or a Voice-over-Internet Protocol ("VoIP") application) in a remote unit 105 can 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 RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 in the packet data network 150 using the PDU session. The PDU session represents a logical connection between the remote unit 105 and a user plane function ("UPF") 141.

[0046] To establish a PDU session (or PDN connection), the remote unit 105 must register with the mobile core network 140 (also referred to as "attaching to the mobile core network" in the context of a fourth generation ("4G") system). Note that the remote unit 105 can establish one or more PDU sessions (or other data connections) with the mobile core network 140. Thus, the remote unit 105 can have at least one PDU session for communicating with the packet data network 150. The remote unit 105 can establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0047] In the context of a 5G system ("5GS"), the term "PDU session" refers to a data connection that provides end-to-end ("E2E") user plane ("UP") connectivity between a remote unit 105 and a specific data network ("DN") through a UPF 141. The PDU session supports one or more quality of service ("QoS") flows. In certain embodiments, there can be a one-to-one mapping between a QoS flow and a QoS profile, such that all packets belonging to a particular QoS flow have the same 5G QoS identifier ("5QI").

[0048] In the context of a 4G / LTE system such as an Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as an EPS session) provides E2E UP connectivity between a remote unit and a PDN. A PDN connectivity procedure establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 140. In certain embodiments, there is a one-to-one mapping between an EPS bearer and a QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS Class Identifier (“QCI”).

[0049] The base units 121 can be distributed over a geographic region. In certain embodiments, the base units 121 can also be referred to as access terminals, access points, bases, base stations, Node Bs (“NBs”), Evolved Node Bs (abbreviated as eNodeBs or “eNBs,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node Bs), 5G / NR Node Bs (“gNBs”), Home NodeBs, relay nodes, RAN nodes, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, which can include one or more controllers that can be communicably coupled to one or more corresponding base units 121. These and other elements of radio access networks are not illustrated but are well known in the art. The base units 121 connect to the mobile core network 140 via the RAN 120.

[0050] The base units 121 can serve various remote units 105 within a serving area, for example, a cell or a cell sector, via wireless communication links 123. The base units 121 can directly communicate with one or more remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and / or spatial domain. Additionally, the DL communication signals can be carried on the wireless communication links 123. The wireless communication links 123 can be any suitable carrier in a licensed or unlicensed radio frequency spectrum. The wireless communication links 123 facilitate communication between one or more remote units 105 and / or one or more base units 121. Note that during NR operation on unlicensed spectrum (referred to as “NR-U”), the base units 121 and remote units 105 communicate over unlicensed (i.e., shared) radio frequency spectrum.

[0051] In one embodiment, the mobile core network 140 is a 5GC or an evolved packet core (“EPC”), which can be coupled to a packet data network 150, like the Internet and private data networks, as well as other data networks. The remote units 105 can have subscriptions or other accounts with the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0052] 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 number of control plane (“CP”) functions, including but not limited to an access and mobility management function (“AMF”) 143, a session management function (“SMF”) 145, a policy control function (“PCF”) 147, a unified data management function (“UDM”), and a user data repository (“UDR”), which serve the RAN 120. While specific numbers and types of network functions are depicted in Figure 1 A person of skill in the art would readily recognize that any number and type of network functions can be included in the mobile core network 140.

[0053] In the 5G architecture, the UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interworking with data networks (DN). The AMF 143 is responsible for termination of NAS signaling, NAS ciphering and integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 145 is responsible for session management (i.e., session establishment, modification, release) of the UPF 141, remote unit (i.e., UE) IP address allocation and management, DL data notification, and traffic steering configuration for proper traffic routing.

[0054] The PCF 147 is responsible for a unified policy framework, providing policy rules to CP functions, and accessing subscription information in the UDR for policy decisions. The UDM is responsible for generating authentication and key agreement (“AKA”) credentials, user identification handling, access authorization, and subscription management. The UDR is a repository of subscriber information and can be used to serve multiple network functions. For example, the UDR can store subscription data, policy-related data, subscriber-related data that is allowed to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as the combined entity “UDM / UDR” 149.

[0055] In various embodiments, the mobile core network 140 may also include a network repository function (“NRF”) (which provides network function (NF) service registration and discovery, enabling NFs to identify appropriate services among themselves and communicate with each other via an application programming interface (“API”), a network exposure function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners), an authentication server function (“AUSF”), or other NFs defined for the 5GC. When present, the AUSF can be used as an authentication server and / or authentication proxy, thereby allowing AMF 143 to authenticate remote unit 105. In some embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0056] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband ("eMBB") service. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication ("URLLC") service. In other examples, network slices may be optimized for machine-type communication ("MTC") service, massive MTC ("mMTC") service, and Internet of Things ("IoT") service. In still other examples, network slices may be deployed for specific application services, vertical services, specific use cases, etc.

[0057] Network slice instances can be identified by individual network slice selection aid information (“S-NSSAI”), while the set of network slices authorized for use by remote unit 105 is identified by network slice selection aid information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In some embodiments, various network slices may include separate instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For illustration purposes, Figure 1 Different network slices are not shown, but their support is assumed. In various embodiments, a first set of network slices may be optimized for a first carrier frequency, while a second set of network slices may be optimized for a second carrier frequency. As discussed in more detail below, RAN 120 sends one or more control signal configurations 125 to remote unit 105 (i.e., via base station unit 121) such that remote unit 105 uses a specific waveform type to receive control signal transmissions from RAN 120.

[0058] Although Figure 1 Embodiments described to associate control signaling configuration with waveform type are applied to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular network), General Packet Radio Service (“GPRS”), Universal Mobile Telecommunication System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, etc., are depicted.

[0059] Furthermore, in an LTE variant where the mobile core network 140 is an EPC, the described network functions can be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), etc. For example, the AMF 143 can be mapped to a MME, the SMF 145 can be mapped to a control plane part of a PGW and / or a MME, the UPF 141 can be mapped to a SGW and a user plane part of a PGW, the UDM / UDR 149 can be mapped to a HSS, etc.

[0060] In the following description, the term “RAN node” is used for a base station, but it can be replaced with any other radio access node, e.g., gNB, eNB, base station (“BS”), access point (“AP”), etc. Moreover, the operations are described mainly in the context of 5G NR. However, the proposed solutions / methods are equally applicable to other mobile communication systems supporting association of control signaling configuration with waveform type.

[0061] According to a first solution of the disclosure, multiple waveforms are associated with multiple CORESETs within a slot. According to a second solution of the disclosure, there is a waveform association between a PDCCH and a corresponding scheduled and / or activated transmission when a UE receives a scheduling grant on the PDCCH. According to a third solution of the disclosure, a UE is configured with a waveform switching pattern of repetitions, retransmissions, and / or multiple transmission occasions of a physical channel. According to a fourth solution of the disclosure, multiple waveforms are associated with different BWP indices.

[0062] Figure 2 A NR protocol stack 200 according to embodiments of the disclosure is depicted. Although Figure 2The UE 205, RAN node 210, and AMF 215 in a 5G Core Network (“5GC”) are shown, but these represent a set of remote units 105 that interact with base unit 121 and mobile core network 140. As depicted, the protocol stack 200 includes a user plane protocol stack 201 and a control plane protocol stack 203. The user plane protocol stack 201 includes a physical (“PHY”) layer 220, a medium access control (“MAC”) sublayer 225, a radio link control (“RLC”) sublayer 230, a packet data convergence protocol (“PDCP”) sublayer 235, and a service data adaptation protocol (“SDAP”) layer 240. The control plane protocol stack 203 includes the physical layer 220, the MAC sublayer 225, the RLC sublayer 230, and the PDCP sublayer 235. The control plane protocol stack 203 also includes a radio resource control (“RRC”) layer 245 and a non-access stratum (“NAS”) layer 250.

[0063] The AS layers for the user plane protocol stack 201 (also referred to as the “AS protocol stack”) are made up of at least the SDAP, PDCP, RLC, and MAC sublayers, and the physical layer. The AS layers for the control plane protocol stack 203 are made up of at least the RRC, PDCP, RLC, and MAC sublayers, and the physical layer. Layer 2 (“L2”) is split into the SDAP, PDCP, RLC, and MAC sublayers. Layer 3 (“L3”) includes the RRC sublayer 245 for the control plane and the NAS layer 250 and includes, for example, an Internet Protocol (“IP”) layer and / or a PDU layer (not depicted) for the user plane. L1 and L2 are referred to as “lower layers,” while L3 and above layers (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”

[0064] The physical layer 220 provides transport channels to the MAC sublayer 225. As described herein, the physical layer 220 can perform clear channel assessment and / or listen-before-talk (“CCA / LBT”) procedures using an energy detection threshold. In certain embodiments, the physical layer 220 can send a notification of a UL listen-before-talk (“LBT”) failure to a MAC entity at the MAC sublayer 225. The MAC sublayer 225 provides logical channels to the RLC sublayer 230. The RLC sublayer 230 provides RLC channels to the PDCP sublayer 235. The PDCP sublayer 235 provides radio bearers to the SDAP sublayer 240 and / or the RRC layer 245. The SDAP sublayer 240 provides QoS flows to a core network (e.g., 5GC). The RRC layer 245 provides addition, modification, and release of carrier aggregation and / or dual connectivity. The RRC layer 245 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRBs”) and data radio bearers (“DRBs”).

[0065] The NAS layer 250 is between the UE 205 and the 5GC 215. NAS messages are passed transparently through the RAN. The NAS layer 250 is used to manage the establishment of communication sessions and to maintain continuous communication with the UE 205 as the UE 205 moves between different cells of the RAN. In contrast, the AS layer is between the UE 205 and the RAN (i.e., the RAN node 210) and carries information through the wireless portion of the network.

[0066] In NR Release 15, multiple waveforms are supported. Specifically, uplink (“UL”) supports both CP-OFDM and DFT-s-OFDM. However, the configuration is only semi-static to select one of them, e.g., by enabling (alternatively, disabling) the parameter “transformPrecoding”. For example, the RAN node 210 can switch between multi-carrier CP-OFDM and single-carrier DFT-s-OFDM via RRC configuration. The higher layer parameter transformPrecoder in Pusch-Config / configuredGrantConfig or msg3-transformPrecoding in RACH-ConfigCommon provides an indication to enable or disable transform precoder (DFT-s-OFDM) for PUSCH. The UE 205 considers transform precoding either “enabled” or “disabled” based on reading these messages, and the RAN node 210 applies simultaneous reception of multiple UEs 205 with different waveforms.

[0067] Fundamentally, CP-OFDM suffers from high PAPR issues, and the issues become more apparent with higher frequency ranges. In Rel-17, the NR frequency range has been extended from 52.6-71 GHz, however, the waveform for DL and UL has not changed, only high subcarrier spacing (“SCS”) is employed to cope with the phase noise issue. However, future releases can support new waveform types, or even further extension of NR operation, e.g., 71-114.25 GHz.

[0068] Given that support for new waveforms is added while also supporting current (i.e., Rel-15, Rel-16, and Rel-17) waveforms, issues with multiple waveform indication / switching / waveform become relevant. Depending on the modulation order of different channels, coverage requirements, and other potential factors, multiplexing / transmission / repetition of control and / or data allowing use of multiple waveforms can be meaningful.

[0069] For multiple PDCCH transmissions / receptions for PDSCH scheduling, if a UE 205 is configured by higher layer parameter PDCCH-Config containing two different values of parameter CORESETPoolIndex in control resource set information element (“IE”), the UE 205 can expect to receive multiple PDCCHs scheduling fully / partially / non-overlapping PDSCHs in time and frequency domains.

[0070] The UE can expect to receive PDSCHs that are fully / partially overlapping in time only when PDCCHs scheduling two PDSCHs are associated to different CORESETs with different values of CORESETPoolIndex. For control resource sets without CORESETPoolIndex, the UE can assume that the control resource set is assigned with CORESETPoolIndex of 0. When the UE is scheduled with fully / partially / non-overlapping PDSCHs in time and frequency domains, the full scheduling information for receiving PDSCHs is only indicated and carried by the corresponding PDCCHs, the UE expects to be scheduled with the same active BWP and the same subcarrier spacing (“SCS”). When the UE is scheduled with fully / partially overlapping PDSCHs in time and frequency domains, the UE can be scheduled with at most two codewords simultaneously. When PDCCHs scheduling two PDSCHs are associated to different CORESETs with different values of CORESETPoolIndex, the following operations are allowed to be performed:

[0071] A) For any two hybrid automatic repeat request (“HARQ”) process IDs in a given scheduling cell, if the UE is scheduled to receive a first PDSCH starting at symbol j by a PDCCH associated with a value of CORESETPoolIndex ending at symbol i, the UE can be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH associated with a different value of CORESETPoolIndex later than the end of symbol i.

[0072] B) In a given scheduling cell, the UE can receive a first PDSCH in slot i, the corresponding HARQ acknowledgement ("HARQ-ACK") is assigned to be transmitted in slot j, and a second PDSCH starting after the first PDSCH associated with a value of CORESETPoolIndex different from the first PDSCH, the corresponding HARQ-ACK of which is assigned to be transmitted in a slot prior to slot j. As used herein, "HARQ-ACK" can collectively represent positive acknowledgement ("ACK") and negative acknowledgement ("NACK") as well as discontinuous transmission ("DTX"). ACK means correct reception of a transport block ("TB"), while NACK (or NAK) means incorrect reception of a TB (i.e., packet), and DTX means no detection of a TB.

[0073] If the PDCCH scheduling the corresponding PDSCH is associated with the same or different CORESET with CORESETPoolIndex of the same value, the UE's procedure to receive the PDSCH upon detection of the PDCCH follows subclause 5.1.

[0074] Basically, the UE can expect to receive multiple PDCCHs only if multiple values of CORESETPoolIndex are configured in the control resource set.

[0075] When the UE is configured by the higher layer parameter RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", "TDMSchemeA", if the UE is indicated with two transmission configuration indicator ("TCI") states in the codepoints of demodulation reference signal ("DM-RS") ports within one code division multiplexing ("CDM") group in the DCI fields "transmission configuration indication" and "antenna ports", then

[0076] • When two TCI states are indicated in the DCI and the UE is set to "FDMSchemeA", the UE shall receive a single PDSCH transmission occasion of the TB, each TCI state associated with a non-overlapping frequency domain resource allocation as described in subclause 5.1.2.3 of 3GPP TS 38.214. Here, "FDM" means frequency division multiplexing.

[0077] • When two TCI states are indicated in the DCI and the UE is set to "FDMSchemeB", the UE shall receive two PDSCH transmission occasions of the same TB, each TCI state associated with a PDSCH transmission occasion with a frequency domain resource allocation that is non-overlapping with respect to the other PDSCH transmission occasion as described in subclause 5.1.2.3 of 3GPP TS 38.214. Here, "FDM" means frequency division multiplexing.

[0078] • When two TCI states are indicated in the DCI and the UE is set to "TDMSchemeA", the UE shall receive two PDSCH transmission occasions for the same TB, each TCI state is associated with a PDSCH transmission occasion, the PDSCH transmission occasions have non-overlapping time domain resource allocation with respect to the other PDSCH transmission occasion, and the two PDSCH transmission occasions shall be received within a given slot, as described in subclause 5.1.2.1 of 3GPP TS 38.214. Here, "TDM" refers to time division multiplexing.

[0079] When the UE is configured by the higher layer parameter PDSCH-config indicating at least one entry in the pdsch-TimeDomainResourceAllocationList containing PDSCH-TimeDomainResourceAllocation with RepNumR16, the UE can expect to be indicated with one or both TCI states in the codepoint of the DCI field "Antenna ports" with one or both of the DCI field "Time domain resource allocation" indicating an entry in the pdsch-TimeDomainAllocationList containing PDSCH-TimeDomainResourceAllocation with RepNumR16 and the DCI field "Transmission configuration indication".

[0080] • When two TCI states are indicated in the DCI with the "Transmission configuration indication" field, the UE can expect to receive multiple slot-level PDSCH transmission occasions for the same TB with the two TCI states used across the multiple PDSCH transmission occasions, as defined in subclause 5.1.2.1 of 3GPP TS 38.214.

[0081] • When one TCI state is indicated in the DCI with the "Transmission configuration indication" field, the UE can expect to receive multiple slot-level PDSCH transmission occasions for the same TB with the one TCI state used across the multiple PDSCH transmission occasions, as defined in subclause 5.1.2.1 of 3GPP TS 38.214.

[0082] When the UE is not indicated with DCI indication of the entry containing RepNumR16 in PDSCH-TimeDomainResourceAllocation in pdsch-TimeDomainAllocationList with DCI field "Time domain resource assignment", and it is indicated with two TCI states in the codepoint of the two CDM groups within the DCI field "Transmission configuration indication" and in the DM-RS ports of the DCI field "Antenna ports", the UE can expect to receive a single PDSCH with the association between DM-RS ports and TCI states as defined in subclause 5.1.6.2.

[0083] When the UE is not indicated with DCI indication of the DCI field "Time domain resource assignment" indicating the entry containing RepNumR16 in PDSCH-TimeDomainResourceAllocation in pdsch-TimeDomainAllocationList, and it is indicated with one TCI state in the codepoint of the DCI field "Transmission configuration indication", the UE procedure to receive PDSCH upon detecting PDCCH follows subclause 5.1.

[0084] For multiple PDCCH transmissions / receptions for PUSCH scheduling, if the UE is configured by higher layer parameter PDCCH-Config containing two different values of CORESETPoolIndex for the active BWP of a serving cell, and the PDCCH scheduling two non-overlapping PUSCH in time domain is associated with different CORESETs with different values of CORESETPoolIndex, for any two HARQ process IDs in a given scheduling cell, if the UE is scheduled to start a first PUSCH transmission starting at symbol j by a PDCCH associated with a value of CORESETPoolIndex ending at symbol i, the UE can be scheduled to transmit a PUSCH starting earlier than the first PUSCH ending by a PDCCH associated with a different value of CORESETPoolIndex ending later than symbol i.

[0085] Various solutions have been proposed to enhance system performance of DL and UL at high frequencies. However, such proposals do not address the problems or provide the benefits of apparatuses, methods, and systems for multiple waveform indication and / or switching as described in the present disclosure.

[0086] For DL with multiple waveforms, the RAN node 210 can select a waveform (possibly including subcarrier spacing) based on some parameters, such as the used carrier frequency, UE measurements (reference signal received power (“RSRP”), reference signal received quality (“RSRQ”), and / or signal-to-interference-and-noise ratio (“SINR”)), UE location, UE 205 and RAN node 210 RF capabilities, UE power status (e.g., power headroom (“PH”) reporting), UE assistance information (e.g., DL transform precoding suggestion based on path loss (“PL”) estimation), indication of UE battery power status, and / or the like. These factors can influence the dynamic requirements of the optimal waveform. For example, UE battery level can help the RAN node 210 select the right waveform, as some waveforms require higher signal processing reception complexity than others, and thus save some UE power in a critical battery power status.

[0087] According to embodiments of the disclosure, a UE can be configured with separate waveforms and / or indicated by separate waveforms to receive for at least one PDCCH CORESET (or for at least one search space configuration associated with a PDCCH CORESET) within a slot, where each CORESET can be associated with the same or different beams and / or the same or different transmission and reception points (“TRPs”).

[0088] According to embodiments of the disclosure, a UE can associate a default waveform for PDSCH and / or PUSCH transmission based on the waveform configured for the CORESET (or search space) of the DCI scheduling / activating the bearer. The default behavior can be defined based on multiple factors, such as the used carrier frequency, UE measurements (RSRP / RSRQ / SINR) / location, and / or the like.

[0089] According to embodiments of the disclosure, a UE can implicitly / explicitly indicate a waveform switching mode in which different waveforms can be used for PDCCH, PDSCH, PUSCH, and / or PUCCH repetition / retransmission.

[0090] One of the key benefits of the proposed solution is to allow increased reliability by providing an additional degree of diversity, allowing waveform switching between different transmission occasions across the same or different beams.

[0091] According to embodiments of the first solution, the RAN node 210 (e.g., gNB) can configure each CORESET ID with a waveform type such as CP-OFDM or DFT-s-OFDM or any other multi-carrier or single-carrier waveform, where the configuration can be provided by higher layer signaling such as RRC. An example of RRC configuration suggestion for CORESET IE is in Figure 3The first solution provides a mechanism to associate different CORESETs with different waveform types.

[0092] Figure 3 is a view illustrating one embodiment of an exemplary RRC configuration of a CORESET IE 300. One approach to indicate the waveform type of a CORESET 300 is to simply introduce a parameter in the CORESET RRC config. In the depicted embodiment, the CORESET IE 300 includes a parameter “waveformType” which enumerates the waveform type for the identified CORESET.

[0093] In one example implementation of the first solution, if the UE 205 is configured with more than one value of CORESETPoolIndex-r16, the UE 205 does not expect to be configured with different waveform types for different CORESET IDs belonging to the same CORESETPoolIndex-r16. Alternatively, the UE 205 can only configure a single waveform type for all PDCCH transmissions (same or different beams) from a single TRP. One criterion here is that CORESETs (CORESETPoolIndex) associated with different TRPs can only have different waveform types. Thus, the UE 205 can configure two different CORESETs for two different TRPs, where the different CORESETs use different waveforms.

[0094] In another example implementation of the first solution, if the UE 205 is configured with the same QCL-TypeD assumption (i.e., same spatial filter / Rx beam for PDCCH reception at the UE) for multiple CORESET IDs, the UE 205 does not expect to be configured with different waveform types for those multiple CORESET IDs. Alternatively, the UE 205 can only configure a single waveform type for all PDCCH transmissions with the same QCL-Type D assumption, i.e., the PDCCH can be received using the same receiver spatial filter (Rx beam). One criterion here is that only CORESETs associated with different QCL-type D assumptions can have different waveform types.

[0095] In another example implementation of the first solution, the UE 205 is not expected to be configured with different waveform types for multiple CORESETs if these multiple CORESETs occupy or overlap at least some resources within the same time domain symbol. Alternatively, the UE 205 is not expected to switch waveform to receive multiple CORESETs within the same time domain symbol. Another criterion depends on the way the CORESET is mapped in time and frequency resources. Basically, it should be non-overlapping, ideally on different symbols.

[0096] Figure 4A A CORESET region 400 within a carrier bandwidth is depicted. A CORESET is a set of physical resources (i.e., a specific region on the NR downlink resource grid) and a set of parameters for carrying PDCCH / DCI. In contrast to LTE PDCCH regions (first 1, 2, 3, 4 OFDM symbols in a subframe) where the control region is always distributed over the entire channel bandwidth, in NR, the CORESET region is localized to a specific region in the frequency domain.

[0097] In an alternative embodiment of the first solution, the UE 205 is not configured with a waveform type indication in the CORESET IE, but as part of the search space configuration, where the waveform type is indicated for each of the DCI formats as part of the search space configuration. A search space is a region within a CORESET that a UE should monitor to detect a specific PDCCH / DCI. There are two broad categories of search spaces (SS), called CSS (Common Search Space) and USS (UE-specific Search Space). Which search space a UE has to monitor is defined by the RNTI type or RRC configuration.

[0098] Another technique to associate a CORESET with a waveform type is based on the search space configuration, rather than directly indicated in the CORESET configuration as described above. In another example, the UE 205 can be configured to receive a common search space with a different waveform compared to the user-specific search space. This would imply that different waveform types can be indicated to receive different DCIs, such as one waveform type for DL scheduling DCI and another waveform type for UL scheduling DCI.

[0099] In another alternative embodiment of the first solution, if the UE 205 is not configured with any waveform type indication for PDCCH transmission by any of the above embodiments (and example implementations), a different waveform type can be indicated as part of the initial access procedure signaling. If the UE is not configured with any waveform type indication, even as part of the initial access procedure, the UE can assume a default waveform type for receiving the PDCCH, depending on other factors such as the subcarrier spacing used for the PDCCH transmission. In another example, the UE expects to receive the rest of the CORESET in the active BWP with the same waveform as the CORESET 0. In another example, the UE expects to receive all CORESETs with the same waveform as the SSB.

[0100] In another embodiment of the first solution, the waveform for receiving the CORESET 0 can be dynamically indicated using bits in the physical broadcast channel (“PBCH”) transmission.

[0101] In another embodiment of the first solution, the UE 205 is configured with a first search space configuration associated with a first CORESET and a second search space configuration associated with a second CORESET, the first search space configuration is configured with a first waveform type, and the second search space configuration is configured with a second waveform type, wherein the first search space and the second search space do not overlap in time domain (e.g., the first search space and the second search space occupy different symbols and / or slots). In one example, the first CORESET and the second CORESET are the same.

[0102] In one example, the waveform type indication can include a waveform type for DL reception (e.g., PDSCH) and / or a waveform type for UL transmission (e.g., PUSCH). In another example, the waveform type for DL UE-specific PDSCH reception (e.g., PDSCH associated with PDCCH scrambled by cell-radio network temporary identifier (“C-RNTI”) in, for example, UE-specific search space (“USS”) or common search space (“CSS”)) can be different from the waveform type for DL group-common / system information PDSCH (e.g., PDSCH associated with PDCCH scrambled by system information-radio network temporary identifier (“SI-RNTI”) in the CSS). The waveform type for the DL group-common / system information PDSCH can be configured, or a default waveform type for receiving the DL group-common / system information PDSCH.

[0103] According to an embodiment of the second solution, when the UE 205 receives a scheduling DCI on a PDCCH CORESET (or in a search space) using a certain waveform, then the UE 205 is expected to receive the corresponding scheduled transmission also using the same waveform, unless a separate waveform indication / switch is indicated / configured additionally for receiving such transmission. It is noted that the determination of the waveform here for data / control channels is implicitly determined, e.g., based on the waveform type of the scheduling PDCCH, or an explicit indication in the DCI.

[0104] In one example implementation of the second solution, when the UE 205 is configured with a waveform type for PDCCH monitoring only on one of the CORESETs (or one of the search spaces) and receives a scheduling / activation DCI for PUSCH transmission, then the UE is expected to transmit the corresponding PUSCH using the same waveform type. In another example implementation of the second solution, when the UE 205 is configured with a waveform type for PDCCH monitoring only on one of the CORESETs (or one of the search spaces) and receives a scheduling / activation DCI for PDSCH reception, then the UE 205 is expected to receive the corresponding PDSCH using the same waveform type.

[0105] In an alternative embodiment of the second solution, when the UE 205 is configured with a certain waveform type for PDCCH monitoring on a CORESET (or on a search space) to monitor a scheduling DCI, and the UE 205 is also configured with a waveform type indication for each DCI format in the search space configuration, then the UE 205 is expected to receive the PDCCH using the waveform configured in the CORESET (or search space) configuration, and to receive the corresponding scheduled PUSCH and / or PDSCH, the UE 205 is expected to use the waveform type indicated in the search space configuration for the respective DCI format.

[0106] In one example implementation of the second solution, if there is a UE capability limitation in terms of minimum delay for switching the waveform type, then the UE 205 is not expected to update the waveform with respect to PDCCH unless the minimum delay for waveform switching is met. Thus, the UE 205 can take into account the minimum timing requirement for switching from one waveform type for PDCCH to a different waveform type for data / control channels. Similarly, the UE capability limitation is expected to be followed for multiple transmissions and / or repetitions for waveform switching for other channels including PDSCH-PDSCH, PDSCH-PUSCH, PUSCH-PDSCH, PUSCH-PUSCH, etc.

[0107] In another alternative embodiment of the second solution, the UE 205 can use a dedicated bit field (or a state in a bit field) to explicitly indicate the waveform type in the scheduling DCI, or implicitly determine depending on other parameters such as the subcarrier spacing value used for the scheduled PUSCH and / or PDSCH transmission / reception.

[0108] In another embodiment of the second solution, the UE 205 can be configured to determine the waveform type based on the precoding granularity applied to the PRB bundling of the reception / transmission of data (e.g., PDSCH or PUSCH) indicated, for example, in the scheduling DCI. For example, a first waveform type (e.g., DFT-s-OFDM) is used for a “wideband” or same precoding granularity as the scheduled bandwidth, and a second waveform type (e.g., CP-OFDM) is used for a precoding granularity of 2 or 4 physical resource blocks (“PRBs”). One PRB used herein spans 12 subcarriers, which corresponds to 180 kHz with 15 kHz SCS. In certain embodiments, the PRBs mapped over one slot (or subframe) represent the smallest time-frequency resources that can be scheduled to the UE.

[0109] According to embodiments of the third solution, when multiple transmissions and / or retransmissions and / or repetitions are scheduled / configured / activated for the UE 205, then the UE 205 can be configured / indicated to also switch the waveform type to receive / transmit different occasions of the same physical channel.

[0110] In one example implementation of the third solution, when the UE 205 is configured to transmit / receive repetitions from multiple beams / TRPs, then the UE 205 is expected to receive / transmit with different waveform types corresponding to different TRPs, where the waveform type associated with a TRP can be determined from the waveform type configuration for a given CORESETPoolIndex-r16 in the CORESET IE. An example is illustrated in Table 1, where two TRPs are transmitting 4 PDSCH repetitions associated with 2 different waveform types.

[0111] In other example implementations of the third solution, a particular pattern for the association of waveforms to transmission occasions (retransmissions / repetitions / actual repetitions) from one or more TRPs can be explicitly configured semi-statically through higher layer signaling such as RRC, or dynamically indicated in the DCI. The UE 205 uses the waveform type associated with the number of retransmissions for receiving a PDSCH TB and / or for transmitting a PUSCH TB. The retransmission pattern can be configured such that the first transmission can be associated with the least robust waveform type and the last retransmission can be associated with the most robust waveform type, e.g., 1 - CP-OFDM, 2 - DFT-s-OFDM, 3 - SC-FDE / CP-SC, etc.

[0112] In certain embodiments, the configured mode can also include a change in numerology for each retransmission, e.g., the retransmission order can be: 1 - CP-OFDM with SCS 1, 2-CP-OFDM with SCS 2, 3-DFT-s-OFDM with SCS 1, 4-DFT-s-OFDM with SCS 2, etc., where the first transmission uses a low SCS value and the SCS increases for subsequent retransmissions. In one example, the waveform type and / or subcarrier spacing can be associated with a redundancy version (“RV”) to be applied for the transmission occasion. For example, CP-OFDM and / or SCS 1 for RV0, DFT-s-OFDM and / or SCS 1 for RV3.

[0113] In additional embodiments of the third solution, when the UE 205 is configured to use a single scheduling DCI to transmit multiple PUSCH or multiple PDSCH transmissions / repetitions / retransmissions, then the UE 205 is not expected to be indicated with DM-RS antenna ports and number of layers that only support a particular waveform type. For example, the UE 205 is not expected to be configured with rank-8 transmission using 8 DM-RS antenna ports as based on current specifications, such DM-RS port indication and high rank support is only specified for CP-OFDM, not for DFT-s-OFDM. The same principle can be applied to other transmission / reception parameters such that only indications that can support configurations for different waveform types are indicated.

[0114] Table 1: Example of multiple repetitions associated with waveform type based on association with TRP

[0115] Number of repetitions K CORESETPoolIndex-r16 (TRP ID) Waveform type 0 0 CP-OFDM 1 1 DFT-s-OFDM 2 0 CP-OFDM 3 1 DFT-s-OFDM

[0116] According to embodiments of the fourth solution, if multiple BWPs are configured for the UE 205 and BWP switching is allowed, then waveform switching can be associated with BWP partial switching. In one example implementation, if a different or higher numerology (subcarrier spacing) is associated for a new BWP, then only waveform switching is done along with BWP switching. In an alternative implementation, each BWP is semi-statically configured with a particular waveform type.

[0117] In another example implementation, the UE 205 is only configured or indicated with waveform type association for different subcarrier values. Based on such configuration, the UE is expected to autonomously switch the waveform type whenever a different numerology is applied based on BWP switching or any other factor.

[0118] Figure 4BCORESET regions 450 localized with bandwidth parts (“BWPs”) 455 are depicted. As shown, the carrier bandwidth can be divided into discrete BWPs. In some embodiments, each configured BWP 455 has localized CORESET regions 450.

[0119] In various embodiments, the apparatuses, methods, and systems for multiple waveform indication and / or switching provide improvements over existing systems, for example:

[0120] • The disclosed CORESET-specific and / or DCI format-specific waveform type association allows different CORESETs (from one or more beams / TRPs) to be received using different waveforms;

[0121] • Providing association in waveform type between scheduling DCI (or received CORESET) and scheduled transmission for PDSCH, PUSCH, or PUCCH;

[0122] • Providing waveform type switching based on BWP switching in case different BWPs are configured with different subcarrier spacing; and

[0123] • Providing waveform switching indication / mechanism for multiple repetitions / retransmissions of any physical channel.

[0124] In some embodiments, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel can be hardware used to transmit and / or receive radio signals at sub-6 GHz frequencies (e.g., frequency range 1 (FR1)) or above-6 GHz frequencies (e.g., frequency range 2 (FR2)) or millimeter wave (mmWave). In some embodiments, an antenna panel can include an array of antenna elements, where each antenna element is connected to hardware such as a phase shifter that allows a control module to apply spatial parameters for transmission and / or reception of signals. The resulting radiation pattern can be referred to as a beam, which can or can not be unimodal and can allow the device to amplify signals transmitted or received from a spatial direction.

[0125] In some embodiments, an antenna panel can or can not be virtualized as an antenna port in the specification. An antenna panel can be connected to a baseband processing module through a radio frequency (“RF”) chain for each of the transmission (egress) and reception (ingress) directions. The capabilities of the device in terms of the number of antenna panels, their duplexing capabilities, their beamforming capabilities, etc. can or can not be transparent to other devices. In some embodiments, the capability information can be communicated via signaling, or in some embodiments, the capability information can be provided to the device without the need for signaling. In cases where such information is available to other devices, it can be used to send signaling or make local decisions.

[0126] In some embodiments, a device (e.g., UE node) antenna panel can be a physical or logical antenna array comprising a set of antenna elements or antenna ports that share a common or important portion of an RF chain (e.g., in-phase / quadrature (“I / Q”) modulator, analog-to-digital (“A / D”) converter, local oscillator, phase shift network). A device antenna panel or “device panel” can be a logical entity to which physical device antennas are mapped. The mapping of physical device antennas to the logical entity can be at the discretion of the device implementation. Communication (reception or transmission) on at least a subset of the antenna elements or antenna ports of the antenna panel that are active in order to radiate energy (also referred to herein as active elements) requires biasing or energizing of the RF chain, which results in current drain or power consumption in the device associated with the antenna panel (including power consumption of power amplifiers / low noise amplifiers (“LNAs”) associated with the antenna elements or antenna ports). The phrase “active in order to radiate energy” as used herein is not intended to be limited to transmission functionality and also encompasses reception functionality. Thus, an antenna element active in order to radiate energy can be coupled to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, either simultaneously or sequentially, or, in general, can be coupled to a transceiver in order to perform its intended functionality. Communication on the active elements of the antenna panel enables the generation of a radiation pattern or beam.

[0127] In some embodiments, depending on the device’s own implementation, a “device panel” can have at least one of the following functionalities as an operational role for independently controlling its Tx beams, as an operational role for independently controlling its transmission power, as an operational role for independently controlling its transmission timing, as an antenna group unit for independently controlling its Tx beams, as an antenna group unit for independently controlling its transmission power, as an antenna group unit for independently controlling its transmission timing. The “device panel” can be transparent to the RAN node. For certain conditions, the RAN node 210 can assume that the mapping between the device’s physical antennas and the logical entity “device panel” can not change. The conditions can include, for example, until the next update or report from the device or a duration of time for which the RAN node assumes the mapping will not change.

[0128] The device can report its capabilities with respect to the “device panel” to the RAN node or network. The device capabilities can include at least the number of “device panels.” In one implementation, the device can support UL transmission from one beam within a panel; in the multiple panel case, more than one beam (one beam per panel) can be used for UL transmission. In another implementation, more than one beam per panel can be supported / used for UL transmission.

[0129] In some embodiments described, an antenna port is defined such that the channel over which a symbol on the antenna port is communicated can be inferred from the channel over which another symbol on the same antenna port is communicated.

[0130] Two antenna ports are considered to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is communicated can be inferred from the channel over which a symbol on the other antenna port is communicated. Large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0131] Two antenna ports can be quasi co-located with respect to a subset of large-scale properties and different subsets of large-scale properties can be indicated by a quasi co-location (“QCL”) type. For example, a parameter qcl-Type can take one of the following values:

[0132] ‘QCL-TypeA’: {Doppler shift, Doppler spread, average delay, delay spread}

[0133] ‘QCL-TypeB’: {Doppler shift, Doppler spread}

[0134] ‘QCL-TypeC’: {Doppler shift, average delay}

[0135] ‘QCL-TypeD’: {spatial Rx parameters}.

[0136] Spatial Rx parameters can include one or more of angle of arrival (“AoA”), dominant AoA, average AoA, angular spread, power angular spectrum (“PAS”) of AoA, average angle of departure (“AoD”), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, spatial channel correlation, etc.

[0137] An “antenna port” according to embodiments can be a logical port, which can correspond to a beam (resulting from beamforming) or can correspond to a physical antenna on a device. In some embodiments, a physical antenna can be mapped directly to a single antenna port, where the antenna port corresponds to the actual physical antenna. Alternatively, a set or subset of physical antennas or an antenna set or antenna array or antenna subarray can be mapped to one or more antenna ports after applying complex weights, cyclic delays, or both to the signals on each physical antenna. The set of physical antennas can have antennas from a single module or panel or from multiple modules or panels. The weights can be fixed as in antenna virtualization schemes such as cyclic delay diversity (“CDD”). The process for deriving antenna ports from physical antennas can be specific to device implementation and transparent to other devices.

[0138] In some embodiments described, a TCI state associated with a target transmission can indicate parameters for configuring a quasi-co-location relationship between the target transmission (e.g., a target RS for DM-RS ports of the target transmission during a transmission occasion) and a source reference signal (e.g., SSB / CSI-RS / SRS) with respect to a quasi-co-location type parameter indicated in the corresponding TCI state. A device can receive a configuration of multiple transmission configuration indicator states for a serving cell for transmissions on the serving cell.

[0139] In some embodiments described, spatial relation information associated with a target transmission can indicate parameters for configuring a spatial setting between the target transmission and a reference RS (e.g., SSB / CSI-RS / SRS). For example, a device can transmit the target transmission with the same spatial domain filter / beam used for reception of the reference RS (e.g., a DL RS such as SSB / CSI-RS). In another example, a device can transmit the target transmission with the same spatial domain transmission filter / beam used for transmission of the reference RS (e.g., an UL RS such as SRS). A device can receive a configuration of multiple spatial relation information configurations for a serving cell for transmissions on the serving cell.

[0140] Figure 5 A user equipment apparatus 500 that can be used to associate control signaling configurations with waveform types according to embodiments of the present disclosure is depicted. In various embodiments, the user equipment apparatus 500 is used to implement one or more of the above described solutions. The user equipment apparatus 500 can be one embodiment of the above-described remote unit 105 and / or UE 205. Moreover, the user equipment apparatus 500 can include a processor 505, a memory 510, an input device 515, an output device 520, and a transceiver 525.

[0141] In some embodiments, the input device 515 and the output device 520 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment apparatus 500 can not include any input device 515 and / or output device 520. In various embodiments, the user equipment apparatus 500 can include one or more of: the processor 505, the memory 510, and the transceiver 525, and can not include the input device 515 and / or the output device 520.

[0142] As depicted, the transceiver 525 includes at least one transmitter 530 and at least one receiver 535. In some embodiments, the transceiver 525 communicates with one or more cells (or wireless coverage areas) supported by one or more base station units 121. In various embodiments, the transceiver 525 can operate on unlicensed spectrum. Additionally, the transceiver 525 can include multiple UE panels supporting one or more beams. Additionally, the transceiver 525 can support at least one network interface 540 and / or application interface 545. The application interface 545 can support one or more APIs. The network interface 540 can support 3GPP reference points such as Uu, N1, PC5, and the like. Other network interfaces 540 can be supported as appreciated by one of ordinary skill in the art.

[0143] In one embodiment, the processor 505 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 505 can be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 505 executes instructions stored in the memory 510 to perform methods and routines described herein. The processor 505 is communicatively coupled to the memory 510, the input device 515, the output device 520, and the transceiver 525.

[0144] In various embodiments, the processor 505 controls the user equipment apparatus 500 to implement the UE behaviors described above. In certain embodiments, the processor 505 can include an application processor (also known as “main processor”) that manages application domains and operating system (“OS”) functions, and a baseband processor (also known as “baseband radio processor”) that manages radio functions.

[0145] In various embodiments, the processor 505 receives, via the transceiver 525, a configuration for control signaling. The processor 505 associates the control signaling configuration with a waveform type, where at least two different waveform types are associated with different control signaling configurations. The transceiver 525 receives a control signal transmission from a radio access network using the associated waveform type.

[0146] In some embodiments, receiving a configuration for control signaling includes receiving a plurality of configurations for a plurality of control resource sets ("CORESETs"), each configuration associating a configured CORESET with a waveform type, where at least two different waveform types are associated with the plurality of configured CORESETs. In certain embodiments, the processor 505 further associates a CORESET configuration and its associated waveform type with a receive beam, a transmit-receive point ("TRP"), or some combination thereof. In further embodiments, CORESET transmissions belonging to different TRPs are associated with different waveform types, where PDCCH transmissions from the same TRP are associated with the same waveform type.

[0147] In certain embodiments, the processor 505 further receives a quasi co-located location ("QCL") Type-D assumption (i.e., receiver spatial filter / beam) for a plurality of CORESETs. In such embodiments, CORESET identifiers with different QCL Type-D assumptions (i.e., different receiver spatial filters / beams) are associated with different waveform types, while PDCCH transmissions with the same QCL Type-D assumption (i.e., the same receiver spatial filter / beam) are associated with the same waveform type. In certain embodiments, CORESET transmissions that overlap in time domain are associated with the same waveform type.

[0148] In some embodiments, receiving a configuration for control signaling includes receiving at least one search space configuration, each search space configuration for monitoring at least one downlink control information ("DCI") format, where different DCI formats are associated with different waveform types. In some embodiments, receiving a control signal transmission includes receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space) using a particular waveform type. In such embodiments, the particular waveform type is also used to receive a downlink transmission scheduled by the DCI or to transmit an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the DCI contains an indication (e.g., a flag, a parameter, or other explicit indication) that the downlink transmission scheduled by the DCI or the uplink transmission scheduled / activated by the DCI is using the same particular waveform type used to receive the DCI.

[0149] In some embodiments, receiving the control signal transmission includes receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space) including a waveform type indication. In such embodiments, the indicated waveform type is used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the scheduling DCI is received using a first waveform type and the waveform indication indicates a second waveform type. In such embodiments, the UE does not switch the waveform when a delay requirement is not satisfied between a reception time of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

[0150] In some embodiments, receiving the control signal transmission includes receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space), where a first waveform type is used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI, the first waveform type being associated with a precoding granularity size of a precoding resource block group.

[0151] In some embodiments, receiving the control signal transmission includes receiving a single scheduling DCI (e.g., on a PDCCH CORESET or search space) scheduling multiple transmission occasions. In such embodiments, the processor 505 further switches a waveform type for different transmission occasions of the multiple transmission occasions. In certain embodiments, the multiple transmission occasions have a property of a same physical channel. In one embodiment, the physical channel is a PDSCH. In another embodiment, the physical channel is a PUSCH.

[0152] In certain embodiments, the multiple transmission occasions are for different Trps, where transmission occasions belonging to different TRPs are associated with different waveform types. In certain embodiments, the processor 505 further receives a waveform switching pattern for retransmitting a TB during the multiple transmission occasions.

[0153] In some embodiments, the processor 505 further receives a configuration for multiple BWPs. In such embodiments, receiving the control signal transmission includes receiving an indication to switch from a current active bandwidth part to a new active bandwidth part, where the processor 505 further switches a waveform type when switching the bandwidth part. In certain embodiments, each bandwidth part is associated with a waveform type. In certain embodiments, different waveform types are configured for different subcarrier spacing values. In such embodiments, switching the bandwidth part includes switching to a different subcarrier value.

[0154] In one embodiment, the storage 510 is a computer readable storage medium. In some embodiments, the storage 510 includes both volatile and nonvolatile computer storage media. For example, the storage 510 can include both a RAM and a Flash memory.

[0155] In some embodiments, the storage 510 stores data relating to associating control signaling configurations with waveform types. For example, the storage 510 can store various parameters, panel / beam configurations, resource assignments, policies, and the like as described above. In certain embodiments, the storage 510 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 500.

[0156] In one embodiment, the input device 515 can include any known computer input device including a touch panel, a button, a keyboard, a pen, a microphone, or the like. In some embodiments, the input device 515 can be integrated with the output device 520, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device 515 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 515 includes two or more different devices, such as a keyboard and a touch panel.

[0157] In one embodiment, the output device 520 is designed to output visual, audible, and / or tactile signals. In some embodiments, the output device 520 includes an electronically controlled display or display device capable of outputting visual data to a user. For example, the output device 520 can include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic LED (“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 520 can include a wearable display separate from, but communicatively coupled to, the remainder of the user equipment apparatus 500, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 520 can be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0158] In certain embodiments, output device 520 includes one or more speakers for producing sound. For example, output device 520 can produce an audible alert or notification (e.g., a beep or chime). In some embodiments, output device 520 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of output device 520 can be integrated with input device 515. For example, input device 515 and output device 520 can form a touchscreen or similar touch-sensitive display. In other embodiments, output device 520 can be located proximate to input device 515.

[0159] Transceiver 525 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 525 operates under the control of processor 505 to transmit and to also receive messages, data, and other signals. For example, processor 505 can selectively activate transceiver 525 (or portions thereof) at particular times in order to send and to receive messages.

[0160] Transceiver 525 includes at least transmitter 530 and at least one receiver 535. One or more transmitters 530 can be used to provide UL communication signals to base units 121, such as the UL transmissions described herein. Similarly, one or more receivers 535 can be used to receive DL communication signals from base units 121, as described herein. Although only one transmitter 530 and one receiver 535 are illustrated, user equipment apparatus 500 can have any suitable number of transmitters 530 and receivers 535. Further, transmitter 530 and receiver 535 can be any suitable type of transmitters and receivers. In one embodiment, transceiver 525 includes a first transmitter / receiver pair for communicating with a mobile communication network over licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network over unlicensed radio spectrum.

[0161] In certain embodiments, the first transmitter / receiver pair for communicating with a mobile communication network over licensed radio spectrum and the second transmitter / receiver pair for communicating with a mobile communication network over unlicensed radio spectrum can be combined into a single transceiver unit, e.g., a single chip that performs functions for both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, certain transceivers 525, transmitters 530, and receivers 535 can be implemented as physically separate components that access shared hardware resources and / or software resources, such as, for example, network interface 540.

[0162] In various embodiments, one or more transmitters 530 and / or one or more receivers 535 can be implemented and / or integrated into a single hardware component, such as a multi- transceiver chip, a system-on-a-chip, an application-specific integrated circuit (“ASIC”), or other type of hardware component. In certain embodiments, one or more transmitters 530 and / or one or more receivers 535 can be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as network interface 540 or other hardware components / circuits, can be integrated with any number of transmitters 530 and / or receivers 535 into a single chip. In such embodiments, the transmitters 530 and receivers 535 can be logically configured as a transceiver 525 that uses one or more common control signals or as modular transmitters 530 and receivers 535 implemented in the same hardware chip or multi-chip module.

[0163] Figure 6 A network apparatus 600 that can be used in performing associating control signaling configuration with waveform type is depicted in accordance with embodiments of the present disclosure. In one embodiment, the network apparatus 600 can be one implementation of a RAN node, such as the base station unit 121 or RAN node 210 as discussed above. Furthermore, the base station network apparatus 600 can include a processor 605, memory 610, input device 615, output device 620, and transceiver 625.

[0164] In some embodiments, the input device 615 and the output device 620 are combined into a single device, such as a touch screen. In certain embodiments, the network apparatus 600 can not include any input device 615 and / or output device 620. In various embodiments, the network apparatus 600 can include one or more of the processor 605, the memory 610, and the transceiver 625, and can not include the input device 615 and / or the output device 620.

[0165] As depicted, the transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, the transceiver 625 communicates with one or more remote units. Additionally, the transceiver 625 can support at least one network interface 640 and / or application interface 645. The application interface 645 can support one or more APIs. The network interface 640 can support 3GPP reference points, such as Uu, Nl, N2, and N3. Other network interfaces 640 can be supported, as appreciated by one of ordinary skill in the art.

[0166] In one embodiment, the processor 605 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 605 can be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processor, a FPGA, or similar programmable controller. In some embodiments, the processor 605 executes instructions stored in the memory 610 to perform methods and routines described herein. The processor 605 is communicatively coupled to the memory 610, the input device 615, the output device 620, and the transceiver 625.

[0167] In various embodiments, the network apparatus 600 is a RAN node (e.g., gNB) in communication with one or more UEs, as described herein. In such embodiments, the processor 605 controls the network apparatus 600 to perform the RAN behaviors described above. When operating as a RAN node, the processor 605 can include an application processor (also known as “main processor”) that manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) that manages radio functions.

[0168] In various embodiments, the processor 605 configures the UE with a set of control signaling configurations, where at least two different waveform types are associated with different control signaling configurations. The transceiver transmits control signal transmissions using the associated waveform types.

[0169] In some embodiments, the set of control signaling configurations includes a plurality of configurations for a plurality of CORESETs, each configuration associating a configured CORESET with a waveform type, where at least two different waveform types are associated with the plurality of configured CORESETs. In certain embodiments, the CORESET configuration further associates the waveform type with a receive beam, a TRP, or some combination thereof.

[0170] In certain embodiments, CORESET transmissions belonging to different TRPs are associated with different waveform types, where PDCCH transmissions from the same TRP are associated with the same waveform type. In certain embodiments, CORESET transmissions that overlap in time are associated with the same waveform type.

[0171] In certain embodiments, the processor further transmits QCL type-D assumptions (i.e., receiver spatial filters / beams) for a plurality of CORESETs. In such embodiments, CORESET identifiers with different QCL Type-D assumptions (i.e., different receiver spatial filters / beams) are associated with different waveform types, where PDCCH transmissions with the same QCL Type-D assumption (i.e., the same receiver spatial filter / beam) are associated with the same waveform type.

[0172] In some embodiments, transmitting the configuration for control signaling includes transmitting at least one search space configuration, each search space configuration for monitoring at least one DCI format. In such embodiments, different DCI formats are associated with different waveform types.

[0173] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space) using a particular waveform type, where the particular waveform type is also used to transmit a downlink transmission scheduled by the DCI or to receive an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the DCI contains an indication (e.g., a flag, a parameter, or other explicit indication) that the downlink transmission scheduled by the DCI or the uplink transmission scheduled / activated by the DCI is to use the same particular waveform type used to transmit the DCI.

[0174] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space) containing a waveform type indication, where the indicated waveform type is used to transmit a downlink transmission scheduled by the DCI or to receive an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the scheduling DCI is transmitted using a first waveform type and the waveform indication indicates a second waveform type. In such embodiments, the UE does not switch the waveform when a delay requirement is not satisfied between a time of reception of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

[0175] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space), where a first waveform type is used to transmit a downlink transmission scheduled by the DCI or to receive an uplink transmission scheduled by the DCI, the first waveform type being associated with a precoding granularity size of a precoding resource block group.

[0176] In some embodiments, transmitting the control signal transmission includes transmitting a single scheduling DCI (e.g., on a PDCCH CORESET or search space) that schedules multiple transmission occasions. In such embodiments, the processor further switches a waveform type used for different transmission occasions of the multiple transmission occasions. In certain embodiments, the multiple transmission occasions have a nature of a same physical channel. In one embodiment, the physical channel includes a PDSCH. In another embodiment, the physical channel includes a PUSCH.

[0177] In certain embodiments, the multiple transmission occasions are for different TRPs, where the transmission occasions belonging to different TRPs are associated with different waveform types. In certain embodiments, the processor further transmits a waveform switching pattern to the UE for retransmitting the TB during the multiple transmission occasions.

[0178] In some embodiments, the processor further configures the UE for multiple BWPs. In such embodiments, transmitting the control signal transmission includes transmitting an indication to switch from a current active bandwidth part to a new active bandwidth part, where the processor further switches the waveform type when switching the bandwidth part.

[0179] In certain embodiments, each bandwidth part is associated with a waveform type. In certain embodiments, different waveform types are configured for different subcarrier spacing values, where switching the bandwidth part includes switching to a different subcarrier value.

[0180] In one embodiment, the memory 610 is a computer readable storage medium. In some embodiments, the memory 610 includes both volatile and nonvolatile computer storage media. For example, the memory 610 can include both a RAM and a flash memory. In some embodiments, the memory 610 includes only volatile computer storage media.

[0181] In some embodiments, the memory 610 stores data relating to associating control signaling configurations with waveform types. For example, the memory 610 can store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory 610 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 600.

[0182] In one embodiment, the input device 615 can include any known computer input device including a touch panel, a button, a keyboard, a pen, a microphone, or the like. In some embodiments, the input device 615 can be integrated with the output device 620, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device 615 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 615 includes two or more different devices, such as a keyboard and a touch panel.

[0183] In one embodiment, output device 620 is designed to output visual, audible, and / or tactile signals. In some embodiments, output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 620 can include, but is not limited to, an LCD display, a 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, output device 620 can include a wearable display separate from, but communicatively coupled to, the rest of network apparatus 600, such as a smart watch, smart glasses, a heads-up display, etc. Further, output device 620 can be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0184] In certain embodiments, output device 620 includes one or more speakers for producing sound. For example, output device 620 can produce an audible alert or notification (e.g., a beep or chime). In some embodiments, output device 620 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of output device 620 can be integrated with input device 615. For example, input device 615 and output device 620 can form a touch screen or similar touch-sensitive display. In other embodiments, output device 620 can be located near input device 615.

[0185] Transceiver 625 includes at least transmitter 630 and at least one receiver 635. One or more transmitters 630 can be used to communicate with UEs, as described herein. Similarly, one or more receivers 635 can be used to communicate with network functions in a PLMN and / or RAN, as described herein. Although only one transmitter 630 and one receiver 635 are illustrated, network apparatus 600 can have any suitable number of transmitters 630 and receivers 635. Further, transmitter 630 and receiver 635 can be any suitable type of transmitters and receivers.

[0186] Figure 7 One embodiment of a method 700 for associating control signaling configurations with waveform types, in accordance with embodiments of the present disclosure, is depicted. In various embodiments, method 700 is performed by a user equipment device, such as remote units 105, UEs 205, and / or user equipment devices 500, as described above, in a mobile communication network. In some embodiments, method 700 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0187] The method 700 begins and receives a configuration for control signaling 705. The method 700 includes associating the control signaling configuration with a waveform type 710, where at least two different waveform types are associated with different control signaling configurations. The method 700 includes receiving a control signal transmission from a radio access network using the associated waveform type 715. The method 700 ends.

[0188] Figure 8 One embodiment of a method 800 for associating control signaling configurations with waveform types is depicted in accordance with embodiments of the present disclosure. In various embodiments, the method 800 is performed by a RAN device such as the base unit 121, RAN node 210, and / or network equipment apparatus 600 as described above in a mobile communication network. In some embodiments, the method 800 is performed by a processor such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0189] The method 800 begins and configures a UE with a set of control signaling configurations 805, where at least two different waveform types are associated with different control signaling configurations. The method 800 includes transmitting a control signal transmission using the associated waveform type. The method 800 ends.

[0190] In accordance with embodiments of the present disclosure, a first apparatus for associating control signaling configurations with waveform types is disclosed herein. The first apparatus can be implemented by a user equipment apparatus in a mobile communication network such as the remote units 105, UE 205, and / or user equipment apparatus 500 as described above. The first apparatus includes a transceiver and a processor that receives a configuration for control signaling. The processor associates the control signaling configuration with a waveform type, where at least two different waveform types are associated with different control signaling configurations. The transceiver receives a control signal transmission from a radio access network using the associated waveform type.

[0191] In some embodiments, receiving a configuration for control signaling includes receiving a plurality of configurations for a plurality of CORESETs, each configuration associating a configured CORESET with a waveform type, where at least two different waveform types are associated with the plurality of configured CORESETs. In certain embodiments, the processor further associates the CORESET configuration and its associated waveform type with a receive beam, a TRP, or some combination thereof. In further embodiments, CORESET transmissions belonging to different TRPs are associated with different waveform types, where PDCCH transmissions from the same TRP are associated with the same waveform type.

[0192] In certain embodiments, the processor further receives QCL type-D assumptions (i.e., receiver spatial filter / beam) for multiple CORESETs. In such embodiments, CORESET identifiers with different QCL Type-D assumptions (i.e., different receiver spatial filter / beam) are associated with different waveform types, while PDCCH transmissions with the same QCL Type-D assumption (i.e., same receiver spatial filter / beam) are associated with the same waveform type. In certain embodiments, CORESET transmissions that overlap in time are associated with the same waveform type.

[0193] In some embodiments, receiving the configuration for control signaling includes receiving at least one search space configuration, each search space configuration for monitoring at least one DCI format, where different DCI formats are associated with different waveform types. In some embodiments, receiving the control signal transmission includes receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space) using a particular waveform type. In such embodiments, the particular waveform type is also used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the DCI contains an indication (e.g., a flag, a parameter, or other explicit indication) that the downlink transmission scheduled by the DCI or the uplink transmission scheduled (or activated) by the DCI is to use the same particular waveform type used for receiving the DCI.

[0194] In some embodiments, receiving the control signal transmission includes receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space) containing a waveform type indication. In such embodiments, the indicated waveform type is used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the scheduling DCI is received using a first waveform type and the waveform indication indicates a second waveform type. In such embodiments, the UE does not switch waveforms when a delay requirement is not satisfied between a time of reception of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

[0195] In some embodiments, receiving the control signal transmission includes receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space), where a first waveform type is used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI, the first waveform type being associated with a precoding granularity size of a precoding resource block group.

[0196] In some embodiments, receiving the control signal transmission includes receiving a single scheduling DCI (e.g., on a PDCCH CORESET or search space) that schedules multiple transmission occasions. In such embodiments, the processor further switches the waveform type used for different transmission occasions of the multiple transmission occasions. In certain embodiments, the multiple transmission occasions have the nature of the same physical channel. In one embodiment, the physical channel is a PDSCH. In another embodiment, the physical channel is a PUSCH.

[0197] In certain embodiments, the multiple transmission occasions are for different TRPs, where transmission occasions belonging to different TRPs are associated with different waveform types. In certain embodiments, the processor further receives a waveform switching pattern for retransmitting the TB during the multiple transmission occasions.

[0198] In some embodiments, the processor further receives a configuration for multiple BWPs. In such embodiments, receiving the control signal transmission includes receiving an indication to switch from a current active bandwidth part to a new active bandwidth part, where the processor further switches the waveform type when switching the bandwidth part. In certain embodiments, each bandwidth part is associated with a waveform type. In certain embodiments, different waveform types are configured for different subcarrier spacing values. In such embodiments, switching the bandwidth part includes switching to a different subcarrier value.

[0199] According to embodiments of the disclosure, a first method for associating control signaling configurations with waveform types is disclosed herein. The first method can be performed by a user equipment device in a mobile communication network, such as the remote units 105, the UE 205, and / or the user equipment device 500 described above. The first method includes receiving a configuration for control signaling and associating the control signaling configuration with a waveform type, where at least two different waveform types are associated with different control signaling configurations. The first method includes receiving a control signal transmission from a radio access network using the associated waveform type.

[0200] In some embodiments, receiving the configuration for control signaling includes receiving multiple configurations for multiple CORESETs, each configuration associating a configured CORESET with a waveform type. In such embodiments, at least two different waveform types are associated with the multiple configured CORESETs. In certain embodiments, the method further associates a CORESET configuration and its associated waveform type with a receive beam, a TRP, or some combination thereof.

[0201] In certain embodiments, CORESET transmissions belonging to different TRPs are associated with different waveform types, where PDCCH transmissions from the same TRP are associated with the same waveform type. In certain embodiments, CORESET transmissions that overlap in time are associated with the same waveform type.

[0202] In certain embodiments, the first method further comprises receiving QCL type-D assumptions (i.e., receiver spatial filters / beams) for the plurality of CORESETs, where CORESET identifiers with different QCL Type-D assumptions (i.e., different receiver spatial filters / beams) are associated with different waveform types, where PDCCH transmissions with the same QCL Type-D assumptions (i.e., the same receiver spatial filters / beams) are associated with the same waveform type.

[0203] In some embodiments, receiving the configuration for control signaling comprises receiving at least one search space configuration, each search space configuration for monitoring at least one DCI format. Here, different DCI formats are associated with different waveform types.

[0204] In some embodiments, receiving the control signal transmission comprises receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space) using a particular waveform type, where the particular waveform type is also used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the DCI contains an indication (e.g., a flag, a parameter, or other explicit indication) that the downlink transmission scheduled by the DCI or the uplink transmission scheduled (or activated) by the DCI is to use the same particular waveform type used to receive the DCI.

[0205] In some embodiments, receiving the control signal transmission comprises receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space) containing a waveform type indication, where the indicated waveform type is used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the scheduling DCI is received using a first waveform type and the waveform indication indicates a second waveform type. In such embodiments, the UE does not switch waveforms when a delay requirement is not satisfied between a time of reception of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

[0206] In some embodiments, receiving the control signal transmission comprises receiving a scheduling DCI (e.g., on a PDCCH CORESET or search space), where the first waveform type is used to receive a downlink transmission scheduled by the DCI or transmit an uplink transmission scheduled by the DCI. In certain embodiments, the first waveform type is associated with a precoding granularity size of a precoding resource block group.

[0207] In some embodiments, receiving the control signal transmission comprises receiving a single scheduling DCI (e.g., on a PDCCH CORESET or search space) that schedules multiple transmission occasions. In such embodiments, the first method further comprises switching the waveform type used for different transmission occasions of the multiple transmission occasions. In certain embodiments, the multiple transmission occasions have the nature of the same physical channel. In one embodiment, the physical channel is PDSCH. In another embodiment, the physical channel is PUSCH.

[0208] In certain embodiments, the multiple transmission occasions are for different TRPs, where transmission occasions belonging to different TRPs are associated with different waveform types. In certain embodiments, the first method comprises receiving a waveform switching pattern for retransmitting the TB during the multiple transmission occasions.

[0209] In some embodiments, the first method comprises receiving a configuration for multiple BWPs. In such embodiments, receiving the control signal transmission comprises receiving an indication to switch from a current active bandwidth part to a new active bandwidth part, where the first method further comprises switching the waveform type when switching the bandwidth part.

[0210] In certain embodiments, each bandwidth part is associated with a waveform type. In certain embodiments, different waveform types are configured for different subcarrier spacing values, where switching the bandwidth part comprises switching to a different subcarrier value.

[0211] According to embodiments of the disclosure, a second apparatus for associating control signaling configurations with waveform types is disclosed herein. The second apparatus can be implemented by a RAN device in a mobile communication network, such as the base unit 121, the RAN node 210, and / or the network equipment apparatus 600 described above. The second apparatus comprises a transceiver and a processor that configures a UE with a set of control signaling configurations, where at least two different waveform types are associated with different control signaling configurations. The transceiver transmits a control signal transmission using the associated waveform type.

[0212] In some embodiments, the set of control signaling configurations includes multiple configurations for multiple CORESETs, each configuration associating a configured CORESET with a waveform type, where at least two different waveform types are associated with the multiple configured CORESETs. In certain embodiments, the CORESET configuration further associates the waveform type with a receive beam, a TRP, or some combination thereof.

[0213] In certain embodiments, CORESET transmissions belonging to different TRPs are associated with different waveform types, where PDCCH transmissions from the same TRP are associated with the same waveform type. In certain embodiments, CORESET transmissions that overlap in time are associated with the same waveform type.

[0214] In certain embodiments, the processor further transmits QCL type-D assumptions (i.e., receiver spatial filters / beams) for multiple CORESETs. In such embodiments, CORESET identifiers with different QCL Type-D assumptions (i.e., different receiver spatial filters / beams) are associated with different waveform types, where PDCCH transmissions with the same QCL Type-D assumption (i.e., the same receiver spatial filter / beam) are associated with the same waveform type.

[0215] In some embodiments, transmitting a configuration for control signaling includes transmitting at least one search space configuration, each search space configuration for monitoring at least one DCI format. In such embodiments, different DCI formats are associated with different waveform types.

[0216] In some embodiments, transmitting a control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space) using a particular waveform type, where the particular waveform type is also used to transmit a downlink transmission scheduled by the DCI or to receive an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the DCI contains an indication (e.g., a flag, a parameter, or other explicit indication) that the downlink transmission scheduled by the DCI or the uplink transmission scheduled (or activated) by the DCI is to use the same particular waveform type used to transmit the DCI.

[0217] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space) including a waveform type indication, where the indicated waveform type is used to transmit a downlink transmission scheduled by the DCI or receive an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the scheduling DCI is sent using a first waveform type and the waveform indication indicates a second waveform type. In such embodiments, the UE does not switch the waveform when a delay requirement is not satisfied between a reception time of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

[0218] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space), where a first waveform type is used to transmit a downlink transmission scheduled by the DCI or receive an uplink transmission scheduled by the DCI, the first waveform type being associated with a precoding granularity size of a precoding resource block group.

[0219] In some embodiments, transmitting the control signal transmission includes transmitting a single scheduling DCI (e.g., on a PDCCH CORESET or search space) scheduling multiple transmission occasions. In such embodiments, the processor further switches a waveform type for different transmission occasions of the multiple transmission occasions. In certain embodiments, the multiple transmission occasions have a nature of a same physical channel. In one embodiment, the physical channel includes a PDSCH. In another embodiment, the physical channel includes a PUSCH.

[0220] In certain embodiments, the multiple transmission occasions are for different TRPs, where a transmission occasion belonging to a different TRP is associated with a different waveform type. In certain embodiments, the processor further sends a waveform switching pattern to the UE for retransmitting a TB during the multiple transmission occasions.

[0221] In some embodiments, the processor further configures multiple BWPs for the UE. In such embodiments, transmitting the control signal transmission includes transmitting an indication to switch from a current active bandwidth part to a new active bandwidth part, where the processor further switches the waveform type when switching the bandwidth part.

[0222] In certain embodiments, each bandwidth part is associated with a waveform type. In certain embodiments, different waveform types are configured for different subcarrier spacing values, where switching the bandwidth part includes switching to a different subcarrier value.

[0223] According to embodiments of the present disclosure, a second method for associating control signaling configurations with waveform types is disclosed herein. The second method can be performed by a RAN device in a mobile communication network, such as the base unit 121, the RAN node 210, and / or the network equipment apparatus 600 described above. The second method includes configuring a UE with a set of control signaling configurations and transmitting control signal transmissions using an associated waveform type, where at least two different waveform types are associated with different control signaling configurations.

[0224] In some embodiments, the configuration for control signaling includes a plurality of configurations for a plurality of CORESETs, each configuration associating a configured CORESET with a waveform type, where at least two different waveform types are associated with the plurality of configured CORESETs. In certain embodiments, the CORESET configuration further associates a waveform type with a receive beam, a TRP, or some combination thereof. In certain embodiments, CORESET transmissions belonging to different TRPs are associated with different waveform types, where PDCCH transmissions from the same TRP are associated with the same waveform type.

[0225] In certain embodiments, the second method includes transmitting QCL type-D assumptions (i.e., receiver spatial filters / beams) for a plurality of CORESETs. In such embodiments, CORESET identifiers with different QCL Type-D assumptions (i.e., different receiver spatial filters / beams) are associated with different waveform types, where PDCCH transmissions with the same QCL Type-D assumption (i.e., the same receiver spatial filter / beam) are associated with the same waveform type. In certain embodiments, CORESET transmissions that overlap in time domain are associated with the same waveform type.

[0226] In some embodiments, transmitting the configuration for control signaling includes transmitting at least one search space configuration, each search space configuration for monitoring at least one DCI format, where different DCI formats are associated with different waveform types.

[0227] In some embodiments, transmitting the control signal transmissions includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space) using a particular waveform type, where the particular waveform type is also used to transmit a downlink transmission scheduled by the DCI or to receive an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the DCI contains an indication (e.g., a flag, a parameter, or other explicit indication) that the downlink transmission scheduled by the DCI or the uplink transmission scheduled (or activated) by the DCI is to use the same particular waveform type used to transmit the DCI.

[0228] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space) including a waveform type indication, where the indicated waveform type is used to transmit a downlink transmission scheduled by the DCI or receive an uplink transmission scheduled by the DCI or activated by the DCI. In certain embodiments, the scheduling DCI is sent using a first waveform type and the waveform indication indicates a second waveform type, where the UE does not switch waveforms when a delay requirement is not satisfied between a reception time of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

[0229] In some embodiments, transmitting the control signal transmission includes transmitting a scheduling DCI (e.g., on a PDCCH CORESET or search space), where a first waveform type is used to transmit a downlink transmission scheduled by the DCI or receive an uplink transmission scheduled by the DCI, the first waveform type being associated with a precoding granularity size of a precoding resource block group.

[0230] In some embodiments, transmitting the control signal transmission includes transmitting a single scheduling DCI (e.g., on a PDCCH CORESET or search space) scheduling multiple transmission occasions. In such embodiments, the second method further includes switching a waveform type for different transmission occasions of the multiple transmission occasions. In certain embodiments, the multiple transmission occasions have a property of a same physical channel. In one embodiment, the physical channel includes a PDSCH. In another embodiment, the physical channel includes a PUSCH.

[0231] In certain embodiments, the multiple transmission occasions are for different TRPs, where transmission occasions belonging to different TRPs are associated with different waveform types. In certain embodiments, the second method includes sending a waveform switching pattern for retransmitting a TB during the multiple transmission occasions.

[0232] In some embodiments, the second method includes sending a configuration for multiple BWPs. In such embodiments, transmitting the control signal transmission includes transmitting an indication to switch from a current active bandwidth part to a new active bandwidth part. In such embodiments, the second method further includes switching a waveform type when switching the bandwidth part.

[0233] In certain embodiments, each bandwidth part is associated with a waveform type. In certain embodiments, different waveform types are configured for different subcarrier spacing values, where switching the bandwidth part includes switching to a different subcarrier value.

[0234] Embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. Accordingly, the scope of the application is indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning of and equivalency of the claims are intended to be embraced within the range of the claims.

Claims

1. A method of a user equipment device ("UE"), the method comprising: receiving a configuration for control signaling; associating a control signaling configuration with a waveform type, wherein at least two different waveform types are associated with different control signaling configurations; and receiving a control signal transmission from a radio access network using the associated waveform type; wherein receiving the configuration for control signaling comprises receiving a plurality of configurations for a plurality of control resource sets (CORESETs), each configuration associating a configured CORESET with a waveform type, wherein at least two different waveform types are associated with a plurality of configured CORESETs; and the method further comprising: receiving a quasi co-location (QCL) type-D assumption for the plurality of CORESETs, wherein a CORESET identifier with a different QCL Type-D assumption is associated with a different waveform type, wherein physical downlink control channel (PDCCH) transmissions with a same QCL Type-D assumption are associated with a same waveform type.

2. The method of claim 1, further comprising associating a CORESET configuration and its associated waveform type with a receive beam, a transmit-receive point ("TRP"), or some combination thereof.

3. The method of claim 2, wherein, CORESET transmissions belonging to different TRPs are associated with different waveform types, wherein physical downlink control channel ("PDCCH") transmissions from a same TRP are associated with a same waveform type.

4. The method of claim 1, wherein, CORESET transmissions that overlap in time domain are associated with a same waveform type.

5. The method of claim 1, wherein, Receiving the configuration for control signaling comprises receiving at least one search space configuration, each search space configuration for monitoring at least one downlink control information ("DCI") format, wherein different DCI formats are associated with different waveform types.

6. The method of claim 1, wherein, Receiving the control signal transmission comprises receiving a scheduling downlink control information ("DCI") using a particular waveform type, wherein the particular waveform type is also used to receive a downlink transmission scheduled by the DCI or to transmit an uplink transmission scheduled by the DCI or activated by the DCI.

7. The method of claim 6, wherein, The DCI contains an indication that the downlink transmission scheduled by the DCI or the uplink transmission scheduled or activated by the DCI is to use the same particular waveform type used to receive the DCI.

8. The method of claim 1, wherein, Receiving the control signal transmission comprises receiving a scheduling downlink control information ("DCI") containing a waveform type indication, wherein the indicated waveform type is used to receive a downlink transmission scheduled by the DCI or to transmit an uplink transmission scheduled by the DCI or activated by the DCI.

9. The method of claim 8, wherein, The scheduling DCI is received using a first waveform type and the waveform type indication indicates a second waveform type, wherein the UE does not switch waveforms when a delay requirement is not satisfied between a time of reception of the scheduling DCI and a scheduled time of the downlink or uplink transmission scheduled by the DCI.

10. The method of claim 1, wherein, Receiving the control signal transmission comprises receiving scheduling downlink control information ("DCI"), wherein a first waveform type is used for receiving a downlink transmission scheduled by the DCI or transmitting an uplink transmission scheduled by the DCI, the first waveform type being associated with a precoding granularity size of a precoding resource block group.

11. The method of claim 1, wherein, Receiving the control signal transmission comprises receiving a single scheduling downlink control information ("DCI") scheduling multiple transmission occasions, the method further comprising switching a waveform type used for different transmission occasions of the multiple transmission occasions.

12. The method of claim 11, wherein, The multiple transmission occasions have a property of a same physical channel, wherein the physical channel comprises one of: a physical downlink shared channel ("PDSCH") and a physical uplink shared channel ("PUSCH").

13. The method of claim 11, wherein, The multiple transmission occasions are for different transmission-reception points ("TRPs"), wherein transmission occasions belonging to different TRPs are associated with different waveform types.

14. The method of claim 11, further comprising receiving a waveform switching pattern for retransmitting a transport block ("TB") during the multiple transmission occasions.

15. The method of claim 1, further comprising receiving a configuration for multiple bandwidth parts ("BWPs"), wherein receiving the control signal transmission comprises receiving an indication to switch from a current active bandwidth part to a new active bandwidth part, the method further comprising switching a waveform type when switching bandwidth parts, wherein each bandwidth part is associated with a waveform type.

16. The method of claim 15, wherein different waveform types are configured for different subcarrier spacing values, wherein switching bandwidth parts comprises switching to a different subcarrier value.

17. A user equipment ("UE") apparatus comprising: a processor that: receives a configuration for control signaling; and associates a control signaling configuration with a waveform type, wherein at least two different waveform types are associated with different control signaling configurations; and a transceiver that receives a control signal transmission from a radio access network using the associated waveform type; wherein receiving the configuration for control signaling comprises receiving a plurality of configurations for a plurality of control resource sets, CORESETs, each configuration associating a configured CORESET with a waveform type, wherein at least two different waveform types are associated with a plurality of configured CORESETs; and the transceiver further receives a quasi co-location, QCL, type-D assumption for the plurality of CORESETs, wherein a CORESET identifier with a different QCL Type-D assumption is associated with a different waveform type, wherein physical downlink control channel, PDCCH, transmissions with a same QCL Type-D assumption are associated with a same waveform type.

18. A radio access network ("RAN") apparatus comprising: a processor that configures a user equipment apparatus ("UE") with a set of control signaling configurations, wherein at least two different waveform types are associated with different control signaling configurations; and a transceiver that transmits a control signal transmission to the UE using a waveform type associated with a control signaling configuration. a transceiver that transmits control signaling transmissions using an associated waveform type; wherein configuring the UE with a set of control signaling configurations includes transmitting a plurality of configurations for a plurality of control resource sets, CORESETs, each configuration associating a configured CORESET with a waveform type, wherein at least two different waveform types are associated with a plurality of configured CORESETs; and the transceiver further transmits a quasi co-location, QCL, type-D assumption for the plurality of CORESETs, wherein CORESET identifiers with different QCL Type-D assumptions are associated with different waveform types, wherein physical downlink control channel, PDCCH, transmissions with a same QCL Type-D assumption are associated with a same waveform type.

Images