Method for random access procedure in ambient internet-of-things communication and device thereof

Abstract

A method according to an embodiment of the present specification comprises the steps of: transmitting an access random ID message to a reader; receiving a random ID response message from the reader; and transmitting a device-to-reader (D2R) message to the reader on the basis of the random ID response message. The random ID response message is received on the basis of any one monitor window among a plurality of monitor windows, and the D2R message is transmitted after the monitor window and before the next monitor window starts.

Description

Method and apparatus for a random access procedure in ambient Internet of Things communication

[0001] This specification relates to a method and apparatus for a random access procedure in ambient Internet of Things communication.

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

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

[0004] In a random access procedure for Ambient IoT, a device that transmits Msg1 (e.g., an Access Random ID message) to a Reader can receive Msg2 (e.g., a Random ID Response message) from the Reader. The said Msg1 may be transmitted to the Reader via Time Division Multiplexing (TDM) and / or Frequency Division Multiplexing (FDM). However, since the availability of bandpass filtering capability varies by device or device type, it may be difficult for the device to properly filter and receive multiple Reader-to-Device (R2D) signals transmitted via FDM from the Reader. Therefore, TDM is fundamentally considered for the transmission of Msg2.

[0005] Regarding the timing of Msg3 transmission (e.g., a D2R message), it is necessary to define whether the device transmits Msg3 after all monitoring and transmission of multiple Msg2s are complete, or whether it transmits Msg3 between the monitor window for the Msg2 associated with the device and the monitor window for the next Msg2.

[0006] According to the prior art, while transmission using Time Division Multiplexing (TDM) or Frequency Division Multiplexing (FDM) is possible for multiple Msg1s (e.g., Access Random ID messages), only the TDM method is fundamentally considered for multiple Msg2s (e.g., Random ID Response messages). Consequently, regarding the transmission of multiple Msg2 PRDCHs (Physical Reader-to-Device Channels), there is a lack of clear definition as to when each device should transmit Msg3 (e.g., D2R message) after receiving the Msg2 PRDCH for itself. The purpose of this specification is to propose a method for improving the efficiency of a Random Access Procedure by clearly defining the timing at which a device transmits Msg3 after receiving the Msg2 PRDCH.

[0007] When multiple Msg2 PRDCHs are transmitted sequentially in a TDM manner, there is a problem where the device waits for a long time before transmitting the Msg3 PDRCH after the transmission and monitoring of all Msg2 PRDCHs are completed. During this long waiting period, there is a concern that transmission performance may degrade due to the accumulation of frequency offsets caused by the Sampling Frequency Offset (SFO). Another objective of the present specification is to propose a method for reducing the delay between the time of receiving Msg2 and the time of transmitting Msg3 by enabling the device to transmit the Msg3 PDRCH after receiving the Msg2 PRDCH associated with the device and before the monitor window of the next Msg2 PRDCH starts.

[0008] In addition, an appropriate number of Msg2 PRDCH monitor windows are required to enable the efficient transmission of Msg3 among multiple Msg2 PRDCHs. Another objective of this specification is to propose a method that enables the random access procedure between a reader and a device to be performed reliably and efficiently by defining a method for setting / indicating additional monitor windows and / or a method for skipping specific monitor windows.

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

[0010] To solve the aforementioned technical problem, a method according to one embodiment of the present specification includes the steps of transmitting an access random ID message to a reader, receiving a random ID response message from the reader, and transmitting a device-to-reader (D2R) message to the reader based on the random ID response message.

[0011] The above random ID response message is received based on one of a plurality of monitor windows.

[0012] The above D2R message is transmitted after the above monitor window and before the next monitor window starts.

[0013] This allows for the improvement of the execution efficiency of random access procedures by clearly defining the timing at which the device transmits Msg3 PDRCH after receiving Msg2 PRDCH. Additionally, since the device can transmit Msg3 PDRCH after receiving the Msg2 PRDCH related to it and before the monitor window for the next Msg2 PRDCH starts, the delay between the time of Msg2 reception and the time of Msg3 transmission can be effectively reduced.

[0014] It may further include the step of receiving a Reader-to-Device (R2D) message from the reader that triggers a Random Access procedure.

[0015] The above R2D message may include information related to the monitor window.

