Method for ambient IoT repeated transmission, and apparatus thereof

Abstract

A method according to one embodiment of the present specification comprises a step of transmitting a signal on the basis of the number of repetitions related to a specific level. The specific level is related to i) a codeword based on line coding, ii) a chip related to modulation, or iii) a forward error correction code (FEC).

Description

Method and device for repeated transmission of AMBIENT IOT

[0001] The present specification relates to a method and device for Ambient IoT repetitive transmission.

[0002] The 5G mobile communications system, the successor to LTE (long-term evolution), is a new, clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. 6G mobile communications systems are being developed based on the underlying technologies of 5G mobile communications.

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

[0004] When performing OFDM waveform-based R2D / D2R transmission, the coverage target (e.g., 10 to 50 m), which is one of the Ambient IoT RAN design targets, must be met.

[0005] The purpose of this specification is to propose a method for meeting the coverage targets of Ambient IoT described above.

[0006] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification pertains from the description below.

[0007] A method according to one embodiment of the present disclosure for solving the above-described technical problem comprises transmitting a signal based on a repetition count associated with a specific level. The specific level is characterized by being associated with i) a codeword based on line coding, ii) a chip associated with modulation, or iii) a forward error correction code (FEC). As described above, coverage satisfying Ambient IoT requirements can be guaranteed through repetition transmission based on a specific level.

[0008] If the performance of OFDM waveform-based R2D / D2R transmission and reception operations does not meet Ambient IoT requirements, the supported use cases for Ambient IoT may be limited. According to embodiments of the present disclosure, OFDM waveform-based R2D / D2R transmission is performed based on a repetition rate based on a specific level to meet the requirements for supporting Ambient IoT. Therefore, a wider range of IoT services can be supported in a wireless communication system.

[0009] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification belongs from the description below.

[0010] Figure 1 illustrates topology 1 related to Ambient IoT.

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

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

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

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

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

[0016] Figure 7 illustrates deployment scenario 1.

[0017] Figure 8 illustrates deployment scenario 2.

[0018] Figure 9 illustrates pulse interval encoding.

[0019] Figure 10 illustrates the relationship between OFDM symbols and chips.

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

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

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

[0023] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0024] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0025] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".

[0026] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

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

[0028] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0029] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0030] In this specification, a terminal (UE, User Equipment) may be a portable device and may be a second node that receives a signal from a base station / first node / IAB node.

[0031] In this specification, a base station (BS) may be a base station / first node / IAB node / Transmission-Reception Point.

[0032] In this specification, higher layer parameters may be parameters that are set for the terminal, preset, or predefined. For example, a base station or network may transmit higher layer parameters to the terminal. For example, higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0033] In this specification, "configured or defined" may be interpreted as being configured or preset to a device through predefined signaling (e.g., SIB, MAC, RRC) from a base station or network. In this specification, "configured or defined" may be interpreted as being preset to a device.

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

[0035] Ambient IoT communication (Rel-18)

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

[0037]

[0038] Table 2 shows the IoT communication-related issues discussed in 3GPP RAN.

[0039]

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

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

[0042] For example, the following basic topologies may be considered to support A-IoT devices in indoor and outdoor scenarios. For example, the basic topologies may include direct connections between base stations and A-IoT devices, connections between base stations and intermediate nodes and A-IoT devices, connection support by auxiliary nodes, and / or connections between terminals and A-IoT devices. The basic topologies proposed in this disclosure are merely examples, and the proposals in this disclosure may be extended / applied to other topologies.

[0043] Figure 1 illustrates topology 1 related to Ambient IoT.

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

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

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

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

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

[0049] Fig. 3 is an example of topology 3 related to Ambient IoT. Fig. 4 is another example of topology 3 related to Ambient IoT.

[0050] FIGS. 3 and 4 illustrate a topology (e.g., Topology 3) supported by an assisting node according to one embodiment of the present disclosure. The embodiments of FIGS. 3 and 4 may be combined with various embodiments of the present disclosure.

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

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

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

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

[0055] For example, transmission by an A-IoT device may be performed over a frequency division duplexing (FDD) spectrum (e.g., an FDD UL spectrum).

[0056] < Ambient IoT solutions SI (Rel-19) >

[0057] A study item titled “Study on solutions for Ambient IoT (Internet of Things) in NR” was approved in 3GPP NR Release 19. Specifically, the study item will be conducted in 3GPP NR Release 19 based on the following:

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

[0059] General range

[0060] The definitions given in TR 38.848 apply to this SI and are of an exclusive general scope.

[0061] A. The overall goal is to study a harmonized wireless interface design that minimizes the differences required to enable Ambient IoT to enable the following devices:

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

[0063] ii. ≤hundreds of μW peak power consumption1, energy storage, initial sampling frequency offset (SFO) of up to 10X ppm, and DL and / or UL amplification within the device. The device's UL transmission may be generated internally or backscattered from an externally provided carrier wave.

[0064] -X is decided by WG.

[0065] - Coverage design goal: Up to 10-50 m distance with the device indoors according to TR 38.848: "...the range within which the WG can sub-select".

[0066] -No RRC state, no mobility (i.e. at least no functionality like cell selection / reselection), no HARQ, no ARQ for topologies 1 and 2 (UE as intermediate node under NW control) according to TR 38.848.

[0067] Note 1: It should be understood that the WG is not tasked with setting a specific value for "≤hundreds of μW", and it is a matter for the WG to discuss whether the proposed design and its power consumption meet the "≤hundreds of μW" requirement.

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

[0069] - Deployment Scenario 1 Using Topology 1

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

[0071] - Deployment scenario 2 using UE as an intermediate node under topology 2 and network control.

[0072] Base Station and Coexistence Characteristics: Macro Cell, Co-site

[0073] The location of the intermediate node is indoors

[0074] C. FDD's FR1 licensed spectrum.

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

[0076] E. Traffic types DO-DTT, DT focusing on rUC1 (indoor inventory) and rUC4 (indoor command).

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

