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

Abstract

Disclosed are a method and a device for performing Internet-of-things (IoT)-based communication in a wireless communication system. A method, according to one embodiment of the present disclosure, may comprise the steps of: receiving, by a terminal from a base station, first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PDRCH) or a first physical reader to device channel (PRDCH); and on the basis of overlapping between a first resource for a first physical uplink control channel (PUCCH) including a first SR and a second resource for a first channel, transmitting, by the terminal, the first PUCCH to the base station according to the priority of the first SR, wherein the first channel may include either a second PUCCH including a second PDRCH, a second PRDCH, and a second SR, or a physical uplink shared channel (PUSCH).

Description

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

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

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

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

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

[0005] The technical problem of the present disclosure relates to a method and device for performing resource allocation for ambient IoT communication.

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

[0007] A method according to one embodiment of the present disclosure comprises the steps of: receiving, by a terminal, from a base station first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH); and transmitting, by the terminal, a first physical uplink control channel (PUCCH) to the base station based on a priority of the first SR, based on overlapping of a first resource for the first PUCCH including the first SR and a second resource for the first channel, wherein the first channel may include at least one of a second PDRCH, a second PRDCH, a second PUCCH including the second SR, or a physical uplink shared channel (PUSCH).

[0008] According to another embodiment of the present disclosure, a method includes the steps of: transmitting, by a base station, first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH) to a terminal; and receiving, by the base station, a first physical uplink control channel (PUCCH) from the terminal based on a priority of the first SR, based on overlapping of a first resource for the first PUCCH including the first SR and a second resource for the first channel, wherein the first channel may include at least one of a second PDRCH, a second PRDCH, a second PUCCH including the second SR, or a physical uplink shared channel (PUSCH).

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

[0010] According to various embodiments of the present disclosure, a method and apparatus for performing resource allocation for ambient IoT communication can be provided.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0028] FIG. 16 is a diagram illustrating a case according to topology 1 to which some examples of the present disclosure can be applied.

[0029] FIG. 17 is a diagram illustrating a case according to topology 2 to which some examples of the present disclosure can be applied.

[0030] FIG. 18 is a flowchart illustrating a procedure for an ambient IoT device to access a leader device according to one embodiment of the present disclosure.

[0031] FIG. 19 illustrates the operation of a first device according to an embodiment of the present disclosure.

[0032] FIG. 20 illustrates the operation of a network node according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

[0040] 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.”

[0041] 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.”

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

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

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

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

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

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

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

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

[0050] 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), 5G NR, and the like.

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

[0052] Network structure

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

[0054] 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 functions 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.

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

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

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

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

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

[0060] Systems applicable to this disclosure

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

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

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

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

[0065] Device applicable to the present disclosure

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

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

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

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

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

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

[0072] 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. Additionally, 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 operational 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 user data, control information, wireless signals / channels, etc. processed by at least one processor (202) from a baseband signal to an RF band signal. For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

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

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

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

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

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

[0080] 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 backhaul communications, and a wired transceiver may not be included.

[0081] Communication procedures

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

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

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

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

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

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

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

[0089] 6G system core technologies

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

[0091] artificial intelligence

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0153] THz communication (terahertz communication)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0172] non-terrestrial networks (NTN)

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

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

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

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

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

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

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

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

[0181] Integrated Sensing and Communication (ISAC)

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

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

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

[0185] Ambient IoT (ambient internet of things)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0209] Technical terms used in this disclosure may be as follows.

[0210] - SSB: Synchronization Signal Block

[0211] - MIB: Master Information Block

[0212] - RMSI: Remaining Minimum System Information

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

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

[0215] - BW: Bandwidth

[0216] - BWP: Bandwidth Part

[0217] - RNTI: Radio Network Temporary Identifier

[0218] - CRC: Cyclic Redundancy Check

[0219] - SIB: System Information Block

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

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

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

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

[0224] - MO: PDCCH monitoring opportunity for Type0-PDCCH CSS set

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

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

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

[0228] - MO-R: PDCCH monitoring opportunity for Type0-PDCCH CSS set

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

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

[0231] - SCS: subcarrier spacing

[0232] - SI-RNTI: System Information-RNTI

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

[0234] - TB: Transport Block

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

[0236] - SIB1(-R)-PDSCH: PDSCH transmitting SIB1(-R)

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

[0238] - SIB1(-R)-PDCCH: PDCCH transmitting SIB1(-R)-DCI

[0239] - FDRA: Frequency Domain Resource Allocation

[0240] - TDRA: Time Domain Resource Allocation

[0241] - RA: Random Access

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

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

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

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

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

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

[0248] - PG-R: MsgA-preamble group for redcap terminals

[0249] - RAR: Random Access Response

[0250] - RAR Window: Time window to monitor RA responses

[0251] - FH: Frequency Hopping

[0252] - iBWP: Initial BWP

[0253] - iBWP-DL(-UL): Initial DL(UL) BWP

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

[0255] - CS: Cyclic shift

[0256] - NB: Narrowband

[0257] - TO: Traffic Offloading

[0258] - mMTC: Massive Machine Type Communications

[0259] - eMBB: enhanced Mobile Broadband Communication

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

[0261] - RedCap: Reduced Capability

[0262] - eRedCap: Enhanced RedCap

[0263] - FDD: Frequency Division Duplex

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

[0265] - DRX: Discontinuous Reception

[0266] - RRC: Radio Resource Control

[0267] - RRM: Radio Resource Management

[0268] - MM: Mobility Management

[0269] - IWSN: Industrial Wireless Sensor Network

[0270] - LPWA: Low Power Wide Area

[0271] - RB: Resource Block

[0272] - CCE: Control Channel Element

[0273] - AL: Aggregation Level

[0274] - PRG: Physical Resource-block Group

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

[0276] - PBCH: Physical Broadcast Channel

[0277] - A-PBCH: Additional PBCH

[0278] - BD: blind detection

[0279] - EPRE: Energy Per RE

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

[0281] - TDM: Time Division Multiplexing

[0282] - FDM: Frequency Division Multiplexing

[0283] - DMRS: Demodulation Reference Signal

[0284] - TDD: Time Division Duplex

[0285] - PCI: Physical layer Cell ID

[0286] - EH: Energy Harvesting

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

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

[0289] - ET: Energy Transfer

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

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

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

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

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

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

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

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

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

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

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

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

[0302] - RF-EH: RF energy harvesting

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

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

[0305] - BS: Base Station

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

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

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

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

[0310] - AmIoT: Ambient IoT

[0311] - F-gap: Frequency gap

[0312] - T-gap: Time gap

[0313] - TD: Time Domain

[0314] - FD: Frequency Domain

[0315] - PEI: Paging Early Indication

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

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

[0318] - RSRP: Reference Signal Received Power

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

[0320] - PRB: Physical Resource Block

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

[0322] - PHR: Power Headroom Report