[0016] The above R2D message may include an A-IoT paging message and / or an access trigger message.

[0017] The above R2D message may further include information related to additional monitor windows for the above random ID response message. In this case, the above random ID response message may be received based on the above monitor window and the above additional monitor windows.

[0018] The above random ID response message may include control information. In this case, the control information may include information related to skipping a specific monitor window among the additional monitor windows. The above random ID response message may be received based on i) the monitor window and ii) one or more monitor windows among the additional monitor windows other than the specific monitor window.

[0019] The information related to the above omission may include information related to the start time of the monitor window to be omitted and / or information related to the time interval of the monitor window to be omitted.

[0020] The above random ID response message may include control information. In this case, the control information may include information related to an additional monitor window for the random ID response message. The random ID response message may be received based on the monitor window and the additional monitor window.

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

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

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

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

[0025] The above random ID response message is transmitted based on one of a plurality of monitor windows.

[0026] The above D2R message is received after the above monitor window and before the next monitor window starts.

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

[0028] In relation to the transmission of multiple Msg2 PRDCH (Physical Reader-to-Device Channel) messages, if it is unclear when a device should transmit a Msg3 PDRCH (Physical Device-to-Reader Channel) after receiving a Msg2 PRDCH for itself, there is a problem in that the timing efficiency of the Random Access Procedure is reduced. According to the embodiments of this specification, by clearly defining the timing at which a device transmits a Msg3 PDRCH after receiving a Msg2 PRDCH, the efficiency of performing the Random Access Procedure can be improved.

[0029] When multiple Msg2 PRDCHs are transmitted sequentially using Time Division Multiplexing (TDM), if a device must wait until the transmission and monitoring of all Msg2 PRDCHs are complete before transmitting a Msg3 PDRCH, a problem arises in which a frequency offset caused by the Sampling Frequency Offset (SFO) accumulates due to the long waiting time. According to the embodiments of this specification, since the device can transmit a Msg3 PDRCH after receiving the Msg2 PRDCH associated with it and before the monitoring window for the next Msg2 PRDCH starts, the delay between the time of Msg2 reception and the time of Msg3 transmission is shortened, and the fluctuation of the frequency offset due to SFO accumulation is reduced, thereby ensuring transmission stability.

[0030] If an appropriate number of Msg2 PRDCH monitor windows are not set to efficiently transmit Msg3 PDRCH among multiple Msg2 PRDCHs, there is a problem in which message timing between the reader and the device becomes irregular and the stability of the random access procedure is degraded. According to the embodiments of this specification, by defining a method for setting and indicating additional monitor windows and a method for omitting specific monitor windows, the random access procedure between the reader and the device can be performed more stably and efficiently.

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

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

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

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

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

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

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

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

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

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

[0041] FIG. 9 is a block diagram showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0042] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0043] A slash ( / ) or a comma used in the present disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

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

[0045] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

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

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

[0048] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

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

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

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

[0052] Ambient IoT

[0053] Ambient IoT (A-IoT) can be a new type of device or segment that operates solely on energy harvested from the surrounding environment. For example, A-IoT can refer to a new type of Internet of Things device that operates by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy. Examples of A-IoT use cases are shown in Table 1 below.

[0054]

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

[0056]

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

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

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

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

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

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

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

[0064] FIG. 3 is an example of topology 3 related to Ambient IoT. FIG. 4 is another example of topology 3 related to Ambient IoT. Specifically, FIG. 3 and FIG. 4 illustrate a topology (e.g., topology 3) supported by an auxiliary node according to an embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

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

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

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

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

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

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

[0071] General range

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

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

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

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

[0076] -X is determined in WG.

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

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

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

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

[0081] - Deployment Scenario 1 using Topology 1

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

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

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

[0085] The location of the intermediate node is indoors

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

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

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

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

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

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

[0092] 1. Evaluation Assumptions

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

[0094] Clause 5.3: Applicable maximum distance target value

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

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

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

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

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

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

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

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

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

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

[0105] RAN1-led:

[0106] For Ambient IoT DL and UL:

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

[0108] Numerology, Bandwidth, and Multiple Access

[0109] Waveform and Modulation

[0110] Channel coding

[0111] Downlink Channel / Signal Aspect

