[go: up one dir, main page]

WO2025194793A1 - Motif de tdd pour ntn de l'ido - Google Patents

Motif de tdd pour ntn de l'ido

Info

Publication number
WO2025194793A1
WO2025194793A1 PCT/CN2024/130033 CN2024130033W WO2025194793A1 WO 2025194793 A1 WO2025194793 A1 WO 2025194793A1 CN 2024130033 W CN2024130033 W CN 2024130033W WO 2025194793 A1 WO2025194793 A1 WO 2025194793A1
Authority
WO
WIPO (PCT)
Prior art keywords
time slots
time
tdd
iot
slots
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/CN2024/130033
Other languages
English (en)
Inventor
Zhi YAN
Hongmei Liu
Yuantao Zhang
Ruixiang MA
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.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
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 Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/130033 priority Critical patent/WO2025194793A1/fr
Publication of WO2025194793A1 publication Critical patent/WO2025194793A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to wireless communications, and more specifically to a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) .
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • a wireless communications system may include one or multiple network communication devices, such as base stations (BSs) , which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • BSs base stations
  • eNB eNodeB
  • gNB next-generation NodeB
  • Each network communication device such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • time resources e.g., symbols, slots, subframes, frames, or the like
  • frequency resources e.g., subcarriers, carriers
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • NTN non-terrestrial network
  • An NTN refers to a network or segments of a network using radio frequency (RF) resources on board a satellite.
  • the satellite in NTN may be a geostationary earth orbiting (GEO) satellite with a fixed location to the earth, or a low earth orbiting (LEO) satellite orbiting around the earth.
  • GEO geostationary earth orbiting
  • LEO low earth orbiting
  • 3GPP third generation partnership project
  • Rel-17 third generation partnership project
  • enhancements on NTN communication especially enhancements on a narrowband internet of things (NB-IoT) NTN to enable an NTN operation in an NB-IoT TDD mode are still needed.
  • NB-IoT narrowband internet of things
  • the present disclosure relates to a method, an apparatus, and a system that supports a TDD pattern for an IoT NTN. With the apparatus and method, it is allowed to support the TDD with flexibility for the IoT NTN.
  • a user equipment UE
  • the UE comprises at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a base station (BS) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap, and communicate with the BS based on the TDD pattern.
  • BS base station
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • a method performed by the UE comprises: receiving, from a base station (BS) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap, and communicating with the BS based on the TDD pattern.
  • BS base station
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a base station (BS) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap, and communicate with the BS based on the TDD pattern.
  • BS base station
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • the target frame may comprise a narrowband internet of things (NB-IoT) frame.
  • NB-IoT narrowband internet of things
  • the time offset may be a time offset of a start of the set of DL time slots or an end of the set of UL time slots relative to a frame boundary of the target frame.
  • the set of UL time slots may be determined based on the set of DL time slots and the set of gap time slots between the set of DL time slots and the set of UL time slots.
  • At least one of the following may be indicated in the configuration or predefined: a period of the TDD pattern, a number of the set of DL time slots, a number of the set of UL time slots, a number of the set of gap time slots, or the time offset.
  • a number of the set of DL time slots or a number of the set of UL time slots may be indicated with a target granularity.
  • a target time slot of every target number of time slots among the set of DL time slots or the set of UL time slots may be determined as an invalid time slot.
  • a respective bit of the bitmap may indicate whether a respective time slot of the set of DL time slots or the set of UL time slots is a valid time slot.
  • a length of the bitmap may be associated with a number of the set of DL time slots or a number of the set of UL time slots.
  • a number of the set of DL time slots or a number of the set of UL time slots may be a constant number, and a length of the bitmap may be a constant length.
  • a base station comprising at least one memory, and at least one processor coupled with the at least one memory and configured to cause the BS to: transmit, to a user equipment (UE) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap, and communicate with the UE based on the TDD pattern.
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • a method performed by the BS comprises: transmitting, to a user equipment (UE) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap, and communicating with the UE based on the TDD pattern.
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a user equipment (UE) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap, and communicate with the UE based on the TDD pattern.
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • the target frame may comprise a narrowband internet of things (NB-IoT) frame.
  • NB-IoT narrowband internet of things
  • the time offset may be a time offset of a start of the set of DL time slots or an end of the set of UL time slots relative to a frame boundary of the target frame.
  • the set of UL time slots may be determined based on the set of DL time slots and the set of gap time slots between the set of DL time slots and the set of UL time slots.
  • At least one of the following may be indicated in the configuration or predefined: a period of the TDD pattern, a number of the set of DL time slots, a number of the set of UL time slots, a number of the set of gap time slots, or the time offset.
  • a number of the set of DL time slots or a number of the set of UL time slots may be indicated with a target granularity.
  • a target time slot of every target number of time slots among the set of DL time slots or the set of UL time slots may be determined as an invalid time slot.
  • a respective bit of the bitmap may indicate whether a respective time slot of the set of DL time slots or the set of UL time slots may be a valid time slot.
  • a length of the bitmap may be associated with a number of the set of DL time slots or a number of the set of UL time slots.
  • a number of the set of DL time slots or a number of the set of UL time slots may be a constant number, and a length of the bitmap may be a constant length.
  • FIG. 1A illustrates an example of a wireless communications system that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure
  • FIG. 1B illustrates an example communication in NTN associated with aspects of the present disclosure
  • FIG. 2 illustrates an example process flow in accordance with some example embodiments of the present disclosure
  • FIGS. 3A to 3I illustrate example TDD patterns in accordance with some example embodiments of the present disclosure
  • FIG. 4 illustrates an example of a device that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure
  • FIG. 5 illustrates an example of a processor that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure
  • FIGS. 6 through 7 illustrate flowcharts of methods that support a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • the term “communication network” refers to a network following any suitable communication standards, such as, 5G new radio (NR) , LTE, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) , and so on.
  • NR 5G new radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a UE and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the 4G, 4.5G, the 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • any suitable generation communication protocols including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the 4G, 4.5G, the 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.
  • the term “network device” generally refers to a node in a communication network via which a UE can access the communication network and receive services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , an infrastructure device for a vehicle-to-everything (V2X) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto a base station (BS) , a pico BS, and so forth, a
  • the network device may further refer to a network function (NF) in the core network, for example, a service management function (SMF) , an access and mobility management function (AMF) , a policy control function (PCF) , a user plane function (UPF) or devices with the same function in future network architectures, and so forth.
  • NF network function
  • SMF service management function
  • AMF access and mobility management function
  • PCF policy control function
  • UPF user plane function
  • UE user equipment
  • a UE generally refers to any end device that may be capable of wireless communications.
  • a UE may also be referred to as a communication device, a terminal device, an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) .
  • SS subscriber station
  • UAV unmanned aerial vehicle
  • MS mobile station
  • AT access terminal
  • the UE may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable UE, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture UE such as a digital camera, a gaming UE, a music storage and playback appliance, a vehicle-mounted wireless UE, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain
  • FIG. 1A illustrates an example of a wireless communications system (or referred to as a communication network) 100 that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may be implemented as a satellite.
  • the network entity 102 may have full or part of an eNB/gNB on board.
  • a network entity 102 in form of a satellite can directly communicate to UE 104 using NR/LTE Uu interface.
  • the satellite may be a transparent satellite or a regenerative satellite.
  • a base station on earth may communicate with a UE via the satellite.
  • a communication link 110 between the satellite and the UE 104, a communication link 110 between the satellite and a base station on earth, and a communication link 116 between the base station on earth and core network 106 may be used for the NTN transparent mode.
  • the base station may be on board and directly communicate with the UE.
  • a communication link 110 between the satellite and the UE 104, and a communication link 116 between the satellite (with full or part of an eNB/gNB on board) and core network 106 may be used for the NTN regenerative mode.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1A.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1A.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink (SL) .
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1 c, F1 u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links .
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • the legacy iridium system was proposed.
  • a new NB-IoT NTN TDD mode has been discussed, which allows configuring the usage of radio resources in an allocated band for a targeted mobile satellite service (MSS) (e.g., in the 1616-1626.5 MHz) with a periodic subset of UL and DL subframes in N radio frames (RFs) .
  • the TDD pattern may consist of a set of usable contiguous UL subframes and a set of usable contiguous DL subframes, and guard periods.
  • the framing of the Iridium TDMA structure as shown in FIG. 1B with a periodicity of 90ms may be with the following structure:
  • a UE receives, from a BS, a configuration of a TDD pattern for an IoT NTN.
  • the TDD pattern comprises one or more of a set of DL time slots, a set of gap time slots, or a set of uplink UL time slots. At least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap.
  • the UE communicates with the BS based on the TDD pattern.
  • this solution can support the TDD for the IoT NTN with flexibility. In this way, it is possible to improve the communication performance in the IoT NTN.
  • FIG. 2 illustrates an example process flow 200 in accordance with some example embodiments of the present disclosure.
  • the process 200 will be described with reference to FIG. 1A, and the process 200 may involve a UE 104 and a network entity 102 as shown in FIG. 1A.
  • the network entity 102 may be implemented as a satellite. It is to be understood that the steps and the order of the steps in FIG. 2 are merely for illustration, and not for limitation. It is to be understood that process 200 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the network entity 102 transmits, to the UE 104, a configuration of a TDD pattern for an IoT NTN.
  • the TDD pattern may be periodical. As an example, the period of the TDD pattern may be 90ms or any other period length.
  • the TDD pattern may comprise one or more of a set of DL time slots, a set of gap time slots, or a set of UL time slots.
  • the period of the TDD pattern may be indicated in the configuration of the TDD pattern or predefined.
  • the time slots may comprise subframes or any other types of time units.
  • the TDD pattern may comprise at least one of a set of consecutive DL time slots, a set of gap time slots, or a set of consecutive UL time slots sequentially.
  • one or more of the number of the set of DL time slots, the number of the set of UL time slots, or the number of the set of gap time slots may be indicated in the configuration of the TDD pattern.
  • the number of the set of DL time slots or the number of the set of UL time slots may be indicated with a target granularity (for example, a granularity of 8ms to be aligned with the legacy slot duration where the time duration of each legacy time slot of Iridium systems is 8.28ms long, or a granularity of 1ms) .
  • FIG. 3A illustrates a first example TDD pattern. As shown in FIG. 3A, the period of the TDD pattern is 90ms.
  • the number of the set of DL time slots is indicated to be 24 (that is, the TDD DL duration (i.e., the consecutive DL time slots) may be 24ms, corresponding to 3 legacy DL time slots of Iridium systems)
  • the number of the set of gap time slots is indicated to be 42 (that is, the TDD gap duration may be 42ms)
  • the number of the set of UL time slots is indicated to be 24 (that is, the TDD UL duration (i.e., the consecutive UL time slots) may be 24ms, corresponding to 3 legacy UL time slots of Iridium systems) .
  • one or more of the number of the set of DL time slots, the number of the set of UL time slots, or the number of the set of gap time slots may be a constant number.
  • one or more of the number of the set of DL time slots, the number of the set of UL time slots, and the number of the set of gap time slots may be predefined. In this case, these parameters of the TDD pattern may be assumed in an initial access.
  • the number of the set of DL time slots and/or the number of the set of gap time slots may be predefined as 8, 24, or 40 (that is, the TDD DL duration (i.e., the consecutive DL time slots) and/or the TDD UL duration (i.e., the consecutive UL time slots) may be 8ms, 24ms, or 40ms) .
  • FIG. 3B illustrates a second example TDD pattern. As shown in FIG. 3B, the period of the TDD pattern is 90ms. The consecutive DL time slots are 40ms, the TDD gap duration is 10ms, and the consecutive UL time slots are 40ms. In this case, it may be aligned with the current NB-IoT system.
  • the location of the set of DL time slots and the location of the set of UL time slots may be determined in a variety of ways, as will be discussed below.
  • the set of DL time slots and/or the set of UL time slots may be indicated based on a time offset (for example, denoted as deltaT) associated with a target frame in the time domain.
  • the target frame may comprise an NB-IoT frame.
  • the time offset may be indicated in the configuration of the TDD pattern. Alternatively or additionally, the time offset may be predefined, for example, specified as 3 or 4.
  • the location of the set of DL time slots may be determined based on a time offset of the start of the set of DL time slots relative to a frame boundary of the target frame.
  • the start of the set of DL time slots of the TDD pattern may be aligned with the deltaT after a reference time (i.e., the frame boundary) of the target frame.
  • the target frame may be frame 0 (i.e., frame with system frame number (SFN) 0)
  • the frame boundary may be the start of frame 0.
  • FIG. 3C illustrates a third example TDD pattern. As shown in FIG. 3C, the period of the TDD pattern is 90ms.
  • the set of DL time slots is determined based on the start of frame 0 and a deltaT with a value of 4.
  • the number of consecutive DL time slots is 8.
  • the target frame may be frame 0 and the frame boundary may be the end of frame 0; or the target frame may be frame 1 (i.e., frame with SFN 1) and the frame boundary may be the start of frame 1.
  • FIG. 3D illustrates a fourth example TDD pattern. As shown in FIG. 3D, the period of the TDD pattern is 90ms. The set of DL time slots is determined based on the end of frame 0 (or the start of frame 1) and a deltaT with a value of 4. The number of consecutive DL time slots is 8.
  • the location of the set of UL time slots may be determined based on a time offset of an end of the set of UL time slots relative to a frame boundary of the target frame.
  • the end of the set of UL time slots of the TDD pattern may be aligned with the deltaT after a reference time (i.e., the frame boundary) of the target frame.
  • the target frame may be frame 8 (i.e., frame with SFN 8) and the frame boundary may be the end of frame 8; or the target frame may be frame 9 (i.e., frame with SFN 9) and the frame boundary may be the start of frame 9.
  • 3E illustrates a fifth example TDD pattern.
  • the period of the TDD pattern is 90ms.
  • the set of UL time slots is determined based on the end of frame 8 (or the start of frame 9) and a deltaT with a value of 4.
  • the number of consecutive UL time slots is 24.
  • the set of UL time slots may be determined based on the set of DL time slots and the set of gap time slots between the set of DL time slots and the set of UL time slots. In this case, the set of UL time slots may be after the set of gap time slots and at the end of the TDD pattern.
  • FIG. 3F illustrates a sixth example TDD pattern. As shown in FIG. 3F, the period of the TDD pattern is 90ms. The set of UL time slots is determined based on the set of DL time slots and the set of gap time slots. The set of UL time slots starts after the set of gap time slots and at the end of the TDD pattern. The number of consecutive UL time slots is 24.
  • a target time slot of every target number of time slots among the set of DL time slots may be determined as an invalid time slot.
  • the first time slot of every 8ms may be assumed to be an invalid time slot, for example, to avoid the potential gap of the legacy system.
  • the network entity 102 may transmit, to the UE 104, an indication indicating whether the invalid time slot (s) exist or not in the set of DL time slots.
  • FIG. 3G illustrates a seventh example TDD pattern, in which the first subframe of every 8ms (except the first subframe of each TDD pattern period) is an invalid subframe.
  • whether a respective time slot of the set of DL time slots is valid or not may be indicated in a bitmap manner.
  • a respective bit of the bitmap may indicate whether a respective time slot of the set of DL time slots is a valid time slot.
  • the length of the bitmap may be associated with the number of the set of DL time slots. For the case as shown in FIG. 3G, a 24-bit bitmap of “111111110111111101111111” may be used to indicate the validity or invalidity of the set of DL time slots within each TDD pattern period.
  • a target time slot of every target number of time slots among the set of UL time slots may be determined as an invalid time slot.
  • the last time slot of every 8ms (except the last subframe of each TDD pattern period) may be assumed to be an invalid time slot, for example, to avoid the potential gap of the legacy system.
  • the network entity 102 may transmit, to the UE 104, an indication indicating whether the invalid time slot (s) exist or not in the set of UL time slots.
  • FIG. 3H illustrates an eighth example TDD pattern, in which the last frame of every 8ms is an invalid frame.
  • whether a respective time slot of the set of UL time slots is valid or not may be indicated with a bitmap manner.
  • a respective bit of the bitmap may indicate whether a respective time slot of the set of UL time slots is a valid time slot.
  • the length of the bitmap may be associated with the number of the set of UL time slots. For the case as shown in FIG. 3H, a 24-bit bitmap of “11111110111111101111111” may be used to indicate the validity or invalidity of the set of UL time slots within each TDD pattern period.
  • FIG. 3I illustrates a seventh example TDD pattern, to discuss a case where the same TDD pattern as that in FIG. 3B is used.
  • the period of the TDD pattern is 90ms.
  • the consecutive DL time slots are assumed to be 40ms, the TDD gap duration is assumed to be 10ms, and the consecutive UL time slots are assumed to be 40ms.
  • bitmaps are used to indicate the validity or invalidity of the set of DL time slots and the set of UL time slots (e.g., the NB-IoT legacy higher layer parameter “subframeBitmap” may be reused to indicate the valid and invalid subframe for the assumed consecutive DL time slots in the TDD pattern, and another similar parameter for uplink may be introduced to indicate the valid and invalid subframe for the assumed consecutive UL time slots) .
  • the length of each of these bitmaps is a constant length, i.e., 40. As shown, a 40-bit bitmap of “11011.... 1100.. 00” is used to indicate the validity or invalidity of the set of DL time slots and a 40-bit bitmap of “0....
  • 001101111 is used to indicate the validity or invalidity of the set of UL time slots, and the TDD gap duration is assumed to be 10ms, which can implicitly be increased by the indication of invalid subframes at the end part of the consecutive DL time slots and/or first part of the consecutive UL time slots.
  • the UE 104 may communicate with the network entity 102 based on the TDD configuration. For example, the UE 104 may receive a DL signal from the network entity 102 based on the TDD pattern. In this case, the UE 104 may receive a DL signal on the set of DL time slots of the TDD pattern. As another example, the UE 104 may transmit a UL signal based on the TDD pattern. In this case, the UE 104 may transmit a UL signal on the set of UL time slots of the TDD pattern.
  • a downlink data transmission may be skipped to a valid DL time slot (e.g. skipping all invalid DL time slots, TDD gap time slots and all UL time slots)
  • a UL data transmission may be skipped to the next valid UL time slot (e.g. skipping all DL time slots, TDD gap time slots and all invalid UL time slots) .
  • MSS Mobile Satellite Service
  • FIG. 4 illustrates an example of a device 400 that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure.
  • the device 400 may be an example of a UE 104 or a network entity 102 as described herein.
  • the device 400 may support wireless communication with one or more devices in the communication system.
  • the device 400 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 402, a memory 404, a transceiver 406, and, optionally, an I/O controller 408. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 402, the memory 404, the transceiver 406, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 402, the memory 404, the transceiver 406, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 402, the memory 404, the transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 402 and the memory 404 coupled with the processor 402 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404) .
  • the processor 402 may support wireless communication at the device 400 in accordance with examples as disclosed herein.
  • the processor 402 may be configured to operable to support a means for receiving, from a base station (BS) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap; and a means for communicating with the BS based on the TDD pattern.
  • BS base station
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • the processor 402 may be configured to operable to support a means for transmitting, to a user equipment (UE) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap; and a means for communicating with the UE based on the TDD pattern.
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • the processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 402 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 402.
  • the processor 402 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 404) to cause the device 400 to perform various functions of the present disclosure.
  • the memory 404 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 402 cause the device 400 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 402 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 404 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 408 may manage input and output signals for the device 400.
  • the I/O controller 408 may also manage peripherals not integrated into the device M02.
  • the I/O controller 408 may represent a physical connection or port to an external peripheral.
  • the I/O controller 408 may utilize an operating system such as or another known operating system.
  • the I/O controller 408 may be implemented as part of a processor, such as the processor 402.
  • a user may interact with the device 400 via the I/O controller 408 or via hardware components controlled by the I/O controller 408.
  • the device 400 may include a single antenna 410. However, in some other implementations, the device 400 may have more than one antenna 410 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 406 may communicate bi-directionally, via the one or more antennas 410, wired, or wireless links as described herein.
  • the transceiver 406 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 406 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 410 for transmission, and to demodulate packets received from the one or more antennas 410.
  • the transceiver 406 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 410 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 410 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 5 illustrates an example of a processor 500 that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure.
  • the processor 500 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 500 may include a controller 502 configured to perform various operations in accordance with examples as described herein.
  • the processor 500 may optionally include at least one memory 504, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 500 may optionally include one or more arithmetic-logic units (ALUs) 506.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 500) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 502 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein.
  • the controller 502 may operate as a control unit of the processor 500, generating control signals that manage the operation of various components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 504 and determine subsequent instruction (s) to be executed to cause the processor 500 to support various operations in accordance with examples as described herein.
  • the controller 502 may be configured to track memory address of instructions associated with the memory 504.
  • the controller 502 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 502 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein.
  • the controller 502 may be configured to manage flow of data within the processor 500.
  • the controller 502 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 500.
  • ALUs arithmetic logic units
  • the memory 504 may include one or more caches (e.g., memory local to or included in the processor 500 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500) . In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote to the processor 500) .
  • caches e.g., memory local to or included in the processor 500 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500) . In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote to the processor 500) .
  • the memory 504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the controller 502 and/or the processor 500 may be configured to execute computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions.
  • the processor 500 and/or the controller 502 may be coupled with or to the memory 504, and the processor 500, the controller 502, and the memory 504 may be configured to perform various functions described herein.
  • the processor 500 may include multiple processors and the memory 504 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 506 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 506 may reside within or on a processor chipset (e.g., the processor 500) .
  • the one or more ALUs 506 may reside external to the processor chipset (e.g., the processor 500) .
  • One or more ALUs 506 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 506 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 506 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 506 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 500 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 500 may be configured to or operable to support a means for receiving, from a base station (BS) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap; and a means for communicating with the BS based on the TDD pattern.
  • BS base station
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • the processor 500 may be configured to or operable to support a means for transmitting, to a user equipment (UE) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap; and a means for communicating with the UE based on the TDD pattern.
  • TDD time division duplex
  • IoT Internet of things
  • NTN non-terrestrial network
  • FIG. 6 illustrates a flowchart of a method 600 that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure.
  • the operations of the method 600 may be implemented by a device or its components as described herein.
  • the operations of the method 600 may be performed by a UE 104 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a base station (BS) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap.
  • the operations of 610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 610 may be performed by a UE 104 as described with reference to FIG. 1A.
  • the method may include communicating with the BS based on the TDD pattern.
  • the operations of 620 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 620 may be performed by a UE 104 as described with reference to FIG. 1A.
  • FIG. 7 illustrates a flowchart of a method 700 that supports a TDD pattern for an IoT NTN in accordance with aspects of the present disclosure.
  • the operations of the method 700 may be implemented by a device or its components as described herein.
  • the operations of the method 700 may be performed by a network entity 102 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, to a user equipment (UE) , a configuration of a time division duplex (TDD) pattern for an Internet of things (IoT) non-terrestrial network (NTN) , wherein the TDD pattern comprises one or more of a set of downlink (DL) time slots, a set of gap time slots, or a set of uplink (UL) time slots, and at least one of the set of DL time slots or the set of UL time slots is indicated based on at least one of a time offset associated with a target frame or a bitmap.
  • the operations of 710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 710 may be performed by a network entity 102 as described with reference to FIG. 1A.
  • the method may include communicating with the UE based on the TDD pattern.
  • the operations of 720 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 720 may be performed by a network entity 102 as described with reference to FIG. 1A.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • a “set” may include one or more elements.

