Method and apparatus for random access procedure

Abstract

A method according to one embodiment of the present specification comprises the steps of: transmitting an access random ID message on the basis of an access occasion; receiving a random ID response message; and transmitting a device to reader (D2R) message on the basis of the random ID response message.

Description

Method and apparatus for a random access procedure

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

[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] In a random access procedure for Ambient IoT, a device that has transmitted Msg1 (e.g., Access Random ID message) to a Reader may receive Msg2 (e.g., Random ID Response message) from the Reader. At this time, Msg2 may include a random number (e.g., a 16-bit random number) transmitted through Msg1. Based on Msg2, the device may transmit Msg3 (e.g., Device to Reader (D2R) message) to the Reader.

[0005] If the above Msg2 contains only the above random number, the following problem may occur. Specifically, the operation performed by the device that transmitted Msg1 in the random access procedure (e.g., transmitting Msg3 after receiving Msg2) may not be performed normally.

[0006] Specifically, it can be assumed that one or more devices select an access occasion FDMed for the same time instance and perform Msg1 transmission by generating / using the same random number. In such a case, a device receiving Msg2 cannot distinguish whether the Msg2 (e.g., the information contained in Msg2) is intended for its own Msg3 transmission. To give a specific example, even if Device #1 receives Msg2 from a Reader containing a random number identical to the random number included in Msg1, the information contained in Msg2 may not be for Device #1 but for another device (e.g., Device #2).

[0007] In other words, even though the Reader has transmitted Msg2 for a specific device (device #2), another device (device #1) that transmitted Msg1 using the same random number as the random number included in said Msg2 may mistake said Msg2 for Msg2 intended for itself and transmit Msg3 to said Reader based on said Msg2.

[0008] As described above, in a contention-based random access procedure for Ambient IoT, the reliability of subsequent procedures / operations may be degraded as Msg2 (e.g., scheduling information included in Msg2) transmitted from a Reader to a specific device is incorrectly identified by another device. For example, there is a possibility that the other device transmitting Msg3 may be mistaken for the specific device by the Reader. For example, the transmission of Msg3 by the specific device may fail due to the transmission of Msg3 by the other device. Furthermore, both the other device and the specific device may need to retransmit Msg3 respectively. The aforementioned problem may occur in the same way even when Msg2 contains information (e.g., fields) regarding multiple devices.

[0009] The purpose of this specification is to propose a method for solving the aforementioned problems.

[0010] 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 specification belongs from the description below.

[0011] A method according to an embodiment of the present specification for solving the above-described technical problem comprises the steps of: transmitting an Access Random ID message including a first ID field based on a random number based on an access occasion; receiving a Random ID Response message; and transmitting a Device to Reader (D2R) message based on the Random ID Response message. The Access Random ID message is transmitted using a first value associated with a frequency domain resource of the access occasion. The Random ID Response message comprises i) one or more second ID fields and ii) one or more frequency index fields. The value indicated by the second ID field among the one or more second ID fields is identical to the value of the first ID field, and the value indicated by the frequency index field among the one or more frequency index fields matches the first value. As described above, since the random ID response message includes not only the second ID field(s) but also the frequency index field(s), problems caused by misidentification / confusion of the aforementioned device identification can be prevented.

[0012] If the Random ID Response message contains only an ID associated with a random number based on the Access Random ID message, retransmission by multiple devices may occur due to device ambiguity.

[0013] According to an embodiment of the present specification, a Random ID Response message includes frequency index field(s) in addition to ID field(s). Therefore, misidentification or confusion regarding device identification can be prevented. Since unnecessary retransmission is prevented, random access procedures for Ambient IoT can be improved in terms of signaling overhead.

[0014] In addition, the power efficiency and battery life of each device performing the random access procedure can be improved.

[0015] In addition, resource utilization and Reader scheduling efficiency related to random access procedures can be improved, and the overall latency of said random access procedures can be reduced.

[0016] 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 to which this specification belongs from the description below.

[0017] Figure 1 illustrates a topology 1 related to Ambient IoT.

[0018] Figure 2 illustrates topology 2 related to Ambient IoT.

[0019] Figure 3 is an example of topology 3 related to Ambient IoT.

[0020] Figure 4 is another example of topology 3 related to Ambient IoT.

[0021] Figure 5 illustrates topology 4 related to Ambient IoT.

[0022] Figure 6 illustrates the state according to the operating state of an energy harvesting-based device.

[0023] Figure 7 is an example of a frequency domain resource according to a value related to a frequency resource.

[0024] Figure 8 is another example of a frequency domain resource according to a value related to a frequency resource.

[0025] FIG. 9 is a flowchart illustrating a method according to one embodiment of the present specification.

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

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

[0028] 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."

[0029] 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."

[0030] 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."

[0031] 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."

[0032] 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."

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

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

[0035] In this specification, a terminal (UE, User Equipment) may be a portable device and may be a second node that receives a signal from a base station / first node / IAB node.

[0036] In this specification, a base station (BS, Base Station) may be a base station / first node / IAB node / transmission-reception point.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] Ambient IoT communication (Rel-18) >

[0041] Ambient IoT (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 can refer to a new type of Internet of Things device that operates by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy. Examples of A-IoT use cases are shown in Table 1 below.

[0042]

[0043] Table 2 shows matters related to IoT communication discussed in the 3GPP RAN.

[0044]

[0045] 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.

[0046] 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 the present disclosure, 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 the 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).

[0047] 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 in this disclosure are merely examples, and the proposals of this disclosure may be extended and applied to other topologies.

[0048] Figure 1 illustrates a topology 1 related to Ambient IoT.

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

[0050] Referring to FIG. 1, an A-IoT device (Ambient IoT device) can communicate directly and bidirectionally with a base station (BS). For example, communication between the base station 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). 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, the base station and the A-IoT device in a micro-cell environment may 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.

[0051] Figure 2 illustrates topology 2 related to Ambient IoT.

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

[0053] 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 can be limited to a terminal, and the intermediate node can be located indoors.