[0112] Uplink Channel / Signal Side

[0113] Scheduling and Timing Relationships

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

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

[0116] RAN2 Lead:

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

[0118] for example:

[0119] Paging

[0120] Random access

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

[0122] Interaction with the upper class

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

[0124] RAN3 Leading:

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

[0126] Paging

[0127] Device Context Management

[0128] Data transmission

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

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

[0131] RAN4 Leading:

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

[0133] Research on RF Requirements for Ambient IoT:

[0134] Ambient IoT BS Transmitter / Receiver

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

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

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

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

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

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

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

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

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

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

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

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

[0147] FIG. 6 illustrates a state according to the operating state of an energy harvesting-based device. Specifically, FIG. 6 shows an example of power consumption and device energy state according to the operating state of an energy harvesting-based device having energy storage capacity, according to one embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure.

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

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

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

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

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

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

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

[0155] For example, technical terms used in this disclosure may be as follows.

[0156] - SSB: Synchronization Signal Block

[0157] - MIB: Master Information Block

[0158] - RMSI: Remaining Minimum System Information

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

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

[0161] - BW: Bandwidth

[0162] - BWP: Bandwidth Part

[0163] - RNTI: Radio Network Temporary Identifier

[0164] - CRC: Cyclic Redundancy Check

[0165] - SIB: System Information Block

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

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

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

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

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

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

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

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

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

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

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

[0177] - SCS: subcarrier spacing

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

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

[0180] - TB: Transport Block

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

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

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

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

[0185] - FDRA: Frequency Domain Resource Allocation

[0186] - TDRA: Time Domain Resource Allocation

[0187] - RA: Random Access

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

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

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

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

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

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

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

[0195] - RAR: Random Access Response

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

[0197] - FH: Frequency Hopping

[0198] - iBWP: initial BWP

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

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

[0201] - CS: Cyclic shift

[0202] - NB: Narrowband

[0203] - TO: Traffic Offloading

[0204] - mMTC; massive Machine Type Communications

[0205] - eMBB: enhanced Mobile Broadband Communication

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

[0207] - RedCap: Reduced Capability

[0208] - eRedCap: enhanced RedCap

[0209] - FDD: Frequency Division Duplex

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

[0211] - DRX: Discontinuous Reception

[0212] - RRC: Radio Resource Control

[0213] - RRM: Radio Resource Management

[0214] - MM: Mobility Management

[0215] - IWSN: Industrial Wireless Sensor Network

[0216] - LPWA: Low Power Wide Area

[0217] - RB: Resource Block

[0218] - CCE: Control Channel Element

[0219] - AL: Aggregation Level

[0220] - PRG: Physical Resource-block Group

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

[0222] - PBCH: Physical Broadcast Channel

[0223] - A-PBCH: Additional PBCH

[0224] - BD: blind detection

[0225] - EPRE: Energy Per RE

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

[0227] - TDM: Time Division Multiplexing

[0228] - FDM: Frequency Division Multiplexing

[0229] - DMRS: DeModulation Reference Signal

[0230] - TDD: Time Division Duplex

[0231] - PCI: Physical layer Cell ID

[0232] - EH: Energy Harvesting

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

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

[0235] - ET: Energy Transfer

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

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

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

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

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

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

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

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

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

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

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

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

[0248] - RF-EH: RF energy harvesting

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

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

[0251] - BS: Base Station

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

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

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

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

[0256] - AmIoT: Ambient IoT

[0257] - F-gap: Frequency gap

[0258] - T-gap: Time gap

[0259] - TD: Time Domain

[0260] - FD: Frequency Domain

[0261] - PEI: Paging Early Indication

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

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

[0264] - RSRP: Reference Signal Received Power

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

[0266] - PRB: Physical Resource Block

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

[0268] - PHR: Power Headroom Report

[0269] - EHR: Energy Headroom Report

[0270] - BPF: Band-Pass Filter

[0271] - SM: Subcarrier Modulation

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

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

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

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

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

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

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

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

[0280] In this specification, 'Msg1' may be replaced with or interpreted as an 'Access Random ID message' or a 'Random ID message'. Additionally, 'Msg2' may be replaced with or interpreted as a 'Random ID Response message'. Additionally, 'Msg3' may be replaced with or interpreted as a 'D2R message'.

