Methods and devices for resource allocation in wireless communication systems
By introducing a flexible D2R scheduling mechanism in the communication between the reader and the device, the problem of inflexible resource scheduling in low-power IoT devices is solved, resource allocation efficiency and response speed are improved, and communication reliability is ensured.
Patent Information
- Application Number
- CN202610641876.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-15
- Filing Date
- 2026-05-11
- Publication Date
- 2026-11-17
AI Technical Summary
Existing wireless communication systems suffer from inflexible resource scheduling, response delays, and low efficiency in resource allocation, especially for Internet of Things (IoT) devices in low-power environments. In particular, when devices cannot respond to commands in a timely manner, subsequent transmissions cannot be effectively scheduled.
By introducing a flexible scheduling mechanism of D2R scheduling information into the communication between the reader and the device, including using a second R2D message to reschedule resources when the device cannot respond to commands in a timely manner, and including new scheduling information in the D2R transmission, the effective communication is ensured.
It improves the flexibility and efficiency of resource allocation, reduces response latency, and ensures the communication quality and reliability of low-power IoT devices in complex environments.
Smart Images

Figure CN123124101A_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 806,501, filed May 15, 2025, which is hereby incorporated herein by reference in its entirety. Technical Field
[0003] This disclosure generally relates to wireless communication networks, and more specifically, to a method and apparatus for resource allocation in a wireless communication system. Background Technology
[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This IP data packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.
[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) New Radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate their evolution and completion. Summary of the Invention
[0006] Methods, systems, and devices for determining the number of processes in a wireless communication system are provided. Therefore, if the device has no available data to transmit at the scheduled time, the reader can effectively schedule subsequent transmissions.
[0007] In various embodiments, according to an embodiment of the present invention, a method for an apparatus includes: receiving a first Reader-to-Device (R2D) message from a reader, wherein the first R2D message includes a command and scheduling information for a first D2R resource for a first Device-to-Reader (D2R) transmission; and in response to receiving the first R2D message, performing the first D2R transmission to the reader on the first D2R resource, wherein if a response to the command is not yet available or the response to the command has not yet been obtained, the apparatus sets a first bit in the first D2R transmission to a first value, and if the response to the command is available or the response to the command has been obtained, the apparatus includes the response to the command in the first D2R transmission.
[0008] In various embodiments, according to an embodiment of the present invention, a method of a reader includes: transmitting a first R2D message to a device, wherein the first R2D message includes a command and scheduling information of a first D2R resource for a first D2R transmission; receiving the first D2R transmission from the device on the first D2R resource, wherein the first D2R transmission indicates that a response to the command is not yet available or that the response to the command has not yet been obtained; and in response to receiving the first D2R transmission indicating that a response to the command is not yet available or that the response to the command has not yet been obtained, transmitting a second R2D message to the device, wherein the second R2D message includes scheduling information of a second D2R resource for a second D2R transmission and excludes the command. Attached Figure Description
[0009] Figure 1 The accompanying drawings illustrate a wireless communication system according to an embodiment of the present invention.
[0010] Figure 2 This is a block diagram of a transmitter system (also called an access network) and a receiver system (also called a user equipment or UE) according to an embodiment of the present invention.
[0011] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention.
[0012] Figure 4 This is an embodiment of the present invention. Figure 3 Functional block diagram of the program code.
[0013] Figure 5 It comes from 3GPP TR 38.848 V18.0.0 (2023-09). Figure 4 2.1.1-1: Reproduction of Topology 1.
[0014] Figure 6 It comes from 3GPP TR 38.848 V18.0.0 (2023-09). Figure 4 2.1.2-1: Reproduction of Topology 2.
[0015] Figure 7 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 3.1-1: Reproduction of the overall AS procedure between the A-IoT device and the reader.
[0016] Figure 8 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.2.1-1: Reproduction of the message flow used for A-IoT inventory in Topology 1.
[0017] Figure 9 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.2.2-1: Reproduction of the message flow for A-IoT commands in Topology 1.
[0018] Figure 10 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.3.1.1-1: Message flow for A-IoT inventory in Topology 2 - Reproduction of the RRC-based solution.
[0019] Figure 11 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.3.2-1: Reproduction of the message flow (RRC-based solution) for A-IoT commands in Topology 2.
[0020] Figure 12 It is from R2-2503997 Figure 6 2.2.1-1: Reproduction of the MAC PDU of the random ID message.
[0021] Figure 13A It is from R2-2504398 Figure 16 .x.5.3-1: A-IoT Access Procedure, (a) Reproduction of A-IoT CBRA.
[0022] Figure 13B It is from R2-2504398 Figure 16.x.5.3-1: A-IoT access procedure, (b) reproduction of A-IoT CFA.
[0023] Figure 14A The accompanying drawing is an example of an instance of a first method according to an embodiment of the present invention, wherein one or more R2D messages may include DSI1, DSI2 and DSI3.
[0024] Figure 14B The accompanying drawing is an example of an embodiment of the second method according to an embodiment of the present invention, wherein an R2D message may include DSI1 or DSI2, and DSI may refer to D2R scheduling information included in an R2D message.
[0025] Figure 14C The accompanying drawing is an example of an example of a third method according to an embodiment of the present invention, wherein an R2D message may include DSI1, and DSI may refer to / indicates D2R scheduling information included / contained in an R2D message.
[0026] Figure 15 This is a flowchart of a method of an apparatus in a wireless communication system according to an embodiment of the present invention, the method comprising: receiving a first R2D message from a reader; performing a first operation in response to receiving the first R2D message; determining, based on a resource indication, to perform a first D2R transmission on one or more D2R resources; and performing the first D2R transmission on one or more D2R resources.
[0027] Figure 16 This is a flowchart of a method of an apparatus in a wireless communication system according to an embodiment of the present invention, the method comprising: receiving a first R2D message from a reader; and performing a first D2R transmission to the reader on a first D2R resource in response to receiving the first R2D message.
[0028] Figure 17 This is a flowchart of a method for using a reader in a wireless communication system according to an embodiment of the present invention. The method includes: sending a first R2D message to a device; receiving a first D2R transmission from the device on a first D2R resource; and sending a second R2D message to the device in response to receiving the first D2R transmission. Detailed Implementation
[0029] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is described primarily in the context of the 3GPP architecture reference model. However, it should be understood that, based on the disclosed information, those skilled in the art can readily make adaptations to use and implement aspects of the invention in 3GPP2 network architectures and other network architectures.
[0030] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMAX®, 3GPP New Radio (NR), or some other modulation techniques.
[0031] Specifically, the exemplary wireless communication systems and apparatus described below may be designed to support one or more standards, such as those provided by the alliance known herein as the 3rd Generation Partnership Project (3GPP), which includes: [1] RP-243326, “Solutions for Ambient Internet of Things (IoT) in NR”; [2] 3GPP TR 38.848 V18.0.0 (2023-09) 3GPP; TSG RAN; Study on Ambient Internet of Things (IoT) in RAN (Revision 18); [3] 3GPP TR 38.769 V19.0.0 (2024-12) 3GPP; TSG RAN; Study on Solutions for Ambient Internet of Things (IoT) (Revision 19); [4] R2-2503997, “A-IoT MAC Operation CR”; and [5] R2-2504398, “38.300 Operation CR for Ambient IoT”. The standards and documents listed above are hereby expressly and wholly incorporated herein by reference in their entirety.
[0032] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one group containing antennas 104 and 106, another group containing antennas 108 and 110, and an additional group containing antennas 112 and 114. Figure 1In this diagram, only two antennas are shown in each antenna group; however, each antenna group can utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can communicate using different frequencies. For example, forward link 120 can use a different frequency than the reverse link 118.
[0033] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by access network 100.
[0034] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, an access network that uses beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in adjacent cells.
[0035] An AN can be a fixed station or base station used for communication with a terminal, and can also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or any other term. An AT can also be referred to as User Equipment (UE), wireless communication device, terminal, access terminal, or any other term.
[0036] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for multiple data streams is provided from the data source 212 to the transport (TX) data processor 214.
[0037] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data streams based on a specific decoding scheme selected for each data stream to provide decoded data.
[0038] OFDM technology can be used to multiplex the decoded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for said data streams are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. The data rate, decoding, and modulation for each data stream can be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.
[0039] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to symbols of the data stream and the antennas from which the symbols are transmitted.
[0040] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over a MIMO channel. Then, from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.
[0041] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.
[0042] The RX data processor 260 then uses specific receiver processing technology from N R 254 receivers receive and process N R The received symbol stream provides N TEach detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data used for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.
[0043] Processor 270 periodically determines which pre-decoded matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index portion and the rank portion.
[0044] The reverse link message may include various types of information relating to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from multiple data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.
[0045] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Next, processor 230 determines which pre-decoding matrix to use to determine beamforming weights and then processes the extracted message.
[0046] Memory 232 can be used to temporarily store some buffered / calculated data from processor 240 or 242 via processor 230, some buffered data from processor 212, or some specific program code. Similarly, memory 272 can be used to temporarily store some buffered / calculated data from processor 260 via processor 270, some buffered data from processor 236, or some specific program code.
[0047] Turn Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, this can be achieved using the communication device 300 in a wireless communication system. Figure 1The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.
[0048] Figure 4 This is an embodiment of the present invention. Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.
[0049] For LTE, LTE-A, or NR systems, Layer 2, Part 404 may include the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer. Layer 3, Part 402 may include the Radio Resource Control (RRC) layer.
[0050] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each paragraph or section of the invention may be logically, reasonably and appropriately combined to form a particular method.
[0051] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following invention paragraphs or sections can be implemented independently and separately to form a particular method or apparatus. Dependencies such as "based on," "more specifically," and "example" in the following invention disclosure are merely one possible embodiment and do not limit the specific method or apparatus.
[0052] The work items for the Internet of Things (IoT) in the environment are specified in RP-243326 [1] as follows:
[0053]
[0054] 4. Objectives
[0055] 4.1 Target of SI or core WI or test WI
[0056] The definitions provided in TR 38.848, TR 38.769, and decisions made during Rel-19 SI in RAN WG are incorporated into this WI, and the general scope of exclusivity is as follows:
[0057] A. The overall goal should be to standardize IoT devices in the following environments:
[0058] Device 1: Approximately 1 µW peak power consumption, with energy storage, RF envelope detector receiver, and up to 10 initial sampling frequency offset (SFO). X The device operates at ppm and contains neither R2D nor D2R amplification. The D2R transmission of the device is backscattered on an externally provided carrier.
[0059] B. According to D1T1-B, deployment scenario 1 with topology 1.
[0060] The FR1 licensed spectrum in C.FDD, where R2D is in the DL spectrum and D2R and CW are in the UL spectrum.
[0061] …
[0062] Starting with the decisions already made in TR 38.769, WG made the following improvements to the scope:
[0063] Set the following objectives within a general range:
[0064] • RAN1 range:
[0065] ○ PRDCH and PDRCH are the only physical channels in R2D and D2R, respectively.
[0066] ○ R2D and D2R signals
[0067] ○ In R2D, multiplexing / multiple access is only through TDMA, while in D2R, multiplexing / multiple access is only through TDMA and FDMA.
[0068] …
[0069] • RAN2 range:
[0070] ○ Specify the necessary functions and procedures for the compact protocol stack and lightweight signaling procedures for environmental IoT to enable DO-DTT and DT data transmission:
[0071] ■ A-IoT paging, including subsequent paging for the same service. Options are supported, including an identifier in the paging message and not including an identifier in the paging message. Temporary identifiers are not supported unless required by the SA WG.
[0072] Note: RAN2 is designed to be a paging message format that allows multiple identifiers to be included in a single paging message for forward compatibility purposes.
[0073] ■ A-IoT random access, including re-access for fault handling. Supports both contention-based and contention-free scenarios. For contention-based random access, only Solution 1 (3 steps only) is included (unless RAN2 decides to use Solution 3 (unified solution) before RAN2#129).
[0074] ■ A-IoT data transmission, including data (re)transmission for fault handling. Segmentation is supported at least in D2R.
[0075] ■ Includes only the MAC layer
[0076]
[0077] The description of the environment IoT can be found in TR 38.848 ([2] 3GPP TR 38.848 V18.0.0 (2023-09) 3GPP) and TR 38.769 ([3] 3GPP TR 38.769 V19.0.0 (2024-12) 3GPP), as follows:
[0078]
[0079] 4.2.1 Connection Topology
[0080] 4.2.1.1 Topology 1: BS Environmental IoT devices
[0081] Figure 5 It comes from 3GPP TR 38.848 V18.0.0 (2023-09). Figure 4 2.1.1-1: Reproduction of Topology 1.
[0082] In Topology 1, the environmental IoT device communicates directly and bidirectionally with the base station. Communication between the base station and the environmental IoT device includes environmental IoT data and / or signaling. This topology allows for the possibility that the base station (BS) transmitting to the environmental IoT device may differ from the base station (BS) receiving data from the environmental IoT device.
[0083] 4.2.1.2 Topology 2: BS intermediate nodes Environmental IoT devices
[0084] Figure 6 It comes from 3GPP TR 38.848 V18.0.0 (2023-09). Figure 4 2.1.2-1: Reproduction of Topology 2.
[0085] In Topology 2, the environmental IoT device communicates bidirectionally with intermediate nodes between the device and the base station. In this topology, the intermediate node can be a relay, IAB node, UE, repeater, etc., capable of environmental IoT. The intermediate node transmits environmental IoT data and / or signaling between the BS and the environmental IoT device.
[0086]
[0087]
[0088] 3.1 Terminology
[0089] …
[0090] Device 1: Approximately 1 µW peak power consumption with energy storage, initial sampling frequency offset (SFO) up to 10 X The device operates at ppm and contains neither R2D nor D2R amplification. The D2R transmission of the device is backscattered on an externally provided carrier.
[0091] …
[0092] Inventory: A service provided by the network to discover and obtain identifiers of A-IoT devices.
[0093] Commands: A service provided by the network to send operation instructions (e.g., read, write, etc.) to A-IoT devices.
[0094]
[0095] 6.1 Physical Layer
[0096] 6.1.1 R2D
[0097] 6.1.1.5 PRDCH
[0098] For R2D, the only physical channel is the PRDCH, which carries any higher-level payloads (including system information, if defined) and L1 R2D control information (if defined). The following design options have been investigated for the PRDCH:
[0099] Option 1: If the PRDCH does not carry L1 R2D control information, then consider the transmission of the PRDCH with only R2D data.
[0100] Note: In this option, R2D control information (if any) can be carried by higher-level signaling.
[0101] Option 2: If the PRDCH supports and carries any L1 R2D control information, then for CRC appending (append if a non-zero length CRC exists), the following two options have been investigated.
[0102] Option 2-1: Attach the combined CRC to the L1 R2D control information and R2D data.
[0103] Option 2-2: Append separate CRCs to the L1 R2D control information and R2D data respectively.
[0104] …
[0105] 6.1.1.9 R2D Scheduling
[0106] For R2D reception, the following information can potentially be explicitly / implicitly indicated to the device via the corresponding PRDCH:
[0107] - An ID associated with the device intended to receive R2D, which may include all devices (if supported).
[0108] For each piece of information, further investigation is needed into whether to use higher-level signaling and / or L1 R2D control signaling – see Clause 6.1.1.10.
[0109] 6.1.1.10 R2D Control Information
[0110] For the transmission of R2D control information used for R2D reception and D2R scheduling, the following two options are studied and documented in TR 38.769:
[0111] - Option 1: L1-Control Signaling
[0112] Option 2: Higher-level signaling
[0113]
[0114] 6.1.2 D2R
[0115] 6.1.2.4 D2R Bandwidth
[0116] For research purposes, the following bandwidth is defined for D2R:
[0117] - Transmission bandwidth B tx,D2R The reader transmits frequency resources scheduled from a device via D2R.
[0118] - Bandwidth usage B occ,D2RThe total transmission bandwidth, plus the potentially associated A-IoT internal guard band, is B. guard,D2R Note: This protection band does not coexist with NR / LTE.
[0119] - B occ,D2R ≥ B tx,D2R .
[0120] …
[0121] 6.1.2.5 PDRCH
[0122] For D2R, the physical channel PDRCH carries any higher-layer payload, the response transmitted from the device to the reader during a contention-based access procedure, and L1 D2R control information (if defined).
[0123] …
[0124] The scheduling information transmitted by the PDRCH is provided by the corresponding PDRCH.
[0125] …
[0126] 6.1.2.8 D2R Scheduling
[0127] For D2R scheduling, the following information can potentially be explicitly / implicitly indicated to the device via the corresponding PRDCH:
[0128] - Time Domain Resources
[0129] - Frequency domain resources
[0130] - Information similar to MCS
[0131] - Chip duration
[0132] - ID associated with the device
[0133] - repeat
[0134] - Intermediate code (if supported) related information
[0135] For each piece of information, further investigation is needed into whether to use higher-level signaling and / or L1 R2D control signaling – see Clause 6.1.1.10.
[0136]
[0137] 6.1.4 Random Access
[0138] From a physical layer perspective, at least when responses from multiple devices intended to be identified are expected, an A-IoT contention-based access procedure initiated by the reader is used. For this procedure, at least slotted ALOHA-based access and FDMA have been studied. The FDMA study includes how to allocate frequency domain resources for Msg1 and how devices determine the allocation of these frequency domain resources.
[0139] During this procedure, the response from the device to the reader is transmitted on the PDRCH.
[0140] The R2D transmission that triggers random access determines X time-domain resources for the D2R transmission for Msg1, wherein each D2R transmission for Msg1 occurs in one of the X time-domain resources.
[0141]
[0142] 6.3 Protocol Stack and Signaling Programs
[0143] 6.3.1 General Aspects and Overall Procedures
[0144] …
[0145] Figure 7 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 3.1-1: Reproduction of the overall AS procedure between the A-IoT device and the reader.
[0146] The overall AS procedure can be defined as follows:
[0147] - Step A: A-IoT Paging. Based on the service request, the reader sends an A-IoT paging message indicating which device needs to respond. See Clause 6.3.3.
[0148] - Step B: D2R Data (Device ID) Transmission. The triggered A-IoT device performs device ID transmission via the A-IoT random access procedure or without using the A-IoT random access procedure. See Clauses 6.3.4 (and 6.3.5).
[0149] - Step C1: Possible R2D data transfer (e.g., for sending commands). See Clause 6.3.5.
[0150] - Step C2: Possible D2R data transfer (e.g., response to a corresponding command). See Clause 6.3.5.
[0151] Then, the above AS program can support indoor inventory and indoor command use cases in the following ways:
[0152] - For the detailed use case of "counting only", it is supported by a procedure based on steps A and B.
[0153] - For the detailed use case of "counting and commanding", it is supported by a procedure based on steps A, B, C1 and C2.
[0154] Note 1: The use case of “inventory and command” does not imply that the IoT paging message contains both inventory and command, nor does it imply that inventory and command are received simultaneously from the upper layer by the reader.
[0155] …
[0156] The following information from CN is considered useful for readers:
[0157] Note 2: Further discussion is needed regarding whether the following information is required or optional.
[0158] - A-IoT service types (e.g., inventory, commands)
[0159] Note 3: Further discussion is needed regarding the usefulness of more information about command types (e.g., read / write / deactivate). The reader needs to know whether a D2R response is expected in the D2R direction, and if so, the expected D2R message size. Further discussion is needed regarding the details of how the reader obtains this information (related to the discussion of "expected D2R message size" in Clause 6.3.5). Further discussion is needed regarding whether the command type (if needed) is explicit or (where available) inferred from the "expected D2R message size."
[0160] - Is the service for one A-IoT device or for more than one A-IoT device?
[0161] - Approximate number of A-IoT devices targeted by this service
[0162]
[0163] 6.3.4 A-IoT Random Access Procedure
[0164] …
[0165] Access timing: The opportunity for an A-IoT device to perform access (e.g., by transmitting A-IoT Msg1 by the device). A set of access timings for different A-IoT devices is scheduled by the reader via R2D messages (see “R2D Transmission Triggers Random Access” in Clause 6.1.4).
[0166] When an A-IoT device is selected to respond pursuant to Clause 6.3.3, the A-IoT device performs the following procedure:
[0167] - Step 1: Determine the random access type (i.e., contention-free or contention-based) and access timing / resources:
[0168] - According to Clause 6.3.3, the A-IoT device determines the random access type from the A-IoT paging message. The reader can be configured for contention-free access or contention-based random access (and the corresponding configuration). Whether this is explicit or implicit needs further discussion.
[0169] - If random access is contention-free access:
[0170] - Select the indicated D2R timing / resource;
[0171] - Skip the race resolution in step 2 and perform data transfer in accordance with clause 6.3.5.
[0172] - If random access is based on contention-based random access:
[0173] - Access Timing / Resource Selection: As a baseline for CBRA, at least for TDMA, the device can randomly select an access timing for A-IoT Msg1 within the access timing provided / assigned by the reader. Further discussion is needed regarding whether this applies to FDMA. Further enhancement options can be considered after more detailed physical layer design on TDMA and FDMA.
[0174] - Perform step 2 for race resolution.
[0175] - Step 2: Contention resolution for contention-based random access:
[0176] - There are three candidate solutions for the competing solution, as described below (further discussion is needed regarding downward selection and / or unified design):
[0177] Solution 1: A-IoT without data Msg1
[0178] - A-IoT Msg1: When an A-IoT device identifies the start of its own access time, it sends a 16-bit random ID generated by the A-IoT device to the reader.
[0179] - A-IoT Msg2: The reader responds with a random ID that was successfully received.
[0180] If an A-IoT device receives an A-IoT Msg2 containing the same random ID as the one previously transmitted in A-IoT Msg1, it considers the race to be resolved successfully.
[0181] …
[0182] After the A-IoT device considers the contention to be resolved successfully, it may perform upper-layer data transmission with the reader in accordance with Clause 6.3.5, whether using contention-based random access or contention-free access, and the upper-layer data transmission may be the device ID and / or any other upper-layer data (if present).
[0183] …
[0184] 6.3.5 A-IoT Data Transmission
[0185] Based on the protocol stack and functions in Clause 6.3.2, this clause examines the data transmission functions in more detail.
[0186] The handling of data transmission failures was investigated. It should be understood that subsequent R2D data transmissions are not always necessary after a D2R data transmission. In the event of a D2R data transmission failure, the A-IoT device follows the reader's subsequent R2D instructions (if any).
[0187] - For example, the reader can repeat the R2D upper-layer "command" to trigger the A-IoT device to resend the same D2R upper-layer "response" (i.e., the A-IoT device only follows the received R2D to transmit subsequent D2Rs).
[0188] For example, if the reader fails to receive the corresponding D2R data transmission (i.e., "Msg3") after the initial A-IoT Msg2, it can resend the A-IoT Msg2 to the specific device to echo the random ID and perform the corresponding D2R resource scheduling. This can trigger the A-IoT device to resend the same D2R data transmission (i.e., "Msg3"). If it supports including echoed random IDs for multiple devices, the resent A-IoT Msg2 will only contain the device's random ID, and its "Msg3" will not be successfully received.
[0189] The functionality of segmentation was investigated. It should be understood that segmentation and reassembly increase complexity. Therefore, considering the following research in the physical layer, simplified segmentation in the A-IoT MAC layer was investigated:
[0190] - In both R2D and D2R directions, there is no lower limit to the minimum TB size, and a maximum TB size of approximately 1000 bits can be supported.
[0191] How many TB can be transmitted in a given time depends on the target coverage / data rate, energy consumption / device availability, etc.
[0192] The segmentation research focuses on the D2R direction (further consideration can be given to the R2D direction). For candidate solutions for segmentation:
[0193] - Serial number, segment number and segment number are not supported;
[0194] - This indicator tells the reader whether the data has been segmented and whether the MAC PDU is the last segment. Further discussion is needed regarding the size of this indicator (one or two bits) and the corresponding details.
[0195] - It is beneficial for the reader to be able to trigger the retransmission of segments;
[0196] - Assume that A-IoT devices will not support AS layer buffering for A-IoT segmentation functionality, i.e., all segments are stored in the upper layer.
[0197] …
[0198] From a higher-level perspective, it is assumed that the "AS ID" is used at least for D2R scheduling and R2D reception purposes (if defined according to the design in Clause 6.1). From a higher-level perspective, it is assumed that this "AS ID" should be a short AS layer ID, not a complete upper-layer device ID. If this "AS ID" can be based on a partial upper-layer device ID, further discussion is required. The length of this "AS ID" needs further discussion. From a higher-level perspective, the following options are possible for this "AS ID" (which aim to define a common design for all access procedures in Clause 6.3.4, if technically possible):
[0199] - Option 1: The random ID (if used in the first D2R message) can be reused;
[0200] Option 2: The reader assigns this "AS ID" to the device. Further discussion is needed regarding which R2D message is used.
[0201] Option 3: Whether to reuse the random ID (if used in the first D2R message) as the "AS ID" or assign a new "AS ID" depends on the reader. Further discussion is needed regarding which R2D message is used.
[0202] Note 1: Further selection of "AS ID" needs to take into account the messages involved and whether the reader needs to handle conflicts.
[0203]
[0204] 6.5 Impact on CN-RAN Interface
[0205] 6.5.1 Information exchanged between A-IoT CN and A-IoT RAN
[0206] 6.5.1.1 Inventory
[0207] A-IoT CN can send an inventory for a single device, a group of devices, or all devices.
[0208] An inventory request from A-IoT CN to A-IoT RAN can include the following:
[0209] (1) A-IoT device identifier (to discover a single device, a group of devices, or all devices)
[0210] Note 1: This identifier is defined outside the RAN3 range.
[0211] For Topology 1, the A-IoT RAN needs to store the A-IoT device identifiers received from the inventory request.
[0212] Note 2: Whether to interpret and process AIoT device identifiers received from inventory requests requires further discussion.
[0213] (2) Scope of the inventory request (e.g., the specific area that will trigger the inventory)
[0214] Multiple individual A-IoT device IDs (one ID per device) can be provided to A-IoT CN via a single inventory report.
[0215] Note 3: For topology 1, whether the device ID received from the device is transparently sent to the A-IoTCN via the A-IoT RAN depends on RAN2 and SA2.
[0216] Note 4: Whether the description in this clause applies to gNBs that support A-IoT in Topology 2 needs further discussion and depends on SA2 and RAN2.
[0217] 6.5.1.2 Commands
[0218] Commands can be sent to a single device by the A-IoT CN.
[0219] For topology 1, A-IoT RAN nodes should be able to distinguish between commands and inventory.
[0220] Note 1: Whether commands can be executed for a set of devices depends on RAN2, SA2, and SA3.
[0221] Note 2: Whether gNBs with A-IoT enabled should be able to distinguish between commands and inventory needs further discussion, depending on SA2 and RAN2.
[0222] Note 3: Whether the description in this clause applies to gNBs that support A-IoT in Topology 2 needs further discussion and depends on SA2 and RAN2.
[0223]
[0224] 6.5.2 Signaling and Procedures for Topology 1
[0225] Note: The XX communications described in the following terms use the protocol elements (message and information elements) detailed in Terms 6.5.1, and will not be repeated unless further description is required.
[0226] 6.5.2.1 Candidate Programs for A-IoT Inventory in Topology 1
[0227] Figure 8 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.2.1-1: Reproduction of the message flow used for A-IoT inventory in Topology 1.
[0228] 1a. The A-IoT CN sends a count request message to the A-IoT RAN node, taking into account the scope of A-IoT transactions.
[0229] 1b. A-IoT RAN node allocation and coordination of the use of A-IoT radio resources.
[0230] 2. The A-IoT RAN node sends an inventory response message to the A-IoT CN.
[0231] Note 1: In step 2, the A-IoT RAN node may alternatively send an inventory failure message to the A-IoT CN, indicating that the inventory procedure cannot be initiated toward the A-IoT device.
[0232] 3. The A-IoT RAN node performs an inventory procedure toward the A-IoT devices via the A-IoT radio interface.
[0233] 4a / 4b. After receiving the inventory results from the A-IoT device, the A-IoT RAN node may send one or more inventory reports containing the received inventory results to the A-IoT CN.
[0234] Note 2: For different A-IoT devices, steps 4a / 4b can occur in parallel with step 3.
[0235] 6.5.2.2 Candidate programs for A-IoT commands in Topology 1
[0236] Figure 9It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.2.2-1: Reproduction of the message flow for A-IoT commands in Topology 1.
[0237] 1. The inventory procedure is executed in step 1, which is related to... Figure 6 The same applies to steps 1-4 in .5.2.1-1.
[0238] Note 1: Step 1 is performed for the “A-IoT Inventory and Command” scenario. Whether Step 1 can be skipped in the “Command Only” scenario, under what conditions Step 1 can be skipped, and what impact this will have on the overall message flow, depends on the discussion led by SA2, SA3, and RAN2.
[0239] Note 2: Whether and in what way steps 2a and 2b can be part of step 1 depends on the discussion led by SA2, SA3 and RAN2.
[0240] 2a. The A-IoT CN node sends a command request message to the A-IoT RAN.
[0241] 2b. The A-IoT RAN node coordinates the use of A-IoT radio resources and allocates A-IoT radio resources during A-IoT commands.
[0242] 3. The A-IoT RAN node executes A-IoT commands to the A-IoT device via the A-IoT radio interface.
[0243] 4. The A-IoT RAN node sends a command response message to the A-IoT CN. If any command result is received from the A-IoT device, the A-IoT RAN node can include the command result in the command response message.
[0244] Note 3: In step 4, the A-IoT RAN node may alternatively send a command failure message to the A-IoT CN, indicating that the command procedure has failed.
[0245] 6.5.3 Signaling and Procedures for Topology 2
[0246] 6.5.3.1 Candidate Programs for A-IoT Inventory in Topology 2
[0247] 6.5.3.1.1 RRC-based solution
[0248] Figure 10 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 65.3.1.1-1: Message flow for A-IoT inventory in Topology 2 - Reproduction of the RRC-based solution.
[0249] 1a. The A-IoT CN sends an inventory request message to the gNB that supports A-IoT.
[0250] 1b. Support gNB allocation and coordination of A-IoT radio resource usage for A-IoT.
[0251] 1c / 2a Occurs RRC communication with A-IoT-enabled UEs.
[0252] Note 1: RRC-based communication is depicted only schematically; details are subject to RAN2.
[0253] 2. The gNB that supports A-IoT sends an inventory response message to the A-IoT CN.
[0254] Note 2: In step 2, the gNB that supports A-IoT can alternatively send an inventory failure message to the A-IoT CN, indicating that an inventory procedure cannot be initiated toward the A-IoT device.
[0255] 3. The gNB that supports A-IoT requests the UE that supports A-IoT to trigger the inventory procedure toward the A-IoT device.
[0256] 4a / 4b. After receiving the inventory results reported from an A-IoT-enabled UE, the A-IoT-enabled gNB may send one or more inventory reports containing the received inventory results to the A-IoT CN.
[0257] Note 3: For different A-IoT devices, steps 4a / 4b can occur in parallel with step 3.
[0258] Note 4: Steps 4a / 4b between an A-IoT-enabled UE and an A-IoT-enabled gNB are subject to RAN2.
[0259] …
[0260] 6.5.3.2 Candidate Programs for A-IoT Commands for Topology 2
[0261] 6.5.3.2.1 RRC-based solution
[0262] Figure 11 It comes from 3GPP TR 38.769 V19.0.0 (2024-12). Figure 6 5.3.2-1: Reproduction of the message flow (RRC-based solution) for A-IoT commands in Topology 2.
[0263] 1. The inventory procedure is executed in step 1, which is related to... Figure 6 The same as steps 1-4 in .5.3.1.1-1.
[0264] Note 1: Step 1 is performed for the “A-IoT Inventory and Command” scenario. Whether Step 1 can be skipped in the “Command Only” scenario, under what conditions Step 1 can be skipped, and what impact this will have on the overall message flow, depends on the discussion led by SA2, SA3, and RAN2.
[0265] Note 2: Whether and in what way steps 2a, 2b and 2c can be part of step 1 depends on the discussion led by SA2, SA3 and RAN2.
[0266] 2a. The A-IoT CN sends a command request message to the gNB that supports A-IoT.
[0267] 2b. The gNB that supports A-IoT coordinates A-IoT radio resources and allocates A-IoT radio resources accordingly to the UE that supports A-IoT.
[0268] 2c. The gNB that supports A-IoT sends an RRC command request message to the UE that supports A-IoT.
[0269] Note 3: The RRC-based communication, i.e., the execution of A-IoT command procedures and the allocation of A-IoT radio resources, is only schematically depicted. Its details are subject to RAN2.
[0270] 3. The UE that supports A-IoT executes A-IoT command programs towards the A-IoT device through the A-IoT radio interface.
[0271] 4a. The UE supporting A-IoT sends a command response message to the gNB supporting A-IoT. If a command result is received from the A-IoT device, the UE supporting A-IoT may include the command result in the command response message.
[0272] 4b. A-IoT-enabled gNBs send command response messages to the A-IoT CN, which may include the command result in the command response message (if available).
[0273] Note 4: In step 4b, the A-IoT-enabled gNB may instead send a command failure message to the A-IoT CN, indicating that the command procedure toward the A-IoT device has failed.
[0274]
[0275] The current Layer 2 procedures and message formats for environmental IoT are described in the running CR of TS 38.391 ([4]R2-2503997) as follows:
[0276]
[0277] 3.1 Definition
[0278] For the purposes of this document, the terms and definitions given in TR 21.905 and below shall apply. Terms defined in this document take precedence over, if any, the definitions of the same term in TR 21.905.
[0279] …
[0280] Access timing: The time-frequency resources used by the device to transmit Msg1 (i.e., random ID message) during the CBRA procedure.
[0281] AS ID: An AS layer identifier used to address a specific device for R2D reception and D2R scheduling.
[0282]
[0283] 5A-IoT MAC Program
[0284] 5.2 A-IoT Paging
[0285] The purpose of this program is to send A-IoT paging messages to one or more devices. The reader may include a paging ID field to select a specific device or a group of devices, or it may not include a paging ID field to select all devices.
[0286] The device listens for A-IoT paging messages and determines whether the device has been selected and initiates a random access procedure.
[0287] Upon receiving an A-IoT paging message, the A-IoT MAC entity should:
[0288] 1> If the transaction ID field included in the A-IoT paging message is the same as the value stored by the device (if it exists):
[0289] 2> If the previous procedure associated with the received value indicated in the Transaction ID field is determined to have failed, as specified in Clause 5.5:
[0290] 3> Consider the device being selected by this A-IoT paging message;
[0291] 1> Otherwise:
[0292] 2> Store the received value in the transaction ID field, or replace the previously stored transaction ID with the currently received value;
[0293] …
[0294] 2> If the A-IoT paging message does not contain a paging ID field:
[0295] 3> Consider the device being selected by this A-IoT paging message and the instruction being sent to the upper layer;
[0296] 2> Otherwise:
[0297] 3> Forward the value of the paging ID field to the upper layer;
[0298] 3> If the upper layer indicates that the paging ID matches:
[0299] 4> Consider the device being selected by this A-IoT paging message;
[0300] 1> If the device is selected by this A-IoT paging message;
[0301] 2> Release the stored AS ID (if it exists);
[0302] 2> If the RA type field in the A-IoT paging message indicates CBRA:
[0303] 3> Process the D2R scheduling information field received in the A-IoT paging message as specified in Clause 5.3.1.1;
[0304] 3> Perform the contention-based random access procedure as specified in Clause 5.3.1;
[0305] 2> Otherwise (the RA type field in the A-IoT paging message indicates CFRA):
[0306] 3> Apply the D2R scheduling information field received in the A-IoT paging message and indicate it to the physical layer;
[0307] 3> Perform the contention-based random access procedure as specified in Clause 5.3.2;
[0308] …
[0309] 5.3 A-IoT Random Access Procedure
[0310] 5.3.1 Contention-based random access procedure
[0311] 5.3.1.1 Selection of Access Timing for D2R Transmission of Random ID Messages
[0312] If a contention-based random access procedure is initiated pursuant to Clause 5.2, the A-IoT MAC entity shall:
[0313] 1> Randomly select the access timing for transmitting the random ID message from the access timing configured in the A-IoT paging message;
[0314] 1> The D2R scheduling information received from the A-IoT paging message will be applied to the selected access timing;
[0315] 1> Initiate the transmission of a random ID message, as specified in Clause 5.3.1.2.
[0316] …
[0317] 5.3.1.2 Transmission of Random ID Messages
[0318] A-IoT MAC entities should:
[0319] 1> Generate a 16-bit random number 'j' within the following range: 0 ≤ j < 2 16 ;
[0320] 1> Set the random ID field to 'j' in the random ID message;
[0321] 1> Instructs the physical layer to use the selected access timing to transmit random ID messages.
[0322] 5.3.1.3 Receiving Random ID Response Messages
[0323] Once the random ID message is transmitted, and if a random ID response message is received, the A-IoT MAC entity should:
[0324] 1> If the value indicated by the echoed random ID field in the random ID response message is the same as the value of the random ID field in the transmitted random ID message:
[0325] 2> This random access procedure is considered to have completed successfully;
[0326] 2> If it contains an assigned AS ID field corresponding to the echoed random ID field:
[0327] 3> Set the AS ID to the value indicated in the assigned AS ID field and store the AS ID;
[0328] 2> Otherwise:
[0329] 3> Set the AS ID to the value of the random ID field in the transmitted random ID message and store the AS ID;
[0330] 2> Apply the D2R scheduling information field received in the random ID response message and indicate it to the physical layer;
[0331] 2> Initiate D2R message transmission as specified in Clause 5.4.1.
[0332] 5.3.2 Contention-free random access procedure
[0333] If a contention-free random access procedure is initiated pursuant to Clause 5.2, the A-IoT MAC entity shall:
[0334] 1> Initiate D2R message transmission as specified in Clause 5.4.1
[0335] 5.4 A-IoT Upper Layer Data Transmission
[0336] 5.4.1 D2R Message Transmission
[0337] Once the A-IoT MAC entity receives D2R scheduling information for D2R upper-layer data transmission in an A-IoT paging message, random ID response message, or R2D upper-layer data transmission message, it should:
[0338] 1> If upper-layer data is available for transmission:
[0339] 2> If the size of the resulting MAC PDU containing the total UL data is less than or equal to the resource size given by the D2R scheduling information:
[0340] 3> Generate D2R upper-layer data transfer messages, including:
[0341] 4> Includes the SDU data field;
[0342] 4> Set the More Data Indicator field to a value of 0;
[0343] 4> If the size of the resulting MAC PDU containing the total UL data is less than the resource size given by the D2R scheduling information:
[0344] 5> Includes a MAC address padding field;
[0345] 3> Instruct the physical layer to transmit the generated D2R upper-layer data transfer message;
[0346] 2> Otherwise (the size of the resulting MAC PDU containing total UL data is greater than the resource size given by the D2R scheduling information):
[0347] 3> The upper-layer data SDU will be segmented according to clause 5.4.3;
[0348] Editor's Note: Whether the write command type might result in a situation where 'no upper-layer data is available for D2R scheduling' due to long write times requires further investigation.
[0349] Note: Avoiding segmentation of D2R upper-layer data transmission messages used for device ID reporting depends on the reader's implementation scheme.
[0350] 5.4.2 R2D Message Reception
[0351] Upon receiving the R2D message, the A-IoT MAC entity should:
[0352] 1> If the device has already stored the AS ID and the R2D message is addressed to the stored AS ID:
[0353] 2> Forward the upper-layer data SDU to the upper layer;
[0354] 2> Apply the D2R scheduling information field and indicate it to the physical layer for subsequent D2R message transmission, as specified in 5.4.1;
[0355] 1> Otherwise:
[0356] 2> If the device does not have a stored AS ID; and
[0357] 2> If the R2D message is a data transfer message from the R2D upper layer; and
[0358] 2> If the CFRA program has already been executed in the current program:
[0359] 3> Set the AS ID to the value indicated in the AS ID field and store the AS ID;
[0360] 3> Forward the upper-layer data SDU to the upper layer;
[0361] 3> Apply the D2R scheduling information field and indicate it to the physical layer for subsequent D2R message transmission, as specified in 5.4.1.
[0362] Editor's Note: Whether the reader always contains commands for retransmitted segments requires further investigation.
[0363] 5.4.3 Segmentation
[0364] When the upper-layer data SDU is to be segmented according to the D2R upper-layer data transmission procedure in Clause 5.4.1, the A-IoTMAC entity performs this segmentation procedure on the original upper-layer data SDU.
[0365] A-IoT MAC entities should:
[0366] 1> If D2R scheduling information is received in the R2D upper-layer data transmission message:
[0367] 2> The following D2R upper-layer data transmission message is generated for this segment based on the D2R scheduling information:
[0368] 3> Based on the segment indicated by the received data size field (i.e., x bytes), set the data SDU field to contain the (x+1)th byte starting from the original upper-layer data SDU;
[0369] Editor's Note: Whether retransmission of first-segment / unsegmented D2R messages always includes offset zero requires further investigation.
[0370] 3> If the segment is the last segment of the original upper-layer data SDU:
[0371] 4> Set the More Data Indicator field to a value of 0;
[0372] 4> If the expected size of the resulting MAC PDU containing the segment is less than the resource size given by the D2R scheduling information:
[0373] 5> Includes a MAC address padding field;
[0374] 3> Otherwise:
[0375] 4> Set the More Data Indicator field to the value 1;
[0376] 2> Instruct the physical layer to transmit D2R upper layer data transfer messages.
[0377] …
[0378] 6. Protocol Data Units, Formats, and Parameters
[0379] 6.1 Protocol Data Unit
[0380] 6.1.1 Overview
[0381] An A-IoT MAC Protocol Data Unit (PDU) is a data unit format encapsulated within an A-IoT MAC message for transmission over the lower layers of the A-IoT protocol stack. An A-IoT MAC PDU is a bit string. The content of each A-IoT MAC message is specified using fields in the table specified in Clause 6.2. In the table, the most significant bit is the leftmost bit of the first row, the least significant bit is the rightmost bit of the last row, and more generally, the bit string is read from left to right, then in the order of row reading. The bit order of each parameter field within the MAC PDU is indicated by the first and most significant bits in the leftmost position and the last and least significant bits in the rightmost position.
[0382] A-IoT MAC SDU is a bit string that is byte-aligned in length (i.e., a multiple of 8 bits). The MAC SDU can be included in the MAC PDU starting from the first bit.
[0383] The R2D message type represents the set of A-IoT MAC messages sent from the reader to the device on the PRDCH. The values for the R2D message type are specified in Table 6.1-1.
[0384] Table 6.1-1: R2D Message Types
[0385]
[0386] D2R message type is a collection of A-IoT MAC messages sent from the device to the reader on the PDRCH. The values for D2R message type are specified in Table 6.1-2.
[0387] Table 6.1-2: D2R Message Types
[0388]
[0389] …
[0390] 6.2 A-IoT MAC Messages
[0391] 6.2.1 R2D Messages
[0392] 6.2.1.1 A-IoT Paging Messages
[0393] The fields defined in this message are as follows:
[0394] - R2D Message Type: This field indicates the message type. See Table 6.1-1.
[0395] - RA Type: This field indicates CBRA or CFRA.
[0396] - Indication of Paging ID Existence: This field indicates whether the Paging ID and its length exist (when set to 1) or not (when set to 0).
[0397] - Paging ID length: When a Paging ID field exists, this field indicates the length of the Paging ID.
[0398] - Paging ID: xxx
[0399] Transaction ID: xxx
[0400] - Number of access opportunities: This field indicates the number of access opportunities.
[0401] - D2R scheduling information: This field indicates the physical layer parameters used for D2R scheduling.
[0402] …
[0403] 6.2.1.2 Access Timing Trigger Message
[0404] Figure 6 .2.1.2-1 shows the format of the access timing trigger message.
[0405] The fields defined in this message are as follows:
[0406] - R2D Message Type: This field indicates the message type. See Table 6.1-1.
[0407] 6.2.1.3 Random ID Response Message (Msg2 in CBRA)
[0408] Figure 6 .2.1.3-1 shows the format of the random ID response message.
[0409] The fields defined in this message are as follows:
[0410] - R2D Message Type: This field indicates the message type. See Table 6.1-1.
[0411] - Random ID displayed: 16 digits
[0412] - Assigned AS ID: This field provides a 16-bit AS ID value.
[0413] - D2R scheduling information: This field indicates the physical layer parameters used for D2R scheduling.
[0414] …
[0415] 6.2.1.4 R2D Upper Layer Data Transmission Messages
[0416] Figure 6 2.1.4-1 shows the format of the upper layer data transmission message in R2D.
[0417] The fields defined in this message are as follows:
[0418] - R2D Message Type: This field indicates the message type. See Table 6.1-1.
[0419] - AS ID: This field provides / indicates the value of the AS ID.
[0420] - Length: xxx
[0421] - Data SDU: xxx
[0422] - Received data size: This field indicates the number of bytes successfully received by the reader.
[0423] - D2R scheduling information: This field indicates the physical layer parameters used for D2R scheduling.
[0424] Editor's Note: Whether offset zero is always included requires further investigation. Whether the reader always includes commands for retransmitted segments requires further investigation.
[0425] 6.2.2 D2R Messages
[0426] 6.2.2.1 Random ID Message (Msg1 in CBRA)
[0427] Figure 6 .2.2.1-1 shows the format of the random ID message.
[0428] The fields defined in this message are as follows:
[0429] - Random ID: 16-digit random number
[0430] Figure 12 It is from R2-2503997 Figure 6 2.2.1-1 Reproduction of the MAC PDU of the random ID message.
[0431] 6.2.2.2 D2R Upper Layer Data Transmission Messages
[0432] Figure 6 .2.2.2-1 shows the format of the upper layer data transmission message in D2R.
[0433] The fields defined in this message are as follows:
[0434] Editor's Note: Whether we need a message type field for D2R requires further investigation.
[0435] - More data indications:
[0436] - Length: xxx
[0437] Editor's Note: How this is provided (i.e., as an SDU length field or a padding length field) requires further investigation. The size of the length field requires further investigation.
[0438] - Data SDU: xxx
[0439] - MAC padding: This field contains padding bits.
[0440]
[0441] The following is a general overview of IoT for the environment described in the operating CR of TS 38.300 ([5]R2-2504398):
[0442]
[0443] 16.x Support for IoT in the Environment
[0444] 16.x.5 A-IoT MAC Layer Functionality
[0445] 16.x.5.1 Services and Features
[0446] The main services and functions of the A-IoT MAC layer include (see TS 38.391[xx]):
[0447] - Construct the MAC PDU to be mapped onto the D2R transport block and delivered to the physical layer;
[0448] - Process MAC PDUs from R2D transport blocks delivered from the physical layer;
[0449] - Paging;
[0450] - Access;
[0451] - Transfer of data from higher layers;
[0452] - D2R segmentation;
[0453] - Fault detection.
[0454] 16.x.5.2 A-IoT Paging
[0455] A-IoT paging allows an A-IoT reader to trigger one or more A-IoT devices to perform an A-IoT CBRA or A-IoT CFA. An A-IoT paging message is sent on the PRDCH. An A-IoT paging message may or may not contain a paging identifier. If a paging identifier is included, the A-IoT paging message can be addressed to a single A-IoT device or a group of A-IoT devices. If no paging identifier is included, the A-IoT paging message is addressed to all A-IoT devices. The A-IoT paging message can also provide configuration for the A-IoT access procedure.
[0456] 16.x.5.3 A-IoT Access Procedure
[0457] For A-IoT access, both the A-IoT CBRA and A-IoT CFA procedures are supported. The A-IoT device initiates either A-IoT CBRA or A-IoT CFA based on the indication in the A-IoT paging message. For CBRA, the A-IoT device randomly selects an A-IoT MSG1 resource from the A-IoT MSG1 resources provided in the A-IoT paging message, listens for R2D trigger messages to determine the start of the selected MSG1 resource, and transmits the A-IoT MSG1 on this resource, as described in TS 38.391. After the A-IoT MSG1 is transmitted, the device listens for A-IoT MSG2 from the A-IoT reader for contention resolution. Upon successfully receiving an A-IoT MSG2 containing the same random ID as the random ID transmitted in the A-IoT MSG1, the A-IoT device considers the contention resolution successful, as... Figure 16 As shown in .x.5.3-1(a). Otherwise, the A-IoT device considers contention resolution to have failed. If contention resolution is successful, the A-IoT device should report the inventory response in the next D2R message. If the A-IoT device considers contention resolution to have failed, the A-IoT device continues to listen for A-IoT MSG2, which can be retransmitted by the A-IoT reader according to the implementation scheme, as well as subsequent A-IoT paging messages. For CFA, the A-IoT device should use the dedicated resources provided in the A-IoT paging message to send the first D2R message, such as... Figure 16 As shown in .x.5.3-1(b).
[0458] Figure 13A It is from R2-2504398 Figure 16 .x.5.3-1: A-IoT Access Procedure, (a) Reproduction of A-IoT CBRA.
[0459] Figure 13B It is from R2-2504398 Figure 16 .x.5.3-1: A-IoT access procedure, (b) reproduction of A-IoT CFA.
[0460] 16.x.5.4 A-IoT Upper Layer Data Transmission
[0461] 16.x.5.4.1 R2D and D2R Data Transfer
[0462] The A-IoT MAC sublayer supports R2D reception and D2R transmission of upper-layer data, including inventory responses, upper-layer commands, and command responses. D2R A-IoT MAC PDUs can include padding bits. If the scheduled TB size of the D2R message exceeds the size of the A-IoT MAC PDU, the A-IoT device adds padding bits to the D2R message.
[0463] 16.x.5.4.2 Segmentation
[0464] When the size of the A-IoT MAC PDU exceeds the scheduling TB size, the D2R upper-layer data SDU, except for the inventory response, can be segmented in the A-IoT MAC layer.
[0465] Segmentation of R2D upper-layer data SDU in the A-IoT MAC layer is not supported.
[0466] 16.x.5.5 AS ID
[0467] To support command procedures in 16.x.7, A-IoT devices are assigned an AS ID, or instructed to reuse a random ID transmitted in A-IoT MSG1 as their AS ID. This AS ID addresses a specific A-IoT device for R2D reception and scheduling resources for D2R transmission. An A-IoT device maintains at most one AS ID at a time. During the A-IoT CBRA procedure, an AS ID can be assigned to the A-IoT device by A-IoT MSG2, or the reuse of a random ID transmitted in A-IoT MSG1 can be instructed. After the A-IoT CFA procedure, an AS ID can be assigned to the A-IoT device along with an R2D command message.
[0468]
[0469] Ambient Internet-of-Thing (A-IoT) devices will feature ultra-low complexity, extremely small device size, and long lifespan. A-IoT devices will have several orders of magnitude lower complexity and power consumption than existing 3GPP Low Power Wide Area (LPWA) technologies (e.g., Narrowband (NB)-IoT, enhanced Machine-Type Communication (eMTC)). A-IoT devices may or may not have energy storage. Energy for A-IoT devices can be provided by harvesting carrier waves, radio waves, light, motion, heat, or any other suitable power source. Energy and / or power can be provided one-off (e.g., unintended or non-periodic), periodically, or continuously. In one embodiment, the power / energy of the A-IoT device can be provided from a carrier wave from the network and / or intermediate nodes. The A-IoT device can receive a carrier wave from a reader. The A-IoT device can receive a carrier wave from nodes other than the reader. The reader can provide / transmit a carrier wave. The reader may not provide / transmit a carrier wave. Device-to-reader (D2R) transmissions from A-IoT devices can be generated internally by the device or backscattered on an externally provided carrier. Comparing New Radio (NR) User Equipment (UE) power consumption to mW (e.g., a maximum UE transmission power of 23 dBm corresponds to 199.5 mW), the output power of A-IoT devices can typically range from 1 μW to several hundred μW. Currently, the general range addresses the following types of IoT devices in different environments:
[0470] - A type I environmental IoT device may have a peak power consumption of 1 μW, energy storage, and neither downlink (DL) nor uplink (UL) amplification. Transmissions from a type I environmental IoT device may be backscattered on an externally provided carrier. A type I environmental IoT device may be a type 1 device.
[0471] - The second type of environmental IoT device may have a peak power consumption of ≤ several hundred μW, energy storage, and DL and / or UL amplification. Transmissions from the second type of environmental IoT device may be backscattered on an externally provided carrier (e.g., a type 2a device) or backscattered on a carrier generated internally by the device (e.g., a type 2b device). The second type of environmental IoT device may be a type 2a device and / or a type 2b device.
[0472] In topology 1, for example, such as TR 38.848 (e.g., [2] 3GPP TR 38.848 V18.0.0 (2023-09)) Figure 4 As shown in .2.1.1-1, the A-IoT device (e.g., the first UE) will communicate directly and bidirectionally with the base station (e.g., the network (NW)). In Topology 2, for example, as in TR 38.848 (e.g., [2] 3GPP TR 38.848 V18.0.0 (2023-09)). Figure 4 As shown in .2.1.1-2, the A-IoT device will communicate bidirectionally with the intermediate node (e.g., reader, second UE) between the A-IoT device and the base station. More details about A-IoT operation, functions and / or device / reader / UE can be found in work items [1] RP-243326, [2] 3GPP TR 38.848 V18.0.0 (2023-09) and [3] 3GPP TR 38.769 V19.0.0 (2024-12).
[0473] In the context of IoT, various services are provided, such as inventory and command. In response to a service request (e.g., inventory, command) received from the A-IoT Core Network (CN), the A-IoT Radio Access Network (RAN) (e.g., Next-Generation Node B (gNB), reader) executes the indicated / corresponding procedure (e.g., inventory, command) to the device, and then sends a response or report (e.g., command response, inventory report) to the A-IoT CN after execution. The purpose of the inventory procedure is to inquire about the device's presence, while the command procedure / type includes at least one of read, write, and deactivate. During the command procedure, the reader sends an R2D message for the command service (e.g., read, write, or deactivate), and the device executes a D2R transmission containing a response to the R2D message. The reader indicates scheduling information for the D2R transmission via the R2D transmission (e.g., an R2D transmission including an R2D message).
[0474] However, the varying characteristics of D2R responses for different command types introduce scheduling complexity for the reader. For example, a response to a read command might be a service data response, which could require a larger transport block (TB) size. On the other hand, a response to a write command might be an operation result indication. Furthermore, different devices may have different operation times (e.g., due to device capabilities), making it difficult for the reader to accurately provide resources for D2R responses in the time domain. When a device is scheduled to perform a D2R transfer for a response, the operation indicated by the command request message (e.g., a write command) may not yet be complete. Therefore, no upper-layer data will be available for D2R transfer. If the reader schedules resources before the D2R response is available for transfer (or before the D2R response is obtained), the device may not be able to use the resources to transfer the D2R response. Additionally, to obtain a response from the device, the reader may have to send follow-up / tracking R2D messages, which can result in signaling overhead. To minimize signaling overhead, some auxiliary information from the device will be required.
[0475] For the inventory service, the A-IoT CN can send an inventory request to the A-IoT RAN node. The inventory request may include the A-IoT device identifier and / or the requested range (area). In response to receiving the request, the reader can perform an inventory procedure with the indicated A-IoT device. The inventory procedure may be supported / executed by a (random) access procedure. After obtaining the device identifier (e.g., in message 1 (Msg1) or Msg3 of the (random) access procedure), the A-IoT RAN node can send one or more inventory report messages to the A-IoT CN containing the received inventory results.
[0476] A command service may (require) be followed by an inventory procedure. Alternatively, a command service may (not) be followed by an inventory procedure. A command service / operation may include (at least) reading, writing, and / or deactivation. The A-IoT CN may send a command request to the A-IoT RAN node. In response to receiving the request, the reader may execute the command procedure with the indicated A-IoT device. After executing the command procedure, the indicated device may send a D2R response to the A-IoT RAN node. The A-IoT RAN node may send a command response message containing the command result to the A-IoT CN.
[0477] The (random) access procedure can be / includes a contention-based (random) access procedure and / or a contention-free (random) access procedure. The reader can send a first R2D message (e.g., an A-IoT paging message) to one or more devices to trigger a (random) access procedure (e.g., by including device identification / ID in the first R2D message). In response to receiving the first R2D message, the device can perform a first D2R transmission to the reader (e.g., Msg1, ID). The device can deduce from the first R2D message a dedicated resource (e.g., for a contention-free procedure) or a shared resource (e.g., for a contention-based procedure) for the first D2R transmission. In response to performing the first D2R transmission, the device can receive a second R2D message (e.g., Msg2). In response to receiving the second R2D message, the device may or may not perform a second D2R transmission (e.g., Msg3). The first D2R transmission may include a (random, device) ID / identifier. The second D2R transmission may include a (device) identifier.
[0478] The reader can send a (third) R2D message to the device (e.g., after a (random) access procedure, after a first / second D2R transmission). The (third) R2D message can be / contain a command (message) (e.g., read, write, and / or deactivate) / related to said command. The (third) R2D message can identify the device by including the device ID (e.g., Access Stratum (AS) ID). The (third) R2D message can be dedicated to the device. The (third) R2D message can instruct the device to perform a (first) operation (e.g., read, write, and / or deactivate). The device can respond to receiving the (third) R2D message / perform the first operation after receiving the (third) R2D message. The (third) R2D message can instruct the device to perform a (third) D2R transmission. The (third) D2R transmission can be / contain (upper-layer) data, an operation result report, and / or (e.g., 1-bit, 2-bit) result indication (e.g., whether the first operation was successfully performed). (Third) D2R transmission can be a response to a (third) R2D message. The reader can allocate / schedule one or more D2R (time / frequency) resources to the device for (third) D2R transmission. The reader can indicate / include one or more D2R resources to the device in a (third) R2D message and / or another (third) R2D message. Another (third) R2D message can be an R2D message providing / indicating scheduling information and / or D2R (time / frequency) resources for (third) D2R transmission. The device can perform (third) D2R transmission on (partial or all) of one or more D2R resources. The reader can allocate / schedule / configure D2R resources using (e.g., first, second, and / or third) methods. The reader can indicate which method (e.g., first, second, and / or third) to apply via R2D messages (e.g., third R2D message, another (third) R2D message). Preferably, in some embodiments, the (third) R2D message and another (third) R2D message may be included in the same R2D transmission or in different / separate R2D transmissions.
[0479] The first method may be to send one or more R2D messages to schedule one or more D2R transmissions. Preferably, in some embodiments, each of the one or more R2D messages may schedule one of the one or more D2R transmissions. The reader may transmit one or more R2D messages to the device for service (request) and / or command procedures. The device may receive one or more R2D messages from the reader during a command procedure. One or more D2R transmissions may and / or contain upper-layer data and / or a response to a command / request / service. The one or more R2D messages may be / contain (at least) a third R2D message, a fourth R2D message, and / or other (subsequent) R2D messages. The reader may send a fourth R2D message in response to receiving a third D2R transmission or after receiving a third D2R transmission. The device may receive a fourth R2D message in response to performing a third D2R transmission or after performing a third D2R transmission. The reader may send other subsequent R2D messages in response to receiving a fourth D2R transmission or after receiving a fourth D2R transmission. The device may respond to performing a fourth D2R transmission or receiving another subsequent R2D message after performing the fourth D2R transmission. (Another) one or more R2D messages may contain / indicate the device's ID (e.g., AS ID). (Another) one or more R2D messages may contain / indicate the ID of the service (request) (e.g., transaction ID). (Another) each of the one or more R2D messages may contain / indicate a D2R resource for the corresponding D2R transmission. For example, (another) third R2D message may indicate / contain a D2R resource for the third D2R transmission. The fourth R2D message may indicate / contain a D2R resource for the fourth D2R transmission. (Another) one or more R2D messages may be / contain a command message (e.g., a (service type / command type) message identical to the third R2D message) (e.g., a retransmission of the third R2D message having the same format as the third R2D message). Alternatively and / or additionally, in some embodiments, (another) one or more R2D messages may not contain a command message. (Another) One or more R2D messages may be / contain (only) resource scheduling messages (e.g., (only) used to indicate D2R resources to the device). Alternatively and / or additionally, in some embodiments, some of the R2D messages may be / contain command messages, and some of the R2D messages may be / contain resource scheduling messages (e.g., a third R2D message is / contains a command message, another third R2D message is / contains a resource scheduling message, and a fourth R2D message is / contains a resource scheduling message).
[0480] Preferably, in some embodiments, the reader may determine (e.g., whether or how to set) one of (another) one or more R2D messages in response to a previously / recently received D2R transmission or detection / reception status (e.g., detected, received, not detected, or not received) of a previous / recent D2R resource. Preferably, in some embodiments, after performing a D2R transmission (in one or more D2R transmissions), the device may listen to (another) one or more R2D messages (any one of them) for, for example, for a specific duration. Preferably, in some embodiments, after a D2R resource is scheduled / indicated by one (another) R2D message (regardless of whether the device performs a D2R transmission on a D2R resource), the device, for example, listens to (another) one or more R2D messages (any one of them) for, for example, for a specific duration. Preferably, in some embodiments, while the device is listening to (another) one or more R2D messages (any one of them), the device may or may not stop / pause / suspend the first operation. Preferably, in some embodiments, after the specific duration or after the device receives one (another) R2D message, the device may resume the first operation.
[0481] Alternatively and / or additionally, in some embodiments, the reader may transmit one or more R2D messages at a specific time / every specific time based on the reader's expected device processing time. The reader may derive / calculate / expect / determine a specific time based on the device type, the type of command / request / service, the reader's location, the device's location, the distance between the reader and the device, the size of the R2D message (e.g., command / request / service), and / or the (expected) size of the D2R message (e.g., response). The reader may derive / calculate / expect / determine a specific value based on the end of the R2D transmission (e.g., command / request / service), the start of the R2D transmission (e.g., command / request / service), and / or predefined / preconfigured values.
[0482] Alternatively and / or additionally, in some embodiments, the reader may periodically transmit one or more (another) R2D messages. The reader may transmit one or more (another) R2D messages based on a time period / duration. The reader may derive / calculate / expect / determine the length of the time period / duration based on the device type, the type of command / request / service, the reader's location, the device's location, the distance between the reader and the device, the size of the R2D message (e.g., command / request / service), and / or the (expected) size of the D2R message (e.g., response). The time period / duration may begin in response to the end of (e.g., command / request / service) R2D transmission and / or the start of (e.g., command / request / service) R2D transmission. The length of the time period / duration and / or the start time of the time period / duration may be predefined and / or (pre)configured by the NW. The time period / duration may be represented by a timer.
[0483] (For example, before completing the first operation) the reader may transmit (another) R2D message (e.g., a resource scheduling message) to the device. This (other) R2D message may not be an A-IoT paging message. This (other) R2D message may not trigger a (random) access procedure. This (other) R2D message may not contain an upper-layer request (e.g., inventory, command). This (other) R2D message may contain information for deriving resources for a D2R transmission (in one or more D2R transmissions). The reader may transmit this (other) R2D message after transmitting this (other / different) R2D message containing an upper-layer request (e.g., a command), and / or before receiving an upper-layer response to said request. The reader may transmit this (other) R2D message for scheduling the device to transmit an upper-layer response. Upon receiving (another) R2D message (or in response to this), the device may include its last or most recent service response (e.g., a command response, if available or obtained) in the corresponding D2R response. Upon receiving (another) R2D message (or in response to it), the device may not use the resources scheduled by (another) R2D message to transmit the D2R response (e.g., no MACSDU) (e.g., if no service response is available or the service response is not yet available or has not yet been obtained). Upon receiving (another) R2D message (or in response to it), the device may include second information in the corresponding D2R response (e.g., if no service response is available or the service response is not yet available or has not yet been obtained).
[0484] The device may receive another R2D message during (e.g., before completing the first operation). The device may perform a D2R transfer during (the first operation). Alternatively and / or additionally, in some embodiments, the device may not perform a D2R transfer during the first operation. The device may need to pause the first operation to receive one or more R2D messages. The device may need to stop / pause the first operation before performing a D2R transfer (on the D2R resource indicated in the corresponding R2D message). The device may need to (temporarily) stop the first operation for performing a D2R transfer (on the D2R resource indicated in the corresponding R2D message). The device may (re)start the first operation after performing a D2R transfer / in response to performing a D2R transfer.
[0485] Alternatively and / or additionally, in some embodiments, the device may periodically pause the first operation and / or listen for / receive (another) one or more R2D messages based on a first duration and a second duration. The first duration may be a periodic time. The second duration may be a listening time. The device may derive / calculate / expect / determine the length of the first duration and / or the second duration itself. The device may receive the length of the first duration and / or the second duration from a reader. The first duration may begin in response to receiving (e.g., a command / request / service) an R2D transmission, and / or the start of the first operation. The first duration and / or the second duration may be represented by a timer.
[0486] One or more D2R transmissions may be / contain one or more second pieces of information in the process of the first operation. Preferably, in some embodiments, each of the one or more D2R transmissions may be / contain a second piece of information in the process of the first operation.
[0487] For example, the second information may indicate whether the device has completed the first operation (e.g., during / before each of one or more D2R transmissions). The second information may include a first bit (e.g., 1 bit). If the device completes the first operation before the transmission of one or more D2R transmissions, the device may include the second information in the D2R transmission and / or set the second information (e.g., the first bit) to a first value (e.g., 1). The reader may acknowledge / consider the device to have successfully completed the first operation in response to receiving a D2R transmission containing the second information and / or the first bit with the first value. The reader may not need to respond to receiving a D2R transmission containing the second information and / or the first bit with the first value or send another R2D message (one or more other R2D messages) afterward. If the device has not completed the first operation before the transmission of one or more D2R transmissions (or the device is still performing the first operation), the device may include the second information in the D2R transmission and / or set the first bit to a second value (e.g., 0). The reader may, in response to receiving a D2R transmission containing second information having / as a second value and / or a first bit, acknowledge / consider that the device has not yet completed the first operation. The reader may, in response to receiving a D2R transmission containing second information having / as a second value and / or a first bit, send ((another) one or more R2D messages) another R2D message.
[0488] Alternatively and / or additionally, in some embodiments, the second information may indicate whether the device is able to continue the first operation. The second information may be / contain a second bit (e.g., 1 bit). If (at least) the device's energy storage is insufficient (to complete the first operation), the device may be unable to continue the first operation. If (at least) the device is able to continue the first operation before a D2R transmission (in one or more D2R transmissions), the device may include the second information in the D2R transmission and / or set the second bit to a third value (e.g., 1). The reader may, in response to receiving a D2R transmission containing the second information and / or the second bit with the third value, or subsequently confirm / consider that the device is able to continue the first operation. If (at least) the device is unable to continue the first operation before a D2R transmission, the device may include the second information in the D2R transmission and / or set the second bit to a fourth value (e.g., 0). The reader may, in response to receiving a D2R transmission containing the second information and / or the second bit with the fourth value, or subsequently confirm / consider that the device is unable to continue the first operation. The reader may stop the first operation (e.g., stop sending (another) or one or more R2D messages) in response to receiving a D2R transmission containing a second information and / or a second bit having a fourth value. The device may stop / terminate the first operation in response to performing a D2R transmission containing a second bit having a fourth value.
[0489] Alternatively and / or additionally, in some embodiments, the second information may indicate whether the device successfully received / decoded the command message (e.g., a third R2D message, a previous (other) one or more R2D messages) (e.g., whether there will be a (upper-layer) response to the command message). The second information may include / contain a third bit (e.g., 1 bit). If the device successfully receives / decodes the command message before a D2R transmission (in one or more D2R transmissions), the device may include the second information in the D2R transmission and / or set the third bit to a fifth value (e.g., 1). The reader may acknowledge / consider that the device successfully received / decoded the command message in response to receiving / after receiving a D2R transmission containing / as a fifth value of the second information and / or the third bit. If the device does not successfully receive / decode the command message before a D2R transmission, the device may include the second information in the D2R transmission and / or set the third bit to a sixth value (e.g., 0). The reader may, in response to receiving a D2R transmission containing a second information and / or a third bit having a sixth value, acknowledge / consider that the device has not successfully received / decoded the command message. The reader may, in response to receiving a D2R transmission containing a second information and / or a third bit having a sixth value, retransmit the command message (or (another) R2D message).
[0490] Alternatively and / or additionally, in some embodiments, the first, second, and / or third bits may be jointly designed (designed to be, for example, the same bit as the fourth bit) to indicate the aforementioned situation. For example, if (at least) the device is unavailable to continue the first operation, the device may set the fourth bit to a seventh value (e.g., 1) in the D2R transmission. If (at least) the device fails to successfully receive / decode the command message, the device may set the fourth bit to an eighth value (e.g., 0) in the D2R transmission.
[0491] Alternatively and / or additionally, in some embodiments, if the device has not completed the first operation before the D2R transmission (e.g., the device is still performing the first operation), the device may not need to perform the D2R transmission (in one or more D2R transmissions). If the reader does not receive a D2R transmission, the reader may retransmit the command message (or another R2D message). If the reader does not receive a D2R transmission (e.g., for a specific duration that can be referenced to the initial command message or the last received D2R transmission), the reader may stop the first operation (e.g., stop sending another one or more R2D messages).
[0492] Alternatively and / or additionally, in some embodiments, if the device is not available / cannot continue the first operation before (at least) a D2R transmission, the device may not (need to) perform a D2R transmission (in one or more D2R transmissions). If (at least) the reader does not receive a D2R transmission, the reader may retransmit the command message (or R2D message). If (at least) the reader does not receive a D2R transmission, the reader may stop the first operation (e.g., stop sending (another) one or more R2D messages).
[0493] Alternatively and / or additionally, in some embodiments, if the device is available / capable of continuing the first operation prior to the D2R transmission, the device may not (need) perform a D2R transmission (in one or more D2R transmissions). If the reader does not receive a D2R transmission, the reader may retransmit the command message (or (another) R2D message). If the reader does not receive a D2R transmission (e.g., for a specific duration that can be referenced to the initial command message or the last received D2R transmission), the reader may stop the first operation (e.g., stop sending another one or more R2D messages).
[0494] Alternatively and / or additionally, in some embodiments, if the device does not successfully receive / decode the command message before the D2R transmission, the device may not (need to) perform a D2R transmission (in one or more D2R transmissions). If the reader does not receive a D2R transmission, the reader may retransmit the command message (or R2D message). If the reader does not receive a D2R transmission, the reader may stop the first operation (e.g., stop sending one or more R2D messages).
[0495] Alternatively and / or additionally, in some embodiments, the second information may indicate the remaining / executed process of the first operation. The second information may be / include a fifth bit. For example (the fifth bit comprises two bits), if, prior to the transmission of a D2R transmission (in one or more D2R transmissions), at least the completion portion of the first operation (e.g., in bits / bytes or as a percentage) exceeds a first threshold, the device may include the second information in the D2R transmission and / or set the fifth bit to a ninth value (e.g., 00). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), at least the completion portion of the first operation (e.g., in bits / bytes or as a percentage) exceeds a second threshold but does not exceed a first threshold, the device may include the second information in the D2R transmission and / or set the fifth bit to a tenth value (e.g., 01). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the completion portion of (at least) the first operation (e.g., in bits / byte or percentage) exceeds a third threshold but does not exceed a second threshold, the device may include second information in the D2R transmission and / or set the fifth bit to an eleventh value (e.g., 10). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the completion portion of (at least) the first operation (e.g., in bits / byte or percentage) does not exceed a third threshold, the device may include second information in the D2R transmission and / or set the fifth bit to a twelfth value (e.g., 11). For another example (where the fifth bit comprises two bits), if, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / byte, percentage, or (expected) time) exceeds a first threshold, the device may include second information in the D2R transmission and / or set the fifth bit to a ninth value (e.g., 00). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / bytes, as a percentage, or the (expected) time) exceeds a second threshold but does not exceed a first threshold, the device may include second information in the D2R transmission and / or set the fifth bit to a tenth value (e.g., 01). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / bytes, as a percentage, or the (expected) time) exceeds a third threshold but does not exceed a second threshold, the device may include second information in the D2R transmission and / or set the fifth bit to an eleventh value (e.g., 10).If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / bytes, in percentages, or (expected) time) does not exceed a third threshold, the device may include second information in the D2R transmission and / or set the fifth bit to a twelfth value (e.g., 11). The (first, second, and third) thresholds may be indicated, (pre)configured / fixed, or specified.
[0496] Preferably, in some embodiments, the remaining / executed process of the first operation may be indicated / provided by the upper layer. Preferably, in some embodiments, when the device receives one of (another) or one or more R2D messages (or in response to this), or before (or in response to) the device transmitting a D2R transmission (e.g., in response to (another) or one or more R2D messages), the device may request the upper layer to obtain the remaining / executed process of the first operation. Alternatively and / or preferably, in some embodiments, the determination of the remaining / executed process of the first operation may be implemented by the device implementation.
[0497] The device may (is) perform a D2R transfer during the first operation. Alternatively and / or additionally, in some embodiments, the device may not (be) able to perform a D2R transfer during the first operation. The device may (need) to stop the first operation before performing a D2R transfer (on a D2R resource indicated in (another) R2D message). The device may (re)start or resume the first operation after performing a D2R transfer / in response to performing a D2R transfer.
[0498] Preferably, in some embodiments, Figure 14A An example of the first method is shown. One or more R2D messages may include D2R scheduling information 1 (DSI1), DSI2, and DSI3. DSI can be / means D2R scheduling information included / contained in the (other) R2D message. One or more D2R transmissions may include D2R tx1, D2R tx2, and D2R tx3 individually / respectively scheduled / indicated by DSI1, DSI2, and DSI3. Preferably, in some embodiments, D2R tx1 and D2R tx2 may indicate that the device has not yet (not yet) completed the first operation (in response to a command). Preferably, in some embodiments, D2R tx3 may indicate that the device has completed the first operation.
[0499] The reader can send a (third) R2D message to the device. The (third) R2D message may contain an (upper-layer) command (message) (e.g., a read / write / (permanent) deactivation message) and / or a first D2R resource for the first D2R transmission. In response to (at least) upper-layer data (e.g., a command response, or a response to a command (message)) not yet being available or not yet acquired (e.g., the device (upper-layer) has not yet completed the command (operation)) (e.g., when the first D2R transmission is (generated) at the first transmission's D2R resource / before the first D2R transmission is (generated) at the first transmission's D2R resource) / after this / in this case, the device may set the first bit in the first D2R transmission to a first value (e.g., 1). In response to (at least) upper-layer data (e.g., a command response, or a response to a command (message)) not yet being available / after this / in this case, the device may not (need) include upper-layer data in the first D2R transmission (e.g., the Media Access Control (MAC) Service Data Unit (SDU) may be 0). In response to (at least) upper-layer data being available (for transmission) (e.g., when the first D2R transmission is generated at the D2R resource of the first transmission / before the first D2R transmission is generated at the D2R resource of the first transmission) / after this / in this case, the device may include upper-layer data in the first D2R transmission. If (at least) upper-layer data is (completely) unavailable (e.g., the device is unable to execute commands), the device may set the first bit in the first D2R transmission to a second value (e.g., 0).
[0500] In response to (at least) receiving a first D2R transmission indicating that upper-layer data is (not yet) available (e.g., the first bit is set to a first value), the reader may send a second R2D message to the device. The second R2D message may contain second D2R resources for the second D2R transmission (e.g., for a command response). The second R2D message may not contain (or may exclude) (upper-layer) commands (messages) (e.g., as in the first R2D message).
[0501] The second method may be / include sending an R2D message to schedule a D2R transmission. The reader may transmit an R2D message to the device for service (request) and / or command procedures. The device may receive an R2D message from the reader during a command procedure. A D2R transmission may and / or contain upper-layer data and / or a response to a command / request / service. An R2D message may be a third R2D message. A D2R transmission may be a third D2R transmission. The device may execute a D2R transmission after / in response to the successful completion of the first operation. A D2R transmission may contain a first bit (e.g., 1 bit) to indicate completion of the first operation. For example, if the device successfully completes the first operation, the device may set the first bit to a first value (e.g., 1). For example, the device may execute a D2R transmission after / once the device determines that it cannot successfully complete the first operation (e.g., decoding fails during the execution of the first operation). A D2R transmission may include a second bit (e.g., 1 bit) to indicate that the first operation was not (successfully) completed (or could not be completed). For example, if the device (at least) believes that it cannot (successfully) complete the first operation, the device may set the second bit to a fourth value (e.g., 0). Alternatively and / or additionally, in some embodiments, if the device (at least) believes that it cannot (successfully) complete the first operation, the device may set the first bit to a second value (e.g., 0).
[0502] An R2D message may indicate / contain a D2R resource for a D2R transmission with one or more time offsets. The D2R resource may be continuous / constant in the time domain. The D2R resource may reside within a continuous / constant transmission time interval (TTI). For example, an R2D message may indicate / contain a first time offset as the start time of the D2R resource. The device may (be allowed) perform a D2R transmission after the first time offset from receiving the R2D message. The device may (not be allowed) perform a D2R transmission before the first time offset from receiving the R2D message. For example, an R2D message may indicate / contain a third time offset as the end time of the D2R resource. The device may (be allowed) perform a D2R transmission before the third time offset from receiving the R2D message. The device may (not be allowed) perform a D2R transmission after the third time offset from receiving the R2D message. Alternatively and / or additionally, in some embodiments, an R2D message may not indicate / include a third time offset. A third time offset may be specified or configured. Preferably, in some embodiments, the D2R resource (continuous / persistent in the time domain) may be in a scheduled / indicated frequency domain resource. Preferably, in some embodiments, the D2R resource (continuous / persistent in the time domain) may be associated with a scheduled / indicated frequency shift (or chip repetition factor).
[0503] Preferably, in some embodiments, the device may be able to trigger / execute (a) D2R transfer after a first time offset and before a third time offset (if any). Preferably, in some embodiments, the device may trigger / execute (a) D2R transfer until the device implements the transfer. Preferably and / or alternatively, in some embodiments, the device may trigger / execute (a) D2R transfer in response to any of (upper-layer) data, operation result reports, and / or result indications (e.g., whether the first operation was successfully performed).
[0504] Preferably, in some embodiments, (a) D2R transmission may be / include second information of the process of the first operation (e.g., second information as described in the first method).
[0505] After receiving / once receiving a D2R transmission, the reader may release the D2R resource. After receiving / performing a D2R transmission, the D2R resource may be considered invalid (e.g., invalid by the reader or device). The device may not (be allowed to) perform (another) D2R transmission after performing a D2R transmission. Alternatively and / or additionally, in some embodiments, after receiving / once receiving a D2R transmission, the reader may not release the D2R resource. After receiving / performing a D2R transmission, the D2R resource may be considered valid (e.g., valid by the reader or device). The device can (is permitted) perform (another) D2R transmission after / once a D2R transmission is performed / during a D2R transmission. The reader can indicate whether the D2R resource is valid in an R2D message (e.g., (another) third R2D message), for example, after / once a D2R transmission is received / performed / during a D2R transmission. The reader can indicate whether the D2R resource is valid via the sixth bit (e.g., a 1-bit indication) in the R2D message, for example, after / once a D2R transmission is received / performed / during a D2R transmission. For example, if the resource is valid / remains valid, for example, after / once a D2R transmission is received / performed / during a D2R transmission, the reader can set the sixth bit to a thirteenth value (e.g., 1). If (at least) the resource is invalid, for example, after receiving / performing a D2R transmission / once receiving / performing a D2R transmission / when receiving / performing a D2R transmission, the reader can set the sixth bit to the fourteenth value (e.g., 0).
[0506] Alternatively and / or additionally, in some embodiments, the reader may release the D2R resource after a second time offset (if indicated) (e.g., if the reader does not receive a D2R transmission). After the second time offset (if indicated), the D2R resource may be considered invalid (e.g., by the reader or device). The device may not (be allowed) perform another D2R transmission after the second time offset. The reader may send another R2D message after the second time offset (if indicated) to indicate another D2R resource (e.g., if the reader does not receive a D2R transmission). Alternatively and / or additionally, in some embodiments, the reader may not (need) release the D2R resource after the second time offset (if indicated). After the second time offset (if indicated), the D2R resource may be considered valid (e.g., by the reader or device). The reader may send (another) R2D message (or resend the R2D message) after the second time offset (if indicated) to indicate the D2R resource (e.g., if the reader does not receive D2R transmissions).
[0507] Alternatively and / or additionally, in some embodiments, the reader may release the D2R resource after the timer expires (e.g., if the reader does not receive D2R transmissions). After the timer expires, the D2R resource may be considered invalid (e.g., by the reader or device). The reader may send another R2D message to indicate another D2R resource after the timer expires. Alternatively and / or additionally, in some embodiments, the reader may not need to release the D2R resource after the timer expires. After the timer expires, the D2R resource may be considered valid (e.g., by the reader or device). The reader may send another R2D message (or resend the R2D message) to indicate the D2R resource after the timer expires (e.g., if the reader does not receive D2R transmissions). The timer may be started during / in response to the transmission of an R2D message. The timer may be started after a first time offset during / in response to the transmission of an R2D message. The timer can be stopped upon receiving a D2R transmission / in response to receiving a D2R transmission. The timer can be configured at the reader. The timer (e.g., the length of the timer) can be (pre)configured / (pre)defined / preset.
[0508] Preferably, in some embodiments, a D2R transmission may be / include the remaining / executed process of the first operation. Preferably, in some embodiments, the remaining / executed process of the first operation may be indicated / provided by an upper layer. Preferably, in some embodiments, the device may (trigger) execute a D2R transmission when the remaining / executed process of the first operation is obtained (or in response to this). Preferably, in some embodiments, the device may request the upper layer to obtain the remaining / executed process of the first operation before the end time of the D2R resource. Alternatively and / or preferably, in some embodiments, the determination of the remaining / executed process of the first operation may be an implementation of the device.
[0509] Preferably, in some embodiments, after performing (one) D2R transmission (and if the first operation has not yet completed), the device may listen for another R2D message, for example, for a specific duration. Preferably, in some embodiments, after the end time of the D2R resource (and if the first operation has not yet completed), the device may listen for another R2D message, for example, for a specific duration. Preferably, in some embodiments, while the device is listening for another R2D message, the device may or may not stop / pause / suspend the first operation. Preferably, in some embodiments, after the specific duration or after the device receives another R2D message, the device may resume the first operation (or follow the instructions / commands of the other R2D message). Preferably, in some embodiments, after performing (one) D2R transmission (and if the first operation has completed), the device may listen for another / other R2D message (e.g., for other commands) for example, for a specific duration.
[0510] The device may (is) perform a D2R transfer during the first operation. Alternatively and / or additionally, in some embodiments, the device may not (be) able to perform a D2R transfer during the first operation. The device may (need) to stop the first operation before performing a D2R transfer (on the D2R resource indicated in the R2D message). The device may (re)start or resume the first operation after performing a D2R transfer or in response to performing a D2R transfer.
[0511] Preferably, in some embodiments, Figure 14BAn example of the second method is shown. An R2D message may include DSI1. An R2D message may include DSI2. DSI can be / means D2R scheduling information included / contained in an R2D message. A D2R transmission may include D2R tx1, wherein the available start time of D2R tx1 is scheduled / indicated by DSI1. A D2R transmission may include D2R tx2, wherein the available start time of D2R tx2 is scheduled / indicated by DSI2. Preferably, in some embodiments, D2R tx1 may indicate that the device has not completed the first operation (in response to a command). Preferably, in some embodiments, D2R tx2 may indicate that the device has completed the first operation.
[0512] The third method may be / include sending an R2D message to schedule one or more D2R transmissions. A reader may transmit an R2D message to a device for service (request) and / or command procedures. The device may receive an R2D message from the reader during a command procedure. One or more D2R transmissions may and / or contain upper-layer data and / or responses to commands / requests / services. One R2D message may be another third R2D message. One R2D message may contain / indicate one or more D2R resources for the corresponding one or more D2R transmissions. One or more D2R resources may be continuous / persistent in the time domain. One or more D2R resources may be located in continuous / persistent TTIs. One or more D2R resources may be separated in the time domain, for example, based on one or more time offsets / gap. For example, another (third) R2D message may indicate / include a D2R resource for a third D2R transmission, a D2R resource for a fourth D2R transmission, and / or a D2R resource for a fifth D2R transmission. An R2D message may indicate / contain one or more D2R resources for a D2R transmission with one or more time offsets. For example, an R2D message may indicate / contain a first time offset for D2R resources for a third D2R transmission. The device may (is permitted) perform a third D2R transmission at the first time offset from when an R2D message is received (e.g., with an error offset (±10%)). The device may not (is permitted) perform a third D2R transmission before or after the first time offset from when an R2D message is received (e.g., with an error offset (±10%)). An R2D message may indicate / contain a second time offset for D2R resources for a fourth D2R transmission. The device may (is permitted) perform a fourth D2R transmission at the second time offset from when an R2D message is received (e.g., with an error offset (±10%)). The device may not (be permitted) perform a fourth D2R transmission before or after a second time offset from the receipt of (a) R2D message (e.g., with a certain error offset (±10%)). Alternatively and / or additionally, in some embodiments, the device may (be permitted) perform a fourth D2R transmission at a second time offset after performing a third D2R transmission (e.g., with a certain error offset (±10%)). The device may not (be permitted) perform a fourth D2R transmission before or after a second time offset after performing a third D2R transmission (e.g., with a certain error offset (±10%)).
[0513] Preferably, in some embodiments, one or more D2R resources may be in the same scheduled / indicated frequency domain resources, for example, scheduled / indicated by (a) R2D message. Preferably, in some embodiments, one or more D2R resources may be associated with the same scheduled / indicated frequency shift (or chip repetition factor), for example, scheduled / indicated by (a) R2D message.
[0514] The device may (is) perform a D2R transfer during the first operation. Alternatively and / or additionally, in some embodiments, the device may not (be) able to perform a D2R transfer during the first operation. The device may (need) to stop or suspend the first operation before performing a D2R transfer (on one of one or more D2R resources indicated in (another) R2D message). The device may (re)start or resume the first operation after performing a D2R transfer / in response to performing a D2R transfer.
[0515] One or more D2R transmissions may be / include one or more third pieces of information in the process of the first operation. Preferably, in some embodiments, each of the one or more D2R transmissions may be / include a third piece of information in the process of the first operation.
[0516] For example, third information can indicate whether the device has completed the first operation. The third information may be / contain a first bit (e.g., 1 bit). If the device completes the first operation before a D2R transmission (in one or more D2R transmissions), the device may include the third information in the D2R transmission and / or set the third information (e.g., the first bit) to a first value (e.g., 1). The reader may acknowledge / consider the device successfully completed the first operation in response to receiving a D2R transmission containing the third information with / as the first value and / or the first bit. The reader may release one or more D2R resources for subsequent D2R transmissions (if provided in the R2D message) in response to receiving a D2R transmission containing the third information with / as the first value and / or the first bit. If the device has not completed the first operation before a D2R transmission (or the device is still performing the first operation), the device may include the third information in the D2R transmission and / or set the first bit to a second value (e.g., 0). The reader may, in response to receiving a D2R transmission containing third information having / as a second value and / or a first bit, acknowledge / consider that the device has not yet completed the first operation. The reader may, in response to receiving a D2R transmission containing third information having / as a second value and / or a first bit, consider one or more D2R resources for subsequent D2R transmissions to be valid (if provided in the R2D message).
[0517] Alternatively and / or additionally, in some embodiments, third information may indicate whether the device is able to continue the first operation. The third information may be / include a second bit (e.g., 1 bit). If (at least) the device's energy storage is insufficient (to complete the first operation), the device may be unable to continue the first operation. If (at least) the device is able to continue the first operation before a D2R transmission (in one or more D2R transmissions), the device may include third information in the D2R transmission and / or set the second bit to a third value (e.g., 1). The reader may, in response to receiving a D2R transmission containing third information with / as a third value and / or the second bit, confirm / consider that the device is able to continue the first operation. If (at least) the device is unable to continue the first operation before a D2R transmission, the device may include third information in the D2R transmission and / or set the second bit to a fourth value (e.g., 0). The reader may, in response to receiving a D2R transmission containing third information with / as a fourth value and / or the second bit, confirm / consider that the device is unable to continue the first operation. The reader may stop the first operation in response to receiving a D2R transmission containing third information and / or a second bit having / as a fourth value. The device may stop / terminate the first operation in response to performing a D2R transmission containing a second bit having / as a fourth value.
[0518] Alternatively and / or additionally, in some embodiments, the third information may indicate whether the device successfully received / decoded the command message (e.g., a third R2D message, (a) R2D message). The third information may be / contain a third bit (e.g., 1 bit). If the device successfully receives / decodes the command message before a D2R transmission (in one or more D2R transmissions), the device may include the third information in the D2R transmission and / or set the third bit to a fifth value (e.g., 1). The reader may acknowledge / consider that the device successfully received / decoded the command message in response to receiving a D2R transmission containing the third information with / as a fifth value and / or the third bit. If the device does not successfully receive / decode the command message before a D2R transmission, the device may include the third information in the D2R transmission and / or set the third bit to a sixth value (e.g., 0). The reader may acknowledge / consider that the device did not successfully receive / decode the command message in response to receiving a D2R transmission containing the third information with / as a sixth value and / or the third bit. The reader can transmit a command message (or (another) R2D message) in response to receiving a D2R transmission containing a third information and / or a third bit with / as a sixth value.
[0519] Alternatively and / or additionally, in some embodiments, the first, second, and / or third bits may be designed together (e.g., designed as a fourth bit) to indicate the aforementioned situation. For example, if (at least) the device is unavailable to continue the first operation, the device may set the fourth bit to a seventh value (e.g., 1) in the D2R transmission. If (at least) the device fails to successfully receive / decode the command message, the device may set the fourth bit to an eighth value (e.g., 0) in the D2R transmission.
[0520] Alternatively and / or additionally, in some embodiments, if the device has not completed the first operation before the D2R transmission (e.g., the device is still performing the first operation), the device may not need to perform the D2R transmission (in one or more D2R transmissions). If the reader does not receive a D2R transmission, the reader may retransmit the command message (or another R2D message). If the reader does not receive a D2R transmission (e.g., for a specific duration that can be referenced to the initial command message or the last received D2R transmission), the reader may stop the first operation.
[0521] Alternatively and / or additionally, in some embodiments, if the device is not available / cannot continue the first operation prior to (at least) a D2R transmission, the device may not (need to) perform a D2R transmission (in one or more D2R transmissions). If (at least) the reader does not receive a D2R transmission, the reader may retransmit the command message (or R2D message). If (at least) the reader does not receive a D2R transmission, the reader may stop the first operation.
[0522] Alternatively and / or additionally, in some embodiments, if the device is available / capable of continuing the first operation prior to the D2R transmission, the device may not (need) perform a D2R transmission (in one or more D2R transmissions). If the reader does not receive a D2R transmission, the reader may retransmit the command message (or (another) R2D message). If the reader does not receive a D2R transmission (e.g., for a specific duration that can be referenced to the initial command message or the last received D2R transmission), the reader may stop the first operation.
[0523] Alternatively and / or additionally, in some embodiments, if the device does not successfully receive / decode the command message before the D2R transmission, the device may not (need to) perform a D2R transmission (in one or more D2R transmissions). If the reader does not receive a D2R transmission, the reader may retransmit the command message (or R2D message). If the reader does not receive a D2R transmission, the reader may stop the first operation.
[0524] Alternatively and / or additionally, in some embodiments, the third information may indicate the remaining / executed process of the first operation. The third information may be / include a fifth bit. For example (the fifth bit comprises two bits), if, prior to the transmission of a D2R transmission (in one or more D2R transmissions), at least the completion portion of the first operation (e.g., in bits / bytes or as a percentage) exceeds a first threshold, the device may include the third information in the D2R transmission and / or set the fifth bit to a ninth value (e.g., 00). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), at least the completion portion of the first operation (e.g., in bits / bytes or as a percentage) exceeds a second threshold but does not exceed the first threshold, the device may include the third information in the D2R transmission and / or set the fifth bit to a tenth value (e.g., 01). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the completion portion of (at least) the first operation (e.g., in bits / byte or percentage) exceeds a third threshold but does not exceed a second threshold, the device may include third information in the D2R transmission and / or set the fifth bit to an eleventh value (e.g., 10). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the completion portion of (at least) the first operation (e.g., in bits / byte or percentage) does not exceed a third threshold, the device may include third information in the D2R transmission and / or set the fifth bit to a twelfth value (e.g., 11). For another example (where the fifth bit comprises two bits), if, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / byte, percentage, or (expected) time) exceeds a first threshold, the device may include third information in the D2R transmission and / or set the fifth bit to a ninth value (e.g., 00). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / bytes, as a percentage, or the (expected) time) exceeds a second threshold but does not exceed a first threshold, the device may include third information in the D2R transmission and / or set the fifth bit to a tenth value (e.g., 01). If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion of (at least) the first operation (e.g., in bits / bytes, as a percentage, or the (expected) time) exceeds a third threshold but does not exceed a second threshold, the device may include third information in the D2R transmission and / or set the fifth bit to an eleventh value (e.g., 10).If, prior to the transmission of a D2R transmission (in one or more D2R transmissions), the incomplete / remaining portion (e.g., in bits / bytes, percentages, or (expected) time) of at least the first operation does not exceed a third threshold, the device may include third information in the D2R transmission and / or set the fifth bit to a twelfth value (e.g., 11). The (first, second, third) thresholds may be indicated, (pre)configured / fixed, or specified.
[0525] Preferably, in some embodiments, the remaining / executed process of the first operation may be indicated / provided by the upper layer. Preferably, in some embodiments, when the device receives (a) R2D message (or in response to it) or before (or in response to it) a D2R transmission (in one or more D2R transmissions), the device may request the upper layer to obtain the remaining / executed process of the first operation. Alternatively and / or preferably, in some embodiments, the determination of the remaining / executed process of the first operation may be implemented by the device implementation.
[0526] Preferably, in some embodiments, after performing a D2R transmission (and / or if the first operation has not yet completed and / or if the device is unable / unavailable to continue the first operation), the device may listen for another R2D message, for example, for a specific duration. Alternatively, after performing a D2R transmission (and / or if the first operation has not yet completed and / or if the device is able / available to continue the first operation), the device may not listen for another R2D message. Preferably, in some embodiments, while the device is listening for another R2D message, the device may or may not stop / pause / suspend the first operation. Preferably, in some embodiments, after a specific duration or after the device receives another R2D message, the device may resume the first operation (or follow the instructions / commands of the other R2D message). Preferably, in some embodiments, after performing a D2R transmission (and if the first operation has completed), the device may listen for other R2D messages (e.g., for other commands) for example, for a specific duration.
[0527] If (at least) the counter exceeds a threshold (e.g., if (at least) the reader does not receive a D2R transmission (in one or more D2R transmissions), the reader may release one or more D2R resources. If (at least) the counter exceeds the threshold, one or more D2R resources may be considered invalid (e.g., considered invalid by the reader or device). If (at least) the counter exceeds the threshold, the reader may send another R2D message to indicate another one or more D2R resources. Alternatively and / or additionally, in some embodiments, if (at least) the counter exceeds the threshold, the reader may not need to release one or more D2R resources. If (at least) the counter exceeds the threshold, the D2R resource may be considered valid (e.g., considered valid by the reader or device). If (at least) the counter exceeds the threshold (e.g., if (at least) the reader does not receive a D2R transmission), the reader may send another R2D message (or resend an R2D message) to indicate one or more D2R resources. A counter can be incremented by 1 when / in response to the failure to receive a D2R transmission (among one or more D2R transmissions). The counter can be set / reset to zero after successfully receiving a D2R transmission (among one or more D2R transmissions). The counter and / or threshold can be configured at the reader. The counter and / or threshold can be (pre)configured / (pre)defined / preset.
[0528] Preferably, in some embodiments, Figure 14C An example of the third method is shown. An R2D message may include DSI1. DSI can be / means D2R scheduling information included / contained in an R2D message. One or more D2R transmissions may include D2R tx1, D2R tx2, and D2R tx3 determined / derived based on one or more time offsets scheduled / indicated by DSI1. Preferably, in some embodiments, D2R tx1 and D2R tx2 may indicate that the device has not completed the first operation (in response to a command). Preferably, in some embodiments, D2R tx3 may indicate that the device has completed the first operation.
[0529] The reader can determine, based on first information, which of the first / second / third methods to allocate / schedule / configure D2R resources. Alternatively and / or additionally, in some embodiments, the device can determine, based on the first information, which of the first / second / third methods to utilize / adopt / use D2R resources. The reader can determine the configuration of one or more D2R resources (e.g., time offset, time domain location, frequency domain resource / bandwidth) based on fourth information. The first information may or may not be the second information. The first / fourth information may be provided / determined / indicated by the network. The first / fourth information may be provided / determined / indicated by the device (e.g., transmitted via the first / second D2R). The first / fourth information may be / include one or more of the following information.
[0530] Device Capacity
[0531] Device capability can refer to device type. Device type can be distinguished (at least) by peak power consumption, energy storage, and / or the method used to perform UL transmission. For example, a first-type environmental IoT device may have a peak power consumption of 1 μW, energy storage, and neither DL amplification nor UL amplification. Transmission from a first-type environmental IoT device may be backscattered on an externally provided carrier. A first-type environmental IoT device may be a type 1 device. For example, a second-type environmental IoT device may have a peak power consumption of ≤ several hundred μW, energy storage, and DL and / or UL amplification. Transmission from a second-type environmental IoT device may be backscattered on an externally provided carrier (e.g., a type 2a device) or backscattered on a carrier generated internally by the device (e.g., a type 2b device). A second-type environmental IoT device may be a type 2a device and / or a type 2b device.
[0532] Alternatively and / or additionally, in some embodiments, device capability may be the device's computing power / speed (e.g., the speed at which a first operation or any operation is performed / completed) (related to the device's computing power / speed). For example, information on device capability may be provided / evaluated / measured based on a threshold (e.g., in bit rate, the expected / required / average time to complete the first operation or any operation). If (at least) the device's computing power / speed is above a first threshold, the information may be (represented as) / belongs to a first level (e.g., 0, 00). If (at least) the device's computing power / speed is below a first threshold and above a second threshold, the information may be (represented as) / belongs to a second level (e.g., 1, 01). If (at least) the device's computing power / speed is below a second threshold and above a third threshold, the information may be (represented as) / belongs to a third level (e.g., 10). If (at least) the device's computing power / speed is below a third threshold, the information may be (represented as) / belongs to a fourth level (e.g., 11). Alternatively and / or additionally, in some embodiments, if the expected / required / average time to complete the first operation is less than a first threshold, the information may be (represented as) / belong to a first level (e.g., 0, 00). If the expected / required / average time to complete the first operation is greater than the first threshold and less than a second threshold, the information may be (represented as) / belong to a second level (e.g., 1, 01). If the expected / required / average time to complete the first operation is greater than the second threshold and less than a third threshold, the information may be (represented as) / belong to a third level (e.g., 10). If the expected / required / average time to complete the first operation is greater than the third threshold, the information may be (represented as) / belong to a fourth level (e.g., 11). The (first, second, and third) thresholds may be (pre-)configured / fixed.
[0533] The information can be device capabilities. For example, if (at least) the device's computing power / speed is above (e.g., a first) threshold, the reader can (determine) to allocate D2R resources by sending one or more R2D messages to schedule one or more D2R transmissions. If (at least) the device's computing power / speed is below (e.g., a third) threshold, the reader can (determine) to allocate D2R resources by sending one R2D message to schedule one (or more) D2R transmissions. For example, if (at least) the device's computing power / speed is above (e.g., a first) threshold, and the reader allocates D2R resources by sending one R2D message to schedule a D2R transmission, the reader can configure a first time offset to be shorter (e.g., shorter than another threshold). If (at least) the device's computing power / speed is below (e.g., a third) threshold, and the reader allocates D2R resources by sending one R2D message to schedule a D2R transmission, the reader can configure a first time offset to be longer (e.g., longer than another threshold).
[0534] Message Type
[0535] The message type can be / contains a service type (e.g., inventory, command), command type (e.g., read, write, deactivate), and / or data type of a (third) R2D message. The message type can be the operation type of the first operation (related to the operation type of the first operation) / contains the operation type of the first operation. The message type can be related to / associated with the processing / operation time during which the device performs the first operation. For example, the device can execute / complete a read command within a first duration. The device can execute a write command within a second duration. The first duration can be shorter than the second duration (e.g., average). The first duration can be fixed / predictable (e.g., for a reader) / with a small standard deviation. The second duration can be variable / unpredictable (e.g., for a reader) / with a larger standard deviation.
[0536] The information can be a message type. For example, if the message type is (at least) inventory / read / deactivate, the reader can (determine) allocate D2R resources by sending one or more R2D messages to schedule one or more D2R deliveries. If the message type is (at least) write, the reader can (determine) allocate D2R resources by sending one R2D message to schedule one (or more) D2R deliveries. For example, if the message type is (at least) write, and the reader (determines) allocate D2R resources by sending one R2D message to schedule a D2R delivery, the reader can (only) schedule the second time offset (and may not (need) to schedule the first time offset).
[0537] The content of the first operation
[0538] The content of the first operation may be / includes the (bit) length and / or duration of the operation. For example, if (at least) the (third) R2D message is / includes a read command, the content of the first operation may be the bit length of the reported data. The content of the first operation may be the required / expected / average time for the device to execute the read command (e.g., from receiving the (third) R2D message to executing the (third) D2R transmission). For example, if (at least) the (third) R2D message is / includes a write command, the content of the first operation may be the bit length of the written data. The content of the first operation may be the required / expected / average time for the device to execute the write command (e.g., from receiving the (third) R2D message to completing the (partial, complete) writing of the data, from receiving the (third) R2D message to executing the (third) D2R transmission).
[0539] The information can be the content of the first operation. For example, if the bit length of the first operation is short, or the required / expected / average time for the device to perform the first operation is short (e.g., shorter than a threshold), the reader can (determine) allocate D2R resources by sending one or more R2D messages to schedule one or more D2R transmissions. If the bit length of the first operation is long, or the required / expected / average time for the device to perform the first operation is long (e.g., longer than a threshold), the reader can (determine) allocate D2R resources by sending one R2D message to schedule one (or more) D2R transmissions. For example, if the bit length of the first operation is short, or the required / expected / average time for the device to perform the first operation is short (e.g., shorter than a threshold), and the reader allocates D2R resources by sending one R2D message to schedule a D2R transmission, the reader can configure a first time offset to be short (e.g., shorter than another threshold). If (at least) the bit length of the first operation is long, or the required / expected / average time for the device to perform the first operation is long (e.g., longer than a threshold), and the reader allocates D2R resources by sending an R2D message to schedule a D2R delivery, then the reader may configure the first time offset to be long (e.g., longer than another threshold).
[0540] Device energy state
[0541] The device energy state can be the energy stored in the device before receiving the (third) R2D message or before performing the first operation. The device energy state can indicate whether the device has sufficient energy to perform / complete the subsequent / follow-up transmission / procedure. The device energy state can be one bit or more bits. For example, if the device has sufficient energy to perform / complete the subsequent / follow-up transmission / procedure, the device can indicate the device energy state as a first value (e.g., 1). If the device does not have sufficient energy to perform / complete the subsequent / follow-up transmission / procedure, the device can indicate the device energy state as a second value (e.g., 0). For example, if the device has sufficient energy to perform / complete the subsequent / follow-up transmission / procedure, the device may not send / provide the device energy state (e.g., omit the device energy state). If the device does not have sufficient energy to perform / complete the subsequent / follow-up transmission / procedure, the device can send / provide the device energy state.
[0542] The information could be the device's energy status. For example, if (at least) the device indicates that it does not have enough energy to perform / complete a subsequent / follow-up transmission / procedure, the reader may not allocate D2R resources for (e.g., a third) D2R transmission.
[0543] After performing (e.g., indicated by a third R2D message) a D2R transmission (e.g., third, fourth), the device may receive (e.g., fourth) an R2D message to instruct the device to perform a D2R transmission / retransmission. The third R2D message may be / contain a command message. The fourth R2D message may be / contain a command message. The device may receive a fourth R2D message to instruct the device to perform (e.g., first, second) an operation while performing a first operation (e.g., indicated by a third R2D message) or after performing / completing a first operation.
[0544] (For example, the third and fourth) R2D messages may contain an ID. The ID may be contained in (MAC) control messages and / or upper layers (e.g., with command messages). (For example, the third and fourth) R2D messages may determine whether to contain an ID based on the message type. (For example, the third and fourth) R2D messages may determine whether to contain an ID based on the command / message / data (type) carried by the R2D message. For example, if the command carried by the R2D message is (at least) a write, then (for example, the third and fourth) the R2D message may contain an ID. If the command carried by the R2D message is (at least) a read / deactivate, then (for example, the third and fourth) the R2D message may not contain an ID. If the message carried by the R2D message is paging, then the R2D message may contain an ID. If the message carried by the R2D message is MSG2, then the R2D message may not contain an ID. The ID may be a transaction ID (e.g., associated with / related to the first R2D message / A-IoT paging message). The ID does not have to be a transaction ID.
[0545] Upon receiving / in response to receiving an R2D message containing an ID (e.g., a third), the device may store the ID (if (at least) no previously stored ID exists). If (at least) no previously stored ID exists, the device may consider the third R2D message to be a new R2D message (e.g., not a retransmission of a previously received R2D message). The device may perform the operation (e.g., a first operation) indicated in the third R2D message. The device may perform a third D2R transmission on the D2R resource indicated by the third R2D message. The device may perform a third D2R transmission containing (e.g., a second, third) information (as described above). The device may determine (e.g., a second, third) information based on the process of the first operation before performing the third D2R transmission.
[0546] Alternatively and / or additionally, in some embodiments, after receiving / in response to receiving an R2D message containing an ID (e.g., a fourth), the device may compare the ID with a previously stored ID (if at least) exists. If the ID differs from a previously stored ID, the device may consider the fourth R2D message to be a new R2D message (e.g., not a retransmission of a previously received R2D message). If the device has completed performing the (previous) first operation, the device may perform the (e.g., a second) operation indicated in the fourth R2D message. If the device is performing the first operation, the device may not perform the (e.g., a second) operation indicated in the fourth R2D message. If the device is performing the first operation, the device may perform the (e.g., a second) operation indicated in the fourth R2D message (and the device stops / terminates the performance of the first operation). The device can perform a D2R transmission (e.g., fourth) on a D2R resource indicated by a (e.g., fourth) R2D message (as described above). The device can perform a D2R transmission (e.g., fourth) containing (e.g., second, third) information (as described above). The device can determine (e.g., second, third) information based on the process of (e.g., second) operation before performing (e.g., fourth) D2R transmission.
[0547] If (at least) the ID is the same as a previously stored ID, the device may consider (e.g., the fourth) R2D message to be a retransmission of a previous (e.g., the third) R2D message. The device may consider the operation indicated in the (e.g., the fourth) R2D message to be the same as the previous / completed / in progress (e.g., the first) operation indicated in the (first) R2D message. The device may not perform the operation indicated in the (e.g., the fourth) R2D message. The device may perform (e.g., the fourth) D2R transmission on the D2R resource indicated by the (e.g., the fourth) R2D message (e.g., as described above). The device may perform (e.g., the fourth) D2R transmission containing (e.g., the second, third) information (e.g., as described above). The device may determine (e.g., the second, third) information based on the process of the previous / completed / in progress (e.g., the first) operation before performing (e.g., the fourth) D2R transmission.
[0548] If (at least) the device receives a first R2D message (e.g., an A-IoT paging message) with a different transaction ID for the device, the device may release the ID. If (at least) the device performs a new transmission of the first D2R transmission after receiving the first R2D message (e.g., an A-IoT paging message) or in response to receiving the first R2D message (e.g., an A-IoT paging message), the device may release the ID. If (at least) the device receives an explicit instruction to release the ID from the reader, the device may release the ID. If (at least) the device is powered off, the device may release the ID.
[0549] The device can determine whether to use the D2R resource indicated by the (e.g., fourth) R2D message based on whether the ID indicated by the R2D message is different from a previously stored ID. If (at least) the ID indicated by the R2D message is different from a previously stored ID, the device can use the D2R resource to perform D2R transmission (e.g., feedback, confirmation, response, or acknowledgment for the R2D message). If (at least) the ID indicated by the R2D message is the same as a previously stored ID, the device can perform D2R transmission without using the D2R resource (e.g., feedback, confirmation, response, or acknowledgment for the R2D message).
[0550] The device can use D2R resources indicated by (e.g., the fourth) R2D message to perform D2R transmission (e.g., feedback, confirmation, response, or acknowledgment to the R2D message), regardless of the ID indicated by the R2D message (e.g., regardless of whether the ID indicated by the R2D message is different from or the same as a previously stored ID, rather than based on the ID indicated by the R2D message).
[0551] IDs can be replaced by numbers, indexes, identifiers, or identifiers.
[0552] The reader can be configured or utilize a first timer (e.g., at the reader). The reader can start the timer after / in response to sending (e.g., third, fourth) R2D messages to the device. The reader can restart the timer after / in response to receiving (e.g., third, fourth) D2R transmissions indicated by R2D messages. The reader can stop the timer after / in response to receiving (e.g., third, fourth) D2R transmissions indicated by R2D messages. If the timer is running, the reader can maintain D2R resources used for performing D2R transmissions. If the timer is running, the reader can consider the D2R resources used for performing D2R transmissions to be valid. If the timer expires, the reader can release the D2R resources used for performing D2R transmissions. If (at least) the timer expires, the reader may consider the D2R resource used to perform the D2R transfer to be invalid.
[0553] It should be noted that any of the concepts, methods, aspects, alternatives, examples and embodiments mentioned above and herein may be combined or applied in whole or in part.
[0554] Throughout this disclosure, "UE" may be referred to as "NR UE" and / or replaced by "NR UE". "UE" may not be an Ambient IoT (A-IoT) UE. A device may be an Ambient IoT (A-IoT) UE.
[0555] An environmental IoT device can receive a first R2D signaling / message from a reader (e.g., an intermediate UE or a UE reader). The environmental IoT device can execute (or initiate) a first environmental IoT procedure in response to (or based on) the first R2D signaling / message. The first R2D signaling / message can be a query, paging (message), command, Layer 2 (L2) signaling / message (e.g., MAC control element (CE)), L1 signaling / message (e.g., Physical Reader Device Channel (PRDCH), R2D control information). The first R2D signaling / message can be received by an environmental IoT device, multiple environmental IoT devices, or (a group or more groups of environmental IoT devices). The first R2D signaling / message can be used to trigger (or instruct) a first environmental IoT procedure. The first R2D signaling / message can instruct which / which type of environmental IoT device should respond to the first R2D signaling / message. The first R2D signaling / message can indicate which / which (environmental IoT) devices are permitted to execute (or initiate) the first environmental IoT procedure. The first R2D signaling / message can indicate which / which data / information is requested to be reported / provided. The first R2D signaling / message can indicate the configuration / resources to be used in the first environmental IoT procedure.
[0556] The first environmental IoT procedure can be, for example, an (initial) environmental IoT access procedure, inventory procedure, command procedure, and / or "inventory and command" procedure for environmental IoT. The first environmental IoT procedure can be contention-based or contention-free. The environmental IoT device can access the NW / reader via the first environmental IoT procedure, receive R2D signaling / messages / configurations, and / or transmit (D2R) data. Resources and / or configurations for the first environmental IoT procedure may include, for example, physical device (to) reader channel (PDRCH) resources, PDRCH timing, frequency, and / or bandwidth for D2R transmission. Resources and / or configurations for the first environmental IoT procedure may include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmission.
[0557] It should be noted that any of the methods, aspects, alternatives, concepts, examples and / or embodiments described above and herein may be combined or applied in whole or in part.
[0558] Throughout this disclosure, PDRCH resources, PDRCH scheduling, D2R authorization, D2R resources and / or D2R scheduling are interchangeable.
[0559] R2D transmission can be a transmission from the reader to the device. R2D data can be (available) data on the reader side and / or data to be transmitted from the reader to the device. R2D transmission and / or R2D data may include indications, configurations, resources, signaling, and / or messages from the reader. R2D reception can be the reception of an R2D transmission. Preferably, in some embodiments, R2D can be / indicated or replaced / modified / represented as from the reader / network / intermediate node to the device / UE. Preferably, in some embodiments, R2D transmission may include / indicate PRDCH transmission. Preferably, in some embodiments, R2D transmission may include / indicate PRDCH transmission and R2D timing acquisition signals associated with PRDCH transmission (e.g., R2D preamble, clock acquisition portion, and / or start indicator portion) and / or intermediate code / postcode associated with PRDCH transmission.
[0560] D2R transmission can be a transmission from device to reader. D2R data can be (available) data on the device side and / or data to be transmitted from the device to the reader. D2R transmission and / or D2R data may include indications, signaling, and / or messages from the device. D2R transmission and / or D2R data may include information related to, for example, the device's UE ID, device ID, power state, buffered data, and / or segmentation. D2R resources and / or PDRCH resources may be or include resources provided from the reader / NW (e.g., via a corresponding R2D transmission), used by the device, and / or used for transmitting / performing D2R transmissions. Preferably, in some embodiments, D2R can be / means or replaces / changes / represents as a transmission from device / UE to reader / network / intermediate node. Preferably, in some embodiments, D2R transmission may include / means PDRCH transmission. Preferably, in some embodiments, D2R transmission may include / mean PDRCH transmission and D2R timing acquisition signals associated with PDRCH transmission (e.g., D2R preamble), intermediate codes associated with PDRCH transmission, and / or postcodes associated with PDRCH transmission.
[0561] (Environmental IoT) devices can receive carrier waves from readers. (Environmental IoT) devices can receive carrier waves from nodes other than readers. Readers can provide / transmit carrier waves. Readers can choose not to provide / transmit carrier waves.
[0562] PDRCH can be, or is referred to as, a channel for transmission from (environmental IoT) devices to readers. PDRCH can be, or is referred to as a (physical) channel for environmental IoT. PDRCH can be, or is referred to as a (physical) channel for D2R (data / control) transmission. R2D transmission can be transmitted via PDRCH. (Data and / or signaling) transmission from readers to (environmental IoT) devices can be transmitted via PDRCH.
[0563] PRDCH can be, or is referred to as, a channel for transmission from a reader to a (environmental IoT) device. PRDCH can be, or is referred to as, a (physical) channel for environmental IoT. PRDCH can be, or is referred to as, a (physical) channel for R2D (data / control) transmission. D2R transmission can be transmitted via PRDCH. Transmission of (data and / or signaling) from a (environmental IoT) device to a reader can be via PRDCH.
[0564] The (Environmental IoT) device can receive configurations related to environmental IoT. The (Environmental IoT) device can receive configurations and / or resources for executing / triggering / reporting a first environmental IoT procedure. The (Environmental IoT) device can receive configurations related to specific messages / signaling, such as those described above. Resources and / or configurations may include, for example, PDRCH (transmission) resources, timing, channel resources, frequency resources, and / or (sub)bands for D2R transmissions. Resources and / or configurations may include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmissions. The (Environmental IoT) device can listen to / receive PDRCHs during / in the first environmental IoT procedure.
[0565] Throughout this disclosure, scheduling can be one or more PDRCH resources for D2R transmission and / or one or more PDRCH resources for R2D reception. The scheduling can be an indication of timing and / or frequency.
[0566] Throughout this disclosure, "reader" can mean "network", "network node", "UE reader" or "intermediate node" or can be replaced by "network", "network node", "UE reader" or "intermediate node".
[0567] Throughout this disclosure, an ID can be (or include) a paging ID, device ID, UE ID, group ID, AS ID, identifier, or a portion (or part) of the foregoing (e.g., a partial ID) used for R2D / D2R transmission / reception between the reader and the device. An ID can be used to identify a device (e.g., within an area). An ID can be (or include) a random value, a temporary number, a Radio Network Temporary Identifier (RNTI), and / or a preamble number. An ID can be selected / generated / determined by the device. An ID can be (pre)configured, (pre)defined, indicated, and / or assigned by the network / reader or device.
[0568] Throughout this disclosure, R2D messages can be / include A-IoT paging messages, access timing trigger messages, R2D trigger messages, random ID response messages, (A-IoT) Msg2, R2D upper-layer data transmission messages, command messages, resource scheduling messages, read commands, write commands, and / or deactivation commands.
[0569] Throughout this disclosure, D2R transmission can be or include (A-IoT) Msg1, (A-IoT) Msg3, random ID message, first D2R message, D2R upper layer data transmission message, response / report message, and / or result indication response message.
[0570] Throughout this disclosure, “(R2D / D2R) transmission” can be interchanged with “(R2D / D2R) message”.
[0571] Throughout this disclosure, TTI / timing can be (time) timing, symbol, set of symbols, time slot, set of time slots and / or subframe.
[0572] The UE can be referred to as the UE, the Radio Resource Control (RRC) layer of the UE, the MAC entity of the UE, or the physical layer of the UE.
[0573] A device can be referred to as a device, the AS layer of a device, the MAC entity of a device, or the physical layer of a device.
[0574] Throughout this disclosure, an (environmental IoT) device can be a device for use in environmental IoT. An (environmental IoT) device can be a device with environmental IoT capabilities. An (environmental IoT) device can be an NR device. An (environmental IoT) device can be a Long Term Evolution (LTE) device. An (environmental IoT) device can be an IoT device. An (environmental IoT) device can be a wearable device. An (environmental IoT) device can be a sensor. An (environmental IoT) device can be a fixed device. An (environmental IoT) device can be a tag.
[0575] Throughout this disclosure, the UE can be a reader for environmental IoT, which, for example, triggers a first environmental IoT procedure, transmits R2D transmissions, and / or receives D2R transmissions. The UE can be a UE capable of performing environmental IoT operations. The UE can be an NR UE. The UE can be an LTE UE. Throughout this disclosure, the following can be used interchangeably: UE, NR UE, ordinary UE, and traditional UE. The UE can be a non-environmental IoT device.
[0576] A network can refer to a network node. A network (node) can refer to a base station. A network (node) can refer to an access point. A network (node) can refer to an evolved Node B (eNB). A network (node) can refer to a gNB. A network (node) can refer to a gateway. A network can refer to a reader.
[0577] Various examples and embodiments of the invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.
[0578] refer to Figure 15 Utilizing this and other concepts, systems, and methods of the present invention, a method 1000 for an apparatus in a wireless communication system includes receiving a first R2D message from a reader, wherein the first R2D message includes a command message, a resource indication, and one or more D2R resources (step 1002); performing a first operation in response to receiving the first R2D message, wherein the first operation is indicated by the command message (step 1004); determining, based on the resource indication, to perform a first D2R transmission on one or more D2R resources, wherein the first D2R transmission includes first information (step 1006); and performing the first D2R transmission on one or more D2R resources (step 1008).
[0579] In various embodiments, the command message includes / is read, write, and / or deactivate.
[0580] In various embodiments, if the device has not yet successfully performed the first operation, the resource indicator indicates whether to perform a D2R transfer.
[0581] In various embodiments, the first information includes / is any of the following: whether the device has completed the first operation before performing the first D2R transmission; whether the response to the first operation is available or has been obtained; whether the device is able to continue performing the first operation before performing the first D2R transmission; whether the device successfully received and / or decoded the command message before performing the first D2R transmission; and / or the remaining / execution process of the first operation before performing the first D2R transmission.
[0582] In various embodiments, the method further includes: in response to performing a first D2R transmission, receiving a second R2D message containing a second or more D2R resources; determining to perform a second D2R transmission on the second or more D2R resources, wherein the second D2R transmission contains second information; and performing the second D2R transmission on the second or more D2R resources.
[0583] In various embodiments, the second R2D message does not contain a command message.
[0584] In various embodiments, the method further includes: storing a first ID contained in a first R2D message; receiving a third R2D message in response to performing a first D2R transmission, the third R2D message containing a second command message, a second ID, and a third or more D2R resources; and / or comparing the second ID contained in the third R2D message with the first ID and / or replacing the second ID contained in the third R2D message with the first ID.
[0585] In various embodiments, the method further includes: if the second ID is different from the first ID, performing a second operation indicated by the second command message, and performing a third D2R transmission containing the second information.
[0586] In various embodiments, the method further includes: if the second ID is the same as the first ID, then not performing the second operation indicated by the second command message, and performing a third D2R transmission containing the second information.
[0587] In various embodiments, the second information includes / is any of the following: a response to the first operation; whether the device has completed the second operation before performing the third D2R transmission; whether the device is able to continue performing the second operation before performing the third D2R transmission; whether the device successfully receives and / or decodes the second command message before performing the third D2R transmission; and / or the remaining / execution process of the second operation before performing the third D2R transmission.
[0588] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a device in a wireless communication system (e.g., A-IoT), device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a first R2D message from a reader, wherein the first R2D message includes a command message, a resource indication, and one or more D2R resources; (ii) perform a first operation in response to receiving the first R2D message, wherein the first operation is indicated by the command message; (iii) determine, based on the resource indication, to perform a first D2R transmission on one or more D2R resources, wherein the first D2R transmission includes first information; and (iv) perform the first D2R transmission on one or more D2R resources. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.
[0589] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a reader in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a first R2D message to (e.g., A-IoT) device, wherein the first R2D message includes a command message, a resource indication, and one or more D2R resources; and (ii) receive a first D2R transmission on one or more D2R resources based on the resource indication, wherein the first D2R transmission includes first information. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.
[0590] refer to Figure 16 Utilizing this and other concepts, systems, and methods of the present invention, a method 1010 for an apparatus in a wireless communication system includes: receiving a first R2D message from a reader, wherein the first R2D message contains a command (e.g., a command message / instruction) and scheduling information for a first D2R resource for a first D2R transmission (step 1012); and in response to receiving the first R2D message, performing a first D2R transmission to the reader on the first D2R resource, wherein if a response to the command is not yet available (or a response to the command has not yet been obtained), the apparatus sets a first bit in the first D2R transmission to a first value, and if a response to the command is available (or a response to the command has been obtained), the apparatus includes the response to the command in the first D2R transmission (step 1014).
[0591] In various embodiments, if the response to the command is not yet available (e.g., when the device is preparing for or performing the first D2R transmission, the response to the command is not yet available or the response to the command has not yet been obtained), the device does not include the response to the command in the first D2R transmission.
[0592] In various embodiments, if the first operation indicated / triggered by the command has not been completed, the response to the command is not yet available or has not yet been obtained.
[0593] In various embodiments, the first value is 1.
[0594] In various embodiments, the first operation is a write command or write operation, a read command or read operation, and / or a deactivation command or deactivation operation. The first operation corresponds to a command that instructs writing, reading, and / or deactivation. The command instructs / triggers a write operation, a read operation, and / or a deactivation operation.
[0595] In various embodiments, if there is no response to the command (at all), the device sets the first bit in the first D2R transmission to a second value, where the second value is 0.
[0596] In various embodiments, after or in response to a first D2R transmission where a response to the command is not yet available (or a response to the command has not yet been received), the device receives a second R2D message, wherein the second R2D message contains scheduling information for a second D2R resource for the second D2R transmission and excludes a command, and / or in response to receiving the second R2D message, the device performs a second D2R transmission on the second D2R resource. The exclusion of a command in the second R2D message means or includes that the second R2D message does not contain a command.
[0597] In various embodiments, the second D2R transmits a response containing commands.
[0598] In various embodiments, the first R2D message is an R2D upper-layer data transfer message or an A-IoT paging message.
[0599] In various embodiments, the first D2R transmission and / or the second D2R transmission includes D2R upper-layer data transfer messages.
[0600] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a device in a wireless communication system (e.g., A-IoT), device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a first R2D message from a reader, wherein the first R2D message contains a command and scheduling information for a first D2R resource for a first D2R transmission; and (ii) in response to receiving the first R2D message, perform a first D2R transmission to the reader on the first D2R resource, wherein if a response to the command is not yet available (or a response to the command has not yet been obtained), the device sets a first bit in the first D2R transmission to a first value, and if a response to the command is available (or a response to the command has been obtained), the device includes the response to the command in the first D2R transmission. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.
[0601] See Figure 17Utilizing this and other concepts, systems, and methods of the present invention, a method 1020 for a reader in a wireless communication system includes: transmitting a first R2D message to a device, wherein the first R2D message contains a command (e.g., a command message / instruction) and scheduling information of a first D2R resource for a first D2R transmission (step 1022); receiving a first D2R transmission from the device on the first D2R resource, wherein the first D2R transmission indicates that a response to the command is not yet available (or a response to the command has not yet been obtained) (step 1024); and in response to receiving a first D2R transmission indicating that a response to the command is not yet available (or indicating that a response to the command has not yet been obtained), transmitting a second R2D message to the device, wherein the second R2D message contains scheduling information of a second D2R resource for a second D2R transmission and excludes the command (step 1026).
[0602] In various embodiments, by including the first bit as the first value, the response to the first D2R transmission instruction command is not yet available (e.g., when preparing for or performing the first D2R transmission, the response to the command is not yet available).
[0603] In various embodiments, the first value is 1.
[0604] In various embodiments, the response to the command is not yet available if the first operation indicated by the command has not been completed.
[0605] In various embodiments, the first operation is a write command or write operation, a read command or read operation, and / or a deactivation command or deactivation operation. The first operation corresponds to a command that instructs writing, reading, and / or deactivation. The command instructs / triggers a write operation, a read operation, and / or a deactivation operation.
[0606] In various embodiments, if there is no response to the command (at all), the first bit in the first D2R transmission is set to a second value, where the second value is 0.
[0607] In various embodiments, excluding a command in a second R2D message means or includes that the second R2D message does not contain a command.
[0608] In various embodiments, the first R2D message is a first R2D upper-layer data transfer message or a first A-IoT paging message, the second R2D message is a second R2D upper-layer data transfer message or a second A-IoT paging message, the first D2R transmission includes the first D2R upper-layer data transfer message, and / or the second D2R transmission includes the second D2R upper-layer data transfer message.
[0609] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a reader in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a first R2D message to the device, wherein the first R2D message contains a command and scheduling information for a first D2R resource for the first D2R transmission; (ii) receive the first D2R transmission from the device on the first D2R resource, wherein the first D2R transmission indicates that a response to the command is not yet available (or a response to the command has not yet been obtained); and (iii) in response to receiving a first D2R transmission indicating that a response to the command is not yet available (or a response to the command has not yet been obtained), transmit a second R2D message to the device, wherein the second R2D message contains scheduling information for a second D2R resource for the second D2R transmission and excludes the command. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.
[0610] Any combination of the concepts or teachings above or herein may be combined, in whole or in part, together or to form new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.
[0611] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein may be used independently, separately, and / or in combination with multiple methods, alternatives, steps, examples, and embodiments.
[0612] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented by using other structures, functions, or structures and functions other than or different from one or more aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time-hopping sequence.
[0613] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.
[0614] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of both, designed using source decoding or some other technique) and have instructions in various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.
[0615] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.
[0616] It should be understood that any particular order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that a particular order or hierarchy of steps in the process may be rearranged based on design preferences while remaining within the scope of this disclosure. The appended method claims present the elements of the various steps in an exemplary order and are not intended to be limited to any particular order or hierarchy presented.
[0617] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. Example storage media can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside in a user equipment as discrete components. Furthermore, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some aspects, the computer program product may include packaging material.
[0618] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications are possible. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which this invention pertains.
Claims
1. A method for an apparatus, characterized in that, include: Receive a first reader-to-device message from the reader, wherein the first reader-to-device message contains commands and scheduling information for the first device-to-reader resource to be transmitted by the first device-to-reader; as well as In response to receiving the first reader-to-device message, the first device-to-reader transmission is performed on the first device-to-reader resource to the reader, wherein: If the response to the command is not yet available or has not yet been obtained, the device sets the first bit in the first device-to-reader transmission to a first value, and If the response to the command is available or the response to the command has been obtained, then the response to the command is included in the transmission from the first device to the reader.
2. The method according to claim 1, characterized in that: If the response to the command is not yet available or has not yet been obtained, the device does not include the response to the command in the first device-to-reader transmission. If the first operation indicated by the command is not completed, then the response to the command is not yet available or the response to the command has not yet been obtained, and / or The first value is 1.
3. The method according to claim 2, characterized in that, The first operation is a write command or write operation, a read command or read operation, and / or a deactivation command or deactivation operation.
4. The method according to claim 1, characterized in that, If there is no response to the command, the device sets the first bit in the first device-to-reader transmission to a second value, and / or wherein the second value is 0.
5. The method according to claim 1, characterized in that: After or in response to a first device-to-reader transmission in which the response to the command is not yet available or has not yet been obtained, the device receives a second reader-to-device message, wherein the second reader-to-device message contains scheduling information for second device-to-reader resources for the second device-to-reader transmission and excludes the command, and / or In response to receiving the second reader-to-device message, the device performs the second device-to-reader transfer on the second device-to-reader resource.
6. The method according to claim 1, characterized in that: The first reader-to-device message is a reader-to-device upper-layer data transfer message or an environmental IoT paging message, and / or The first device transmits to the reader a data transfer message from the device to the upper layer of the reader.
7. A method for a reader, characterized in that, include: A first reader-to-device message is transmitted to the device, wherein the first reader-to-device message contains commands and scheduling information for the first device-to-reader resource for the first device-to-reader transmission; Receive a first device-to-reader transmission from the device on the first device-to-reader resource, wherein the first device-to-reader transmission indicates that the response to the command is not yet available or the response to the command has not yet been obtained; as well as In response to receiving a first device-to-reader transmission indicating that the response to the command is not yet available or that the response to the command has not yet been obtained, a second reader-to-device message is transmitted to the device, wherein the second reader-to-device message contains scheduling information for second device-to-reader resources for the second device-to-reader transmission and excludes the command.
8. The method according to claim 7, characterized in that: By including the first bit as a first value, the first device transmits to the reader an indication that the response to the command is not yet available or that the response to the command has not yet been obtained. The first value is 1, and / or If the first operation indicated by the command is not completed, then the response to the command is not yet available or the response to the command has not yet been obtained.
9. The method according to claim 8, characterized in that, The first operation is a write command or write operation, a read command or read operation, and / or a deactivation command or deactivation operation.
10. The method according to claim 7, characterized in that: The first reader-to-device message is either a data transmission message from the first reader to the upper layer of the device or a paging message for the first environment IoT. The second reader-to-device message is either a second reader-to-device upper-layer data transmission message or a second environment IoT paging message. The first device transmits to the reader a data transfer message from the first device to the upper layer of the reader, and / or The second device transmits a data transfer message to the reader containing information about the data transfer between the second device and the upper layer of the reader.
11. An apparatus, characterized in that, include: Memory; as well as A processor, operatively coupled to the memory, wherein the processor is configured to execute program code to: Receive a first reader-to-device message from the reader, wherein the first reader-to-device message contains commands and scheduling information for the first device-to-reader resource to be transmitted by the first device-to-reader; as well as In response to receiving the first reader-to-device message, the first device-to-reader transmission is performed on the first device-to-reader resource to the reader, wherein: If the response to the command is not yet available or has not yet been obtained, the device sets the first bit in the first device-to-reader transmission to a first value, and If the response to the command is available or the response to the command has been obtained, then the response to the command is included in the transmission from the first device to the reader.
12. The apparatus according to claim 11, characterized in that: If the response to the command is not yet available or has not yet been obtained, the device does not include the response to the command in the first device-to-reader transmission. If the first operation indicated by the command is not completed, then the response to the command is not yet available or the response to the command has not yet been obtained, and / or The first value is 1.
13. The apparatus according to claim 12, characterized in that, The first operation is a write command or write operation, a read command or read operation, and / or a deactivation command or deactivation operation.
14. The apparatus according to claim 11, characterized in that, If there is no response to the command, the device sets the first bit in the first device-to-reader transmission to a second value, and / or wherein the second value is 0.
15. The apparatus according to claim 11, characterized in that: After or in response to a first device-to-reader transmission in which the response to the command is not yet available or has not yet been obtained, the device receives a second reader-to-device message, wherein the second reader-to-device message contains scheduling information for second device-to-reader resources for the second device-to-reader transmission and excludes the command, and / or In response to receiving the second reader-to-device message, the device performs the second device-to-reader transfer on the second device-to-reader resource.
16. The apparatus according to claim 11, characterized in that: The first reader-to-device message is a reader-to-device upper-layer data transfer message or an environmental IoT paging message, and / or The first device transmits to the reader a data transfer message from the device to the upper layer of the reader.
