[go: up one dir, main page]

WO2025212572A1 - Améliorations de la couverture pour ia embarquée - Google Patents

Améliorations de la couverture pour ia embarquée

Info

Publication number
WO2025212572A1
WO2025212572A1 PCT/US2025/022439 US2025022439W WO2025212572A1 WO 2025212572 A1 WO2025212572 A1 WO 2025212572A1 US 2025022439 W US2025022439 W US 2025022439W WO 2025212572 A1 WO2025212572 A1 WO 2025212572A1
Authority
WO
WIPO (PCT)
Prior art keywords
alot
transmission
reader
repetitions
value
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/US2025/022439
Other languages
English (en)
Inventor
Aata EL HAMSS
Paul Marinier
Erdem Bala
Martino Freda
Moon Il Lee
Remun KOIRALA
Janet Stern-Berkowitz
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.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025212572A1 publication Critical patent/WO2025212572A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0245—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal according to signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity

Definitions

  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • WTRU wireless transmit/receive unit
  • FIG. 6 is a flowchart of an example process performed by the AloT device.
  • a first type of AloT device that is capable of a peak power consumption around one micro watt, has energy storage and is not capable of DL or UL amplification was studied.
  • the first type of device ’s UL transmission is backscattered on a carrier wave provided externally
  • a third type of device that is capable of peak power consumption around few hundred micro watts, has energy storage and is capable of DL or UL amplification was studied.
  • the third type of device ’s UL transmission is generated internally by the device.
  • Topology 2 the AloT can communicate with intermediate node(s) that transfers the communication to the gNB.
  • Such intermediate node(s) can be a WTRU, repeater or IAB node, for example
  • the gNB may be responsible for scheduling the AloT device whereas for topology 2, the intermediate WTRU may be responsible for scheduling the AloT device.
  • the design of AloT targets different D2R transmission ranges that can be from 10 to 50 meters. For short distance, a short D2R transmission may be sufficient for the reader to be able to decode the transmission. For long distance, D2R transmission repetition may be needed to decode the transmission.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA singlecarrier FDMA
  • ZT-UW-DFT-S- OFDM zero-tail unique-word discrete Fourier transform Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though itwill be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs wireless transmit/receive units
  • RAN radio access network
  • ON core network
  • PSTN public switched telephone network
  • the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e , Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e , Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106.
  • the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • IP internet protocol
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit)
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li- ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors.
  • the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e g., for transmission) or the DL (e g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e g., for transmission) or the DL (e g., for reception)).
  • FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the ON 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the ON 106 may facilitate communications with other networks
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WL ⁇ N in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • DS Distribution System
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • IFFT Inverse Fast Fourier Transform
  • time domain processing may be done on each stream separately
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11ah relative to those used in 802.11n, and 802.11ac.
  • 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine- Type Communications (MTC), such as MTC devices in a macro coverage area.
  • MTC Meter Type Control/Machine- Type Communications
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • the AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
  • the CN 106 may facilitate communications with other networks
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers
  • the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network
  • the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • Enabling different communication range(s) for an AloT device may be needed.
  • the D2R transmission repetition may need to be adapted depending on the coverage need and the device’s synchronization capability.
  • loT operates in current 3GPP systems.
  • LTE supports NB-loT and MTC where devices use low power and can have large communication range.
  • the supported loT devices in LTE/NR are assumed to have better synchronization capability compared to AloT devices.
  • the transmissions timing may be changed and may impact the decoding performance at the receiver side
  • an AloT device may repeat the D2R transmission in time domain given a high SFO.
  • methods for determining the number of repetitions and/or the transmission duration as function of the synchronization capability, RSRP measurement of the D2R preamble transmission and the energy level of the device are provided
  • the reader may determine a number of repetitions and a duration of each repetition for D2R transmission for the AloT device (e.g., a same duration for each repetition or a separate duration for each repetition) based on one or more of the following: the determined maximum duration of the D2R transmission, the determined coverage level of the device, a payload of the transmission intended from the device to the reader, and a reported energy level of (e.g., by) the AloT device.
  • the reader may configure the device (e.g., sends a configuration or indication to the device) with the determined number of repetitions and the determined duration(s) for D2R transmission where each repetition is separated by a time gap.
  • the reader optionally also sends a timing offset threshold.
  • the reader may configure the device (e.g., sends a configuration or indication to the device) to do one or more of the following during one or more of the time gaps between the repetitions: transmit a signal (e.g., a midamble or preamble) to help determine the synchronization offset of the device, receive a signal (e.g., a preamble), e.g., for the reader to use to correct the synchronization of the device, perform energy harvesting and stop the remaining repetitions if the timing offset at the device is above the timing offset threshold.
  • a signal e.g., a midamble or preamble
  • receive a signal e.g., a preamble
  • the AloT device may receive a configuration or indication to perform one or more of the following during one or more of the time gaps between the repetitions: transmit a signal (e.g., a midamble or preamble) to help the reader determine the synchronization offset of the device, receive a signal (e.g., a preamble), e.g., for the reader to use to correct the synchronization of the device, perform energy harvesting, and determining if a timing offset between the AloT device transmission and a reader transmission is above the configured timing offset threshold: If the timing offset is above the timing offset threshold, the AloT device stops transmitting remaining repetitions.
  • a signal e.g., a midamble or preamble
  • the AloT device may transmit the D2R payload N times (corresponding to the configured or indicated number of repetitions, N) where the duration of each transmission (repetition i) is the duration D or the corresponding duration Di.
  • the AloT device performs one or more of the operation(s) configured or indicated to be performed during the time gaps.
  • the device can be configured to correct the synchronization and/or indicate its timing and/or energy harvest in between the repetitions to achieve the required coverage for the D2R transmission
  • a device may refer to Ambient loT device, loT device, Machine type communication (MTC) device or a WTRU with reduced capability (e.g., reduced power capability).
  • MTC Machine type communication
  • a reader may refer to gNB, Integrated Access Backhaul (IAB), a device acting as relay or an intermediate UE acting as a relay between the gNB and the device.
  • IAB Integrated Access Backhaul
  • a reader can be configured to schedule one or multiple devices simultaneously.
  • the reader can indicate to a group of devices using a multi-cast/group cast control information the scheduling parameters for the transmission.
  • Such parameters can include a coding scheme, modulation type, transmission duration, repetition number and frequency allocation.
  • the reader can indicate to one device using a unicast cast control information the scheduling parameters for the transmission.
  • scheduling parameters can include one or more of the following: coding scheme, modulation scheme, transmission duration, repetition number, frequency allocation, and transmit power.
  • the control information can be carried in a separate channel (e.g., reader to device control information channel) or can be carried with data channel (e.g., reader to device channel).
  • the reader can indicate explicitly each scheduling parameters to the device.
  • the reader can implicitly indicate the scheduling parameters to the device
  • the implicit scheduling parameters indication can be based on carrier waveform.
  • a carrier waveform can be associated with one or multiple scheduling parameters. For example, a first carrier waveform can be associated with a first modulation scheme and a second carrier waveform can be associated with a second modulation scheme. When the reader transmits the first waveform to be used by the device for backscattering, the device uses the first modulation scheme.
  • a carrier waveform can be characterized by frequency location and bandwidth size. For example, a first carrier waveform has B1 bandwidth, and a second carrier waveform has B2 waveform.
  • a transmission from a device to reader can be a transmission of data information, transmission of control information or preamble/midamble/postamble/reference signal transmission.
  • a D2R transmission can be transmitted following receiving a scheduling from a reader or alternatively initiated by the device. For example, a device can initiate a transmission for initial access.
  • the device can be pre-configured with one or multiple preamble/midamble/postamble/reference signal transmission parameters and the reader indicates to the device which preamble to use for the transmission.
  • Each preamble can be configured with different sequence.
  • a coverage level can be used by the reader to determine the transmission parameters of D2R transmission.
  • a coverage level can be associate with a distance between a reader and a device.
  • a first coverage level is associated with a first distance and a second coverage level is associated with a second distance.
  • a coverage level can be associate with a path loss between a reader and a device.
  • a first coverage level is associated with a first path loss and a second coverage level is associated with a second path loss.
  • a coverage level can be associate with RSRP measurements, in the reader, of a D2R transmission from a device.
  • a first coverage level is associated with a first RSRP range (RSRP is less that a threshold an above another threshold) and a second coverage level is associated with a second RSRP range (RSRP is less that a threshold an above another threshold).
  • a synchronization capability can be associated with sampling frequency offset (SFO).
  • SFO sampling frequency offset
  • a first value of SFO can be associated with a first synchronization capability and a second value of SFO can be associated with a second synchronization capability.
  • a synchronization capability can be associated with a jitter value. For example, for a first value of jitter can be associated with a first synchronization capability and a second value of jitter capability can be associated with a second synchronization capability.
  • Examples are provided below for a reader and a device to determine the maximum duration of D2R transmission, for a reader and a device to determine the number of repetitions for D2R transmission, and for a reader and a device to use a time gap between D2R transmission repetitions.
  • a device may be configured by the reader to transmit a D2R preamble(s) to help the reader determine the synchronization capability and/or determine the coverage level of the device.
  • the device can be configured to transmit such preamble separately (i.e., not multiplexed with other signal/channel) or, alternatively, the device can be configured to transmit the preamble multiplexed with data and/or control information.
  • the reader can indicate to the device using control information or data transmission the request to transmit the preamble. For example, the reader can indicate to the device using a bitfield in the data information a preamble transmission request.
  • the reader may transmit a reader to device (R2D) preamble to the device to trigger the device to transmit the preamble.
  • the device may transmit a preamble to the reader.
  • the device may determine autonomously to transmit the preamble to the reader. In an example, if the device determines that its time synchronization has drifted with X micro second from the time synchronization of the reader. The device may determine its time synchronization has drifted based on a received channel/signal from the reader. In another example solution, if the device cannot decode a transmission received from the reader, the device transmits the preamble.
  • a device may be configured to report the payload of D2R transmission to the reader.
  • the reader may determine the payload of D2R transmission.
  • the reader may determine the payload of D2R transmission based on the data type to be scheduled by the reader for the D2R transmission.
  • For each traffic type a set of pre-configured transmission payloads can be configured to the reader Depending on the information intended to be transmitted from the device to the reader, the reader selects the transmission payload accordingly.
  • the reader is configured with two types of traffic: location service and medical instruments inventory positioning. For location service a payload size of N1 bits is used for D2R transmission and for medical instruments inventory positioning N2 bits is used for D2R transmission.
  • the reader may determine the payload of D2R transmission based on scheduling request from the device. In an example, the reader may receive an indication of the payload of D2R transmission from a gNB
  • an intermediate WTRU is configured to be a reader and the gNB configures the intermediate WTRU with the payload of D2R transmission.
  • a device may be configured by a reader to report its energy level to the reader.
  • the reader can periodically request the device to report its energy level.
  • the reader can aperiodically request the device to report its energy level based on one or more of the following: received RSRP of a D2R transmission is below a configured threshold; expiry of timer where the reader can start a timer after receiving energy level from the device and after the expiry of the timer, the reader requests the device to report its energy level; after receiving a D2R transmission, for example, after each received D2R transmission, the reader can request the device to report its energy level; absence of D2R transmission for a period of time, for example, the reader can start a timer after receiving a D2R transmission and when another D2R transmission is received, the reader restarts the timer. After the expiry of the timer, the reader requests the device to report its energy level.
  • a reader can request a device to report its synchronization capability.
  • the device can report to the reader one of the following.
  • the timing shift e.g., the device can report a value of timing shift value within a preconfigured time window indicate by the reader.
  • the SFO e.g., the device can report a value of X parts per million (ppm).
  • the jitter e.g., the device can report the jitter period where the jitter period is the deviation of the device’s clock signal with respect to a reference point indicated by the reader.
  • a reader can determine the synchronization capability of a device based on a received preamble from the device.
  • the reader can determine the synchronization capability of the device based on one or more of the following.
  • the time reception of the preamble for example, when receiving the preamble from the device, the reader determines that there is a time offset (e.g., X micro) between the actual reception time and the expected time of reception.
  • the reader can determine the jitter/timing shift of the device by removing the estimated propagation delay from the time offset.
  • the frequency reception of the preamble for example, when receiving the preamble from the device, the reader determines that there is a frequency offset (e.g., Y Hz) between the actual reception frequency and the expected frequency of reception.
  • the reader can determine the SFO of the device by removing the estimated doppler shift from the frequency offset.
  • the reader may determine a maximum duration of a D2R transmission based on the synchronization capability of the device.
  • the reader can be configured by the network with a mapping between synchronization capability and a maximum duration.
  • the reader can be configured with a mapping between jitter values and maximum transmission duration.
  • the reader can be configured with a mapping between SFO values and maximum transmission duration.
  • the device may receive an indication from the reader indicating the maximum duration of D2R transmissions.
  • the maximum D2R duration can be indicated for all D2R transmissions or alternatively can be indicated for each transmission.
  • the device may receive the maximum transmission duration indication using a control information scheduling a D2R transmission or without scheduling D2R transmission.
  • a device may monitor signals from a reader or transmit according to a time pattern or duty cycle.
  • time pattern may be described as a sequence of alternating On and Off time periods wherein the device monitors signals only during the On periods.
  • the duration of an On period may be referred to as “On-duration”.
  • the reader may determine a maximum duration of a D2R transmission based on the timing of this D2R transmission with respect to the time pattern.
  • the maximum duration of a D2R transmission may be a function of the time difference between: the start time of the transmission and the start time of the on-going On-duration; and the end time of the on-going On-duration and the start time of the of the transmission.
  • the reader may determine that the maximum duration of a D2R transmission starting at time tO is a scaling factor (k) times the difference (t1-tO) where t1 corresponds to the end of the On period.
  • the scaling factor may represent the relative power consumption of reception compared to transmission.
  • the reader may obtain a value for the scaling factor k using one of the following: assuming a pre-defined value; requesting and receiving the value from the device; and receiving signaling from the network.
  • the number of repetitions for D2R transmission includes a coverage level determination, the number of repetitions, and a timing offset threshold.
  • the reader may determine the coverage level of a device based on measurements of one or more D2R transmissions received from the device.
  • the reader may be pre-configured with a set of measurements ranges, and each range is associated with a coverage level.
  • the reader determines the coverage level of the device based on the RSRP measurements of received D2R transmission from the device.
  • the reader may be pre-configured with a set of RSRP ranges, and each range is associated with a coverage level.
  • the reader may perform measurements on data channels, control channels or preamble/signal transmissions received from the device.
  • the reader may determine the coverage level of a device based on proximity detection. For example, a proximity detection procedure may be used by the reader to determine the distance between the reader and the device. The reader may be pre-configured with a distance ranges, and each range is associated with a coverage level. The determined distance can be used to determine the coverage level of the device.
  • a proximity detection procedure may be used by the reader to determine the distance between the reader and the device.
  • the reader may be pre-configured with a distance ranges, and each range is associated with a coverage level. The determined distance can be used to determine the coverage level of the device.
  • a proximity detection procedure may be used by the reader to determine the proximity of a device and may involve one or more of the following: RSRP measurements of signals transmitted by the device to the reader, RSRP measurements of signals transmitted by the reader to the device.
  • the device reports to the reader the measurement results, time difference of arrival (TDoA) measurements of signals transmitted by the device to the reader, time difference of arrival (TDoA) measurements of signals transmitted by the reader to the device and the device reports to the reader the measurement results, angle of arrival (AoA) measurements of signals transmitted by the device to the reader, angle of Departure (AoD) measurements of signals transmitted by the device to the reader, angle of arrival (AoA) measurements of signals transmitted by the reader to the device and the device reports to the reader the measurement results, angle of Departure (AoD) measurements of signals transmitted by the reader to the device where the device reports to the reader the measurement results, and round trip time (RTT) measurements of signals transmitted by the reader to the device and signals transmitted by the device to the reader where the device reports to the reader the reader
  • the reader may determine the number of repetitions and a duration of each repetition for D2R transmission for the AloT device based on one or more of the following: the determined maximum duration of the D2R transmission, the determined coverage level of the device, a payload of the transmission intended from the device to the reader, and a reported energy level of the device.
  • a reader may indicate to a device the same duration for each repetition.
  • the device is constrained to transmit the same coded bits in each repetition.
  • the reader configures the device with the same transmission duration for each repetition.
  • the reader may indicate to the device different duration for each repetition.
  • the reader first determines the number of repetitions (using the solution described above) where each repetition can have different number of coded bits and/or different redundancy version(s).
  • the reader determines the duration of each repetition (using the solution described above).
  • the reader configures the device (e.g., sends a configuration or indication to the device) with the determined number of repetitions and the determined duration(s) for D2R transmission where each repetition is separated by a time gap.
  • the device may receive the indication of the number of repetition and the duration for each repetition with the indicated scheduling parameters.
  • a reader can be configured a device with a timing offset threshold.
  • the device may use the timing offset threshold to determine whether to continue the D2R transmission and its repetitions.
  • the D2R transmission timing is shifted (due to synchronization capability) with an offset above the timing offset, the device stops transmitting the repetitions.
  • D2R repetitions with a time gap includes transmitting a signal to the reader, receiving a signal from the reader, energy harvesting, and early termination.
  • the reader may configure the device with a time gaps between the repetitions. For example, the reader may send a configuration or indication to the device with the time gap configuration. Such configuration can include time duration of the gap and a request the device to transmit a signal within the time gap to help determining the synchronization offset of the device.
  • the reader may indicate to the device to transmit a midamble occupying the time gap
  • the reader may indicate to the device to transmit a preamble preceding the transmission of the next repetition.
  • the reader may indicate to the device to transmit a postamble after the transmission of the repetition.
  • FIG. 2 illustrates a device 200 transmitting synchronization signal during the time gap 210.
  • the device 200 may receive a configuration or indication to transmit a signal within the time gap 210.
  • the device 200 may transmit a midamble 220 occupying the time gap 210
  • the device 200 may transmit a preamble 230 preceding the transmission of the next D2R repetition 260.
  • the device 200 may transmit a postamble 250 after the transmission of the D2R repetition 270.
  • the reader may indicate to the device to terminate transmission and not transmit any remaining repetitions.
  • the device may monitor a channel/signal from the reader wherein a message contained in the channel and/or a signal may indicate to the device to terminate transmission.
  • the absence of such indication from the reader may indicate to the device to continue transmitting the remaining repetitions.
  • the frequency of the gaps e.g., every gap, every other gap, etc.
  • the frequency of the gaps may be configured and/or signaled by the reader.
  • the device may send an indication (e.g., message) wherein the indication may be a request to terminate transmission
  • the message may contain a “cause” field, e.g., the cause may be low energy.
  • the causes may be specified and/or configured and may be identifiable with an associated set of bits For example, “00” may indicate low energy, “01” may indicate congestion, etc.
  • the reader may transmit an ACK to the device.
  • the reader may configure the device with a time gaps between the repetitions. For example, the reader may send a configuration or indication to the device with the time gap configuration. Such configuration can include time duration of the gap and scheduling/configuration to receive a signal within the time gap to help correcting the synchronization offset of the device.
  • the reader may schedule/configure the device to receive a signal occupying the time gap.
  • the reader may schedule/configure the device to receive a preamble preceding R2D transmission within the time gap.
  • the reader may schedule/configure the device to receive a postamble after R2D transmission within the time gap.
  • FIG. 3 illustrates a device 300 receiving synchronization signal during the time gap 310.
  • the device 300 may receive a configuration/scheduling to receive a signal within the time gap.
  • the device 300 may receive a signal 320 occupying the time gap 310.
  • the device 300 may receive a preamble 330 preceding R2D transmission signals 340 within the time gap 310.
  • the device 300 may receive a postamble 350 after R2D transmission signals 360 within the time gap 310.
  • the reader may configure the device with a time gaps between the repetitions.
  • the reader may send a configuration or indication to the device with the time gap configuration.
  • Such configuration can include time duration of the gap to allow the device to perform energy harvesting.
  • the device may perform energy harvesting during the time gap.
  • the device may receive the energy from the reader and/or external source of energy.
  • the device may receive a carrier waveform from the reader to charge its battery.
  • the device may be configured to stop harvesting energy if the energy level in the device is above a configured threshold.
  • Such energy threshold can be configured or indicated by the reader when configuring the time gap.
  • the device may be configured to continue harvesting energy during the entire time gap duration.
  • the reader may configure/indicate to the device to stop the remaining repetitions if the timing offset at the device is above the timing offset threshold. If the device timing offset is above the timing offset threshold, the device stops transmitting remaining repetitions.
  • the device may determine during the time gap its timing offset relative to the reader timing offset.
  • the device may receive a signal from the reader to help determining the timing offset relative the reader timing.
  • the device may measure the time duration between two received signals from the reader, where the time duration is already indicated by the reader to the device. The timing offset is calculated as the difference between the device determination of the time duration and the time duration indication from the reader.
  • the device can request/i ndicate to the reader to stop the repetition.
  • the device can indicate the request to stop using a pre-configured signal.
  • the device can be configured with a first timing offset for transmitting the request/indication to stop the repetition and a second timing offset for stopping the repetition. If the device timing offset is above the first timing offset threshold, the device sends a request to stop the repetition. If the device timing offset is above the second timing offset threshold, the device stops the repetition.
  • the method of any of the preceding examples comprising determining a maximum duration of a D2R transmission based on a synchronization capability of an AloT device.
  • the method of any of the preceding examples comprising the synchronization capability including at least one of timing shift, timing drift, SFO or jitter.
  • the method of any of the preceding examples comprising determining the synchronization capability of the AloT device based on a preamble transmission received from the AloT device.
  • the method of any of the preceding examples comprising requesting the synchronization capability from the AloT device and receiving the requested capability information.
  • the method of any of the preceding examples comprising determining a coverage level of the AloT device based on measurements (e.g., RSRP measurements) being within a measurement range and/or proximity to the device.
  • the method of any of the preceding examples comprising determining a number of repetitions and a duration of each repetition for D2R transmission for the AloT device (e.g., a same duration for each repetition or a separate duration for each repetition) based on one or more of the following: the determined maximum duration of the D2R transmission; the determined coverage level of the device; a payload of the transmission intended from the device to the reader; and a reported energy level of (e.g., by) the AloT device.
  • FIG. 4 illustrates a method 400 for the reader.
  • the reader performing method 400 may determine a maximum duration of a D2R transmission based on a synchronization capability of an AloT device (e.g., timing shift, timing drift, SFO or jitter).
  • the reader determines the synchronization capability of the AloT device based on a preamble transmission received from the AloT device.
  • the reader requests the synchronization capability from the AloT device and the reader receives the requested capability information.
  • the reader performing method 400 may determine a number of repetitions and a duration of each repetition for D2R transmission for the AloT device (e.g., a same duration for each repetition or a separate duration for each repetition) based on one or more of the following: the determined maximum duration of the D2R transmission; the determined coverage level of the device; a payload of the transmission intended from the device to the reader; and a reported energy level of (e.g., by) the AloT device
  • An AloT device performing method 500, at 510, may report its synchronization capability, e.g., based on a request from the reader, or transmits a signal (e.g., a preamble) to enable the reader to determine the synchronization capability of the AloT device.
  • a signal e.g., a preamble
  • the transmission of the preamble may be based on a request from the reader
  • the AloT device performing method 500, at 520 may transmit (e.g., reports) to the reader one or more of the following, e.g , based on a request received from the reader including a preamble transmission to the reader, e.g., to determine a coverage level of the AloT device, a payload of a D2R transmission, and an energy level of the AloT device.
  • the AloT device performing method 500 may receive a configuration or indication of a timing offset threshold.
  • the AloT device performing method 500, at 540, may receive a configuration or indication to perform one or more of the following during one or more of the time gaps between the repetitions: transmit a signal (e g., a midamble or preamble) to help the reader determine the synchronization offset of the device; receive a signal (e.g., a preamble), e.g., for the reader to use to correct the synchronization of the device; perform energy harvesting; determining if a timing offset between the AloT device transmission and a reader transmission is above the configured timing offset threshold including if the timing offset is above the timing offset threshold, the AloT device stops transmitting remaining repetitions
  • a signal e.g., a midamble or preamble
  • the AloT device may transmit the D2R payload N times (corresponding to the configured or indicated number of repetitions, N) where the duration of each transmission (repetition i) is the duration D or the corresponding duration Di.
  • the AloT device performs one or more of the operation(s) configured or indicated to be performed during the time gaps.
  • FIG. 6 is a flowchart of an example process performed by the AloT device.
  • process 600 may include determining a maximum duration of a device-to-reader (D2R) transmission based on a synchronization capability of an ambient loT (AloT) device at 602
  • a reader device for example a WTRU, may determine a maximum duration of a device-to-reader (D2R) transmission based on a synchronization capability of an AloT device, as described above.
  • process 600 at 604, may include determining a coverage level of the AloT device based on at least one of a signal measurement or proximity detection.
  • the reader device may determine a coverage level of the AloT device based on at least one of a signal measurement or proximity detection, as described above.
  • process 600 at 606 may include determining a number of repetitions and a corresponding duration of each repetition for a D2R transmission based on at least one of: the determined maximum duration of the D2R transmission, or the determined coverage level of the AloT device, where each repetition of the D2R transmission has a same or a distinct duration.
  • the reader device may determine a number of repetitions and a corresponding duration of each repetition for a D2R transmission based on at least one of: the determined maximum duration of the D2R transmission, or the determined coverage level of the AloT device, where each repetition of the D2R transmission has a same or a distinct duration, as described above.
  • process 600, at 608, may include sending configuration information to the AloT device, the configuration information indicating the determined number of repetitions and a respective duration for each repetition of the D2R transmission, where each repetition is separated by a time gap.
  • the reader device may send configuration information to the AloT device, the configuration information indicating the determined number of repetitions and a respective duration for each repetition of the D2R transmission, where each repetition is separated by a time gap, as described above.
  • process 600 at 610 may include sending an indication message to the AloT device, the indication message instructing the AloT device to perform one or more operations during one or more time gaps between repetitions of the D2R transmission, the one or more operations including: transmitting a midamble signal, transmitting a preamble signal, receiving a preamble signal, performing energy harvesting, or stopping remaining D2R transmission repetitions.
  • Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. re