[0281] In this specification, control information associated with Msg2 (e.g., L1 control information, L2 control information, or L1 / L2 control information) may be included in the PRDCH to which Msg2 is transmitted. Alternatively, said control information may be transmitted to the device via separate signaling prior to the transmission of Msg2.

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

[0283] On the other hand, Msg2 is fundamentally designed to utilize TDM. This is because, since bandpass filtering capability varies by device (or device type), it may be difficult for each device to properly filter and receive multiple FDMed R2D signals / channels transmitted from the reader.

[0284] This specification proposes a method for setting a monitoring window for receiving Msg2 PRDCH during a contention-based access procedure (or contention-based random access (CBRA) procedure) in an ambient IoT system. In this specification, 'monitoring window' may be replaced or interpreted as 'monitor window'.

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

[0286] [Method #1] How to configure TDM between Msg2 PRDCH monitoring window and Msg3 PDRCH transmission

[0287] A monitoring window for receiving Msg2 PRDCH can be defined by a starting time and a duration, etc. For example, the starting time may refer to the start time of the monitoring window. Additionally, the duration may refer to the time interval during which the monitoring window continues.

[0288] For example, the reader can set / instruct the device to set a monitoring window for Msg2 via Msg0 (e.g., an A-IoT Paging message). As a specific example, the reader can set / instruct the device to set a monitoring window for Msg2 via the K field of Msg0.

[0289] If the Msg1 transmission resource is configured with TDM and / or FDM, the reader can TDM multiple Msg2 PRDCHs and transmit them to the device. In this case, the reader can set multiple monitoring windows by i) setting one common monitoring window for the multiple Msg2 PRDCHs or ii) setting a monitoring window for each of the Msg2 PRDCHs.

[0290] When the Reader sets multiple monitoring windows for each of multiple Msg2 PRDCHs, it is necessary to determine whether the Msg3 PDRCH transmission to be sent by each device will be performed after the reception of multiple Msg2 PRDCHs is complete or between the reception of multiple Msg2 PRDCHs.

[0291] For example, the reader can transmit / set / instruct the device information related to the transmission of Msg3 (e.g., a D2R message) through Msg0. As a specific example, the reader can transmit / set / instruct the device parameters used for transmitting Msg3 through the D2R Scheduling Info field of Msg0.

[0292] According to one embodiment, when a plurality of Msg2 PRDCH monitoring windows are set for a device to receive Msg2 PRDCH from a reader, Msg3 PDRCH transmission may be set / defined so as not to be performed between a preceding monitoring window and a subsequent monitoring window.

[0293] For example, devices intending to transmit Msg3 PDRCH after receiving Msg2 PRDCH can be defined as expecting to be set / instructed by the reader on the Msg3 transmission timing so that they can transmit Msg3 PDRCH after the time when multiple monitoring windows for Msg1 PDRCH transmission have all expired (or after the time when multiple Msg2 PRDCHs have all been transmitted from the reader).

[0294] In other words, it can be defined that devices intending to transmit Msg3 PDRCH after receiving Msg2 PRDCH do not expect to be set / instructed by the reader to transmit Msg3 PDRCH before the point in time when multiple monitoring windows have not all closed (or before the point in time when multiple Msg2 PRDCHs have not all been transmitted from the reader).

[0295] Through such settings / instructions, multiple Msg3 PRDCHs within an inventory round can be defined to be TDMed and / or FDMed and transmitted after the Msg2 PRDCH monitoring window has ended (or after all multiple Msg2 PRDCHs have been transmitted from the reader).

[0296] According to one embodiment, when a plurality of Msg2 PRDCH monitoring windows are provided for a device to receive Msg2 PRDCH from a reader, it can be defined so that Msg3 PDRCH transmission is performed between a specific monitoring window and a subsequent monitoring window.

[0297] For example, one or more Msg2 PRDCHs are transmitted within a specific monitoring window, and devices that receive the transmitted Msg2 payload can be defined to transmit all Msg3 PDRCHs associated with that Msg2 payload before the subsequent Msg2 PRDCH monitoring window begins. With this configuration, a device intending to transmit a Msg3 PDRCH can do so without waiting for an extended period after receiving the Msg2 PRDCH directed at it. Consequently, since the device can transmit the Msg3 PDRCH without significant changes in frequency offset caused by the SFO, there is an advantage in transmitting Msg3 more reliably.

