Method and device for d2r transmission for random access

The method addresses inefficiencies in 6G A-IoT random access by defining clear processing criteria for reserved message types, enhancing synchronization and resource allocation, and ensuring reliable device operations.

WO2026235344A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005853
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In 6G mobile communication systems, the unclear handling of reserved or invalid message type values in the random access procedure for Ambient IoT (A-IoT) devices leads to unnecessary uplink transmissions, synchronization issues, inconsistent resource allocation, and uncertainty in device operations, resulting in inefficiencies and malfunctions.

Method used

A method is proposed to handle reserved or invalid message types by defining clear processing criteria, including count-down behaviors, resource configuration, and mapping relationships, ensuring consistent device operations and efficient resource utilization.

Benefits of technology

This approach reduces unnecessary transmissions, enhances synchronization, improves resource allocation efficiency, and ensures reliable device operations by providing clear criteria for handling reserved or invalid message types, thus stabilizing the random access procedure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005853_12112026_PF_FP_ABST
    Figure KR2026005853_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving a reader-to-device (R2D) message from a reader; and performing device-to-reader (D2R) transmission to the reader on the basis of an access occasion. On the basis that a field of the R2D message indicates a defined value, a count-down behavior of a value related to selection of the access occasion is performed. On the basis that the field of the R2D message indicates a reserved value, the R2D message is discarded.
Need to check novelty before this filing date? Find Prior Art

Description

D2R transmission method and device for random access

[0001] This specification relates to a D2R transmission method and apparatus for random access.

[0002] The 5G mobile communication system is a successor technology to LTE (Long Term Evolution) and is a new clean-slate type of mobile communication system characterized by high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging from low-frequency bands below 1 GHz to intermediate frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. Based on the underlying technology of 5G mobile communication, 6G mobile communication systems are being developed.

[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0004] Meanwhile, in Ambient IoT (A-IoT) communication, the device transmits Msg1 (Access Random ID message) and / or Msg3 (D2R Upper Layer Data Transfer message) in a random access procedure.

[0005] According to the prior art, when a message type field included in a message that triggers a contention-based random access (CBRA) procedure in A-IoT indicates a reserved value or an invalid value, the behavior of a device receiving such a value is not clearly defined. As a result, the device may mistake the message for a valid message and perform the random access procedure, which may lead to unnecessary uplink transmission. The purpose of this specification is to propose a method to solve the above-mentioned problems.

[0006] According to the prior art, due to the absence of clear processing criteria for message type values ​​indicating reserved or invalid values, it is unclear whether a device should perform a count-down behavior, which may lead to reduced synchronization and procedural consistency of random access procedures. Another objective of this specification is to propose a method for controlling the count-down behavior of a device to solve the above-mentioned problems.

[0007] According to the prior art, a resource configuration method based on the time offset and transmission length of D2R transmission resources triggered by R2D transmission is not clearly defined, which may lead to inconsistencies in resource allocation interpretation between the device and the reader, resulting in transmission collisions or inefficient resource usage. Another objective of this specification is to propose a transmission resource configuration method to solve the above-mentioned problems.

[0008] According to the prior art, when D2R transmissions are repeatedly triggered by multiple R2D transmissions in the same inventory round, the priority or application criteria of parameters applied to each transmission are unclear, which may increase uncertainty in device operation. Another objective of this specification is to propose a method to solve the above-mentioned problems.

[0009] According to the prior art, when multiple Msg2 responses exist, the mapping relationship between each Msg2 and Msg1 transmission resource is not clearly defined, which may result in a problem where the device receives unnecessary Msg2s or fails to accurately determine whether it is responding. Another objective of the present specification is to propose a response setting method to solve the above-mentioned problems.

[0010] According to the prior art, the scheduling relationship and timing conditions between Msg2 and Msg3 are unclear, which may lead to problems where the device misjudges whether to retransmit or fails to accurately determine whether the random connection procedure has failed. Another objective of this specification is to propose a scheduling and timing control method to solve the above-mentioned problems.

[0011] The technical problems to be solved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this invention belongs from the description below.

[0012] To solve the aforementioned technical problem, a method according to one embodiment of the present specification includes the steps of receiving a reader-device message (R2D message) from a reader and performing a device-to-reader transmission (D2R transmission) to the reader based on an access occasion.

[0013] Based on the fact that the fields of the above R2D message represent defined values, a count-down behavior of the value related to the selection of the access opportunity is performed.

[0014] Based on the fact that the field of the above R2D message indicates a reserved value, the R2D message is discarded.

[0015] This prevents device malfunction and reduces unnecessary transmission when a specific field from the reader indicates a reserved value.

[0016] The above countdown operation may not be performed based on the fact that the field of the above R2D message represents the above reserved value.

[0017] The above field can represent an R2D message type.

[0018] The above R2D message may include a MAC protocol data unit (MAC PDU).

[0019] The above MAC PDU may include control information and other information other than the control information.

[0020] The above control information may have a first CRC added, and the above other information may have a second CRC added.

[0021] A device according to another embodiment of the present specification comprises one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions. The instructions are characterized by causing the device to perform all steps of any one of the methods based on execution by the one or more processors.

[0022] An apparatus according to another embodiment of the present specification comprises one or more memories and one or more processors connected to the one or more memories. The one or more memories are characterized by storing instructions that cause the apparatus to perform all steps of any one of the methods based on execution by the one or more processors.

[0023] A non-transitory computer-readable storage medium according to another embodiment of the present specification stores instructions. The instructions, executable by one or more processors, are characterized by causing a device to perform all steps of any one of the methods.

[0024] A method according to another embodiment of the present specification includes the steps of transmitting a reader-device message (R2D message) to a device and receiving a device-reader transmission (D2R transmission) from the device based on an access occasion.

[0025] Based on the fact that the fields of the above R2D message represent defined values, a count-down behavior of the value related to the selection of the access opportunity is performed.

[0026] Based on the fact that the field of the above R2D message indicates a reserved value, the above R2D message is discarded.

[0027] The above countdown operation may not be performed based on the fact that the field of the above R2D message represents the above reserved value.

[0028] The above field can represent an R2D message type.

[0029] The above R2D message may include a MAC protocol data unit (MAC PDU).

[0030] The above MAC PDU may include control information and other information other than the control information.

[0031] The above control information may have a first CRC added, and the above other information may have a second CRC added.

[0032] A reader according to another embodiment of the present specification comprises one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions. The instructions are characterized by causing the reader to perform all steps of any one of the methods based on execution by the one or more processors.

[0033] According to the prior art, the behavior of a device receiving a message type representing a reserved value or an invalid value is unclear, which may result in unnecessary uplink transmission. According to the embodiments of the present specification, there is an advantage in reducing unnecessary transmission and device malfunction by causing the device to ignore the message when the message type represents a reserved value or an invalid value.

[0034] According to the prior art, it is unclear whether a device performs a countdown operation based on a message type value, which may lead to reduced consistency in arbitrary connection procedures. According to the embodiments of this specification, there is an advantage in ensuring procedural consistency by distinguishing device operations based on a defined value and a reserved value.

[0035] According to the prior art, the D2R resource configuration method is unclear, which may lead to resource conflicts or inefficient resource usage. According to the embodiments of this specification, providing a time offset determination method based on transmission length has the advantage of improving the accuracy and efficiency of resource allocation.

[0036] According to the prior art, the consistency of device operation may be reduced because the criteria for applying parameters to transmissions repeated in the same inventory round are unclear. According to the embodiments of this specification, defining the priority of parameter application has the advantage of improving the predictability of device operation.

[0037] According to the prior art, the mapping between multiple Msg2 responses and Msg1 transmission resources is unclear, which may lead to unnecessary reception or misjudgment. According to the embodiments of this specification, providing clear mapping criteria has the advantage of improving reception efficiency and reducing malfunctions.

[0038] According to the prior art, errors in determining retransmission may occur because the scheduling and timing conditions between Msg2 and Msg3 are unclear. According to the embodiments of this specification, there is an advantage in improving the reliability of the random access procedure by providing clear timing conditions and scheduling criteria.

[0039] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below.

[0040] The drawings attached below are intended to aid in understanding the present disclosure and may provide embodiments of the present disclosure together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with one another to form new embodiments. Reference numerals in each drawing may denote structural elements.

[0041] Figure 1 is an example showing a topology of direct connection between a base station and an A-IoT device.

[0042] Figure 2 is an example showing a topology in which a base station and an A-IoT device are connected through an intermediate node.

[0043] Figure 3 is an example showing a topology supported by auxiliary nodes.

[0044] Figure 4 is another example showing a topology supported by auxiliary nodes.

[0045] Figure 5 is an example showing a topology of direct connection between a terminal and an A-IoT device.

[0046] Figure 6 shows an example of power consumption and device energy status according to the operating state of an energy harvesting-based device.

[0047] Figure 7 is an example showing a combination of Deployment scenario 1 and topology 1 with various CWs.

[0048] Figure 8 is an example showing a combination of Deployment scenario 2 and topology 2 with various CWs.

[0049] FIG. 9 is an example showing device type 1 according to an embodiment of the present specification.

[0050] FIG. 10 is an example showing a different device type 2a of the embodiments of the present specification.

[0051] FIG. 11 is an example showing a different device type 2b of the embodiments of the present specification.

[0052] Figure 12 is an example showing the entire AS procedure between an A-IoT device and a reader.

[0053] Figure 13 is an example illustrating the procedure for transmitting Msg2 resources via TDM.

[0054] Figure 14 is an example illustrating the allocation of time resources for a D2R transmission triggered by an R2D transmission.

[0055] FIG. 15 is an example showing scheduling methods of Msg2-Msg3 according to an embodiment of the present specification.

[0056] FIG. 16 is an example showing various transmission structures of control information and PRDCH / PDRCH according to an embodiment of the present specification.

[0057] FIG. 17 is an example showing the transmission structure of preamble / postamble and PRDCH / PDRCH according to an embodiment of the present specification.

[0058] FIG. 18 is an example showing various MAC payload structures according to embodiments of the present specification.

[0059] FIG. 19 is an example illustrating D2R transmission and midamble transmission according to an embodiment of the present specification.

[0060] FIG. 20 is a flowchart for explaining a method according to one embodiment of the present specification.

[0061] FIG. 21 is a flowchart illustrating a method according to another embodiment of the present specification.

[0062] FIG. 22 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0063] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0064] A slash ( / ) or a comma used in this specification 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."

[0065] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0066] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "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."

[0067] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0068] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0069] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0070] In this specification, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0071] In this specification, "set or defined" may be interpreted as being set or pre-configured to the device through pre-defined signaling (e.g., SIB, MAC, RRC) from a base station or network. In this specification, "set or defined" may be interpreted as being pre-configured to the device.

[0072] In this specification, user equipment (UE) may refer to portable devices, wireless devices, etc. In this specification, base station (BS) may refer to a radio access network (RAN) node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a portable device, a wireless device, etc.

[0073] In the following, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of the base station and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal and the receiver may be part of the base station. The base station may be referred to as the first communication device and the terminal as the second communication device. The base station (BS) may be replaced by terms such as fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), Access Point (AP), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device.

[0074] Ambient IoT (A-IoT)

[0075] Below, Ambient IoT (A-IoT) is explained.

[0076] A-IoT can be a new type of device or segment that operates solely on energy harvested from the surrounding environment. For example, A-IoT may refer to a new class of Internet of Things devices that operate by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy. Table 1 shows examples of use cases for A-IoT. Table 2 shows matters related to IoT communications discussed in the 3GPP RAN.

[0077]

[0078]

[0079] For example, active signal generation and / or backscattering may be one of the communication technologies considered to achieve low-power operation of A-IoT devices. For example, backscattering is a widely used technique in radio frequency identification (RFID) that can enable a device to communicate with a network by reflecting incident waves after modulating them with information to be transmitted. For example, the device may be powered by an incident RF signal or stored energy.

[0080] For example, A-IoT devices can be classified into various device types, such as passive, semi-passive, and active, depending on the energy storage and transmission signal generation methods. For example, a passive device does not have an energy storage device (e.g., a capacitor) and can communicate based on backscatter communication technology. For example, a semi-passive device has an energy storage device and can communicate using backscatter communication technology with the assistance of the energy storage device. For example, an active device has an energy storage device and can communicate by actively generating signals using active RF components and stored energy. For example, in this specification, the following three types of IoT devices may be considered. For example, device A may be a device without energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). For example, device B may be a device with energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). In this case, for example, the use of stored energy may include amplification of the reflected signal. For example, device C may be a device with energy storage and independent signal generation (e.g., a device with an active RF component for transmission).

[0081] For example, the following basic topologies may be considered to support A-IoT devices in indoor and outdoor scenarios. For example, basic topologies may include a direct connection between a base station and an A-IoT device, a connection between a base station, an intermediate node, and an A-IoT device, support for connection by an auxiliary node, and / or a connection between a terminal and an A-IoT device. The basic topologies proposed herein are merely examples, and the proposals in this specification may be extended and applied to other topologies.

[0082] FIG. 1 is an example illustrating a topology in which a base station and an A-IoT device are directly connected. Specifically, FIG. 1 illustrates a topology in which a base station and an A-IoT device are directly connected (e.g., Topology 1) according to one embodiment of the present specification. The embodiment of FIG. 1 may be combined with various embodiments of the present specification.

[0083] Referring to FIG. 1, an A-IoT device can communicate directly and bidirectionally with a base station. For example, communication between a base station and an A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel). In the embodiment of FIG. 1, the base station transmitting to the A-IoT device and the base station receiving from the A-IoT device may be different. For example, in the topology 1, a base station in a micro-cell environment and an A-IoT device can communicate directly with each other. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology.

[0084] FIG. 2 is an example illustrating a topology in which a base station and an A-IoT device are connected through an intermediate node. Specifically, FIG. 2 illustrates a topology (e.g., Topology 2) in which a base station and an A-IoT device are connected through an intermediate node, according to one embodiment of the present specification. The embodiment of FIG. 2 may be combined with various embodiments of the present specification.

[0085] Referring to FIG. 2, an A-IoT device can communicate bidirectionally with an intermediate node between the device and the base station. Here, for example, the intermediate node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc. For example, the intermediate node may transmit A-IoT data and / or signals between the base station and the A-IoT device. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel). In the embodiment of FIG. 2, the intermediate node transmitting to the A-IoT device and the intermediate node receiving from the A-IoT device may be different. For example, in the topology 2, an intermediate node may exist between the base station in a macro-cell environment and the A-IoT device. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology. For example, the intermediate node may be limited to a terminal, and the intermediate node may be located indoors.

[0086] Figure 3 is an example showing a topology supported by auxiliary nodes.

[0087] Figure 4 is another example showing a topology supported by auxiliary nodes.

[0088] Specifically, FIGS. 3 and 4 illustrate a topology (e.g., topology 3) supported by an auxiliary node according to one embodiment of the present specification. The embodiment of FIGS. 3 and 4 may be combined with various embodiments of the present specification.

[0089] Referring to FIG. 3, an auxiliary node may be supported for downlink reception. For example, an A-IoT device may transmit data / signals to a base station, and the A-IoT device may receive data / signals from an auxiliary node. Referring to FIG. 4, an auxiliary node may be supported for uplink transmission. For example, an A-IoT device may receive data / signals from a base station, and the A-IoT device may transmit data / signals to an auxiliary node. Here, for example, the auxiliary node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc.