Landscapes

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

Abstract

Dans certains modes de réalisation, un dispositif lecteur peut déterminer la durée maximale d'une transmission de dispositif à lecteur (D2R) sur la base d'une capacité de synchronisation d'un dispositif intelligence artificielle (IA) embarquée. Le dispositif lecteur peut déterminer un niveau de couverture du dispositif d'IA embarquée sur la base d'une mesure de signal ou d'une détection de proximité. Le lecteur peut déterminer un nombre de répétitions et une durée correspondante de chaque répétition pour une transmission D2R sur la base de la durée maximale déterminée de la transmission D2R et/ou du niveau de couverture déterminé du dispositif IA embarquée. Le lecteur peut envoyer des informations de configuration à l'IA embarquée indiquant le nombre déterminé de répétitions et une durée respective pour chaque répétition, chaque répétition étant séparée par un intervalle de temps. Le lecteur peut envoyer un message d'indication au dispositif IA embarquée lui ordonnant d'effectuer une ou plusieurs opérations pendant un ou plusieurs intervalles de temps entre des répétitions de la transmission D2R.
PCT/US2025/022439 2024-04-01 2025-04-01 Améliorations de la couverture pour ia embarquée Pending WO2025212572A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463572649P 2024-04-01 2024-04-01
US63/572,649 2024-04-01

