WO2018175578A1 - Attribution de ressources pour canal de commande de liaison montante - Google Patents

Attribution de ressources pour canal de commande de liaison montante Download PDF

Info

Publication number
WO2018175578A1
WO2018175578A1 PCT/US2018/023559 US2018023559W WO2018175578A1 WO 2018175578 A1 WO2018175578 A1 WO 2018175578A1 US 2018023559 W US2018023559 W US 2018023559W WO 2018175578 A1 WO2018175578 A1 WO 2018175578A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
wtru
ucrs
prb
information
Prior art date
Application number
PCT/US2018/023559
Other languages
English (en)
Inventor
Shahrokh Nayeb Nazar
Seyed Mohsen HOSSEINIAN
Boroujeni Mahmoud THERZADEH
Afshin Haghighat
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2018175578A1 publication Critical patent/WO2018175578A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/006—Quality of the received signal, e.g. BER, SNR, water filling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path

Definitions

  • a fifth generation of mobile communications may be referred to as 5G.
  • a previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).
  • Mobile wireless communications may implement a variety of radio access technologies (RATs), such as New Radio (NR).
  • RATs such as New Radio (NR).
  • Use cases for NR may include, for example, extreme Mobile Broadband (eMBB), Ultra High Reliability and Low Latency Communications (URLLC) and massive Machine Type Communications (mMTC).
  • eMBB extreme Mobile Broadband
  • URLLC Ultra High Reliability and Low Latency Communications
  • mMTC massive Machine Type Communications
  • a wireless transmit/receive unit may be configured to provide uplink control information (UCI) in one or more Uplink Control Resource Sets (UCRSs).
  • UCI uplink control information
  • UCRS Uplink Control Resource Sets
  • a UCRS may comprise one or more Resource Blocks (RBs) (e.g., Physical Resource Blocks (PRBs)) in a frequency domain spanning over one or more OFDM symbols in a time domain.
  • RBs Resource Blocks
  • PRBs Physical Resource Blocks
  • An UL control channel e.g., a Physical Uplink Control Channel (PUCCH)
  • PUCCH Physical Uplink Control Channel
  • a WTRU may derive a UCRS configuration and/or may be provided with a UCRS configuration (e.g., via Downlink Control Information (DCI) or higher layer signaling) by a transmission/reception point (TRP).
  • UCCH signals may be provided on different RBs or multiplexed on the same RB.
  • a UCCH may be multiplexed with an uplink shared channel (USCH), e.g., a Physical Uplink Shared Channel (PUSCH), for example on the same RB.
  • Interference for a short UCCH signal may be randomized, for example, by distributing a short UCCH signal to different RBs.
  • Implementation features may include multi-slot short PUCCH hopping, spreading-based multi-bit short PUCCH and overlapping ultra-reliable low latency communications (URLLC) PUCCH and enhanced Mobile Broadband (eMBB) PUSCH.
  • URLLC ultra-reliable low latency communications
  • eMBB enhanced Mobile Broadband
  • a WTRU may receive higher layer signaling, which may be used to configure a UCRS.
  • the higher layers signaling may include orthogonal frequency division-multiplexing (OFDM) information.
  • the UCRS may comprise a PRB, which may be used for the transmission of PUCCH information.
  • the PUCCH information may be transmitted using a short format configuration.
  • the PUCCH information may be transmitted using the short format configuration if the transmission has a short duration (e.g., a duration that is less than or equal to two OFDM symbols).
  • the PUCCH information may be transmitted using a long format configuration.
  • the PUCCH information may be transmitted using the long format configuration if the transmission has a long duration (e.g., a duration that is more than two OFM symbols).
  • FIG. 1 A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A.
  • WTRU wireless transmit/receive unit
  • FIG. 1 C is a system diagram of an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A.
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram of further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A.
  • FIG. 2 is an example configuration of Uplink Control Resource Sets (UCRSs) in a system based on a subband approach.
  • UCRSs Uplink Control Resource Sets
  • FIG. 3 is an example of multiplexing short Physical Uplink Control Channel (PUCCH) and long PUCCH in a mixed Physical Resource Block (PRB).
  • PUCCH Physical Uplink Control Channel
  • PRB Physical Resource Block
  • FIG. 4 is an example associated with PUCCH transmission on mini-slots.
  • FIG. 5 is an example of multiplexing Physical Uplink Shared Channel (PUSCH) and PUCCH on the same one or more PRBs.
  • PUSCH Physical Uplink Shared Channel
  • FIG. 6 is an example associated with interference randomization for a short PUCCH.
  • FIG. 7 is an example associated with interference randomization for a short PUCCH.
  • FIG. 8 is an example associated with aggregated mini-slot short PUCCH hopping.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 1 14b.
  • Each of the base stations 1 14a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 1 10, and/or the other networks 112.
  • the base stations 1 14a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 1 14a may include three transceivers, e.g., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 1 14a, 1 14b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 1 14a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/1 16/1 17 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • NR New Radio
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (e.g., Wireless Fidelity (WiFi), IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV- DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 e.g., Wireless Fidelity (WiFi)
  • IEEE 802.16 e.g., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV- DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE- A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 1 14b may have a direct connection to the Internet 1 10.
  • the base station 1 14b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/1 13 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common
  • the networks 1 12 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 1 12 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/1 13 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 1 18 may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 1 18 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 1 18 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 1 16.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ M IMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 1 16.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 1 18 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 1 18 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 1 18 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 1 14a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
  • the processor 1 18 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the el ⁇ lode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers [0049]
  • the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 1 12 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11 e DLS or an 802.1 1z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an "ad- hoc" mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.1 1 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 ⁇ , and 802.11 ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 ⁇ , 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 1 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 1 15 according to an embodiment.
  • the RAN 1 13 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 1 13 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 162 may provide a control plane function for switching between the RAN 1 13 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 1 15 via an N1 1 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet- based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 1 13 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 1 15 and the PSTN 108.
  • the CN 1 15 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • IMS IP multimedia subsystem
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • Uplink Control Information may comprise, for example, numerous control and status information indicators that may facilitate transmission procedures at a physical layer.
  • a UCI may contain a Hybrid Automatic Retransmission Request (HARQ) Acknowledgement or Negative Acknowledgement (ACK/NACK) that may be used to indicate whether a HARQ was properly received.
  • UCI may (e.g., also) include a Channel Quality Indicator (CQI), which may serve as a measurement of a communication quality of a wireless channel.
  • CQI Channel Quality Indicator
  • a CQI for a given channel may depend on, for example, a type of modulation scheme that may be used by a communications system.
  • UCI may include a Scheduling Request (SR), which may serve to request radio transmission resources for an upcoming downlink (DL) or uplink (UL) transmission.
  • UCI may comprise a Precoding Matrix Indicator (PMI) or Rank Indicator (Rl) for downlink or uplink transmission.
  • PMI may be used to facilitate communication over multiple data streams and signal interpretation at the physical layer, for example, by indicating a designated precoding matrix.
  • An Rl may indicate, for example, a number of layers (e.g., a maximum number of layers) that may be used for spatial multiplexing in a communication system.
  • a wireless transmit/receive unit (WTRU) or User Equipment (UE) may transmit UCI to a network and/or a base station, for example, to provide a physical layer with information that may facilitate wireless communication.
  • WTRU Wireless transmit/receive unit
  • UE User Equipment
  • a UCI (e.g., in New Radio (NR)) may be transmitted, for example, in a Physical Uplink Control Channel (PUCCH).
  • a PUCCH may be transmitted in a short duration (e.g., one or two OFDM symbols), for example, around the last transmitted UL symbol(s) of a slot, or in long duration over multiple (e.g., more than two OFDM symbols) UL symbols, e.g., to improve coverage.
  • a UL control channel may be, for example, frequency-division-multiplexed with an UL data channel within a slot.
  • a WTRU may be assigned a PUCCH resource for UCI transmission.
  • a (e.g., each) PUCCH resource may include, for example, time, frequency and (e.g., when applicable) code domains.
  • UL control resource allocation may be provided (e.g., may be efficiently provided in NR).
  • UL resource allocation may be signaled to a WTRU.
  • Implementations may be provided herein, which may reduce signaling overhead (e.g., in NR).
  • Multiple (e.g., two) PUCCH categories may be defined (e.g., short PUCCH and long PUCCH).
  • Implementations may be provided herein, which may multiplex categories of PUCCHs (e.g., may efficiently multiplex different categories of PUCCHs) with various durations in frequency and time. Interference randomization may be provided, e.g., for short and long PUCCH.
  • Implementations may provide interference randomization that may, for example, be specific to each PUCCH category.
  • a PUCCH may carry, for example, hybrid-ARQ acknowledgements (HARQ ACKs), Channel State Information (CSI) reports (e.g., including beamforming information) and scheduling requests (SR).
  • An Uplink Control Resource Set (UCRS) may comprise, for example, one or more Physical Resource Blocks (PRBs) in the frequency domain that may span one or more OFDM symbols in the time domain.
  • PRBs Physical Resource Blocks
  • PUCCH may be transmitted over one or more UCRSs.
  • a WTRU may transmit uplink control information (e.g., PUCCH information) in one or more UCRSs.
  • PRBs that may comprise a UCRS may be contiguous (e.g., localized) in the frequency domain, for example, to maximize UL precoding/beamforming gain and/or UL frequency scheduling gain.
  • PRBs comprising UCRS e.g., PUCCH RBs
  • PRBs comprising UCRS may (e.g., may alternatively) be non-contiguous (e.g., distributed) in the frequency domain, for example, to achieve frequency diversity gain, such as when accurate channel estimation may not be available for an uplink to achieve an acceptable UL beamforming/scheduling gain.
  • UCRS bandwidth may be, for example, as small as a single PRB (e.g., for power limited WTRUs) or may span an entire system BW (e.g., to maximize frequency diversity gain).
  • a WTRU may transmit an uplink control channel (e.g., PUCCH) on one or more PRBs, for example, when UCRS may span multiple PRBs.
  • PUCCH uplink control channel
  • a WTRU may be configured with one or more UCRS, for example, depending on the type of UL control channel information (e.g., CSI, HARQ ACK, SR, etc.).
  • a WTRU may transmit a PUCCH with a short duration on a UCRS (e.g., one UCRS) and a PUCCH with a long duration on a different UCRS.
  • a WTRU may transmit a PUCCH with a short duration and a PUCCH with a long duration on a single UCRS, for example, which may provide efficient utilization of UL resources.
  • a UCRS (e.g., each UCRS) may be configured to be localized or distributed.
  • a WTRU may (e.g., for coverage limited WTRUs) transmit a PUCCH with a long duration on a distributed UCRS while a WTRU may (e.g., for WTRUs with good channel conditions) transmit a PUCCH with a short duration on a localized UCRS, e.g., to take advantage of beamforming gain.
  • Uplink control resource set signaling may be provided.
  • a WTRU may receive an assigned configuration for UCRS, for example, from a transmission/reception point (TRP), such as a gNodeB (gNB).
  • TRP transmission/reception point
  • gNB gNodeB
  • a configuration may be assigned, for example, semi-statically (e.g., through higher layer signaling), dynamically or a combination thereof.
  • a WTRU may derive RB allocations for a given UCRS configuration (e.g., semi-statically), for example, through higher layer signaling.
  • a WTRU may derive OFDM symbol indices for a given UCRS configuration (e.g., dynamically), for example, through DCI signaling.
  • a WTRU may (e.g., for a given UCRS) derive UCRS configuration information from a 2- dimensional bitmap.
  • a first bitmap may carry information regarding a PRB, a set of PRBs or subband comprising the UCRS.
  • a second bitmap may carry information regarding indices of one or more OFDM symbols that may be reserved for a UCRS, e.g., at the end of each slot/mini-slot/subframe.
  • an entire system BW may be split to form multiple sets of PRBs.
  • a (e.g., each) PRB set may be physically contiguous or physically non-contagious but logically contiguous.
  • a (e.g., each) UCRS may comprise one or more PRB sets.
  • a size of a (e.g., each) PRB set may be a function of, for example, system bandwidth, which may be pre-specified (e.g. , known to gNB and WTRU).
  • an entire system BW may be divided into multiple subbands.
  • a UCRS (e.g., each UCRS) may comprise one or more subbands.
  • a bitmap may be smaller (e.g., compared to the previous example).
  • a bitmap may have a lower signaling overhead, for example, by defining a relatively large subband compared to system BW.
  • Subband size may be (e.g., may also be) a function of the system bandwidth, which may be pre-specified (e.g., known to gNB and WTRU).
  • FIG. 2 is an example configuration of Uplink Control Resource Sets (UCRSs) in a system based on a subband approach.
  • UCRSs Uplink Control Resource Sets
  • a bitmap with four bits may be sufficient to signal two configured UCRSs (e.g., UCRS 0 and UCRS 2) to a WTRU (e.g., [1 0 1 0]) from a total four available UCRSs over an entire system BW.
  • a WTRU may (e.g., explicitly) receive an indicator, for example, a one-bit indicator, e.g., to determine whether a PUCCH may be long or short duration for a given PRB, a set of PRBs or a subband.
  • This (e.g., one-bit) information may be, for example, included in a DCI or signaled by a higher layer, e.g., as a part of a PUCCH resource configuration.
  • a WTRU may (e.g., may alternatively) implicitly derive a PUCCH format (e.g., short format or long format) based on the number of OFDM symbols in a given PRB (e.g., UCRS duration).
  • a WTRU may conclude that a PUCCH with a short duration format may be transmitted, for example, when the number of OFDM symbols in a given UCRS (e.g., a given PRB(s)) may be less than or equal to a certain number (e.g., less than or equal to two OFDM symbols).
  • a WTRU may determine (e.g., otherwise determine) that a PUCCH with a long duration format may be transmitted when the number of OFDM symbols in a given UCRS is greater than a certain number (e.g., greater than two OFDM symbols). In examples (e.g., as shown in FIG.
  • UCRS 1 may occupy an entire slot while three other UCRSs may occupy 1 to 2 OFDM symbols (e.g., 1 to 2 OFDM symbols toward the end of the slot), examples, a WTRU may determine (e.g., may implicitly determine), for example, one or more of the following: UCRS 0 may be used for PUCCH with short duration spanning two OFDM symbols; UCRS 1 may be used for PUCCH with long duration transmission; UCRS 2 may be used for PUCCH with short duration spanning one OFDM symbol; or UCRS 3 is not configured so the WTRU may not transmit PUCCH on these resources, but UCRS 3 may be used for other users in the system.
  • UCRS 0 may be used for PUCCH with short duration spanning two OFDM symbols
  • UCRS 1 may be used for PUCCH with long duration transmission
  • UCRS 2 may be used for PUCCH with short duration spanning one OFDM symbol
  • UCRS 3 is not configured so the WTRU may not transmit PUCCH
  • a WTRU may be configured with PUCCH with short duration and PUCCH with long duration in the same slot and on the same PRB (e.g., mixed PRB), set of PRBs or subband.
  • PUCCH with short duration and PUCCH with long duration may be multiplexed, e.g., in a time domain (TDM) manner or TDM+frequency domain (FDM) manner.
  • Multiple PUCCHs with short duration may be configured on the same PRB, set of PRBs or subband.
  • a WTRU may derive indices of OFDM symbols within a slot for a (e.g., each) PUCCH format (e.g., short or long) in mixed PRB(s), for example, according to one or more of the following: explicit indication, e.g., in a DCI or higher layer signaling; implicitly, e.g., based on a pre-specified order to reduce signaling overhead or implicitly, e.g., based on a restrictive rule to reduce signaling overhead.
  • explicit indication e.g., in a DCI or higher layer signaling
  • implicitly e.g., based on a pre-specified order to reduce signaling overhead
  • implicitly e.g., based on a restrictive rule to reduce signaling overhead.
  • FIG. 3 is an example of multiplexing short PUCCH and long PUCCH in a Mixed PRB.
  • a PRB may transmit a short PUCCH and a long PUCCH in the same slot.
  • a WTRU may assume that a long PUCCH may precede (e.g., may always precede) a short PUCCH within a slot and/or mini-slot in one or more mixed PRBs.
  • FIG. 3 shows an example of this configuration wherein a long PUCCH precedes a short PUCCH in a Mixed RB (e.g., RB1 ).
  • a WTRU may assume that a PUCCH duration may be limited to certain values for a PUCCH format (e.g., each PUCCH format) in one or more mixed PRBs (e.g., a subset of pre-specified PUCCH durations). For example (e.g., as shown in FIG. 3), a WTRU may assume that a short PUCCH may span a single OFDM symbol while a long PUCCH may span an entire slot and/or mini-slot duration, e.g., minus a length of a short PUCCH in one or more Mixed PRBs.
  • a PUCCH duration may be limited to certain values for a PUCCH format (e.g., each PUCCH format) in one or more mixed PRBs (e.g., a subset of pre-specified PUCCH durations). For example (e.g., as shown in FIG. 3), a WTRU may assume that a short PUCCH may span a single OFDM symbol while a
  • a WTRU may assume, for example, that a PUCCH with a long duration may not be transmitted on a mini-slot.
  • a WTRU may transmit (e.g., may only transmit) an UL control channel on a PUCCH with a short duration on mini-slots, for example, when the WTRU may be configured with mini- slots.
  • a WTRU may assume, for example, that (e.g., only) a PUCCH with a short duration spanning one OFDM symbol may be transmitted in a mini slot, e.g., to provide room for a PUSCH transmission in the mini-slot.
  • a WTRU may transmit an UL control channel across multiple mini-slots, for example, to enhance coverage. Aggregated mini-slots may be continuous or non-continuous in time (e.g., as shown by example in FIG. 4).
  • FIG. 4 is an example of a restriction on PUCCH transmission on mini-slots.
  • a WTRU may be configured with multiple UCRSs.
  • a WTRU may assume, for example, that the indices of OFDM symbols comprising PUCCH with long or short duration may be identical for multiple (e.g., both) UCRSs in one or more Mixed PRBs.
  • a WTRU may assume that a long PUCCH may not be configured for one or more PRBs, for example, when the WTRU may be configured with multiple short PUCCHs on the same PRBs within a slot (e.g., short PUCCHs may be TDM multiplexed).
  • PRBs within a system bandwidth that may comprise UCRS may (e.g., from a WTRU perspective) have one or more OFDM symbols that may be reserved for UL transmissions around the end of a slot/mini- slot/subframe. Allocated PRBs for UL data transmission may overlap with configured PRBs for a UL control channel.
  • a WTRU may not (e.g., should not) transmit data (e.g., PUSCH) on OFDM symbols that may be allocated for UL control channel transmission toward the end of a slot/mini-slot/subframe, for example, even when the WTRU may be scheduled for data transmission on those PRBs concurrently configured for a UL control channel (e.g., PUSCH+PUCCH RBs).
  • a WTRU may (e.g., in this case) rate match a UL data packet, for example, according to available resources within a slot that may exclude OFDM symbols configured for a UL control channel for PRBs allocated for PUSCH transmission that may overlap with configured PRBs for a UL control channel.
  • PRBs allocated for UL data transmissions may overlap with PRBs that may be configured for UL control channel transmissions within a slot and/or mini-slot.
  • a WTRU may derive (e.g., may implicitly derive) OFDM symbols available for data transmission on an allocated PRB (e.g., each allocated PRB) from a UL control channel configuration, for example, by excluding resources that may be configured for an UL control channel transmission at the end of a slot/mini-slot/subframe (e.g., each slot/mini-slot/subframe).
  • a WTRU may use this information for rate matching of an encoded UL packet.
  • FIG. 5 is an example of multiplexing PUSCH and PUCCH on the same one or more PRBs.
  • PUSCH allocation may be, for example, on RB1 , RB2 and RB3 while PUCCH with short duration may be configured on RB1.
  • a WTRU may (e.g., in this case) exclude resources for short PUCCH on RB1 , for example, when determining resources available for a PUSCH transmission that may (e.g., also) be used for rate matching.
  • a WTRU may identify (e.g., for each PRB within system BW) whether a PRB may be for a UL data transmission (e.g., PUSCH PRBs), for UL control transmission (e.g., PUCCH PRBs) or for UL data plus control transmissions (e.g., PUCCH+PUSCH PRBs).
  • RB0 may be dedicated for PUCCH transmission
  • RB1 may be used for control and data transmissions (e.g., PUCCH+PUSCH)
  • ⁇ RB2 RB3 ⁇ may be for PUSCH transmission (e.g., only).
  • PUCCH and PUSCH may not be multiplexed on the same PRB(s) and may be FDM multiplexed.
  • a WTRU may follow a waveform used for PUSCH transmission for PUSCH+PUCCH RBs, for example, when the WTRU may support two waveforms for PUCCH (e.g., OFDM and DFT-s-OFDM).
  • PUCCH e.g., OFDM and DFT-s-OFDM
  • a WTRU may use OFDM for PUCCH transmissions when PUCCH and PUSCH RBs may be transmitted on the same slot.
  • Interference randomization for a short PUCCH may be provided.
  • a PUCCH with a short duration may, for example, span two OFDM symbols and multiple PRBs in the frequency domain.
  • a WTRU may randomize UL inter-cell and intra-cell interference, for example, by transmitting a UL control channel on a different (e.g., and possibly non-overlapping) set of PRBs and/or code sequences for an OFDM symbol (e.g., each OFDM symbol).
  • FIG. 6 is an example of interference randomization for a short PUCCH.
  • a WTRU may follow an implementation for short PUCCH transmission with interference randomization.
  • One or more of the following may apply.
  • a WTRU may identify a system-wide configured pool of UL control resources for first and second OFDM symbols within a slot/mini-slot allocated by gNB for potential PUCCH transmissions in the cell (e.g., UCRS).
  • This information may include, for example, a list of PRB indices within UL bandwidth and code sequence indices (e.g., for code division multiplexing of multiple PUCCH resources).
  • a code sequence for PUCCH resource multiplexing may, for example, be based on Zadoff-Chu (ZC) sequences.
  • Sequence length for example, may be a function of the length of PRBs allocated for PUCCH transmission or may be fixed to the length of a PRB (e.g., 12).
  • a WTRU may determine the allocated set of PRBs and code sequence indices for a PUCCH transmission on the first OFDM symbol. These resources may be subsets of the identified pool of UL control resources that the WTRU may receive, for example, using a combination of semi-static configuration and dynamic signaling.
  • an allocated set of PRBs indices for PUCCH transmission on the first OFDM symbol may be, for example, the first half indices of a pseudo-random permutation of the set ⁇ 0, 1 , ... , N ⁇ CCH -1 ⁇ , where N ⁇ CCH may be the number of configured PRBs for PUCCH.
  • a pseudo-random permutation of the set may be calculated, for example, using an algorithm (e.g., "Knuth Shuffles”) whose input random integer number may be a pseudo-random value that may be a function of a slot/mini- slot/subframe number and/or cell ID.
  • Code sequence indices for a PUCCH transmission may be derived, for example, using different cyclic shifts of the same ZC sequence or from multiple ZC sequences with different roots.
  • a WTRU may derive a set of PRBs and code indices within the pool of UL control resources in the second OFDM symbol for PUCCH transmission.
  • a WTRU may derive a set of PRB indices in the second OFDM symbol, for example, from a pseudo-random sequence obtained from the output of a length-31 Gold sequence generator.
  • a pseudo-random sequence generator may be a function of a Cell ID, for example, so that PRB mappings for PUCCH resources on the second OFDM symbol for different cells may be randomized for inter-cell interference.
  • a pseudo-random sequence generator may be a function of a slot/mini- slot/subframe number, for example, so that PRB mappings for PUCCH resources on the second OFDM symbol for different slots may be different for a given WTRU (e.g., time varying PUCCH resources).
  • a WTRU may derive a set of PRB indices in the second OFDM symbol using a predefined one-to-one mapping function.
  • a one-to-one PUCCH resource mapping function between the first and second OFDM symbols may be based on a circular shift.
  • PRB index in 2 nd Symbol Mod(PRB index in the 1 st symbol + A ⁇ CH , NTM CCH )
  • Mod(a.b) may be a modulo function that may return the remainder after division of a by b
  • a ⁇ CH may be a shift value that may be a function of a slot/mini-slot/subframe number and/or cell ID.
  • a WTRU may (e.g., alternatively) employ a pseudo-random interleaving pattern (e.g., permutation) on the set of PRB indices in the first OFDM symbol.
  • a pseudo-random interleaving pattern e.g., permutation
  • PRB indices that may be used for PUCCH transmissions on the first OFDM symbol may be [0, 2, 5, 6] while PRB indices for the second OFDM symbol (e.g., after pseudo-random interleaving) may be [1 , 3, 4, 7].
  • a permutation may be an identity permutation (e.g., the same arrangement).
  • the first and the second OFDM symbols may have the same set of PRB indices.
  • a WTRU may (e.g., advantageously) use the reference signals (RS) in both adjacent OFDM symbols on the same PRB for channel estimation. This may not preclude the possibility of having RS in an OFDM symbol (e.g., only one OFDM symbol).
  • RS reference signals
  • a WTRU may derive (e.g., may additionally derive) a ZC sequence index in a second OFDM symbol, for example, using a pseudo-random cyclic shift offset of the assigned ZC sequence on a first OFDM symbol.
  • a pseudo-random cyclic shift offset may be obtained from the output of a length-31 Gold sequence generator.
  • a ZC sequence index may be PRB specific.
  • a PRB (e.g., each PRB) may have a different ZC sequence cyclic shift and/or root sequence.
  • a length of a ZC sequence (e.g., in this case) may be 12.
  • a WTRU may transmit a PUCCH signal on UL control channel resources that may be identified on the first and second OFDM symbols.
  • FIG. 7 is an example of interference randomization for a short PUCCH.
  • FIG. 7 shows an (e.g., alternative) example for PUCCH interference randomization based on, for example, interlaced mapping of subcarrier resources.
  • a WTRU may map its payload or sequence (e.g., only) on either odd or even subcarrier locations.
  • Interference may be whitened (e.g., interference becomes noise) to some extent, for example, by spreading a PUCCH over a larger number of PRBs.
  • Interference randomization may (e.g., also) provide a better capability for channel estimation, higher frequency diversity and/or potentially faster decoding.
  • a WTRU may identify a system-wide configured pool of UL control resources that may be available within a slot/mini-slot that may be allocated (e.g., by gNB) for potential PUCCH transmissions in a cell (e.g., UCRS).
  • This information may include, for example, a list of PRB indices within a UL bandwidth and code sequence indices (e.g., for code division multiplexing of multiple PUCCH resources).
  • Code sequence for PUCCH resource multiplexing may be based on Zadoff-Chu (ZC) sequences.
  • ZC Zadoff-Chu
  • Sequence length may be based on a function of the length of PRBs allocated for PUCCH transmission or may be fixed to the length of a PRB (e.g., 12). Odd/even mapping locations may be signaled (e.g., implicitly or explicitly), for example, through an L1 command and/or as part of an initial designation of resources (e.g., as previously described).
  • the WTRU may determine an allocated set of PRBs and code sequence indices for a PUCCH transmission that may be subsets of an identified pool of UL control resources that the WTRU may receive, for example, using a combination of semi-static configuration and dynamic signaling.
  • the WTRU may transmit a PUCCH signal on UL control channel resources that may be identified resources of the OFDM symbols.
  • Mini-slot short PUCCH hopping may be provided.
  • a WTRU may be configured with aggregated mini-slots.
  • a WTRU may transmit a short PUCCH over aggregated mini-slots, for example, to enhance coverage.
  • a WTRU may (e.g., alternatively) transmit a long PUCCH over aggregated slots, e.g., for extreme coverage.
  • a WTRU may transmit PUCCH on a different resource on each mini-slot/slot, for example, using a pseudo-random hopping pattern, which may be a function of the mini-slot/slot number.
  • FIG. 8 is an example of aggregated mini-slot short PUCCH hopping.
  • FIG. 8 shows an example of mini-slot hopping, e.g., where the Short PUCCH PRB may be changed in every mini-slot.
  • a short PUCCH (e.g., includes one to tens of bits) may be sent, for example, without an RS.
  • Orthogonal sequences e.g., Zadoff-Chu sequence or other CAZAC sequences that may (e.g., also) be useful for restricting PAPR
  • a (e.g., each) one or two bits of UCI may be sent, for example, by multiplying a BPSK or QPSK symbol with a CAZAC sequence that may be sent over a set of frequency tones (e.g., one or more PRBs). More bits may be sent per WTRU.
  • multiple cyclic shifts of a Zadoff-Chu sequence may be assigned to a WTRU for multiplexing different bits. This rate increase through using multiple cyclic shifts of the CAZAC sequence may be used, for example, together with using multiple groups of PRB and the OFDM symbol associated with the PUCCH control resource set.
  • 4 PRBs may be assigned to a PUCCH that may correspond to a group of WTRUs. Two OFDM symbols on those 4 PRBs may be included, for example, in an uplink control resource set.
  • a WTRU may send 8k bits, for example, where k cyclic shift of the assigned CAZAC sequences may be assigned to the WTRU over those PRBs.
  • Uplink control resource sets may, for example, contain a time/frequency resource for a group of WTRUs. Control resource sets may not have overlap (e.g., any overlap) with a data region. Grantless uplink access with high reliability may be supported in some applications (e.g., URLLC). [0117] Distinct uplink control resource sets may be separate from a PUSCH region. A PUCCH of grantless URLLC WTRUs may be allowed to transmit with very low rates, for example, by spreading over part of the OFDM resources elements that may be assigned to a PUSCH of eMBB. Spreading may be performed, for example, using CAZAC sequences (e.g., to ensure low PAPR and pseudo-random properties of the sequence).
  • a receiver may detect and decode data.
  • a gNodeB may (e.g., first) determine whether a URLLC PUCCH transmission may be present. This URLLC detection may be performed, for example, using a CDMA detection procedure, such as a linear decorrelator or a nonlinear detection scheme. URLLC control information may or may not be detected.
  • eMBB data may be decoded, for example, by a SIC (successive interference cancellation) scheme.
  • a wireless transmit/receive unit may be configured to provide uplink control information (UCI) in one or more Uplink Control Resource Sets (UCRSs).
  • UCI uplink control information
  • UCRS Uplink Control Resource Sets
  • a UCRS may comprise one or more Resource Blocks (RBs) in a frequency domain spanning over one or more OFDM symbols in a time domain.
  • a UCCH may be configured to provide UCI for one or more PRBs in one or both a short UCCH signal and a long UCCH signal.
  • a WTRU may derive a configuration and/or may be provided with a configuration by a transmission/reception point (TRP).
  • TRP transmission/reception point
  • UCCH signals may be provided on different RBs or multiplexed on the same RB.
  • a UCCH may be multiplexed with an uplink shared channel (USCH) on the same RB.
  • Interference for a short UCCH signal may be randomized, for example, by distributing a short UCCH signal to different RBs.
  • Other implementation features may include multi-slot short PUCCH hopping, spreading-based multi-bit short PUCCH and overlapping URLLC PUCCH and eMBB PUSCH.
  • a WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc.
  • WTRU may refer to application-based identities, e.g., user names that may be used per application.
  • the processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor.
  • Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes, des procédés et des instruments destinés à l'attribution de ressources pour un canal de commande de liaison montante dans un système de communication sans fil. Une unité d'émission/de réception sans fil (WTRU) peut être configurée pour recevoir une signalisation de couche supérieure provenant d'un récepteur. La signalisation de couche supérieure peut comprendre des informations associées à un multiplexage par répartition orthogonale de la fréquence (OFDM). La WTRU peut configurer un ensemble de ressources de commande de liaison montante (UCRS), qui peut comprendre un bloc de ressources physiques (PRB). La WTRU peut être configurée pour émettre des informations de canal de commande de liaison montante physique (PUCCH) par l'intermédiaire du PRB. L'émission de PUCCH peut comprendre une configuration de format court et/ou une configuration de format long. Si l'émission de PUCCH est inférieure ou égale à deux symboles OFDM, l'émission de PUCCH peut comprendre une configuration de format court, si l'émission de PUCCH est supérieure à deux symboles OFDM, l'émission de PUCCH peut comprendre une configuration de format long.
PCT/US2018/023559 2017-03-22 2018-03-21 Attribution de ressources pour canal de commande de liaison montante WO2018175578A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762474678P 2017-03-22 2017-03-22
US62/474,678 2017-03-22

Publications (1)

Publication Number Publication Date
WO2018175578A1 true WO2018175578A1 (fr) 2018-09-27

Family

ID=61913600

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/023559 WO2018175578A1 (fr) 2017-03-22 2018-03-21 Attribution de ressources pour canal de commande de liaison montante

Country Status (1)

Country Link
WO (1) WO2018175578A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113396548A (zh) * 2018-12-17 2021-09-14 Idac控股公司 与能量和信息的同时递送相关联的信号设计
CN113519138A (zh) * 2019-02-13 2021-10-19 Idac控股公司 物理上行链路共享信道传输
US20220247537A1 (en) * 2019-07-12 2022-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Method for selecting physical uplink control channel (pucch) orthogonal cover codes (occ) repetition sequence

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology Physical Layer Aspects (Release 14)", 15 February 2017 (2017-02-15), XP051222110, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_88/Docs/> [retrieved on 20170215] *
HUAWEI ET AL: "Resource indication of UL control channel", vol. RAN WG1, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), XP051208815, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170212] *
LG ELECTRONICS: "Configuration of long NR-PUCCH resource", vol. RAN WG1, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), XP051209636, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170212] *
NTT DOCOMO ET AL: "Summary of [87-32]: UL L1/L2 control channel design for NR", vol. RAN WG1, no. Spokane, USA; 20170116 - 20170120, 17 January 2017 (2017-01-17), XP051222223, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_AH/NR_AH_1701/Docs/> [retrieved on 20170117] *
ZTE ET AL: "NR PUCCH resource allocation", vol. RAN WG1, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), XP051208758, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170212] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113396548A (zh) * 2018-12-17 2021-09-14 Idac控股公司 与能量和信息的同时递送相关联的信号设计
CN113396548B (zh) * 2018-12-17 2024-05-07 交互数字专利控股公司 与能量和信息的同时递送相关联的信号设计
CN113519138A (zh) * 2019-02-13 2021-10-19 Idac控股公司 物理上行链路共享信道传输
US20220247537A1 (en) * 2019-07-12 2022-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Method for selecting physical uplink control channel (pucch) orthogonal cover codes (occ) repetition sequence