[0323] - EHR: Energy Headroom Report

[0324] - BPF: Band-Pass Filter

[0325] - SM: Subcarrier Modulation

[0326] - PIE: pulse interval encoding

[0327] Ambient IoT (AmIoT)-based communication

[0328] The present disclosure describes a method for transmitting and receiving signals in topologies 1 and 2, in which direct communication (i.e., 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.

[0329] For example, in topology 1, a direction from a base station (e.g., a gNB) 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 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 (e.g., an R2D channel or PRDCH), and the device may transmit a D2R message or data information to the base station via a D2R signal (e.g., a D2R channel or PDRCH).

[0330] 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 the 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 (e.g., an R2D channel or PRDCH), and the device may transmit a D2R message or data information to the intermediate node (IN) via a D2R signal (e.g., a D2R channel or PDRCH).

[0331] The examples described above in this disclosure can be commonly applied to topologies 1 and 2, and terminal 1 as a base station and an IN can be designated as a leader. In addition, a leader receiving a BSS can directly generate and transmit a CW, and the node transmitting the CW can be a separate node from the leader, and the examples described above in this disclosure can also be applied to such situations.

[0332] Additionally, an ambient IoT base station (e.g., a leader) may be a gNB in ​​topology 1 and may be a specific terminal in topology 2. Additionally, an ambient IoT device (e.g., a tag) described in the present disclosure may be interpreted as an ambient IoT device in topology 1 and / or topology 2.

[0333] In describing the present disclosure, a preamble means a unit transmitted at the very front of a specific D2R and / or R2D, a midamble means a unit transmitted at the middle of a specific D2R, R2D, and a postamble means a unit transmitted at the very end of a specific D2R, R2D.

[0334] Specifically, the physical channel PRDCH or / and PDRCH can include / transmit a TB (transport block) (or MAC PDU) of a higher layer. In addition, the PRDCH or / and PDRCH can include / transmit L1 control information (e.g., DCI, etc.) or L2 control information (e.g., MAC header or MAC CE, etc.). In this case, the PRDCH or / and PDRCH can be transmitted starting with a preamble and ending with a postamble. In addition, a midamble can be included / placed between L1 / L2 control information or TB transmission.

[0335] In describing the present disclosure, the X-amble may include / collectively refer to all of the preamble, midamble, and postamble. In addition, the preamble, midamble, and postamble may be transmitted together with D2R, R2D transmissions (e.g., PRDCH, PDRCH, etc.) or included in the D2R, R2D transmissions.

[0336] FIG. 16 is a diagram illustrating a case according to topology 1 to which some examples of the present disclosure may be applied. Nodes R, R1, and R2 in FIG. 16 all represent base stations or network nodes connected to base stations.

[0337] In the case according to (a) of Fig. 16 (e.g., D1TI-A1 case), each of the different R1 nodes (e.g., leader 1) and R2 nodes (e.g., leader 2) can perform R2D channel transmission and D2R channel reception, respectively. In this case, the R1 node can perform CW signal transmission.

[0338] In the case according to (b) of Fig. 16 (e.g., D1TI-A2 case), the same R node (e.g., leader) can perform R2D channel transmission and D2R channel reception. At this time, the R node can transmit a CW signal.

[0339] In the case according to (c) of Fig. 16 (e.g., D1TI-B case), the same R node (e.g., leader) can perform R2D channel transmission and D2R channel reception. In this case, the CW signal can be transmitted by a separate CW node.

[0340] FIG. 17 is a diagram illustrating a case according to topology 2 to which some examples of the present disclosure may be applied. Nodes R, R1, and R2 in FIG. 17 all represent terminals performing the IN role. As another example, in FIG. 17 (a), node R1 may represent a base station and node R2 may represent a terminal, or node R1 may represent a terminal and node R2 may represent a base station.

[0341] In the case according to (a) of Fig. 17 (e.g., D2T2-A1 case), each of the different R1 nodes (e.g., leader 1) and R2 nodes (e.g., leader 2) can perform R2D channel transmission and D2R channel reception, respectively. In this case, the R1 node can perform CW signal transmission.

[0342] In the case according to (b) of Fig. 17 (e.g., D2T2-A2 case), the same R node (e.g., leader) can perform R2D channel transmission and D2R channel reception. In this case, the R node can transmit a CW signal.

[0343] In the case according to (c) of Fig. 17 (e.g., D2T2-B case), the same R node (e.g., leader) can perform R2D channel transmission and D2R channel reception. In this case, the CW signal can be transmitted by a separate CW node.

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

[0345] Below, we will describe how an ambient IoT device (e.g., Terminal 1) requests resources from a leader (e.g., BS / gNB / intermediate node / Terminal 2, etc.).

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

[0347] Example 1

[0348] Embodiment 1 relates to a process in which an ambient IoT device (e.g., terminal 1, etc.) connects to a leader device (e.g., BS / gNB / intermediate node / terminal 2, etc.). As an example of the present disclosure, FIG. 18 is a flowchart illustrating a process in which an ambient IoT device connects to a leader device. Specifically, the connection process may be composed of an MSG0 transmission / reception process (Embodiment 1-1), an MSG1 transmission / reception process (Embodiment 1-2), an MSG2 transmission / reception process (Embodiment 1-3), an MSG3 transmission / reception process (Embodiment 1-4), an MSG4 transmission / reception process, and an MSG5 transmission / reception process (Embodiment 1-5).

[0349] (Example 1-1)

[0350] As an example of the present disclosure, a leader device may transmit MSG0 (e.g., a query signal and / or a PDCCH order, etc.) to an ambient IoT device. As an example, one or more leader devices may transmit MSG0 to an ambient IoT device according to an instruction from an upper node. As an example, multiple INs (e.g., multiple terminals 2, etc.) managed by the same base station may transmit MS0 according to an instruction from the base station.

[0351] For example, if MSG0 is a query signal, the ambient IoT device can determine whether to transmit MSG1 based on MSG0. MSG0 can be used as a DL sync signal, such as PSS / SSS. For example, MSG0 can be reused as a DL sync signal, such as PSS / SSS, or defined as a new sync signal.

[0352] Ambient IoT devices can monitor MSG0 for carrier sensing-based connectivity. MSG0 may include information indicating whether the ambient IoT device can connect to the reader device (e.g., whether the ambient IoT device can transmit MSG1). For example, if MSG0 includes information indicating "busy" or / and "idle," the ambient IoT device may determine that it can transmit MSG1 within a certain period of time.

[0353] Additionally or alternatively, ambient IoT devices may use the carrier of another device to avoid collisions. For example, (ambient IoT) device 2 may detect the carrier transmitted by device 1 and avoid accessing it for a period of time after detecting the carrier.

[0354] At this time, MSG0 may include connection-related system information. For example, the connection-related system information may include a timer value for connection operations, information related to the time interval during which MSG1 transmission is possible (e.g., information related to the start time, length, window pattern, etc.). Additionally or alternatively, the connection-related system information may be transmitted via a separate MSG 0 for each specific device type, and the MSG 0 may indicate that the system information applies only to the specific device type.

[0355] Additionally or alternatively, MSG0 may include information for resolving conflicts. For example, MSG0 may include probability-based access information, UE ID-based access information, early indication-based access information, UE group / type-based access information, service / access type-based access information, etc.

[0356] Additionally or alternatively, an ambient IoT device that detects the transmission of a message (e.g., MSG0, MSG2, MSG4, etc.) to another device may not transmit MSG 1. However, if the ambient IoT device does not detect such a message for a certain period of time, the ambient IoT device may transmit MSG 1.

[0357] For example, an ambient IoT device can monitor MSG0 to determine whether access to the leader device is permitted. If MSG0 indicates "Busy" or "Idle," the ambient IoT device can access the leader device only after the "Idle" indication.

[0358] (Example 1-2)

[0359] The ambient IoT device can (re)transmit MSG1 to the reader device. For example, the ambient IoT device can (re)transmit MSG1 to the reader device using backscattering. The method described below can also be applied to transmitting and receiving messages subsequent to MSG1 (e.g., MSG 3 / 5).

[0360] As an example of the present disclosure, when MSG1 is transmitted in a slotted ALOHA manner, the ambient IoT device can transmit MSG1 at a time aligned with a specific time point (e.g., a transmission time of a DL sync signal or MSG0 transmitted by a reader device, a CW (carrier wave) transmission time, a backscattering transmission time (e.g., ambient IoT device A or B), etc.). The slotted ALOHA manner is a method of transmitting data by unit time (e.g., slot). As another example, the ambient IoT device can transmit MSG1 by selectively backscattering CW.

[0361] Additionally, MSG 1 may include a sequence for collision avoidance. The sequence for collision avoidance may be determined based on at least one of the options described below.

[0362] When multiple leaders transmit MSG0, an ambient IoT device can only respond to one MSG0. For example, an ambient IoT device may transmit MSG1 in response to the first MSG0 transmission it received. In another example, an ambient IoT device may transmit MSG1 in response to the MSG0 transmission it received with the highest intensity.

[0363] (Example 1-3)

[0364] The ambient IoT device may receive MSG2 (from the reader device) after performing (re)transmission of MSG1. In one example of the present disclosure, MSG2 may include / indicate ACK and / or NACK information. For example, if the reader device successfully receives MSG1 and allows connection, MSG2 may include / indicate ACK. If the reader device does not successfully receive MSG1 or / and does not allow connection, MSG2 may include / indicate NACK.

[0365] For example, if MSG2 includes / indicates ACK, MSG2 may include at least one of information included in MSG1 (e.g., sequence information), transmission / reception resources of MSG1 (e.g., time / frequency resources), time / frequency for transmitting / receiving MSGs (e.g., MSG0, MSG1, MSG2, MSG3, MSG4, and / or MSG5, etc.), or CW time / frequency information for backscattering. If MSG2 includes / indicates NACK, MSG2 may include a back-off time.

[0366] (Example 1-4)

[0367] In one embodiment of the present disclosure, when an ACK including / indicating an ACK is received, the ambient IoT device may transmit MSG3 (to the reader device). For example, the ambient IoT device may transmit MSG3 in a backscattering manner. The selection of a time interval / point in time / frequency / resource for transmitting MSG3 may be determined / selected based on at least one of the transmission / reception time interval / point in time / frequency / resource selection methods of MSG2.

[0368] MSG3 may contain at least one of UE ID, sequence, early indication, UE group / type, connection type, RRC connection / resume request message for initial connection, and C-RNTI MAC CE for UE within RRC_CONNECTED.

[0369] Here, the UE ID (e.g., C-RNTI) may be scrambled, masked, or attached to all UL messages. The sequence may be part or all of the sequence selected for MSG1. In another example, the sequence may be part or all of a newly selected sequence using at least one of the MSG1 sequence selection methods described above. The early indication may include the device type (e.g., device A, device B, or device C) and / or other processing times. The RRC connection / resume request message may include the UE ID (e.g., s-TMSI or resumption ID), etc.

[0370] (Example 1-5)

[0371] An ambient IoT device that transmitted MSG 3 may receive MSG4 (from a reader device). MSG4 may include a UE ID (or / and contention resolution MAC CE) and / or sequence information. Here, the sequence may be selected / determined based on at least one of the MSG1 sequence selection methods described above.

[0372] If MSG4 contains the UE ID (or device ID) or sequence of the ambient IoT device, the ambient IoT device may transmit MSG5 (to the reader device).

[0373] For example, MSG5 may include terminal capability information. For example, the terminal capability information may include capability information related to device type (e.g., device type A, B, C), other processing times, early indication (e.g., device type, other processing times), terminal group / type, connection type, etc. Additionally or alternatively, MSG5 may include at least one of a UE ID, a sequence, and user data.

[0374] Example 2

[0375] Example 2 relates to a method for requesting R2D transmission and D2R reception resources of an IN UE of topology 2.

[0376] In one embodiment of the present disclosure, an IN terminal can perform PRDCH transmission (e.g., R2D transmission) and PDRCH reception. To this end, the terminal can transmit signals / information requesting PRDCH resources for one or more devices and / or PRDCH resources transmitted by one or more devices to the base station. For example, the terminal can transmit PRDCH resources and / or information / signals requesting PRDCH resources to the base station via a PUCCH for SR or a MAC CE (e.g., a MAC CE associated with a buffer status report (BSR)).

[0377] In one embodiment of the present disclosure, if buffered data exists / is included on a logical channel for R2D transmission, the terminal may trigger a MAC CE for PRDCH (e.g., trigger a MAC CE transmission). If a D2R response transmission is expected according to buffered R2D data transmission before or after a D2R transmission, or if buffered D2R data is generated in the terminal upon receiving a D2R transmission, the terminal may trigger a MAC CE for PDRCH (e.g., trigger a MAC CE transmission).

[0378] When a MAC CE for PRDCH is triggered and / or a MAC CE for PDRCH is triggered and PUSCH resources for transmitting the MAC CE(s) do not exist / are not allocated (within a certain period of time), the UE may trigger an SR, and a pending SR may occur for this. Here, the certain period of time may be determined according to the QoS parameters (e.g., delay requirements) of the buffered data.

[0379] In the above-described operation, the terminal may trigger a BSR MAC CE instead of a new MAC CE for PRDCH / PDRCH. In this case, the BSR MAC CE may include a buffer size for a logical channel for R2D and a buffer size for a logical channel for D2R.

[0380] At this time, the MAC CE for PRDCH can request the buffered data size, the number of radio resources of PRDCH transmission resources, the PRDCH transmission length, or the number of PRDCH frequency channels per logical channel for R2D, per logical channel group for R2D, per inventory round, per query message, per procedure, or per R2D message. The buffered data size, the number of RBs, or the transmission length can be requested per device (group) or for all devices belonging to the IN terminal. The transmission length can be a PRDCH transmission length considering the currently applied chip rate for the corresponding device or a PRDCH transmission length considering a specific default chip rate.

[0381] Additionally, the MAC CE for PDRCH can request the buffered data size, the number of radio resources of PDRCH transmission resources, the PDRCH transmission length, or the number of PDRCH frequency channels per logical channel for D2R, per logical channel group for D2R, per inventory round, per query message, per procedure, or per D2R message. The buffered data size, the number of RBs, or the transmission length can be requested per device (group) or for all devices belonging to an IN terminal. The transmission length can be a PDRCH transmission length considering the currently applied chip rate for the corresponding device or a PDRCH transmission length considering a specific default chip rate.

[0382] For example, the MAC CE for PRDCH / PDRCH may be a single common MAC CE that includes requests for both PRDCH and PDRCH. As another example, the MAC CE requesting PDRCH (e.g., MAC CE for PDRCH) and the MAC CE requesting PRDCH (e.g., MAC CE for PRDCH) may be configured / defined separately.

[0383] As an example of the present disclosure, for a case where an SR is triggered for R2D or D2R transmission, a PUCCH SR requesting R2D resources may be set according to at least one of the methods described below.

[0384] Method 1: The SR setting of the logical channel that triggered the MAC CE for PRDCH / PDRCH can be considered as the corresponding SR setting for the triggered SR. The priority value of the triggered SR can correspond to the priority value of the logical channel that triggered the SR.

[0385] Method 2: Each PRDCH / PDRCH channel priority or device priority can be mapped to zero or one SR configuration configured by RRC. The priority value of a triggered SR triggered by a MAC CE for the PRDCH / PDRCH can correspond to the priority value of the PRDCH / PDRCH channel or device that triggers the MAC CE for the PRDCH / PDRCH. The priority can be configured by the gNB (e.g., through dedicated signaling or system information) or by a preset configuration.

[0386] Example 3

[0387] Example 3 relates to the MAC CE priority of the IN terminal of topology 2.

[0388] In the present disclosure, if a priority value for a specific data / transmission is equal to or lower than a threshold value, this may indicate that the specific data / transmission has a higher priority. If a priority value for a specific data / transmission is equal to or higher than a threshold value, this may indicate that the specific data / transmission has a lower priority.

[0389] For PUSCH transmission, an IN terminal can configure RLC PDU(s) for one or more logical channels and zero or one or more MAC CEs into a single MAC PDU. Then, the IN terminal can transmit a PUSCH containing one MAC PDU to the base station. At this time, when the MAC PDU size is determined, only a limited number of MAC CE(s) can be included in the MAC PDU according to the priority described below.

[0390] - Logical channels can be prioritized in the following order (highest priority listed first):

[0391] - MAC CE for data on C-RNTI or UL-CCCH (common control channel);

[0392] - MAC CE for (enhanced) BFR, MAC CE for confirmation of established grant, or MAC CE for confirmation of multiple entry established grant;

[0393] - MAC CE for sidelink setup grant verification;

[0394] - MAC CE for LBT (listen before talk) failure;

[0395] - MAC CE for SL(sidelink) LBT failure;

[0396] - MAC CE for timing advance reporting;

[0397] - MAC CE for delay status reporting;

[0398] - (Alternative 1) MAC CE for PRDCH or PDRCH;

[0399] - MAC CE for prioritized SL-BSR;

[0400] - (Alternative 2) MAC CE for PRDCH or PDRCH;

[0401] - MAC CE for (extended) BSR, excluding BSR included for padding;

[0402] - MAC CE of (enhanced) single-entry PHR (power headroom report), MAC CE of (enhanced) multi-entry PHR, MAC CE of single-entry PHR with assumed PUSCH, or MAC CE of multi-entry PHR with assumed PUSCH;

[0403] - (Alternative 3) MAC CE for PRDCH or PDRCH;

[0404] - MAC CE for location measurement gap enable / disable request;

[0405] - MAC CE for the desired number of guard symbols;

[0406] - MAC CE for Case-6 timing request;

[0407] - MAC CE for (extended) preemptive BSR;

[0408] - Excluding MAC CE for SL-BSR, SL-BSR priority and padding for SL-BSR;

[0409] - MAC CE for IAB-MT recommended beam marking, or MAC CE for desired IAB (integrated access backhaul)-MT (mobile terminal) PSD (power spectrum density) range, or MAC CE for desired DL Tx power adjustment;

[0410] - Data of all logical channels except data of UL-CCCH;

[0411] - MAC CE for recommended bitrate query;

[0412] - MAC CE for BSR included for padding;

[0413] - MAC CE for SL-BSR included for padding.

[0414] At this time, the priority between MAC CEs with the same priority may depend on the terminal implementation.

[0415] The MAC entity must prioritize all MAC CEs listed higher than 'data on all logical channels except UL-CCCH data' over NR sidelink transmissions and PRDCH / PDRCH / preamble / midamble / postamble. Terminals supporting both NR UL and D2R or R2D can prioritize all MAC CEs over the postamble.

[0416] A terminal may transmit a MAC CE to request PDRCH and / or PDRCH transmission resources. At this time, as in alternative 1, alternative 2, and / or alternative 3, the priority of the MAC CE for the PDCRCH and / or PDRCH may be higher or lower than the priority of the MAC CE for the BSR. In addition, the priority of the MAC CE for the PDCRCH and / or PDRCH may be higher or lower than the priority of the MAC CE for the SL-BSR. In addition, the priority of the MAC CE for the PRDCH may be set higher or lower than the priority of the MAC CE for the PDRCH.

[0417] Example 4

[0418] Example 4 relates to priorities between R2D transmission and SR PUCCH transmission of an IN terminal in topology 2.

[0419] An IN terminal may or may not perform PRDCH transmission and scheduling request simultaneously. The terminal may prioritize PUCCH transmission for SR or trigger RACH for SR according to the conditions and methods described below.

[0420] If at least one SR is pending, the MAC entity may perform the following actions for each pending SR:

[0421] 1> If there is no valid PUCCH resource set for the pending SR in the MAC entity; and

[0422] 1> If there is no LTM cell switch in progress; and

[0423] 1> If "rach-lessHO(handover)" is not set:

[0424] 2> Start a random access procedure in SpCell and cancel the pending SR.

[0425] 1> Otherwise, for SR settings corresponding to pending SR:

[0426] 2> When the MAC entity has an opportunity to transmit SR on a valid PUCCH resource set for SR; and

[0427] 2> If the "sr-ProhibitTimer" (e.g., the timer for SR transmission on PUCCH) is not running at the time of the SR transmission opportunity; and

[0428] 2> If the PUCCH resources and measurement gap for SR transmission opportunities do not overlap:

[0429] 3> If the MAC entity can perform the corresponding SR transmission simultaneously with the R2D transmission; or

[0430] 3> When both "r2d-PrioritizationThres" (e.g., priority thresholds associated with R2D transmissions) and "ul-PrioritizationThres" (e.g., uplink priority thresholds that can be used to determine whether SL transmissions are prioritized over UL transmissions) are set and the PUCCH resources for the SR transmission opportunity for the pending SR triggered on the PRDCH overlap with all UL-SCH resources carrying the MAC PDU, and the priority value of the triggered SR on the PRDCH is lower than "r2d-PrioritizationThres", and the highest priority value of the logical channel of the MAC PDU is higher than or equal to "ul-PrioritizationThres", and not all MAC CEs that are prioritized as described above are included in the MAC PDU, and the MAC PDU is not prioritized in a higher layer; or

[0431] 3> When both "d2r-PrioritizationThres" and "ul-PrioritizationThres" are set and a PUCCH resource for an SR transmission opportunity for a pending SR triggered on a PDRCH overlaps with any UL-SCH resource carrying a MAC PDU, and a priority value of the triggered SR on the PDRCH is lower than "d2r-PrioritizationThres" (i.e., a priority threshold associated with a D2R transmission), and the highest priority value of the logical channel of the MAC PDU is higher than or equal to "ul-PrioritizationThres", and not all prioritized MAC CEs are included in the MAC PDU as described above, and the MAC PDU is not prioritized in a higher layer; or

[0432] 3> When a PRDCH resource overlaps with a PUCCH resource for an SR transmission opportunity for a pending SR triggered on PUSCH, the MAC entity cannot perform the SR transmission concurrently with the PRDCH resource transmission, and the transmission on the PRDCH resource is not prioritized as described above or the priority value of the logical channel that triggered the SR is lower than "ul-PrioritizationThres" (if set); or

[0433] 3> If the PRDCH resource overlaps with the PUCCH resource for the SR transmission opportunity for the pending SR triggered for the PRDCH or PDRCH, if the MAC entity cannot perform the SR transmission at the same time as the PRDCH resource transmission, or if the priority of the triggered SR determined for the PRDCH or PDRCH is higher than the priority of the MAC PDU determined for the PRDCH resource; or

[0434] 3> If the PRDCH resource overlaps with the PUCCH resource for the SR transmission opportunity for the pending SR triggered on the PRDCH or PDRCH, if the MAC entity cannot perform the SR transmission simultaneously with the PRDCH resource transmission, or if the priority of the triggered SR determined on the PRDCH or PDRCH is higher than the priority of the MAC PDU to be received on the PDRCH resource; or

[0435] 4> SR transmission is considered as a high priority SR transmission.

[0436] 4> Except for overlapping uplink grants for which simultaneous transmission is allowed by the configuration of simultaneous PUCCH-PUSCH or simultaneous "PUCCH-PUSCH-SecondaryPUCCHgroup" or simultaneous "SR-PUSCH-diffPUCCH-Groups", if there is another overlapping uplink grant, it is regarded as an uplink grant with a lower priority.

[0437] 4> If the uplink grant with deprioritized status is a "configured uplink grant" that is already set to "autonomousTx" (i.e., configuration information related to autonomous transmission) with PUSCH initiated:

[0438] 5> Stop the grant timer configured for the corresponding HARQ process of the uplink grant with lower priority.

[0439] 5> Stop the "cg-RetransmissionTimer" (i.e., the timer related to retransmission) for the corresponding HARQ process of the lowered priority uplink grant.

[0440] 4> If SR_COUNTER < "sr-TransMax" (i.e. maximum number of SR transmissions):

[0441] 5> Instructs the physical layer to signal the SR on one valid PUCCH resource for the SR.

[0442] 5> If no LBT failure indication is received from the lower layer:

[0443] 6> Increase SR_COUNTER by 1.

[0444] 6> Start the "sr-ProhibitTimer" (e.g., a timer for SR transmission on PUCCH).

[0445] 5> If "lbt-FailureRecoveryConfig" (i.e. configuration information related to parameters used to detect consistent uplink LBT failures using shared spectrum channel access) is not set:

[0446] 6> Increase SR_COUNTER by 1.

[0447] 4> If not:

[0448] 5> Notify RRC to release PUCCH for all serving cells;

[0449] 5> Notify RRC to release SRS for all serving cells;

[0450] 5> Clear all configured downlink allocations and uplink grants;

[0451] 5> Clear all PUSCH resources for semi-persistent CSI reporting;

[0452] 5> If "rach-lessHO" is not set:

[0453] 6> Start a random access procedure in SpCell and cancel all pending SRs.

[0454] 3> If not:

[0455] 4> SR transmission is considered as a low priority SR transmission.

[0456] A MAC entity may abort an ongoing random access procedure due to a pending SR on the PRDCH or PDRCH, which was initiated by the MAC entity prior to the assembly of the R2D MAC PDU for the UL MAC PDU carrying D2R data on the PRDCH or PUSCH, and a valid PUCCH resource may not be established. The above operation may be performed when at least one of the conditions described below is satisfied.

[0457] - When a MAC PDU is transmitted using a UL grant other than the UL grant provided in the Random Access Response or the UL grant determined for MSGA payload transmission, and the PDU includes a MAC CE for the PRDCH / PDRCH that includes the buffer status up to (and including) the last event that triggered a MAC CE for the PRDCH / PDRCH prior to MAC PDU assembly; or

[0458] - PRDCH / PDRCH resources accommodate all pending data available for R2D / D2R transmission.

[0459] Example 5

[0460] Example 5 relates to a PRDCH / PDRCH resource allocation and request method between a leader and a device.

[0461] The PRDCH channel can allocate CW time / frequency resources (e.g., frequency channel and reception timing) for backscattering or / and energy harvesting via the PRDCH's x-amble, L1 control information, or L2 control information (e.g., MAC header or MAC CE included in a MAC PDU).

[0462] Additionally, time / frequency resources of the PDRCH channel (e.g., FDRA with frequency shift or frequency hopping on / off / pattern and TDRA with midamble presence and maximum time interval) can be allocated.

[0463] When the device transmits a PDRCH channel upon reception of the PRDCH channel, and / or when the device transmits PDRCH channel(s) after reception of the PRDCH channel, the device may transmit the PDRCH channel(s) according to the CW time / frequency resources and / or the time / frequency resources of the PDRCH channel indicated by the x-amble, L1 control information or L2 control information of the PRDCH.

[0464] For example, according to the above instructions, the device may decide to perform backscattering for PDRCH transmission using CW time / frequency resources or to perform energy harvesting.

[0465] Additionally or alternatively, the device may determine whether to frequency shift the PDRCH channel, determine a frequency channel according to the frequency shift, determine whether to frequency hop, or determine frequency channel or frequency domain resource allocation according to a frequency hopping pattern, according to the above instructions.

[0466] Additionally or alternatively, the device may determine the maximum time interval or transmission length of the PDRCH channel, or determine whether to include a preamble, midamble, or postamble, or the transmission length, based on the above instructions. The device may transmit the PDRCH based on these determinations.

[0467] As an example of the present disclosure, when a maximum time interval or transmission length is allocated according to the above-described method, the device can transmit the PDRCH for the allocated length. In this case, the allocated length can be defined as the length of data transmission only, excluding some or all of the x-amble, L1 control information, or L2 control information of the PDRCH.

[0468] For example, the allocated length may be the length from the preamble to the postamble, the length from the preamble to just before the postamble, the length from the L1 / L2 control information to just before the postamble, or the transmission length of pure data (e.g., TB, MAC PDU).

[0469] As an example of the present disclosure, if a maximum time interval or transmission length is allocated according to the method described above, the device may not be able to transmit all data during the allocated length.

[0470] For example, due to the time required for data processing, the entire payload may not be transmitted within the maximum time interval. In this case, the device may transmit information requesting additional PDRCH time / frequency resources via an x-amble, L1 control information, or L2 control information (e.g., MAC header or MAC CE).

[0471] At this time, the request information may include one, some, or all of the requested 1-bit information, PDRCH transmission (maximum / minimum) length, TB / MAC PDU / MAC SDU size, PDRCH frequency channel, PDRCH transmission start (maximum / minimum) time, and PDRCH transmission end (maximum / minimum) time.

[0472] Meanwhile, if the device starts a timer after receiving a PRDCH and performs PDRCH transmission corresponding to the PRDCH before the timer expires, the device may transmit information requesting timer extension or restart through an x-amble, L1 control information (e.g., SR), or L2 control information (e.g., MAC header or MAC CE) (e.g., BSR MAC CE).

[0473] The above request information may include one, some, or all of the requested 1-bit information, the timer (maximum / minimum) length after the timer was initially started, whether the timer is extended / restarted, the extended timer (maximum / minimum) length when the timer is extended, and the restarted timer (maximum / minimum) length. When extending / restarting the timer, the device may extend / restart the timer from the start or end time of the requested PDRCH transmission.

[0474] When a device transmits request information via a postamble of the PDRCH, the postamble may be constrained to be transmitted within the allocated length or immediately after. Alternatively, the postamble may be configured to be transmitted across the end of the allocated length.

[0475] A leader that receives the request information can transmit the PRDCH channel. At this time, the PRDCH channel can allocate the time / frequency resources of the PDRCH channel (e.g., FDRA with frequency shift or frequency hopping on / off / pattern and TDRA with midamble presence and maximum time interval). If there is no R2D data, only the preamble for allocation, or only the preamble and L1 / L2 control information, can be transmitted.

[0476] Example 6

[0477] Example 6 is about how to categorize resources.

[0478] The gNB can categorize transmit and receive resources for R2D / D2R signals (e.g., PRDCH / PDRCH) into the following categories. These categories can apply to both dynamic and semi-static (or configured) resources:

[0479] - TX dedicated resources of gNB / IN (i.e. R2D signaling resources);

[0480] -- The resource types described above can be set for system information or paging transmission for initial connection of the device.

[0481] - TX and CW resources of gNB / IN (e.g., R2D signal resources and CW transmission resources);

[0482] -- The resource type described above can be set for paging transmission for initial connection of a device, or a device that has already completed connection can be set with RX-only resources.

[0483] - TX, CW and RX resources of gNB / IN (e.g., R2D signal transmission resources, CW transmission resources and D2R signal reception resources);

[0484] -- The resource types described above can be set up for device-specific message exchange after the devices complete their initial connection.

[0485] - CW and RX resources of gNB / IN (e.g., CW transmission resources and D2R signal reception resources);

[0486] -- The resource type described above can be configured to allow the device to send a delayed response to the leader.

[0487] - CW transmission-only resources;

[0488] -- The resource types described above can be set for CW transmission by the leader or a separate CW transmitting node.

[0489] - RX dedicated resources of gNB / IN;

[0490] The resource type described above can be configured for a device to receive CW from a separate node and send a delayed response to the leader.

[0491] When configuring one or more resource pools, the gNB or IN may configure / indicate that a specific resource pool belongs to one of the categories described above. For example, the gNB may configure a specific resource pool to belong to one of the categories described above via an RRC message, and may configure / reconfigure / indicate that the configured resource pool belongs to a specific category via a MAC CE or DCI transmitted to the IN.

[0492] The gNB can configure specific logical channels to be D2R only, R2D only, or both D2R and R2D.

[0493] For example, if a logical channel is dedicated to D2R, the gNB or IN selects a resource from a resource pool in a category that supports D2R transmission resources to receive data for that logical channel.

[0494] As another example, if a logical channel is dedicated to R2D, the gNB or IN selects a resource from a resource pool in a category that supports R2D transmission resources to transmit data for that logical channel.

[0495] As another example, if the logical channel is both D2R / R2D, the gNB or IN can select a resource from a resource pool in a category that supports R2D transmission resources to transmit R2D data, select a resource from a resource pool in a category that supports D2R transmission resources to receive D2R data, and select a resource from a resource pool in a category that supports both D2R / R2D to transmit R2D data or receive D2R data.

[0496] Example 7

[0497] Example 7 relates to a method for sharing resource information between gNBs.

[0498] Step 1: gNB1 can share information about the time / frequency resources it has used, the time / frequency resources it is currently using, and / or the time / frequency resources it plans to use with gNB2. The resource information shared by gNB1 is as follows:

[0499] - Time / frequency resources that gNB1 has used, is using, or plans to use;

[0500] - Time / frequency resource(s) used, in use, or scheduled to be used by one or more INs belonging to the cell of gNB1; and / or

[0501] - “Used, in use or scheduled to be used time / frequency resources” as indicated by the shared information received by gNB1 from gNB3.

[0502] Step 2: gNB 2 may reselect the time / frequency resources to be used by gNB 2 or its INs based on the information shared from gNB 1 in Step 1.

[0503] - Time / frequency resources to be used by gNB2 or INs of gNB2 can be (re)selected from among the remaining time / frequency resources excluding the time / frequency resources that have been used, are being used, or are scheduled to be used included in the gNB 1 shared information of Step 1.

[0504] - If the used, in-use or scheduled-to-be-used time / frequency resources included in the gNB 1 shared information of Step 1 overlap with the time / frequency resources to be used by gNB2 or the INs of gNB2, the time / frequency resources are excluded and the time / frequency resources to be used by gNB2 or the INs of gNB2 may be (re)selected.

[0505] As an example of the present disclosure, gNB2 can share time / frequency resource information used, currently in use, or scheduled to be used with gNB1. The resource information shared by gNB2 can modify or verify the information shared by gNB1, and may include the following information:

[0506] - Time / frequency resources that gNB2 has used, is using, or plans to use;

[0507] - Time / frequency resources that have been used, are being used, or are scheduled to be used by one or more INs belonging to the cell of gNB2;

[0508] - "Time / frequency resources used, being used or scheduled to be used" as indicated by the shared information received by gNB2 from gNB4;

[0509] - Time / frequency resources that gNB2 has used, is using, or is scheduled to use among the time / frequency resources of gNB1 / IN / gNB3 that gNB1 shared in step 1; and / or

[0510] - Request for consent, modification, or rejection of the use of time / frequency resources of gNB1 / IN / gNB3 shared by gNB1 in Step 1.

[0511] Step 3: gNB 1, which has received the shared information of gNB 2 in Step 2, can perform the following actions:

[0512] - gNB 1 can maintain the time / frequency resources of gNB1 / IN with the consent of gNB2.

[0513] - gNB 1 may not use specific time / frequency resources of gNB1 / IN based on modification request or rejection by gNB2 and may reselect time / frequency resources to avoid them.

[0514] At this time, gNB 1 can perform step 1 again to share the reselection resource information with gNB2.

[0515] Example 8

[0516] Example 8 relates to a method for allocating time / frequency resources to INs belonging to a cell of a gNB.

[0517] As an example of the present disclosure, when one or more INs transmit an R2D signal temporarily or one-shot, such as a wake-up signal, the gNB may transmit a specific DCI or MAC CE to the INs and allocate time / frequency resources through the specific DCI or MAC CE.

[0518] - A DCI scheduling a PDSCH carrying a specific DCI or MAC CE may be CRC scrambled by a terminal-specific RNTI of the IN (e.g., C-RNTI or new IN-RNTI) or by an IN group RNTI (e.g., G-RNTI or new ING-RNTI) assigned to multiple IN groups.

[0519] - A specific DCI indicates a time difference and a specific time / frequency resource of a specific channel, and an IN that receives a specific DCI can transmit an R2D signal with the time / frequency resource of the indicated channel after the time difference indicated by the DCI.

[0520] - MAC CE indicates a time / frequency resource pattern of a specific channel for a certain time period, and an IN that receives the MAC CE can transmit an R2D signal according to the time / frequency resource pattern of the indicated channel after the application time of the MAC CE.

[0521] As an example of the present disclosure, when one or more INs transmit periodic or pattern-based persistent R2D signals (e.g., system information or paging signals), the gNB may transmit specific MAC CE and / or RRC messages to the INs, thereby configuring / allocating periodic or persistent time / frequency resources.

[0522] An IN that has received an RRC message or MAC CE that sets up periodic or continuous time / frequency resources can allocate / activate the periodic or continuous time / frequency resources after the utilization time according to the instructions of the RRC message or MAC CE, and can transmit an R2D message with the periodic or continuous time / frequency resources accordingly.

[0523] The gNB may send another RRC message, MAC CE, or DCI to the IN to instruct it to transmit a specific R2D message periodically or continuously using the periodic or continuous time / frequency resources.

[0524] At this time, a specific R2D message can be generated and transmitted by the gNB or the IN. If the gNB or the core network generates a specific R2D message, the gNB can additionally transmit the generated R2D message to the IN by including it in the RRC message, MAC CE, or DCI.

[0525] Additionally, the gNB may send another RRC message, MAC CE, or DCI to the IN to indicate that the periodic or continuous transmission of the specific R2D message should be discontinued. The specific R2D message may be a system information message, a paging message, a selection message, or a query message.

[0526] The gNB may deactivate or release the periodic or persistent time / frequency resources by sending another RRC message or MAC CE to the IN.

[0527] The gNB can activate, deactivate or release the configured / allocated periodic or persistent time / frequency resources by transmitting DCI or MAC CE to the IN.

[0528] If the R2D signal is system information, periodic or continuous time / frequency resources can be specified for transmitting the system information. The IN can use the time / frequency resources to transmit the system information to devices.

[0529] For example, if the R2D signal is paging, periodic or continuous time / frequency resources may be the same as or include a paging occasion (PO). The IN can use the time / frequency resources to transmit paging to devices.

[0530] The gNB can allocate the same or different time / frequency resources to different INs as POs. At this time, the gNB can configure a specific PO to transmit paging for a specific paging group. The IN can then only transmit paging for a specific paging group from a specific PO.

[0531] FIGS. 19 and 20 illustrate the operation of a device and a network node in relation to a method of performing AmIoT communication according to embodiments of the present disclosure described above.

[0532] In FIGS. 19 and 20, based on various topologies in AmIoT communication, each terminal and / or base station can be replaced with any one of an intermediate node (IN), an auxiliary node (AN), and an AmIoT device. In FIGS. 19 and 20, the terminal may correspond to a leader (e.g., an intermediate node, an auxiliary node, etc.), but is not limited thereto.

[0533] The terminal may receive first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH) from the base station (S1910).