[0078] Transmissions from surrounding IoT devices (including backscattering when used) can occur at least in the UL spectrum.

[0079] The following goals are set within the general range:

[0080] 1. Evaluation assumptions

[0081] a) Conclude at least the following aspects of the design objectives left to the WG in clause 5 (RAN design objectives) of TR 38.848 [RAN1]:

[0082] Article 5.3: Applicable Maximum Distance Target Value

[0083] Clause 5.6: Refines the definition of latency suitable for use in RAN WGs.

[0084] Article 5.8: 2D Distribution of Devices

[0085] b) Define additional assessment assumptions required for deployment scenarios for coverage and coexistence assessments [RAN1, RAN4].

[0086] c) Identify the basic blocks / components of a possible peripheral IoT device architecture, considering the latest implementations of low-power, low-complexity devices that meet RAN design goals for power consumption and complexity. [RAN1]

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

[0088] Note: The evaluation performance of the design target falls within the scope of the feasibility and necessity study of the proposal, with the following objectives: For example, testing a reference implementation in the field, conducting simulations, and conducting analytical tests.

[0089] Note: RAN1 strives to minimize evaluation cases.

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

[0091] Positioning research for Rel-19 is led by RAN3 and is limited to features that have no or minimal impact on the specification (Note: This does not imply decisions regarding WI generation).

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

[0093] - RAN1 led:

[0094] For Ambient IoT DL and UL:

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

[0096] Numerology, Bandwidth, and Multi-Access

[0097] Waveforms and modulation

[0098] Channel coding

[0099] Downlink channel / signal aspect

[0100] Uplink channel / signal aspect

[0101] Scheduling and Timing Relationships

[0102] We study the required characteristics of the carrier wave waveform provided to ambient IoT devices from outside, including interference handling at ambient IoT UL receivers and NR base stations.

[0103] For topology 2, there is no difference in the physical layer design from topology 1.

[0104] RAN2 led:

[0105] We study and determine the features required for an ambient IoT compact protocol stack and lightweight signaling procedures that enable DO-DTT and DT data transmission.

[0106] for example:

[0107] Paging

[0108] Random access

[0109] Data transmission including necessary radio resource control aspects that comply with general range limitations.

[0110] Interaction with higher layers

[0111] Features not listed above will only be studied if deemed essential.

[0112] RAN3 led:

[0113] Identify the necessary impacts on the signals and procedures of the CN-RAN interface to enable:

[0114] Paging

[0115] Device context management

[0116] Data transfer

[0117] Identify RAN architecture aspects, including whether split architecture support is required.

[0118] Identify potential solutions for finding Ambient IoT devices that don't impact the specifications. For example, reusing existing user location reports or transmitting location information to the core network with minimal impact on the specifications.

[0119] RAN4 led:

[0120] A study on the coexistence of Ambient IoT and NR / LTE.

[0121] RF Requirements Study for Ambient IoT:

[0122] Ambient IoT BS Transmission and Reception

[0123] Ambient IoT devices, transmitting and receiving, according to general scope

[0124] Intermediate nodes (UEs) according to general range, transmitting and receiving

[0125] RAN2 and RAN3 are expected to work with SA2 to identify the RAN-CN functional split.

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

[0127] For example, as mentioned above, the types of A-IoT devices can be divided into two as follows. For example, a Type 1 device has a maximum power consumption of approximately 1 uW, can store energy, has no amplification function, and can transmit by backscattering a carrier wave (CW) provided from the outside (e.g., a reader such as a base station or a terminal, or a separate node). For example, a Type 2 device has a maximum power consumption of approximately several hundred uW, can store energy, has an amplification function, and can transmit by backscattering a carrier wave (CW) provided from the outside (e.g., a reader such as a base station or a terminal, or a separate node) or by using a signal generated internally by itself.

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

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

[0130] For example, some types / classes of A-IoT devices (e.g., Device B, Device C, Type 1 devices, and / or Type 2 devices) may have energy storage capabilities (e.g., capacitors or charging batteries) for the following purposes:

[0131] - Stable energy security at the time of reception / transmission

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

[0133] For example, the minimum RF reception sensitivity for operation of a low-power communication module may be -20 dBm, and the minimum reception sensitivity for energy harvesting may be -20 dBm. In this case, if the reception power of the A-IoT device ranges between -30 and -20 dBm, communication may not be possible without a capacitor, but communication may be possible after a charging time with a capacitor.

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

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

[0136] Specifically, FIG. 6 illustrates power consumption and device energy states according to the operating states of an energy harvesting-based device with energy storage capabilities, according to an embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure.

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

[0138] Figure 6 (a) may represent a device energy state corresponding to Figure 6 (b). Referring to Figure 6 (a), the E1 value and the E2 value may differ depending on the device (type / class), and the device may report information related to the E1 value and / or information related to the E2 value to R and / or the base station as capability parameters. For example, the E2 value may be defined as an energy value in a buffered state, and the E1 value may be defined as a minimum energy value required in an active state.

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

[0140] For example, A-IoT devices may require externally provided CW for backscatter transmission. For example, CW may be used to power A-IoT devices or as CW for downlink transmission, regardless of the transmission mode (e.g., backscatter transmission or internally generated transmission).

[0141] For example, CW waveforms can be supported in various types. For example, the CW waveform type can be a single-tone CW waveform type or a more complex multi-tone CW waveform type. For example, single-tone CW can be advantageous over multi-tone CW in terms of the multiplexing capacity of tags or readers and in terms of interference because it uses fewer resources. On the other hand, multi-tone CW has advantages such as being able to transfer more energy when transmitting CW in DL, and also securing greater coverage from a single device.

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

