Waveform indication for PUCCH

Abstract

Aspects of the present disclosure provide techniques for waveform indication for physical uplink control channel (PUCCH) transmission. A network entity can provide to a user equipment (UE) an indication of a waveform type, such as CP-OFDM, DFT-s-OFDM, or other suitable waveform type, for a PUCCH format. The UE can then communicate the PUCCH with the network entity using the waveform type for the PUCCH format.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to pending U.S. non-provisional application No. 17 / 894,969, filed on August 24, 2022, which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more particularly to indicating a waveform to be used to transmit a Physical Uplink Control Channel (PUCCH). Background Art

[0004] In a wireless communication system, such as that specified under the standards of 5G New Radio (NR), a user equipment (UE) may be able to communicate with a network entity over an air interface. Transmission from a network entity to a UE over an air interface may be referred to as downlink (DL) transmission, and transmission from a UE to a network entity over an air interface may be referred to as uplink (UL) transmission. In a DL transmission, a network entity may send DL control information (DCI) including one or more DL control channels, such as a physical downlink control channel (PDCCH), to a UE. In addition, a network entity may send DL data services to a UE on one or more DL traffic channels, such as a physical downlink shared channel (PDSCH). In an UL transmission, a UE may send UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH), to a network entity. In addition, a UE may send UL data services to a network entity on one or more UL traffic channels, such as a physical uplink shared channel (PUSCH).

[0005] UL and / or DL ​​control information and UL and / or DL ​​data traffic may be sent on a waveform. For example, DL transmissions may utilize a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, while UL transmissions may utilize a CP-OFDM waveform or a discrete Fourier transform spread OFDM (DFT-s-OFDM) waveform. Summary of the invention

[0006] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0007] In one example, a network entity is disclosed. The network entity includes a memory and a processor coupled to the memory. The processor is configured to provide an indication of a waveform type for a first format for a physical uplink control channel (PUCCH) and to communicate the PUCCH using the waveform type for the first format.

[0008] Another example provides a method for wireless communication at a network entity. The method includes providing an indication of a waveform type for a first format of a physical uplink control channel (PUCCH), and communicating the PUCCH using the waveform type for the first format.

[0009] Another example provides a user equipment (UE) including a memory and a processor coupled to the memory. The processor is configured to receive an indication of a waveform type for a first format of a physical uplink control channel (PUCCH) and communicate the PUCCH using the waveform type for the first format.

[0010] Another example provides a method for wireless communication at a user equipment (UE). The method includes receiving an indication of a waveform type for a first format of a physical uplink control channel (PUCCH), and communicating the PUCCH using the waveform type for the first format.

[0011] These and other aspects will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, other aspects, features and examples will be apparent to those of ordinary skill in the art. Although each feature may be discussed below with respect to certain examples and drawings, all examples may include one or more of the features discussed herein. In other words, although one or more examples may be discussed as having certain features, one or more of such features may also be used according to the various examples discussed herein. Similarly, although each example may be discussed below as an example of a device, system or method, it should be understood that such examples may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system in accordance with some aspects.

[0013] Figure 2 is a diagram illustrating an example of a radio access network (RAN) in accordance with some aspects.

[0014] Figure 3 is a diagram providing a high-level illustration of one example of a configuration of a decomposed base station in accordance with some aspects.

[0015] Figure 4 is a schematic illustration of organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0016] Figure 5 is a schematic illustration of a comparison of Orthogonal Frequency Division Multiplexing (OFDM) and Single Carrier Frequency Division Multiplexing (SC-FDM) that may be implemented within a radio access network in accordance with some aspects.

[0017] Fig. 6A is a schematic illustration of a transmitter configured to transmit and / or receive using a CP-OFDM waveform according to some aspects.

[0018] Figure 6B is a schematic illustration of a transmitter configured to transmit and / or receive using a DFT-s-OFDM (eg, SC-FDM) waveform according to some aspects.

[0019] Figure 7 is a diagram illustrating an example of a physical uplink control channel (PUCCH) format in accordance with some aspects.

[0020] Fig. 8A and Figure 8B is a diagram illustrating examples of long PUCCH and short PUCCH according to some aspects.

[0021] Fig. 9 is a signaling diagram illustrating exemplary signaling for PUCCH waveform indication according to some aspects.

[0022] Fig.10 is a signaling diagram illustrating example signaling for dynamic PUCCH waveform indication according to some aspects.

[0023] Fig.11A and Fig. 11B is a diagram illustrating an example of a short PUCCH using different numbers of symbols according to some aspects.

[0024] Fig.12 is a signaling diagram illustrating example signaling for PUCCH waveform switching according to some aspects.

[0025] Fig.13 is a block diagram illustrating an example of a hardware implementation for user equipment employing a processing system in accordance with some aspects.

[0026] Fig.14 is a flow chart of an example process for PUCCH waveform indication in accordance with some aspects.

[0027] Fig.15is a block diagram illustrating an example of a hardware implementation of a network entity employing a processing system according to some aspects.

[0028] Fig.16 is a flow chart of an example process for PUCCH waveform indication in accordance with some aspects. DETAILED DESCRIPTION

[0029] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0030] Although various aspects and examples are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be generated via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementation can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical settings, the device in conjunction with the described aspects and features may also necessarily include additional components and features for the specific implementation and practice of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains (RF chains), power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in various devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or UEs), end-user devices, etc.

[0031] 5G NR provides several different types of waveforms for downlink and uplink communications. For example, DL transmissions may utilize a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, while UL transmissions may utilize a CP-OFDM waveform or a discrete Fourier transform spread OFDM (DFT-s-OFDM) waveform. In the example of uplink communications, a physical uplink control channel (PUCCH) may be used to send uplink control information from a UE to a network entity (e.g., an aggregated or decomposed base station). There are five PUCCH formats defined for 5G NR, each of which utilizes a corresponding waveform. For example, PUCCH format 2 utilizes CP-OFDM, while PUCCH formats 3 and 4 utilize DFT-s-OFDM. Here, PUCCH format 2 is a short PUCCH format using one or two symbols, while PUCCH formats 3 and 4 are long PUCCH formats using four to fourteen symbols. In addition, each of PUCCH formats 2, 3, and 4 includes more than two bits.

[0032] In the current 5G NR specification, the waveform associated with a particular PUCCH format may not change, even through semi-static configuration. However, there may be scenarios in which different waveforms may be beneficial for a particular PUCCH format. For example, the peak-to-average power ratio (PAPR) is a measure of how efficiently a power amplifier operates when transmitting a signal. For the UE, a low PAPR indicates that the power amplifier is more efficient, thus saving battery in the UE. The PAPR in an OFDM signal is higher due to the linear combination of symbols. However, the PAPR in a DFT-s-OFDM signal is lower because the symbols are first distributed (spread) with a discrete cosine transform block. Therefore, in an example where network coverage is limited, in order to save power, a DFT-s-OFDM waveform may be preferred for a particular PUCCH format (e.g., PUCCH format 2).

[0033] Various aspects of the present disclosure relate to waveform indications for PUCCH. A network entity (e.g., a converged or decomposed base station) may provide an indication of a waveform type (e.g., CP-OFDM, DFT-s-OFDM, or other suitable waveform type) for a PUCCH format. In some examples, the PUCCH format may be PUCCH format 2, and the network entity may indicate whether CP-OFDM or DFT-s-OFDM should be used to send PUCCH with PUCCH format 2. In other examples, another short PUCCH format may be defined for more than two bits with a DFT-s-OFDM waveform, and the network entity may indicate whether PUCCH format 2 (with CP-OFDM) or other short PUCCH formats (with DFT-s-OFDM) should be used to send PUCCH. In some examples, the indication of the waveform type may indicate a pulse shape and / or filter for the waveform. In this example, the waveform type may remain the same for the PUCCH format (e.g., CP-OFDM for PUCCH format 2), but the pulse shape and / or filter may change.

[0034] In some examples, a network entity may semi-statically configure a waveform for a PUCCH format via, for example, radio resource control (RRC) signaling. In other examples, a network entity may dynamically configure a waveform for a PUCCH format. For example, a network entity may configure a waveform for a PUCCH format as part of a PUCCH resource configuration. The PUCCH resource configuration may indicate, for example, a corresponding waveform for each PUCCH resource. The network entity may then dynamically indicate the PUCCH resources within, for example, downlink control information (DCI). For example, the DCI may include a PUCCH resource indicator (PRI) indicating a specific PUCCH resource for the PUCCH. Based on the PUCCH resource configuration, the PUCCH resource is associated with a specific waveform, and therefore, the PRI may dynamically indicate a waveform for the PUCCH. In some examples, a combination of the PRI and the index of the first control channel element (CCE) carrying the DCI containing the PRI may be used to determine the waveform. Dynamic indication of the waveform via DCI may be used, for example, for a PUCCH carrying hybrid automatic repeat request (HARQ) feedback information for a dynamically scheduled physical downlink shared channel (PDSCH) or for a semi-persistently scheduled PDSCH (e.g., based on an activation DCI for an SPS configuration).

[0035] In some examples, changing the waveform for a PUCCH format may result in changing the number of symbols for the PUCCH. For example, a PUCCH resource configuration may configure a corresponding number of symbols for each PUCCH resource, and dynamic indication of the waveform via the PRI may result in a number of PUCCH symbols that is different from a predefined (e.g., predefined by a 5G NR standard and / or specification) number of symbols for a particular PUCCH format. In some examples, the number of symbols for each waveform may be based on a PUCCH format configuration or rule specified in one or more 5G NR standards or specifications. In this example, the PUCCH resources indicated in the PRI may be PUCCH resources having a number of symbols equal to the configured number of symbols for the waveform and PUCCH format.

[0036] In some examples, switching from one waveform (e.g., DFT-s-OFDM) to another waveform (e.g., CP-OFDM) for a particular PUCCH format (e.g., PUCCH format 2 or other short PUCCH formats) may change the number of symbols from one symbol to two symbols or from two symbols to more than two symbols (e.g., three or more symbols). In this example, demodulation reference signal (DMRS) overhead may decrease as the number of symbols increases.

[0037] In some examples, the network entity may provide a semi-persistent command to the UE for waveform switching. For example, the semi-persistent command may change the waveform for PUCCH format 2 from CP-OFDM to DFT-s-OFDM, or may change PUCCH format 2 to a different (new) short PUCCH format with a DFT-s-OFDM waveform. In some examples, the PUCCH format configuration may indicate whether the waveform of the PUCCH format may be switched by a semi-persistent command. In some examples, the semi-persistent command may be transmitted via DCI or a medium access control (MAC) control element (MAC-CE).

[0038] In some examples, PUCCH waveform switching can be based on UE capabilities. For example, the UE capabilities for PUCCH waveform switching can be per UE, per frequency range, per frequency band, per frequency band combination, or per bandwidth portion.

