Method and device for signal transmission and reception for IoT device in wireless communication system

Abstract

An operation method performed by a reader in an A-IoT system in a wireless communication system may comprise the steps in which: the reader receives first DCI configured in a first DCI format, wherein the first DCI includes A-IoT transmission timing indication information; and the reader transmits an A-IoT signal to an A-IoT device through an R2D link on the basis of the A-IoT transmission timing indication information.

Description

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

[0001] The present disclosure relates to a method and device for transmitting and receiving signals for an Internet of Things (IoT) device in a wireless communication system. Specifically, the present disclosure relates to a method and device 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 is currently discussing fifth-generation (5G) communications through a program called "IMT for 2020 and beyond."

[0004] To meet the requirements presented in "IMT for 2020 and beyond," the 3rd Generation Partnership Project (3GPP) NR (New Radio) system is being discussed to support various numerologies based on time-frequency resource units, taking into account various scenarios, service requirements, and potential system compatibility.

[0005] Additionally, 5G communications can support the transmission of physical signals or physical channels through multiple beams to overcome adverse channel conditions such as high path loss, phase noise, and frequency offset that occur at high carrier frequencies. Through this, 5G communications can support applications such as enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communication (URLLC).

[0006]

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

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

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

[0010] The technical problem of the present disclosure is a method and device for transmitting DCI (downlink control information) information for A-IoT from a base station to a leader in a wireless communication system.

[0011] The technical problem of the present disclosure is a method and device for transmitting control information indicating transmission timing of an R2D link and a D2R link between an A-IoT device and a reader in a wireless communication system.

[0012] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0013]

[0014] According to one aspect of the present disclosure, a method of operating a leader in an ambient-internet of things (A-IoT) system may include a step of the leader receiving a first DCI (downlink control information) format configured through a physical downlink control channel (PDCCH), wherein the first DCI includes A-IoT transmission timing indication information; and a step of the leader transmitting an A-IoT signal to an A-IoT device through an R2D (reader to device) link based on the A-IoT transmission timing indication information.

[0015] In addition, according to one aspect of the present disclosure, a leader of an A-IoT system includes at least one processor, and a memory storing instructions for causing a wireless user device to perform a specific operation by the at least one processor, wherein the specific operation comprises: receiving a first DCI configured in a first DCI format through a PDCCH, wherein the first DCI includes A-IoT transmission timing indication information, and the leader can transmit an A-IoT signal to an A-IoT device through an R2D (reader to device) link based on the A-IoT transmission timing indication information.

[0016] Additionally, the following may be commonly applied:

[0017] According to one aspect of the present disclosure, the first DCI includes a first identifier indicating an A-IoT transmission type, wherein if the first identifier is a first value, only R2D transmission is performed from the reader to the A-IoT device, and if the first identifier is a second value, after the R2D transmission from the reader to the A-IoT device, a D2R (device to reader) transmission corresponding to the R2D transmission may be further performed.

[0018] Additionally, according to one aspect of the present disclosure, when the first identifier is the first value, the A-IoT transmission timing indication information in the first DCI includes a first timing offset, and the first timing offset may indicate a slot in which R2D transmission is performed based on a slot in which the first DCI is transmitted.

[0019] Additionally, according to one aspect of the present disclosure, the A-IoT transmission timing indication information within the first DCI may further include a second timing offset together with the first timing offset, wherein the second timing offset may indicate a transmission time point at which R2D transmission is performed within the slot from the boundary of the slot at which R2D transmission is performed.

[0020] Additionally, according to one aspect of the present disclosure, A-IoT transmission timing indication information within the first DCI further includes a first timing offset and start point and length information at which R2D transmission is performed, and a transmission time point at which R2D transmission within a slot is performed from a slot boundary can be indicated based on the start point and length information.

[0021] In addition, according to one aspect of the present disclosure, when the first identifier is the second value, the A-IoT transmission timing indication information in the first DCI includes a first timing offset and a second timing offset as timing offsets of R2D transmission, and the A-IoT transmission timing indication information in the first DCI further includes a third timing offset as timing of D2R transmission, wherein the first timing offset indicates a slot in which R2D transmission is performed based on a slot in which the first DCI transmitted through the PDCCH is transmitted, and the second timing offset may indicate a transmission time point in which R2D transmission is performed within the slot from a boundary of the slot in which R2D transmission is performed.

[0022] Additionally, according to one aspect of the present disclosure, the third timing offset may indicate the slot in which the D2R transmission is performed or the actual D2R transmission time within the slot relative to the slot in which the R2D transmission is performed.

[0023] Additionally, according to one aspect of the present disclosure, the third timing offset may indicate a slot in which the D2R transmission is performed or an actual D2R transmission time within a slot relative to the slot in which the first DCI is transmitted.

[0024] Additionally, according to one aspect of the present disclosure, the third timing offset may indicate the slot in which the D2R transmission is performed or the actual D2R transmission time within the slot relative to the time at which the R2D transmission is performed.

[0025] Additionally, according to one aspect of the present disclosure, the third timing offset may indicate the start time of a contention window in which at least one A-IoT device can perform D2R transmission, relative to the slot in which the first DCI is transmitted.

[0026] Additionally, according to one aspect of the present disclosure, the A-IoT transmission timing indication information within the first DCI may further include a fourth timing offset together with the third timing offset, wherein the fourth timing offset may indicate a transmission time point at which D2R transmission is performed within the slot from the boundary of the slot at which D2R transmission is performed.

[0027]

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

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

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

[0031] According to the present disclosure, a method for transmitting DCI information for A-IoT to a leader by a base station in a wireless communication system can be provided.

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

[0033] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0034]

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

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

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

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

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

[0040] Figure 6 is a diagram showing a modulation method and waveform to which the present disclosure can be applied.

[0041] FIG. 7 is a diagram illustrating a method for configuring a transmission block to which the present disclosure can be applied.

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

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

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

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

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

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

[0048] Figure 14 may be a D2R bandwidth to which the present disclosure may be applied.

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

[0050] Figure 16 is a diagram showing different scenarios of the R2D reader and the D2R reader applied to the present disclosure.

[0051] Figure 17 is a diagram showing the same scenario for the R2D reader and the D2R reader applied to the present disclosure.

[0052] Figure 18 is a diagram showing an A-IoT topology applied to the present disclosure.

[0053] FIG. 19 is a diagram illustrating a method for indicating A-IoT timing through DCI in the R2D only case applied to the present disclosure.

[0054] FIG. 20 is a diagram illustrating a method for determining S and L values ​​based on a chip time interval applied to the present disclosure.

[0055] FIG. 21 is a diagram illustrating a method for indicating A-IoT timing through DCI in the case of R2D and D2R applied to the present disclosure.

[0056] FIG. 22 is a diagram illustrating a method for indicating A-IoT timing through DCI in the case of R2D and D2R applied to the present disclosure.

[0057] FIG. 23 is a diagram illustrating a method for indicating A-IoT timing through DCI in the case of R2D and D2R applied to the present disclosure.

[0058] FIG. 24 is a diagram illustrating a method for indicating A-IoT timing through DCI in the case of R2D and D2R applied to the present disclosure.

[0059] FIG. 25 is a diagram illustrating a method for indicating A-IoT timing through DCI in the case of R2D and D2R applied to the present disclosure.

[0060] FIG. 26 is a flowchart illustrating a method for indicating A-IoT timing via DCI in the R2D only case applied to the present disclosure.

[0061] FIG. 27 is a flowchart illustrating a method for indicating A-IoT timing via DCI in the case of R2D and D2R applied to the present disclosure.

[0062] Figure 28 is a drawing showing a base station device and a terminal device to which the present disclosure is applied.

[0063]

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

[0065] In describing embodiments of the present disclosure, detailed descriptions of known configurations or functions will be omitted if they are deemed to obscure the gist of the present disclosure. Furthermore, portions of the drawings that are irrelevant to the description of the present disclosure have been omitted, and similar portions are designated with similar reference numerals.

[0066] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to 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 said to "include" or "have" another component, unless otherwise specifically stated, this does not exclude the other component, but rather implies that the other component may be included.

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

[0068] In this disclosure, distinct components are used to clearly illustrate their respective characteristics, and do not necessarily imply that the components are separated. That is, multiple components may be integrated into a single hardware or software unit, or a single component may be distributed into multiple hardware or software units. Therefore, even if not specifically mentioned, such integrated or distributed embodiments are also included within the scope of this disclosure.

[0069] In the present disclosure, the components described in various embodiments are not necessarily essential components, and some may be optional components. Therefore, embodiments comprising a subset of the components described in one embodiment are also within the scope of the present disclosure. Furthermore, embodiments including other components in addition to the components described in various embodiments are also 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 a process of controlling the network and transmitting or receiving a signal in a system (e.g., a base station) that manages the wireless communication network, or in a process of transmitting or receiving a signal in a terminal connected to the wireless network.

[0071] It is self-evident that various operations performed for communication with terminals 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. 'Base station (BS)' can be replaced by terms such as fixed station, Node B, eNodeB (eNB), ng-eNB, gNodeB (gNB), and access point (AP). In addition, 'terminal' can be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station), SS (Subscriber Station), and non-AP station (non-AP STA).

[0072] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0073] In the following description, the term NR (New Radio) system is used for the purpose of distinguishing the system to which various examples of the present disclosure are applied from existing systems; however, the scope of the present disclosure is not limited by this term.

[0074] NR systems support a variety of subcarrier spacings (SCS) to accommodate diverse scenarios, service requirements, and potential system compatibility. Furthermore, NR systems can support the transmission of physical signals / channels across multiple beams to overcome challenging channel conditions, such as high path loss, phase noise, and frequency offsets that occur at high carrier frequencies. This enables NR systems to support applications such as enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC) / ultra Machine Type Communications (uMTC), and Ultra Reliable and Low Latency Communications (URLLC).

[0075] Hereinafter, 5G mobile communication technology can be defined to include not only the NR system, but also the existing LTE-A (Long Term Evolution-Advanced) system and LTE (Long Term Evolution) system. 5G mobile communication may include technology that operates in consideration of backward compatibility with previous systems as well as the newly defined NR system. Therefore, the 5G mobile communication below may include technology that operates based on the NR system and technology that operates based on previous systems (e.g., LTE-A, LTE), and is not limited to a specific system.

[0076] First, we would like to briefly explain the physical resource structure of the NR system to which the present invention is applied.

[0077] FIG. 1 is a drawing for explaining an NR frame structure to which the present disclosure can be applied.

[0078] In NR, the basic unit of time domain is It can be, , and N can be 4096. Meanwhile, in LTE, the basic unit of the time domain is It can be, And, =2048. The constant for the multiplication relationship between the NR time base unit and the LTE time base unit is k= can be defined as

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

[0080] 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, based on the following mathematical expression 1.

[0081] [Mathematical Formula 1]

[0082]

[0083]

[0084] Here, It may be a TA offset value that occurs due to differences in duplex mode, etc. In FDD (Frequency Division Duplex), has a value of 0, but in TDD (Time Division Duplex), it takes into account 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. At this time, 13792 is 7.020 μs.

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

[0086] 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 each subcarrier spacing. Uplink and downlink transmission and reception can be performed based on the corresponding resource grid.

[0087] In the frequency domain, one Resource Block (RB) consists of 12 REs, and each of the 12 REs can be configured with an index (nPRB) for one RB. 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 in the following mathematical expression 2. Here, represents the number of subcarriers per RB, and k represents the subcarrier index.

[0088] [Equation 2]

[0089]

[0090]

[0091] Different numerologies can be configured to meet the diverse services and requirements of NR systems. For example, while LTE / LTE-A systems can support a single subcarrier spacing (SCS), NR systems can support multiple SCSs.

[0092] A new numerology for NR systems supporting multiple SCSs can operate in frequency ranges or carriers such as below 3GHz, 3GHz-6GHz, 6GHZ-52.6GHz or above 52.6GHz to address the issue of not being able to use wide bandwidth in frequency ranges or carriers such as 700MHz or 2GHz.

[0093] Table 1 below shows examples of numerologies supported by the NR system.

[0094] [Table 1]

[0095]

[0096] Referring to Table 1 above, the numeral can be defined based on the subcarrier spacing (SCS), cyclic prefix (CP) length, and number of OFDM symbols per slot used in the Orthogonal Frequency Division Multiplexing (OFDM) system. The above values ​​can be provided to the terminal through the upper layer parameters DL-BWP-mu and DL-BWP-cp for the downlink, and through the upper layer parameters UL-BWP-mu and UL-BWP-cp for the uplink.

[0097] In Table 1 above, when the subcarrier spacing setting index (u) is 2, the subcarrier spacing (Δf) is 60 kHz, and normal CP and extended CP can be applied. For other numerology indices, only normal CP can be applied.

[0098] A normal slot can be defined as the basic time unit used to transmit a single piece of data and control information in an NR system. The length of a normal slot can be set to the number of OFDM symbols, which is 14 by default. Furthermore, unlike slots, a subframe has an absolute time length equivalent to 1 ms in an NR system and can be used as a reference time for the length of other time intervals. Here, for coexistence or backward compatibility between LTE and NR systems, a time interval similar to an LTE subframe may be required in the NR standard.