Publications (1)

Publication Number Publication Date
WO2025212572A1 true WO2025212572A1 (fr) 2025-10-09

Family

ID=95554823

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/022439 Pending WO2025212572A1 (fr) 2024-04-01 2025-04-01 Améliorations de la couverture pour ia embarquée

Country Status (1)

Country Link
WO (1) WO2025212572A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
JOHAN BERGMAN ET AL: "Downlink and uplink channel/signal aspects for Ambient IoT", vol. RAN WG1, no. Athens, GR; 20240226 - 20240301, 19 February 2024 (2024-02-19), XP052567865, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_116/Docs/R1-2400079.zip R1-2400079 Downlink and uplink channel and signal aspects for Ambient IoT.docx> [retrieved on 20240219] *
PATRICK MERIAS ET AL: "Final feature lead summary on downlink and uplink channel/signal aspects", vol. RAN WG1, no. Athens, GR; 20240226 - 20240301, 1 March 2024 (2024-03-01), XP052577884, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_116/Docs/R1-2401857.zip R1-2401857_Final_Summary_9_4_2_3.docx> [retrieved on 20240301] *

Similar Documents

Publication Publication Date Title
US20240188153A1 (en) Nr positioning - methods for resource provision in sidelink positioning
EP4075871B1 (fr) Relocalisation de plan d&#39;utilisateur
US11412446B2 (en) Network energy efficiency
EP4515831A1 (fr) Procédés, appareil et systèmes pour mesure d&#39;étalement de retards, comptes-rendus et détermination de préfixe cyclique
EP4381313A1 (fr) Activation de positionnement dans un spectre sans licence
WO2025034872A1 (fr) Coordination inter-wtru pour sélection de porteuse
WO2025212572A1 (fr) Améliorations de la couverture pour ia embarquée
US20240147410A1 (en) Methods and Systems for Positioning Group Monitoring and Maintenance
WO2025235531A1 (fr) Procédés de planification de dispositifs aiot avec un temps de traitement différent
WO2025035098A1 (fr) Ensembles de pdu dl avec atsss
WO2025034830A1 (fr) Détermination d&#39;adéquation pour une surveillance de signal de réveil faible puissance (lp-wus) dans des états de rrc ou des configurations de lp-wus
WO2025240874A1 (fr) Détection et rapport d&#39;événements de rejet actif
EP4595666A1 (fr) Transmissions de signal de commande court
WO2025034792A1 (fr) Procédés pour opération basée sur un réseau assisté par relais effectuée par une wtru cible hors couverture
WO2024211333A1 (fr) Détermination de l&#39;inclusion d&#39;une mesure pru dans rapport de positionnement de liaison latérale
WO2025034794A1 (fr) Procédés de fonctionnement basé sur un réseau assisté par relais par une wtru d&#39;ancrage en couverture
WO2025075602A2 (fr) Division de qos dans un relais u2u
WO2024151934A1 (fr) Procédures pour rapporter un sinr et/ou un rssi avec une granularité dépendant de l&#39;application dans une détection de wlan
WO2024211337A1 (fr) Détermination d&#39;une mesure de positionnement pour calcul de positionnement
WO2025072897A1 (fr) Demande de resélection de relais indiquant un support de relais à sauts multiples
WO2025034795A1 (fr) Procédés de continuité de service pour wtru cible hors couverture
WO2024233954A1 (fr) Procédés de sélection par une unité d&#39;émission/réception sans fil (wtru) de client d&#39;une wtru de serveur de positionnement par état d&#39;une wtru
WO2025034750A1 (fr) Sélection ou resélection de ressources pour une opération de réception discontinue de liaison latérale sur une wtru à sauts multiples vers des relais wtru
WO2025174890A1 (fr) Configuration et rapport de rejet d&#39;unité de données par paquets actifs pour des applications de réalité étendue
WO2025034873A1 (fr) Procédure de synchronisation

Legal Events

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

Ref document number: 25721652

Country of ref document: EP

Kind code of ref document: A1