[0039] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0040] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate according to a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0041] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example in which RAN 104 operates according to two standards, LTE and 5G NR, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station. In addition, one or more base stations in the base station may have a decomposed configuration.

[0042] RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[0043] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but it can be stationary. The term "mobile device" or "mobile device" refers to a wide variety of devices and technologies. A UE may include a number of hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, for example, corresponding to the "Internet of Things" (IoT).

[0044] The mobile device may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter Etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access priority over other types of information, for example, in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0045] The wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" can refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme can be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" can refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0046] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by the scheduling entity 108.

[0047] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0048] like Figure 1 , the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112, and in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, the scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network (such as the scheduling entity 108). The scheduled entity 106 may also send uplink control information 118 (including but not limited to scheduling requests or feedback information or other control information) to the scheduling entity 108.

[0049] In addition, uplink and / or downlink control information 114 and / or 118 and / or business 112 and / or 116 information may be sent on a waveform that may be time-divided into frames, subframes, time slots and / or symbols. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Within the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0050] Generally speaking, base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of wireless communication system 100. Backhaul portion 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0051] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0052] See now Figure 2 , by way of illustrative example and not limitation, a schematic illustration of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 may be similar to the ones described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0053] The geographic area covered by the RAN 200 may be divided into a number of cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station within the geographic area. Figure 2Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0054] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNodeB, etc.) because base station 218 supports a cell with a relatively small range. Cell size settings may be performed according to system design and component constraints.

[0055] It should be appreciated that RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The scheduling entity 108 illustrated in FIG. 1 is the same as or similar to that in FIG.

[0056] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0057] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and Figure 1 202. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0058] In another aspect of RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. Sidelink communications may be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UE 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 may each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UE 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.

[0059] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 212 via a D2D link (e.g., side link 227 or 237). For example, one or more UEs (e.g., UE 228) within the coverage area of ​​base station 212 may operate as relay UEs to expand the coverage of base station 212, improve transmission reliability to one or more UEs (e.g., UE 226), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.

[0060] In order to obtain a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message improves the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0061] Data decoding can be implemented in a variety of ways. In early 5G NR specifications, user data is decoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and physical broadcast channel (PBCH) are decoded based on nested sequences using polar decoding. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0062] Aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communications.

[0063] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include: a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage security contexts for both control plane functions and user plane functions in whole or in part.

[0064] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0065] In a network configured for UL-based mobility, the network may select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and send uplink pilots or reference signals in response to the derived opportunities. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signals sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0066] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0067] In various specific implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, access is generally available to any operator or device. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0068] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0069] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0070] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as a frequency that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0071] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP-OFDM). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0072] The equipment in the radio access network 200 may also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex simulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0073] The deployment of a communication system such as a 5G New Radio (NR) system may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or decomposed architecture. For example, a BS such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB (gNB), an access point (AP), a transmit receive point (TRP) or a cell, etc. may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0074] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0075] Base station type operations or network designs may take into account the aggregated nature of base station functions. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0076] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 350 via one or more radio frequency (RF) access links. In some implementations, a UE 350 may be served simultaneously by multiple RUs 340.

[0077] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0078] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0079] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, the DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0080] The lower layer functions may be implemented by one or more RUs 340. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 350. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0081] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 3G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0082] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0083] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0084] Reference Figure 3 Various aspects of the present disclosure are described using OFDM waveforms (e.g., CP-OFDM waveforms) schematically illustrated in FIG. 1 . It should be understood by those of ordinary skill in the art that various aspects of the present disclosure may be applied to SC-FDMA waveforms (e.g., DFT-s-OFDM waveforms) in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles may also be applied to SC-FDMA waveforms.

[0085] Reference now Figure 4 , illustrates an expanded view of an exemplary subframe 402 showing an OFDM resource grid. However, as will be readily apparent to one skilled in the art, the PHY transmit structure for any particular application may differ from the example described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers of a carrier in the vertical direction.

[0086] Resource grid 404 may be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 404 may be available for communication. Resource grid 404 is divided into a plurality of resource elements (REs) 406. RE (which is 1 subcarrier x 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 408, which may contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0087] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Therefore, a UE typically utilizes only a subset of a resource grid 404. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., a gNB, an eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0088] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, but this is just one possible example.

[0089] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources that are scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0090] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. Generally speaking, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 4 The structures illustrated in are merely exemplary in nature, and different slot structures may be utilized and may include one or more regions in each of the control region and the data region.

[0091] Although not in Figure 4 4, but various REs 406 within RB 408 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control channels and / or data channels within RB 408.

[0092] In some examples, time slot 410 may be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0093] In an example of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmissions, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmissions and UL transmissions. The PDCCH may also carry HARQ feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any appropriate integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0094] The base station may also allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.

[0095] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0096] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 406 to a scheduling entity to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission. In this document, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

[0097] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS. In some examples, the PDSCH may carry multiple SIBs, not limited to the SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above SIBs).

[0098] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by the initiating (transmitting) sidelink device in resources reserved by the transmitting sidelink device via the SCI on the sidelink carrier. Other information may also be sent via various REs 406 within the time slot 410. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410. Additionally, one or more reference signals may be sent within slot 410, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0099] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0100] Figure 3 The channels or carriers illustrated in the figure are not necessarily all channels or carriers that can be utilized between devices, and a person of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic channels, control channels, and feedback channels.

[0101] Figure 5 is available on a radio access network (such as Figure 2 200) as illustrated in FIG. 20A and 20B. In some examples, this illustration may represent wireless resources as they may be allocated in a CP-OFDM or SC-FDM system utilizing multiple-input multiple-output (MIMO). It should be understood that Figure 5 The concepts illustrated in may also be applied to radio access networks implementing OFDMA or SC-FDMA on downlink channels and / or uplink channels.

[0102] In a CP-OFDM system, a two-dimensional grid of resource elements (REs) can be defined by dividing the frequency resources into closely spaced narrowband frequency subcarriers and separating the time resources into a sequence of OFDM symbols of a given duration. Figure 5 In the example shown, each RE is represented by a rectangle having dimensions of one subcarrier (eg, 15 kHz bandwidth) by one OFDM symbol (eg, 1 / 15 kHz = 667 ms duration).

[0103] Therefore, each RE represents a subcarrier modulated by one OFDM data symbol for an OFDM symbol period. Each OFDM symbol can be modulated using, for example, quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64QAM or any other suitable modulation. For simplicity, only four subcarriers over two OFDM symbol periods are illustrated. However, it should be understood that any number of subcarriers and OFDM symbol periods can be utilized within a time slot or subframe. Within each OFDM symbol period, a corresponding cyclic prefix (CP) can be inserted for each subcarrier. CP operates as a guard band between OFDM symbols and is typically generated by copying a small portion of the end of an OFDM symbol to the beginning of an OFDM symbol.

[0104] By setting the spacing between subcarriers based on the symbol rate, inter-symbol interference can be reduced or eliminated. OFDM channels support high data rates by allocating data streams across multiple subcarriers in a parallel manner. However, OFDM suffers from a high peak-to-average power ratio (PAPR), which may make OFDM undesirable on the uplink, where UE (scheduled entity) transmit power efficiency and amplifier cost are important factors. In addition, OFDM may be undesirable for high-frequency band (e.g., above 52.6 GHz) networks where path loss is more severe.

[0105] In an SC-FDM system, a two-dimensional grid of resource elements (REs) can be defined by utilizing a single carrier frequency with a wider bandwidth and dividing the time resources into a sequence of SC-FDM symbols with a given duration. Figure 5 In the example shown, a 60kHz carrier is shown corresponding to four 15kHz subcarriers in an OFDM system. Furthermore, although OFDM and SC-FDM symbols have the same duration, each SC-FDM symbol contains N "subsymbols" representing the modulated data symbol. Thus, in Figure 5 In the example shown with four modulated data symbols, in an OFDM system, four modulated data symbols are sent in parallel (one modulated data symbol per subcarrier), while in an SC-FDM system, four modulated data symbols are sent serially at four times the rate, with each data symbol occupying a 5kHz×15kHz bandwidth.

[0106] By sending N data symbols serially at N times the rate, the SC-FDM bandwidth is the same as a multi-carrier OFDM system; however, the PAPR is greatly reduced. In general, as the number of subcarriers increases, the PAPR of an OFDM system approaches Gaussian noise statistics, but the SC-FDM PAPR remains essentially the same regardless of the number of subcarriers. Therefore, SC-FDM can provide benefits on the uplink by improving transmit power efficiency and reducing power amplifier costs. In addition, SC-FDM can provide benefits in high-band networks for better coverage.