[0534] As an example of the present disclosure, the first configuration information may include at least one of a priority threshold associated with reader-to-device (R2D), a priority threshold associated with device-to-reader (D2R), or a priority threshold associated with uplink. Additionally or alternatively, the first configuration information may include resource information associated with at least one SR among the first PDRCH or PRDCH.

[0535] The terminal may receive the first configuration information from the base station via a radio resource control (RRC) message, but is not limited thereto.

[0536] Prior to step S1910, the terminal may transmit information to the base station regarding whether simultaneous transmission of the first PUCCH and the second PRDCH is possible. Figures 19 and 20 illustrate a case where the terminal is not capable of simultaneous transmission of the first PUCCH and the second PRDCH. If simultaneous transmission of the first PUCCH and the second PRDCH is possible, the terminal may perform simultaneous transmission of the first PUCCH and the first channel.

[0537] Based on the overlap of the first resource for the first physical uplink control channel (PUCCH) including the first SR and the second resource for the first channel, the terminal can transmit the first PUCCH to the base station based on the priority of the first SR (S1920).

[0538] For example, assume that a first resource (e.g., a first time resource, a first frequency resource, or / and a first transmission opportunity (TO), etc.) for a first PUCCH transmission including a first SR overlaps with a second resource (e.g., a second time resource, a second frequency resource, or / and a second TO, etc.) for the first channel.

