Virtual hopping for physical uplink control channel

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may apply a Discrete Fourier Transform (DFT) Orthogonal Cover Code (OCC) to a first virtual hop associated with a Physical Uplink Control Channel (PUCCH) transmission. The UE may apply the DFT OCC to a second virtual hop associated with the PUCCH transmission, where the first virtual hop and the second virtual hop are associated with an equal number of orthogonal frequency division multiplexing (OFDM) symbols, where a size of the DFT OCC is based at least in part on the number of OFDM symbols, and where the first virtual hop and the second virtual hop are not associated with a physical frequency hopping. Numerous other aspects are described.

Description

[0001] Cross Reference to Related Applications

[0002] This Patent Application claims priority to U.S. Provisional Patent Application No. 63 / 519,132, filed August 11, 2023, entitled “VIRTUAL HOPS FOR PHYSICAL UPLINK CONTROL CHANNEL,” and U.S. Non-Provisional Patent Application No. 18 / 433,979, filed February 6, 2024, entitled “VIRTUAL HOPS FOR PHYSICAL UPLINK CONTROL CHANNEL,” which are hereby expressly incorporated by reference herein. TECHNICAL FIELD

[0003] Aspects of the present disclosure relate generally to wireless communication, and techniques and apparatuses for virtual hops for physical uplink control channel. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and / or the like). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0005] A wireless network can include one or more network nodes that support communications for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE can communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to communications from network nodes to UEs, and “uplink” (or “UL”) refers to communications from UEs to network nodes. Some wireless networks can support device-to-device communications, such as via local links (e.g., sidelink (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, among others).

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols to communicate over the air interfaces. New Radio (NR), which can be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE can include one or more memories and one or more processors coupled to the one or more memories. The one or more processors can be configured to cause the UE to apply a discrete Fourier transform (DFT) orthogonal cover code (OCC) to a first virtual hop associated with a physical uplink control channel (PUCCH) transmission. The one or more processors can be configured to cause the UE to apply the DFT OCC to a second virtual hop associated with the PUCCH transmission, where the first virtual hop and the second virtual hop are associated with an equal number of orthogonal frequency division multiplexing (OFDM) symbols, where a size of the DFT OCC is based at least in part on the number of OFDM symbols, and where the first virtual hop and the second virtual hop are not associated with a physical frequency hopping.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node can include one or more memories and one or more processors coupled to the one or more memories. The one or more processors can be configured to cause the network node to obtain a first virtual hop associated with a PUCCH transmission, where a DFT OCC is applied to the first virtual hop. The one or more processors can be configured to cause the network node to obtain a second virtual hop associated with the PUCCH transmission, where the DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, a size of the DFT OCC is based at least in part on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with a physical frequency hopping.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method can include applying a DFT OCC to a first virtual hop associated with a PUCCH transmission. The method can include applying the DFT OCC to a second virtual hop associated with the PUCCH transmission, where the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, where a size of the DFT OCC is based at least in part on the number of OFDM symbols, and where the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network node. The method can include obtaining a first virtual hop associated with a PUCCH transmission, where a DFT OCC is applied to the first virtual hop. The method can include obtaining a second virtual hop associated with the PUCCH transmission, where the DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, a size of the DFT OCC is based at least in part on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, can cause the UE to apply a DFT OCC to a first virtual hop associated with a PUCCH transmission. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to apply the DFT OCC to a second virtual hop associated with the PUCCH transmission, where the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, where a size of the DFT OCC is based at least in part on the number of OFDM symbols, and where the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, can cause the network node to obtain a first virtual hop associated with a PUCCH transmission, where a DFT OCC is applied to the first virtual hop. The set of instructions, when executed by the one or more processors of the network node, can cause the network node to obtain a second virtual hop associated with the PUCCH transmission, where the DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, a size of the DFT OCC is based at least in part on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for applying a DFT OCC to a first virtual hop associated with a PUCCH transmission. The apparatus can include means for applying the DFT OCC to a second virtual hop associated with the PUCCH transmission, where the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, where a size of the DFT OCC is based at least in part on the number of OFDM symbols, and where the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for obtaining a first virtual hop associated with a PUCCH transmission, where a DFT OCC is applied to the first virtual hop. The apparatus can include means for obtaining a second virtual hop associated with the PUCCH transmission, where the DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, a size of the DFT OCC is based at least in part on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

[0015] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0016] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions are not to depart from the scope of the appended claims. The present disclosed concepts are best understood from the below when read in connection with the accompanying drawings. Each figure is provided by way of example of the and therefore should not be considered to limit the scope of the claims. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure.

[0017] While aspects are described in the disclosure by illustration to some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. Techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying sizes, shapes, and constitution. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order that the above-recited features of the present disclosure can be understood in detail, a more particular description will be rendered by reference to various aspects, some of which are illustrated in the which are appended hereto. It is appreciated that the are intended primarily for purposes of illustration and that the description can acknowledge other equally effective aspects. Like reference numerals can be used throughout the to denote like elements.

[0019] FIG. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0020] FIG. 2 is a diagram illustrating an example of a network node in communication with user equipment (UE) in a wireless network, in accordance with the present disclosure. is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0021] FIG. 3 is a diagram illustrating an example disaggregated base station architecture in accordance with the present disclosure.

[0022] FIG. 4 is a diagram illustrating an example of physical uplink control channel (PUCCH) format 1 multiplexing in accordance with the present disclosure.

[0023] FIG. 5 is a diagram illustrating an example of PUCCH multiplexing issues without sequence hopping and an example of PUCCH multiplexing issues with sequence hopping in accordance with the present disclosure.

[0024] FIG. 6 is a diagram illustrating an example of a system including UEs not configured for frequency hopping and UEs configured for frequency hopping in accordance with the present disclosure.

[0025] FIG. 7 is a diagram illustrating an example of using virtual hopping for PUCCH in accordance with the present disclosure.

[0026] FIG. 8 is a diagram illustrating an example involving virtual hopping without sequence hopping and an example involving virtual hopping with sequence hopping in accordance with the present disclosure.

[0027] FIG. 9 is a diagram illustrating an example involving block-level orthogonal cover code (OCC) for virtual hopping without sequence hopping and an example involving block-level OCC for virtual hopping with sequence hopping in accordance with the present disclosure.

[0028] FIG. 10 is a diagram illustrating an example involving legacy discrete Fourier transform (DFT) matrices and an example of DFT matrices computed based on block-level OCC and a half-sized DFT orthogonal cover code (OCC) matrix in accordance with the present disclosure.