[0107] Fig. 6A is based on some aspects of RAN (such as Figure 2 Schematic illustration of a transmitter 600a within the RAN 200) configured to transmit and / or receive using a CP-OFDM waveform. Figure 6B is based on some aspects of RAN (such as Figure 2 Schematic illustration of a transmitter 600b within the RAN 200 (shown in FIG. 1 ) configured to transmit and / or receive using a DFT-s-OFDM (e.g., SC-FDM) waveform. In some examples, each transmitter 600a and 600b may correspond to Figures 1 to 3 A UE or network entity as shown in any one of the above.

[0108] exist Fig. 6A In the example shown, the transmitter 600a may receive a symbol stream s, which may have a length M and is composed of complex modulation symbols generated from an original bit stream using a particular modulation scheme (e.g., QPSK, 16QAM, 64QAM, etc.). The symbol stream s may be encoded (not shown) and input to a mapping circuit 602, which is configured to map the encoded symbols onto assigned subcarriers to generate modulated subcarriers. The modulated subcarriers are then passed through an N-point inverse fast Fourier transform (IFFT) 604 for time domain conversion to generate corresponding OFDM symbols, such as Figure 5 shown.

[0109] The OFDM symbols output from the N-point IFFT 604 pass through a parallel-to-serial (P-to-S) converter 606 and a cyclic prefix (CP) insertion circuit 608, where a guard interval (e.g., a cyclic prefix) is inserted between OFDM symbols to reduce inter-symbol interference (ISI) caused by multipath propagation and generate CP-OFDM symbols. The CP-OFDM symbols are then input to a digital-to-analog converter (DAC) / radio frequency (RF) circuit 610 for analog conversion and up-converting the analog signal to RF. The RF signal can then be transmitted via an antenna 612.

[0110] exist Figure 6BIn the example shown, the transmitter 600b may receive a symbol stream s, which may have a length M and be composed of complex modulation symbols generated from an original bit stream using a particular modulation scheme (e.g., QPSK, 16QAM, 64QAM, etc.). The symbol stream s may be encoded (not shown) and input to an M-point discrete Fourier transform (DFT) 620 (corresponding to the length M of the symbol stream) that performs DFT precoding on the symbol stream s. In general, the DFT 620 constructs a discrete frequency domain representation of the complex modulation symbols to produce precoded symbols. At the output of the DFT 620, the precoded symbols are then mapped onto the assigned subcarriers by a mapping circuit 622 to produce modulated subcarriers. In some examples, the assigned subcarriers form a set of continuous tones representing a single carrier waveform. The modulated subcarriers are then passed through an N-point inverse fast Fourier transform (IFFT) 624 for time domain conversion to produce corresponding SC-FDM subsymbols, such as Figure 5 Multiple SC-FDM sub-symbols can be sent within a SC-FDM symbol, such as Figure 5 Therefore, one SC-FDM symbol carries M complex modulation symbols.

[0111] The SC-FDM sub-symbols output from the N-point IFFT 624 pass through a parallel-to-serial (P-to-S) converter 626 and a cyclic prefix (CP) insertion circuit 628, where a guard interval (e.g., a cyclic prefix) is inserted between SC-FDM symbols (e.g., SC-FDM sub-symbol blocks) to reduce inter-symbol interference (ISI) caused by multipath propagation. The SC-FDM symbols and CP are then input to a digital-to-analog converter (DAC) / radio frequency (RF) circuit 630 for analog conversion and up-converting the analog signal to RF. The RF signal may then be transmitted via an antenna 632. At Fig. 6A and Figure 6B In the example shown, transmitters 600a and 600b each include a single antenna 612 and 632, respectively. However, it should be understood that transmitters 600a and 600b may each include any number of antennas.

[0112] In 5G NR, downlink transmissions such as PDCCH and PDSCH are transmitted using a CP-OFDM waveform. For uplink transmissions, there are two waveform options: CP-OFDM or DFTs-OFDM (e.g., SC-FDM). For example, the PUCCH may be transmitted using a CP-OFDM waveform or a DFT-s-OFDM waveform based on the PUCCH format used. Each 5G NR PUCCH format may be pre-configured within, for example, 3GPP Technical Specification (TS) 36.211, Release 15, Release 16, or Release 17. Thus, each PUCCH format may be fixed based on the specification.

[0113] Figure 7 is a diagram illustrating an example of a physical uplink control channel (PUCCH) format in accordance with some aspects. Figure 7 The format shown may correspond to the PUCCH format specified in, for example, 3GPP TS 36.211 Release 15. Figure 7 A table 700 is illustrated that includes a plurality of PUCCH formats 702, a corresponding length 704 (in units of the number of OFDM symbols) for each of the PUCCH formats 702, a corresponding number of uplink control information (UCI) bits 706 for each of the PUCCH formats 702, a corresponding waveform 708 for each of the PUCCH formats 702, and a corresponding description 710 for each of the PUCCH formats 702. Figure 7 In the example shown, there are five PUCCH formats 702 (e.g., PUCCH formats 0, 1, 2, 3, and 4). PUCCH formats 0 and 2 are short formats with a length 704 of one to two OFDM symbols. PUCCH formats 1, 3, and 4 are long formats with a length 704 between four and fourteen OFDM symbols. PUCCH format 3 does not have multiplexing capability, while PUCCH format 4 has multiplexing capability (e.g., multiplexing with other UEs).

[0114] In addition, PUCCH formats 0 and 1 have a smaller payload size 706 of one or two bits (e.g., ≤ 2 UCI bits), while PUCCH formats 2, 3, and 4 have a larger payload size 706 of more than two bits (e.g., > 2 UCI bits). Each PUCCH format 702 further has a predetermined waveform 708 associated therewith. For example, PUCCH formats 0 and 1 are transmitted using a computer generated sequence (CGS) waveform, PUCCH format 2 is transmitted using a CP-OFDM waveform, and PUCCH formats 3 and 4 are transmitted using a DFT-s-OFDM waveform.

[0115] Fig. 8A and Figure 8B is a diagram illustrating examples of long PUCCH and short PUCCH according to some aspects. Fig. 8A and Figure 8B In the example shown, time is illustrated along the horizontal axis and frequency is illustrated along the vertical axis. Fig. 8A and Figure 8B Each of the examples illustrates a corresponding time slot 802a and 802b, each of which includes a plurality of symbols in the time domain (e.g., fourteen OFDM or SC-FDM symbols). Fig. 8A and Figure 8BEach of them illustrates a corresponding BWP 804 comprising a subset of contiguous PRBs on a carrier in the frequency domain (eg, each of these PRBs comprises a suitable number of subcarriers, such as twelve subcarriers).

[0116] Each time slot 802a and 802b includes a PDCCH 806 carrying a DCI including a downlink scheduling assignment and an uplink scheduling grant. In some examples, the DCI may include scheduling information for scheduling a PUSCH or PUCCH in the same time slot or a subsequent time slot. In other examples, the DCI may include scheduling information for scheduling a PDSCH in the same time slot or a subsequent time slot. For example, Figure 8B As shown, the PDCCH 806 may schedule the PDSCH 810 to be transmitted in the time slot 802b.

[0117] Each time slot 802a and 802b may also include a PUCCH carrying UCI. Examples of UCI may include, but are not limited to, a scheduling request (SR), a HARQ-ACK bit (e.g., HARQ feedback information), a channel state feedback (CSF), or other suitable UCI. Figure 7 As shown in the table, PUCCH formats 1, 3, and 4 are long PUCCH formats occupying four to fourteen symbols, and PUCCH formats 0 and 2 are short PUCCH formats occupying one or two symbols. Fig. 8A Long PUCCH 808a is illustrated, and Figure 8B A short PUCCH 808b is illustrated.

[0118] In the long PUCCH 808a, symbols with DMRS are time-division multiplexed with UCI symbols to maintain low PAPR, while in the short PUCCH 808b, DMRS subcarriers are frequency-division multiplexed with UCI subcarriers. Whether to use the long PUCCH 808a or the short PUCCH 808b may depend on, for example, the number of UCI bits to be carried in the PUCCH, whether multiple UE multiplexing is required on the same PUCCH resource, and the channel conditions.

[0119] The resources to be used for PUCCH (e.g., time-frequency resources, such as the number of PRBs, the starting PRB, the starting symbol, and the number of symbols) (hereinafter referred to as PUCCH resources) may be predefined or dynamically configured. For example, PUCCH resources may be predefined by 3GPP, TS 38.213, Release 15-17, Table 9.2.1-1. As another example, PUCCH resources may be dynamically configured via an RRC message (e.g., PUCCH-Config). In either example, the UE may be configured with up to four PUCCH resource sets for UCI transmission including HARQ-ACK bits, wherein each PUCCH resource set may be used to transmit UCI within a range of payload sizes. For example, one PUCCH resource set in a PUCCH resource set may be used for up to two UCI bits (e.g., two HARQ-ACK bits). Here, this PUCCH resource set may include up to 32 PUCCH resources. Other PUCCH resource sets may be applicable to more than two UCI bits, each having a different range of UCI bit numbers and each having up to 8 PUCCH resources. Each PUCCH resource set may have a PUCCH format associated with it (e.g., PUCCH formats 0-4). The UE may select one of the configured PUCCH resource sets based on the UCI payload size. The UE may then further select a specific single PUCCH resource within the selected PUCCH resource set. For example, the DCI may include a PUCCH resource indicator (PRI) that identifies a specific PUCCH resource to be used for PUCCH transmission. The PRI may be, for example, a 3-bit field within DCI format 1_0 or DCI format 1_1. In some examples, the PUCCH format and time domain resource allocation may be determined by the PUCCH resource configuration, but the frequency domain resource allocation may not be explicitly specified. In this example, the frequency domain resource allocation may be determined by the DCI and the control channel element (CCE) position of the PDCCH carrying the DCI (e.g., based on the index of the first CCE of the PDCCH and the number of CCEs in the control resource set (CORESET) of the PDCCH).

[0120] As indicated above, each PUCCH format has a fixed waveform, such as Figure 7 As shown in Table 700 of . For example, CP-OFDM is used to send a short PUCCH format 2 for more than two UCI bits. In mmWave systems (e.g., FR2 or higher frequency range), short formats of PUCCH such as PUCCH format 2 are used to enable more frequent beam switching by a network entity (e.g., gNB). However, in coverage-limited situations, DFT-s-OFDM may be preferred due to lower PAPR, which results in lower power backoff.

[0121] Various aspects relate to mechanisms for waveform indication for PUCCH. For example, a network entity may provide an indication of a waveform for a PUCCH format to a UE. In some examples, the network entity may semi-statically or dynamically indicate a waveform to be used by the UE when sending a PUCCH with a specific PUCCH format to the network entity. In other examples, the network entity may transmit a semi-persistent command to the UE for waveform switching. In some examples, the waveform switching may be based on UE capabilities.

[0122] Fig. 9 is a signaling diagram illustrating exemplary signaling for PUCCH waveform indication between a network entity 902 and a UE 904 according to some aspects. The UE 904 may correspond to, for example Figure 1 and / or Figure 2 Any of the UEs or other scheduled entities shown. The network entity 902 may correspond to, for example Figure 1 , Figure 2 and / or Figure 3 Any of the network entities shown (e.g., a base station or gNB in ​​a converged base station architecture, or a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC in a disaggregated base station architecture).

[0123] exist Fig. 9 In the example shown, at 906, the UE 904 may provide the network entity 902 with the UE capabilities of the UE. The UE capabilities may indicate, for example, whether the UE 904 supports waveform switching for PUCCH and / or supports different waveform types per PUCCH format. For example, the UE capabilities may indicate that the UE supports CP-OFDM or DFT-s-OFDM for PUCCH format 2, and only supports DFT-s-OFDM for PUCCH formats 3 and 4. As another example, the UE capabilities may indicate that the UE supports only DFT-s-OFDM for PUCCH format 3, but supports CP-OFDM or DFT-s-OFDM for PUCCH formats 2 and 4. As yet another example, the UE capabilities may indicate that the UE supports waveform switching between CP-OFDM and DFT-s-OFDM for any of PUCCH formats 2, 3, and 4. In some examples, the UE capabilities may indicate that the UE supports waveform switching between short PUCCH formats for more than two UCI bits (e.g., between PUCCH format 2 using CP-OFDM and a different (new) PUCCH format using DFT-s-OFDM). In some examples, the UE capabilities may be per frequency range (FR), per band, per band combination, or per bandwidth part (BWP).

[0124] At 908, the network entity 902 may provide a waveform indication for a PUCCH format to the UE 904. The waveform indication may indicate a waveform type for the PUCCH format (e.g., CP-OFDM, DFT-s-OFDM, or other suitable waveform type). In some examples, the PUCCH format is PUCCH format 2. In other examples, the PUCCH format is PUCCH format 2 or a different (new) short PUCCH format with more than two UCI bits. Here, the waveform type associated with PUCCH format 2 may be CP-OFDM, and the waveform type associated with the different short PUCCH format may be DFT-s-OFDM. In some examples, the waveform indication may indicate at least one parameter associated with the waveform. For example, the waveform indication may indicate a pulse shape and / or filter for the waveform. In this example, the waveform indication may not indicate a waveform type (e.g., a predefined waveform type for the PUCCH format may be used), but instead provide different pulse shapes and / or filters for the waveform type. In other examples, the waveform indication may indicate a waveform type (e.g., a predefined waveform type for a PUCCH format or a different waveform type for a PUCCH format) and at least one parameter for the waveform type (e.g., a pulse shape and / or filter).

[0125] In some examples, the network entity 902 may semi-statically provide a waveform indication to the UE 904. For example, the network entity may provide an RRC message including an RRC configuration of a waveform type for a PUCCH format. The RRC configuration may be an RRC configuration of a PUCCH format that indicates a waveform type and other parameters associated with the PUCCH format (e.g., number of UCI bits, length of the PUCCH (number of symbols), etc.). For example, for PUCCH format 2, the network entity 902 may semi-statically configure the waveform type to CP-OFDM or DFT-s-OFDM (or other suitable waveform types). In some examples, the RRC message may include at least one parameter associated with the waveform type, and may also include (or not include) the waveform type, as indicated above.

[0126] In other examples, the network entity 902 can dynamically provide a waveform indication to the UE 904. For example, the waveform indication can correspond to a combination of a PUCCH resource configuration including a corresponding waveform configuration for each PUCCH resource (e.g., within a PUCCH resource set) and a PUCCH resource indicator (PRI) that selects one of the PUCCH resources within the PUCCH resource set for PUCCH transmission, as described in more detail below. In still other examples, the waveform indication can correspond to a semi-persistent command for waveform switching, as described in more detail below.

[0127] At 910, the UE 904 may transmit a PUCCH having a PUCCH format and waveform type indicated in the waveform indication. For example, the UE 904 may transmit a PUCCH having PUCCH format 2 using a DFT-s-OFDM waveform. As another example, the UE 904 may transmit a PUCCH having PUCCH format 2 using a CP-OFDM waveform having one or more parameters indicated in the waveform indication. As yet another example, the UE 904 may transmit a PUCCH having a different (new) short PUCCH format using a DFT-s-OFDM waveform.

[0128] Fig.10 1 is a signaling diagram illustrating exemplary signaling for dynamic PUCCH waveform indication between a network entity 1002 and a UE 1004 according to some aspects. The UE 1004 may correspond to, for example Figure 1 and / or Figure 2 Any of the UEs or other scheduled entities shown. The network entity 1002 may correspond to, for example Figure 1 , Figure 2 and / or Figure 3 Any of the network entities shown (e.g., a base station or gNB in ​​a converged base station architecture, or a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC in a disaggregated base station architecture).

[0129] exist Fig.10 In the example shown, at 1006, the network entity 1002 may provide the PUCCH resource and waveform configuration to the UE 1004. For example, the network entity 1002 may provide a PUCCH resource configuration indicating a corresponding waveform configuration (e.g., a waveform type and / or parameters associated with the waveform type) for each of the multiple PUCCH resources. Here, each of the multiple PUCCH resources may be included in a corresponding PUCCH resource set configured for the UE. For example, the PUCCH resource configuration (PUCCH-config) may include up to four PUCCH resource sets, each of which includes multiple PUCCH resources. Each PUCCH resource set may be associated with a corresponding PUCCH format. The PUCCH resource configuration may also include a corresponding waveform type associated with each of the multiple PUCCH resources.

[0130] An example of a PUCCH-config with two PUCCH resource sets is as follows:

[0131]

[0132]

[0133] In the above example, the first PUCCH resource set (pucch-ResourceSetID 0) may be associated with two or fewer UCI bits, while the second PUCCH resource set (pucch-ResourceSetID 1) may be associated with more than two UCI bits and may therefore be configured with a CP-OFDM or DFT-s-OFDM waveform type (or other suitable waveform type). In some examples, the waveform field may indicate a waveform type, one or more parameters associated with a predefined waveform type for a PUCCH format associated with the PUCCH resource set, or both a waveform type and one or more parameters associated with the waveform type.

[0134] At 1008, the network entity 1002 may provide a PUCCH resource indicator (PRI) within downlink control information (DCI) to the UE 1004. The PRI indicates the PUCCH resources within the PUCCH resource set that the UE 1004 will use for PUCCH transmission. For example, the UE 1004 may select a PUCCH resource set based on the number of UCI bits (UCI size) to be transmitted within the PUCCH. The UE 1004 may then use the PRI to select a specific PUCCH resource within the PUCCH resource set selected by the UE. For example, if the UCI size is greater than two bits, the UE 1004 may select a second PUCCH resource set (pucch-ResourceSetId 1). If the PRI is set to 1, the UE 1004 may select a PUCCH resource associated with index 1 within the second PUCCH resource set (resourceid i1) and utilize a waveform (e.g., a waveform type and parameters associated therewith) associated with resourceid i1.

[0135] In some examples, multiple waveform types and / or parameters may be configured for a PUCCH resource within a PUCCH-config (e.g., a waveform field for a particular PUCCH resource may indicate two or more different waveforms / parameters that may be used for that PUCCH resource). In this example, the waveform (e.g., waveform type and / or parameters associated with the waveform type) may be indicated based on the PRI together with the control channel element (CCE) position of the PDCCH carrying the DCI (e.g., based on the index of the first CCE of the PDCCH and / or the number of CCEs in a control resource set (CORESET) of the PDCCH).

[0136] In other examples, rather than configuring a specific waveform for each PUCCH within a PUCCH resource configuration, the waveform may be indicated by the PRI together with the control channel element (CCE) position of the PDCCH carrying the DCI (e.g., based on the index of the first CCE of the PDCCH and / or the number of CCEs in a control resource set (CORESET) of the PDCCH).

[0137] At 1010, the UE 1004 may send a PUCCH with a PUCCH format and waveform type / parameters indicated by the PUCCH resource configuration and / or PRI. For example, the UE 1004 may use a DFT-s-OFDM waveform to send a PUCCH with PUCCH format 2. As another example, the UE 1004 may use a CP-OFDM waveform with one or more parameters indicated in the waveform indication to send a PUCCH with PUCCH format 2. As yet another example, the UE 1004 may use a DFT-s-OFDM waveform to send a PUCCH with a different (new) short PUCCH format.

[0138] Fig.10 The dynamic waveform indication illustrated in can be used, for example, for PUCCH transmission including HARQ-ACK UCI bits. In some examples, UE 1004 may transmit a PUCCH including confirmation information (e.g., HARQ-ACK bits) for a scheduled PDSCH (e.g., a dynamically scheduled PDSCH). In other examples, UE 1004 may transmit a PUCCH including confirmation information for an SPS PDSCH based on an activation DCI for activating an SPS configuration for a semi-persistently scheduled (SPS) PDSCH.

[0139] In some examples, using different waveform types for PUCCH formats can result in different numbers of symbols (e.g., OFDM symbols) being used to transmit the PUCCH. For example, changing from CP-OFDM to DFT-s-OFDM for a short PUCCH (e.g., PUCCH format 2) can change the number of OFDM symbols from one to two or from two to more than two (e.g., three or more OFDM symbols). In some examples, for dynamic indication of the waveform, such as Fig.10 As shown, the number of symbols may be based on the PUCCH resource configuration. For example, each PUCCH resource may indicate the number of symbols of the PUCCH resource. An example PUCCH resource configuration for the second PUCCH resource (pucch-ResourceId 2) is as follows:

[0140]

[0141] Therefore, the number of symbols (nrofSymbols) may be specified for the PUCCH resource. In addition, a waveform type (waveform) may be further specified for the PUCCH resource, and the UE 1004 may transmit the PUCCH using the number of symbols and the waveform type indicated by the PUCCH resource configuration.

[0142] In other examples, the number of symbols for each waveform type may be based on a PUCCH format configuration or rule specified in one or more 5G NR standards or specifications. In this example, the PUCCH resources indicated in the PRI may be PUCCH resources having a number of symbols equal to the configured number of symbols for the waveform and PUCCH format. Thus, the network entity 1002 may select a PRI based on the configured number of symbols for the waveform associated with the PUCCH format (e.g., PUCCH resource set) to be used when sending the PUCCH.

[0143] If the number of symbols used when transmitting a PUCCH having a specific PUCCH format is changed from a predefined number of symbols (e.g., Figure 7 As shown in FIG. 1 , the DMRS overhead of the PUCCH may also change. For example, if the number of symbols of the short PUCCH (eg, PUCCH format 2) is changed from two symbols to more than two symbols, the DMRS overhead may be reduced, thereby allowing a more efficient DMRS.

[0144] Fig.11A and Fig. 11B is a diagram illustrating an example of a short PUCCH using different numbers of symbols according to some aspects. Fig.11A and Fig. 11B In the example shown, time is illustrated along the horizontal axis and frequency is illustrated along the vertical axis. Fig.11A and Fig. 11B Each of the examples illustrates a corresponding time slot 1102a and 1102b, each of which includes a plurality of symbols in the time domain (e.g., fourteen OFDM or SC-FDM symbols). Fig.11A and Fig. 11B Each of them illustrates a corresponding BWP 1104 comprising a subset of contiguous PRBs on a carrier in the frequency domain (eg, each of these PRBs comprises a suitable number of subcarriers, such as twelve subcarriers).

[0145] Each time slot 1102a and 1102b includes a PDCCH 1106 carrying a DCI including a downlink scheduling assignment and an uplink scheduling grant. In some examples, the DCI may include scheduling information for scheduling a PUSCH or PUCCH in the same time slot or a subsequent time slot. In other examples, the DCI may include scheduling information for scheduling a PDSCH in the same time slot or a subsequent time slot. For example, Fig.11A and Fig. 11B As shown, PDCCH 1106 may schedule PDSCH 1110 to be transmitted in the same time slot.

[0146] Each time slot 1102a and 1102b may also include a corresponding PUCCH 1108a and 1108b that carries UCI such as acknowledgment information (e.g., HARQ-ACK bits). In some examples, the UCI may include more than two bits. Fig.11A In the example shown, PUCCH 1108a is a short PUCCH (e.g., PUCCH format 2) transmitted over two OFDM symbols using, for example, a CP-OFDM waveform. Fig.11A In the short PUCCH 1108a shown, the DMRS subcarrier 1112a is frequency division multiplexed with the UCI subcarrier.

[0147] exist Fig. 11B In the example shown, PUCCH 1108b has Fig.11A The same PUCCH format (e.g., PUCCH format 2) as in FIG. 1108 is used, but PUCCH 1108b is sent over four symbols using, for example, a DFT-s-OFDM waveform. For DFT-s-OFDM, one OFDM symbol is dedicated to DMRS 1112b in PUCCH 1108b, which makes Fig.11A Approximately the same amount of PUCCH resources (eg, time-frequency resources) is used for DMRS 1112a in PUCCH 1108a as shown. Fig. 11B DMRS 1112b in PUCCH 1108b is shown. However, due to Fig. 11B The PUCCH 1108b is shown spread over four OFDM symbols, so Fig. 11B The DMRS overhead of PUCCH 1108b is shown to be less than Fig.11A DMRS overhead for PUCCH 1108a is shown. Fig. 11B The percentage of PUCCH resources (e.g., time-frequency resources) for DMRS 1112b in PUCCH 1108b is shown to be less than that for Fig.11A The percentage of PUCCH resources for DMRS 1112a in PUCCH 1108a is shown. This allows for improved DMRS efficiency in short PUCCH transmissions.

[0148] Fig.12 1 is a signaling diagram illustrating exemplary signaling for PUCCH waveform switching between a network entity 1202 and a UE 1204 according to some aspects. The UE 1204 may correspond to, for example, Figure 1 and / or Figure 2Any of the UEs or other scheduled entities shown. The network entity 1202 may correspond to, for example Figure 1 , Figure 2 and / or Figure 3 Any of the network entities shown (e.g., a base station or gNB in ​​a converged base station architecture, or a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC in a disaggregated base station architecture).

[0149] exist Fig.12 In the illustrated example, at 1206, the network entity 1202 can optionally provide a PUCCH format configuration to the UE 1204. For example, the network entity 1202 can send an RRC configuration of a PUCCH format (e.g., PUCCH format 2 or a different (new) PUCCH format) indicating the number of UCI bits, the length of the PUCCH (number of OFDM symbols), the waveform type, and other suitable parameters. In other examples, the PUCCH format can be predefined (e.g., via a 3GPP standard or specification).

[0150] At 1208, the network entity 1202 may provide a semi-persistent (SPS) command for waveform switching to the UE 1204. For example, PUCCH format 2 may be configured with CP-OFDM (e.g., via the PUCCH format configuration transmitted at 1206 or via a predefined standard or specification). In this example, the SPS command may indicate that PUCCH format 2 should be switched from CP-OFDM to DFT-s-OFDM. In some examples, the PUCCH format configuration transmitted at 1206 may indicate whether waveform switching is allowed for PUCCH format 2. If waveform switching is allowed, the UE 1204 may switch from using a CP-OFDM waveform to a DFT-s-OFDM waveform for PUCCH transmissions utilizing PUCCH format 2. In other examples, a different (new) short PUCCH format may be configured with a different waveform (such as DFT-s-OFDM) (e.g., via the PUCCH format configuration at 1206 or via a 3GPP standard or specification). In this example, the SPS command may indicate that the UE 1204 should switch from using PUCCH format 2 with a CP-OFDM waveform to a different (new) short PUCCH format with a DFT-s-OFDM waveform for short PUCCH transmissions. The SPS command may be transmitted via, for example, DCI or MAC-CE.

[0151] At 1210, the UE 1204 may transmit a PUCCH having a PUCCH format and waveform type indicated in the SPS command. For example, the UE 1204 may transmit a PUCCH having PUCCH format 2 using a DFT-s-OFDM waveform. As another example, the UE 1204 may transmit a PUCCH having a different (new) PUCCH format using a DFT-s-OFDM waveform. The UE 1204 may continue to use the waveform type indicated in the SPS command for a PUCCH format (e.g., PUCCH format 2 or a different (new) PUCCH format) until a new SPS command is received again to switch waveforms (e.g., from DFT-s-OFDM to CP-OFDM) for the same length range PUCCH transmission (e.g., a PUCCH transmission using a short PUCCH format).

[0152] Fig.13 1 is a block diagram illustrating an example of a hardware implementation of a user equipment (UE) 1300 employing a processing system 1314 according to some aspects. The UE 1300 may be a Figure 1 , Figure 2 , Fig. 9 , Fig.10 and / or Fig.12 Any one of the UEs or other scheduled entities illustrated in any one or more of .

[0153] According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1314 including one or more processors, such as the processor 1304. Examples of the processor 1304 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic element, a discrete hardware circuit, and other suitable hardware configured to perform various functions described throughout the present disclosure. In various examples, the UE 1300 may be configured to perform any one or more of the functions described herein. That is, the processor 1304 as utilized in the UE 1300 may be used to implement, for example, Fig. 9 or Fig.14 Any one or more of the methods or processes described and exemplified in .

[0154] In some examples, processor 1304 may be implemented via a baseband or modem chip, and in other implementations, processor 1304 may include several devices distinct and other than a baseband or modem chip (e.g., in scenarios such as those that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0155] In this example, the processing system 1314 may be implemented using a bus architecture, which is generally represented by bus 1302. Bus 1302 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1314 and the overall design constraints. Bus 1302 communicatively couples together various circuits including one or more processors, which are generally represented by processor 1304, memory 1305, and computer-readable media, which are generally represented by computer-readable media 1306. Bus 1302 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0156] The bus interface 1308 provides an interface between the bus 1302 and the transceiver 1310. For example, the transceiver 1310 can be a wireless transceiver. The transceiver 1310 provides a component for communicating with various other devices through a transmission medium (e.g., an air interface). The bus interface 1308 further provides an interface between the bus 1302 and a user interface 1312 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, control features, etc.). Of course, such a user interface 1312 can be omitted in some examples.

