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; and receiving a random ID response message from the reader. The random ID response message is one of a plurality of random ID response messages related to different frequency domain resources. The plurality of random ID response messages are multiplexed in a time domain on the basis of a gap.

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. At this time, 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] A device that has transmitted Msg1 (e.g., an Access Random ID message) to a Reader can receive Msg2 (e.g., a Random ID Response message) from the Reader. At this time, since the support for bandpass filtering capability varies by device or device type, TDM is fundamentally considered for the transmission of Msg2. However, when multiple Msg2s are transmitted via TDM, a problem arises in that devices must monitor Msg2 for a long period of time to receive the Msg2 addressed to them. The purpose of this specification is to propose a method to solve the aforementioned problem.

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

[0007] 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 and receiving a Random ID Response message from the reader.

[0008] The above random ID response message is one of a plurality of random ID response messages associated with different frequency domain resources.

[0009] The above multiple random ID response messages are multiplexed in the time domain based on the gap.

[0010] Through this, the device does not have to monitor Msg2 for a long time to receive Msg2 for itself, so the device's power consumption can be effectively reduced.

[0011] The method may further include the step of receiving a Reader-to-Device (R2D) message from the reader that triggers a Random Access procedure. In this case, the R2D message may include an indicator related to the multiplexing of the plurality of random ID response messages.

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

[0013] The above gap may be a time interval between a first timing and a second timing. In this case, the first timing may be related to the control information of the first random ID response message that has an earlier transmission time among two random ID response messages related to two adjacent frequency domain resources. Additionally, the second timing may be related to the second random ID response message among the two random ID response messages.

[0014] The above second timing may be related to the start time of transmission of the above second random ID response message.

[0015] The second timing above may be related to the control information of the second random ID response message.

[0016] Among the plurality of random ID response messages mentioned above, the random ID response message with the earliest transmission time may have a preamble added before the control information. At this time, the remaining random ID response messages among the plurality of random ID response messages may not have a preamble added.

[0017] Based on the fact that the above random ID response message is included in the same Physical Reader-to-Device Channel (PRDCH) as one or more other random ID response messages, the PRDCH may include one or more midambles.

[0018] The above midambles can be added to each of a preset or defined number of random ID response messages.

[0019] The method may further include the step of receiving an R2D message from the reader that triggers random access. In this case, the R2D message may include information related to the number.

[0020] The above midambles can be added at preset or defined time intervals.

[0021] A postamble may be added after the last random ID response message within the above PRDCH.

[0022] A device according to another embodiment of the present specification may include 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.

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

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

[0025] A method according to another embodiment of the present specification includes the steps of receiving an access random ID message from a device and transmitting a random ID response message to the device.

[0026] The above random ID response message is one of a plurality of random ID response messages associated with different frequency domain resources.

[0027] The above multiple random ID response messages are multiplexed in the time domain based on the gap.

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

[0029] According to conventional technology, both Time Division Multiplexing (TDM) and Frequency Division Multiplexing (FDM) transmission methods can be considered for multiple Msg1s, but basically only the TDM method is considered for multiple Msg2s. In this case, since each device must monitor Msg2 for a long time to receive the Msg2 corresponding to it, the power consumption of the device increases, and there is a problem of inefficiency in Ambient IoT environments where low-power operation is required. According to the embodiments of this specification, multiple Msg2s can be transmitted in the FDM method, so each device does not need to monitor the Msg2 corresponding to it for a long time, thus having the advantage of effectively reducing the power consumption of the device.

[0030] In addition, according to an embodiment of the present specification, a gap is set between the control information of Msg2s transmitted via the FDM method, thereby enabling the device to sequentially monitor the control information area, which has the effect of reducing unnecessary receiving operations of the device and improving power efficiency.

[0031] Furthermore, when multiple Msg2s are transmitted over a single Physical Reader-to-Device Channel (PRDCH), it is difficult for each device to determine whether it has received a Msg2, which may lead to the problem of unnecessarily continuing to monitor Msg2s. According to an embodiment of this specification, by adding a midamble between Msg2s within the PRDCH, the device can determine whether to further monitor Msg2s or to stop monitoring since it has already received its own Msg2, thereby improving the reception performance of Msg2s and reducing the power consumption of the device.

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

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

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

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

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

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

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

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

[0040] FIG. 7 illustrates FDM and TDM methods for control information of Msg2 PRDCHs according to an embodiment of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0054] Ambient IoT

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

[0056]

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