[0090] FIG. 5 is an example illustrating a topology in which a terminal and an A-IoT device are directly connected. Specifically, FIG. 5 illustrates a topology in which a terminal and an A-IoT device are directly connected (e.g., topology 4) according to one embodiment of the present specification. The embodiment of FIG. 5 may be combined with various embodiments of the present specification.

[0091] Referring to FIG. 5, an A-IoT device can communicate bidirectionally with a terminal. For example, communication between the terminal and the A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel).

[0092] For example, transmission by an A-IoT device can be performed in the frequency division duplexing (FDD) spectrum (e.g., FDD UL spectrum).

[0093] Meanwhile, a study item titled "Study on solutions for Ambient IoT (Internet of Things) in NR" was approved in 3GPP NR release 19. Specifically, the study item is scheduled to proceed in 3GPP NR release 19 based on the following content.

[0094] This study aims to further evaluate Ambient IoT at the RAN WG level, a new 3GPP IoT technology suitable for deployment in 3GPP systems, which relies on ultra-low complexity devices with ultra-low power consumption for very low-level IoT applications. This study must provide a clear differentiation; that is, it must address use cases and scenarios that cannot be met based on existing 3GPP LPWA IoT technologies (e.g., NB-IoT with reduced peak Tx power).

[0095] General range

[0096] The definitions provided in TR 38.848 apply to this SI, and the following are exclusive general scopes.

[0097] A. The overall objective is to research a harmonized wireless interface design that minimizes differences when Ambient IoT is required to enable the following devices.

[0098] i. ~1μW peak power consumption, energy storage, initial sampling frequency offset (SFO) of up to 10X ppm, no DL or UL amplification in the device. The device's UL transmission is backscattered from the externally provided carrier wave.

[0099] ii. Peak power consumption ≤ several hundred μW1, energy storage, initial sampling frequency offset (SFO) of up to 10X ppm, and DL and / or UL amplification in the device. UL transmission in the device may be generated internally or backscattered from carrier waves provided externally.

[0100] -X is determined in WG.

[0101] -Coverage design target: Up to 10-50m distance with the device indoors according to TR 38.848: "...range where WG can sub-select".

[0102] - According to TR 38.848, for Topologies 1 and 2 (UEs acting as intermediate nodes under NW control), there is no RRC state, no mobility (i.e., no functions such as cell selection / reselection at least), no HARQ, and no ARQ.

[0103] Note 1: It should be understood that the WG has no duty to set a specific value for "≤ hundreds of μW", and that determining whether the proposed design and its power consumption meet the "≤ hundreds of μW" requirement is a matter for the WG to discuss.

[0104] B. Deployment scenarios with the following characteristics, referring to the table in Clause 4.2.2 of TR 38.848:

[0105] - Deployment Scenario 1 using Topology 1

[0106] Base Station and Coexistence Characteristics: Microcells, Co-sites

[0107] - Deployment Scenario 2 using a UE as an intermediate node under Topology 2 and network control

[0108] Base Station and Coexistence Characteristics: Macro Cells, Co-sites

[0109] The location of the intermediate node is indoors

[0110] C. FDD's FR1 License Spectrum.

[0111] D. In-band spectrum distribution for NR, guard band for LTE / NR, standalone band(s)

[0112] E. Traffic types DO-DTT, DT focused on rUC1 (Indoor Inventory) and rUC4 (Indoor Command).

[0113] - In RAN#104, this study evaluates whether a harmonized wireless interface design (see bullet point 'A' above) can handle DO-A (Device-Initiated Autonomous) use cases and identifies which parts of the harmonized wireless interface design (see bullet point 'A' above) are insufficient for DO-A use cases.

[0114] Transmission from surrounding IoT devices (including backscattering when in use) may occur at least within the UL spectrum.

[0115] The next goal is set within the general range.

[0116] 1. Evaluation Assumptions

[0117] a) Conclude at least the following aspects of the design objectives left to the WG in Clause 5 (RAN Design Objectives) of TR 38.848 [RAN1].

[0118] Clause 5.3: Applicable maximum distance target value

[0119] Clause 5.6: Refine the definition of latency suitable for use in the RAN WG.

[0120] Clause 5.8: 2D distribution of the device

[0121] b) Define the necessary additional evaluation assumptions for deployment scenarios for coverage and coexistence evaluation. [RAN1, RAN4]

[0122] c) Identify the basic blocks / components of possible peripheral IoT device architectures by considering modern implementations of low-power, low-complexity devices that meet RAN design goals regarding power consumption and complexity. [RAN1]

[0123] d) Define link budget calculations for coverage, including whether / how to model carrier waves at nodes inside or outside the connection topology.

[0124] Note: The evaluation performance of the design target falls within the scope of the feasibility and necessity study of the proposal in the following objectives. For example, it involves inspecting the reference implementation in the field, performing simulations, and conducting analytical analysis.

[0125] Note: We strive to minimize evaluation cases in RAN1.

[0126] 2. Investigate necessary and viable solutions for Ambient IoT as defined in the general scope. This includes determining which functions, procedures, etc. are necessary and which are not, and ensuring at least the essential functions specified in Section 6.2 of TR 38.848.

[0127] Rel-19 localization studies are led by RAN3 and are limited to features that have no or minimal impact on the specification (Note: This does not imply decisions related to WI generation).

[0128] We study the feasibility and necessary functions for proximity determination (coordination with SA3 is necessary for privacy reasons).

[0129] - RAN1-led:

[0130] For Ambient IoT DL and UL:

[0131] Frame structure, synchronization and timing, random access

[0132] Numerology, Bandwidth, and Multiple Access

[0133] Waveform and Modulation

[0134] Channel coding

[0135] Downlink Channel / Signal Aspect

[0136] Uplink Channel / Signal Side

[0137] Scheduling and Timing Relationships

[0138] We study the necessary characteristics of carrier wave waveforms provided externally to ambient IoT devices, including interference processing at ambient IoT UL receivers and NR base stations.

[0139] For Topology 2, there is no difference in the physical layer design compared to Topology 1.

[0140] RAN2 Lead:

[0141] We research and determine the functions required for the Ambient IoT Compact Protocol stack and lightweight signaling procedures that enable DO-DTT and DT data transmission, and study those functions.

[0142] for example:

[0143] Paging

[0144] Random access

[0145] Data transmission including necessary wireless resource control aspects that comply with general range limitations

[0146] Interaction with the upper class

[0147] Features not listed above are researched only if deemed essential.

[0148] RAN3 Leading:

[0149] Identify the necessary effects on the signals and procedures of the CN-RAN interface to enable the following.

[0150] Paging

[0151] Device Context Management

[0152] Data transmission

[0153] Identify RAN architecture aspects, including whether partitioned architecture support is required.

[0154] Identify potential solutions for finding Ambient IoT devices without impacting specifications. For example, reuse existing user location reports or transmit location information to the core network with minimal impact on specifications.

[0155] RAN4 Leading:

[0156] Research on the coexistence of Ambient IoT and NR / LTE.

[0157] Research on RF Requirements for Ambient IoT:

[0158] Ambient IoT BS Transmitter / Receiver

[0159] Ambient IoT devices and transmission / reception based on general range

[0160] Intermediate node (UE) and transmission / reception based on general range

[0161] RAN2 and RAN3 are expected to cooperate with SA2 to identify RAN-CN functional splits.

[0162] Note: This study targets IoT segments that are much lower than existing 3GPP IoT technologies (e.g., NB-IoT, eMTC, RedCap, etc.). This study does not aim to replace existing 3GPP LPWA technologies.

[0163] For example, as described above, the types of A-IoT devices can be classified into two as follows. For example, a Type 1 device has a maximum power consumption of approximately 1 uW, is capable of energy storage, has no amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node). For example, a Type 2 device has a maximum power consumption of approximately several hundred uW, is capable of energy storage, has an amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node) or by using a signal generated internally.

[0164] For example, in addition to the classification methods described above, the type / class of an A-IoT device may be distinguished based on parameters associated with device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of parameters. Here, for example, the BPF capability may be distinguished by the 3-dB bandwidth of the supported BPF, sharpness, etc., and the UL transmission methods may be distinguished by, for example, backscattered UL transmission, UL transmission by internal signal generation, etc.

[0165] In addition, the type / class of an A-IoT device may be subdivided based on parameters associated with the above device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of such parameters. For example, the above-described Type 2 device may be classified into Type 2a when it performs transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node), and Type 2b when it performs transmission using a signal generated internally. In this case, Types 2a and 2b may be identical in that they have a maximum power consumption of approximately several hundred uW, are capable of energy storage, and have amplification capabilities.

[0166] For example, some types / classes of A-IoT devices (e.g., device B, device C, type 1 device, and / or type 2 device) may be equipped with energy storage capabilities (e.g., capacitors or charging batteries) for the following purposes.

[0167] - Securing stable energy at the time of reception / transmission

[0168] - Operation of low-power communication modules through energy storage in low RF energy states

[0169] For example, the minimum RF reception sensitivity for operating a low-power communication module may be -20dBm, and the minimum reception sensitivity for energy harvesting may be -20dBm. In this case, if the received power of the A-IoT device is distributed between -30 and -20dBm, communication may be impossible without a capacitor, and communication may be possible after a charging time with a capacitor.

[0170] - Store energy harvested from different energy sources (e.g., solar, thermal, wind, kinetic, etc.) in a single capacitor to operate a low-power communication module at a desired time.

[0171] FIG. 6 illustrates examples of power consumption and device energy status according to the operating state of an energy harvesting-based device. Specifically, FIG. 6 illustrates examples of power consumption and device energy status according to the operating state of an energy harvesting-based device having energy storage capabilities, according to one embodiment of the present specification. The embodiment of FIG. 6 may be combined with various embodiments of the present specification.

[0172] Referring to FIG. 6(b), S1 may be a sleep state, S2 may be an active state, and P1 and P2 may be power consumption in S1 and S2, respectively. For example, the active state may refer to a state in which the device consumes power to perform operations such as receiving / transmitting for communication or sensing, and the sleep state may be a state that is not an active state.

[0173] FIG. 6(a) may represent the device energy state corresponding to FIG. 6(b). Referring to FIG. 6(a), the E1 and E2 values ​​may vary by device (type / class), and the device may report information related to the E1 value and / or information related to the E2 value to R and / or the base station as capability parameters. For example, the E2 value may be defined as the energy value in the buffered state, and the E1 value as the minimum energy value required in the active state.

[0174] For example, the transition from S1 to S2 may be possible only when the device energy state value is E2 or reaches E2. For example, the transition from S1 to S2 may be possible when the device energy state value is greater than E1 (i.e., within the range between E1 and E2). An embodiment of FIG. 6 illustrates an example in which the transition from S1 to S2 is performed when the device energy state value is E2 or reaches E2.

[0175] For example, an A-IoT device may require an externally provided CW for backscatter transmission. For example, the CW can be used to supply energy to A-IoT devices or as a CW for DL ​​transmission, regardless of the transmission mode (e.g., backscatter transmission or internally generated transmission).

[0176] For example, CW waveforms can be supported in various types. For instance, the type of CW waveform can be a single-tone CW waveform or a somewhat complex multi-tone CW waveform. For instance, single-tone CW may be advantageous over multi-tone CW in terms of the multiplexing capacity of tags or readers and in terms of interference, as it uses fewer resources. On the other hand, multi-tone CW has advantages, such as the ability to deliver more energy when transmitting CW over DL and to secure greater coverage on a single device.

[0177] Considering the advantages of these different CW waveform types, multiple CW waveform types may be supported in an A-IoT system, and the base station / IN / AN / UE may configure the CW waveform type. For example, one or more CW waveform types supported in the A-IoT communication system may be pre-configured / defined, and the base station / IN / AN / UE may select one of the one or more supported CW waveform types and transmit it to an A-IoT device. For example, the base station / IN / AN / UE may configure / instruct / display the selected CW waveform type to the A-IoT device in the form of a command / message transmitted as a preamble / frame-sync or payload.

[0178] For example, in this specification, for A-IoT communication, at least one of the necessary characteristics of a carrier waveform for a carrier provided outside the A-IoT device (including interference handling at the A-IoT device UL receiver and NR base station) may be proposed. For example, in this specification, for A-IoT communication, at least one of paging, random access, data transmission including necessary radio resource control aspects complying with general range limitations, interaction with upper layers (e.g., RRC layer, NAS (non-access stratum) layer, application layer, etc.), device context management, data transmission, coexistence of A-IoT and 6G / NR / LTE, and / or RF requirements for A-IoT may be proposed.

[0179] For example, technical terms used in this specification may be as follows.

[0180] - SSB: Synchronization Signal Block

[0181] - MIB: Master Information Block

[0182] - RMSI: Remaining Minimum System Information

[0183] - FR1: Frequency Range 1. Refers to the frequency range of 6 GHz or lower (e.g., 450 MHz ~ 6000 MHz).

[0184] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) region above 24 GHz (e.g., 24,250 MHz ~ 52,600 MHz).

[0185] - BW: Bandwidth

[0186] - BWP: Bandwidth Part

[0187] - RNTI: Radio Network Temporary Identifier

[0188] - CRC: Cyclic Redundancy Check

[0189] - SIB: System Information Block

[0190] - SIB1: SIB1 for NR devices (i.e., Remaining Minimum System Information (RMSI)). Broadcasts information necessary for cell connection of NR terminals.

[0191] - CORESET: Control Resource Set. The time / frequency resource when the NR terminal attempts candidate PDCCH decoding.

[0192] - CORESET#0: CORESET for Type0-PDCCH CSS set for NR devices (configured in MIB)

[0193] - Type0-PDCCH CSS set: a search space set in which an NR UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0194] - MO: PDCCH Monitoring Occasion for Type0-PDCCH CSS set

[0195] - SIB1-R: (additional) SIB1 for reduced capability NR devices. This may be limited to cases where it is created as a separate TB from SIB1 and transmitted via a separate PDSCH.

[0196] - CORESET#0-R: CORESET#0 for reduced capability NR devices

[0197] - Type0-PDCCH-R CSS set: a search space set in which a redcap UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0198] - MO-R: PDCCH Monitoring Occasion for Type0-PDCCH CSS set

[0199] - Cell defining SSB (CD-SSB): An NR SSB that includes RMSI scheduling information

[0200] - Non-cell defining SSB (non-CD-SSB): Refers to an SSB deployed in an NR sync raster that does not include the corresponding cell's RMSI scheduling information for measurement purposes. However, it may include information indicating the location of the cell defining SSB.

[0201] - SCS: subcarrier spacing

[0202] - SI-RNTI: System Information Radio-Network Temporary Identifier

[0203] - Camp on: “Camp on” is the UE state in which the UE stays on a cell and is ready to initiate a potential dedicated service or to receive an ongoing broadcast service.

[0204] - TB: Transport Block

[0205] - RSA (Redcap standalone): Redcap device 또는 service만 지원하는 cell.

[0206] - SIB1(-R)-PDSCH: SIB1(-R)을 전송하는 PDSCH

[0207] - SIB1(-R)-DCI: SIB1(-R)-PDSCH를 scheduling하는 DCI. DCI format 1_0 with CRC scrambled by SI-RNTI.

[0208] - SIB1(-R)-PDCCH: SIB1(-R)-DCI를 전송하는 PDCCH

[0209] - FDRA: Frequency Domain Resource Allocation

[0210] - TDRA: Time Domain Resource Allocation

[0211] - RA: Random Access

[0212] - MSGA: preamble and payload transmissions of the random access procedure for 2-step RA type.

[0213] - MSGB: response to MSGA in the 2-step random access procedure. MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication.