[0157] Computer readable medium 1306 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1306 may reside in processing system 1314, be located outside processing system 1314, or be distributed across multiple entities including processing system 1314. Computer readable medium 1306 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. In some examples, computer readable medium 1306 may be part of memory 1305. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system. In some examples, computer-readable medium 1306 may be implemented on an article of manufacture, which may also include one or more other elements or circuits, such as processor 1304 and / or memory 1305.

[0158] The computer readable medium 1306 may store computer executable code (e.g., software). Software shall be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures / procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0159] One or more processors, such as processor 1304, may be responsible for managing bus 1302 and general processing, including executing software (e.g., instructions or computer executable code) stored on computer readable medium 1306. The software, when executed by processor 1304, causes processing system 1314 to perform various processes and functions described herein for any particular device. Computer readable medium 1306 and / or memory 1305 may also be used to store data that may be manipulated by processor 1304 when executing the software. For example, memory 1305 may store one or more waveform indications 1316, one or more PUCCH formats 1318, and PUCCH resource configurations 1320 that may be used by the processor in communicating PUCCH.

[0160] In some aspects of the present disclosure, processor 1304 may include circuits configured for various functions. For example, processor 1304 may include communication and processing circuitry 1342 that is configured to communicate with a network entity (e.g., a converged or decomposed base station such as a gNB or eNB). In some examples, communication and processing circuitry 1342 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, communication and processing circuitry 1342 may include one or more transmit / receive chains.

