Method and device for performing random access procedure

The proposed method optimizes power consumption and maintenance costs by coordinating MSG2 monitoring settings and transmission times in Ambient IoT devices, addressing the inefficiencies of battery-less operations and supporting wider coverage.

WO2026235387A1PCT designated stage Publication Date: 2026-11-12KT CORP
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

Existing IoT devices face challenges in efficient power management, particularly in battery-less operations, leading to high maintenance costs and environmental issues, and there is a need for improved energy management methods to support a large number of interconnected devices.

Method used

A method and apparatus for performing a random access procedure in an Ambient IoT environment, where terminals and reader devices coordinate MSG2 monitoring settings and transmission times based on different time offsets and resource allocations to optimize power consumption.

Benefits of technology

Enables efficient MSG2 monitoring by Ambient IoT terminals, reducing power consumption and maintenance costs while supporting wider coverage and battery-less operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005976_12112026_PF_FP_ABST
    Figure KR2026005976_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present embodiments provide a method by which an ambient IoT terminal performs a random access procedure, the method comprising the steps of: receiving MSG2 monitoring configuration information from a reader device; transmitting MSG1 by occupying a specific resource among one or more time domain resources allocated to the terminal; determining a monitoring start time point on the basis of the MSG2 monitoring configuration information and a MSG2 transmission scheme of the reader device; and monitoring for MSG2 from the determined monitoring start time point.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for performing a random access procedure

[0001] The embodiments propose a method and apparatus for performing a random access procedure in a next-generation wireless access network (in this disclosure, "5G", "NR [New Radio]", "5G-Advanced", "6G" or subsequent 3GPP wireless access networks).

[0002] In recent years, the Internet of Things (IoT) has attracted significant attention in the field of wireless communication. It is expected that an increasing number of objects will become interconnected to improve productivity efficiency and enhance the comfort of daily life. Further reducing the size, complexity, and power consumption of IoT devices enables the deployment of tens or even hundreds of billions of IoT devices for various applications, thereby providing added value across the entire value chain. However, it is impossible to power all IoT devices with batteries, and since batteries must be manually replaced or recharged, this can lead to high maintenance costs, serious environmental issues, and even safety risks for some use cases.

[0003] In this regard, efficient power consumption of IoT devices is required, and accordingly, there is a need for specific designs regarding methods to manage the energy of IoT devices more efficiently.

[0004] Embodiments of the present disclosure may provide a method and apparatus for performing a random access procedure in an Ambient IoT (hereinafter also referred to as A-IoT) environment.

[0005] In one aspect, the present embodiments provide a method for an Ambient IoT terminal to perform a random access procedure, comprising the steps of receiving a second message (MSG2) monitoring setting information from a reader device, transmitting a first message (MSG1) by occupying a specific resource among one or more time domain resources allocated to the terminal, determining a monitoring start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device, and monitoring MSG2 from the determined monitoring start time, wherein the monitoring start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and based on the occupied specific resource.

[0006] In another aspect, the present embodiments provide a method for a reader device to perform a random access procedure in an Ambient IoT system, comprising the steps of: transmitting a second message (MSG2) monitoring setting information to an Ambient IoT terminal; receiving a first message (MSG1) from the terminal through a specific resource among one or more time domain resources allocated to the terminal; determining a transmission start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device; and transmitting MSG2 to the terminal at the determined transmission start time. The transmission start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and based on a specific resource occupied by the terminal.

[0007] In another aspect, the embodiments may provide an Ambient IoT terminal that performs a random access procedure, comprising a transmitter, a receiver, and a control unit that controls the operation of the transmitter and the receiver. The control unit receives a second message (MSG2) monitoring setting information from a reader device, occupies a specific resource among one or more time domain resources allocated to the terminal to transmit a first message (MSG1), determines a monitoring start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device, and monitors MSG2 from the determined monitoring start time, wherein the monitoring start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and based on the occupied specific resource.

[0008] In another aspect, the present embodiments may provide a reader device that performs a random access procedure, comprising a transmitter, a receiver, and a control unit that controls the operation of the transmitter and the receiver. The control unit transmits a second message (MSG2) monitoring setting information to an Ambient IoT terminal, receives a first message (MSG1) from the terminal through a specific resource among one or more time domain resources allocated to the terminal, determines a transmission start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device, transmits MSG2 to the terminal at the determined transmission start time, and the transmission start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and based on a specific resource occupied by the terminal.

[0009] According to the embodiments, a method and apparatus for performing a random access procedure in an ambient IoT environment can be provided.

[0010] In addition, based on the MSG2 transmission method transmitted by the reader device and the number of supported time domain resources, Ambient IoT terminals can perform efficient MSG2 monitoring according to the MSG1 time resources they occupy.

[0011] FIG. 1 is a diagram briefly illustrating the structure of an NR wireless communication system to which the present embodiment can be applied.

[0012] FIG. 2 is a drawing illustrating the frame structure in an NR system to which the present embodiment can be applied.

[0013] FIG. 3 is a diagram illustrating a resource grid supported by wireless access technology to which the present embodiment can be applied.

[0014] FIG. 4 is a diagram illustrating the bandwidth part supported by the wireless access technology to which the present embodiment can be applied.

[0015] FIG. 5 is a diagram illustrating an exemplary synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0016] FIG. 6 is a diagram illustrating a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0017] Figure 7 is a diagram for explaining CORESET.

[0018] FIG. 8 is a diagram illustrating the Reader / Tag operations and tag state of RFID.

[0019] FIGS. 9 and FIGS. 10 are drawings illustrating a connectivity topology for an A-IoT network and device to which the present embodiment can be applied.

[0020] FIG. 11 is a diagram illustrating the procedure of the Access Stratum (AS) layer between an A-IoT terminal and a reader according to one embodiment.

[0021] FIG. 12 is a diagram illustrating a wireless interface protocol stack between an A-IoT terminal and a reader according to one embodiment.

[0022] FIG. 13 is a diagram illustrating a 3-step CBRA procedure according to one embodiment.

[0023] FIG. 14 is a diagram illustrating a CFRA procedure according to one embodiment.

[0024] FIG. 15 is a diagram illustrating R2D transmission corresponding to D2R of an FDMA-based D2R and multiple A-IoT terminals according to one embodiment.

[0025] FIG. 16 is a diagram illustrating an R2D transmission corresponding to D2R of a single A-IoT terminal and an FDMA-based D2R according to one embodiment.

[0026] FIG. 17 is a diagram illustrating R2D transmission corresponding to D2R of a single A-IoT terminal and FDMA-based D2R according to another embodiment.

[0027] FIG. 18 is a diagram illustrating R2D transmission corresponding to D2R of a TDMA-based D2R and multiple A-IoT terminals according to one embodiment.

[0028] FIG. 19 is a diagram illustrating R2D transmission corresponding to D2R of a single A-IoT terminal and a TDMA-based D2R according to one embodiment.

[0029] FIGS. 20 and 21 are drawings for explaining the MSG2 monitoring setting component of an A-IoT terminal for a common MSG2 transmission according to one embodiment.

[0030] FIGS. 22 and FIGS. 23 are drawings for illustrating the MSG2 monitoring setting component of an A-IoT terminal for separate MSG2 transmission according to one embodiment.

[0031] FIG. 24 is a diagram illustrating a procedure for an A-IoT terminal to perform random access according to one embodiment.

[0032] FIG. 25 is a diagram illustrating a procedure for a reader device to perform random access according to one embodiment.

[0033] FIG. 26 is a diagram illustrating one common MSG2 transmission (X=1) corresponding to one or more MSG1s according to one embodiment.

[0034] FIG. 27 is a diagram illustrating one common MSG2 transmission (X=2) corresponding to one or more MSG1s according to one embodiment.

[0035] FIG. 28 is a diagram illustrating one or more separate MSG2 transmissions (X=1) corresponding to one or more MSG1s according to one embodiment.

[0036] FIG. 29 is a diagram illustrating one or more separate MSG2 transmissions (X=2) corresponding to one or more MSG1s according to one embodiment.

[0037] FIG. 30 is a diagram showing the configuration of a terminal according to another embodiment.

[0038] FIG. 31 is a drawing showing the configuration of a reader device according to another embodiment.

[0039] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the exemplary drawings. In assigning reference numerals to the components of each drawing, the same components may have the same reference numeral as much as possible, even if they are shown in different drawings. Furthermore, in describing the embodiments, if it is determined that a detailed description of related known components or functions may obscure the essence of the technical concept, such detailed description may be omitted. Where terms such as "comprising," "having," or "consisting of" are used in this specification, other parts may be added unless "only" is used. Where a component is expressed in the singular, it may include a plural unless otherwise specified.

[0040] Additionally, terms such as first, second, A, B, (a), (b), etc., may be used to describe the components of the present disclosure. These terms are used merely to distinguish the components from other components, and the nature, order, sequence, or number of the components are not limited by such terms.

[0041] In describing the positional relationship of components, where it is stated that two or more components are "connected," "combined," or "joined," it should be understood that while the two or more components may be directly "connected," "combined," or "joined," they may also be "connected," "combined," or "joined" with other components "intervened." Here, the other components may be included in one or more of the two or more components that are "connected," "combined," or "joined" with one another.

[0042] In describing the temporal flow relationship regarding components, methods of operation, or methods of production, for example, when the temporal or sequential relationship is described using "after," "following," "next," or "before," it may include cases where the relationship is not continuous unless "immediately" or "directly" is used.

[0043] Meanwhile, where numerical values ​​or corresponding information regarding a component (e.g., levels, etc.) are mentioned, even without separate explicit notation, the numerical values ​​or corresponding information may be interpreted as including a range of error that may occur due to various factors (e.g., process factors, internal or external shocks, noise, etc.).

[0044] A wireless communication system in this specification refers to a system for providing various communication services, such as voice and data packets, using wireless resources, and may include a terminal, a base station, or a core network.

[0045] The embodiments disclosed below may be applied to wireless communication systems using various wireless access technologies. For example, the embodiments may be applied to various wireless access technologies such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), or NOMA (non-orthogonal multiple access). Furthermore, wireless access technology may refer not only to specific access technologies but also to communication technologies for each generation established by various telecommunication organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA may be implemented as a wireless technology such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA may be implemented as a wireless technology such as GSM (global system for mobile communications), GPRS (general packet radio service), or EDGE (enhanced datarates for GSM evolution). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronic Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink. As such, these embodiments can be applied to currently disclosed or commercialized radio access technologies, and can also be applied to radio access technologies currently under development or to be developed in the future.

[0046] Meanwhile, the term "terminal" in this specification is a comprehensive concept meaning a device including a wireless communication module that communicates with a base station in a wireless communication system. It should be interpreted as a concept that includes not only User Equipment (UE) in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), but also Mobile Station (MS), User Terminal (UT), Subscriber Station (SS), and wireless device in GSM. Furthermore, depending on the usage type, the terminal may be a user portable device such as a smartphone, or in a V2X communication system, it may refer to a vehicle or a device including a wireless communication module inside a vehicle. Additionally, in the case of a Machine Type Communication (MMC) system, it may refer to an MTC terminal, M2M terminal, URLLC terminal, etc., equipped with a communication module to perform machine type communication.

[0047] In this specification, "base station" or "cell" refers to an end that communicates with a terminal in terms of a network, and encompasses various coverage areas such as Node-B, eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node), Sector, Site, various types of antennas, BTS (Base Transceiver System), Access Point, Point (e.g., Transmitter Point, Receiver Point, Transceiver Point), Relay Node, Mega Cell, Macro Cell, Micro Cell, Pico Cell, Femto Cell, RRH (Remote Radio Head), RU (Radio Unit), and Small Cell. Additionally, "cell" may include a Bandwidth Part (BWP) in the frequency domain. For example, a serving cell may refer to the Activation BWP of a terminal.

[0048] Since there is a base station controlling one or more of the various cells listed above, the term "base station" can be interpreted in two senses. 1) It may refer to the device itself that provides a mega cell, macro cell, micro cell, pico cell, femto cell, or small cell in relation to a wireless area, or 2) it may refer to the wireless area itself. In 1), all devices that provide a specific wireless area are controlled by the same entity or interact to configure the wireless area collaboratively are referred to as base stations. Depending on the configuration method of the wireless area, a point, a transmitting / receiving point, a transmitting point, a receiving point, etc., are examples of a base station. In 2), the wireless area itself that receives or transmits a signal from the perspective of a user terminal or from the perspective of a neighboring base station may also be referred to as a base station.