[0099] For example, in LTE, data can be transmitted based on a unit of time called a Transmission Time Interval (TTI), which can be set to one or more subframes. Here, one subframe can be set to 1ms and can contain 14 OFDM symbols (or 12 OFDM symbols).

[0100] In addition, a non-slot can be defined in NR. A non-slot can mean a slot having a number that is at least one symbol smaller than a normal slot. For example, in the case of providing low latency such as URLLC service, latency can be reduced through a non-slot having a number of symbols smaller than a normal slot. Here, the number of OFDM symbols included in a non-slot can be determined by considering the frequency range. For example, a non-slot with a length of 1 OFDM symbol can be considered in a frequency range of 6 GHz or higher. As an additional example, the number of OFDM symbols defining a non-slot can include at least 2 OFDM symbols. Here, the range of the number of OFDM symbols included in a non-slot can be set as the length of a mini-slot up to a predetermined length (e.g., the normal slot length - 1). However, as a specification of a non-slot, the number of OFDM symbols may be limited to 2, 4, or 7 symbols, but is not limited thereto.

[0101] Additionally, for example, in unlicensed bands below 6 GHz, subcarrier spacing where u equals 1 and 2 may be used, and in unlicensed bands above 6 GHz, subcarrier spacing where u equals 3 and 4 may be used. For example, when u equals 4, it may be used for SSB (Synchronization Signal Block).

[0102] [Table 2]

[0103]

[0104] 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 ( ) is shown. Table 2 shows the above-described values ​​based on a normal slot having 14 OFDM symbols.

[0105] [Table 3]

[0106]

[0107]

[0108] Table 3 shows the number of slots per frame and the number of slots per subframe based on normal slots with 12 OFDM symbols per slot when extended CP is applied (i.e., when u is 2 and the subcarrier spacing is 60 kHz).

[0109] As mentioned above, one subframe may correspond to 1ms on the time axis. Additionally, 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, the 480kHz SCS may not be considered, but is not limited to these examples.

[0110] [Table 4]

[0111]

[0112]

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

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

[0115]

[0116] low power consumption

[0117] A-IoT devices consume very low power and use energy harvesting technology to collect energy from the surrounding environment, which can significantly extend battery life and minimize maintenance requirements.

[0118] Constant connectivity

[0119] AIoT devices are constantly connected and can communicate with servers and other IoT devices via various network technologies (e.g. NB-IoT, LoRaWAN, 5G, etc.), enabling real-time data collection and analysis to improve decision-making processes and promote automation.

[0120] Integration and interoperability

[0121] A-IoT solutions can be easily integrated into various platforms and systems, enhancing interoperability. A-IoT can enable devices from various manufacturers to communicate and collaborate, leading to more efficient systems.

[0122] Intelligent interaction

[0123] 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 may detect changes in ambient temperature and automatically adjust the heating system, but this may not be limited to this specific example.

[0124] Security and Privacy

[0125] Ambient IoT systems can ensure security and privacy when collecting and processing personal data, and this can be achieved through various security measures such as encryption technology.

[0126] Areas of application

[0127] A-IoT can be utilized in a variety of fields. For example, it can be used in smart homes, smart cities, healthcare, agriculture, industrial automation, and other fields, thereby enhancing the convenience of daily life. A-IoT can also improve energy efficiency and enable more effective resource management.

[0128] A-IoT may be a revolutionary technology in its own right, but it is growing alongside IoT technology and is expected to be deeply applied to our daily lives and industries in the coming years.

[0129] Two sets of groups for use cases / services

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

[0131] [Table 5]

[0132]

[0133]

[0134] [Table 6]

[0135]

[0136]

[0137] The following describes A-IoT technology based on the above. Terms related to A-IoT technology may include the following, but are not limited to these names or technologies.

[0138]

[0139] PRDCH (R2D, reader to device)

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

[0141] PDRCH (R2D, device to reader)

[0142] 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). PDRCH is a physical layer D2R channel that can transmit data information and control information from the physical layer / upper layers.

[0143] reader

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

[0145] As described above in Topology 2, various intermediate nodes (340) including user devices can perform communication with the A-IoT device (350) as a leader. For example, the base station (330) may be located outdoors as a macro 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 performing communication with the A-IoT device (350) as a relay, IAB node, UE, repeater, and other devices as described above, and is not limited to a specific form.

[0146] For example, transmissions from A-IoT devices (including backscattering transmissions) may be performed at least in the uplink frequency spectrum. However, transmissions from A-IoT devices are not limited to the uplink frequency spectrum, and may also utilize other frequency spectrums.

[0147] device

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

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

[0150] Another type, device 2a, may have a peak power consumption of less than a few hundred μW and may be 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, which is different from 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.

[0151] Another type, device 2b, may have a peak power consumption of less than a few hundred μW and may be equipped with an energy storage device. Device 2b may have an initial sampling frequency offset (SFO) of up to 10X ppm. In addition, device 2b may 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 different from the UL transmission of device 2a.

[0152] For example, transmissions related to A-IoT devices may use, but are not limited to, the uplink spectrum (UL spectrum). Furthermore, the target coverage of an A-IoT system may be, but is not limited to, 10 to 50 meters in India.

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

[0154] Additionally, A-IoT can support a combination of the following use cases. Specifically, A-IoT use cases may include, but are not limited to, "Inventory only," "Command only," or "Inventory + Command." The specific details of each use case may be as shown in Table 7 below.

[0155] [Table 7]

[0156]

[0157]

[0158] Candidate scenarios for A-IoT

[0159] In addition, A-IoT related scenarios may consider combinations of scenarios and topologies in Table 8 below. For example, Table 8 may be a possible environment for an A-IoT system, and each candidate scenario in Table 8 may include at least one of a diagram of the scenario, a CW (carrier wave) transmission location, a supported device type, and a CW / D2R / R2D spectrum. Below, related technologies are discussed based on combinations of scenarios and topologies in Table 8, but may not be limited thereto.

[0160] [Table 8]

[0161]

[0162]

[0163]

[0164] A-IoT R2D / D2R link

[0165] FIG. 4 is a diagram illustrating A-IoT-related links to which the present disclosure may be applied. The R2D link (reader-to-device link) and the D2R link (device-to-reader link) considered in each topology (topology 1 / topology 2) of the 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). In addition, 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 case the intermediate node (440) in topology 2 is a mobile node (e.g., UE), a method for maintaining connectivity and service continuity of the A-IoT device due to mobility may be required, but may not be limited to a specific embodiment.

[0166] FIG. 5 is a diagram illustrating a frequency spectrum usage mode for A-IoT to which the present disclosure can be applied. Referring to FIG. 5, the A-IoT system can 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 set 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 set to be available in a guard band band other than the transmission band with a frequency spectrum of about hundreds of kHz. In addition, the standalone mode may be a mode in which a bandwidth of about tens of MHz is separately set as an A-IoT frequency spectrum (530). The A-IoT frequency band may be considered an FDD (frequency division duplex) of a Frequency Range 1 (FR 1) licensed band. However, the above-described mode is only an example and may not be limited to the embodiment.

[0167]

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

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

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

[0171] FIG. 7 is a diagram illustrating a method for configuring a transport block to which the present disclosure can be applied. Referring to FIG. 7, the transport block can be configured to apply an OOK modulation scheme while basically maintaining an OFDM transport block chain. To this end, a CP-OFDM-based OOK-1 modulation scheme can generate an OOK waveform with a flat spectrum in the frequency domain required to cope with a frequency-selective fading channel environment by utilizing an OFDM overlay sequence on OOK symbols. For example, an OFDM overlay sequence can be used to provide flatness to a pulse waveform in the time domain, and information about the sequence used in on-waveform generation can help improve receiver performance. Considering the above, the OFDM overlay sequences may currently be a Zadoff-Chu (ZC) sequence or an M sequence, but may not be limited to the above embodiment. Here, the overlay sequence can be allocated on-chip on N subcarriers to transform a frequency-domain signal into a time-domain time. Conversely, in the frequency domain, zeros can be allocated on the remaining subcarriers for off-chip use. After this, IFFT and CP insertion can be performed on the sequence.

[0172] In addition, as an example, a transmission method using M-bit OOK modulation based on discrete Fourier transform (DFT)-s-OFDM waveform can be used, and the transmission method can provide higher transmission efficiency than OOK-1. M OOK chips can be transmitted in one OFDM symbol through DFT-s-OFDM processing. As an example, a least square or DFT sequence selection operation can be applied for the purpose of processing optimization, but may not be limited thereto.

[0173] Additionally, the truncation / modification procedure may be an additional processing method that can be applied to the frequency domain signal, and may be considered as an operation for inserting optimization and additional information necessary for performing the IFFT operation. However, the procedure may not be mandatory, and its application may be determined based on the implementation. In addition, the DFT-s-OFDM processing method may consider other methods in the process of generating the OFDM waveform to support the OOK-4 modulation method, which is different from CP-OFDM, and is not limited to a specific form.

[0174] As described above, M-bit OOK in the time domain by DFT-s-OFDM processing can be used for high frequency efficiency. That is, one OFDM symbol can be used for M OOK chips through DFT-s-OFDM processing. After that, the least square (LS) or DFT sequence selection procedure described above can be applied. In addition, truncation / modification can be applied on the frequency domain signal, and finally, a signal in the time domain can be generated through the IFFT+CP insertion procedure. Here, the DFT-s-OFDM processing method for OOK-4 can also be supported in the case of a single OOK chip (i.e., M=1(=OOK-1)) through the same processing procedure.

[0175] With respect to OOK-1 and OOK-4 generation, the M value of OOK-4 can directly influence the transmission rate of the A-IoT system. For example, A-IoT transmissions may be designed to provide a transmission rate similar to that of UHF RFID (ultrahigh-frequency identification), but may not be limited thereto.

[0176] For example, in OOK-4 with Manchester coding and SCS 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 about 107kbps, at least up to M=16 can be supported. In addition, SCS for A-IoT transmission can consider OFDM-based waveforms considering coexistence with existing wireless communication systems (e.g., NR / LTE systems). Therefore, the numerology can basically use the 15kHz SCS value of the FR1 band, and additionally consider 30kHz SCS, but may not be limited thereto.

[0177] D2R transmission can be a method of transmitting by generating an internal carrier wave via backscatter on the carrier wave, thereby allowing the use of a single carrier waveform rather than OFDM. For example, if D2R transmission performs OFDM transmission like R2D, the same numerology as R2D can be applied, but this is not limited to this.

[0178] [Table 9]

[0179]

[0180]

[0181] 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 can be a coding method that assigns a single codeword (CW) to each original binary data bit. For example, a method of transforming a codeword using line coding can define each pattern differently for each line coding according to predetermined rules, which can have different advantages and disadvantages.

[0182] Line coding can not only prevent the original data bit string from continuously appearing as '1' or '0', but also provide voltage transitions that can be utilized for synchronization purposes. The above-described synchronization method (i.e., chip-level timing tracking) can be greatly utilized as an advantage for A-IoT receiving devices that require low-complexity operation. As an example, Manchester encoding and pulse-interval encoding (PIE) can be used as line coding methods for R2D, as shown in FIG. 8. However, the present invention may not be limited thereto.

[0183]

[0184] Manchester Code

[0185] For example, a Manchester code-based encoding method may map bit "1" to codeword "01" and bit "0" to codeword "10". Alternatively, the opposite encoding method may also be possible.

[0186] Here, a transition can always occur between each codeword, which may be a significant feature of Manchester codes, which are self-clocking. Furthermore, Manchester codes can convey clock information along with the data, providing an advantage in timing tracking at the receiver. The encoding rule for Manchester codes may be such that a transition occurs at the boundary between two consecutive bits.

[0187]

[0188] Pulse-interval encoding (PIE)

[0189] For example, the PIE scheme can convey binary information based on the duration of a transition interval. For example, the PIE encoding method can map bit "1" to codeword "1110" and bit "0" to codeword "10". Also, the reverse encoding mapping method may be possible. For example, the long high-voltage chip of bit "1" can increase the high-to-low voltage ratio, which can provide stable transient RF energy to the device. The average high-to-low voltage ratio in PIE can be 66.7%, and the average high-to-low voltage ratio in Manchester encoding can be 50%, but is not limited thereto.

[0190] In UHF RFID, PIE can be used as line coding. Specifically, PIE line coding in UHF RFID can be such that Data-0 has a short on-duration and Data-1 has a longer on-duration. Furthermore, in UHF RFID, PIE can utilize the R2D preamble to enable the receiver to use an on-duration threshold.

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

[0192] 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 envelopes per Manchester symbol are 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 PIE is used for an A-IoT device, as described above, the data length may differ, resulting in an inefficient terminal implementation, but this may not be limited thereto.

[0193] 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 one Manchester coded chip may be T, and the chip length for one bit in Manchester encoding may be 2T. Here, if a transition from low to high is detected in the middle of a bit, the bit may be detected as "0". Conversely, if a transition from high to low is detected in the middle of a bit, the 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 effects for the received R2D transmission.

