Method and device for transmitting or receiving scheduling information through downlink shared channel in wireless communication system

Abstract

Disclosed are a method and a device for transmitting or receiving scheduling information through a downlink shared channel in a wireless communication system. A method according to an embodiment of the present disclosure may comprise the steps of: receiving, by a terminal from a network, first scheduling information related to a scheduling-downlink shared channel; on the basis of the first scheduling information, receiving, by the terminal from the network, the scheduling-downlink shared channel including second scheduling information related to one or more scheduled-shared channels; and on the basis of the second scheduling information, receiving or transmitting, by the terminal, each of the one or more scheduled-shared channels.

Description

Method and device for transmitting or receiving scheduling information through a downlink shared channel in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting or receiving scheduling information through a downlink shared channel in a wireless communication system.

[0002] The 5th generation (5G) wireless communication system is a successor technology to 4G LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. In the case of 5G NR (New Radio), all available spectrum resources can be utilized, ranging from low-frequency bands below 1 GHz to intermediate frequency bands between 1 GHz and 10 GHz, and high-frequency (or millimeter wave) bands above 24 GHz. Based on the foundational technology of 5G wireless communication, 6G wireless communication systems are being developed.

[0003] 6G wireless communication systems are being developed with the goal 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 IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of 6G systems can be seen in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity. Various technologies are being researched in consideration of the requirements for 6G systems, such as a peak data rate of 1 Tbps per device, an end-to-end (E2E) latency of 1ms, 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.

[0004] The technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving scheduling information for an uplink shared channel(s) and / or downlink shared channel(s) through a downlink shared channel in a wireless communication system.

[0005] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below.

[0006] A method according to one aspect of the present disclosure may include: receiving first scheduling information related to a scheduling-downlink shared channel from a network by a terminal; receiving the scheduling-downlink shared channel from the network by the terminal, the scheduling information including second scheduling information related to one or more scheduled-shared channels based on the first scheduling information; and performing reception or transmission of each of the one or more scheduled-shared channels by the terminal based on the second scheduling information.

[0007] A method according to a further aspect of the present disclosure may include: transmitting first scheduling information related to a scheduling-downlink shared channel to a terminal by a base station; transmitting the scheduling-downlink shared channel, which includes second scheduling information related to one or more scheduled-shared channels, to the terminal by the base station based on the first scheduling information; and performing transmission or reception of each of the one or more scheduled-shared channels by the base station based on the second scheduling information.

[0008] According to the present disclosure, a method and apparatus for transmitting or receiving scheduling information for an uplink shared channel(s) and / or a downlink shared channel(s) through a downlink shared channel in a wireless communication system may be provided.

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

[0010] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description.

[0011] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.

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

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

[0014] FIG. 4 illustrates an exemplary communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

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

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

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

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

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

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

[0021] FIG. 11 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.

[0022] FIGS. 12 and FIGS. 13 show examples of NTN scenarios to which some examples of the present disclosure may be applied.

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

[0024] FIG. 15 illustrates an example of a cell DTX / DRX operation to which some examples of the present disclosure may be applied.

[0025] FIG. 16 illustrates an example of a carrier aggregation (CA) operation including an SSB-free cell to which some examples of the present disclosure may be applied.

[0026] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.

[0027] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.

[0028] FIG. 19 shows examples of on-demand SIB1 operations to which some examples of the present disclosure may be applied.

[0029] FIG. 20 is a drawing for illustrating an example of scheduling-PDSCH according to the present disclosure.

[0030] FIG. 21 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.

[0031] FIG. 22 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.

[0032] FIG. 23 shows an example of L1 activation-based SPS-style scheduling-PDSCH according to the present disclosure.

[0033] FIG. 24 illustrates an example of upper-layer activation-based SPS method scheduling-PDSCH according to the present disclosure.

[0034] FIG. 25 is a diagram showing examples of the configuration of scheduling information within a scheduling-PDSCH according to the present disclosure.

[0035] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will know that the present disclosure may be practiced without such specific details.

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

[0037] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

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

[0039] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise.

[0040] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0041] A slash ( / ) or a comma used in the present disclosure 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."

[0042] 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 as synonymous with "at least one of A and B."

[0043] Additionally, in the present disclosure, "at least one of A, B and C" may 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" may mean "at least one of A, B and C."

[0044] 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, the "control information" of 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."

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

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

[0047] 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 / integrated access backhaul (IAB) node.

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

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

[0050] In the present disclosure, "set or defined" may be interpreted as being set to a device through predefined signaling (e.g., System Information Block (SIB), MAC, RRC) from a base station or network. In the present disclosure, "set or defined" may be interpreted as being set to a device through separate signaling or being predefined without separate signaling.

[0051] In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or a signal through said 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.

[0052] The technology described in this 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), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

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

[0054] Network structure

[0055] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.

[0056] To compensate for incomplete areas of network coverage, a network topology in which the split radio access network (RAN) is configured more flexibly and resiliently may be considered. To this end, various nodes such as integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as exemplified in Fig. 1, may be applied, and 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 performs simple signal amplification and forwarding functions, and in the case of a network-controlled repeater, it may adjust transmit / receive settings based on information provided by the network as well as signal amplification and forwarding. For example, NTN nodes can correspond to satellites or aircraft that provide NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

[0057] Referring to FIG. 1, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may 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 DU, various intermediate points may be introduced to compensate for this.

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

[0059] In some examples of the present disclosure, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. In most cases where there is no additional description of the operation of three or more subjects, the communication subjects in the present disclosure are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.

[0060] As such, in some examples of the present disclosure, for the sake of brevity of description, the subject of the operation may be referred to as a terminal and / or base station (or a first node and / or a second node). Additionally, the term terminal and / or base station (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the terminal (or first node) and the base station (or second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; or may correspond to a first intermediate point and a second intermediate point, respectively.

[0061] In the present disclosure, there may be no intermediate points between the base station and the terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.

[0062] Systems applicable to the present disclosure

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

[0064] The communication system (100) to which the present disclosure applies 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 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 Thing) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.). 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 a 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 operate as a network device (120) to another wireless device (110).

[0065] Wireless devices (110a to 110f) can be connected to a network (130) through a network device (120). AI technology may be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) through the network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. The wireless devices (110a to 110f) may communicate with each other through the network device (120) / network (130), but may 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). Also, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or other wireless devices (110a to 110f).

[0066] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120) and between network devices (120). Here, 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 wireless communication / connection (150a, 150b, 150c), wireless devices and network devices / wireless devices, and network devices and network devices can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various descriptions of the present disclosure, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.

[0067] Devices applicable to the present disclosure

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

[0069] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals through 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).

[0070] 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 sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a second information / signal through the transceiver (206) and then store information obtained from the 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, memory (204) may store software code containing 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 sequences of operations disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through at least one antenna (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with a radio frequency (RF) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.

[0071] Hereinafter, 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., functional layers such as PHY (physical), MAC (media access control), RLC (radio link control), PDCP (packet data convergence protocol), RRC (radio resource control), and SDAP (service data adaptation protocol). At least one processor (202) may generate at least one PDU (Protocol Data Unit) and / or at least one SDU (service data unit) according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to at least one transceiver (206). At least one processor (202) may receive a signal (e.g., a baseband signal) from at least one transceiver (206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document.

[0072] At least one processor (202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. 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 at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in at least one processor (202) or stored in at least one memory (204) and driven by at least one processor (202). The descriptions, functions, procedures, proposals, 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.

[0073] At least one memory (204) may be connected to at least one processor (202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one memory (204) may be composed of ROM (read-only memory), RAM (random access memory), EPROM (erasable programmable read-only memory), flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. At least one memory (204) may be located inside and / or outside of at least one processor (202). Additionally, at least one memory (204) may be connected to at least one processor (202) via various technologies, such as wired or wireless connections.

[0074] At least one transceiver (206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this document to at least one other device. At least one transceiver (206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this document from at least one other device. For example, at least one transceiver (206) may be connected to at least one processor (202) and may transmit and receive wireless signals. For example, at least one processor (202) may control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Additionally, at least one processor (202) may 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., as described in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document through 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) can convert user data, control information, wireless signals / channels, etc. processed using at least one processor (202) from a baseband signal to an RF band signal. To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

[0077] For example, the device may be a portable device such as a smartphone, smartpad, wearable device (e.g., smart watch, smart glasses), or portable computer (e.g., 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 video information / signals, audio information / signals, data, and / or information input by a user.

[0078] For example, the device may be a mobile device such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), or ship. In this case, the device may further include at least one of a drive unit comprising at least one of an engine, motor, power train, wheel, brake, and steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, battery, etc.; a sensor unit that senses state 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 acquires position information of the moving body through a GPS (global positioning system) and various sensors.

[0079] For example, the device may be an XR device such as an HMD, a HUD (head-up display) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, 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 acquires control information, data, etc. from the outside and outputs a generated XR object, and a sensor unit that senses state information, environment information, and user information of the device or the surroundings of the device.

[0080] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc., 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 state information, environmental information, and user information of the device or its surroundings, and a drive unit that performs various physical actions, such as moving robot joints.

[0081] For example, the device may be an AI device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, 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 state information, environmental information, and user information of the device or its surroundings, and a training unit that learns a model composed of an artificial neural network using training data.

[0082] The structure of the wireless device illustrated in FIG. 3 may be understood as part of a terminal (or first node), or part of an intermediate point, or 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 communication. If the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) illustrated in FIG. 3 is used for front haul and / or back haul communication, and a wired transceiver may not be included.

[0083] Communication procedures

[0084] FIG. 4 illustrates an exemplary communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0085] FIG. 4 illustrates the operation 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 the operation performed prior to this.

[0086] 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 may include a plurality of synchronization signals (e.g., a primary synchronization signal, a secondary synchronization signal) classified according to structure or use. Through this, the terminal (110) can identify the boundaries of the frame, subframe, slot, and / or symbol of the base station (120) and obtain information about the base station (120) (e.g., a cell identifier).

[0087] 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 attributes, characteristics, and / or capabilities of the base station (120) required to connect to the base station (120) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc., and can be classified, for example, into a master information block (MIB) and a system information block (SIB). If necessary, the terminal (110) may transmit a signal requesting system information prior to receiving the system information. Such request and provision of system information may be performed after a random access procedure described later.

[0088] 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 for a random access procedure (e.g., a random access preamble, a RAR (random access response) message, etc.) based on information related to the random access channel of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) may transmit a preamble (e.g., message 1 (MSG1)) through a random access channel, receive a random access response (RAR) message (e.g., message 2 (MSG2)), transmit a message (e.g., message 3 (MSG3)) containing information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the RAR message, and receive a message (e.g., message 4 (MSG4)) for contention resolution and / or connection establishment. As another example, MSG1 and MSG3 may be transmitted and received as a single message (e.g., message A (MSG A), or MSG2 and MSG4 may be transmitted and received as a single message (e.g., message B (MSG B).

[0089] In step S107, the first node (110) and the second node (120) can perform signaling of control information. For example, the control information may be defined in various layers, such as a layer that controls the 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) may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0090] 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 data based on the signaling of control information and transmit and / or receive data. 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 the information bits. For example, when receiving data, the terminal (110) or the base station (120) can perform at least one of extracting a signal from a resource, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0091] 6G System Core Technology

[0092] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, multiple input multiple output (MIMO) 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.

[0093] artificial intelligence

[0094] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in machine-to-machine (M2M), machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). 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.

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

[0096] Below, to provide a more specific explanation of AI (or AI / ML (machine learning)), terms can be defined as follows.

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

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

[0099] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.

[0100] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and an AI model using a trained AI model.

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

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

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

[0104] After the data preparation process is performed, the data collection function (10) can provide training data (11) to the model training function (20) and provide inference data (12) to the model inference function (30). Here, the training data (11) corresponds to data required as input for the AI ​​model training function (20), and the inference data (12) corresponds to data required as input for the AI ​​model inference function (30).

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

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

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

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

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

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