[0049] In this specification, "Cell" may refer to a component carrier having coverage of a signal transmitted from a transmitting / receiving point or coverage of a signal transmitted from a transmitting / receiving point (transmission point or transmission / reception point), or the transmitting / receiving point itself.

[0050] Uplink (UL, or Uplink) refers to the method of transmitting and receiving data from a terminal to a base station, and Downlink (DL, or Downlink) refers to the method of transmitting and receiving data from a base station to a terminal. Downlink may refer to communication or a communication path from multiple transmission and reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission and reception points. In this case, in the downlink, the transmitter may be part of the multiple transmission and reception points, and the receiver may be part of the terminal. Additionally, in the uplink, the transmitter may be part of the terminal, and the receiver may be part of the multiple transmission and reception points.

[0051] The uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control Channel) and PUCCH (Physical Uplink Control Channel), and transmit and receive data by configuring data channels such as PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). In the following description, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also referred to as "transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH."

[0052] To clarify the explanation, the technical concept described below is based primarily on 3GPP LTE / LTE-A / NR (New RAT) communication systems, but the technical features are not limited to said communication systems.

[0053] Following research on 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of the ITU-R for next-generation radio access technology. Specifically, 3GPP develops LTE-A pro, which enhances LTE-Advanced technology to meet ITU-R requirements, and NR, a new communication technology distinct from 4G communication technology, as 5G communication technologies. Since both LTE-A pro and NR refer to 5G communication technology, the following description of 5G communication technology will focus on NR unless a specific technology is being identified.

[0054] The operational scenarios in NR define various operation scenarios by adding considerations for satellites, automobiles, and new verticals to the existing 4G LTE scenarios, and in terms of service, they support eMBB (Enhanced Mobile Broadband) scenarios, mMTC (Massive Machine Communication) scenarios which require low data rates and asynchronous access while having high terminal density and being deployed over a wide range, and URLLC (Ultra Reliability and Low Latency) scenarios which require high responsiveness and reliability and can support high-speed mobility.

[0055] To satisfy these scenarios, NR introduces a wireless communication system equipped with new waveform and frame structure technologies, low latency technology, mmWave support technology, and forward compatibility technology. In particular, the NR system presents various technical changes in terms of flexibility to provide forward compatibility. The main technical features of NR are explained below with reference to the drawings.

[0056]

[0057] <NR 시스템 일반>

[0058] FIG. 1 is a simplified diagram illustrating the structure of an NR system to which the present embodiment can be applied.

[0059] Referring to FIG. 1, the NR system is divided into a 5G Core Network (5GC) and an NR-RAN part. The NG-RAN consists of gNBs and ng-eNBs that provide control plane (RRC) protocol endpoints for the user plane (SDAP / PDCP / RLC / MAC / PHY) and User Equipment (UE). gNBs are interconnected with each other, or gNBs and ng-eNBs are interconnected via Xn interfaces. Each gNB and ng-eNB is connected to the 5GC via an NG interface. The 5GC may be configured to include an Access and Mobility Management Function (AMF), which is responsible for control plane functions such as terminal access and mobility control, and a User Plane Function (UPF), which is responsible for control functions for user data. The NR system includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

[0060] gNB refers to a base station that provides NR user plane and control plane protocol terminations to a terminal, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol terminations to a terminal. The base station described in this specification should be understood as encompassing both gNB and ng-eNB, and may also be used to refer to gNB or ng-eNB separately as necessary.

[0061] <NR 웨이브 폼, 뉴머롤러지 및 프레임 구조>

[0062]

[0063] In NR, CP-OFDM waveforms using a cyclic prefix are used for downlink transmission, and CP-OFDM or DFT-s-OFDM are used for uplink transmission. OFDM technology is easy to combine with MIMO (Multiple Input Multiple Output) and has the advantage of allowing the use of low-complexity receivers along with high frequency efficiency.

[0064] Meanwhile, in NR, since the requirements for data rate, latency, coverage, etc. differ for each of the three scenarios mentioned above, it is necessary to efficiently satisfy the requirements for each scenario through the frequency bands that constitute an arbitrary NR system. To this end, a technology has been proposed to efficiently multiplex wireless resources based on multiple different numerologies.

[0065] Specifically, the NR transmission numerator is determined based on sub-carrier spacing and CP (Cyclic prefix), and as shown in Table 1 below, the μ value is used as an exponential value of 2 based on 15 kHz and changes exponentially.

[0066] μ서브캐리어 간격Cyclic prefixSupported for dataSupported for synch015NormalYesYes130NormalYesYes260Normal, ExtendedYesNo3120NormalYesYes4240NormalNoYes

[0067] As shown in Table 1 above, the numerators of NR can be classified into five types based on the subcarrier spacing. This differs from LTE, one of the 4G communication technologies, where the subcarrier spacing is fixed at 15 kHz. Specifically, the subcarrier spacings used for data transmission in NR are 15, 30, 60, and 120 kHz, while the subcarrier spacings used for synchronization signal transmission are 15, 30, 12, and 240 kHz. Additionally, extended CP applies only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR defines a frame with a length of 10ms, composed of 10 subframes of equal length of 1ms. A single frame can be divided into 5ms half-frames, and each half-frame contains 5 subframes. In the case of a 15 kHz subcarrier interval, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. FIG. 2 is a diagram illustrating the frame structure in an NR system to which the present embodiment can be applied. Referring to FIG. 2, in the case of a normal CP, the slot is fixedly composed of 14 OFDM symbols, but the length in the time domain of the slot may vary depending on the subcarrier interval. For example, in the case of a numeral with a 15 kHz subcarrier interval, the slot is composed of a length of 1 ms, which is the same length as the subframe. In contrast, in the case of a numeral with a 30 kHz subcarrier interval, the slot is composed of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, the subframe and the frame are defined with a fixed time length, while the slot is defined by the number of symbols, and the time length may vary depending on the subcarrier interval.

[0068] Meanwhile, NR defines the basic unit of scheduling as a slot and introduced mini-slots (or sub-slots or non-slot based schedules) to reduce transmission delay in the wireless section. Using a wide subcarrier spacing reduces transmission delay in the wireless section because the length of a single slot becomes inversely shorter. Mini-slots (or sub-slots) are designed for efficient support of URLLC scenarios and allow scheduling in units of 2, 4, or 7 symbols.

[0069] Furthermore, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within a single slot. To reduce HARQ latency, a slot structure was defined that allows HARQ ACK / NACK to be transmitted directly within the transmission slot; this slot structure is described as a self-contained structure.

[0070] NR is designed to support a total of 256 slot formats, of which 62 are used in 3GPP Rel-15. Additionally, it supports common frame structures that form FDD or TDD frames through various slot combinations. For example, it supports slot structures where all slot symbols are set to downlink, slot structures where all symbols are set to uplink, and slot structures where downlink and uplink symbols are combined. Furthermore, NR supports data transmission being distributed and scheduled across one or more slots. Therefore, base stations can use a Slot Format Indicator (SFI) to inform a terminal whether a slot is a downlink slot, an uplink slot, or a flexible slot. Base stations can indicate the slot format by using the SFI to indicate an index of a table configured via UE-specific RRC signaling, or they can indicate it dynamically via Downlink Control Information (DCI) or statically or semi-statically via RRC.

[0071] <NR 물리 자원 >

[0072] Regarding physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.

[0073] An antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the large-scale property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0074] FIG. 3 is a diagram illustrating a resource grid supported by wireless access technology to which the present embodiment can be applied.

[0075] Referring to FIG. 3, a resource grid may exist for each numerator because NR supports multiple numerators on the same carrier. Additionally, a resource grid may exist depending on the antenna port, subcarrier spacing, and transmission direction.

[0076] A resource block consists of 12 subcarriers and is defined only in the frequency domain. Additionally, a resource element consists of one OFDM symbol and one subcarrier. Therefore, as shown in Fig. 3, the size of a single resource block can vary depending on the subcarrier spacing. Furthermore, NR defines "Point A," which serves as a common reference point for the resource block grid, as well as common resource blocks, virtual resource blocks, etc.

[0077] FIG. 4 is a diagram illustrating the bandwidth part supported by the wireless access technology to which the present embodiment can be applied.

[0078] In NR, unlike LTE where the carrier bandwidth is fixed at 20 MHz, the maximum carrier bandwidth is set from 50 MHz to 400 MHz depending on the subcarrier interval. Therefore, it is not assumed that all terminals use this entire carrier bandwidth. Accordingly, in NR, as shown in Fig. 4, a Bandwidth Part (BWP) can be designated within the carrier bandwidth for the terminal to use. Additionally, a Bandwidth Part is associated with a single numerator and consists of a subset of a continuous common resource block, and can be dynamically activated over time. Up to four Bandwidth Parts are configured for the uplink and downlink respectively, and data is transmitted and received using the Bandwidth Part activated at a given time.

[0079] In the case of paired spectrum, the uplink and downlink bandwidth parts are set independently, whereas in the case of unpaired spectrum, the downlink and uplink bandwidth parts are paired to share a center frequency in order to prevent unnecessary frequency re-tuning between downlink and uplink operations.

[0080] <NR 초기 접속>

[0081] In NR, the terminal performs cell search and random access procedures to connect to the base station and perform communication.

[0082] Cell search is a procedure in which a terminal uses a Synchronization Signal Block (SSB) transmitted by a base station to synchronize with the corresponding base station's cell, obtain a physical layer cell ID, and acquire system information.

[0083] FIG. 5 is a diagram illustrating an exemplary synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0084] Referring to FIG. 5, the SSB consists of a PSS (primary synchronization signal) and an SSS (secondary synchronization signal) each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

[0085] The terminal monitors the SSB in the time and frequency domains and receives the SSB.

[0086] SSBs can be transmitted up to 64 times within 5ms. Multiple SSBs are transmitted via different transmission beams within the 5ms timeframe, and the terminal performs detection by assuming that an SSB is transmitted every 20ms based on a specific beam used for transmission. The number of beams available for SSB transmission within the 5ms timeframe can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted at 3GHz or lower, up to 8 beams in the frequency band from 3GHz to 6GHz, and up to 64 different beams can be used to transmit SSBs in the frequency band above 6GHz.

[0087] Two SSBs are included in a single slot, and the starting symbol and number of repetitions within the slot are determined according to the subcarrier interval as follows.

[0088] Meanwhile, unlike the SS of conventional LTE, the SSB is not transmitted at the center frequency of the carrier bandwidth. That is, the SSB can be transmitted even at locations other than the center of the system band, and multiple SSBs can be transmitted across the frequency domain when broadband operation is supported. Accordingly, the terminal monitors the SSB using a synchronization raster, which is a candidate frequency location for monitoring the SSB. The carrier raster, which is information on the center frequency location of the channel for initial connection, and the synchronization raster were newly defined in NR, and the synchronization raster is set with a wider frequency interval compared to the carrier raster, thereby supporting fast SSB search by the terminal.

[0089] The terminal can obtain the MIB through the SSB's PBCH. The Master Information Block (MIB) contains minimum information for the terminal to receive the Remaining Minimum System Information (RMSI) broadcast by the network. Additionally, the PBCH may include information regarding the location of the first DM-RS symbol in the time domain, information for the terminal to monitor SIB1 (e.g., SIB1 numeral information, information related to SIB1 CORESET, search space information, PDCCH related parameter information, etc.), and offset information between the Common Resource Block and the SSB (the absolute location of the SSB within the carrier is transmitted via SIB1). Here, the SIB1 numeral information is applied identically to some messages used in the random access procedure for the terminal to connect to the base station after completing the cell search procedure. For example, the SIB1 numeral information may be applied to at least one of messages 1 to 4 for the random access procedure.

[0090] The aforementioned RMSI may refer to SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., 160ms) from the cell. SIB1 contains information necessary for the terminal to perform the initial random access procedure and is transmitted periodically via PDSCH. To receive SIB1, the terminal must receive the numerology information used for transmitting SIB1 and the CORESET (Control Resource Set) information used for scheduling SIB1 via PBCH. The terminal checks the scheduling information for SIB1 using SI-RNTI within the CORESET and obtains SIB1 on the PDSCH according to the scheduling information. The remaining SIBs, excluding SIB1, may be transmitted periodically or upon the terminal's request.