[0298] As a specific example, it can be defined that devices intending to transmit Msg3 PDRCH after receiving Msg2 PRDCH expect to be set / instructed by the reader on the Msg3 transmission timing so that they can transmit Msg3 PDRCH (related to the received Msg2 PRDCH) from the time the monitoring window for the currently transmitted Msg2 PRDCH ends until the monitoring window for the next Msg2 PRDCH begins. Alternatively, it can be defined that devices intending to transmit Msg3 PDRCH after receiving Msg2 PRDCH expect to be set / instructed by the reader on the Msg3 transmission timing so that they can transmit Msg3 PDRCH from the time the currently transmitted Msg2 PRDCH is received until the monitoring window for the next Msg2 PRDCH begins.

[0299] In other words, devices intending to transmit Msg3 PDRCH after receiving Msg2 PRDCH can be defined as not expecting to be set / instructed by the reader to transmit Msg3 PDRCH after the start of the next Msg2 PRDCH monitoring window.

[0300] [Method #2] How to define the signals / channels a device can expect within the Msg2 PRDCH monitoring window

[0301] According to one embodiment, when a Msg2 PRDCH monitoring window is defined for receiving Msg2 PRDCH of a device, the device may be defined to expect only a portion of the Msg2 PRDCH to be transmitted within the monitoring window.

[0302] For example, a device can be defined to expect that the preamble of a Msg2 PRDCH will always be transmitted within the Msg2 PRDCH monitoring window. In other words, i) the preamble of a Msg2 PRDCH can be defined to always be transmitted within the monitoring window, and ii) the L1 / L2 control information or Msg2 Payload following the preamble can be defined to be acceptable even if they are outside the monitoring window. In this case, the device can be defined to determine that the Msg1 transmission failed and attempt Msg1 re-access in the following cases:

[0303] - If the device fails to receive the Msg2 PRDCH preamble within the Msg2 PRDCH monitoring window

[0304] - The CRC of the L1 control information in Msg2 PRDCH is not OK

[0305] - If the CRC of Msg2 PRDCH is not OK

[0306] As another example, the device may be defined to expect that the preamble and L1 (or L1 / L2) control information of the Msg2 PRDCH will always be transmitted within the Msg2 PRDCH monitoring window. Specifically, i) the preamble and L1 (or L1 / L2) control information of the Msg2 PRDCH are defined to always be transmitted within the monitoring window, and ii) subsequent Msg2 Payload, etc., can be defined so that it is acceptable even if they exit the monitoring window. In this case, the device may be defined to determine that the Msg1 transmission failed and attempt Msg1 re-access in the following cases:

[0307] - If Msg2 PRDCH preamble and L1 (or L1 / L2) control information is not received within the Msg2 PRDCH monitoring window

[0308] - If the CRC of the L1 control information in Msg2 PRDCH is not OK

[0309] - If the CRC of Msg2 PRDCH is not OK

[0310] As another example, when a Msg2 PRDCH monitoring window is defined for a device to receive a Msg2 PRDCH, the device may be defined to expect the entire Msg2 PRDCH to always be transmitted within the Msg2 PRDCH monitoring window. In this case, if the Msg2 PRDCH contains multiple Msg2 payloads, the payload size may become long; therefore, the reader may set the Msg2 PRDCH monitoring window to be sufficiently long to account for this.

[0311] Meanwhile, cases may be considered where multiple Msg2 PRDCH monitoring windows are configured or directed, and multiple Msg2 PRDCH monitoring windows are assigned discontinuously. In such cases, the following method may be applied.

[0312] According to one embodiment, when a plurality of Msg2 PRDCH monitoring windows are allocated discontinuously, the device can be configured to monitor a subsequent Msg2 PRDCH monitoring window in the following cases:

[0313] - If the device does not receive the Msg2 PRDCH preamble and L1 (or L1 / L2) control information during the first Msg2 PRDCH monitoring window among the plurality of Msg2 PRDCH monitoring windows

[0314] - If the CRC of the L1 control information in Msg2 PRDCH is not OK