[0111] The actor function (40) is a function that receives an output (16) from the model inference function (30) and triggers or performs a corresponding operation / action. The actor function (40) can trigger an operation / action on another entity (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or on itself.

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

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

[0114] - Training data: Refers to the dataset used to train a model.

[0115] - Validation data: This refers to a dataset used to validate a model that has already been trained. Validation data typically refers to a dataset used to prevent overfitting of the training dataset. Additionally, validation data can refer to a dataset used to select the best model among the various models trained during the learning process. Therefore, validation can be viewed as a type of training.

[0116] - Test data: Refers to the dataset for final evaluation. This data is unrelated to training.

[0117] For example, within the entire dataset, training data and validation data can be divided in a ratio of approximately 8:2 or 7:3. Alternatively, within the entire dataset, training data:validation data:test data can be divided in a ratio of 6:2:2.

[0118] Depending on whether the base station and the terminal possess the capability for AI / ML functions, the cooperation level can be defined as follows, and variations resulting from the combination of multiple levels below or the separation of any one level are also possible.

[0119] Category 0a: This corresponds to a no collaboration framework. In this case, the AI / ML algorithm is based on pure implementation and may not require changes to the wireless interface.

[0120] Category 0b: Corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but lacks cooperation.

[0121] Category 1: This applies to cases involving inter-node support to improve the AI / ML algorithms of each node. For example, it 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.

[0122] Category 2: This applies to cases where joint ML operations between a terminal and a base station can be performed. This level requires AI / ML model commands or exchanges between network nodes.

[0123] The functions exemplified in Figure 5 above may be implemented at RAN nodes (e.g., base station, TRP, base station CU, etc.), network nodes, network operator's OAM (operation administration maintenance), or terminals.

[0124] Alternatively, two or more entities among a RAN, a network node, a network operator's OAM, or a terminal may cooperate to implement the functions exemplified in FIG. 5. For example, one entity may perform some of the functions of FIG. 5, and another entity may perform the remaining functions. As such, some of the functions exemplified 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 distribution / update (13) and model performance feedback (14) may be omitted.

[0125] Alternatively, any one of the functions exemplified in FIG. 5 may be performed by two or more entities among the RAN, network node, network operator's OAM, or terminal in collaboration. This may be referred to as a split AI operation.

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

[0127] For example, the AI ​​model training function can be performed by network nodes (e.g., core network nodes, network operator's OAM, etc.), and the AI ​​model inference function can be performed by RAN nodes (e.g., base station, TRP, base station's CU, etc.).

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

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

[0130] Step 3: The network node can 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.

[0131] For the sake of convenience of explanation, it is assumed that the AI ​​model was deployed / updated only to RAN Node 1.

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

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

[0134] Step 6: If applicable, RAN node 1 can send model performance feedback to network nodes.

[0135] 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') can perform an action based on the output data. For example, in the case of a load balancing action, the terminal may move from RAN Node 1 to RAN Node 2.

[0136] Step 8: RAN Node 1 and RAN Node 2 can transmit feedback information to network nodes.

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

[0138] For example, both AI model training and AI model inference functions can be performed by RAN nodes (e.g., base station, TRP, base station's CU, etc.).

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

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

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

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

[0143] 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') can perform an action based on the output data. For example, in the case of a load balancing action, the terminal may move from RAN Node 1 to RAN Node 2.

[0144] Step 6: RAN Node 2 can send feedback information to RAN Node 1.

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

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

[0147] Step 1: A terminal can transmit input data (e.g., training data) for training an AI model to a RAN node. Here, the RAN node can collect data (e.g., terminal measurements related to RSRP, RSRQ, SINR of the serving cell and neighboring cells, terminal location, velocity, etc.) from various terminals and / or other RAN nodes.

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

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

[0150] Step 4: Input data (e.g., inference data) for AI model inference can be received from terminals and RAN nodes (and / or other terminals).

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

[0152] Step 6: If applicable, the terminal can transmit model performance feedback to the RAN node.

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

[0154] Step 8: The terminal can transmit feedback information to the RAN node.

[0155] THz communication

[0156] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz–300 GHz band range (sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the RF band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF.

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

[0158] Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0159] When transmitting system information (e.g., MIB) of a cell in the THz frequency band, it can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of ​​the cell as the beam width becomes narrower. In particular, transmitting system information using this method is even more inefficient when there are not many users in the cell.

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

[0161] The example of FIG. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applied. In addition, the procedure exemplified in FIG. 10 can be combined with various embodiments of the present disclosure described below. For example, embodiments described below can be performed based on system information obtained by the procedure exemplified in FIG. 10.

[0162] In step S1010, the second node (120) (e.g., a base station) can transmit system information of cell #1 through 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 a system frame number (SFN) generated at a higher layer, a PDCCH configuration for SIB1, cell barring, cell re-selection, and subcarrier spacing, and may include at least one of a synchronization signal / PBCH (physical broadcast channel) block index generated at a physical layer. To this end, as an example, cell #1 and cell #2 may have a secondary cell and primary cell relationship.

[0163] In step S1030, the first node (110) (e.g., a terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Generally, synchronization is acquired prior to receiving system information, but since the system information of cell #1 is received in cell #2, the acquisition of synchronization for cell #1 can be performed after receiving system information. For example, the terminal can acquire synchronization based on system information. Alternatively, the acquisition of synchronization may be performed prior to step S1010.

[0164] In step S1050, the first node (110) may transmit a signal to connect to cell #1. For example, the signal may include a random access preamble. The structure of such a signal and the resource for transmitting the signal (e.g., a channel) may be identified through system information. Subsequently, in step S1070, the first node (110) and the second node (120) may perform a connection procedure to cell #1 and perform communication.

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

[0166] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations may be required to use very sharp beams. The use of sharp beams implies that terminals and base stations must perform beam control in addition to beamforming, meaning that a very large number of beams are utilized. Consequently, aligning the transmit and receive beams between the base station and the terminal takes a very long time. Furthermore, if the beam alignment between the base station and the terminal is disrupted due to the movement of the terminal, time is frequently required to realign the beams, which may lead to link instability.

[0167] FIG. 11 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.

[0168] Figure 11 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but this procedure is not limited to a THz environment and can also be applied in a 6G communication environment where THz communication is not applied.

[0169] Here, "beam" can be interpreted as other terms having equivalent technical meanings capable of distinguishing beams, such as "spatial domain filter," "spatial domain transmit filter," "spatial domain receive filter," reference signal (RS) resources for distinguishing beams, and SSB index.

[0170] In step S1110, the second node (120) (e.g., base station) may set resources for beam management to the first node (110) (e.g., terminal). Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station may utilize a beam search signal (BSS) that is transmitted spatially separated from the existing downlink signal / channel for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port used for transmitting the 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 may be included in the technical concept according to the present embodiment.

[0171] In step S1130, the second node (120) (e.g., a base station) transmits measurement signals using multiple 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 requiring measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, or a true time delay (TTD).

[0172] In step S1050, the first node (110) (e.g., a terminal) may transmit a feedback signal to the 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 in step S1030.

[0173] In step S1070, 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 receiving beam of the first node (110) selected in step S1050. If channel reciprocity is established, the transmission beam of the first node (110) can also be determined through steps S1030 and S1050, so the transmission operation from the first node (110) can also be performed using a beam that has a reciprocity relationship with the beam selected in step S1050. If channel reciprocity is not established, a procedure including the transmission of measurement signal(s) by the first node (110) and the transmission of feedback signal(s) by the second node (120) may be performed first to determine the transmission beam of the first node (110).

[0174] Non-terrestrial networks (NTN)

[0175] FIGS. 12 and FIGS. 13 show examples of NTN scenarios to which some examples of the present disclosure may be applied.

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

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

[0178] Referring to FIG. 12, the 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. A beam footprint may refer to an area where signals transmitted by the satellite can be received.

[0179] Referring to FIG. 13, a satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) connected to the terminal can be connected to another satellite (or UAS platform) via inter-satellite links (ISL). Another satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on a regenerated payload, the satellite can be connected to a data network via another satellite and a gateway. If no ISL exists between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.

[0180] FIGS. 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 (with on-board 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) may vary depending on the on-board antenna diagram and the minimum elevation angle.

[0181] For example, the transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered.

[0182] For example, the regeneration payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, the regeneration payload may be substantially the same as carrying all or part of the base station functions on a satellite (or UAS platform).

[0183] Integrated Sensing and Communication (ISAC)

[0184] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, distance (or range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection and recognition (e.g., vehicles, humans, animals, UAVs), as well as high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable 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 may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, such as sensing operations, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks to wireless communication and sensing networks.

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

[0186] Specifically, FIG. 14(a) illustrates an example of monostatic sensing operation using a sensing receiver and a sensing transmitter located at the same position. FIG. 14(b) illustrates an example of bistatic sensing operation using a sensing receiver and a sensing transmitter located at separate positions. A sensing receiver receives a signal that is reflected or scattered by a sensing object from a sensing signal transmitted from a sensing transmitter, and can extract or acquire sensing data based on the received signal. A sensing result can be generated or determined through appropriate processing of this sensing data. The sensing result can be provided to a trusted third-party entity or service outside the 3GPP system via an entity or service within the 3GPP system.

[0187] Network Energy Saving (NES)

[0188] Energy conservation in base stations is considered important in wireless communication systems, including 3GPP, because it can contribute to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditure (OPEX) of telecommunication operators. In particular, as the introduction of 5G communication requires high transmission rates, base stations must be equipped with a larger number of antennas and provide services through wider bandwidths and frequency bands. Consequently, according to recent studies, the energy cost of base stations has reached the level of 20% of total OPEX. For example, in 5G wireless communication systems, various technologies for reducing energy consumption are being discussed under the name NES (network energy savings).

[0189] With the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time axis, controlling transmission and reception resources for terminal-common or terminal-specific signals / channels, changing the amount of resources in the frequency axis, controlling transmission power, or turning on / off antenna ports, TRPs (transmission-reception points), etc. in the spatial domain.

[0190] For example, the base station can identify the NES solution(s) to be applied, perform signaling for the NES, and perform operations on the NES.

[0191] NES solution(s) may relate to the control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution(s) to apply may be adaptively selected based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.) or may be predefined.

[0192] A base station that has identified the NES solution(s) performs signaling for the NES. The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information regarding the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of NES operation to at least one terminal. Additionally, the base station may receive capability information related to the NES from at least one terminal.

[0193] Based on signaled NES-related information, the base station can perform operations for the NES. For example, depending on system information, configuration information, and control information transmitted via signaling, the base station can turn the transmission and reception of specific signals on or off, turn elements of the spatial domain on or off, or adjust resources for the transmission and reception of measurement signals.

[0194] Examples of NES solutions that can be implemented through this procedure are as follows.

[0195] Intra-system energy saving: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0196] Inter-system energy saving: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.

[0197] SSB-less cell: When no SSB or SMTC (SSB-based RRM (radio resource management) measurement timing configuration) setting is provided for a specific cell (e.g., secondary cell (SCell) or primary cell (PCell))(s), the terminal may obtain timing reference and automatic gain control (AGC) sources from other serving cells. In frequency range 1 (FR1) or FR2, the base station may establish intra-band carrier aggregation (CA) or inter-band CA that includes cells without SSB transmission, in which case SSB / SIB transmission may be triggered by the terminal's wake-up signal (WUS). Accordingly, the period of common channels / signals such as SSB is increased, so the base station may remain in a sleep state for a longer time.

[0198] Cell DTX (discontinuous transmission) / DRX (discontinuous reception): To reduce the downlink transmission / uplink reception activity time of a base station, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be set commonly for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be set and activated separately, and up to two cell DTX / DRX patterns may be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for semi-persistent scheduling (SPS) opportunities or monitoring for PDCCH may be suspended during the cell DTX inactive period. When cell DRX is set and activated, at least one of transmission from configured grant (CG) resources or scheduling request (SR) transmission may be suspended during the cell DRX inactive period. Cell DTX / DRX can be enabled / disabled through RRC signaling or L1 (layer 1) group common signaling.

[0199] Parameters such as active duration and cycle may be set for Cell DTX / DRX. Active duration is the period during which a terminal waits to transmit an SR or CG after receiving a PDCCH or SPS opportunity, and cycle may specify the periodic repetition of active duration and inactive duration. When both Cell DTX and Cell DRX are set, parameters such as active duration and cycle may be common. If the base station recognizes an emergency call or public safety-related service (e.g., Multimedia Priority Service (MPS) or Mission Critical Service (MCS)), the network may release or disable the Cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap may be required between the active period of the terminal's connected mode DRX and the active period of the Cell DTX / DRX. For example, the period of the terminal's connected mode DRX may be a multiple of the Cell DTX / DRX period, or vice versa.

[0200] Conditional Handover (CHO): A CHO procedure performed in such a manner that the execution of a handover is determined by the terminal may be used while NES technology is applied (e.g., when a cell enables or disables the cell DTX / DRX). In this case, the terminal may use an NES-specific CHO event to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as an NES event indication may be applied.

[0201] Spatial and power domain adaptation: To support the base station for transceiver muting and / or transmit power adaptation, the terminal may be configured to report multiple CSI quantities in the CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting behavior may be affected.

[0202] Cell DTX / DRX

[0203] To operate the base station in sleep mode for a relatively long period without frequent wake-ups, the base station's DTX / DRX was introduced for NES purposes. By configuring the cell DTX and setting the on-duration of the terminals' C-DRX within the active period of the cell DTX, the base station can reduce energy consumption by utilizing DTX transmission under low system load conditions.

[0204] FIG. 15 illustrates an example of a cell DTX / DRX operation to which some examples of the present disclosure may be applied.

[0205] The second node (120) (e.g., a base station) can transmit system information to the first node (110) (e.g., a terminal). Accordingly, the first node (110) can check information related to the cell DTX / DRX of the second node (120).

[0206] For example, system information may include MIB, SIB1, etc. In relation to NES technology, MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to the cell barring state (e.g., cellBarredNES). For example, if cellBarred included in MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. For example, if cellBarred included in the received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred.

[0207] For example, if a terminal has the capability to support NES cell DTX / DRX, the terminal can check SIB1 to determine the cell blocking status. For example, if cellBarred in the MIB is set to barred and cellBarredNES is absent in SIB1, a terminal supporting NES cell DTX / DRX can treat the cell as blocked and perform cell-reselection to another cell. For example, if cellBarred in the MIB is set to barred and cellBarredNES is included in SIB1, a terminal supporting NES cell DTX / DRX can determine that the cell is not blocked.

[0208] In the example of FIG. 15, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and that cellBarred in the MIB is set to notBarred or cellBarred in the MIB is set to barred, and cellBarredNES is included in SIB1. Accordingly, the terminal can perform a random access procedure to connect to the base station and then perform communication. For example, the base station can perform a cell DTX / DRX operation and transmit configuration information related to the cell DTX / DRX operation to the terminal. The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include at least one of, for example, an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). In addition, the configuration information may further include information for receiving and interpreting control information related to cell DRX / DRX (e.g., DCI-related information such as cellDTRX-RNTI included in physicalCellGroupConfig, size of DCI format 2_9, etc.).