[0058]

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

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

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

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

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

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

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

[0066] 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 one embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

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

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

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

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

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

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

[0073] General range

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

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

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

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

[0078] -X is determined in WG.

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

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

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

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

[0083] - Deployment Scenario 1 using Topology 1

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

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

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

[0087] The location of the intermediate node is indoors

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

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

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

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

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

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

[0094] 1. Evaluation Assumptions

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

[0096] Clause 5.3: Applicable maximum distance target value

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

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

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

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

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

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

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

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

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

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

[0107] RAN1-led:

[0108] For Ambient IoT DL and UL:

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

[0110] Numerology, Bandwidth, and Multiple Access

[0111] Waveform and Modulation

[0112] Channel coding

[0113] Downlink Channel / Signal Aspect

[0114] Uplink Channel / Signal Side

[0115] Scheduling and Timing Relationships

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

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

[0118] RAN2 Lead:

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

[0120] for example:

[0121] Paging

[0122] Random access

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

[0124] Interaction with the upper class

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

[0126] RAN3 Leading:

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

[0128] Paging

[0129] Device Context Management

[0130] Data transmission

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

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

[0133] RAN4 Leading:

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

[0135] Research on RF Requirements for Ambient IoT:

[0136] Ambient IoT BS Transmitter / Receiver

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] - SSB: Synchronization Signal Block

[0159] - MIB: Master Information Block

[0160] - RMSI: Remaining Minimum System Information

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

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

[0163] - BW: Bandwidth

[0164] - BWP: Bandwidth Part

[0165] - RNTI: Radio Network Temporary Identifier

[0166] - CRC: Cyclic Redundancy Check

[0167] - SIB: System Information Block

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

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

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

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

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

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

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

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

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

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

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

[0179] - SCS: subcarrier spacing

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

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

[0182] - TB: Transport Block

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

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

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

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

[0187] - FDRA: Frequency Domain Resource Allocation

[0188] - TDRA: Time Domain Resource Allocation

[0189] - RA: Random Access

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

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

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

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

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

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

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

[0197] - RAR: Random Access Response

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

[0199] - FH: Frequency Hopping

[0200] - iBWP: initial BWP

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

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

[0203] - CS: Cyclic shift

[0204] - NB: Narrowband

[0205] - TO: Traffic Offloading

[0206] -mMTC; Massive Machine Type Communications

[0207] - eMBB: enhanced Mobile Broadband Communication

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

[0209] - RedCap: Reduced Capability

[0210] - eRedCap: enhanced RedCap

[0211] - FDD: Frequency Division Duplex

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

[0213] - DRX: Discontinuous Reception

[0214] - RRC: Radio Resource Control

[0215] - RRM: Radio Resource Management

[0216] - MM: Mobility Management

[0217] - IWSN: Industrial Wireless Sensor Network

[0218] - LPWA: Low Power Wide Area

[0219] - RB: Resource Block

[0220] - CCE: Control Channel Element

[0221] - AL: Aggregation Level

[0222] - PRG: Physical Resource-block Group

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

[0224] - PBCH: Physical Broadcast Channel

[0225] - A-PBCH: Additional PBCH

[0226] - BD: blind detection

[0227] - EPRE: Energy Per RE

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

[0229] - TDM: Time Division Multiplexing

[0230] - FDM: Frequency Division Multiplexing

[0231] - DMRS: DeModulation Reference Signal

[0232] - TDD: Time Division Duplex

[0233] - PCI: Physical layer Cell ID

[0234] - EH: Energy Harvesting

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

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

[0237] - ET: Energy Transfer

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

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

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

[0241] - T: Tag / ambient IoT device. 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.

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

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

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

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

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

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

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

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

[0250] - RF-EH: RF energy harvesting

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

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

[0253] - BS: Base Station

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

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

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

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

[0258] - AmIoT: Ambient IoT

[0259] - F-gap: Frequency gap

[0260] - T-gap: Time gap

[0261] - TD: Time Domain

[0262] - FD: Frequency Domain

[0263] - PEI: Paging Early Indication

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

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

[0266] - RSRP: Reference Signal Received Power

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

[0268] - PRB: Physical Resource Block

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

[0270] - PHR: Power Headroom Report

[0271] - EHR: Energy Headroom Report

[0272] - BPF: Band-Pass Filter

[0273] - SM: Subcarrier Modulation

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

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

[0276] 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 (Device to Reader) or R2D (Reader to Device) transmission, a midamble in the middle, and a postamble at the very end.

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

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

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

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

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

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

