Determination of end of procedure
A timer-based mechanism in wireless devices enables reliable determination of procedure completion, addressing inefficiencies by reducing unnecessary restarts and power consumption in multi-reader environments.
Patent Information
- Application Number
- PCT/KR2026/096623
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
In wireless communication systems, devices face challenges in reliably determining the end of an ongoing procedure without explicit signaling, leading to inefficiencies such as repeated procedure restarts and increased power consumption, particularly in multi-reader environments with imperfect coordination.
A wireless device employs a timer mechanism to manage procedures, allowing it to respond to subsequent messages and restart the timer upon receiving new messages, thereby determining the end of an ongoing procedure based on timer expiration.
This approach enhances the device's ability to recognize procedure completion reliably, reduces unnecessary power consumption, and prevents inefficient restarts, improving responsiveness and resource utilization.
Smart Images

Figure KR2026096623_12112026_PF_FP_ABST
Abstract
Description
DETERMINATION OF END OF PROCEDURE
[0001] The present disclosure relates to determination of end of procedure.
[0002] 3rd Generation Partnership Project (3GPP) New Radio (NR) targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.
[0003] 6G is the successor to 5G cellular technology. 6G networks will be able to use higher frequencies than 5G networks and provide substantially higher capacity and much lower latency. The 6G technology market is expected to facilitate large improvements in the areas of imaging, presence technology and location awareness. Working in conjunction with Artificial Intelligence (AI), the 6G computational infrastructure will be able to identify the best place for computing to occur. This includes decisions about data storage, processing and sharing.
[0004] In wireless communication systems, particularly in scenarios involving A-IoT deployments and multi-reader environments, a device may receive multiple service requests while an ongoing procedure is still in progress. In such situations, the device behavior for handling newly received service requests becomes an important design consideration.
[0005] Conventionally, two approaches may be considered. According to a first approach, the device ignores new service requests and corresponding reader-to-device (R2D) messages that are not associated with the ongoing procedure. According to a second approach, the device terminates the ongoing procedure and responds to the latest service request. However, each approach presents certain limitations.
[0006] In the second approach, where the ongoing procedure is terminated in response to a new request, the device may experience a ping-pong problem, particularly in environments involving multiple readers. For example, when multiple readers initiate procedures in parallel, the device may repeatedly terminate and restart procedures without completing any of them, leading to inefficient operation and increased power consumption. Such behavior may be exacerbated in future deployments where coordination among multiple readers is imperfect, for example due to mobility of reader devices or temporary coverage gaps, thereby reducing reliability of the system.
[0007] On the other hand, the first approach, which ignores new requests during an ongoing procedure, may avoid the ping-pong problem but introduces a different challenge. Specifically, for the device to correctly ignore new requests, the device needs to accurately determine whether the ongoing procedure has ended. In conventional systems, the end of the procedure may be indicated through a signaling message from the reader. However, if the device fails to receive such an indication, the device may remain unaware of the completion of the procedure and may continue to ignore subsequent valid requests, resulting in degraded service responsiveness.
[0008] Accordingly, there exists a need for a mechanism that enables the device to reliably determine the end of an ongoing procedure without relying solely on explicit signaling, while avoiding inefficiencies such as repeated procedure restarts or unnecessary power consumption.
[0009] Therefore, there may be a need for a mechanism that enables a device to reliably determine whether an ongoing procedure has ended, even in the absence of explicit signaling from a reader. Such a mechanism should allow the device to correctly handle subsequent service requests without remaining in an indefinite state of ignoring new requests, while avoiding inefficiencies such as repeated procedure restarts or unnecessary power consumption.
[0010] In an aspect, a method performed by a wireless device is provided. The method comprises receiving a first Reader-to-Device (R2D) message related to a first procedure. The method comprises starting a timer related to the first procedure. while the timer is running, the method comprises i) receiving a subsequent R2D message related to the first procedure, ii) responding to the subsequent R2D message, iii) restarting the timer, iv) receiving a second R2D message related to a second procedure, and v) discarding the second R2D message.
[0011] The present disclosure may have various advantageous effects.
[0012] For example, the device can reliably recognize the end of an ongoing procedure even when an explicit end-of-procedure indication is not successfully received from a reader, thereby improving robustness of procedure handling.
[0013] For example, by enabling the device to determine the completion of the procedure based on a timer mechanism, the device can avoid remaining in a state of continuously ignoring valid subsequent service requests, thereby improving responsiveness to new requests.
[0014] For example, the proposed mechanism can prevent repeated termination and restarting of procedures in multi-reader scenarios, thereby avoiding ping-pong effects and reducing unnecessary energy consumption.
[0015] For example, by reducing unnecessary procedure restarts and inefficient processing, the device can operate more efficiently in terms of both resource utilization and power consumption.
[0016] For example, the overall system performance can be improved by ensuring stable procedure completion and efficient handling of subsequent service requests, particularly in environments where coordination among multiple readers is imperfect.
[0017] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.
[0018] FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.
[0019] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.
[0020] FIG. 3 shows an example of UE to which implementations of the present disclosure are applied.
[0021] FIGS. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.
[0022] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.
[0023] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.
[0024] FIG. 8 shows an example of Support of Ambient IoT.
[0025] FIG. 9 shows an example of Radio Protocol Architecture for A-IoT Communication.
[0026] FIGS. 10 and 11 show examples of A-IoT Access Procedure.
[0027] FIG. 12 shows an example of a method performed by a wireless device to which implementations of the present disclosure are applied.
[0028] FIG. 13 shows an example of a method performed by a reader to which implementations of the present disclosure are applied.
[0029] FIG. 14 shows an example in which a device performs a timer-based determination of procedure completion to which implementations of the present disclosure are applied.
[0030] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and a Multi Carrier Frequency Division Multiple Access (MC-FDMA) system. CDMA may be embodied through radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA may be embodied through radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is a part of a Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in Downlink (DL) and SC-FDMA in Uplink (UL). Evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, and / or 5G New Radio (NR).
[0031] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.
[0032] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.
[0033] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".
[0034] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".
[0035] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".
[0036] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C".
[0037] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".
[0038] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.
[0039] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.
[0040] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.
[0041] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.
[0042] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.
[0043] Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).
[0044] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.
[0045] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.
[0046] The wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR / VR / Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.
[0047] In the present disclosure, the wireless devices 100a to 100f may be called user equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.
[0048] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
[0049] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.
[0050] NR supports multiples numerologies (and / or multiple Sub-Carrier Spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.
[0051] The NR frequency band may be defined as two types of frequency range, i.e., Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter Wave (mmW).
[0052] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz
[0053] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).
[0054] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz
[0055] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.
[0056] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.
[0057] In FIG. 2, The first wireless device 100 and / or the second wireless device 200 may be implemented in various forms according to use cases / services. For example, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / parts, and / or modules.
[0058] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and / or one or more antennas 108.
[0059] The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. Additional and / or alternatively, the memory 104 may be placed outside of the processing chip 101.
[0060] The processor 102 may control the memory 104 and / or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106 and then store information obtained by processing the second information / signals in the memory 104.
[0061] The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a firmware and / or a software code 105 which implements codes, commands, and / or a set of commands that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more protocols. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.
[0062] Herein, the processor 102 and the memory 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.
[0063] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and / or one or more antennas 208.
[0064] The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. Additional and / or alternatively, the memory 204 may be placed outside of the processing chip 201.
[0065] The processor 202 may control the memory 204 and / or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver 206. The processor 202 may receive radio signals including fourth information / signals through the transceiver 106 and then store information obtained by processing the fourth information / signals in the memory 204.
[0066] The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a firmware and / or a software code 205 which implements codes, commands, and / or a set of commands that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more protocols. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.
[0067] Herein, the processor 202 and the memory 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be interchangeably used with RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.
[0068] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Unit (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.
[0069] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. For example, the one or more processors 102 and 202 may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a memory control processor.
[0070] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cash memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.
[0071] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.
[0072] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208. Additionally and / or alternatively, the one or more transceivers 106 and 206 may include one or more antennas 108 and 208. The one or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).
[0073] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202.
[0074] Although not shown in FIG. 2, the wireless devices 100 and 200 may further include additional components. The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, an Input / Output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The additional components 140 may be coupled to the one or more processors 102 and 202 via various technologies, such as a wired or wireless connection.
[0075] In the implementations of the present disclosure, a UE may operate as a transmitting device in UL and as a receiving device in DL. In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.
[0076] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.
[0077] FIG. 3 shows an example of a UE to which implementations of the present disclosure are applied.
[0078] Referring to FIG. 3, a UE 100 may correspond to the first wireless device 100 of FIG. 2.
[0079] A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keypad 144, a Subscriber Identification Module (SIM) card 145, a speaker 146, and a microphone 147.
[0080] The processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of DSP, CPU, GPU, a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by QUALCOMM®, EXYNOSTMseries of processors made by SAMSUNG®, A series of processors made by APPLE®, HELIOTMseries of processors made by MEDIATEK®, ATOMTMseries of processors made by INTEL® or a corresponding next generation processor.
[0081] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.
[0082] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.
[0083] The power management module 141 manages power for the processor 102 and / or the transceiver 106. The battery 142 supplies power to the power management module 141.
[0084] The display 143 outputs results processed by the processor 102. The keypad 144 receives inputs to be used by the processor 102. The keypad 144 may be shown on the display 143.
[0085] The SIM card 145 is an integrated circuit that is intended to securely store the International Mobile Subscriber Identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards.
[0086] The speaker 146 outputs sound-related results processed by the processor 102. The microphone 147 receives sound-related inputs to be used by the processor 102.
[0087] FIGS. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.
[0088] In particular, FIG. 4 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 5 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 4, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 5, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a Non-Access Stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an Access Stratum (AS).
[0089] In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network Quality of Service (QoS) flows.
[0090] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / de-multiplexing of MAC SDUs belonging to one or different logical channels into / from Transport Blocks (TB) delivered to / from the physical layer on transport channels; scheduling information reporting; error correction through Hybrid Automatic Repeat reQuest (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.
[0091] Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast Control Channel (BCCH) is a downlink logical channel for broadcasting system control information, Paging Control Channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing Public Warning Service (PWS) broadcasts, Common Control Channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and Dedicated Control Channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated Traffic Channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to Broadcast Channel (BCH); BCCH can be mapped to Downlink Shared Channel (DL-SCH); PCCH can be mapped to Paging Channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to Uplink Shared Channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.
[0092] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration is per logical channel with no dependency on numerologies and / or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).
[0093] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using Robust Header Compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.
[0094] In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS Flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.
[0095] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5G Core network (5GC) or Next-Generation Radio Access Network (NG-RAN); establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to / from NAS from / to UE.
[0096] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.
[0097] The frame structure shown in FIG. 6 is purely exemplary and the number of subframes, the number of slots, and / or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., SCS, Transmission Time Interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or Cyclic Prefix (CP)-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols).
[0098] Referring to FIG. 6, downlink and uplink transmissions are organized into frames. Each frame has Tf= 10ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a CP. In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing △f = 2u*15 kHz.
[0099] Table 3 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the normal CP, according to the subcarrier spacing Δf= 2u*15 kHz.
[0100] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016
[0101] Table 4 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing △f = 2u*15 kHz.
[0102] uNslotsymbNframe,uslotNsubframe,uslot212404
[0103] A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid of Nsize,ugrid,x*NRBscsubcarriers and Nsubframe,usymbOFDM symbols is defined, starting at Common Resource Block (CRB) Nstart,ugridindicated by higher-layer signaling (e.g., RRC signaling), where Nsize,ugrid,xis the number of Resource Blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system, NRBscis 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth Nsize,ugridfor subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a Resource Element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.In the 3GPP NR system, RBs are classified into CRBs and Physical Resource Blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a BandWidth Part (BWP) and numbered from 0 to NsizeBWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB= nCRB+ NsizeBWP,i, where NsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.
[0104] In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL Component Carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.
[0105] In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment / re-establishment / handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment / handover, one serving cell provides the security input. The cell is referred to as the Primary Cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of Special Cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For Dual Connectivity (DC) operation, the term SpCell refers to the PCell of the Master Cell Group (MCG) or the Primary SCell (PSCell) of the Secondary Cell Group (SCG). An SpCell supports Physical Uplink Control Channel (PUCCH) transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA / DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.
[0106] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.
[0107] Referring to FIG. 7, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted / received using radio resources through the PHY layer to / from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.
[0108] In the PHY layer, the uplink transport channels UL-SCH and Random Access Channel (RACH) are mapped to their physical channels Physical Uplink Shared Channel (PUSCH) and Physical Random Access Channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH) and PDSCH, respectively. In the PHY layer, Uplink Control Information (UCI) is mapped to PUCCH, and Downlink Control Information (DCI) is mapped to Physical Downlink Control Channel (PDCCH). A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.
[0109] Hereinafter, technical features related to IoT technology are described. TR 38.848 V18.00 may be referred.
[0110] In recent years, IoT has attracted much attention in the wireless communication world. More 'things' are expected to be interconnected for improving productivity efficiency and increasing comforts of life. Further reduction of size, complexity, and power consumption of IoT devices can enable the deployment of tens or even hundreds of billions of IoT devices for various applications and provide added value across the entire value chain. It is impossible to power all the IoT devices by battery that needs to be replaced or recharged manually, which leads to high maintenance cost, serious environmental issues, and even safety hazards for some use cases, for example, wireless sensors in electrical power, and petroleum industries.
[0111] Most of the existing wireless communication devices are powered by batteries that need to be replaced or recharged manually. The automation and digitization of various industries opens numerous new markets requiring new IoT technologies of supporting batteryless devices with no energy storage capability or devices with energy storage that do not need to be replaced or recharged manually.
[0112] An example type of application is asset identification, which presently has to resort mainly to barcodes and RFID in most industries. The main advantage of these two technologies is the ultra-low complexity and small form factor of the tags. However, the limited reading range of a few meters usually requires handheld scanning which leads to labor intensive and time-consuming operations, or RFID portals / gates which leads to costly deployments. Moreover, the lack of interference management scheme results in severe interference between RFID readers and capacity problems, especially in case of dense deployment. It is hard to support a large-scale network with seamless coverage for RFID.
[0113] Hereinafter, technical features related to IoT technology are described. TS 38.300 V18.00 may be referred.
[0114] FIG. 8 shows an example of Support of Ambient IoT.
[0115] A-IoT radio interface provides the communication between A-IoT device(s) and A-IoT reader, as shown in FIG. 8. the A-IoT reader is a gNB-reader. A-IoT radio interface can support both inventory procedure and command procedure. An A-IoT device monitors the R2D message as long as it has sufficient energy.
[0116] The NG-RAN overall architecture is applicable for Ambient IoT along the following adaptations and additions:
[0117] - For the sake of supporting the provision of A-IoT services, the involved gNBs are enabled to support A-IoT, specifically, the gNB supports communication with A-IoT devices by means of A-IoT radio.
[0118] - A gNB may or may not only support communication with A-IoT devices by means of A-IoT radio.
[0119] - A gNB serves one or multiple readers.
[0120] - A gNB is aware of the mapping relationship between A-IoT Areas and readers by means of OAM configuration.
[0121] - An A-IoT Area may include readers belonging to the same or different gNB.
[0122] - One reader only belongs to one gNB.
[0123] - One reader can be mapped to one or multiple A-IoT Areas.
[0124] - the A-IoT CN node which the gNB connects to is either the AIOTF (in case of direct connectivity with the AIOTF) or the AMF (in case of indirect connectivity with the AIOTF). A gNB is aware of direct connectivity with the AIOTF via OAM.
[0125] A deployment with both direct connectivity and indirect connectivity is not expected.
[0126] - A-IoT specific information is transported between the gNB and the A-IoT CN node via the NG-C interface, the protocol stack in section 4.3.1.2 applies. In case of indirect connectivity with the AIOTF, A-IoT specific information is transferred transparently via the AMF.
[0127] - In this version of the specification, no A-IoT specific communication takes place between gNBs.
[0128] - In this version of the specification, split gNB architecture is not supported.
[0129] The AIOTF may request the gNB to perform an A-IoT operation within a specific area (requested service area). The requested service area may be indicated by means of a list of A-IoT Areas and / or a list of readers. The A-IoT Area is represented by an A-IoT Area ID.
[0130] The AIOTF is aware of the area within which the gNB supports provision of A-IoT services by means of OAM configuration. This area may be represented as A-IoT Areas and / or the readers supported by the gNB.
[0131] The AIOTF may also be aware of the reader's location by means of OAM configuration.
[0132] The AIOTF is aware of the mapping relationship among gNBs, readers and A-IoT areas by means of OAM configuration, as needed.
[0133] FIG. 9 shows an example of Radio Protocol Architecture for A-IoT Communication.
[0134] The AS protocol stack for A-IoT radio interface contains A-IoT MAC layer and A-IoT physical layer as shown in Figure 16.23.3-1. The AS layer control information and data are handled by A-IoT MAC layer and A-IoT physical layer. For A-IoT radio interface, there is no differentiation between the control plane and the user plane.
[0135] The main services and functions of A-IoT MAC layer include:
[0136] - Paging;
[0137] - Access;
[0138] - Transfer of upper layer data;
[0139] - Construct MAC PDUs to be mapped onto D2R transport blocks and delivered to the physical layer;
[0140] - MAC padding;
[0141] - D2R segmentation;
[0142] - Process MAC PDUs from R2D transport blocks delivered from the physical layer;
[0143] - Failure detection.
[0144] A-IoT Paging
[0145] A-IoT paging allows the A-IoT reader to trigger one, multiple or all A-IoT device(s) to perform A-IoT CBRA or A-IoT CFA. The A-IoT paging message is transmitted on PRDCH. The A-IoT paging message may include zero or one paging identifier, i.e., AIoT Device Permanent Identifier or Filtering Information. If a paging identifier is included, the A-IoT paging message may 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 also provides configuration for A-IoT access procedure.
[0146] FIGS. 10 and 11 show examples of A-IoT Access Procedure.
[0147] Both A-IoT CBRA procedure and A-IoT CFA procedure are supported for A-IoT access. The A-IoT device initiates either A-IoT CBRA or A-IoT CFA based on an explicit indication in the A-IoT paging message, if the device is paged.
[0148] For CBRA, the A-IoT device randomly selects one access occasion among access occasions configured in A-IoT paging message. The A-IoT device may then monitor the Access Trigger message(s) to determine the start of the selected access occasion and transmits the A-IoT MSG1 (i.e. the Access Random ID message) on this access occasion. The start of the first set of A-IoT MSG1 resources is indicated by A-IoT Paging message directly instead of the Access Trigger message. After A-IoT MSG1 transmission, the device monitors A-IoT MSG2 (i.e. the Random ID Response message) from the A-IoT reader for contention resolution until it has received the configured number of Access Trigger messages or subsequent A-IoT Paging message (i.e., the device does not process the A-IoT MSG2 received after that). Upon successful reception of A-IoT MSG2 which contains the matched frequency index (if present) as used and same random ID as transmitted in A-IoT MSG1, the A-IoT device considers the contention resolution as successful as shown in FIG. 10. Otherwise, the A-IoT device considers the contention resolution as failed. If contention resolution is successful, the A-IoT device transmits the D2R Upper Layer Data Transfer message in the resource provided in A-IoT MSG2. If the A-IoT device considers the contention resolution as failed, the A-IoT device shall perform re-access if an A-IoT Paging message with the same transaction ID is received.
[0149] For CFA, the A-IoT device shall use the dedicated resource provided in A-IoT paging message to send the D2R Upper Layer Data Transfer message as shown in FIG. 11. The A-IoT device does not need to monitor the Access Trigger message.
[0150] For CBRA, the A-IoT reader is expected to transmit enough Access Trigger message(s) to provide a number of access occasions not less than that configured in the A-IoT Paging message, unless the A-IoT reader is about to transmit subsequent A-IoT Paging message with either the same transaction ID or a different transaction ID.
[0151] It has been discussed when a device receives a new service request while a procedure is ongoing. Two options may be considered:
[0152] - Option (a): ignore all new requests and R2D messages addressed to the device but not associated with the ongoing procedure
[0153] - Option (b): terminate the ongoing procedure and respond to the latest request
[0154] Option (b) may lead to a ping-pong problem at the device, particularly in scenarios with multiple readers in future releases. For example, if multiple readers trigger their procedures parallelly, the device may repeatedly restart the newly incoming procedure, being unable to complete any of the procedures and wasting energy. To address the issue in a multiple-reader scenario, option (b) may require coordination between the readers (e.g., the CN coordinates the readers to execute their procedures sequentially rather than in parallel).
[0155] However, in future releases, coordination among readers may be imperfect. For example, in topology 2, where UE-readers are deployed, if the UE-readers are mobile and move, the coordination among the UE-readers at a given moment may become imperfect after movement. For example, if two UE-readers with non-overlapping coverage areas are scheduled to trigger procedures simultaneously, the two UE-readers may subsequently and unexpectedly move into overlapping coverage areas, resulting in parallel transmission of paging and R2D messages. Additionally, temporary out-of-coverage situations for UE-readers may lead to similar issues, as a UE-reader that is temporarily out of coverage reader may not be able to participate in coordination. Considering the above discussion, reliance of option (b) on network coordination is prone to malfunction, and as a result, option (b) may not be forward compatible.
[0156] Option (a) may help prevent the ping-pong problem without relying on coordination. however, option (a) may have certain requirements. The device may need to identify an end of an ongoing procedure. Additionally, it is needed for the device to know which procedure each reader-to-device (R2D) message, including a paging message, is associated with. For the purpose, information, such as a transaction ID, may be included in the R2D messages. However, similar information may also be required for option (b) to handle unexpected parallel requests, and overhead related to the information may be common to both option (a) and option (b). Therefore, the option (a) may be considered for device behavior.
[0157] To support option (a), the device may need to be aware of an end of an ongoing procedure. Since a reader triggers and manages the A-IoT procedure, it may be reasonable for the reader to inform the device of the end of the ongoing procedure through a reader-to-device (R2D) message that includes a certain indication. However, if the device misses the indication (i.e., if it fails to receive the message), the device may remain unaware of whether the procedure has ended. The lack of awareness may prevent the device from responding to any new incoming triggers, even if the procedure has actually finished and there are no remaining transactions for the device to perform. Therefore, the device may need to be capable of determining the end of the procedure even if the device does not receive the indication. In the present disclosure, how the device may identify the end of the procedure without receiving an explicit indication may be demonstrated.
[0158] To address the problem described above, according to implementations of the present disclosure, the device may start and maintain a timer associated with an ongoing procedure based on reception of R2D messages. While the timer is running, the device may determine whether a received R2D message is related to the ongoing procedure and may respond to the R2D message or discard the R2D message accordingly. Upon expiration of the timer, the device may determine that the ongoing procedure has ended and may process subsequently received R2D messages as new procedure triggers. In addition, the device may determine the end of the ongoing procedure based on reception of an indication and may stop the timer accordingly.
[0159] The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals / messages / fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings.
[0160] An embodiment of the present disclosure related to a specific drawing described below may be combined with various embodiments of the present disclosure related to other drawings, and some descriptions, functions, procedures, proposals, methods and / or operations of the embodiment may be omitted.
[0161] FIG. 12 shows an example of a method performed by a wireless device to which implementations of the present disclosure are applied.
[0162] In step S1200, the method comprises receiving a first Reader-to-Device (R2D) message related to a first procedure.
[0163] In step S1201, the method comprises starting a timer related to the first procedure. while the timer is running: the method comprises i) receiving a subsequent R2D message related to the first procedure, ii) responding to the subsequent R2D message, iii) restarting the timer, iv) receiving a second R2D message related to a second procedure, and v) discarding the second R2D message.
[0164] In some implementations, the first R2D message may be at least one of (i) an initial trigger message, (ii) a subsequent trigger message, (iii) an access occasion trigger message, (iv) a random ID response message, (v) a Negative Acknowledgement (NACK) feedback message, (vi) a R2D upper layer data transfer message, or (vii) another message transmitted from a reader to the wireless device.
[0165] In some implementations, it may be determined whether the subsequent R2D message is related to at least one of (i) the wireless device, (ii) the timer, or (iii) the first procedure.
[0166] In some implementations, it may be determined whether the subsequent R2D message is related to the first procedure based on an Identifier (ID). the ID may be related to at least one of (i) transaction ID, (ii) paging ID, (iii) reader ID, (iv) Application Service (AS) ID, (v) temporary ID.
[0167] In some implementations, it may be determined that the subsequent R2D message is related to the first procedure based on an ID included in the subsequent R2D message being matched with a previously received ID.
[0168] In some implementations, a duration of the timer may be at least one of: (i) indicated based on the first R2D message, (ii) preconfigured in the wireless device, (iii) provided by a lower layer, or (iv) determined based on a capability of the wireless device.
[0169] In some implementations, restarting the timer may comprise resetting a remaining time of the timer to the duration of the timer.
[0170] In some implementations, the method may further comprise determining that the first procedure has ended upon expiration of the timer.
[0171] In some implementations, the method may further comprise releasing an AS ID related to the wireless device based on determination that the first procedure has ended.
[0172] In some implementations, the method may further comprise receiving a third R2D message after the expiration of the timer. the method may further comprise responding to the third R2D message regardless of whether the third R2D message is related to the first procedure.
[0173] In some implementations, the method may further comprise receiving information related to an end of the first procedure. the method may further comprise determining that the first procedure has ended based on the information.
[0174] In some implementations, the method may further comprise stopping the timer based on the information.
[0175] In some implementations, the information may be related to at least one of (i) a number of access occasions field in A-IoT paging message to zero, (ii) combination of specific field values or other information in A-IoT paging message or other R2D message.
[0176] In some implementations, the method may further comprise releasing an AS ID related to the wireless device based on receiving the information.
[0177] In some implementations, the method may further comprise receiving a paging message targeting the wireless device or triggering a contention-free random access (CFRA) for the wireless device while the timer is running. the paging message may be at least one of (i) a paging message designated to the wireless device, or (ii) a paging message triggering contention-free random access (CFRA) targeting the wireless device. the method may further comprise responding to the paging message.
[0178] In some implementations, responding to the paging message may comprise terminating the timer.
[0179] In some implementations, responding to the paging message may comprise pausing the timer, and restarting the timer after responding to the paging message.
[0180] Furthermore, the wireless device may be implemented by the first wireless device 100 shown in FIG. 2, and / or the UE 100 shown in FIG. 3.
[0181] More specifically, the wireless device comprises at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions. Operations performed based on the instructions being executed by the at least one processor are as follows.
[0182] The wireless device receives a first Reader-to-Device (R2D) message related to a first procedure.
[0183] The wireless device starts a timer related to the first procedure.
[0184] while the timer is running: the wireless device i) receives a subsequent R2D message related to the first procedure, ii) responds to the subsequent R2D message, iii) restarts the timer, iv) receives a second R2D message related to a second procedure, and v) discards the second R2D message.
[0185] In some implementations, the first R2D message may be at least one of (i) an initial trigger message, (ii) a subsequent trigger message, (iii) an access occasion trigger message, (iv) a random ID response message, (v) a Negative Acknowledgement (NACK) feedback message, (vi) a R2D upper layer data transfer message, or (vii) another message transmitted from a reader to the wireless device.
[0186] In some implementations, it may be determined whether the subsequent R2D message is related to at least one of (i) the wireless device, (ii) the timer, or (iii) the first procedure.
[0187] In some implementations, it may be determined whether the subsequent R2D message is related to the first procedure based on an Identifier (ID). the ID may be related to at least one of (i) transaction ID, (ii) paging ID, (iii) reader ID, (iv) Application Service (AS) ID, (v) temporary ID.
[0188] In some implementations, it may be determined that the subsequent R2D message is related to the first procedure based on an ID included in the subsequent R2D message being matched with a previously received ID.
[0189] In some implementations, a duration of the timer may be at least one of: (i) indicated based on the first R2D message, (ii) preconfigured in the wireless device, (iii) provided by a lower layer, or (iv) determined based on a capability of the wireless device.
[0190] In some implementations, restarting the timer may comprise resetting a remaining time of the timer to the duration of the timer.
[0191] In some implementations, the method may further comprise determining that the first procedure has ended upon expiration of the timer.
[0192] In some implementations, the method may further comprise releasing an AS ID related to the wireless device based on determination that the first procedure has ended.
[0193] In some implementations, the method may further comprise receiving a third R2D message after the expiration of the timer. the method may further comprise responding to the third R2D message regardless of whether the third R2D message is related to the first procedure.
[0194] In some implementations, the method may further comprise receiving information related to an end of the first procedure. the method may further comprise determining that the first procedure has ended based on the information.
[0195] In some implementations, the method may further comprise stopping the timer based on the information.
[0196] In some implementations, the information may be related to at least one of (i) a number of access occasions field in A-IoT paging message to zero, (ii) combination of specific field values or other information in A-IoT paging message or other R2D message.
[0197] In some implementations, the method may further comprise releasing an AS ID related to the wireless device based on receiving the information.
[0198] In some implementations, the method may further comprise receiving a paging message targeting the wireless device or triggering a contention-free random access (CFRA) for the wireless device while the timer is running. the paging message may be at least one of (i) a paging message designated to the wireless device, or (ii) a paging message triggering contention-free random access (CFRA) targeting the wireless device. the method may further comprise responding to the paging message.
[0199] In some implementations, responding to the paging message may comprise terminating the timer.
[0200] In some implementations, responding to the paging message may comprise pausing the timer, and restarting the timer after responding to the paging message.
[0201] Furthermore, the method described above in FIG. 12 may be performed by control of a processing apparatus. The processing apparatus may be implemented by the processor 102 included in the first wireless device 100 shown in FIG. 2 and / or the processor 102 included in the UE 100 shown in FIG. 3.
[0202] More specifically, the processing apparatus comprises at least one processor that is integrated with a wireless device, and at least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform the method described in FIG. 12.
[0203] Furthermore, the method described above in FIG. 12 may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2.
[0204] The technical features of the present disclosure may be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.
[0205] Some example of storage medium may be coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For other example, the processor and the storage medium may reside as discrete components.
[0206] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.
[0207] For example, non-transitory computer-readable media may include RAM such as Synchronous DRAM (SDRAM), ROM, Non-Volatile RAM (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.
[0208] In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.
[0209] More specifically, a non-transitory Computer-Readable Medium (CRM) stores instructions that, based on being executed by at least one processor, perform the method described in FIG. 12.
[0210] FIG. 13 shows an example of a method performed by a reader to which implementations of the present disclosure are applied.
[0211] In step S1300, the method comprises transmitting to a wireless device a first R2D message related to a first procedure. a timer related to the first procedure is started, and based on the timer being running, i) transmitting to the wireless device a subsequent R2D message related to the first procedure, ii) the subsequent R2D message is responded, iii) the timer is restarted, iv) transmitting to the wireless device a second R2D message related to a second procedure, and v) the second R2D message is discarded.
[0212] Furthermore, the reader may be implemented by the second wireless device 200 shown in FIG. 2.
[0213] More specifically, the reader comprises at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions. Operations performed based on the instructions being executed by the at least one processor are as follows.
[0214] The reader transmits, to a wireless device, first information related to a paging status in a current time period.
[0215] a timer related to the first procedure is started, and based on the timer being running, i) transmitting to the wireless device a subsequent R2D message related to the first procedure, ii) the subsequent R2D message is responded, iii) the timer is restarted, iv) transmitting to the wireless device a second R2D message related to a second procedure, and v) the second R2D message is discarded.
[0216] Hereinafter, various aspects for determining whether to determine whether a subsequent R2D message is related to a first procedure are described according to implementations of the present disclosure.
[0217] According to the present disclosure, the wireless device may configure, set, or start a timer upon receiving an R2D message that is associated with the procedure triggered and managed by the sender of the R2D message (i.e., the reader).
[0218] (1) R2D messages
[0219] - the R2D message may be an initial trigger message (i.e., paging message) transmitted from a reader to initiate an A-IoT procedure.
[0220] - the R2D message may be a subsequent trigger message (i.e., subsequent paging message) sent from the reader to initiate a re-access procedure.
[0221] - the R2D message may be an access occasion trigger message, which indicates a start of a Msg1 resource for random access procedure.
[0222] - the R2D message may be a Random ID Response Message (i.e., the Msg2 in random access procedure).
[0223] - the R2D message may be a NACK feedback message
[0224] - the R2D message may be an R2D upper layer data transfer message, or a command message.
[0225] - the R2D message may be another message transmitted from a reader to the device.
[0226] (2) Start of the timer
[0227] - The device may start or restart the timer based on reception of an initial triggering message (A-IoT paging message), if the initial triggering message is related to the device.
[0228] - The device may start the timer based on the reception of the initial triggering message (A-IoT paging message) even if the initial triggering message is not related to the device.
[0229] - The device may start or restart the timer based on reception of other R2D messages if the R2D messages are related to the device. The device may start the timer based on the reception of other R2D messages even if other R2D messages are not related to the device.
[0230] (3) Association between device, timer, and the ongoing procedure
[0231] - The device may determine whether an R2D message is related to the device, the timer, or an ongoing procedure based on an identifier included in the R2D message. The identifier may comprise a transaction ID. For example, the device may determine a relationship by comparing the transaction ID included in the R2D message with a previously received transaction ID. When the transaction ID included in the R2D message and the previously received transaction ID match, the device may determine that the R2D message is related to the device, the timer, or the ongoing procedure.
[0232] - The identifier may comprise a paging ID. For example, the device may determine a relationship by comparing the paging ID included in the R2D message with a previously received paging ID. the paging ID may correspond to a single device ID, a group of device IDs, or an identifier targeting all devices. When the paging ID included in the R2D message and the previously received paging ID match, the device may determine that the R2D message is related to the device, the timer, or the ongoing procedure.
[0233] - The identifier may comprise a reader ID representing an identity of a reader transmitting the R2D message. For example, the device may determine a relationship between the R2D message and at least one of the device, the timer, or the ongoing procedure by comparing the reader ID included in the R2D message with a previously received reader ID. When the reader ID included in the R2D message and the previously received reader ID match, the device may determine that the R2D message is related to the device, the timer, or the ongoing procedure.
[0234] - The identifier may comprise an AS ID included in the R2D message, if present. For example, the device may determine a relationship between the R2D message and at least one of the device, the timer, or the ongoing procedure by comparing the AS ID included in the R2D message with a previously received AS ID. When the AS ID included in the R2D message and the previously received AS ID match, the device may determine that the R2D message is related to the device, the timer, or the ongoing procedure.
[0235] - The identifier may comprise a temporary ID. For example, the device may determine a relationship between the R2D message and at least one of the device, the timer, or the ongoing procedure by comparing the temporary ID included in the R2D message with a previously received temporary ID. When the temporary ID included in the R2D message and the previously received temporary ID match, the device may determine that the R2D message is related to the device, the timer, or the ongoing procedure.
[0236] - The device may determine a relationship between the R2D message and at least one of the device, the timer, or the ongoing procedure based on at least one piece of information or a combination of two or more pieces of information, including the identifiers described above or other identifiers. For example, the device may determine a relationship by comparing one or more identifiers included in the R2D message with one or more identifiers stored in the device. When at least one identifier included in the R2D message matches at least one stored identifier, the device may determine that the R2D message is related to the device, the timer, or the ongoing procedure.
[0237] (4) Timer duration
[0238] 1) The timer duration may be provided via a R2D message that triggers to start the timer.
[0239] - a specific duration may be provided.
[0240] - an indication or information for the device to determine the duration may be provided.
[0241] 2) The timer duration may be preconfigured in the device.
[0242] - information, an indication, or a field for the device to derive the duration based on the pre-configuration may be provided via R2D messages.
[0243] 3) The device may determine the timer duration based on certain requirements (e.g., the timer duration may be derived from requirement values defined by RAN1 or RAN4).
[0244] 4) The timer duration may be provided by a lower layer.
[0245] - A specific duration may be provided.
[0246] - An indication for the device to determine the duration may be provided.
[0247] 5) The device may derive an appropriate timer duration value based on the abovementioned indication or information, or the pre-configuration.
[0248] 6) The device may derive an appropriate timer duration value based on its capability along with the abovementioned indication or information, or the pre-configuration.
[0249] 7) For example, if a device can run a long-term timer, then the device may start the timer only when receiving certain R2D messages (e.g., (subsequent) paging messages), with a long duration (e.g., long enough to include the two certain consecutive R2D messages).
[0250] 8) For example, if a device cannot run a long-term timer, then the device may start the timer when receiving every R2D messages, with a short duration.
[0251] For example, if an A-IoT device that is running the timer receives an R2D message before the timer expires, and if the R2D message is associated with the procedure related to the timer (i.e., the ongoing procedure), the device may (re)configure, (re)set, or (re)start the timer, thereby increasing or resetting / initializing the remaining time until the timer expires.
[0252] (1) R2D messages
[0253] - the R2D message may be an initial trigger message (paging message) sent from a reader to initiate an A-IoT procedure.
[0254] - the R2D message may be a subsequent trigger message (subsequent paging message) sent from a reader to initiate a re-access procedure.
[0255] - the R2D message may be an access occasion trigger message, which indicates a start of a Msg1 resource for random access procedure.
[0256] - the R2D message may be a Random ID Response Message (i.e., the Msg2 in random access procedure).
[0257] - the R2D message may be a NACK feedback message
[0258] - the R2D message may be an R2D Upper Layer Data Transfer message, or a command message.
[0259] - the R2D message may be another message sent by a reader to the device.
[0260] (2) Timer duration
[0261] 1) The timer duration may be provided via a R2D message that triggers to start the timer
[0262] - a specific duration may be provided.
[0263] - an indication or information for the device to determine the duration may be provided.
[0264] 2) The timer duration may be preconfigured to the device.
[0265] - information, an indication or a field for the device to derive the duration based on the pre-configuration may be provided via R2D messages.
[0266] 3) The device may determine the timer duration based on certain requirements (e.g., the timer duration may be derived from the RAN1 or RAN4 requirement values).
[0267] 4) The timer duration may be provided by a lower layer.
[0268] - a specific duration may be provided.
[0269] - an indication for the device to determine the duration may be provided.
[0270] 5) The device may derive the appropriate timer duration value based on the abovementioned indication or information, or the pre-configuration.
[0271] 6) The device may derive an appropriate timer duration value based on its capability along with the abovementioned indication or information, or the pre-configuration.
[0272] 7) For example, if a device can run a long-term timer, then the device may start the timer only when receiving certain R2D messages (e.g., (subsequent) paging messages), with a long duration (e.g., long enough to include the two certain consecutive R2D messages).
[0273] 8) For example, if a device cannot run a long-term timer, then the device may start the timer when receiving every R2D messages, with a short duration.
[0274] For example, if the timer is running (i.e., before the timer expires), meaning the ongoing procedure is not yet determined as complete, an A-IoT device may discard the R2D messages associated with procedures different from the ongoing procedure, which is associated with the R2D message that configured, set, or started the timer, or which is associated with the timer (i.e., not responding to the different procedures). However, the device may respond to the messages associated with the ongoing procedure, which is associated with the R2D message that configured, set, or started the timer, or which is associated with the timer.
[0275] An A-IoT device may determine that the ongoing procedure associated with the R2D message that configured, set, or started the timer, or which is associated with the timer, has ended when the timer expires.
[0276] - Upon the expiration of the timer and determination that the procedure has ended, the device ID may release AS ID allocated to the device and associated with the procedure, if any.
[0277] Once the timer expires, an A-IoT device may determine that the ongoing procedure associated with the timer (or associated with the R2D message that configured, set, or started the timer) has ended. For example, if another R2D message is received thereafter, the A-IoT device may respond to the R2D message and perform subsequent operations related to the newly received R2D message, such as performing random access procedure, even if the R2D message is not associated with the previously ended procedure.
[0278] Once an A-IoT device receives the indication of an end of the ongoing procedure (e.g., through an R2D message), the device may determine that the procedure associated with the R2D message has ended. For example, if the device is running the timer for the ongoing procedure, and receives the indication of an end of the ongoing procedure through an R2D message associated with the R2D message that configured, set, or started the timer, or associated with the timer, the device may stop the timer and determine that the procedure associated with the R2D message has ended.
[0279] - Once an A-IoT device receives an indication of an end of an ongoing procedure (e.g., through an R2D message) before the timer expires, the device may determine that the procedure associated with the timer has ended and may stop the timer.
[0280] - The reader may transmit the R2D message indicating an end of an ongoing procedure if the necessary operations for the procedure have been completed.
[0281] - The reader may transmit the R2D message to terminate the ongoing procedure early, even if the required operations have not been completed (e.g., to initiate a new procedure).
[0282] - the indication of an end of an ongoing procedure may be provided by setting a number of access occasions field in the A-IoT paging message to zero. For example, if an A-IoT device receives A-IoT paging with the number of access occasions field of zero, the device may determine that the associated procedure has ended.
[0283] - the indication of an end of an ongoing procedure may be conveyed through a combination of specific field values and / or other indications in an A-IoT paging message or another R2D message.
[0284] - Upon expiration of the timer and determination that the procedure has ended, the device may release an AS ID allocated to the device, if any.
[0285] Once an A-IoT device receives a paging message designated to the device, or a paging message triggering contention-free random access (CFRA) for the device (which may not include a transaction ID), the device may respond to the paging message.
[0286] - The device may receive a designated paging message or the paging message triggering CFRA targeting for the device.
[0287] - Upon receiving the paging message, the device may terminate the timer and respond to the paging message.
[0288] - Upon receiving the paging message, the device may pause the timer and respond to the paging message, and then restart the timer.
[0289] - Upon receiving the paging message, the device may respond to the paging message while the timer is running.
[0290] In the disclosure, the reader may be a user equipment (UE) or a network, e.g., eNB or gNB.
[0291] In the disclosure, the device may be an A-IoT device or a user equipment (UE).
[0292] FIG. 14 shows an example in which a device performs a timer-based determination of procedure completion to which implementations of the present disclosure are applied.
[0293] FIG. 14 shows the disclosure involving one device and two readers.
[0294] The device may receive an initial paging message from reader 1 and start a timer associated with a procedure for reader 1 while responding to the paging message. Upon receiving Msg2 from the reader 1, the device may restart the timer indicating that the procedure is still ongoing.
[0295] Next, reader 2 may transmit a paging message to initiate a separate procedure. However, since the device is already engaged in the ongoing procedure with the running timer, the device may discard the paging message from the reader 2. Subsequently, the device may receive a command message from the reader 1 and restart the timer, indicating continuation of the ongoing procedure.
[0296] After completing the procedure, the reader 1 may send an end-of-procedure indication. however, the device may fail to receive the indication. Despite this, the device may conclude that the ongoing procedure has ended when the timer expires
[0297] The present disclosure may have various advantageous effects.
[0298] For example, it may be ensured that the device can recognize the end of the ongoing procedure even if it misses the end of procedure indication. As a result, the device will be aware of the procedure's completion and can proceed with a new service request procedure. Or, it could be prevented unnecessary energy consumption by the device, such as avoiding ping-pong effects. This addresses the issue where the device fails to complete the procedure for a service request and continuously restarts, leading to wasted energy and resources.
[0299] For example, the device can reliably recognize the end of an ongoing procedure even when an explicit end-of-procedure indication is not successfully received from a reader, thereby improving robustness of procedure handling.
[0300] For example, by enabling the device to determine the completion of the procedure based on a timer mechanism, the device can avoid remaining in a state of continuously ignoring valid subsequent service requests, thereby improving responsiveness to new requests.
[0301] For example, the proposed mechanism can prevent repeated termination and restarting of procedures in multi-reader scenarios, thereby avoiding ping-pong effects and reducing unnecessary energy consumption.
[0302] For example, by reducing unnecessary procedure restarts and inefficient processing, the device can operate more efficiently in terms of both resource utilization and power consumption.
[0303] For example, the overall system performance can be improved by ensuring stable procedure completion and efficient handling of subsequent service requests, particularly in environments where coordination among multiple readers is imperfect.
[0304] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.
[0305] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.
Claims
1.A method comprising:receiving, by a wireless device, a first Reader-to-Device (R2D) message related to a first procedure;starting, by the wireless device, a timer related to the first procedure;while the timer is running:i) receiving a subsequent R2D message related to the first procedure;ii) responding to the subsequent R2D message;iii) restarting the timer;iv) receiving a second R2D message related to a second procedure; andv) discarding the second R2D message.2.The method of claim 1, wherein the first R2D message is at least one of (i) an initial trigger message, (ii) a subsequent trigger message, (iii) an access occasion trigger message, (iv) a random ID response message, (v) a Negative Acknowledgement (NACK) feedback message, (vi) a R2D upper layer data transfer message, or (vii) another message transmitted from a reader to the wireless device.3.The method of claim 1, wherein it is determined whether the subsequent R2D message is related to the first procedure based on an Identifier (ID), andwherein the ID is related to at least one of (i) transaction ID, (ii) paging ID, (iii) reader ID, (iv) Application Service (AS) ID, (v) temporary ID.4.The method of claim 1, wherein it is determined that the subsequent R2D message is related to the first procedure based on an ID included in the subsequent R2D message being matched with a previously received ID.5.The method of claim 1, wherein a duration of the timer is at least one of: (i) indicated based on the first R2D message, (ii) preconfigured in the wireless device, (iii) provided by a lower layer, or (iv) determined based on a capability of the wireless device.6.The method of claim 5, wherein restarting the timer comprises resetting a remaining time of the timer to the duration of the timer.7.The method of claim 1, further comprising:determining, by the wireless device, that the first procedure has ended upon expiration of the timer.8.The method of claim 7, further comprising:releasing, by the wireless device, an AS ID related to the wireless device based on determination that the first procedure has ended.9.The method of claim 7, further comprising:receiving, by the wireless device, a third R2D message after the expiration of the timer; andresponding, by the wireless device, to the third R2D message regardless of whether the third R2D message is related to the first procedure.10.The method of claim 1, further comprising:receiving, by the wireless device, information related to an end of the first procedure;determining, by the wireless device, that the first procedure has ended based on the information.11.The method of claim 10, further comprising:stopping, by the wireless device, the timer based on the information.12.The method of claim 9, wherein the information is related to at least one of (i) a number of access occasions field in A-IoT paging message to zero, (ii) combination of specific field values or other information in A-IoT paging message or other R2D message.13.The method of claim 12, further comprising:releasing, by the wireless device, an AS ID related to the wireless device based on receiving the information.14.The method of claim 1, further comprising:receiving, by the wireless device, a paging message targeting the wireless device or triggering a contention-free random access (CFRA) for the wireless device while the timer is running,wherein the paging message is at least one of (i) a paging message designated to the wireless device, or (ii) a paging message triggering contention-free random access (CFRA) targeting the wireless device; andresponding, by the wireless device, to the paging message.15.The method of claim 14, wherein responding to the paging message comprises terminating the timer.16.The method of claim 14, wherein responding to the paging message comprises pausing the timer, and restarting the timer after responding to the paging message.17.A wireless device comprising:at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving a first R2D message related to a first procedure;starting a timer related to the first procedure;while the timer is running:i) receiving a subsequent R2D message related to the first procedure;ii) responding to the subsequent R2D message;iii) restarting the timer;iv) receiving a second R2D message related to a second procedure; andv) discarding the second R2D message.18.A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a wireless device, cause the wireless device to perform operations, the operations comprising:receiving a first R2D message related to a first procedure;starting a timer related to the first procedure;while the timer is running:i) receiving a subsequent R2D message related to the first procedure;ii) responding to the subsequent R2D message;iii) restarting the timer;iv) receiving a second R2D message related to a second procedure; andv) discarding the second R2D message.19.A method comprising:transmitting, by a reader to a wireless device, a first R2D message related to a first procedure;wherein a timer related to the first procedure is started, andwherein, based on the timer being running,i) transmitting, by the reader to the wireless device, a subsequent R2D message related to the first procedure;ii) the subsequent R2D message is responded;iii) the timer is restarted;iv) transmitting, by the reader to the wireless device, a second R2D message related to a second procedure; andv) the second R2D message is discarded.20.A reader comprising:at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:transmitting, to a wireless device, a first R2D message related to a first procedure;wherein a timer related to the first procedure is started, andwherein, based on the timer being running,i) transmitting, to the wireless device, a subsequent R2D message related to the first procedure;ii) the subsequent R2D message is responded;iii) the timer is restarted;iv) transmitting, to the wireless device, a second R2D message related to a second procedure; andv) the second R2D message is discarded.