[0054] Figure 3 is an example of topology 3 related to Ambient IoT. Figure 4 is another example of topology 3 related to Ambient IoT.

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

[0056] 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 the 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 the auxiliary node. Here, for example, the auxiliary node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc.

[0057] Figure 5 illustrates topology 4 related to Ambient IoT.

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

[0059] 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).

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

[0061] < Ambient IoT solutions SI (Rel-19) >

[0062] 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.

[0063] 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).

[0064] General range

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

[0066] 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.

[0067] 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.

[0068] ii. Peak power consumption ≤ hundreds of μ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.

[0069] -X is determined in WG.

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

[0071] - 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.

[0072] 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.

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

[0074] - Deployment Scenario 1 using Topology 1

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

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

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

[0078] The location of the intermediate node is indoors

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

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

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

[0082] - 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.

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

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

[0085] 1. Evaluation Assumptions

[0086] 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].

[0087] Clause 5.3: Applicable maximum distance target value

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

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

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

[0091] 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]

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

[0093] 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.

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

[0095] 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.

[0096] 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).

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

[0098] RAN1-led:

[0099] For Ambient IoT DL and UL:

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

[0101] Numerology, Bandwidth, and Multiple Access

[0102] Waveform and Modulation

[0103] Channel coding

[0104] Downlink Channel / Signal Aspect

[0105] Uplink Channel / Signal Side

[0106] Scheduling and Timing Relationships

[0107] 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.

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

[0109] RAN2 Lead:

[0110] 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.

[0111] for example:

[0112] Paging

[0113] Random access

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

[0115] Interaction with the upper class

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

[0117] RAN3 Leading:

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

[0119] Paging

[0120] Device Context Management

[0121] Data transmission

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

[0123] 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.

[0124] RAN4 Leading:

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

[0126] Research on RF Requirements for Ambient IoT:

[0127] Ambient IoT BS Transmitter / Receiver

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

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

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

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] 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.

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

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

[0138] 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.

[0139] - 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.

[0140] Figure 6 illustrates the state according to the operating state of an energy harvesting-based device.

[0141] 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 capacity, according to one embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure.

[0142] 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.

[0143] 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.

[0144] For example, the transition from S1 to S2 may be possible only when the device energy state value is E2 or when E2 is reached. 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 when E2 is reached.

[0145] 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).

[0146] 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.

[0147] 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.

[0148] For example, in the present disclosure, 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 the present disclosure, 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.

[0149] FIG. 7 is an example of a frequency domain resource according to a value related to a frequency resource. FIG. 8 is another example of a frequency domain resource according to a value related to a frequency resource. Below, frequency domain resources related to D2R transmission will be described in detail with reference to FIG. 7 and FIG. 8.

[0150] D2R bandwidths

[0151] The following bandwidths can be defined for D2R.

[0152] - Transmission bandwidth, ): It is a frequency resource scheduled by the reader for D2R transmission from a single device.

[0153] - Occupied bandwidth ): Total in transmission bandwidth It adds the potential related A-IoT (Ambient IoT) internal guard band. This guard band is not intended for coexistence with NR / LTE.

[0154] D2R transmission associated with a single tone of the carrier wave Regarding this, FIGS. 7 and 8 show a small frequency-shift. Specifically, FIGS. 7 and 8 show a Manchester line code using Option 1, and a case where a D2R line code is not used (i.e., the use of a square wave corresponding to a small frequency-shift).

[0155] Here:

[0156] is the carrier frequency at least when generated externally.

[0157] This represents an example of a small frequency shift amount.

[0158] In the case of 2SB (SubBand) transmission, + and - All parts are included in Fig. 7.

[0159] In the case of 1SB transmission, either the upper part or the lower part is appropriately applied in Fig. 8.

[0160] The Bocc,D2R of D2R transmission associated with a single tone of the carrier is affected by at least the following aspects:

[0161] Possible guard band due to minimum SFO (Sampling Frequency Offset)

[0162] Possible guard bands due to the Carrier Frequency Offset (CFO) of Device 2b

[0163] Since device 2b generates an internal carrier, 2SB and / or 1SB and It can be affected by D2R modulation and baseband waveform generation methods.

[0164] Small Frequency Shifts

[0165] For OOK and BPSK, a small frequency shift can be considered.

[0166] Number of repetitions When applying to the Manchester line code:

[0167] Option 1: Each Manchester codeword is the same time corresponding to an information bit. It is repeated R times within the codeword, where R = Since it is / (2 × chip length), the small frequency shift amount in Hz is R / = 1 / (2 × chip length).

[0168] Option 2: By multiplying the Manchester codeword by a square wave corresponding to a small frequency shift, the time corresponding to each information bit contains R square wave periods, where R = Since it is / (2 * chip length), the small frequency shift in Hz is R / = 1 / (2 × chip length).

[0169] Multiplication operations are performed as XOR or XNOR operations between a Manchester codeword corresponding to an information bit and a square wave for small frequency shift.

[0170] If the D2R line code is not used, the time corresponding to each information bit is obtained by using a square wave with a small frequency shift. It includes R square wave periods generated by a 2R OOK chip [0, 1, 0, 1 ...] / [1, 0, 1, 0 ..] or a BPSK chip [-1, +1, -1, +1, ...] / [+1, -1, +1, -1, ...], and the small frequency shift amount in Hz is R / am.

[0171] The potential purposes of Small Frequency Shift are as follows:

[0172] If supported, D2R's FDMA

[0173] CW (Continuous Wave) interference avoidance if supported

[0174] For BPSK and OOK, the small-frequency-shift factor is the bit length (e.g., ) chip length (e.g., It can be defined as a ratio divided by two (e.g., small frequency shift factor( ) = ).

[0175] The value of the small-frequency-shift factor varies depending on the design details, and according to the proposals considered, the small-frequency-shift factor could be, for example, as follows:

[0176] Duration The number of Manchester codeword repetitions R within

[0177] Miller's M value in Figure 6-12 of the UHF RFID standard

[0178] Number of square wave periods within

[0179] In the embodiments of this specification described below, the frequency gap index, F-shift resource index, and F-shift index may be interpreted / replaced with a small frequency shift factor.

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

[0181] - SSB: Synchronization Signal Block

[0182] - MIB: Master Information Block

[0183] - RMSI: Remaining Minimum System Information

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

[0185] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) region of 24 GHz or higher (e.g., 24250 MHz ~ 52600 MHz).