[0029] FIG. 11 is a diagram illustrating an example process performed, for example, at a UE or device of a UE in accordance with the present disclosure.

[0030] FIG. 12 is a diagram illustrating an example process performed, for example, at a network node or device of a network node in accordance with the present disclosure.

[0031] FIG. 13 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure.

[0032] FIG. 14 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION

[0033] User equipments (UEs) not configured for frequency hopping have a different discrete Fourier transform (DFT) orthogonal cover code (OCC) size than UEs configured for frequency hopping. For example, the DFT OCC size for UEs with frequency hopping can be half of the DFT OCC size for UEs without frequency hopping. The difference in DFT OCC size between UEs configured for frequency hopping and UEs not configured for frequency hopping can prevent UEs configured for frequency hopping from multiplexing with UEs not configured for frequency hopping. Moreover, if UEs configured for frequency hopping use a different sequence than UEs not configured for frequency hopping, the difference in sequence can also prevent the UEs from multiplexing with each other. The inability of the UEs to multiplex with each other can result in congestion of available bandwidth.

[0034] Various aspects generally relate to physical uplink control channel (PUCCH) transmissions. Some aspects more specifically relate to virtual hopping for PUCCH transmissions. In some examples, a UE not configured for frequency hopping can apply a DFT OCC to a first virtual hop associated with a PUCCH transmission (e.g., a PUCCH format 1 transmission) and apply a DFT OCC to a second virtual hop associated with the PUCCH transmission. The first virtual hop and the second virtual hop can not be associated with a physical frequency hop, can be associated with (e.g., have, include, etc.) a same number of orthogonal frequency-division multiplexing (OFDM) symbols, and can be associated with DFT OCCs having equal sizes. In some aspects, the first virtual hop or the second virtual hop can be multiplexed on a resource block (RB) with a hop of another PUCCH transmission. The hop of the other PUCCH transmission can be transmitted by another UE configured for frequency hopping and can be associated with another DFT OCC having a same size as the DFT OCC of the first virtual hop or the second virtual hop. The virtual hops can use a same demodulation reference signal (DMRS) sequence (e.g., no sequence hopping) or different DMRS sequences (e.g., sequence hopping). In either case, the hop with which the virtual hop (e.g., the first virtual hop or the second virtual hop) is multiplexed can use a same DMRS sequence as the virtual hop. In some aspects, a block-level OCC (e.g., a block OCC code) can be applied to the first virtual hop and the second virtual hop.

[0035] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by applying DFT OCCs to the first virtual hop and the second virtual hop, the described techniques can be used to multiplex the first virtual hop and / or the second virtual hop with a hop of a PUCCH transmission that involves a physical frequency hopping, which can reduce congestion of available bandwidth. For example, the first virtual hop and / or the second virtual hop can have a DFT OCC size that is the same as a DFT OCC size of a hop that involves frequency hopping, which can enable the virtual hop (which is not associated with a physical frequency hopping) to be multiplexed on the same RB as the hop associated with the frequency hopping, thereby saving RB usage. The first virtual hop and the second virtual hop being associated with the same DMRS sequence can enable multiplexing of the virtual hops in a scenario without sequence hopping, and the first virtual hop and the second virtual hop being associated with different DMRS sequences can enable multiplexing of the virtual hops in a scenario with sequence hopping. Block-level OCCs applied to the first virtual hop and the second virtual hop can increase multiplexing capacity (e.g., a maximum number of UEs that can be multiplexed), which would otherwise be reduced (e.g., halved) for users without frequency hopping due to a reduction (e.g., halving) in size of the DFT OCC.

[0036] Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided as illustrative examples so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. As such, various aspects of the disclosure can take many different forms with the scope of the disclosure being substantially limited only by the appended claims. It will be appreciated that any aspect of the disclosure disclosed herein can be implemented by one or more elements of a claim.

[0037] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, among other examples (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0038] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0039] FIG. 1 This is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0040] In some examples, network node 110 is or includes network nodes such as RU that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes such as DU that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes such as CU that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0041] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. FIG. 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. Network nodes may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0042] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device can include more than one base station.

[0043] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. FIG. 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0044] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0045] Network controller 130 may be coupled to or communicate with network node set 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or core network device, or may include a CU or core network device.

[0046] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0047] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0048] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0049] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary device to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0050] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided by frequency or wavelength into various categories, bands, channels, etc. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0051] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0053] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may apply a DFT OCC to a first virtual hop associated with a PUCCH transmission; and apply a DFT OCC to a second virtual hop associated with a PUCCH transmission, wherein the first and second virtual hops are associated with an equal number of OFDM symbols, wherein the size of the DFT OCC is based at least in part on the number of OFDM symbols, and wherein the first and second virtual hops are not associated with physical frequency hopping. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0054] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may obtain a first virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the first virtual hop; and obtain a second virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the second virtual hop, the first and second virtual hops being associated with an equal number of OFDM symbols, the size of the DFT OCC being at least partially based on the number of OFDM symbols, and the first and second virtual hops not being associated with physical frequency hopping. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0055] As indicated above, FIG. 1 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 1 The examples described are different.

[0056] FIG. 2 This is a diagram illustrating an example 200 of communication between a network node 110 and a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with antenna sets 234a to 234t, such as... T One antenna ( T ≥1). UE 120 may be equipped with antenna sets 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0057] At network node 110, transmitting processor 220 may receive data from data source 212 intended for use by UE 120 (or UE set 120). Transmitting processor 220 may select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmitting processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output symbol stream sets (e.g., T Each output symbol stream is provided to the corresponding set of modems 232 (e.g., ...). T Each modem 232a to 232t (shown as modems 232a to 232t) may be used. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t may be used via a corresponding antenna set 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0058] At UE 120, antenna set 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can transmit the received signal set (e.g., R The received signals are provided to the modem set 254 (e.g., REach modem 254 (shown as modems 254a to 254r) may receive a signal, for example, which may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0059] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0060] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, and / or be coupled to one or more transmitting and / or receiving components (such as...). FIG. 2 One or more antenna elements (one or more components in a )

[0061] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). FIG. 7 through FIG. 14 ( ) any aspect of the methods described in the method.

[0062] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., reference). FIG. 7 through FIG. 14 ( ) any aspect of the methods described in the method.

