WO2025211782A1 - Method and device for performing internet-of-things-based communication in wireless communication system - Google Patents

Abstract

A method and a device for performing internet-of-things (IoT)-based communication in a wireless communication system are disclosed. The method according to one embodiment of the present disclosure may comprise steps in which a first device: transmits, to a second device, a first message directed from the first device toward the second device; and receives, from the second device, a second message directed from the second device toward the first device. Here, the second message includes data and one or more pre-defined sequences and, with respect to the one or more sequences, each sequence can correspond to one from among a preamble, a midamble and a postamble. On the basis that a plurality of sequences are included in the second message, time gaps between the sequences can be set to be shorter than a specific time interval.

Description

Method and device for performing Internet of Things-based communication in a wireless communication system

The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing Internet of Things (IoT)-based communication in a wireless communication system.

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

The 6G wireless communication system is being developed with the goals of (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free 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. Considering the requirements of the 6G system, such as a peak data rate of 1 Tbps per device, an end-to-end latency of 1 ms, a maximum spectrum efficiency of 100 bps/Hz, support for mobility of 1000 km/h, satellite integration, artificial intelligence (AI), autonomous vehicles, extended reality (XR), and haptic communication, various technologies are being researched.

The technical problem of the present disclosure relates to a method and device for performing Internet of Things (IoT)-based communication in a wireless communication system.

The technical problem of the present disclosure relates to a method and device for setting a transmission/reception point of a message/signal related to ambient IoT communication.

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 can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

A method according to one embodiment of the present disclosure may include: transmitting, by a first device, a first message from the first device to a second device, the first message being directed to the second device; and receiving, by the first device, a second message from the second device, the second message being directed to the first device, in response to the first message. Here, a start time of transmission of the second message is based on a minimum time interval from a transmission end time of the first message, and, based on the second message being transmitted based on a carrier wave (CW), the minimum time interval may be based on a specific delay associated with a request of the CW.

A method according to another embodiment of the present disclosure may include: receiving, by a second device, a first message from a first device, the first message being directed to the second device; and transmitting, by the second device, a second message from the second device to the first device, in response to the first message, the second message being directed to the first device. Here, a start time of transmission of the second message is based on a minimum time interval from a transmission end time of the first message, and, based on the second message being transmitted based on a carrier wave (CW), the minimum time interval may be based on a specific delay associated with a request of the CW.

According to various embodiments of the present disclosure, a method and device for performing Internet of Things (IoT)-based communication in a wireless communication system can be provided.

According to various embodiments of the present disclosure, a method and device for setting a transmission and reception time of a message/signal related to ambient IoT communication can be provided.

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.

The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.

FIG. 2 illustrates an example of a communication system to which some examples of the present disclosure may be applied.

FIG. 3 illustrates an example of a wireless device to which some examples of the present disclosure may be applied.

FIG. 4 exemplarily illustrates a communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

FIG. 5 illustrates a functional framework for AI operations to which some examples of the present disclosure may be applied.

FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

FIG. 9 illustrates an electromagnetic spectrum to which some examples of the present disclosure may be applied.

FIG. 10 illustrates an example of a system information transmission/reception procedure to which some examples of the present disclosure may be applied.

FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.

Figure 12 illustrates an example NTN scenario to which some examples of the present disclosure may be applied.

Figure 13 illustrates another example of an NTN scenario to which some examples of the present disclosure may be applied.

FIG. 14 illustrates examples of sensing operations to which some examples of the present disclosure may be applied.

FIG. 15 illustrates topologies that can be supported in ambient IoT communications to which some examples of the present disclosure may be applied.

FIG. 16 illustrates a specific example of a topology supported in ambient IoT communication to which some examples of the present disclosure may be applied.

FIG. 17 illustrates the operation of a first device according to an embodiment of the present disclosure.

FIG. 18 illustrates the operation of a second device according to an embodiment of the present disclosure.

FIG. 19 is a block diagram illustrating the configuration of device 1 according to one embodiment of the present disclosure.

FIG. 20 is a block diagram illustrating the configuration of device 2a according to one embodiment of the present disclosure.

FIG. 21 is a block diagram illustrating the configuration of device 2b according to one embodiment of the present disclosure.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

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 between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and/or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof.

In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the 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.

The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

In this disclosure, "A or B" can mean "only A," "only B," or "both A and B." In other words, "A or B" in this disclosure can be interpreted as "A and/or B." For example, "A, B or C" in this disclosure can mean "only A," "only B," "only C," or "any combination of A, B and C."

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

In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and/or B” may be interpreted identically to “at least one of A and B.”

Additionally, in the present disclosure, “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.”

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

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

Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.

In the present disclosure, a terminal or user equipment (UE) may be a portable device and may be a first node that receives a signal from a base station/second node/IAB (integrated access backhaul) node.

In the present disclosure, a base station (BS) may be a second node/IAB node/Transmission-Reception Point (TRP).

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

In the present disclosure, "setting or defining" may be interpreted as being set to a device through predefined signaling (e.g., SIB (system information block), MAC, RRC) from a base station or network. In the present disclosure, "setting or defining" may be interpreted as being set to a device through separate signaling or being defined in advance without separate signaling.

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.

The technology described in the present disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications)/GPRS (general packet radio service)/EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

The technology described in the present disclosure can be implemented with 6G wireless technology and applied to various 6G systems. For example, the 6G system can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

Network structure

Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.

To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as illustrated in Figure 1, may be applied, or a non-terrestrial network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, or in the case of a network-controlled repeater, it may not only amplify and forward signals but also adjust its transmission and reception settings based on information provided by the network. For example, NTN nodes could be satellites or aircraft that provide NTN coverage that terrestrial networks struggle to provide. Beyond these examples, various intermediate points can be introduced to improve the network topology.

Referring to Figure 1, a split RAN can support the division of a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DUs, various intermediate points can be introduced to compensate for this.

An intermediate point may correspond to a terminal or a base station, depending on its relationship to other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a unit (DU). The MT may connect the IAB node to a donor node. The unit (DU) of an IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to the terminal. For example, an IAB node may correspond to a base station in its relationship to a user-side node, and to a terminal in its relationship to a network-side node.

In some examples of the present disclosure, the description of a terminal may equally apply not only to a user-side endpoint, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may equally apply not only to a network-side endpoint, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side endpoint. In most cases where there is no additional description of the operations of three or more entities, the communicating entities in the present disclosure are briefly described as terminals and/or base stations (or first nodes and/or second nodes), where the terms terminal and/or base stations (or first nodes and/or second nodes) are interpreted to include/replace any endpoint or any intermediate point in relation to other nodes.

As such, in some examples of the present disclosure, for the sake of simplicity of explanation, the subjects of the operation may be referred to as terminals and/or base stations (or first nodes and/or second nodes). In addition, the terms terminal and/or base station (or first node and/or second node) may also be interpreted/replaced as in the following examples: For example, the terminal (or first node) and the base station (or second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

In the present disclosure, there may be zero or more intermediate points between the base station and the terminal. If an intermediate point exists, it may correspond to an IAB node/relay/RF repeater/NTN node, or a node supporting other functions. The intermediate point may be a node with a fixed location or a node with an unfixed location.

Systems applicable to this disclosure

FIG. 2 illustrates an example of a communication system to which some examples of the present disclosure may be applied.

The communication system (100) applied to the present disclosure includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using a wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication/wireless/5G/6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Things) device (110f), and an AI (artificial intelligence) device/server (110g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR)/virtual reality (VR)/mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point. The network device (120) may correspond to a base station (or second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may act as a network device (120) to another wireless device (110).

Wireless devices (110a to 110f) can be connected to a network (130) via a network device (120). AI technology can be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR), or a 6G network. The wireless devices (110a to 110f) can communicate with each other via the network device (120)/network (130), but can also communicate directly (e.g., sidelink communication) without going through the network device (120)/network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle)/V2X (vehicle to everything) communication). Additionally, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or another wireless device (110a to 110f).

Wireless communication/connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f)/network devices (120), network devices (120)/network devices (120). Here, the wireless communication/connection can be established through various wireless access technologies such as uplink/downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through the wireless communication/connection (150a, 150b, 150c), the wireless device and the network device/wireless device, and the network device and the network device can transmit/receive wireless signals to each other. For example, the wireless communication/connection (150a, 150b, 150c) can transmit/receive signals through various physical channels. To this end, based on various descriptions of the present disclosure, at least some of various configuration information setting processes for transmitting/receiving wireless signals, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), resource allocation processes, etc., may be performed.

Device applicable to the present disclosure

FIG. 3 illustrates an example of a wireless device to which some examples of the present disclosure may be applied.

Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and/or at least one antenna (208).