[0186] - BW: Bandwidth

[0187] - BWP: Bandwidth Part

[0188] - RNTI: Radio Network Temporary Identifier

[0189] - CRC: Cyclic Redundancy Check

[0190] - SIB: System Information Block

[0191] - SIB1: SIB1 for NR devices = RMSI (Remaining Minimum System Information). Broadcasts information necessary for cell connection of NR terminals.

[0192] - CORESET: Control REsource SET. The time / frequency resource at which the terminal attempts candidate PDCCH decoding.

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

[0194] - 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

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

[0196] - 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.

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

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

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

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

[0201] - 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.

[0202] - SCS: subcarrier spacing

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

[0204] - 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.

[0205] - TB: Transport Block

[0206] - RSA (Redcap standalone): A cell that supports only the Redcap device or service.

[0207] - SIB1(-R)-PDSCH: PDSCH transmitting SIB1(-R)

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

[0209] - SIB1(-R)-PDCCH: PDCCH transmitting SIB1(-R)-DCI

[0210] - FDRA: Frequency Domain Resource Allocation

[0211] - TDRA: Time Domain Resource Allocation

[0212] - RA: Random Access

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

[0214] - 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.

[0215] - RO-N: RO(RACH Occasion) for normal UE 4-step RACH and 2-step RACH (if configured)

[0216] - 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).

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

[0218] - 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).

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

[0220] - RAR: Random Access Response

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

[0222] - FH: Frequency Hopping

[0223] - iBWP: initial BWP

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

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

[0226] - CS: Cyclic shift

[0227] - NB: Narrowband

[0228] - TO: Traffic Offloading

[0229] - mMTC; massive Machine Type Communications

[0230] - eMBB: enhanced Mobile Broadband Communication

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

[0232] - RedCap: Reduced Capability

[0233] - eRedCap: enhanced RedCap

[0234] - FDD: Frequency Division Duplex

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

[0236] - DRX: Discontinuous Reception

[0237] - RRC: Radio Resource Control

[0238] - RRM: Radio Resource Management

[0239] - MM: Mobility Management

[0240] - IWSN: Industrial Wireless Sensor Network

[0241] - LPWA: Low Power Wide Area

[0242] - RB: Resource Block

[0243] - CCE: Control Channel Element

[0244] - AL: Aggregation Level

[0245] - PRG: Physical Resource-block Group

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

[0247] - PBCH: Physical Broadcast Channel

[0248] - A-PBCH: Additional PBCH

[0249] - BD: blind detection

[0250] - EPRE: Energy Per RE

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

[0252] - TDM: Time Division Multiplexing

[0253] - FDM: Frequency Division Multiplexing

[0254] - DMRS: DeModulation Reference Signal

[0255] - TDD: Time Division Duplex

[0256] - PCI: Physical layer Cell ID

[0257] - EH: Energy Harvesting

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

[0259] - 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.

[0260] - ET: Energy Transfer

[0261] - 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.

[0262] - 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.

[0263] - 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.

[0264] - T: Tag / ambient IoT device. An RFID standard term. It may be interchangeable with EH device in this specification, and in the 3GPP Ambient IoT context, it primarily refers to Ambient IoT device, Device A / B / C. The abbreviation 'T' above may be interpreted / replaced with 'D', which signifies Ambient IoT Device.

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

[0266] - 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. 'R=>T' can be interpreted / replaced with 'R=>D' (Reader-to-Device).

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

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

[0269] - T=>R: Tag-to-Reader or Tag-to-Reader communication link. If the base station or intermediate / assisting node is a reader, it may have the same meaning as a UL or reverse / backward link. 'T=>R' can be interpreted / substituted as 'D=>R' (Device-to-Reader).

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

[0271] - 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.

[0272] - 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)

[0273] - RF-EH: RF energy harvesting

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

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

[0276] - BS: Base Station

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

[0278] - 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.

[0279] - 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.

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

[0281] - AmIoT: Ambient IoT (=A-IoT)

[0282] - F-gap: Frequency gap

[0283] - T-gap: Time gap

[0284] - TD: Time Domain

[0285] - FD: Frequency Domain

[0286] - PEI: Paging Early Indication

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

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

[0289] - RSRP: Reference Signal Received Power

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

[0291] - PRB: Physical Resource Block

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

[0293] - PHR: Power Headroom Report

[0294] - EHR: Energy Headroom Report

[0295] - BPF: Band-Pass Filter

[0296] - SM: Subcarrier Modulation

[0297] The methods proposed in this specification may be applied commonly to topology 1 and topology 2, and UE1 as gNB and IN is referred to as the reader for convenience. Furthermore, the embodiments of this specification may be extended to cases where the reader receiving the beam search signal (BSS) may directly generate and transmit a CW, or where the node transmitting the CW is a separate node from the reader. The BSS may refer to a signal transmitted spatially separated from the existing signal / channel (e.g., downlink signal / channel) for beam search. The BSS may be transmitted based on a dedicated port for beam search. For example, the dedicated port may be a port different from the port used for transmitting the existing signal / channel (e.g., SSB, PDSCH, etc.).

[0298] As used herein, an Ambient IoT BS (base station) (e.g., reader) may be a gNB in ​​topology 1 and a specific UE in topology 2. Additionally, as used herein, an Ambient IoT device (e.g., tag) may be interpreted as an Ambient IoT device in both topology 1 and / or topology 2.

[0299] 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.

[0300] 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.

[0301] 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 specification, 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.

[0302] 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. 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.

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

