Method and apparatus for transmitting and receiving signal for IoT device in wireless communication system

Abstract

A device of an A-IoT system in a wireless communication system comprises: at least one processor; and a memory storing instructions causing a wireless user device to perform a specific operation via the at least one processor, wherein, in the specific operation: the device receives a first message from a reader via an R2D link; and the device transmits a second message via a D2R link, in response to the first message, wherein the same information bit may be repeatedly included in the second message on the basis of a repetition transmission level.

Description

Method and device for transmitting and receiving signals for IoT devices in a wireless communication system

[0001] The present disclosure relates to a method and apparatus for transmitting and receiving signals for an Internet of Things (IoT) device in a wireless communication system. Specifically, it relates to a method and apparatus for transmitting control information for transmitting and receiving signals for an IoT device in a wireless communication system.

[0002]

[0003] The International Telecommunication Union (ITU) is developing the International Mobile Telecommunication (IMT) framework and standards, and recently, discussions for 6th generation (6G) communication are underway through a program called "IMT for 2030 and beyond." 6G communication, a next-generation mobile communication technology, requires ultra-high speed, ultra-low latency, and ultra-high capacity communication performance that surpasses existing 5G. To realize this, securing new radio frequency resources and utilizing them efficiently are emerging as key challenges. In particular, a multi-layered spectrum structure ranging from high to low bands is essential to satisfy various service scenarios, and this requires technical optimization based on the characteristics of each frequency band.

[0004]

[0005] The technical problem of the present disclosure is a method and device for transmitting and receiving signals for an IoT device in a wireless communication system.

[0006] The technical problem of the present disclosure is a method and apparatus for transmitting and receiving signals for an Ambient IoT (A-IoT) device in a wireless communication system.

[0007] The technical problem of the present disclosure is a method and apparatus for transmitting control information for transmitting R2D (reader to device) links and D2R (device to reader) links between an A-IoT device and a reader in a wireless communication system.

[0008] The technical problem of the present disclosure is a method and apparatus for an A-IoT device to perform D2R iterative transmission to a reader in a wireless communication system.

[0009] The technical problem of the present disclosure is a method and apparatus for performing D2R iterative transmission based on control information received from a reader by an A-IoT device in a wireless communication system.

[0010] The technical problems to be solved in this disclosure 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 disclosure belongs from the description below.

[0011]

[0012] According to one aspect of the present disclosure, an ambient-internet of things (A-IoT) system device comprises at least one processor and a memory storing instructions for a wireless user device to perform a specific operation by the at least one processor, wherein the specific operation is: the device receiving a first message from a reader via a reader-to-device (R2D) link, and the device transmitting a second message via a device-to-reader (D2R) link in response to the first message, wherein the second message may include the same information bits repeated based on a repeat transmission level.

[0013] Additionally, according to one aspect of the present disclosure, a method of operating a device in an A-IoT system comprises the steps of: the device receiving a first message from a reader via an R2D (reader to device) link; and the device transmitting a second message via a D2R (device to reader) link in response to the first message, wherein the second message may include the same information bits repeated based on a repeat transmission level.

[0014] In addition, the following points may apply in common.

[0015] According to one aspect of the present disclosure, a second message containing the same information bits repeatedly based on a repeat transmission level can be transmitted from a device to a reader through a single D2R transmission resource.

[0016] Additionally, according to one aspect of the present disclosure, at least one of a time domain resource, a frequency domain resource, and repeat transmission level information of a D2R transmission resource may be transmitted from a reader to a device through a first message.

[0017] Additionally, according to one aspect of the present disclosure, at least one of the time domain resource, frequency domain resource, and repeat transmission level information of a D2R transmission resource may be pre-configured in the device.

[0018] Additionally, according to one aspect of the present disclosure, the first message includes at least one identification information, each of which corresponds to a device or a group of devices, and based on the identification information, setting information related to the transmission of a second message may be transmitted from a reader to a device.

[0019] Additionally, according to one aspect of the present disclosure, the device may directly determine a repeat transmission level for the second message based on setting information related to the transmission of the second message received from a reader.

[0020] Additionally, according to one aspect of the present disclosure, the second message may be transmitted within a predetermined time interval from the time of completion of reception of the first message.

[0021]

[0022] According to the present disclosure, a method for transmitting and receiving signals for an IoT device in a wireless communication system can be provided.

[0023] According to the present disclosure, a method for transmitting and receiving signals for an A-IoT device in a wireless communication system can be provided.

[0024] According to the present disclosure, a method for transmitting control information for transmitting R2D links and D2R links between an A-IoT device and a reader in a wireless communication system can be provided.

[0025] According to the present disclosure, a method can be provided for an A-IoT device to perform D2R iterative transmission to a reader in a wireless communication system.

[0026] According to the present disclosure, a method can be provided for an A-IoT device in a wireless communication system to perform D2R iterative transmission based on control information received from a reader.

[0027] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0028]

[0029] FIG. 1 is a drawing for explaining the frame structure of a wireless communication system to which the present disclosure can be applied.

[0030] FIG. 2 is a diagram showing the resource structure of a wireless communication system to which the present disclosure can be applied.

[0031] FIG. 3 is a diagram showing an A-IoT related topology to which the present disclosure can be applied.

[0032] FIG. 4 is a diagram showing an A-IoT related link to which the present disclosure can be applied.

[0033] FIG. 5 is a diagram showing a frequency spectrum usage mode for A-IoT to which the present disclosure can be applied.

[0034] FIG. 6 is a diagram showing a modulation scheme and waveform to which the present disclosure can be applied.

[0035] FIG. 7 is a diagram showing a method of configuring a transmission block to which the present disclosure can be applied.

[0036] FIG. 8 is a diagram showing Manchester coding and PIE coding to which the present disclosure can be applied.

[0037] FIG. 9 is a diagram illustrating a Manchester encoding and decoding method to which the present disclosure can be applied.

[0038] FIG. 10 is a diagram showing a PIE encoding and decoding method to which the present disclosure can be applied.

[0039] FIG. 11 is a diagram showing the R2D bandwidth and numerology to which the present disclosure can be applied.

[0040] FIG. 12 is a diagram showing the R2D bandwidth to which the present disclosure can be applied.

[0041] FIG. 13 is a diagram showing PRDCH generation and PDRCH generation to which the present disclosure can be applied.

[0042] FIG. 14 may be a D2R bandwidth to which the present disclosure can be applied.

[0043] FIG. 15 is a drawing showing the basic frame structure of PRDCH and PDRCH to which the present disclosure can be applied.

[0044] FIG. 16 is a diagram showing block level, bit level type 1 and bit level type 2 to which the present disclosure can be applied.

[0045] FIG. 17 is a diagram illustrating the overall AS (Access Stratum) procedure between an A-IoT device and a reader to which the present disclosure can be applied.

[0046] FIG. 18 is a diagram illustrating a 4-step based A-IoT random access procedure to which the present disclosure can be applied.

[0047] FIG. 19 is a diagram illustrating a 2-step based A-IoT random access procedure to which the present disclosure can be applied.

[0048] FIG. 20 is a diagram showing the minimum and maximum time required between R2D / D2R transmission and reception that can be applied to the present disclosure.

[0049] FIG. 21 is a diagram showing a general framework of slotted-ALOHA for an A-IoT random access procedure that can be applied to the present disclosure.

[0050] FIG. 22 is a diagram showing a control information structure for D2R transmission within a Paging message applicable to the present disclosure.

[0051] FIG. 23 is a diagram showing an example of repeated transmission of A-IoT Msg1 (D2R) after receiving a paging message that can be applied to the present disclosure.

[0052] FIG. 24 is a diagram showing an AO selection considering the minimum time between D2R iterative transmissions that can be applied to the present disclosure.

[0053] FIG. 25 is a diagram illustrating a method for selecting N AO resources for repetitive transmission that can be applied to the present disclosure.

[0054] FIG. 26 is a diagram illustrating a method for selecting N AO resources for repetitive transmission that can be applied to the present disclosure.

[0055] FIG. 27 is a diagram illustrating an AO Set random selection-based D2R iterative transmission resource allocation applicable to the present disclosure.

[0056] FIG. 28 is a diagram illustrating an AO Set random selection-based D2R iterative transmission resource allocation applicable to the present disclosure.

[0057] FIG. 29 is a diagram illustrating an example of D2R iterative transmission based on explicit signaling from R2D that can be applied to the present disclosure.

[0058] FIG. 30 is a diagram illustrating an example of D2R iterative transmission based on explicit signaling from R2D that can be applied to the present disclosure.

[0059] FIG. 31 is a diagram showing an example of a Msg1 (D2R) repeated transmission method (only TDM) for a plurality of devices applicable to the present disclosure.

[0060] FIG. 32 is a diagram showing the determination of the D2R repetitive transmission level based on the received power strength of an R2D signal using two threshold values ​​applicable to the present disclosure.

[0061] FIG. 33 is a flowchart illustrating the repetitive transmission operation of an A-IoT device to which the present disclosure applies.

[0062] FIG. 34 is a drawing showing a base station device and a terminal device to which the present disclosure can be applied.

[0063]

[0064] Hereinafter, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein.

[0065] In describing the embodiments of the present disclosure, if it is determined that a detailed description of known configurations or functions may obscure the essence of the present disclosure, such detailed description is omitted. Furthermore, parts of the drawings unrelated to the description of the present disclosure have been omitted, and similar parts are denoted by similar reference numerals.

[0066] In the present disclosure, when a component is described as being "connected," "combined," or "joined" with another component, this may include not only a direct connection but also an indirect connection in which another component exists in between. Furthermore, when a component is described as "comprising" or "having" another component, this means that, unless specifically stated otherwise, it does not exclude the other component but may include an additional component.

[0067] In the present disclosure, terms such as first, second, etc. are used solely for the purpose of distinguishing one component from another and do not limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0068] In this disclosure, distinct components are intended to clearly describe their respective features and do not imply that the components are separate. That is, multiple components may be integrated to form a single hardware or software unit, or a single component may be distributed to form multiple hardware or software units. Accordingly, such integrated or distributed embodiments are included within the scope of this disclosure, unless otherwise noted.

[0069] In the present disclosure, the components described in various embodiments do not necessarily mean essential components, and some may be optional components. Accordingly, embodiments consisting of a subset of the components described in one embodiment are also included within the scope of the present disclosure. Furthermore, embodiments including additional components in addition to the components described in various embodiments are also included within the scope of the present disclosure.

[0070] The present disclosure describes a wireless communication network, and operations performed in the wireless communication network may be performed in the process of controlling the network and transmitting or receiving signals by a system (e.g., a base station) governing the wireless communication network, or in the process of transmitting or receiving signals by a terminal connected to the wireless network.

[0071] It is self-evident that various operations performed for communication with a terminal in a network consisting of multiple network nodes, including a base station, can be performed by the base station or other network nodes other than the base station. The term 'Base Station (BS)' may be replaced by terms such as fixed station, Node B, eNodeB (eNB), ng-eNB, gNodeB (gNB), and Access Point (AP). Additionally, the term 'terminal' may be replaced by terms such as User Equipment (UE), Mobile Station (MS), Mobile Subscriber Station (MSS), Subscriber Station (SS), and non-AP Station (non-AP STA).

[0072] In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or signals through said channel. For example, transmitting a control channel means transmitting control information or signals through the control channel. Similarly, transmitting a data channel means transmitting data information or signals through the data channel.

[0073] In the following description, the terms NR (New Radio) or 6GR system are used to distinguish the system to which the various examples of the present disclosure apply from existing systems, but the scope of the present disclosure is not limited by these terms.

[0074] As the aforementioned 5G NR systems enter maturity and are widely deployed, the need for new radio access technologies is emerging to meet anticipated technological evolution and increasing demand. Simple evolution of existing technologies alone is insufficient to meet the extreme performance, flexibility, and scalability required by immersive multimedia, large-scale IoT, the convergence of communications and sensing, and various other future use cases. Accordingly, 3GPP is conducting research on '6G Radio (hereinafter 6GR),' which aims to break free from backward compatibility constraints, re-examine radio system design from scratch, and achieve a groundbreaking leap in performance, efficiency, and simplicity.

[0075] 6GR is defined as a non-backward compatible wireless access technology for existing mobile communication systems (4G, 5G, etc.). This research aims to develop a single technology framework covering frequency bands up to 52.6 GHz (including FR1, the band between FR1 and FR2, FR2-1, and FR3) and is based on a stand-alone architecture. The core principle of 6GR is to reduce implementation costs and energy consumption by minimizing unnecessary options and configuration complexity through a unified technology framework that provides a unified technology framework even in environments with fragmented spectrum and heterogeneous devices.

[0076] The physical layer of 6GR uses 5G NR as a benchmark, but performs optimization to satisfy 6G requirements.

[0077] - Waveform and Modulation: Consider OFDM-based waveforms and modulation schemes similar to 5G NR, but seek improved methods based on this as a baseline.

[0078] - Frame structure and spectrum sharing: To support seamless migration from 5G to 6G, a frame structure compatible with 5G NR is considered to enable Multi-RAT Spectrum Sharing (MRSS) between 5G NR and 6GR.

[0079] - Channel Coding: LDPC and Polar codes are used as the baseline, but scalability is considered by taking into account the trade-off between performance and complexity.

[0080] - Bandwidth and Duplexing: Aim to support a wideband channel bandwidth of at least 200 MHz in bands above 2 GHz (especially near 7 GHz), and avoid the use of multiple numerologies within the same band.

[0081]

[0082] The 6GR study aims to achieve the following key performance indicators:

[0083] Energy Efficiency: Improvement of energy efficiency and energy savings in both the network and the terminal.

[0084] Coverage improvement: Focus on improving cell-edge performance and uplink coverage, and particularly when introducing the 7GHz band, aim to secure coverage at a level where the existing 3.5GHz 5G site grid can be reused.

[0085] Flexibility and Harmony: Aims for a scalable design that supports various device types and a harmonious design between the terrestrial (TN) and non-terrestrial (NTN) networks.

[0086] System Simplification: Pursue overall system simplification by reducing configuration complexity and increasing the efficiency of cell and terminal management.

[0087] Furthermore, 6G mobile communication technology may include new wireless communication transmission and reception technologies that fundamentally exclude backward compatibility with previous systems, including not only 5G NR systems but also existing 4G LTE-A (Long Term Evolution-Advanced) and LTE (Long Term Evolution) systems. On the other hand, technologies are required to facilitate coexistence and efficient operation between existing systems and 6GR systems in order to efficiently and gradually migrate from existing systems to the new 6GR. Therefore, research on technologies for 6G mobile communication that can share wireless resources and coexist with existing 5G NR systems and / or 4G LTE / LTE-A systems is necessary. Of course, existing systems are not limited to the aforementioned 4G / 5G systems; compatibility with various systems such as 3G or other LPWA systems (NB-IoT / LTE-M), Ambient IoT, 5G NTN, and RedCap must be considered.

[0088] First, I would like to briefly explain the physical resource structure of the wireless communication system to which the present invention is applied.

[0089] FIG. 1 is a drawing for explaining the frame structure of a next-generation mobile communication system to which the present disclosure can be applied.

[0090] The frame structure and numerology of next-generation mobile communication systems (e.g., 6GR) may be similar or identical to those of current wireless communication systems (e.g., 5G NR). Although they may vary depending on the numerology applied according to each frequency band / range, next-generation wireless communication systems (e.g., 6GR) can also operate based on at least OFDM (orthogonal frequency division multiplexing) waveforms. That is, the following frame structure may be reused in next-generation mobile communication systems (e.g., 6GR), but additional improvements may be applied, and it is not limited to a specific form.