[0209] Subsequently, the base station may transmit control information related to cell DTX / DRX to the terminal. The control information related to cell DTX / DRX may include DCI having a specified format (e.g., DCI format 2_9). When an operation for a serving cell according to at least one of cell DTX operation and cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config included in servingcell-config), the terminal may identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring a PDCCH that transmits control information of the specified format during the active time through an upper-level parameter (e.g., SearchSpace included in PDCCH-Config), and obtain the location of information about the serving cell within the control information through an upper-level parameter (e.g., positionInDCI-cellDTRX included in ServingCell-config). Then, the terminal may obtain the control information based on the identified set of search spaces and location.

[0210] Control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide NES-mode indicators (e.g., NES-specific CHO execution conditions, etc.), and may include, for example, at least one block including cell DTX / DRX indicators and NES-mode indicators. In this case, if the serving cell is set as a supplementary uplink (SUL) carrier, the instruction to activate or deactivate cell DRX by the cell DTX / DRX indicator may be applied to both the uplink (UL) carrier and the SUL carrier.

[0211] Subsequently, the terminal and the base station can communicate based on the cell DTX / DRX. Specifically, the base station can turn the transmission and reception of signals on or off according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor signals from the base station. During the DTX-OFF duration, the base station can enter sleep mode to reduce energy consumption. For example, the base station DTX cycle can be aligned with the terminal DRX cycle. The base station DTX-ON duration can fully cover the terminal's DRX-ON duration. Furthermore, for NES purposes, the base station can align transmissions on Xn (interface between base stations) / NG (interface between 5G RAN and 5G core network) with transmissions on Uu (interface between terminal and network). The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station may perform dormancy-like behavior of infrequently transmitting or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. Depending on the base station's configuration, the terminal may infrequently receive or not receive downlink signals / channels. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF duration, the terminal may receive the corresponding CSI-RS, SSB, or PDCCH discontinuously.

[0212] SSB-less cell

[0213] FIG. 16 illustrates an example of a carrier aggregation (CA) operation including an SSB-free cell to which some examples of the present disclosure may be applied.

[0214] In the example of Fig. 16, it is assumed that the SSB-free cell is a SCell in CA, but the SSB-free cell may also be a PCell in CA.

[0215] A second node (120) (e.g., a base station) can transmit configuration information for a SCell to a first node (110) (e.g., a terminal). For example, the base station can transmit configuration information for CA to provide services to the terminal through CA operation. Here, the CA operation may be intra-band CA or inter-band CA. For example, the configuration information for a SCell may include information containing information for adding a SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL settings, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Accordingly, the terminal can determine the settings for CA operation and perform communication using the base station's PCell and SCell.

[0216] For example, the terminal can verify that the SCell is an SSB-less SCell based on information related to the downlink frequency included in the configuration information, and can verify the relevant parameters. For example, the terminal can determine that the SCell is an SSB-less SCell by verifying the existence of a parameter indicating that it is an SSB-less SCell (e.g., SSBlessSCell), and can verify the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the example of FIG. 16, the reference cell may be a PCell. Therefore, the terminal can use the PCell as a timing reference and AGC source for communication in the SCell. For example, the reference of the SSB-less cell may be (another) cell, TRP, CORESET pool (control resource set pool), (additional) PCI (physical cell ID), etc.

[0217] Conditional Handover (CHO)

[0218] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.

[0219] The order of the operations exemplified in Fig. 17 may vary depending on the case.

[0220] A second node (120) (e.g., a base station) may transmit configuration information for a CHO to a first node (110) (e.g., a terminal). The configuration information for a CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to configuration for reporting (e.g., ReportConfigNR). For example, information related to configuration for reporting may include information related to events related to reporting, identifiers of events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 17, it is assumed that event information indicating that it is an NES-specific CHO event is received.

[0221] The base station may transmit information to the terminal that enables NES-specific CHO execution conditions. The information that enables NES-specific CHO execution conditions may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information that enables NES-specific CHO execution conditions may be referred to as an NES-mode indicator, and may indicate that NES-specific CHO execution conditions are enabled, for example, as 1-bit information, if the relevant upper layer parameter (e.g., nesEvent) is set and the serving cell of the relevant block in the corresponding DCI is the primary cell.

[0222] Subsequently, the terminal may perform a measurement and transmit the measurement report to the base station. The base station may determine the CHO based on the measurement report and perform signaling for a handover request with the adjacent / neighboring base station(s) indicated by the measurement report. The base station may determine the adjacent base station(s) that have affirmed admission through signaling as candidate base station(s) and transmit information about the candidate base station(s) to the terminal. Accordingly, the terminal may evaluate the CHO execution conditions for the candidate base station(s). Based on the evaluation results, if a candidate cell satisfying the conditions is determined, the terminal may perform detachment from the previous / old cell and perform synchronization for the new cell.

[0223] For example, based on event information indicating that the event received by the terminal in the previous procedure is an NES-specific CHO event, and information enabling the NES-specific CHO execution condition, the terminal can determine whether the event is satisfied. For example, if an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that the event is an NES-specific CHO event (e.g., nesEvent), the terminal can determine that the event associated with the corresponding measurement identifier (e.g., measId) is satisfied, and accordingly, determine that the CHO execution condition is satisfied.

[0224] Measurement and Reporting of Channel Status Information (CSI)

[0225] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.

[0226] The second node (120) (e.g., base station) can transmit configuration information for CSI to the first node (110) (e.g., terminal). The configuration information for CSI may include information related to a reference signal (e.g., CSI-RS) resource or resource set for CSI (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., quantity information, report type information, report resource information, codebook information, etc.), information related to CSI measurement, etc.

[0227] For example, to assist the base station with base station transceiver muting and / or transmit power adaptation, the terminal may be configured to report multiple CSI entries in a CSI report based on multiple sub-configs. For example, each sub-config may correspond to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. In relation to CSI reporting, a higher-level parameter included in the configuration information (e.g., CSI-ReportConfig) may include a list of sub-configs, and each sub-config may be identified by an identifier (e.g., csi-ReportSubConfigID). For example, each sub-setting may correspond to a list of at least one CSI-RS resource, a subset of CSI-RS antenna ports, and / or power-related parameters of the CSI-RS resource(s) (e.g., power control offset related parameters (e.g., powerControlOffset) and / or power offset for PDSCH related to CSI-RS).

[0228] For example, an information element (IE) for a list of aperiodic trigger states for CSI may include a trigger list parameter for a CSI reporting sub-setting. This parameter may include a list of sub-setting ID(s) of N sub-setting(s) out of L configured sub-settings within a CSI reporting setting associated with a triggering state for an aperiodic CSI reporting on an uplink data channel (e.g., PUSCH (physical uplink shared channel)).

[0229] For example, an IE for a CSI reporting configuration may include a parameter for a list of CSI reporting sub-configuration ID(s) to be added, modified, or released. A list of port subset indicators and non-zero power (NZP) CSI-RS resources may not be configured simultaneously in the same CSI reporting configuration.

[0230] For example, IE for CSI reporting sub-settings may include port-subset indicator parameters, NZP CSI-RS resource list parameters, and power offset parameters.

[0231] The port-subset indicator parameter may indicate the number of ports of NZP CSI-RS resources indicated in the NZP CSI-RS resource list (the value being equal to the number of ports of the corresponding NZP CSI-RS resources) and a (sub)set of CSI-RS antenna ports used for CSI calculation of the sub-configuration. Each bit in the bit string of the port-subset indicator corresponds to an antenna port, and if any bit is set to 1, the corresponding port may be enabled for CSI calculation corresponding to the sub-configuration, and if any bit is set to 0, the corresponding port may not be enabled for CSI calculation corresponding to the sub-configuration.

[0232] The NZP CSI-RS resource list parameter may indicate a list of NZP CSI-RS resources for a sub-setting that is a (sub)set of NZP CSI-RS resource(s) of a set of CSI-RS resources for channel measurements associated with the sub-setting of a CSI reporting setting. Values ​​0, 1, 2, ... may mean the first, second, third, ... NZP CSI-RS resources of the set of CSI-RS resources.

[0233] When the power offset parameter is set for an NZP CSI-RS resource, it may indicate that a power offset between the PDSCH RE (resource element) and the NZP CSI-RS RE is applied by the difference between the value of the power offset parameter and the value of the power control offset parameter.

[0234] When a configuration for CSI includes multiple sub-configurations, the terminal may determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report items, etc., by considering the sub-configurations when interpreting the configuration information for CSI. When configuration information related to CSI reporting that includes sub-configurations (e.g., CSI-ReportConfig) is provided to the terminal, the terminal may not expect that a higher-level parameter related to a report item (e.g., reportQuantity) is set to 'cri-RSRP', 'cri-SINR', 'cri-SINR-Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', 'ssb-Index-SINR-Index', or 'tdcp' (where CRI corresponds to the CSI-RS resource index and tdcp corresponds to time domain channel properties). Additionally, if the type of CSI report is set to semi-persistent CSI report or aperioditic CSI report, the base station may activate / trigger only some of the sub-settings configured for the terminal via MAC-CE (control element) or DCI (downlink control information). For example, the trigger state of the aperioditic CSI report may be set as needed, and the activation of the semi-persistent CSI report may be controlled by an activation command.

[0235] For example, regarding the setting of a report quantity, the terminal may determine CSI-RS port index(s) for each CSI-RS resource based on information related to a port-subset per sub-setting (hereinafter referred to as 'port-subset indicator'). The port-subset indicator may include a bitmap for specifying some of the antenna ports for the corresponding CSI-RS resource. Thus, the terminal may identify at least one antenna port for the corresponding sub-setting based on the positions of bits set to a positive value (e.g., 1) in the port-subset indicator.

[0236] For example, regarding the settings for a report quantity, the terminal can determine the codebook type based on the existence of sub-settings. Specifically, if sub-settings are configured for a CSI report, the terminal may exclude the configuration of at least one codebook type. For example, if the terminal's capability supports it, the corresponding at least one codebook type may be configured.

[0237] For example, regarding the settings for report quantities, a power offset value and an NZP CSI-RS resource set may be set for each sub-setting. For example, depending on whether a power offset value and an NZP CSI-RS resource set are set for each sub-setting, the interpretation of the NZP CSI-RS resource set for each sub-setting may vary.

[0238] In determining the CQI (channel quality indicator), a higher-level parameter related to the time limit for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be set. In this case, the terminal can derive a channel estimate to determine the CSI based on the most recent CSI reference resource. For example, if Cell DTX for the base station is enabled, the Cell DTX activation time may be considered to determine the CSI reference resource.

[0239] The CSI is derived based on the CSI reference resource. The CSI reference resource is defined as a group of downlink physical resource blocks corresponding to the bands related to the CSI derived in the frequency domain, and is defined as a single downlink slot determined in the time domain based on upper-layer parameters and subcarrier spacing. The terminal may transmit the CSI report no later than the CSI reference resource after receiving the CSI-RS. For example, if sub-configurations are configured for the CSI report, the CSI reference resource may be considered for each sub-configuration.

[0240] When configured to report at least one of the CQI index, PMI (precoding matrix index), and RI (rank indicator), in a CSI reference resource, the terminal may assume specific values ​​for the symbol location and number occupied in control signaling, the number of PDSCH and DMRS (demodulation reference signal) symbols, the subcarrier spacing of the BWP (bandwidth part), the bandwidth for CQI reporting, the CP (cyclic prefix) length and subcarrier spacing of the reference resource, and the RV (redundancy version), for the purpose of deriving at least one of the CQI index, PMI, and RI. In this case, if sub-settings are configured for CSI reporting, assumptions regarding the antenna port, EPRE (energy per resource element), etc., may be determined based on the sub-settings.