[0194] FIG. 10 is a diagram illustrating a PIE encoding and decoding method to which the present disclosure can 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 because each information bit starts with a 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. In addition, the length of one PIE high voltage chip for bit "0" can be determined as T, and if a 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 a 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 of the two interval types, due to the high frequency offset (SFO) and channel effects on the received R2D transmission, but may not be limited to the embodiment.

[0195]

[0196] R2D BW and Numerology

[0197] Fig. 11 is a diagram showing the R2D bandwidth and numerology to which the present disclosure can be applied. Referring to Fig. 11, the bandwidth for the A-IoT R2D link is the transmission bandwidth ( , 1110), occupied bandwidth ( , 1120) and system bandwidth ( , 1130). The above-mentioned 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 filters.

[0198] Specifically, the transmission bandwidth ( , 1110) may be a frequency resource used for A-IoT R2D signal transmission, and the 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 limited frequency resource within the RF filter of the receiver and may not be determined separately depending on the R2D transmission method.

[0199] The A-IoT frequency bandwidth needs to be determined considering the efficient operation of the system and coexistence with other wireless technologies, and considering the above, guard bands and guard subcarriers may be required. In addition, the A-IoT frequency bandwidth needs to consider coexistence with NR / LTE. For example, the minimum channel bandwidth for 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 can be as shown in Figure 12. On the other hand, if a guard band is required, it can be as shown in Figure 11. In other words, the frequency guard band can mean that the maximum signal bandwidth of the A-IoT R2D link can be as large as the channel bandwidth. Considering the above, there is a need to design an A-IoT system that creates minimum requirements for the spectrum, which may facilitate A-IoT deployment, but may not be limited to the given embodiment. In addition, the possible frequency bandwidth values ​​may be determined as multiple values. Basically, 1 PRB (assuming 15 kHz SCS, 180 kHz) can be used as the minimum bandwidth value, and additionally, a value corresponding to an integer multiple of 180 kHz and at least one of the other frequency bandwidth values ​​may be defined for A-IoT transmission, but may not be limited thereto.

[0200] R2D time unit and allocation method

[0201] The R2D link can support an in-band mode operating on the NR frequency band, as described above. Therefore, the reader can determine the basic time unit as Tc defined in NR, as shown in Equation 3 below. Furthermore, for example, a time unit considering other wireless systems may be determined, and the present invention is not limited to this embodiment.

[0202] [Equation 3]

[0203]

[0204]

[0205] The smallest time unit Tc can be utilized as the basic sampling time for R2D transmission for OFDM waveforms based on multiples of that value. Furthermore, 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 duration.

[0206]

[0207] R2D multiple access

[0208] The receiver of an A-IoT device may fundamentally operate based on RF-ED (envelope detection), which may limit its ability to simultaneously extract different R2D signals. Specifically, an A-IoT device may operate by detecting voltage transitions, and may have limitations in implementing narrow band-pass filtering. Therefore, the application of multiplexing methods such as orthogonal frequency division multiple access (OFDMA) or frequency division multiple access (FDMA) for the R2D of an A-IoT device may have limitations, but may not be limited thereto.

[0209] Additionally, A-IoT devices do not inherently have the computing power for computational operations such as correlation, and thus may have limitations in performing CDMA (code division multiple access) operations. Therefore, A-IoT R2D transmission may be considered to apply R2D multiple access based on TDMA (time division multiple access), but may not be limited to this embodiment.

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

[0211] Referring to Fig. 13(a), the leader can transmit R2D data (transport block, TB) to the A-IoT device by allocating it to the PRDCH. Specifically, the source bits { } is transmitted as one TB (S1301), the leader can generate CRC bits based on CRC bits having CRC length K based on a CRC polynomial having CRC length k and attach them to the data source bit string as in mathematical expression 4 (S1302).

[0212] [Equation 4]

[0213]

[0214]

[0215] After that, in mathematical formula 4 ( ) bits are based on line coding { } can be composed of M bits. (S1303) Specifically, the data bit string after CRC attachment is It is composed of bits, and when Manchester coding (line coding) is applied, the M-bit string of mathematical expression 6 can be composed.

[0216] [Equation 5]

[0217]

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

[0219] Additionally, a D2R grant may not be required as an uplink grant in connection with a PDRCH transmission. For example, an A-IoT device may perform a passive response based on an R2D message. In another example, the D2R grant may be included in a higher layer message along with other messages conveyed by the last PRDCH transmission. Additionally, scheduling of the PDRCH may be performed via a higher layer signal (e.g., MAC CE) including the modulation coding scheme (MCS), TBS, chip length, chip repetition count, and line coding code length in the previous PRDCH, but may not be limited to the embodiment.

[0220] 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 0. (S1307) Then, coding is performed on the D2R information bits with the CRC attached (S1308), and after modulation is applied (S1309), a PDRCH can be generated (S1310). Here, the coding can be performed in different forms depending on whether line coding and FEC are applied, and the modulation can also be performed based on the above, but may not be limited to a specific form.

[0221] Also, as an example, a preamble can be configured in the R2D transmitted from the reader to the A-IoT device. For example, the R2D preamble can indicate the start of the R2D transmission. Additionally, the R2D preamble can be transmitted from the reader to the device for timing indication. For example, as an A-IoT device type, device type 1 (i.e., ~1us peak power consumption device) cannot use sequence correlation operation, and thus cannot acquire timing or perform signal detection differently from existing NR / LTE terminals. 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 detecting transition edges based on envelope detection (ED) through the preamble signal.

[0222] 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 positioned immediately before the clock acquisition part in terms of time and transmitted as part of the preamble. The start indicator part may indicate at least the starting point of the R2D transmission. In addition, the clock acquisition part may be utilized for the purpose of chip synchronization of the R2D channel transmission (Data / Control Information Transfer Channel, PRDCH) located immediately after the preamble.

[0223] Additionally, the D2R waveform may 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, ) may cause time alignment errors and may not be suitable for D2R waveforms.

[0224] In addition, the 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 above-mentioned OOK, binary PSK (phase shift keying), or binary FSK (frequency shift keying) can be used, but are not limited to the embodiments. For example, OOK can be guaranteed to have the simplest implementation and the 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 loss for backscatter modulation. In addition, binary FSK can be implemented through frequency-dependent on / off switching, similar to OOK. Binary FSK may require twice the clock speed as OOK for the same maximum bandwidth at the same data rate, which may increase power consumption, but may not be limited thereto.

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

[0226] In addition, Fig. 14 may be a D2R bandwidth to which the present disclosure may be applied. For example, the D2R bandwidth may be a transmission bandwidth (B tx,D2R 1411,1412), occupied bandwidth (B occ,D2R , 1421, 1422) and system bandwidth (B sys,D2R, 1430). The transmission bandwidth (1411, 1412) may be a frequency resource scheduled by the leader 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 ) may be a bandwidth including the system bandwidth (1430). The system bandwidth (1430) may refer to a frequency resource that the leader can schedule for D2R transmission to support frequency division multiplexing (FDM) between other devices. In addition, a guard band for coexistence between A-IoT D2R and NR / LTE may be configured, but is not limited to a specific form. Here, each bandwidth may satisfy the following mathematical expression 6.

[0227] [Equation 6]

[0228]

[0229]

[0230] Fig. 15 is a diagram showing the basic frame structure of PRDCH and PDRCH to which the present disclosure can be applied. In an A-IoT system, it may not be possible to maintain synchronization between a leader and an A-IoT device. The A-IoT device may be a device that assumes very low capability and low power consumption. Therefore, synchronization between a leader and an A-IoT device may be caused by a timing error (e.g., SFO) caused by a sampling frequency offset. (parts per million)(10% timing error)) may not be maintained. For example, if a timing error of 1ms occurs every 10ms between a reader and an A-IoT device, the reader may need to continuously transmit a synchronization signal to the A-IoT device every 1ms, which may result in a very large system overhead. Therefore, in order 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 is transmitted and received between a reader and an A-IoT device, a timing acquisition signal may be used between the reader and the A-IoT device, and a method for this may be necessary. For example, in R2D, the R2D preamble may perform this role. Additionally, in D2R, the D2R preamble may perform this role, but may not be limited thereto. For example, as a timing acquisition signal, timing acquisition may be performed using at least one of the preamble, midamble, postamble, periodic sync signal, control information / fields, and guard period, but may not be limited to a specific form.

[0231] 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 control information transmission. In FIG. 15, a start indicator (1511) may indicate the start time of PRDCH / PDRCH transmission. For example, the start indicator (1511) may play a role similar to a delimiter of UHF RFID (ultra high frequency radio frequency identification), but may not be limited thereto. The start indicator (1511) may enable a receiving node to quickly determine when the corresponding channel transmission occurs. For the above-described purpose, the start indicator (1511) may be indicated through a specific voltage pattern (e.g., low-voltage) or other indication method, and the corresponding 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 chip synchronization of the physical channel part using a square wave. The transmission length of the clock acquisition (1512) can be determined in a form proportional to the chip length used for the subsequent data / control transmission portion. In addition, information about the clock reference can be provided based on information about the corresponding chip length. The receiving node can check the interval between the rising or falling edges through the clock acquisition (1512) and acquire information about the chip based on this.

[0232]

[0233] Hereinafter, the DCI (downlink control information) format and related control information fields for A-IoT data scheduling or control are described in consideration of the network environment corresponding to A-IoT topology 2 in FIG. 3 described above. The leader may need to transmit at least one of scheduling and related control information to the A-IoT device for A-IoT data transmission and reception between the leader and the A-IoT device. As an example, in topology 2 of FIG. 3, the case where the leader is an NR UE (user equipment) or an LTE UE may be considered. As another example, the leader may be a network node that is not capable of data scheduling (e.g., relay, IAB (integrated access and backhaul) node). For the convenience of explanation, the following description is based on an NR UE of an NR system, but this is only for the convenience of explanation and may not be limited thereto. As an example, it may be obvious that the operation for an LTE UE of an LTE system and other network nodes may be applied in the same or similar manner.

[0234] The leader needs to provide at least one of data scheduling and L1 (or higher layer) control information for A-IoT data transmission and reception to the A-IoT device. However, in topology 2, the UE (intermediate UE, leader) may have limitations in handling data scheduling and related control information transmission. Since the UE generally implements only terminal functions, it may be difficult for the UE to handle data scheduling and related control information transmission. In other words, the UE may have limitations in performing functions such as data scheduling as a base station (e.g., gNB) function. Therefore, a method to overcome the functional limitations of the intermediate node (UE, leader) may be necessary.

[0235] For example, in a topology 2 environment, a leader (intermediate UE) can receive A-IoT resource scheduling and control information transmission by a network (gNB) through a wireless radio protocol layer corresponding to a Uu link, and a method for this is described below.

[0236] Table 8 described above may be combinations of A-IoT scenarios and topologies. Scenarios in which a CW (carrier wave) transmitting node exists within the topology in Table 8 may be as shown in FIGS. 16 to 18. Each scenario may perform CW transmission to an A-IoT device as an intermediate node with a node transmitting CW. CW transmission may be a signal required to support energy harvesting as well as backscattering transmission of the A-IoT device. The following description is based on the assumption that CW transmission is performed by an intermediate node within the topology, but may not be limited thereto.

[0237] Additionally, as an example, the intermediate node may be at least one of an NR / LTE terminal and another network node (e.g., IAB, Relay, etc.), as described above. Furthermore, the intermediate node may be a terminal to which a subsequent communication system is applied, and other types of terminals may also be possible. The following description assumes that the intermediate node is an NR terminal, but is not limited thereto, and the same concept may be applied to other types of terminals.

[0238] For example, the terminal (or node) may be equipped with a wireless interface function and may be a terminal (or node) that constitutes a 3GPP wireless access system. Accordingly, a Uu link (a wireless interface between an LTE / NR base station and a terminal) may exist between the base station and the intermediate node (reader) referred to below, but may not be limited thereto. The link between the reader and the A-IoT device may be based on an A-IoT wireless access interface for A-IoT data / signaling.

[0239] Here, for example, if a terminal (or node) supports multiple wireless interface functions, the terminal can handle transmission of scheduling and control information for A-IoT data / signaling via a wireless interface currently connected to a base station. As a specific example, if the terminal supports both NR and LTE and forms a Uu link with the base station via the NR system, the terminal can handle transmission of scheduling and control information for A-IoT data / signaling via the NR Uu link. On the other hand, if the terminal supports both NR and LTE and forms a Uu link with the base station via the LTE system, the terminal can handle transmission of scheduling and control information for A-IoT data / signaling via the LTE Uu link. That is, the terminal can handle, but is not limited to, the transmission of scheduling and control information for A-IoT data / signaling via the link through which the terminal is currently connected to the base station. For convenience of explanation, the following description is based on the NR system.

[0240] FIG. 16 is a diagram illustrating different scenarios of an R2D reader and a D2R reader applicable to the present disclosure. Referring to FIG. 16, each of the two readers (1610, 1620) can be connected to a base station (1630) via a Uu link. On the other hand, each of the two readers (1610, 1620) and an A-IoT device (1640) can be connected via an A-IoT wireless link (R2D / D2R). In addition, the A-IoT device (1640) can receive an R2D signal from a first leader (CW transmission node, 1610) and perform a D2R transmission to a second leader (1620). For example, when a terminal performs existing cellular-based communication, the terminal can select a specific serving cell to transmit and receive data. In contrast, in an A-IoT system, at least one reader capable of data communication and at least one A-IoT device around the A-IoT device can confirm each other's presence, and data transmission and reception can be possible based on this. In other words, in an A-IoT system, A-IoT data transmission and reception can be possible at the point when each's presence is confirmed.