The processor (202) controls the memory (204) and/or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate first information/signal, and then transmit a wireless signal including the first information/signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including second information/signal via the transceiver (206), and then store information obtained from signal processing of the second information/signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may store software code including instructions for performing some or all of the processes controlled by the processor (202), or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem/circuit/chip designed to implement wireless communication technology. The transceiver (206) may be connected to the processor (202) and may transmit and/or receive wireless signals via at least one antenna (208). The transceiver (206) may include a transmitter and/or a receiver. The transceiver (206) may be used interchangeably with an RF (radio frequency) unit. In the present disclosure, a wireless device may also mean a communication modem/circuit/chip.

Hereinafter, the hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., a functional layer such as physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor (202) may generate at least one Protocol Data Unit (PDU) and/or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. At least one processor (202) may generate a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. At least one processor (202) can generate a signal (e.g., a baseband signal) comprising a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and/or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document.

At least one processor (202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The at least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in the at least one processor (202). The descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be included in the at least one processor (202), or may be stored in at least one memory (204) and driven by the at least one processor (202). The descriptions, functions, procedures, suggestions, methods and/or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions and/or sets of instructions.

At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and/or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and/or a combination thereof. The at least one memory (204) can be located internally and/or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.

At least one transceiver (206) can transmit user data, control information, wireless signals/channels, etc., mentioned in the methods and/or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals/channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and/or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. In addition, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals/channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and/or operation flowcharts disclosed in this document via at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals/channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals/channels, etc. using at least one processor (202). At least one transceiver (206) may convert the processed user data, control information, wireless signals/channels, etc. from baseband signals to RF band signals using at least one processor (202). For this purpose, at least one transceiver (206) may include an (analog) oscillator and/or filter.

The components of the wireless device described with reference to FIG. 3 may be referred to by different terms in terms of functionality. For example, the processor (202) may be referred to as a control unit, the transceiver (206) as a communication unit, and the memory (204) as a storage unit. In some cases, the communication unit may be used to mean at least a portion of the processor (202) and the transceiver (206).

The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least a portion of various devices. For example, the structure of the wireless device illustrated in FIG. 3 can be at least a portion of various devices described with reference to FIG. 2 (e.g., a robot (110a), a vehicle (110b-1, 110b-2), an XR device (110c), a portable device (110d), a home appliance (110e), an IoT device (110f), an AI device/server (110g)). Furthermore, according to various embodiments, in addition to the components illustrated in FIG. 3, the device may further include other components.

For example, the device may be a portable device such as a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired/wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., an audio input/output port, a video input/output port), and an input/output unit for inputting and outputting image information/signals, audio information/signals, data, and/or information input from a user.

For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired/wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting, and a position measurement unit that obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

For example, the device may be an XR device such as an HMD, a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired/wireless charging circuit, a battery, etc., an input/output unit that obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.

For example, the device may be a robot that can be classified into industrial, medical, household, military, etc. types depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a driving unit that performs various physical actions, such as moving the robot joints.

For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcasting terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, digital signage, a robot, a vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a training unit that trains a model composed of an artificial neural network using learning data.

The structure of the wireless device illustrated in FIG. 3 may be understood as a part of a terminal (or first node), or as a part of an intermediate point, or as a part of a base station (or second node). If the device illustrated in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and/or back haul communications. If the front haul and/or back haul communications are based on wireless communications, at least one transceiver (206) illustrated in FIG. 3 may be used for front haul and/or back haul communications, and a wired transceiver may not be included.

Communication procedures

FIG. 4 exemplarily illustrates a communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

FIG. 4 illustrates operations of a first node (110) (e.g., a terminal) and a second node (120) (e.g., a base station) transmitting and/or receiving data and operations performed prior thereto.

In step S101, the first node (110) and the second node (120) can perform synchronization. For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect at least one synchronization signal transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals (e.g., a primary synchronization signal, a secondary synchronization signal) classified according to a structure or purpose. Through this, the terminal (110) can confirm the boundaries of the frame, subframe, slot, and/or symbol of the base station (120) and obtain information (e.g., a cell identifier) about the base station (120).

In step S103, the first node (110) can obtain system information transmitted from the second node (120). For example, the system information is information related to the properties, characteristics, and/or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., the channel used, whether it is provided in an on-demand manner), etc., and can be classified into, for example, a master information block (MIB) and a system information block (SIB). If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. Such requesting and providing of system information may be performed after a random access procedure described below.

In step S105, the first node (110) and the second node (120) can perform a random access procedure. For example, the terminal (110) can transmit and/or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for a random access procedure based on information related to a random access channel of the base station (120) obtained through system information (e.g., channel position, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) may transmit a preamble (e.g., message 1 (MSG1)) over a random access channel, receive a random access response (RAR) message (e.g., message 2 (MSG2)), transmit a message (e.g., message 3 (MSG3)) including information related to the terminal (110) (e.g., identification information) using scheduling information included in the RAR message to the base station (120), and receive a message for contention resolution and/or connection establishment (e.g., message 4 (MSG4)). As another example, MSG1 and MSG3 may be transmitted and received as one message (e.g., message A (MSG A)), or MSG2 and MSG4 may be transmitted and received as one message (e.g., message B (MSG B)).

In step S107, the first node (110) and the second node (120) can perform signaling of control information. For example, the control information can be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

In step S109, the first node (110) and the second node (120) can transmit and/or receive data. For example, the terminal (110) and the base station (120) can process, transmit, and/or receive data based on signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on information bits. For example, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

6G system core technologies

As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

artificial intelligence

Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

FIG. 5 illustrates a functional framework for AI operations to which some examples of the present disclosure may be applied.

Below, to explain AI (or AI/ML (machine learning)) in more detail, the terms can be defined as follows.

- Data collection: Data collected from network nodes, management entities, or terminals as a basis for AI model training, data analysis, and inference.

- AI model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and/or decision parameters based on a set of inputs.

- AI/ML training: An online or offline process of training an AI model by learning features and patterns that best represent the data and obtain a trained AI/ML model for inference.

- AI/ML inference: The process of making predictions or inducing decisions based on collected data and the AI model using a trained AI model.

Referring to FIG. 5, the data collection function (10) is a function that collects input data and provides processed input data to the model training function (20) and the model inference function (30).

Examples of input data may include measurements from terminals or other network entities, feedback from actors, and output from AI models.

The data collection function (10) performs data preparation based on input data and provides input data processed through the data preparation. Here, the data collection function (10) does not perform data preparation specific to each AI algorithm (e.g., data pre-processing and cleaning, formatting, and transformation), but can perform data preparation common to all AI algorithms.

After the data preparation process is performed, the data collection function (10) may provide training data (11) to the model training function (20) and may provide inference data (12) to the model inference function (30). Here, the training data (11) may correspond to data required as input for the AI model training function (20), and the inference data (12) may correspond to data required as input for the AI model inference function (30).

The data collection function (10) may be performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), but may also be performed by multiple entities. In this case, training data (11) and inference data (12) may be provided to the model training function (20) and model inference function (30), respectively, from multiple entities.

The model training function (20) may correspond to a function that performs AI model training, validation, and testing, which can generate model performance metrics as part of the AI model testing procedure. If necessary, the model training function (20) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation, etc.) based on training data (11) provided by the data collection function (10).

Here, model deployment/update (13) can be used to initially deploy a trained, validated and tested AI model to the model inference function (30) or to provide an updated model to the model inference function (30).

The model inference function (30) may correspond to a function that provides AI model inference output (16) (e.g., prediction or decision). If applicable, the model inference function (30) may provide model performance feedback (14) to the model training function (20). In addition, the model inference function (30) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on inference data (12) provided by the data collection function (10), if necessary.

Here, output (16) refers to the inference output of the AI model generated by the model inference function (30), and the details of the inference output may vary depending on the use case.

Model performance feedback (14) can be used to monitor the performance of the AI model, if available, and this feedback may be omitted.

An actor function (40) is a function that receives an output (16) from a model inference function (30) and triggers or performs a corresponding task/action. The actor function (40) can trigger tasks/actions for other entities (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or for itself.

Feedback (15) can be used to derive training data (11), inference data (12), or to monitor the performance of the AI model, its impact on the network, etc.

Meanwhile, the definitions of training/validation/test in data sets used in AI/ML can be distinguished as follows.

- Training data: refers to a data set for learning a model.

- Validation data: This refers to a dataset used to validate a model that has already completed training. Validation data can typically be used to prevent overfitting of the training data set. It can also be used to select the best model among the various models learned during the training process. Therefore, validation can be considered a type of learning.

- Test data: This refers to the data set for final evaluation. This data is unrelated to learning.

For example, the training and validation data can be divided into an 8:2 or 7:3 ratio within the entire data set. Alternatively, the training data:validation data:test data can be divided into a 6:2:2 ratio within the entire data set.

The level of cooperation can be defined as follows depending on whether the base station and the terminal have capabilities for AI/ML functions, and variations due to combination of multiple levels or separation of any one level are also possible.

Category 0a: This category corresponds to a no-collaboration framework. In this case, AI/ML algorithms are purely implementation-based and may not require any changes to the wireless interface.

Category 0b: Frameworks that involve a wireless interface modified to fit efficient implementation-based AI/ML algorithms, but without collaboration.

Category 1: This category applies to cases where inter-node support is required to improve the AI/ML algorithms of each node. For example, this applies when a terminal receives support from a base station (for training, adaptation, etc.), and vice versa. At this level, model exchange between network nodes is not required.

Category 2: This applies to cases where joint ML tasks can be performed between terminals and base stations. This level requires exchange of AI/ML model commands or network nodes.

The functions exemplified in FIG. 5 above may be implemented in a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), a network node, an OAM (operation administration maintenance) of a network operator, or a terminal.