[0304] Msg1, Msg2, Msg3, and (Msg4) are each considered for the contention-based access procedure to be performed by multiple devices in an ambient IoT system. Among these, Msg1 and Msg3 are D2R signals / channels transmitted by the device, and Msg2 and (Msg4) are R2D signals / channels transmitted by the reader.

[0305] In this specification, 'Msg1' can be interpreted / replaced as an Access Random ID message, 'Msg2' can be interpreted / replaced as a Random ID Response message, and 'Msg3' can be interpreted / replaced as a Device to Reader message.

[0306] In this specification, 'Query' and 'Query rep' may be interpreted or replaced with an A-IoT paging message or an Access Trigger message.

[0307] At this time, if the Reader sets / instructs a time gap index / frequency gap index for D2R transmission to multiple devices, the Msg1 / Msg3 of the multiple devices can be transmitted via TDM / FDM. In this specification, 'time gap index' may be interpreted as a value related to a time domain resource, a value related to a time resource, a value based on a time index field, or a value based on a time resource indication field. Additionally, in this specification, 'frequency gap index' may be interpreted as a value related to a frequency domain resource, a value related to a frequency resource, a value based on a frequency index field, or a value based on a frequency resource indication field.

[0308] On the other hand, TDM is considered for Msg2 by default. This is based on the following technical considerations. Since the availability of bandpass filtering capability varies by device (or device type), it may be difficult for each device to properly filter and receive multiple FDMed R2D signals / channels transmitted from the reader. Taking this into account, TDM is considered for the transmission of Msg2.

[0309] This specification proposes a method for instructing information related to Msg1 to the L1 / L2 control information of Msg2 PRDCH during a contention-based access procedure (or random access procedure) in an ambient IoT system. In this specification, 'L1 / L2 control information of Msg2 PRDCH' may be interpreted or replaced with 'Msg2' or 'Random ID Response message'.

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

[0311] [Method #1] Method to indicate Msg1 information through the control information of Msg2 PRDCH

[0312] In an ambient IoT system, the contention-based access procedure involves a reader providing Msg0 PRDCH (e.g., paging) to devices, and the devices subsequently transmitting Msg1 PRDCH. Afterward, the reader transmits Msg2 PRDCH for the successfully received Msg1. The reader can include information about Msg1 in the L1 / L2 control information of Msg2 PRDCH. This helps devices decode Msg2 PRDCH.

[0313] According to one embodiment, the reader may provide the entire (or part or result value obtained through a specific rule based on the said random number) of the 16-bit random number transmitted by the device through Msg1 to the L1 or L2 control information of Msg2 PRDCH. In other words, Msg2 may contain the same value as the entire (or part) of the 16-bit random number contained in Msg1.

[0314] For example, if the L1 / L2 control information of the Msg2 PRDCH includes all or part of the random number transmitted by the device, the device can be configured / defined to continue receiving the Msg2 payload.

[0315] For example, if it is confirmed that there is no information regarding the random number transmitted by the device in the L1 / L2 control information of the Msg2 PRDCH, the device may be configured / defined to no longer receive the Msg2 PRDCH. As a specific example, the device may be configured / defined to wait for another Msg2 PRDCH to be transmitted within the configured Msg2 PRDCH monitoring window. As a specific example, the device may be configured / defined to attempt to retransmit the Msg1 PDRCH at the time of retransmission if the Msg2 PRDCH monitoring window has ended.

[0316] According to one embodiment, the reader may be configured / defined to provide the time / frequency index value of the resource transmitted via Msg1 PDRCH through Msg2 PRDCH L1 / L2 control information. In other words, Msg2 may include a time / frequency index associated with the time / frequency domain resource of the access occasion in which Msg1 was transmitted.

[0317] Specifically, if multiple Msg2 payloads are provided in Msg2 PRDCH, time / frequency index values ​​of multiple Msg1 resources may be indicated sequentially. In other words, Msg2 may include i) one or more time index fields and / or ii) one or more frequency index fields.

[0318] In addition, the Msg2 payload can be placed and transmitted in the same order as the time / frequency index.

[0319] For example, if three Msg1 resources are TDMed in the time domain and two Msg1 resources are FDMed in the frequency domain, the time domain index can be defined as 0, 1, and 2, and the frequency domain index can be defined as 0 and 1.

[0320] At this time, it is assumed that there are a total of 4 time / frequency indices of resources that the reader successfully received Msg1 from (e.g., {0, 0}, {0, 1}, {1, 1}, {2, 0}). The corresponding time / frequency index values ​​(e.g., in the order of {0, 0}, {0, 1}, {1, 1}, {2, 0}) can be provided to the L1 / L2 control information of the Msg2 PRDCH. Subsequently, the Msg2 payload can be placed in the order of the Msg1 transmitted resources provided in the control information (e.g., {0, 0}, {0, 1}, {1, 1}, {2, 0}).

[0321] According to one embodiment, an independent ID may be defined for each resource to which Msg1 PDRCH is transmitted. The reader may be configured / defined to provide the corresponding ID value through Msg2 PDRCH L1 / L2 control information. In this case, the ID of the resource to which Msg1 PDRCH is transmitted (e.g., access occasion) may be defined in a frequency first - time second (or time first - frequency second) manner.

[0322] For example, in the case where 3 Msg1 resources are TDMed in the time domain (e.g., the value indicated by the time resource indication field is 3, X=3) and 2 Msg1 resources are FDMed in the frequency domain (e.g., frequency resource indication field broadcast The number of bits set to 1 in the 8-bit value is 2, N SFS =2, in other words, the number of allowed small frequency shift factors is 2), and it can be assumed that the ID is defined in the order of frequency first - time second.

[0323] In the above case, the IDs of the two Msg1 transmission resources located in the first time domain can be #0 and #1 starting from the lowest frequency. The IDs of the two Msg1 transmission resources located in the second time domain can be #2 and #3 starting from the lowest frequency. The IDs of the two Msg1 transmission resources located in the last, third time domain can be #4 and #5 starting from the lowest frequency. Subsequently, if the reader successfully receives a total of four resources with IDs #0, #2, #3, and #4, these IDs (e.g., #0, #2, #3, #4) can be provided to the L1 / L2 control information of the Msg2 PRDCH. Then, the Msg2 payload can be arranged in the order of the Msg1 transmission resource IDs provided in the control information (e.g., #0, #2, #3, #4).