[0214] - RO-N: normal UE 4-step RACH and 2-step RACH(if configured)를 위한 RO(RACH Occasion)

[0215] - RO-N1, RO-N2: When separate ROs are configured for normal UE 2-step RACH, they are distinguished as RO-N1 (4-step) and RO-N2 (2-step).

[0216] - RO-R: RO (RACH Occasion) configured separately from RO-N for Redcap UE 4-step RACH and 2-step RACH (if configured)

[0217] - RO-R1, RO-R2: When separate ROs are configured for Redcap UE 2-step RACH, they are distinguished as RO-R1 (4-step) and RO-R2 (2-step).

[0218] - PG-R: MsgA-Preambles Group for redcap UEs

[0219] - RAR: Random Access Response

[0220] - RAR window: the time window to monitor RA response(s)

[0221] - FH: Frequency Hopping

[0222] - iBWP: initial BWP

[0223] - iBWP-DL(-UL): initial DL(UL) BWP

[0224] - iBWP-DL(-UL)-R: (separate) initial DL(UL) BWP for RedCap

[0225] - CS: Cyclic shift

[0226] - NB: Narrowband

[0227] - TO: Traffic Offloading

[0228] -mMTC; Massive Machine Type Communications

[0229] - eMBB: enhanced Mobile Broadband Communication

[0230] - URLLC: Ultra-Reliable and Low Latency Communication

[0231] - RedCap: Reduced Capability

[0232] - eRedCap: enhanced RedCap

[0233] - FDD: Frequency Division Duplex

[0234] - HD-FDD: Half-Duplex-FDD

[0235] - DRX: Discontinuous Reception

[0236] - RRC: Radio Resource Control

[0237] - RRM: Radio Resource Management

[0238] - MM: Mobility Management

[0239] - IWSN: Industrial Wireless Sensor Network

[0240] - LPWA: Low Power Wide Area

[0241] - RB: Resource Block

[0242] - CCE: Control Channel Element

[0243] - AL: Aggregation Level

[0244] - PRG: Physical Resource-block Group

[0245] - DFT-s-OFDM: DFT-spread OFDM

[0246] - PBCH: Physical Broadcast Channel

[0247] - A-PBCH: Additional PBCH

[0248] - BD: blind detection

[0249] - EPRE: Energy Per RE

[0250] - SNR: Signal-to-Noise Ratio

[0251] - TDM: Time Division Multiplexing

[0252] - FDM: Frequency Division Multiplexing

[0253] - DMRS: DeModulation Reference Signal

[0254] - TDD: Time Division Duplex

[0255] - PCI: Physical layer Cell ID

[0256] - EH: Energy Harvesting

[0257] - EH device: A device that operates based on EH. It may include all of Device A / B / C currently under discussion at 3GPP. Additionally, while the present invention primarily considers RF EH, the EH device does not necessarily have to be RF EH-based.

[0258] - ES: Energizing Signal. A signal / channel transmitted by a base station / IN / AN / UE for the purpose of supplying RF energy to a device operating on an RF-based energy harvesting basis. (Modulated) CW, NR / LTE DL / UL signals, etc. can be ES, and a dedicated signal / channel for ES can be designed to support it.

[0259] - ET: Energy Transfer

[0260] - CW: Carrier wave. Ambient IoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering the “externally provided” CW. Ambient IoT devices supporting independent signal generation-based UL transmission transmit information by modulating the “internally generated” CW. Unless otherwise noted, it is assumed to refer to the “externally provided” CW for backscattering. The CW can be used as an ES (Energizing Signal) for RF energy transfer.

[0261] - CWN: Carrier Wave Node. A node that provides the above CW. It may be a base station, IN, AN, or UE, and a separate CWN may exist for the purpose of providing CW.

[0262] - R: Reader / Interrogator. This is an RFID standard term. In the 3GPP Ambient IoT context, depending on the topology, gNBs / eNBs, intermediate / assisting nodes, UEs, etc., can act as readers. Furthermore, since Ambient IoT is not limited to 4G / 5G communication systems, it can include base stations, intermediate / assisting nodes, and UEs of next-generation communication systems. It may also refer to an Ambient IoT reader.

[0263] - T: Tag / ambient IoT device. It is an RFID standard term. In the present invention, it can be interchangeably used with EH device, and in the 3GPP Ambient IoT context, it mainly refers to Ambient IoT device, Device A / B / C.

[0264] - D: Ambient IoT device (may have the same meaning as T above)

[0265] - R=>T: Reader-to-Tag or Reader-to-Tag communication link. If the base station or intermediate / assisting node is the reader, it may have the same meaning as DL or forward link.

[0266] - R2D: R-to-D link (Can be synonymous with R=>T. Can be denoted as R=>D.)

[0267] - CW2D: CWN-to-D link (CW node to Ambient IoT device link)

[0268] - T=>R: Tag-to-Reader or Tag-to-Reader communication link. If the base station or intermediate / assisting node is the reader, it may have the same meaning as UL or reverse / backward link.

[0269] - D2R: May have the same meaning as T=>R. Can be written as D=>R.

[0270] - R<=>T: Includes cases of R=>T and T=>R, or R=>T or T=>R. May apply to both R=>T and T=>R.

[0271] - R<=>D: Includes cases of R2D and D2R, or R2D or D2R. May apply to both R2D and D2R. (May have the same meaning as R<=>T)

[0272] - RF-EH: RF energy harvesting

[0273] - PRDCH: Physical R2D CHannel (may be denoted as PR2DCH). Physical channel for R2D communication.

[0274] - PDRCH: Physical D2R CHannel (may be denoted as PD2RCH). Physical channel for D2R communication.

[0275] - BS: Base Station

[0276] - IN: Intermediate node. In Topology 2 (BS <-> IN <-> Ambient IoT device), IN acts as a reader. Relays, IABs, UEs, repeaters, etc., can be INs.

[0277] - AN: Assisting node. It can assist with DL transmission in Topology 3-1 (BS -> AN -> Ambient IoT device -> BS) or assist with UL transmission in Topology 3-2 (BS -> Ambient IoT device -> AN -> BS). Relays, IABs, UEs, repeaters, etc. can be ANs.

[0278] - UE: User Equipment. In the case of LTE, NR, or next-generation communication systems, it refers to the LTE, NR, or next-generation communication system UE / terminal, respectively. It is a general wireless communication terminal form distinct from Ambient IoT devices or Devices A / B / C. In Topology 4 (UE <-> Ambient IoT device), the UE acts as a reader.

[0279] - Device: Unless otherwise noted, and when used alone, it refers to the EH device, Ambient IoT device, or Device A / B / C without distinction.

[0280] - AmIoT: Ambient IoT

[0281] - F-gap: Frequency gap

[0282] - T-gap: Time gap

[0283] - TD: Time Domain

[0284] - FD: Frequency Domain

[0285] - PEI: Paging Early Indication

[0286] - LP-WUS: Low-Power Wake-Up Signal

[0287] - LP-SS: Low-Power Synchronization Signal

[0288] - RSRP: Reference Signal Received Power

[0289] - ESRP: ES Received Power. May refer to RSRP measured using ES. May have the same meaning as ES-RSRP.

[0290] - PRB: Physical Resource Block

[0291] - EH circuit: A circuit that performs EH operation. An EH device can be viewed as including the EH circuit as a component.

[0292] - PHR: Power Headroom Report

[0293] - EHR: Energy Headroom Report

[0294] - BPF: Band-Pass Filter

[0295] - SM: Subcarrier Modulation

[0296] The methods proposed in this specification can be applied commonly to topology 1 and topology 2, and UE1 as gNB and IN is referred to as reader for convenience. Additionally, the invention can be extended to cases where the reader receiving the BSS directly generates and transmits the CW, or where the node transmitting the CW is a separate node from the reader.

[0297] As used in this specification, the Ambient IoT BS (base station) (e.g., reader) may be a gNB in ​​topology 1 and a specific UE in topology 2. Additionally, the Ambient IoT device (e.g., tag) used in this specification may be interpreted as an Ambient IoT device in both topology 1 and / or topology 2. The D1T1 series scenarios in Table 3 represent scenarios for topology 1, and the D2T2 series scenarios in Table 4 represent scenarios for topology 2. In this case, depending on the scenario, the reader for R2D transmission and the reader for D2R reception may be the same or different nodes. Additionally, depending on the scenario, the CW node performing CW2D transmission may be the same or different node as the reader.

[0298] Figure 7 is an example showing a combination of Deployment scenario 1 and topology 1 with various CWs.

[0299] Referring to Fig. 7, it can be seen that in Deployment scenario 1 and topology 1 (indoor BS and indoor AIoT device), i) the case where the external CW is inside the topology (D1T1-A), ii) the case where the external CW is outside the topology (D1T1-B), and iii) the case where there is no external CW (in other words, the case where D2R is transmitted using an internally generated CW, D1T1-C) are considered.

[0300] D1T1-A can be considered in cases i) where the CW2D / R2D and D2R nodes are different (D1T1-A1 in Fig. 7) and ii) where the CW and R nodes for CW2D, D2R, and R2D are the same (D1T1-A2 in Fig. 7).

[0301] Specifically, D1T1-A1 represents the case where i) CW of CW2D and R of D2R are different, ii) CW of CW2D and R of R2D are the same, and iii) R of R2D and R of D2R are different.

[0302] D1T1-B represents the case where i) CW of CW2D and R of D2R are different, ii) CW of CW2D and R of R2D are different, and iii) R of R2D and R of D2R are the same.

[0303] D1T1-C can be considered only for device 2b.

[0304] Figure 8 is an example showing a combination of Deployment scenario 2 and topology 2 with various CWs.

[0305] Referring to Fig. 8, it can be seen that in Deployment scenario 2 and topology 2 (outdoor BS, Indoor Intermediate UE and Indoor AIoT device), i) the case where the external CW is inside the topology (D2T2-A), ii) the case where the external CW is outside the topology (D2T2-B), and iii) the case where there is no external CW (i.e., when D2R is transmitted using an internally generated CW, D2T2-C).

[0306] D2T2-A can be considered in cases i) where the CW2D / R2D and D2R nodes are different (D2T2-A1 in FIG. 8) and ii) where the CW and R nodes for CW2D, D2R, and R2D are the same (D2T2-A2 in FIG. 8).

[0307] Specifically, D2T2-A1 represents the case where i) CW of CW2D and R of D2R are different, ii) CW of CW2D and R of R2D are the same, and iii) R of R2D and R of D2R are different.

[0308] D2T2-B represents the case where i) CW of CW2D and R of D2R are different, ii) CW of CW2D and R of R2D are different, and iii) R of R2D and R of D2R are the same.

[0309] D2T2-C can be considered only for device 2b.

[0310] FIG. 9 is an example showing device type 1 according to an embodiment of the present specification.

[0311] FIG. 10 is an example showing a different device type 2a of the embodiments of the present specification.

[0312] FIG. 11 is an example showing a different device type 2b of the embodiments of the present specification.

[0313] Devices 1 and 2a, illustrated in FIGS. 9 and 10 respectively, perform D2R transmission by backscattering CW, and device 2b, illustrated in FIG. 11, is equipped with a local oscillator at the transmitting end to perform D2R transmission without the assistance of CW. Device 1 has a simple structure without amplifiers for R2D reception and D2R transmission at the receiving end and transmitting end, respectively, whereas devices 2a and 2b have a structure equipped with a reflection amplifier and a power amplifier at the transmitting end, respectively, for D2R transmission.

[0314] Meanwhile, this specification proposes preamble, midamble, and postamble design methods that can be used for Ambient IoT transmission and reception. In this specification, the term "x-amble" is used to refer collectively to preamble, midamble, and postamble. Characteristically, a preamble refers to a transmission that occurs at the very beginning of a specific D2R or R2D transmission, a midamble in the middle, and a postamble at the very end.

[0315] Meanwhile, the preamble, midamble, and postamble mentioned in this specification may be transmitted together with D2R, R2D transmissions (e.g., PDRCH, PRDCH), etc., or may be transmitted included in said D2R, R2D transmissions.

[0316] The device ID mentioned in this specification may refer to a unique ID embedded within each device. However, instead of the device ID used in this invention, a method of using an ID such as a C-RNTI that can be exchanged between devices / readers during the inventory round phase may also be considered.

[0317] The state mentioned in this specification refers to states such as ON / SLEEP / OFF to increase the available time of a device in an Ambient IoT system. In this case, the ON state is defined as a state in which the device can perform TX / RX while consuming energy, the SLEEP state is defined as a state in which the device can perform energy harvesting without performing TX / RX while maintaining memory content or timer / clock, etc., from the ON state, and finally, the OFF state is defined as a state in which the device can perform energy harvesting without maintaining memory content or timer / clock, etc., from the ON state and without performing TX / RX.

[0318] In this document, ' / ' means 'and', 'or', or 'and / or' depending on the context.

[0319] Figure 12 is an example showing the entire AS procedure between an A-IoT device and a reader.

[0320] Referring to Fig. 12, the entire AS (Access Stratum) procedure can be configured as follows.

[0321] - Step A: A-IoT paging based on the service request. The reader sends an A-IoT paging message indicating the device(s) requiring a response.

[0322] - Step B: Transmission of D2R data (Device ID). The triggered A-IoT device(s) perform device ID transmission using the A-IoT random access procedure or without using the A-IoT random access procedure.

[0323] - Step C1: Possible R2D data transmission (e.g., R2D data transmission for sending commands)

[0324] - Step C2: Transmit possible D2R data (e.g., response corresponding to a command)

[0325] In step A of FIG. 12, paging (or Msg0) may include one or more device IDs, a device group ID, or all devices, so that one or more or all devices that receive this may trigger the random access procedure of Step B.

[0326] In Step B of Fig. 12, Msg1 / Msg2 / Msg3 / (Msg4) are each considered for a random access (RA) procedure to be performed by multiple devices in an Ambient IoT system. Among these, Msg1 / Msg3 are D2R signals / channels transmitted by the device, and Msg2 / (Msg4) are R2D signals / channels transmitted by the reader. At this time, if a time gap index / frequency gap index for D2R transmission is set for Msg1 / Msg3, they can be transmitted via TDM / FDM between multiple devices. On the other hand, Msg2 basically considers TDM because, since the presence or absence of bandpass filtering capability varies by device (or device type), it may not be easy for each device to properly filter and receive multiple FDMed R2D signals / channels transmitted from the reader.

[0327] This specification proposes a method for configuring TDMed / FDMed resources for Msg1 / Msg2 / Msg3 / (Msg4) during a contention-based access procedure (or random access procedure) in an ambient IoT system.

[0328] As used in this specification, the term "slot" refers to a slot considered in slotted ALOHA operation, which may have a variable length in the time domain depending on the reader's settings or instructions. Alternatively, in A-IoT, a slot of slotted ALOHA may be defined as an access occasion.

[0329] TDM / FDM transmission of Msg1 and Msg3

[0330] In this specification, an R2D message that triggers the start of an inventory round, such as the A-IoT paging message of FIG. 12, or triggers one or more RAs (Random Access) within the same inventory round, can be defined as Msg0. In this case, the R2D messages that trigger one or more RAs within the same inventory round may include the same specific ID or be associated with a specific ID. For example, the specific ID may be a transaction ID. The reader and the device may determine i) that the connection process is for the same inventory round if the specific IDs are the same, and ii) that the connection process is for a different inventory round if the specific IDs are different. When an RA is triggered, the device transmits Msg1 and receives Msg2 in response. Subsequently, if the Msg2 received by the device instructs the transmission or retransmission of Msg3, the device transmits / retransmits Msg3 and may receive Msg4 in response.