[0091] For example, in next-generation mobile communication systems (e.g., 6GR), the time unit structure of basic radio frames (10ms) and subframes (1ms) can be utilized identically. Additionally, in next-generation mobile communication systems (e.g., 6GR), slot units having different time intervals depending on the Subcarrier Spacing (SCS) can be utilized identically. Furthermore, in next-generation mobile communication systems (e.g., 6GR), a resource defined by one subcarrier and one symbol can be a resource element (RE), and a resource block (RB) consists of 12 consecutive subcarriers per RB and can be applied identically to all SCSs. Additionally, one radio frame contains 10 subframes, and for a given SCS and symbol, the symbol interval, normal cyclic prefix (CP) length, and boundaries can all be identical to those of current wireless communication systems (e.g., 5G). However, this is not limited thereto.

[0092] For example, a single slot may be configured to include 14 consecutive symbols for all SCS and normal CP. Additionally, to accommodate a wider variety of traffic types within the frame structure, more flexible time domain bundling-based transmission times (e.g., time domain bundling based TTI) may be utilized for at least one of data, control signals, and channel transmission based on various OFDM symbol count settings (e.g., 7, 14, 28, 56 symbols within this period).

[0093] FIGS. 1 and FIGS. 2 are frameworks based on current wireless communication systems and may be applied to next-generation mobile communication systems (e.g., 6GR), but are not limited thereto. That is, it may be possible to configure them differently in consideration of next-generation mobile communication systems (e.g., 6GR), and are not limited to the following items.

[0094] For example, in a wireless communication system, the basic unit of the time domain is It could be, and N can be 4096. Meanwhile, the basic unit of the time domain in LTE is It could be, And, = can be 2048. The constant for the multiple relationship between the NR time base unit and the LTE time base unit is k= It can be defined as.

[0095] Referring to FIG. 1, the time structure of a frame for downlink / uplink (DL / UL) transmission is It can have. Here, one frame is It consists of 10 subframes corresponding to time. The number of consecutive OFDM symbols per subframe is = It may be possible. In addition, each frame may be divided into two half frames of the same size, half frame 1 may consist of subframes 0-4, and half frame 2 may consist of subframes 5-9.

[0096] represents the timing advance (TA) between the downlink (DL) and uplink (UL). Here, the transmission timing of the uplink transmission frame i is determined based on the downlink reception timing at the terminal and the following Equation 1.

[0097] [Mathematical Formula 1]

[0098]

[0099]

[0100] Here, can be a TA offset value resulting from duplex mode differences, etc. In FDD (Frequency Division Duplex), Although it has a value of 0, in TDD (Time Division Duplex), considering the margin for DL-UL switching time, It can be defined as a fixed value. For example, in TDD (Time Division Duplex) of FR1 (Frequency Range 1), which is a frequency below 6 GHz. is 39936 or 25600 It could be. 39936 is 20.327μs, and 25600 is 13.030 μs. Also, at FR2 (Frequency Range 2), which is a millimeter wave (mmWave) frequency is 13792 It could be. In this case, 13792 It is 7.020 μs.

[0101] FIG. 2 is a diagram showing an NR resource structure to which the present disclosure can be applied.

[0102] Resource elements (REs) within a resource grid can be indexed according to each subcarrier spacing. Here, one resource grid can be created for each antenna port and for each subcarrier spacing. Uplink and downlink transmission and reception can be performed based on the corresponding resource grid.

[0103] In the frequency domain, a single Resource Block (RB) consists of 12 REs, and an index (nPRB) for one RB can be configured for each of the 12 REs. The index for an RB can be utilized within a specific frequency band or system bandwidth. The index for an RB can be defined as shown in Equation 2 below. Here, represents the number of subcarriers per RB, and k represents the subcarrier index.

[0104] [Mathematical Formula 2]

[0105]

[0106]

[0107] The new technology of the 6GR system can be configured to satisfy various services and requirements. Referring to Table 1, the new technology can be defined based on at least one of the SCS, CP length, number of OFDM symbols per slot, and other criteria used in the OFDM system. These values ​​may be provided to the terminal via the upper layer parameters DL-BWP-mu and DL-BWP-cp for the downlink, and via the upper layer parameters UL-BWP-mu and UL-BWP-cp for the uplink, but are not limited thereto.

[0108] In addition, only cases where μ is 0 to 4 in Table 1 below and SCS is a normal CP can be applied to the 6GR system (except for PRACH). Here, for other systems (e.g., NTN, ISAC, IoT, etc.), an extended CP may be considered in addition to the numerologies in Table 1, and is not limited to a specific form. Table 1 below shows examples of numerologies supported by the NR system.

[0109] [Table 1]

[0110]

[0111] A normal slot can be defined as the basic time unit used to transmit one data and control information in an NR / 6GR system. The length of a normal slot can be set to the number of 14 OFDM symbols by default. In addition, unlike a slot, a subframe has an absolute time length of 1 ms in an NR / 6GR system and can be used as a reference time for the length of other time intervals. Here, for the coexistence or backward compatibility of LTE, NR, and 6GR systems, time intervals similar to the LTE / NR subframe may be required in the 6GR specification.

[0112] For example, in LTE, data can be transmitted based on a unit of time called a Transmission Time Interval (TTI), and the TTI can be set to one or more subframe units. Here, one subframe can be set to 1ms and can contain 14 OFDM symbols (or 12 OFDM symbols). On the other hand, in NR / 6GR, the normal slot (slot) form is utilized as the basic TTI unit, and the time length of the corresponding slot can be defined in various ways according to the numerology (1ms, 0.5ms, 0.25ms, etc.). Here, based on the aforementioned characteristics, various numerologies can be configured to meet the required quality of service (QoS) and the wireless channel environment of the terminal. Additionally, a non-slot can be defined in NR / 6GR. A non-slot may refer to a slot having a number that is at least one symbol smaller than a normal slot. For example, when providing low latency such as in URLLC services, latency can be reduced through non-slots having a smaller number of symbols than normal slots. Here, the number of OFDM symbols included in the non-slots can be determined by considering the frequency range. For example, in frequency ranges of 6 GHz or higher, non-slots with a length of 1 OFDM symbol may be considered. As an additional example, the number of OFDM symbols defining a non-slot may include at least 2 OFDM symbols. Here, the range of the number of OFDM symbols included in the non-slots can be set as the length of a mini-slot up to a predetermined length (e.g., normal slot length - 1). However, as a specification for non-slots, the number of OFDM symbols may be limited to a range of 2, 4, or 7 symbols, but is not limited thereto.

[0113] In addition, when performing time resource scheduling in 6GR, one data channel scheduling can be supported across one or more slots. That is, wireless data and control channel transmission using more than 14 OFDM symbols, which is the number of OFDM symbols included in at least one slot, can be performed by the base station to the terminal.

[0114] [Table 2]

[0115]

[0116] Table 2 shows the number of OFDM symbols per slot for normal CP by subcarrier spacing setting (u) ( ), number of slots per frame( ), number of slots per subframe( It represents ). Table 2 shows the values ​​described above based on a normal slot with 14 OFDM symbols.

[0117] In addition, 6GR may be defined based on the following SCS for all signals / channels excluding PRACH, but is not limited thereto.

[0118] ● Sub 6 GHz (6 GHz or lower band)

[0119] o Supported SCS: 15 kHz for FDD, 30 kHz for TDD.

[0120] o 30 kHz for FDD (e.g., 1-2.5 GHz band) and 7.5 kHz for Sub-1 GHz FDD may be added, but are not limited to specific embodiments.

[0121] ● Around 7 GHz (band near 7 GHz)

[0122] o SCS: 30 kHz, 60 kHz.

[0123] o Bandwidth and SCS Assumptions: From a network perspective, "maximum 400 MHz channel bandwidth (Max CBW) and 30 kHz SCS" are assumed by default. (How the UE (terminal) supports the 400 MHz bandwidth may vary and is not limited to a specific form.)

[0124] ● Around 15 GHz (15GHz band)

[0125] o Target SCS: 30 kHz, 60 kHz, 120 kHz.

[0126] ● 24.25 GHz - 52.6 GHz (mmWave band)

[0127] o Supported SCS: 120 kHz SCS.

[0128]

[0129] Additionally, for example, Extended CP may not be applied to 6GR TN (Terrestrial Network) communications. Specifically, in a terrestrial network environment, Normal CP alone may be sufficient to cover the Delay Spread, or the benefits may not outweigh the overhead when introducing Extended CP, so only Normal CP may be applied. However, for example, it may be possible to apply Extended CP separately to non-terrestrial networks such as NTN or other services such as ISAC (Integrated Sensing and Communication), and it is not limited to a specific form.

[0130] Additionally, FR2-1 bandwidth may be considered in 6GR. FR2-1 may support a Maximum Channel Bandwidth of 400 MHz or 800 MHz, but is not limited thereto. Table 3 below represents structural options for a UE to receive / process a signal when the network transmits a 400 MHz Single Carrier, which may be Options 1 through 5. For example, the specific functions of the BB processor separated in Options 3 and 4 of Table 3 may differ and are not limited to a specific form. Furthermore, in Table 3 below, the DL (downlink) and UL (uplink) designs may be independent, but are not limited thereto. In addition, for example, a 16k FFT to process 400MHz at once may be burdensome to the terminal, and in Table 3, a method of splitting into two 8k FFTs to avoid the 16k FFT may be considered (Option 2, Option 3), but is not limited thereto. Also, the number of RF chains may be a single RF chain in Option 1 and Option 4. In the above cases, since the RF chain must cover 400MHz, high-performance PA / LNA and broadband filtering technology may be required. On the other hand, Option 2 and Option 3 are dual RF chains, which increase the number of components but reduce the bandwidth burden on individual components. That is, different options may be determined based on the combination of "broadband RF processing capability" and "Baseband (BB) processing capability" based on hardware feasibility, but are not limited thereto.

[0131]

[0132] [Table 3]

[0133]

[0134]

[0135] Additionally, as previously mentioned, one subframe may correspond to 1ms on the time axis. Also, one slot may correspond to 14 symbols on the time axis. For example, one slot may correspond to 7 symbols on the time axis. Accordingly, the number of slots and symbols that can be considered within 10ms corresponding to one radio frame may be set differently. Table 4 may show the number of slots and symbols according to each SCS. In Table 4, an SCS of 480kHz may not be considered, but is not limited to these examples.

[0136] [Table 4]

[0137]

[0138]

[0139] [Ambient IoT (A-IoT)] Basic Background Technology:

[0140] Ambient IoT (A-IoT) is a form of Internet of Things (IoT) technology that can provide various services and functions and has the following advantages.

[0141]

[0142] Low power consumption

[0143] A-IoT devices consume very low power and utilize energy harvesting technology to collect energy from the surrounding environment, which significantly extends battery life and minimizes maintenance requirements.

[0144] Endless connectivity

[0145] A-IoT devices are continuously connected and can communicate with servers or other IoT devices through various network technologies (e.g., NB-IoT, LoRaWAN, 5G, etc.), enabling real-time data collection and analysis, which can improve decision-making processes and promote automation.

[0146] Integration and interoperability

[0147] A-IoT solutions can be easily integrated into various platforms and systems, thereby enhancing interoperability. A-IoT enables the construction of more efficient systems by allowing devices from various manufacturers to communicate and cooperate with each other.

[0148] intelligent interaction

[0149] A-IoT devices can combine sensors and artificial intelligence (AI) algorithms to detect and respond to user behavior and environmental changes. For example, a smart home system can detect changes in ambient temperature and automatically adjust the heating system, but is not limited to such embodiments.

[0150] Security and privacy

[0151] Ambient IoT systems can perform security and privacy protection in the collection and processing of personal data, and this can be achieved through various security measures such as encryption technology.

[0152] Application fields

[0153] A-IoT can be utilized in various fields. For example, it can be applied in smart homes, smart cities, healthcare, agriculture, industrial automation, and other areas, thereby enhancing the convenience of daily life. Furthermore, A-IoT can improve energy efficiency and enable the effective management of resources.

[0154] A-IoT can be an innovative technology in itself, and as it grows alongside IoT technology, it is expected to be deeply applied to our daily lives and industries within the next few years.

[0155] Two group sets for use cases / services

[0156] A-IoT can be classified based on the deployment environment (Group A), as shown in Table 5 below. Additionally, Ambient IoT can be classified based on functionality / application (Group B), as shown in Table 6.

[0157] [Table 5]

[0158]

[0159]

[0160] [Table 6]

[0161]

[0162]

[0163] Based on the foregoing, A-IoT technology is described below. Terms related to A-IoT technology may be as follows, but are not limited to these names or technologies.

[0164]

[0165] PRDCH (R2D, reader to device)

[0166] PRDCH (physical reader to device channel) can refer to a communication channel that transmits A-IoT information from a reader (e.g., base station or user device) to an A-IoT device. As a physical layer R2D channel, PRDCH can transmit data information as well as control information from the physical layer or higher layers.

[0167] PDRCH (R2D, device to reader)

[0168] PDRCH (physical device to reader channel) can refer to a communication channel that transmits A-IoT information from an A-IoT device to a reader (e.g., a base station or user device). As a physical layer D2R channel, PDRCH can transmit data information as well as control information from the physical layer or higher layers.

[0169] reader

[0170] FIG. 3 is a diagram illustrating an A-IoT related topology to which the present disclosure may be applied. Referring to FIG. 3, a user device may be a leader at a base station (310) in topology 1 or at an intermediate node (340) in topology 2. Additionally, any one of a relay, an IAB node (integrated access / backhaul node), and a repeater capable of transmitting and receiving signals to and from A-IoT may be a leader. The leader may be located at the base station (310) in topology 1 and may perform direct bidirectional communication with an A-IoT device (320). Additionally, the leader may be located at a repeater in a micro cell or co-site in a form that coexists with the base station (310).

[0171] As described above in Topology 2, various intermediate nodes (340), including user devices, can communicate with the A-IoT device (350) as leaders. For example, the base station (330) may be located outdoors as a micro cell, and the intermediate node (340) may be located indoors as a leader, but is not limited thereto. For example, the intermediate node (340) may be a node capable of communicating with the A-IoT device (350) as a relay, IAB node, UE, repeater, and other device as described above, and is not limited to a specific form.

[0172] For example, transmission from an A-IoT device (including backscattering transmission) may be performed at least in the uplink frequency spectrum. However, transmission from an A-IoT device is not limited to the use of the uplink frequency spectrum alone, and it may be possible to use other frequency spectra.

[0173] device

[0174] The device may have multiple types as an A-IoT device. For example, the A-IoT device may be determined as a type to which a new wireless access technology is applied, taking into account use cases and scenarios. The A-IoT device type may be a device requiring lower specifications and lower power consumption than a terminal applied to existing NB-IoT (narrowband-IoT) / eMTC (enhanced machine type communication) wireless access technology, and the A-IoT device type may be as follows, but is not limited thereto.

[0175] Device 1 type may consume about 1 μW of peak power and be a type equipped with an energy storage device. Device 1 type may have an initial sampling frequency offset (SFO) of up to 10X ppm. Additionally, Device 1 type may not perform DL (downlink) or UL (uplink) amplification. Additionally, the UL transmission (i.e., D2R transmission) of Device 1 type may be transmitted in a manner that backscatters from an externally provided carrier wave.

[0176] In another type, device 2a may be a type having a peak power consumption of a few hundred μW or less and equipped with an energy storage device. Device 2a may have an initial sampling frequency offset (SFO) of up to 10X ppm. Additionally, device 2a may have DL and / or UL amplification, unlike device 1. The UL transmission (i.e., D2R transmission) of device 2a may be transmitted in a manner that is backscattered from an externally provided carrier wave.

[0177] As another type, device 2b may have a peak power consumption of a few hundred μW or less and may be a type equipped with an energy storage device. Device 2b may have an initial sampling frequency offset (SFO) of up to 10X ppm. Additionally, device 2b may also have DL and / or UL amplification like device 2a. On the other hand, the UL transmission (i.e., D2R transmission) of device 2b may be transmitted via an internally generated frequency clock, unlike the UL transmission of device 2a.