[0539] Here, the first channel may include at least one of a second PDRCH, a second PRDCH, a second PUCCH including a second SR, or a physical uplink shared channel (PUSCH).

[0540] As an example of the present disclosure, assume that the first channel is a PUSCH and the first resource is associated with an SR for the first PRDCH. In this case, the priority of the first SR may be lower than a threshold value for a priority associated with leader-to-device (R2D), and the priority of the first channel may be higher than a threshold value for a priority associated with uplink. Accordingly, the terminal may consider / determine that the first SR transmission has a higher priority and transmit the first PUCCH to the base station.

[0541] As another example of the present disclosure, assume that the first channel is a PUSCH and the first resource is associated with an SR for the first PDRCH. In this case, the priority of the first SR may be lower than a priority threshold associated with device-to-reader (D2R), and the priority of the first channel may be higher than a priority threshold associated with uplink. Accordingly, the terminal may consider / determine that the first SR transmission has a higher priority and transmit the first PUCCH to the base station.

[0542] As another example of the present disclosure, assume that the first channel is a second PDRCH or a second PRDCH. In this case, the priority of the first SR may be higher than that of the second PRDCH or the second PDRCH. Accordingly, the terminal may consider / determine that the first SR transmission has a higher priority and transmit the first PUCCH to the base station.