[0331] In this specification, a case in which the Msg1 resource undergoes TDM and FDM can be considered, and a case in which the Msg3 resource also undergoes TDM and FDM can be considered. For example, a case may be considered in which the Msg1 resource undergoes TDM X times within a specific slot in an inventory round to create X sub-slots, and each sub-slot undergoes FDM Y times to create Y frequency domain resources. In such a case where Msg1 undergoes TDM and FDM, a case in which Msg3 also undergoes TDM and FDM in a similar manner can be considered. In other words, after Msg2 is received within the aforementioned specific slot, the Msg3 resource undergoes TDM X times to create X sub-slots, and each sub-slot undergoes FDM Y times to create Y frequency domain resources.

[0332] Meanwhile, when the Msg1 resource is configured with TDM and FDM as described above, the corresponding Msg2 resource can be transmitted with TDM. At this time, the Msg2 resource can be configured to be transmitted with TDM according to the time first - frequency second (or frequency first - time second) order relative to the Msg1 resource. This can be illustrated as shown in Fig. 13.

[0333] FIG. 13 is an example illustrating the procedure for transmitting the Msg2 resource after TDM. Specifically, FIG. 13 illustrates a case where D2R messages Msg1 and Msg3 are transmitted after TDM and FDM, and Msg2 is transmitted after TDM.

[0334] Referring to Fig. 13, for Msg1 in the D2R message, X=3 and Y=2, and for the Msg2 resource in the R2D message, the Msg2 resource is arranged in a frequency first - time second manner based on the Msg1 resource. In other words, for Msg2, the Msg2 resource is first arranged in an order of increasing frequency index within the same time index based on the Msg1 resource, and then after increasing the time index, the Msg2 resource can be arranged subsequently in an order of increasing frequency index within that time index.

[0335] Meanwhile, when an R2D transmission such as Msg0 triggers an RA, such an R2D transmission may allocate X sub-slot time resources and Y frequency resources. In this case, X and Y each have a positive integer value of 1 or greater than 1, and one or more resources determined by the multiplication of X and Y may be composed of the R2D transmission that triggers the RA.

[0336] Figure 14 is an example illustrating the allocation of time resources for a D2R transmission triggered by an R2D transmission.

[0337] Referring to FIG. 14, in the case where a single R2D transmission triggering RA allocates two sub-slots corresponding to X=2 for D2R transmission, T from the R2D transmission triggering RA (e.g., the end time of the sub-slot of the R2D transmission triggering RA) to the start time of the Msg1 transmission of the first sub-slot offset1 The first sub-slot can be determined / assigned by defining ('T' in 'Option 1' and 'Option 2' in Fig. 14). offset1 ' - reference).

[0338] For example, referring to Option 1 in FIG. 14, the second sub-slot for Msg1#2 is defined as T from the start or end of the transmission of Msg1 in the first sub-slot ('Msg1#1' in FIG. 14) to the start of the transmission of Msg1 in the second sub-slot ('Msg1#2' in FIG. 14). offset2 It can be determined / assigned according to. As another example, referring to Option 2 in FIG. 14, the second sub-slot for Msg1#2 is defined as T from the R2D transmission triggering RA to the start of the Msg1 transmission of the second sub-slot. offset3 It can be determined / assigned according to.

[0339] As described above, X sub-slots are determined / assigned by R2D transmission, and one or more Y frequency resources can be determined / assigned by the same R2D transmission. When the R2D transmission triggers the RA of one or more devices, the device can select one sub-slot among the X sub-slots, select one frequency resource among the Y frequency resources, and transmit Msg1 to the selected sub-slot location and the selected frequency resource.

[0340] In this specification, the Toffset-based D2R transmission resource allocation method may also be applied in all cases where Msg3 transmission triggered by Msg2 or R2D transmission after RA triggers D2R transmission.

[0341] In the case where multiple responses to multiple Msg1s are transmitted to Msg2 as described above, the device may set a Msg2 transmission window (or a time interval for monitoring Msg2) starting from a certain time after the transmission of Msg1, and monitor the transmission of Msg2 during the window. For example, the start time and length of the window may be indicated / set by the reader through L1 control information, L2 control information, MAC CE, or premable of Msg0 that triggered Msg1. For another example, if Msg0 does not indicate / set / include the start time and length of the window, or if the L1 control information, L2 control information, MAC CE, or premable of Msg0 indicates / sets the exclusion of the start time and length of the window, the device may determine the start time and length of the window using a stored pre-defined value and monitor Msg2. As another example, if Msg0's L1 control information, L2 control information, MAC CE, or premable instructs the use of a pre-defined value, the device can monitor Msg2 by determining the start time and length of the window using the stored pre-defined value.

[0342] Specifically, a specific 1 bit of L1 control information, L2 control information, or MAC CE may indicate whether to use a pre-defined value or to set the window start time and length using a value subsequently indicated / set. For example, if the specific 1 bit indicates to set the window start time and length using a value subsequently indicated / set, the device may obtain the value to be indicated / set from the bits after the specific 1 bit and use the obtained value to set the window start time and length. As another example, if the specific 1 bit indicates to use a pre-defined value, the device determines that there are no bits indicating the value to be indicated / set after the specific 1 bit. In other words, if the specific 1 bit indicates to use a pre-defined value, the reader may not include bits indicating the value to be indicated / set in the L1 control information, L2 control information, or MAC CE after the specific 1 bit of L1 control information, L2 control information, or MAC CE.

[0343] In this specification, a single R2D transmission or D2R transmission / D2R repeat transmission may be transmitted by filling all resources within the sub-slot or by filling only a portion of them. When a single R2D transmission or D2R transmission / D2R repeat transmission is performed by filling only a portion of the sub-slot, the device may transmit i) so that the start and end of each R2D transmission or D2R transmission / D2R repeat transmission enter the allocated sub-slot, ii) so that only the start of each R2D transmission or D2R transmission / D2R repeat transmission enters the allocated sub-slot, or iii) so that only the end of each R2D transmission or D2R transmission / D2R repeat transmission enters the allocated sub-slot.

[0344] In this specification, x-amble may mean a preamble and / or a midamble and / or a postamble. An x-amble may be a specific sequence or a specific binary pattern (e.g., a binary pattern consisting entirely of '1s', entirely of '0s', or a combination of '1s' and '0s'). In this specification, in addition to the D2R preamble transmitted prior to the PDRCH, if an x-amble is added immediately after the D2R preamble, immediately before or after the PDRCH, or within the PDRCH, the added x-amble occupies the time / frequency resources of the PDRCH, and the length corresponding to the x-amble may or may not be included in the TB size or message size of the PDRCH. Additionally, if an x-amble is added according to the option(s) below, and the added x-amble exceeds the allocated PDRCH resource range, the device may i) truncate the portion of the resource that exceeds the range to transmit the PDRCH, or ii) transmit the PDRCH including the portion of the resource that exceeds the range. Accordingly, the reader can receive a PDRCH by taking into account that the device i) transmits the PDRCH by truncation of the overflowing resource portion to match the allocated resource range, or ii) transmits the PDRCH including the overflowing resource portion.

[0345] [Method #1] Method for Determining Toffset

[0346] As shown in FIG. 14, when two sub-slots corresponding to X=2 are allocated for a single R2D transmission that triggers an RA, the first sub-slot can be determined / assigned by defining Toffset1 from the R2D transmission that triggers the RA to the start of the Msg1 transmission of the first sub-slot. Additionally, the second sub-slot can be determined / assigned by defining Toffset2 from the start of the Msg1 transmission of the first sub-slot to the start of the Msg1 transmission of the second sub-slot as in option 1 of FIG. 14, or by defining Toffset3 from the R2D transmission that triggers the RA to the start of the Msg1 transmission of the second sub-slot as in option 2.

[0347] When determining / assigning Toffset2 or Toffset3 as above, the values ​​of Toffset2 and Toffset3 (or the time intervals corresponding to Toffset2 and Toffset3, respectively) include the transmission length of Msg1 (see 'Msg1#1' in FIG. 14), and thus the values ​​of Toffset2 and Toffset3 can be determined according to the length of Msg1.

[0348] For example, if the transmission time interval of a PDRCH containing Msg1 is 16ms, Toffset2 may be determined to be 18ms including a specific time gap (e.g., a 2ms gap) in the 16ms interval, and if the transmission time interval of a PDRCH containing Msg1 is 8ms, Toffset2 may be determined to be 9ms including a specific time gap (e.g., a 1ms gap) in the 8ms interval. In this case, the length of the specific gap may be determined by considering the device's Sampling Frequency Offset (SFO) error, and the length of the gap may be determined to be longer as the transmission length of the PDRCH increases. And / or, Toffset3 may be determined as a value that changes according to the transmission length of the PDRCH containing Msg1, similar to the example for Toffset2 above.

[0349] In this specification, the following alternatives may be considered for determining the value of Toffset2 or Toffset3, which determines the configuration of D2R transmission resources that are TDMA-controlled according to the D2R transmission length.

[0350] Alternative 1 (Alt 1): A method for determining one value of Toffset2 or one value of Toffset3 from among multiple candidate values ​​for Toffset2 or Toffset3 based on the length of the current D2R time resource or sub-slot.

[0351] In this case, the length of the D2R time resource or sub-slot may be the temporal length of the resource containing a single D2R transmission. In other words, the length of the D2R time resource or sub-slot may have a value equal to or greater than the length of the D2R transmission.

[0352] For example, candidate values ​​and / or the values ​​of Toffset2 or Toffset3 can be determined in the following way.

[0353] - T offset2 can be determined by adding a (specific) gap to the length of the time domain resource / sub-slot of the first Msg1 (T offset2 = the duration of the first Msg1 time domain resource / sub-slot + gap).

[0354] - T offset3 Eun T offset1 , can be determined by the sum of the length of the time domain resource / sub-slot of the first Msg1 and the (specific) gap (T offset3 = T offset1 + the duration of the first Msg1 time domain resource / sub-slot +gap).

[0355] Alternative 2: A method to determine one value of Toffset2 or one value of Toffset3 from among multiple candidate values ​​for Toffset2 or Toffset3 based on the current D2R transmission length.

[0356] For example, the D2R transmission length can be determined by combining the length of the D2R x-amble(s), such as the preamble / midamble, with the PDRCH length, which is determined by the transmission block size (TB size), CRC length, coding rate, bit / chip duration, etc.

[0357] For example, the candidate values ​​and the values ​​of Toffset2 or Toffset3 can be determined in the following way.

[0358] - T offset2can be determined by the value of 'Msg1's chip / bit duration * (TB size + CRC length) + gap'.

[0359] - T offset3 is 'T offset1 It can be determined by the value of '+ chip / bit duration of Msg1 * (TB size + CRC length) + gap'.

[0360] At this time, gap and Toffset1 may be determined by the device based on the device type or the SFO difference according to the device type, or may be indicated / determined through control information of R2D transmission. Meanwhile, chip / bit duration, TB size, and CRC length may be indicated / determined through control information of R2D transmission.

[0361] In the methods described above, the length of the D2R transmission triggered by the R2D transmission is determined, and if the X value for the D2R transmission resource is X=2 and a second time resource / sub-slot is selected for the D2R transmission, the device receiving the R2D transmission may select one of the candidate values ​​based on the determined D2R length. Subsequently, the device may determine Toffset2 or Toffset3 with the selected value and perform the D2R transmission through the second time resource / sub-slot. In this case, if the R2D transmission is Msg0, the D2R transmission may be Msg1 or Msg3, and if the R2D transmission is Msg2, the D2R transmission may be Msg3. Additionally, the length of the D2R transmission may be indicated / determined through the control information of the R2D transmission, and the candidate values ​​may be fixed values ​​or indicated / determined by the R2D transmission.

[0362] Alternatively, in the above methods, the reader determines the length of the D2R transmission triggered by the R2D transmission, and if the X value for the D2R transmission resource is X=2, the reader may select one of the candidate values ​​based on the determined D2R length. Subsequently, the reader determines Toffset2 or Toffset3 with the selected value and may instruct the device with the determined value of Toffset2 or Toffset3 through the control information of the R2D transmission.

[0363] [Method #2] Resource configuration method for D2R transmissions that persist after RA is triggered by Paging

[0364] The reader can initiate one inventory round by transmitting an A-IoT Paging message, and subsequently trigger one or more D2R transmission(s) for the same inventory round for each R2D message by transmitting another paging message or another R2D message (e.g., Msg0, Msg2, Msg4, etc.). For example, each R2D message may be of the same type or a different type. For example, the D2R transmission(s) may refer to the transmission / retransmission of D2R transmissions such as Msg1, Msg3, or Msg5.

[0365] At this time, a single device may receive the k-th R2D transmission and perform a D2R transmission, and receive the k+m-th R2D transmission and perform a D2R transmission for the same inventory round. For example, if the first R2D transmission is an A-IoT Paging message, the device may transmit Msg1 as the first D2R transmission, receive the second R2D transmission corresponding to Msg2, and transmit Msg3 as the second D2R transmission. Alternatively, it may receive Msg2, which is the k-th R2D transmission, transmit Msg3, which is the k-th D2R transmission, and receive Msg2, which is the k+m-th R2D transmission, and retransmit Msg3, which is the k+m-th D2R transmission. At this time, all of the above R2D transmissions and D2R transmissions may be transmissions or retransmissions for the same inventory round, and k and m may each be 1 or a positive integer greater than 1.

[0366] As described above, if a D2R transmission is triggered by the k-th R2D transmission and the k+m-th R2D transmission for the same inventory round triggers a D2R transmission again, one or more D2R transmission resources triggered by the k+m-th R2D transmission may be determined / assigned as shown in the following examples. Additionally, the device may select any one of the D2R transmission resources determined / assigned according to the following examples to perform a D2R transmission.

[0367] For example, regarding a specific parameter related to a D2R transmission triggered by the k+m-th R2D transmission, if the k+m-th R2D transmission indicates a specific parameter value, the device can perform a D2R transmission according to the currently indicated specific parameter value.

[0368] For example, regarding a specific parameter associated with a D2R transmission triggered by the k+m-th R2D transmission, if the k+m-th R2D transmission does not indicate a specific parameter value, the device may perform a D2R transmission based on i) a value indicated by the first A-IoT Paging message for the same inventory round, ii) a value indicated by the first R2D transmission, iii) a value indicated by the k-th R2D transmission that indicated the most recent specific parameter value, iv) a value indicated by the k+m-1-th R2D transmission (in other words, the previous R2D transmission), or v) a parameter value applied to the most recent D2R transmission.

[0369] For example, for a Toffset (e.g., Toffset1, Toffset2, or Toffset3) for configuring one or more TDMA resources triggered by the k+m-th R2D transmission, if the k+m-th R2D transmission indicates a specific Toffset value, the device may configure X TDMA resources determined according to the currently indicated specific Toffset value and perform a D2R transmission with one of the X resources.

[0370] For example, for a Toffset (e.g., Toffset1 or Toffset2 or Toffset3) for configuring one or more TDMA resources triggered by the k+m-th R2D transmission, if the k+m-th R2D transmission does not indicate a specific Toffset value, the device may configure X TDMA resources based on i) the value indicated by the first A-IoT Paging message for the same inventory round, ii) the value indicated by the first R2D transmission, iii) the value indicated by the k-th R2D transmission that indicated the most recent specific Toffset value, iv) the value indicated by the k+m-1-th R2D transmission, or v) the value applied to the most recent D2R transmission, and select one of the X resources to perform a D2R transmission.

