WO2025167140A1 - Id de strate d'accès de dispositif - Google Patents

Id de strate d'accès de dispositif

Info

Publication number
WO2025167140A1
WO2025167140A1 PCT/CN2024/122482 CN2024122482W WO2025167140A1 WO 2025167140 A1 WO2025167140 A1 WO 2025167140A1 CN 2024122482 W CN2024122482 W CN 2024122482W WO 2025167140 A1 WO2025167140 A1 WO 2025167140A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
reader
processor
random
cbra
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/122482
Other languages
English (en)
Inventor
Luning Liu
Jing HAN
Jie Hu
Lihua Yang
Haiming Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/122482 priority Critical patent/WO2025167140A1/fr
Publication of WO2025167140A1 publication Critical patent/WO2025167140A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • 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
  • IoT has attracted much attention in the wireless communication technical field. More ‘things’a re expected to be interconnected for improving productivity efficiency and increasing comforts of life. Most of the existing wireless IoT devices are powered by battery that need to be replaced or recharged manually. The automation and digitalization of various industries open numbers of new markets requiring new IoT technologies of supporting battery-less devices with no energy storage capability or devices with energy storage that do not need to be replaced or recharged manually. Regarding these IoT devices, it is needed to design the compact protocol stack and corresponding procedures e.g. paging, random access, data transmission etc. Thus, how to efficiently schedule communication with devices (for example, the IoT devices) becomes to be a key aspect.
  • the present disclosure relates to methods, apparatuses, and systems that support the operation related to communication based on an access stratum (AS) identifier (ID) of a device. Specifically, the present disclosure relates to procedure and signaling for the communication related to ambient internet of things (IoT) device.
  • AS access stratum
  • IoT internet of things
  • a first device transmits, to a second device, a reader to device (R2D) message comprising a first access stratum (AS) identifier (ID) for scheduling communication with the second device.
  • R2D reader to device
  • AS access stratum
  • ID first access stratum
  • a second AS ID obtained at the second device and the first AS ID are used by the second device to determine whether the R2D message is targeted to the second device.
  • the first device may further transmit, to the second device, information for obtaining the second AS ID.
  • the information comprises at least one of: a first indication of an AS ID, a second indication of generating an AS ID, or a random ID of the second device.
  • the random ID is obtained from Message 1 received from the second device for a contention-based random access (CBRA) .
  • CBRA contention-based random access
  • the first device may transmit the information comprising the random ID and without the first indication and second indication by the following: determine whether the random ID of the second device collides with a further AS ID of a third device associated with the first device; and based on determining that the random ID does not collide with the further AS ID, transmit the information comprising the random ID and without the first indication and the second indication to the second device.
  • the second indication of generating the second AS ID comprises a length of the second AS ID.
  • the first device may further receive, from the second device, a message comprising the second AS ID generated by the second device; and determine the second AS ID generated by the second device as the first AS ID to be comprised in the R2D message.
  • the message comprising the second AS ID further comprises a random ID, wherein the random ID is also contained in Message 1 received from the second device for CBRA.
  • At least one of the first AS ID or the second AS ID is valid before one of the following: a transmission of an Ambient Internet of Things (AIoT) paging message; a transmission of an access round trigger message; a transmission of an access occasion trigger message; a transmission of an end indication for a service for the second device; or a transmission or reception of the last message for the service.
  • AIoT Ambient Internet of Things
  • At least one of the first AS ID and the second AS ID are valid during a SLEEP status of the second device.
  • a plurality of AS IDs is determined for the second device with respect to a plurality of reader devices comprising the first device; and a validity of an AS ID of the plurality of AS IDs is associated with the reader device of the plurality of reader devices which uses the AS ID to schedule communication with the second device.
  • the first device is a first reader device
  • the second device is an Ambient Internet of Things (AIoT) device.
  • AIoT Ambient Internet of Things
  • the second device is assigned with a plurality of AS IDs by a plurality of reader devices comprising the first device; and the first AS ID or the second AS ID is different from a third AS ID that is assigned by another reader device of the plurality of reader devices to the second device.
  • the first device may further receive, from a core network (CN) device, an indication of a range of AS IDs for the first device, wherein the range of AS IDs does not overlap with another range of AS IDs indicated to another reader device of the plurality of reader devices.
  • CN core network
  • a second device obtains a second access stratum (AS) identifier (ID) of the second device, the second AS ID being for scheduling communication with the second device.
  • the second device receives, from a first device, a reader to device (R2D) message comprising a first AS ID.
  • the second device determines, based on the first AS and the second AS ID, whether the R2D message is targeted to the second device.
  • AS access stratum
  • R2D reader to device
  • the second device may determine whether the R2D message is targeted to the second device by the following: determine whether the first AS ID matches with the second AS ID; based on determining that the first AS ID matches with the second AS ID, determining that the R2D message is targeted to the second device; and based on determining that the first AS ID does not match with the second AS ID, determining that the R2D message is not targeted to the second device.
  • the second device may obtain the second AS ID by the following: receiving, from the first device, information for obtaining the second AS ID, wherein the information comprises at least one of: a first indication of an AS ID, a second indication of generating an AS ID, or a random ID of the second device, and wherein the random ID is obtained from Message 1 transmitted by the second device for a contention-based random access (CBRA) .
  • CBRA contention-based random access
  • the CBRA comprises a first type of CBRA and a second type of CBRA
  • the information for obtaining the second AS ID is transmitted in at least one of the following: Message 2 for a first type of CBRA or a second type of CBRA; Message 4 for the first type of CBRA; a R2D message after Message 3 for the first type of CBRA; or a R2D message after Message 1 for the second type of CBRA.
  • the second indication of generating the second AS ID comprises a length for the second AS ID.
  • the second device may further transmit, to the first device, a message comprising the second AS ID generated by the second device.
  • the message comprising the second AS ID further comprises a random ID of the second device, wherein the random ID is also contained in Message 1 transmitted by the second device for CBRA.
  • At least one of the first AS ID or the second AS ID is valid before at least one of the following: a reception of an Ambient Internet of Things (AIoT) paging message; a reception of an access round trigger message; a reception of an access occasion trigger message; a reception of an end indication for a service for the second device; or a reception or transmission of the last message for the service.
  • AIoT Ambient Internet of Things
  • a plurality of AS IDs is determined for the second device with respect to a plurality of reader devices comprising the first device; and a validity of an AS ID of the plurality of AS IDs is associated with a reader device of the plurality of reader devices which uses the AS ID to schedule communication with the second device.
  • the second device is assigned with a plurality of AS IDs by a plurality of reader devices comprising the first device; and the first AS ID or the second AS ID is different from a third AS ID that is assigned by another reader device of the plurality of reader devices to the second device.
  • the second device may further determine that the second AS ID is the same as another AS ID obtained for another reader device of a plurality of reader devices; and generate a fourth AS ID different from the second AS ID.
  • a processor for communication comprising: at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: transmit, to a second device, a reader to device (R2D) message comprising a first access stratum (AS) identifier (ID) for scheduling communication with the second device.
  • R2D reader to device
  • AS access stratum
  • ID access stratum
  • a method performed by a first device comprising: transmitting, to a second device, a reader to device (R2D) message comprising a first access stratum (AS) identifier (ID) for scheduling communication with the second device.
  • R2D reader to device
  • AS access stratum
  • ID access stratum
  • a method performed by a second device comprising: obtaining a second access stratum (AS) identifier (ID) of the second device, the second AS ID being for scheduling communication with the second device; receiving, from a first device, a reader to device (R2D) message comprising a first AS ID; and determining, based on the first AS and the second AS ID, whether the R2D message is targeted to the second device.
  • AS access stratum
  • ID second access stratum
  • R2D reader to device
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method according to any of the above methods.
  • FIG. 1A illustrates an example of a wireless communications system that supports the operation related to ambient internet of things (AIoT) device in accordance with aspects of the present disclosure.
  • AIoT ambient internet of things
  • FIG. 1B to FIG. 1D illustrate example communication scenarios involving the ambient IoT device in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example signaling process of communication related to AIoT device in accordance with some example embodiments of the present disclosure.
  • FIG. 3 illustrates an example of a device that supports the operation related to ambient IoT device in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a processor that supports the operation related to ambient IoT device in accordance with aspects of the present disclosure.
  • FIGS. 5 through 6 illustrate flowcharts of methods that support the operation related to ambient IoT device 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 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.
  • 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
  • terminal device generally refers to any end device that may be capable of wireless communications.
  • a terminal device may also be referred to as a communication device, a user equipment (UE) , 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) .
  • UE user equipment
  • SS subscriber station
  • UAV unmanned aerial vehicle
  • MS mobile station
  • AT access terminal
  • Reader refers to the device which communicates with the A-IoT device directly.
  • the reader may include the base station, user equipment, and any other wireless communication device.
  • the AIoT device needs to determine which of the messages or signaling from the reader device is targeted to this AIoT device.
  • the messages or signaling may include an identifier (ID) of an AIoT to which the message or signaling is targeted, such that the AIoT may determine whether the message is targeted to itself based on the identifier.
  • ID identifier
  • the permanent device ID of the AIoT device may be not suitable as the ID included in the messages/signaling due to its large size and potential security issues.
  • AS short access stratum
  • embodiments of the present disclosure provide a method for communication based on an access stratum (AS) identifier (ID) of a device, such as, an ambient Internet of things (IoT) device.
  • AS access stratum
  • ID an ambient Internet of things
  • a reader device transmits a reader to device (R2D) message to an AIoT device, and the R2D message includes a first AS ID for scheduling communication with the second device.
  • the AIoT device may use the first AS ID included in the R2D message and a second AS ID obtained at the AIoT device to determine whether the R2D message is targeted to the AIoT device.
  • the R2D message may be determined as to be targeted to the AIoT device. Otherwise, the R2D message is not targeted to the AIoT device.
  • the AS ID (first AS ID and/or second AS ID) may be assigned by the reader device, may be generated by the AIoT device and/or may be a random ID used by the AIoT device for the CBRA.
  • the communication between the reader devices and the AIoT devices can be scheduled and performed efficiently.
  • 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.
  • 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.
  • 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
  • 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.
  • 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 may include 14 symbols.
  • 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.
  • FIG. 1B to FIG. 1D illustrate example communication scenarios involving the ambient IoT device in accordance with aspects of the present disclosure. Specifically, in FIG. 1B to FIG. 1D, three different topologies involving the A-IoT device are shown.
  • the A-IoT devices are characterized in the study according to their energy storage capacity, and capability of generating RF signals for their transmissions. For example, the capability considers that a device has either: no energy storage at all; or limited energy storage. Relying on these storage capacities, the considering the following set of A-IoT devices: Device A: No energy storage, no independent signal generation/amplification, i.e. backscattering transmission; Device B: Has energy storage, no independent signal generation, i.e. backscattering transmission. Use of stored energy can include amplification for reflected signals; and Device C: Has energy storage, has independent signal generation, i.e., active RF components for transmission.
  • a limited energy storage can be different among implementations within Device B or implementations within Device C, and different between Device B and Device C. Such storage is expected to be order (s) of magnitude smaller than an NB-IoT device would typically include.
  • Device A, B, and C are able to demodulate control, data, etc. from the relevant entity in RAN according to connectivity topology.
  • the A-IoT devices may be classified based on its capability. Specifically, the A-IoT devices classified by their capabilities may include device 1 type, device 2a type, and device 2b type.
  • the device 1 type is capable of 1 ⁇ W peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, neither downlink (DL) nor uplink (UL) amplification in the device.
  • the device’s UL transmission is backscattered on a carrier wave provided externally.
  • the device 2a type is capable of a few hundred ⁇ W peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, both DL and/or UL amplification in the device.
  • SFO initial sampling frequency offset
  • the device’s UL transmission is backscattered on a carrier wave provided externally.
  • the device 2b type is capable of a few hundred ⁇ W peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, both DL and/or UL amplification in the device.
  • SFO initial sampling frequency offset
  • the device’s UL transmission is generated internally by the device.
  • the A-IoT device 130 directly and bidirectional communicates with a base station.
  • the base station may be the network entity 102 as shown in FIG. 1A. To discuss simplicity, the base station is also identified by the reference number 102.
  • the communication between the base station 102 and the ambient IoT device 130 includes A-IoT data and/or signaling.
  • This topology includes the possibility that the base station 102 that transmits to the A-IoT device 130 is different from another base station that receives from the A-IoT device 130.
  • the A-IoT device 130 communicates bidirectional with a UE.
  • the UE may be the UE 104 as shown in FIG. 1A. To discuss simplicity, the UE is also identified by the reference number 104.
  • the communication between UE and the A-IoT device 130 includes ambient IoT data and/or signaling.
  • the A-IoT device 130 communicates bidirectional with an intermediate node between the A-IoT device 130 and base station 102.
  • the intermediate node can be a relay, IAB node, UE, repeater, etc. which is capable of ambient IoT.
  • the intermediate node transfers ambient IoT data and/or signaling between BS 102 and the A-IoT device 130.
  • the intermediate node may be the network entity 102 and/or the UE 104 as shown in FIG. 1A.
  • the A-IoT device may be provided with a carrier wave from other node (s) either inside or outside the topology.
  • the links in each topology may be bidirectional or unidirectional.
  • BS, UE, assisting node, or intermediate node could be multiple BSs or UEs, respectively. That is, the A-IoT device may communicate with more than one nodes.
  • the mixture of indoor and outdoor placement of such nodes is regarded as a network implementation choice. Account would need to be taken of potential impact on device or node complexity. In the connectivity topologies, this does not imply the existence of multi-hop assisting or intermediate nodes.
  • the AIoT device may access to the network by initiating a procedure of contention-based random access (CBRA) .
  • CBRA contention-based random access
  • the CBRA may include two types of CBRA.
  • the first type of CBRA may refer to the “4 step” RA or “3 step” RA.
  • A-IoT Message 1 of the first type of CBRA the device (e.g., the IoT device 130) sends an ID to the reader. This ID is a random ID generated by device.
  • the reader echoes the ID received in Message 1. Further information may be included in Message based on RAN1 agreements.
  • A-IoT Message 3 of the first type of CBRA the device sends Device ID and/or any other upper layer data (depending on upper layer request) .
  • the device considers the contention resolution as successful, if the Message 2 including the same random ID in Message 1 is received.
  • the second type of CBRA may refer to the “2 step” CBRA.
  • Example Messages in the second type of CBRA are shown below.
  • the device e.g., the IoT device 130
  • the reader device may echo some information (e.g., random ID) from Message 1.
  • Message 2 may be supported.
  • the random ID (e.g., 16bits) may be also included in A-IoT Message 1, and the random ID is echoed in A-IoT Message 2.
  • FIG. 2 illustrates an example signaling process 200 of communication related to ambient IoT device in accordance with some example embodiments of the present disclosure.
  • the process 200A will be described with reference to FIGS. 1A to 1D.
  • the first device 210 in FIG. 2 may be a reader device associated with the first device 210.
  • the first device 210 may be the base station 102, the UE 104, an intermediate node or an assisting node as shown in FIGS. 1A to 1D.
  • the second device 220 in FIG. 2 may be the A-IoT device 130 in FIGS. 1B to 1D.
  • 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 210 may assign an AS ID to the second device.
  • the first device 210 may transmit (230) information 232 for obtaining the second AS ID to the second device 220.
  • the information 232 may include a first indication of an assigned AS ID.
  • the second device 220 may obtain the second AS ID by determining the AS ID indicated by the first indication as the second AS ID.
  • the assigned AS ID indicated by the first indication may be the same as the random ID in Message 1 received from the second device 220 for CBRA.
  • the second device 220 as AIoT device may transmit (222) Message 1 224 including a random ID of the second device 220 to the first device 210 to access the network.
  • the first device 210 may handle the contention for the AIoT devices in response to receiving (226) the Message 1.
  • the assigned AS ID indicated by the first indication may be the same as the random ID in Message 1 or different from the random ID in Message 1. The conditions for assigning the AS ID that is the same as the random ID will be further discussed below.
  • the first device 210 may determine that the random ID in Message 1 224 is reused as the AS ID for the scheduling communication with the second device 220.
  • the first device 210 may include the random ID obtained from the Message 1 into the Message 2.
  • the second device 220 may determine the confirmed random ID as the AS ID. Then, if the second device 220 detects that ID (e.g., a first AS ID) in the R2D message maps with the random ID confirmed as the AS ID, the second device 220 may decode the R2D message.
  • ID e.g., a first AS ID
  • the second device 220 may obtain the second AS ID by determining the confirmed random ID in Message 2 as the second AS ID for scheduling communication with the second device 220.
  • the second device 220 may obtain the second AS ID by determining the assigned AS ID as the second AS ID for subsequent communication.
  • the information 232 may indicate the second device 220 to generate the second AS ID or reuse the random ID transmitted in Message 1 as the second AS ID.
  • the first device 210 may explicitly or implicitly indicate, via e.g., Message 2, the second device 220 to use the random ID in Message as the second AS ID or generate a new AS ID.
  • the second device 220 may generate new AS ID as the second AS ID based on the second indication. If the first device 210 includes ‘random ID’ or ‘random ID in Message 1’ in the information 224, the second device 220 may use random ID in Message 1 as the second AS ID.
  • the second device 220 may generate AS ID based on the length. That is, the second indication of generating the AS ID may be a length of AS ID. In some embodiments, if the first device 210 does not include the length of the AS ID or does not include explicit indication of generating new AS ID, the second device 220 may directly determine the confirmed random ID in Message 1 as the second AS ID.
  • the first device 210 may request whether there’ re existing AS ID for the second device 220 from neighboring BS-readers or serving BS of UE-readers via Xn interface.
  • the first device 210 is a UE-reader, it may request whether there’ re existing AS ID for the device from neighboring UE-readers via PC5 interface if they can communicate directly.
  • UE-reader may request its serving base station to coordinate with other neighboring BSs to find whether there’ re existing AS ID for the second device 220.
  • the AS ID associated with first device 210 needs to be released, but the AS ID associated with the other reader device needs to be maintained. The details of release of the AS ID will be discussed in the following.
  • the second AS ID may be generated by the second device 220.
  • the second device 220 may generate different random IDs (for e.g. the case that the random ID is reused as the second AS ID) or AS IDs for different reader devices or services which may be ongoing during the same period, in order to avoid ID collision.
  • the second device 220 may generate the second AS ID for the first device, and generate a third AS ID that is different from the second AS ID for another reader device of the plurality of reader devices.
  • the second device 220 may need to re-generate a random ID/AS ID.
  • the second device 220 determines (270) , based on the first AS and the second AS ID, whether the R2D message is targeted to the second device. In some embodiments, the second device 220 may determine whether the first AS ID matches with the second AS ID. If the first AS ID matches with the second AS ID, the second device 220 may determine that the R2D message is targeted to the second device. Otherwise, the second device 220 may determine that the R2D message is not targeted to the second device.
  • the second device 220 may or may not include the AS ID in each D2R message for the current service. If the AS ID is not included in the D2R message, the second device 220 may be addressed by the resource of D2R message. As an example, the second device 220 may transmit (272) the D2R message 274 with or without the second AS ID. The first device 210 receives (276) the D2R message 274 accordingly. In turn, the first device 210 should include the AS ID (which is shown as the first AS ID in FIG. 2) in each R2D message if the AS ID is determined. Hence the second device 220 which receives the R2D message can know whether the message targets to itself.
  • the first device 210 and second device 220 may release the first AS ID and/or second AS ID in response to at least one of the following: the first and/or second AS ID being invalid, or a service for the second device being completed. In this way, the validity of the AS ID is considered. As such, the storage burden may be reduced.
  • the AS ID (including the first AS ID and the second AS ID) may be released if the current service for the second device is completed from the second device 220 and the first device 210.
  • the AS ID may be valid until the second device 220 receives a new access occasion trigger message which not includes the AS ID.
  • the AS ID may be valid until the second device 220 receives the ‘end’ indication from first device for the current service.
  • the AS ID may be valid until the second device 220 has completed a transmission of the last message of the current paging response.
  • the AS ID may be valid until the second device 220 has no energy/memory size to store the AS ID.
  • the AS ID may valid before the second device enters an OFF status.
  • the AS ID may be valid until the second device 220 is assigned with a new AS ID from the first device 210.
  • at least one of the first AS ID and the second AS ID may be valid during the SLEEP status of the second device. That is, the validity of AS ID may be impacted by the status of the second device 220
  • the random ID in Message 1 may be reused as the AS ID.
  • the AS ID may be valid until the second device 220 re-generates a new random ID for Message 1.
  • the second device 220 may re-generate a new random ID in Message 1 upon receiving an AIoT paging message.
  • the second device 220 may always use the newest random ID in Message 1 as the AS ID.
  • the second device 220 may generate the second AS ID which is not the random ID in Message 1.
  • the AS ID may be valid until device re-generates a new AS ID.
  • the second device 220 may re-generate a new random ID in Message 1 upon receiving the indication from reader.
  • the reader may indicate whether to use random ID in Message 1 as the AS ID or assign a new AS ID to the device explicitly or implicitly.
  • the AIoT device may generate another AS ID randomly as the AS ID other than use the random ID in Message 1 as the AS ID.
  • the reader indicates the AIoT device to use the random ID in Message 1 as the AS ID or generate a new AS ID explicitly or implicitly.
  • the AIoT device may or may not include the AS ID in each D2R message for the current service.
  • the AS ID design for multi-readers case is proposed.
  • the AS ID for different readers/services need to be different.
  • the AIoT device may store the association between reader/service and AS ID.
  • FIG. 3 illustrates an example of a device 300 that supports the communication related to ambient internet of things (IoT) device in accordance with aspects of the present disclosure.
  • the device 300 may be an example of the first device 210 or the second device 220 as described herein.
  • the device 300 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 300 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 302, a memory 304, a transceiver 306, and, optionally, an I/O controller 308. 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 302, the memory 304, the transceiver 306, 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 302, the memory 304, the transceiver 306, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 302, the memory 304, the transceiver 306, 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 302 and the memory 304 coupled with the processor 302 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 302, instructions stored in the memory 304) .
  • the processor 302 may support wireless communication at the device 300 in accordance with examples as disclosed herein.
  • the processor 302 may be configured to operable to support a means for the operation related to ambient internet of things (IoT) device.
  • IoT internet of things
  • the processor 400 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 controller 402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 404 and determine subsequent instruction (s) to be executed to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may be configured to track memory address of instructions associated with the memory 404.
  • the controller 402 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 402 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 400 to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may be configured to manage flow of data within the processor 400.
  • the controller 402 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 400.
  • ALUs arithmetic logic units
  • the one or more ALUs 400 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 400 may reside within or on a processor chipset (e.g., the processor 400) .
  • the one or more ALUs 400 may reside external to the processor chipset (e.g., the processor 400) .
  • One or more ALUs 400 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 400 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 400 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 1200 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 400 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 400 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 400 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 402 may be configured to or operable to support a means for the communication related to ambient internet of things (IoT) device.
  • IoT internet of things
  • FIG. 5 illustrates a flowchart of a method 500 that supports the operation related to ambient internet of things (IoT) device in accordance with aspects of the present disclosure.
  • the operations of the method 500 may be implemented by a device or its components as described herein.
  • the operations of the method 400 may be performed by the first device 210 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 first device 210 transmits, to a second device, a reader to device (R2D) message comprising a first access stratum (AS) identifier (ID) for scheduling communication with the second device.
  • R2D reader to device
  • AS access stratum
  • ID first access stratum
  • a second AS ID obtained at the second device and the first AS ID are used by the second device to determine whether the R2D message is targeted to the second device.
  • the first device may further transmit, to the second device, information for obtaining the second AS ID.
  • the information comprises at least one of: a first indication of an AS ID, a second indication of generating an AS ID, or a random ID of the second device.
  • the random ID is obtained from Message 1 received from the second device for a contention-based random access (CBRA) .
  • CBRA contention-based random access
  • the CBRA comprises a first type of CBRA and a second type of CBRA
  • the information for obtaining the second AS ID is transmitted in at least one of the following: Message 2 for a first type of CBRA or a second type of CBRA; Message 4 for the first type of CBRA; a R2D message after Message 3 for the first type of CBRA; or a R2D message after Message 1 for the second type of CBRA.
  • the information comprising the random ID and without the first indication and the second indication indicates the second device to determine the random ID as the second AS ID; the information comprising the first indication or the information comprising both the random ID and the first indication indicates the second device to determine the AS ID indicated by the first indication as the second AS ID; and/or the information comprising the second indication or the information comprising both the random ID and the second indication indicates the second device to generate the second AS ID.
  • the first device may transmit the information comprising the random ID and without the first indication and second indication by the following: determine whether the random ID of the second device collides with a further AS ID of a third device associated with the first device; and based on determining that the random ID does not collide with the further AS ID, transmit the information comprising the random ID and without the first indication and the second indication to the second device.
  • the second device is assigned with a plurality of AS IDs by a plurality of reader devices comprising the first device; and the first AS ID or the second AS ID is different from a third AS ID that is assigned by another reader device of the plurality of reader devices to the second device.
  • the first device is a terminal device reader, and the first device may communicate the information associated with the one or more AS IDs by: transmitting, to a network device, a request for communicating the information associated with the one or more AS IDs with one or more other network devices.
  • FIG. 6 illustrates a flowchart of a method 600 that supports the operation related to ambient internet of things (IoT) device in accordance with aspects of the present disclosure.
  • the operations of the method 600 may be implemented by a second device 220 or its components 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 second device 220 obtains a second access stratum (AS) identifier (ID) of the second device, the second AS ID being for scheduling communication with the second device.
  • the second device 220 receives, from a first device, a reader to device (R2D) message comprising a first AS ID.
  • R2D reader to device
  • the second device 630 determines, based on the first AS and the second AS ID, whether the R2D message is targeted to the second device.
  • the second device may obtain the second AS ID by the following: receiving, from the first device, information for obtaining the second AS ID, wherein the information comprises at least one of: a first indication of an AS ID, a second indication of generating an AS ID, or a random ID of the second device, and wherein the random ID is obtained from Message 1 transmitted by the second device for a contention-based random access (CBRA) .
  • CBRA contention-based random access
  • the second device may further transmit, to the first device, a message comprising the second AS ID generated by the second device.
  • At least one of the first AS ID or the second AS ID is valid before at least one of the following: a reception of an Ambient Internet of Things (AIoT) paging message; a reception of an access round trigger message; a reception of an access occasion trigger message; a reception of an end indication for a service for the second device; or a reception or transmission of the last message for the service.
  • AIoT Ambient Internet of Things
  • At least one of the first AS ID and the second AS ID are valid during the SLEEP status of the second device.
  • a plurality of AS IDs is determined for the second device with respect to a plurality of reader devices comprising the first device; and a validity of an AS ID of the plurality of AS IDs is associated with a reader device of the plurality of reader devices which uses the AS ID to schedule communication with the second device.
  • the second device is assigned with a plurality of AS IDs by a plurality of reader devices comprising the first device; and the first AS ID or the second AS ID is different from a third AS ID that is assigned by another reader device of the plurality of reader devices to the second device.
  • the second device may further: generate the second AS ID for the first device; generate a third AS ID that is different from the second AS ID for another reader device of a plurality of reader devices comprising the first device.
  • 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.
  • 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.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

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