[0091] FIG. 6 is a diagram illustrating a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0092] Referring to FIG. 6, when cell search is completed, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted via PRACH. Specifically, the random access preamble is transmitted to the base station via PRACH, which consists of a series of radio resources in specific slots that are repeated periodically. Generally, when the terminal initially connects to a cell, a contention-based random access procedure is performed, and when performing random access for Beam Failure Recovery (BFR), a non-contention-based random access procedure is performed.

[0093] The terminal receives a random access response for the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), an UL Grant (uplink radio resource), a temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier), and a TAC (Time Alignment Command). Since a single random access response may contain random access response information for one or more terminals, the random access preamble identifier may be included to indicate which terminal the included UL Grant, temporary C-RNTI, and TAC are valid for. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the terminal to coordinate uplink synchronization. The random access response may be indicated by the random access identifier on the PDCCH, namely the RA-RNTI (Random Access - Radio Network Temporary Identifier).

[0094] A terminal that receives a valid random access response processes the information contained in the random access response and performs a transmission scheduled to the base station. For example, the terminal applies a TAC and stores a temporary C-RNTI. Additionally, using a UL Grant, it transmits data stored in the terminal's buffer or newly generated data to the base station. In this case, information that can identify the terminal must be included.

[0095] Finally, the terminal receives a downlink message to resolve competition.

[0096] <NR CORESET>

[0097] The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) with a length of 1 to 3 symbols, and transmits uplink / downlink scheduling information, SFI (Slot format Index), TPC (Transmit Power Control) information, etc.

[0098] In this way, NR introduced the concept of CORESET to ensure system flexibility. CORESET (Control Resource Set) refers to time-frequency resources for downlink control signals. A terminal can decode control channel candidates by using one or more search spaces from the CORESET time-frequency resources. Quasi CoLocation (QCL) assumptions were established for each CORESET, and these are used to indicate characteristics regarding the analog beam direction in addition to the characteristics assumed by conventional QCL, such as delay spread, Doppler spread, Doppler shift, and mean delay.

[0099] Figure 7 is a diagram for explaining CORESET.

[0100] Referring to FIG. 7, CORESET can exist in various forms within a single slot and within the carrier bandwidth, and in the time domain, CORESET can be composed of up to 3 OFDM symbols. Additionally, CORESET is defined as a multiple of 6 resource blocks up to the carrier bandwidth in the frequency domain.

[0101] The first CORESET is specified via the MIB as part of the initial bandwidth part configuration to enable the reception of additional configuration and system information from the network. After establishing a connection with the base station, the terminal can be configured by receiving one or more CORESET information via RRC signaling.

[0102] Wider bandwidth operations

[0103] In the case of existing LTE systems, scalable bandwidth operation was supported for any LTE Component Carrier (CC). That is, depending on the frequency deployment scenario, any LTE operator could configure a bandwidth ranging from a minimum of 1.4 MHz to a maximum of 20 MHz when configuring a single LTE CC, and normal LTE terminals supported a transmit / receive capability of 20 MHz bandwidth for a single LTE CC.

[0104] However, in the case of NR, the design is made to enable support for NR terminals with different transmit / receive bandwidth capabilities through a single wideband NR CC. Accordingly, it is required to configure one or more bandwidth parts (BWPs) consisting of subdivided bandwidths for any NR CC, and to support flexible wider bandwidth operation through different bandwidth part configurations and activations for each terminal.

[0105] Specifically, in NR, one or more bandwidth parts can be configured through a single serving cell configured from the perspective of a terminal, and the terminal is defined to activate one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) in the serving cell to use for uplink / downlink data transmission and reception. In addition, for terminals where multiple serving cells are configured, i.e., terminals to which CA is applied, it is defined to activate one downlink bandwidth part and / or uplink bandwidth part for each serving cell to use the wireless resources of the serving cell for uplink / downlink data transmission and reception.

[0106] Specifically, an initial bandwidth part for the initial access procedure of a terminal is defined in any serving cell, and one or more terminal-specific (UE-specific) bandwidth parts are configured for each terminal through dedicated RRC signaling, and a default bandwidth part for a fallback operation can also be defined for each terminal.

[0107] However, depending on the capability and bandwidth part(s) configuration of the terminal in any serving cell, it may be defined to simultaneously activate and use multiple downlink and / or uplink bandwidth parts, but in NR rel-15, it is defined to activate and use only one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) at any time in any terminal.

[0108] In this specification, frequencies, frames, subframes, resources, resource blocks, regions, bands, subbands, control channels, data channels, synchronization signals, various reference signals, various signals, or various messages related to NR (New Radio) may be interpreted in the sense used in the past or present, or in various senses used in the future.

[0109]

[0110] Below, we will specifically explain how to perform a random access procedure in an Ambient IoT environment with reference to the relevant drawings.

[0111] The present disclosure relates to a monitoring timing control technique for efficiently receiving R2D (Reader-to-Device) messages or MSG2 by an Ambient IoT terminal (also referred to as an Ambient IoT device, Ambient IoT apparatus, or A-IoT terminal in the present disclosure) performing a random access procedure in an Ambient Internet of Things (Ambient IoT; referred to as Ambient IoT or A-IoT in the present disclosure) system of a 3GPP (3rd Generation Partnership Project) wireless access network (hereinafter referred to as "5G" or "NR [New Radio]" in the present disclosure) or a next-generation wireless access network (hereinafter referred to as "5G-Advanced or 6G" in the present disclosure). Ambient IoT terminals that receive R2D messages and PRDCH containing resource information separated by different times and frequencies or triggering random access from a reader device can obtain MSG2 monitoring start timing and monitoring interval setting information after MSG1 transmission through the method proposed in the present disclosure, and can efficiently receive MSG2 based on this.

[0112] In recent years, IoT technology has garnered significant attention in wireless communication. IoT technology has evolved to enable a greater number of interconnected objects, thereby improving industrial productivity and quality of life. NB-IoT and eMTC technologies are examples of this. However, to build a more effective IoT ecosystem, improvements are needed in various aspects, such as the size, form factor, price, complexity, power consumption, and coverage of IoT devices.

[0113] RFID is a representative technology service of the IoT. The advantages of RFID include very low complexity, and RFID tags have a very small form factor. However, RFID supports a very narrow coverage area with a reading distance of only a few meters, is labor-intensive due to handheld scanning, and requires high deployment costs due to the installation costs of RFID portals / gates. Therefore, RFID has limitations in supporting seamless service and coverage in large-scale networks.

[0114] To meet these demands, research on Ambient IoT technology has been conducted. Ambient IoT terminals feature a lower form factor compared to conventional IoT terminals and support energy harvesting based on battery-less operation and minimal energy storage capability, enabling them to operate without charging or with minimal power consumption. Furthermore, research is underway to support wider coverage based on higher power efficiency and to enable the utilization of RF signals supported by existing networks.

[0115] 3GPP is conducting research on protocol stacks and signaling procedures that take into account the low form factor and battery capacity characteristics of Ambient IoT terminals, such as less than 1 μW or less than several hundred μW. In particular, definitions are being made for the paging message functionality, which is the first message transmitted by a reader or base station to an Ambient IoT terminal for wireless access of the Ambient IoT terminal, and the random access procedure of the Ambient IoT terminal.

[0116] FIG. 8 is a diagram illustrating the Reader / Tag operations and tag state of RFID.

[0117] RFID technology, the foundation of Ambient IoT technology, is "EPC TM It is defined in the document "Radio-Frequency Identity Protocols Generation-2 UHF RFID". The document defines the protocol between the Reader and the Tag and adopts a slotted-ALOHA-based random access procedure. As shown in Fig. 8, there are three main "Select, Inventory, Access" operations.

[0118] The Select operation is an action in which the Reader selects one or more tag populations, and consists of "Select" and "Challenge" commands. At this time, the Tag enters the Ready state. The Select command is a mandatory operation, while the Challenge command is optional. The Select command allows the Reader to select a set of Tags based on user-defined criteria. The Inventory operation prepares for Access by having the Reader identify and detect each Tag, and generating a unique random number based on commands and responses with each Tag. The Access operation involves the Reader communicating with each Tag to perform procedures such as Read, Write, and Authenticate.

[0119] In the following, the method by which an ambient IoT terminal performs a random access procedure will be explained in detail with reference to the relevant drawings.

[0120] In the present disclosure, the ambient IoT device may be referred to by various terms such as terminal, ambient IoT terminal, A-IoT terminal, ambient IoT device, IoT device, and IoT terminal. Additionally, the reader may be referred to by various terms such as reader device, reader device, base station, intermediate node, and general terminal, and may include a base station of the aforementioned topology 1 or an intermediate node of topology 2, for example, a UE. Furthermore, the carrier wave node (CW node) is a device that transmits carrier waves for energy harvesting and may include a base station, a reader, or a CW node. Additionally, in describing the link between the reader and the ambient IoT device, transmission from the reader to the ambient IoT device is referred to as R2D (Reader-to-Device) transmission, and conversely, transmission from the ambient IoT device to the reader is referred to as D2R (Device-to-Reader) transmission. Additionally, the physical channel for R2D transmission is referred to as PRDCH (Physical Reader-to-Device Channel), and the physical channel for D2R transmission is referred to as PDRCH (Physical Device-to-Reader Channel). However, these terms are provided as examples and are not limited thereto; other terms may be used if the technical concept of the present disclosure can be applied substantially identically.

[0121] For example, Ambient IoT terminals can be classified into three types as shown in Table 2 below.

[0122] DeviceTypeEnergyStoragePeak PowerConsumptionAmplificationUL Independentsignal generationUL Tx methodPassiveDevice 1Yes≤ 1 μWNoNoBackscatteringfrom external CWDevice 2aYes≤ a few hundred μWYes (DL and / or UL)NoBackscatteringfrom external CWActiveDevice 2bYes≤ a few hundred μWYes (DL and / or UL)YesGenerated internally

[0123] In Table 2, the difference between Passive and Active lies in the presence or absence of independent signal generation functions and hardware within the Ambient IoT terminal. It is defined as Passive if there is no independent signal generation function for uplink signal transmission, and Active if there is. Device 1 has a maximum power consumption of 1 μW or less and lacks independent signal generation and amplification functions. Additionally, the uplink of the Ambient IoT terminal is transmitted via backscattering of the external carrier wave signal. Device 2a has a maximum power consumption of several hundred μW or less, does not support independent signal generation, but supports UL / DL amplification functions. Furthermore, UL is transmitted via backscattering of the external carrier wave signal. Device 2b has a maximum power consumption of several hundred μW or less and supports independent signal generation and UL / DL amplification functions. Additionally, UL is transmitted through the device's internal signal generation.

[0124] Meanwhile, the common feature of Device 1, 2a, and 2b discussed by 3GPP to date is that they are equipped with energy storage inside the Ambient IoT terminal. However, Ambient IoT terminals may have energy storage of limited capacity depending on the topology and deployment scenario. In this case, limited energy storage refers to a storage device composed of small-sized capacitors. To support seamless communication between a Reader and an Ambient IoT device, protocols and signaling to support energy harvesting need to be defined.

[0125] FIGS. 9 and FIGS. 10 are drawings illustrating a connectivity topology for an A-IoT network and device to which the present embodiment can be applied.

[0126] Discussions regarding Ambient IoT topologies are ongoing in the standard. FIGS. 9 and FIGS. 10 are Ambient IoT topologies applicable in the present disclosure, and topologies 3 and 4 defined in TR 38.848 are also applicable.

[0127] It was decided to support paging messages at the Access Stratum (AS) layer between Ambient IoT terminals and readers / base stations, but since existing paging messages are difficult to support, A-IoT paging messages are newly defined. The purpose of A-IoT paging messages is to identify Ambient IoT terminal(s), select / determine a radio resource, and send a Device-to-Reader (D2R) response message to the reader.

[0128] To identify A-IoT device(s), the paging message may include identifier information types in the form of Table 3.

[0129] Cases Information Type Recipient Case 1 Single A-IoT device ID A single A-IoT Device Case 2 Group ID Multiple A-IoT device(s) mapped to a Group ID Case 3 No ID-related information All A-IoT device(s) receiving A-IoT paging messages Case 4 Multiple A-IoT device IDs Multiple A-IoT device IDs