Landscapes

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

Abstract

Divers aspects de la présente divulgation concernent un motif de duplexage par répartition dans le temps (TDD) pour un réseau non terrestre (NTN) de l'Internet des objets (IdO). Selon un aspect, un équipement utilisateur (UE) reçoit, en provenance d'une station de base (BS), une configuration d'un motif de TDD pour un NTN de l'IdO, le motif de TDD comprenant un ou plusieurs d'un ensemble de créneaux temporels de liaison descendante (DL), un ensemble de créneaux temporels d'intervalle, ou un ensemble de créneaux temporels de liaison montante (UL), et au moins l'un parmi l'ensemble de créneaux temporels de DL ou l'ensemble de créneaux temporels d'UL étant indiqué sur la base d'un décalage temporel associé à une trame cible et/ou d'un tableau de bits. De plus, l'UE communique avec la BS sur la base du motif de TDD. De cette manière, il est possible d'améliorer les performances de communication dans le NTN de l'IdO.
PCT/CN2024/130033 2024-11-05 2024-11-05 Motif de tdd pour ntn de l'ido Pending WO2025194793A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/130033 WO2025194793A1 (fr) 2024-11-05 2024-11-05 Motif de tdd pour ntn de l'ido

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/130033 WO2025194793A1 (fr) 2024-11-05 2024-11-05 Motif de tdd pour ntn de l'ido