[0371] For example, regarding specific parameters for configuring one or more FDMA resources (e.g., D2R chip duration, R values, and / or D2R bit duration) triggered by the k+m-th R2D transmission, if the k+m-th R2D transmission indicates a specific parameter value, the device may configure Y FDMA resources determined according to the currently indicated specific parameter value and perform a D2R transmission with one of the Y resources.

[0372] For example, regarding specific parameters (e.g., D2R chip duration, R values ​​and / or D2R bit duration) for configuring one or more FDMA resources triggered by the k+m-th R2D transmission, if the k+m-th R2D transmission does not indicate specific parameter values, the device may configure Y FDMA resources based on i) the value indicated by the first A-IoT Paging message for the same inventory round, ii) the value indicated by the first R2D transmission, iii) the value indicated by the k-th R2D transmission that indicated the most recent specific Toffset value, iv) the value indicated by the k+m-1-th R2D transmission, or v) the value applied to the most recent D2R transmission, and select one of the Y resources to perform D2R transmission.

[0373] In the examples described above, the R2D transmission for the same inventory round may indicate the same transaction ID or be associated with the same transaction ID.

[0374] [Method #3] Msg1 response method of multiple Msg2 PRDCHs

[0375] When multiple Msg1 transmission resources are allocated by the instruction of Msg0, and one or more devices transmit Msg1 according to Msg0, and N Msg2 PRDCHs are subsequently transmitted in response (e.g., when a second Msg2 PRDCH is transmitted following the transmission of the first Msg2 PRDCH), each Msg2 PRDCH may be mapped to a Msg1 transmission resource as follows and may include the corresponding Msg1 response. A device may receive only a specific Msg2 PRDCH according to this mapping.

[0376] - Option 1 (Opt 1): The method by which each Msg2 PRDCH is mapped to a Msg1 transmission resource based on frequency resources.

[0377] When multiple frequency transmission resources with Y > 1 are allocated for multiple Msg1s by the instruction of Msg0, and one or more devices transmit Msg1 according to Msg0, and two Msg2 PRDCHs are transmitted in succession in response thereto (e.g., when a second Msg2 PRDCH is transmitted following the transmission of the first Msg2 PRDCH), each Msg2 PRDCH may include a Msg1 response as follows. In this case, the device may perform the following operations.

[0378] For example, the first Msg2 PRDCH may include a response to some or all of the Msg1 transmitted using only frequencies higher (or lower) than the Msg1 frequency position or frequency-related parameter value indicated by Msg0, based on the Msg1 frequency position or frequency-related parameter value indicated by Msg0. In this case, the device may operate as follows.

[0379] If Msg0 indicates a frequency position (e.g., by the value of R), devices can expect that the first Msg2 may include only the response to Msg1 corresponding to the range from the indicated frequency position to the lowest (or highest) frequency position.

[0380] For example, if there is no frequency position or frequency-related parameter value of Msg1 indicated by Msg0, the first Msg2 PRDCH may include a response to some or all of Msg1 transmitted using only high (or low) frequencies based on the middle position / middle value of Msg1 frequency resources or the frequency position / frequency-related parameter value closest to the middle position / middle value. In this case, the device may operate as follows.

[0381] If Msg0 does not indicate a frequency position, devices can expect that the first Msg2 may include only the response to Msg1 corresponding to the range from the lowest (or highest) frequency position to the center of the frequency position.

[0382] Subsequently, the second Msg2 PRDCH may include a response to some or all of Msg1 transmitted using only frequencies opposite to the reference of the first Msg2 PRDCH. In other words, for example, if the first Msg2 PRDCH includes a response to some or all of Msg1 transmitted using only frequencies higher (or lower) than the Msg1 frequency position or frequency-related parameter value indicated by Msg0, based on the Msg1 frequency position or frequency-related parameter value indicated by Msg0, the second Msg2 PRDCH may include a response to some or all of Msg1 transmitted using only frequencies lower (or higher) than the Msg1 frequency position or frequency-related parameter value indicated by Msg0, based on the Msg1 frequency position or frequency-related parameter value indicated by Msg0. Alternatively, if the first Msg2 PRDCH includes a response to some or all of Msg1 transmitted using only high (or low) frequencies based on parameter values ​​associated with the middle position / middle value of Msg1 frequency resources or the frequency position / frequency closest to the middle position / middle value, the second Msg2 PRDCH may include a response to some or all of Msg1 transmitted using only low (or high) frequencies based on parameter values ​​associated with the middle position / middle value of Msg1 frequency resources or the frequency position / frequency closest to the middle position / middle value.

[0383] Option 2: How each Msg2 PRDCH is mapped to a Msg1 transmission resource based on time resources

[0384] When multiple time transmission resources are allocated for multiple Msg1s by the instruction of Msg0, and one or more devices transmit Msg1 according to Msg0, and multiple Msg2 PRDCHs are subsequently transmitted in response thereto, each Msg2 PRDCH may include a Msg1 response as follows. In this case, the device may perform the following operations.

[0385] For example, N Msg2 PRDCHs can evenly distribute X Msg1 sub-slot resources. For example, when N=2 and X=2, the first Msg2 PRDCH may respond to a Msg1 sent to the first sub-slot, and the second Msg2 PRDCH may respond to a Msg1 sent to the second sub-slot.

[0386] Option 3: Method by which each Msg2 PRDCH is mapped to a Msg1 transmission resource based on the Msg1 resource index

[0387] When multiple transmission resources are allocated for multiple Msg1s by the instruction of Msg0, and one or more devices transmit Msg1 according to Msg0, and multiple Msg2 PRDCHs are subsequently transmitted in response thereto, each Msg2 PRDCH may include a Msg1 response as follows. In this case, the device may perform the following operations.

[0388] For example, N Msg2 PRDCHs can distribute K Msg1 resources (e.g., Msg1 resources with a Msg1 resource index from 0 to 7) evenly. For example, when N=2 and K=8, the first Msg2 PRDCH may respond to a Msg1 sent to a resource with a Msg1 resource index value from 0 to 3, and the second Msg2 PRDCH may respond to a Msg1 sent to a resource with a Msg1 resource index value from 4 to 7.

[0389] For example, in the above case, the resource index value can be calculated as follows:

[0390] Alternative 1: Msg1 resource index = (y-1) + Y * (x-1), where x is 1 to X and y is 1 to Y.

[0391] Alternative 2: Msg1 resource index = y + Y*x, where x is 0 to X-1 and y is 0 to Y-1.

[0392] For example, if N=3 Msg2 PRDCHs are responded to and the maximum value of the Msg1 resource index is 11, the Msg1 resources can be divided into 3 groups as in the following alternatives, and the first, second, and third Msg2 PRDCHs can be responded to for each of group A, group B, and group C, respectively.

[0393] Alternative 1: Consecutive Msg1 resource indexes for each group

[0394] - group A: Msg1 resource index 0 to 3

[0395] - group B: Msg1 resource index 4 to 7

[0396] - group C: Msg1 resource index 8 to 11

[0397] Alternative 2: Msg1 resource indexes with N intervals for each group

[0398] - group A: Msg1 resource index 0, N, 2N

[0399] - group B: Msg1 resource index 1, N+1, 2N+1

[0400] - group C: Msg1 resource index 2, N+2, 2N+2

[0401] For example, each Msg2 can respond to only one group. For instance, the first Msg2 can respond only to group A, the second Msg2 can respond only to group B, and the third Msg2 can respond only to group C.

[0402] Option 4: A method combining some of the above options (Options 1 through 3).

[0403] - Example of combination method 1 (example 1)

[0404] If Msg0 indicates a frequency position (e.g., by the value of R) for the first time resource, devices can expect that the first Msg2 may include only the response to Msg1 corresponding to the range from the indicated frequency position of the first time resource to the lowest or highest frequency position of the first time resource.

[0405] If Msg0 does not indicate a frequency position (e.g., by the value of R) for the first time resource, devices can expect that the first Msg2 may include only the response to Msg1 corresponding to the range from the lowest or highest frequency position of the first time resource to the center of the frequency position of the first time resource.

[0406] Subsequently, devices can expect that the second Msg2 may include only the response to Msg1 corresponding to the remaining frequency positions among the frequency positions of the first time resource that are not covered by the first Msg2.

[0407] Subsequently, devices can expect that the third Msg2 may contain only the response to Msg1 corresponding to the second time resource.

[0408] - Example of combination method 2

[0409] If Msg0 indicates a frequency position (e.g., by the value of R) for a second time resource, devices can expect that the second Msg2 may include only the response to Msg1 corresponding to the range from the indicated frequency position of the second time resource to the lowest or highest frequency position of the second time resource.

[0410] If Msg0 does not indicate a frequency position (e.g., by the value of R) for a second time resource, devices can expect that the second Msg2 may include only the response to Msg1 corresponding to the range from the lowest or highest frequency position of the second time resource to the center of the frequency position of the second time resource.

[0411] Subsequently, devices can expect that the third Msg2 may include only the response to Msg1 corresponding to the remaining frequency positions among the remaining frequency positions of the second time resource that were not covered by the second Msg2.

[0412] Subsequently, the devices assume that the first Msg2 can only contain a response to Msg1 corresponding to the first time resource.

[0413] [Method #4] Msg2-Msg3 Scheduling Method

[0414] FIG. 15 is an example illustrating scheduling methods for Msg2-Msg3 according to an embodiment of the present specification. Specifically, with reference to FIG. 15, i) Case 1, in which one Msg2 PRDCH schedules frequency division multiplexed (FDMed) Msg3 PDRCHs; ii) Case 2, in which multiple Msg2 PRDCHs schedule FDMed Msg3 PDRCHs; and iii) Case 3, in which Msg2 and Msg3 are interleaved, are illustrated.

[0415] The present specification describes the operation of the device for Case 2 and Case 3 among the scheduling methods (Case 1 to Case 3) shown in FIG. 15.

[0416] For one inventory round associated with a specific transaction ID, when an RA corresponding to Case 2 of FIG. 15 is triggered and the device transmits Msg1, the first Msg2 may schedule Msg3 of the first frequency resource (e.g., Msg3 with a high frequency position or Msg3 with a low frequency position in Case 2 of FIG. 15), and the second Msg2 may schedule the transmission of Msg3 of the second frequency resource (e.g., Msg3 with a low frequency position or Msg3 with a high frequency position in Case 2 of FIG. 15). In this case, the condition that the first T_R2D value indicated by the first Msg2 (in other words, the time interval between the transmission of Msg2 and the transmission of Msg3) must be longer than the transmission length of the second Msg2 may be satisfied. To this end, the reader can indicate / transmit to the device via Msg0 or Msg2 i) whether the above Case is Case 1, Case 2, or Case 3 and ii) the transmission length of the second Msg2.

[0417] For example, if the first T_R2D value indicated by the first Msg2 does not satisfy the above condition, the device may expect that the second Msg2 will not be transmitted during the first T_R2D. For example, a device that transmitted Msg1 may determine that the device’s transmission of Msg1 has failed if the first Msg2 does not contain a response to the Msg1 it transmitted and the first T_R2D value does not satisfy the above condition.

[0418] For example, if the first T_R2D value indicated by the first Msg2 does not satisfy the above condition, the device may resend Msg1 when it receives Msg0 or Msg2 indicating (or related to) a transaction ID that is the same as or different from a specific transaction ID.

[0419] Alternatively, if the first T_R2D value indicated by the first Msg2 does not satisfy the above conditions, the device determines that the scheduling of Case 2 has been switched to another Case (e.g., Case 3) and can expect that the response to the Msg1 it sent will be sent to the next Msg2.

[0420] For example, even if the first T_R2D value satisfies the above condition, if the second Msg2 is not received within the first T_R2D value, the device determines that the transmission of Msg1 has failed and may retransmit Msg1 upon receiving the next Msg0 or Msg2.

[0421] Alternatively, if the first T_R2D value satisfies the above condition but the second Msg2 is not received within the first T_R2D value, the device may expect Msg2 to be transmitted again after the transmission of Msg3 scheduled by the first Msg2. In this case, if the device receives Msg0, the device determines that the transmission of Msg1 has failed and may retransmit Msg1 based on the received Msg0.

[0422] Alternatively, if the first T_R2D value satisfies the above conditions but the second Msg2 is not received within the first T_R2D value, the device determines that the scheduling of Case 2 has been switched to another Case (e.g., Case 3) and can expect that a response to the Msg1 it transmitted will be transmitted as the next Msg2.

[0423] In the case of Case 2 above, the reader may transmit / instruct the device via Msg0 or Msg2 i) whether the case is Case 1, Case 2, or Case 3, and ii) the transmission length of all Msg2(s) after the first Msg2 (e.g., the transmission length of the second Msg2 if only the second Msg2 is transmitted after the first Msg2). In this case, the device may calculate the first T_R2D value (the time interval between the transmission of the first Msg2 and the transmission of the Msg3 scheduled as a result thereof) by adding a gap to the transmission length of all Msg2(s) after the first Msg2.

[0424] For example, if only the second Msg2 is transmitted after the first Msg2, the device can calculate the time interval between the transmission of the first Msg2 and the Msg3 transmission scheduled as a result by adding a gap to the transmission length of the second Msg2. Subsequently, the device can transmit Msg3 according to the calculated value.

[0425] For example, the gap may be indicated by Msg0 or Msg2 or pre-defined. Additionally, the gap may include i) the minimum value of T_R2D_R2D, the maximum value of T_R2D_R2D and / or a specific value, or ii) the minimum value of T_R2D_R2D, the maximum value of T_R2D_R2D and / or a specific value.

[0426] For example, T_R2D_R2D is the required time interval between R2D transmissions, which may represent a minimum, maximum, or specific time interval required between different Msg2 transmissions. As a specific example, if N Msg2 transmissions occur, the device may calculate the gap by considering N-1 T_R2D_R2D values. Additionally, a specific time interval for processing the Nth-to-last Msg2 transmission may be additionally included in the gap.

[0427] For the cases 2 and 3 above, each Msg2 PRDCH may indicate i) which Msg2 PRDCH it is after the transmission of Msg1 triggered by Msg0, ii) whether it is the last Msg2 PRDCH, or iii) whether there are any remaining Msg2 PRDCH transmissions after the transmission of the Msg2 PRDCH.

[0428] For example, if a device transmits Msg1 and knows which Msg2 PRDCH contains the response to the Msg1 it transmitted, it can determine when to receive the Msg2 PRDCH or whether to receive a positive response to the Msg1 it transmitted, according to the instructions above. For example, if a device expecting a response from the second Msg2 PRDCH receives i) the third Msg2 PRDCH or the last Msg2 PRDCH, or ii) receives a Msg2 PRDCH indicating that there will be no future Msg2 PRDCH, the device may determine that it did not receive a positive response to the Msg1 it transmitted (or determined that it received a negative response) and determine that the transmission of Msg1 and the RA process for it have failed. For example, the instructions above may be included in the L1CI or L2CI of the Msg2 PRDCH. Additionally, the above instructions may be included in the L1CI or L2CI of the Msg2 PRDCH, respectively, by i) each Msg1 resource index, ii) random ID, or iii) device ID. In other words, a Msg2 PRDCH may be the last Msg2 transmission for some devices, but the first or second Msg2 transmission for others.

[0429] For example, one bit in the R2D control information of the MSG2 PRDCH (e.g., R2D L1CI or R2D L2CI) may indicate either 'last / no Msg2' or 'second / next Msg2'.