[0143] For example, the present disclosure may propose at least one of the following for A-IoT communication: frame structure, synchronization and timing, random access, numerology, bandwidth, multiple access, waveforms, modulation, channel coding, channel / signal aspects, scheduling and timing relationships, and / or required characteristics of carrier waveforms for carriers provided external to the A-IoT device (including interference handling at the A-IoT device UL receiver and the NR base station). For example, the present disclosure may propose at least one of the following for A-IoT communication: paging, random access, data transmission including required radio resource control aspects to comply with general range limitations, interaction with upper layers (e.g., RRC layer, non-access stratum (NAS) layer, application layer, etc.), device context management, data transmission, coexistence of A-IoT and 6G / NR / LTE, and / or RF requirements for A-IoT.

[0144] For example, technical terms used in this specification may include:

[0145] - SSB: Synchronization Signal Block

[0146] - MIB: Master Information Block

[0147] - RMSI: Remaining Minimum System Information

[0148] - FR1: Frequency Range 1. Refers to the frequency range below 6 GHz (e.g., 450 MHz to 6000 MHz).

[0149] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) range above 24 GHz (e.g., 24250 MHz to 52600 MHz).

[0150] - BW: Bandwidth

[0151] - BWP: Bandwidth Part

[0152] - RNTI: Radio Network Temporary Identifier

[0153] - CRC: Cyclic Redundancy Check

[0154] - SIB: System Information Block

[0155] - SIB1: SIB1 for NR devices = RMSI (Remaining Minimum System Information). Broadcasts information necessary for NR terminals to access cells.

[0156] - CORESET: CONTOL REsource SET. Time / frequency resource for the terminal to attempt candidate PDCCH decoding.

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

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

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

[0160] - SIB1-R: (additional) SIB1 for reduced capability NR devices. May be limited to cases where it is generated as a separate TB from SIB1 and transmitted on a separate PDSCH.

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

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

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

[0164] - Cell defining SSB (CD-SSB): SSB containing RMSI scheduling information among NR SSBs

[0165] Non-cell defining SSB (non-CD-SSB): An SSB that is placed in the NR sync raster but does not contain RMSI scheduling information for the corresponding cell for measurement purposes. However, it may contain information indicating the location of the cell defining SSB.

[0166] - SCS: subcarrier spacing

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

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

[0169] - TB: Transport Block

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

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

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

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

[0174] - FDRA: Frequency Domain Resource Allocation

[0175] - TDRA: Time Domain Resource Allocation

[0176] - RA: Random Access

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

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

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

[0180] - RO-N1, RO-N2: When a separate RO is set for normal UE 2-step RACH, it is divided into RO-N1 (4-step) and RO-N2 (2-step).

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

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

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

[0184] - RAR: Random Access Response

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

[0186] - FH: Frequency Hopping

[0187] - iBWP: initial BWP

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

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

[0190] - CS: Cyclic shift

[0191] - NB: Narrowband

[0192] - TO: Traffic Offloading

[0193] -mMTC; Massive Machine Type Communications

[0194] - eMBB: enhanced Mobile Broadband Communication

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

[0196] - RedCap: Reduced Capability

[0197] - eRedCap: enhanced RedCap

[0198] - FDD: Frequency Division Duplex

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

[0200] - DRX: Discontinuous Reception

[0201] - RRC: Radio Resource Control

[0202] - RRM: Radio Resource Management

[0203] - MM: Mobility Management

[0204] - IWSN: Industrial Wireless Sensor Network

[0205] - LPWA: Low Power Wide Area

[0206] - RB: Resource Block

[0207] - CCE: Control Channel Element

[0208] - AL: Aggregation Level

[0209] - PRG: Physical Resource-block Group

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

[0211] - PBCH: Physical Broadcast Channel

[0212] - A-PBCH: Additional PBCH

[0213] - BD: blind detection

[0214] - EPRE: Energy Per RE

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

[0216] - TDM: Time Division Multiplexing

[0217] - FDM: Frequency Division Multiplexing

[0218] - DMRS: DeModulation Reference Signal

[0219] - TDD: Time Division Duplex

[0220] - PCI: Physical layer Cell ID

[0221] - EH: Energy Harvesting

[0222] - EH device: A device that operates based on EH. It can include all of Device A / B / C being discussed in 3GPP. In addition, although this specification primarily considers RF EH, an EH device does not necessarily have to be RF EH-based.

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

[0224] - ET: Energy Transfer

[0225] CW: Carrier wave. Ambient IoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering "externally provided" CW. Ambient IoT devices supporting independent signal generation-based UL transmission transmit information by modulating "internally generated" CW. Unless otherwise specified, "externally provided" CW for backscattering is assumed. CW can be used as an energizing signal (ES) for RF energy transfer.

[0226] - CWN: Carrier Wave Node. A node that provides the CW. It may be a base station / IN / AN / UE, and there may be a separate CWN for CW provision purposes.

[0227] - R: Reader / interrogator. This is a standard RFID term. In the 3GPP Ambient IoT context, readers can include gNB / eNB, intermediate / assisting nodes, and UEs, depending on the topology. Furthermore, Ambient IoT is not limited to 4G / 5G communication systems, and can include base stations, intermediate / assisting nodes, and UEs in next-generation communication systems. This can also mean Ambient IoT readers.

[0228] - T: Tag / ambient IoT device. This is a standard RFID term. In this specification, it can be interchanged with EH device, and in the 3GPP Ambient IoT context, it mainly refers to Ambient IoT device, Device A / B / C. The abbreviation 'T' can be interpreted / replaced with 'D', which stands for Ambient IoT Device.

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

[0230] - R=>T: Reader-to-Tag or Reader-to-Tag communication link. When the base station or intermediate / assisting node is the reader, it can have the same meaning as DL or forward link. 'R=>T' can be interpreted / replaced with 'R=>D' (Reader-to-Device).

[0231] - R2D: R-to-D link (can mean the same thing as R=>T. Can also be written as R=>D.)

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

[0233] - T=>R: Tag-to-Reader or Tag-to-Reader communication link. When the base station or intermediate / assisting node is the reader, it may have the same meaning as UL or reverse / backward link. 'T=>R' can be interpreted / replaced with 'D=>R' (Device-to-Reader).

[0234] - D2R: It can have the same meaning as T=>R. It can be written as D=>R.