[0241] Based on the configuration as described above, the base station may transmit at least one CSI-RS to the terminal. Based on the configuration as described above, the terminal may receive at least one CSI-RS and perform a measurement thereon. For example, at least one CSI-RS may be transmitted through a CSI-RS resource or resource set configured by the configuration information.

[0242] When the terminal is configured for DRX (discontinuous reception), the terminal may perform measurements as follows. For example, if the terminal is configured to monitor power saving-related control information (e.g., DCI format 2_6) and, in a situation where the DRX-related timer (e.g., drx-onDurationTimer) is not started by the upper layer parameter (e.g., ps-TransmitOtherPeriodicCSI), and is configured to report CSI using a reporting configuration type set to periodic reporting and a reporting item set to an item other than cri-RSRP and ssb-index-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer in the DRX-related configuration information (e.g., DRX-Config), in addition to the DRX active time or the DRX active time for the CSI to be reported. As another example, if the terminal is configured to monitor power saving-related control information (e.g., DCI format 2_6) and, under conditions where drx-onDurationTimer is not initiated by a higher-level parameter (e.g., ps-TransmitPeriodicL1-RSRP), is configured to report L1-RSRP using a report setting type configured for periodic reporting and a report item configured for cri-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer within the DRX-related setting information (e.g., DRX-Config), excluding the DRX active time or the DRX active time for the CSI to be reported. Additionally, the most recent CSI measurement opportunity occurs within the DRX active time for the CSI to be reported.

[0243] The base station may perform cell DTX and / or cell DRX operations. In this case, during the non-active period of the cell DTX, the terminal configured as the cell DTX may not expect to receive periodic CSI-RS and semi-static CSI-RS, which are configured in the CSI reporting configuration associated with a reporting item including at least RI. When the cell DTX is activated for the serving cell, the most recent CSI measurement opportunity of the semi-static CSI-RS resource or periodic CSI-RS resource may occur within the active periods of the cell DTX for CSI reporting, which are configured by the configuration information (e.g., CSI-ReportConfig) associated with the CSI reporting associated with a reporting item including at least RI.

[0244] A terminal that has received at least one CSI-RS can determine the CSI. For example, the terminal can perform a CSI calculation. The terminal can perform a CSI calculation based on CSI processing criteria. The terminal can indicate the number of supported concurrent CSI calculations, for example, the number of concurrently run CSI processing units (CPUs), which is the NCPU. The terminal can determine the number of CPUs for the corresponding CSI report based on at least one of the NCPU, the number of CPUs for each CSI report, the number of currently occupied CPUs, and the settings of the report item. For example, for configuration information related to CSI reporting (e.g., CSI-ReportConfig) containing a report item parameter (e.g., reportQuantity) that is not set to 'none', the CPU(s) may be occupied for at least one OFDM (orthogonal frequency division multiplexing) symbol, wherein the number of at least one symbol may be determined based on the CSI-RS resource or CSI-IM (interference measurement) resource associated with the sub-configurations.

[0245] If configuration information related to CSI reporting (e.g., CSI-ReportConfig) includes multiple sub-configurations, the number of CPUs occupied by CSI reporting may be determined based on the number of CSI-RS resources corresponding to the sub-configurations. For example, the number of CSI-RS resources may be determined based on the number of times the configuration information related to CSI reporting (e.g., CSI-ReportConfig) is referred or the number of sub-configurations referencing the CSI-RS resources.

[0246] A terminal that has determined the CSI may transmit a CSI report to a base station. The terminal may transmit CSI(s) for at least one sub-configuration according to a report item parameter (e.g., reportQuantity) configured for configuration information related to the CSI report (e.g., CSI-ReportConfig). For example, the CSI report may include at least one of PMI, CQI, RI, CRI, SSBRI (SSB resource index), LI (layer indicator), and RSRP. In this case, the CSI report may include a Part 1 CSI report and a Part 2 CSI report. Additionally, the CSI report may be transmitted via at least one of a PUCCH (physical uplink control channel) or a PUSCH.

[0247] When a terminal multiplexes CSI reports containing Part 2 CSI reports to a PUCCH resource, the terminal determines the number of physical resource blocks (PRBs) or Part 2 CSI reports for the PUCCH resource and the PUCCH resource, assuming that each CSI report or each CSI sub-report included in the CSI report indicates Rank 1 or a Rank combination {1, 1}. When a higher-level parameter related to the CSI report mode (e.g., csi-ReportMode) is set to 'Mode2', the terminal determines the number of PRBs or Part 2 CSI reports for the PUCCH resource and the PUCCH resource, assuming that each CRI of the CSI report is associated with a resource pair.

[0248] If a CSI report in PUSCH contains two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. Except where the corresponding CSI report contains at least one CSI sub-report including Part 2 that corresponds to a sub-configuration from a list of sub-configurations provided by a higher-level parameter (e.g., csi-ReportSubConfigList) included in the information related to the CSI report (e.g., CSI-ReportConfig), if the terminal omits Part 2 CSI information for a specific priority level, the terminal must exclude all information for that priority level.

[0249] For report configurations related to information (e.g., CSI-ReportConfig) containing a list of sub-configurations for a CSI report, the following processing is possible. For a corresponding CSI report containing at least one CSI sub-report, the omission of Part 2 CSI is performed at the sub-configuration level within the same priority level. Here, the sub-configuration having a lower index value has a higher priority.

[0250] If a CSI report consists of two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. For a given CSI report containing at least one CSI sub-report, the omission of the Part 2 CSI may be applied according to the CSI reporting procedure using PUSCH, for a report configuration related to information (e.g., CSI-ReportConfig) containing a list of sub-configurations related to the CSI report. The Part 2 CSI may be omitted starting from the lowest priority level up to a Part 2 CSI code rate that is less than or equal to the code rate set by the upper-level parameter (e.g., maxCodeRate).

[0251] Additionally, if a CQI request (or CSI request) field within a DCI triggers CSI report(s) in a PUSCH, the first uplink symbol carrying the CSI report(s) may not precede a symbol specified after a certain interval from the last symbol of the PDCCH carrying the DCI. Accordingly, the CSI calculation time may be guaranteed. For example, if multiple sub-configurations are configured for a CSI report, the starting position of the aforementioned interval may be determined based on all triggered sub-configurations.

[0252] CSI is transmitted via PUCCH or PUSCH and can be represented as a bit sequence of a fixed size. When CSI is transmitted via PUCCH, if a parameter (e.g., csi-ReportSubConfig) specifying sub-configuration settings for the CSI report is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to a predefined rule.

[0253] When a CSI is transmitted via PUSCH, if a parameter (e.g., csi-ReportSubConfig) that specifies settings per sub-configuration for the CSI report is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to a predefined rule.

[0254] Some or all of the examples of FIGS. 1 to 18 described above may be combined with some or all of the examples of the present disclosure described below, and such combined examples are included within the scope of the present disclosure.

[0255] Improved NES

[0256] To enhance NES technology, on-demand SSB, on-demand SIB1, and adaptation of common signal / channel transmissions are being discussed.

[0257] The following describes the on-demand SSB.

[0258] On-demand SSB corresponds to an NES scheme in which an SSB is transmitted when triggered on a specific cell, and not transmitted when not triggered. In existing NR systems, it is required to periodically transmit SSB at all times for purposes such as time / frequency synchronization or RRM measurement, so it was difficult to reduce energy consumption even when the base station had no data to receive or send. Considering this, the energy consumption of the base station can be reduced by ensuring that the base station does not perform SSB transmission and only performs SSB transmission when the on-demand SSB process is performed.

[0259] This on-demand SSB process can be triggered through one or more of the following examples:

[0260] - The terminal requests the base station's SSB transmission by transmitting an uplink signal / channel (e.g., PRACH (physical random access channel), PUCCH, PUSCH, SRS (sounding reference signal), etc. in 5G NR systems; in 6G systems, it may be a signal / channel with a different name).

[0261] - The first base station (or TRP) requests the second base station (or TRP) to transmit an SSB via an inter-base station interface (e.g., the Xn interface in a 5G NR system, or an interface with a different name in a 6G system) or backhaul signaling, etc.

[0262] - Signals whether the corresponding SCell transmits SSB through SCell activation / deactivation signaling

[0263] On-demand SSB operation for connected mode terminals and SCells may be limited to considerations such as coexistence with existing NR terminals. In subsequent releases or next-generation communication systems, on-demand SSB operation (e.g., support for on-demand SSB on PCells) may be defined for inactive or idle mode terminals or for initial connection terminals. Additionally, carrier aggregation (CA) including SCells to which on-demand SSB is applicable may be applied to both intra-band CA and inter-band CA. The SSB on the SCell transmitted through the on-demand SSB process may be utilized for at least time / frequency synchronization, L1 / L3 measurement, SCell activation, etc.

[0264] The following describes the on-demand SIB1.

[0265] On-demand SIB1 corresponds to an NES scheme in which SIB1 is transmitted when triggered on a specific cell, and not transmitted when not triggered. In existing NR systems, it is required to periodically and constantly transmit SIB1 containing system information, random access information, etc., to support cell access for initial access terminals or idle mode terminals; therefore, it was difficult to reduce energy consumption even when the base station had no data to receive or send. By having the base station not perform SIB1 transmission and only perform SIB1 transmission when the on-demand SIB1 process is performed, the energy consumption of the base station can be reduced.

[0266] This on-demand SIB1 process may include the terminal transmitting an uplink signal / channel (e.g., PRACH in a 5G NR system, or a signal / channel with a different name in a 6G system) to trigger the base station's SIB1 transmission.

[0267] FIG. 19 illustrates examples of on-demand SIB1 operations to which some examples of the present disclosure may be applied. FIG. 19 illustrates examples only, and on-demand SIB1 operations are not limited to the examples of FIG. 19.