Alternatively, two or more entities, such as a RAN, a network node, a network operator's OAM, or a terminal, may cooperate to implement the functions illustrated in FIG. 5. For example, one entity may perform some of the functions of FIG. 5, and another entity may perform the remaining functions. In this way, since some of the functions illustrated in FIG. 5 are performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), the transmission/provision of data/information between each function may be omitted. For example, if the model training function (20) and the model inference function (30) are performed by the same entity, the transmission/provision of model deployment/update (13) and model performance feedback (14) may be omitted.

Alternatively, any one of the functions illustrated in FIG. 5 may be performed collaboratively by two or more entities, including a RAN, a network node, a network operator's OAM, or a terminal. This may be referred to as a split AI operation.

FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

For example, the AI model training function may be performed by a network node (e.g., a core network node, an OAM of a network operator, etc.), and the AI model inference function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.).

Step 1: RAN node 1 and RAN node 2 can transmit input data (e.g., training data) for AI model training to the network node. Here, RAN node 1 and RAN node 2 can also transmit data collected from the terminal (e.g., terminal measurements related to RSRP (reference signal received power), RSRQ (reference signal received quality), SINR (signal to interference-plus-noise ratio) of the serving cell and neighboring cells, terminal location, speed, etc.) to the network node.

Step 2: Network nodes can train AI models using the received training data.

Step 3: The network node may distribute/update the AI model to RAN node 1 and/or RAN node 2. RAN node 1 (and/or RAN node 2) may also continue model training based on the received AI model.

For convenience of explanation, we assume that the AI model is deployed/updated only to RAN node 1.

Step 4: RAN node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN node 2.

Step 5: RAN node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

Step 6: If applicable, RAN node 1 may send model performance feedback to the network nodes.

Step 7: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.

Step 8: RAN node 1 and RAN node 2 can transmit feedback information to the network nodes.

FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

For example, both AI model training functions and AI model inference functions can be performed by RAN nodes (e.g., base stations, TRPs, CUs of base stations, etc.).

Step 1: The terminal and RAN node 2 can transmit input data (e.g., training data) for AI model training to RAN node 1.

Step 2: RAN node 1 can train an AI model using the received training data.

Step 3: RAN node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN node 2.

Step 4: RAN node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

Step 5: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.

Step 6: RAN node 2 may transmit feedback information to RAN node 1.

FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

For example, the AI model training function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), and the AI model inference function may be performed by a terminal.

Step 1: The terminal may transmit input data (e.g., training data) for AI model training to the RAN node. Here, the RAN node may collect data (e.g., terminal measurements related to RSRP, RSRQ, SINR of the serving cell and neighboring cells, terminal location, speed, etc.) from various terminals and/or from other RAN nodes.

Step 2: RAN nodes can train AI models using the received training data.

Step 3: The RAN node can distribute/update the AI model to the terminal. The terminal can also continue model training based on the received AI model.

Step 4: Input data (e.g., inference data) for AI model inference can be received from the terminal and RAN node (and/or from another terminal).

Step 5: The terminal can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

Step 6: If applicable, the terminal may send model performance feedback to the RAN node.

Step 7: The terminal and RAN node can perform actions based on the output data.

Step 8: The terminal may transmit feedback information to the RAN node.

THz communication (terahertz communication)

Data transmission rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (the sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase 6G cellular capacity. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

FIG. 9 illustrates an electromagnetic spectrum to which some examples of the present disclosure may be applied.

Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates, and (ii) the high path loss at high frequencies (which necessitates highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

Transmitting system information (e.g., MIB) in a cell in the THz frequency band can be inefficient because the beam width in high-frequency bands narrows, requiring more beam sweeps to cover the entire cell area. This method is particularly inefficient when there are only a few users within the cell.

FIG. 10 illustrates an example of a system information transmission/reception procedure to which some examples of the present disclosure may be applied.

The example of Fig. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applicable. Furthermore, the procedure illustrated in Fig. 10 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Fig. 10.

In step S1010, the second node (120) (e.g., base station) can transmit system information of cell #1 via cell #2. For example, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one of an SFN (system frame number), a PDCCH configuration for SIB1, cell barring, cell re-selection, and subcarrier spacing generated in a higher layer, and may include at least one of an SFN, a half frame indicator, and an SSB index (synchronization signal/PBCH (physical broadcast channel) block index) generated in a physical layer. For this purpose, as an example, cell #1 and cell #2 may have a relationship of a secondary cell and a primary cell.

At step S1030, the first node (110) (e.g., terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information, but since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the terminal can acquire synchronization based on the system information. Alternatively, synchronization acquisition can be performed before step S1010.

At step S1050, the first node (110) may transmit a signal for accessing cell #1. For example, the signal may include a random access preamble. The structure of this signal and the resources (e.g., channels) for transmitting the signal may be identified through system information. Thereafter, at step S1070, the first node (110) and the second node (120) may perform an access procedure for cell #1 and communicate.

The procedure described with reference to FIG. 10 may be performed when the first node (110) initially connects to cell #1 of the second node (120). Alternatively, a similar procedure may be performed when the first node (110) hands over to cell #1 of the second node (120). However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the second node (120).

Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations may be required to use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to movement or movement of the terminals, frequent re-alignment of the beams may be required, resulting in link instability.

FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.

Although FIG. 11 illustrates an example of a procedure for searching and/or selecting beams for THz communication, this procedure is not limited to a THz environment and can also be applied to a 6G communication environment where THz communication is not applied.

Here, beam may be interpreted as other terms having equivalent technical meanings that can distinguish beams, such as 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', reference signal (RS) resource that distinguishes beams, SSB index, etc.

In step S1110, the second node (120) (e.g., base station) can set resources for beam management to the first node (110) (e.g., terminal). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from an existing downlink signal/channel for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a port for transmitting an existing downlink signal/channel (e.g., SSB, PDSCH (physical downlink shared channel), etc.). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. For example, a signal transmitted based on a dedicated port defined/set for beam search can be included in the technical concept according to the present embodiment.

In step S1130, the second node (120) (e.g., base station) transmits measurement signals using a plurality of transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams that require measurement, and may also be transmitted in a multi-beam transmission method that forms a plurality of beams simultaneously to reduce sweeping time. Here, the multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

At step S1150, a first node (110) (e.g., a terminal) may transmit a feedback signal to a second node (120) (e.g., a base station). The feedback signal may indicate at least one beam selected by the terminal. The terminal may select at least one preferred beam based on the measurement signals received at step S1130.

In step S1170, the first node (110) and the second node (120) can perform communication. For example, the second node (120) can perform transmission to the first node (110) using the reception beam of the first node (110) selected in step S1150. If channel reciprocity is established, the transmission beam of the first node (110) can also be determined through steps S1130 and S1150, so that the transmission operation from the first node (110) can also be performed using a beam that has a reciprocal relationship with the beam selected in step S1150. If channel reciprocity is not established, a procedure including transmission of measurement signal(s) by the first node (110) and transmission of feedback signal(s) by the second node (120) may be performed first to determine the transmission beam of the first node (110).

non-terrestrial networks (NTN)

Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.

NTN can represent a network or network segment that uses radio frequency (RF) resources mounted on a satellite (or unmanned aerial system (UAS) platform).

Figure 12 shows an example of a typical scenario of NTN based on transparent payload, and Figure 13 shows an example of a typical scenario of NTN based on regenerative payload.

Referring to Figure 12, a satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) can be connected to a gateway via a feeder link. The satellite can be connected to a data network via the gateway. The beam footprint can refer to the area where the signal transmitted by the satellite can be received.

Referring to Figure 13, a satellite (or UAS platform) can establish a service link with a terminal. A satellite (or UAS platform) connected to a terminal can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the regenerated payload, the satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.

Figures 12 and 13 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios. For example, a satellite (or UAS platform) can implement a transparent or regenerative (e.g., with onboard processing) payload. For example, a satellite (or UAS platform) can generate multiple beams across a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) can vary depending on the onboard antenna diagram and the minimum elevation angle.

For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may remain unchanged.

For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation/decoding, switching and/or routing, and coding/modulation. For example, a regenerative payload may be substantially equivalent to mounting all or part of a base station function on a satellite (or UAS platform).

Integrated Sensing and Communication (ISAC)

Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (or range) of an object, and thus obtain information about the characteristics of the environment and/or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, such as sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communications network to a wireless communication and sensing network.

FIG. 14 illustrates examples of sensing operations to which some examples of the present disclosure may be applied.

Specifically, Fig. 14(a) shows an example of a monostatic sensing operation using a sensing receiver and a sensing transmitter located in the same location. Fig. 14(b) shows an example of a bistatic sensing operation using a sensing receiver and a sensing transmitter located in separate locations. A sensing signal transmitted from a sensing transmitter is reflected/scattered by a sensing object, and the sensing receiver can receive the signal, and extract/obtain sensing data based on the received signal. A sensing result can be generated/determined through appropriate processing of the sensing data. The sensing result can be provided to a trusted third-party entity/service outside the 3GPP system through an entity/service within the 3GPP system.

Ambient IoT (ambient internet of things)

The Internet of Things (IoT) has recently attracted significant attention in the wireless communications world. By reducing the size, complexity, and power consumption of IoT devices and installing and connecting hundreds of billions to trillions of IoT devices, it can be applied to a wide range of applications.

In this regard, the IoT technology is being developed for various use cases, scenarios, requirements, signaling, settings, etc. under the name of ambient IoT (AmIoT).

For example, active signal generation and/or backscattering may be among the communication technologies considered to achieve low-power operation of AmIoT devices. For example, backscattering could allow the device to communicate with the network by reflecting incident waves after modulating them with information to be transmitted. For example, the device could be powered by the incident RF signal or by stored energy.

AmIoT devices can be categorized into various device types, such as passive, semi-passive, and active, based on how they store energy and generate transmission signals. For example, passive devices do not have energy storage devices (e.g., capacitors) and can communicate based on backscatter communication technology. For example, semi-passive devices have energy storage devices and can communicate using backscatter communication technology with the help of energy storage devices. For example, active devices have energy storage devices and can actively generate signals using active RF components and stored energy to communicate.

In the present disclosure, the following types of IoT devices may be considered.

Device Type 1 has a maximum power consumption of approximately 1 uW and can perform uplink transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station/terminal or a separate node). For example, Device Type 1 may be a device without energy storage or independent signal generation.