[0283] At this time, when a time gap index / frequency gap index for D2R transmission is set / instructed to multiple devices, the Msg1 / Msg3 of the multiple devices can be transmitted via TDM / FDM. In this specification, 'time gap index' may be interpreted as a value related to a time domain resource, a value related to a time resource, a value based on a time index field, or a value based on a time resource 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.

[0284] On the other hand, Msg2 is designed with TDM in mind by default. This is due to the technical consideration that, because 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.

[0285] In this specification, a Msg2 PRDCH design method is proposed for a contention-based access procedure (or contention-based random access (CBRA) procedure) in an ambient IoT system.

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

[0287] [Method #1] Method for transmitting multiple Msg2 PRDCHs as FDM

[0288] When multiple Msg2 PRDCHs are transmitted via FDM, a method can be considered in which the L1 / L2 control information of different Msg2 PRDCHs transmitted in at least different frequency domains is transmitted via TDM. For example, the L1 / L2 control information of a Msg2 PRDCH may include a preamble. In other words, the reader can set the transmission timing (TX timing) of different Msg2 PRDCHs to be transmitted via FDM in different frequency domains differently. Through this, it can be configured so that the control information (including preambles) of two or more different Msg2 PRDCHs does not exist via FDM during a specific time interval. For example, since the device must receive the Msg2 PRDCH through frequency filtering, this operation can be used for frequency filtering capable devices (e.g., device type 2b). The proposed method can be illustrated as shown in Fig. 7.

[0289] FIG. 7 illustrates FDM and TDM methods for control information of Msg2 PRDCHs according to an embodiment of the present specification.

[0290] Referring to FIG. 7, devices capable of receiving FDM-enhanced Msg2 PRDCH can be configured to check the control information of Msg2 PRDCH #1 transmitted first. In other words, frequency filtering capable devices can be configured to check the control information of Msg2 PRDCH #1 transmitted first. At this time, if the control information of Msg2 PRDCH #1 contains information related to Msg1 transmitted by the device, the device can be configured to receive the Msg2 payload of Msg2 PRDCH #1. On the other hand, if the control information of Msg2 PRDCH #1 does not contain information related to Msg1 transmitted by the device, the device can be configured to shift the frequency of receiving Msg2 PRDCH and check the control information of Msg2 PRDCH #2 transmitted next. In this way, when the device checks the control information of the Msg2 PRDCHs, a minimum timing gap can be defined between the end of the transmission of the control information of the previously transmitted Msg2 PRDCH and the start of the transmission of the preamble of the next Msg2 PRDCH to be transmitted, so that the device can receive the Msg2 PRDCH transmitted to a different frequency position.

[0291] As another example, i) the first Msg2 PRDCH transmitted consists of a preamble, control information, and data (or payload), and ii) subsequent Msg2 PRDCHs transmitted thereafter may be configured to omit the preamble and transmit only control information and data (or payload). In this case, a minimum timing gap may be defined between the end of the transmission of control information of the previously transmitted Msg2 PRDCH and the start of the transmission of control information of the next Msg2 PRDCH.

[0292] According to one embodiment, a method may also be considered in which the reader defines the section where Msg2 PRDCH transmission is TDMed and the section where FDMed (including TDM) is performed through a separate Msg2 PRDCH monitoring window.

[0293] For example, when a reader provides information regarding the Msg2 PRDCH monitoring window settings, it may indicate via a 1-bit flag whether the Msg2 PRDCHs in the window are TDMed and / or FDMed. In this case, devices that are not capable of frequency filtering (devices without frequency filtering capability) (e.g., device type 1 / 2a) may be configured not to monitor the Msg2 PRDCH monitoring window indicated as being FDMed and transmitted. In other words, devices without frequency filtering capability may be configured to monitor only the Msg2 PRDCH monitoring window indicated as being TDMed and transmitted.

[0294] For example, devices with frequency filtering capability (e.g., device type 2b, etc.) can be configured / defined to monitor all configured Msg2 PRDCH monitoring windows without any particular restrictions.

[0295] As another example, devices with frequency filtering capability may be configured not to monitor the Msg2 PRDCH monitoring window in which the Msg2 PRDCH is TDM-transmitted. In other words, devices with frequency filtering capability may be configured to monitor only the Msg2 PRDCH monitoring window in which the Msg2 PRDCH is FDM-transmitted.