[0235] - R<=>T: Includes cases where R=>T and T=>R, or R=>T or T=>R. It may be the case that both R=>T and T=>R apply.

[0236] - R<=>D: Includes R2D and D2R, or either R2D or D2R. This may apply to both R2D and D2R. (This may have the same meaning as R<=>T.)

[0237] - RF-EH: RF energy harvesting

[0238] - PRDCH: Physical R2D CHannel (may be written as PR2DCH). A physical channel for R2D communication.

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

[0240] - BS: Base Station

[0241] - IN: Intermediate node. In Topology 2 (BS ↔ IN ↔ Ambient IoT device), IN acts as the reader. Relay, IAB, UE, repeater, etc. can be IN.

[0242] - AN: Assisting node. It can assist DL transmission in Topology 3-1 (BS -> AN -> Ambient IoT device -> BS), or assist UL transmission in Topology 3-2 (BS -> Ambient IoT device -> AN -> BS). AN can be a relay, IAB, UE, repeater, etc.

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

[0244] - Device: Unless otherwise stated, and when used alone, refers to EH device, Ambient IoT device, or Device A / B / C indiscriminately.

[0245] - AmIoT: Ambient IoT (=A-IoT)

[0246] - F-gap: Frequency gap

[0247] - T-gap: Time gap

[0248] - TD: Time Domain

[0249] - FD: Frequency Domain

[0250] - PEI: Paging Early Indication

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

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

[0253] - RSRP: Reference Signal Received Power

[0254] - ESRP: ES Received Power. This may refer to RSRP measured using ES. It may have the same meaning as ES-RSRP.

[0255] - PRB: Physical Resource Block

[0256] - EH circuit: A circuit that performs EH operations. An EH device can be viewed as containing an EH circuit in component form.

[0257] - PHR: Power Headroom Report

[0258] - EHR: Energy Headroom Report

[0259] - BPF: Band-Pass Filter

[0260] - SM: Subcarrier Modulation

[0261] - FS: Frequency Shift. In FDD, it can be divided into small FS, which is performed within a small range (e.g., hundreds of kHz) within the DL spectrum or within the UL spectrum (mainly through baseband processing), and large FS, which is performed over a relatively large range (e.g., tens of MHz) from the DL to the UL spectrum or from the UL to the DL spectrum.

[0262] - SFO: Sampling Frequency Offset

[0263] - ASK: Amplitude Shift Keying

[0264] -DSB-ASK: Double-SideBand ASK

[0265] -SSB-ASK: Single-SideBand ASK

[0266] - PR-ASK: Phase-Reversal ASK

[0267] - OOK: On-Off Keying

[0268] - PSK: Phase-Shift Keying

[0269] - BPSK: Binary-PSK

[0270] - FSK: Frequency-Shift Keying

[0271] - B-FSK: Binary FSK

[0272] - M-FSK: M-ary FSK

[0273] - PIE: Pulse-Interval Encoding

[0274] - Ncp-ofdm, Ncp, Nu: The length of the sample unit of the CP-OFDM symbol section, CP section, and useful OFDM symbol section, respectively, in the CP-OFDM symbol. Ncp-ofdm=Ncp+Nu.

[0275] In this specification, '()' can be interpreted as either excluding the contents within () or including the contents within the parentheses.

[0276] In this specification, ' / ' may mean including all of the contents separated by / (and) or including only some of the contents separated by / (or).

[0277] UHF passive RFID communication (ISO 18000-6C) can be considered as a standardized conventional technology that uses a communication method similar to Ambient IoT communication. This UHF passive RFID supports PIE (Pulse-Interval Encoding) as a data encoding method for R=>T communication and DSB-ASK and / or SSB-ASK and / or PR-ASK as modulation methods. In addition, for T=>R communication, it supports FM0 baseband encoding and Miller modulated subcarrier as data encoding methods and ASK and / or PSK-based backscatter modulation as modulation method.

[0278] Meanwhile, supporting Ambient IoT in 4G / 5G / 6G communication systems requires determining data encoding and modulation methods that take into account requirements different from conventional UHF passive RFID, device types, (spectrum) deployment scenarios, connectivity topologies, design targets, and functions. Furthermore, coexistence with efficient 4G / 5G / 6G communication systems must also be considered.

[0279] In this specification, we propose repetitive transmission methods for expanding the AmIoT transmission and reception range, taking into account the points mentioned above.

[0280] The methods proposed in this specification can be applied to both topology 1 and topology 2. They can also be applied to both deployment scenario 1 and deployment scenario 2. To support Ambient IoT communication in 4G / 5G / 6G communication systems, the following combinations of topologies, deployment scenarios, and CW node types (CW inside topology or CW outside topology) are being considered. These are described below with reference to FIGS. 7 and 8.

[0281] Figure 7 illustrates deployment scenario 1.

[0282] Referring to Fig. 7, in Deployment scenario 1 with topology 1 (indoor BS + indoor AIoT device), the cases where external CW is within the topology (D1T1-A), the case where external CW is outside the topology (D1T1-B), and the case where there is no external CW (i.e., D2R transmission using internally generated CW, D1T1-C) are considered, as shown in Table 3 below.

[0283]

[0284] Figure 8 illustrates deployment scenario 2.

[0285] Referring to Fig. 8, in Deployment scenario 2 with topology 2 (outdoor BS + Indoor Intermediate UE + Indoor AIoT device), the cases in which external CW is within the topology (D2T2-A), the case in which external CW is outside the topology (D2T2-B), and the case in which there is no external CW (i.e., D2T2-C for D2R transmission using internally generated CW) are considered, as shown in Table 4 below.

[0286]

[0287] < Data encoding and modulation method >

[0288] For R2D / D2R communication, low-power / low-complexity modulation schemes such as ASK (e.g., OOK), PSK (e.g., BPSK), and FSK (e.g., B-FSK) can be considered. In addition, for efficient control of R2D / D2R communication, a chip, which is the basic unit of modulation application, can be defined, and based on this, the start and / or end points can be aligned between the transmission symbols (e.g., OFDM symbols) of coexisting 4G / 5G / 6G communication systems and AmIoT transmission symbols, or parameters for R2D / D2R communication (e.g., R2D / D2R data / chip rate, FS value) can be directed / controlled.