[0268] In FIG. 19(a), the terminal may receive an SSB (and / or other downlink signal / channel) from the first cell (cell#1) and recognize that SIB1 is not being transmitted on cell#1. The terminal may trigger the transmission of SIB1 on cell#1 by transmitting a signal requesting SIB1 (e.g., a wake-up signal (WUS)) based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information. For example, a base station that receives the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#1 in response and transmit SIB1 on cell#1. Alternatively, the base station may transmit SIB1 on cell#1 without transmitting a specific DL signal / channel (e.g., ACK).

[0269] In FIG. 19(b), the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from the first cell (cell#1) and recognize that SIB1 is not being transmitted from the second cell (cell#2). The terminal may attempt to camp-on through cell#2. The terminal may trigger the transmission of SIB1 to cell#2 by transmitting a signal (e.g., WUS) requesting SIB1 on cell#1 based on information provided in the SSB (and / or other downlink signal / channel such as SIB1) received from cell#1 and / or predetermined information. For example, a base station receiving the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#1 (or on cell#2) in response and transmit SIB1 to cell#2 (or on cell#2). Alternatively, the base station may transmit SIB1 for cell #2 on cell #1 (or on cell #2) without transmitting a specific DL signal / channel (e.g., ACK).

[0270] In FIG. 19(c), the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from the first cell (cell#1) and recognize that SIB1 is not being transmitted from the second cell (cell#2). The terminal may attempt to camp-on through cell#2. The terminal may trigger the transmission of SIB1 to cell#2 by transmitting a signal (e.g., WUS) requesting SIB1 on cell#2 based on information provided in the SSB (and / or other downlink signal / channel such as SIB1) received from cell#1 and / or predetermined information. For example, a base station that receives the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#2 (or on cell#1) in response and transmit SIB1 to cell#2 (or on cell#1). Alternatively, the base station may transmit SIB1 for cell #2 on cell #2 (or on cell #1) without transmitting a specific DL signal / channel (e.g., ACK).

[0271] The following describes the adaptation of common signal / channel transmission.

[0272] Base stations may apply NES schemes that regulate the transmission of common signals / channels such as SSB, PRACH, and paging. While energy consumption can be significantly reduced by transmitting SSB only as needed rather than fully, stable operation of terminals in the corresponding cell may not be guaranteed if SSB, which supports time / frequency synchronization or RRM measurement, is not fully transmitted. Considering this, energy savings in the base station can be achieved by adjusting or changing the SSB transmission pattern (e.g., transmission period, period per SSB candidate index(s), SSB candidate index(s) transmitted within a single transmission period, transmission power, etc.) according to the situation.

[0273] In the case of PRACH resources, for contention-based random access, network energy consumption may increase because the base station is required to always attempt reception from the PRACH resources configured for the terminal, as it does not know when the terminal will transmit PRACH. Considering this, measures to adjust the amount of PRACH resources can be applied. For example, the cycle of PRACH resources can be adjusted to be longer so that the base station attempts to receive PRACH less frequently. For example, the number of PRACH resources can be reduced, such as by pre-configuring PRACH resource sets #1 and #2 and activating only one of the sets or activating both sets. For example, the amount of PRACH resources corresponding to each SSB index can be provided uniformly or non-uniformly.

[0274] In the case of paging, it is conventionally defined that paging frames (PF) and / or paging occasions (PO) are distributed along the time axis within a DRX cycle (or paging cycle), and terminals attempt to receive paging at specific PF / POs derived from formulas based on their identification information. From the perspective of a base station, if it is intended to transmit paging to multiple terminals simultaneously, it may be necessary to transmit paging messages frequently based on various terminal identification information values. To reduce base station energy consumption resulting from this, methods such as placing the PF and / or PO as close as possible along the time axis or placing them on distinct frequency resources within the same time resource may be applied.

[0275] Transmission / reception of scheduling information via downlink sharing channel

[0276] In 6G systems, technologies for performance enhancement and improvement compared to 5G systems may be introduced. For example, in 5G systems, signaling by a single DCI / PDCCH is required to schedule a single PDSCH or PUSCH. The DCI of the PDCCH may include the frequency position, time position, control information for receiving / transmitting the PDSCH / PUSCH, and control information for operations after receiving / transmitting the PDSCH / PUSCH for the scheduled PDSCH / PUSCH, and may perform L1 (Layer 1) signaling. Generally, the terminal can detect the DCI format, which is CRC scrambled by RNTI, using a blind decoding method in the CORESET monitoring the PDCCH, identify the PDCCH / DCI for itself, and thereby receive / decode or encode / transmit the scheduled PXSCH (PDSCH / PUSCH). Although there are cases where the PDCCH provides simple information instructions to one or more terminals rather than scheduling information for the PXSCH, the present disclosure describes the process based on the PDCCH that schedules the PXSCH.

[0277] A terminal-specific PDCCH contains a DCI format scrambled by C-RNTI and can include control / scheduling information for a single PXSCH transmission and reception. Furthermore, a technique has been introduced in which up to four PDSCH / PUSCHs are scheduled through a single PDCCH. In this case, there is a problem with container constraints, as information for scheduling up to four PXSCHs must be included in a single PDCCH. For example, generally, information for scheduling one PXSCH can be considered to require up to 80 bits, and the size of control information that can be included in a single PDCCH is approximately 140 bits. Therefore, the case where control information for four PXSCHs can be included within a 140-bit container assumes that there is a lot of common information in the scheduling information for two PXSCHs because the in-band channel states are similar during carrier aggregation; however, in cases of low similarity, such as different channel environments, it may be difficult to schedule multiple PXSCHs simultaneously through a single PDCCH.

[0278] In next-generation communication systems, the number of carrier-merged cells may increase from the current 4 or 5 to a maximum of 7 or 8 or more, and services may be possible in various frequency bands ranging from 600 MHz to 100 GHz (or sub-THX). Considering this, scheduling 8 or more PXSCHs through a single PDCCH may exceed the maximum bit limit of the PDCCH. If scheduling information is provided through a separate PDCCH for each PXSCH, overhead may occur where the terminal must perform blind decoding for each of the PDCCHs equal to the number of scheduled PXSCHs. Since blind decoding is a method of verifying whether the information is control information for itself through a CRC check via trial and error based on the terminal's capabilities, very high terminal performance is required to blind decode multiple PDCCHs that simultaneously schedule multiple PXSCHs, or simultaneous scheduling of multiple PXSCHs may not be supported due to limitations in terminal performance. Therefore, in order to support the scheduling of multiple PXSCHs across multiple frequency bands, a new scheduling method is required instead of the existing PDSCH / PUSCH scheduling method using only PDCCH.

[0279] This disclosure describes a new downlink channel that schedules PXSCH. Although channel names defined in 5G systems may not be used in 6G systems, 5G channel names are used exemplarily for clarity of explanation. For example, physical layer channel names such as PDCCH, PDSCH, and PUSCH are used for description; however, the scope of this disclosure is not limited by such names, and the examples of this disclosure may be applied to various channels corresponding to the relevant components. For example, PDCCH is used as a term representing a downlink control channel that carries control information generated at L1 (or the physical layer). PXSCH is used as a term representing a shared / data channel that carries information / data encoded by L1 channel coding MAC PDUs from L2 (or the MAC sublayer). PXSCH is a collective term for PDSCH and PUSCH, and L1 channel coded information / data of downlink-related MAC PDUs can be transmitted and received through PDSCH, and L1 channel coded information / data of uplink-related MAC PDUs can be transmitted and received through PUSCH.

[0280] The maximum number of coded bits of DCI provided through the existing PDCCH is approximately 140. To overcome this limitation, the present disclosure describes a method of scheduling multiple PXSCHs through L1 DCI or L2 MAC CE via PDSCH. These may be referred to as L1 DCI PDSCH and L2 MAC CE PDSCH. Although the existing PDSCH is a shared channel generated by coding MAC PDUs into L1 channels, the DCI, which has a limit on the number of bits because it is provided through the existing PDCCH, can be provided through the PDSCH without a limit on the number of bits in the present disclosure.

[0281] For example, unlike conventional PDCCHs, which apply specific coding (e.g., polar coding in 5G systems) by concatenating DCI field information containing one channel and group-common channel information for a single terminal at L1 in a parallel manner, L1 DCI PDSCHs may include scheduling information for multiple PXSCHs distinguished by BWPs and / or frequency bands for a single terminal at L1. The channel coding of these scheduling PDSCHs may apply a PDCCH channel coding method or a MAC PDU channel coding method. Additionally, while conventional PDCCHs are monitored and received via blind decoding within a specific location (e.g., CORESET), L1 DCI PDSCHs may be received in a different manner.

[0282] For example, an L2 MAC CE PDSCH can be generated by channel coding such an L2 MAC CE, wherein the contents (e.g., bit fields) of a MAC CE generated in L2 (or MAC sublayer) contain scheduling information for PXSCH.

[0283] Such L1 DCI PDSCH and L2 MAC CE PDSCH are collectively referred to as Scheduling-PDSCH in the following description. Scheduling-PDSCH is not only applied for scheduling multiple PXSCHs, but can also be applied for scheduling of a single channel, scheduling of a single terminal, and scheduling of multiple terminals.

[0284] The table below is a comparison of L2 MAC CE PDSCH for L1 DCI PDSCH and PXSCH scheduling corresponding to examples of scheduling-PDSCH.

[0285] Generation Location Channel Coding Comment L1 DCI PDSCHL1 (Physical Layer) Depending on the number of bits to be coded, channel coding applied to the original L1 control PDCCH is applied, or channel coding is applied based on the transport block (TB) corresponding to the MAC PDU transmitted from / to the MAC layer. The channel coding applied to the L2 MAC CE PDSCH may also be applied to the L1 DCI PDSCH. L2 MAC CE PDSCHL2 for PXSCH scheduling Channel coding is applied based on the transport block (TB) corresponding to the MAC PDU transmitted from / to the MAC layer. Channel coding for the MAC PDU may be Turbo Coding (similar to 4G LTE coding technique) or LDPC (similar to 5G NR coding technique).

[0286] FIG. 20 is a drawing for illustrating an example of scheduling-PDSCH according to the present disclosure.

[0287] In the example of Fig. 20(a), when scheduling 8 PXSCHs (PDSCH / PUSCH), it shows a case of one-to-one association between PDCCH and PXSCH, where each L1 DCI PDCCH schedules one PXSCH.

[0288] In the example of FIG. 20(b), since the scheduling-PDSCH (e.g., L1 DCI PDSCH or L2 MAC CE PDSCH) also corresponds to a PDSCH, it can be scheduled by the L1 DCI PDCCH. One scheduling-PDSCH may contain scheduling information for 8 PXSCHs.

[0289] In the example of FIG. 20(a), the scheduling information for 8 PDCCHs for 8 PXSCHs includes common and individual parts, which may result in wasted resources and high computational complexity for blind decoding of 8 PDCCHs. In the example of FIG. 20(b), one scheduling PDSCH is used for scheduling 8 PXSCHs, which increases resource utilization efficiency and reduces the burden of blind decoding. However, compared to FIG. 20(a), one additional step is performed in which scheduling information for scheduling-PDSCH is provided through the PDCCH, which may result in latency.

[0290] In the following sections, process relaxation time and the like are explained through various examples related to the application of Scheduling-PDSCH. Furthermore, regarding semi-persistent scheduling (SPS) in this disclosure, the present disclosure is not limited to the existing method of enabling / disabling periodic transmission and reception of SPS PDSCH within a interval according to a specific SPS setting by L1 DCI PDCCH; a method of enabling / disabling a specific SPS setting through L2 MAC CE and / or L3 RRC messages may also be applied. For example, if Scheduling-PDSCH corresponds to SPS PDSCH, the enabling / disabling of SPS PDSCH can be performed by L1 / L2 / L3 signaling.

[0291] FIG. 21 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.

[0292] In step S2110, the terminal can receive first scheduling information related to the scheduling-downlink shared channel from the network.

[0293] In some examples, the scheduling-downlink shared channel may be based on semi-persistent scheduling (SPS) settings. In this case, the first scheduling information may include information about the activation of the scheduling-downlink shared channel.

[0294] For example, the first scheduling information may include information about one SPS setting among a plurality of SPS settings. For example, the first scheduling information may include information about a plurality of SPS settings. For example, the first scheduling information may include information about one SPS setting associated with a plurality of candidates for a scheduling-downlink shared channel.

[0295] For example, a maximum length limit (e.g., number of OFDM symbols) may be applied to the time length of the scheduling-downlink shared channel. For example, reception of the scheduling-downlink shared channel and transmission of HARQ-ACK (hybrid automatic repeat request-acknowledgement) feedback for the scheduling-downlink shared channel may be performed within a single time unit (e.g., slot) or consecutive time units (e.g., slot).

[0296] In some examples, a maximum limit on the number of scheduled-shared channels may be applied. For example, among the time-frequency resources of a number of scheduled-downlink shared channels corresponding to a maximum number (e.g., N), a specific value (e.g., all 0 or all 1) may be assigned to the time-frequency resources corresponding to an unscheduled number (e.g., NK) based on the second scheduling information scheduling a number of scheduled-shared channels less than the maximum number (e.g., K).

[0297] In some examples, the scheduling-downlink shared channel may be based on dynamic scheduling. For example, the first scheduling information and the scheduling-downlink shared channel may be received within a single time unit (e.g., a slot). For example, a maximum length limit may be applied to the time length of the scheduling-downlink shared channel (e.g., the number of OFDM symbols). For example, the reception of the scheduling-downlink shared channel and the transmission of HARQ-ACK feedback for the scheduling-downlink shared channel may be performed within a single time unit (e.g., a slot) or consecutive time units (e.g., slots).

[0298] In some examples, the first scheduling information may be received via a physical downlink control channel (e.g., PDCCH). Alternatively, the first scheduling information may be received via upper-layer signaling (e.g., L2 MAC CE or L3 RRC message). The upper-layer signaling may be received via a physical downlink shared channel (e.g., PDSCH).

[0299] In step S2120, the terminal may receive from the network a scheduling-downlink shared channel comprising second scheduling information related to one or more scheduled-shared channels based on first scheduling information.

[0300] In some examples, the second scheduling information may include individual scheduling information for each of one or more scheduled-shared channels.

[0301] In some examples, the second scheduling information may include common scheduling information for one or more scheduled-shared channels, and individual scheduling information other than common scheduling information for each of one or more scheduled-shared channels.

[0302] In some examples, the second scheduling information may include common scheduling information of one or more scheduled-shared channels and scheduling information for the difference value between the common scheduling information for each of one or more scheduled-shared channels.

[0303] In step S2130, the terminal may perform reception or transmission of each of one or more scheduled-shared channels based on the second scheduling information.

[0304] The method described in the example of FIG. 21 may be performed by the wireless device (200) of FIG. 3 corresponding to the first node (110) of FIG. 2 described above. For example, one or more processors (202) of the wireless device (200) of FIG. 3 may be configured to receive first scheduling information related to a scheduling-downlink shared channel from a network through one or more transceivers (206), receive a scheduling-downlink shared channel including second scheduling information related to one or more scheduling-shared channels based on the first scheduling information from a network through one or more transceivers (206), and perform the reception or transmission of each of the one or more scheduling-shared channels based on the second scheduling information through one or more transceivers (206). Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 21 or the examples described below when executed by one or more processors (202).

[0305] FIG. 22 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.

[0306] In step S2210, the base station may transmit first scheduling information related to the scheduling-downlink shared channel to the terminal.

[0307] In step S2220, the base station may transmit a scheduling-downlink shared channel to the terminal, which includes second scheduling information related to one or more scheduling-shared channels, based on first scheduling information.

[0308] In step S2230, the base station may perform transmission or reception of each of one or more scheduled-shared channels based on the second scheduling information.

[0309] In the example of FIG. 22, the specific features related to the first scheduling information, the second scheduling information, the scheduling-downlink shared channel, and the scheduled-shared channel are the same as those described with reference to the example of FIG. 21, so redundant descriptions are omitted.

[0310] The method described in the example of FIG. 22 may be performed by the wireless device (200) of FIG. 3 corresponding to the second node (120) of FIG. 2 described above. For example, one or more processors (202) of the wireless device (200) of FIG. 3 may be configured to transmit first scheduling information related to a scheduling-downlink shared channel to a terminal through one or more transceivers (206), transmit a scheduling-downlink shared channel including second scheduling information related to one or more scheduling-shared channels based on the first scheduling information to a terminal through one or more transceivers (206), and perform transmission or reception of each of the one or more scheduling-shared channels based on the second scheduling information through one or more transceivers (206). Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 22 or the examples described below when executed by one or more processors (202).

[0311] In the examples of FIGS. 21 and 22, one or more scheduling-shared channels may include one or more scheduling downlink shared channels and / or one or more scheduling uplink shared channels. For example, the second scheduling information may include scheduling information for a plurality of downlink shared channels. For example, the second scheduling information may include scheduling information for a plurality of uplink shared channels. For example, the second scheduling information may include scheduling information for one or more downlink shared channels and scheduling information for one or more uplink shared channels. The downlink shared channel may be a physical downlink shared channel (e.g., PDSCH). The uplink shared channel may be a physical uplink shared channel (e.g., PUSCH).

[0312] Specific examples of the present disclosure regarding a scheduling-downlink shared channel (e.g., PDSCH) and an uplink / downlink shared channel scheduled accordingly (e.g., PXSCH) are described below.

[0313] Example 1

[0314] Multiple scheduling information for multiple PXSCHs (PDSCH / PUSCH) can be mapped / transmitted through a single physical channel (e.g., scheduling PDSCH). The transmission resources (or transmission opportunities) of the scheduling PDSCH can be set with a predetermined period / pattern. For example, the scheduling PDSCH may correspond to the SPS PDSCH. In the following description, scheduling information for the PXSCH is referred to as DCI, and the scheduling-PDSCH for the PXSCH may also be referred to as DCI PDSCH.

[0315] Example 1-1

[0316] For DCI PDSCH, N DCIs can always be mapped / transmitted using all the resources configured. If the number of DCIs (K) that are actual valid scheduling information is less than N, the remaining (NK) DCIs can be transmitted by mapping values ​​corresponding to invalidity (e.g., a predefined specific value, a padding value such as 0 or 1, or a null value).

[0317] Through SPS settings, the following DCI PDSCH transmission resources and parameters can be configured (e.g., independently of each SPS setting index). The terminal can perform blind decoding of the DCI PDSCH based on the corresponding SPS settings. For example, the maximum number of PXSCHs that can be scheduled through a single DCI PDSCH or the number of cells to be scheduled (e.g., N) and / or cell combinations can be configured. For example, the value of N may be configured as an independent / different value for each SPS setting index. For example, the modulation scheme and / or code rate value for DCI PDSCH signal generation may be configured. For example, frequency resources (e.g., PRB) and time resources (e.g., slot / symbol) for DCI PDSCH signal mapping may be configured.

[0318] These DCI PDSCHs may not contain information (or indicators) indicating the number of scheduled-PXSCH / cells.

[0319] N DCIs can always be multiplexed / mapped and transmitted via DCI PDSCH. For example, K, which is all or part of the N DCIs <N) 개의 DCI가 유효한 PXSCH 스케줄링 정보를 포함할 수 있다. 만약 유효한 K 개의 DCI를 제외한 나머지 (N-K 개) 무효의 DCI에는, 특정 필드(예를 들어, FDRA(frequency domain resource allocation) 필드 또는 TDRA(time domain resource allocation) 필드)를 통해 무효에 해당하는 값이 지시될 수 있으며, 이를 통해 단말은 해당 DCI를 적용하지 않고 무시 또는 폐기(discard)할 수 있다.

[0320] For example, it can be assumed that the entire DCI PDSCH resource is set to 8 PRB indices (0 to 7), the maximum number of PXSCH / cells is set to N=4, and mapped to 2 PRBs per DCI.

[0321] In this case, if K=1, the number of valid DCIs, a valid value may be indicated through the FDRA / TDRA field in the corresponding 1 valid DCI, and an invalid value may be indicated through the FDRA / TDRA field in the remaining 3 DCIs.

[0322] If K=2, valid values ​​may be indicated through the FDRA / TDRA fields in the corresponding 2 valid DCIs, and invalid values ​​may be indicated through the remaining 2 FDRA / TDRA fields in the DCIs.

[0323] If K=3, valid values ​​may be indicated through the FDRA / TDRA fields in the corresponding 3 valid DCIs, and invalid values ​​may be indicated through the remaining 1 FDRA / TDRA field in the DCI.

[0324] If K=4, valid values ​​can be indicated through the FDRA / TDRA fields within all 4 corresponding valid DCIs.

[0325] Examples 1-2

[0326] For a PDSCH containing scheduling MAC CEs, all resources configured can always be used to map / transmit N scheduling MAC CEs. If the number of MAC CEs (K) that are actual valid scheduling information is less than N, the remaining (NK) scheduling MAC CEs can be mapped to and transmitted with values ​​corresponding to invalidity (e.g., a predefined specific value, a padding value such as 0 or 1, or a null value).

[0327] The scheduling MAC CE may include bit fields similar to or corresponding to the DCI. Accordingly, the scheduling MAC CE may include information for scheduling one or more PXSCHs. For example, the scheduling MAC CE may include information similar to the L1 DCI.

[0328] The scheduling MAC CE may include information in the MAC header indicating that scheduling information for N PXSCHs is included. Additionally or alternatively, the scheduling MAC CE may include information in the MAC header indicating that scheduling information for the nth PXSCH is included.

[0329] Through the SPS settings, the transmission resources and parameters of a PDSCH containing a scheduling-MAC CE can be configured (e.g., independently by each SPS setting index). The terminal can perform blind decoding of the PDSCH containing the scheduling-MAC CE based on the corresponding SPS settings. For example, the maximum number of PXSCHs that can be scheduled through a PDSCH containing a single scheduling-MAC CE, or the number of cells being scheduled (e.g., N), and / or cell combinations can be configured. For example, the value of N may be configured as an independent / different value for each SPS setting index. For example, the modulation scheme and / or code rate value for generating the PDSCH signal containing the scheduling-MAC CE can be configured. For example, frequency resources (e.g., PRB) and time resources (e.g., slot / symbol) for mapping the PDSCH signal containing the scheduling-MAC CE can be configured.

[0330] Within the PDSCH containing such scheduling-MAC CE, information (or indicators) indicating the number of scheduled PXSCH / cells may be included. Additionally, information in the form of a bitmap indicating which PXSCH / cells of which order / index are included in the scheduling-MAC CE may be included within the PDSCH containing the scheduling-MAC CE, which sets the order / index for the scheduled PXSCH / cells. For example, such information / indicators regarding the number / order / index may be individually encoded (separate from the scheduling information for the PXSCH) and mapped to a predetermined (or fixed) resource location (e.g., a predetermined PRB / RE index, symbol index) within the PDSCH resource containing the scheduling-MAC CE.

[0331] Through a PDSCH including scheduling-MAC CEs, N MAC CEs can always be multiplexed / mapped and transmitted. For example, K, which is all or part of the N MAC CEs <N) 개의 MAC CE가 유효한 PXSCH 스케줄링 정보를 포함할 수 있다. 만약 유효한 K 개의 MAC CE를 제외한 나머지 (N-K 개) 무효의 MAC CE에는, 특정 필드(예를 들어, FDRA 필드 또는 TDRA 필드)를 통해 무효에 해당하는 값이 지시될 수 있으며, 이를 통해 단말은 해당 MAC CE를 적용하지 않고 무시 또는 폐기(discard)할 수 있다.

[0332] For example, it can be assumed that a PDSCH resource containing the entire scheduling-MAC CE is set to 8 PRB indices (0 to 7), N is set to the maximum number of PXSCH / cells to 4, and that each MAC CE is mapped to 2 PRBs.

[0333] In this case, if K=1, the number of valid MAC CEs, a valid value may be indicated through the FDRA / TDRA field in the corresponding 1 valid MAC CE, and an invalid value may be indicated through the FDRA / TDRA field in the remaining 3 MAC CEs.

[0334] If K=2, valid values ​​may be indicated through the FDRA / TDRA fields in the two corresponding valid MAC CEs, and invalid values ​​may be indicated through the FDRA / TDRA fields in the other two MAC CEs.

[0335] If K=3, valid values ​​may be indicated through the FDRA / TDRA fields in the corresponding 3 valid MAC CEs, and invalid values ​​may be indicated through the FDRA / TDRA field in the remaining 1 MAC CE.

[0336] If K=4, valid values ​​can be indicated through the FDRA / TDRA fields within all 4 corresponding valid MAC CEs.

[0337] Example 2

[0338] This embodiment relates to a dynamic scheduling scheme using 2-stage scheduling-PDSCH.

[0339] L1 scheduling methods may include dynamic scheduling and semi-persistent scheduling. Dynamic scheduling is a method in which scheduling information, such as transmission and reception resources for the PXSCH, is provided whenever PXSCH transmission and reception are required. Semi-persistent scheduling is a method in which an SPS setting is provided to the terminal to pre-allocate resources where the PDSCH can be transmitted, and the SPS PDSCH can be transmitted from the pre-allocated resources from the time SPS activation is instructed via PDCCH / DCI until SPS deactivation is instructed via PDCCH / DCI.

[0340] For example, a method in which first scheduling information for scheduling-PDSCH (e.g., L1 DCI PDSCH or L2 MAC CE PDSCH) is provided through PDCCH and second scheduling information for one or more PXSCHs is provided through scheduling-PDSCH may correspond to a dynamic scheduling method.

[0341] For example, the scheduling-PDSCH of Fig. 20(b) may correspond to a scheduling-PDSCH that is dynamically scheduled by the PDCCH.

[0342] Example 2-1

[0343] The time interval between the PDCCH containing the first scheduling information and the scheduling-PDSCH containing the second scheduling information can be minimized.

[0344] For example, PDCCH and scheduling-PDSCH can be transmitted / received within a single slot.

[0345] For example, a parameter (e.g., k0) corresponding to the time interval between PDCCH and scheduling-PDSCH can be defined / set / fixed to 0 or a very small value.

[0346] By minimizing the latency of the first stage of 2-stage scheduling, the overall latency of PDCCH, scheduling-PDSCH, and scheduled-PXSCH can be reduced.

[0347] Example 2-2

[0348] Limitations on the time length of the scheduling-PDSCH (e.g., the number of OFDM symbols) may be applied.

[0349] For example, the time length of the scheduling-PDSCH can be limited to the minimum number of allowed OFDM symbols (e.g., 2 or 1).

[0350] Alternatively, a predetermined upper limit for the time length of the scheduling-PDSCH is defined / set, and the time length of the scheduling-PDSCH may be limited within a range that does not exceed the said upper limit value.

[0351] For example, such time length limitations may apply to L1 DCI PDSCH. Alternatively, such time length limitations may not apply to PDSCHs that include scheduling-L2 MAC CE.

[0352] Examples 2-3

[0353] The time interval between scheduling-PDSCH and the HARQ-ACK feedback (e.g., ACK / NACK) for it can be minimized.

[0354] For example, a parameter (e.g., k1) for the time interval between PDSCH and HARQ-ACK feedback can be defined / set / fixed to a very small value such as 0 or 1.

[0355] For example, the reception / transmission of the scheduling-PDSCH and the transmission / reception of the HARQ-ACK feedback thereon may be performed within a single slot or on consecutive slots.

[0356] For example, if HARQ-ACK feedback is transmitted via PUCCH, and if it is not easy to transmit PUCCH in the slot where PDSCH was received, the next available PUCCH resource may be given the highest priority to transmit the HARQ-ACK feedback preferentially.

[0357] If candidate value(s) of k1 are provided as a list from the upper layer and the lower layer indicates an index of one of the candidate value(s), the value at the lowest index (or lowest value) among them can be applied as the value of k1.

[0358] Example 3

[0359] This embodiment relates to a one-step semi-persistent scheduling scheme.

[0360] For example, a method in which first scheduling information is provided including information that enables an SPS setting associated with a scheduling-PDSCH (e.g., L1 DCI PDSCH or L2 MAC CE PDSCH) through a PDCCH, and second scheduling information for one or more PXSCHs is provided through the scheduling-PDSCH in SPS resource(s) that appear at a predetermined period may correspond to a semi-persistent scheduling method.

[0361] FIG. 23 shows an example of L1 activation-based SPS-style scheduling-PDSCH according to the present disclosure.

[0362] The first scheduling-PDSCH may correspond to an SPS PDSCH that is enabled / triggered by a PDCCH. In this case, for the scheduling-PDSCH transmitted from the first SPS resource, activation / triggering via the previous PDCCH is required, but for subsequent periodic SPS resource(s), the scheduling-PDSCH may be transmitted without a PDCCH. Each scheduling-PDSCH may include second scheduling information for one or more PXSCHs.

[0363] SPS can be primarily applied in cases where there is no significant change in the size and location of periodically occurring radio resources (e.g., frequency resources such as PRBs and time resources such as symbols / slots) (e.g., VoLTE or VoNR). For example, in cases where the size of a transmission block (TB) corresponding to a MAC PDU of an upper layer is constant and is periodically transmitted to a lower layer, it may correspond to a method of scheduling / activating a periodic PDSCH only once instead of scheduling through PDCCH every time. Similarly, for the uplink, periodic transmission resources may be pre-allocated, and a configured grant (CG)-based PUSCH transmission may be performed in which a PUSCH is transmitted over the resource if there is data to be transmitted by the terminal. Since SPS in this disclosure is not limited to PDSCH but can also be applied to PUSCH, it may be referred to as SPS for PXSCH.

[0364] FIG. 24 illustrates an example of upper-layer activation-based SPS method scheduling-PDSCH according to the present disclosure.

[0365] Unlike the example in FIG. 23 where SPS activation / triggering is provided by L1 DCI PDCCH, the example in FIG. 24 shows a case where information regarding SPS setting / activation / triggering / instruction is provided through upper-level signaling.

[0366] For example, first scheduling information including SPS setting / activation information (e.g., SPS activation information after SPS setting is provided, or SPS activation information provided with SPS setting) may be provided through upper layer signaling. The upper layer signaling may include L2 MAC CE or RRC setting / reset messages and may be received through another PDSCH prior thereto.

[0367] In the example of FIG. 23 or FIG. 24, the second scheduling information included in the scheduling-PDSCH transmitted / received in the SPS method may include information indicating the activation / deactivation of another SPS method PXSCH (e.g., SPS PDSCH or CG-based PUSCH).

[0368] The size of the scheduling-PDSCH may vary with each SPS period depending on factors such as the number of scheduling-PXSCHs. Below, examples are described that support cases where the size of the frequency and time resources transmitted by the scheduling-PDSCH is not constant.

[0369] Example 3-1

[0370] Multiple SPS settings associated with scheduling-PDSCH are provided to a terminal through upper-layer signaling, and one of the SPS setting indices may be indicated along with first scheduling information through a PDCCH that instructs SPS activation. One or more of the multiple SPS settings may be associated with different SPS resources, such as time resource size / location and frequency resource size / location.

[0371] If a change in the size / period of the scheduling-PDSCH is required (e.g., if a change occurs in the number of scheduled-PXSCHs, etc.), a PDCCH for SPS activation may be transmitted to indicate a different SPS setting index along with new first scheduling information. The scheduling-PDSCH transmitted after the said SPS activation PDCCH may be transmitted on a time-frequency resource according to the changed SPS setting.

[0372] Example 3-2

[0373] The activation of multiple SPS settings may be indicated along with the first scheduling information of the SPS-enabled PDCCH. One or more of the time resource size / location and frequency resource size / location may be associated with different SPS resources.

[0374] In this case, the terminal attempts to decode PDSCH on different SPS resources associated with multiple indicated SPS settings and can detect the scheduling-PDSCH transmitted to it among the multiple SPS settings.

[0375] For example, the terminal may determine whether a scheduling-PDSCH is being transmitted to it based on whether the second scheduling information, which is CRC scrambled by the RNTI assigned to it, is included in the scheduling-PDSCH.

[0376] Example 3-3

[0377] Multiple candidates for scheduling-PDSCH can be associated with a single SPS configuration. When a single SPS configuration is activated through an SPS-enabled PDSCH, the terminal attempts to decode the multiple scheduling-PDSCH candidates associated with the activated SPS configuration. Among the multiple scheduling-PDSCH candidates, the terminal can detect the scheduling-PDSCH being transmitted to it.

[0378] For example, the terminal may determine whether a scheduling-PDSCH is being transmitted to it based on whether the second scheduling information, which is CRC scrambled by the RNTI assigned to it, is included in the scheduling-PDSCH.

[0379] Examples 3-4

[0380] Limitations on the time length of the scheduling-PDSCH (e.g., the number of OFDM symbols) may be applied.

[0381] For example, the time length of the scheduling-PDSCH can be limited to the minimum number of allowed OFDM symbols (e.g., 2 or 1).

[0382] Alternatively, a predetermined upper limit for the time length of the scheduling-PDSCH is defined / set, and the time length of the scheduling-PDSCH may be limited within a range that does not exceed the said upper limit value.

[0383] For example, such time length limitations may apply to L1 DCI PDSCH. Alternatively, such time length limitations may not apply to PDSCHs that include scheduling-L2 MAC CE.

[0384] Examples 3-5

[0385] The time interval between scheduling-PDSCH and the HARQ-ACK feedback (e.g., ACK / NACK) for it can be minimized.

[0386] For example, a parameter (e.g., k1) for the time interval between PDSCH and HARQ-ACK feedback can be defined / set / fixed to a very small value such as 0 or 1.

[0387] For example, the reception / transmission of the scheduling-PDSCH and the transmission / reception of the HARQ-ACK feedback thereon may be performed within a single slot or on consecutive slots.

[0388] For example, if HARQ-ACK feedback is transmitted via PUCCH, and if it is not easy to transmit PUCCH in the slot where PDSCH was received, the next available PUCCH resource may be given the highest priority to transmit the HARQ-ACK feedback preferentially.

[0389] If candidate value(s) of k1 are provided as a list from the upper layer and the lower layer indicates an index of one of the candidate value(s), the value at the lowest index (or lowest value) among them can be applied as the value of k1.

[0390] Examples 3-6

[0391] A limit on the maximum value (e.g., Mmax) of the number of PXSCHs scheduled by PDSCH can be applied.

[0392] If the number of added SCells is 7, theoretically, second scheduling information for scheduled-PXSCH transmission and reception in up to 8 cells, including PCell, can be provided through a single scheduling-PDSCH. If the number of scheduled-PXSCHs is limited to 4, 5, or 6, the time resource size and frequency resource size of the scheduling-PDSCH may not change significantly probabilistically.

[0393] When fewer than the maximum value Mmax is allocated by the scheduling-PDSCH, the second scheduling information corresponding to the unallocated PXSCH may be filled entirely with a predetermined value (e.g., a padding value of 0 or 1, or a null value) to implicitly indicate that the PXSCH is not scheduled. Alternatively, some bit field(s) (e.g., FDRA and / or TDRA) of the second scheduling information corresponding to the unallocated PXSCH may be set to a predetermined value (e.g., a padding value of 0 or 1, or a null value) to implicitly indicate that the PXSCH is not scheduled.

[0394] Examples 3-7

[0395] The time-frequency resources of the scheduling-PDSCH may be maximized by considering the maximum number of multiple PXSCHs that can be scheduled. If there is a PXSCH that is not scheduled, the time-frequency resources of the scheduling-PDSCH may be filled with all the time-frequency resources for that PXSCH to a predetermined value (e.g., padding values ​​of 0 or 1, or null values) to implicitly indicate that the PXSCH is not scheduled. Alternatively, some bit field(s) (e.g., FDRA and / or TDRA) of the second scheduling information corresponding to the unscheduled PXSCH may be set to a predetermined value (e.g., padding values ​​of 0 or 1, or null values) to implicitly indicate that the PXSCH is not scheduled.

[0396] Examples 3-8

[0397] Along with the second scheduling information of the scheduling-PDSCH, bitmap information indicating which individual PXSCH among the multiple PXSCHs includes scheduling information may be provided. For example, if the maximum number of schedulable scheduled-PXSCHs is 8, the individual scheduling status of the scheduled-PXSCH at the index corresponding to each bit position may be indicated through an 8-bit bitmap.

[0398] Example 4

[0399] This embodiment relates to the structure of a scheduling-PDSCH.

[0400] As mentioned above, the scheduling-PDSCH may include bit fields related to scheduling information configured in the L1 PHY layer, or bit fields related to scheduling information configured in the MAC PDU format in the L2 MAC sublayer may be transmitted to the L1 PHY layer in the form of a transmission block (TB) to apply L1 channel coding.

[0401] According to the present disclosure, control information for scheduling one or more scheduled-PXSCHs (e.g., second scheduling information) may be included in a single scheduling-PDSCH (e.g., L1 DCI PDSCH or L2 MAC CE PDSCH). Various examples of bit fields corresponding to the second scheduling information being included / arranged in the scheduling-PDSCH are described below. The examples described below may be equally applicable to L1 DCI PDSCH and L2 MAC CE PDSCH, and in the case of L2 MAC CE, MAC header information may be additionally included.

[0402] Example 4-1

[0403] The second scheduling information included in the scheduling-PDSCH may include individual scheduling information for each of one or more scheduled-PXSCHs.

[0404] For example, scheduling information for a single scheduled-PDSCH may include a set of DL allocation bit fields (e.g., bit fields corresponding to DCI format 1 series).

[0405] For example, scheduling information for a single scheduled-PUSCH may include a set of UL grant bit fields (e.g., bit fields corresponding to the DCI format 0 series).

[0406] In one scheduling-PDSCH, one or more DL allocation information and / or one or more UL grant information for one or more scheduling-PXSCHs may be arranged sequentially / consequentially.

[0407] FIG. 25 is a diagram showing examples of the configuration of scheduling information within a scheduling-PDSCH according to the present disclosure.

[0408] As shown in the example of FIG. 25(a), scheduling information for the scheduled-PXSCH 1, scheduling information for the scheduled-PXSCH 2, and scheduling information for the scheduled-PXSCH 3 may be included contiguously or concatenatedly.

[0409] When the second scheduling information is configured in MAC CE format, MAC header information indicating that it is individual scheduling information for each scheduled-PXSCH may be added. For individual scheduling information for PXSCH 1, header information indicating that it is scheduling information for PXSCH 1 may be added. For individual scheduling information for PXSCH 2, header information indicating that it is scheduling information for PXSCH 2 may be added. For individual scheduling information for PXSCH 3, header information indicating that it is scheduling information for PXSCH 3 may be added.

[0410] For example, scheduling information for a single scheduled-PXSCH may be included in a single MAC CE. Alternatively, scheduling information for multiple scheduled-PXSCHs may be included in a single MAC CE.

[0411] If a single scheduling-PDSCH contains multiple scheduling-MAC CEs, each scheduling-MAC CE can be distinguished by an LCID (logical channel ID) or MAC header information. If one scheduling-MAC CE is configured for each of three scheduling-PXSCHs, the three scheduling-MAC CEs may be included in the scheduling-PDSCH in a continuous / contiguous manner.

[0412] Example 4-2

[0413] The second scheduling information included in the scheduling-PDSCH may include common scheduling information for one or more scheduled-PXSCHs, and individual scheduling information other than common scheduling information for each of the one or more scheduled-PXSCHs.

[0414] A single scheduling-PDSCH may include a single common scheduling information part. Additionally, in a single scheduling-PDSCH, individual scheduling information parts excluding the common scheduling information part may be arranged sequentially / consequentially for each scheduling-PXSCH.

[0415] As shown in the example of FIG. 25(b), a scheduling information portion common to the scheduled-PXSCHs, an individual scheduling information portion for scheduled-PXSCH 1, an individual scheduling information portion for scheduled-PXSCH 2, and an individual scheduling information portion for scheduled-PXSCH 3 may be included contiguously or concatenatedly.

[0416] For example, individual scheduling information for each scheduled-PXSCH may include information related to time / frequency resources such as FDRA and / or TDRA. For example, common scheduling information for scheduled-PXSCHs may include modulation and coding scheme (MCS) information, etc.

[0417] When the second scheduling information is configured in MAC CE format, MAC header information indicating that it is a scheduling information part common to the scheduled-PXSCHs, and MAC header information indicating that it is an individual scheduling information part for each scheduled-PXSCH may be added.

[0418] For example, the common scheduling information portion and each individual scheduling information portion may be included in separate MAC CEs. The MAC CE containing the common scheduling information portion and the MAC CE containing each individual scheduling information portion may be distinguished by the logical channel ID (LCID) or MAC header information. Alternatively, the common scheduling information portion and / or one or more individual scheduling information portions may be included in a single MAC CE.

[0419] Example 4-3

[0420] The second scheduling information included in the scheduling-PDSCH may include common scheduling information of one or more scheduled-PXSCHs, and scheduling information regarding the difference value (or delta value) between the common scheduling information for each of the one or more scheduled-PXSCHs.

[0421] A single scheduling-PDSCH may include a common scheduling information portion. Additionally, a difference (or delta) information portion based on the common scheduling information portion may be sequentially / consequentially placed in a single scheduling-PDSCH for each scheduling-PXSCH.

[0422] As shown in the example of FIG. 25(b), a scheduling information portion common to the scheduled-PXSCHs, a difference information portion for scheduled-PXSCH 1, a difference information portion for scheduled-PXSCH 2, and a difference information portion for scheduled-PXSCH 3 may be included contiguously or concatenatedly.

[0423] For example, common scheduling information for scheduled-PXSCHs includes a reference value for modulation and coding scheme (MCS) information, and difference information for each scheduled-PXSCH may include a delta value for the reference MCS.

[0424] For example, common scheduling information for the scheduled-PXSCHs includes a reference offset value for the TDRA information, and difference information for each scheduled-PXSCH may include a delta offset value applied additionally to the reference offset.

[0425] When the second scheduling information is configured in MAC CE format, MAC header information indicating that it is a scheduling information part common to the scheduled-PXSCHs and MAC header information indicating that it is a difference information part for each scheduled-PXSCH may be added.

[0426] For example, the common scheduling information portion and each difference information portion may be included in separate MAC CEs. The MAC CE containing the common scheduling information portion and the MAC CE containing each difference information portion may be distinguished by the logical channel ID (LCID) or MAC header information. Alternatively, the common scheduling information portion and / or one or more difference information portions may be included in a single MAC CE.

[0427] In the examples above, MCS, TDRA, and FDRA were exemplified as bit fields for the common scheduling information part, the individual scheduling information part, or the difference information part, but are not limited thereto, and field(s) corresponding to other names or other information may be defined, and among them, fields to be included in the common / individual / difference information part may be distinguished and defined.

[0428] In the examples described above, PXSCH 1, PXSCH 2, and PXSCH 3 may be assigned to CC (component carrier) 1, CC 2, and CC 3 (or cell 1, cell 2, cell 3), respectively. A single PXSCH may be assigned to a single CC / cell, or multiple PXSCHs may be assigned.

[0429] If scheduling-PDSCH includes L2 MAC CE, the first octet may contain the octet usage length or the ID of the CC (or PCell, SCell) for each CC. Depending on whether PXSCH scheduling is performed per CC / cell, the corresponding field portion may or may not be included in the MAC CE.

[0430] When scheduling-PDSCH includes L1 DCI, since it is difficult to define the total DCI size variably, bit field(s) for unscheduled PXSCH may need to be padded with padding / null values.

[0431] By combining the aforementioned embodiments 4-2 and 4-3, the second scheduling information may be configured such that a common scheduling information portion is included in the scheduling-PDSCH, an individual scheduling information portion is included for one or more scheduled-PXSCHs, and a difference information portion is included for one or more other scheduled-PXSCHs.

[0432] Example 5

[0433] In the examples of the present disclosure, the scheduling-PDSCH may be configured to include a MAC PDU transmitted from an upper layer, and its content may correspond to a combination of one or more existing L1 DCI PDCCHs for one or more scheduling-PXSCHs. Additional examples applicable to the scheduling-PDSCH are described below.

[0434] Example 5-1

[0435] Since carrying a large amount of data through scheduling-PDSCH is rarely required, limitations may be applied to channel state information (CSI) feedback.

[0436] For example, in CSI reports related to scheduling-PDSCH, Rank Indicator (RI) information may be omitted. For example, the RI value may always be fixed at 1.

[0437] For example, for Scheduling-PDSCH, the spatial multiplexing transmission method can be restricted to a specific method, or the spatial multiplexing transmission method can be restricted so that it is not applied.

[0438] These examples apply to L1 DCI scheduling-PDSCH, but may not apply to L2 MAC CE scheduling-PDSCH.

[0439] Example 5-2

[0440] For scheduling-PDSCH, multi-user (MU)-MIMO may not be applied to the (logical) antenna port.

[0441] For example, if MU-MIMO is applied to a second terminal on a PRB containing second scheduling information for a first terminal in a scheduling-PDSCH, and the second terminal uses a different antenna port on the PRB, it may affect the reception performance of the first terminal, thereby increasing the probability of CRC errors occurring. Therefore, MU-MIMO may be restricted so that it is not applied to the PRB within the scheduling-PDSCH.

[0442] These examples apply to L1 DCI scheduling-PDSCH, but may not apply to L2 MAC CE scheduling-PDSCH.

[0443] Example 5-3

[0444] For scheduling-PDSCH, it is possible to ensure that DMRS is always placed on the first OFDM symbol.

[0445] For example, in 5G NR, PDSCH mapping types considering URLLC can be restricted so that only Type B methods are applied to scheduling-PDSCH.

[0446] Examples 5-4

[0447] A parameter k0 for the time interval between the reception time of the existing scheduling information (PDCCH / DCI) and the reception time of the scheduled PDSCH, and a parameter k2 for the time interval between the reception time of the scheduling information (PDCCH / DCI) and the transmission time of the scheduled PUSCH are defined.

[0448] In the case of Scheduling-PDSCH, parameters k0 and k2 may be applied based on the reception time of Scheduling-PDSCH instead of the reception time of the existing scheduling information (PDCCH / DCI). Alternatively, if HARQ-ACK feedback is required for Scheduling-PDSCH, parameters k0 and k2 may be applied based on the transmission time of HARQ-ACK instead of the reception time of the existing scheduling information (PDCCH / DCI).

[0449] If the scheduling-PDSCH is based on L2 MAC CE rather than L1 DCI, additional MAC decoding processing time (e.g., 3ms) may be required. Therefore, parameters k0 and k2 for the time interval from the reception time of the scheduling-PDSCH to the reception / transmission time of the scheduled-PXSCH may be given as values ​​with added MAC decoding processing time, or values ​​greater than the MAC decoding processing time.

[0450] Examples 5-5

[0451] When scheduling-PDSCH is allocated on frequency domain resources, frequency diversity is not applied, and PRBs may be restricted to be placed consecutively.

[0452] These restrictions apply to L1 DCI scheduling-PDSCH but may not apply to L2 MAC CE scheduling-PDSCH.

[0453] For example, in the first scheduling information for scheduling-PDSCH, a new form of FDRA may be applied through simple information such as offsets and counts in RBG units, rather than the existing FDRA's RBG (resource block group) or RIV (resource indication value) methods. Alternatively, in the first scheduling information for scheduling-PDSCH, only RIV may be applied, or an allocation method in the form of RBG may not be applied.

[0454] Examples 5-6

[0455] PDSCH and PUSCH may be scheduled together by scheduling-PDSCH. In this case, when applying Mmax, which is the maximum number of schedulable PXSCHs, Mmax may be defined individually for the scheduled-PDSCH and the scheduled-PUSCH, or Mmax may be defined for the sum of the scheduled-PDSCH and the scheduled-PUSCH.

[0456] These Mmax values ​​can be set by the upper layer.

[0457] Examples 5-7

[0458] If the scheduling-PDSCH corresponds to the SPS PDSCH, the activation / deactivation of the SPS PDSCH can be directed not only by the PDCCH / DCI but also by other scheduling-PDSCHs.

[0459] Examples 5-8

[0460] The scheduling-PDSCH in the examples described above may be applied to provide scheduling for multiple cells / carriers / BWPs for a single terminal, and furthermore, may be applied to schedule multiple PXSCHs for multiple terminals. For example, one or more PXSCHs may be scheduled for a first terminal, and one or more PXSCHs may be scheduled for a second terminal. In this case, identification information such as RNTI that can be commonly identified by multiple terminals may be defined.

[0461] To enable multiple terminals to decode a single scheduling-PDSCH, the single scheduling-PDSCH may include identification information for multiple terminals. For example, an L1 DCI-based scheduling-PDSCH may include a DCI that is CRC-scrambed by the ID of each terminal. For example, an L2 MAC CE-based scheduling-PDSCH may include the ID of each terminal in the MAC header of the MAC CE.

[0462] According to the various examples of the present disclosure described above, a downlink shared channel (e.g., scheduling-PDSCH) that schedules one or more downlink / uplink shared channels (e.g., scheduling-PDSCH / PUSCH) may be provided. Furthermore, various detailed examples for reducing process relaxation time, error rates, and enhancing reliability for scheduling-PDSCH may be applied. Accordingly, the complexity, power consumption, and overhead of terminal operations regarding blind decoding in conventional PDCCH / DCI-based scheduling can be reduced or eliminated. In addition, unlike conventional PDCCH / DCI which is limited to a CORESET / search space, scheduling-PDSCH can be flexibly deployed on any resource. From the perspective of eMBB, operations in which uplink and downlink scheduling are simultaneously scheduled / serviced for a single terminal may also be supported. Therefore, while simplifying the process of searching for terminal scheduling information, various scheduling information that could not previously be provided together can be easily provided. In addition, the scheduling-PDSCH according to the present disclosure can provide scheduling information for one terminal or multiple terminals together, and scheduling information for the commonly / individually scheduled-PXSCH can be efficiently provided in a unicast / multicast / broadcast manner.

[0463] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0464] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Accordingly, the detailed description set forth above should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0465] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and may include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0466] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0467] Although the method proposed in this disclosure has been described with an example applied to 3GPP LTE / LTE-A, 5G, and 6G systems, it is possible to apply it to various wireless communication systems in addition to 3GPP LTE / LTE-A, 5G, and 6G systems.