[0315] - If the CRC of Msg2 PRDCH is not OK

[0316] For example, in the following case, the device can be defined to determine that the transmission of Msg1 failed and attempt Msg1 re-access later.

[0317] - If the device fails to receive the Msg2 PRDCH preamble and L1 (or L1 / L2) control information even in the last Msg2 PRDCH monitoring window

[0318] - If the CRC of the L1 control information in Msg2 PRDCH is not OK

[0319] - If the CRC of Msg2 PRDCH is not OK

[0320] [Method #3] How to set up the Msg2 PRDCH monitoring window based on Msg1 resource configuration

[0321] According to one embodiment, resources for transmitting Msg1 PDRCH may be configured by TDM and / or FDM. In this case, a method may be considered in which the same Msg2 PDRCH monitoring window is allocated to multiple Msg1 PDRCHs transmitted by FDM in the same time instance.

[0322] For example, the explanation assumes a case where the Msg1 resource is i) 3 times in the time domain TDM and ii) 2 times in the frequency domain FDM. In this case, for the Msg1 resource, i) the time domain index can be defined as 0, 1, or 2, and ii) the frequency domain index can be defined as 0 or 1. At this time, Msg2 PRDCHs associated with two different Msg1 PDRCHs having the same time domain index can be defined to be transmitted within the same Msg2 PRDCH monitoring window. As a specific example, it can be defined so that a monitoring window for transmitting Msg2 PRDCHs associated with two Msg1 PDRCHs having time domain index 0 is first placed, followed by a monitoring window for transmitting Msg2 PRDCHs associated with two Msg1 PDRCHs having time domain index 1, and finally a monitoring window for transmitting Msg2 PRDCHs associated with two Msg1 PDRCHs having time domain index 2. In this case, the reader can transmit frequency domain resource information of the Msg1 PDRCH to the device through the L1 / L2 control information of each Msg2 PRDCH, thereby setting / instructing the device which Msg2 payload is provided.

[0323] According to one embodiment, when resources for transmitting Msg1 PDRCH are configured to be TDM or FDM, i) Msg2 payloads for each Msg1 PDRCH that are FDMed are defined to be transmitted to a single Msg2 PRDCH, and ii) Msg2 payloads for each Msg1 PRDCH that are TDMed are defined to be transmitted through a separate Msg2 PRDCH. In this case, a single Msg2 PRDCH can be defined to correspond to a single monitoring window, and when a Msg2 PRDCH is transmitted to the corresponding monitoring window, the device can be defined not to perform monitoring any further.