[0130] In relation to the radio resource selection / determination method for D2R (Msg1) transmission of the aforementioned Ambient IoT terminal, it can also be defined how (implicit / explicit / configured / preconfigured) or through which resource (dedicated / shared) D2R transmission is performed.

[0131] FIG. 11 is a diagram illustrating the procedure of the Access Stratum (AS) layer between an A-IoT terminal and a reader according to one embodiment. Referring to FIG. 11, the procedure of the AS layer between an A-IoT device and a reader is defined.

[0132] Step A is the step where the reader sends an A-IoT paging message to wake up the A-IoT device. In this case, the A-IoT paging message is triggered by the reader receiving a service request.

[0133] Step B is a step for random access between the reader and the A-IoT device. In this case, the D2R data transmission message includes the Device ID.

[0134] Step C is the data transmission step between the reader and the A-IoT device following random access by the A-IoT device. In this case, it can be a message intended to instruct the A-IoT device to perform a command service. Step C1 (R2D data transmission) is the step where the reader transmits a message to the device to transmit a command. Step C2 (D2R data transmission) is the step of transmitting a response message from the device that received the Step C1 message. Steps A, B, C1, and C2 may be configured differently depending on the type of service, such as inventory-only, command-only, or inventory and command.

[0135] FIG. 12 is a diagram illustrating a wireless interface protocol stack between an A-IoT terminal and a reader according to one embodiment.

[0136] Figure 12 shows the protocol stack for the wireless interface between an A-IoT device and a reader. As shown in Figure 12, since the device and the reader only support the PHY and MAC layers, they may not support the RRC, SDAP, PDCP, and RLC layers, which are layers higher than the MAC layer.

[0137] Meanwhile, for the random access procedure of Ambient IoT terminal(s), the Slotted-ALOHA random access procedure was adopted as the default. Contention-based (CBRA) and contention-free (CFRA) access procedures can be defined for a single terminal, a group of terminals, and all terminals. Additionally, "4-step", "3-step", and "2-step" random access type procedures based on CBRA and CFRA can also be defined.

[0138] FIG. 13 is a diagram illustrating a 3-step CBRA procedure according to one embodiment. FIG. 14 is a diagram illustrating a CFRA procedure according to one embodiment.

[0139] Figures 13 and 14 are examples of 3-step CBRA and CFRA procedures based on the standards agreed upon to date. A-IoT devices can select or know the CBRA and CFRA procedures explicitly or implicitly through device ID information or access occasion information within paging messages or A-IoT trigger messages.

[0140] Figure 13 shows an example of a 3-step CBRA procedure for an A-IoT device. Paging messages include identifier information for the purpose of distinguishing them from paging messages transmitted by other readers and avoiding duplicate reception. Paging or A-IoT trigger messages include wireless resource information or access occasion information required by the device to transmit a D2R (Msg1) message.

[0141] A device receiving a D2R(Msg1) message may randomly select one or more resources or access occasions consisting of time, frequency, or code sequences. The device may transmit D2R(Msg1) including random ID or AS ID information. The reason for including random ID and AS ID is to identify the device through the exchange of random ID / AS ID within Msg1 and Msg2, and to perform contention resolution and avoid contention conflicts.

[0142] A reader that receives Msg1 may transmit R2D (Msg2) to the device, including the random ID or AS ID information received via Msg1 and dedicated resource information for Msg3. If the random ID (or AS ID) included in the received Msg2 is identical to the random ID (AS ID) it transmitted in Msg1, the device determines that contention resolution has been successfully performed and may transmit Msg3. Msg3 may include a device ID and upper layer data information.

[0143] Msg4 may contain success / failure indication information to handle the reader's failure to receive Msg3, and it may not necessarily be a message that needs to be transmitted or received. If Msg4 transmission or reception is required, the Reader / base station transmits Msg4 to the A-IoT device(s), and this can be assumed to be a 4-step RA procedure. In addition to Msg4, additional message transmission or reception between the A-IoT device and the reader / base station may occur as needed. However, discussions are still ongoing regarding which random access procedure type the A-IoT device(s) will determine during the random access process, and what information is required in the paging and R2D messages transmitted by the Reader / base station for the random access decision.

[0144] Figure 14 illustrates an example of a CFRA procedure for an A-IoT device. The paging message includes a device ID and dedicated resource information for transmitting D2R messages. Due to the nature of CFRA, the device skips the contention resolution procedure and then transmits a D2R (Msg1) message via a dedicated resource and access occasion. The D2R (Msg1) message may include a device ID, upper layer data, and a random ID or AS ID. The random ID or AS ID can be used for the purpose of scheduling dedicated resources for A-IoT data transmission after random access and for device identification. If AS ID information is pre-configured in the device, the device transmits the AS ID; if AS ID information is not pre-configured in the device, it may transmit including a random ID.

[0145] A reader that receives D2R(Msg1) can transmit an R2D(Msg2) message containing dedicated resource information required for the device's A-IoT data transmission and random ID or AS ID information. The reader can decide which information to use between the random ID and the AS ID, and depending on the decision, can transmit Msg2 containing the necessary information.

[0146] FIG. 15 is a diagram illustrating an FDMA-based D2R and an R2D transmission corresponding to the D2R of multiple A-IoT terminals according to one embodiment. FIG. 16 is a diagram illustrating an FDMA-based D2R and an R2D transmission corresponding to the D2R of a single A-IoT terminal according to one embodiment. FIG. 17 is a diagram illustrating an FDMA-based D2R and an R2D transmission corresponding to the D2R of a single A-IoT terminal according to another embodiment. FIG. 18 is a diagram illustrating a TDMA-based D2R and an R2D transmission corresponding to the D2R of multiple A-IoT terminals according to one embodiment. FIG. 19 is a diagram illustrating a TDMA-based D2R and an R2D transmission corresponding to the D2R of a single A-IoT terminal according to one embodiment.

[0147] In addition, the standard is also discussing communication methods based on FDM(A), TDM(A), and CDM(A) in A-IoT systems. Detailed specification definitions are underway regarding support methods for frequency, time, or code sequence-based communication in wireless resource allocation, and discussions are also underway regarding which method to adopt. Figures 15, 16, 17, 18, and 19 illustrate various embodiments of various D2R and R2D transmission methods based on FDM(A) and / or TDM(A).

[0148] FIGS. 15 through 19 assume a procedure in which A-IoT devices perform random access in different steps, such as 2-step or 3-step. Based on this, when an A-IoT device transmits a D2R message using FDMA or TDMA, an embodiment according to the corresponding R2D transmission method is shown. However, this is not limited thereto, and there may be other additional embodiments.

[0149] FIG. 15 shows an example of FDMA-based D2R (Msg1) transmission and R2D (Msg2) transmission corresponding to D2R messages transmitted by multiple A-IoT devices. FIG. 16 shows an example of FDMA-based D2R (Msg1) transmission and sequential transmission of R2D (Msg2) messages corresponding to D2R messages transmitted by a single A-IoT device. This is a case where a reader that receives a D2R message transmitted by an A-IoT device transmits a corresponding R2D message individually and sequentially for each D2R message.

[0150] FIG. 17 is similar to the method of FIG. 16, but differs in that, from the reader's perspective, the transmission of R2D(Msg2) is triggered for device 2, which first receives the D2R message, and the D2R(Msg3) message transmitted by device 2 is executed first. Subsequently, it is a case where an R2D message corresponding to the D2R message transmitted by device 1 is transmitted.

[0151] FIG. 18 shows an example of TDMA-based D2R (Msg1) transmission and R2D (Msg2) transmission corresponding to D2R messages transmitted by multiple A-IoT devices. FIG. 19 shows a case where an A-IoT device transmits D2R (Msg1) based on TDMA and a reader transmits R2D messages through a different frequency than the A-IoT device. In this case, the reader can transmit a corresponding R2D message for each D2R message transmitted by the A-IoT device.

[0152] As shown in Table 4, D2R and R2D message transmission and reception and timing relationships can be defined considering the processing time of the A-IoT device and the reader / base station. R2D_min From the Reader's perspective, it refers to the minimum time required from the transmission of an R2D message to the transmission of the corresponding D2R message. D2R_min From the perspective of the Device, it refers to the minimum time required from the transmission of a D2R message to the transmission of the corresponding R2D message. D2R_max represents the maximum time from the device's perspective during which the corresponding R2D message must be transmitted from the transmission of the D2R message. In other words, the transmission timing of the R2D (Msg2) message corresponding to the D2R (Msg1) message is [T D2R_min , T D2R_max It can be defined that it must occur within the ] time interval. Additionally, consider that the reader can continuously transmit two different R2D transmissions to a single device. In this case, the minimum time between R2D transmissions is T R2D_R2D_min It can be defined as. Additionally, the same device can transmit two different D2R transmissions consecutively, and the minimum time between each D2R transmission is T. D2R_D2R_min It can be defined as.

[0153] T R2D_min: Minimum time between a R2D transmission and the corresponding D2R transmission following it.T D2R_min : Minimum time between a D2R transmission and the corresponding R2D transmission following it.T D2R_max : Maximum time between the D2R transmission and the corresponding R2D transmission following it, so that the R2D transmission timing is expected to be within [T D2R_min ,T D2R_max ], when a R2D transmission in response to a D2R transmission is expected for A-IoT Msg2 response to A-IoT Msg1 for the A-IoT device. See clause 6.3 for message descriptions.T R2D_R2D_min : Minimum time between two different consecutive R2D transmissions to the same A-IoT device.T D2R_D2R_min : Minimum time between two different consecutive D2R transmissions from the same A-IoT device.For the time interval between a R2D transmission and the corresponding D2R transmission following it, there are two options studied:Option 1: Define a maximum timeT R2D_maxbetween a R2D transmission and the corresponding D2R transmission following it, so that the device transmits D2R transmission within [T R2D_min ,T R2D_max ].Option 2: The corresponding D2R transmission timingT R2D Following a R2D transmission is determined based on the control information in the R2D transmission, whereT R2D ≥T R2D_min .

[0154] Meanwhile, a method for a reader that has received one or more MSG1s to transmit MSG2 in response thereto, and the start time and monitoring time interval of MSG2 monitoring for devices according to the MSG2 transmission method can be defined.

[0155] In relation to the operation of transmitting a downlink message (MSG2) in response to multiple uplink message (MSG1) transmissions initiated by an R2D (Reader-to-Device) transmission that triggers random access, the start time of MSG2 monitoring of the terminal, the monitoring interval, and the reference time setting may be defined.

[0156] The following examples may be considered regarding the starting time for MSG2 monitoring of a terminal. In one example, where a physical channel for MSG2 transmission (e.g., PRDCH) corresponds to a single MSG1 received from a single terminal, the starting time for MSG2 monitoring may be set separately for each MSG1 resource or commonly for multiple MSG1 resources. In another example, where a physical channel for MSG2 transmission (e.g., PRDCH) corresponds to multiple MSG1s received from different terminals, the starting time for MSG2 monitoring may be commonly set for multiple MSG1 resources.

[0157] Regarding the method for determining the time duration during which the terminal performs MSG2 monitoring, the following methods may be considered. In one example, Method 1, which determines based on a predefined value, may be considered. Alternatively, in another example, Method 2, which determines based on an indication included in an R2D transmission that triggers random access, may be considered. Here, Method 1 and Method 2 are not mutually exclusive and may be applied together in some cases.

[0158] The following options may be considered regarding the method for determining the reference time, which is a reference point used by the terminal to determine the MSG2 monitoring start time described above. As Option 1, the end time of the time domain resource to which the terminal transmitted MSG1 may be considered. As Option 2, the end time of the last resource among the X time domain resource(s) determined for MSG1 transmission may be considered. As Option 3, the end time of the R2D transmission that triggers random access may be considered. As Option 4, the end time of the R2D transmission carrying MSG2 may be considered. For example, the reference time is merely a time that the terminal uses as a basis to derive the MSG2 monitoring start time, and does not mean that the monitoring start time must always coincide with the reference time.