[0241] FIG. 17 is a diagram illustrating a scenario in which an R2D leader and a D2R leader applied to the present disclosure are identical. Referring to FIG. 17, unlike FIG. 16, a single leader (1710) may exist as an intermediate node, and the leader (1720) may be connected to a base station (1720) via a Uu link. In addition, the intermediate node (1710) may perform R2D / D2R-based wireless transmission and reception with an A-IoT device (1730), as well as CW transmission for backscattering transmission of the A-IoT device (1730).

[0242] For example, in the scenarios of FIGS. 16 and 17, there is a need to determine how to transfer data between a base station and an A-IoT device, how to perform instructions related to at least one of a command and inventory received from a network (CN), and a transmission method for which intermediate node (leader) within the topology should perform CW transmission, which is described below.

[0243] The following description is based on the case where the intermediate node (or leader) in the above-described scenario / topology is connected to the base station in RRC (radio resource control) connected (RRC CONNECTED) mode based on NR wireless access. That is, the RRC idle / inactive mode terminal may be restricted from operating as an intermediate node (or leader). Since the RRC idle / inactive terminals may be restricted from being controlled by the base station, the intermediate node (or leader) needs to operate in RRC connected mode in order for the base station to smoothly perform A-IoT transmission / reception control, and the following description is based on this.

[0244] In the A-IoT topology 2 environment of the above-described FIG. 3, an intermediate node terminal (leader) (e.g., NR UE or LTE UE) can receive DCI (downlink control information) related to A-IoT and scheduling from a base station for A-IoT scheduling, and a DCI format for this can be determined. In the following, DCI related to A-IoT scheduling is referred to as A-IoT DCI, and the DCI format for this is referred to as A-IoT DCI format. However, it may not be limited to this name, and may be referred to by another name that performs the same function. The A-IoT-DCI format can be used to transmit A-IOT DCI through a PDCCH (physical downlink control channel) channel as a physical layer control information format for a base station to control an A-IoT intermediate node (A-IoT Intermediate UE, leader).

[0245] As mentioned above, for convenience of explanation, the following description is based on the NR system, but it can be equally applied to the LTE system and subsequent generation systems. For example, if the intermediate node leader is an LTE terminal, the LTE terminal can be connected to a base station in the LTE system, and the DCI format considering the LTE PDCCH can be determined in a form identical or similar to that of the NR system. In addition, the DCI format can be determined in the same or similar way in subsequent generation systems and is not limited to a specific form. That is, the DCI format can be used to control the leader as an A-IoT intermediate node. For convenience of explanation, the following description is based on the NR system, but it is not limited thereto, and it can be obviously applied equally to other 3GPP mobile communication systems that define the DCI format (e.g., LTE, LTE-M, NB-IoT, etc.).

[0246] FIG. 18 is a diagram illustrating an A-IoT topology applicable to the present disclosure. Referring to FIG. 18, an NR Uu link (LTE Uu link in the case of LTE) may exist between a leader (UE, 1810) and a base station (1820).

[0247] Here, the A-IoT DCI may be indicated by one or more A-IoT RNTI (radio network temporary identifier) ​​value(s). Specifically, an A-IoT-RNTI value for a wireless communication system (NR or LTE) may be determined. The base station (1820) may transmit at least one of A-IoT data and A-IoT-related control information to a leader, which is an A-IoT intermediate terminal (1810), via a PDCCH. In A-IoT topology 2 of FIG. 18, the base station (1820) may transmit a PDCCH including a DCI format and control field information proposed for A-IoT control to the leader (1810). Here, the CRC (cyclic redundancy check) of the A-IoT DCI format(s) in the corresponding PDCCH may be scrambled by at least one of the A-IoT RNTI value(s) of Table 10 below.

[0248] Considering that only one type of DCI format is supported through PDCCH, an A-IoT RNTI for the A-IoT DCI format (A-IoT-RNTI for DCI format) can be determined. That is, the base station (1820) can transmit only one A-IoT DCI format to control the reader (1810). For example, control information that differs depending on the A-IoT usage purpose and type can be distinguished through the control information field value in the corresponding DCI. Specifically, an A-IoT DCI format that is CRC scrambled by a specific A-IoT RNTI value can include a control field that distinguishes between R2D and D2R (or R2D and R2D&D2R) links. Through the field, control information for R2D and control information fields for D2R can be distinguished and configured.

[0249] In addition, the A-IoT R2D RNTI for the A-IoT DCI format of Table 10 may be an RNTI value for the A-IoT DCI format that transmits control information to the leader to support PRDCH (R2D) only transmission via PDCCH. That is, a DCI format and an RNTI therefor that consider a case where only R2D transmission is performed from the leader to the A-IoT device may be set. When the base station (1820) performs PDCCH transmission including control information for R2D transmission to the leader (1810), the base station (1820) may utilize the A-IoT R2D RNTI value for the A-IoT DCI format to configure the control information and perform the PDCCH transmission. When the A-IoT R2D RNTI value is used, the A-IoT DCI format for transmitting control information related to R2D transmission may be configured independently.

[0250] As another example, the A-IoT R2D-D2R RNTI for the A-IoT DCI format in Table 10 may be an RNTI value for indicating a DCI format that transmits control information to the reader to support both PRDCH (R2D) and PDRCH (D2R) transmissions via the PDCCH. That is, a DCI format and an RNTI for this may be configured considering cases where R2D transmission from the reader to the A-IoT device and D2R transmission from the A-IoT device to the reader are performed without any transmission. As an example, DT or DO-DTT may be considered as a traffic type in the A-IoT system. That is, a case where D2R transmission is performed in response to an R2D transmission as well as an R2D transmission may be considered. As another example, considering other traffic types or use cases, scheduling information for D2R-only transmission may also be provided. Here, the base station (1820) can perform PDCCH transmission with a DCI format including control information for R2D and D2R transmission to the leader (1810) through the A-IoT R2D-D2R RNTI value. When using the A-IoT R2D-D2R RNTI value, the A-IoT DCI format including control information for R2D transmission and D2R transmission can be independently configured.

[0251] As another example, in Table 10, the A-IoT D2R RNTI for the A-IoT DCI format may be an RNTI value for indicating a DCI format for transmitting control information to the leader to support only PDRCH (D2R) transmission via PDCCH. That is, a DCI format and an RNTI for this may be set considering a case where D2R transmission, which is a transmission from an A-IoT device to a leader, is performed. Here, through the A-IoT D2R RNTI value, the base station (1820) may perform PDCCH transmission having a DCI format including control information for R2D and D2R transmission to the leader (1810). When the A-IoT D2R RNTI value is used, the A-IoT DCI format including control information for R2D transmission and D2R transmission may be configured independently.

[0252] For example, when acquiring traffic from an A-IoT device considering the use case described above in an A-IoT system, an A-IoT DCI containing relevant control information based on at least one of the RNTI values ​​in Table 10 may be transmitted from the base station to the leader.

[0253] [Table 10]

[0254]

[0255]

[0256] As another example, the RNTI value may be utilized for the DCI format by at least one of the RNTI values ​​in Table 11 below to additionally indicate the cast type (e.g., groupcast / broadcast). Specifically, it may be possible to utilize the RNTI values ​​in Table 11 below by further considering the cast type in the RNTI format in Table 10, but it may not be limited to the embodiment.

[0257] [Table 11]

[0258]

[0259]

[0260] As another example, at least one of the RNTI values ​​in Table 12 below may be utilized for the DCI format to additionally indicate a use case (e.g., Inventory / Command). Specifically, it may be possible to utilize the RNTI values ​​in Table 12 below by considering additional use cases in the RNTI format of Table 10, but the present invention may not be limited to this embodiment.

[0261] [Table 12]

[0262]

[0263]

[0264] As another example, the RNTI value may be utilized for the DCI format as an "A-IoT-RA RNTI" value to additionally indicate A-IoT random access, but may not be limited to that embodiment.

[0265] At least one of the RNTI values ​​described in Tables 10 to 12 and the A-IoT-RA RNTI can be used for the A-IoT DCI format for controlling the A-IoT link, and is not limited to a specific form. That is, the base station can transmit a PDCCH on which CRC scrambling is performed based on at least one of the RNTI values ​​described in Tables 10 to 12 and the A-IoT-RA RNTI to the leader, and can deliver A-IoT link-related control information to the leader based on the PDCCH.

[0266] Specifically, the PDCCH may scramble the corresponding CRC parity bits as in Equations 7 and 8 below based on at least one RNTI (RNTI for A-IoT) value among the RNTI values ​​described in Tables 10 to 12 and the A-IoT-RA RNTI after the CRC parity bits are generated and attached to the DCI control information bits. For example, may be at least one RNTI (RNTI for A-IoT) value among the RNTI values ​​described in Tables 10 to 12 and the A-IoT-RA RNTI. In addition, In order to form a sequence bit, scrambling can be performed using the CRC parity bits and the RNTI values ​​described above, as in Equations 7 and 8.

[0267] [Equation 7]

[0268]

[0269] [Equation 8]

[0270]

[0271]

[0272] Next, multiple A-IoT DCI formats supporting different types or purposes can be considered, along with at least one RNTI (RNTI for A-IoT) value among the RNTI values ​​described in Tables 10 to 12 and the A-IoT-RA RNTI. Here, each of the one or more A-IoT DCI formats can be determined in consideration of each purpose. An independent DCI format can utilize a control information (including scheduling information) field for at least one of the A-IoT R2D and D2R in consideration of each purpose and situation. For example, the two DCI formats can have the same DCI bit size, and the reader can receive A-IoT-related DCI based on the above. Here, if the size of one of the two DCI formats is smaller, the smaller DCI format can add a padding bit consisting of zero bits to match the size of the larger DCI format. As another example, if one of the two DCI formats is smaller in size, truncation may be performed on the larger DCI format to make it the same size as the smaller DCI format, but is not limited to a specific format.

[0273] As another example, the Identifier for A-IoT DCI formats value can be determined as a first value (0 or 1) and a second value (1 or 0), thereby indicating each A-IoT DCI format (e.g., R2D only or R2D and D2R). Here, each DCI format can be distinguished by indicating whether a response from an A-IoT device is not required (R2D only) or whether a response is required (R2D and D2R) by considering at least one of the A-IoT use cases and traffic characteristics. As another example, a case in which traffic corresponding to D2R only is supported can also be considered by considering at least one of the A-IoT use cases and traffic characteristics. That is, a case in which only D2R only transmission is performed can also be considered, in which case an additional DCI identifier can be further defined.

[0274] As a specific example, the Identifier for A-IoT DCI formats value may be composed of 2 bits, and the first value may indicate an A-IoT DCI format for R2D only transmission, the second value may indicate an A-IoT DCI format for R2D / D2R transmission, and the third value may indicate an A-IoT DCI format for D2R only transmission. In other words, the Identifier for A-IoT DCI formats value may be set with more consideration given to D2R only transmission, and may not be limited to a specific form.

[0275] Considering the above, DCI formats supporting A-IoT transmission and reception can be independently determined and utilized. This allows each control field to be configured using a DCI format appropriate for the situation or purpose, taking into account at least one of the A-IoT use cases and traffic characteristics, thereby enabling efficient PDCCH transmission and clear control information transmission from the base station to the leader.

[0276] Below, we describe the criteria for using two different DCI formats for different A-IoT link purposes: one for R2D only transmissions and the other for D2R transmissions based on R2D transmissions.

[0277] Referring to Table 13, when defining only one DCI format, the DCI formats for different A-IoT links can be differentiated and applied through the proposed control fields in the DCI. The identifier field can indicate which A-IoT link it is for, and the use and configuration of the corresponding control field can be different accordingly. For example, if the identifier field indicates a DCI field for R2D only, the control field after the identifier in the DCI can be composed of control information fields for R2D transmission. On the other hand, if the identifier field indicates R2D and D2R, the control field after the identifier in the DCI can be composed of control information fields for R2D and D2R transmission. In the above case, since the DCI format for the A-IoT link supports only one DCI format, if the control field configuration and number of bits for the two A-IoT links are different, the DCI size can be determined based on the case with the larger size. That is, the DCI format can be determined as a DCI size corresponding to an A-IoT link with a larger DCI size by utilizing zero padding or reserved bits in the DCI corresponding to an A-IoT link with a small size.

[0278] As another example, at least one of the RNTI values ​​of Tables 10 to 12 described above and the A-IoT RA RNTI may be additionally utilized by PDCCH CRC scrambling (e.g., cast type related RNTI) to implicitly indicate the cast type or group transmission status and other information corresponding to each R2D / D2R transmission, and is not limited to a specific form.

[0279] [Table 13]

[0280]

[0281]