[0430] In the above example, if the first Msg2 does not indicate the second Msg2 or if the first Msg2 indicates 'last / no Msg2', the device may not expect to receive the second Msg2.

[0431] For example, if the first Msg2 does not contain a response to the device's Msg1, the device may determine that Msg1 has failed. In this case, the device may retransmit Msg1 upon receiving a new Msg2 (new re-MSG2) that triggers subsequent paging reception or the retransmission of Msg1.

[0432] In the above example, if i) the first Msg2 indicates the second Msg2 or ii) the first Msg2 does not indicate a new Msg2 that triggers 'last / no Msg2' or Msg1 retransmission, the device can expect to receive the second Msg2.

[0433] For example, if a second Msg2 is not received prior to the reception of Msg0, which triggers Msg1, or Msg2, which triggers Msg3, the device may determine that Msg1 has failed. In this case, the device may retransmit Msg1 upon receiving Msg0 or Msg2, which triggers the retransmission of Msg1.

[0434] Meanwhile, the device that transmitted Msg1 may receive Msg2, which triggers the retransmission of Msg1 or Msg3 as follows.

[0435] For example, after T_D2Rmin from the time of the end of the transmission of Msg1, the device may expect the reception of Msg2, which triggers the transmission of Msg3 or the retransmission of Msg1.

[0436] In this case, the device may not expect to receive Msg2 that triggers the retransmission of Msg1 prior to receiving the last Msg2 PRDCH. Therefore, if the device receives Msg2 that triggers the retransmission of Msg1, it may determine that the transmission of Msg1 has failed.

[0437] In this case, T_D2Rmin can be defined as the minimum time interval required between the end time of transmission of Msg1 and the start time of transmission of Msg2.

[0438] Meanwhile, the device that transmitted Msg3 according to the above case may receive Msg2 (or Msg4) that triggers the transmission of Msg5 or the retransmission of Msg3 as follows, or receive R2D transmission that instructs to stop the currently ongoing RA.

[0439] For example, after T_D2Rmin from the end of transmission of Msg3, the device may expect to receive an R2D transmission (e.g., Msg2 or Msg4) that triggers the retransmission of Msg3 or the transmission of Msg5, or indicates the end of the current RA.

[0440] For example, if Msg2 (or Msg4) indicates the next Msg2 (or Msg4), the device may expect the reception of an R2D transmission (e.g., Msg2 or Msg4) that triggers the retransmission of Msg3 or the transmission of Msg5 after T_D2Rmin from the end of the transmission of Msg3.

[0441] For example, if Msg2 (or Msg4) does not indicate the next Msg2 (or Msg4) or if Msg2 (or Msg4) indicates the termination of the current RA, the device may not expect to receive an R2D transmission (e.g., Msg2 or Msg4) for the current RA after T_D2Rmin from the time of the end of the transmission of Msg3. In this case, the device may determine that the current RA has been terminated after the end of the transmission of Msg3.

[0442] R2D transmission for CBRA and CFA

[0443] For example, an R2D transmission such as Msg0 can trigger CBRA (Contention-based Random Access) or CFA (Contention-Free Access). In other words, an R2D transmission can trigger either CBRA or CFA. As another example, one or more R2D transmissions can trigger both CBRA and CFA simultaneously. In this case, X sub-slot time resource(s) and Y frequency resource(s) may be allocated for the RA (Random Access) triggered by one or more R2D transmissions, and the allocated time resource(s) and frequency resource(s) may be composed of the R2D transmissions that trigger the RA. In this specification, the CFA may be substituted / interpreted as CFRA (Contention-free Random Access).

[0444] According to one embodiment, when an R2D transmission indicates or triggers a CBRA or CFRA, the R2D control information included in the R2D transmission may indicate X, Y, and / or Toffset values ​​for the RA. When an R2D transmission indicates or triggers a CFRA, the R2D control information may indicate related parameters as follows.

[0445] According to one embodiment, instructions for the X value in the R2D control information that triggers CFRA may be excluded.

[0446] For example, the X value can be implicitly set to 1 for CFRA.

[0447] For example, Toffset1 can be specified. If Toffset1 is not specified, Toffset1 can be set to a default value or a specified value.

[0448] For example, in the R2D control information that triggers CFRA, both Toffset2 and Toffset3 can be omitted.

[0449] For example, the device can assume that only the first time resource is used for CFRA Msg1.

[0450] According to one embodiment, instructions for the Y value in the R2D control information that triggers CFRA may be excluded.

[0451] For example, the Y value can be implicitly set to 1 for CFRA.

[0452] For example, the R value can be specified. If the R value is not specified, R can be set to a default value, a specified value, a minimum value, or a maximum value.

[0453] At this time, an R2D transmission indicating CBRA or CFRA, or an R2D transmission indicating both CBRA and CFRA, may be one or multiple R2D transmissions. At this time, an R2D transmission indicating CBRA or CFRA, or an R2D transmission indicating both CBRA and CFRA, may indicate time / frequency resources for D2R transmission as follows.

[0454] According to one embodiment, time resources can be allocated as follows.

[0455] - Option (Opt) 1A: A single R2D transmission may indicate one or more sub-slots for CBRA and one or more sub-slots for CFRA.

[0456] - Option 1B: The first R2D transmission may indicate one or more sub-slots for CBRA, and then the second R2D transmission may indicate one or more sub-slots for CFRA. Or, the first R2D transmission may indicate one or more sub-slots for CFRA, and then the second R2D transmission may indicate one or more sub-slots for CBRA.

[0457] - In option 1B, for example, the first R2D transmission may be an A-IoT paging transmission having a transaction ID, and the second R2D transmission may be a subsequent A-IoT paging transmission having the same transaction ID as the first R2D transmission.

[0458] According to one embodiment, frequency resources can be allocated as follows.

[0459] - Option 2A: One R2D transmission can indicate one or more frequency positions for CBRA and one or more frequency positions for CFRA.

[0460] - Option 2B: The first R2D transmission may indicate one or more frequency positions for CBRA, and then the second R2D transmission may indicate one or more frequency positions for CFRA. Or, the first R2D transmission may indicate one or more frequency positions for CFRA, and then the second R2D transmission may indicate one or more frequency positions for CBRA.

[0461] - In option 2B, for example, the first R2D transmission may be an A-IoT paging transmission having a transaction ID, and the second R2D transmission may be a subsequent A-IoT paging transmission having the same transaction ID as the first R2D transmission.

[0462] i) where one or more R2D transmissions such as Msg0 indicate / trigger CBRA and CFRA respectively, or ii) where one or more R2D transmissions such as Msg0 indicate / trigger both CBRA and CFRA, the control information included in the R2D transmission may indicate RA-related parameters X, Y, and Toffset values, etc. as follows.

[0463] According to one embodiment, if one R2D transmission or two R2D transmissions (e.g., a first R2D transmission and a second R2D transmission) indicate X>1 for CBRA and / or CFRA, the reader and the device may perform one or more of the following options and examples.

[0464] - Option A1: One or more specific sub-slots are explicitly or implicitly allocated for CBRA, and the remaining sub-slot(s) may be implicitly allocated for CFRA. Examples for Option A1 may be as follows.

[0465] - Example 1: When X=2, if the first sub-slot is implicitly allocated for CBRA, the remainder (the second sub-slot) can be implicitly allocated for CFRA.

[0466] - Example 2: When X=2, if the first sub-slot is (explicitly) allocated for CBRA based on the instructions of the R2D control information, the remainder (the second sub-slot) may be implicitly allocated for CFRA.

[0467] - Example 3: When X=2, if the second sub-slot is (explicitly) allocated for CBRA based on the instructions of the R2D control information, the remainder (the first sub-slot) may be implicitly allocated for CFRA.

[0468] For example, in the above examples (e.g., Examples 1 to 3 for Option A1), if the R2D control information does not indicate a sub-slot allocated for CBRA, the following alternatives may be considered.

[0469] - Alternative (Alt) 1: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for CBRA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for CFRA.

[0470] - Alternative 2: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for CFRA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for CBRA.

[0471] For example, if the first R2D transmission triggers CBRA and then the second R2D transmission triggers CFRA, or if the first R2D transmission triggers CFRA and then the second R2D transmission triggers CBRA, the following alternatives may be considered.

[0472] - Alternative 1: The first R2D transmission may indicate Toffset1, and the second R2D transmission may indicate Toffset2 and / or Toffset3.

[0473] - In the above alternative 1, when the first R2D transmission is received, the device to which the first sub-slot is allocated for RA can transmit Msg1 in the first sub-slot.

[0474] - In the above alternative 1, when the second R2D transmission is received, the device allocated the second sub-slot for RA can transmit Msg1 in the second sub-slot.

[0475] - For example, if a parameter related to an RA triggered by a second R2D transmission is indicated / set by a first R2D transmission and is not explicitly indicated in the second R2D transmission, the device may apply the parameter indicated / set by the first R2D transmission to the RA triggered by the second R2D transmission.

[0476] - Alternative 2: The first R2D transmission may indicate Toffset2 and Toffset3, and the second R2D transmission may indicate Toffset1.

[0477] - In the above alternative 2, when the second R2D transmission is received, the device in which either the first sub-slot or the second sub-slot is allocated for RA transmits Msg1 in either the first sub-slot or the second sub-slot.

[0478] - Option A2: One or more specific sub-slots may be explicitly or implicitly allocated for CFRA, and the remaining sub-slot(s) may be implicitly allocated for CBRA. Examples for Option A2 may be as follows.

[0479] - Example 1: When X=2, if the first sub-slot is implicitly allocated for CFRA, the remainder (the second sub-slot) can be implicitly allocated for CBRA.

[0480] - Example 2: When X=2, if the first sub-slot is (explicitly) allocated for CFRA based on the instructions of the R2D control information, the remainder (the second sub-slot) may be implicitly allocated for CBRA.

[0481] - Example 3: When X=2, if the second sub-slot is (explicitly) allocated for CFRA based on the instructions of the R2D control information, the remainder (the first sub-slot) may be implicitly allocated for CBRA.

[0482] For example, in the above examples (e.g., Examples 1 to 3 for Option A2), if the R2D control information does not indicate a sub-slot allocated for CFRA, the following alternatives may be considered.

[0483] - Alternative 1: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for CBRA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for CFRA.

[0484] - Alternative 2: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for CFRA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for CBRA.

[0485] According to one embodiment, if one R2D transmission or two R2D transmissions (e.g., a first R2D transmission and a second R2D transmission) indicate Y>1 ​​for CBRA and / or CFRA, the reader and the device may perform one or more of the following options and examples.

[0486] - Option B1: One or more specific frequency locations are explicitly or implicitly allocated for CBRA, and the remaining frequency location(s) may be implicitly allocated for CFRA. Examples for Option B1 may be as follows.

[0487] - Example 1: When Y=2, if the first frequency position is implicitly assigned for CBRA, the remainder (second frequency position) can be implicitly assigned for CFRA.

[0488] - Example 2: When Y=2, if the first frequency position is (explicitly) assigned for CBRA based on the instructions of the R2D control information, the remainder (second frequency position) may be implicitly assigned for CFRA.

[0489] - Example 3: When Y=2, if the second frequency position is (explicitly) assigned for CBRA based on the instructions of the R2D control information, the remainder (first frequency position) may be implicitly assigned for CFRA.

[0490] - For example, in the above examples (e.g., Examples 1 to 3 for Option B1), if the R2D control information does not indicate the frequency position allocated for CBRA, the following alternatives may be considered.

[0491] - Alternative 1: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for CBRA, and the rest (e.g., a second frequency position) may be implicitly allocated for CFRA.

[0492] - Alternative 2: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for CFRA, and the rest (e.g., a second frequency position) may be implicitly allocated for CBRA.

[0493] - Option B2: One or more specific frequency positions may be explicitly or implicitly allocated for CFRA, and the remaining frequency position(s) may be implicitly allocated for CBRA. Examples for Option B2 may be as follows.

[0494] - Example 1: When Y=2, if the first frequency position is implicitly assigned for CFRA, the remainder (second frequency position) can be implicitly assigned for CBRA.

[0495] - Example 2: When Y=2, if the first frequency position is (explicitly) assigned for CFRA based on the instructions of the R2D control information, the remainder (second frequency position) may be implicitly assigned for CBRA.

[0496] - Example 3: When Y=2, if the second frequency position is (explicitly) assigned for CFRA based on the instructions of the R2D control information, the remainder (first frequency position) may be implicitly assigned for CBRA.

[0497] For example, in the above examples (e.g., Examples 1 through 3 for Option B2), if the R2D control information does not indicate the frequency position allocated for CFRA, the following alternatives may be considered.

[0498] - Alternative 1: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for CBRA, and the rest (e.g., a second frequency position) may be implicitly allocated for CFRA.

[0499] - Alternative 2: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for CFRA, and the rest (e.g., a second frequency position) may be implicitly allocated for CBRA.

[0500] In this specification, the first frequency position may mean any one of the lowest frequency position(s), the highest frequency position, and / or a specific frequency position that is predefined or indicated by R2D transmission.

[0501] R2D transmission for Device Type 1 and Advanced Device Type(s)

[0502] For example, in this specification, advanced device type(s) may include device type(s) for the wireless communication specification version Release-20 (Rel-20) defined by 3GPP.

[0503] For example, an R2D transmission such as Msg0 may trigger different RAs (e.g., the first RA and the second RA of this specification) for different types of devices. For example, an R2D transmission may trigger a first RA (first RA) for device type 1 and a second RA (second RA) for an advanced device such as device type 2 simultaneously or at a time interval. Alternatively, an R2D transmission may trigger a first RA for a Rel-19 device and a second RA for an advanced device such as a Rel-20 device simultaneously or at a time interval.

[0504] According to one embodiment, one or more R2D transmissions may simultaneously trigger RAs for different device types or trigger only one device type's RA at a time. In this case, X sub-slot time resources and Y frequency resources may be allocated for the RAs triggered by one or more R2D transmissions, and the time resource(s) and / or frequency resource(s) may be composed of the R2D transmissions that trigger the RAs.

[0505] At this time, an R2D transmission indicating the first RA or the second RA, or an R2D transmission indicating both the first RA and the second RA, may be one or multiple R2D transmissions. An R2D transmission indicating the first RA or the second RA, or an R2D transmission indicating both the first RA and the second RA, may indicate time / frequency resources for D2R transmission as follows.

[0506] According to one embodiment, time resources can be allocated as follows.

[0507] - Option 1A: One R2D transmission may indicate one or more sub-slots for the first RA for device type 1 and one or more sub-slots for the second RA for advanced device type(s). Or, one R2D transmission may indicate one or more sub-slots for the first RA for Rel-19 devices and one or more sub-slots for the second RA for other devices Rel-20 and later.

[0508] - Option 1B: The first R2D transmission may indicate one or more sub-slots for the first RA, and the subsequent second R2D transmission may indicate one or more sub-slots for the second RA. Or, the first R2D transmission may indicate one or more sub-slots for the second RA, and the subsequent second R2D transmission may indicate one or more sub-slots for the first RA.

[0509] - In option 1B, for example, the first R2D transmission may be an A-IoT paging transmission including a transaction ID, and the second R2D transmission may be a subsequent A-IoT paging transmission having the same transaction ID as the first R2D transmission.

[0510] According to one embodiment, frequency resources can be allocated as follows.

[0511] - Option 2A: A single R2D transmission can indicate one or more frequency positions for the first RA and one or more frequency positions for the second RA.