[0296] As another example, one could consider a method where the reader configures / instructs the device that K of the directly connected Msg2 PRDCH monitoring windows do not need to be monitored.

[0297] According to one embodiment, only a specific device type (e.g., device type 2b) that has frequency filtering capability and can receive Msg2 PRDCH transmitted via FDM can be defined to perform PRDCH monitoring during a specific time interval in the Msg2 PRDCH monitoring window when Msg2 PRDCH is transmitted via FDM. In other words, a specific device type (e.g., device type 1 / 2a) that does not have frequency filtering capability and cannot receive Msg2 PRDCH transmitted via FDM can be configured / defined so that PRDCH monitoring does not need to be performed during a specific time interval in the Msg2 PRDCH monitoring window when Msg2 PRDCH is transmitted via FDM.

[0298] According to one embodiment, Msg1 resources can be divided by device type, and Msg2 PRDCH monitoring window can be configured / defined to monitor only specific device types.

[0299] For example, device type 2b (device type with frequency filtering capability) and device type 1 / 2a (device type without frequency filtering capability) can be defined to be assigned to different Msg1 resource groups. In this case, the Msg2 PRDCH monitoring window configured for the Msg1 resource group to which device type 2b is assigned and the Msg2 PRDCH monitoring window configured for the Msg1 resource group to which device type 1 / 2a is assigned can be configured / defined individually.

[0300] According to one embodiment, the Msg1 resource is used commonly by devices, but the Msg2 PRDCH monitoring window can be defined to monitor only specific device types. In other words, the Msg1 resource is allocated to devices regardless of device type, and the Msg2 PRDCH monitoring window can be configured / defined differently for each device type. Specifically, for devices that transmit Msg1 using a specific Msg1 resource, the window for monitoring PRDCH can be individually configured / defined according to the device type.

[0301] For example, the Msg2 PRDCH monitoring window configured for device type 2b can be defined separately from the Msg2 PRDCH monitoring window configured for device type 1 / 2a. Thus, each device can be configured to monitor Msg2 PRDCH using the Msg2 PRDCH monitoring window appropriate for its respective type.

[0302] According to one embodiment, a method for triggering a device type to use the Msg1 resource through Paging (or Query or Query rep / adjust, etc.) may be considered. In this specification, 'Msg0', 'Query', 'Query rep' and / or 'Query adjust' may be replaced / interpreted as an ambient IoT paging message (A-IoT Paging message) or an access trigger message (Access Trigger message).

[0303] For example, if the reader is triggered to use only device type 2b Msg1 resources, the Msg2 PRDCH monitoring window associated with the Msg1 resources may be defined to transmit Msg2 PRDCH via FDM (and TDM). In this case, the frequency resource list, starting time, duration, etc., occupied by the Msg2 PRDCH monitoring window can be provided through Paging (or Query or Query rep / adjust, etc.).

[0304] As another example, if a reader is triggered to use the Msg1 resource for device type 1 and / or device type 2a, the Msg2 PRDCH monitoring window associated with the Msg1 resource may be defined to transmit the Msg2 PRDCH via TDM. In this case, the starting time, duration, etc., of the Msg2 PRDCH monitoring window may be provided through Paging (or Query or Query rep / adjust, etc.).

[0305] [Method #2] A method in which multiple Msg2 payloads are transmitted through a single PRDCH, including a midamble and / or a postamble.

[0306] When a Reader transmits multiple Msg2 payloads through a single PRDCH, a method of transmitting them together with midamble and / or postamble may be considered.

[0307] According to one embodiment, N Msg2 payloads may be added to PRDCH, and one midamble may be added after the N Msg2 payloads.

[0308] For example, the value of N can be defined as being instructed by the reader to the device via Msg0 (e.g., Paging, Query, Query rep / adjust, etc.) or Msg2 PRDCH L1 control information. In this case, N can be defined as a positive integer greater than or equal to 1.

[0309] As a specific example, when a reader intends to transmit K Msg2 payloads within a single PRDCH, midambles can be added one by one after N Msg2 payloads have been added. If, after adding a midamble, there are no more Msg2 payloads to add when fewer than or equal to N Msg2 payloads have been added, it can be defined so that a postamble is added instead of a midamble after the last Msg2 payload.

[0310] According to one embodiment, a method may also be considered in which a reader indicates to a device the total number of Msg2 payloads transmitted within a single PRDCH through Msg0 (e.g., Paging, Query, Query rep / adjust, etc.) or Msg2 PRDCH L1 control information. In this case, since the device knows the last Msg2 payload within the PRDCH, it can be defined so that no separate postamble is added.

[0311] According to one embodiment, since the size may vary for each Msg2 payload, a method of adding a midamble after a specific time may be considered instead of a method of adding a midamble for each Msg2 payload.

[0312] For example, the reader may be defined to pre-set / instruct the timing (e.g., X) for adding a midamble to the Msg2 PRDCH. Additionally, if the time from the end of the preamble transmission for the Msg2 PRDCH to the end of the transmission of the n-th Msg2 payload is greater than the timing value (e.g., X) set / instructed by the reader, a method may be considered to add the midamble after the (n-1)-th Msg2 payload or after the n-th Msg2 payload. Furthermore, it may be defined so that a postamble is added when the transmission of the Msg2 payload is fully completed.

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

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

[0315] 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. 10 (e.g., the processor (110, 210) of FIG. 10).

[0316] 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. 10) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 10).