[0063] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or FIG. 2Any other component may perform one or more techniques associated with virtual hops used for PUCCH, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or FIG. 2 Any other component that can execute or direct, for example FIG. 11 Process 1100 FIG. 12 The operation of process 1200 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, these one or more instructions may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). FIG. 11 Process 1100 FIG. 12 The operation of process 1200 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0064] In some aspects, UE 120 includes components for applying DFT OCC to a first virtual hop associated with PUCCH transmission; and / or components for applying DFT OCC to a second virtual hop associated with PUCCH transmission, wherein the first and second virtual hops are associated with an equal number of OFDM symbols, wherein the size of the DFT OCC is at least partially based on the number of OFDM symbols, and wherein the first and second virtual hops are not associated with physical frequency hopping. Components for UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0065] In some aspects, network node 110 includes components for obtaining a first virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the first virtual hop; and / or components for obtaining a second virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the second virtual hop, the first and second virtual hops are associated with an equal number of OFDM symbols, the size of the DFT OCC is at least partially based on the number of OFDM symbols, and the first and second virtual hops are not associated with physical frequency hopping. Components for network node 110 to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0066] In some respects, a single processor can perform all the functions described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors can be the same group of processors or can be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. FIG. 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... FIG. 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0067] Although FIG. 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0068] As indicated above, FIG. 2 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 2 The examples described are different.

[0069] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a converged or decomposed architecture. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5G NB, access points (APs), TRPs, or cells, etc.) or one or more units (or one or more components) that perform base station functions can be implemented as converged base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0070] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0071] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0072] FIG. 3This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a 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 DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0073] Each unit in the cells (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other cells via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other cells via a wireless transmission media, or both.

[0074] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0075] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0076] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

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

[0078] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface that connects one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0079] In some implementations, to generate AI / ML models 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. This information can be utilized by the near-RT RIC 325 and may be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0080] As indicated above, FIG. 3 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 3 The examples described are different.

[0081] FIG. 4 This is an illustration of example 400, which is a multiplexing of PUCCH format 1 according to this disclosure.

[0082] PUCCH format 1 includes a one-bit or two-bit payload with 4-14 OFDM symbols. For a given cell-specific base sequence S of length 12, a one-bit or two-bit payload b can be transmitted as follows: Sequence S1 (which is a base sequence S with a cyclic shift or index CS1) can be transmitted as DMRS on even-numbered OFDM symbols and modulated by payload b on odd-numbered OFDM symbols. For user i, size N / 2 DFT OCC C_i is applied to the DMRS symbols, and size N / 2 DFT OCC C_i is applied to the uplink control information (UCI) symbols. Using a different OCC C_i for another user j allows user i and user j to be multiplexed on the same RB.

[0083] As indicated above, FIG. 4 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 4 The examples described are different.

[0084] FIG. 5 These are illustrations of Example 500 of the PUCCH multiplexing problem without sequence jumps and Example 510 of the PUCCH multiplexing problem with sequence jumps according to this disclosure.

[0085] As shown in Example 500, UEs not configured for frequency hopping have different DFT OCC sizes than UEs configured for frequency hopping. For example, the DFT OCC sizes of UE1 and UE2 (with frequency hopping) are half the DFT OCC sizes of UE3 and UE4 (without frequency hopping). This difference in DFT OCC sizes between UEs configured for frequency hopping and those not configured for frequency hopping prevents multiplexing between them.

[0086] In Example 510, the UEs configured for frequency hopping are also configured for sequence hopping. For example, UE1 and UE2 use S1 for the first frequency hopping and S2 for sequence hopping. However, UE3 and UE4 (which are not configured for frequency hopping) only use S1. The difference in sequence between UEs configured for frequency hopping and those not configured for frequency hopping also prevents UEs configured for frequency hopping from multiplexing with each other.

[0087] As indicated above, FIG. 5 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 5 The examples described are different.

[0088] FIG. 6 This is an illustration of example 600 of a system according to the present disclosure, including a UE not configured for frequency hopping and a UE configured for frequency hopping.

[0089] Many systems (e.g., 5G systems, 6G systems, etc.) include (or will include) UEs with different bandwidth capabilities. For example, the system in Example 600 includes UEs with small bandwidth capabilities (e.g., 5MHz capability) and wideband UEs (e.g., 100MHz capability). Enabling frequency hopping for a UE with small bandwidth capabilities may cause spectrum fragmentation for the wideband UE without achieving frequency hopping gain (due to the small 5MHz hop range). Therefore, many systems may include UEs configured for frequency hopping (e.g., wideband UEs) and UEs not configured for frequency hopping (e.g., UEs with small bandwidth capabilities), as combined above. FIG. 5The UEs discussed are not compatible with multiplexing. Therefore, transmissions from UEs configured for frequency hopping and those not configured for frequency hopping occupy different RBs, which may lead to congestion of available bandwidth.

[0090] As indicated above, FIG. 6 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 6 The examples described are different.

[0091] FIG. 7 This is an illustration of example 700 of using virtual jumps for PUCCH according to this disclosure.

[0092] As shown by reference numeral 710, the UE (e.g., UE 120) applies the DFT OCC to a first virtual hop. The first virtual hop is associated with a PUCCH transmission (e.g., PUCCH format 1 transmission). As shown by reference numeral 720, the UE applies the DFT OCC to a second virtual hop associated with the PUCCH transmission. The first and second virtual hops may be associated with an equal number of OFDM symbols (e.g., having, containing, etc.). In some aspects, the DFT OCC may be an OFDM symbol-level OCC.

[0093] The size of the DFT OCC can be based at least in part on the number of OFDM symbols. For example, the first virtual jump and the second virtual jump can have the same number of OFDM symbols and be associated with DFT OCCs of equal size.

[0094] Virtual hops may not be associated with physical frequency hopping. For example, a UE may transmit two virtual hops on the same frequency. The UE may not be configured for frequency hopping (e.g., the UE may have low bandwidth capabilities). The hop is "virtual" because the UE can treat the virtual hop as an actual frequency hopping for the purpose of applying DFT OCC. For example, the UE may apply DFT OCC individually (e.g., separately) to each virtual hop, rather than applying a larger DFT OCC on both virtual hops.

[0095] As shown by reference numeral 730, the UE may send a first virtual hop, and a network node (e.g., network node 110) may receive the first virtual hop. As shown by reference numeral 740, the UE may send a second virtual hop, and a network node may receive the second virtual hop. On the same frequency (e.g., in the absence of frequency hopping), the UE may send both the first and second virtual hops, and a network node may receive both the first and second virtual hops.