Device Type 2 has a maximum power consumption of approximately several hundred microwatts (µW) and can perform uplink transmission by backscatter-ing a carrier wave provided from an external source (e.g., a leader such as a base station/terminal or a separate node) or by internally generating a signal. Specifically, a device type that performs signal transmission by backscatter may be referred to as device type 2a, and a device type that performs signal transmission by internally generating a signal may be referred to as device type 2b. For example, device type 2a is a device that has energy storage and no independent signal generation, in which case the use of stored energy may include amplification of a reflected signal. Also, for example, device type 2b may be a device that has energy storage and independent signal generation (e.g., a device with an active RF component for transmission).

In addition to the above-described classification methods, the type/class of an AmIoT device 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.

In relation to AmIoT communications, various basic topologies may be considered to support AmIoT devices in indoor and outdoor scenarios. For example, basic topologies may include a direct connection topology between a base station and an AmIoT device, a topology in which the base station and an AmIoT device are connected via an intermediate node, a topology in which connections are supported by auxiliary nodes, and/or a connection topology between a terminal and an AmIoT device.

The basic topology described in this disclosure is merely an example, and the proposals of this disclosure can be extended and applied to other types of topologies.

FIG. 15 illustrates topologies that can be supported in ambient IoT communications to which some examples of the present disclosure may be applied.

FIG. 15 (a) illustrates a direct connection topology (e.g., topology 1) between a base station and an AmIoT device according to an embodiment of the present disclosure.

Referring to (a) of FIG. 15, an AmIoT device can communicate directly and bidirectionally with a base station. For example, communication between the base station and the AmIoT device may include AmIoT data and/or signals. For example, the AmIoT 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 this regard, the base station that performs transmission to the AmIoT device and the base station that performs reception from the AmIoT device may be different. For example, in topology 1, the base station and the AmIoT device in a micro-cell environment may perform direct communication with each other. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology.

Figure 15 (b) shows a topology (e.g., topology 2) in which a base station and an AmIoT device are connected through an intermediate node according to an embodiment of the present disclosure.

Referring to (b) of FIG. 15, an AmIoT device can bidirectionally communicate with an intermediate node between the device and a base station. For example, the intermediate node may be an AmIoT-capable relay, an IAB node, a terminal, a repeater, etc. The intermediate node may transmit AmIoT data and/or signals between the base station and the AmIoT device. The AmIoT 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 this regard, the intermediate node that performs transmission to the AmIoT device and the intermediate node that performs reception from the AmIoT device may be different. For example, in topology 2, an intermediate node may exist between a base station and an AmIoT device in a macro-cell environment. For example, the base station may be co-sited with a base station equipped with existing 3GPP technology. For example, the intermediate node may be limited to a terminal, and the intermediate node may be located indoors.

Figure 15 (c) shows a topology (e.g., topology 3) in which connection by an auxiliary node is supported according to an embodiment of the present disclosure.

Referring to the left topology of Fig. 15 (c), an auxiliary node may be supported for downlink reception. For example, an AmIoT device may transmit data/signals to a base station, and the AmIoT device may receive data/signals from the auxiliary node. Also, referring to the right topology of Fig. 15 (c), an auxiliary node may be supported for uplink transmission. For example, an AmIoT device may receive data/signals from a base station, and the AmIoT device may transmit data/signals to an auxiliary node. For example, the auxiliary node may be an AmIoT-capable relay, an IAB node, a terminal, a repeater, etc.

Figure 15 (d) shows a connection topology (e.g., topology 4) between a terminal and an AmIoT device according to an embodiment of the present disclosure.

Referring to (d) of FIG. 15, an AmIoT device can communicate bidirectionally with a terminal. For example, communication between a terminal and an AmIoT device may include AmIoT data and/or signals. The AmIoT data and/or signals may be transmitted or received based on a control channel and/or a data channel (e.g., a shared channel).

FIG. 16 illustrates a specific example of a topology supported in ambient IoT communication to which some examples of the present disclosure may be applied.

Figure 16 (a) illustrates various cases of topology 1, and Figure 16 (b) illustrates various cases of topology 2.

Referring to (a) of FIG. 16, in the case of the D1T1-A1, different leaders, the R1 node (e.g., leader 1) and the R2 node (e.g., leader 2), can be responsible for R2D channel transmission and D2R channel reception, respectively. At this time, the CW signal can be transmitted by the R1 node. In the case of the D1T1-A2, the same leader, the R node, can be responsible for both R2D channel transmission and D2R channel reception. At this time, the CW signal can be transmitted by the R node. In the case of the D1T1-B, the same leader, the R node, can be responsible for both R2D channel transmission and D2R channel reception. At this time, the CW signal can be transmitted by a separate CW node. In this regard, the R/R1/R2 nodes can all be base stations or network nodes connected to the base station.

In this regard, a case where a CW node exists within the topology can be defined as D1T1-A, a case where a CW node exists outside the topology can be defined as D1T1-B, and a case where a CW does not exist can be defined as D1T1-C.

Referring to (b) of FIG. 16, in the case of the D2T2-A1, different leaders, the R1 node (e.g., leader 1) and the R2 node (e.g., leader 2), can be responsible for R2D channel transmission and D2R channel reception, respectively. At this time, the CW signal can be transmitted by the R1 node. In the case of the D2T2-A2, the same leader, the R node, can be responsible for both R2D channel transmission and D2R channel reception. At this time, the CW signal can be transmitted by the R node. In the case of the D2T2-B case, the same leader, the R node, can be responsible for both R2D channel transmission and D2R channel reception. At this time, the CW signal can be transmitted by a separate CW node. In this regard, the R/R1/R2 nodes can all be terminals that perform the role of intermediate nodes (IN). Alternatively, in the D2T2-A1 case, the R1 node may be a base station and the R2 node may be a terminal, or the R1 node may be a terminal and the R2 node may be a base station.

In this regard, a case where a CW node exists within the topology can be defined as D2T2-A, a case where a CW node exists outside the topology can be defined as D2T2-B, and a case where a CW does not exist can be defined as D2T2-C.

Additionally, AmIoT devices may require externally provided CW for backscatter transmission. For example, CW may be used to power AmIoT devices or as CW for downlink transmission, regardless of the transmission mode (e.g., backscatter transmission or internally generated transmission).

In this regard, CW waveforms can be supported in various types. For example, the CW waveform type can be a single-tone CW waveform or a more complex multi-tone CW waveform type. For example, single-tone CW can be advantageous over multi-tone CW in terms of multiplexing capacity of tags or readers and interference reduction due to its lower resource consumption. In contrast, multi-tone CW has advantages such as being able to transmit more energy when transmitting CW in DL and securing greater coverage from a single device.