Claims

1. Scheduling - A step of receiving first scheduling information related to a downlink shared channel from a network by a terminal; A step of receiving from the network by the terminal the scheduling-downlink shared channel comprising second scheduling information related to one or more scheduled-shared channels based on the first scheduling information; and A method comprising the step of performing reception or transmission of each of the one or more scheduled-shared channels by the terminal based on the second scheduling information.

2. In Paragraph 1, The above scheduling-downlink shared channel is based on semi-persistent scheduling (SPS) configuration, and A method in which the first scheduling information includes information on the activation of the scheduling-downlink sharing channel.

3. In Paragraph 2, The above first scheduling information is: Information on one SPS setting among multiple SPS settings; Information on multiple SPS settings; or Information regarding a single SPS configuration associated with multiple candidates for the above scheduling-downlink shared channel A method including 4. In Paragraph 2, A method in which a maximum number limit is applied to the number of the above-mentioned scheduled-shared channels.

5. In Paragraph 4, A method in which, among the time-frequency resources of the number of scheduling-downlink shared channels corresponding to the maximum number, the second scheduling information schedules the number of scheduling-shared channels less than the maximum number, and a specific value is assigned to the time-frequency resources corresponding to the number of unscheduled channels.

6. In Paragraph 1, The above scheduling-downlink shared channel is a method based on dynamic scheduling.