[0096] In some aspects, a hop from another PUCCH transmission (e.g., another PUCCH format 1 transmission) is multiplexed with a first or second virtual hop on an RB. This hop may be associated with another DFT OCC having the same size as the first or second virtual hop. For example, another UE may apply another DFT OCC to a hop from another PUCCH transmission. In some aspects, another UE may transmit a hop, and a network node may receive the hop multiplexed with the first or second virtual hop on an RB.

[0097] Another PUCCH transmission hop can be associated with physical frequency hopping. For example, another PUCCH transmission can be sent by another UE (e.g., a wideband UE) configured for frequency hopping, which sends the hop on a first frequency and another hop of the other PUCCH transmission on a second frequency.

[0098] The UE applies DFT OCC to the first virtual hop and applies DFT OCC to the second virtual hop, and / or the network node obtains the first and second virtual hops, enabling the first and / or second virtual hops to be multiplexed with hops transmitted via PUCCH involving frequency hopping. For example, the first and / or second virtual hops may have the same DFT OCC size as the hops transmitted via PUCCH involving frequency hopping, which allows the virtual hops (which are not associated with physical frequency hopping) to be multiplexed on the same RB as the hops associated with frequency hopping.

[0099] Multiplexing virtual hops (e.g., virtual hops of UEs not configured for frequency hopping) on ​​an RB with other hops can save RB usage. For example, multiplexing virtual hops on an RB with hops associated with frequency hopping (e.g., hops of UEs configured for frequency hopping) allows PUCCH transmissions of UEs not configured for frequency hopping (e.g., UEs that can operate in low bandwidth) to be multiplexed with PUCCH transmissions of UEs configured for frequency hopping (e.g., wideband UEs).

[0100] As indicated above, FIG. 7 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 7 The examples described are different.

[0101] FIG. 8 These are illustrations of example 800, which involves a virtual jump without sequence transitions, and example 810, which involves a virtual jump with sequence transitions, according to this disclosure.

[0102] In Example 800, a first virtual hop is associated with a sequence (e.g., a DMRS sequence), and a second virtual hop is associated with that sequence. For example, UE3 and UE4 use virtual hops. The virtual hop associated with UE3 has the same sequence S1, and the virtual hop associated with UE4 has the same sequence S1. Associating the first and second virtual hops with the sequence enables the reuse of virtual hops in scenarios without sequence transitions.

[0103] A hop multiplexed with either the first or second virtual hop on an RB (e.g., another PUCCH format 1 hop) can be associated with this sequence. For example, a hop associated with UE1 and UE2 (e.g., the actual frequency hopping) also has sequence S1. In some examples, UE3 may transmit a first virtual hop multiplexed with a hop transmitted by UE1, and UE3 may transmit a second virtual hop multiplexed with a hop transmitted by UE2. In some examples, UE4 may transmit a first virtual hop multiplexed with a hop transmitted by UE2, and UE4 may transmit a second virtual hop multiplexed with a hop transmitted by UE1. In some aspects, a network node may receive a hop transmitted by UE1 or UE2 that is multiplexed with a virtual hop transmitted by UE3 or UE4 on the same RB.

[0104] In Example 810, a first virtual hop is associated with a first sequence (e.g., a first DMRS sequence), and a second virtual hop is associated with a second sequence (e.g., a second DMRS sequence different from the first DMRS sequence). For example, the first virtual hop associated with UE3 has sequence S1, and the second virtual hop associated with UE4 has sequence S2. Similarly, the first virtual hop associated with UE4 has sequence S1, and the second virtual hop associated with UE4 has sequence S2. Associating the first and second virtual hops with different sequences enables the reuse of virtual hops in scenarios with sequence transitions.

[0105] In some examples, a hop in another PUCCH transmission (e.g., another PUCCH format 1 transmission) multiplexed with the first virtual hop on the RB can be associated with a first sequence. For example, the first hop associated with UE1 (e.g., actual frequency hopping) can be multiplexed with the first virtual hop of UE3 and also has sequence S1. Similarly, the first hop associated with UE2 (e.g., actual frequency hopping) can be multiplexed with the first virtual hop of UE4 and also has sequence S1. The second hop associated with UE1 (e.g., actual frequency hopping) can be multiplexed with the second virtual hop of UE3 and also has sequence S2. Similarly, the second hop associated with UE1 (e.g., actual frequency hopping) can be multiplexed with the first virtual hop of UE4 and also has sequence S2.

[0106] In some examples, UE3 may send a first virtual hop that can be multiplexed with a first hop sent by UE1, and UE3 may send a second virtual hop that can be multiplexed with a second hop sent by UE2. In some examples, UE4 may send a first virtual hop that can be multiplexed with a first hop sent by UE2, and UE4 may send a second virtual hop that can be multiplexed with a second hop sent by UE1. In some aspects, network nodes may obtain on the same RB a first virtual hop of UE3 multiplexed with a first virtual hop sent by UE1, a second virtual hop of UE3 multiplexed with a second virtual hop sent by UE2, a first virtual hop of UE4 multiplexed with a first virtual hop sent by UE2, or a second virtual hop of UE4 multiplexed with a second virtual hop sent by UE1.

[0107] As indicated above, FIG. 8 This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. FIG. 8 The examples described are different.

[0108] FIG. 9 These are illustrations of Example 900, which relates to a block-level OCC for a virtual jump without sequence transitions, and Example 910, which relates to a block-level OCC for a virtual jump with sequence transitions, according to this disclosure.

[0109] In Examples 900 and 910, block-level OCC (e.g., block-based OCC codes) are applied to the first and second virtual hops. The block-level OCC code can be a virtual hop level code. In Example 900, block-level OCC is applied to virtual hops without sequence transitions (as described above regarding Example 800). FIG. 8 The discussion covers virtual jumps without sequence transitions. In Example 910, block-level OCC is applied to virtual jumps with sequence transitions (as discussed above regarding Example 810). FIG. 8 (The discussion covers virtual hops with sequence transitions). In both Examples 900 and 910, the block-level OCC for the first and second virtual hops applied to UE3 is [1,1] (e.g., "1" is applied to the first virtual hop and "1" is applied to the second virtual hop), and the block-level OCC for the first and second virtual hops applied to UE4 is [1,-1] (e.g., "1" is applied to the first virtual hop and "-1" is applied to the second virtual hop).