Considering the advantages of these different CW waveform types, multiple CW waveform types can be supported in the AmIoT 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 AmIoT 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 AmIoT device. For example, the base station/IN/AN/UE can configure/instruct/indicate the selected CW waveform type to the AmIoT device in the form of a command/message transmitted as a preamble/frame-sync or payload.

In the present disclosure, for AmIoT communication, at least one of the following may be proposed: frame structure, synchronization and timing, random access, numerology, bandwidth, multiple access, waveform, modulation, channel coding, channel/signal aspects, scheduling and timing relationships, and/or required characteristics of carrier waveforms for carriers provided external to the AmIoT device (including interference handling at the AmIoT device UL receiver and the NR base station). In addition, in the present disclosure, for AmIoT communication, at least one of the following may be proposed: 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 AmIoT and 6G/NR/LTE, and/or RF requirements for AmIoT.

Technical terms used in this disclosure may be as follows.

- SSB: Synchronization Signal Block

- MIB: Master Information Block

- RMSI: Remaining Minimum System Information

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

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

- BW: Bandwidth

- BWP: Bandwidth Part

- RNTI: Radio Network Temporary Identifier

- CRC: Cyclic Redundancy Check

- SIB: System Information Block

- SIB1: SIB1 for NR devices (e.g., RMSI). Broadcasts information necessary for NR terminals to access the cell.

- CORESET: Control Resource Set. Time/frequency resources for NR terminals to attempt candidate PDCCH decoding.

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

- Type0-PDCCH CSS set: A search space set for which NR terminals monitor PDCCH candidate sets for DCI formats with CRC scrambled with SI-RNTI.

- MO: PDCCH monitoring opportunity for Type0-PDCCH CSS set

- SIB1-R: (Additional) SIB1 for NR devices with reduced capabilities. May be limited to cases where it is generated as a separate TB from SIB1 and transmitted on a separate PDSCH.

- CORESET#0-R: CORESET#0 for reduced capability NR devices

- Type0-PDCCH-R CSS set: A search space set with redcap UEs monitoring a set of PDCCH candidates for DCI formats with CRC scrambled with SI-RNTI.

- MO-R: PDCCH monitoring opportunity for Type0-PDCCH CSS set

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

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.

- SCS: subcarrier spacing

- SI-RNTI: System Information-RNTI

- Camp On: “Camp On” is a terminal state in which the UE is staying in the cell and ready to initiate a potential dedicated service or receive an ongoing broadcast service.

- TB: Transport Block

- RSA (Redcap standalone): A cell that supports only Redcap devices or services.

- SIB1(-R)-PDSCH: PDSCH transmitting SIB1(-R)

- SIB1(-R)-DCI: DCI scheduling SIB1(-R)-PDSCH. DCI format 1_0 CRC scrambled by SI-RNTI.

- SIB1(-R)-PDCCH: PDCCH transmitting SIB1(-R)-DCI

- FDRA: Frequency Domain Resource Allocation

- TDRA: Time Domain Resource Allocation

- RA: Random Access

- MSGA: Preamble and payload transmission of a two-step RA type random access procedure.

- MSGB: A response to an MSGA in a two-phase random access procedure. MSGB may consist of responses to contention resolution, fallback instructions, and backoff instructions.

- RO-N: RO (RACH Occasion) for general terminal 4-step RACH and 2-step RACH (if configured)

- RO-N1, RO-N2: When a separate RO is set for the general terminal 2-stage RACH, it is divided into RO-N1 (stage 4) and RO-N2 (stage 2).

- RO-R: RO (RACH Occasion) set separately from RO-N for redcap terminal 4-stage RACH and 2-stage RACH (if set)

- RO-R1, RO-R2: When a separate RO is set for the redcap terminal 2nd stage RACH, it is divided into RO-R1 (stage 4) and RO-R2 (stage 2).

- PG-R: MsgA-preamble group for redcap terminals

- RAR: Random Access Response

- RAR Window: Time window to monitor RA responses

- FH: Frequency Hopping

- iBWP: Initial BWP

- iBWP-DL(-UL): Initial DL(UL) BWP

- iBWP-DL(-UL)-R: (separated) initial DL(UL) BWP for redcap

- CS: Cyclic shift

- NB: Narrowband

- TO: Traffic Offloading

- mMTC: Massive Machine Type Communications

- eMBB: enhanced Mobile Broadband Communication

- URLLC: Ultra-Reliable and Low Latency Communication

- RedCap: Reduced Capability

- eRedCap: Enhanced RedCap

- FDD: Frequency Division Duplex

- HD-FDD: Half-Duplex-FDD

- DRX: Discontinuous Reception

- RRC: Radio Resource Control

- RRM: Radio Resource Management

- MM: Mobility Management

- IWSN: Industrial Wireless Sensor Network

- LPWA: Low Power Wide Area

- RB: Resource Block

- CCE: Control Channel Element

- AL: Aggregation Level

- PRG: Physical Resource-block Group

- DFT-s-OFDM: DFT-spread OFDM

- PBCH: Physical Broadcast Channel

- A-PBCH: Additional PBCH

- BD: blind detection

- EPRE: Energy Per RE

- SNR: Signal-to-Noise Ratio

- TDM: Time Division Multiplexing

- FDM: Frequency Division Multiplexing

- DMRS: Demodulation Reference Signal

- TDD: Time Division Duplex

- PCI: Physical layer Cell ID

- EH: Energy Harvesting

- EH device: A device that operates based on EH. It can include all device types in AmIoT. In addition, although this disclosure primarily considers RF EH, an EH device does not necessarily have to be RF EH-based.

- ES: Energizing Signal. A signal/channel transmitted by a base station/IN/AN/UE to supply RF energy to devices operating on RF-based EH. ES can be (modulated) CW, NR/LTE DL/UL signals, etc., and dedicated signals/channels can be designed to support ES.

- ET: Energy Transfer

CW: Carrier wave. AmIoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering "externally provided" CW. AmIoT devices supporting independent signal generation-based UL transmission transmit information by modulating "internal 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.

- CWN: CW Node. A node that provides CW. It can be a base station/IN/AN/UE, and there may be a separate CWN for CW provisioning purposes.

- R: Reader/Interrogator. In the AmIoT description, readers can be gNB/eNB, intermediate node (IN)/assisting node (AN), or terminals depending on the topology. Furthermore, AmIoT is not limited to 4G/5G communication systems, and can include base stations, intermediate/assisting nodes, and terminals of next-generation communication systems. This can also mean AmIoT leaders.

- T: Tag/AmIoT device. In this disclosure, it can be interchanged with EH device, and in the AmIoT description, it mainly refers to AmIoT device, device type 1/2a/2b.

- D: AmIoT device (may have the same meaning as T mentioned above)

- R=>T: Leader-to-tag or leader-to-tag communication link. When the base station or intermediate node/auxiliary node is the leader, it may have the same meaning as DL or forward link.

- R2D: Reader (R)-to-Device (D) link (can be synonymous with R=>T or AmIoT DL. Can also be written as R=>D.)

- CW2D: CWN-to-Device (D) link (CW node-to-AmIoT device link)

- T=>R: Tag-to-reader or tag-to-reader communication link. When the base station or intermediate/auxiliary node is the leader, this may be synonymous with UL or reverse/backward link.

- D2R: Device (D)-to-Reader (R) link (can be the same meaning as T=>R or AmIoT UL. Can be written as D=>R.)

- 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.

- 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.)

- RF-EH: RF energy harvesting

- PRDCH: Physical R2D Channel (may be written as PR2DCH). A physical channel for R2D communications.

- PDRCH: Physical D2R Channel (may be denoted as PD2RCH). A physical channel for D2R communication.

- BS: Base Station

- IN: Intermediate node. In topology 2 (BS <-> IN <-> AmIoT device), IN acts as the leader. Relays, IABs, terminals, repeaters, etc. can be INs.

- AN: Assisting node. It can assist DL transmission in topology 3-1 (BS -> AN -> AmIoT device -> BS), or assist UL transmission in topology 3-2 (BS -> AmIoT device -> AN -> BS). ANs can be relays, IABs, terminals, repeaters, etc.

- UE: User Equipment. For LTE, NR, or next-generation communication systems, this refers to the LTE, NR, or next-generation communication system UE/terminal, respectively. It is a general wireless communication terminal type, distinct from AmIoT devices or device types 1/2a/2b. In topology 4 (UE <-> AmIoT device), the UE acts as the leader.

- Device: Unless otherwise stated, and when used alone, refers to EH devices, AmIoT devices or device types 1/2a/2b indiscriminately.

- AmIoT: Ambient IoT

- F-gap: Frequency gap

- T-gap: Time gap

- TD: Time Domain

- FD: Frequency Domain

- PEI: Paging Early Indication

- LP-WUS: Low-Power Wake-Up Signal

- LP-SS: Low-Power Synchronization Signal

- RSRP: Reference Signal Received Power

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

- PRB: Physical Resource Block