[0178] For example, transmissions related to A-IoT devices may use the uplink spectrum (UL spectrum), but are not limited thereto. Additionally, the target coverage of the A-IoT system may be up to 10 to 50 m in India, but is not limited thereto.

[0179] The A-IoT system may not support all of the radio resource control (RRC) states, mobility, hybrid automatic repeat request (HARQ), and automatic repeat request (ARQ) for Topology 1 and Topology 2 of FIG. 3. The traffic environment of the A-IoT device may be communication based on DO-DTT (device originated-device terminated triggered) and DT (device terminated) traffic, and may have data traffic triggered by the network. That is, data transmission may not be triggered at the terminal side. For example, data traffic related to indoor inventory and data traffic related to indoor command may be A-IoT data traffic related to DO-DTT and DT traffic, but is not limited thereto.

[0180] In addition, A-IoT can support combinations of the following use cases. Specifically, A-IoT use cases may include "Inventory only," "Command only," or "Inventory+Command," but are not limited thereto. Here, the specific details of each use case may be as shown in Table 7 below.

[0181] [Table 7]

[0182]

[0183]

[0184] Candidate scenarios for A-IoT

[0185] In addition, A-IoT related scenarios may consider combinations of the scenarios and topologies in Table 8 below. For example, Table 8 may represent possible environments for an A-IoT system, and each candidate scenario in Table 8 may include at least one of the scenario diagram, the carrier wave (CW) transmission location, the supported device types, and the CW / D2R / R2D spectrum. The following discusses related technologies based on the combinations of scenarios and topologies in Table 8, but is not limited thereto.

[0186] [Table 8]

[0187]

[0188]

[0189]

[0190] A-IoT R2D / D2R Link

[0191] FIG. 4 is a diagram illustrating an A-IoT-related link to which the present disclosure may be applied. The R2D link (reader-to-device link) and D2R link (device-to-reader link) considered on each topology (topology 1 / topology 2) of an A-IoT system may be as shown in FIG. 4. For example, in topology 1, an R2D link and a D2R link may be established between a reader (410) and an A-IoT device (420). Additionally, in topology 2, an R2D link and a D2R link may be established between an intermediate node (440) and an A-IoT device (450). In topology 2, if the intermediate node (440) is a movable node (e.g., UE), a method to maintain the connectivity and service continuity of the A-IoT device through mobility may be required, but is not limited to specific embodiments.

[0192] FIG. 5 is a diagram illustrating a frequency spectrum usage mode for A-IoT to which the present disclosure may be applied. Referring to FIG. 5, an A-IoT system may operate based on any one of an in-band mode, a guard-band mode, and a standalone mode. Referring to FIG. 5, the in-band mode may be a mode in which a bandwidth of about tens of MHz within a transmission band is configured to be available as an A-IoT frequency spectrum (510) for an A-IoT device. On the other hand, the guard-band mode may be a mode in which an A-IoT frequency spectrum (520) is configured to be available in a guard band outside the transmission band with a frequency spectrum of about hundreds of kHz. Additionally, the standalone mode may be a mode in which a bandwidth of about tens of MHz is separately configured as an A-IoT frequency spectrum (530). The A-IoT frequency band may be considered as a frequency division duplex (FDD) of the FR 1 (Frequency Range 1) license band. However, the above-described mode is merely one example and is not limited to such embodiments.

[0193]

[0194] FIG. 6 is a diagram illustrating a modulation scheme and waveform to which the present disclosure may be applied. R2D modulation and waveforms may be determined by considering the R2D link. The waveform of the signal used in the R2D link basically uses an OFDM (orthogonal frequency division multiplexing) waveform, and the modulation scheme may use an OOK (on-off keying) modulation scheme. For example, since transmission to an A-IoT device requires the application of a modulation scheme suitable for low-capacity data transmission that is simple, cost-effective, and consumes little power, the above-described method may be applied. For example, OOK-1 and OOK-4 may be used as OOK modulation schemes for A-IoT R2D transmission, but are not limited thereto.

[0195] Referring to FIG. 6, a CP-OFDM (cyclic prefix-OFDM) based OOK-1 modulation scheme can be used for R2D transmission. The CP-OFDM based OOK-1 modulation scheme may be a method of transmitting 1-bit data by utilizing one OOK bit / pulse per OFDM symbol. The transmission speed may vary depending on the SCS (subcarrier spacing) value. For example, in the case of an "On" chip, a specific sequence may be mapped to N subcarriers in the frequency domain. On the other hand, for an "Off" chip, zero values ​​may be assigned to the same subcarriers. Subsequently, an IFFT (inverse fast Fourier transform) and CP insertion are applied to the sequence to perform the final transmission.

[0196] For example, the R2D waveform can be determined as an OFDM waveform to maintain orthogonality with wireless communication systems coexisting on the in-band / guard-band. The R2D waveform may not use an OFDM processing chain in consideration of the device reception complexity on OFDM modulation / demodulation, and OOK-1 / OOK-4 modulation-based OFDM waveforms may be used for low-power and low-complexity terminals. As a specific example, a modulation scheme using one chip per OFDM symbol transmission is OOK-1, and a modulation scheme using multiple (M) chips per OFDM symbol transmission may be OOK-4.

[0197] FIG. 7 is a diagram illustrating a method of configuring a transmission block to which the present disclosure can be applied. Referring to FIG. 7, the transmission block can be configured to apply an OOK modulation scheme while essentially maintaining an OFDM transmission block chain. To this end, a CP-OFDM-based OOK-1 modulation scheme can generate an OOK waveform having a flat spectrum in the frequency domain required to respond to frequency-selective fading channel environments by utilizing an OFDM overlay sequence on OOK symbols. For example, the OFDM overlay sequence can be used to provide flatness to the pulse waveform in the time domain, and the information of the sequence used in on-waveform generation can help improve receiver performance. With the foregoing in mind, the OFDM overlay sequences may currently be a Zadoff-chu (ZC) sequence or an M sequence, but are not limited to such embodiments. Here, the overlay sequence may be allocated for on-chip on N subcarriers and transformed from a frequency domain signal to a time domain time. On the other hand, zeros in the frequency domain can be allocated to the remaining subcarriers for off-chip. After this, IFFT and CP insertion can be performed on the sequence.

[0198] Additionally, as an example, a transmission method utilizing M-bit OOK modulation based on the DFT (discrete Fourier transform)-s-OFDM waveform may be used, and this transmission method can provide higher transmission efficiency than OOK-1. M OOK chips can be transmitted in a single OFDM symbol through DFT-s-OFDM processing. For example, least squares or DFT sequence selection operations may be applied for processing optimization purposes, but are not limited thereto.

[0199] Furthermore, truncation / modification procedures may be processing methods additionally applied to frequency domain signals and can be considered as operations for inserting additional information and optimizations necessary for performing IFFT operations. However, such procedures may not be essential, and their application may be determined based on the implementation. Additionally, the DFT-s-OFDM processing method may consider different approaches during the process of generating OFDM waveforms to support the OOK-4 modulation scheme, unlike CP-OFDM, and is not limited to a specific form.

[0200] As described above, an M-bit OOK in the time domain produced by DFT-s-OFDM processing can be used for high frequency efficiency. That is, a single OFDM symbol can be used for M OOK chips through DFT-s-OFDM processing. Subsequently, the least squares (LS) or DFT sequence selection procedure described above can be applied. Additionally, truncation / modification can be applied to the frequency domain signal, and finally, a signal in the time domain can be generated through an IFFT+CP insertion procedure. Here, the DFT-s-OFDM processing method for OOK-4 can be supported through the same processing procedure even in the case of a single OOK chip (i.e., M=1 (=OOK-1)).

[0201] Regarding the generation of OOK-1 and OOK-4, the M value of OOK-4 can directly influence the determination of the transmission rate of the A-IoT system. For example, A-IoT transmission may be considered to be designed with the goal of providing a transmission rate similar to that of UHF RFID (ultrahigh-frequency identification), but is not limited to this.

[0202] For example, in Manchester coding and OOK-4 with an SCS of 15kHz, M=1, 2, 4, 8, and 16 can provide 7, 14, 28, 56, and 112kbps, respectively, as shown in Table 9. Considering that the maximum transmission rate of UHF RFID R2D is approximately 107kbps, at least up to M=16 can be supported. Additionally, for SCS for A-IoT transmission, OFDM-based waveforms can be considered in consideration of coexistence with existing wireless communication systems (e.g., NR / LTE systems). Therefore, the numerology can basically use a 15kHz SCS value in the FR1 band, and additionally consider a 30kHz SCS, but is not limited to this.

[0203] D2R transmission can be a method that generates and transmits an internal carrier wave through backscatter from the carrier wave, and accordingly, a single carrier waveform rather than an OFDM-based one may be used. For example, if D2R transmission performs OFDM transmission like R2D, the same numerology as R2D may be applied, but it is not limited to this.

[0204] [Table 9]

[0205]

[0206]

[0207] Next, coding methods for A-IoT transmission can be considered. For example, R2D line coding can be applied for A-IoT transmission. R2D line coding is a coding method utilized in systems such as RFID, which assigns a single codeword (CW) to original binary data bits. For instance, regarding the method of transforming codewords using line coding, each pattern can be defined differently for each line coding according to predetermined rules, and accordingly, they may have different advantages and disadvantages.

[0208] Line coding can not only prevent the original data bit sequence from continuously displaying '1' or '0', but can also provide voltage transitions that can be utilized for synchronization purposes. The aforementioned synchronization method (i.e., chip-level timing tracking) can be utilized as a significant advantage for A-IoT receiving devices requiring low-complexity operation. For example, Manchester encoding and pulse-interval encoding (PIE) can be used as line coding methods for R2D below, as shown in FIG. 8. However, it is not limited thereto.

[0209]

[0210] Manchester Code

[0211] For example, a Manchester code-based encoding method could be one that maps bit "1" to the codeword "01" and bit "0" to the codeword "10". Additionally, the reverse encoding method is also possible.

[0212] Here, transitions can always occur in the middle of each codeword, and the Manchester code can be an important self-clocking characteristic. Additionally, the Manchester code can provide an advantage in timing tracking at the receiver by transmitting clock information along with the data. The encoding rule of the Manchester code may be a rule that causes transitions to occur at the boundary of two consecutive bits.

[0213]

[0214] Pulse-interval encoding (PIE)

[0215] For example, the PIE method can transmit binary information based on the duration of the transition interval. For example, the PIE encoding method may map bit "1" to the codeword "1110" and bit "0" to the codeword "10". In addition, the reverse encoding mapping method may also be possible. For example, due to the long high-voltage chip of bit "1", the high-to-low voltage ratio is increased, which can provide stable instantaneous RF energy to the device. The average high-to-low voltage ratio in PIE is 66.7%, and the average high-to-low voltage ratio in Manchester encoding may be 50%, but is not limited thereto.

[0216] In UHF RFID, PIE can be used for line coding. Specifically, PIE line coding in UHF RFID can be a method where Data-0 has a short on duration and Data-1 has a longer on duration. Additionally, in UHF RFID, PIE can utilize an R2D preamble to allow the receiving end to use an on-duration threshold.

[0217] In A-IoT R2D, the aforementioned Manchester coding method may be more efficient than the PIE method. Specifically, in PIE, the length of the data may vary depending on the distribution of bit-0 and bit-1, and accordingly, the transmission time of the data payload may be randomly determined depending on the data bits. In particular, in the case of R2D transmission, when performed together with OFDM-based NR transmission, this may act as interference in terms of time for R2D transmission. Furthermore, as mentioned above, the random determination of transmission time makes it difficult to predict resource utilization (TDM / FDM) and can lead to inefficient wireless transmission. For example, the transmission rate can provide an average data rate of 30kbps (30 bits per 1ms), and accordingly, the data bits may consist of between [20, 40] bits within 1ms depending on data bit-1 or data bit-0.

[0218] On the other hand, a decoder for Manchester coding may not require a hard threshold. That is, the decoder may be used to determine whether the left and right-side envelope per Manchester symbol is 0 or 1. An A-IoT device can switch a single antenna for energy harvesting and communication in the time domain and perform communication based on this. If a PIE is used for an A-IoT device, inefficient terminal implementation may result from differing data lengths as described above, but it is not limited to this.

[0219] FIG. 9 is a diagram illustrating a Manchester encoding and decoding scheme to which the present disclosure may be applied. Referring to FIG. 9, the length of a single Manchester encoded chip may be T, and the chip length for a single bit in the Manchester encoding may be 2T. Here, if a transition from low to high is detected in the middle of a single bit, the corresponding bit may be detected as "0". On the other hand, if a transition from high to low is detected in the middle of a single bit, the corresponding bit may be detected as "1". For example, the transition location may be detected within a time window of a chip length deviation range (e.g., within [-50% +50%]) at a given point in time due to high frequency offset (SFO) and channel influence on the received R2D transmission.

[0220] FIG. 10 is a diagram illustrating a PIE encoding and decoding method to which the present disclosure may be applied. Referring to FIG. 10, PIE encoding and decoding can be performed. In PIE encoding and decoding, the transition interval from low voltage to high voltage can be detected by the device as each information bit starts at high voltage. The length of one PIE low voltage chip can be determined as T, and the length of one PIE high voltage chip for bit "1" can be 3T. Additionally, the length of one PIE high voltage chip for bit "0" can be determined as T, and if the transition from low voltage to high voltage is detected at time +4T, the corresponding bit can be detected as "1". On the other hand, if the transition from low voltage to high voltage is detected at time +2T, the corresponding bit can be detected as "0". The two transition intervals from low voltage to high voltage may be detected by comparing them to a defined time interval threshold, such as the average value of the two interval types, due to high frequency offset (SFO) and channel influence on the received R2D transmission, but are not limited to such embodiments.

[0221]

[0222] R2D BW and Numerology

[0223] FIG. 11 is a diagram illustrating R2D bandwidth and numerology to which the present disclosure may be applied. Referring to FIG. 11, the bandwidth for an A-IoT R2D link is the transmission bandwidth ( , 1110), occupied bandwidth( , 1120) and system bandwidth( It may include , 1130). The above-described bandwidths need to be determined in consideration of the efficient design of the A-IoT system and coexistence with NR or other radio access technologies (RAT). Each bandwidth can be determined from the perspective of the transmitter and the receiver, and can be determined in consideration of limited frequency resources within the A-IoT signal transmission and reception filter.

[0224] Specifically, transmission bandwidth ( , 1110) may be a frequency resource used for A-IoT R2D signal transmission, and occupied bandwidth ( , 1120) may be a frequency resource including A-IoT R2D signal transmission and a guard band. Here, the guard band may be a frequency bandwidth considered for coexistence with other R2D transmissions. System bandwidth ( , 1130) is a frequency resource limited within the RF filter of the receiver and may not be determined separately depending on the R2D transmission method.

[0225] The A-IoT frequency bandwidth needs to be determined considering the efficient operation of the system and coexistence with other wireless technologies, and a guard band and guard subcarrier may be required in consideration of the aforementioned points. Additionally, the A-IoT frequency bandwidth needs to consider coexistence with NR / LTE. For example, the minimum channel bandwidth for the A-IoT R2D can be determined as 1 PRB (physical resource block). The downlink of the A-IoT system needs to maintain subcarrier orthogonality with wireless communication technology (e.g., NR) transmission, and if a frequency guard band is unnecessary, it may be as shown in Fig. 12. On the other hand, if a guard band is required, it may be as shown in Fig. 11. That is, the frequency guard band may mean that the maximum signal bandwidth of the A-IoT R2D link can be as large as the channel bandwidth. Considering the above points, it is necessary to design an A-IoT system that creates minimum requirements for the spectrum, thereby facilitating A-IoT deployment, but this is not limited to the embodiments described. Additionally, possible frequency bandwidth values ​​can be determined as multiple values. Basically, 1 PRB (assuming 15 kHz SCS, 180 kHz) can be used as the minimum bandwidth value, and additionally, at least one of values ​​corresponding to integer multiples of 180 kHz and other frequency bandwidth values ​​may be defined for A-IoT transmission, but is not limited thereto.