[0324] According to one embodiment, considering a multiple reader environment or multiple parallel inventory rounds, a method of defining an ID by additionally considering the reader ID and / or a specific value of Msg0 (e.g., inventory round / transaction / session ID) in addition to the time / frequency resource information of the Msg1 resource may be considered.

[0325] For example, a specific offset can be set / defined for each reader ID value (or a specific value indicated by the above Msg0) to distinguish the Msg1 resource index.

[0326] For example, the reader ID value (or a specific value indicated by the above Msg0) can be grouped moduloed by the number of groups (e.g., N, where N is a positive integer greater than or equal to 1) to set different Msg1 resource indices for each reader (or inventory round / transaction / session) corresponding to each group. Specifically, considering the method of grouping reader IDs, the final Msg1 index can be defined as shown in Equation 1 below.

[0327]

[0328] The reason for applying these methods is to differentiate ID values ​​by applying an offset to the ID values ​​of Msg1 resources based on the reader ID in a multiple reader environment (or based on the inventory round ID in multiple parallel inventory rounds). Subsequently, the ID information of the resource for which the reader successfully received Msg1 can be provided through the L1 / L2 control information of the Msg2 PRDCH. Additionally, for this purpose, the reader ID and / or group ID and / or specific values ​​of Msg0 (e.g., inventory round / transaction / session ID) can also be provided through the L1 / L2 control information of the Msg2 PRDCH. Afterward, the Msg2 payload can be arranged in the order of the IDs of the Msg1 transmission resources provided in the control information.

[0329] For example, an ID can be defined based on a time domain resource (or frequency domain resource) among the resources transmitted by Msg1 PDRCH. Multiple frequency resources located within that time domain resource (or multiple time resources located within that frequency domain resource) can be defined to use the same ID. Subsequently, the reader can be configured to provide the corresponding ID value through Msg2 PRDCH L1 / L2 control information. In this case, if the reader successfully receives at least one of the multiple Msg1 resources sharing a specific ID, the reader can be configured to provide the corresponding ID value through Msg2 PRDCH L1 / L2 control information. This method has the advantage of reducing the signaling overhead of the information provided to the Msg2 PRDCH L1 / L2 control information compared to the previously proposed methods.

[0330] As a specific example, it can be assumed that three Msg1 resources are TDMed in the time domain and two Msg1 resources are FDMed in the frequency domain, and that IDs are defined based on the time domain resources. In such a case, the IDs of the two Msg1 transmission resources located in the first time domain can be defined to share #0. The IDs of the two Msg1 transmission resources located in the second time domain can be defined to share #1. Finally, the IDs of the two Msg1 transmission resources located in the third time domain can be defined to share #2. Subsequently, if the reader successfully receives a total of two resources with IDs #0 and #2, the corresponding IDs (e.g., #0, #2) can be provided through the L1 / L2 control information of the Msg2 PRDCH. Then, the Msg2 payload can be arranged in the order of the Msg1 transmission resource IDs (e.g., #0, #2) provided in the control information. For example, if Msg1 resources using the same ID are TDMed, it can be defined so that the Msg2 payload corresponding to the first (or last) time domain resource among the TDMed Msg1 resources is arranged in order. For example, if Msg1 resources using the same ID are FDMed, it can be defined so that the Msg2 payload corresponding to the lowest (or highest) frequency domain resource among the FDMed Msg1 resources is arranged in order.

[0331] The device operation that can be commonly applied to the above proposed methods is as follows.

[0332] A device can be defined to receive L1 / L2 control information from Msg2 PRDCH and, if the Msg1 resources transmitted by the device (or the IDs of the resources, or the IDs of the resource groups) are specified, to receive the Msg2 payloads in the specified order.

[0333] It may be assumed that the Msg1 resource transmitted by the device (or the ID of the resource, or the ID of the resource group) is not specified. For example, the device may be configured / defined to wait for another Msg2 PRDCH to be transmitted within the configured Msg2 PRDCH monitoring window. For example, the device may be configured / defined to attempt to retransmit the Msg1 PDRCH at the time of retransmission if the Msg2 PRDCH monitoring window has ended.

[0334] In addition, in the methods proposed above, the indexing (or ID) value of the Msg1 resource provided in the L1 / L2 control information of the Msg2 PRDCH can be defined as identical to the indexing defined for the Msg1 resource.

[0335] Additionally, one or a combination of the methods (examples) proposed above may be applied to the operation of the reader / device.

[0336] For example, in a situation where the Msg1 resource is TDM & FDM configured, Msg1 resources with the same time domain index may be configured to have the same ID. In this case, the reader may consider a method of simultaneously providing the ID information along with a 16-bit random number value successfully received through the Msg1 resource to the L1 / L2 control information of the Msg2 PRDCH.

[0337] For example, one can consider a method of applying an offset between the indices of the Msg1 resource based on a 16-bit random number. Specifically, the 16-bit random number can be grouped by taking the modulo of a specific value specified by the reader (e.g., K, where K is a positive integer greater than or equal to 1), and then the Msg1 resource can be defined to differ according to that group. This can be expressed mathematically as Equation 2. Subsequently, the result derived from Equation 2 can be provided through the L1 / L2 control information of the Msg2 PRDCH. The reason for applying such methods is to differentiate the ID values ​​by applying an offset to the ID values ​​of each Msg1 resource based on the specific value (e.g., K) specified by the reader.

[0338]

[0339] For example, an ID value based on the time / frequency resource of Msg1 resource can be provided through Msg2 PRDCH L1 control information, and a 16-bit random number (e.g., RN16 in Table 2 below) can be provided through Msg2 PRDCH L2 control information. Specifically, operations as shown in Table 3 below can be defined.

[0340]