[0289] A chip, which is the basic unit of modulation application, can be defined as a unit of bit sequence or phase sequence of a channel / baseband / data encoder output terminal. For example, when Manchester Encoding (ME) is applied to data-0, a 2-chip Manchester codeword consisting of {1, 0} is generated. For example, according to the ME, data-0 can be mapped to {+phase, -phase} or {1, 0}, and data-1 can be mapped to {-phase, +phase} or {0, 1}. For example, according to the ME, data-0 can be mapped to {-phase, +phase} or {0, 1}, and data-1 can be mapped to {+phase, -phase} or {1, 0}.

[0290] Based on the definition of these chips, the codeword duration can be defined for the channel / baseband / data encoding schemes considered in AmIoT communication. As explained above, in the case of the ME codeword, the codeword duration can be 2 chips. In the case of the Extended / Repeated ME (e-ME / r-ME), the codeword duration can be defined as 4 chips, 8 chips, etc. depending on the degree of extension / repetition. For example, in the case of e-ME / r-ME, in the case of 4 chips, data-0 can be mapped to {1, 1, 0, 0} or {1, 0, 1, 0}, respectively.

[0291] Figure 9 illustrates pulse interval encoding.

[0292] Referring to Fig. 9, in the case of PIE, as in the example of UHF passive RFID application, the length of the low section (PW) is set equally by R regardless of data-0 and data-1, and data-0 and data-1 are identified by the difference in the high section. R can select / determine the length of data-0 and data-1 within a certain range, and can instruct T about this selection / decision related information through R=>T preamble or frame sync. In order to support this method in Topology 2 for AmIoT communication, the base station can set / instruct IN (e.g., UE) about information related to the length of data-0 and data-1. Or, it can set / instruct information about the difference between the length of data-0, the length of data-1, and the length of data-0. IN (e.g., UE) can perform R2D transmission and / or D2R reception operations using the set / instructed information.

[0293] When applying the PIE method for AmIoT communication, the chip can be defined in the following two ways.

[0294] Method 1) Defining a chip based on the duration of low / off / -phase (e.g. PW in Fig. 9)

[0295] The codeword / encoded (symbol) duration of Data-0 can be defined as 2 chips, and Data-1 can be defined as N1(>2) chips.

[0296] Eg, data-0 codeword / encoded (symbol) duration can be defined in the form of {high, low} with 2 chips, data-1 codeword / encoded (symbol) duration can be defined in the form of {high, high, low} with 3 chips (N1=3), and {high, high, high, low} with 4 chips (N1=4).

[0297] For example, to apply method 1, the data-0 codeword / encoded (symbol) duration can be limited to twice the chip duration, and the data-1 codeword / encoded (symbol) duration can be limited to an integer multiple of the chip duration.

[0298] For example, method 1 can be applied only when the following conditions i) and ii) are satisfied.

[0299] i) data-0 codeword / encoded (symbol) duration is twice the chip duration

[0300] ii) data-1 codeword / encoded (symbol) duration is an integer multiple of the chip duration.

[0301] Method 2) Defining a chip based on the Reference (e.g. data-0) codeword / encoded (symbol) duration (e.g. Tari in Fig. 9)

[0302] It could be a method where the codeword / encoded (symbol) duration of Data-0 is defined as 1 chip, and Data-1 is defined as N2(>1) chips.

[0303] For example, data-0 codeword / encoded (symbol) duration can be defined as {high, low} with 1 chip, and data=1 codeword / encoded (symbol) duration can be {high, high, low} with 1.5 chip (N2=1.5), and {high, high, high, low} with 2 chip (N2=2).

[0304] To apply method 2, the data-1 codeword / encoded (symbol) duration can be limited to X / 2 times the chip duration (where X is an integer greater than or equal to 3), or method 2 can be applied only when these conditions are satisfied.

[0305] Codeword / encoded (symbol) duration, data rate, FS value, etc. can be controlled in units of chips defined above, and such control information can be transmitted / indicated through preamble / midamble / postamble / sync signals and / or payload.

[0306] The reader (or AmIoT device) can select / decide between the above method 1 and method 2, and transmit / instruct the selection / decision information to the AmIoT device (or reader) via frame sync / preamble / midamble / postamble / sync signals. Or, in Topology 2 for AmIoT communication, the base station can set / instruct the IN (e.g., UE) to use one of method 1 and method 2. The IN (e.g., UE) can perform R2D transmission and / or D2R reception operations by applying the set / instructed method.

[0307] <OFDM waveform 기반의 R2D 전송 방식>

[0308] In OFDM waveform-based R2D / D2R transmission, unintended phase / energy / value transitions / changes may be detected from the R2D receiver's perspective due to the CP (Cyclic Prefix) insertion operation. When an AmIoT device receives OFDM-based R2D (depending on the device type or capability), the following Assumption 1 or Assumption 2 may be considered for the AmIoT device's operation for the corresponding CP.

[0309] (Assumption 1) AmIoT devices can handle unintended phase / energy / value transitions / changes due to CP insertion.

[0310] (Assumption 2) AmIoT devices may not be able to handle unintended phase / energy / value transitions / changes due to CP insertion.

[0311] For these AmIoT devices, the following CP handling method in the R2D transmission stage is being considered.

[0312] Method Type 1: Removal of CP from device without specified transmit-side operation (based on Assumption 1)

[0313] Method Type 2: Ensure the CP insertion of OFDM-based waveform will not introduce false rising / falling edge between the last OOK chip in OFDM symbol (n-1) and the first OOK chip in OFDM symbol n (based on Assumption 2)

[0314] Method Type 1 may be a method in which, for example, M (e.g., M = 1, 2, 4, 8, 16, 32) chips are mapped during the Nu section, and a CP (Cyclic Prefix) of size Ncp is inserted based on this to generate an OFDM-based waveform of size Ncp-ofdm (= Nu+Ncp).