[0324] [Method #4] Method to provide information related to the Msg2 PRDCH monitoring window through Msg2 PRDCH control information

[0325] According to one embodiment, information related to the initial Msg2 PRDCH monitoring window may be provided to the device from the reader via Paging (or Query or Query rep / adjust, etc.). In this specification, 'Msg0' may be replaced / interpreted as an Ambient IoT Paging message (A-IoT Paging message) or an Access Trigger message. Also, in this specification, 'Query' may be replaced / interpreted as an A-IoT Paging message. Also, in this specification, 'Query rep' and / or 'Query adjust' may be replaced / interpreted as an Access Trigger message.

[0326] For example, a method to allocate an additional monitoring window can be considered if the reader determines that a single monitoring window is insufficient. In other words, the reader can set / instruct the starting point and / or duration of the additional Msg2 PRDCH monitoring window to be allocated through the L1 / L2 control information of Msg2 PRDCH.

[0327] According to one embodiment, information related to the Msg2 PRDCH monitoring window may be provided to the device from the reader in advance through Paging (or Query or Query rep / adjust, etc.).

[0328] For example, the reader can set / instruct the device to set a monitoring window for Msg2 via Msg0 (e.g., an A-IoT Paging message). As a specific example, the reader can set / instruct the device to set a monitoring window for Msg2 via the K field of Msg0.

[0329] For example, if the reader subsequently determines that too many monitoring windows have been allocated to the device, the reader can configure or instruct the device to skip some monitoring windows. In other words, the reader can instruct the device to skip the subsequent Msg2 PRDCH monitoring windows through the L1 / L2 control information of the Msg2 PRDCH.

[0330] For example, the reader can set / instruct the device for each of one or more monitoring windows in the form of a bitmap, and based on this, the device can skip the one or more monitoring windows.

[0331] For example, the reader can provide the device with an on / off pattern for a specific time interval to set / instruct the device to skip the monitoring window(s) associated with the specific time interval.

[0332] For example, the reader can configure / instruct the device that it does not need to monitor a specific time interval of the current monitoring window through the L1 / L2 control information of Msg2 PRDCH.

[0333] As a specific example, the reader can set / instruct the device the start point and duration of a time interval that does not require monitoring.

[0334] As another specific example, the reader can configure / instruct the device, via the L1 / L2 control information of the Msg2 PRDCH, that the current monitoring window no longer needs to be monitored from a specific point in time until the window ends. In this case, the reader may specify the aforementioned specific point in time separately. Alternatively, the aforementioned specific point in time may be predefined, such as the end time of transmission of the Msg2 PRDCH in which the L1 / L2 control information is delivered.

[0335] In the proposed methods #1 to #4 above, the timing value that is set / instructed by the predefined timing and / or reader may be i) set / instructed in units of chip(s) / codeword(s) / NR OFDM(s) symbol / NR slot, ii) set / instructed in units of a time unit defined for Ambient IoT (e.g., Tc), or iii) set / instructed as a multiple of the time unit defined for Ambient IoT.

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

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

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

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

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

[0341] Referring to FIG. 7, a method according to one embodiment of the present specification includes an access random ID message transmission step (S710), a random ID response message reception step (S730), and a D2R message transmission step (S750).

[0342] In S710, the device sends an Access Random ID message to the reader.

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

[0344] For example, a method according to one embodiment of the present specification may further include the step of receiving a Reader-to-Device (R2D) message from the reader that triggers a Random Access procedure. The step of receiving the R2D message may be performed prior to step S710.

[0345] For example, the above R2D message may mean Msg0 based on at least one of the methods #1 to #4 described above.

[0346] For example, the above R2D message may include an A-IoT paging message and / or an access trigger message.

[0347] As a specific example, if the R2D message is the A-IoT Paging message, a contention-based random access (CBRA) procedure may be initiated by the A-IoT Paging message.

[0348] For example, the above R2D message may include information related to the monitor window.

[0349] In S730, the device receives a Random ID Response message from the reader.

[0350] For example, the above random ID response message may mean Msg2 based on at least one of the methods #1 to #4 described above.

[0351] The above random ID response message is received based on one of a plurality of monitor windows.

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

[0353] For example, the plurality of monitor windows may be related to the monitoring. As a specific example, the monitor window may refer to a preset or defined time interval for monitoring the PRDCH.

[0354] In S750, the device sends a Device-to-Reader (D2R) message to the reader based on the random ID response message.

[0355] For example, the above D2R message may mean Msg3 based on at least one of the above-described methods #1 to #4.

[0356] The above D2R message is transmitted after the above monitor window and before the next monitor window starts. This can be based on the above-described method #1.

[0357] According to one embodiment, the R2D message may further include information related to additional monitor windows for the random ID response message.

[0358] For example, the above random ID response message can be received based on the monitor window and the additional monitor windows.

[0359] For example, the random ID response message may include control information. In this case, the control information may include information related to skipping a specific monitor window among the additional monitoring windows. As a specific example, the random ID response message may be received based on i) the monitor window and ii) one or more monitor windows among the additional monitor windows other than the specific monitor window.

[0360] For example, the information related to the omission may include information related to the start time of the monitor window to be omitted and / or information related to the time interval of the monitor window to be omitted. This embodiment may be based on the above-described method #4.

[0361] According to one embodiment, the random ID response message may include control information. In this case, the control information may include information related to an additional monitor window for the random ID response message.

[0362] For example, the random ID response message may be received based on the monitor window and the additional monitor window. This embodiment may be based on the above-described method #4.

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