[0341] [Method #2] Method to indicate the presence or absence of Msg2 Payload via control information in Msg2 PRDCH

[0342] Based on the resource mapping relationship between the Msg1 transmission resource and the Msg2 PRDCH, a method may be considered to indicate whether the Msg2 payload is provided to the L1 / L2 control information of the Msg2 PRDCH.

[0343] For example, if a Msg1 transmission resource is mapped to a Msg2 PRDCH, the L1 control information of the Msg2 PRDCH may be defined to indicate whether to transmit the Msg2 payload via a 1-bit flag. For example, the transmission of the Msg2 payload may be defined to indicate whether to transmit the Msg2 payload via a 1-bit flag in D2R data (e.g., L2 control information, Msg2 header, etc.) rather than in the L1 control information. For example, the Msg2 payload transmission may be indicated by setting the payload size to 0 within the L1 control information. Specifically, if the payload size is indicated as the actual size of the Msg2 payload being transmitted instead of 0, it may indicate that the Msg2 payload is being transmitted.

[0344] As another example, it can be assumed that N Msg1 transmission resources are mapped to one Msg2 PRDCH, and that up to N Msg2 payloads can be provided to the Msg2 PRDCH. The reader can be configured / defined to provide information regarding the M Msg2 payloads (i.e., M-hub) to be actually transmitted among the N Msg2 payloads through the L1 / L2 control information of the Msg2 PRDCH. As a specific example, the provision of Msg2 payloads may be indicated in the L1 control information of the Msg2 PRDCH in the form of an N-bit bitmap (specifically, by marking only M bits as 1 and the remaining NM bits as 0 out of an N-bit field). As a specific example, the provision of Msg2 payloads may be indicated by providing M information regarding Msg1-related resources. As a specific example, the provision of the Msg2 payload can be indicated all at once in the form of an N-bit bitmap in D2R data (e.g., L2 control information, Msg2 header, etc.) rather than in L1 control information. As a specific example, a 1-bit flag can be configured / defined immediately before each Msg2 payload to indicate whether to send the Msg2 payload.

[0345] [Method #3] Method for indicating additional information when Msg2 PRDCH is TDM-transmitted

[0346] When multiple Msg2 PRDCHs are TDM-transmitted within a specific Msg2 PRDCH monitoring window, a method may be considered in which the reader indicates whether additional Msg2 PRDCHs will be transmitted. Specifically, if the reader indicates that there will be additional Msg2 PRDCH transmissions (or if there is no specific indication from the reader), the device may be configured / defined to continue Msg2 PRDCH monitoring within the current Msg2 PRDCH monitoring window. If the reader indicates that there will be no more Msg2 PRDCH transmissions, the device may be configured / defined to stop Msg2 PRDCH monitoring within the current Msg2 PRDCH monitoring window. This behavior may be maintained for a specific Msg2 PRDCH monitoring window, and when a new monitoring window begins, the device may be defined to monitor Msg2 PRDCHs anew.

[0347] At this point, a method to allow the reader to indicate whether to send an additional Msg2 PRDCH is proposed as follows.

[0348] First, if another Msg2 PRDCH transmission is scheduled after a specific Msg2 PRDCH within a specific Msg2 PRDCH monitoring window, a 1-bit flag can be provided indicating that the Msg2 PRDCH transmission will continue through the L1 / L2 control information of the preceding Msg2 PRDCH.

[0349] Alternatively, one can consider a method in which the reader indicates the total number of Msg2 PRDCHs to be transmitted to the corresponding Msg2 PRDCH monitoring window. Specifically, if N Msg2 PRDCHs are scheduled to be transmitted within the Msg2 PRDCH monitoring window, the total number of Msg2 PRDCHs can be indicated as N through the L1 / L2 control information of each of the N Msg2 PRDCHs.

[0350] Alternatively, a 1-bit flag indicating that it is the last Msg2 PRDCH transmission may be introduced within the L1 / L2 control information of the Msg2 PRDCH. The L1 / L2 control information of the Msg2 PRDCH that is transmitted last within the Msg2 PRDCH monitoring window may be defined to have this 1-bit flag set to ON.

[0351] Alternatively, it can be defined so that only the last Msg2 PRDCH transmitted within the Msg2 PRDCH monitoring window includes a pre-configured / defined postamble, while the remaining Msg2 PRDCHs do not include a postamble.

[0352] In the proposed methods above, the predefined timing and / or timing values ​​set / indicated by the reader may be set in units of chip(s), codeword(s), NR OFDM(s) symbols, or NR slots. Alternatively, a time unit may be defined for Ambient IoT (e.g., Tc). The reader may set / indicate the timing value in units of the corresponding time unit. The reader may set / indicate the timing value as a multiple of the corresponding time unit, etc.

[0353] Various embodiments of the present disclosure may be combined with one another.

[0354] In terms of implementation, the operations of the first device (e.g., Ambient IoT Device or Reader, BS, IN, AN, UE) / second device (e.g., Reader, BS, IN, AN, UE or Ambient IoT Device) according to the embodiments described above can be processed by the device of FIG. 11 (e.g., the processor (110, 210) of FIG. 11).

[0355] In addition, the operations of the first device (e.g., Ambient IoT Device or Reader, BS, IN, AN, UE) / second device (e.g., Reader, BS, IN, AN, UE or Ambient IoT Device) according to the above-described embodiment may be stored in memory (e.g., 140, 240 of FIG. 11) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 11).

[0356] The embodiments described above will be explained in detail below with reference to FIGS. 9 and FIG. 10 in terms of the operation of a first device (e.g., Ambient IoT Device) and a second device (e.g., Reader, base station, intermediate node, auxiliary node). 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.

[0357] FIG. 9 is a flowchart illustrating a method according to one embodiment of the present specification.

[0358] Referring to FIG. 9, a method according to one embodiment of the present specification includes a random ID message transmission step (S910), a random ID response message reception step (S920), and a D2R message transmission step (S930).

[0359] In S910, the device transmits an access random ID message to the reader based on an access occasion, the message including a first ID field (e.g., Random ID field) based on a random number.

[0360] For example, the access random ID message may mean Msg1 based on at least one of the methods #1 to #3 described above.

[0361] For example, the access occasion may be an access occasion selected from among m access occasions (e.g., all Msg1 resources based on the TDM / FDM described above) triggered by an A-IoT paging message (or Access Trigger message). The m is a first number (e.g., X) and a second number (e.g., N). SFS It can be calculated / determined based on ). For example, the above m is X*N SFS It may be. For example, the first number (e.g., X) may be related to the number of time-domain resources (e.g., the number of TDMed Msg1 resources in the time-domain described above). As a specific example, the first number (e.g., X) may be the number of time-domain resources of triggered access occasions indicated based on the A-IoT paging message (the time resource indication field of the message). For example, the second number (e.g., N SFS ) may be related to the number of frequency domain resources (e.g., the number of Msg1 resources FDMed in the aforementioned frequency domain). As a specific example, the second number (e.g., N SFS) may be the number of frequency domain resources for triggered access occasions indicated based on the frequency resource indication field of the A-IoT paging message.