[0315] Method Type 2 may be a method for generating an OFDM-based waveform so that M chips are mapped during, for example, an Ncp-ofdm section. For example, Method Type 2 may be a method that satisfies the following conditions i) to iii).

[0316] i) The values ​​of the first X chip(s) and the last X chip(s) in the OFDM symbol are the same so that false rising / falling edges do not occur even after CP insertion.

[0317] ii) X=1 or 2. If the number of chips M in an OFDM symbol is less than or equal to M0, X=1, otherwise X=2. M0 is a value determined based on (Nu+Ncp) / Ncp, and can be the maximum value that satisfies the condition M0 < (Nu+Ncp) / Ncp (e.g., M0=8).

[0318] iii) After CP insertion, the length of all chips is the same.

[0319] Figure 10 illustrates the relationship between OFDM symbols and chips.

[0320] Specifically, Fig. 10 shows the relationship between OFDM symbols and chips in Method Type 2. In Fig. 10, it is assumed that there are M chips in one OFDM symbol, and the chips in the OFDM symbol are distinguished by chip index = 0, 1, 2, .., M-1.

[0321] For convenience, the value / phase / state of chip m of OFDM symbol n is denoted as m@n.

[0322] The Reader (or AmIoT device) can select / decide one of the above methods (Method Type 1 and Method Type 2). The Reader (or AmIoT device) can transmit / instruct information based on the selection / decision to the AmIoT device (or reader) through frame sync / preamble / midamble / postamble / sync signals / R2D (or D2R) control info / payload transmitted as PRDCH (or PDRCH). Or, in Topology 2 for AmIoT communication, the base station can configure / instruct one of the above methods to the IN (e.g., UE). The IN (e.g., UE) can perform R2D transmission and / or D2R reception operations by applying the configured / instructed method.

[0323] For example, whether Method Type 1 or Method Type 2 is supported and / or applied may be determined based on the number of chips M in the supported OFDM symbol. For example, Method Type 2 may be supported / applied / configured only when the M value is greater than a specific value M1 (e.g., M1=4).

[0324] For example, whether Method Type 1 or Method Type 2 is supported and / or applied may be determined by other R2D / D2R transmission parameters. For example, considering that Method Type 1 is relatively easy to apply when line coding (e.g., ME, PIE) is applied, when line coding is set / applied, only Type 1 can be set / applied without any additional settings.

[0325] < R2D / D2R repeat transmission method >

[0326] In OFDM waveform-based R2D / D2R transmission, the following R2D / D2R repetitive transmission methods are proposed to meet the 10 to 50 m coverage target, which is one of the AmIoT RAN design targets described above.

[0327] [Method 1] How to repeatedly transmit codewords N times

[0328] A method of applying LE (Line Encoding) after repeating each input bit N times can be considered.

[0329] Example 1-1) When transmitting twice using the ME (Manchester Encoding) method (i.e., when N=2), the ME codeword can be transmitted repeatedly as follows.

[0330] 10 -> 1010, 01 -> 0101

[0331] Example 1-2) In case of PIE, N=2, the PIE codeword can be transmitted repeatedly as follows.

[0332] 10 -> 1010, 1110 -> 11101110

[0333] [Method 2] How to repeatedly transmit N times per chip

[0334] A method of transmitting the LE output codeword by repeating it N times in chip units.

[0335] Example 2-1) In case of ME, N=2, the ME codeword can be transmitted repeatedly as follows.

[0336] 10 -> 1100, 01 -> 0011

[0337] Example 2-2) In case of PIE, N=2, the PIE codeword can be transmitted repeatedly as follows.

[0338] 10 -> 1100, 1110 -> 11111100

[0339] For method 2, it may be similar to lowering the chip rate by 1 / N times.

[0340] [Method 3] Repeat N times per chip + scrambling or SM (Subcarrier / square-wave Modulation)

[0341] A method of repeating the LE output codeword N times per chip and then applying an N-bit scrambling sequence or SM to the N repeated chips can be considered.

[0342] [Method 3-1] Repeat N times per chip + N-bit scrambling

[0343] Example 3-1) When ME, N=4, the ME codeword can be repeated and scrambled and transmitted in the following order.

[0344] Repetition: 10 -> 11110000, 01 -> 00001111

[0345] Scrambling by {1 0 0 1}: 11110000 -> 10010000, 00001111 -> 00001001

[0346] The above results (10010000, 00001001) exemplify a case where the scrambling sequence is applied based on the XNOR operation. Specifically, the 11110000 can become 10010000 by applying an XNOR operation with {1 0 0 1} to every chip (1111, 0000) repeated N times. Specifically, the 00001111 can become 00001001 by applying an XNOR operation with {1 0 0 1} to every chip (0000, 1111) repeated N times. The above-described XNOR operation is only an example of a method of applying the scrambling sequence, and the technical idea of ​​the present embodiment is not intended to be limited to the XNOR operation. In other words, the scrambling sequence can be applied based on other operations (multiplication operation, XOR operation).

[0347] [Method 3-2] Repeat N times per chip + apply SM

[0348] Example 3-2) When ME, N=4, the ME codeword is repeated in the following order and SM (Subcarrier / square-wave Modulation) is applied for transmission.

[0349] Repetition: 10 -> 11110000, 01 -> 00001111

[0350] SM: 11110000 -> 10100000, 00001111 -> 00001010

[0351] Here, the square wave can be expressed in the form of {1, 0, 1, 0, …} or {0, 1, 0, 1, …} in the OOK chips to which OOK modulation is applied. In other words, the square wave can be expressed in the form of {1, 0} or {0, 1} being repeated. In this case, one cycle of the square wave can be the length of {1, 0} or {0, 1} (two chip duration). The following describes in detail the method of applying the scrambling sequence or square wave multiplication.

[0352] SM (Subcarrier / square-wave Modulation) can be performed based on XOR (or XNOR) or multiplication as follows.