[0282] In addition, the following describes a method for providing scheduling information for A-IoT R2D / D2R transmission and reception to a leader by using a DCI format for A-IoT R2D / D2R transmission and reception control. For example, the base station may provide time setting information related to A-IoT transmission and reception timing to the leader in advance through upper layer signaling (e.g., RRC Signaling, MAC CE). Here, the upper layer information may include, but is not limited to, setting information for at least one of an A-IoT R2D resource pool and a D2R resource pool and at least one of an A-IoT timing offset.

[0283] The configuration information for at least one of the A-IoT R2D resource pool and the D2R resource pool may be configuration information for at least one of the time domain and the frequency domain. The base station may provide the resource pool configuration information for A-IoT to the leader through a higher layer so that NR resources and A-IoT resources can be independently utilized. Here, the configuration information for at least one of the A-IoT R2D resource pool and the D2R resource pool may be periodically configured in the time domain. In addition, the configuration information for at least one of the A-IoT R2D resource pool and the D2R resource pool may be transmitted from the base station to the leader in both the time domain and the frequency domain.

[0284] For example, in the case of a standalone A-IoT scenario, configuration information for at least one of the A-IoT R2D resource pool and the D2R resource pool may not need to be provided. Accordingly, the leader may determine to utilize all wireless resources for A-IoT if configuration information for at least one of the A-IoT R2D resource pool and the D2R resource pool is not provided. As another example, the leader may configure all wireless resources to be utilized for A-IoT even if configuration information for at least one of the A-IoT R2D resource pool and the D2R resource pool is provided. However, in the case of in-band mode, the A-IoT resource pool configuration information may be transmitted from the base station to the leader by at least one of system information and RRC signaling, through which configuration information for A-IoT wireless resources may be indicated. Additionally, as an example, A-IoT timing offset setting information can be transmitted from the base station to the leader via the upper layer, as described below.

[0285]

[0286] FIG. 19 is a diagram illustrating a method for indicating A-IoT timing through DCI in the R2D only case applied to the present disclosure.

[0287] The leader (1910) can perform R2D transmission to the A-IoT device (1930). Here, a DCI format for A-IoT (hereinafter, referred to as the A-IoT DCI format) can be transmitted from the base station (1920) to the leader (1910). Referring to FIG. 19, the time point at which the leader (1910) performs A-IoT transmission / reception (e.g., R2D) to the A-IoT device (1930) needs to be determined. Here, timing gap / offset information related to the time point at which A-IoT transmission / reception is performed can be provided from the base station (1920) to the leader (1910). Since the leader (1910) can be a terminal in an RRC connection state, the base station can provide timing gap / offset information to the leader (1910) through a PDCCH that transmits the A-IoT DCI format. Specifically, when the terminal is set to operate as a leader (1910) and the corresponding A-IoT leader role mode is activated, the base station (1920) can set timing offset values ​​corresponding to the timing offset field value in the A-IoT DCI format to the leader (1910) through an upper layer. As another example, timing offset values ​​corresponding to the timing offset field value in the A-IoT DCI format may be preset in the leader (1910) and may not be limited to a specific form. The number of bits of the timing offset field in the A-IoT DCI format may be determined based on the number of timing offset values ​​preset in the leader (1910) as described above. As another example, the number of bits of the timing offset field in the A-IoT DCI format may be fixed and may not be limited to a specific form.

[0288] Within the A-IoT DCI format, an A-IoT Tx timing offset field can be set. The A-IoT Tx timing offset field is K AIoT or K R2D may be set to a value, but may not be limited to that term. Referring to FIG. 19, the A-IoT Transmission Timing Offset field indicates the A-IoT transmission timing at which the leader (1910) can first transmit an A-IoT signal, using a timing offset value (K AIoT or K R2D ) can be directed. Here, the leader (1910) sets a timing offset value (K) based on the slot (slot n) in which the PDCCH including the A-IoT DCI format is received. AIoT or K R2D) can indicate that R2D transmission is possible thereafter. The offset value indicated by the A-IoT transmission timing offset field value can indicate the number of slots based on at least one of a slot offset based on the SCS (subcarrier spacing) of the downlink or uplink BWP (bandwidth part) set for the corresponding terminal (i.e., the leader), a slot offset based on the A-IoT SCS, and an A-IoT chip offset value based on the chip duration set for the A-IoT. For example, in order to indicate the A-IoT transmission timing at which the leader (1910) can perform the A-IoT transmission first, the timing offset value may be indicated by further considering the number of OFDM (orthogonal frequency division multiplexing) symbols based on one of the above-described SCS values. Here, a candidate timing offset value may be set to the leader (1910) through an upper layer. Alternatively, the candidate timing offset value may be set to a predetermined value in the leader (1910). The leader (1910) can perform transmission based on a timing offset value indicated through the A-IoT transmission timing offset field among candidate timing offset values.

[0289] For example, the upper layer parameter (egAIoT-DCI-ToAIoT-R2D-Trans) can set multiple candidate offset values ​​to the reader (1910) by the upper layer. In addition, an A-IoT resource pool (A-IoT time / frequency resource pool) can be set to the reader (1910). The reader (1910) can perform an actual R2D (or D2R) transmission in at least one of the first A-IoT transmission slot, chip, and OFDM index indicated by the timing offset value in the A-IoT DCI format within the set A-IoT resource pool. As another example, at least one of the first A-IoT transmission slot, chip, and OFDM index indicated by the timing offset value in the A-IoT DCI format can indicate a time before the time at which an actual A-IoT transmission is performed within the A-IoT resource pool set to the reader (1910). The A-IoT transmission timing offset value may indicate a position based on at least one of the associated slot, A-IoT slot, chip, and OFDM for R2D transmission by the reader (1910), and the reader (1910) may perform the A-IoT transmission after that position.

[0290] For example, the A-IoT transmission timing offset value may only indicate possible A-IoT transmission start positions based on slot boundaries. Here, the actual R2D transmission start point may be determined by considering at least one of the A-IoT time resource pool information related to the slot and the radio resource information that is determined (or set) to enable only A-IoT wireless transmission channel transmission. Specifically, the actual R2D transmission start point by the leader (1910) may not be aligned with the slot boundary, but may be determined at an arbitrary point in the slot. For example, there may be resources in the slot that cannot be used for the A-IoT wireless transmission channel, and the resources may also be used for other purposes. Therefore, the leader (1910) needs to determine the actual R2D transmission start point based on decisions that take radio resource selection into account. However, even in the above-described case, the R2D transmission start point may be aligned with the OFDM symbol boundary in consideration of the influence of interference.

[0291] As another example, an A-IoT Tx chip / OFDM symbol offset field may be considered within the A-IoT DCI format. The A-IoT Tx chip / OFDM symbol offset field value is K AIoT_offset#2 or K R2D_offset#2 may be, but may not be limited to the term. Here, the slot indicated by the A-IoT transmission timing offset value in the A-IoT DCI format may be the first slot in which A-IoT transmission is possible within the A-IoT resource pool. However, the actual A-IoT transmission (e.g. R2D) may start at one OFDM symbol boundary (or chip boundary) as the middle point of the slot. Therefore, the base station (1920) may use an additional timing offset value (K) to indicate the exact A-IoT transmission time to the reader (1910). AIoT_offset#2 or K R2D_offset#2) can be provided within the A-IoT DCI format through the A-IoT transmission chip / OFDM symbol offset field as a separate field. However, the field may not be limited to the above-described name.

[0292] In Fig. 19, the above-described K is used to indicate the A-IoT transmission point. AIoT_offset#2 or K R2D_offset#2 The value can indicate the number of chips (or OFDM) symbols based on the A-IoT SCS-based chip duration (or OFDM symbol duration). K AIoT_offset#2 The value is also a parameter that indicates slot timing (K AIoT ) can be provided to the leader (1910) by upper layer signaling of the base station. As another example, the leader (1910) can be provided with multiple K AIoT_offset#2 The value can be preset and is not limited to a specific form. Here, the size of the A-IoT transmission chip / OFDM symbol offset field in the A-IoT DCI format is candidate K AIoT_offset#2 can be determined by the value. As another example, the size of the A-IoT transmission chip / OFDM symbol offset field in the A-IoT DCI format can be determined by the candidate K AIoT_offset#2 It can be a fixed value regardless of the value. As described above, multiple candidates K AIoT_offset#2 One of the values ​​may be indicated via the A-IoT Transmit Chip / OFDM Symbol Offset field within the A-IoT DCI format, thereby indicating the actual A-IoT transmission point in time within the slot.

[0293] Here, if the above-mentioned field is not defined in the A-IoT DCI format, K AIoTThe exact transmission point of the A-IoT by the leader (1910) in the middle of the slot indicated by may be determined from the resources excluding the OFDM symbol / chip duration allocated for other predetermined usages (e.g. Tx-Rx switching, CW reception, AGC, Backscattering) and the pre-configured upper layer parameters indicating the resource area that cannot be used for A-IoT physical channel transmission. That is, K AIoT_offset#2 The value may not be included within the A-IoT DCI format and may not need to be signaled via the A-IoT DCI format.

[0294] For example, if the A-IoT transmission chip / OFDM symbol offset field value within the A-IoT DCI format is not defined within the DCI format, the A-IoT channel transmission timing (e.g., the first slot / chip / OFDM symbol) can be determined by the following mathematical expression 9 or mathematical expression 10.

[0295]

[0296] [Equation 9]

[0297]

[0298] [Equation 10]

[0299]

[0300]

[0301] In equations 9 and 10, is the start time of the DL slot in which the proposed A-IoT DCI format (PDCCH) is transmitted, may be a TA (timing advance) value corresponding to the TAG (timing advance group) of the serving cell where the DCI is received. As another example, if the TA value is not considered when determining the A-IoT transmission timing, can be 0. Also, is at least one of the number of slots, chips and OFDM symbols indicated by the A-IoT DCI format, may be at least one of the chips and OFDM symbols indicated by the A-IoT DCI format. However, If the parameter associated with is not used, its value may be 0. Also, is the slot duration (or the duration of at least one of the chip and OFDM symbol), may be the duration of at least one of a chip and an OFDM symbol.

[0302] As another example, K through the control field described above and Table 14 below AIoT , the start time of R2D transmission can be indicated by a method of determining the Start and Length values. FIG. 20 is a diagram illustrating a method of determining S and L values ​​based on a chip time interval applied to the present disclosure. Referring to FIG. 20, K is indicated through the A-IoT DCI of the PDCCH. AIoT , start and length values ​​can be indicated. In Fig. 20, K AIoT can be in slot units, and the start and length units can indicate the start and end of the R2D physical channel based on chip time intervals. The start and length units may not be limited to slots and chip time intervals, and may also be indicated by other time intervals such as OFDM symbol intervals, physical time units (ms or us, etc.), and other units. In Fig. 20, the time resource allocation of R2D channel transmission transmitted across two slots can be determined based on at least one of the number and index of chip time intervals. The start time when the A-IoT transmission is actually performed by the leader (2010) is K AIoTThe number can be determined by indicating the start and length units based on the slot boundary indicated by .

[0303] Another example is the timing offset (K AIoT ) can be set to correspond to the number of slots (chips), the starting OFDM symbol index (or the starting chip index), and the OFDM symbol length. These values ​​can be indicated through a specific field in the A-IoT DCI format as one or more values.

[0304] Specifically, referring to Table 14 below, when a row index is indicated through a specific field within the A-IoT DCI format, the related values ​​(K AIoT , Start, Length) can be indicated at once. Here, the above-mentioned values ​​can be indicated based on at least one of slot, chip, and OFDM symbol. In Table 14, the related values ​​(K AIoT , Start, Length) can be a predefined value (default) or a value set by a higher layer. However, Table 14 is only an example, and ultimately, a row index is indicated through a specific field in the A-IoT DCI format, and the related values ​​(K) corresponding to the row index AIoT , Start, Length) can be finally directed. For example, it may be possible to determine the D2R transmission timing through a row index in a specific field within the A-IoT DCI format, which will be described later.

[0305] [Table 14]

[0306]

[0307]

[0308] As another example, the S and L values ​​can be indicated as in Equation 11 below by utilizing the SLIV (start length indicator value) value rather than the form in Table 14. Here, the SLIV value is indicated by K through another field in the A-IoT DCI format. AIoT It can be indicated with a value. For example, the start (S) and length (L) values ​​described above can be determined based on the SLIV value and are not limited to a specific form.

[0309] [Equation 11]

[0310]

[0311]

[0312] Although the above description is based on the case where R2D only transmission is performed, the same can be applied to the case where D2R only transmission is performed, and the specific details can be the same as described above. That is, A-IoT transmission can be performed by indicating a timing offset value through the A-IoT DCI format, but other details can be the same. However, in the case of D2R only transmission, the A-IoT DCI format can be transmitted from the base station to the A-IoT device, but it may not be limited thereto.

[0313]