[0362] For example, the access random ID message may be transmitted using a first value (e.g., a value of a frequency index or a small frequency shift factor) associated with a frequency domain resource of the access occasion.

[0363] In S920, the device receives a Random ID Response message from the reader. For example, the Random ID Response message may mean Msg2 based on at least one of the above-described methods #1 to #3.

[0364] In S930, the device transmits a Device to Reader (D2R) message to the reader based on the random ID response message. For example, the D2R message may mean Msg3 based on at least one of the methods #1 to #3 described above.

[0365] According to one embodiment, the random ID response message may include at least one of i) one or more second ID fields (e.g., Echoed Random ID field(s)), ii) one or more frequency index fields (e.g., Frequency Index field(s)), and / or iii) one or more time index fields (e.g., Time Index field(s)). This embodiment may be based on Method #1.

[0366] For example, the random ID response message may include one or more second ID fields. In this case, the random ID response message may further include one or more time index fields.

[0367] For example, the random ID response message may include i) one or more second ID fields and ii) one or more frequency index fields. In this case, the random ID response message may further include one or more time index fields.

[0368] For example, the above random ID response message may include i) one or more second ID fields and ii) one or more time index fields.

[0369] For example, the random ID response message may include i) one or more second ID fields, ii) one or more frequency index fields, and iii) one or more time index fields.

[0370] As a specific example, among the one or more second ID fields, the value indicated by the second ID field may be identical to the value of the first ID field.

[0371] As a specific example, among the one or more frequency index fields, the value indicated by the frequency index field may match the first value. The value indicated by the frequency index field may be the frequency index value of the access occasion associated with the second ID field (e.g., small frequency shift factor value).

[0372] As a specific example, among the one or more time index fields mentioned above, the value indicated by the time index field may match the second value. The second value may be associated with the time domain resource of the access occasion.

[0373] According to one embodiment, the random number may be a 16-bit random number.

[0374] According to one embodiment, the length of the second ID field may be 16 bits. Specifically, the length of each of the one or more second fields may be 16 bits.

[0375] According to one embodiment, the random ID response message may be received based on monitoring of the PRDCH (Physical Reader-to-Device Channel). The monitoring may be related to R2D (Reader to Device) messages (e.g., A-IoT paging message, Access Trigger message, Random ID Response message, R2D upper layer data transfer message, etc.).

[0376] According to one embodiment, the method may further include a step of receiving control information. Specifically, the device may receive control information from a reader. Based on the control information, information related to at least one random ID response message based on the PRDCH may be indicated. This embodiment may be based on Method #2 and / or Method #3. The step of receiving control information may be performed after S910.

[0377] According to one embodiment, based on the control information, the number (e.g., M) of at least one random ID response message to be transmitted by a Reader among all random ID response messages (e.g., N random ID response messages) associated with the PRDCH may be indicated. This embodiment may be based on Method #2.

[0378] According to one embodiment, based on the control information, i) information related to the at least one random ID response message and / or ii) information related to the window for monitoring may be indicated. This embodiment may be based on Method #2 and / or Method #3.

[0379] For example, based on the control information, it may be indicated whether another PRDCH is scheduled after the PRDCH within the window. This embodiment may be based on Method #3.

[0380] For example, based on the control information above, the number of PDRCHs to be transmitted by the reader within the window may be indicated. This embodiment may be based on Method #3.

[0381] For example, based on the control information, it may be indicated whether the PRDCH among the PRDCHs based on the window is the last PRDCH.

[0382] According to one embodiment, the control information may be based on L1 information or L2 information. Specifically, the control information may be based on L1 parameters (Layer 1, L1 parameter) or upper layer data (upper layer data).

[0383] According to one embodiment, the method may further include a step of receiving an A-IoT paging message. Specifically, the device may receive an ambient IoT paging message (Ambient IoT, A-IoT, paging message) from a reader. The step of receiving the A-IoT paging message may be performed prior to S910.

[0384] For example, a contention-based random access (CBRA) procedure may be initiated by the above A-IoT paging message.

[0385] For example, transmission by a reader may be R2D (Reader to Device) transmission, and transmission by a device may be D2R (Device to Reader) transmission.

[0386] According to one embodiment, the device and the reader may be based on devices operating based on one of four topologies related to Ambient IoT (see FIG. 1 to 5). Specifically, the reader may be i) a base station, ii) user equipment, iii) an intermediate node, or iv) an assisting node. The device may be an Ambient IoT (Internet of Things) device.