[0226] R2D time unit and allocation method

[0227] The R2D link may support an in-band mode operating on the NR frequency band, as described above. Accordingly, the reader may determine the basic time unit as Tc defined in NR, which may be as shown in Equation 3 below. Additionally, as an example, it may be possible to determine a time unit considering other wireless systems, but is not limited to such embodiments.

[0228] [Mathematical Formula 3]

[0229]

[0230]

[0231] The smallest time unit Tc can be utilized for OFDM waveforms as the basic sampling time for R2D transmission based on multiples of that value. Additionally, the minimum time unit for resource allocation in the time domain can be a "chip." The chip duration generated by line coding can be the smallest unit for resource allocation in the time domain, and one chip can be determined as a single OOK symbol time interval.

[0232]

[0233] R2D multiple access

[0234] The receiver of an A-IoT device can fundamentally operate based on RF-ED (envelope detection), and consequently, there may be limitations in simultaneously extracting other R2D signals. Specifically, the A-IoT device can operate by detecting voltage shifts, and there may be limitations in implementing narrow band-pass filtering. Therefore, while there may be limitations in applying multiplexing methods such as OFDMA (orthogonal frequency division multiple access) or FDMA (frequency division multiple access) for the R2D of the A-IoT device, it is not limited to these methods.

[0235] Furthermore, A-IoT devices fundamentally lack the computing power for computational operations such as correlation, and consequently, there may be limitations in performing CDMA (code division multiple access) operations. Therefore, A-IoT R2D transmission can be considered as applying R2D multiple access based on TDMA (time division multiple access), but it is not limited to such embodiments.

[0236] FIG. 13 is a diagram showing PRDCH generation and PDRCH generation to which the present disclosure can be applied.

[0237] Referring to FIG. 13(a), the reader can assign R2D data (transport block, TB) to PRDCH and transmit it to an A-IoT device. Specifically, source bits consisting of N bits { When this is transmitted as a single TB (S1301), the reader can generate a CRC bit based on a CRC bit of length K based on a CRC polynomial of length k and attach it to the data source bit sequence as shown in Equation 4 (S1302).

[0238] [Mathematical Formula 4]

[0239]

[0240]

[0241] After that, of mathematical formula 4 ( ) bits are based on line coding { It can be composed of M bits of} (S1303). Specifically, the data bit sequence after CRC attachment is It consists of bits, and if Manchester coding (line coding) is applied, an M-bit sequence of mathematical formula 6 can be formed.

[0242] [Mathematical Formula 5]

[0243]

[0244] Afterwards, represented by a 2X(N+K) chip through OOK modulation A can be generated as an output block (S1304). Finally, a CP-OFDM or DFT-s-OFDM waveform can be applied to the generated block to generate an R2D waveform. Based on the above, the reader can perform transmission to A-IoT based on the modulated OFDM waveform (S1305). For example, if an M-bit OOK is transmitted within a single OFDM symbol by DFT-s-OFDM, the time of each chip modulated with OOK based on the SCS and M values ​​can be determined by 1 / (M*SCS). Then, the reader can perform resource allocation in the time and frequency domains to finally perform R2D transmission. Here, the transport block size (TBS) can be limited to a size that can be indicated by a 'terminator' signal in the PRDCH postamble.

[0245] Additionally, a D2R grant may not be required as an uplink grant in relation to the PDRCH transmission. For example, an A-IoT device may perform a passive response according to an R2D message. As another example, the D2R grant may be included in an upper-layer message along with other messages delivered by the last PRDCH transmission. Additionally, the scheduling of the PDRCH may be achieved through upper-layer signals (e.g., MAC CE) including the modulation coding scheme (MCS), TBS, chip length, chip iteration count, and line coding code length in the previous PRDCH, but is not limited to such embodiments.

[0246] Referring to FIG. 13(b), the A-IoT device can configure D2R information bits with D2R data (TB) (S1306). Then, CRC bits can be attached to the D2R information bits, and the CRC length may not be zero (S1307). Then, coding is performed on the D2R information bits with attached CRC (S1308), and after modulation is applied (S1309), PDRCH can be generated (S1310). Here, coding can be performed in different forms depending on line coding and whether FEC is applied, and modulation can also be performed based on the above description, but may not be limited to a specific form.

[0247] Additionally, for example, a preamble may be configured in the R2D transmitted from the reader to the A-IoT device. For example, the R2D preamble may indicate the start of the R2D transmission. Additionally, the R2D preamble may be transmitted from the reader to the device for timing indication. For example, as an A-IoT device type, Device 1 type (i.e., a ~1us peak power consumption device) cannot use sequence correlation operations, and consequently, unlike existing NR / LTE terminals, it cannot acquire timing or perform signal detection. The A-IoT device can determine the start of the R2D transmission and the chip duration of the R2D transmission by detecting extremely low power energy and transition edges based on envelope detection (ED) through the preamble signal.

[0248] As a more specific example, the R2D preamble may be composed of at least two parts for the R2D timing acquisition signal. Each of the two parts may be a start-indicator part and a clock-acquisition part. The start-indicator part may be located immediately before the clock-acquisition part in terms of time and may be transmitted as part of the preamble. The start-indicator part may indicate at least the start time of the R2D transmission. Additionally, the clock-acquisition part may be utilized for the purpose of chip synchronization of the R2D channel transmission (data / control information transmission channel, PRDCH) located immediately after the preamble.

[0249] In addition, the D2R waveform can be a single-carrier waveform. For example, OFDMA may not be suitable for A-IoT devices due to its high processing complexity and high timing error (large SFO, Time alignment errors may occur depending on ), so it may not be suitable for D2R waveforms.

[0250] In addition, D2R modulation needs to be supported to achieve a target device power consumption of approximately 1 μW, considering that D2R transmission is a backscatter modulation-based transmission. Accordingly, the aforementioned OOK, binary PSK (phase shift keying), or binary FSK (frequency shift keying) may be used, but are not limited to such embodiments. For example, OOK can guarantee the simplest implementation and lowest power consumption. On the other hand, binary PSK may require more complex switching circuitry to adjust the phase of the reflected RF carrier waveform, but may have smaller reflection losses for backscatter modulation. Additionally, binary FSK can be implemented through frequency-dependent on / off switching similar to OOK. Binary FSK may require twice the clock speed of OOK for the same maximum bandwidth at the same data rate, which may increase power consumption, but is not limited thereto.

[0251] Additionally, D2R line coding can be configured to prevent the transmission of consecutive bits "1" or "0". For example, if data remains at 0 for an extended period, power may not be supplied. D2R line coding needs to provide timing information embedded in the data so that the receiver can synchronize with the transmitter, and it can shift the spectrum of the D2R signal away from the carrier wave in response to a reflected signal. Furthermore, D2R line coding can achieve different frequency shifts for the D2R signal by adjusting the length of the line code and the chip length to support FDMA. In other words, line coding can play an important role for the simple implementation of FDMA (frequency division multiple access) for D2R transmission, but is not limited thereto. For example, D2R line coding can be performed based on at least one of Manchester encoding, FM0 encoding, Miller encoding, and no line coding. Here, Miller code and FM0 code can be used in the tag-to-reader link in an RFID system. FM0 and Miller codes can be used for self-clock coding, and the reader can synchronize with FM0 and Miller codes by observing code pattern transitions and estimate and overcome timing errors / variations during backscatter communication. On the other hand, no-line coding can be used in coherent receivers as a receiver option for BPSK (binary phase shift keying) modulation and BPSK demodulation, but is not limited thereto.

[0252] Additionally, FIG. 14 may be a D2R bandwidth to which the present disclosure can be applied. For example, the D2R bandwidth is a transmission bandwidth (B tx,D2R 1411,1412), occupied bandwidth (B occ,D2R , 1421, 1422) and system bandwidth (B sys,D2RIt can be configured based on , 1430). The transmission bandwidth (1411, 1412) may be a frequency resource scheduled by a reader for D2R transmission from one A-IoT device, and the occupied bandwidth (1421, 1422) may be an A-IoT internal guard band (B potentially associated with the transmission bandwidth) guard,D2R It may be a bandwidth including ). System bandwidth (1430) may refer to frequency resources that a reader can schedule for D2R transmission to support frequency division multiplexing (FDM) between other devices. Additionally, a guard band may be configured for coexistence between A-IoT D2R and NR / LTE, but is not limited to a specific form. Here, each bandwidth may satisfy the following Equation 6.

[0253] [Mathematical Formula 6]

[0254]

[0255]