[0314] As another example, referring to FIGS. 19 and 20, a timing offset (K) indicating uplink or downlink transmission timing in a Uu link UL) may be determined based on which uplink or downlink transmission is performed. Here, A-IoT data transmission and reception may be performed based on at least one of R2D and D2R at the same timing as the timing at which uplink or downlink transmission is performed. For example, referring to FIGS. 19 and 20 , the timing at which at least one of R2D or D2R is performed may be determined based on a timing offset in a PDCCH for scheduling A-IoT or the A-IoT leader / device itself, and the timing at which R2D or D2R is performed may be the same as the transmission timing of at least one of the uplink and downlink on the Uu link. As a result, a collision between the Uu link channel transmission and reception and the A-IoT link channel transmission and reception may occur within one A-IoT leader (intermediate UE) in at least one of the corresponding slot, OFDM symbol, and chip duration. That is, in an A-IoT system based on a wireless communication system (e.g., NR system), a conflict may occur between at least one of the existing PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUSCH (physical uplink shared channel), and PUCCH (physical uplink control channel) that uses Uu link (downlink / uplink) resources and at least one of R2D and D2R during transmission and reception of an A-IoT device in the same time interval (slot, OFDM symbol, or chip duration).

[0315] As a more specific example, the timing offset (K) of the uplink transmission UL) based UL transmission is delayed and overlaps with the A-IoT link (or A-IoT transmission / reception), a collision may occur. As another example, a collision may occur when a configured grant based SPS (semi-persistent scheduling) based UL transmission is performed and the UL transmission timing overlaps with the A-IoT link (or A-IoT transmission / reception). As another example, when the A-IoT transmission is scheduled based on a fixed repetition interval (sparse or dense period), the A-IoT transmission and the uplink transmission may overlap, resulting in a collision. In addition, other collision situations may be considered and may not be limited to those described above.

[0316] Considering the above, a method may be needed to minimize resource conflicts between A-IoT transmission and reception (at least one of R2D and D2R) and Uu link physical channel / control signal transmission and reception, and to prevent QoS loss. That is, a case in which a conflict occurs between at least one of A-IoT device-based transmission and reception and at least one of Uu link transmission and reception may be considered, and for convenience of explanation, this is referred to as A-IoT transmission and reception and Uu link transmission and reception below, but this may include the above-described cases.

[0317]

[0318] For example, if Uu link transmission and reception collide with A-IoT transmission and reception, a method of avoiding the collision by dropping or deferring A-IoT transmission and reception can be considered. If a collision between Uu link transmission and reception and A-IoT transmission and reception is detected, A-IoT transmission and reception (D2R or R2D) can be dropped or deferred for a certain period of time. As a specific example, if a random access procedure and A-IoT transmission and reception are performed at the same timing in a terminal and a collision occurs, the terminal can give priority to the random access signal and drop or defer A-IoT transmission and reception. Here, the dropping and delay of A-IoT transmission and reception can be determined by considering the characteristics of A-IoT service (or traffic (e.g., inventory, command). In the above example, only random access signals are mentioned, but the same operation can be applied to procedures related to other common control signals / channels (e.g., paging, initial access, measurement, mobility).

[0319] As another example, if Uu link transmission / reception and A-IoT transmission / reception collide, the conflict can be resolved based on service priority. Specifically, priority (or priority) can be set based on the traffic type and importance of A-IoT transmission / reception and Uu link transmission / reception, and the conflict can be resolved based on this. As a specific example, Critical A-IoT Tx, such as a command response, can be protected first. That is, if a Critical A-IoT Tx, such as a command response, collides with a Uu link transmission / reception, the Critical A-IoT Tx, such as a command response, is performed, and the Uu link transmission / reception can be dropped or postponed. As another example, if URLLC (ultra reliable low latency communications) transmission and A-IoT transmission / reception collide due to Uu link transmission / reception, URLLC transmission may be performed and A-IoT transmission / reception may be dropped or postponed. In terms of priority (or priority), the priority of D2R transmission as a command in A-IoT transmission / reception may be higher than that of Uu link transmission / reception. In addition, uplink transmission including HARQ-ACK may be higher in priority than A-IoT transmission / reception, but this may not be limited to the embodiment.

[0320] As another example, if a collision occurs between HARQ-ACK and other essential transmissions and A-IoT transmission / reception, HARQ-ACK and other essential transmissions may be performed first, and A-IoT transmission / reception may be dropped or postponed. Specifically, if HARQ-ACK, SR (scheduling request), and other essential control channels (e.g., PUCCH) collide with A-IoT transmission / reception due to Uu link transmission / reception, Uu link transmission / reception may be performed, and A-IoT transmission / reception may be dropped or postponed.

[0321] As another example, if Uu link transmission and reception collide with A-IoT transmission and reception, A-IoT transmission and reception may be postponed based on timing indication information of the Uu link. Specifically, A-IoT transmission and reception timing may be shifted to a non-conflicting section based on scheduling or timing information provided in the PDCCH or system information on the Uu link. For example, A-IoT transmission and reception timing may be shifted to a non-conflicting section based on semi-static or dynamic scheduling.

[0322] As another example, when Uu link transmission and reception collide with A-IoT transmission and reception, Uu link transmission and reception and A-IoT transmission and reception can be performed based on time division multiplexing (TDM) at the OFDM symbol level. For example, within the same slot, a specific OFDM symbol or chip duration can be set as a guard interval dedicated to A-IoT transmission, and the remaining OFDM symbols or chip durations can be set as guard intervals dedicated to Uu link transmission and reception. With the above-described structure, the range of the TDM guard interval can be flexibly configured.

[0323] Based on the above-described method, when a collision occurs between Uu link transmission and reception and A-IoT transmission and reception, the collision can be resolved, thereby minimizing the impact on the overall system performance.

[0324]

[0325] Next, we can consider a case where control information for R2D transmissions and corresponding D2R transmissions is transmitted from the base station to the leader. That is, the A-IoT DCI format can indicate the transmission timing for both R2D and D2R, respectively.

[0326] FIG. 21 is a diagram illustrating a method for indicating A-IoT timing via DCI in the case of R2D and D2R applied to the present disclosure. Referring to FIG. 21, R2D and D2R transmission and reception timing can be indicated in an A-IoT DCI format. The A-IoT DCI format may further include control information for determining D2R transmission timing in addition to the control information for determining the R2D transmission timing described above. For example, the R2D transmission timing determination method described above may be applied to the method according to FIG. 19 or FIG. 20. In addition, the R2D transmission timing determination may be determined by a method other than the method described above, and may not be limited to a specific form. The transmission timing of D2R transmission performed after R2D transmission may be determined based on the control information indicated in the A-IoT DCI format.

[0327] For example, the A-IoT Tx timing offset field is used as the K D2R A field set to a value can be considered. The field can be defined in the A-IoT DCI format to indicate the D2R transmission timing, and the base station (2120) can first indicate the A-IoT D2R transmission timing that is possible to the reader (2110) through the A-IoT DCI format using a timing offset value (K D2R ) can be transmitted.

[0328] For example, the first A-IoT D2R transmission timing is indicated by a timing offset value (K). D2R ) is a timing offset value (K) from the associated R2D transmission start point (or associated R2D transmission end point) to the slot of the D2R transmission start point (or D2R transmission end point) (or to the start or end point of the actual D2R transmission). D2R) can be directed through the A-IoT DCI format.

[0329] Referring to FIG. 21, K is defined as the A-IoT Tx timing offset field within the A-IoT DCI format. R2D The slot at which the leader (2110) can perform R2D transmission can be indicated through the value. For example, the time at which the leader (2110) performs actual R2D transmission is determined by an additional timing offset value based on the slot. It may be determined through, but may not be limited to, the A-IoT Tx timing offset field in the A-IoT DCI format. D2R The A-IoT device (2130) can indicate a slot in which D2R transmission is possible or when actual D2R transmission starts based on a slot in which R2D transmission can be performed.

[0330] Additionally, as an example, the start and length values ​​related to D2R transmission can be indicated through the A-IoT DCI format similar to Table 14 described above. In Fig. 21, K D2R The start and length units may be slot units, and the start and length units may indicate the start and end of the D2R physical channel based on chip time intervals. The start and length units may not be limited to slot and chip time intervals, and may also be indicated in other time intervals such as OFDM symbol intervals, physical time units (ms or us, etc.), and other units. The start time when the A-IoT transmission is actually performed by the A-IoT device (2130) to the reader (2110) is K D2R The number can be determined by starting and length units based on the slot boundary indicated by . As another example, the timing offset (KD2R ) can be set to correspond to the number of slots (chips), the starting OFDM symbol index (or the starting chip index), and the OFDM symbol length. The values ​​can be indicated through a specific field in the A-IoT DCI format as one or more values. For example, a specific field in the A-IoT DCI format can indicate a row index, and can be indicated in a form similar to Table 14, but is not limited to the embodiment.

[0331] FIG. 22 is a diagram illustrating a method for indicating A-IoT timing via DCI in the case of R2D and D2R applied to the present disclosure. Referring to FIG. 22, R2D and D2R transmission and reception timing can be indicated in an A-IoT DCI format. The A-IoT DCI format may further include control information for determining D2R transmission timing in addition to the control information for determining the R2D transmission timing described above. For example, the R2D transmission timing determination method described above may be applied to the method according to FIG. 19 or FIG. 20. In addition, the R2D transmission timing determination may also be determined by a method other than the method described above, and may not be limited to a specific form. The transmission timing of D2R transmission performed after R2D transmission may be determined based on the control information indicated in the A-IoT DCI format.

[0332] For example, the A-IoT Tx timing offset field is used as the K D2R A field set to a value can be considered. The field can be defined in the A-IoT DCI format to indicate the D2R transmission timing, and the base station (2220) can first indicate the A-IoT D2R transmission timing that is possible to the reader (2210) through the A-IoT DCI format using a timing offset value (K D2R) can be transmitted. For example, based on the slot (slot n) in which the PDCCH including the A-IoT DCI format is received (i.e., the PDCCH transmission slot), the starting point of the D2R transmission (or the starting end point of the D2R transmission) is overlapped with the slot, or the starting point of the actual D2R transmission (the ending point of the D2R transmission) is the timing offset value (K) within the A-IoT DCI format. D2R ) can be directed through.

[0333] Referring to Figure 22, K is defined as the A-IoT Tx timing offset field within the A-IoT DCI format. R2D The slot at which the leader (2210) can perform R2D transmission can be indicated through the value. For example, the time at which the leader (2210) performs actual R2D transmission is determined by an additional timing offset value based on the slot. It may be determined through, but may not be limited to, the A-IoT Tx timing offset field in the A-IoT DCI format. D2R The A-IoT device (2130) can indicate a slot in which D2R transmission is possible or a point in time when actual D2R transmission starts based on a slot (slot n) in which a PDCCH including an A-IoT DCI format is received that is not a slot in which R2D transmission can be performed.

[0334] Additionally, as an example, the start and length values ​​related to D2R transmission can be indicated through the A-IoT DCI format similar to Table 14 described above. In Fig. 22, K D2RThe start and length units may be slot units, and the start and length units may indicate the start and end of the D2R physical channel based on chip time intervals. The start and length units may not be limited to slot and chip time intervals, and may also be indicated in other time intervals such as OFDM symbol intervals, physical time units (ms or us, etc.), and other units. The start time when the A-IoT transmission is actually performed by the A-IoT device (2230) to the reader (2210) is K D2R The number can be determined by starting and length units based on the slot boundary indicated by . As another example, the timing offset (K D2R ) can be set to correspond to the number of slots (chips), the starting OFDM symbol index (or the starting chip index), and the OFDM symbol length. The values ​​can be indicated through a specific field in the A-IoT DCI format as one or more values. For example, a specific field in the A-IoT DCI format can indicate a row index, and can be indicated in a form similar to Table 14, but is not limited to the embodiment.

[0335] FIG. 23 is a diagram illustrating a method for indicating A-IoT timing via DCI in the case of R2D and D2R applied to the present disclosure. Referring to FIG. 23, R2D and D2R transmission and reception timing can be indicated in an A-IoT DCI format. The A-IoT DCI format may further include control information for determining D2R transmission timing in addition to the control information for determining the R2D transmission timing described above. For example, the R2D transmission timing determination method described above may be applied to the method according to FIG. 19 or FIG. 20. In addition, the R2D transmission timing determination may also be determined by a method other than the method described above, and may not be limited to a specific form. The transmission timing of D2R transmission performed after R2D transmission may be determined based on the control information indicated in the A-IoT DCI format.

[0336] For example, the A-IoT Tx timing offset field is used as the K D2R A field set to a value can be considered. The field can be defined in the A-IoT DCI format to indicate the D2R transmission timing, and the base station (2320) can first indicate the A-IoT D2R transmission timing that is possible to the reader (2210) through the A-IoT DCI format using a timing offset value (K D2R ) can be transmitted. For example, a slot in which a D2R transmission can be performed (or the actual start point at which a D2R transmission is performed or the actual end point at which a D2R transmission is performed) relative to the start point of a previous associated R2D transmission (or the end point of an R2D transmission) is a timing offset value (K D2R ) can be directed through the A-IoT DCI format.

[0337] Referring to FIG. 23, K is defined as the A-IoT Tx timing offset field within the A-IoT DCI format. R2D The slot at which the leader (2310) can perform R2D transmission can be indicated through the value. For example, the time at which the leader (2310) performs actual R2D transmission is determined by an additional timing offset value based on the slot. can be determined through. Here, K is defined as the A-IoT Tx timing offset field within the A-IoT DCI format. D2R The A-IoT device (2130) can indicate a slot in which D2R transmission is possible or when actual D2R transmission begins based on the time at which R2D transmission is actually performed.