[0387] The operation based on the above-described S910 to S930, the control information reception step, and the A-IoT paging message reception step can be implemented by the device of FIG. 11. For example, referring to FIG. 11, the device (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operation based on S910 to S930, the control information reception step, and the A-IoT paging message reception step.

[0388] The embodiments described above will be explained in detail below in terms of the operation of the second device.

[0389] The control information transmission step and A-IoT paging message transmission step described below, S1010 to S1030, the control information reception step and the A-IoT paging message reception step described in FIG. 9, correspond to S910 to S930, the control information reception step and the A-IoT paging message reception step described in FIG. 9. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the second device operation described below can be replaced by the description / embodiment of FIG. 9 corresponding to the operation.

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

[0391] Referring to FIG. 10, a method according to another embodiment of the present specification includes a step of receiving a random ID message (S1010), a step of transmitting a random ID response message (S1020), and a step of receiving a D2R message (S1030).

[0392] In S1010, the Reader receives an Access Random ID message from the device based on an access occasion, the message including a first ID field (e.g., Random ID field) based on a random number.

[0393] For example, the access random ID message may mean Msg1 based on at least one of methods #1 to #3 described above. For example, the access random ID message may be received using a first value (e.g., a value of a frequency index or a small frequency shift factor) associated with a frequency domain resource of the access occasion.

[0394] In S1020, the reader transmits a Random ID Response message to the device. For example, the Random ID Response message may mean Msg2 based on at least one of the methods #1 to #3 described above.

[0395] In S1030, the reader receives a Device to Reader (D2R) message from the device based on the random ID response message. For example, the D2R message may mean Msg3 based on at least one of the methods #1 to #3 described above.

[0396] According to one embodiment, the random ID response message may include at least one of i) one or more second ID fields (e.g., Echoed Random ID field(s)), ii) one or more frequency index fields (e.g., Frequency Index field(s)), and / or iii) one or more time index fields (e.g., Time Index field(s)). As an example, the random ID response message may include i) one or more second ID fields and ii) one or more frequency index fields. In this case, the random ID response message may further include one or more time index fields.

[0397] As a specific example, among the one or more second ID fields, the value indicated by the second ID field may be identical to the value of the first ID field.

[0398] As a specific example, among the one or more frequency index fields, the value indicated by the frequency index field can match the first value.

[0399] According to one embodiment, the method may further include a control information transmission step. Specifically, the reader may transmit control information to the device. The control information transmission step may be performed after S1010.

[0400] According to one embodiment, the method may further include a step of transmitting an A-IoT paging message. Specifically, a reader may transmit an ambient IoT paging message (Ambient IoT, A-IoT, paging message) to a device. The step of transmitting the A-IoT paging message may be performed prior to S1010.

[0401] Operations based on the above-described S1010 to S1030, control information transmission step, and A-IoT paging message transmission step can be implemented by the device of FIG. 11. For example, referring to FIG. 11, a reader (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S1010 to S1030, control information transmission step, and A-IoT paging message transmission step.

[0402] 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. 11.

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

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

[0405] 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).

[0406] 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.

[0407] 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.

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

[0409] 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).

[0410] 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.

[0411] 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.

[0412] 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.

[0413] 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.

[0414] 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.

[0415] 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. Regarding the method, A step of transmitting an Access Random ID message, including a first ID field based on a random number, by a device based on an access occasion, The above access random ID message is transmitted using a first value associated with the frequency domain resource of the access occasion; The step of receiving a Random ID Response message by the above device; and The above device includes the step of transmitting a D2R (Device to Reader) message based on the random ID response message, The above random ID response message includes i) one or more second ID fields and ii) one or more frequency index fields, and The value indicated by the second ID field among the one or more second ID fields is identical to the value of the first ID field, and A method characterized in that the value indicated by the frequency index field among the one or more frequency index fields above matches the first value.

2. In Paragraph 1, A method characterized in that the above random ID response message further includes one or more time index fields.

3. In Paragraph 1, A method characterized in that the above random number is a 16-bit random number.

4. In Paragraph 1, A method characterized in that the length of the second ID field is 16 bits.

5. In Paragraph 1, A method characterized by receiving the above random ID response message based on monitoring of the PRDCH (Physical Reader-to-Device Channel).

6. In Paragraph 5, The above method further includes the step of receiving control information, and A method characterized by indicating information related to at least one random ID response message based on the PRDCH based on the above control information.

7. In Paragraph 6, A method characterized by indicating the number of at least one random ID response message to be transmitted by a reader among all random ID response messages associated with the PRDCH based on the above control information.

8. In Paragraph 6, A method characterized by indicating, based on the above control information, i) information related to the at least one random ID response message and / or ii) information related to the window for monitoring.

9. In Paragraph 8, A method characterized by indicating whether another PRDCH is scheduled after the PRDCH within the window based on the above control information.

10. In Paragraph 8, A method characterized by indicating the number of PDRCHs to be transmitted by a reader within the window based on the above control information.

11. In Paragraph 8, A method characterized by indicating whether the PRDCH among the PRDCHs based on the window is the last PRDCH based on the above control information.

12. In Paragraph 6, A method characterized in that the above control information is based on L1 parameters (Layer 1, L1 parameter) or upper layer data (upper layer data).

13. In Paragraph 1, A method characterized by further including the step of receiving an ambient IoT paging message (Ambient IoT, A-IoT, paging message) by the above device.

14. In Paragraph 13, A method characterized by initiating a contention-based random access (CBRA) procedure by the above A-IoT paging message.

15. 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 14, based on execution by the one or more processors.

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

17. In a non-transitory computer-readable storage medium for storing instructions, A non-transitory computer-readable storage medium characterized by instructions executable by one or more processors that cause the device to perform all steps of the method according to any one of claims 1 to 14.

18. Regarding the method, A step of receiving an Access Random ID message containing a first ID field based on a random number by a Reader based on an access occasion, The above access random ID message is received using a first value associated with the frequency domain resource of the access occasion; A step of transmitting a Random ID Response message by the above reader; and The above reader includes the step of receiving a D2R (Device to Reader) message based on the above random ID response message, The above random ID response message includes i) one or more second ID fields and ii) one or more frequency index fields, and The value indicated by the second ID field among the one or more second ID fields is identical to the value of the first ID field, and A method characterized in that the value indicated by the frequency index field among the one or more frequency index fields above matches the first value.

19. Regarding 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, causing the reader to perform all steps of the method according to claim 18.

Images