7. In Paragraph 6, A method in which the first scheduling information and the scheduling-downlink sharing channel are received within one time unit.

8. In Paragraph 1, A method in which a limit on the maximum length of the time length of the above scheduling-downlink shared channel is applied.

9. In Paragraph 1, A method in which the reception of the scheduling-downlink shared channel and the transmission of HARQ-ACK (hybrid automatic repeat request-acknowledgement) feedback for the scheduling-downlink shared channel are performed within a single time unit or consecutive time units.

10. In Paragraph 1, A method in which the second scheduling information comprises individual scheduling information for each of the one or more scheduled-shared channels.

11. In Paragraph 1, A method comprising the second scheduling information, the common scheduling information of the one or more scheduled-shared channels, and individual scheduling information other than the common scheduling information for each of the one or more scheduled-shared channels.

12. In Paragraph 1, A method comprising: the second scheduling information comprising common scheduling information of one or more scheduled-shared channels, and scheduling information for a difference value from the common scheduling information for each of the one or more scheduled-shared channels.

13. In Paragraph 1, The above one or more scheduled-shared channels, A method comprising one or more scheduled-downlink shared channels, or one or more scheduled-uplink shared channels.

14. In Paragraph 1, A method in which the above-mentioned first scheduling information is received through a physical downlink control channel or through upper-layer signaling.