[0512] - Option 2B: A first R2D transmission may indicate one or more frequency positions for the first RA, and a second R2D transmission may indicate one or more frequency positions for the second RA. Or, a first R2D transmission may indicate one or more frequency positions for the second RA, and a second R2D transmission may indicate one or more frequency positions for the first RA.

[0513] - In option 2B, for example, the first R2D transmission may be an A-IoT paging transmission including a transaction ID, and the second R2D transmission may be a subsequent A-IoT paging transmission having the same transaction ID as the first R2D transmission.

[0514] i) when one or more R2D transmissions such as Msg0 indicate / trigger the first RA and the second RA respectively, or ii) when one or more R2D transmissions such as Msg0 indicate / trigger both the first RA and the second RA, the control information included in the R2D transmission may indicate RA-related parameters X, Y, and Toffset values, etc. as follows.

[0515] According to one embodiment, one R2D transmission or two R2D transmissions (e.g., a first R2D transmission and a second R2D transmission) indicate one or more sub-slots for a first RA and / or one or more sub-slots for a second RA, and according to one embodiment, when one R2D transmission or two R2D transmissions (e.g., a first R2D transmission and a second R2D transmission) indicate X>1 for the first RA and / or the second RA, the reader and the device may perform one or more of the following options and examples.

[0516] - Option A1: One or more specific sub-slots are explicitly or implicitly allocated for the first RA, and the remaining sub-slot(s) may be implicitly allocated for the second RA. Examples for Option A1 may be as follows.

[0517] - Example 1: When X=2, if the first sub-slot is implicitly allocated for the first RA, the remainder (the second sub-slot) can be implicitly allocated for the second RA.

[0518] - Example 2: When X=2, if the first sub-slot is allocated (explicitly) for the first RA based on the instructions of the R2D control information, the remainder (the second sub-slot) may be implicitly allocated for the second RA.

[0519] - Example 3: When X=2, if the second sub-slot is allocated (explicitly) for the first RA based on the instructions of the R2D control information, the remainder (the first sub-slot) may be implicitly allocated for the second RA.

[0520] For example, in the above examples (e.g., Examples 1 to 3 for Option A1), if the R2D control information does not indicate the sub-slot allocated for the first RA, the following alternatives may be considered.

[0521] - Alternative 1: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for the first RA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for the second RA.

[0522] - Alternative 2: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for the second RA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for the first RA.

[0523] - Option A2: One or more specific sub-slots are explicitly or implicitly allocated for the second RA, and the remaining sub-slot(s) may be implicitly allocated for the first RA.

[0524] - Example 1: When X=2, if the first sub-slot is implicitly allocated for the second RA, the remainder (the second sub-slot) can be implicitly allocated for the first RA.

[0525] - Example 2: When X=2, if the first sub-slot is (explicitly) allocated for the second RA based on the instructions of the R2D control information, the remainder (the second sub-slot) may be implicitly allocated for the first RA.

[0526] - Example 3: When X=2, if the second sub-slot is (explicitly) allocated for the second RA based on the instructions of the R2D control information, the remainder (the first sub-slot) may be implicitly allocated for the first RA.

[0527] In the above examples (e.g., Examples 1 through 3 for Option A2), if the R2D control information does not indicate a sub-slot allocated for the second RA, the following alternatives may be considered.

[0528] - Alternative 1: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for the first RA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for the second RA.

[0529] - Alternative 2: A specific sub-slot (e.g., the first sub-slot) may be implicitly allocated for the second RA, and the remainder (e.g., the second sub-slot) may be implicitly allocated for the first RA.

[0530] According to one embodiment, if one R2D transmission or two R2D transmissions (e.g., a first R2D transmission and a second R2D transmission) indicate one or more frequency positions for a first RA and / or one or more frequency positions for a second RA, and if one R2D transmission or two R2D transmissions indicate Y>1 ​​for the first RA and / or second RA, the reader and the device may perform one or more of the following options and examples.

[0531] - Option B1: One or more specific frequency positions are explicitly or implicitly assigned for the first RA, and the remaining frequency position(s) may be implicitly assigned for the second RA. Examples for Option B1 may be as follows.

[0532] - Example 1: When Y=2, if the first frequency position is implicitly allocated for the first RA, the remainder (second frequency position) can be implicitly allocated for the second RA.

[0533] - Example 2: When Y=2, if the first frequency position is assigned (explicitly) for the first RA based on the instructions of the R2D control information, the remainder (second frequency position) may be implicitly assigned for the second RA.

[0534] - Example 3: When Y=2, if the second frequency position is (explicitly) assigned for the first RA based on the instructions of the R2D control information, the remainder (first frequency position) may be implicitly assigned for the second RA.

[0535] - For example, in the above examples (e.g., Examples 1 to 3 for Option B1), if the R2D control information does not indicate the frequency position allocated for the first RA, the following alternatives may be considered.

[0536] - Alternative 1: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for the first RA, and the rest (e.g., a second frequency position) may be implicitly allocated for the second RA.

[0537] - Alternative 2: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for the second RA, and the remainder (e.g., a second frequency position) may be implicitly allocated for the first RA.

[0538] - Option B2: One or more specific frequency positions are explicitly or implicitly allocated for the second RA, and the remaining frequency position(s) may be implicitly allocated for the first RA. Examples for Option B1 may be as follows.

[0539] - Example 1: When Y=2, if the first frequency position is implicitly assigned for the second RA, the remainder (second frequency position) can be implicitly assigned for the first RA.

[0540] - Example 2: When Y=2, if the first frequency position is assigned (explicitly) for the second RA based on the instructions of the R2D control information, the remainder (the second frequency position) may be implicitly assigned for the first RA.

[0541] - Example 3: When Y=2, if the second frequency position is assigned (explicitly) for the second RA based on the instructions of the R2D control information, the remainder (first frequency position) may be implicitly assigned for the first RA.

[0542] - For example, in the above examples (e.g., Examples 1 to 3 for Option B2), if the R2D control information does not indicate the frequency position allocated for the second RA, the following alternatives may be considered.

[0543] - Alternative 1: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for the first RA, and the rest (e.g., a second frequency position) may be implicitly allocated for the second RA.

[0544] - Alternative 2: A specific frequency position (e.g., a first frequency position) may be implicitly allocated for the second RA, and the remainder (e.g., a second frequency position) may be implicitly allocated for the first RA.

[0545] Control information and PRDCH or PDRCH transmission structure method

[0546] FIG. 16 is an example showing various transmission structures of control information and PRDCH / PDRCH according to an embodiment of the present specification.

[0547] FIG. 17 is an example showing the transmission structure of preamble / postamble and PRDCH / PDRCH according to an embodiment of the present specification.

[0548] Referring to FIG. 16, various options for i) control information and ii) the transmission structure of PRDCH or PDRCH according to an embodiment of the present specification (e.g., see 'a' to 'e' in FIG. 16). In FIG. 16, each transmission option may be transmitted immediately after the preamble. Additionally, a postamble may be transmitted immediately after the transmission of each transmission option. For example, if the PRDCH or PDRCH transmission of option a) or option b) of FIG. 16 is transmitted including a preamble and / or a postamble, it may be transmitted as in the example shown in FIG. 17.

[0549] As shown in FIG. 16, R2D / D2R Layer 1 control information (R2D / D2R L1 control information) can be transmitted in one of the following ways. For convenience of explanation in this specification, L1 control information is described using R2D transmission as an example, but the L1 control information of this specification can be applied equally to D2R transmission.

[0550] - Alternative 1: L1 control information can be located at the end of the preamble as part of the R2D preamble.

[0551] In Alternative 1, the chip duration of the L1 control information may be the same as the chip duration of the preamble.

[0552] For example, L1 control information may be added immediately after the clock acquisition part of Fig. 16, and then PRDCH may be transmitted.

[0553] - Alternative 2: L1 control information can be located between the R2D preamble and PRDCH.

[0554] At this time, the transmission structure of PRDCH may be the same as option c), d), or e) of Fig. 16.

[0555] For example, if the transmission structure of PRDCH is like option d), L1 control information can be transmitted through a separate R2D control channel.

[0556] For example, if the transmission structure of PRDCH is like option c) or e), L1 control information can be transmitted as a separate part without a separate channel.

[0557] - Alternative 3: L1 control information can be located at the beginning of PRDCH as part of PRDCH.

[0558] In Alternative 3, the chip duration of the L1 control information may be the same as the chip duration of the PRDCH.

[0559] At this time, the transmission structure of PRDCH may be the same as option b) in Fig. 16, and in option b) of Fig. 16, PRDCH may start with L1 control information.

[0560] FIG. 18 is an example showing various MAC payload structures according to embodiments of the present specification.

[0561] In Fig. 18, the MAC payload may correspond to a single transport block.

[0562] According to one embodiment, in options a), c), and d) of FIG. 18, the L2 control information may be located at the beginning of the MAC payload. According to another embodiment, the L2 control information may not be located at the beginning of the MAC payload.

[0563] For example, the clock acquisition part of the L1 control information or preamble of FIG. 16 may indicate that the L2 control information is included in the MAC payload or that the L2 control information is not included in the MAC payload.

[0564] As another example, without separate instructions, the MAC payload may or may not always include L2 control information.

[0565] As another example, the first bit / field of the L2 control information or the bit / field immediately preceding the L2 control information may indicate whether the L2 control information is included in the MAC payload or whether the L2 control information is not included in the MAC payload.

[0566] According to one embodiment, a MAC control element (MAC Control Element, MAC CE) following the MAC subheader of FIG. 18 may include L2 control information.

[0567] According to one embodiment, padding may be added to the last part of the payload of FIG. 18.

[0568] When a payload (or transmission block (TB)) is configured at the MAC layer as per the options of FIG. 18 (see options 'a' through 'd' of FIG. 18), the TB is transmitted to the physical layer, and the physical layer can configure PRDCH or PDRCH transmission by adding a CRC to the TB. At this time, L1 control information, L2 control information, or MAC CE may indicate whether a CRC is added to the TB. In FIG. 18, L2 control information may be classified as a specific MAC CE that is always located before the payload or as a MAC header.

[0569] FIG. 19 is an example illustrating D2R transmission and midamble transmission according to an embodiment of the present specification.

[0570] According to one embodiment, a reader transmitting a PRDCH may or may not include L1 control information (L1CI) within the PRDCH. In this case, the R2D L1CI transmitted to the R2D may include control information for PRDCH transmission and / or control information for PDRCH transmission.

[0571] According to one embodiment, the reader may or may not include L2 control information (L2CI) within the PRDCH. In this case, the R2D L2CI transmitted to the R2D may include control information for PRDCH transmission and / or control information for PDRCH transmission.

[0572] According to one embodiment, a device transmitting a PDRCH may or may not include L1 control information (L1CI) within the PDRCH. In this case, the D2R L1CI transmitted to the D2R may include control information for the PDRCH transmission, control information for subsequent PRDCH transmission, and / or information reported to the reader. For example, the information reported to the reader may include a buffer status, a remining D2R data size, and / or a device energy status / level.

[0573] According to one embodiment, the device may or may not include L2 control information (L2CI) within the PDRCH. In this case, the D2R L2CI transmitted to the D2R may include control information for PDRCH transmission, control information for PRDCH transmission, and / or information reported to the reader. For example, the information reported to the reader may include buffer status, remining D2R data size, and / or device energy status / level. For example, the L2CI may be a MAC CE included in the MAC PDU, a MAC header / MAC sub-header, or part of a MAC CE / MAC header / MAC sub-header.

[0574] [Method #5] L2 R2D control information with a separate CRC

[0575] When L2CI is included in a MAC PDU of PRDCH or PDRCH, the L2CI and the remaining parts constituting a single MAC PDU are separated, and a reader or device transmitting the MAC PDU can construct a single MAC PDU by separately generating CRC1 for the L2CI and CRC2 for the remaining parts.

[0576] For example, when transmitting the corresponding PRDCH or PDRCH, the bits for L2CI can be placed at the beginning in time.

[0577] For example, if the MAC PDU is a PRDCH, the device may first decode the L2CI portion before completing reception of the MAC PDU, and receive the PRDCH transmission to the end and process the MAC PDU only if i) the CRC check for the L2CI passes, and ii) it is determined that the PRDCH is the PRDCH that the device is supposed to receive based on the L2CI. For example, if the CRC check for the L2CI does not pass, or if it is determined that the PRDCH is not the PRDCH that the device is supposed to receive based on the L2CI, the device may not receive the PRDCH transmission to the end and may not process the MAC PDU.

[0578] For example, if the MAC PDU is a PDRCH, the reader may first decode the L2CI portion before completing reception of the MAC PDU, and receive the PDRCH transmission to the end and process the MAC PDU only if i) the CRC check for the L2CI passes, and ii) the PDRCH is determined to be a PDRCH that the reader is supposed to receive based on the L2CI. For example, if the CRC check for the L2CI does not pass, or if the PDRCH is determined not to be a PDRCH that the reader is supposed to receive based on the L2CI, the reader may not receive the PDRCH transmission to the end and may not process the MAC PDU.

[0579] For example, the L2CI method(s) described above may be applied only to specific message types. For example, the L2CI method(s) described above may be applied only to Msg2 or only to Msg0, or ii) only to R2D messages for a specific device. Alternatively, the L2CI method(s) described above may be applied only to D2R and not to R2D, or ii) only to R2D and not to D2R.

[0580] For example, the L2CI method(s) described above may be applied only when the corresponding PRDCH or PDRCH does not contain L1CI. For example, if the corresponding PRDCH or PDRCH contains L1CI, the reader or device may generate and attach a separate CRC1 only to the L1CI and generate and attach a CRC2 to the entire MAC PDU to transmit the corresponding PRDCH or PDRCH.