[0364] Operations based on the steps of receiving an R2D message (e.g., an A-IoT paging message or an Access Trigger message) that triggers the above-described S710 to S750 and random access procedures can be implemented by the device of FIG. 9. For example, referring to FIG. 9, the device (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on the steps of receiving an R2D message that triggers the above-described S710 to S750 and random access procedures.

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

[0366] The step of transmitting an R2D message (e.g., A-IoT paging message, Access Trigger message) that triggers the random access procedure and S810 to S850 described below corresponds to the step of receiving an R2D message (e.g., A-IoT paging message, Access Trigger message) that triggers the random access procedure and S710 to S750 described in FIG. 7. Considering the above correspondence, redundant descriptions are omitted. In other words, the specific description of the second device operation described below may be replaced by the description / embodiment of FIG. 7 corresponding to the operation.

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

[0368] Referring to FIG. 8, a method according to another embodiment of the present specification includes a step of receiving an access random ID message (S810), a step of transmitting a random ID response message (S830), and a step of receiving a D2R message (S850).

[0369] In S810, the Reader receives an Access Random ID message from the device.

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

[0371] For example, a method according to another embodiment of the present specification may further include the step of transmitting a Reader-to-Device (R2D) message to the device that triggers a Random Access procedure. The step of transmitting the R2D message may be performed prior to step S810.

[0372] For example, the above R2D message may mean Msg0 based on at least one of the methods #1 to #4 described above.

[0373] For example, the above R2D message may include an A-IoT paging message and / or an access trigger message.

[0374] As a specific example, if the R2D message is the A-IoT Paging message, a contention-based random access (CBRA) procedure may be initiated by the A-IoT Paging message.

[0375] In S830, the reader sends a Random ID Response message to the device.

[0376] For example, the above random ID response message may mean Msg2 based on at least one of the methods #1 to #4 described above.

[0377] The above random ID response message is transmitted based on one of a plurality of monitor windows.

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

[0379] For example, the plurality of monitor windows may be related to the monitoring. As a specific example, the monitor window may refer to a preset or defined time interval for monitoring the PRDCH.

[0380] In S850, the reader receives a Device-to-Reader (D2R) message from the device based on the random ID response message.

[0381] For example, the above D2R message may mean Msg3 based on at least one of the above-described methods #1 to #4.

[0382] The above D2R message is received after the above monitor window and before the next monitor window starts.

[0383] Operations based on the transmission steps of R2D messages (e.g., A-IoT paging message, Access Trigger message) that trigger the above-described S810 to S850 and random access procedures can be implemented by the device of FIG. 9. For example, referring to FIG. 9, a reader (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on the transmission steps of R2D messages that trigger S810 to S850 and random access procedures.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. Regarding the method, A step of transmitting an Access Random ID message to a reader; A step of receiving a Random ID Response message from the reader; and The method includes the step of transmitting a Device-to-Reader (D2R) message to the reader based on the random ID response message; The above random ID response message is received based on one of a plurality of monitor windows, and A method characterized by the above D2R message being transmitted after the above monitor window and before the next monitor window starts.

2. In Paragraph 1, The method further includes the step of receiving a Reader-to-Device (R2D) message from the reader that triggers a Random Access procedure; A method characterized in that the above R2D message includes information related to the monitor window.

3. In Paragraph 2, A method characterized in that the above R2D message includes an A-IoT paging message and / or an access trigger message.

4. In Paragraph 2, The above R2D message further includes information related to additional monitor windows for the above random ID response message, and A method characterized in that the above random ID response message is received based on the above monitor window and the above additional monitor windows.

5. In Paragraph 4, The above random ID response message includes control information, and The above control information includes information related to skipping a specific monitor window among the additional monitor windows, and A method characterized in that the above random ID response message is received based on i) the above monitor window and ii) one or more monitor windows other than the specific monitor window among the above additional monitor windows.

6. In Paragraph 4, A method characterized by including information related to the above omission, which includes information related to the start time of the monitor window to be omitted and / or information related to the time interval of the monitor window to be omitted.

7. In Paragraph 1, The above random ID response message includes control information, and The above control information includes information related to an additional monitor window for the above random ID response message, and A method characterized in that the above random ID response message is received based on the above monitor window and the above additional monitor window.

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

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

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

11. Regarding the method, A step of receiving an Access Random ID message from a device; A step of transmitting a Random ID Response message to the device; and The method includes the step of receiving a Device-to-Reader (D2R) message based on the above random ID response message from the device; The above random ID response message is transmitted based on one of a plurality of monitor windows, and A method characterized by receiving the above D2R message after the above monitor window and before the next monitor window starts.

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

Images