[go: up one dir, main page]

WO2025177182A1 - Procédés de prise en charge de codes de couverture orthogonaux dans un ntn-iot - Google Patents

Procédés de prise en charge de codes de couverture orthogonaux dans un ntn-iot

Info

Publication number
WO2025177182A1
WO2025177182A1 PCT/IB2025/051800 IB2025051800W WO2025177182A1 WO 2025177182 A1 WO2025177182 A1 WO 2025177182A1 IB 2025051800 W IB2025051800 W IB 2025051800W WO 2025177182 A1 WO2025177182 A1 WO 2025177182A1
Authority
WO
WIPO (PCT)
Prior art keywords
occ
time
ues
domain
sequences
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/IB2025/051800
Other languages
English (en)
Inventor
Gerardo Agni MEDINA ACOSTA
Jie Chen
Ola Lundqvist
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025177182A1 publication Critical patent/WO2025177182A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/26025—Numerology, i.e. varying one or more of symbol duration, subcarrier spacing, Fourier transform size, sampling rate or down-clocking
    • 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/0014—Three-dimensional division
    • H04L5/0016—Time-frequency-code
    • 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/0037—Inter-user or inter-terminal allocation

Definitions

  • loT- NTN in particular NB-IoT
  • NB-IoT will have to support massive capacity in terms of number and types of UE, some of which have significantly different characteristics than others (e.g., low-cost devices, wearables, etc.).
  • the method further comprises that the plurality of UEs concurrently transmit through the narrowband physical uplink for a single-tone or multi-tone transmission having a first subcarrier spacing (SCS), and appliance of the plurality of OCC sequences is with respect to one or more OFDM symbols, one or more time-domain slots, or a time-domain resource unit (RU).
  • SCS subcarrier spacing
  • RU time-domain resource unit
  • a method is performed by a network node receiving concurrent transmissions on the same time-frequency resources from a plurality of user equipments (UEs) that receive a plurality of orthogonal cover codes (OCC) sequences.
  • the method comprises sending, to a UE of the plurality of UEs, an orthogonal cover codes (OCC) sequence of the plurality of OCC sequences.
  • the plurality of OCC sequences are assigned to respective ones of the plurality of UEs.
  • the method further comprises receiving, through a narrowband physical uplink shared channel (NPUSCH) format, from the UE on the same time-frequency resources shared by other UEs of the plurality of UEs.
  • NPUSCH narrowband physical uplink shared channel
  • the method comprises that the network node concurrently receives from the plurality of UEs through the narrowband physical uplink for a single-tone or multi-tone transmission having a first subcarrier spacing (SCS), and that appliance of the plurality of OCC sequences is with respect to one or more OFDM symbols, one or more time-domain slots, or a time-domain resource unit.
  • SCS subcarrier spacing
  • Figure 1 illustrates the number of simultaneous NPUSCH users, when NPUSCH Format 1 with 3.75 kHz SCS has available bandwidth of 180 kHz.
  • FIG. 2 illustrates an example of a Preamble Repetition Unit (PRU).
  • PRU Preamble Repetition Unit
  • Figure 3 shows an example of a communication system in accordance with some embodiments.
  • FIG. 4 shows a user equipment (UE) in accordance with some embodiments.
  • Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 7A is a flowchart illustrating a method performed by a UE of a plurality of UEs that receive a plurality of orthogonal cover codes (OCC) sequences for concurrently transmitting to a network node on the same time-frequency resources, in accordance with some embodiments.
  • Figure 7B is a flowchart illustrating a method performed by a network node receiving concurrent transmissions on the same time-frequency resources from a plurality of user equipments (UEs) that receive a plurality of orthogonal cover codes (OCC) sequences, in accordance with some embodiments.
  • UEs user equipments
  • OCC orthogonal cover codes
  • Figure 8 is a diagram illustrating OCCs of length 2 and applying the OCCs to symbols for transmitting symbols of multiple UEs using the same time-frequency resources, in accordance with some embodiments.
  • Figures 9A-9B are diagrams illustrating OCCs of length 2 and applying the OCCs to time-domain slots for single-tone transmission with 3.75 KHz SCS.
  • Figures 10A-10B are diagrams illustrating OCCs of length 2 and applying the OCCs to time-domain slots for single-tone transmission with 15 KHz SCS.
  • an objective to increase the uplink capacity for loT-NTN includes the following aspects. Specifically, enhancements should be developed to enable multiplexing of multiple UEs (e.g. up to the minimum of 4 and the maximum allowed by the existing UL and DL signaling) in a single 3.75 kHz or 15 kHz subcarrier via OCC for NPUSCH format 1 and NPRACH. Moreover, Multi-tone support for 15 kHz SCS should also be considered.
  • Figure 1 illustrates the number of simultaneous NPUSCH users, when NPUSCH Format 1 with 3.75 kHz SCS has available 180 kHz.
  • NPUSCH Format 1 with 3.75 kHz subcarrier spacing SCS
  • the current 3GPP specification offers the possibility of multiplexing a non-negligible number of users. For example, if NPRACH and NPUSCH Format 1 with 3.75 kHz subcarrier spacing were to co-exist, it would be possible having NPRACH on 45 kHz and NPUSCH on 135 kHz as to have up to 36 single-tone users simultaneously. Thus, if the NPRACH and NPUSCH co-exist, the NPRACH transmission can have up to 12 users and the NPUSCH transmission can have up to 36 users.
  • the total number of users on the co-existing transmissions can be 48 maximum.
  • both NPRACH and NPUSCH have 3.75 kHz subcarrier spacing.
  • a single-tone refers to a single subcarrier spacing like the 3.75 kHz being used for transmission.
  • multi-tone refers to multiple subcarrier spacings (e.g., 3, 6, 12) being used for transmission.
  • NPRACH preambles use a single-tone transmission with 3.75 kHz SCS and frequency hopping.
  • NB-IoT supports two NPRACH formats (Format 0 using a cyclic prefix (CP) of 66.7 us, and Format 1 using a CP of 266.67 us), and the basic NPRACH repetition unit includes four symbol groups.
  • Table 1 below illustrates example Deterministic Frequency Hopping patterns for an NPRACH repetition unit.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the techniques described herein provide the support of OCC for loT-NTN accounts for the physical layer structure and mechanisms of NPUSCH Format 1 and NPRACH (e.g., for NPUSCH, a transport block size (TBS) is mapped across multiple UE slots (e.g., , the number of consecutive slots in an UL resource unit for NB-IoT) composing a resource unit, which can be used as a reference for the OCC sequence).
  • TBS transport block size
  • the systems and methods described herein providing the physical layer structure and mechanisms of NPUSCH Format 1 and NPRACH can serve to put an upper limit on the number of simultaneous transmissions using OCCs.
  • the systems and methods described herein providing the performance requirement of NPRACH for preamble detection (a total probability of false detection of the preamble (Pfa) and the probability of detection of the preamble (Pd)).
  • Figure 3 shows an example of a communication system 300 in accordance with some embodiments.
  • the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308.
  • the access network 304 includes one or more access network nodes, such as network nodes 310a and 310b (one or more of which may be generally referred to as network nodes 310), or any other similar 3 rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points.
  • 3GPP 3 rd Generation Partnership Project
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • the telecommunication network 302 includes one or more Open- RAN (ORAN) network nodes.
  • ORAN Open- RAN
  • An ORAN network node is a node in the telecommunication network 302 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 302, including one or more network nodes 310 and/or core network nodes 308.
  • ORAN Open- RAN
  • Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
  • the network nodes 310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 312a, 312b, 312c, and 312d (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.
  • UE user equipment
  • the UEs 312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 310 and other communication devices.
  • the network nodes 310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 312 and/or with other network nodes or equipment in the telecommunication network 302 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 302.
  • the core network 306 connects the network nodes 310 to one or more host computing systems, such as host 316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 306 includes one more core network nodes (e.g., core network node 308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 308.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and/or the telecommunication network 302.
  • the host 316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 300 of Figure 3 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunications network 302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 312 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312c and/or 312d) and network nodes (e.g., network node 310b).
  • the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 314 may be a broadband router enabling access to the core network 306 for the UEs.
  • the hub 314 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 314 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
  • the hub 314 may have a constant/persistent or intermittent connection to the network node 310b.
  • the hub 314 may also allow for a different communication scheme and/or schedule between the hub 314 and UEs (e.g., UE 312c and/or 312d), and between the hub 314 and the core network 306.
  • the hub 314 is connected to the core network 306 and/or one or more UEs via a wired connection.
  • the hub 314 may be configured to connect to an M2M service provider over the access network 304 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection.
  • the hub 314 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 310b.
  • the hub 314 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 310b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG 4 shows a UE 400 in accordance with some embodiments.
  • the UE 400 presents additional details of some embodiments of the UE 312 of Figure 1.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • the UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a power source 408, a memory 410, a communication interface 412, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410.
  • the processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 402 may include multiple central processing units (CPUs).
  • the input/output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 400.
  • the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 408 may further include power circuitry for delivering power from the power source 408 itself, and/or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.
  • the memory 410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416.
  • the memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.
  • the memory 410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 410 may allow the UE 400 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.
  • the processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412.
  • the communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422.
  • the communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 418 and/or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 412, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 5 shows a network node 500 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • O-RAN nodes or components of an O-RAN node e.g., O-RU, O-DU, O-CU.
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508.
  • the network node 500 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 500 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 500 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs).
  • the network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 500.
  • RFID Radio Frequency Identification
  • the processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 500 components, such as the memory 504, to provide network node 500 functionality.
  • the processing circuitry 502 includes a system on a chip (SOC).
  • the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514.
  • the radio frequency (RF) transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.
  • the memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 502.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-
  • the memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500.
  • the memory 504 may be used to store any calculations made by the processing circuitry 502 and/or any data received via the communication interface 506.
  • the processing circuitry 502 and memory 504 is integrated.
  • the communication interface 506 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 506 comprises port(s)/terminal(s) 516 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. Radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502.
  • the radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 520 and/or amplifiers 522.
  • the radio signal may then be transmitted via the antenna 510.
  • the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518.
  • the digital data may be passed to the processing circuitry 502.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 500 does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510.
  • the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510.
  • all or some of the RF transceiver circuitry 512 is part of the communication interface 506.
  • the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).
  • the antenna 510 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.
  • the power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein.
  • the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508.
  • the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • FIG. 6 is a block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • the virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.
  • Applications 602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 604 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 608a and 608b (one or more of which may be generally referred to as VMs 608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 606 may present a virtual operating platform that appears like networking hardware to the VMs 608.
  • the VMs 608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 606.
  • a virtualization layer 606 Different embodiments of the instance of a virtual appliance 602 may be implemented on one or more of VMs 608, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 608, and that part of hardware 604 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 608 on top of the hardware 604 and corresponds to the application 602.
  • Hardware 604 may be implemented in a standalone network node with generic or specific components. Hardware 604 may implement some functions via virtualization. Alternatively, hardware 604 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 610, which, among others, oversees lifecycle management of applications 602.
  • hardware 604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 612 which may alternatively be used for communication between hardware nodes and radio units.
  • computing devices described herein may include the illustrated combination of hardware components
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • a UE receives an orthogonal cover codes (OCC) sequence of the plurality of OCC sequences.
  • OCC orthogonal cover codes
  • the plurality of OCC sequences are assigned to respective ones of the plurality of UEs.
  • the UE transmits, through a narrowband physical uplink shared channel (NPUSCH) format 1, to the network node on the same time-frequency resources shared by other UEs of the plurality of UEs.
  • NPUSCH narrowband physical uplink shared channel
  • the plurality of UEs concurrently transmit through the narrowband physical uplink for a single-tone or multi-tone transmission having a first subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • the appliance of the plurality of OCC sequences is with respect to one or more OFDM symbols, one or more time-domain slots, or a time-domain resource unit.
  • FIG. 7B is a flowchart illustrating a method 720 performed by a network node, which receives concurrent transmissions on the same time-frequency resources from a plurality of user equipments (UEs) that receive a plurality of orthogonal cover codes (OCC) sequences.
  • Method 720 corresponds to method 700, but is performed by a network node communicating concurrently with multiple UEs.
  • the network node sends, to a UE of the plurality of UEs, an orthogonal cover codes (OCC) sequence of the plurality of OCC sequences.
  • the plurality of OCC sequences are assigned to respective ones of the plurality of UEs.
  • a plurality of orthogonal cover codes OCCs are assigned, received, and applied by a plurality of UEs for transmitting NPUSCH Format 1 with 3.75 kHz SCS simultaneously on the same time-frequency resources.
  • the OCC sequences spanning on the time-frequency resources account for the resource unit (RU) length on which a transport block of NPUSCH Format 1 with 3.75 kHz SCS is mapped.
  • a transport block can map to a resource unit or multiple resource units (e.g., up to 10).
  • Each resource unit has 16 time-domain slots, and each time-domain slot can have multiple symbols (e.g., 7).
  • a time-domain slot is also simply referred to as a slot.
  • the OCC sequences can be applied with respect to one or more timedomain resource unit, one or more time-domain slots, or one or more OFDM symbols.
  • the OCC sequences received by the UE to transmit NPUSCH Format 1 with 3.75 kHz SCS can be re-used to increase the UL capacity.
  • the capacity of NPUSCH Format 1 with 3.75 kHz SCS can be doubled using only two OCC sequences which length can be for example a power of 2, since each A' s 'J i; is associated to different timefrequency resources (i.e., different and independent single-tones) in the transmission bandwidth assigned to NPUSCH Format 1.
  • the UL capacity of NPUSCH Format 1 with 3.75 kHz SCS can be tripled using three OCC sequences or quadrupled using four OCC sequences and so on using the same principle as in the previous embodiment until the DL capacity becomes a bottleneck, wherein the length of the OCC sequences can be for example a power of 2.
  • FIG. 8 illustrates an example of applying OCCs to symbols in resource unit.
  • OCCs 806 are provided for appliance to the symbols of multiple UEs (e.g., UE1, UE2, ... UEn).
  • Each of OCCs 806 has a length of 2, and there are two OCC sequences in OCCs 806.
  • Each of the OCC sequences in OCCs 806 is orthogonal to the other OCC sequence, and therefore can be applied to the symbols of RUs transmitted by different UEs.
  • UE1 can transmit various time-domain slots (e.g., 16) in a RU.
  • Each of the time-domain slot include multiple OFDM symbols.
  • a first time-domain slot includes 7 symbols 802A-802G and a guard period 803.
  • An OCC sequence 806 having a length of 2 can be applied to at least some of symbols 802A-802G. Applying the OCC sequence to the symbols is also referred to as symbol spreading.
  • another OCC sequence of OCCs 806 having a length of 2 can be applied to at least some of symbols 804A-804G.
  • the OCC sequences in OCCs 806 are orthogonal to each other, and therefore, after symbol spreading, the symbols in RUs of different UEs (e.g., UE1 and UE2) can be transmitted concurrently on the same time-frequency resource to a network node, thereby increasing the uplink capacity.
  • some area data symbols, and some are non-data symbols e.g., DMRS - demodulation reference signal symbols.
  • the UEs can transmit concurrently, for example, through a narrowband physical uplink shared channel (NPUSCH) format 1 having a single-tone or 1 consecutive subcarrier of 3.75 kHz SCS.
  • NPUSCH narrowband physical uplink shared channel
  • symbols from different UEs can be mixed or combined and transmitted to the network node on the same time-frequency resource.
  • Figures 9A-9B illustrate an example of applying OCCs to time-domain slots in a resource unit.
  • the OCCs 906 has a length of 2
  • each OCC sequence in OCCs 906 is orthogonal to other OCC sequence.
  • the RU 900 includes 16 time-domain slots such as slots 902 A and 902B. Each time-domain slot has a duration of 2 ms, and therefore, the total duration of the RU 900 is 32 ms.
  • the OCCs sequences 906 are applied to RUs of two UEs (UE1 and UE2) at the time-domain slot level.
  • a single-tone e.g., 3.75 kHz SCS
  • UE1 and UE2 can transmit at the same time on the same time-frequency resource.
  • the OCC spreading granularity can be an OFDM symbol, or a slot, or a Resource Unit.
  • the above example are for illustration of OCC spreading at the symbol level or the slot level with a single-tone of 3.75 KHz SCS.
  • the capacity of the uplink for the single-tone or multi-tone transmission can be increased N times with N OCC sequences, where N is an integer number.
  • Figures 10A-10B illustrate an example of applying OCCs to time-domain slots in a resource unit.
  • the example shown in Figures 10A-10B illustrates increasing the uplink capacity by using OCCs on NPUSCH Format 1 with 15 kHz SCS for single-tone transmission.
  • a plurality of orthogonal cover codes OCCs are assigned, received, and applied by a plurality of UEs for transmitting NPUSCH Format 1 with 15 kHz SCS simultaneously on the same time-frequency resources.
  • the OCC sequences spanning on the time-frequency resources account for the resource unit (RU) length on which a transport block of NPUSCH Format 1 with 15 kHz SCS is mapped.
  • RU resource unit
  • a transport block can map to a resource unit or multiple resource units (e.g., up to 10).
  • Each resource unit has 16 time-domain slots, and each time-domain slot can have multiple symbols (e.g., 7).
  • a time-domain slot is also simply referred to as a slot.
  • the OCC sequences can be provided based on the resource unit length, the number of slots, and the number of symbols
  • the NPUSCH Format 1 with 15 kHz SCS for single-tone transmissions is described.
  • the OCC sequences account for the resource unit (RU) using as reference and granularity in the frequency-domain the “Number of consecutive subcarriers in an UE resource unit for NB-IoT” (denoted as N s ⁇ u ) and in the time-domain “Number of consecutive slots in an UL resource unit for NB-IoT” (denoted as A ⁇ s ).
  • the RU 1000 includes 16 time-domain slots such as slots 1002 A and 1002B. Each time-domain slot has a duration of 0.5 ms, and therefore, the total duration of the RU 900 is 8 ms.
  • the OCC sequences received by the UE to transmit NPUSCH Format 1 with 15 kHz SCS can be re-used to increase the UL capacity.
  • the capacity of NPUSCH Format 1 with 15 kHz SCS can be doubled using only two OCC sequences which length can be for example a power of 2, since each N s ⁇ u is associated to different timefrequency resources (e.g., different and independent single-tones) in the transmission bandwidth assigned to NPUSCH Format 1.
  • the OCCs 1006 has a length of 2.
  • the UE capacity of NPUSCH Format 1 with 15 kHz SCS can be tripled using three OCC sequences or quadrupled using four OCC sequences and so on using the same principle as in the previous embodiment until the DE capacity becomes a bottleneck, wherein the length of the OCC sequences can be for example a power of 2.
  • the OCCs sequences 1006 are applied to RUs of two UEs (UE1 and UE2) at the time-domain slot level.
  • a singletone e.g., 15 KHz SCS
  • UE1 and UE2 can transmit at the same time on the same time-frequency resource.
  • one OCC sequence having a length of 2 is applied to two RUs of UE1, each of the RUs has 16 time-domain slots.
  • the other orthogonal OCC sequence having a length of 2 is applied to two RUS of UE2, each of the RUs have 16 time-domain slots.
  • the time-domain slots or RUs of UE1 and UE2 can be mixed or combined, and transmitted concurrently at the same time on the same timefrequency resource to a network node.
  • NPUSCH Format 1 with 15 kHz SCS for multi-tone transmissions.
  • the OCC sequences can be applied with respect to one or more of a frequency-domain resource having 3, 6, or 12 subcarriers used for the multi-tone transmission and the time-domain resource unit having 8, 4, or 2 time-domain slots.
  • Each of the OCC sequences can be applied at the symbol level, at the slot level, or at the time-domain resource unit with respect to each one of the multi-tones, thereby significantly increasing the uplink capacity of transmission from multiple UEs at the same time. For instance, in a multi-tone transmission, similar to the single-tone transmission described above, an OCC sequence can be applied to symbols, where a time-domain slot can have 7 symbols.
  • a plurality of orthogonal cover codes OCCs are assigned, received, and applied by a plurality of UEs for transmitting NPRACH with 3.75 kHz SCS simultaneously on the same time-frequency resources, wherein the OCC sequences spanning on the time-frequency resources account for the basic NPRACH repetition unit including four symbol groups and the frequency hopping applied on those symbol groups.
  • An example of frequency hopping is described above using Table 0 and Figure 2.
  • an orthogonal sequence of length equal to the number of symbol groups in a preamble repetition unit is used (e.g., an OCC sequence length 4).
  • OCC sequence length 4 the number of UEs using frequency hopping patterns resulting in back-to-back frequency resource utilization.
  • the 4 UEs are paired as a function of frequency hopping patterns that qualify to have back-to-back transmissions on the same subcarrier or tone index.
  • subcarrier#0 is an example of the frequency resource utilized back-to-back among the 4 UEs.
  • UE2 (NPRACH Preamble 1): subcarrier#l for symbol groupO, subcarrier#0 for symbol groupl, subcarrier#6 for symbol group2, and subcarrier#7 for symbol group3.
  • UE4 NPRACH Preamble 6: subcarrier#6 for symbol groupO, subcarrier#7 for symbol groupl, subcarrier#l for symbol group2, and subcarrier#O for symbol group3.
  • the Table 4 below illustrates the spreading of symbol group 0 (i.e., first symbol group out of the four composing a preamble repetition unit) of Preamble 0, where the spreading spans across adjacent symbol groups of other NPRACH preambles using subcarrier#0.
  • symbol group 0 i.e., first symbol group out of the four composing a preamble repetition unit
  • the spreading spans across adjacent symbol groups of other NPRACH preambles using subcarrier#0.
  • those other NPRACH preambles in this example UEs using NPRACH preambles 1, 6, and 7 would have to be assigned OCC sequences.
  • Table 4 Illustration of the spreading of symbol group 0 of Preamble 0 across subcarrier#0 of adjacent symbol groups of other NPRACH Preambles.
  • the performance requirements for NPRACH defined in 3GPP TS 36.141 clause 8.5.3 set the upper limit for the number of UEs transmitting on the same NPRACH resource using OCC, as to preserve the current total probability of false detection of the preamble (Pfa) and the probability of detection of the preamble (Pd).
  • the performance requirements for NPRACH defined in TS 36.141 clause 8.5.3 can be relaxed for the support of OCC on NPRACH, such that the total probability of false detection of the preamble (Pfa) and the probability of detection of the preamble (Pd) are higher than currently stipulated in TS 36.141 clause 8.5.3.
  • Random Access Preamble ID will also take the OCC sequence into account, different UEs with same time-frequency NPRACH resource but different OCCs can have different RAPID so they can be distinguished by Random Access Response.
  • the UEs that can potentially be scheduled (e.g., paired) to transmit simultaneously using OCC are selected by the network entity based on one or more of the following aspects: traffic characteristics, number of repetitions, modulation schemes, location, power, short-term performance records, long-term performance records, etc.
  • pairing the most suitable UEs to transmit simultaneously using OCCs is essential towards preserving orthogonality, otherwise the orthogonality may suffer from an unsuitable UE pairing (e.g., if the UEs being paired happen to be too unbalanced in terms of transmit power).
  • a given UE is assigned an OCC using dynamic signaling through receiving scheduling information via Downlink Control Information (DO).
  • DO Downlink Control Information
  • the DO size is increased by one or more bits as to introduce a new field associated with the OCC assignment.
  • the DO size is unchanged, and one or more bits of an existing field or fields are repurposed as to introduce a new field associated with the OCC assignment.
  • a given UE is assigned an OCC using semi-static signaling via a Radio Resource Control (RRC) configuration.
  • RRC Radio Resource Control
  • One or more of the embodiments in previous sections are used in one or more beams transmitted from a given satellite.
  • One or more of the embodiments in previous sections are used in a deployment having one beam per cell.
  • One or more of the embodiments in previous sections are used in a deployment having more than one beam per cell.
  • one or more of the embodiments in previous sections are equally applicable to a non-terrestrial network scenario based on transparent payload or regenerative payload.
  • one or more of the embodiments in previous sections are equally applicable to different satellite orbits such as LEO (low earth orbit), MEO (medium earth orbit), and GEO (geostationary earth orbit).
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • Coupled to is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms “coupled to” and “coupled with” are used synonymously. Within the context of a networked environment where two or more components or devices are able to exchange data, the terms “coupled to” and “coupled with” are also used to mean “communicatively coupled with”, possibly via one or more intermediary devices.
  • inventive subject matter is considered to include all possible combinations of the disclosed elements. As such, if one embodiment comprises elements A, B, and C, and another embodiment comprises elements B and D, then the inventive subject matter is also considered to include other remaining combinations of A, B, C, or D, even if not explicitly discussed herein.
  • transitional term “comprising” means to have as parts or members, or to be those parts or members. As used herein, the transitional term “comprising” is inclusive or open-ended and does not exclude additional, unrecited elements or method steps.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé est mis en œuvre par un équipement utilisateur (UE) d'une pluralité d'UE qui reçoivent une pluralité de séquences de codes de couverture orthogonaux (OCC) pour transmettre simultanément à un nœud de réseau sur les mêmes ressources temps-fréquence. Le procédé consiste à recevoir une séquence de codes de couverture orthogonaux (OCC) de la pluralité de séquences d'OCC. La pluralité de séquences d'OCC sont attribuées à des UE respectifs de la pluralité d'UE. Le procédé consiste en outre à transmettre, par l'intermédiaire d'un format 1 de canal partagé de liaison montante physique à bande étroite (NPUSCH), au nœud de réseau sur les mêmes ressources temps-fréquence partagées par d'autres UE de la pluralité d'UE. La pluralité d'UE transmet simultanément via la liaison montante physique à bande étroite pour une transmission à tonalité unique ou à tonalités multiples ayant un premier espacement de sous-porteuse (SCS). L'appareil de la pluralité de séquences d'OCC est relatif à un ou plusieurs symboles OFDM, un ou plusieurs intervalles de domaine temporel, ou une unité de ressource de domaine temporel.
PCT/IB2025/051800 2024-02-19 2025-02-19 Procédés de prise en charge de codes de couverture orthogonaux dans un ntn-iot Pending WO2025177182A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2024077502 2024-02-19
CNPCT/CN2024/077502 2024-02-19

Publications (1)

Publication Number Publication Date
WO2025177182A1 true WO2025177182A1 (fr) 2025-08-28

Family

ID=94871324

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/051800 Pending WO2025177182A1 (fr) 2024-02-19 2025-02-19 Procédés de prise en charge de codes de couverture orthogonaux dans un ntn-iot

Country Status (1)

Country Link
WO (1) WO2025177182A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190387383A1 (en) * 2017-03-24 2019-12-19 Intel IP Corporation DESIGN OF SCHEDULING REQUEST FOR FURTHER ENHANCED NARROWBAND INTERNET OF THINGS (feNB-IoT)
US20200236524A1 (en) * 2017-08-10 2020-07-23 Apple Inc. Uplink Transmission in TDD Supporting feNB-IOT Operation
US20210021393A1 (en) * 2016-01-08 2021-01-21 Apple Inc. Downlink hybrid automatic repeat request feedback for narrowband internet of things devices

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210021393A1 (en) * 2016-01-08 2021-01-21 Apple Inc. Downlink hybrid automatic repeat request feedback for narrowband internet of things devices
US20190387383A1 (en) * 2017-03-24 2019-12-19 Intel IP Corporation DESIGN OF SCHEDULING REQUEST FOR FURTHER ENHANCED NARROWBAND INTERNET OF THINGS (feNB-IoT)
US20200236524A1 (en) * 2017-08-10 2020-07-23 Apple Inc. Uplink Transmission in TDD Supporting feNB-IOT Operation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
UMER SALIM ET AL: "IoT-NTN uplink capacity/throughput enhancement", vol. RAN WG1, no. Athens, GR; 20240226 - 20240301, 18 February 2024 (2024-02-18), XP052568411, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_116/Docs/R1-2400629.zip R1-2400629_116_AI9114_R19_NTN_IoT_UL_Capacity.docx> [retrieved on 20240218] *
ZHANPING YIN ET AL: "IoT NTN uplink enhancement with NPRACH multiplexing", vol. RAN WG1, no. Athens, GR; 20240226 - 20240301, 18 February 2024 (2024-02-18), XP052568832, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_116/Docs/R1-2401061.zip R1-2401061.docx> [retrieved on 20240218] *

Similar Documents

Publication Publication Date Title
US20250184077A1 (en) Td-occ over nonconsecutive dm-rs symbols
US20250202651A1 (en) Dynamic Switching Between Legacy and Extended DMRS Procedures
WO2024241201A1 (fr) Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante
WO2024161343A1 (fr) Saut à décalage en peigne et à décalage cyclique srs combinés/séparés
WO2024209386A1 (fr) Procédés d&#39;association de paramètres de liaison montante à des trps pour une opération multi-trp basée sur des dci multiples
US20240430899A1 (en) Multi-slot physical layer downlink control channel (pdcch) monitoring
WO2023174859A1 (fr) Tables de port d&#39;antenne pour canal physique partagé de liaison montante ayant un nombre accru de codes de domaine de fréquence
WO2025177182A1 (fr) Procédés de prise en charge de codes de couverture orthogonaux dans un ntn-iot
EP4494293A1 (fr) Tables de ports d&#39;antenne pour canal partagé de liaison descendante physique avec un nombre accru de codes de division de fréquence
WO2025214148A1 (fr) Dispositif terminal, dispositif réseau et procédés dans ceux-ci permettant de faciliter une transmission basée sur un code de couverture orthogonale
US20240372678A1 (en) Physical downlink control channel monitoring for enhanced cross carrier scheduling
US20250247187A1 (en) Demodulation Reference Signal in a Communication Network
WO2025233912A1 (fr) Procédés d&#39;accusé de réception de rapport de faisceau initié par un ue
WO2025233531A1 (fr) Systèmes et procédés de gestion de ressources pour des transmissions de liaison montante basées sur un code de couverture orthogonal dans des réseaux non terrestres
WO2024141991A1 (fr) Systèmes et procédés pour motifs de signal de référence de densité dynamique
WO2025209950A1 (fr) Dispositif terminal et procédé dans celui-ci pour une transmission en liaison montante
WO2025079001A1 (fr) Correspondance de ports ptrs vers dmrs améliorée pour trois ue tx
WO2025079000A1 (fr) Commutation d&#39;antenne srs pour ue à 3 tx
WO2024150156A1 (fr) Estimation de canal pour transmissions précodées
WO2024127320A1 (fr) Amélioration de pt-rs pour plusieurs ports dmrs
WO2025230457A1 (fr) Nœud de réseau radio, équipement utilisateur et procédés de gestion de partage de spectre dans un réseau de communication sans fil
WO2025259141A1 (fr) Calcul de différence de paramètre de retard de nœud inter-réseau pour une transmission de liaison descendante conjointe cohérente
WO2025078972A1 (fr) Conception de ressources à trois ports de srs
WO2025177179A1 (fr) Configuration de ressource de domaine temporel sbfd
KR20250134637A (ko) 다중-trp 방식들을 위한 mac ce를 통한 통합 tci 상태들의 활성화를 위한 방법들

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: 25710135

Country of ref document: EP

Kind code of ref document: A1