[0581] [Method #6] R2D Control Information for Msg2 and Msg4

[0582] PRDCH or PDRCH may include an indicator that specifies a message type (msg type). For example, the msg type indicator may indicate only specific msg type(s) and not the remaining msg type(s), or indicate only other msg type(s). In this case, the msg type indicator may be included in the L1CI or L2CI of the corresponding channel.

[0583] For example, in the case of PRDCH, the msg type indicator included in PRDCH may indicate one, some, or all of Msg0, Msg2, and Msg4, and the remaining msg types may not be indicated or may be indicated only as other msg type. If other msg type is indicated, the receiving device may determine that the R2D message is a broadcast message that all devices must decode.

[0584] Meanwhile, a reader that has received one or more Msg1s with X sub-slots and Y frequency resources may transmit a PRDCH instructed by Msg2 to some or all of the corresponding device(s). In this case, the reader detects the transmission of Msg1, and if the CRC included in the transmission of Msg1 passes, it may include a positive response in Msg2. For example, if the reader detects the transmission of Msg1 but the CRC included in the transmission of Msg1 does not pass, it may include a negative response in Msg2 or not include a response in Msg2.

[0585] For example, a msg type indicating Msg2 may be included in the L1CI or L2CI of PRDCH. In this case, if the Msg2 responds positively to N Msg1s, the value of N may be included in the L1CI or L2CI, and for each positive response, the resource index value of the corresponding Msg1 resource may be further included in the said L1CI or L2CI.

[0586] For example, if the Msg2 contains both positive and negative responses for N Msg1s, the value of N may be included in L1CI or L2CI, and for each response to the positive and / or negative responses, the resource index value of the corresponding Msg1 resource may be included in the said L1CI or L2CI.

[0587] For example, the resource index value can be calculated as follows.

[0588] - Alternative 1: Msg1 resource index = (y-1) + Y*(x-1), where x is 1 to X and y is 1 to Y.

[0589] - Alternative 2: Msg1 resource index = y + Y*X, where x is 0 to X-1 and y is 0 to Y-1.

[0590] Meanwhile, if the L1CI of the PRDCH of Msg2 indicates some or all of the msg type, N value, and resource index, the L2CI of the corresponding PRDCH may include an ID obtained from Msg1 for a positive response. In this case, if the L1CI indicates 'resource index = 1, 2, … , N', the L2CI may be configured to include IDs obtained from the corresponding resource index within the L2CI according to the ascending or descending order of the resource index values ​​in the L1CI, or the same order in which the resource index within the L1CI is included. In this case, the obtained ID may be a random ID or a device ID. For example, if a random ID is included in the L2CI, the reader may transmit the PRDCH by including a newly assigned device ID for each random ID in the L2CI. In this case, the reader may configure the L2CI by attaching (or adding) the device ID after all random IDs have been listed up, or by attaching the device ID immediately following each random ID. For example, if the reader obtains a device ID via Msg1, the reader may append the obtained device ID to the random ID location. In this case, the newly assigned device ID may not be appended separately to the random ID, or the newly assigned device ID may be appended (as above), or a dummy field may be appended. In this case, the dummy field may be filled with a specific reserved ID value.

[0591] For example, a device that receives the PRDCH of Msg2 first decodes the L1CI. If the CRC1 of the L1CI passes and the resource index of the Msg1 it transmitted is included within the L1CI, the device can process the corresponding MAC PDU to obtain the L2CI from the MAC PDU. Subsequently, if the ID value corresponding to the sequence of the resource index of the Msg1 it transmitted matches the ID value included in the Msg1 it transmitted, the device can determine that the transmission of Msg1 was successful. Alternatively, if the ID value corresponding to the sequence of the resource index of the Msg1 it transmitted does not match the ID value included in the Msg1 it transmitted, the device can determine that the transmission of Msg1 failed. For example, if the device determines that the transmission of Msg1 was successful and the corresponding L1CI or L2CI allocates a D2R resource for Msg3, the device transmits Msg3.

[0592] For example, if a device transmits Msg3 and the msg type indicator of a subsequently received PRDCH indicates Msg4, the device may determine that the transmission of Msg3 was successful only if the L1CI or L2CI of the corresponding PRDCH indicates the device ID of the device; otherwise (e.g., if it does not indicate the device ID of the device), the device may determine that the transmission of Msg3 failed. In this case, the device may expect the transmission of a new Msg2 indicating the retransmission of Msg3, and may retransmit Msg3 if the L1CI or L2CI of such Msg2 transmission allocates D2R resources for the transmission of Msg3 as described above.

[0593] [Method #7] How to handle invalid / reserved values

[0594] The device receives a PRDCH and, if i) an event occurs indicating that a specific field of the L1CI or L2CI of the received PRDCH is an invalid value or a reserved value, or ii) an event occurs indicating that a combination of value(s) of specific field(s) of the L1CI and / or L2CI of the PRDCH is invalid, it may perform one of the following actions. For example, the specific field may indicate an R2D message type. In this case, the R2D message type may be indicated as any one of a plurality of R2D message type values. In this specification, the reserved value may refer to a value that is not currently used in the standard but is reserved for future use. Additionally, the reserved value may include a value not currently defined in the standard.

[0595] - Option 1: The device may ignore the entire PRDCH where the above event occurred. In other words, the PRDCH where the above event occurred may be discarded.

[0596] For example, the device may continue the current RA process based on subsequent R2D transmissions. For example, i) if the device receives Msg0 again for the same inventory round later, the device may trigger RA, and ii) if the device receives Msg2, the device may retransmit Msg3.

[0597] - Option 2: The device may determine that the entire RA process associated with the PRDCH where the above event occurred has failed.

[0598] For example, if the PRDCH is Msg0 that triggers a specific RA, or Msg2 or Msg4 of the RA process, the device may determine that the RA has failed.

[0599] At this time, the device may stop only the corresponding RA and continue the corresponding inventory round. For example, if the device receives Msg0 for the same inventory round, it may trigger the RA for that round and send Msg1. At this time, all Msg0s for the same inventory round may indicate the same transaction ID or be associated with the same transaction ID.

[0600] As another example, the device can suspend both the corresponding RA and the corresponding inventory round. For instance, if the device receives a Msg0 for the same inventory round, it may not trigger the RA for that round, but may trigger the RA only when it receives a Msg0 for a different inventory round. In this case, the Msg0s for different inventory rounds may indicate different transaction IDs or be associated with different transactions.

[0601] According to one embodiment, the device may transmit Msg1 (Access Random ID message) based on an access occasion selected from among access occasions set for the transmission of Msg1 (Access Random ID message). For example, the access occasion may be indicated by Msg0 (e.g., an A-IoT Paging message or an Access Trigger message) that triggers a random access procedure. For example, the access occasion may be selected based on a count-down behavior. In this case, the count-down behavior may be performed as follows.

[0602] First, for selecting an access occasion, the access opportunity counter (ACCESS_OCCASION_COUNTER) may be set to a specific value (e.g., i). Subsequently, if the value of the access opportunity counter is less than a specific value (e.g., m), the device may select the 'value of the access opportunity counter + 1'th access occasion among the m access occasions triggered by Msg0, and transmission of Msg1 may be initiated based on the selected access occasion. If the value of the access opportunity counter is equal to or greater than m, the device may subsequently decrease the value of the access opportunity counter by m each time it receives an R2D message (e.g., an Access Trigger message), and if the value of the access opportunity counter becomes less than m through this process, the device may select the 'value of the access opportunity counter + 1'th access occasion among the m access occasions triggered by the corresponding R2D message, and transmission of Msg1 may be initiated based on the selected access occasion.

[0603] In other words, the device may decrease the stored Q value (in other words, i in the countdown operation described above) upon receiving Msg0, and trigger RA when the Q value reaches a specific value. At this time, the countdown operation may or may not be performed depending on the PRDCH in which the event occurred. For example, the countdown operation may be performed even if the event occurs on a PRDCH received by the device. Alternatively, if the event occurs on a PRDCH received by the device, the corresponding PRDCH is ignored, so the countdown operation may not be performed. As a specific example, regarding the PRDCH in which the event occurred, the device may decrease the Q value or not decrease the Q value.

[0604] For example, if the following cases occur in L1CI and / or L2CI, the device may perform the actions of Option 1 and / or Option 2 above.

[0605] - When the D2R iteration count instruction within the R2D control information and the number of sub-slots X greater than a specific value are indicated simultaneously

[0606] - When the long preamble and short midamble of D2R in R2D control information are indicated simultaneously

[0607] - If a combination consisting of some or all of the D2R chip durations, R values, and D2R bit durations values ​​in the R2D control information is invalid, or if a specific value among the D2R chip durations, R values, and D2R bit durations values ​​is invalid

[0608] Various embodiments of the present specification (e.g., methods 1 to 7) may be combined with each other.

[0609] In terms of implementation, the operations of the first device (e.g., Reader, base station (BS), intermediate node (IN), auxiliary node (AN), terminal (UE) / Ambient IoT Device) / second device (e.g., Ambient IoT Device / Reader, base station, intermediate node, auxiliary node, terminal) according to the embodiments described above can be processed by the device of FIG. 22 (e.g., the processor (110, 210) of FIG. 22).

[0610] In addition, the operations of the first device (e.g., Reader, base station, intermediate node, auxiliary node, terminal / Ambient IoT Device) / second device (e.g., Ambient IoT Device / Reader, base station, intermediate node, auxiliary node, terminal) according to the above-described embodiment may be stored in memory (e.g., 140, 240 of FIG. 22) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., processor (110, 210) of FIG. 22).

[0611] The embodiments described above will be explained in detail below with reference to FIGS. 20 and 21 in terms of the operation of a first device (e.g., Reader, base station, intermediate node, auxiliary node, terminal / Ambient IoT Device) and a second device (e.g., Ambient IoT Device / Reader, base station, intermediate node, auxiliary node, terminal). The methods described below are distinguished only for convenience of explanation, and it is understood that a part of one method may be substituted with a part of another method or combined with one another and applied.

[0612] FIG. 20 is a flowchart for explaining a method according to one embodiment of the present specification.

[0613] Referring to FIG. 20, a method according to one embodiment of the present specification includes i) a step of receiving an R2D message (S2010) and ii) a step of performing D2R transmission (S2030).

[0614] In S2010, the device receives a reader-device message (R2D message) from the reader.

[0615] In S2030, the device performs a device-to-reader (D2R) transmission to the reader based on an access occasion.

[0616] For example, the above R2D message may include message 0 (Msg0) that triggers a random access procedure.

[0617] For example, the above Msg0 may include an ambient IoT paging message (A-IoT Paging message) and / or an access trigger message (Access Trigger Message). As a specific example, the above R2D message may be an access trigger message.

[0618] Based on the fact that the fields of the above R2D message represent defined values, a count-down behavior of the value related to the selection of the access opportunity is performed.

[0619] For example, the above field may indicate an R2D message type. For example, the R2D message type may be indicated as any one of a plurality of R2D message type values ​​and / or reserved values ​​defined for each of the R2D message types (e.g., A-IoT Paging message, Access Trigger message, etc.).

[0620] Based on the fact that the field of the above R2D message indicates a reserved value, the R2D message is discarded.

[0621] For example, if the field of the R2D message represents a reserved value, the R2D message is discarded, so the countdown operation may not be performed based on the fact that the field of the R2D message represents the reserved value.

[0622] This embodiment may be based on the above-described method #7.

[0623] According to one embodiment, the R2D message may include a MAC protocol data unit (MAC PDU).

[0624] For example, the MAC PDU may include control information and other information other than the control information.

[0625] In this case, a first CRC may be added to the control information, and a second CRC may be added to the other information. In other words, a CRC separate from the other information may be added to the control information.

[0626] This embodiment may be based on the above-described method #5.

[0627] Operations based on the above-described S2010 to S2030 can be implemented by the device of FIG. 22. For example, referring to FIG. 22, the device (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S2010 to S2030.

[0628] S2110 to S2130 described below correspond to S2010 to S2030 described in FIG. 20. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the operation of the reader described below can be replaced by the description / execution of FIG. 20 corresponding to the operation.

[0629] FIG. 21 is a flowchart illustrating a method according to another embodiment of the present specification.

[0630] Referring to FIG. 21, a method according to another embodiment of the present specification includes i) an R2D message transmission step (S2110) and ii) a D2R transmission reception step (S2130).

[0631] In S2110, the reader sends a reader-device message (R2D message) to the device.

[0632] In S2130, the reader receives a device-to-reader (D2R) transmission from the device based on an access occasion.

[0633] Based on the fact that the fields of the above R2D message represent defined values, a count-down behavior of the value related to the selection of the access opportunity is performed.

[0634] Based on the fact that the field of the above R2D message indicates a reserved value, the above R2D message is discarded.

[0635] For example, the above countdown operation may not be performed based on the fact that the field of the above R2D message represents the above reserved value.

[0636] For example, the above field may represent an R2D message type.

[0637] According to one embodiment, the R2D message may include a MAC protocol data unit (MAC PDU).

[0638] For example, the MAC PDU may include control information and other information other than the control information.

[0639] For example, the control information may have a first CRC added, and the other information may have a second CRC added.

[0640] Operations based on the above-described S2110 to S2130 can be implemented by the device of FIG. 22. For example, referring to FIG. 22, a reader (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S2110 to S2130.

[0641] Hereinafter, an apparatus to which the embodiments of the present specification can be applied (an apparatus implementing the method / operation according to the embodiments of the present specification) will be described with reference to FIG. 22.

[0642] FIG. 22 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0643] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0644] The processor (110) performs baseband-related signal processing and may include an upper layer processing unit (111) and a physical layer processing unit (115). The upper layer processing unit (111) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (115) may process operations of the PHY layer. For example, if the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, if the first device (100) is a first terminal device in terminal-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0645] The antenna section (120) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110) and software, operating systems, applications, etc. related to the operation of the first device (100), and may include components such as a buffer.

[0646] The processor (110) of the first device (100) may be configured to implement the operation of the base station in base station-terminal communication (or the operation of the first terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0647] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0648] The processor (210) performs baseband-related signal processing and may include an upper layer processing unit (211) and a physical layer processing unit (215). The upper layer processing unit (211) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (215) may process operations of the PHY layer. For example, if the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device (200) is a second terminal device in terminal-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0649] The antenna section (220) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210) and software, operating systems, applications, etc. related to the operation of the second device (200), and may include components such as a buffer.

[0650] The processor (210) of the second device (200) may be configured to implement the operation of the terminal in base station-terminal communication (or the operation of the second terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0651] In the operation of the first device (100) and the second device (200), the details described in the examples of the present disclosure regarding the base station and terminal (or the first terminal and the second terminal in terminal-to-terminal communication) in base station-to-terminal communication may be applied in the same way, and redundant descriptions are omitted.

[0652] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above.

[0653] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above.

[0654] Additionally or generally, the wireless communication technology implemented in the device of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN) for low-power communication, but is not limited to the names mentioned above. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

Claims

1. In a method performed by a device, A step of receiving a reader-device message (R2D message) from a reader; and The step of performing a device-to-reader transmission (D2R transmission) to the reader based on an access occasion; wherein Based on the fact that the fields of the above R2D message represent defined values, a count-down behavior of the value related to the selection of the access opportunity is performed, and A method characterized in that the R2D message is discarded based on the fact that the field of the R2D message indicates a reserved value.

2. In Paragraph 1, A method characterized in that the above countdown operation is not performed based on the fact that the field of the above R2D message represents the above reserved value.

3. In Paragraph 1, A method characterized in that the above field represents an R2D message type.

4. In Paragraph 1, The above R2D message includes a MAC protocol data unit (MAC PDU), and The above MAC PDU includes control information and other information other than the control information, and The above control information has a first CRC added, and The above other information is a method characterized by the addition of a second CRC.

5. Regarding the device, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A device characterized by the above instructions enabling the device to perform all steps of the method according to any one of claims 1 to 4, based on execution by the one or more processors.

6. A device comprising one or more memories and one or more processors connected to said one or more memories, A device characterized in that the one or more of the above memories store instructions that cause the device to perform all steps of the method according to any one of claims 1 to 4, based on execution by the one or more processors.

7. In a non-transitory computer-readable storage medium for storing instructions, A non-transient computer-readable storage medium characterized by instructions executable by one or more processors such that the device performs all steps of the method according to any one of claims 1 to 4.

8. In a method performed by a reader, A step of transmitting a reader-device message (R2D message) to a device; and The method comprises the step of receiving a device-to-reader (D2R) transmission from the device based on an access occasion. Based on the fact that the fields of the above R2D message represent defined values, a count-down behavior of the value related to the selection of the access opportunity is performed, and A method characterized in that the R2D message is discarded based on the fact that the field of the R2D message indicates a reserved value.

9. In Paragraph 8, A method characterized in that the above countdown operation is not performed based on the fact that the field of the above R2D message represents the above reserved value.

10. In Paragraph 8, A method characterized in that the above field represents an R2D message type.

11. In Paragraph 8, The above R2D message includes a MAC protocol data unit (MAC PDU), and The above MAC PDU includes control information and other information other than the control information, and The above control information has a first CRC added, and The above other information is a method characterized by the addition of a second CRC.

12. Regarding the reader, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A reader characterized by the above instructions, based on execution by the one or more processors, having the reader perform all steps of the method according to any one of claims 8 to 11.