[0256] FIG. 15 is a diagram showing the basic frame structure of PRDCH and PDRCH to which the present disclosure may be applied. In an A-IoT system, maintaining synchronization between a reader and an A-IoT device may not be possible. The A-IoT device may be a device assumed to have very low capability and low power consumption. Therefore, synchronization between the reader and the A-IoT device is subject to timing errors caused by the sampling frequency offset (SFO) (e.g. It may not be maintained due to a 10% timing error (parts per million). For example, if a timing error of 1ms occurs every 10ms between the reader and the A-IoT device, the reader may need to continuously transmit a synchronization signal to the A-IoT device every 1ms, and the resulting system overhead can be very large. Therefore, to practically utilize the A-IoT system, the A-IoT system may fundamentally operate as an asynchronous communication system. That is, A-IoT devices may not be able to perform slot alignment in the time domain. Accordingly, when data transmission and reception occur between the reader and the A-IoT device, a timing acquisition signal may be used between them, and a method for this may be required. For example, in R2D, the R2D preamble can perform this role. Additionally, in D2R, the D2R preamble may perform this role, but it is not limited to this. For example, as a timing acquisition signal, the timing acquisition operation may be performed using at least one of the following: not only the preamble, but also the midamble, postamble, periodic sync signal, control information / fields, and guard period, but it is not limited to a specific form.

[0257] Here, the basic frame structure of PRDCH and PDRCH may be as shown in FIG. 15. The basic frame may include a preamble (1510) and a header (1520) at the very front for synchronization purposes and for transmitting control information. In FIG. 15, a start indicator (1511) may indicate the start time of PRDCH / PDRCH transmission. For example, the start indicator (1511) may serve a role similar to a delimiter in UHF RFID (ultra high frequency radio frequency identification), but is not limited thereto. The start indicator (1511) may allow the receiving node to quickly determine at what point the corresponding channel transmission occurs. For the above, the start indicator (1511) may be indicated by a specific voltage pattern (e.g., low-voltage) or other indication methods, and the transmission may be performed by the transmitting node. The clock acquisition (1512) portion following the start indicator can be used to provide synchronization information for synchronizing the chip of the physical channel part using a square wave. The transmission length of the clock acquisition (1512) can be determined in a proportional form to the chip length used for the subsequent data / control transmission portion. Additionally, information regarding the clock reference can be provided based on information regarding the chip length. The receiving node can identify the interval between the rising or falling edge through the clock acquisition (1512) and acquire information about the chip based on this.

[0258] FIG. 16 is a diagram showing block level, bit level type 1 and bit level type 2 to which the present disclosure can be applied.

[0259] Referring to FIG. 16(a), Direct-to-Reader (D2R) detection via Block Level Repetition can obtain both Combining Gain and Time Diversity Gain by utilizing block repetition. Additionally, if a block is successfully decoded, the reader can terminate the reception in advance before the reception operation following all block level repetitions. Block level repetition can provide a performance gain of approximately 2.5 dB compared to bit level type 2 due to the additional time diversity gain for decoding combination.

[0260] Referring to FIG. 16(b), in bit-level type 1, the repeated data bits are decoded after the Forward Error Correction (FEC) detection, so the digital data bits cannot utilize the combined gain. On the other hand, referring to FIG. 16(c), in bit-level type 2, bit repetition is performed after the FEC at the transmitter, so at the receiver, each bit can have a Log-Likelihood Ratio (LLR), and since the LLR is combined and provided as the input for FEC decoding, it can provide better performance than bit-level type 1. However, the repetition operation may not be limited as described above.

[0261] FIG. 17 is a diagram illustrating the overall AS (Access Stratum) procedure between an A-IoT device and a reader to which the present disclosure applies.

[0262] Referring to FIG. 17, an overall AS (Access Stratum) procedure for managing wireless resources and transmitting data in an A-IoT system can be considered. Specifically, based on a service request from a device (1710), a reader (1720) may transmit a paging message indicating the device(s) that require a response (Step A). ​​Then, the device (1710) may transmit D2R data (including Device ID). Specifically, the triggered device(s) may transmit D2R data to the reader after performing an A-IoT random access procedure. Alternatively, the triggered device(s) may perform D2R data transmission without an A-IoT random access procedure. That is, a random access procedure may be required for the triggered device(s) to perform D2R transmission, but it may not be essential. (Step B) Afterwards, the reader (1720) can perform possible R2D data transmission (e.g., sending the command). (Step C1) Additionally, the device(s) can perform possible D2R data transmission (e.g., the corresponding response to the command). (Step C2) Through the above description, the device (1710) and the reader (1720) within the A-IoT system can perform data exchange. The above-described AS procedure can be supported in indoor inventory and indoor and command use cases as follows.

[0263] - Inventory-only case: Support along with Step A and Step B procedures

[0264] - For Inventory and command: Supported along with Step A, Step B, Step C1, and Step C2 procedures

[0265] (In the case of inventory and command, this does not mean that the paging message must always include both inventory and command.)

[0266] - Command-only case:

[0267] □ Support with Step A, Step B, Step C1, and Step C2 procedures

[0268] Other procedural methods to support the above-mentioned cases may be as follows:

[0269] o Step A': Based on the service request, the reader sends a paging message containing a command to the device.

[0270] o Step C2: Transmit D2R data if possible (e.g., response to Command and Device ID), performed with or without the Random access procedure.

[0271]

[0272] For example, the reader may obtain information about the A-IoT service type (e.g., inventory, command) from the CN (core network). Additionally, the reader may need to determine whether information about the command type (e.g., read / write / disable) is useful. Furthermore, the reader may need to determine whether it is necessary to be aware in advance that a D2R response is expected on the D2R link. In the aforementioned case, the reader may need to determine how to determine the D2R message size and whether the reader can obtain information about the expected D2R message size. Additionally, it may be necessary to determine whether the aforementioned command type is explicitly specified or can be determined based on the expected D2R message size. Furthermore, information about whether the service targets one or more A-IoT devices and information about the approximate number of A-IoT devices targeted by the service may be required.

[0273]

[0274] A-IoT Random Access Procedure

[0275] A-IoT can support combinations of the following use cases, which may be as shown in Table 7 above. In addition, from the perspective of wireless access technology, the above use cases can be handled through the following basic procedures.

[0276] ● Basic Procedures for A-IoT Use Cases:

[0277] □ Step A: Upon a service request, the Reader sends an Initial Trigger Message (e.g., A-IoT Paging Message) to the device. The aforementioned Initial Trigger Message requests a response from the device that received the message.

[0278] □ Step B: Based on the initial trigger message described above, the triggered device(s) may perform a procedure similar to contention-based random access. Of course, if random access is not required (e.g., in the case of contention-free access), the contention-based random access procedure may not be performed. Here, the contention-based random access may be performed based on 4 steps or 2 steps.

[0279] □ Step C: The device(s) or group(s) that have performed contention resolution through Step B can perform data communication with the leader through physical layer channel transmission and reception on the R2D and D2R links.

[0280] The aforementioned use cases can be supported by commonly utilizing the same procedure consisting of the steps described above.

[0281] Based on the basic procedure described above, the specific procedure for an A-IoT use case may be as follows.

[0282]

[0283] ● 4-step competition-based A-IoT random access procedure:

[0284] FIG. 18 is a diagram illustrating a 4-step based A-IoT random access procedure to which the present disclosure can be applied.

[0285] □ MSG 0: A Reader (hereinafter, Reader, 1820) can transmit an A-IoT Paging Message to one or more devices (A-IoT devices, 1810). The Paging Message can be transmitted via R2D from the Reader (1820) to the device (1810) to trigger a 4-step or 2-step based random access procedure to perform an Inventory Procedure. Based on service requests transmitted from the CN (Core Network) for other use cases (e.g., Inventory+Command, Command) as well as the aforementioned Inventory, the Reader (1820) can transmit the aforementioned A-IoT Paging Message (Trigger Msg, MSG 0) to the device(s) (1810) or a group of devices. Devices (1810) located near the Reader that receive the Trigger Message can determine whether to respond based on the message. All devices (1810) surrounding the reader may not respond to the receipt of the corresponding trigger message. Consequently, only the device(s) or device group that meet the selection criteria for determining whether to respond provided in the trigger message may subsequently perform the transmission of A-IoT Msg 1 (Random ID). Specifically, the reader may receive from the CN various information (e.g., information related to device masking / filtering / group identification) necessary for the reader's surrounding device(s) to determine whether to respond to the A-IoT paging message (trigger message). The reader (1820) may include control information based on the aforementioned information received from the CN within the A-IoT paging message and transmit it to the surrounding device(s) via PRDCH transmission. The aforementioned control information (e.g.Selection criteria information, D2R (PDRCH) scheduling / resource allocation / timing information, and related control and parameter information requiring 4-step or 2-step random access execution, etc., may be included and transmitted within the Msg 0 A-IoT paging message. Here, devices (or groups of devices) that respond upon receiving the message may be referred to as target devices or target device groups, but are not limited thereto.

[0286] The aforementioned selection criteria information may include a device ID (or device group ID) or equivalent device-related identification information. Additionally, the aforementioned masking / filtering / group-related information may be additionally included and transmitted along with the device ID. Such information may be utilized based on data information stored in the device memory or as predetermined information. Furthermore, A-IoT paging message transmission may be transmitted via the physical channel PRDCH through the R2D link.

[0287] □ MSG 1: A device (1810) may transmit at least one ID value to a reader (1820) via D2R transmission. The ID value may be a random ID value generated randomly by the device or generated based on a device ID. At least the random ID value may be included in the D2R (PDRCH) and transmitted so that the reader can recognize that devices with different ID values ​​are performing MSG 1 transmission on the same time / frequency resource. Here, a method by a random access procedure and a method without a random access procedure may be considered.

[0288] ● Opt 1. Method by random access procedure

[0289] - The target device performing random access performs the random access procedure to the reader.

[0290] ● Opt 2. A method performed without a random access procedure

[0291] - It can be performed without a random access procedure to minimize connection delay. As a specific example, if only one device is triggered by the reader, the corresponding random access procedure can be skipped.

[0292] □ MSG 2: When the reader (1820) accurately detects the corresponding random ID value through the reception of Msg 1 (PDRCH), the detected random ID can transmit Msg 2 for the response via PRDCH. Of course, additional control information (e.g., Msg 3 scheduling / resource allocation / timing information, Msg 3 control information for random access procedures, etc.) can also be included in the transmission of Msg 2 along with the aforementioned random ID value and transmitted from the reader (1820) to the device (1810).

[0293] □ MSG 3: If the device (1810) successfully receives the same random ID in Msg 2, the device may be considered for contention resolution. Subsequently, the device (1810) may transmit Msg 3, which includes upper layer related data control information different from the device ID, via PDRCH.

[0294] □ MSG 4: Msg 4 does not fundamentally need to be transmitted for the purpose of random access contention resolution. Since this purpose has already been achieved in the transmission and reception of Msg 2 and Msg 3, the transmission of Msg 4 may be performed to handle the case where the reader failed to receive the previous Msg 3. That is, if the reader expects to receive Msg 3 (PDRCH) within a certain time window period but fails to receive it, the reader (1820) may transmit Msg 4 to the device / device group to instruct and perform whether to retransmit Msg 3 or other subsequent actions.

[0295]

[0296] ● 2-step competition-based A-IoT random access procedure:

[0297] FIG. 19 is a diagram illustrating a 2-step based A-IoT random access procedure to which the present disclosure can be applied.

[0298] Referring to FIG. 19, the 2-step based A-IoT random access procedure can minimize transmission and reception delays by further simplifying the aforementioned 4-step contention-based A-IoT random access procedure. The 2-step contention-based A-IoT random access procedure can be considered similar to existing wireless communication systems (e.g., NR) in an A-IoT system. The characteristics of MSG 1 / MSG 2 required for the A-IoT 2-step random access procedure may be as follows.

[0299] □ MSG 1: Similar to 4-step random access, the transmission of MSG 1 for a 2-step random access procedure can be performed from a device / device group (1910) to a reader (1920) by receiving a paging message (triggering message, MSG0). The device (1910) can transmit MSG 1, which includes at least one of a device ID, other upper layer data, and an additional random ID, to the reader via PDRCH.

[0300] □ MSG 2: The reader (1920) can transmit device-related information (e.g., device ID) and related response information received from MSG 1 to the device / device group (1910) via MSG 2. Contention resolution can be performed through the transmission of MSG 2.

[0301]

[0302] The following describes the basic transmission and reception timing relationship of at least one of R2D (PRDCH) and D2R (PDRCH) transmissions on an A-IoT system. Since A-IoT systems fundamentally consider asynchronous synchronization (i.e., data transmission and reception between a reader and a device is performed based on requests and responses), the transmission and reception timing between readers and devices may not always be performed based on consistent timing. Here, as mentioned above, due to physical / hardware limitations, A-IoT devices 10% ( It can be assumed that timing errors / errors at the level of ppm occur. For example, even if the reader and the device are time-synchronized with each other, a timing error of about 100ms may occur after 1 second. Therefore, various synchronization methods can be considered to minimize the aforementioned error.

[0303] Considering the aforementioned wireless environment, system, and service characteristics, it may be necessary to define a timing interval between R2D and / or D2R transmissions and receptions. The definition of the timing interval may consider the timing between an R2D (repetitive) transmission and its corresponding immediately next D2R (repetitive) transmission, conversely, the timing interval between a D2R (repetitive) transmission and its corresponding immediately next R2D (repetitive) transmission, the timing between consecutive R2D transmissions, the timing between consecutive D2R transmissions, the timing between R2D / D2R repetitive transmissions, and other timings.

[0304] For example, Table 10 below may show the timing relationships between R2D transmission and D2R transmission that can be considered, but is not limited thereto.

[0305] [Table 10]

[0306]

[0307]

[0308] The minimum time for R2D and D2R transmissions can be defined by the parameters described above. Here, in order to perform associated or consecutive transmissions after a single transmission, it is necessary to determine a timing interval that reflects the minimum processing time and the processing time of the reception operation for the previous transmission, and a definition for this may be required. Additionally, a time that reflects the minimum preparation time required to prepare for the next transmission (e.g., a response) based on the previous reception can be defined to determine the transmission timing interval.

[0309] FIG. 20 is a diagram showing the minimum and maximum time required between R2D / D2R transmission and reception that can be applied to the present disclosure.

[0310] Referring to FIG. 20, the times for the A-IoT timing relationship can be defined by considering the processing time of the reader (2010) or device(s) (2020, 2030, 2040). Here, the minimum time may be information necessary to determine the requirement that a transmission must be performed at least after the minimum time following the reception of a previous transmission between all devices (2020, 2030, 2040) and the reader (2010). Additionally, the maximum time may be the maximum transmission time possible to perform the next transmission after receiving the previous transmission. Here, the maximum time information may be a requirement regarding how long the next action must be performed. Additionally, the maximum time information may be a time window where receiving a specific physical channel / signal is expected from the perspective of the receiving side. For example, the reader (2010) performs an R2D transmission, and the device that received the R2D transmission may subsequently perform a D2R transmission corresponding to the reception of the R2D. In the aforementioned case, the device may need to provide requirements or guidelines regarding from what point in time to what point in time D2R transmission should be performed (or from what point in time the reader should expect D2R reception). Without the aforementioned information, the reader may make incorrect judgments and perform incorrect actions regarding D2R reception. Furthermore, through the above, the transmitting device can define a clear timeline regarding when to perform processing for D2R transmission, thereby clarifying the operation for the subsequent transmission and reception procedure. Therefore, it is necessary to define a clear time window regarding the operation of the reader and device(s), and to ensure that the desired signal is transmitted and received within that window. For example, if the transmission or reception of the desired signal cannot be performed within the time window, the operation can be clarified even if the immediately following procedure and action can be performed. Additionally, the aforementioned maximum time is related to the command type (e.g., DT or DO-DTT) and other use cases (e.g.,It may be defined with one or more values ​​to cover different devices (e.g., devices with different capabilities) by considering at least one of Inventory or Command. If the maximum time is defined with a single maximum value, the largest value among the maximum values ​​for each type, use case, and different device may be determined. Alternatively, if the maximum time is defined with one or more values, different maximum time values ​​may be defined and used for each type, use case, and different device.

[0311] This disclosure describes at what point in time the R2D and D2R transmissions are to be performed, based on the minimum / maximum time between an R2D transmission and its associated D2R transmission or between a D2R transmission and its associated R2D transmission, and the minimum / maximum time between consecutive R2D / D2R transmissions. Scenarios may be considered in which the R2D and D2R transmissions are transmitted aligned with OFDM (orthogonal frequency division multiplexing) symbol boundaries and / or slot boundaries, along with basic resource allocation methods (i.e., chip or bit symbol, time-domain frame structure (TTI)-based resource allocation). However, in an A-IoT standalone scenario, consideration of existing wireless communication system (e.g., NR) time boundaries may not be necessary. In the above-described cases, the A-IoT transmission may not be performed aligned with OFDM symbol, slot, frame, and other time-related boundaries.

[0312] The following describes the procedures for transmitting and receiving data between a reader and multiple devices within an Ambient IoT (A-IoT) system. An A-IoT system may differ from existing wireless systems (e.g., LTE / NR systems) in at least one of the following: devices, wireless network scenarios, cell topology, and wireless environment. For example, an A-IoT random access procedure may be triggered to peripheral devices for the transmission of upper-layer data (e.g., inventory, command) generated by the reader / CN (Core Network). In the above case, the peripheral devices may determine whether to respond to the random access response based on criteria and related parameters required for the random access response provided (or transmitted) by the reader. Here, if the above criteria are satisfied, the target devices may perform a random access procedure (i.e., transmit A-IoT Msg 1 (D2R)) to the reader. Subsequently, R2D and D2R data transmission and reception can be performed based on identification information (e.g., device ID, random ID) shared between the reader and the device through a random access procedure. The following describes a method for performing iterative D2R (PDRCH) transmission applicable within an A-IoT random access procedure or a general A-IoT data transmission and reception procedure, as well as the corresponding procedure.

[0313] In this disclosure, only the application of iterative transmission for D2R transmission may be considered for the purpose of minimizing coverage mismatch between the R2D link (reader to device) and the D2R link (device to reader). Specifically, generally, the maximum value for transmit power and the availability of high transmit power may be higher for the reader than for the device. Therefore, the R2D link may not be an issue in terms of coverage. On the other hand, A-IoT devices with low power may have limited D2R transmission power due to RF (radio frequency) and capability constraints of the equipment, and the use of wireless resources may also be limited. Therefore, D2R link coverage may be smaller than R2D coverage, and accordingly, the application of iterative transmission over the D2R link (i.e., PDRCH transmission) in an A-IoT system may be considered, and this is described below.

[0314] Methods and procedures can be considered to satisfy D2R coverage expansion, efficient wireless resource utilization, and optimized D2R transmission and reception performance based on features transmitted to respond to R2D transmissions based on D2R (PDRCH) iterative transmission. Here, assumptions regarding the A-IoT device for the 'D2R iterative transmission method' may be as follows, but are not limited thereto.

[0315] - A-IoT devices can perform data communication and RF energy harvesting operations using a single antenna.

[0316] - The D2R iterative transfer type corresponds to at least one of the following types:

[0317] o Block level: After attaching the CRC, all bits received from the physical layer and / or upper layers are in the form of repeating R blocks.

[0318] o Bit level type 1: After attaching CRC, each bit is repeated R bits

[0319] o Bit level type 2: After CRC attachment and FEC, each bit is repeated R bits

[0320] o Chip level: After line coding or square wave modulation, each chip is repeated R times (equivalent to expanding each chip segment by R chip segments)

[0321]

[0322] When D2R repetition transmission is performed, the repetition transmission may be performed based on at least one of the aforementioned block level, bit level 1, bit level 2, and chip level units. In particular, the present disclosure may consider at least 'PDRCH-level repetition transmission' as the aforementioned block level repetition transmission. That is, it may be a case where both combined gain and time diversity gain are obtained through one or more PDRCH (D2R) repetition transmissions, but is not limited thereto. In other words, with respect to repetition transmission, not only the block level but also the bit level and chip level may be applicable.

[0323] In this disclosure, the description is based on the case where R2D transmission is always performed from a reader to a device (or group of devices) or an unspecified plurality of devices prior to D2R transmission. Accordingly, D2R transmission for A-IoT upper layer data transmission may be performed at least based on control information indicated in the corresponding previous R2D transmission. Furthermore, the above-described repeated transmission may also be applied in the random access procedure performed for the wireless access procedure of an A-IoT device, specifically in the transmission of Msg 1 corresponding to the paging message (R2D) from the reader and the transmission of Msg 3 (D2R) corresponding to the transmission of Msg 2 (R2D). However, it may not be limited thereto.

[0324] An A-IoT Random Access (RA) procedure may be used for A-IoT devices to connect to a network for data transmission. Here, the RA procedure may involve triggering A-IoT network access by a leader for a single A-IoT device (or a group of devices) or all devices within the leader's coverage. Additionally, 'Slotted-ALOHA' may be considered as the underlying technique for wireless resource allocation for the RA procedure. Here, an access occasion (AO) may be a time-frequency resource used by a device for D2R (or A-IoT Msg 1) transmission. For example, a set of AOs for different A-IoT devices may be scheduled by an R2D message. Furthermore, an AO may be a resource containing an actual physical resource area used for actual D2R (e.g., Msg 1 or Msg 3 transmission) transmission. For example, D2R (PDRCH) transmissions on a single AO can be transmitted within an AO scheduled according to the actual payload size. As a specific example, if Ts is the AO time interval and Tm is the Msg 1 transmission time interval, each time resource interval (i.e., Ts, Tm) can be set under the condition that 'Ts >= Tm'. Such AO time intervals can serve as a time gap to minimize interference caused by SFO (Sampling Frequency Offset) between D2Rs transmitted on neighboring AOs, and provide the advantage of facilitating the actual physical transmission start time and resource allocation method.

[0325] Additionally, the time-frequency resources through which the device performs D2R transmission may be referred to as D2R transmission resources and are not limited to the aforementioned AO. Specifically, the AO resources may be utilized for the transmission of Msg 1 in the aforementioned RACH procedure. That is, in contention-based random access (CBRA), the aforementioned D2R transmission resources may correspond to AO resources. Furthermore, when data transmission is performed via D2R transmission, the D2R transmission resources may be resources determined by D2R scheduling information received by the device from the reader. In other words, the aforementioned D2R transmission resources may refer to resources used by the device for D2R transmission and may include both the aforementioned AO and scheduling resources based on D2R scheduling information. Alternatively, the D2R transmission resources may include additional resources related to D2R transmission and are not limited to a specific form. For the convenience of explanation, the following description is based on AO resources and AO resource sets, but this may also apply to D2R transmission resources and D2R transmission resource sets, and it may be obvious that they are interpreted as D2R transmission resources.

[0326] In this disclosure, a resource allocation method is described using definitions for various time intervals. The basic time used here may be in chip units. Of course, various other time units (e.g., ms units, slots, subframes, payload (TB, bits), time for transmitting one bit (number of one or more chips), R2D / D2R transmission slots, Tc defined in NR specifications, etc.) may also be considered and are not limited to a specific form. Furthermore, in this disclosure, time domain-related control information and resource information for D2R repetitive transmission may be predefined or indicated by a reader (by R2D paging), but are not limited thereto.

[0327] FIG. 21 is a diagram showing a general framework of slotted-ALOHA for an A-IoT random access procedure that can be applied to the present disclosure.

[0328] Referring to FIG. 21, the device can determine whether it is necessary to send a response to the corresponding reader based on the reception of A-IoT paging. If the device determines that it is necessary to send a response to the corresponding reader based on the reception of A-IoT paging, the device may perform a random access procedure. Alternatively, the device may send a response to the reader without performing a random access procedure, as described above.

[0329] For example, in a random access procedure, the random access type (i.e., contention-free or contention-based) and the access occasion / resource may be specified (Step 1). That is, an A-IoT device may receive information regarding the random access type (contention-based or contention-free random access) from an A-IoT paging message transmitted by a reader. The reader may provide the device with information regarding the contention-free random access type or the contention-based random access type, along with configuration information associated with each type. Here, the aforementioned configuration information may be specified to the device explicitly or implicitly.

[0330] Additionally, specific methods for performing repeated PDRCH (D2R) transmissions may be further provided from the reader to the device. Specifically, an R2D (PRDCH) transmission may always precede the D2R (PDRCH) transmission by the reader, as described above. Here, regarding the D2R transmission corresponding to Msg 1 transmission within the A-IoT random access procedure, an A-IoT paging message that triggers the random access procedure before the D2R transmission may be transmitted from the reader to the device(s) (or device group(s)) via the R2D link. Likewise, in the case of general upper-layer data transmissions (e.g., Inventory, command), the reader performs the transmission of the corresponding upper-layer data to the device via the R2D link, and the device transmits the response information to the reader via the D2R link. The device may not always require the transmission of response information (D2R) for a previous R2D reception, and the device may decide whether to transmit the response information or be instructed by the reader based on the use case or data content.

[0331] Here, operation and configuration information related to D2R repetitive transmission can be provided from the reader to the device. Specifically, control information transmitted from the reader to the device can be delivered to the device by being included in an A-IoT paging message (R2D) through at least one of upper layer signaling and L1 R2D control signaling. The aforementioned A-IoT paging functionality can perform operations to transmit paging messages to devices that require response transmission. That is, the A-IoT paging functionality can transmit paging messages through the PRDCH physical channel on the R2D link.

[0332] FIG. 22 is a diagram illustrating a control information structure for D2R transmission within a paging message applicable to the present disclosure. Referring to FIG. 22, control information for D2R transmission may be included within the paging message. For example, FIG. 22(a) may be a case where the paging message is transmitted for only one device (or one group of devices). On the other hand, FIG. 22(b) may be a control information structure corresponding to a plurality of IDs for a plurality of devices, but is not limited thereto. Here, the paging message may include information related to D2R repetitive transmission, and the device may perform D2R repetitive transmission based on the received paging message.

[0333] Additionally, the aforementioned paging message may include an identifier (ID) to identify a device (or a group of devices) within the trigger message. Here, the identifier included in the paging message may include a single ID for a single A-IoT device. As another example, the identifier included in the paging message may include a single ID for a single A-IoT device group associated with multiple devices. As yet another example, the identifier included in the paging message may not include any ID. That is, a message requiring a response from all devices receiving the paging message may be delivered as a paging message. As yet another example, the identifier included in the paging message may include multiple IDs of multiple A-IoT devices. That is, multiple IDs of A-IoT devices may be supported within the paging message. Here, the transmission described above may be possible depending on the multiplexing design of the paging message and the transport block (TB) size, but it is not limited to a specific form.

[0334] Depending on the paging message characteristics described above, information related to D2R scheduling and recurring transmission within the paging message may be specific to a single A-IoT device or to multiple devices associated with a group of A-IoT devices. Alternatively, information related to D2R scheduling and recurring transmission may be applied to all devices that receive the paging message, and is not limited to a specific form. For example, one can consider a case where multiple IDs of multiple A-IoT devices are included within the paging message, and control information for independent D2R (recurring) transmission is provided for each device; for this purpose, an identifier may be used.

[0335] For example, referring to FIG. 22, in the case of a single device ID, a single group ID, or multiple IDs for multiple devices, at least control information required for D2R (repeated) transmission may be included in each paging message for each device or group referred to by each ID. For example, in the case of multiple devices (Fig. 22(b)), some control information may be applied commonly, thereby reducing the overhead within the message. The control information in FIG. 22 is information that can generally be considered, and other additional information may be included, and is not limited to FIG. 22.

[0336] For example, A-IoT D2R repetition may be performed based on A-IoT D2R repetition transmission control information instructed by a predetermined method or a reader. Based on the proposed transmission time interval and timing within the D2R transmission time interval (or, A-IoT Msg 1 transmission time interval), D2R transmission resources (or AO resources) and related configuration information may be instructed to the device via an A-IoT paging message. Alternatively, D2R transmission resources (or AO resources) and related configuration information may be determined in advance based on the proposed transmission time interval and timing within the D2R message transmission time interval (or, A-IoT Msg 1 transmission time interval).

[0337] When configuration information related to D2R repetitive transmission is provided to the device, at least one of the following information may be explicitly or implicitly instructed to the device, and based thereon, the device may determine whether to perform repetitive transmission. As a specific example, whether to re-transmit and the method of re-transmitting A-IoT Msg 1 and A-IoT Msg 3 (D2R, PDRCH) transmissions may be instructed from the reader to the device via an A-IoT paging message. In the above case, additional configuration information related to at least one of Msg 1 and Msg 3 may be set in common with the following information. Alternatively, additional configuration information related to at least one of Msg 1 and Msg 3 may be set independently of the following information and is not limited to a specific form.

[0338] - Whether to perform repeated transmissions (enable or disable): Can be explicitly set. Alternatively, it may be implicitly indicated based on whether the following resource setting information is provided.

[0339] o X time domain resources (number of available AOs): X may be the number of time domain resources available for D2R iterative transmission, and refer to Fig. 23 below. For example, the maximum value of X may be set or determined in advance by taking into account the influence on at least one of device implementation complexity, device power consumption, resource consumption efficiency affected by SFO, and inventory latency.

[0340] o Size of the AO time interval within the time domain ( ) : It can be set considering the impact of 'Guard Time - SFO (Sampling Frequency Offset)' and resource efficiency. This may be the time required to avoid overlap between previous D2R transmissions and current D2R transmissions between terminals or between AO intervals, and the guard time may not be explicitly defined but may be determined to be included within the AO time interval by reflecting it when determining the size of the AO time interval.

[0341] o K Frequency Domain Resources (Number of available AOs in the frequency domain): K represents the number of available frequency domain resources at a given time. Guard bands (frequency gaps) between AOs in the frequency domain may be set (or defined) to handle the effects of SFOs.

[0342] o Repeat transmission level (e.g., number of repeat transmissions) or number of repeat transmission resources (N) (e.g., N <= X): X may be the total number of time domain resources for D2R transmission. If N=1, one transmission is performed. On the other hand, if N is greater than 1, it may mean that repeat transmissions are performed. If N is greater than 1, N transmissions (or AOs) for repeat transmissions may be allocated consecutively or discontinuously. Generally, considering the synchronization operation and power consumption of the device, it may be preferred to allocate N transmissions (or AOs) consecutively, but is not limited thereto, and discontinuous allocation of transmissions (or AOs) may also be possible.

[0343] o Information regarding D2R transmission timing

[0344]

[0345] FIG. 23 is a diagram illustrating the repeated transmission of A-IoT Msg1 (D2R) after receiving a paging message applicable to the present disclosure. Referring to FIG. 23, the device may receive a paging message and perform repeated transmission for D2R (or A-IoT Msg1, 2310). For example, in FIG. 23, X=6 and K may be 4, but this is merely an example for convenience of explanation and is not limited thereto. In FIG. 23, through the paging message (R2D), the reader may indicate to the terminal the resources (or AO)(s) available for the repeated transmission of D2R (or A-IoT Msg1). The indicating method may indicate the number of transmission resources (or the number of AOs) based on at least one of the available X time domain resources and K frequency domain resources as described above. Here, the resources (or AOs) corresponding to X and K are within the transmission time described above based on the time of receiving R2D. It may exist in. For example, resources (or AOs) may be allocated in the time domain when X is 1 or when X is greater than 1. Additionally, resources in the frequency domain may be configured in addition to resources in the time domain. For example, configurations for both the case of K=0 (No FDM (frequency division multiplexing)) and the case of K>=1 (FDM) may be possible.

[0346] In FIG. 23, the case may be X=6, K=4, and N=3, but this is for convenience of explanation only and is not limited thereto. Here, the minimum time after the transmission of the A-IoT paging message. Maximum time from then on D2R transmission may be possible up to this point. For example, the maximum time during which the device can repeatedly transmit the corresponding D2R based on R2D reception is It can be limited through. The aforementioned time information It can be determined in advance or instructed to the device via a paging message (R2D). In addition, as a time interval for a single AO Time may be determined, and time interval information for each AO may be predefined or instructed to the device through the transmission of the reader's R2D (e.g., paging message, R2D upper layer data). Based on the above, it may be necessary to determine which resource (AO) among the resources (AOs) on 'different times' or 'different times and frequencies (if frequency resources are set)' can be allocated a repetitive transmission resource, and this is described below.

[0347] For example, If the value is defined, Repeated transmission may be possible from different time domain resources within my X time domain resource. D2R transmission timing indicated by R2D control information transmission, unlike what was described above. can be indicated based on control information within the R2D transmission. Here, It may be. For example, repeated transmissions may be performed N times as indicated, from a starting resource (AO) corresponding to the indicated D2R transmission timing to a resource (AO) available within the X time domain, but are not limited thereto.

[0348] FIG. 24 is a diagram showing an AO selection considering the minimum time between D2R iterative transmissions that can be applied to the present disclosure.

[0349] Referring to FIG. 24, the selection of the next AO after the start AO selected for repetitive transmission is the minimum time to prepare for D2R repetitive transmission by at least the same device. ...can be considered. That is, at least the minimum time after the D2R(PDRCH) transmission within the AO for the start of the first transmission has ended. Afterwards, you can select a resource for repeated transmission starting from the next AO.

[0350] FIG. 24 may be an AO selection method considering the minimum processing time between D2R iterative transmissions. As described above, the D2R Tx time length proportional to the D2R payload size ( ) and AO time interval( Considering ), a transmission structure such as that shown in Fig. 24 can appear in the time domain. When selecting AOs required for D2R repetitive transmission, continuous AO transmission resources can be selected by considering the minimum processing time required for D2R repetitive transmission and handling the impact on SFO.

[0351] For example, the minimum time To always finish within this AO time interval (i.e., without moving to the next slot) The value and AO slot time can be determined. In the above-described case, repeated transmissions can be performed between consecutive AO indices in the time domain. However, as shown in FIG. 24 If the value exceeds the start of the next AO slot (AO#1, 2420) following the current AO slot (AO#0, 2410), repetitive transmissions may be performed continuously in the next AO slot (AO#2, 2430). Here, if the number of repetitive transmissions (N) is specified by the reader via R2D transmission, it may always be specified to satisfy 'N <= X'. For example, if 'N > X' is specified, repetitive transmissions may be performed for a number of possible repetitive transmissions less than X. Alternatively, if transmissions are possible in other AOs after X, the remaining number of repetitive transmissions or the entire number of repetitive transmissions may be performed in those other AOs. As another example, 'D2R Tx time length ( ) > AO time interval( In the case of )', repeated transmission may not apply. Or, D2R Tx time length( ) may also be adjusted considering the length of the AO time interval.

[0352] Based on the above, a method for selecting resources for repetitive transmission is described below, based on conditions for at least one of the resources in the time domain and frequency domain for R2D transmission and D2R repetitive transmission associated with R2D transmission, time setting, and resource selection.

[0353] Specifically, consider the case where there is a single ID, in which a single device corresponding to a single ID within the paging message performs the transmission of a D2R response (Case 1). Alternatively, consider the case where multiple IDs associated with multiple devices are included within the paging message, in which multiple devices perform the transmission of a D2R response (Case 2).

[0354] FIGS. 25 and 26 are drawings illustrating a method for selecting N AO resources for repetitive transmission that can be applied to the present disclosure.

[0355] Specifically, FIG. 25 illustrates a case where a D2R transmission instructed to a device by a reader is performed. Referring to FIG. 25, among X available time domain resources, N different time domain resources (or AO, 2510) for D2R (repeated) transmission can be randomly selected to perform repeated D2R transmission. Additionally, if K FDM frequency domain resources are additionally set (or instructed), frequency domain resources can also be considered as available resources in the random selection of resources for D2R (repeated) transmission. (Alt 1) As described above, N different D2R transmission resources (or AO resources, 2510) can be selected continuously or discontinuously in the time domain. Also, referring to FIG. 26, a D2R transmission instructed to each device by a reader can be performed. Among X available time domain resources, N different time domain resources (or AO, 2610) for D2R (repeated) transmission may be allocated for Device #1, and N other different time domain resources (or AO, 2620) may be randomly selected for Device #2 so that D2R transmission may be performed repeatedly.

[0356] In addition, as an example, as a method for selecting D2R transmission resources (or AO resources), N D2R transmission resources (or AO resources) for repetitive transmission can always be selected at different times and can be randomly selected from among D2R transmission resources (or AO resources) located at the same frequency (Alt 1-1). Since the above method performs D2R transmission on the same frequency, the reader can easily receive the corresponding D2R repetitive transmission. Specifically, the reader can easily receive the D2R repetitive transmission in terms of synchronization and SFO handling. The above may be as shown in Table 11 below, but is not limited thereto.

[0357] [Table 11]

[0358]

[0359]

[0360]

[0361] FIGS. 27 and 28 are drawings illustrating D2R iterative transmission resource allocation based on AO Set random selection that can be applied to the present disclosure.

[0362] As another example, among X time domain resources available for D2R transmission instructed to a device by a reader, N sets of consecutive resources (or AO Sets) of different time domains for D2R (repeated) transmission may be randomly selected to perform D2R transmission (or Msg1 transmission) repeatedly. (Alt 2) Additionally, if K FDM frequency domain resources are set (or instructed), frequency domain resources may also be considered as available resources in the random selection of the D2R transmission resources described above. However, N consecutive resources for repeated transmission may be limited to resources on the same frequency and / or different frequencies.

[0363] Referring to FIGS. 27 and 28, unlike FIGS. 25 and 26, N consecutive resource sets (or AO Sets) can be selected as D2R transmission resources. The transmission resources corresponding to the possible resource sets each have a minimum time to indicate the available resource sets. and maximum time This can be defined in this dictionary or signaled by R2D.

[0364] The available resource set determined through the above description may be a specific resource set unit among the possible resource sets, and the device may select it randomly. Referring to FIGS. 27 and 28, a D2R transmission resource (or AO resource) for D2R transmission may be selected based on two resource set (or AO resource set) indices (or related time information). The device may perform D2R repetitive transmission through the selected resource and resource set based on the timing of receiving R2D from the reader. For example, in FIGS. 27 and 28, part '(a)' may be an operation for a D2R transmission resource configured by the reader based on D2R scheduling information as described above, and '(b)' may be an operation for an AO resource based on a RACH procedure. However, the following matters may apply equally when performing D2R transmission and are not limited to a specific form.

[0365] Referring to FIG. 27(a), D2R #1 may be configured by repeating D2R transmission resources (2710) for Device #1, and D2R #2 (AO Set #2, 2740) may also be configured by repeating D2R transmission resources (2720) for Device #2. D2R #1 may be a resource selected by Device #1 for D2R repeated transmission (N=2), and D2R #2 may be a resource selected by Device #2 for D2R repeated transmission (N=2). Here, each D2R resource set configuration may be composed of consecutive D2R resources. However, it is not limited thereto, and the D2R resource set may be composed of discontinuous D2R resource indices and is not limited to a specific form. The device can perform D2R transmissions through each D2R resource within the set of D2R resources configured as described above, and transmissions are repeatedly performed over the D2R resources, but may not be in a single form of transmission. (Alt2-1)

[0366] Additionally, referring to FIG. 27(b), based on the RACH procedure, AO Set #1 (AO Set #1, 2730) may be composed of AO #1 and AO #2, and AO Set #2 (AO Set #2, 2740) may be composed of AO #3 and AO #4. ​​AO Set #1 (2730) may be a resource selected by Device #1 for D2R iterative transmission (N=2), and AO Set #2 (2740) may be a resource selected by Device #2 for D2R iterative transmission (N=2). Here, each AO resource set configuration may consist of consecutive AOs. However, it is not limited thereto, and the AO resource set may consist of discontinuous AO resource indices and is not limited to a specific form. The device can perform D2R transmission through each AO resource within the AO resource set configured as described above, and transmission is performed repeatedly over the AO resources but may not be in a single transmission form. (Alt2-1)

[0367] On the other hand, referring to FIG. 28(a), the D2R transmission resource can be configured in the same way as FIG. 27(a). However, unlike FIG. 28, the payload for D2R repetitive transmission can be transmitted continuously in the form of a single transmission. That is, D2R repetitive transmission can be performed in a single transmission. D2R transmission can be repeated within a single D2R transmission resource (2810) for device #1, and D2R transmission resource can be repeated within a single D2R transmission resource (2820) for device #2. Specifically, information bits within a single payload related to D2R transmission can be included repeatedly, thereby obtaining benefits for repetitive transmission. Specifically, information bits can be repeated within a single D2R transmission directed (or pre-configured) by the reader. That is, the same information can be transmitted repeatedly within a single D2R transmission. Here, the repeat transmission level or the number of repeat transmissions may be indicated or pre-set by the reader via R2D and is not limited to a specific form. That is, the device can perform D2R transmission by applying the repeat transmission level or the number of repeat transmissions within a single D2R transmission based on the setting information indicated by the reader (or pre-set setting information).

[0368] Referring to FIG. 28(b), the AO resource set (2830, 2840) can be configured in the same way as FIG. 27(b). However, unlike FIG. 28(b), the payload for D2R repetitive transmission can be transmitted continuously in the form of a single transmission. That is, D2R repetitive transmission can be performed in a single transmission. Specifically, information bits within a single payload related to D2R transmission can be included repeatedly, thereby obtaining benefits for repetitive transmission. Specifically, information bits can be repeated within a single D2R transmission indicated (or pre-configured) by the reader. That is, the same information can be transmitted repeatedly within a single D2R transmission. Here, the repetitive transmission level or the number of repetitive transmissions can be indicated or pre-configured by the reader via R2D and is not limited to a specific form. That is, the device can perform D2R transmission by applying a repeat transmission level or a number of repeat transmissions within a single D2R transmission based on setting information instructed by the reader (or pre-set setting information).

[0369] For example, comparing FIGS. 28 and 27, as described above, D2R transmission containing a single payload can result in a longer transmission time. Here, while a decrease in reception reliability based on traffic conditions, interference, and SFO effects may be considered due to the long transmission time, it can have the advantage of increased transmission efficiency by utilizing guard time. (Alt 2-2)

[0370] Comparing the operation of FIG. 27 and FIG. 28 described above, FIG. 27 (Alt 2-1) may be a structure capable of independent D2R transmission and reception processing for each D2R resource, and accordingly, even if a loss occurs in a specific D2R resource, it may not affect other D2R resources. In addition, since transmission is performed on a D2R resource basis, it may be easy to adapt to changes in the network environment (interference, presence of traffic).

[0371] On the other hand, while FIG. 28 (Alt 2-2) cannot possess the advantages of FIG. 27 (Alt 2-1), it can minimize guard time between AO resources (or D2R resources) and increase transmission time and time resource utilization by utilizing continuous D2R resources (AO set resources). Additionally, since the reader receives a long payload, it may not need to perform the task of processing data reception for each individual AO resource (D2R resource). For example, any one of the methods described above may be used, or each method may be selectively determined and used according to the A-IoT use case or network environment, and is not limited to a specific form.

[0372] As described above, the method may be to perform the corresponding D2R iterative transmission on a D2R resource (or AO resource / AO resource set) randomly determined from among the available AO resources (or D2R resources) of the device.

[0373] As another example, a D2R transmission resource may be determined based on an instruction from the reader to the device on whether to perform a D2R iterative transmission using a specific D2R resource (or AO resource) on the D2R resources (or AO resources) explicitly available to the device. (Alt 3) Although the following description is based on time division multiplexing (TDM), as mentioned above, it is possible to apply both TDM and FDM. For example, as described in FIG. 26, all methods described below may additionally apply FDM resources and are not limited to a specific form. (TDM / FDM) However, for the convenience of explanation, the description is based on TDM.

[0374] FIGS. 29 and 30 illustrate an example of D2R iterative transmission based on explicit signaling from R2D that can be applied to the present disclosure. For example, in FIGS. 29 and 30, part '(a)' may be an operation on a D2R transmission resource configured by a reader based on D2R scheduling information as described above, and '(b)' may be an operation on an AO resource based on a RACH procedure. However, the following matters may be applied equally when performing D2R transmission and are not limited to a specific form.

[0375] Referring to FIGS. 29(a) and FIGS. 30(a), the reader can explicitly instruct the device to use N D2R resources (2910, 3010) for D2R transmission via R2D transmission (Alt 3). The device, having received instructions from the reader, can perform D2R (repeated) transmission using the instructed N D2R resources. Here, to determine the exact transmission time of the D2R transmission, via an R2D message and ...can be indicated. Additionally, whether a repetitive transmission will be initiated from which of the indicated D2R resources can be indicated along with the number of repetitive transmissions. As another example, the aforementioned control information can be predefined and used prior to the transmission of the R2D message and is not limited to a specific form.

[0376] Specifically, the first D2R resource, subsequent consecutive D2R resources, and FDM D2R resources (if available) can be indicated from the reader to the device. Here, the first D2R resource may indicate the index of the first D2R resources configured based on the R2D reception timing and the number of consecutive resources. For example, as a signaling method, the first starting D2R resource and the number of consecutively allocated resources may be indicated via a RIV (Resource Indication Value). As another example, the first starting D2R resource and the number of consecutively allocated resources may be indicated via a bitmap. As yet another example, a specific first starting D2R resource and the number of consecutively allocated resources, selected from a predetermined first starting D2R resource and the number of consecutively allocated resources, may be indicated as a single code point (among code points corresponding to N bits) in the form of a code point. The aforementioned consecutive D2R resources may all be resources allocated to the same frequency. Therefore, operations such as frequency hopping or additional signaling operations for this purpose may not be necessary between repeated transmissions.

[0377] Referring to FIGS. 29(b) and FIGS. 30(b), the reader may explicitly instruct the device to use N D2R resources (or AO resources, AO resource set, 2920, 3020) for D2R transmission (Msg-1 transmission) through the transmission of an A-IoT paging message (R2D). (Alt 3) Upon receiving instructions from the reader, the device may perform D2R (or Msg1) (repeated) transmission through the instructed N D2R resources (or AO resources, AO resource set). Here, to determine the exact transmission time of the D2R transmission, via the paging message and ...can be indicated. In addition, whether a repeat transmission will start from which of the indicated D2R resources (or AO resources) iterations will be initiated can be indicated along with the number of repeat transmissions. As another example, the control information described above may be predefined and used prior to the transmission of the paging message and is not limited to a specific form.

[0378] Specifically, the first D2R resource (or AO resource) and subsequent consecutive D2R resources (or AO resource counts) and FDM AO resources (if available) may be indicated from the reader to the device. Here, the first D2R resource (or AO resource) may indicate the index of the first D2R resources (or AO resources) configured based on the R2D reception timing and the number of consecutive resources. As an example, as a signaling method, the starting first D2R resource (or AO resource) and the number of consecutively allocated resources may be indicated via a RIV (Resource Indication Value). As another example, the starting first D2R resource (or AO resource) and the number of consecutively allocated resources may be indicated via a bitmap. As another example, a specific starting first D2R resource (or AO resource) and a number of consecutively allocated resources, determined in advance in the form of a code point, may be indicated as a single code point (among the code points corresponding to N bits). The aforementioned consecutive D2R resources (or AO resources) may all be resources allocated to the same frequency. Therefore, operations such as frequency hopping or additional signaling operations for this purpose may not be required between repeated transmissions.

[0379] Referring to FIGS. 29 and FIGS. 30, when R2D transmission (or paging message transmission) is performed for only one device, the reader may transmit control information as described above together to cause one device to perform repeated transmission. Here, in FIG. 29, transmission can be performed between consecutive D2R resources (or AO resources, 2910, 2920) as described above. On the other hand, in FIG. 30, the same transmission block within one PDRCH can be repeatedly transmitted between consecutive D2R resources (or AO resources, 3010, 3020).

[0380] Specifically, referring to FIG. 30, the repeat transmission level and the number of repeat transmissions within a single D2R transmission may be indicated or predetermined in advance, as described above. The device may perform D2R transmission based on the repeat transmission level and the number of repeat transmissions determined within a single D2R transmission. For example, the transmission method may be determined or indicated by a reader according to the device's capability or random access type. Alternatively, a specific repeat transmission method may be determined in advance, but is not limited thereto.

[0381] For example, from the perspective of transmission efficiency, repetitive transmission using a single PDRCH may be more efficient. However, as the PDRCH transmission time increases, the impact of SFO accumulates, which may lead to additional operations or resource usage to handle errors. Therefore, if the transmission time of a single PDRCH is appropriately set, it may be efficient to perform transmission by including two transmission blocks within a single PDRCH transmission. Here, the single PDRCH transmission time corresponding to the aforementioned D2R transmission resource (time) can be determined based on the size of the data to be transmitted, the transmission time per bit, and the number of repetitive transmissions within the scheduling information provided by the reader. Alternatively, considering simple implementation and design consistency, a single transmission block may be included in each PDRCH and PDRCH repetitive transmission may be performed, but this is not limited thereto.

[0382] As another example, the reader may designate N D2R resources (or AO resources) individually. Through the above, D2R resources (or AO resources) can be allocated contiguously or discontinuously. In the above case, signaling overhead for transmitting control information may increase, but specific D2R resources (or AO resources) can be flexibly designated for repetitive transmission through a bitmap consisting of N bits. Each bit value among the N bits may correspond to a single D2R resource index (or AO index), and if the corresponding bit value is determined to be 1, it may be used as a resource for repetitive transmission. Conversely, if the corresponding bit value is designated as 0, it may not be used as a resource for repetitive transmission. Of course, it may be designated with the opposite value, and it may not be limited to a specific designation method.

[0383] As another example, repetitive transmission resources can be indicated in units of set indices based on a set unit composed of N resources. Set indexing can be performed by increasing frequency first and then indexing in chronological order, but indexing in the reverse order may also be applicable. Additionally, if FDM AO resources are available, information regarding FDM frequency positions can be indicated. The frequency positions of one or more AOs in the frequency domain can indicate the positions of the remaining FDM AO resources through offset values ​​in the frequency domain based on a reference AO (or start AO).

[0384] As another example, consider a case where the system is extended to multiple devices (Case 2). That is, the reader can transmit 'multiple IDs' associated with multiple devices included in the paging message to peripheral devices. Here, the peripheral device associated with each ID can independently receive control information corresponding to each device via the paging message based on the ID, as shown in FIG. 22. In the above case, the overhead within the paging message may increase. For example, to reduce overhead, some common control information may be unified and used and directed by each device as a single value. Additionally, the above-described matters may apply equally to other matters.

[0385] FIG. 31 is a diagram illustrating an example of a Msg1 (D2R) iterative transmission method (only TDM) for a plurality of devices applicable to the present disclosure. For example, in FIG. 31, part '(a)' may be an operation for a D2R transmission resource configured by a reader based on D2R scheduling information as described above, and '(b)' may be an operation for an AO resource based on a RACH procedure. However, the following matters may be equally applicable even when performing D2R transmission and are not limited to a specific form.

[0386] Referring to FIG. 31(a), this may be an operation for a case where a reader receives an R2D transmission and instructs multiple devices (e.g., two devices) corresponding to the response to repeat transmission (e.g., twice). However, this is for convenience of explanation only and is not limited thereto. Referring to FIG. 31(a), to indicate a total of four D2R resources (3110, 3110) for D2R transmission through R2D transmission, each minimum time and maximum time This can be defined or signaled in advance. In FIG. 31(a), this may be a case where multiplexing between devices is performed only in the TDM manner without additional resources being set in the frequency domain, but it is not limited thereto and can be applied equally even when frequency resources are set. The reader contains information regarding the timing of the repeated transmissions along with the number of D2R repeated transmissions within the R2D transmission. It can transmit. As described above, when the repeated transmission of Device #1 is indicated via R2D transmission, regarding the two repeated transmissions Information may be provided to the device. Additionally, if the repeated transmission of Device #2 (Device #1) is instructed via R2D transmission, regarding the two repeated transmissions Information may be provided to the device. Referring to FIG. 31(a), Device #1 can perform D2R repetitive transmission through the D2R resources allocated to Device #1, and Device #2 can perform D2R repetitive transmission through the D2R resources allocated to Device #2. ID information for distinguishing each device within the R2D transmission may be transmitted in association with at least the control information for the repetitive transmission described above. Additionally, in the case of a single device group ID in which multiple devices are associated, multiple devices associated with a single device group may perform D2R response transmission (Case 3). Or, if an ID is not included in the R2D transmission, all devices that have successfully received the R2D transmission may perform D2R response transmission based on the R2D transmission (Case 4). Here, when repetitive transmission is supported for multiple devices, specific D2R resources among X available D2R resources commonly indicated to multiple devices may be used for D2R response transmission.

[0387] Referring to FIG. 31(b), this may be an operation for a case where a paging message transmitted by a reader is received, and a repetitive transmission (e.g., twice) is instructed to all of the multiple devices (e.g., two devices) corresponding to the response. However, this is for convenience of explanation only and is not limited thereto. Referring to FIG. 31, to instruct a total of four D2R resources (or AO resources, 3130, 3140) for D2R transmission (or A-IoT Msg 1) transmission via a paging message, the respective minimum time and maximum time This can be defined in advance or signaled. In FIG. 31, this may be a case where multiplexing between devices is performed only in the TDM manner without additional resources being set in the frequency domain, but it is not limited thereto and can be applied equally even when frequency resources are set. The reader contains information regarding the timing of the repeated transmissions along with the number of D2R repeated transmissions within the paging message. It can transmit. As described above, when the repeated transmission of Device #1 is indicated via a paging message, regarding the two repeated transmissions Information may be provided to the device. Additionally, if the repeated transmission of Device #2 (Device #1) is instructed via a paging message, regarding the two repeated transmissions Information may be provided to the device. Referring to FIG. 31, Device #1 can perform D2R repetitive transmission using AO#1 and AO#2, and Device #2 can perform D2R repetitive transmission using AO#3 and AO#4. ID information for distinguishing each device within the paging message may be transmitted in association with at least the control information for the repetitive transmission described above. Additionally, in the case of a single device group ID associated with multiple devices, multiple devices associated with a single device group may perform D2R response transmission (Case 3). Or, if an ID is not included in the paging message, all devices that have successfully received the paging message may perform D2R response transmission based on the paging message (Case 4). Here, when repetitive transmission is supported for multiple devices, specific D2R resources (or specific AO resources) among X available D2R resources (or AO resources) commonly indicated to multiple devices may be used for D2R response transmission.

[0388] In addition to what has been described above, each device can independently select an A-IoT D2R repeat transmission level to perform A-IoT D2R repeat transmission. Specifically, as described above, the D2R (or A-IoT Msg1) repeat transmission may be variably determined by the device based on the proposed transmission time interval / timing within the D2R transmission (or A-IoT Msg1 transmission) time interval. Here, the device may receive configuration information related to the determination method via an A-IoT paging message to variably determine at least one of the number of repeat transmissions and the number of D2R resources (or AO resources). As another example, the information described above may be predetermined information, but is not limited thereto. As described above, the number of repeat transmissions may be determined independently for each device. For example, multiple devices corresponding to an R2D paging message may have different channel environments. As a specific example, a device located close to the reader and a device located far from the reader may be considered. In the above-described case, a device located close to the reader may not necessarily need to perform repeated transmissions, while a device located far away and in a situation with limited transmission and reception power needs to perform more repeated transmissions. In the above-described environment, each device can utilize the ability to overcome these limitations by variably determining at least one of the number of repeated transmissions and the number of D2R resources (or AO resources).

[0389] FIG. 32 illustrates the determination of a D2R repeat transmission level based on the received power strength of an R2D signal using two threshold values ​​applicable to the present disclosure. Since the device determines the level (number) of D2R repeat transmissions based on control information provided by a reader or predetermined control information, each device may determine a different number of D2R repeat transmissions by considering the device's channel environment, traffic characteristics, and the following items. For example, the information required for determining an independent D2R repeat transmission level for each device may include the following information.

[0390] Channel environment between reader and device (strength of reception power of paging message (R2D) signal)

[0391] Based on the information described above, the D2R (or Msg 1) repeat transmission level (number) can be determined. Here, threshold information regarding the intensity of the received power (e.g., dBm) may be provided within the paging message transmitted from the reader. The device may utilize this information to determine the level of D2R repeat transmission. Here, the number of D2R repeat transmission levels may be determined according to the number of threshold values ​​provided. For example, if one threshold value is provided, it may be indicated that N repeat transmissions are performed if the intensity of the received power is greater than the threshold value, and no repeat transmissions are performed if it is less than the threshold value.

[0392] As another example, referring to FIG. 32, two threshold values ​​may be provided to the device. Here, the threshold values ​​may be included in a paging message transmitted by the reader or determined in advance and provided to the device. The device may determine the number of repeated transmissions for D2R transmissions corresponding to response information for subsequent paging messages by comparing the threshold values ​​with the strength of the received power measured during the reception of the paging message. The threshold values ​​may be determined by dynamically changing depending on the network environment, but they may not be limited to a specific form and may operate as shown in Table 12 below. However, Table 12 is for convenience of explanation only and is not limited thereto.

[0393] [Table 12]

[0394]

[0395]

[0396] In addition, the device can determine the level of repetitive transmission and resource utilization by combining the frequency domain (FDM) and the time domain (TDM) under the same conditions as an active repetitive transmission decision method for resource efficiency. For example, at low reception power, only time domain-based repetitive transmission may be applied. On the other hand, at high reception power, 'time + frequency' or 'frequency' domain-based repetitive transmission may be applied, but is not limited thereto. Through the above, the transmission power and resources of the device can be efficiently utilized to improve D2R transmission quality.

[0397]

[0398] Traffic characteristics, A-IoT service types (e.g., inventory, command), Quality of Service (QoS)

[0399] D2R repetitive transmission can be performed by determining different repetitive transmission counts based on service types possessing the characteristics / quality of important traffic. Additionally, for high-importance traffic, it may be possible to transmit it with a higher transmission priority in addition to the number of repetitive transmissions. That is, for high-importance traffic, not only is the number of repetitive transmissions guaranteed, but resources can also be allocated with high priority. For example, independent numbers of repetitive transmissions may be applied depending on the cases of 'No D2R data', 'Inventory-only', and 'Inventory and command'. For example, if Command information corresponds to relatively important traffic, D2R transmissions corresponding to response information to R2D transmissions based on Commands may be configured to apply more repetitive transmissions. As another example, it may be possible to perform repetitive transmissions by determining that more repetitive transmissions are allocated in the case of Inventory. In other words, the present disclosure does not limit the level of repetitive transmission to a specific traffic type, but allows for the allocation and application of repetitive transmission levels according to various A-IoT traffic types and corresponding AS layer procedures. In addition, cases where data information is not always present in D2R transmission may be included, and in such cases, the method described above may be considered as a type of traffic.

[0400]

[0401] Determination of repeated transmission levels based on random access situations (non-contention access or contention-based access procedures):

[0402] For example, if a reconnection is performed after two repeated transmissions on the first attempt fails, the number of repeated transmissions can be increased to three. In other words, the number of repeated transmissions can be dynamically adjusted based on network load and the number of reconnections.

[0403]

[0404] Cases of D2R data transmission failure and contention-based random access contention resolution failure:

[0405] The A-IoT device may be supported in performing a reconnection at other opportunities provided (or controlled) by the reader (i.e., the random access retry mentioned above). Here, the A-IoT device may not be expected to perform a reconnection automatically; that is, the reconnection may always be controlled by the reader. The reader may use an explicit R2D failure / success feedback indication to determine whether the device reconnects. However, the aforementioned indication may be optional. In the aforementioned case, the D2R transmission for the reconnection attempt may be based on a repeat transmission. Configuration information regarding the repeat transmission applied during reconnection may be indicated by the reader or determined in advance.

[0406]

[0407] Determination of specific D2R iterative transmission levels based on device-side power status or energy harvesting time:

[0408] In cases where the device performs D2R transmission, the device may not perform repetitive transmission in at least one of the low-power state and the energy harvesting time interval. Since the device is in a low-power state, it may not possess sufficient energy for repetitive transmission. Therefore, even if D2R repetitive transmission should be performed by satisfying the proposed control information and corresponding conditions, the device may not perform D2R repetitive transmission if it corresponds to a low-power state or energy harvesting time. Alternatively, in the above-mentioned case, the device may limit D2R repetitive transmission to a specific number of repetitive transmissions. However, as an example, the decision regarding repetitive transmission may be made when urgent traffic occurs within the energy harvesting time.

[0409]

[0410] Determining whether to repeat transmission by combining energy and traffic importance:

[0411] For example, transmission may be omitted when the energy level is low and the traffic importance is low. As another example, if the traffic importance is high even with low energy, a single transmission or repeated transmission may be performed. When the device performs a D2R transmission to trigger the corresponding R2D transmission again due to a situation where the reader side is unable to transmit a specific R2D (e.g., Msg 2) or fails to receive the R2D message, the device may support the D2R transmission by applying a specific D2R repeated transmission level. In the above case, since system performance degradation is expected when the reader side is delayed in determining the failure, a timer may be defined to automatically perform repeated transmission within a certain period without an acknowledgment message from the reader. Here, the device can perform a D2R transmission that actively responds to the case of R2D message reception failure through a timer-based mechanism.

[0412]

[0413] Determination of repetitive transmission level based on A-IoT network loading information

[0414] For example, the number of repeated transmissions can be dynamically determined by considering the overall network load. In other words, the number of repeated transmissions can dynamically decrease or increase depending on the overall network load. For instance, if the network load is low, a higher number of repeated transmissions may be allowed by the leader. Conversely, if the load is high, repeated transmissions may be allowed only for critical traffic, but are not limited to this.

[0415]

[0416] FIG. 33 is a flowchart illustrating the repetitive transmission operation of an A-IoT device to which the present disclosure applies. Referring to FIG. 33, the device receives a first message from a reader via an R2D link (S3310), and the device can transmit a second message to the reader via a D2R link in response to the first message (S3320). That is, the device can perform D2R transmission. Here, the D2R transmission transmitted by the device as the second message may include the same information bits repeated based on a repetitive transmission level. Here, the second message containing the same information bits repeated based on a repetitive transmission level may be transmitted from the device to the reader through a single D2R transmission resource. Here, at least one of the time domain resource and the frequency domain resource for the aforementioned single D2R transmission resource may be transmitted from the reader to the device. Additionally, as an example, the aforementioned repetitive transmission level information may be transmitted from the reader to the device and is not limited to a specific form. The device may apply repetitive transmission to the D2R transmission transmitted to the reader based on information obtained from the reader. That is, the device can perform transmission including information bits that are repeated in the payload within a single D2R transmission. Here, the repeat transmission level may be determined based on configuration information indicated by the reader or may be a pre-set value. Alternatively, the repeat transmission level may be directly determined by the device using additional information and is not limited to a specific form. Furthermore, the first message transmitted by the reader to the device may include at least one identification information. Here, each identification information corresponds to a device or a group of devices, and configuration information related to the transmission of a second message may be transmitted from the reader to the device based on the identification information. That is, configuration information related to D2R transmission may be provided for each device or group of devices. Additionally, the second message may be transmitted within a pre-set time interval from the time of completion of reception of the first message.

[0417] FIG. 34 is a drawing showing a device configuration to which the present disclosure can be applied.

[0418] Referring to FIG. 34, the first device (3400) and the second device (3450) can communicate with each other. In this case, for example, the first device (3400) may be a base station device and the second device (3450) may be a terminal device. In another example, both the first device (3400) and the second device (3450) may be terminal devices. In yet another example, the first device (3400) and the second device (3450) may be satellite IAB nodes. That is, the first device (3400) and the second device (3450) may be devices that communicate with each other based on NR-based communication and are not limited to a specific form.

[0419] The first device (3400) may include a processor (3420), an antenna unit (3412), a transceiver (3414), and a memory (3416). The processor (3420) performs baseband-related signal processing and may include an upper layer processing unit (3430) and a physical layer processing unit (3440). The upper layer processing unit (3430) may process operations of the MAC (Medium Access Control) layer, the RRC (Radio Resource Control) layer, or higher upper layers. The physical layer processing unit (3440) may process operations of the physical (PHY) layer (e.g., uplink reception signal processing, downlink transmission signal processing). In addition to performing baseband-related signal processing, the processor (3420) may also control the overall operation of the first device (3400). The antenna section (3412) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO (Multiple Input Multiple Output) transmission and reception. Additionally, it may support beamforming. The memory (3416) may store information processed by the processor (3420), software related to the operation of the first device (3400), operating system, application, etc., and may include components such as a buffer. The processor (3420) of the first device (3400) may be configured to implement the operation of the first device in the embodiments described in the present invention.

[0420] The second device (3450) may include a processor (3470), an antenna unit (3462), a transceiver (3464), and a memory (3466). For example, in the present invention, the second device (3450) may communicate with the first device (3400). The processor (3470) performs baseband-related signal processing and may include an upper layer processing unit (3480) and a physical layer processing unit (3490). The upper layer processing unit (3480) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (3490) may process operations of the PHY layer (e.g., downlink reception signal processing, uplink transmission signal processing, sidelink signal processing). In addition to performing baseband-related signal processing, the processor (3470) may also control the overall operation of the second device (3450). The antenna section (3462) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. Additionally, it may support beamforming. The memory (3466) may store information processed by the processor (3470), software related to the operation of the second device (3450), operating systems, applications, etc., and may include components such as buffers. The second device (3450) according to an example of the present invention may be associated with a vehicle. For example, the second device (3450) may be integrated into the vehicle, located in the vehicle, or located on the vehicle. Additionally, the second device (3450) according to the present invention may be the vehicle itself. Furthermore, the second device (3450) according to the present invention may be at least one of a wearable terminal, an AV / VR, an IoT terminal, a robot terminal, or a public safety terminal.The terminal device (3450) to which the present invention is applicable may include any type of communication device that supports interactive services utilizing sidelinks for services such as internet access, service execution, navigation, real-time information, autonomous driving, safety and risk diagnosis. Additionally, it may include any type of communication device that acts as an AR / VR device capable of sidelink operation or a sensor to perform relay operations.

[0421] Here, the vehicle / terminal to which the present invention is applied may include an autonomous vehicle / terminal, a semi-autonomous vehicle / terminal, a non-autonomous vehicle / terminal, etc. Meanwhile, although the second device (3450) according to one example of the present invention is described as being associated with a vehicle, one or more of the UEs may not be associated with a vehicle. This is an example, and the application of the present invention should not be interpreted as being limited to the example described. In addition, the second device (3450) according to one example of the present invention may include various types of communication devices capable of performing cooperation to support interactive services utilizing sidelinks. That is, the second device (3450) may be utilized not only when it directly supports interactive services utilizing sidelinks, but also as a cooperation device to support interactive services utilizing sidelinks.

[0422] Here, the terminal device (3400) receives a first message from the reader via an R2D link, and the device can transmit a second message to the reader via a D2R link in response to the first message. That is, the terminal device (3400) can perform D2R transmission. Here, the D2R transmission transmitted by the terminal device (3400) as the second message may include the same information bits repeated based on a repeat transmission level. Here, the second message including the same information bits repeated based on a repeat transmission level may be transmitted from the terminal device (3400) to the reader through a single D2R transmission resource. Here, at least one of the time domain resource and the frequency domain resource for the aforementioned single D2R transmission resource may be transmitted from the reader to the terminal device (3400). Additionally, as an example, the aforementioned repeat transmission level information may be transmitted from the reader to the terminal device (3400) and is not limited to a specific form. The terminal device (3400) may apply repetitive transmission to the D2R transmission transmitted to the reader based on information obtained from the reader. That is, the terminal device (3400) may perform transmission including information bits that are repeated in the payload within a single D2R transmission. Here, the repetitive transmission level may be determined based on setting information indicated by the reader or may be a pre-set value. Alternatively, the repetitive transmission level may be directly determined by the terminal device (3400) using additional information and is not limited to a specific form. Additionally, the first message transmitted by the reader to the terminal device (3400) may include at least one identification information. Here, each identification information corresponds to the terminal device (3400) or a group of terminal devices, and setting information related to the transmission of a second message may be transmitted from the reader to the terminal device (3400) based on the identification information. That is, setting information related to D2R transmission may be provided for each terminal device (3400) or group of devices.In addition, the second message can be transmitted within a preset time interval from the time the first message is received.

[0423] In addition, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, it may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), general processors, controllers, microcontrollers, microprocessors, etc.

[0424] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating system, application, firmware, program, etc.) that enable an operation according to a method of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer.

[0425] The various embodiments of the present disclosure are not intended to list all possible combinations but to describe representative aspects of the present disclosure, and the matters described in the various embodiments may be applied independently or in combination of two or more.

[0426]

[0427] The above-mentioned matters may also be applied to other systems.

Claims

1. In a device of an ambient-Internet of Things (A-IoT) system, At least one processor; and It includes a memory that stores instructions for the wireless user device to perform a specific operation by the above at least one processor, and The above specific operation is: The above device receives a first message from a reader via an R2D (reader to device) link, and The device transmits a second message via a D2R (device to reader) link in response to the first message, A device in which the second message above includes the same information bits repeated based on the repetition transmission level.

2. In Paragraph 1, A device in which the second message, which includes the same information bits repeatedly based on the above-mentioned repeat transmission level, is transmitted from the device to the reader through a single D2R transmission resource.

3. In Paragraph 2, A device in which at least one of the time domain resource, frequency domain resource, and repeat transmission level information of the above-mentioned D2R transmission resource is transmitted from the reader to the device through the first message.

4. In Paragraph 2, A device in which at least one of the time domain resource, frequency domain resource, and repeat transmission level information of the above-mentioned D2R transmission resource is pre-set in the device.

5. In Paragraph 1, The first message above includes at least one identification information, wherein each of the identification information corresponds to a device or a group of devices, and A device in which the second message transmission related setting information is transmitted from the reader to the device based on the above identification information.

6. In Paragraph 5, The device directly determines the repeat transmission level for the second message based on the second message transmission related setting information received from the reader.

7. In Paragraph 1, A device in which the second message is transmitted within a preset time interval from the time of completion of reception of the first message.

8. In a method of operation of a device in an ambient-internet of things (A-IoT) system, The step of the device receiving a first message from a reader via an R2D (reader to device) link; and The above device includes the step of transmitting a second message via a D2R (device to reader) link in response to the first message, wherein A method of operation in which the second message above includes the same information bits repeated based on a repeat transmission level.

Images