[0110] The block-level OCC applied to the first and second virtual hops can increase the multiplexing capacity (e.g., the maximum number of UEs that can be multiplexed). Otherwise, due to the reduction in the size of the DFT OCC (e.g., halving), the multiplexing capacity for users without frequency hopping will be reduced (e.g., halved). Therefore, without reducing the multiplexing capacity, PUCCH transmissions with and without frequency hopping can be orthogonally multiplexed on the same RB.

[0111] As indicated above, FIG. 9 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 9 The examples described are different.

[0112] FIG. 10 These are illustrations of Example 1000, which involves a legacy DFT matrix according to this disclosure, and Example 1010, which involves a matrix computed based on a block-level OCC (e.g., block OCC) and a half-size DFT OCC matrix. In Examples 1000 and 1010, the matrix contains... M / 2 = 6 rows or columns, where M This represents the number of symbols transmitted via PUCCH. Both matrices are 6×6 matrices and can be used to determine the OCC set for one or more UEs.

[0113] In Example 1000, via RRC parameters timeDomainOCC The signal notifies the use of format 1 PUCCH without frequency hopping, and the RRC parameter indicates the magnitude. M The index of the DFT OCC code of / 2. For example, timeDomainOCC The parameter points to a row or column of the old-style matrix. Therefore, timeDomainOCC The parameter can specify rows or columns as OCC C_i for a given UE application.

[0114] As shown in Example 1010, a half-sized DFT OCC matrix (e.g., a DFT(3) matrix containing three rows or columns) is multiplied by the block-level OCC to obtain a 6×6 matrix. Therefore, a 6×6 matrix can be constructed at least in part based on the DFT matrix (e.g., a DFT(3) matrix) and the block-level OCC. The UE can apply the DFT OCC corresponding to the rows or columns of the 6×6 matrix to one or more virtual hops. For example, the UE can apply the DFT OCC from a first DFT(3) matrix within the 6×6 matrix to a first virtual hop and the DFT OCC from a second DFT(3) matrix within the 6×6 matrix to a second virtual hop. Network modes can use RRC parameters. timeDomainOCC Signal the UE to notify which DFT OCC will be applied to the virtual hop.

[0115] In the first aspect of signaling which DFT OCC will be applied to the virtual hop, the network node may output an indication of a first index associated with the block-level OCC (e.g., the block code index) and a second index associated with the DFT OCC (e.g., the index of a half-size DFT OCC), and the UE may receive this indication. Therefore, timeDomainOCC Parameters can be used to signal the index of half the size of the DFT OCC and the index of the block code. For example, timeDomainOCCThe parameter can be used to determine the first index based on the following relationship: block code index = timeDomainOCC mod 2. timeDomainOCC The output of mod 2 can be binary (e.g., 0 or 1). For example, if the output is 0, block-level OCC [1,1] can be applied to the virtual jump, and if the output is 1, block-level OCC [1,-1] can be applied to the virtual jump. timeDomainOCC The parameter can be used to determine the second index based on the following relationship: index of size M / 4 OCC = floor( timeDomainOCC / 2). The second index can point to one of the three rows of the DFT(3) matrix, which is multiplied by the block-level OCC, such as FIG. 10 As shown. Therefore, it is possible to base it on the RRC parameters. timeDomainOCC The first and second indices are derived to calculate the DFT OCC.

[0116] Secondly, the network node can output an indication (e.g., a single index) associated with the block-level OCC and DFT OCC, and the UE can receive this indication. For example, as FIG. 10 As shown, an index can indicate a row or column in a matrix (e.g., a 6×6 matrix) constructed at least in part based on the DFT matrix (e.g., a DFT(3) matrix) and block-level OCCs. The row or column may contain DFT OCCs (e.g., DFT OCCs to be applied to virtual jumps). For example, timeDomainOCC The parameter can point to a value with size. M A 6×6 OCC matrix of size M / 4. For example, the block code index and the index of size M / 4 OCC can be combined to point to a matrix of size M / 4. M A single index of a row or column in a 6×6 OCC matrix of size / 2. Therefore, the DFT OCC can be calculated based on a single index, which is based on the RRC parameter. timeDomainOCC .

[0117] As indicated above, FIG. 10 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 10 The examples described are different.

[0118] FIG. 11 This is a diagram illustrating an example process 1100 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1100 is an example in which a device or UE (e.g., UE 120) performs operations associated with a virtual hop for PUCCH.

[0119] like FIG. 11 As shown, in some aspects, process 1100 may include: applying DFT OCC to a first virtual hop associated with PUCCH transmission (box 1110). For example, the UE (e.g., using...) FIG. 13The described communication manager 1306 can apply DFTOCC to the first virtual hop associated with PUCCH transmission, as described above.

[0120] like FIG. 11 Further shown, in some aspects, process 1100 may include: applying a DFT OCC to a second virtual hop associated with a PUCCH transmission, wherein the first and second virtual hops are associated with an equal number of OFDM symbols, wherein the size of the DFT OCC is at least partially based on the number of OFDM symbols, and wherein the first and second virtual hops are not associated with physical frequency hopping (box 1120). For example, a UE (e.g., using...) FIG. 13 The described communication manager 1306 can apply DFTOCC to a second virtual hop associated with PUCCH transmission, wherein the first and second virtual hops are associated with an equal number of OFDM symbols, wherein the size of the DFT OCC is based at least in part on the number of OFDM symbols, and wherein the first and second virtual hops are not associated with physical frequency hopping, as described above.

[0121] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0122] In a first aspect, the PUCCH transmission is a first PUCCH transmission, the DFT OCC is a first DFT OCC, the hop of the second PUCCH transmission that is multiplexed on the RB with the first virtual hop or the second virtual hop is associated with the second DFT OCC, and the size of the second DFT OCC is the size of the first DFT OCC.

[0123] In the second aspect, either alone or in combination with the first aspect, the hop transmitted by the second PUCCH is associated with physical frequency hopping.

[0124] In a third aspect, the first virtual jump is associated with the DMRS sequence alone or in combination with one or more of the first and second aspects, and the second virtual jump is associated with the DMRS sequence.

[0125] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the PUCCH transmission is a first PUCCH transmission, and the hop of the second PUCCH transmission that is multiplexed on the RB with the first virtual hop or the second virtual hop is associated with the DMRS sequence.

[0126] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first virtual jump is associated with the first DMRS sequence, and the second virtual jump is associated with the second DMRS sequence, which is different from the first DMRS sequence.

[0127] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the PUCCH transmission is a first PUCCH transmission, and the hop of the second PUCCH transmission is multiplexed on the RB with the first virtual hop and associated with the first DMRS sequence, or the hop is multiplexed on the RB with the second virtual hop and associated with the second DMRS sequence.