[0159] Additionally, regarding a method for transmitting a downlink message (MSG2) in response to multiple uplink message (MSG1) transmissions initiated by a Reader-to-Device (R2D) transmission that triggers random access, the following two options may be supported. As Option 1, a method may be supported in which a physical channel for MSG2 transmission (e.g., PRDCH) corresponds to a single Ambient Internet of Things (A-IoT) MSG1 received from a single terminal. As Option 2, a method may be supported in which a physical channel for MSG2 transmission (e.g., PRDCH) corresponds to multiple Ambient Internet of Things (A-IoT) MSG1s received from multiple different terminals. Further discussion is required regarding the maximum number of responses to MSG1 that can be accommodated within a single physical channel (PRDCH) for MSG2 transmission. Meanwhile, regarding a method for indicating a chip duration for an uplink transmission (D2R) from the terminal toward the reader, the following may be supported. The D2R chip interval is determined by a specific value among a set of predefined D2R chip interval values ​​and can be indicated within the R2D control information.

[0160] Meanwhile, the access occasion and the number of time-domain resource(s) X in the time-domain for MSG1 transmission are determined to be at most two. Additionally, the reader uses a 1-bit to inform the device whether the number of time-domain resources (X) for MSG1 transmission is one or two. If X is two, different devices can occupy different time-domain resources to transmit MSG1. Therefore, the device that selected the first resource in the time-domain and the device that selected the second resource will have different MGS1 transmission timings. Accordingly, an offset value T is used to derive the transmission start times of the different time-domain resources for the devices. offset1 and T offset2 A new one can be introduced.

[0161] T offset1 represents the offset value between the time the device completes receiving the R2D message that triggers random access and the start time of the first time-domain resource. offset2 represents the offset value between the start time of the first MSG1 time-domain resource and the start time of the second MSG1 time-domain resource. Therefore, devices can determine and transmit the MSG1 transmission timing based on the time-domain resource they occupy, based on the offset values. Here, after completing the MSG1 transmission, devices can start MSG2 monitoring by considering the reference time options for deriving the MSG2 monitoring start time described above. However, further consideration is needed regarding the reference time options and the methods for setting the device's MSG2 monitoring start time accordingly.

[0162] Meanwhile, regarding the transmission of an uplink message (MSG1) during a random access process triggered by a single R2D (Reader-to-Device) transmission, the following may apply. The number of D2R (Device-to-Reader) time domain resources (X) for the transmission of an uplink message (MSG1) may be supported as one (X=1) or two (X=2). The terminal transmits MSG1 from one of the allocated X time domain resources. All terminals must support this, but the specification impact (e.g., signaling overhead) on a reader that supports only X=1 may be configured to be minimized. On the other hand, for MSG3 transmitted in response to the reception of a downlink message (MSG2), only one time domain resource (X=1) is supported. The base station or reader may use 1-bit instruction information to inform the terminal of the number of time domain resources (X=1 or X=2) for MSG1 transmission.

[0163] From the perspective of the terminal, the following time offset (Toffset) may be defined in relation to the start time of the time domain resource for transmitting MSG1. When the number of time domain resources is one or two (X=1 or X=2), the start time of the first MSG1 time domain resource may be determined as the time after the first time offset (Toffset1) has elapsed from the time when the R2D transmission triggering random access has ended. Further consideration is needed regarding whether the first time offset (Toffset1) is defined in advance or implicitly / explicitly indicated through the R2D transmission, and the specific value taking into account the terminal's processing time (including the influence of Forward Error Correction (FEC)).

[0164] In the case where the number of time domain resources is two (X=2), the start time of the second MSG1 time domain resource can be derived by adding a second time offset (Toffset2) to the start time of the first MSG1 time domain resource. Further consideration is also needed regarding the specific method of determining the second time offset (Toffset2) (pre-definition, derivation based on rules, or whether it is instructed, etc.). Additionally, regarding the downlink monitoring time after uplink transmission, the terminal is not required to monitor the R2D transmission corresponding to itself until a minimum waiting time (TD2R_min) has elapsed from the time when its uplink (D2R) transmission ends.

[0165] Below, we will specifically explain how to perform a random access procedure in an Ambient IoT environment with reference to the relevant drawings.

[0166] The purpose of the present disclosure is to provide a method for A-IoT devices expecting to receive MSG2 from a reader after transmitting MSG1 to efficiently receive MSG2 based on information regarding the MSG2 monitoring start time and monitoring interval setting.

[0167] As shown in FIGS. 20 to 23, regarding a method in which a reader that has received MSG1 from one or more devices transmits MSG2 in response to MSG1, a method of transmitting a single common MSG2 corresponding to multiple MSG1s, or a method of transmitting individual MSG2s corresponding to a single MSG1, is discussed. Accordingly, regarding the MSG2 monitoring starting time of the device, the devices may set separate MSG2 monitoring starting times for each MSG1 resource they occupy, or a common MSG2 monitoring starting time for multiple MSG1 resources may be set. Here, the reference time, which serves as a criterion for determining the time when the device starts MSG2 monitoring, can be considered as various options as described above.

[0168] Lack of MSG2 monitoring start time and interval settings for the device

[0169] FIGS. 20 and 21 illustrate examples of problems arising from the absence of information regarding the device's MSG2 monitoring start time and monitoring interval settings, in the case where a reader that has received MSG1 from one or more devices transmits a common MSG2 in response. FIG. 20 illustrates the case where there is one time domain resource (X=1) for MSG1 transmission, and FIG. 21 illustrates the case where there are two time domain resources (X=2) for MSG1 transmission. Regarding MSG2 monitoring, after the device finishes transmitting D2R, T D2R_min Although it was agreed only that R2D messages are not monitored faster than the value, T D2R_minIt is not defined as to what unit this is derived or configured. Here, when up to two time domain resources (X=2) are supported for MSG1 transmission, the devices that transmitted MSG1 through the first time domain resource are T D2R_min If only the value is considered, additional power consumption may occur for the duration of the time corresponding to at least the second time domain resource.

[0170] FIGS. 22 and 23 illustrate an example of a problem arising from the absence of information regarding the start time and monitoring interval setting of MSG2 monitoring by a device, in the case where a reader that has received MSG1 from one or more devices transmits multiple separate MSG2s in response. Since the devices receive individual MSG2s from the reader after transmitting MSG1, if the time of MSG2 reception can be known, efficient MSG2 monitoring can be performed based on the time of MSG2 reception, and power consumption can be minimized at the same time.

[0171] The present disclosure provides a method for performing MSG2 monitoring based on MSG2 monitoring configuration information when an Ambient IoT device(s) performing a random access procedure transmits MSG1 and receives MSG2 in response.

[0172]

[0173] FIG. 24 is a diagram illustrating a procedure (2400) in which an Ambient IoT terminal performs random access according to one embodiment.

[0174] Referring to FIG. 24, the Ambient IoT terminal can receive second message (MSG2) monitoring setting information from a reader device (S2410).

[0175] For example, monitoring configuration information may be transmitted explicitly or implicitly by being included in a message that triggers random access (e.g., R2D message) or an ambient IoT paging (A-IoT paging) message transmitted from a reader device. Specifically, the monitoring configuration information includes various parameters for the terminal to efficiently receive a downlink message (MSG2) after transmitting an uplink message (MSG1).

[0176] The configuration information may include information (e.g., a 1-bit indicator) indicating whether the number of resources (X) supported in the time domain for transmitting an uplink message (MSG1) is 1 (X=1) or 2 (X=2). Additionally, the configuration information may include wireless resource information or access occasion information for transmitting MSG1.

[0177] Additionally, the monitoring setting information may include at least one of the parameters required for the terminal to determine the start time of MSG2 monitoring, such as a time offset value from when the terminal receives a message triggering random access until it starts transmitting MSG1, a time interval or offset between multiple MSG1 resources, and a minimum processing time required for the terminal to wait for reception after MSG1 transmission is completed.

[0178] In addition, the configuration information may additionally include a reference time option serving as a criterion for deriving the MSG2 monitoring start time, information for setting the monitoring duration or window for receiving downlink messages (e.g., K value), and chip duration information for uplink transmission (D2R chip duration). Through this, the terminal is able to perform MSG2 monitoring at an optimized time based on the reader's MSG2 transmission method (Common or Separate) and the time domain resources it occupies, following the MSG1 transmission described later.

[0179] Referring again to FIG. 24, the Ambient IoT terminal can transmit a first message (MSG1) by occupying a specific resource among one or more time domain resources allocated to the terminal (S2420).

[0180] A reader device may provide one or more time domain resources in the time domain to a terminal as resources for transmitting MSG1, which is an uplink message. In this case, the number of time domain resources (X) may be determined to be one (X=1) or two (X=2), and the reader may notify the terminal of this through a 1-bit indicator.

[0181] The terminal transmits MSG1 by selecting or occupying a specific time domain resource among the X allocated time domain resources. The specific transmission timing is as follows. For the first time domain resource, it starts when the first time offset has elapsed from the time the R2D message triggering random access is received. For the second time domain resource (when X=2), it starts when the second time offset has elapsed from the start time of the first time domain resource.

[0182] The terminal transmits MSG1 based on the D2R chip duration indicated by the reader device through the selected resource, and MSG1 may include a Random ID or AS ID for terminal identification and contention resolution. In one example, MSG1 may further include upper layer data. Such MSG1 transmission may be performed as part of a 3-step contention-based random access (CBRA) or contention-free random access (CFRA) procedure adopting a slotted-ALOHA scheme. Which of the multiple time-domain resources the terminal occupies to transmit MSG1 serves as a key parameter in determining the time when the reader device transmits MSG2 and the time when the terminal starts monitoring MSG2 in the steps to be described later.

[0183] Referring again to FIG. 24, the Ambient IoT terminal can determine the monitoring start time based on MSG2 monitoring setting information and the MSG2 transmission method of the reader device (S2430).

[0184] The monitoring start time can be determined by applying different time offsets based on whether the reader device transmits a common MSG2 to multiple MSG1s or transmits a separate MSG2 to each MSG1, and based on specific resources occupied.

[0185] The specific method for determining the monitoring start time can be classified as follows, depending on the reader's transmission method and the number of time domain resources (X). In the case of the Common Downlink Message Transmission Method (Common MSG2), that is, when the reader device transmits a single Common MSG2 for MSG1s transmitted by one or more terminals, the terminals are configured to have a common monitoring start time for efficient reception.

[0186] When X=1, the terminal calculates the monitoring start time by considering the minimum processing time after the completion of MSG1 transmission and the time required for MSG1 transmission. When X=2, the difference in transmission time occurring between terminals occupying different time domain resources (the first or second resource) must be corrected. In particular, to prevent the terminal occupying the first resource from wasting power by starting monitoring unnecessarily early, a correction offset reflecting the time interval between resources is applied to derive a common start time based on the end time of the second resource.

[0187] In the case of the Separate MSG2 downlink message transmission method, that is, when the reader device transmits individual MSG2s in response to each terminal's MSG1, the terminal can determine the start time for individual monitoring based on the order of the resources it occupies. The terminal calculates the time based on the access occasion index used for transmitting the MSG1 and time offset information that takes into account the size of a single MSG2 payload.

[0188] Specifically, the terminal that sent MSG1 through the n-th resource derives the monitoring time optimized for the MSG2 reception sequence assigned to it by adding the product of the corresponding index and offset to the minimum waiting time. To determine this time, the terminal may utilize the end time of the resource through which the terminal sent MSG1, the end time of the last resource among the total X resources, or the end time of the message that triggered random access as a reference time.

[0189] Through this, Ambient IoT terminals can maximize power efficiency by activating the receive mode only at timings that precisely match the reader's transmission scheduling.

[0190] Referring again to FIG. 24, the Ambient IoT terminal can monitor MSG2 from a determined monitoring start time (S2440).

[0191] The terminal performs monitoring of downlink messages (MSG2) during a specific monitoring period (monitoring duration or monitoring window) calculated from a determined monitoring start time. At this time, the length of the monitoring period may be determined by applying a predefined value or based on instruction information included in an R2D message that triggers random access. The specific method for setting the monitoring period may be applied differently as follows depending on the transmission method of the reader device.