[0543] For example, a terminal may receive first downlink control information (DCI) from a base station for scheduling resources for a first PDRCH or a first PRDCH. That is, the terminal may perform scheduling of the first PDRCH or the first PRDCH based on the DCI.

[0544] And, at the time of the transmission occasion of the first SR, the timer for transmission of the first SR on the first PUCCH may not run.

[0545] The method described in the example of FIG. 19 can be performed by the wireless device (200) of FIG. 3. That is, the terminal of FIG. 19 can be implemented as the wireless device (200). For example, one or more processors (202) of the wireless device (200) of FIG. 3 can receive first configuration information related to an SR for a first PRDCH or a first PDRCH from a base station through one or more transceivers (206). Based on the overlap of a first resource for a first PUCCH including the first SR and a second resource for the first channel, the one or more processors (202) can transmit the first PUCCH to the base station through one or more transceivers (206) based on the priority of the first SR.

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

[0547] Figure 20 illustrates the operation of a base station according to an embodiment of the present disclosure.

[0548] The base station may transmit first configuration information related to SR for the first PRDCH or the first PDRCH to the terminal (S2010). For example, the base station may transmit the first configuration information to the terminal via an RRC message (or signaling), but is not limited thereto.

[0549] As described above, the first configuration information may include at least one of a priority threshold associated with R2D, a priority threshold associated with D2R, or a priority threshold associated with uplink.