[0128] In the seventh aspect, block-level OCC is applied to the first virtual hop and the second virtual hop, either alone or in combination with one or more of the first to sixth aspects.

[0129] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1100 includes receiving indications of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

[0130] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1100 includes receiving an indication of an index associated with the block-level OCC and the DFT OCC.

[0131] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the index indicates a row or column in a matrix constructed at least in part based on the DFT matrix and the block-level OCC, and the row or column contains the DFT OCC.

[0132] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the DFTOCC is an OFDM symbol-level OCC.

[0133] In the twelfth aspect, the PUCCH transmission is a PUCCH format 1 transmission, either alone or in combination with one or more of the first to eleventh aspects.

[0134] although FIG. 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... FIG. 11 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in process 1100 may be executed in parallel.

[0135] FIG. 12This is a diagram illustrating an example process 1200 performed, for example, at a network node or a device of a network node according to the present disclosure. Example process 1200 is an example in which a device or network node (e.g., network node 110) performs operations associated with a virtual hop for PUCCH.

[0136] like FIG. 12 As shown, in some aspects, process 1200 may include: obtaining a first virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the first virtual hop (box 1210). For example, a network node (e.g., using...) FIG. 14 The described receiving component 1402 and / or communication manager 1406 may obtain a first virtual hop associated with PUCCH transmission, wherein DFTOCC is applied to the first virtual hop as described above.

[0137] like FIG. 12 Further, in some aspects, process 1200 may include: obtaining a second virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the second virtual hop, the first and second virtual hops are associated with an equal number of OFDM symbols, the size of the DFT OCC is at least partially based on the number of OFDM symbols, and the first and second virtual hops are not associated with physical frequency hopping (box 1220). For example, network nodes (e.g., using...) FIG. 14 The described receiving component 1402 and / or communication manager 1406 may obtain a second virtual hop associated with PUCCH transmission, wherein a DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, the size of the DFT OCC is at least partially based on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with physical frequency hopping, as described above.

[0138] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0139] In a first aspect, the PUCCH transmission is a first PUCCH transmission, and the DFT OCC is a first DFT OCC. The process 1200 includes obtaining a hop of a second PUCCH transmission that is multiplexed on the RB with the first virtual hop or the second virtual hop, the hop of the second PUCCH transmission being associated with a second DFT OCC, and the size of the second DFT OCC being the size of the first DFT OCC.

[0140] In the second aspect, either alone or in combination with the first aspect, the hop transmitted by the second PUCCH is associated with physical frequency hopping.

[0141] In a third aspect, the first virtual jump is associated with the DMRS sequence alone or in combination with one or more of the first and second aspects, and the second virtual jump is associated with the DMRS sequence.

[0142] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the PUCCH transmission is a first PUCCH transmission, and process 1200 includes obtaining a hop on the RB that is multiplexed with the first virtual hop or the second virtual hop for a second PUCCH transmission, and the hop is associated with the DMRS sequence.

[0143] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first virtual jump is associated with the first DMRS sequence, and the second virtual jump is associated with the second DMRS sequence, which is different from the first DMRS sequence.

[0144] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the PUCCH transmission is a first PUCCH transmission, and process 1200 includes obtaining a hop for a second PUCCH transmission, and the hop for the second PUCCH transmission is multiplexed on an RB with the first virtual hop and associated with the first DMRS sequence, or the hop for the second PUCCH transmission is multiplexed on an RB with the second virtual hop and associated with the second DMRS sequence.

[0145] In the seventh aspect, block-level OCC is applied to the first virtual hop and the second virtual hop, either alone or in combination with one or more of the first to sixth aspects.

[0146] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1200 includes outputting indications of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

[0147] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1200 includes outputting an indication of the index associated with the block-level OCC and the DFT OCC.

[0148] although FIG. 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... FIG. 12 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in process 1200 may be executed in parallel.

[0149] FIG. 13This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be a UE, or a UE may include device 1300. In some aspects, device 1300 includes a receiving component 1302, a transmitting component 1304, and / or a communication manager 1306 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1306 is combined with... FIG. 1 The described communication manager 140. As shown, device 1300 can communicate with another device 1308 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1302 and transmitting component 1304.

[0150] In some respects, device 1300 can be configured to perform the functions described herein. FIG. 7 through FIG. 10 The described one or more operations. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as FIG. 11 The process 1100. In some respects, FIG. 13 The illustrated device 1300 and / or one or more components may include a combination FIG. 2 One or more components of the described UE. Additionally or alternatively, FIG. 13 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0151] Receiver 1302 may receive communications from device 1308, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... FIG. 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0152] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1308. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1308. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1308. In some aspects, transmitting component 1304 may include combinations of... FIG. 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1304 may co-located with the receive component 1302 in one or more transceivers.

[0153] The communication manager 1306 may support the operation of the receiving component 1302 and / or the transmitting component 1304. For example, the communication manager 1306 may receive information associated with configuring the reception of communications by the receiving component 1302 and / or the transmission of communications by the transmitting component 1304. Additionally or alternatively, the communication manager 1306 may generate control information and / or provide control information to the receiving component 1302 and / or the transmitting component 1304 to control the reception and / or transmission of communications.

[0154] The communication manager 1306 may apply a DFT OCC to a first virtual hop associated with a PUCCH transmission. The communication manager 1306 may also apply a DFT OCC to a second virtual hop associated with a PUCCH transmission, wherein the first and second virtual hops are associated with an equal number of OFDM symbols, wherein the size of the DFT OCC is at least partially based on the number of OFDM symbols, and wherein the first and second virtual hops are not associated with physical frequency hopping.

[0155] The receiving component 1302 can receive indications of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

[0156] The receiving component 1302 can receive an indication of an index associated with the block-level OCC and the DFT OCC.

[0157] FIG. 13 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 13 The components shown are compared to components with more components, fewer components, different components, or components arranged in a different way. Furthermore, FIG. 13The two or more components shown can be implemented within a single component, or FIG. 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 13 The collection of (one or more) components shown can be executed as described by FIG. 14 The other set of components shown performs one or more functions.

[0158] FIG. 1 This is a diagram of an example device 1400 for wireless communication according to the present disclosure. Device 1400 may be a network node, or a network node may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and / or a communication manager 1406 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is combined with... FIG. 7 through FIG. 10 The described communication manager 150. As shown, device 1400 can communicate with another device 1408 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1402 and transmitting component 1404.