Similar Documents

Publication Publication Date Title
US20240014956A1 (en) Beam-based pdcch transmission in nr
US20220159674A1 (en) Methods for nr sl multi-sub-channel pscch transmission
US20230336316A1 (en) Methods, systems, and apparatus for transmitting uplink control information
US20220132497A1 (en) Control channel for new radio
WO2020146580A1 (fr) Canaux de rétroaction de liaison latérale
WO2020033704A1 (fr) Transmission améliorée de commande de liaison latérale
WO2019195505A1 (fr) Signalisation d&#39;informations de commande, et procédure pour des communications new radio (nr) de véhicule à tout (v2x)
US20200036470A1 (en) Common control channel and reference symbol for multiple waveform data transmission
WO2019099435A1 (fr) Procédés de détermination de candidats de canal physique de commande de liaison descendante (pdcch)
WO2018144852A1 (fr) Transmission et réception de canaux de commande de liaison descendante physique
EP3520294B1 (fr) Conception des canaux de contrôle non-orthogonaux pour des systèmes de communication sans fil
US11716746B2 (en) Scheduling and transmission for NOMA
WO2021178788A1 (fr) Attribution dynamique de ressources de signal de démodulation
EP3881614A1 (fr) Transmission de noma robuste
WO2018175578A1 (fr) Attribution de ressources pour canal de commande de liaison montante
WO2019195103A1 (fr) Procédés de harq pour noma
US20240023103A1 (en) Physical uplink control channel transmission
WO2019143941A1 (fr) Mises en œuvre de signaux de référence pour un accès multiple non orthogonal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18716775

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18716775

Country of ref document: EP

Kind code of ref document: A1