[0161] In some implementations where communication involves receiving information, the communication and processing circuitry 1342 may obtain information from a component of the UE 1300 (e.g., from a transceiver 1310 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1342 may output the information to another component of the processor 1304, to the memory 1305, or to the bus interface 1308. In some examples, the communication and processing circuitry 1342 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1342 may receive information via one or more channels. In some examples, the communication and processing circuitry 1342 may include functionality for components for receiving. In some examples, the communication and processing circuitry 1342 may include functionality for components for processing, including components for demodulation, components for decoding, and the like.

[0162] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1342 may obtain information (e.g., from another component of the processor 1304, the memory 1305, or the bus interface 1308), process the information (e.g., modulate, encode, etc. the information), and output the processed information. For example, the communication and processing circuitry 1342 may output the information to the transceiver 1310 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1342 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1342 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1342 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1342 may include functionality for components for generating, including components for modulating, components for encoding, and the like.

[0163] In some examples, the communication and processing circuitry 1342 may be configured to receive (e.g., via the transceiver 1310) from a network entity an indication of a waveform type for a first format of a PUCCH (e.g., one of the PUCCH formats 1318) (e.g., waveform indication 1316). In some examples, the waveform type may include CP-OFDM or DFT-s-OFDM. In some examples, the first format includes PUCCH format 2. In some examples, the first format includes PUCCH format 2 or a different (new) short PUCCH format having more than two bits. In this example, the waveform type associated with PUCCH format 2 may be CP-OFDM, while the waveform type associated with a different PUCCH format may be DFT-s-OFDM. In some examples, the indication 1316 may indicate at least one parameter associated with the waveform type (e.g., a pulse shape and / or filter).

[0164] In some examples, indication 1316 is a semi-static indication. In this example, the communication and processing circuit 1342 may be configured to receive (e.g., via transceiver 1310) an RRC configuration of a waveform type for a first format of the PUCCH. In some examples, indication 1316 is a dynamic indication. In this example, the communication and processing circuit 1342 may be configured to receive (e.g., via transceiver 1310) a PUCCH resource configuration (e.g., PUCCH resource configuration 1320) indicating a corresponding waveform configuration for each of a plurality of PUCCH resources. In addition, the communication and processing circuit 1342 may be configured to receive a PUCCH resource indicator (PRI) within downlink control information (DCI). The PRI may indicate a PUCCH resource for a PUCCH in a plurality of PUCCH resources. The PRI may further indicate a waveform type for a first format of the PUCCH based on the PUCCH resource.

[0165] In some examples, a corresponding waveform configuration for each of the plurality of PUCCH resources within the PUCCH resource configuration 1320 may indicate one of at least two waveform types and a corresponding number of symbols (e.g., OFDM symbols) associated with the corresponding waveform configuration. In this example, the PRI may further indicate the number of symbols of the PUCCH based on the PUCCH resource.

[0166] In some examples, indication 1316 is a semi-persistent command for a waveform switch from a first waveform type to a second waveform type for a PUCCH. In some examples, the first waveform type is associated with a second format (e.g., one of PUCCH formats 1318) having the same length range as the first format. In some examples, communication and processing circuitry 1342 may be configured to receive the semi-persistent command for the waveform switch via one of a DCI or a MAC-CE (e.g., via transceiver 1310).

[0167] In some examples, the communication and processing circuitry 1342 may be further configured to send (e.g., via the transceiver 1310) the capabilities of the UE for waveform switching. For example, the capabilities of the UE may be based on at least one of a frequency range, a frequency band, a frequency band combination, or a BWP for the PUCCH. In this example, the indication 1316 of the waveform type for the first format of the PUCCH may be based on the capabilities of the UE. The communication and processing circuitry 1342 may be further configured to execute communication and processing instructions (software) 1352 stored on the computer-readable medium 1306 to implement one or more functions described herein.

[0168] The processor 1304 may also include a PUCCH waveform generation circuit 1344 configured to generate a PUCCH and communicate the PUCCH using a waveform type for the first format via the communication and processing circuit 1342 and the transceiver 1310. In some examples, the PUCCH may include confirmation information for the scheduled PDSCH. In other examples, the PUCCH may include confirmation information for the SPS PDSCH based on activating the SPS configuration for the semi-persistently scheduled (SPS) PDSCH.

[0169] In some examples, the PUCCH waveform generation circuit 1344 may be configured to switch from a first waveform type having a first number of symbols (e.g., OFDM symbols) to a second waveform type having a second number of symbols different from the first number of symbols. In some examples, the second number of symbols is greater than the first number of symbols. In this example, a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols. The PUCCH waveform generation circuit 1344 may be further configured to execute PUCCH waveform generation instructions (software) 1354 stored on the computer-readable medium 1306 to implement one or more functions described herein.

[0170] Fig.14is a flow chart illustrating an exemplary process 1400 for PUCCH waveform indication according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1400 may be performed by Fig.13 In some examples, process 1400 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0171] At block 1402, the UE may receive an indication of a waveform type for a first format for a physical uplink control channel (PUCCH). In some examples, the waveform type includes cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform spread OFDM (DFT-s-OFDM). In some examples, the first format includes PUCCH format 2. In some examples, the first format includes PUCCH format 2 or a different short PUCCH format having more than two bits. In this example, the waveform type associated with PUCCH format 2 includes CP-OFDM, and the waveform type associated with the different short PUCCH format includes DFT-s-OFDM. In some examples, the indication indicates at least one parameter associated with the waveform type.