[0192] According to one example, in a method where a reader device transmits a common downlink message for multiple uplink messages (MSG1), all terminals simultaneously start monitoring at the common monitoring start time. At this time, the terminals can set a maximum monitoring interval by considering the payload size of the expected total downlink message. Specifically, the terminal can calculate the monitoring interval based on the total number of uplink message (MSG1) resources confirmed through a paging message received from the reader device in advance and the payload size of a single downlink message. For example, if the terminal confirms that it has been allocated 8 MSG1 resources from the paging message, it determines that a common response corresponding to up to 8 MSG2s may be received from the reader device and can set a monitoring interval proportional to this.

[0193] In another example, if the reader device transmits separate downlink messages for each uplink message (MSG1), the monitoring interval may be set per terminal based on the payload size of a single downlink message or a specific offset value. Similar to the common transmission method described above, a maximum monitoring interval proportional to the total number of MSG1 resources may be set, and monitoring may continue within that interval until the reception of the downlink message corresponding to itself is completed.

[0194] The terminal can determine the conditions for terminating monitoring to minimize battery consumption. The terminal can perform downlink message monitoring until it receives K access trigger messages according to a pre-set parameter (K, e.g., K=1 or 4) via paging messages. In addition, the terminal continues monitoring until it receives any one of the following: the next A-IoT Paging message directly directing the terminal, a Downlink Upper Layer Data Transfer (R2D) message, or a NACK feedback message containing the terminal's identifier (AS ID), and can terminate the monitoring operation upon receiving any of these messages.

[0195] According to this, a method and device for performing a random access procedure in an Ambient IoT environment can be provided. Additionally, based on the MSG2 transmission method transmitted by the reader device and the number of supported time domain resources, Ambient IoT terminals can perform efficient MSG2 monitoring according to the MSG1 time resources they occupy.

[0196] FIG. 25 is a diagram illustrating a procedure (2500) in which a reader device according to one embodiment performs random access. The description in FIG. 24 above may be omitted to avoid redundant descriptions, and in this case, the omitted content may be applied substantially the same to the reader device as long as it does not contradict the technical concept of the invention.

[0197] Referring to FIG. 25, the reader device can transmit second message (MSG2) monitoring setting information to the Ambient IoT terminal (S2510).

[0198] The reader device may transmit monitoring configuration information via a message that triggers random access of the terminal (e.g., an R2D message) or an A-IoT paging message. In this case, the configuration information may be explicitly included within the message or implicitly indicated through a specific signaling field. Specifically, the monitoring configuration information transmitted by the reader device includes various parameters as follows to enable the terminal to efficiently receive the downlink message MSG2 in accordance with the transmission method after the transmission of the first message (MSG1).

[0199] Uplink resource configuration information may include information indicating whether the number of resources (X) supported in the time domain for MSG1 transmission is 1 (X=1) or 2 (X=2) (e.g., a 1-bit indicator), and wireless resource information or access occasion information for MSG1 transmission. Timing control parameters may include at least one of a time offset value from the end of transmission by the reader device to the start of MSG1 transmission by the terminal, a time interval between multiple MSG1 resources, and a minimum processing time required for the terminal's transmit / receive switching, so that the terminal can determine the start time for MSG2 monitoring. Monitoring window setting information may include a reference time option for deriving the start time for MSG2 monitoring and a parameter (e.g., a value of K) for determining the length of the monitoring duration or window. Physical layer parameters may include D2R chip duration information for defining the uplink transmission speed and specifications of the terminal.

[0200] By providing the aforementioned configuration information to the terminal, the reader device establishes an environment in which the terminal can activate the radio function and perform monitoring at an optimized time based on the actual MSG2 transmission method (Common or Separate) of the reader device and the location of the time domain resource occupied by the terminal after the MSG1 transmission described below.

[0201] Referring again to FIG. 25, the reader device can receive a first message (MSG1) from the terminal through a specific resource among one or more time domain resources allocated to the terminal (S2520).

[0202] The reader device receives MSG1, an uplink message transmitted by the terminal, through one or more time domain resources (time domain resource(s)) previously allocated and instructed to the terminal. At this time, the total number of time domain resources (X) supported for uplink transmission may be one (X=1) or two (X=2), and the reader device monitors or waits for the terminal's signal in the corresponding resource interval according to the value of X set by itself.

[0203] The specific timing and method by which the reader device receives MSG1 are as follows. The reader device can receive MSG1 through the first time domain resource that starts at a time when a first time offset has elapsed from the time it has completed transmitting the random access trigger message. If the number of time domain resources is set to 2 (X=2), the reader device can also wait for MSG1 to be received from the second time domain resource that starts at a time when a second time offset has elapsed from the start time of the first time domain resource.

[0204] The reader device obtains Random ID or AS ID information from the received MSG1 for terminal identification and contention resolution. Additionally, depending on one example, it may also receive upper layer data included in the MSG1. In particular, the reader device according to the present disclosure can identify which specific resource among a plurality of allocated time domain resources the terminal occupied to transmit the MSG1. The location information of the occupied resource identified by the reader device (e.g., resource index) is utilized as a key parameter in the steps to be described later to determine the time when the reader device transmits the MSG2 and to correspond it to the start time of the terminal's MSG2 monitoring.

[0205] Through this, the reader device can precisely control the transmission timing so that the terminal can receive MSG2 at an optimized time.

[0206] Referring again to FIG. 25, the reader device determines the transmission start time based on MSG2 monitoring setting information and the MSG2 transmission method of the reader device, and can transmit MSG2 to the terminal at the determined transmission start time (S2530).

[0207] The transmission start time may be determined by applying different time offsets based on whether the reader device transmits a common MSG2 to multiple MSG1s or transmits a separate MSG2 to each MSG1, and based on specific resources occupied by the terminal.

[0208] The reader device determines a transmission timing that precisely corresponds to the start time of monitoring of the terminal so that the terminal can efficiently receive a downlink message (MSG2). The transmission start time may be determined by applying different time offsets based on whether the reader device transmits a single common downlink message for multiple uplink messages (MSG1) (Common MSG2) or transmits individual downlink messages for each MSG1 (Separate MSG2), and based on a specific time domain resource occupied by the terminal.

[0209] Specifically, the method by which the reader device determines the transmission time includes the following examples. In the case of a Common Downlink Message Transmission Method (Common MSG2), the reader device transmits a common MSG2 in response to MSG1s received from one or more terminals and adjusts the transmission time so that all terminals can start monitoring at the same time. In the case where the number of resources (X) for Uplink Message Transmission is 1 (X=1), the reader device may determine the transmission time by considering the minimum processing time of the terminal and the time required to transmit MSG1.

[0210] When the number of resources (X) is 2 (X=2), the reader device applies a corrected offset so that terminals occupying different time domain resources can receive MSG2 in common. In particular, the reader device can correct the transmission time by reflecting the end time of the second resource and the interval between resources so that a terminal that sent MSG1 through the first resource does not consume unnecessary standby power during the second resource interval.

[0211] In the case of the Separate MSG2 downlink message transmission method, the reader device sequentially transmits individual MSG2s corresponding to the MSG1 transmitted by each terminal. The reader device calculates different transmission times for each terminal based on the access occasion index (n) used by the terminal to transmit the MSG1. By transmitting the individual MSG2 for each terminal at the time calculated by summing the product of the corresponding index (n) and an offset considering the size of one MSG2 payload to the minimum waiting time, the reader device supports the terminal in performing monitoring at the optimal timing corresponding to its receiving order.

[0212] In addition, the reader device equally considers the reference time options used as a standard by the terminal side when determining the transmission time. The reference time can be set to one of the terminal's MSG1 transmission end time, the end time of the last resource among all resources, or the end time of the message that triggered random access. Through this transmission time control method, the reader device provides an environment in which the Ambient IoT terminal can power-efficiently monitor downlink messages, and consequently, can maximize the energy efficiency of the entire system.

[0213] According to this, a method and device for performing a random access procedure in an Ambient IoT environment can be provided. Additionally, based on the MSG2 transmission method transmitted by the reader device and the number of supported time domain resources, Ambient IoT terminals can perform efficient MSG2 monitoring according to the MSG1 time resources they occupy.

[0214]

[0215] Hereinafter, each embodiment related to a method for performing a random access procedure in an Ambient IoT environment will be described in detail with reference to the relevant drawings.

[0216] The present disclosure provides a method for performing MSG2 monitoring based on MSG2 monitoring configuration information when an Ambient IoT device(s) performing a random access procedure transmits MSG1 and receives MSG2 in response.

[0217] The Reader may provide one or more time domain resource(s) to the device as resources for transmitting MSG1. The Device may select the first or second time domain resource(s) among the time domain resource(s) to transmit MSG1. Here, the Reader may transmit a common MSG2 in response to MSG1 transmitted by one or more different devices, or transmit separate MSG2(s) in response to MSG1 transmitted by one or more different devices.

[0218] The device considers the reader's MSG2 transmission method and starts MSG2 monitoring based on the reference time for MSG2 monitoring after the completion of MSG1 transmission. The start time for MSG2 monitoring is T according to the reference time options. D2R_min , T D2R payload size, T offset1 , T offset2 , T R2D It can be determined by considering the payload size, α, etc.

[0219] In consideration of the aforementioned matters, the present disclosure provides a configuration method for MSG2 monitoring as follows, depending on the reader's MSG2 transmission method and the number of time domain resources (X=1 or X=2) for MSG1 transmission. Additionally, the present disclosure proposes considering the reference time used to determine the MSG2 monitoring start time, the MSG2 monitoring start time, and the MSG2 monitoring interval stage.

[0220] - Example 1. One common MSG2 transmission corresponding to one or more MSG1s (X=1)

[0221] - Example 2. One common MSG2 transmission corresponding to one or more MSG1s (X=2)

[0222] - Example 3. One or more separate MSG2 transmissions corresponding to one or more MSG1s (X=1)

[0223] - Example 4. One or more separate MSG2 transmissions corresponding to one or more MSG1s (X=2)

[0224] Example 1. One common MSG2 transmission corresponding to one or more MSG1s (X=1)

[0225] FIG. 26 is a diagram illustrating one common MSG2 transmission (X=1) corresponding to one or more MSG1s according to one embodiment.

[0226] After the devices complete the MSG1 transmission, at least T D2R_min We can expect to receive MSG2 after the value. However, here T D2R_min The value is the minimum processing time required for the device to switch from MSG1 transmit mode to MSG2 receive mode, and this value can be pre-defined or set by the reader. However, T D2R_min In setting this, the reference unit serving as the standard is not defined, and one of the following can be set as the reference unit: R2D chip duration, R2D bit duration, R2D symbol duration, D2R chip duration, or D2R bit duration. Therefore, the device can determine the MSG2 monitoring start time according to the reference time option as follows. Below, T D2R The payload size is the time required to transmit MSG1 considering the MSG1 size, and T offset2 It could be like that.

[0227] Starting time for MSG2 monitoring

[0228] ① T offset1 + T D2R payload size+T D2R_min

[0229] ② T D2R payload size+T D2R_min

[0230] ③ T D2R_min

[0231] An A-IoT paging message can include the number of MSG1 resources.

[0232] Monitoring duration