Abstract

Divers aspects de la présente divulgation concernent la communication basée sur un identifiant (ID) de strate d'accès (AS) d'un dispositif, tel qu'un dispositif de l'Internet des objets (IoT) ambiant. Dans une solution de la divulgation, un premier dispositif transmet à un second dispositif un message de lecteur à dispositif (R2D) comprenant un premier ID d'AS pour planifier une communication avec le second dispositif. Un second ID d'AS obtenu au niveau du second dispositif et le premier ID d'AS sont utilisés par le second dispositif pour déterminer si le message R2D cible le second dispositif.
PCT/CN2024/122482 2024-09-29 2024-09-29 Id de strate d'accès de dispositif Pending WO2025167140A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/122482 WO2025167140A1 (fr) 2024-09-29 2024-09-29 Id de strate d'accès de dispositif

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/122482 WO2025167140A1 (fr) 2024-09-29 2024-09-29 Id de strate d'accès de dispositif

Publications (1)

Publication Number Publication Date
WO2025167140A1 true WO2025167140A1 (fr) 2025-08-14

Family

ID=96699090

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/122482 Pending WO2025167140A1 (fr) 2024-09-29 2024-09-29 Id de strate d'accès de dispositif

Country Status (1)

Country Link
WO (1) WO2025167140A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180041934A1 (en) * 2016-03-18 2018-02-08 Parallel Wireless, Inc. IuGW Architecture with RTP Localization
US20230043937A1 (en) * 2020-04-10 2023-02-09 Huawei Technologies Co., Ltd. Random access method and related device
WO2023246431A1 (fr) * 2022-06-22 2023-12-28 华为技术有限公司 Procédé et appareil de communication
WO2024001726A1 (fr) * 2022-06-30 2024-01-04 华为技术有限公司 Procédé et dispositif d'accès de terminal
WO2024159504A1 (fr) * 2023-02-03 2024-08-08 Qualcomm Incorporated Gestion de dispositif de l'internet des objets ambiant dans un réseau de communication mobile

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180041934A1 (en) * 2016-03-18 2018-02-08 Parallel Wireless, Inc. IuGW Architecture with RTP Localization
US20230043937A1 (en) * 2020-04-10 2023-02-09 Huawei Technologies Co., Ltd. Random access method and related device
WO2023246431A1 (fr) * 2022-06-22 2023-12-28 华为技术有限公司 Procédé et appareil de communication
WO2024001726A1 (fr) * 2022-06-30 2024-01-04 华为技术有限公司 Procédé et dispositif d'accès de terminal
WO2024159504A1 (fr) * 2023-02-03 2024-08-08 Qualcomm Incorporated Gestion de dispositif de l'internet des objets ambiant dans un réseau de communication mobile