[0317] The embodiments described above will be explained in detail below with reference to FIGS. 8 and 9 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.

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

[0319] Referring to FIG. 8, a method according to one embodiment of the present specification includes an access random ID message transmission step (S810) and a random ID response message reception step (S830).

[0320] In S810, the device sends an Access Random ID message to the reader.

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

[0322] 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 S810.

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

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

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

[0326] For example, the R2D message may include an indicator related to the multiplexing of the plurality of random ID response messages. In this case, the indicator may include an indicator related to multiplexing in the frequency domain and / or an indicator related to multiplexing in the time domain.

[0327] In S830, the device receives a Random ID Response message from the reader.

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

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

[0330] The above random ID response message is one of a plurality of random ID response messages associated with different frequency domain resources.

[0331] The above multiple random ID response messages are multiplexed in the time domain based on the gap.

[0332] According to one embodiment, the gap may be a time interval between a first timing and a second timing.

[0333] For example, the first timing may be related to the control information of the first random ID response message that has an earlier transmission time among two random ID response messages related to two adjacent frequency domain resources. Additionally, the second timing may be related to the second random ID response message among the two random ID response messages.

[0334] As a specific example, the second timing may be related to the start time of transmission of the second random ID response message. In other words, the gap may refer to the time interval between the end time of transmission of the control information of the first random ID response message and the start time of transmission of the second random ID response message. More specifically, the gap may refer to the time interval between the end time of transmission of the control information of the first random ID response message and the start time of transmission of the preamble of the second random ID response message.

[0335] As another specific example, the second timing may be related to the control information of the second random ID response message. Alternatively, the gap may refer to the time interval between the end of transmission of the control information of the first random ID response message and the start of transmission of the control information of the second random ID response message. This embodiment may be based on Method #1 described above.

[0336] As another example, the control information of the above random ID response message may refer to control information related to the above random ID response message.

[0337] As a specific example, a method according to one embodiment of the present specification may further include the step of receiving control information related to the random ID response message from the reader. The step of receiving control information related to the random ID response message may be performed after S810 and before S830. For example, the control information may be based on an L1 parameter (Layer 1, L1 parameter) or upper layer data. Based on the control information related to the random ID response message, information related to the random ID response message may be directed to the device. In this case, the control information related to the first random ID response message and the control information related to the second random ID response message may be received from the reader at different time intervals.

[0338] According to one embodiment, among the plurality of random ID response messages, the random ID response message with the earliest transmission time may have a preamble added before the control information. At this time, among the plurality of random ID response messages, the remaining random ID response message(s) may not have a preamble added. This embodiment may be based on the above-described method #1.

[0339] According to one embodiment, based on the fact that the random ID response message is included in the same physical reader-to-device channel (PRDCH) as one or more other random ID response messages, the PRDCH may include one or more midambles.

[0340] For example, the above midambles may be added to each of a preset or defined number of random ID response messages.

[0341] For example, a method according to one embodiment of the present specification may further include the step of receiving an R2D message from the reader that triggers random access. In this case, the R2D message may include information related to the number. This embodiment may be based on Method #2 described above.

[0342] According to one embodiment, the midambles may be added at preset or defined time intervals.

[0343] For example, a postamble may be added after the last random ID response message within the above PRDCH.

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