- EH circuit: A circuit that performs EH operations. An EH device can be viewed as containing an EH circuit as a component.

- PHR: Power Headroom Report

- EHR: Energy Headroom Report

- BPF: Band-Pass Filter

- SM: Subcarrier Modulation

- PIE: pulse interval encoding

Ambient IoT (AmIoT)-based communication

The present disclosure describes a method for transmitting and receiving signals in topologies 1 and 2, in which direct communication (e.g., mono-static communication) is performed between a base station (or/and intermediate node) and an IoT device among four topologies. However, this is only one embodiment, and the present disclosure may also be applied to topologies 3 and/or 4.

For example, in topology 1, the direction from a base station (e.g., gNB) to a device (e.g., AmIoT device) may be referred to as DL, R2T, or R2D, and the direction from the device to the base station may be referred to as UL, T2R, or D2R. The base station may transmit an R2D message or data information to the device via an R2D signal, and the device may transmit a D2R message or data information to the base station via a D2R signal.

For example, in topology 2, a direction from an intermediate node (IN) to a device (e.g., an AmIoT device) may be referred to as DL, R2T, or R2D, and a direction from a device to the intermediate node (IN) may be referred to as UL, T2R, or D2R. The intermediate node (IN) may transmit an R2D message or data information to the device via an R2D signal, and the device may transmit a D2R message or data information to the intermediate node (IN) via a D2R signal.

In describing the present disclosure, “/” means “and”, “or”, or “and/or”, depending on the context.

Below, in relation to AmIoT communication, we propose a timing setting method that needs to be considered depending on the topology (e.g., see Figs. 15 and 16).

The timing delay considered in this disclosure is proposed based on a time unit to be used in an AmIoT communication system. Here, the time unit (e.g., T_A) to be used in the AmIoT communication system may be defined as one or more T_Cs (e.g., the sampling time of an NR system).

Based on this, the number of T_As required for timing delay for a specific purpose can be defined/set/indicated. At this time, the value of the aforementioned T_C can be defined by reusing the value defined in the NR system. For example, if M T_Cs are defined to constitute T_A, T_A can be defined as M*T_C (e.g., M is an integer greater than or equal to 1). When M is 1, T_A can be defined as T_C, and when M is 4, T_A can be defined as 4*T_C.

The embodiments described below are written separately for clarity of explanation, and each embodiment may be applied independently, or the proposed method/configuration of one embodiment may be combined or replaced with the proposed method/configuration of another embodiment.

Example 1

This embodiment relates to a method for setting a backhaul delay for an AmIoT communication system.

First, a case may be considered where different readers are involved in R2D link transmission and reception (hereinafter referred to as R2D transmission and reception) and D2R link transmission and reception (hereinafter referred to as D2R transmission and reception) of a single AmIoT device (e.g., case D1T1-A1 and case D2T2-A1 in Fig. 16). In this case, the R2D transmission received by the AmIoT device (D) may be performed from the first reader (R1) toward the AmIoT device, and the D2R transmission transmitted by the AmIoT device may be performed from the AmIoT device toward the second reader (R2).

In this case, when an AmIoT device performs a D2R transmission toward a second reader (e.g., MSG1 (random number)), the second reader must transmit information about the D2R transmission to the first reader, and then the first reader, which receives the information, must perform an R2D transmission (e.g., ACK/NACK transmission) toward the AmIoT device. At this time, a minimum timing (hereinafter referred to as T_D2R_min) from the end of the D2R transmission to the reception of the R2D may be defined, and in this case, a backhaul delay (or forwarding delay) for transmitting information from the second reader to the first reader needs to be considered.

In other words, when different leaders are not used (e.g., only one leader is used), T_D2R_min can be determined by considering only the leader's processing delay. Alternatively, when different leaders are used, T_D2R_min can be defined by considering not only the leader's processing delay but also the backhaul delay (or forwarding delay) required to transmit information from the second leader to the first leader.

For example, the leader can separately set/instruct timing information for the backhaul delay to the AmIoT device in the form of a timing offset (hereinafter referred to as T_BH_offset), and based on this, the reader can set the AmIoT device to understand/judge the total T_D2R_min by adding the T_BH_offset (additionally set/instructed by the base station) to the T_D2R_min (pre-set/defined). As another example, when defining the T_D2R_min value in advance (on the standard specification), the T_D2R_min value may be defined by taking into account both the processing delay of the reader and the backhaul delay (or forwarding delay) for transmitting information from the second reader to the first reader.

Next, a case may be considered where a single leader is involved in both R2D transmission and D2R transmission of a single AmIoT device (e.g., case D1T1-B and case D2T2-B in Fig. 16). In this case, the D2R transmission transmitted by the AmIoT device (D) may be performed toward the leader (R) through a backscattering operation using the CW transmitted from the CW node (CW).

In this case, similarly to the method described above, after the leader performs an R2D transmission (e.g., an indoor command) to the AmIoT device, the leader needs to request the CW node to transmit a CW so that the AmIoT device can perform a D2R transmission. Afterwards, when the CW node transmits a CW based on the leader's request, the AmIoT device that receives the CW can perform a D2R transmission (e.g., a reply) toward the leader using a backscattering operation.

At this time, the minimum timing (hereinafter referred to as T_R2D_min) from the R2D reception end point to the D2R transmission point can be defined, and in this case, it is necessary to consider the backhaul delay (or forwarding delay, or CW request delay) required for the leader to request CW transmission to the CW node.

For example, the leader can separately set/instruct timing information for the backhaul delay to the AmIoT device in the form of a timing offset (hereinafter referred to as T_BH_offset), and based on this, the reader can set the AmIoT device to understand/judge the total T_R2D_min by adding the T_BH_offset (additionally set/instructed by the base station) to the T_R2D_min (pre-set/defined). As another example, when defining the T_R2D_min value in advance (on the standard specification), in addition to the processing delay of the reader, the T_R2D_min value may be defined by taking into account all the backhaul delays (or forwarding delays, or CW request delays) required for the reader to request CW transmission to the CW node.

Considering the CW request delay described above, this approach may be proposed for situations where the leader (or CW node) can dynamically control CW transmissions. Conversely, if the leader (or CW node) cannot dynamically control CW transmissions, other methods may need to be considered.

For example, a leader (or CW node) might configure CW transmission to occur over a certain period of time, and assume that CW is available during that period without any CW transmission requests from other leaders. In this case, the CW request delay may not need to be considered.

Additionally or alternatively, in such cases, the T_BH_offset value among the aforementioned proposed methods can be defined to not take into account the CW request delay by setting/indicating it to 0. Additionally or alternatively, the AmIoT device can be defined to determine the minimum timing (e.g., T_R2D_min or T_D2R_min) based on information about the CW transmission interval set by the leader (or CW node).

Additionally or alternatively, a minimum timing (e.g., a T1 value) that does not take into account the backhaul delay and/or CW request delay values and a minimum timing (e.g., a T2 value) that takes into account the backhaul delay and/or CW request delay values may be preset, respectively. Based on this, an operation that sets/indicates information on which minimum timing value the leader uses between the T1 value and the T2 value may also be considered/applied.

Example 2

This embodiment relates to a method for setting a frequency tuning delay for an AmIoT communication system.

D2R and R2D transmissions and receptions between a reader and an AmIoT device can be defined to be transmitted on different NR frequency spectrums (e.g., DL spectrum, UL spectrum). In this case, the AmIoT device needs to change the frequency spectrum to perform D2R transmission after receiving the R2D transmission. In addition, the AmIoT device needs to change the frequency spectrum to receive R2D transmission after performing the D2R transmission. Therefore, the R2D/D2R transmission timing needs to be defined considering the time required for the AmIoT device to change the frequency spectrum.

For example, a case may be considered where R2D transmission is performed in the NR DL band (or NR UL band), and CW transmission and/or D2R transmission are performed in the NR UL band (or NR DL band). In this case, the AmIoT device must receive the R2D transmission in the NR DL band (or NR UL band), then change the frequency to the NR UL band (or NR DL band) and then perform the subsequent D2R transmission. In this case, when defining the minimum timing (hereinafter referred to as T_R2D_min) from the end time of reception of the R2D transmission to the start time of the D2R transmission, the frequency tuning delay of the AmIoT device may be defined to be taken into consideration.

Specifically, the reader can separately set/instruct the device with timing information for the frequency tuning delay in the form of a timing offset (hereinafter referred to as T_FT_offset), and based on this, the reader/AmIoT device can be set to understand/judge the total T_R2D_min by adding T_FT_offset to the (pre-set/defined) T_R2D_min. Alternatively, when defining the T_R2D_min value (on the standard specification), it can be defined by taking into account the frequency tuning delay in the AmIoT device in addition to the processing delay of the reader.