[0550] Based on the overlap of the first resource for the first PUCCH including the first SR and the second resource for the first channel, the base station can receive the first PUCCH from the terminal based on the priority of the first SR (S2020).

[0551] Specifically, whether to transmit the first PUCCH can be determined based on the comparison result between the priority of the first SR and the priority threshold associated with R2D / D2R. The procedure for transmitting the first PUCCH from the terminal to the base station has been described above, so a redundant description will be omitted.

[0552] The method described in the example of FIG. 20 can be performed by the wireless device (200) of FIG. 3. That is, the base station of FIG. 20 can be implemented by the wireless device (200). For example, one or more processors (202) of the wireless device (200) of FIG. 3 can transmit first configuration information related to an SR for a first PRDCH or a first PDRCH to a terminal via one or more transceivers (206). Based on the overlap of a first resource for a first PUCCH including the first SR and a second resource for the first channel, the one or more processors (202) can receive the first PUCCH from the terminal via one or more transceivers (206) based on the priority of the first SR.

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

[0554] By the various embodiments described above, a leader terminal can efficiently request various resources from a base station through PUCCH SR, and the base station can allocate R2D / D2R resources to the terminal.

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

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

1. A step of receiving, by a terminal, first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH) from a base station; and A step of transmitting, by the terminal, the first PUCCH to the base station based on the priority of the first SR, based on the overlap of a first resource for the first physical uplink control channel (PUCCH) including the first SR and a second resource for the first channel, A method wherein the first channel includes at least one of a second PDRCH, a second PRDCH, a second PUCCH including a second SR, or a physical uplink shared channel (PUSCH).