[0338] Additionally, as an example, the start and length values ​​related to D2R transmission can be indicated through the A-IoT DCI format similar to Table 14 described above. In Fig. 21, K D2R The start and length units may be slot units, and the start and length units may indicate the start and end of the D2R physical channel based on chip time intervals. The start and length units may not be limited to slot and chip time intervals, and may also be indicated in other time intervals such as OFDM symbol intervals, physical time units (ms or us, etc.), and other units. The start time when the A-IoT transmission is actually performed by the A-IoT device (2330) to the reader (2310) is K D2R The number can be determined by starting and length units based on the slot boundary indicated by . As another example, the timing offset (K D2R) can be set to correspond to the number of slots (chips), the starting OFDM symbol index (or the starting chip index), and the OFDM symbol length. The values ​​can be indicated through a specific field in the A-IoT DCI format as one or more values. For example, a specific field in the A-IoT DCI format can indicate a row index, and can be indicated in a form similar to Table 14, but is not limited to the embodiment.

[0339] FIG. 24 is a diagram illustrating a method for indicating A-IoT timing via DCI when performing R2D and D2R transmissions applicable to the present disclosure.

[0340] Referring to FIG. 24, a contention window start point for a D2R transmission is determined based on at least one of a slot (FIG. 21) including a previous associated R2D transmission start point (or an R2D transmission end point), a slot (i.e., a PDCCH transmission slot) (FIG. 22) in which a PDCCH including an A-IoT DCI format is received, and an actual start point of a previous associated R2D transmission (or an actual end point of a related R2D transmission) (FIG. 23) and a timing offset value (K) of an A-IoT transmission timing offset field. D2R ) can be indicated in A-IoT DCI format.

[0341] That is, an operation for competitively allocating resources for D2R transmission by multiple A-IoT devices can be performed within a contention window determined based on the PDCCH / R2D transmission timing prior to the operation. For example, when a slotted-ALOHA-based resource allocation method is used (or set) for D2R transmission of an A-IoT device (2430), the start of the contention window (resource allocation window) can be indicated through signaling for timing determination. In addition, the end point of the contention window can be indicated or set by at least one of other upper layer signaling, DCI signaling, R2D / D2R transmission-related control information value, and a pre-determined value for the window size.

[0342] Specifically, when D2R transmission resources are determined based on slotted-ALOHA, the timing offset value (K) is set to the start of the contention window for D2R transmission. D2R ) can be indicated in the A-IoT DCI format. That is, in the case where multiple A-IoT devices perform D2R transmission, and in the case where D2R transmission is performed on a contention basis in slot units within a contention window, a timing offset value (K) until the start of the contention window D2R ) can be indicated in the A-IoT DCI format. On the other hand, if the D2R transmission resource is not determined based on slotted-ALOHA, the D2R transmission resource can be determined by the above-described FIGS. 21 to 23.

[0343] For example, the timing offset value within the A-IoT DCI format may be indicated based on at least one of a slot offset based on the SCS of the downlink BWP or uplink BWP set for the corresponding terminal, a slot offset based on the A-IoT SCS, and an A-IoT chip offset based on the chip duration set for A-IoT. In addition, it may be considered to additionally consider and indicate the number of OFDM symbols within a slot based on one of the above-described SCS values. Here, as described above, one of the candidate offset values ​​provided to the leader in advance by the upper layer setting may be indicated through the timing offset field within the A-IoT DCI format.

[0344] For example, the upper layer parameter (egAIoT-DCI-ToAIoT-R2D-D2R-Trans) can set multiple candidate offset values ​​to the reader (2410) by the upper layer. In addition, an A-IoT resource pool (A-IoT time / frequency resource pool) can be set to the reader (2410). The reader (2410) can perform actual R2D and D2R transmission in at least one of the first A-IoT transmission slot, chip, and OFDM index indicated by the timing offset value in the A-IoT DCI format within the set A-IoT resource pool. As another example, at least one of the first A-IoT transmission slot, chip, and OFDM index indicated by the timing offset value in the A-IoT DCI format can indicate a time before the time at which actual A-IoT transmission is performed within the A-IoT resource pool set to the reader (2410). The A-IoT transmission timing offset value may indicate a location based on at least one of the associated slot, A-IoT slot, chip, and OFDM for R2D and D2R transmissions, where R2D and D2R transmissions may be performed.

[0345] The A-IoT transmission timing offset value may indicate at least one of the associated slot, A-IoT slot, chip, and OFDM symbol position for D2R transmission, but the value may be an indication of a potential starting position. Here, the exact D2R transmission start point may be determined by the reader (2410) based on the related A-IoT time resource pool information and the start of the D2R transmission. The actual D2R transmission start point may not be aligned with the slot boundary, but the transmission may be started at any point within the slot by the reader, and the actual D2R transmission point may be different as described above. However, considering the influence of interference, the DR2 transmission point may be performed aligned with the OFDM symbol boundary within the slot. Referring to FIG. 24, the timing offset value (K) of the A-IoT transmission timing offset field is determined based on the start point at which the actual R2D transmission is started by the reader (2410). D2R ) may be applied, which may determine the starting point of the contention window within which DR2 transmission may be possible.

[0346] Figure 25 is a diagram illustrating a method of indicating A-IoT timing through DCI in the case of R2D and D2R applied to the present disclosure. A-IoT transmission timing offset value (K) in the DCI format DSR ) may be the first slot within the A-IoT resource pool. However, as described above, the actual A-IoT transmission (e.g., D2R) may start at any point within the slot, at an OFDM symbol boundary (or chip boundary). Therefore, the base station (2520) may include an offset value (K) in the A-IoT transmission chip / OFDM symbol offset field as an additional timing offset value to indicate the exact A-IoT transmission time to the reader (2510). D2R_offset#2 ) can be indicated. Here, the offset value (K D2R_offset#2) may not be limited to the term. Referring to FIG. 25, the offset value (K) described above is used to indicate the actual exact A-IoT transmission time. D2R_offset#2 ) value can indicate at least one of the chips (or OFDM symbol number) based on the A-IoT SCS-based chip duration (or OFDM symbol duration). Here, the corresponding offset value (K D2R_offset#2 ) is also a parameter for slot timing instructions (K DSR ) can be provided to the leader (2510) by upper layer signaling of the base station (2520). Therefore, multiple candidate offset values ​​(K D2R_offset#2 ) are set to the leader (2510) by the upper layer, the size of the corresponding field in the A-IoT DCI format is a multiple candidate offset value (K D2R_offset#2 ) can be determined by the size. As another example, the field within the A-IoT DCI format may have a predetermined size and may not be limited to a specific form. The offset value (K D2R_offset#2 ) can be set by the upper layer according to the size of the A-IoT DCI format. One of the values ​​set in this way can be indicated through the A-IoT transmission chip / OFDM symbol offset field in the A-IoT DCI format, and the reader (2510) can recognize the actual A-IoT transmission time through this.