Publications (1)

Publication Number Publication Date
WO2025194793A1 true WO2025194793A1 (fr) 2025-09-25

Family

ID=97138323

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/130033 Pending WO2025194793A1 (fr) 2024-11-05 2024-11-05 Motif de tdd pour ntn de l'ido

Country Status (1)

Country Link
WO (1) WO2025194793A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112292881A (zh) * 2018-06-08 2021-01-29 上海诺基亚贝尔股份有限公司 用于动态时分双工的偏差控制
WO2021163956A1 (fr) * 2020-02-20 2021-08-26 Qualcomm Incorporated Agrégation d'intervalles pour des communications d'autorisation configurée avec des stations de base
CN115396063A (zh) * 2022-08-10 2022-11-25 中国联合网络通信集团有限公司 帧结构配置方法、装置、存储介质及设备
WO2023132990A1 (fr) * 2022-01-06 2023-07-13 Qualcomm Incorporated Configuration d'écart de liaison montante
US20230224839A1 (en) * 2022-01-07 2023-07-13 Qualcomm Incorporated Reference timing for an uplink transmission in a non-terrestrial network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112292881A (zh) * 2018-06-08 2021-01-29 上海诺基亚贝尔股份有限公司 用于动态时分双工的偏差控制
WO2021163956A1 (fr) * 2020-02-20 2021-08-26 Qualcomm Incorporated Agrégation d'intervalles pour des communications d'autorisation configurée avec des stations de base
WO2023132990A1 (fr) * 2022-01-06 2023-07-13 Qualcomm Incorporated Configuration d'écart de liaison montante
US20230224839A1 (en) * 2022-01-07 2023-07-13 Qualcomm Incorporated Reference timing for an uplink transmission in a non-terrestrial network
CN115396063A (zh) * 2022-08-10 2022-11-25 中国联合网络通信集团有限公司 帧结构配置方法、装置、存储介质及设备