Similar Documents

Publication Publication Date Title
WO2025156694A1 (fr) Messages de radiomessagerie multiples pour dispositif d'idoa
WO2024198635A1 (fr) Attribution de ressources pour système de communication rétrodiffusée
WO2025036090A1 (fr) Dispositifs et procédés de communication
WO2025123718A1 (fr) Accès aléatoire à ido-a
WO2024239726A1 (fr) Accès aléatoire pour dispositifs
WO2025060437A1 (fr) Accès aléatoire pour un dispositif d'ido-a
WO2025035788A1 (fr) Commande pour système d'ido-a
WO2024234740A1 (fr) Transmission de sib1
WO2024239666A1 (fr) Transmission d'ondes porteuses
WO2025167140A1 (fr) Id de strate d'accès de dispositif
WO2025107674A1 (fr) Compte-rendu d'informations sur un dispositif ido-a
WO2025123717A1 (fr) Ré-accès pour un système d'ido-a
WO2026031580A1 (fr) Défaillance de transmission de message
WO2025055356A1 (fr) Accès aléatoire dans un système d'ido-a
WO2025107669A1 (fr) Ressource pour transmission de données associée à une communication par ido ambiant
WO2025189793A1 (fr) Modulation à bande latérale d'un dispositif iot
WO2025107691A1 (fr) Répétitions pour transmission
WO2025208868A1 (fr) Dispositifs et procédés de communication
WO2025055355A1 (fr) Opération associée à un dispositif de l'internet des objets (ido) ambiant
WO2025145568A1 (fr) Détermination de ressources pour une transmission
WO2025236289A1 (fr) Accès aléatoire pour un dispositif a-iot
WO2025066375A1 (fr) Déclenchement de radiomessagerie ou de service de dispositifs aiot
WO2026045260A1 (fr) Attribution d'un id as pour un dispositif a-iot
WO2025060445A1 (fr) Configuration pour réception de radiomessagerie
WO2025097839A1 (fr) Structure de pdu mac dans un système ido-a

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

Country of ref document: EP

Kind code of ref document: A1