[0353] In the OOK modulation method, when the square wave is OOK chips {1 0 1 0}, SM can be applied as follows.

[0354] Multiplication method: 1111 -> 1010, 0000 -> 0000

[0355] XNOR method: 1111 -> 1010, 0000 -> 0101

[0356] In the BPSK modulation method, when the square wave is BPSK chips {+1 -1 +1 -1}, SM can be applied as follows.

[0357] Multiplication method

[0358] {1, 1, 1, 1} -> {1, -1, 1, -1}

[0359] {-1, -1, -1, -1} -> {-1, 1, -1, 1}

[0360] Meanwhile, the square wave can be expressed in the form of {+1, -1, +1, -1, …}, or {-1, +1, -1, +1, …} in chips to which BPSK modulation is applied. In other words, the square wave can be expressed in the form of {+1, -1}, or {-1, +1} being repeated. In this case, one period of the square wave is the length of {+1, -1}, or {-1, +1} (the duration of two chips).

[0361] [Method 4] FEC + bit repetition + scrambling or SM

[0362] A method of repeating the FEC output bits N times in bit units and then applying an N-bit scrambling sequence or SM to the N repeated chips can be considered.

[0363] [Method 4-1] Repeating FEC output bits N times + N-bit scrambling

[0364] Example 4-1) If the FEC output bit sequence is 10, the FEC output bits can be repeated and scrambled in the following order and transmitted.

[0365] Repetition: 10 -> 11110000

[0366] Scrambling by {1 0 0 1}: 11110000 -> 10010000

[0367] [Method 4-2] Repeat FEC output bits N times + SM

[0368] Example 4-2) If the FEC output bit sequence is 10, the FEC output bits can be repeated and scrambled in the following order and transmitted.

[0369] Repetition: 10 -> 11110000

[0370] SM: 11110000 -> 10100000

[0371] The Reader (or AmIoT device) can select / decide one of the above methods. The Reader (or AmIoT device) can transmit / instruct the selection / decision information (e.g., one of Methods 1 to 4) to the AmIoT device (or reader) via frame sync / preamble / midamble / postamble / sync signals / R2D (or D2R) control info / payload transmitted on PRDCH (or PDRCH). Or, in Topology 2 for AmIoT communication, the base station can configure / instruct the IN (e.g., UE) to select one of the above methods (e.g., one of Methods 1 to 4). The IN (e.g., UE) can perform R2D transmission and / or D2R reception operations by applying the configured / instructed method.

[0372] The various embodiments of the present disclosure may be combined with each other.

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

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

[0375] The embodiments described below are specifically described with reference to FIGS. 11 and 12 in terms of the operation of a first device (e.g., Ambient IoT Device or Reader, base station, intermediate node, auxiliary node, terminal) and a second device (e.g., Reader, base station, intermediate node, auxiliary node, terminal or Ambient IoT Device). The methods described below are distinguished only for convenience of explanation, and it goes without saying that some components of one method may be substituted for some components of another method or may be applied in combination with each other.

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

[0377] Referring to FIG. 11, a method according to one embodiment of the present specification includes a step (S1110) of transmitting a signal based on a number of repetitions associated with a specific level.

[0378] In S1110, the first device transmits a signal to the second device based on a repetition number associated with a specific level.

[0379] In one embodiment, the specific level may be related to i) a codeword based on line coding, ii) a chip associated with modulation, or iii) a Forward Error Correction Code (FEC). The present embodiment may be based on at least one of Methods 1 to 4.

[0380] In one embodiment, each of the one or more codewords associated with the signal may be repeated based on the repetition count. This embodiment may be based on Method 1. For example, if the one or more codewords are codeword 10 based on Manchester Encoding (ME) and the repetition count is 2, 1010 may be transmitted.

[0381] In one embodiment, among one or more codewords associated with the signal, each of a plurality of chips based on each codeword may be repeated based on the repetition number. This embodiment may be based on Method 2 or Method 3. For example, if the one or more codewords are codeword 10 based on Manchester Encoding (ME) and the repetition number is 2, 1100 may be transmitted.

[0382] For example, scrambling or square wave modulation may be applied to the repeated chips based on the number of repetitions. This embodiment may be based on Method 3-1 or Method 3-2. Methods 3-1 and 3-2 will be described below with specific examples.

[0383] It can be assumed that the above one or more codewords are codeword 10 based on Manchester Encoding (ME) and the number of repetitions is 4. Each chip based on codeword 10 is repeated 4 times, so the codeword 10 becomes 11110000.

[0384] In the case of method 3-1, scrambling can be applied to the repeated chips (1111, 0000) based on the number of repetitions (4). If the scrambling sequence {1001} is applied to each of the repeated chips (1111, 0000), 11110000 based on the repetition of codeword 10 becomes 10010000. Finally, 10010000 can be transmitted.

[0385] In the case of method 3-2, square wave modulation (SM) can be applied to the repeated chips (1111, 0000) based on the number of repetitions (4). If the square wave (1, 0, 1, 0, etc.) is applied to each of the repeated chips (1111, 0000), 11110000 based on the repetition of codeword 10 becomes 10100000. Finally, 10100000 can be transmitted.

[0386] In one embodiment, each bit of the bit sequence associated with the FEC of the signal may be repeated based on the repetition number. This embodiment may be based on Method 4. For example, if the bit sequence associated with the FEC of the signal is 10 and the repetition number is 4, 11110000 may be transmitted.

[0387] For example, scrambling or square wave modulation may be applied to the repeated bits based on the number of repetitions. This embodiment may be based on Method 4-1 or Method 4-2. Methods 4-1 and 4-2 will be described below with specific examples.

[0388] It can be assumed that the bit sequence related to the FEC of the above signal is 10 and the number of repetitions is 4. Each bit based on the bit sequence 10 is repeated 4 times, so the bit sequence 10 becomes 11110000.

