[go: up one dir, main page]

WO2025246424A1 - Amélioration de transmission dans un système a-iot - Google Patents

Amélioration de transmission dans un système a-iot

Info

Publication number
WO2025246424A1
WO2025246424A1 PCT/CN2025/075314 CN2025075314W WO2025246424A1 WO 2025246424 A1 WO2025246424 A1 WO 2025246424A1 CN 2025075314 W CN2025075314 W CN 2025075314W WO 2025246424 A1 WO2025246424 A1 WO 2025246424A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
bound
repetition
iot
control information
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/CN2025/075314
Other languages
English (en)
Inventor
Xin Guo
Haipeng Lei
Xiaodong Yu
Zhennian SUN
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/CN2025/075314 priority Critical patent/WO2025246424A1/fr
Publication of WO2025246424A1 publication Critical patent/WO2025246424A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Definitions

  • the present disclosure relates to wireless communications, and more specifically to a transmission enhancement in an ambient Internet of things (A-IoT) system.
  • A-IoT ambient Internet of things
  • 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
  • a wireless communication system may include an A-IoT device, which has a lower capability in terms of complexity and power consumption.
  • the wireless communication system may also be referred to as an A-IoT system.
  • Multiple topologies for example, Topologies 1 to 4, are supported for the A-IoT device.
  • Topology 1 the A-IoT device directly and bidirectionally communicates with a BS.
  • Topology 2 the A-IoT device communicates bidirectionally with an intermediate node between the A-IoT device and a BS.
  • Topology 3 the A-IoT device communicates uidirectionally with a BS and communicates uidirectionally with an assisting node.
  • the A-IoT device communicates bidirectionally with a UE.
  • some transmission enhancements in the A-IoT system especially, enhancements on a transmission (especially, a device-to-reader (D2R) transmission) in an A-IoT system considering one or more of the above topologies, are still needed.
  • D2R device-to-reader
  • the present disclosure relates to methods, apparatuses, and systems that support a transmission enhancement in an A-IoT system. With the apparatuses and methods, it is possible to improve communication performance in the A-IoT system.
  • a first device comprising at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first device to: perform a first transmission related to ambient Internet of things (A-IoT) communication to a second device; and receive, from the second device, at least one second transmission, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • a method performed by the first device comprises: performing a first transmission related to ambient Internet of things (A-IoT) communication to a second device; and receiving, from the second device, at least one second transmission, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: perform a first transmission related to ambient Internet of things (A-IoT) communication to a second device; and receive, from the second device, at least one second transmission, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • the configuration information may comprise at least one of the following: a new data indicator (NDI) ; a number of one or more accumulated transmitted second transmissions for same data; a number of one or more repetitions within the second transmission; a transport block size (TBS) of a repetition within the second transmission.
  • NDI new data indicator
  • TBS transport block size
  • an end of a repetition within the second transmission may be indicated based on at least one of a midamble within the second transmission, or a number of one or more repetitions within the second transmission. In some implementations of the method and the first device described herein, an end of a repetition within the second transmission may be indicated based on control information within the second transmission, the control information indicating a TBS of a repetition within the second transmission.
  • an end of the second transmission may be indicated based on at least one of a postamble within the second transmission, or a number of one or more repetitions within the second transmission. In some implementations of the method and the first device described herein, an end of the second transmission may be indicated based on control information within the second transmission, the control information indicating a TBS of a repetition within the second transmission and a number of one or more repetitions within the second transmission.
  • the at least second transmission may comprise one or more second transmissions for same data, and an end of a last second transmission of the one or more second transmissions for same data may be indicated based on at least one of a postamble within the last second transmission, or an NDI indicated in a next second transmission after the last second transmission.
  • the at least second transmission may comprise one or more second transmissions for same data, and an end of a last second transmission of the one or more second transmissions for same data may be indicated based on control information within the last second transmission, the control information indicating a TBS of a repetition within a second transmission of the one or more second transmissions, a number of one or more repetitions within a second transmission of the one or more second transmissions, and an NDI indicated in a next second transmission after the last second transmission.
  • the first transmission may comprise an indication indicating the second device to calibrate at least one bound of a window for communication between the first device and the second device.
  • at least one of a first guard period for calibrating a starting bound of the at least one bound or a second guard period for calibrating an ending bound of the at least one bound may be indicated in control information within the first transmission, or pre-defined.
  • a value range of a guard period for calibrating a bound of the at least one bound may be based on a length of the window, and the length of the window may be indicated in the first transmission.
  • the first device may comprise one of a relay, an integrated access backhaul (IAB) node, a user equipment (UE) , a repeater, or a base station (BS)
  • the second device may comprise an A-IoT device.
  • a second device comprising at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second device to: receive, from a first device, a first transmission related to ambient Internet of things (A-IoT) communication; and perform at least one second transmission to the first device, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • a method performed by the second device comprises: receiving, from a first device, a first transmission related to ambient Internet of things (A-IoT) communication; and performing at least one second transmission to the first device, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • 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 first device, a first transmission related to ambient Internet of things (A-IoT) communication; and perform at least one second transmission to the first device, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • the configuration information may comprise at least one of the following: a new data indicator (NDI) ; a number of one or more accumulated transmitted second transmissions for same data; a number of one or more repetitions within the second transmission; a transport block size (TBS) of a repetition within the second transmission.
  • NDI new data indicator
  • TBS transport block size
  • an end of a repetition within the second transmission may indicated based on at least one of a midamble within the second transmission, or a number of one or more repetitions within the second transmission. In some implementations of the method and the second device described herein, an end of a repetition within the second transmission may be indicated based on control information within the second transmission, the control information indicating a TBS of a repetition within the second transmission.
  • an end of the second transmission may be indicated based on at least one of a postamble within the second transmission, or a number of one or more repetitions within the second transmission. In some implementations of the method and the second device described herein, an end of the second transmission may be indicated based on control information within the second transmission, the control information indicating a TBS of a repetition within the second transmission and a number of one or more repetitions within the second transmission.
  • the at least second transmission may comprise one or more second transmissions for same data, and an end of a last second transmission of the one or more second transmissions for same data may be indicated based on at least one of a postamble within the last second transmission, or an NDI indicated in a next second transmission after the last second transmission.
  • the at least second transmission may comprise one or more second transmissions for same data, and an end of a last second transmission of the one or more second transmissions for same data may be indicated based on control information within the last second transmission, the control information indicating a TBS of a repetition within a second transmission of the one or more second transmissions, a number of one or more repetitions within a second transmission of the one or more second transmissions, and an NDI indicated in a next second transmission after the last second transmission.
  • the first transmission may comprise an indication indicating the second device to calibrate at least one bound of a window for communication between the first device and the second device.
  • at least one of a first guard period for calibrating a starting bound of the at least one bound or a second guard period for calibrating an ending bound of the at least one bound may be indicated in control information within the first transmission, or pre-defined.
  • a value range of a guard period for calibrating a bound of the at least one bound may be based on a length of the window, and the length of the window may be indicated in the first transmission.
  • the first device may comprise one of a relay, an integrated access backhaul (IAB) node, a user equipment (UE) , a repeater, or a base station (BS)
  • the second device may comprise an A-IoT device.
  • FIG. 1A illustrates an example of a wireless communications system that supports a transmission enhancement in an A-IoT system in accordance with aspects of the present disclosure
  • FIG. 1B illustrates an example of Topology 1 associated with aspects of the present disclosure
  • FIG. 1C illustrates an example of Topology 2 associated with aspects of the present disclosure
  • FIG. 1D illustrates an example of Topology 3 associated with aspects of the present disclosure
  • FIG. 1E illustrates an example of Topology 4 associated with aspects of the present disclosure
  • FIG. 1F illustrates another example of a wireless communications system associated with aspects of the present disclosure
  • FIG. 2 illustrates an example process flow in accordance with some example embodiments of the present disclosure
  • FIG. 3A illustrates an example D2R transmission in accordance with some example embodiments of the present disclosure
  • FIG. 3B illustrates an example preamble structure in accordance with some example embodiments of the present disclosure
  • FIG. 3C illustrates an example set of windows in accordance with some example embodiments of the present disclosure
  • FIG. 3D illustrates an example window calibration illustration in accordance with some example embodiments of the present disclosure
  • FIG. 4 illustrates an example of a device that supports a transmission enhancement in an A-IoT system in accordance with aspects of the present disclosure
  • FIG. 5 illustrates an example of a processor that supports a transmission enhancement in an A-IoT system in accordance with aspects of the present disclosure
  • FIGS. 6 through 7 illustrate flowcharts of methods that support a transmission enhancement in an A-IoT system 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) , long term evolution (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
  • the term “A-IoT device” refers to a device without batteries or with limited energy storage capabilities.
  • energy is provided by harvesting radio waves, light, motion, heat, or any other suitable source.
  • the A-IoT device can also be called a zero-power terminal, a near-zero power terminal, a passive IoT device, an ambient backscatter communication (AmBC) device, a tag, etc.
  • AmBC ambient backscatter communication
  • A-IoT has lower complexity and lower power consumption, and is suitable for more application scenarios.
  • D2R transmission refers to a transmission initiated by an A-IoT device and transmitted to a reader (such as a BS, an intermediate node, an assisting node, or a UE) .
  • a reader such as a BS, an intermediate node, an assisting node, or a UE
  • R2D transmission refers to a transmission initiated by a reader and transmitted to an A-IoT device.
  • FIG. 1A illustrates an example of a wireless communications system (or referred to as a communication network) 100 that supports a transmission enhancement in an A-IoT system 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) , 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 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.
  • 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, MAC layer) functionality and signaling, and may each be at least partially controlled by the CU.
  • L1 e.g., physical (PHY) layer
  • L2 radio link 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, N2, 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) .
  • FIG. 1B illustrates an example of Topology 1 associated with aspects of the present disclosure.
  • an A-IoT device 121 communicates with a BS 122 directly and bi-directionally.
  • the communication between the BS 122 and the A-IoT device 121 includes A-IoT data and/or signalling.
  • This topology includes a possibility of a transmission from the BS 122 to the A-IoT device 121 and a different possibility of a transmission from the A-IoT device 121 to the BS 122.
  • FIG. 1C illustrates an example of Topology 2 associated with aspects of the present disclosure.
  • an A-IoT device 131 communicates bidirectionally with an intermediate node 132 between the A-IoT device 131 and base station 133.
  • the intermediate node 132 may be a relay node, an IAB node, a UE, a repeater, etc., which is capable of A-IoT.
  • the intermediate node 132 transfers A-IoT data and/or signalling between the BS 133 and the A-IoT device 131.
  • Topology 3 may comprise two topology types, i.e., Topology 3A and Topology 3B.
  • FIG. 1D illustrates an example of Topology 3 with a topology type of 3B associated with aspects of the present disclosure.
  • an A-IoT device 141 receives data/signalling from a BS 142 and transmits data/signalling to an assisting node 143.
  • the assisting node 143 may be a relay, IAB, UE, repeater, etc. which is capable of A-IoT.
  • the example illustration of FIG. 1D also applies, only with the difference that it has the opposite direction of the A-IoT data/signaling.
  • an A-IoT device 141 transmits data/signalling to a BS 142, and receives data/signalling from an assisting node 143.
  • FIG. 1E illustrates an example of Topology 4 associated with aspects of the present disclosure.
  • an A-IoT device 151 communicates bidirectionally with a UE 152.
  • the communication between the UE 152 and the A-IoT device 151 includes A-IoT data and/or signalling.
  • the above communicate devices involved in Topologies 1 to 4 with reference to FIG. 1B to FIG. 1E may be implemented by devices involved in the wireless communications system 100 as described herein with reference to FIG. 1A.
  • the BS 122, the BS 133, or the BS 142 may be implemented by the base station 102 in FIG. 1A.
  • the BS intermediate node 132 (when implemented by a UE) , the assisting node 143 (when implemented by a UE) , or the UE 152 may be implemented by the UE 104 in FIG. 1A.
  • FIG. 1F illustrates another example of a wireless communications system 160 associated with aspects of the present disclosure.
  • the wireless communications system 160 may comprise a first device 161 and a second device 162.
  • the first device 161 and the second device 162 may perform communications.
  • the communication between the first device 161 and the second device 162 may be direct or indirect.
  • the first device 161 and/or the second device 162 may communicate with one or more further devices not shown in FIG. 1F.
  • the first device 161 may comprise the BS 122, and the second device 162 may comprise the A-IoT device 121.
  • the first device 161 may comprise the intermediate node 132, and the second device 162 may comprise the A-IoT device 131.
  • the first device 161 may comprise the BS 142 or the assisting node 143, and the second device 162 may comprise the A-IoT device 141.
  • the first device 161 may comprise the UE 152, and the second device 162 may comprise the A-IoT device 151.
  • the communications system 160 may include any suitable number of communication devices and any suitable number of communication links for implementing embodiments of the present disclosure.
  • frequency hopping is applied in a synchronized system where a fixed time unit and a frequency offset may be used to indicate a hopping pattern for the frequency hopping.
  • Frequency hopping can achieve many benefits. For example, considering a resource allocation where a frequency location does not change throughout a transmission, data for a user may be corrupted completely if some impairment happens at the specific frequency region where the data is carried. To solve this issue, frequency hopping is introduced starting from LTE. For example, a split resource allocation is introduced to each resource-block pair such that the two resource blocks of the resource-block pair are transmitted with a certain frequency gap in between, which is called slot-based frequency. The frequency hopping can achieve frequency diversity.
  • RAN1-led For the Ambient IoT DL and UL: ⁇ Frame structure, synchronization and timing, random access ⁇ Numerologies, bandwidths, and multiple access ⁇ Waveforms and modulations ⁇ Channel coding ⁇ Downlink channel/signal aspects ⁇ Uplink channel/signal aspects ⁇ Scheduling and timing relationships ⁇ Study necessary characteristics of carrier-wave waveform for a carrier wave provided externally to the Ambient IoT device, including for interference handling at Ambient IoT UL receiver, and at NR basestation. ⁇ For Topology 2, no difference in physical layer design from Topology 1.
  • carrier wave (CW) waveform 1 i.e., single-tone
  • CW waveform 1 with frequency hopping outperforms CW waveform 1 without frequency hopping in terms of frequency diversity gain.
  • CW waveform 2 i.e., dual-tone
  • PAPR peak to average power ratio
  • the frequency domain information of the frequency hopping pattern does not need to be indicated to the A-IoT device.
  • the D2R transmission may suffer from frequency resource split.
  • how to enhance the D2R transmission, especially, considering the impacts of frequency resource split on the D2R transmission is still an open issue to be solved.
  • Embodiments of the present disclosure provide a solution to resolve the above issue that occurred in the A-IoT communication system or any other applicable issue that the solution can solve.
  • a first device for example, a reader
  • performs a first transmission related to A-IoT communication to a second device for example, an A-IoT device
  • the first device receives, from a second device, at least one second transmission.
  • a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • this solution can decrease control signaling as well as the length of the second transmission, and thus decrease the impacts of frequency resource split on the second transmission. In this way, it is possible to improve communication performance in the A-IoT system.
  • FIG. 2 illustrates an example process flow 200 in accordance with some example embodiments of the present disclosure.
  • the processes 200 will be described with reference to FIG. 1F. 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 the 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 first device 161 performs (205) a transmission (also referred to as a first transmission or an R2D transmission) related to A-IoT communication to the second device 162.
  • the first transmission may trigger at least one transmission (also referred to as at least one second transmission or at least one D2R transmission) from the second device 162 to the first device 161.
  • the second device 162 performs (210) the at least one second transmission to the first device 161.
  • the at least one second transmission may be backscattered on a further transmission (also referred to as a third transmission) with frequency hopping.
  • the third transmission may comprise a CW transmission with frequency hopping provided by a CW provider (also referred to as a CW node) .
  • the CW node may transmit CW signals on two frequencies, i.e., frequency 1 and frequency 2, alternatively.
  • the frequency and time duration (also referred to as hop length) of each hop may be determined by the first device 161 and indicated to the CW node.
  • the repetition type may comprise block-level repetition or bit-level repetition.
  • the block level repetition all the bits received from a higher layer and/or physical layer (according to what is present) after the CRC attachment (if used) may be blockwise repeated Rblock times.
  • each bit after the CRC attachment (if used) may be repeated Rbit times.
  • each bit after both the CRC attachment (if used) and forward error correction (FEC) (if used) may be repeated Rbit times.
  • the block-level repetition may outperform the bit-level repetition in terms of reception performance and complexity.
  • a second transmission i.e., a D2R transmission
  • PDRCH physical device-to-reader channel
  • one or more D2R signals within the second transmission may be important to facilitate the reception of the second transmission.
  • FIG. 3A illustrates an example second transmission (i.e., an example D2R transmission) .
  • the D2R signals may be further divided according to the functions and the locations within the D2R transmission.
  • a possible design may be that the D2R transmission may comprise at least one of a preamble, a midamble, or a postamble.
  • the preamble/midamble/postamble may be a binary sequence.
  • D-TAS D2R timing acquisition signal
  • CFO carrier frequency offset
  • channel estimation channel estimation
  • interference estimation a D2R timing acquisition signal preceding each PDRCH may be included in the D2R transmission, for example, at least for timing acquisition (indicating the start of the D2R transmission in the time domain) , and may be studied potentially for SFO estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation.
  • a D-TAS structure using a preamble may be studied, for which a binary signal may be considered.
  • the use of the preamble in the D2R transmission may need to be considered.
  • the bandwidth and spectrum characteristics of the D2R transmission, and the channel coherence bandwidth may need to be taken into account.
  • the channel characteristics for different hops may need to be diverse, and thus channel estimation/timing tracking may need to be performed per hop.
  • the D2R transmission of each hop may start with a preamble for channel estimation/timing tracking.
  • layer 1 (L1) control information may not preferred to be defined for the D2R transmission, and high layer control information carried in the data part of the PDRCH may increase the latency for decoding information for the reception of the D2R transmission, and that it may be easy for sequence-based preamble to convey information.
  • the preamble of the D2R transmission may be suitable to convey configuration information for the second transmission especially considering the frequency hopping case.
  • a preamble of a second transmission of the at least one second transmission may indicate configuration information for the second transmission.
  • sequence-based preamble may be used to carry the configuration information to facilitate the reception of the second transmission at the first device 161.
  • the following implementations may be considered for the configuration information.
  • the configuration information may comprise an NDI.
  • the NDI may be defined to indicate that the D2R transmission is carrying new data (or transport block (TB) ) , compared to a previous D2R transmission.
  • the NDI may be defined by a one-bit indicator in the preamble to indicate two statuses.
  • the NDI may be set as TRUE to indicate new data (or TB)
  • the NDI may be set as FALSE to indicate the D2R transmission is repeated and carrying the same data (or TB) as the previous D2R transmission.
  • the NDI may facilitate combining decoding and may be efficient in terms of information bits.
  • the configuration information may comprise the number of one or more accumulated transmitted second transmissions for the same data.
  • the number of accumulated D2R transmission (s) for the same data (or TB) may be used to facilitate combining decoding.
  • this parameter be defined by a multi-bit indicator, and the number of bits may be determined by the maximized number of repeated D2R transmission (s) for the same data (or TB) .
  • the number of accumulated D2R transmission (s) for a sequence of D2R transmission (s) of the same data (or TB) may be labeled as 1, 2, 3, and so on.
  • the configuration information may comprise the number of one or more repetitions within the second transmission.
  • the number of repetition (s) carried within the D2R transmission may be indicated in the preamble of the D2R transmission.
  • this parameter may be defined by a multi-bit indicator, and the number of bits may be determined by the maximized number of repetition (s) within a D2R transmission.
  • the configuration information may comprise a TBS of a repetition within the second transmission.
  • the size of a TB for each repetition carried within the D2R transmission may be indicated in the preamble of the D2R transmission.
  • the TBS of a repetition may be defined to identify the end of a repetition.
  • this parameter may be defined by a multi-bit indicator, and the number of bits may be determined by the maximized size of a TB within a D2R transmission.
  • the preamble within the second transmission may be further divided into two parts, i.e., part 1 and part 2, as illustrated in FIG. 3B.
  • the part 1 may comprise a fixed sequence of binary bits, which may be used for the purpose of timing tracking and/or channel estimation.
  • the part 2 may be defined to carry the configuration information as described above to facilitate the reception of the D2R transmission.
  • a D2R signal within the D2R transmission may be used as an end timing signal to identify a corresponding end within the communication between the first device 161 and the second device 162.
  • the end of a repetition within the second transmission (which is not be the last repetition within the second transmission) may be indicated based on the midamble immediately following the repetition within the second transmission. For example, if the midamble immediately following the repetition is different from the preamble and the postamble within the second transmission, the midamble may be sufficient to identify the end of the repetition which is not the last repetition within the second transmission. Accordingly, the first device 161 may acquire the end of a repetition within the second transmission based on the midamble immediately following the repetition.
  • the end of a repetition within the second transmission (which is not be the last repetition within the second transmission) may be indicated based on a midamble immediately following the repetition within the second transmission, and the number of one or more repetitions within the second transmission. For example, if the midamble immediately following the repetition is as same as the part 1 (as shown in FIG. 3B) in the preamble within the second transmission, the end of the repetition within the second transmission may be indicated based on the midamble immediately following the repetition and the number of repetition (s) carried in the second transmission.
  • the midamble immediately following the repetition may be used to identify the end of the repetition and whether this repetition is the last repetition within the second transmission. Accordingly, the first device 161 may acquire the end of a repetition within the second transmission based on the midamble immediately following the repetition and the number of one or more repetitions within the second transmission.
  • the end of a repetition within the second transmission may be indicated based on control information within the second transmission.
  • the control information may indicate a TBS of a repetition within the second transmission.
  • the size of a repetition indicated in the control information may be used to identify a repetition within the second transmission. Accordingly, the first device 161 may acquire the end of a repetition within the second transmission based on the control information.
  • the end of the second transmission may be indicated based on a postamble within the second transmission. For example, if the postamble within the second transmission is different from the preamble and the postamble within the second transmission, the postamble may be sufficient to identify the end of the second transmission. Accordingly, the first device 161 may acquire the end of the second transmission based on the postamble within the second transmission.
  • the end of the second transmission may be indicated based on a postamble within the second transmission and the number of one or more repetitions within the second transmission. For example, if the postamble within the second transmission is the as same as the midamble within the second transmission, the postamble within the second transmission together with the number of repetition (s) within the second transmission may be used to identify the end of the second transmission. Accordingly, the first device 161 may acquire the end of the second transmission based on the postamble within the second transmission and the number of one or more repetitions within the second transmission.
  • the end of the second transmission may be indicated based on control information within the second transmission.
  • the control information may indicate a TBS of a repetition within the second transmission and the number of one or more repetitions within the second transmission.
  • the size of a repetition together with the number of repetition (s) within the second transmission indicated in the control information may be used to identify the end of the second transmission. Accordingly, the first device 161 may acquire the end of the second transmission based on the control information.
  • the first transmission may trigger one or more second transmissions for the same data (or TB) , and in this case, the end of a last second transmission of the one or more second transmissions for the same data (or TB) may be determined in a variety of ways as will be discussed below.
  • the end of a last second transmission of the one or more second transmissions for the same data (or TB) may be indicated based on a postamble within the last second transmission. For example, if the postamble within the last second transmission is different from the postamble within other second transmission (s) of the one or more second transmissions for the same data (or TB) , the postamble within the last second transmission may be sufficient to identify the end of the last second transmission for the same data (or TB) . As an example implementation, the postamble within the last second transmission may be a sequence of ‘0000’ or ‘1111’ . Accordingly, the first device 161 may acquire the end of the last second transmission of the one or more second transmissions based on the postamble within the last second transmission.
  • the end of a last second transmission of the one or more second transmissions for the same data (or TB) may be indicated based on a postamble within the last second transmission, and an NDI indicated in the next second transmission after the last second transmission. For example, if the postamble within the last second transmission is the same as the postamble within other second transmission (s) of the one or more second transmissions for the same data (or TB) , the postamble may be used to identify the end of the current second transmission, and an NDI indicated in the next second transmission (i.e., for new data) may be used to identify the current second transmission is the last second transmission for the data (or TB) .
  • the first device 161 may acquire the end of a last second transmission of the one or more second transmissions for the same data (or TB) based on the postamble within the last second transmission and the NDI indicated in the next second transmission after the last second transmission.
  • the end of a last second transmission of the one or more second transmissions for the same data (or TB) may be indicated based on control information within the last second transmission.
  • the control information may indicate a TBS of a repetition within a second transmission of the one or more second transmissions, the number of one or more repetitions within a second transmission of the one or more second transmissions, and an NDI indicated in a next second transmission after the last second transmission.
  • the size of a repetition together with the number of repetition (s) within a D2R transmission, and an NDI for the next second transmission indicated in the control information may be used to identify the end of a last second transmission for the same data (or TB) .
  • the first device 161 may indicate in the first transmission a set of windows for the communication between them. For example, a window of the set of windows may be used for the second 162 to monitor an R2D transmission from the first device 161, for example, in the random access procedure.
  • the time-domain information of the frequency hopping pattern i.e., a sequence of windows for a set of D2R transmissions, where each window may correspond to a frequency hop in the time domain
  • the sequence of windows may be defined by one or more parameters as will be discussed below. The one or more parameters may need to be indicated by the first device 161 to the second device 162 in the first transmission.
  • the one or more parameters for defining the set of windows may comprise a starting point of a first window of the set of windows.
  • the starting point of the first window may be defined to identify the starting of the first window within the sequence of windows.
  • the starting point may be indicated based on a reference point and a time gap between the reference point and the starting point of the first window.
  • the one or more parameters for defining the set of windows may comprise a length of a window of the set of windows. For example, if the window is used for a D2R transmission in the case of frequency hopping, the length of a window of the set of windows may be equal to a length of a corresponding hop in the frequency hopping pattern.
  • the one or more parameters for defining the set of windows may comprise the window number of the set of windows, i.e., the number of window (s) in the sequence. If the set of windows comprises multiple windows, the multiple windows may locate in a contiguous way in the time domain.
  • FIG. 3C illustrates an example set of windows. As shown in FIG. 3C, the starting point is determined based on the reference point and the time gap. The set of windows is determined based on the starting point, the length of one window, and the number of windows (for example, 3) .
  • the corresponding communication between the first device 161 and the second device 162 may be expected to be performed within a corresponding window of the set of windows.
  • the starting (or ending) boundary of a window of the set of windows determined by the second device 162 may tend to have an offset relative to the corresponding boundary of the actual window, for example, due to clock accuracy and SFO impacts on the second device 162. Consequently, the second transmission performed according to the boundary (ies) determined by the second device 162 may probably cross the boundary (ies) of the actual window.
  • the first transmission may comprise an indication (or an indicator) indicating the second device 162 to calibrate at least one bound of a window of the set of windows for the communication between the first device 161 and the second device 162.
  • a guard period (s) may be introduced when determining the bound (s) of the window.
  • the guard period (s) for the bound (s) of a window may be defined as a time offset (s) relative to the bound (s) of the window determined by a clock of the second device 162, and may be used to calibrate the bound (s) of the window.
  • a value range of a guard period for calibrating a bound of the at least one bound of the window may be based on a length (denoted as L) of the window indicated in the first transmission.
  • the value range of a guard period may be [-L, L] .
  • L may be the time-domain length of a hop (or a D2R window) .
  • the granularity of setting a guard period for calibrating a bound of the at least one bound of the window may be per device type.
  • the guard period (s) for calibrating the bound (s) of the window may be the same for the same device type.
  • the value (s) of the guard period (s) may be pre-defined or pre-configured in the second device 162. This case may be reasonable because the same device type may be equipped with the same level clock.
  • the granularity of setting a guard period for calibrating a bound of the at least one bound of the window may be per device.
  • the guard period (s) for calibrating the bound (s) of the window may be determined (or set) for each A-IoT device.
  • the value (s) of the guard period (s) for calibrating the bound (s) may be indicated in control information within the first transmission.
  • the value (s) of the bound (s) may be indicated to the second device 162 by the first device 161 after each round of calibration procedure.
  • the at least one bound of the window may comprise a starting bound of the window and an ending bound of the window.
  • a first guard period for calibrating the starting bound of the window and/or a second guard period for calibrating an ending bound of the window may be considered.
  • the first guard period for the starting bound may be defined as a time offset relative to the starting bound of the window (i.e., the actual window) , and may be used to calibrate the starting point of the window determined by the clock of the second device 162, and thus decrease the possibility that the starting bound of the window determined by the second device 162 exceeds the starting bound of the actual window.
  • the second guard period for the ending bound may be defined as a time offset relative to the ending bound of the window (i.e., the actual window) , and may be used to calibrate the ending point of the window determined by the clock of the second device 162, and thus decrease the possibility that the ending bound of the window determined by the second device 162 exceeds the ending bound of the actual window.
  • the first guard period and the second guard period may be the same.
  • the first guard period and the second guard period may be different. How to apply the first guard period and/or the second guard period in calibrating the starting bound and/or the ending bound of the window will be discussed respectively with reference to FIG. 3D, which illustrates an example window calibration illustration.
  • the starting point (e.g., determined by the internal clock of the second device 162)
  • the first guard period for calibrating the starting bound TS i may be denoted by GPS i
  • the calibrated starting point CS i may locate at the right side of the starting point TS i , as illustrated in FIG. 3D.
  • This case may occur when the starting bound TS i of the window determined by the clock of the second device 162 is expected to be earlier than the actual starting bound of this window. Otherwise, the calibrated starting point CS i may locate at the left side of the starting point TS i . This case may occur when the starting bound TS i of the window determined by the clock of the second device 162 is expected to be later than the actual starting bound of this window.
  • the starting point (e.g., determined by the internal clock of the second device 162)
  • the ending point may be TS i +L
  • the second guard period for calibrating the ending bound may be denoted by GPE i
  • the calibrated ending point CE i may locate at the left side of the starting point TS i +L, as illustrated in FIG. 3D.
  • the calibrated ending point CE i may locate at the right side of the ending point TS i +L. This case may occur when the ending bound TS i +L of the window determined by the clock of the second device 162 is expected to be earlier than the actual ending bound of this window.
  • the second device 162 may determine a window of the set of windows according to one or more parameters for defining the set of windows indicated in the first transmission, and then apply guard period (s) to the determined bound (s) of the window.
  • the guard period (s) may be obtained based on the control information in the received first transmission or pre-defined.
  • the corresponding communication between the first device 161 and the second device 162 may be performed within the calibrated bounds of the window.
  • the guard period (s) may be applied to avoid SFO impacts on determining the bound (s) of the window for a D2R transmission.
  • FIG. 4 illustrates an example of a device 400 that supports a transmission enhancement in an A-IoT system in accordance with aspects of the present disclosure.
  • the device 400 may be an example of a first device 161 or a second device 162 as described herein.
  • the device 400 may support wireless communication with one or more other devices in the A-IoT 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 performing a first transmission related to ambient Internet of things (A-IoT) communication to a second device; and a means for receiving, from the second device, at least one second transmission, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • the processor 402 may be configured to operable to support a means for receiving, from a first device, a first transmission related to ambient Internet of things (A-IoT) communication; and a means for performing at least one second transmission to the first device, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • 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 transmission enhancement in an A-IoT system 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 performing a first transmission related to ambient Internet of things (A-IoT) communication to a second device; and a means for receiving, from the second device, at least one second transmission, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • the processor 500 may be configured to or operable to support a means for receiving, from a first device, a first transmission related to ambient Internet of things (A-IoT) communication; and a means for performing at least one second transmission to the first device, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • A-IoT ambient Internet of things
  • FIG. 6 illustrates a flowchart of a method 600 that supports a transmission enhancement in an A-IoT system 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 first device 161 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 performing a first transmission related to ambient Internet of things (A-IoT) communication to a second device.
  • A-IoT ambient Internet of things
  • 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 first device 161 as described with reference to FIG. 1F.
  • the method may include receiving, from the second device, at least one second transmission, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • 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 first device 161 as described with reference to FIG. 1F.
  • FIG. 7 illustrates a flowchart of a method 700 that supports a transmission enhancement in an A-IoT system 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 second device 162 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 first device, a first transmission related to ambient Internet of things (A-IoT) communication.
  • A-IoT ambient Internet of things
  • 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 second device 162 with reference to FIG. 1F.
  • the method may include performing at least one second transmission to the first device, wherein a preamble of a second transmission of the at least one second transmission indicates configuration information for the second transmission.
  • 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 second device 162 with reference to FIG. 1F.
  • 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

  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation se rapportent à une amélioration de transmission dans un système de l'internet des objets ambiant (A-IoT). Selon un aspect, un premier dispositif (par exemple, un lecteur) effectue une première transmission associée à une communication A-IoT vers un second dispositif (par exemple, un dispositif A-IoT). De plus, le premier dispositif reçoit, en provenance d'un second dispositif, au moins une seconde transmission. Un préambule d'une seconde transmission de l'au moins une seconde transmission indique des informations de configuration pour la seconde transmission. Ainsi, il est possible d'améliorer les performances de communication dans le système A-IoT.