Similar Documents

Publication Publication Date Title
WO2025060447A1 (fr) Groupe d'occasions rach pour répétitions de préambule
WO2024156270A1 (fr) Synchronisation pour un dispositif iot ambiant
WO2024239688A1 (fr) Adaptation de ressources prach
WO2024187850A1 (fr) Sous-bande décalée pour duplex intégral
WO2025194793A1 (fr) Motif de tdd pour ntn de l'ido
WO2025194928A1 (fr) Communication basée sur un motif tdd pour un ntn de l'iot
WO2025161471A1 (fr) Transmission de msg3 pour accès aléatoire
WO2025123717A1 (fr) Ré-accès pour un système d'ido-a
WO2025241524A1 (fr) Configuration de radiorecherche
WO2025232267A1 (fr) Transmission sps pour un ntn de l'ido
WO2025107691A1 (fr) Répétitions pour transmission
WO2025200559A1 (fr) Adaptation de ressources de prach
WO2025161464A1 (fr) Accès aléatoire pour réseau non terrestre
WO2025161470A1 (fr) Valeurs temporelles maximales pour transmissions d2r
WO2025107615A1 (fr) Indication de saut relative à des intervalles de mesure
WO2025035824A1 (fr) Occasion de rach valide
WO2024169553A1 (fr) Détermination de signal de liaison descendante
WO2025200463A1 (fr) Adaptation de radiorecherche
WO2025145568A1 (fr) Détermination de ressources pour une transmission
WO2025246424A1 (fr) Amélioration de transmission dans un système a-iot
WO2025185218A1 (fr) Saut de fréquence dans un système a-ido
WO2025107665A1 (fr) Rapport d'avance temporelle pour équipement utilisateur semi-duplex
WO2025123719A1 (fr) Configuraton de wus
WO2024093394A1 (fr) Récupération d'informations système
WO2025241593A1 (fr) Signal d'alerte pour ntn

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

Country of ref document: EP

Kind code of ref document: A1