[0389] For method 4-1, scrambling can be applied to the repeated bits (1111, 0000) based on the repetition number (4). If the scrambling sequence {1001} is applied to each of the bits (1111, 0000), 11110000 based on the repetition of bit sequence 10 becomes 10010000. Finally, 10010000 can be transmitted.

[0390] For method 4-2, square wave modulation (SM) can be applied to the repeated bits (1111, 0000) based on the repetition number (4). If a square wave (1, 0, 1, 0, etc.) is applied to each of the bits (1111, 0000), 11110000 based on the repetition of bit sequence 10 becomes 10100000. Finally, 10100000 can be transmitted.

[0391] In one embodiment, the line coding may be based on Manchester Encoding or Pulse Interval Encoding.

[0392] In one embodiment, the transmission of the signal may be a R2D (Reader to Device) transmission or a D2R (Device to Reader) transmission.

[0393] As an example of R2D (Reader to Device), a signal transmitted from a first device (Reader) to a second device (Ambient IoT Device) may be based on a physical channel. The physical channel may be referred to as an R2D channel or a Physical Reader-to-Device CHannel (PRDCH). As a specific example, the PRDCH may carry i) all higher-layer payloads (e.g., higher-layer payload including system information, higher-layer payload including settings / information other than system information) and / or ii) R2D control information.

[0394] As an example of D2R (Device to Reader), the signal transmitted from a first device (Ambient IoT Device) to a second device (Reader) may be based on a physical channel. The physical channel may be referred to as a D2R channel or a Physical Device-to-Reader Channel (PDRCH). As a specific example, the PDRCH may carry i) any higher-layer payload, ii) a response transmitted from the Ambient IoT Device to the Reader during a contention-based access procedure, and / or iii) D2R control information.

[0395] In one embodiment, the first device and the second device may be based on devices that operate based on one of four topologies related to Ambient IoT (see FIGS. 1 to 5 ). Specifically, the first device (or the second device) may be i) a base station, ii) a user equipment (UE), iii) an intermediate node, or iv) an assisting node. The second device (or the first device) may be an Ambient IoT (Internet of Things) device.

[0396] In one embodiment, the method may further include a configuration transmission step. Specifically, the first device (e.g., Reader) may transmit configuration related to repeated transmission to the second device (e.g., Ambient IoT device). For example, the configuration may include information related to at least one of the above-described embodiments. For example, the configuration may include information indicating the number of repetitions. For example, the configuration may include information indicating the specific level (or information indicating at least one of Methods 1 to 4). The configuration transmission step may be performed before S1110.

[0397] The operations based on the above-described S1110 and setup transmission steps can be implemented by the device of FIG. 13. For example, referring to FIG. 13, the first device (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S1110 and setup transmission steps.

[0398] The embodiments described below are specifically described in terms of the operation of the second device.

[0399] The S1210 and setting reception steps described below correspond to the S1110 and setting transmission steps described in FIG. 11. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the second device operation described below may be replaced with the description / example of FIG. 11 corresponding to the corresponding operation.

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

[0401] Referring to FIG. 12, a method according to another embodiment of the present specification includes a step (S1210) of receiving a signal based on a number of repetitions associated with a specific level.

[0402] In S1210, the second device receives a signal from the first device based on a repetition number associated with a specific level.

[0403] In one embodiment, the specific level may be related to i) a codeword based on line coding, ii) a chip associated with modulation, or iii) a Forward Error Correction Code (FEC). The present embodiment may be based on at least one of Methods 1 to 4.

[0404] In one embodiment, the method may further include a configuration receiving step. Specifically, the second device (e.g., Ambient IoT device) may receive configuration related to repeated transmission from the first device (e.g., Reader). For example, the configuration may include information related to at least one of the above-described embodiments. For example, the configuration may include information indicating the number of repetitions. For example, the configuration may include information indicating the specific level (or information indicating at least one of Methods 1 to 4). The configuration receiving step may be performed before S1210.

[0405] The operations based on the above-described S1210 and setup receiving steps can be implemented by the device of FIG. 13. For example, referring to FIG. 13, the second device (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S1210 and setup receiving steps.

[0406] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 13.

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

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

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

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

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

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

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

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

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

[0416] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.

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

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

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

Claims

1. In the method, A step of transmitting a signal based on a number of repetitions associated with a specific level; comprising: A method characterized in that the above specific level is related to i) a codeword based on line coding, ii) a chip related to modulation, or iii) a forward error correction code (FEC).

2. In paragraph 1, A method characterized in that each of one or more codewords associated with the signal is repeated based on the number of repetitions.

3. In paragraph 1, A method characterized in that, among one or more codewords associated with the signal, each of a plurality of chips based on each codeword is repeated based on the number of repetitions.

4. In paragraph 3, A method characterized in that scrambling or square wave modulation is applied to the repeated chips based on the number of repetitions.

5. In paragraph 1, A method characterized in that each bit of the bit sequence related to the FEC of the signal is repeated based on the number of repetitions.

6. In paragraph 5, A method characterized in that scrambling or square wave modulation is applied to the repeated bits based on the number of repetitions.

7. In paragraph 1, A method characterized in that the above line coding is based on Manchester encoding or pulse interval encoding.

8. In paragraph 1, A method characterized in that the transmission of the signal is R2D (Reader to Device) transmission or D2R (Device to Reader) transmission.

9. In the first device, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A first device characterized in that the instructions, based on being executed by the one or more processors, cause the first device to perform all steps of the method according to any one of claims 1 to 8.

10. In an electronic device comprising one or more memories and one or more processors connected to the one or more memories, An electronic device characterized in that said one or more memories store instructions that cause said electronic device to perform all steps of a method according to any one of claims 1 to 8, based on being executed by said one or more processors.

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

12. In the method, A step of receiving a signal based on a number of repetitions associated with a specific level; comprising: A method characterized in that the above specific level is related to i) a codeword based on line coding, ii) a chip related to modulation, or iii) a forward error correction code (FEC).

13. In the second device, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A second device characterized in that said instructions, based on being executed by said one or more processors, cause said second device to perform all steps of the method according to claim 12.

Images