2. In paragraph 1, Based on the above first channel being the PUSCH and the above first resource being associated with an SR for the above first PRDCH: The priority of the above first SR is less than the threshold value of the priority associated with the leader-to-device (R2D), A method wherein the priority of the first channel is greater than a threshold value of a priority associated with the uplink.

3. In paragraph 2, Based on the above first channel being the PUSCH and the above first resource being associated with an SR for the above first PDRCH: The priority of the above first SR is less than the threshold value of the priority associated with device-to-reader (D2R), A method wherein the priority of the first channel is greater than a threshold value of a priority associated with the uplink.

4. In paragraph 3, A method wherein the first setting information includes at least one of a priority threshold value related to the R2D, a priority threshold value related to the D2R, or a priority threshold value related to the uplink.

5. In paragraph 1, Based on the above first channel being the second PDRCH or the second PRDCH: A method wherein the priority of the first SR is higher than the priority of the second PRDCH or the second PDRCH.

6. In paragraph 1, A method in which first downlink control information (DCI) for scheduling resources for the first PDRCH or the first PRDCH is transmitted from the second device to the first device.

7. In paragraph 1, A method in which information related to whether simultaneous transmission of the first PUCCH and the second PRDCH is possible is transmitted from the first terminal to the base station.

8. In paragraph 1, A method in which a timer for transmission of the first SR on the first PUCCH does not operate at the time of a transmission occasion of the first SR.