For another example, a case may be considered where CW transmission and/or D2R transmission are performed in the NR DL band (or NR UL band), and R2D transmission is performed in the NR UL band (or NR DL band). In this case, the AmIoT device must perform the D2R transmission in the NR DL band (or NR UL band), then change the frequency to the NR UL band (or NR DL band) to receive the subsequent R2D transmission. In this case, when defining the minimum timing (hereinafter referred to as T_D2R_min) from the end time of the D2R transmission to the start time of receiving the R2D transmission, the frequency tuning delay of the AmIoT device may be defined to be taken into consideration.

Specifically, the reader can separately set/instruct the device with timing information for the frequency tuning delay in the form of a timing offset (hereinafter referred to as T_FT_offset), and based on this, the reader/AmIoT device can be set to understand/judge the total T_D2R_min by adding T_FT_offset to the (pre-set/defined) T_D2R_min. Alternatively, when defining the T_D2R_min value (on the standard specification), it can be defined by taking into account the frequency tuning delay in the AmIoT device in addition to the processing delay of the reader.

The T_FT_offset associated with the frequency (re)tuning delay value proposed in this embodiment can be independently set/indicated for each type of AmIoT device (e.g., device type 1/2a/2b) and/or for each device capability within the same AmIoT device type.

Example 3

This embodiment relates to a method for handling D2R synchronization when different device types coexist in an AmIoT communication system.

As mentioned above, AmIoT device types can be classified into device type 1 and device type 2, and in detail, device type 2 can be classified into device type 2a and device type 2b. At this time, device type 1 and device type 2a have the characteristic of performing D2R transmission by backscattering a carrier wave (e.g., CW) provided from a leader (or a separate CW node). In addition, device type 2b has the characteristic of performing D2R transmission using a signal generated internally by itself.

In relation to the AmIoT communication system, a case may be considered where device types 1/2a/2b coexist within the system (in a situation where CW can be transmitted), and the reader can transmit a specific command (e.g., indoor inventory, etc.) regardless of the device type. In this case, for device types 1 and 2a, the AmIoT device can perform D2R transmission through backscattering using the CW transmitted by the reader (or CW node). In contrast, for device type 2b, the AmIoT device can generate a signal for D2R transmission on its own and perform the transmission.

In this regard, in terms of reception by the reader, it may be desirable/efficient for the D2R transmission due to backscattering by an AmIoT device of device type 1/2a and the D2R transmission generated and transmitted by the AmIoT device of device type 2b to be received at the same timing. At this time, an operation in which the AmIoT devices perform D2R transmissions in different frequency domains for each device type and each is received at the same timing may be considered, and an operation in which multiple AmIoT devices perform D2R transmissions in different frequency domains and each is received at the same timing may also be considered.

For the above-described operation, the reader can set/instruct the timing information from the R2D transmission applied to the AmIoT device(s) of device type 1/2a to the start of the D2R transmission to be applied equally to the AmIoT device(s) of device type 2b. At this time, the timing information may be in the form of a minimum value and/or a maximum value, may be defined in advance (in the standard specification), and may be set/instructed by the reader. Alternatively, when AmIoT device(s) of device type 1/2a and AmIoT device(s) of device type 2b coexist, the timing information may be set to a specific fixed value (e.g., a value in the middle of the minimum value and the maximum value) rather than the minimum value and/or the maximum value, and each AmIoT device may be set to perform the D2R transmission according to the set/instructed timing.

Additionally or alternatively, when AmIoT devices of different device types (e.g., device types 1/2a/2b) coexist, there may be multiple timing delays to consider for each topology and/or each device type. In this regard, a method in which the reader separately determines and sets/instructs/defines timing delay values for each topology and/or each device type may be considered, but a method in which a minimum timing value is defined by defining a timing delay value that takes into account all topologies and/or all device types may also be considered. For example, the minimum timing value may be defined based on the maximum backhaul delay and/or the maximum CW request delay considering the topology (e.g., T1 and T2). As another example, the minimum timing value may be defined based on the maximum frequency (re)tuning delay, etc. that takes into account all device types (e.g., device types 1/2a/2b) of AmIoT devices.

FIGS. 17 and 18 illustrate the operation of a device and/or network node in relation to a method of performing AmIoT communication according to embodiments of the present disclosure described above.

In FIGS. 17 and 18, the first device and/or the second device may correspond to any one of a base station, an intermediate node (IN), an auxiliary node (AN), a terminal, and an AmIoT device, respectively, based on various topologies in AmIoT communication. For example, in FIGS. 17 and 18, the first device may correspond to a leader (e.g., a base station, an intermediate node (IN), an auxiliary node (AN), a terminal), and the second device may correspond to an AmIoT device.

FIG. 17 illustrates the operation of a first device according to an embodiment of the present disclosure.

Referring to FIG. 17, the first device may transmit a first message from the first device to the second device (S1710). For example, the transmission and reception of the first message may correspond to the transmission and reception of the R2D signal/message described above in the present disclosure (e.g., including PRDCH transmission and reception).

Thereafter, in response to the first message, the first device may receive a second message from the second device, which is directed to the first device (S1720). For example, the transmission and reception of the second message may correspond to the transmission and reception of the D2R signal/message described above in the present disclosure (e.g., including the transmission and reception of PDRCH).

In this regard, the start time of transmission of the second message may be based on a minimum time interval from the end time of transmission of the first message. Specifically, if the second message is transmitted based on carrier wave (CW), the minimum time interval may be based on a specific delay associated with a CW request (e.g., backhaul delay, forwarding delay, CW request delay, etc.).

For example, the minimum time interval can be set by adding a second value corresponding to a specific delay related to the request of the CW mentioned above to a first value corresponding to the minimum time from the end time of transmission of the first message to the start time of transmission of the second message. In this case, the first value can be defined in advance or can be set in advance by the first device to the second device (e.g., T_R2D_min set/defined in advance). In addition, the second value can be set or indicated to the second device by the first device in the form of a separate timing offset (e.g., T_BH/CW_offset).

As another example, the minimum time interval may be predefined (in the standard specification) based on a specific delay associated with the aforementioned CW request.

Additionally, according to the present disclosure, the aforementioned CW request may be transmitted by the first device to the CW node. Here, the CW node may be located outside the AmIoT topology based on the first device and the second device (e.g., see D1T1-B, D2T2-B of FIG. 16).

Additionally, according to the present disclosure, if a first minimum time interval based on a specific delay associated with a request of a CW and a second minimum time interval unrelated to the specific delay associated with the request of the CW are set in advance, the first device can transmit information to the second device as to which of the first minimum time interval or the second minimum time interval applies to transmission of the second message.

Additionally, according to the present disclosure, if a frequency change is required between the transmission and reception of the first message and the transmission and reception of the second message, the minimum time interval described above may be further based on a delay for the frequency change (see, for example, the proposed method of Example 2).

Additionally, according to the present disclosure, when multiple device types are defined for ambient IoT communication (e.g., device types 1/2a/2b), information on the aforementioned minimum time interval may be set according to a device type corresponding to a second device among the multiple device types. That is, information on the minimum time interval may be set individually for each device type.

The method described in the example of FIG. 17 can be performed by the wireless device (200) of FIG. 3. That is, the first device of FIG. 17 can be implemented as the wireless device (200). For example, one or more processors (202) of the wireless device (200) of FIG. 3 can be configured to transmit a first message from the first device to the second device and receive a second message from the second device to the first device via one or more transceivers (206).

Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 17 or the examples described above when executed by one or more processors (202).

FIG. 18 illustrates the operation of a second device according to an embodiment of the present disclosure.

Referring to FIG. 18, the second device may receive a first message from the first device, which is intended for the second device (S1810). For example, the transmission and reception of the first message may correspond to the transmission and reception of the R2D signal/message described above in the present disclosure (e.g., including PRDCH transmission and reception).

Thereafter, in response to the first message, the second device may transmit a second message to the first device, directed from the second device to the first device (S1820). For example, the transmission and reception of the second message may correspond to the transmission and reception of the D2R signal/message described above in the present disclosure (e.g., including the transmission and reception of PDRCH).

In this regard, the start time of transmission of the second message may be based on a minimum time interval from the end time of transmission of the first message. Specifically, if the second message is transmitted based on carrier wave (CW), the minimum time interval may be based on a specific delay associated with a CW request (e.g., backhaul delay, forwarding delay, CW request delay, etc.).

Specific features regarding how to set/define/interpret the minimum time interval, the minimum time interval depending on whether a request for CW and a CW node, a specific delay is taken into consideration, the minimum time interval based on frequency change and/or device type, etc. are the same as the description referring to FIG. 17, so redundant descriptions are omitted.

The method described in the example of FIG. 18 can be performed by the wireless device (200) of FIG. 3. That is, the network node of FIG. 18 can be implemented by the wireless device (200). For example, one or more processors (202) of the wireless device (200) of FIG. 3 can be configured to receive a first message from a first device to a second device and transmit a second message from the second device to the first device via one or more transceivers (206).

Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 18 or the examples described above when executed by one or more processors (202).