15. In Paragraph 13, The above downlink sharing channel is a physical downlink sharing channel, and The above uplink sharing channel is a physical uplink sharing channel, method.

16. One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Scheduling—receiving first scheduling information related to a downlink shared channel from a network through one or more transceivers; Based on the first scheduling information, receiving the scheduling-downlink shared channel from the network through the one or more transceivers, the scheduling-downlink shared channel including second scheduling information related to one or more scheduled-shared channels; and A terminal configured to perform the reception or transmission of each of the one or more scheduled-shared channels through the one or more transceivers based on the second scheduling information above.

17. Scheduling - A step of transmitting first scheduling information related to a downlink shared channel to a terminal by a base station; A step of transmitting the scheduling-downlink shared channel, comprising second scheduling information related to one or more scheduled-shared channels based on the first scheduling information, to the terminal by the base station; and A method comprising the step of performing transmission or reception of each of the one or more scheduled-shared channels by the base station based on the second scheduling information.

18. One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Scheduling—transmitting first scheduling information related to a downlink shared channel to a terminal through one or more transceivers; Based on the first scheduling information, the scheduling-downlink shared channel including second scheduling information related to one or more scheduled-shared channels is transmitted to the terminal through the one or more transceivers; and A base station configured to perform transmission or reception of each of the one or more scheduled-shared channels through the one or more transceivers based on the above second scheduling information.

19. One or more processors; and A processing device comprising one or more computer memories that are operably connected to one or more processors and store instructions for performing a method according to any one of claims 1 to 15 based on execution by one or more processors.

20. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the execution of a method according to any one of claims 1 through 15.

Images