PCT/CN2025/075314 2025-01-26 2025-01-26 Amélioration de transmission dans un système a-iot Pending WO2025246424A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2025/075314 WO2025246424A1 (fr) 2025-01-26 2025-01-26 Amélioration de transmission dans un système a-iot

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2025/075314 WO2025246424A1 (fr) 2025-01-26 2025-01-26 Amélioration de transmission dans un système a-iot

Publications (1)

Publication Number Publication Date
WO2025246424A1 true WO2025246424A1 (fr) 2025-12-04

Family

ID=97869449

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/075314 Pending WO2025246424A1 (fr) 2025-01-26 2025-01-26 Amélioration de transmission dans un système a-iot

Country Status (1)

Country Link
WO (1) WO2025246424A1 (fr)

Similar Documents

Publication Publication Date Title
WO2024088019A1 (fr) Signalisation de rapport d'état de retard
WO2025060447A1 (fr) Groupe d'occasions rach pour répétitions de préambule
WO2024156270A1 (fr) Synchronisation pour un dispositif iot ambiant
WO2024093430A1 (fr) Gestion de données basée sur une configuration d'ensemble de pdu
WO2024187850A1 (fr) Sous-bande décalée pour duplex intégral
WO2025246424A1 (fr) Amélioration de transmission dans un système a-iot
WO2025236725A1 (fr) Transmission d2r basée sur un saut de fréquence dans un système iot
WO2025185218A1 (fr) Saut de fréquence dans un système a-ido
WO2025241580A1 (fr) Détermination de fréquence pour transmission d2r dans un système iot ambiant
WO2024250732A1 (fr) Commande pour système iot ambiant
WO2025194928A1 (fr) Communication basée sur un motif tdd pour un ntn de l'iot
WO2025194793A1 (fr) Motif de tdd pour ntn de l'ido
WO2025189793A1 (fr) Modulation à bande latérale d'un dispositif iot
WO2025232267A1 (fr) Transmission sps pour un ntn de l'ido
WO2025161490A1 (fr) Saut de fréquence dans un système iot
WO2025097815A1 (fr) Transmission dans un système d'ido-a
WO2025123717A1 (fr) Ré-accès pour un système d'ido-a
WO2025107665A1 (fr) Rapport d'avance temporelle pour équipement utilisateur semi-duplex
WO2025107615A1 (fr) Indication de saut relative à des intervalles de mesure
WO2025161388A1 (fr) Gestion de nœud d'onde porteuse dans un système d'ido-a
WO2025035788A1 (fr) Commande pour système d'ido-a
WO2025107692A1 (fr) Mesure d'interférence dans un système ido-a
WO2025030899A1 (fr) Accès aléatoire dans un système d'ido-a
WO2025161471A1 (fr) Transmission de msg3 pour accès aléatoire
WO2025123687A1 (fr) Mesure et rapport d'interférence dans un système d'ido-a