[0172] In some examples, the indication is a semi-static indication. In this example, the UE may receive a radio resource control (RRC) configuration of a waveform type for a first format of the PUCCH. In some examples, the indication includes a dynamic indication. In this example, the UE may receive a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources. In addition, the UE may receive a PUCCH resource indicator (PRI) within downlink control information (DCI). The PRI indicates a PUCCH resource for a PUCCH in a plurality of PUCCH resources. The PRI further indicates a waveform type for a first format of the PUCCH based on the PUCCH resource.

[0173] In some examples, a corresponding waveform configuration for each of the plurality of PUCCH resources within the PUCCH resource configuration indicates one of at least two waveform types and a corresponding number of symbols (e.g., OFDM symbols) associated with the corresponding waveform configuration. In this example, the PRI further indicates the number of symbols of the PUCCH based on the PUCCH resource.

[0174] In some examples, the UE may receive a semi-persistent command for a waveform switch from a first waveform type to a second waveform type for a PUCCH. In some examples, the first waveform type is associated with a second format of the PUCCH having the same length range as the first format. In some examples, the UE receives the semi-persistent command for the waveform switch via one of downlink control information (DCI) or a medium access control (MAC) control element (MAC-CE). In some examples, the UE may receive an indication of the waveform type for the first format of the PUCCH based on the capabilities of the UE. In some examples, the capabilities of the UE are based on at least one of a frequency range, a frequency band, a frequency band combination, or a bandwidth part (BWP) of the PUCCH. For example, the above in combination Fig.13 The communication and processing circuitry 1342 in conjunction with the transceiver 1310 as shown and described may provide means for receiving an indication of a waveform type for a first format of the PUCCH.

[0175] At box 1404, the UE may communicate the PUCCH using a waveform type for a first format. In some examples, the PUCCH includes confirmation information for a scheduled physical downlink shared channel (PDSCH). In other examples, the PUCCH includes confirmation information for an SPS PDSCH based on an activated DCI for an SPS configuration for a semi-persistently scheduled (SPS) PDSCH. In some examples, the UE may switch from a first waveform type having a first number of symbols to a second waveform type having a second number of symbols different from the first number of symbols for the first format of the PUCCH. In some examples, the second number of symbols is greater than the first number of symbols, and a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols. For example, the above in combination Fig.13 The PUCCH waveform generation circuit 1344, along with the communication and processing circuit 1342 and transceiver 1310, as shown and described may provide means for communicating PUCCH using a waveform type for a first format.

[0176] In one configuration, a UE includes means for receiving an indication of a waveform type for a first format for a physical uplink control channel (PUCCH), and means for communicating the PUCCH using the waveform type for the first format. In one aspect, the aforementioned means may be Fig.13 The processor 1304 is shown configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.

[0177] Of course, in the above examples, the circuits included in the processor 1304 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to storage in the computer-readable storage medium 1306 or in Figure 1 , Figure 2 , Figure 6 and Fig.13 In any other suitable device or component described in any of the foregoing and utilizing, for example, Fig. 9 , Fig.10 , Fig.12 and Fig.14 Instructions for the described processes and / or algorithms.

[0178] Fig.15 1 is a block diagram illustrating an example of a hardware implementation of a network entity 1500 employing a processing system 1514 according to some aspects. The network entity 1500 can be, for example, any base station (e.g., gNB, eNB) or Figures 1 to 3 , Fig. 9 , Fig.10 and / or Fig.12 The network entity 1500 may be further implemented in a converged or monolithic base station architecture, or in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In addition, the network entity 1500 may be a stationary network entity or a mobile network entity.

[0179] According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1514 including one or more processors (such as processor 1504). The processing system 1514 may be combined with the above Fig.13 The processing system 1314 shown and described is substantially the same, including a bus interface 1508, a bus 1502, a memory 1505, a processor 1504, and a computer-readable medium 1506. Therefore, for the sake of brevity, their description will not be repeated. In addition, the network entity 1500 may include an optional user interface 1512 and a communication interface 1510. The communication interface 1510 may provide an interface (e.g., wireless or wired) between the network entity 1500 and multiple transmit receive points (TRPs), core network nodes, and / or multiple UEs. In some examples, the communication interface 1510 may include a wireless transceiver.

[0180] Processor 1504, as utilized in network entity 1500, may be used to implement any one or more of the processes described below. In some examples, memory 1505 may store UE capabilities 1516 of the UE.

[0181] In some aspects of the present disclosure, processor 1504 may include communication and processing circuitry 1542 that is configured for various functions, including, for example, communicating with one or more UEs or other scheduled entities or core network nodes. In some examples, communication and processing circuitry 1542 may communicate with one or more UEs via one or more TRPs associated with network entity 1500. In some examples, communication and processing circuitry 1542 may include one or more hardware components that provide a physical structure that performs processes associated with wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). In addition, communication and processing circuitry 1542 may be configured to process and transmit downlink traffic and downlink control, and receive and process uplink traffic and uplink control.

[0182] In some examples, the communication and processing circuitry 1542 may be configured to provide (e.g., via the communication interface 1510) an indication of a waveform type for a first format for the PUCCH. The indication may, for example, be provided to one or more UEs. In some examples, the waveform type may include CP-OFDM or DFT-s-OFDM. In some examples, the first format includes PUCCH format 2. In some examples, the first format includes PUCCH format 2 or a different (new) short PUCCH format having more than two bits. In this example, the waveform type associated with PUCCH format 2 may be CP-OFDM, while the waveform type associated with a different PUCCH format may be DFT-s-OFDM. In some examples, the indication may indicate at least one parameter associated with the waveform type (e.g., a pulse shape and / or filter).

[0183] In some examples, the indication is a semi-static indication. In this example, the communication and processing circuit 1542 may be configured to provide an RRC configuration of a waveform type for a first format of the PUCCH (e.g., via the communication interface 1510). In some examples, the indication is a dynamic indication. In this example, the communication and processing circuit 1542 may be configured to provide a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources (e.g., via the communication interface 1510). In addition, the communication and processing circuit 1542 may be configured to provide a PUCCH resource indicator (PRI) within the downlink control information (DCI) (e.g., via the communication interface). The PRI may indicate a PUCCH resource for a PUCCH in a plurality of PUCCH resources. The PRI may further indicate a waveform type for a first format of the PUCCH based on the PUCCH resource.

[0184] In some examples, the indication is a semi-persistent command for a waveform switch from a first waveform type to a second waveform type for the PUCCH. In some examples, the first waveform type is associated with a second format having the same length range as the first format. In some examples, the communication and processing circuitry 1542 may be configured to provide the semi-persistent command for the waveform switch via one of the DCI or the MAC-CE (e.g., via the communication interface 1510).

[0185] In some examples, the communication and processing circuitry 1542 may be further configured to receive (e.g., via the communication interface 1510) the capabilities of the UE for waveform switching (e.g., UE capabilities 1516). The communication and processing circuitry 1542 may be further configured to, for example, store the capabilities 1516 in the memory 1505. The UE capabilities 1516 may be based on at least one of a frequency range, a frequency band, a frequency band combination, or a bandwidth part (BWP) of the PUCCH.

[0186] The communication and processing circuit 1542 may be further configured to communicate (e.g., receive) a PUCCH using a waveform type for a first format. The PUCCH may be received, for example, from a UE. In some examples, the communication and processing circuit 1542 may be configured to receive (e.g., via the communication interface 1510) a PUCCH including confirmation information for a scheduled physical downlink shared channel (PDSCH). In some examples, the communication and processing circuit 1542 may be configured to receive (e.g., via the communication interface 1510) a PUCCH including confirmation information for an SPS PDSCH based on an activation DCI configured for an SPS for a semi-persistently scheduled (SPS) PDSCH. The communication and processing circuit 1542 may be further configured to execute communication and processing instructions (software) 1552 stored on the computer-readable medium 1506 to implement one or more functions described herein.

[0187] The processor 1504 may also include a PUCCH waveform identification circuit 1544 configured to identify a waveform type from at least two waveform types. In some examples, the PUCCH waveform identification circuit 1544 may be further configured to identify the number of symbols of the PUCCH for the waveform type. In this example, the PUCCH waveform identification circuit 1544, together with the communication and processing circuit 1542, may be configured to provide a PUCCH resource configuration indicating a corresponding waveform configuration for each of the multiple PUCCH resources. The corresponding waveform configuration for each of the multiple PUCCH resources indicates one of the at least two waveform types and a corresponding number of symbols associated with the corresponding waveform configuration. The PUCCH waveform identification circuit 1544, together with the communication and processing circuit 1542, may be further configured to provide a PUCCH resource indicator (PRI) within downlink control information (DCI). The PRI indicates a PUCCH resource for the PUCCH in the multiple PUCCH resources, and further indicates a waveform type for the first format of the PUCCH and the number of symbols of the PUCCH based on the PUCCH resource. In some examples, the PUCCH waveform identification circuit 1544 may be configured to identify the number of symbols of the PUCCH for the waveform type based on the first format of the PUCCH.

[0188] The PUCCH waveform identification circuit 1544 may be further configured to switch, for a first format of the PUCCH, from a first waveform type having a first number of symbols to a second waveform type having a second number of symbols different from the first number of symbols. In some examples, the second number of symbols is greater than the first number of symbols, and wherein a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols.