[0233] Since all devices share a common MSG2 monitoring start time, they begin MSG2 monitoring simultaneously. At this time, devices can set a maximum monitoring interval by considering the expected payload size of the entire R2D message. The reader can provide the number of MSG1 resources via a paging message. Therefore, devices can determine that MSG2 can be transmitted from the reader up to the number of received MSG1 resources. For example, if a device receives 8 MSG1 resources, it can determine that a maximum of 8 MSG2s can be received from the reader. Therefore, based on a single MSG2 payload size and the number of MSG1 resources, the MSG2 monitoring interval (T R2D_total You can set the payload size.

[0234] Example 2. One common MSG2 transmission corresponding to one or more MSG1s (X=2)

[0235] FIG. 27 is a diagram illustrating one common MSG2 transmission (X=2) corresponding to one or more MSG1s according to one embodiment.

[0236] When a time domain resource is supported with X=2, a time offset occurs between the device occupying the first time domain resource and the device occupying the second time domain resource. Since this becomes a variable in deriving the common MSG2 monitoring start point, it needs to be corrected. Here, T D2R_minThe value is the minimum time required for the device to switch from MSG1 transmission mode to MSG2 reception mode. If this value is applied to devices that transmitted MSG1 via the first time domain resource, it may cause unnecessary power consumption because MSG2 monitoring can be performed before devices that transmitted MSG1 via the second time domain resource.

[0237] Therefore, the present disclosure proposes a method for devices to perform MSG2 monitoring in common by considering the MSG1 payload size and the following reference time options for determining the MSG2 monitoring start time. The MSG2 monitoring start time for each of the reference times below is based on the following MSG1 payload size and T D2R_min It can be corrected and set based on values, etc.

[0238] Starting time for MSG2 monitoring

[0239] ① T offset1 +(T D2R payload size·2)+α+T D2R_min

[0240] ② (T D2R payload size·2)+α+T D2R_min

[0241] ③ T D2R payload size+α+T D2R_min

[0242] ④ T D2R payload size+T D2R_min

[0243] ⑤ T D2R_min

[0244] Monitoring duration

[0245] In this embodiment, the MSG2 monitoring interval is the same as in the aforementioned Example 1.

[0246] Examples 3 and 4. One or more separate MSG2 transmissions corresponding to one or more MSG1s (X=1 or X=2)

[0247] FIG. 28 is a diagram illustrating one or more separate MSG2 transmissions (X=1) corresponding to one or more MSG1s according to one embodiment. FIG. 29 is a diagram illustrating one or more separate MSG2 transmissions (X=2) corresponding to one or more MSG1s according to one embodiment.

[0248] Here, Examples 3 and 4 are described together. After the MSG1 transmission is complete, the devices, at least T D2R_min Reception of MSG2 can be expected after the value. Considering the MSG2 transmission method of the corresponding embodiment, each device can expect to receive MSG2 from the reader after completing its own MSG1 transmission. At this time, if the reader provides access occasion index information regarding resource information classified by time / frequency for MSG1 transmission, the start time for MSG2 monitoring can be determined in the following manner. Additionally, the reader can transmit MSG2 in accordance with the access occasion index. The method for MSG2 monitoring correction based on the reference time can be derived in the same way as the aforementioned Examples 1 and 2.

[0249] Starting time for MSG2 monitoring

[0250] T D2R_n =T D2R_min +(n · T offset )

[0251] According to the aforementioned formula, TD2R_n represents the time required for a device that transmitted MSG1 via the nth access occasion to start monitoring MSG2. offset T is the size of a single MSG2 payload. R2D This is a time value that takes into account the payload size, and this can be set as a reference unit for the R2D chip, bit, symbol duration or the D2R chip, bit duration. Here, when determining the MSG2 monitoring start time in Example 4, the value that takes into account the D2R payload size according to the first or second time domain resource must be corrected.

[0252] Monitoring duration

[0253] The MSG2 monitoring section is T offset It can be set considering the value or MSG2 payload size. Alternatively, the device may continue monitoring until MSG2 reception is completed based on the maximum monitoring interval considering the number of MSG1 resources and one MSG2 payload size, as in Example 1 and Example 2.

[0254] The present disclosure relates to the setting of a monitoring start time and a monitoring interval for receiving MSG2 after Ambient IoT devices transmit MSG1. Depending on the MSG2 transmission method transmitted by the Reader and the number of supported time domain resources, devices can perform efficient MSG2 monitoring based on the MSG1 time resources they occupy.

[0255] With respect to the aforementioned embodiments, each embodiment is included within the scope of the invention according to the present disclosure not only in independent cases but also in all cases comprising combinations of embodiments.

[0256]

[0257] Hereinafter, the configuration of an Ambient IoT terminal and a reader device capable of performing some or all of the embodiments described with reference to FIGS. 1 to 29 will be described with reference to the drawings. The foregoing description may be omitted to avoid redundant descriptions, and in such cases, the omitted content may be applied substantially identically to the following description, provided that it does not contradict the technical concept of the invention.

[0258] FIG. 30 is a diagram showing the configuration of an Ambient IoT terminal (3000) according to another embodiment.

[0259] Referring to FIG. 30, an Ambient IoT terminal (3000) according to another embodiment includes a transmitter (3020), a receiver (3030), and a control unit (3010) that controls the operation of the transmitter and the receiver.

[0260] The control unit (3010) controls the overall operation of the terminal (3000) according to a method for performing a random access procedure necessary to perform the embodiments of the present disclosure described above.

[0261] The control unit (3010) allows the Ambient IoT terminal to receive monitoring setting information for a second message (MSG2) from a reader device. According to one example, the monitoring setting information may be included in a message that triggers random access (e.g., an R2D message) or an Ambient IoT paging (A-IoT paging) message transmitted from the reader device and transmitted explicitly or implicitly. Specifically, the monitoring setting information includes various parameters for the terminal to efficiently receive a downlink message (MSG2) after transmitting an uplink message (MSG1).

[0262] The configuration information may include information (e.g., a 1-bit indicator) indicating whether the number of resources (X) supported in the time domain for transmitting an uplink message (MSG1) is 1 (X=1) or 2 (X=2). Additionally, the configuration information may include wireless resource information or access occasion information for transmitting MSG1.

[0263] Additionally, the monitoring setting information may include at least one of the parameters required for the terminal to determine the start time of MSG2 monitoring, such as a time offset value from when the terminal receives a message triggering random access until it starts transmitting MSG1, a time interval or offset between multiple MSG1 resources, and a minimum processing time required for the terminal to wait for reception after MSG1 transmission is completed.

[0264] Additionally, the configuration information may further include a reference time option that serves as a criterion for deriving the MSG2 monitoring start time, information for setting the monitoring duration or window for receiving downlink messages (e.g., K value), and information for the chip duration (D2R chip duration) for uplink transmission. Through this, the control unit (3010) is able to perform MSG2 monitoring at an optimized time based on the reader's MSG2 transmission method (Common or Separate) and the time domain resources it occupies after the MSG1 transmission described later.

[0265] The control unit (3010) can transmit a first message (MSG1) by occupying a specific resource among one or more time domain resources allocated to the terminal. The reader device can provide one or more time domain resources (time domain resource(s)) in the time domain to the terminal as resources for transmitting MSG1, which is an uplink message. At this time, the number of time domain resources (X) can be determined to be one (X=1) or two (X=2), and the reader can notify the terminal of this through a 1-bit indicator.

[0266] The control unit (3010) selects or occupies a specific time domain resource among the allocated X time domain resources and transmits MSG1. The specific transmission timing is as follows. For the first time domain resource, it starts at the time when the first time offset has elapsed from the time when the R2D message triggering random access is received is completed. For the second time domain resource (when X=2), it starts at the time when the second time offset has elapsed from the start time of the first time domain resource.

[0267] The control unit (3010) transmits MSG1 based on the D2R chip duration indicated by the reader device through the selected resource, and MSG1 may include a Random ID or AS ID for terminal identification and contention resolution. According to one example, MSG1 may further include upper layer data. Such MSG1 transmission may be performed as part of a 3-step contention-based random access (CBRA) or contention-free random access (CFRA) procedure adopting a slotted-ALOHA method. Which of the multiple time domain resources the terminal occupies to transmit MSG1 serves as a key parameter for determining the time when the reader device transmits MSG2 and the time when the terminal starts monitoring MSG2 in the steps to be described later.

[0268] The control unit (3010) can determine the monitoring start time based on MSG2 monitoring setting information and the MSG2 transmission method of the reader device. The monitoring start time can be determined by applying different time offsets based on whether the reader device transmits a common MSG2 to multiple MSG1s or transmits a separate MSG2 to each MSG1, and based on specific resources occupied.

[0269] The specific method for determining the monitoring start time can be classified as follows, depending on the reader's transmission method and the number of time domain resources (X). In the case of the Common Downlink Message Transmission Method (Common MSG2), that is, when the reader device transmits a single Common MSG2 for MSG1s transmitted by one or more terminals, the terminals are configured to have a common monitoring start time for efficient reception.

[0270] When X=1, the control unit (3010) calculates the monitoring start time by considering the minimum processing time after MSG1 transmission is completed and the time required for MSG1 transmission. When X=2, the difference in transmission time occurring between terminals occupying different time domain resources (first or second resources) must be corrected. In particular, to prevent the terminal occupying the first resource from unnecessarily starting monitoring early and wasting power, a correction offset reflecting the time interval between resources is applied to derive a common start time based on the end time of the second resource.

[0271] In the case of a separate downlink message transmission method (Separate MSG2), that is, when a reader device transmits a separate MSG2 corresponding to the MSG1 of each terminal, the control unit (3010) can determine the start time for individual monitoring in accordance with the order of resources it occupies. The control unit (3010) calculates the time based on the access occasion index used for MSG1 transmission and time offset information considering the size of one MSG2 payload.

[0272] Specifically, the control unit (3010) that sent MSG1 through the nth resource derives a monitoring time optimized for the MSG2 reception sequence assigned to it by adding the product of the corresponding index and offset to the minimum waiting time. To determine this time, the control unit (3010) may use the end time of the resource to which the terminal sent MSG1, the end time of the last resource among the total X resources, or the end time of the message that triggered random access as a reference time.

[0273] Through this, Ambient IoT terminals can maximize power efficiency by activating the receive mode only at timings that precisely match the reader's transmission scheduling.

[0274] The control unit (3010) can monitor MSG2 from a determined monitoring start time. The control unit (3010) performs monitoring of the downlink message (MSG2) during a specific monitoring period (monitoring duration or monitoring window) calculated from the determined monitoring start time. At this time, the length of the monitoring period may be determined based on a predefined value or based on instruction information included in an R2D message that triggers random access. The specific method of setting the monitoring period may be applied differently as follows depending on the transmission method of the reader device.

[0275] According to one example, in a method where a reader device transmits a common downlink message for multiple uplink messages (MSG1), all terminals simultaneously start monitoring at the common monitoring start time. At this time, the terminals can set a maximum monitoring interval by considering the payload size of the expected total downlink message. Specifically, the control unit (3010) can calculate the monitoring interval based on the total number of uplink message (MSG1) resources confirmed through a paging message received from the reader device in advance and the payload size of one downlink message. For example, if a terminal confirms that it has been allocated 8 MSG1 resources from the paging message, it can determine that a common response corresponding to up to 8 MSG2s can be received from the reader device and set a monitoring interval proportional to this.

[0276] In another example, if the reader device transmits separate downlink messages for each uplink message (MSG1), the monitoring interval may be set per terminal based on the payload size of a single downlink message or a specific offset value. Similar to the common transmission method described above, a maximum monitoring interval proportional to the total number of MSG1 resources may be set, and monitoring may continue within that interval until the reception of the downlink message corresponding to itself is completed.

[0277] The control unit (3010) can determine the termination condition of monitoring to minimize battery consumption. The control unit (3010) can perform downlink message monitoring until it receives K access trigger messages according to a pre-set parameter (K, e.g., K=1 or 4) through a paging message. In addition, the control unit (3010) continues monitoring until it receives any one of the following: the next A-IoT Paging message directly indicating the terminal, the R2D Upper Layer Data Transfer message, or the NACK feedback message containing the terminal's identifier (AS ID), and can terminate the monitoring operation when it receives any one of these messages.

[0278] According to this, a method and device for performing a random access procedure in an Ambient IoT environment can be provided. Additionally, based on the MSG2 transmission method transmitted by the reader device and the number of supported time domain resources, Ambient IoT terminals can perform efficient MSG2 monitoring according to the MSG1 time resources they occupy.

[0279]

[0280] FIG. 31 is a drawing showing the configuration of a reader device (3100) according to another embodiment.

[0281] Referring to FIG. 31, a reader device (3100) according to another embodiment includes a transmitter (3120), a receiver (3130), and a control unit (3110) that controls the operation of the transmitter and the receiver.

[0282] The control unit (3110) controls the operation of the overall reader device (3100) according to a method for performing a random access procedure necessary to perform the embodiments of the present disclosure described above. The transmitting unit (3120) transmits R2D messages, etc. to an Ambient IoT terminal through a predetermined channel. The receiving unit (3130) receives D2R messages, etc. from the Ambient IoT terminal through a predetermined channel.

[0283] The control unit (3110) may transmit monitoring configuration information via a message (e.g., R2D message) that triggers random access of the terminal or via an A-IoT paging message. At this time, the configuration information may be explicitly included within the message or implicitly indicated through a specific signaling field. Specifically, the monitoring configuration information transmitted by the control unit (3110) includes various parameters such as the following so that the terminal can efficiently receive the downlink message MSG2 according to the transmission method after the transmission of the first message (MSG1).

[0284] Uplink resource configuration information may include information (e.g., a 1-bit indicator) indicating whether the number of resources (X) supported in the time domain for MSG1 transmission is 1 (X=1) or 2 (X=2), and wireless resource information or access occasion information for MSG1 transmission. Timing control parameters may include at least one of a time offset value from the end of transmission by the control unit (3110) to the start of MSG1 transmission by the terminal, a time interval between multiple MSG1 resources, and a minimum processing time required for the terminal's transmission and reception switching, so that the terminal can determine the start time for MSG2 monitoring. Monitoring window setting information may include a reference time option for deriving the start time for MSG2 monitoring and a parameter (e.g., a K value) for determining the length of the monitoring duration or window. Physical layer parameters may include D2R chip duration information for defining the uplink transmission speed and specifications of the terminal.

[0285] The control unit (3110) provides the aforementioned setting information to the terminal, thereby establishing an environment in which the terminal can activate the radio function and perform monitoring at an optimized time based on the actual MSG2 transmission method (Common or Separate) of the control unit (3110) and the location of the time domain resource occupied by the terminal after the MSG1 transmission described later.

[0286] The control unit (3110) can receive a first message (MSG1) from the terminal through a specific resource among one or more time domain resources allocated to the terminal. The control unit (3110) receives MSG1, which is an uplink message transmitted by the terminal, through one or more time domain resources (time domain resource(s)) previously allocated and instructed to the terminal. At this time, the total number of time domain resources (X) supported for uplink transmission may be one (X=1) or two (X=2), and the control unit (3110) monitors or waits for reception of the terminal's signal in the corresponding resource section according to the value of X set by itself.

[0287] The specific timing and method by which the control unit (3110) receives MSG1 are as follows. The control unit (3110) can receive MSG1 through the first time domain resource that starts at a time when a first time offset has elapsed from the time when it has completed transmitting the random access trigger message. If the number of time domain resources is set to 2 (X=2), the control unit (3110) can also wait for MSG1 to be received from the second time domain resource that starts at a time when a second time offset has elapsed from the start time of the first time domain resource.

[0288] The control unit (3110) obtains Random ID or AS ID information for terminal identification and contention resolution from the received MSG1. Additionally, according to one example, upper layer data included in the MSG1 may also be received. In particular, the control unit (3110) according to the present disclosure can identify which specific resource among a plurality of allocated time domain resources the terminal occupied to transmit the MSG1. The location information of the occupied resource (e.g., resource index) identified by the control unit (3110) is used as a key parameter to determine the time when the control unit (3110) transmits the MSG2 and to correspond to the start time of the terminal's MSG2 monitoring in the steps to be described later.

[0289] Through this, the control unit (3110) can precisely control the transmission timing so that the terminal can receive MSG2 at an optimized time.

[0290] The control unit (3110) determines the transmission start time based on MSG2 monitoring setting information and the MSG2 transmission method of the reader device, and can transmit the MSG2 to the terminal at the determined transmission start time. The transmission start time may be determined by applying different time offsets based on whether the control unit (3110) transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and based on a specific resource occupied by the terminal.

[0291] The control unit (3110) determines a transmission timing that accurately corresponds to the start time of monitoring of the terminal so that the terminal can efficiently receive a downlink message (MSG2). The start time of transmission may be determined by applying different time offsets based on whether the control unit (3110) transmits a common downlink message for multiple uplink messages (MSG1) (Common MSG2) or transmits individual downlink messages for each MSG1 (Separate MSG2), and based on a specific time domain resource occupied by the terminal.

[0292] Specifically, the method by which the control unit (3110) determines the transmission time includes the following examples. In the case of a common downlink message transmission method (Common MSG2), the control unit (3110) transmits a common MSG2 in response to MSG1s received from one or more terminals, and adjusts the transmission time so that all terminals can start monitoring at the same time. In the case where the number of resources (X) for uplink message transmission is 1 (X=1), the control unit (3110) can determine the transmission time by considering the minimum processing time of the terminal and the time required for MSG1 transmission.

[0293] When the number of resources (X) is 2 (X=2), the control unit (3110) applies a corrected offset so that terminals occupying different time domain resources can receive MSG2 in common. In particular, the control unit (3110) can correct the transmission time by reflecting the end time of the second resource and the interval between resources so that a terminal that sent MSG1 through the first resource does not consume unnecessary standby power during the second resource interval.

[0294] In the case of the individual downlink message transmission method (Separate MSG2), the control unit (3110) sequentially transmits individual MSG2s corresponding to the MSG1 transmitted by each terminal. The control unit (3110) calculates different transmission times for each terminal based on the access occasion index (n) used by the terminal to transmit the MSG1. By transmitting individual MSG2s for each terminal at the time calculated by summing the product of the index (n) and an offset considering the size of one MSG2 payload to the minimum waiting time, the control unit (3110) supports the terminal in performing monitoring at the optimal timing corresponding to its reception order.

[0295] Additionally, the control unit (3110) equally considers the reference time options used as a standard by the terminal side when determining the transmission time. The reference time can be set to one of the terminal's MSG1 transmission end time, the end time of the last resource among all resources, or the end time of the message that triggered random access. Through this transmission time control method, the control unit (3110) provides an environment in which the Ambient IoT terminal can power-efficiently monitor downlink messages, and consequently, the energy efficiency of the entire system can be maximized.

[0296] According to this, a method and device for performing a random access procedure in an Ambient IoT environment can be provided. Additionally, based on the MSG2 transmission method transmitted by the reader device and the number of supported time domain resources, Ambient IoT terminals can perform efficient MSG2 monitoring according to the MSG1 time resources they occupy.

[0297] The aforementioned embodiments may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802, 3GPP, and 3GPP2. That is, steps, configurations, and parts in the embodiments that are not described to clearly reveal the technical concept may be supported by the aforementioned standard documents. Furthermore, all terms disclosed in this specification may be explained by the standard documents disclosed above.

[0298] The embodiments described above may be implemented through various means. For example, the embodiments may be implemented by hardware, firmware, software, or a combination thereof.

[0299] In the case of implementation by hardware, the method according to the embodiments may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

[0300] In the case of implementation by firmware or software, the method according to the embodiments may be implemented in the form of a device, procedure, or function that performs the functions or operations described above. Software code may be stored in a memory unit and executed by a processor. The memory unit may be located inside or outside the processor and may exchange data with the processor by various means already known.

[0301] Additionally, terms such as "system," "processor," "controller," "component," "module," "interface," "model," or "unit" described above may generally refer to computer-related entities, hardware, combinations of hardware and software, software, or running software. For example, the aforementioned components may be, but are not limited to, processes driven by a processor, processors, controllers, control processors, objects, execution threads, programs, and / or computers. For example, both the application running on the controller or processor and the controller or processor may be components. One or more components may reside within a process and / or execution thread, and the components may be located on a single device (e.g., a system, a computing device, etc.) or distributed across two or more devices.

[0302] The foregoing description is merely an illustrative explanation of the technical concept of the present disclosure, and those skilled in the art to which the present disclosure pertains may make various modifications and variations within the scope of the essential characteristics of the technical concept. Furthermore, since these embodiments are intended to explain, not limit, the scope of the technical concept is not limited by these embodiments. The scope of protection of the present disclosure shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of the present disclosure.

[0303]

[0304] CROSS-REFERENCE TO RELATED APPLICATION

[0305] This patent application claims priority pursuant to Section 119(a) of the U.S. Patent Act (35 USC § 119(a)) to Korean Patent Application No. 10-2025-0060753 filed on May 9, 2025, all of which are incorporated by reference into this patent application. Furthermore, this patent application claims priority in countries other than the United States for the same reasons as above, all of which are incorporated by reference into this patent application.

Claims

1. A method for an ambient IoT terminal to perform a random access procedure, A step of receiving second message (MSG2) monitoring setting information from a reader device; A step of transmitting a first message (MSG1) by occupying a specific resource among one or more time domain resources allocated to the terminal; A step of determining a monitoring start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device; and It includes the step of monitoring the MSG2 from the above-determined monitoring start time, and The above monitoring start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to multiple MSG1s or transmits a separate MSG2 to each MSG1, and based on the occupied specific resource.

2. In Paragraph 1, A method in which the reader device transmits the common MSG2 and the number of allocated time domain resources is two, wherein the monitoring start time is determined by correcting the time offset so that the terminal occupying the first resource and the terminal occupying the second resource among the two allocated time domain resources start monitoring at the same time.

3. In Paragraph 1, In the case where the reader device transmits the individual MSG2, the monitoring start time is determined differently for each terminal based on the index of a specific resource occupied by the terminal and the size of a single MSG2 payload.

4. In Paragraph 1, A method in which the duration of the time interval during which the terminal monitors the MSG2 is determined based on at least one of the total number of MSG1 resources received from the reader device and the payload size of the MSG2.

5. In Paragraph 1, A method in which the above time offset is determined using at least one of the following parameters: the minimum processing time required for the terminal to transition from the transmitting state of MSG1 to the receiving state of MSG2, the payload size of MSG1, and the time interval between the time of completion of receiving the message that triggers the random access and the start time of the first time domain resource.

6. A method for a reader device to perform a random access procedure in an ambient IoT system, A step of transmitting second message (MSG2) monitoring setting information to an Ambient IoT terminal; A step of receiving a first message (MSG1) from the terminal through a specific resource among one or more time domain resources allocated to the terminal; and The method includes the step of determining a transmission start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device, and transmitting the MSG2 to the terminal at the determined transmission start time. The above transmission start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and a specific resource occupied by the terminal.

7. In Paragraph 6, A method in which the reader device transmits the common MSG2, and when the number of allocated time domain resources is two, the transmission start time is determined by correcting the time offset so that the terminal that transmitted MSG1 through the first resource and the terminal that transmitted MSG1 through the second resource among the two allocated time domain resources can start monitoring at the same time.

8. In Paragraph 6, A method in which the reader device transmits the individual MSG2, wherein the transmission start time is determined differently for each terminal based on the index of a specific resource occupied by the terminal for the MSG1 transmission and the size of a single MSG2 payload.

9. In Paragraph 6, A method in which the MSG2 transmission period of the reader device corresponding to the duration during which the terminal monitors the MSG2 is determined based on at least one of the total number of MSG1 resources allocated by the reader device and the payload size of the MSG2.

10. In Paragraph 6, A method in which the above time offset is determined using at least one of the following parameters: the minimum processing time required for the terminal to transition from the transmitting state of MSG1 to the receiving state of MSG2, the payload size of MSG1, and the time interval between the time of completion of message transmission that triggers the random access and the start time of the first time domain resource.

11. In an Ambient IoT terminal performing a random access procedure, Transmitter; Receiver; and It includes a control unit that controls the operation of the transmitting unit and the receiving unit, and The above control unit is, Receives second message (MSG2) monitoring setting information from a reader device, occupies a specific resource among one or more time domain resources allocated to the terminal to transmit a first message (MSG1), determines a monitoring start time based on the MSG2 monitoring setting information and the MSG2 transmission method of the reader device, and monitors the MSG2 from the determined monitoring start time, A terminal in which the above monitoring start time is determined by applying different time offsets based on whether the reader device transmits a common MSG2 to a plurality of MSG1s or transmits a separate MSG2 to each MSG1, and based on the occupied specific resource.

12. In Paragraph 11, A terminal in which the reader device transmits the common MSG2 and the number of allocated time domain resources is two, wherein the monitoring start time is determined by correcting the time offset so that the terminal occupying the first resource and the terminal occupying the second resource among the two allocated time domain resources start monitoring at the same time.

13. In Paragraph 11, In the case where the reader device transmits the individual MSG2, the monitoring start time is determined differently for each terminal based on the index of a specific resource occupied by the terminal and the size of a single MSG2 payload.

14. In Paragraph 11, The duration during which the terminal monitors the MSG2 is determined based on at least one of the total number of MSG1 resources received from the reader device and the payload size of the MSG2.

15. In Paragraph 11, The above time offset is determined using at least one of the following parameters: the minimum processing time required for the terminal to transition from the transmitting state of MSG1 to the receiving state of MSG2, the payload size of MSG1, and the time interval between the time of completion of receiving the message triggering the random access and the start time of the first time domain resource.