FIGS. 19 to 21 illustrate types and configurations of AmIoT devices to which some examples of the present disclosure may be applied. Each of device 1, device 2a, and device 2b of FIGS. 19 to 21 may correspond to device type 1, device type 2, and device type 3 described above in the present disclosure, respectively.

Device 1 may be collectively referred to as a device having a peak power consumption of less than 1 μW, capable of storing energy, having an initial sampling frequency offset (SFO) of up to 10X ppm, and having no DL or UL amplification capability. The UL transmission of Device 1 may be backscattered from an externally provided carrier wave.

Device 2a may have a peak power consumption of less than a few hundred μW, may store energy, may have an initial sampling frequency offset (SFO) of up to 10X ppm, and may have DL and/or UL amplification capabilities. The UL transmission of device 2a may be backscattered from an externally provided carrier wave.

Device 2b may have a peak power consumption of less than a few hundred μW, may store energy, may have an initial sampling frequency offset (SFO) of up to 10X ppm, and may have DL and/or UL amplification capabilities. The UL transmissions of the device may be generated internally in the device.

FIG. 19 is a diagram of a configuration of device 1 to which some examples of the present disclosure may be applied. As an example of the present disclosure, as illustrated in FIG. 19, device 1 may include at least one of an antenna, a matching network, an RF energy harvester, an energy storage, a power management unit, a digital BB logic, a memory, a clock generator, a reception-related block, and a transmission-related block.

The antenna may be shared or separate for the RF energy harvester and receiver/transmitter. A matching network may match the impedance between the antenna and other components (e.g., including blocks related to the RF energy harvester and receiver). The RF energy harvester may include a rectifier that converts the RF signal (AC) to DC.

An energy storage unit (e.g., a capacitor) can store energy harvested from an RF energy harvester. A power management unit (PMU) can store energy from the energy harvester in the energy storage unit and supply power to the active component blocks that require power.

Digital BB logic may include functional blocks such as encoders, decoders, and controllers. Memory may include 1) non-volatile memory (NVM), such as EEPROM, for permanent storage of device IDs and other information, and 2) registers for temporarily storing information necessary for operation while the energy storage device is powered. A clock generator may provide the necessary clock signals.

The receiver-related block may include an RF BPF, an RF envelope detector, a BB LPF, and a comparator. The RF BPF may be used to improve selectivity. However, the RF BPF may not be present depending on the implementation. RAN4 RF requirements (if any, e.g., ACS) and peak power consumption targets may be considered. The RF envelope detector may convert the RF signal to baseband. The BB (baseband) LPF may improve the input signal quality to the comparator by filtering out harmonics and high frequency components. However, the BB LPF may not be present depending on the implementation. The comparator may determine whether the input signal is high or low.

The transmission-related block may include a backscatter modulator. The backscatter modulator can switch impedances to modulate a backscatter signal into a transmit signal of the BB logic. The waveform/modulation type is FFS.

FIG. 20 is a diagram illustrating a configuration of a device 2a to which some examples of the present disclosure may be applied. As an example of the present disclosure, as illustrated in FIG. 20, the device 2a may include at least one of an antenna, a matching network, an energy harvester, an energy storage, a power management unit, a digital BB logic, a memory, a clock generator, a reflection amplifier, a reception-related block, and a transmission-related block.

A reflective amplifier can amplify the reflected backscatter signal. At least one of the R2D/CW2D and D2R can be amplified by the reflective amplifier or LNA.

The receiving related block may include at least one of an RF band-pass filter (BPF), a low noise amplifier (LNA), an RF envelope detector, a BB amplifier, a BB low-pass filter (LPF), and a comparator or an N-bit analog-to-digital converter (ADC).

An LNA can be used to improve the signal strength and sensitivity of a receiver, and at least one of the R2D/CW2D and D2R can be amplified by a reflective amplifier or LNA. An RF envelope detector (RF-ED) can detect the envelope in an RF signal. A BB amplifier can amplify the BB signal to improve signal strength. A BB LPF can filter out harmonics and high-frequency components to improve the input signal quality to the comparator/ADC.

The transmission-related block may include a backscatter modulator and a large frequency shifter. The backscatter modulator can modulate the backscatter signal into a transmit signal for the BB logic by switching the impedance. A large frequency shifter may be used to shift the backscatter signal from one frequency (e.g., an FDD-DL frequency) to another frequency (e.g., an FDD-UL frequency).

The overlapping configuration between device 2a and device 1 is described in Fig. 19, so the overlapping description is omitted.

FIG. 21 illustrates a configuration of a device 2b to which some examples of the present disclosure may be applied. As an example of the present disclosure, as illustrated in FIG. 21, the device 2b may include at least one of an antenna, a matching network, an energy harvester, an energy storage, a power management unit, a digital BB logic, a memory, a clock generator, a reception-related block, and a transmission-related block. Here, the energy harvester may harvest energy from RF signals, sunlight, vibrations/motions, temperature differences, and the like.

The receiving-related block may include an RF BPF, an LNA, an RF envelope detector, a BB amplifier, a BB LPF, a comparator, and an N-bit ADC. The transmitting-related block may include at least one of a transmitting modulator, a DAC, a low-pass filter, a mixer, a local oscillator, and a power amplifier.

The baseband bits can be modulated by a modulator, depending on the modulation method. The modulator block can be part of the BB logic. A digital-to-analog converter (DAC) can convert digital signals to analog signals. A low-pass filter can filter out unwanted signals. A mixer can convert the baseband signal to the RF range. A local oscillator can generate a carrier frequency. A power amplifier (PA) can amplify the transmitted signal.

In describing the present disclosure, each of the configurations of FIGS. 19 to 21 may be included in at least one transceiver illustrated in FIG. 3.

The above-described embodiments of the present disclosure may be applied independently. Additionally or alternatively, all or part of the operations of the above-described embodiments of the present disclosure may be performed in combination.

The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE/LTE-A, 5G, and 6G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE/LTE-A, 5G, and 6G systems.

Claims (15)

A step of transmitting a first message from the first device to the second device, the first message being directed to the second device; and A step of receiving, by the first device, a second message directed to the first device from the second device in response to the first message, The transmission start time of the above second message is based on the minimum time interval from the transmission end time of the above first message, A method wherein the minimum time interval is based on a specific delay associated with a request for the CW, based on the second message being transmitted based on a carrier wave (CW). In the first paragraph, A method in which the minimum time interval is set by adding a second value corresponding to the specific delay to a first value corresponding to the minimum time from the end time of transmission of the first message to the start time of transmission of the second message. In the second paragraph, The first value is predefined or pre-set to the second device by the first device, A method wherein the second value is set or instructed to the second device in the form of a separate timing offset by the first device. In the first paragraph, A method wherein the above minimum time interval is defined in advance based on the above specific delay. In the first paragraph, The above CW request is transmitted to the CW node by the first device, A method wherein the CW node is located outside of an ambient Internet of Things (IoT) topology based on the first device and the second device. In the first paragraph, A method comprising: transmitting, by the first device, information to the second device as to which of the first minimum time interval or the second minimum time interval applies to transmission of the second message, based on a first minimum time interval based on a specific delay associated with the request of the CW and a second minimum time interval unrelated to the specific delay associated with the request of the CW being set in advance. In the first paragraph, A method wherein the minimum time interval is further based on a delay for the frequency change, based on the requirement for a frequency change between the transmission and reception of the first message and the transmission and reception of the second message. In the first paragraph, Based on the definition of multiple device types for ambient IoT communication, A method in which information about the above minimum time interval is set according to a device type corresponding to the second device among the plurality of device types. In paragraph 8, A method wherein some of the above multiple device types are classified based on whether the second message is transmitted based on the CW. In the first paragraph, The above first device corresponds to a reader or intermediate node in ambient IoT communication, The above second device corresponds to a device in ambient IoT communication. one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting a first message from a first device to a second device; In response to the first message, a second message directed to the first device is set to be received from the second device, The transmission start time of the above second message is based on the minimum time interval from the transmission end time of the above first message, A device wherein the minimum time interval is based on a specific delay associated with a request for the CW, based on the second message being transmitted based on a carrier wave (CW). A step of receiving a first message from a first device, the first message being directed to the second device, by a second device; and Including, by the second device, a step of transmitting a second message from the second device to the first device in response to the first message, The transmission start time of the above second message is based on the minimum time interval from the transmission end time of the above first message, A method wherein the minimum time interval is based on a specific delay associated with a request for the CW, based on the second message being transmitted based on a carrier wave (CW). one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving a first message from the first device to the second device; In response to the first message, a second message directed to the first device is set to be transmitted from the second device to the first device, The transmission start time of the above second message is based on the minimum time interval from the transmission end time of the above first message, A device wherein the minimum time interval is based on a specific delay associated with a request for the CW, based on the second message being transmitted based on a carrier wave (CW). one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 10 based on execution by said one or more processors. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the performance of a method according to any one of claims 1 to 10.