[0189] In some examples, the PUCCH waveform identification circuit 1544 may be further configured to identify the waveform type of the first format for the PUCCH based on the UE capabilities 1516. The PUCCH waveform identification circuit 1544 may be further configured to execute PUCCH waveform identification instructions (software) 1554 stored on the computer-readable medium 1506 to implement one or more functions described herein.

[0190] Fig.16 1600 is a flowchart illustrating an exemplary process 1600 for waveform indication according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1600 may be performed by Fig.15In some examples, process 1600 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0191] At block 1602, a network entity may provide an indication of a waveform type for a first format for a physical uplink control channel (PUCCH). In some examples, the waveform type includes cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform spread OFDM (DFT-s-OFDM). In some examples, the first format includes PUCCH format 2. In some examples, the first format includes PUCCH format 2 or a different short PUCCH format having more than two bits. In this example, the waveform type associated with PUCCH format 2 includes CP-OFDM, and the waveform type associated with the different short PUCCH format includes DFT-s-OFDM. In some examples, the indication indicates at least one parameter associated with the waveform type.

[0192] In some examples, the indication is a semi-static indication. In this example, the network entity may provide a radio resource control (RRC) configuration of a waveform type for a first format of the PUCCH. In some examples, the indication includes a dynamic indication. In this example, the network entity may provide a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources. In addition, the network entity may provide a PUCCH resource indicator (PRI) within downlink control information (DCI). The PRI indicates a PUCCH resource for a PUCCH in a plurality of PUCCH resources. The PRI further indicates a waveform type for a first format of the PUCCH based on the PUCCH resource.

[0193] In some examples, the network entity may identify a waveform type from at least two waveform types. In addition, the network entity may identify the number of symbols of the PUCCH for the waveform type. In some examples, the network entity may identify the number of symbols of the PUCCH for the waveform type based on the first format of the PUCCH. In some examples, the network entity may provide a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources. The corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources indicates a waveform type in at least two waveform types and a corresponding number of symbols associated with the corresponding waveform configuration. In some examples, the network entity may provide a PUCCH resource indicator (PRI) within downlink control information (DCI). The PRI indicates a PUCCH resource for the PUCCH in a plurality of PUCCH resources. The PRI further indicates the waveform type for the first format of the PUCCH and the number of symbols of the PUCCH based on the PUCCH resource. In some examples, the network entity may switch from a first waveform type having a first number of symbols to a second waveform type having a second number of symbols different from the first number of symbols for the first format of the PUCCH. In some examples, the second number of symbols is greater than the first number of symbols, and a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols.

[0194] In some examples, a network entity may provide a semi-persistent command for a waveform switch from a first waveform type to a second waveform type for a PUCCH. In some examples, the first waveform type is associated with a second format of a PUCCH having the same length range as the first format. In some examples, the network entity may provide a semi-persistent command for a waveform switch via one of downlink control information (DCI) or a medium access control (MAC) control element (MAC-CE). In some examples, the network entity may provide an indication of the waveform type for the first format of the PUCCH to the UE based on the capabilities of the UE. In some examples, the capabilities of the UE are based on at least one of a frequency range, a frequency band, a frequency band combination, or a bandwidth part (BWP) of the PUCCH. For example, the above in combination Fig.15 The communication and processing circuitry 1542 in conjunction with the PUCCH waveform identification circuitry 1544 and the communication interface 1510 shown and described may provide means for providing an indication of a waveform type for a first format of the PUCCH.

[0195] At block 1604, the network entity may communicate a PUCCH using a waveform type for the first format. In some examples, the PUCCH includes confirmation information for a scheduled physical downlink shared channel (PDSCH). In other examples, the PUCCH includes confirmation information for an SPS PDSCH based on an activation DCI for activating an SPS configuration for a semi-persistently scheduled (SPS) PDSCH. For example, the above in conjunction with Fig.15 The illustrated and described communication and processing circuitry 1542 and communication interface 1510 may provide means for communicating PUCCH using a waveform type for a first format.

[0196] In one configuration, a network entity includes means for providing an indication of a waveform type for a first format for a physical uplink control channel (PUCCH), and means for communicating the PUCCH using the waveform type for the first format. In one aspect, the aforementioned means may be Fig.15 The processor 1504 shown in FIG. 1 is configured to perform the functions recited by the aforementioned components. On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions recited by the aforementioned components.

[0197] Of course, in the above examples, the circuits included in the processor 1504 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to storage in the computer-readable storage medium 1506 or in Figures 1 to 3 , Figure 6 and Fig.15 In any other suitable device or component described in any of the foregoing and utilizing, for example, Fig. 9 , Fig.10 , Fig.12 and Fig.16 Instructions for the described processes and / or algorithms.

[0198] The following provides an overview of various aspects of the disclosure:

[0199] Aspect 1: A method for wireless communications at a network entity, the method comprising: providing an indication of a waveform type for a first format of a physical uplink control channel (PUCCH); and communicating the PUCCH using the waveform type for the first format.

[0200] Aspect 2: The method according to aspect 1, wherein the waveform type includes cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform spread OFDM (DFT-s-OFDM).

[0201] Aspect 3: The method according to aspect 1 or 2, wherein the first format includes PUCCH format 2.

[0202] Aspect 4: A method according to aspect 1 or 2, wherein the first format includes PUCCH format 2 or a different short PUCCH format having more than two bits, and wherein the waveform type associated with the PUCCH format 2 includes CP-OFDM, and the waveform type associated with the different short PUCCH format includes DFT-s-OFDM.

[0203] Aspect 5: The method according to any one of aspects 1 to 4, wherein the indication indicates at least one parameter associated with the waveform type.

[0204] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the indication comprises a semi-static indication, and wherein providing the indication of the waveform type further comprises: providing a radio resource control (RRC) configuration of the waveform type for the first format of the PUCCH.

[0205] Aspect 7: A method according to any one of Aspects 1 to 5, wherein the indication includes a dynamic indication, and wherein providing the indication of the waveform type of the first format for the PUCCH also includes: providing a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources.

[0206] Aspect 8: A method according to aspect 7, wherein providing the indication of the waveform type of the first format for the PUCCH also includes: providing a PUCCH resource indicator (PRI) within downlink control information (DCI), the PRI indicating a PUCCH resource used for the PUCCH among the multiple PUCCH resources, and the PRI further indicating the waveform type of the first format for the PUCCH based on the PUCCH resource.

[0207] Aspect 9: The method of aspect 8, wherein communicating the PUCCH using the waveform type for the first format further comprises: receiving the PUCCH including confirmation information for a scheduled physical downlink shared channel (PDSCH).

[0208] Aspect 10: A method according to aspect 8, wherein conveying the PUCCH using the waveform type for the first format also includes: receiving the PUCCH including confirmation information for the SPS PDSCH based on activation DCI for activating an SPS configuration for a semi-persistently scheduled (SPS) PDSCH.

[0209] Aspect 11: The method according to any one of aspects 1 to 5 or 7 to 10 further includes: identifying the waveform type from at least two waveform types; and identifying the number of symbols of the PUCCH for the waveform type.

[0210] Aspect 12: A method according to aspect 11, wherein providing the indication of the waveform type of the first format for the PUCCH further includes: providing a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources, the corresponding waveform configuration for each PUCCH resource in the plurality of PUCCH resources indicating one of the at least two waveform types and a corresponding number of symbols associated with the corresponding waveform configuration; and providing a PUCCH resource indicator (PRI) within downlink control information (DCI), the PRI indicating a PUCCH resource for the PUCCH in the plurality of PUCCH resources, the PRI indicating the waveform type of the first format for the PUCCH and the number of symbols of the PUCCH based on the PUCCH resource.

[0211] Aspect 13: The method according to aspect 11 or 12, wherein identifying the number of symbols of the PUCCH for the waveform type further comprises: identifying the number of symbols of the PUCCH for the waveform type based on the first format of the PUCCH.

[0212] Aspect 14: A method according to any one of Aspects 11 to 13, wherein identifying the waveform type further comprises: switching from a first waveform type having a first number of symbols to a second waveform type having a second number of symbols different from the first number of symbols for the first format of the PUCCH.

[0213] Aspect 15: A method according to Aspect 14, wherein the second number of symbols is greater than the first number of symbols, and wherein a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols.

[0214] Aspect 16: A method according to any one of Aspects 1 to 5, wherein providing the indication of the waveform type of the first format for the PUCCH also includes: providing a semi-persistent command for waveform switching from a first waveform type to a second waveform type for the PUCCH.

[0215] Aspect 17: The method according to aspect 16, wherein the first waveform type is associated with a second format of the PUCCH, the second format having the same length range as the first format.

[0216] Aspect 18: A method according to Aspect 16 or 17, wherein providing the semi-persistent command for waveform switching also includes: providing the semi-persistent command for waveform switching via one of downlink control information (DCI) or medium access control (MAC) control element (MAC-CE).

[0217] Aspect 19: A method according to any one of Aspects 1 to 18, wherein providing the indication of the waveform type of the first format for the PUCCH also includes: providing to a user equipment (UE) the indication of the waveform type of the first format for the PUCCH based on the capabilities of the UE.

[0218] Aspect 20: The method according to aspect 19, wherein the capability of the UE is based on at least one of a frequency range, a frequency band, a frequency band combination, or a bandwidth part (BWP) of the PUCCH.

[0219] Aspect 21: A network entity, comprising: a memory; and a processor, the processor being coupled to the memory, the processor being configured to execute the method according to any one of aspects 1 to 20.

[0220] Aspect 22: A network entity comprising means for performing the method according to any one of aspects 1 to 20.

[0221] Aspect 23: A non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of a network entity to perform the method according to any one of aspects 1 to 20.

[0222] Aspect 24: A method for wireless communications at a user equipment, the method comprising: receiving an indication of a waveform type for a first format of a physical uplink control channel (PUCCH); and communicating the PUCCH using the waveform type for the first format.

[0223] Aspect 25: The method according to aspect 24, wherein the waveform type includes cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform spread OFDM (DFT-s-OFDM).

[0224] Aspect 26: A method according to aspect 24 or 25, wherein the first format comprises PUCCH format 2.

[0225] Aspect 27: A method according to aspect 24 or 25, wherein the first format includes PUCCH format 2 or a different short PUCCH format having more than two bits, and wherein the waveform type associated with the PUCCH format 2 includes CP-OFDM, and the waveform type associated with the different short PUCCH format includes DFT-s-OFDM.

[0226] Aspect 28: A method according to any one of aspects 24 to 27, wherein the indication indicates at least one parameter associated with the waveform type.

[0227] Aspect 29: A method according to any one of Aspects 24 to 28, wherein the indication comprises a semi-static indication, and wherein receiving the indication of the waveform type further comprises: receiving a radio resource control (RRC) configuration of the waveform type for the first format of the PUCCH.