[0159] In some respects, device 1400 can be configured to perform the functions described herein. FIG. 12 One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as FIG. 14 The process is 1200. In some respects, FIG. 2 The device 1400 and / or one or more components shown may include a combination FIG. 14 One or more components of the described network node. Additionally or alternatively, FIG. 2 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0160] Receiver 1402 may receive communications from device 1408, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1400. In some aspects, receiver 1402 may include combinations of... FIG. 2 The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1402 and / or transmitter component 1404 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals from device 1400 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0161] Transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1408. In some aspects, one or more other components of device 1400 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1408. In some aspects, transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1408. In some aspects, transmitting component 1404 may include combinations of... FIG. 14 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1404 may co-located with the receive component 1402 in one or more transceivers.

[0162] The communication manager 1406 may support the operation of the receiving component 1402 and / or the transmitting component 1404. For example, the communication manager 1406 may receive information associated with configuring the reception of communications by the receiving component 1402 and / or the transmission of communications by the transmitting component 1404. Additionally or alternatively, the communication manager 1406 may generate control information and / or provide control information to the receiving component 1402 and / or the transmitting component 1404 to control the reception and / or transmission of communications.

[0163] The receiving component 1402 can obtain a first virtual hop associated with PUCCH transmission, wherein a DFT OCC is applied to the first virtual hop. The receiving component 1402 can obtain a second virtual hop associated with PUCCH transmission, wherein a DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, the size of the DFT OCC is at least partially based on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with physical frequency hopping.

[0164] The sending component 1404 can output indications of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

[0165] The sending component 1404 can output an indication of the index associated with the block-level OCC and DFT OCC.

[0166] FIG. 14 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 14 The components shown are compared to components with more components, fewer components, different components, or components arranged in a different way. Furthermore, FIG. 14 The two or more components shown can be implemented within a single component, or FIG. 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, ​ The set (one or more) components shown are executable descriptions by ​ The other component shown performs one or more functions.

[0167] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a UE, the method comprising: applying a DFT OCC to a first virtual hop associated with a PUCCH transmission; and applying the DFT OCC to a second virtual hop associated with the PUCCH transmission, wherein the first virtual hop and the second virtual hop are associated with an equal number of OFDM symbols, wherein the size of the DFT OCC is at least partially based on the number of OFDM symbols, and wherein the first virtual hop and the second virtual hop are not associated with physical frequency hopping.

[0168] Aspect 2: According to the method of aspect 1, wherein the PUCCH transmission is a first PUCCH transmission, wherein the DFT OCC is a first DFT OCC, wherein the hop multiplexed on the RB by the second PUCCH transmission with the first virtual hop or the second virtual hop is associated with a second DFT OCC, and wherein the size of the second DFT OCC is the size of the first DFT OCC.

[0169] Aspect 3: According to the method of aspect 2, wherein the hop transmitted by the second PUCCH is associated with physical frequency hopping.

[0170] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first virtual hop is associated with a DMRS sequence, and the second virtual hop is associated with the DMRS sequence.

[0171] Aspect 5: According to the method of aspect 4, wherein the PUCCH transmission is a first PUCCH transmission, and wherein the hop of the second PUCCH transmission that is multiplexed on the RB with the first virtual hop or the second virtual hop is associated with the DMRS sequence.

[0172] Aspect 6: The method according to any one of Aspects 1 to 3, wherein the first virtual jump is associated with a first DMRS sequence and the second virtual jump is associated with a second DMRS sequence, the second DMRS sequence being different from the first DMRS sequence.

[0173] Aspect 7: According to the method of aspect 6, wherein the PUCCH transmission is a first PUCCH transmission, and wherein the hop of the second PUCCH transmission is multiplexed with the first virtual hop on the RB and associated with the first DMRS sequence, or the hop is multiplexed with the second virtual hop on the RB and associated with the second DMRS sequence.

[0174] Aspect 8: The method according to any one of Aspects 1 to 7, wherein block-level OCC is applied to the first virtual hop and the second virtual hop.

[0175] Aspect 9: According to the method of aspect 8, the method further includes: receiving an indication of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

[0176] Aspect 10: The method according to aspect 8, the method further comprising: receiving an indication of an index associated with the block-level OCC and the DFT OCC.

[0177] Aspect 11: According to the method of aspect 10, wherein the index indicates a row or column in a matrix constructed at least in part based on the DFT matrix and the block-level OCC, and wherein the row or column contains the DFT OCC.

[0178] Aspect 12: The method according to aspects 1 to 11, wherein the DFT OCC is an OFDM symbol-level OCC.

[0179] Aspect 13: The method according to aspects 1 to 12, wherein the PUCCH transmission is PUCCH format 1 transmission.

[0180] Aspect 14: A method for wireless communication performed by a network node, the method comprising: obtaining a first virtual hop associated with a PUCCH transmission, wherein a DFT OCC is applied to the first virtual hop; and obtaining a second virtual hop associated with the PUCCH transmission, wherein a DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop being associated with an equal number of OFDM symbols, the size of the DFT OCC being at least partially based on the number of OFDM symbols, and the first virtual hop and the second virtual hop not being associated with physical frequency hopping.

[0181] Aspect 15: The method according to aspect 14, wherein the PUCCH transmission is a first PUCCH transmission, and wherein the DFT OCC is a first DFT OCC, the method further comprising: obtaining a hop of a second PUCCH transmission multiplexed on an RB with the first virtual hop or the second virtual hop, wherein the hop of the second PUCCH transmission is associated with a second DFT OCC, and wherein the size of the second DFT OCC is the size of the first DFT OCC.

[0182] Aspect 16: According to the method of aspect 15, wherein the hop transmitted by the second PUCCH is associated with physical frequency hopping.

[0183] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the first virtual hop is associated with a DMRS sequence, and the second virtual hop is associated with the DMRS sequence.

[0184] Aspect 18: The method according to aspect 17, wherein the PUCCH transmission is a first PUCCH transmission, the method further comprising: obtaining a hop of a second PUCCH transmission multiplexed on an RB with the first virtual hop or the second virtual hop, wherein the hop is associated with the DMRS sequence.

[0185] Aspect 19: The method according to any one of Aspects 14 to 16, wherein the first virtual jump is associated with a first DMRS sequence and the second virtual jump is associated with a second DMRS sequence, the second DMRS sequence being different from the first DMRS sequence.