[0345] Operations based on the above-described S810 to S830, the step of receiving an R2D message (e.g., A-IoT paging message, Access Trigger message) that triggers a random access procedure, and the step of receiving control information related to a random ID response message can be implemented by the device of FIG. 10. For example, referring to FIG. 10, the device (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S810 to S830, the step of receiving an R2D message that triggers a random access procedure, and the step of receiving control information related to a random ID response message.

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

[0347] The steps described below, S910 to S930, the step of transmitting an R2D message (e.g., A-IoT paging message, Access Trigger message) that triggers a random access procedure, and the step of transmitting control information related to a random ID response message, correspond to the steps described in FIG. 8, S810 to S830, the step of receiving an R2D message (e.g., A-IoT paging message, Access Trigger message) that triggers a random access procedure, and the step of receiving control information related to a random ID response message. Considering the above correspondence, redundant descriptions are omitted. Alternatively, the specific description of the second device operation described below may be replaced by the description / embodiment of FIG. 8 corresponding to the operation.

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

[0349] Referring to FIG. 9, a method according to another embodiment of the present specification includes a step of receiving an access random ID message (S910) and a step of transmitting a random ID response message (S930).

[0350] In S910, the Reader receives an Access Random ID message from the device.

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

[0352] 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 S910.

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

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

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

[0356] For example, the R2D message may include an indicator related to the multiplexing of the plurality of random ID response messages. In this case, the indicator may include an indicator related to multiplexing in the frequency domain and / or an indicator related to multiplexing in the time domain.

[0357] In S930, the Reader sends a Random ID Response message to the device.

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

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

[0360] The above random ID response message is one of a plurality of random ID response messages associated with different frequency domain resources.

[0361] The above multiple random ID response messages are multiplexed in the time domain based on the gap.

[0362] A method according to one embodiment of the present specification may further include the step of transmitting control information related to the random ID response message to the device. The step of transmitting control information related to the random ID response message may be performed after S910 and before S930.

[0363] Operations based on the above-described S910 to S930, the step of transmitting an R2D message (e.g., A-IoT paging message, Access Trigger message) that triggers a random access procedure, and the step of transmitting control information related to a random ID response message can be implemented by the device of FIG. 10. For example, referring to FIG. 10, a reader (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S910 to S930, the step of transmitting an R2D message that triggers a random access procedure, and the step of transmitting control information related to a random ID response message.

[0364] 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. 10.

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

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

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

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

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

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

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

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

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

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

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

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

[0377] 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; and The method includes the step of receiving a Random ID Response message from the reader; The above random ID response message is one of a plurality of random ID response messages associated with different frequency domain resources, and A method characterized in that the plurality of random ID response messages are multiplexed in the time domain based on a gap.

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 an indicator related to the multiplexing of the plurality of random ID response messages.

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 1, The above gap is a time interval between the first timing and the second timing, and The above first timing is related to the control information of the first random ID response message, which has an earlier transmission time among two random ID response messages related to two adjacent frequency domain resources, and A method characterized in that the second timing is associated with the second random ID response message among the two random ID response messages.

5. In Paragraph 4, A method characterized in that the second timing is related to the start time of transmission of the second random ID response message.

6. In Paragraph 4, A method characterized in that the second timing is related to the control information of the second random ID response message.

7. In Paragraph 1, Among the plurality of random ID response messages mentioned above, the random ID response message with the earliest transmission time has a preamble added before the control information, and A method characterized in that, among the plurality of random ID response messages, the remaining random ID response messages do not have a preamble added.

8. In Paragraph 1, A method characterized in that, based on the fact that the above random ID response message is included in the same Physical Reader-to-Device Channel (PRDCH) as one or more other random ID response messages, the PRDCH includes one or more midambles.

9. In Paragraph 8, A method characterized by the above midambles being added to each of a predetermined or defined number of random ID response messages.

10. In Paragraph 9, The method further includes the step of receiving an R2D message from the reader that triggers random access; A method characterized in that the above R2D message includes information related to the above number.

11. In Paragraph 8, A method characterized in that the above midambles are added at predetermined or defined time intervals.

12. In Paragraph 8, A method characterized by adding a postamble after the last random ID response message within the above PRDCH.

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

14. An electronic device comprising one or more memories and one or more processors connected to the 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 12, based on execution by the one or more processors.

15. 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 to 12.

16. Regarding the method, A step of receiving an Access Random ID message from a device; and The method includes the step of transmitting a Random ID Response message to the device; The above random ID response message is one of a plurality of random ID response messages associated with different frequency domain resources, and A method characterized in that the plurality of random ID response messages are multiplexed in the time domain based on a gap.

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

Images