[0347] Here, if the A-IoT transmission chip / OFDM symbol offset field within the A-IoT DCI format is not defined within the A-IoT DCI format, the reader shall DSRIn the middle of the slot indicated by, the A-IoT may determine that the A-IoT transmission is possible in the resources excluding the OFDM symbol / chip duration allocated for other predetermined usages (e.g. Tx-Rx switching, CW reception, AGC, Backscattering) and the pre-configured upper layer parameters indicating the resource area that cannot be used for A-IoT physical channel transmission. In the above case, the offset value (K D2R_offset#2 ) value may not need to be signaled separately via the A-IoT DCI format. Here, the A-IoT D2R / CW start timing (e.g., the start first slot / chip / OFDM symbol) indicated by the proposed signaling may consider the following mathematical expressions 12 to 15.

[0348] [Equation 12]

[0349]

[0350] [Equation 13]

[0351]

[0352] [Equation 14]

[0353]

[0354] [Equation 15]

[0355]

[0356] In mathematical expressions 12 to 15 is the start time of the DL slot in which the A-IoT DCI format (PDCCH) is transmitted, may be the start time of a slot that overlaps with a previous R2D transmission. Or, may be the actual start time of the previous R2D transmission, may be a TA value corresponding to the TAG of the serving cell where the DCI is received. For example, if the TA value is not considered when determining the A-IoT transmission timing, can be 0. Also, may be a value indicated based on at least one of the number of slots, chips, and OFDM symbols indicated by the A-IoT DCI format. In addition, may be at least one of the number of chips and OFDM symbols indicated by the A-IoT DCI format. For example, If is not used, can be 0. Also, may be the duration of at least one of a slot, a chip, and an OFDM symbol. As another example, may be physical time (ms, us, etc.), but is not limited to the given embodiment. In addition, In the case of backscattering-based D2R transmission or energy harvesting, this may be a time to provide a margin for additional transmission delay. Here, if the above considerations do not apply, the value may be 0. In addition, may be the duration for at least one of the chips and OFDM symbols. For example, This slot duration (= ) if can be used as a chip or OFDM symbol duration. Here, the timing offset value ( ) may be the starting point of a competition window.

[0357] In addition, as an example, although FIGS. 19 to 25 describe cases where an A-IoT time resource pool for R2D transmission and an A-IoT time resource pool for D2R transmission are respectively set, the A-IoT time resource pool for R2D transmission and the A-IoT time resource pool for D2R transmission may be set as a single resource pool. That is, a single A-IoT time resource pool for A-IoT transmission may be set, and at least one of R2D transmission and D2R transmission may be performed within the A-IoT time resource pool, and is not limited to a specific form.

[0358] As another example, other DCI formats for A-IoT may be considered. For example, the aforementioned A-IoT DCI format may include not only control information indicating A-IoT transmission timing, but also other control information, which may be transmitted from the base station to the leader, thereby enabling the leader to perform A-IoT communication with the A-IoT device. Specifically, signaling information for leader selection by the base station may be included as control information. That is, the base station may signal which UE will operate as the leader. Additionally, uplink time-frequency domain resource indication (UL time-frequency domain resource indication) information may be included as control information. For example, in an in-band scenario, scheduling information for other uplink resource allocations may be provided as additional information. As another example, at least one of an R2D time-frequency domain resource indication, a D2R time-frequency domain resource indication, an A-IoT device identifier indication, and an A-IoT device type indication may be included in the control information. The A-IoT device type may indicate whether it is type 1 / 2a or 2b, and may then cause a specific A-IoT device (or group of A-IoT devices) corresponding to the control information indicated by the leader to perform control appropriate for the corresponding type.

[0359] Additionally, the control information may include information on at least one of MCS, coding rate, modulation type, transport block size (TBS), repetitions, A-IoT device ID (or A-IoT device group ID), cast type, leader ID, message type, payload size, energy harvesting indication, and contention window transmission.

[0360] For example, the message type may be an inventory or command type message. As another example, the message type may be a random access (RA) related message, but may not be limited to a specific form. In addition, the energy harvesting indication may be an indication on whether to perform energy harvesting, and the contention window indication may instruct the leader on whether to transmit on CW. At least one of the above-described information may be defined and used within the A-IoT DCI format. Some control information may be determined in advance. As another example, some control information may be indicated by upper layer signaling or L1 signaling (including NR DCI). Here, some R2D control information may vary depending on the device type. As another example, the R2D control information may be applied equally to all types. If the control information has a fixed length, the control information may be transmitted through L1 signaling. On the other hand, if the control information does not have a fixed length, the control information may be transmitted through upper layer signaling (e.g., MAC CE, RRC). The base station can also provide wake-up related information for the device to the leader via L1 signaling.

[0361] FIG. 26 is a flowchart illustrating a method for indicating A-IoT timing via DCI in the R2D only case applied to the present disclosure. Referring to FIG. 26, a leader may receive a first DCI configured in a first DCI format from a base station via a PDCCH (S2610). Here, the first DCI format may be the aforementioned A-IoT DCI format, and the A-IoT DCI format may include A-IoT transmission timing indication information. Thereafter, the leader can transmit an A-IoT signal to the A-IoT device through the R2D link based on the A-IoT transmission timing indication information. (S2620) Here, the first DCI includes a first identifier indicating an A-IoT transmission type, and if the first identifier is the first value, only R2D transmission is performed from the leader to the A-IoT device, and if the first identifier is the second value, after the R2D transmission from the leader to the A-IoT device, a D2R transmission corresponding to the R2D transmission may be further performed, as described above. For example, if the first identifier is the first value, the A-IoT transmission timing indication information in the first DCI may include a first timing offset. That is, the first identifier may indicate R2D only transmission, and in the case described above, the first timing offset may indicate a slot in which R2D transmission is performed based on a slot in which the first DCI is transmitted. As another example, the A-IoT transmission timing indication information within the first DCI may further include a second timing offset along with the first timing offset. Here, the second timing offset may indicate a transmission point in time at which the R2D transmission is performed within the slot from the boundary of the slot at which the R2D transmission is performed, as described above.As another example, the A-IoT transmission timing indication information within the first DCI further includes a first timing offset and start point and length information at which R2D transmission is performed, and based on the start point and length information, a transmission time point at which R2D transmission within a slot is performed from the boundary of the slot can be indicated, as described above.

[0362] Fig. 27 is a flowchart illustrating a method for indicating A-IoT timing via DCI in the R2D only case applied to the present disclosure. Referring to Fig. 27, a leader may receive a first DCI configured in a first DCI format from a base station via a PDCCH (S2710). Here, the first DCI format may be the above-described A-IoT DCI format, and the A-IoT DCI format may include A-IoT transmission timing indication information. Thereafter, the leader can transmit an A-IoT signal to the A-IoT device through the R2D link based on the A-IoT transmission timing indication information. (S2720) Thereafter, the leader can receive an A-IoT signal from the A-IoT device through the D2R link based on the A-IoT transmission timing indication information. (S2730) Here, the first DCI includes a first identifier indicating an A-IoT transmission type, and if the first identifier is the first value, only R2D transmission is performed from the leader to the A-IoT device, and if the first identifier is the second value, after the R2D transmission from the leader to the A-IoT device, a D2R transmission corresponding to the R2D transmission may be further performed, as described above. For example, if the first identifier is the second value, the A-IoT transmission timing indication information in the first DCI may include a first timing offset and a second timing offset as timing offsets of the R2D transmission. Additionally, the A-IoT transmission timing indication information within the first DCI may further include a third timing offset as a timing offset of the D2R transmission. The first timing offset may indicate a slot in which R2D transmission is performed based on a slot in which the first DCI transmitted via the PDCCH is transmitted, and the second timing offset may indicate a transmission time point in which R2D transmission is performed within the slot from the boundary of the slot in which R2D transmission is performed.

[0363] Here, as an example, the third timing offset may indicate an actual D2R transmission time point within a slot or slots in which a D2R transmission is performed based on a slot in which an R2D transmission is performed, which may be as shown in FIG. 21 described above. As another example, the third timing offset may indicate an actual D2R transmission time point within a slot or slots in which a D2R transmission is performed based on a slot in which the first DCI is transmitted, which may be as shown in FIG. 22. As another example, the third timing offset may indicate an actual D2R transmission time point within a slot or slots in which a D2R transmission is performed based on a time point in which an R2D transmission is performed, which may be as shown in FIG. 23. In addition, the third timing offset may indicate a start time point of a contention window in which at least one A-IoT device can perform a D2R transmission based on a slot in which the first DCI is transmitted, which may be as shown in FIG. 24. As another example, the A-IoT transmission timing indication information within the first DCI may further include a fourth timing offset together with the third timing offset, wherein the fourth timing offset may indicate a transmission point in time at which D2R transmission is performed within the slot from the boundary of the slot at which D2R transmission is performed, as illustrated in FIG. 25.

[0364] Figure 28 is a drawing showing a device configuration to which the present disclosure can be applied.

[0365] Referring to FIG. 28, a first device (2800) and a second device (2850) can communicate with each other. In this case, as an example, the first device (2800) may be a base station device, and the second device (2850) may be a terminal device. In another example, both the first device (2800) and the second device (2850) may be terminal devices. In another example, the first device (2800) and the second device (2850) may be satellite IAB nodes. In other words, the first device (2800) and the second device (2850) may be devices that communicate with each other based on NR-based communication, and are not limited to a specific form.

[0366] The first device (2800) may include a processor (2820), an antenna unit (2812), a transceiver (2814), and a memory (2816). The processor (2820) performs baseband-related signal processing and may include a higher layer processing unit (2830) and a physical layer processing unit (2840). The higher layer processing unit (2830) may process operations of a medium access control (MAC) layer, a radio resource control (RRC) layer, or higher layers. The physical layer processing unit (2840) may process operations of a physical (PHY) layer (e.g., uplink reception signal processing, downlink transmission signal processing). In addition to performing baseband-related signal processing, the processor (2820) may also control the overall operation of the first device (2800). The antenna unit (2812) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO (Multiple Input Multiple Output) transmission and reception. In addition, beamforming may be supported. The memory (2816) may store information processed by the processor (2820), software related to the operation of the first device (2800), an operating system, applications, etc., and may include components such as a buffer. The processor (2820) of the first device (2800) may be configured to implement the operation of the first device in the embodiments described in the present invention.

[0367] The second device (2850) may include a processor (2870), an antenna unit (2862), a transceiver (2864), and a memory (2866). For example, in the present invention, the second device (2850) may communicate with the first device (2800). The processor (2870) may perform baseband-related signal processing and may include a higher layer processing unit (2880) and a physical layer processing unit (2890). The higher layer processing unit (2880) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (2890) may process operations of a 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 (2870) may also control the overall operation of the second device (2850). The antenna unit (2862) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. In addition, it may support beamforming. The memory (2866) may store information processed by the processor (2870), software related to the operation of the second device (2850), an operating system, applications, etc., and may include components such as a buffer. The second device (2850) according to an example of the present invention may be associated with a vehicle. For example, the second device (2850) may be integrated into the vehicle, located in the vehicle, or located on the vehicle. In addition, the second device (2850) according to the present invention may be the vehicle itself. In addition, the second device (2850) according to the present invention may be at least one of a wearable terminal, an AV / VR, an IoT terminal, a robot terminal, and a public safety terminal.The terminal device (2850) to which the present invention is applicable may include any type of communication device that supports interactive services utilizing sidelink for services such as Internet access, service execution, navigation, real-time information, autonomous driving, and safety and risk diagnosis. Furthermore, any type of communication device capable of sidelink operation, such as an AR / VR device or sensor that performs relay operations, may be included.

[0368] Here, the vehicles / terminals to which the present invention is applied may include autonomous vehicles / driving terminals, semi-autonomous vehicles / driving terminals, non-autonomous vehicles / driving terminals, etc. Meanwhile, although the second device (2850) according to an 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 merely an example, and should not be construed as limiting the application of the present invention to the described example. In addition, the second device (2850) according to an example of the present invention may also include various types of communication devices capable of performing cooperation to support interactive services utilizing sidelink. That is, the second device (2850) may not only directly support interactive services utilizing sidelink, but may also be utilized as a cooperation device to support interactive services utilizing sidelink.

[0369] Here, the terminal device (2800) can receive a PDCCH from a base station, the first DCI configured in the first DCI format. For example, the terminal device (2800) can be the above-described leader, but is not limited thereto. The first DCI format can be the above-described A-IoT DCI format, and the A-IoT DCI format can include A-IoT transmission timing indication information. Thereafter, the terminal device (2800) can transmit an A-IoT signal to the A-IoT device via an R2D link based on the A-IoT transmission timing indication information. Here, the first DCI includes a first identifier indicating an A-IoT transmission type, and if the first identifier is the first value, only R2D transmission is performed from the reader to the A-IoT device, and if the first identifier is the second value, after the R2D transmission from the reader to the A-IoT device, a D2R transmission corresponding to the R2D transmission may be further performed, as described above. For example, if the first identifier is the first value, the A-IoT transmission timing indication information in the first DCI may include a first timing offset. That is, the first identifier may indicate R2D only transmission, and in the case described above, the first timing offset may indicate a slot in which the R2D transmission is performed based on a slot in which the first DCI is transmitted. As another example, the A-IoT transmission timing indication information in the first DCI may further include a second timing offset together with the first timing offset. Here, the second timing offset may indicate a transmission point in time at which R2D transmission is performed within a slot from the boundary of the slot where R2D transmission is performed, as described above. As another example, the A-IoT transmission timing indication information within the first DCI may further include a first timing offset and start point and length information at which R2D transmission is performed, and based on the start point and length information, a transmission point in time at which R2D transmission is performed within a slot from the boundary of the slot may be indicated, as described above.

[0370] For example, when the first identifier is the second value, the A-IoT transmission timing indication information in the first DCI may include a first timing offset and a second timing offset as timing offsets of R2D transmission. In addition, the A-IoT transmission timing indication information in the first DCI may further include a third timing offset as a timing offset of D2R transmission. The first timing offset may indicate a slot in which R2D transmission is performed based on a slot in which the first DCI transmitted through the PDCCH is transmitted, and the second timing offset may indicate a transmission time point in which R2D transmission is performed within the slot from a boundary of the slot in which R2D transmission is performed.

[0371] Here, as an example, the third timing offset may indicate an actual D2R transmission time point within a slot or slots in which a D2R transmission is performed based on a slot in which an R2D transmission is performed, which may be as shown in FIG. 21 described above. As another example, the third timing offset may indicate an actual D2R transmission time point within a slot or slots in which a D2R transmission is performed based on a slot in which the first DCI is transmitted, which may be as shown in FIG. 22. As another example, the third timing offset may indicate an actual D2R transmission time point within a slot or slots in which a D2R transmission is performed based on a time point in which an R2D transmission is performed, which may be as shown in FIG. 23. In addition, the third timing offset may indicate a start time point of a contention window in which at least one A-IoT device can perform a D2R transmission based on a slot in which the first DCI is transmitted, which may be as shown in FIG. 24. As another example, the A-IoT transmission timing indication information within the first DCI may further include a fourth timing offset together with the third timing offset, wherein the fourth timing offset may indicate a transmission point in time at which D2R transmission is performed within the slot from the boundary of the slot at which D2R transmission is performed, as illustrated in FIG. 25.

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

[0373] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer.

[0374] The various embodiments of the present disclosure are not intended to list all possible combinations but rather to illustrate 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.

[0375]

[0376] The above may also apply to other systems.

Claims

1. In the method of operation of a leader in an ambient-IoT (ambient-internet of things, A-IoT) system, A step in which the above leader receives a first DCI (downlink control information) format configured through a physical downlink control channel (PDCCH), wherein the first DCI includes A-IoT transmission timing indication information; and An operating method comprising a step of transmitting an A-IoT signal to an A-IoT device via an R2D (reader to device) link by the reader based on the A-IoT transmission timing indication information.

2. In paragraph 1, The above first DCI includes a first identifier indicating an A-IoT transmission type, If the first identifier is the first value, only R2D transmission is performed from the leader to the A-IoT device, An operating method in which, if the first identifier is a second value, after R2D transmission from the reader to the A-IoT device, a D2R (device to reader) transmission corresponding to the R2D transmission is further performed.

3. In paragraph 1, An operating method, wherein when the first identifier is the first value, the A-IoT transmission timing indication information in the first DCI includes a first timing offset, and the first timing offset indicates a slot in which the R2D transmission is performed based on a slot in which the first DCI is transmitted.

4. In paragraph 3, An operating method, wherein the A-IoT transmission timing indication information within the first DCI further includes a second timing offset together with the first timing offset, wherein the second timing offset indicates a transmission time point at which the R2D transmission is performed within the slot from the boundary of the slot at which the R2D transmission is performed.

5. In paragraph 3, The A-IoT transmission timing indication information within the first DCI further includes the first timing offset and the start point and length information at which the R2D transmission is performed, An operating method, wherein a transmission point at which the R2D transmission within the slot is performed is indicated from the boundary of the slot based on the starting point and length information.

6. In paragraph 2, An operating method, wherein when the first identifier is the second value, the A-IoT transmission timing indication information in the first DCI includes a first timing offset and a second timing offset as timing offsets of the R2D transmission, and the A-IoT transmission timing indication information in the first DCI further includes a third timing offset as timing of the D2R transmission, wherein the first timing offset indicates a slot in which the R2D transmission is performed based on a slot in which the first DCI transmitted through the PDCCH is transmitted, and the second timing offset indicates a transmission time point in which the R2D transmission is performed within the slot from a boundary of the slot in which the R2D transmission is performed.

7. In paragraph 6, The method of operation, wherein the third timing offset indicates the slot in which the D2R transmission is performed or the actual D2R transmission time within the slot based on the slot in which the R2D transmission is performed.

8. In paragraph 6, The method of operation, wherein the third timing offset indicates the slot in which the D2R transmission is performed or the actual D2R transmission time within the slot based on the slot in which the first DCI is transmitted.

9. In paragraph 6, The method of operation, wherein the third timing offset indicates the slot in which the D2R transmission is performed or the actual D2R transmission time within the slot based on the time at which the R2D transmission is performed.

10. In paragraph 6, The method of operation, wherein the third timing offset indicates the start time of a contention window in which at least one A-IoT device can perform the D2R transmission based on the slot in which the first DCI is transmitted.

11. In paragraph 6, An operating method, wherein the A-IoT transmission timing indication information within the first DCI further includes a fourth timing offset together with the third timing offset, wherein the fourth timing offset indicates a transmission time point at which the D2R transmission is performed within the slot from the boundary of the slot at which the D2R transmission is performed.

12. As a leader in the ambient-Internet of Things (A-IoT) system, at least one processor; and A memory storing instructions that cause the wireless user device to perform a specific operation by the at least one processor, The above specific actions are: Receiving a first DCI (downlink control information) format configured in a first DCI (downlink control information) format through a PDCCH (physical downlink control channel), wherein the first DCI includes A-IoT transmission timing indication information; and A reader that transmits an A-IoT signal to an A-IoT device via an R2D (reader to device) link based on the A-IoT transmission timing indication information.

Images