[0186] Aspect 20: The method according to aspect 19, wherein the PUCCH transmission is a first PUCCH transmission, the method further comprising: obtaining a hop of a second PUCCH transmission, wherein the hop of the second PUCCH transmission is multiplexed with the first virtual hop on an RB and associated with the first DMRS sequence, or wherein the hop of the second PUCCH transmission is multiplexed with the second virtual hop on an RB and associated with the second DMRS sequence.

[0187] Aspect 21: The method according to any one of Aspects 14 to 20, wherein block-level OCC is applied to the first virtual hop and the second virtual hop.

[0188] Aspect 22: According to the method of aspect 21, the method further includes: outputting an indication of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

[0189] Aspect 23: The method according to aspect 21 further includes: outputting an indication of an index associated with the block-level OCC and the DFT OCC.

[0190] Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 23.

[0191] Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0192] Aspect 26: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 23.

[0193] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 23.

[0194] Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including, when executed by one or more processors of a device, causing the device to perform one or more of the methods described in one or more of aspects 1 to 23.

[0195] Aspect 29: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0196] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0197] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented through various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referred to in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0198] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0199] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0200] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase referring to “at least one of” the list of entries means any combination of these entries, including a single member. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0201] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Additionally, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Additionally, as used herein, the terms “having” and the like are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the UE to: apply a discrete Fourier transform (DFT) orthogonal cover code (OCC) to a first virtual hop associated with a physical uplink control channel (PUCCH) transmission; and apply the DFT OCC to a second virtual hop associated with the PUCCH transmission, wherein the first virtual hop and the second virtual hop are associated with an equal number of orthogonal frequency-division multiplexing (OFDM) symbols, wherein a size of the DFT OCC is based at least in part on the number of OFDM symbols, and wherein the first virtual hop and the second virtual hop are not associated with a physical frequency hopping.

2. The UE of claim 1, wherein the PUCCH transmission is a first PUCCH transmission, wherein the DFT OCC is a first DFT OCC, wherein a hop of a second PUCCH transmission that is multiplexed on a resource block (RB) with the first virtual hop or the second virtual hop is associated with a second DFT OCC, and wherein a size of the second DFT OCC is the size of the first DFT OCC.

3. The UE of claim 2, wherein the hop of the second PUCCH transmission is associated with a physical frequency hopping.

4. The UE of claim 1, wherein the first virtual hop is associated with a demodulation reference signal (DMRS) sequence and the second virtual hop is associated with the DMRS sequence.

5. The UE of claim 4, wherein the PUCCH transmission is a first PUCCH transmission, and wherein a hop of a second PUCCH transmission that is multiplexed on a resource block (RB) with the first virtual hop or the second virtual hop is associated with the DMRS sequence.

6. The UE of claim 1, wherein the first virtual hop is associated with a first demodulation reference signal (DMRS) sequence and the second virtual hop is associated with a second DMRS sequence that is different from the first DMRS sequence.

7. The UE of claim 6, wherein the PUCCH transmission is a first PUCCH transmission, and wherein a hop of a second PUCCH transmission is multiplexed on a resource block (RB) with the first virtual hop and is associated with the first DMRS sequence or the hop is multiplexed on the RB with the second virtual hop and is associated with the second DMRS sequence.

8. The UE of claim 1, wherein a block-level OCC is applied to the first virtual hop and the second virtual hop.

9. The UE of claim 8, wherein the one or more processors are further configured to cause the UE to: receive an indication of a first index associated with the block-level OCC and a second index associated with the DFT OCC.

10. The UE of claim 8, wherein the one or more processors are further configured to cause the UE to: receive an indication of an index associated with the block-level OCC and the DFT OCC.

11. The UE of claim 10, wherein the index indicates a row or column in a matrix constructed based at least in part on a DFT matrix and the block-level OCC, and wherein the row or column contains the DFT OCC.

12. The UE of claim 1, wherein the DFT OCC is an OFDM symbol-level OCC.

13. The UE of claim 1, wherein the PUCCH transmission is a PUCCH format 1 transmission.

14. A network node for wireless communication, the network node comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: obtain a first virtual hop associated with a physical uplink control channel (PUCCH) transmission, wherein a discrete Fourier transform (DFT) orthogonal cover code (OCC) is applied to the first virtual hop; and obtain a second virtual hop associated with the PUCCH transmission, wherein the DFT OCC is applied to the second virtual hop, the first virtual hop and the second virtual hop are associated with an equal number of orthogonal frequency-division multiplexing (OFDM) symbols, a size of the DFT OCC is based at least in part on the number of OFDM symbols, and the first virtual hop and the second virtual hop are not associated with a physical frequency hop.

15. The network node of claim 14, wherein the PUCCH transmission is a first PUCCH transmission, wherein the DFT OCC is a first DFT OCC, and wherein the one or more processors are further configured to cause the network node to: obtain a hop on a resource block (RB) of a second PUCCH transmission that is multiplexed with the first virtual hop or the second virtual hop, wherein the hop of the second PUCCH transmission is associated with a second DFT OCC, and wherein a size of the second DFT OCC is the size of the first DFT OCC.

16. The network node of claim 14, wherein the first virtual hop is associated with a demodulation reference signal (DMRS) sequence and the second virtual hop is associated with the DMRS sequence.

17. The network node of claim 14, wherein the first virtual hop is associated with a first demodulation reference signal (DMRS) sequence and the second virtual hop is associated with a second DMRS sequence, the second DMRS sequence being different from the first DMRS sequence.

18. The network node of claim 14, wherein a block-level OCC is applied to the first virtual hop and the second virtual hop.

19. A method of wireless communication performed by a user equipment (UE), the method comprising: applying a discrete Fourier transform (DFT) orthogonal cover code (OCC) to a first virtual hop associated with a physical uplink control channel (PUCCH) transmission; and applying the DFT OCC to a second virtual hop associated with the PUCCH transmission, wherein the first virtual hop and the second virtual hop are associated with an equal number of orthogonal frequency division multiplexing (OFDM) symbols, wherein a size of the DFT OCC is based at least in part on the number of OFDM symbols, and wherein the first virtual hop and the second virtual hop are not associated with a physical frequency hopping.

20. The method of claim 19, wherein the PUCCH transmission is a first PUCCH transmission, wherein the DFT OCC is a first DFT OCC, wherein a hop on a resource block (RB) that multiplexes with the first virtual hop or the second virtual hop for a second PUCCH transmission is associated with a second DFT OCC, and wherein a size of the second DFT OCC is the size of the first DFT OCC.

Images