[0228] Aspect 30: A method according to any one of Aspects 24 to 28, wherein the indication includes a dynamic indication, and wherein receiving the indication of the waveform type of the first format for the PUCCH also includes: receiving a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource in a plurality of PUCCH resources.

[0229] Aspect 31: A method according to aspect 30, wherein receiving the indication of the waveform type of the first format for the PUCCH also includes: receiving a PUCCH resource indicator (PRI) within downlink control information (DCI), the PRI indicating a PUCCH resource used for the PUCCH among the multiple PUCCH resources, and the PRI further indicating the waveform type of the first format for the PUCCH based on the PUCCH resource.

[0230] Aspect 32: The method according to aspect 31, wherein communicating the PUCCH using the waveform type for the first format further comprises: sending the PUCCH including confirmation information for a scheduled physical downlink shared channel (PDSCH).

[0231] Aspect 33: A method according to aspect 31, wherein using the waveform type for the first format to convey the PUCCH also includes: sending the PUCCH including confirmation information for the SPS PDSCH based on activating DCI for an SPS configuration for a semi-persistently scheduled (SPS) PDSCH.

[0232] Aspect 34: A method according to any one of Aspects 24 to 28 or 30 to 33, wherein receiving the indication of the waveform type for the first format of the PUCCH further includes: receiving a PUCCH resource configuration indicating a corresponding waveform configuration for each of a plurality of PUCCH resources, the corresponding waveform configuration for each of the plurality of PUCCH resources indicating one of at least two waveform types and a corresponding number of symbols associated with the corresponding waveform configuration; and receiving a PUCCH resource indicator (PRI) within downlink control information (DCI), the PRI indicating a PUCCH resource for the PUCCH among the plurality of PUCCH resources, the PRI indicating the waveform type for the first format of the PUCCH and the number of symbols of the PUCCH based on the PUCCH resource.

[0233] Aspect 35: The method according to aspect 34 further comprises: switching from a first waveform type having a first number of symbols to a second waveform type having a second number of symbols different from the first number of symbols for the first format of the PUCCH.

[0234] Aspect 36: A method according to Aspect 35, wherein the second number of symbols is greater than the first number of symbols, and wherein a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols.

[0235] Aspect 37: A method according to any one of Aspects 24 to 28, wherein receiving the indication of the waveform type of the first format for the PUCCH also includes: receiving a semi-persistent command for waveform switching from a first waveform type to a second waveform type for the PUCCH.

[0236] Aspect 39: The method according to aspect 37, wherein the first waveform type is associated with a second format of the PUCCH, the second format having the same length range as the first format.

[0237] Aspect 40: A method according to Aspect 37 or 38, wherein receiving the semi-persistent command for waveform switching also includes: receiving the semi-persistent command for waveform switching via one of downlink control information (DCI) or medium access control (MAC) control element (MAC-CE).

[0238] Aspect 41: A method according to any one of Aspects 24 to 40, wherein receiving the indication of the waveform type for the first format for the PUCCH also includes: receiving the indication of the waveform type for the first format for the PUCCH based on the capability of the user equipment.

[0239] Aspect 42: The method of aspect 41, wherein the capability of the user equipment is based on at least one of a frequency range, a frequency band, a frequency band combination, or a bandwidth part (BWP) of the PUCCH.

[0240] Aspect 43: A user equipment comprising: a memory; and a processor, the processor being coupled to the memory, the processor being configured to perform the method according to any one of aspects 24 to 42.

[0241] Aspect 44: A user equipment comprising means for performing the method according to any one of aspects 24 to 42.

[0242] Aspect 45: A non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of a network entity to perform the method according to any one of aspects 24 to 42.

[0243] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0244] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0245] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).

[0246] Figures 1 to 16 One or more of the components, steps, features, and / or functions illustrated in the embodiments may be rearranged and / or combined into a single component, step, feature, or function or may be embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 3 Figure 6 Fig. 9 , Fig.10 , Fig.12 , Fig.13 and / or Fig.15 The apparatus, device and / or component illustrated in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0247] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of various steps in an example order, but are not intended to be limited to the specific order or hierarchy presented unless explicitly stated herein.

[0248] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims. No claim element is to be construed under 35 USC §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for.”

Claims

1. A network entity configured for wireless communication, comprising: Memory; and a processor coupled to the memory, the processor being configured to: providing an indication of a waveform type for a first format of a physical uplink control channel (PUCCH); and The PUCCH is communicated using the waveform type for the first format.

2. The network entity of claim 1, wherein the waveform type comprises cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform spread OFDM (DFT-s-OFDM). 3 . The network entity of claim 1 , wherein the first format comprises PUCCH format 2. 4 .

4. The network entity of claim 1 , wherein the first format comprises PUCCH format 2 or a different short PUCCH format having more than two bits, and wherein the waveform type associated with the PUCCH format 2 comprises CP-OFDM, and the waveform type associated with the different short PUCCH format comprises DFT-s-OFDM.

5. The network entity of claim 1, wherein the indication indicates at least one parameter associated with the waveform type.

6. The network entity of claim 1 , wherein the indication comprises a semi-static indication, and wherein the processor is further configured to: A radio resource control (RRC) configuration of the waveform type for the first format of the PUCCH is provided.

7. The network entity of claim 1 , wherein the indication comprises a dynamic indication, and wherein the processor is configured to: A PUCCH resource configuration is provided indicating a corresponding waveform configuration for each PUCCH resource of a plurality of PUCCH resources.

8. The network entity according to claim 7, wherein the processor is further configured to: A PUCCH resource indicator (PRI) is provided within downlink control information (DCI), the PRI indicating a PUCCH resource for the PUCCH among the plurality of PUCCH resources, the PRI further indicating the waveform type of the first format for the PUCCH based on the PUCCH resource.

9. The network entity according to claim 8, wherein the processor is further configured to: The PUCCH including acknowledgement information for a scheduled physical downlink shared channel (PDSCH) is received.

10. The network entity according to claim 8, wherein the processor is further configured to: The PUCCH is received including confirmation information for the SPS PDSCH based on activation DCI for activating an SPS configuration for a semi-persistently scheduled (SPS) PDSCH.

11. The network entity of claim 1 , wherein the processor is further configured to: identifying the waveform type from at least two waveform types; and The number of symbols of the PUCCH for the waveform type is identified.

12. The network entity according to claim 11, wherein the processor is further configured to: providing a PUCCH resource configuration indicating a respective waveform configuration for each of a plurality of PUCCH resources, the respective waveform configuration for each of the plurality of PUCCH resources indicating one of the at least two waveform types and a respective number of symbols associated with the respective waveform configuration; and A PUCCH resource indicator (PRI) is provided within downlink control information (DCI), the PRI indicating a PUCCH resource for the PUCCH among the plurality of PUCCH resources, the PRI indicating the waveform type of the first format for the PUCCH and the corresponding number of symbols of the PUCCH based on the PUCCH resource.

13. The network entity of claim 11, wherein the processor is further configured to: The number of symbols of the PUCCH for the waveform type is identified based on the first format of the PUCCH.

14. The network entity of claim 11, wherein the processor is further configured to: Switching from a first waveform type having a first number of symbols to a second waveform type having a second number of symbols different from the first number of symbols is performed for the first format of the PUCCH.

15. The network entity of claim 14, wherein the second number of symbols is greater than the first number of symbols, and wherein a first overhead of a demodulation reference signal (DMRS) for the first number of symbols is greater than a second overhead of the DMRS for the second number of symbols.

16. The network entity of claim 1, wherein the processor is further configured to: A semi-persistent command to switch a waveform from a first waveform type to a second waveform type for the PUCCH is provided.

17. The network entity of claim 16, wherein the first waveform type is associated with a second format of the PUCCH, the second format having a same length range as the first format.

18. The network entity of claim 16, wherein the processor is further configured to: The semi-persistent command to switch waveforms is provided via one of downlink control information (DCI) or a medium access control (MAC) control element (MAC-CE).

19. The network entity of claim 1, wherein the processor is further configured to: The indication of the waveform type of the first format for the PUCCH based on capabilities of the UE is provided to a user equipment (UE).

20. The network entity of claim 19, wherein the capability of the UE is based on at least one of a frequency range, a frequency band, a frequency band combination, or a bandwidth part (BWP) of the PUCCH.

21. A method for wireless communication at a network entity, the method comprising: providing an indication of a waveform type of a first format for a physical uplink control channel (PUCCH); as well as The PUCCH is communicated using the waveform type for the first format.

22. The method of claim 21 , wherein the indication comprises a semi-static indication, and wherein providing the indication of the waveform type further comprises: A radio resource control (RRC) configuration of the waveform type for the first format of the PUCCH is provided.

23. The method of claim 21, wherein the indication comprises a dynamic indication, and wherein providing the indication of the waveform type for the first format for the PUCCH further comprises: providing a PUCCH resource configuration indicating a corresponding waveform configuration for each PUCCH resource of a plurality of PUCCH resources; as well as A PUCCH resource indicator (PRI) is provided within downlink control information (DCI), the PRI indicating a PUCCH resource for the PUCCH among the plurality of PUCCH resources, the PRI further indicating the waveform type of the first format for the PUCCH based on the PUCCH resource.

24. The method of claim 21 , wherein providing the indication of the waveform type for the first format for the PUCCH further comprises: A semi-persistent command to switch a waveform from a first waveform type to a second waveform type for the PUCCH is provided.

25. A user equipment configured for wireless communication, comprising: a transceiver configured to communicate with a network entity; Memory; and a processor coupled to the transceiver and the memory, the processor being configured to: receiving an indication of a waveform type of a first format for a physical uplink control channel (PUCCH); and The PUCCH is communicated using the waveform type for the first format.

26. The user equipment of claim 25, wherein the indication comprises a semi-static indication, and wherein the processor is further configured to: A radio resource control (RRC) configuration of the waveform type for the first format of the PUCCH is received.

27. The user equipment of claim 25, wherein the indication comprises a dynamic indication, and wherein the processor is configured to: receiving a PUCCH resource configuration indicating a corresponding waveform configuration for each of a plurality of PUCCH resources; and A PUCCH resource indicator (PRI) is received within downlink control information (DCI), the PRI indicating a PUCCH resource for the PUCCH among the plurality of PUCCH resources, the PRI further indicating the waveform type of the first format for the PUCCH based on the PUCCH resource.

28. The user equipment of claim 25, wherein the processor is further configured to: A semi-persistent command to switch a waveform from a first waveform type to a second waveform type for the PUCCH is provided.

29. A method for wireless communication at a user equipment, the method comprising: receiving an indication of a waveform type of a first format for a physical uplink control channel (PUCCH); as well as The PUCCH is communicated using the waveform type for the first format.

30. The method of claim 29, wherein the indication comprises a semi-static indication, a dynamic indication, or a semi-persistent command to switch waveforms.

Images