9. In paragraph 1, A method in which the above first setting information is transmitted from the base station to the terminal via a radio resource control (RRC) message.

10. In paragraph 1, The above terminal corresponds to a reader, A method in which the first PRDCH is transmitted from the terminal to an ambient Internet of Things (IoT) device.

11. One or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receive first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH) from a base station through the one or more transceivers; and Based on the overlap of a first resource for a first physical uplink control channel (PUCCH) including the first SR and a second resource for the first channel, the first PUCCH is set to be transmitted to the base station through the one or more transceivers based on the priority of the first SR. A terminal, wherein the first channel includes at least one of a second PDRCH, a second PRDCH, a second PUCCH including a second SR, or a physical uplink shared channel (PUSCH).

12. A step of transmitting first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH) to a terminal by a base station; and A step of receiving the first PUCCH from the terminal based on the priority of the first SR by the base station based on the overlap of the first resource for the first physical uplink control channel (PUCCH) including the first SR and the second resource for the first channel, A method wherein the first channel includes at least one of a second PDRCH, a second PRDCH, a second PUCCH including a second SR, or a physical uplink shared channel (PUSCH).

13. 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 first configuration information related to a scheduling request (SR) for a first physical device to reader channel (PRDCH) or a first physical reader to device channel (PDRCH) to a terminal through the one or more transceivers; and Based on the overlap of a first resource for a first physical uplink control channel (PUCCH) including the first SR and a second resource for the first channel, the first PUCCH is set to be received from the terminal through the one or more transceivers based on the priority of the first SR, A device wherein the first channel includes at least one of a second PDRCH, a second PRDCH, a second PUCCH including a second SR, or a physical uplink shared channel (PUSCH).

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

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

Images