Method and device for transmitting or receiving channel state information in wireless communication system
The method facilitates quicker CSI reporting and resource allocation by having the UE and base station exchange CSI-RS and CSI, addressing the challenge of rapid CSI derivation in 6G systems during state transitions and Scell activation.
Patent Information
- Application Number
- PCT/KR2026/096695
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
The challenge in 6G wireless communication systems is the rapid calculation, derivation, and reporting of channel state information (CSI) when transitioning from an IDLE/INACTIVE state to a CONNECTED state or activating a dormant secondary cell (Scell), which is not efficiently addressed by existing technologies.
A method involving a user device (UE) receiving a downlink transmission and CSI-RS from a base station, determining an uplink resource, and transmitting CSI based on a request, while the base station transmits a downlink transmission and receives CSI from the UE, facilitating quicker CSI reporting and effective resource allocation.
Enables faster CSI reporting and more efficient resource allocation for early CSI acquisition, enhancing the transition process from IDLE/INACTIVE to CONNECTED states and Scell activation.
Smart Images

Figure KR2026096695_12112026_PF_FP_ABST
Abstract
Description
Method and device for transmitting and receiving channel state information 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 and receiving channel state information 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 proposes a method to support the rapid calculation, derivation, and reporting of channel status information when changing the state of a UE from an IDLE / INACTIVE state to a CONNECTED state or when activating a deactivated / dormant secondary cell (Scell).
[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 an aspect of the present disclosure may include: receiving, by a user device (UE), a downlink transmission associated with a random access procedure or a secondary cell (Scell) from the base station; receiving, by the UE, a channel state information-reference signal (CSI-RS) from the base station; and transmitting the CSI to the base station by the UE based on a request to report the CSI by the downlink transmission. An uplink resource for transmitting the CSI may be determined based on the downlink transmission.
[0007] A method according to a further aspect of the present disclosure may include: transmitting a downlink transmission associated with a random access procedure or a secondary cell (Scell) to user equipment (UE) by a base station; transmitting a channel state information-reference signal (CSI-RS) to the UE by the base station; and receiving the CSI from the UE by the base station based on a request to report the CSI by the downlink transmission. An uplink resource for transmitting the CSI may be determined based on the downlink transmission.
[0008] According to an embodiment of the present disclosure, when transitioning from an IDLE / INACTIVE state to a CONNECTED state or when an Scell is activated from an inactive / dormancy state, the UE can report CSI more quickly.
[0009] In addition, according to an embodiment of the present disclosure, resources to perform CSI reporting for early CSI acquisition can be more effectively allocated to a terminal by utilizing existing operations / messages.
[0010] 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.
[0011] 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.
[0012] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.
[0013] FIG. 2 illustrates an exemplary communication system to which some examples of the present disclosure may be applied.
[0014] FIG. 3 illustrates an exemplary wireless device to which some examples of the present disclosure may be applied.
[0015] 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.
[0016] FIG. 5 illustrates an exemplary functional framework for AI / ML operations to which some examples of the present disclosure may be applied.
[0017] FIG. 6 illustrates an exemplary communication procedure based on an AI / ML model between a first node and a second node to which some examples of the present disclosure may be applied.
[0018] FIG. 7 shows an electromagnetic spectrum to which some examples of the present disclosure may be applied.
[0019] FIG. 8 illustrates an exemplary system information transmission / reception procedure to which some examples of the present disclosure may be applied.
[0020] FIG. 9 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.
[0021] FIG. 10 is a diagram illustrating the operation of a UE for a channel status information transmission and reception method according to one embodiment of the present disclosure.
[0022] FIG. 11 is a diagram illustrating the operation of a base station for a channel status information transmission and reception method according to one embodiment of the present disclosure.
[0023] 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.
[0024] 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.
[0025] 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.
[0026] 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.
[0027] 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.
[0028] 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."
[0029] 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."
[0030] 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."
[0031] 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."
[0032] Additionally, parentheses used in this 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 this 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."
[0033] In the following explanation, '...when, if, in case of' can be replaced with '...based on'.
[0034] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.
[0035] 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.
[0036] In the present disclosure, the base station (BS) may be a second node / IAB node / Transmission-Reception Point (TRP).
[0037] 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.
[0038] 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.
[0039] 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.
[0040] 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) / 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.
[0041] 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.
[0042] Network structure
[0043] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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; and may correspond to a first intermediate point and a second intermediate point, respectively.
[0049] 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.
[0050] Systems applicable to the present disclosure
[0051] FIG. 2 illustrates an exemplary communication system to which some examples of the present disclosure may be applied.
[0052] 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).
[0053] 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).
[0054] 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.
[0055] Devices applicable to the present disclosure
[0056] FIG. 3 illustrates an exemplary wireless device to which some examples of the present disclosure may be applied.
[0057] 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).
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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).
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] Communication procedures
[0072] 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.
[0073] 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.
[0074] 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).
[0075] 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.
[0076] 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 the 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).
[0077] 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.
[0078] 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.
[0079] 6G System Core Technology
[0080] 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.
[0081] artificial intelligence
[0082] 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. In other words, 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 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.
[0083] The following describes a functional framework for AI / ML operations.
[0084] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.
[0085] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for AI model training, data analysis, and inference.
[0086] - 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.
[0087] - 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.
[0088] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.
[0089] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updating, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identifiable within the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified within the network, and the network or terminal can activate, deactivate, select, or switch AI / ML models via the model ID.
[0090] FIG. 5 illustrates an exemplary functional framework for AI / ML operations to which some examples of the present disclosure may be applied.
[0091] Figure 5 illustrates a general functional architecture related to both Functionality-based LCM and Model-based LCM. Some functions or some data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.
[0092] Referring to FIG. 5, a general functional framework may be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).
[0093] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The Data Collection function (10) may be performed by a single entity (e.g., terminal, network node, etc.) but may also be performed by multiple entities.
[0094] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).
[0095] The Model Training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the Training Data (11) delivered from the Data Collection function (10).
[0096] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).
[0097] The Management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the Management function (30) may make decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).
[0098] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).
[0099] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).
[0100] Performance Feedback / Retraining Request (31) refers to information required as input to Model Training function (20) (e.g., for the purpose of retraining or updating the model).
[0101] The inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).
[0102] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.
[0103] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40). The Model Storage function (50) exemplified in FIG. 2 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the Model Storage function (50) is an example and is not intended to restrict the storage location of the actual AI / ML model and may be omitted.
[0104] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.
[0105] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.
[0106] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.
[0107] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.
[0108] Cat 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.
[0109] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.
[0110] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and all functions and / or all data / information / command signals illustrated in FIG. 5 may not be performed within a specific node, and only some may be performed.
[0111] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.
[0112] A one-side model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a terminal or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.
[0113] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.
[0114] - First type: An AI / ML model can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / entities.
[0115] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation) and model reconstruction (CSI compression by sub-use cases) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).
[0116] - Third Type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.
[0117] FIG. 6 illustrates an exemplary communication procedure based on an AI / ML model between a first node and a second node to which some examples of the present disclosure may be applied.
[0118] Step 1: In the description of the present disclosure below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or a set of signaling of Step 1 used to perform an operation based on an AI / ML model, unless otherwise noted. For example, it may correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 2, or to inference data used for inference of the AI / ML model, or to feedback to the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present disclosure, Step 1 may be omitted. If a one-side model is used in the present disclosure, unidirectional / bidirectional signaling (set) in the present disclosure may correspond to the signaling of Step 1. In addition, when a two-side model is used in the present disclosure, unidirectional / bidirectional signaling in the present disclosure may correspond to one stage of signaling, and repetitive signaling operations may also correspond to one stage of signaling.
[0119] For example, in AI / ML model-based beam management, when a base station predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from the terminal. Additionally, when a terminal predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the terminal can receive multiple beams from the base station.
[0120] Step 2: In the description of the present disclosure below, operations (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or common operations (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., terminal, network, etc.) may correspond to operations of Step 2 based on one or more functions in the functional framework of an AI / ML model, unless otherwise noted. For example, they may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 2 or to inference of the AI / ML model. When a one-side model is used, operations performed by a single node in the present disclosure may correspond to operations of Step 2, and when a two-side model is used, common operations performed by multiple nodes in the present disclosure may correspond to operations of Step 2.
[0121] For example, in an AI / ML model-based BM, a base station can predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using quality / intensity information for multiple beams received from a terminal as inference data. Additionally, a terminal can measure multiple beams received from a base station and predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using the measurement results as inference data.
[0122] Step 3: In the description of the present disclosure below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or set of signaling of Step 3 generated as a result of an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 2. If signaling between nodes is not required as a result of an operation based on an AI / ML model in the present disclosure, Step 3 may be omitted. If a one-side model is used in the present disclosure, unidirectional / bidirectional signaling (set) in the present disclosure may correspond to the signaling of Step 3. Furthermore, if a two-side model is used in the present disclosure, unidirectional / bidirectional signaling in the present disclosure may correspond to the signaling of Step 3, and repetitive signaling operations may also correspond to the signaling of Step 3.
[0123] For example, in an AI / ML model-based BM, the base station may transmit beam(s) predicted based on the AI / ML model as candidates to the terminal so that the terminal can determine the optimal beam. Additionally, the terminal may report the beam(s) predicted based on the AI / ML model to the base station to request the base station to transmit candidate beams as candidates for determining the optimal beam.
[0124] THz communication
[0125] 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.
[0126] FIG. 7 shows an electromagnetic spectrum to which some examples of the present disclosure may be applied.
[0127] 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.
[0128] 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.
[0129] FIG. 8 illustrates an exemplary system information transmission / reception procedure to which some examples of the present disclosure may be applied.
[0130] The example of FIG. 8 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applied. In addition, the procedure illustrated in FIG. 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information obtained by the procedure illustrated in FIG. 8.
[0131] 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.
[0132] 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 for cell #1 is received in cell #2, the acquisition of synchronization for cell #1 can be performed after receiving the system information. For example, the terminal can acquire synchronization based on the system information. Alternatively, the acquisition of synchronization may be performed prior to step S1010.
[0133] 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.
[0134] The procedure described with reference to FIG. 8 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).
[0135] 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.
[0136] FIG. 9 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.
[0137] Figure 9 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.
[0138] 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.
[0139] In step S1110, the second node (120) (e.g., a base station) may set resources for beam management to the first node (110) (e.g., a 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.
[0140] 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).
[0141] In step S1150, 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.
[0142] In step S1170, the first node (110) and the second node (120) can communicate. 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).
[0143] Channel State Information (CSI) Related Operations
[0144] In NR (New Radio) systems, CSI-RS (channel state information-reference signal) is used for time and / or frequency tracking, CSI computation, L1 (layer 1)-RSRP (reference signal received power) computation, and mobility. Here, CSI computation is related to CSI acquisition, and L1-RSRP computation is related to beam management (BM).
[0145] CSI (channel state information) is a general term for information that can indicate the quality of the wireless channel (also called a link) formed between a terminal and an antenna port.
[0146] - To perform one of the uses of CSI-RS as described above, a terminal (e.g., user equipment, UE) receives configuration information related to CSI from a base station (e.g., general Node B, gNB) via RRC (radio resource control) signaling.
[0147] The configuration information related to the above CSI may include at least one of information related to CSI-IM (interference management) resources, information related to CSI measurement configurations, information related to CSI resource configurations, information related to CSI-RS resources, or information related to CSI report configurations.
[0148] i) Information related to CSI-IM resources may include CSI-IM resource information, CSI-IM resource set information, etc. A CSI-IM resource set is identified by a CSI-IM resource set ID (identifier), and one resource set includes at least one CSI-IM resource. Each CSI-IM resource is identified by a CSI-IM resource ID.
[0149] ii) Information related to CSI resource configuration may be expressed as CSI-ResourceConfig IE. Information related to CSI resource configuration defines a group including at least one of an NZP (non-zero power) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the information related to CSI resource configuration includes a CSI-RS resource set list, and the CSI-RS resource set list may include at least one of an NZP CSI-RS resource set list, a CSI-IM resource set list, or a CSI-SSB resource set list. A CSI-RS resource set is identified by a CSI-RS resource set ID, and one resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.
[0150] For each NZP CSI-RS resource set, parameters indicating the use of CSI-RS (e.g., BM-related 'repetition' parameter, tracking-related 'trs-Info' parameter) can be set.
[0151] iii) Information related to the CSI report configuration includes a reportConfigType parameter representing the time domain behavior and a reportQuantity parameter representing the quantity of CSI to be reported. The time domain behavior may be periodic, aperiodic, or semi-persistent.
[0152] - The terminal measures the CSI based on configuration information related to the above CSI.
[0153] The above CSI measurement may include (1) a process of receiving CSI-RS from a terminal and (2) a process of computing CSI through the received CSI-RS, and a detailed explanation thereof will be provided later.
[0154] In CSI-RS, the mapping of resource elements (RE) of CSI-RS resources in the time and frequency domains is established by the higher layer parameter CSI-RS-ResourceMapping.
[0155] - The terminal reports the above-mentioned CSI to the base station.
[0156] Here, if the quantity of CSI-ReportConfig is set to 'none (or No report)', the terminal may omit the report. However, even if the quantity is set to 'none (or No report)', the terminal may still report to the base station. The case where the quantity is set to 'none' is when aperiodic TRS is triggered or when repetition is set. Here, the terminal may omit the report only when repetition is set to 'ON'.
[0157] 1) CSI measurement
[0158] The NR system supports more flexible and dynamic CSI measurement and reporting. Here, the CSI measurement may include a procedure for receiving CSI-RS and acquiring CSI by computationing the received CSI-RS.
[0159] As time domain behaviors for CSI measurement and reporting, aperiodic / semi-persistent / periodic CM (channel measurement) and IM (interference measurement) are supported. A 4-port NZP CSI-RS RE pattern is used for CSI-IM configuration.
[0160] NR's CSI-IM-based IMR has a design similar to LTE's CSI-IM and is configured independently of ZP CSI-RS resources for PDSCH rate matching. In addition, in the NZP CSI-RS-based IMR, each port emulates an interference layer with (desired channel and) precoded NZP CSI-RS. This is for intra-cell interference measurement in the multi-user case and primarily targets MU interference.
[0161] The base station transmits precoded NZP CSI-RS to the terminal on each port of the configured NZP CSI-RS-based IMR.
[0162] The terminal measures interference by assuming a channel / interference layer for each port in the resource set.
[0163] For a channel, if there is no PMI and RI feedback, multiple resources are set, and the base station or network indicates a subset of NZP CSI-RS resources via DCI for channel / interference measurement.
[0164] We will examine resource setting and resource setting configuration in more detail.
[0165] 2) Resource setting
[0166] Each CSI resource setting 'CSI-ResourceConfig' contains a configuration for S≥1 CSI resource sets (given by the higher layer parameter csi-RS-ResourceSetList). The CSI resource setting corresponds to the CSI-RS-resourcesetlist, where S represents the number of configured CSI-RS resource sets. Here, the configuration for S≥1 CSI resource sets includes each CSI resource set containing CSI-RS resources (configured as NZP CSI-RS or CSI-IM) and the SS / PBCH block (SSB) resource used for L1-RSRP computation.
[0167] Each CSI resource setting is located in a DL BWP (bandwidth part) identified by the higher layer parameter bwp-id. Additionally, all CSI resource settings linked to a CSI reporting setting have the same DL BWP.
[0168] Within the CSI resource setting included in CSI-ResourceConfig IE, the time domain behavior of the CSI-RS resource is dictated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource settings, the number of configured CSI-RS resource sets (S) is limited to '1'. For periodic and semi-persistent CSI resource settings, the configured periodicity and slot offset are given from the numerology of the associated DL BWP, as given by bwp-id.
[0169] When a UE is configured with multiple CSI-ResourceConfigs containing the same NZP CSI-RS resource ID, the same time domain behavior is configured for the CSI-ResourceConfigs.
[0170] When a UE is configured with multiple CSI-ResourceConfigs containing the same CSI-IM resource ID, the same time domain behavior is configured for the CSI-ResourceConfigs.
[0171] Next, one or more CSI resource settings for channel measurement (CM) and interference measurement (IM) are established through higher layer signaling.
[0172] - CSI-IM resource for interference measurement.
[0173] - NZP CSI-RS resources for interference measurement.
[0174] - NZP CSI-RS resources for channel measurement.
[0175] That is, the CMR (channel measurement resource) may be an NZP CSI-RS for CSI acquisition, and the IMR (Interference measurement resource) may be an NZP CSI-RS for CSI-IM and IM.
[0176] Here, CSI-IM (or ZP CSI-RS for IM) is primarily used for inter-cell interference measurements.
[0177] Also, the NZP CSI-RS for IM is mainly used for intra-cell interference measurement from multi-users.
[0178] The UE can assume that the CSI-RS resource(s) for channel measurement and the CSI-IM / NZP CSI-RS resource(s) for interference measurement set for one CSI reporting are 'QCL-TypeD' on a resource-by-resource basis.
[0179] 3) Resource setting configuration
[0180] As examined, resource setting can refer to a resource set list.
[0181] For aperiodic CSI, each trigger state set using the higher layer parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, each of which is linked to a periodic, semi-persistent, or aperiodic resource setting.
[0182] One reporting setting can be linked to up to three resource settings.
[0183] - When a resource setting is set, the resource setting (given by the higher layer parameter resourcesForChannelMeasurement) is for channel measurements for L1-RSRP computation.
[0184] - When two resource settings are set, the first resource setting (given by the higher layer parameter resourcesForChannelMeasurement) is for channel measurement, and the second resource setting (given by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) is for interference measurement performed on CSI-IM or NZP CSI-RS.
[0185] - When three resource settings are set, the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement, the second resource setting (given by csi-IM-ResourcesForInterference) is for CSI-IM based interference measurement, and the third resource setting (given by nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference measurement.
[0186] For semi-persistent or periodic CSI, each CSI-ReportConfig is linked to a periodic or semi-persistent resource setting.
[0187] - When a resource setting (given by resourcesForChannelMeasurement) is configured, said resource setting is for channel measurements for L1-RSRP computation.
[0188] - When two resource settings are configured, the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement, and the second resource setting (given by higher layer parameter csi-IM-ResourcesForInterference) is used for interference measurement performed on CSI-IM.
[0189] 4) CSI Computation
[0190] When interference measurements are performed on CSI-IM, each CSI-RS resource for channel measurement is associated with a CSI-IM resource by resource in the order of CSI-RS resources and CSI-IM resources within the corresponding resource set. The number of CSI-RS resources for channel measurement is equal to the number of CSI-IM resources.
[0191] And, when interference measurement is performed in NZP CSI-RS, the UE does not expect to be set to one or more NZP CSI-RS resources in the associated resource set within the resource setting for channel measurement.
[0192] A terminal with the Higher layer parameter nzp-CSI-RS-ResourcesForInterference configured does not expect more than 18 NZP CSI-RS ports to be configured within the NZP CSI-RS resource set.
[0193] For CSI measurement, the terminal assumes the following:
[0194] - Each NZP CSI-RS port configured for interference measurement corresponds to the interference transport layer.
[0195] - All interference transmission layers of the NZP CSI-RS port for interference measurement consider the EPRE (energy per resource element) ratio.
[0196] - Other interference signals on the RE(s) of the NZP CSI-RS resource for channel measurement, the NZP CSI-RS resource for interference measurement, or the CSI-IM resource for interference measurement.
[0197] 5) CSI Report
[0198] For CSI reporting, the time and frequency resources available to the UE are controlled by the base station.
[0199] Channel state information (CSI) may include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), or an L1-RSRP.
[0200] For CQI, PMI, CRI, SSBRI, LI, RI, and L1-RSRP, the terminal is configured by a higher layer with N≥1 CSI-ReportConfig reporting settings, M≥1 CSI-ResourceConfig resource settings, and a list of one or two trigger states (provided by aperiodicTriggerStateList and semiPersistentOnPUSCH-TriggerStateList). In the aperiodicTriggerStateList, each trigger state includes an associated list of CSI-ReportConfigs indicating resource set IDs for the channel and optionally interference. In the semiPersistentOnPUSCH-TriggerStateList, each trigger state includes one associated CSI-ReportConfig.
[0201] In addition, the time domain behavior of CSI reporting supports periodic, semi-persistent, and aperiodic.
[0202] i) Periodic CSI reporting is performed on short PUCCH and long PUCCH. The periodicity and slot offset of Periodic CSI reporting can be set to RRC, and refer to CSI-ReportConfig IE.
[0203] ii) SP (semi-periodic) CSI reporting is performed on short PUCCH, long PUCCH, or PUSCH.
[0204] In the case of SP CSI on Short / long PUCCH, periodicity and slot offset are set to RRC, and CSI reporting is activated / deactivated with separate MAC CE / DCI.
[0205] In the case of SP CSI on PUSCH, the periodicity of SP CSI reporting is set to RRC, but the slot offset is not set to RRC, and SP CSI reporting is activated / deactivated by DCI(format 0_1). For SP CSI reporting on PUSCH, a separate RNTI (SP-CSI C-RNTI) is used.
[0206] The initial CSI reporting timing follows the PUSCH time domain allocation value specified by DCI, and subsequent CSI reporting timing follows the period set by RRC.
[0207] DCI format 0_1 includes a CSI request field and can activate / deactivate a specific configured SP-CSI trigger state. SP CSI reporting has the same or similar activation / deactivation mechanism as the data transmission mechanism on SPS PUSCH.
[0208] iii) aperiodic CSI reporting is performed on PUSCH and triggered by DCI. In this case, information related to the trigger of aperiodic CSI reporting can be transmitted / instructed / set via MAC-CE.
[0209] In the case of an AP CSI with AP CSI-RS, the AP CSI-RS timing is set by the RRC, and the timing for AP CSI reporting is dynamically controlled by the DCI.
[0210] NR does not apply the method of splitting CSIs across multiple reporting instances (e.g., transmitting in the order of RI, WB PMI / CQI, SB PMI / CQI) that was applied to PUCCH-based CSI reporting in LTE. Instead, NR restricts the setting of specific CSI reports in short / long PUCCHs, and CSI omission rules are defined. Regarding AP CSI reporting timing, the PUSCH symbol / slot location is dynamically determined by the DCI, and candidate slot offsets are set by the RRC. For CSI reporting, the slot offset (Y) is set per reporting setting. For UL-SCH, the slot offset K2 is set separately.
[0211] Two CSI latency classes (low latency class and high latency class) are defined in terms of CSI computation complexity. Low-latency CSI refers to WB CSIs that include up to 4-port Type-I codebooks or up to 4-port non-PMI feedback CSIs. High-latency CSI refers to any CSI other than low-latency CSIs. For a normal terminal, (Z, Z') is defined in the unit of OFDM symbols. Here, Z represents the minimum CSI processing time from receiving an Aperiodic CSI-triggering DCI to performing a CSI report. Additionally, Z' represents the minimum CSI processing time from receiving a CSI-RS for channel / interference to performing a CSI report.
[0212] Additionally, the terminal reports the number of CSIs that can be calculated simultaneously.
[0213] The activation or deactivation of a semi-persistent CSI-RS / CSI-IM resource set is directed by the network via a specific MAC CE. The configured semi-persistent CSI-RS / CSI-IM resource set is initially deactivated at the time of configuration and after a handover. The MAC entity receiving the corresponding MAC CE directs the lower layer (e.g., PHY) to the information related to that MAC CE.
[0214] Aperiodic CSI trigger state subselection is directed from the network via a specific MAC CE, and an Aperiodic CSI trigger state can be selected from among the configured AP CSI trigger states of the serving cell. The MAC entity receiving the corresponding MAC CE instructs the lower layer (e.g., PHY) with information related to the MAC CE.
[0215] Quasi-Co Location (QCL)
[0216] An antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship.
[0217] Here, the channel characteristics include one or more of delay spread, Doppler spread, frequency / Doppler shift, average received power, received timing / average delay, and spatial Rx parameters. Here, spatial Rx parameters refer to spatial (received) channel characteristic parameters such as the angle of arrival.
[0218] The terminal may be configured with a list of up to M TCI-State settings within the upper-level parameter PDSCH-Config to decode the PDSCH according to the detected PDCCH having the DCI intended for the terminal and the given serving cell. The said M depends on the UE capability.
[0219] Each TCI-State includes parameters for establishing a quasi-co-location relationship between one or two DL reference signals and the DM-RS port of the PDSCH.
[0220] The quasi co-location relationship is established by the upper-level parameter qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if set). For two DL RSs, the QCL type is not the same regardless of whether the references are the same DL RS or different DL RSs.
[0221] The quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info and can take one of the following values:
[0222] - 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}
[0223] - 'QCL-TypeB': {Doppler shift, Doppler spread}
[0224] - 'QCL-TypeC': {Doppler shift, average delay}
[0225] - 'QCL-TypeD': {Spatial Rx parameter}
[0226] For example, if a target antenna port is a specific NZP CSI-RS, the NZP CSI-RS antenna port(s) may be indicated / configured to be QCLed with a specific TRS in terms of QCL-Type A and with a specific SSB in terms of QCL-Type D. A terminal that receives such indication / configuration can receive the NZP CSI-RS using the Doppler and delay values measured at the QCL-Type A TRS, and apply the receiving beam used for receiving the QCL-Type D SSB to receiving the NZP CSI-RS.
[0227] The UE can receive an activation command via MAC CE signaling used to map up to eight TCI states to codepoints in the DCI field 'Transmission Configuration Indication'.
[0228] Channel State Information (CSI) Transmission and Reception Method
[0229] In this disclosure, ' / ' may mean 'and', 'or', or 'and / or' depending on the context. In this disclosure, 'beam' may mean a (source / reference) RS for a 'spatial Tx / Rx filter' or a 'spatial relation', and may be interpreted as a QCL (source / reference) RS, a (DL / UL / joint) TCI state, or a spatial relation RS (in the case of an uplink) (corresponding ID).
[0230] Proposals are being discussed in 3GPP NR to support early CSI reporting for terminals transitioning from IDLE / INACTIVE mode to CONNECTED mode, as well as for secondary cell (Scell) activation and Scell dormancy wake-up. The relevant details in the related document are as follows.
[0231] 1) The following improvements are specified regarding the enhancement of downlink (DL) CSI acquisition targeting FR1 (frequency range 1):
[0232] a) When the UE switches from IDLE / INACTIVE mode to CONNECTED mode via message 4 (MSG4) of the 4th stage RACH (random access channel), SRS / CSI / CSI-RS early triggering is supported in the case of SCell activation and SCell switching out from CONNECTED mode via the existing signaling mechanism (based on existing SCell activation MAC CE and SCell dormancy wake DCI, respectively).
[0233] - Reusing existing designs, the scope is limited to an SRS for antenna switching, a non-periodic broadband CSI with a Rel-15 Type-I single-panel codebook (FDD (frequency division duplexing) targeting) and reporting without PMI (TDD (time division duplexing) targeting) via existing uplink control information (UCI), a CSI-RS for CSI, and a CSI-RS for tracking.
[0234] - In IDLE mode, UE capability and resource / reporting settings for early triggering are signaled via MSG3 and system information (SI), respectively.
[0235] As such, the UE performs a RACH procedure (i.e., a random access procedure) to change from IDLE / INACTIVE mode to CONNECTED mode, and a method to support CSI / CSI-RS triggering using MSG4 in the 4-stage RACH procedure is being discussed. In addition, a method to support rapid SRS / CSI / CSI-RS triggering during SCell activation or exiting dormancy is being discussed.
[0236] The present disclosure proposes a method for allocating / directing uplink resources to perform reporting of CSI that may occur during this process.
[0237] The aforementioned early CSI / CSI-RS triggering method corresponds to a method that supports CSI / CSI-RS triggering using MSG4 in the 4-step RACH procedure (i.e., random access procedure) when a UE performs a RACH procedure to change from IDLE / INACTIVE mode to CONNECTED mode. To support this early CSI / CSI-RS triggering, CSI / CSI-RS related settings for a UE in the IDLE state can be included in the System Information (SI) and signaled. Additionally, a UE in the INACTIVE state can use CSI / CSI-RS related settings that were configured before transitioning to the INACTIVE state (i.e., configured in the CONNECTED state). Furthermore, the aforementioned early CSI / CSI-RS triggering method also considers a method for rapidly triggering CSI measurement / reporting while activating inactive / dormant SCells.
[0238] The CSI reporting behavior resulting from the early CSI / CSI-RS triggering currently under discussion is primarily limited to aperiodic (AP) CSI reporting.
[0239] In this regard, AP CSI reporting under the NR standard can be performed based on AP CSI-RS, semi-persistent (SP) CSI-RS, or periodic (P) CSI-RS.
[0240] In a general situation, for a base station to trigger an AP CSI report to a terminal, it uses an uplink (UL) DCI (i.e., a DCI that schedules PUSCH) (e.g., DCI format 0_1, 0_2) to provide information related to PUSCH allocation and transmission (e.g., time / frequency domain allocation, DMRS port indication, UL precoder indication (e.g., SRI (SRS Resource Indicator) / TPMI (Transmitted Precoding Matrix Indicator)), UL power control, and UL TCI / spatial relationships (e.g., TCI status applied, which may include a UL timing advance (group) (TA(G)) indication, through the indicated SRS resource) to provide a CSI report (and associated AP CSI-RS resource (set)) through a CSI request field.
[0241] Issue: In the fast / early CSI acquisition scenarios described earlier, it may be difficult to support the general AP CSI reporting described previously. This is due to the following reasons:
[0242] - Because MSG4 (i.e., the UE Contention Resolution Identity MAC CE containing the UE Contention Resolution Identifier, or a message containing it) is delivered to the UE via PDSCH (i.e., downlink (DL) DCI (scheduling PDSCH) + PDSCH (carrying Msg4)), there are no UL resources to report CSI.
[0243] - Since the SCell-enabled MAC-CE is delivered to the terminal via PDSCH (i.e., DL DCI (scheduling PDSCH) + PDSCH (carrying the SCell-enabled MAC-CE)), there are no UL resources to report the CSI.
[0244] Additionally, in the description of the present disclosure, for convenience of explanation, a UE Contention Resolution Identity MAC CE (UE Contention Resolution Identity MAC CE) or a message containing a UE Contention Resolution Identity MAC CE is referred to as Msg4 for contention resolution in a four-step random access procedure, but the present disclosure is not limited thereto.
[0245] To address these issues, the present disclosure proposes the following method.
[0246] Example 1: A base station that triggers a CSI report via Msg4 or Scell activation (SA: Scell activation) MAC-CE may instruct a terminal to perform a CSI report using UL resource information through one or more of the following methods.
[0247] Method 1) Specify the UL resource information to report the CSI in Msg4 or SA MAC-CE
[0248] Method 2) Configure / define to report CSI along with HARQ-ACK through the HARQ-ACK PUCCH resource for the PDSCH carrying Msg4 or SA MAC-CE
[0249] Method 3) Allocate / instruct UL resources to report CSI in the scheduling DCI for the PDSCH passing Msg4 or SA MAC-CE
[0250] Method 4) Set / instruct UL resource information to report CSI (in advance via RRC, etc.) prior to Msg4 or SA MAC-CE transmission
[0251] Method 5) Assign / direct UL resources to report CSI as a separate DCI after Msg4 or SA MAC-CE
[0252] Here, the 'UL resource information' may include at least one of i) time / frequency domain allocation for physical layer UL channel resources (e.g., PUSCH / PUCCH) (e.g., slot / symbol location information, resource block (RB) location information), ii) resource format information (e.g., PUCCH format), iii) slot offset information, iv) DMRS / PTRS (phase tracking reference signal) information (e.g., port indicator), v) UL precoder information (e.g., SRI / TPMI), vi) UL transmit power control related information (e.g., transmit power control (TPC) command, path loss RS, power control parameters (e.g., P0, alpha)), vii) UL beam / TCI / spatial relationship information (e.g., TCI status applied through the indicated SRS resource), viii) UL timing advance (TA) information, and ix) modulation and coding scheme (MCS) information.
[0253] The above CSI can be encoded in various forms, such as MAC-CE / RRC, as well as uplink control information (UCI), through UL resources allocated / assigned via the methods proposed in this disclosure, and transmitted to a base station.
[0254] Method 1: Msg4 or SA (Scell activation) MAC-CE may include (some of) the UL resource information described above, and the UE may obtain resource information for reporting CSI through Msg4 or SA (Scell activation) MAC-CE. For example, PUSCH / PUCCH allocation information (some of) for CSI reporting may be directed to the Msg4 or SA MAC-CE. Some of the UL resource information described above may be set in advance via RRC messages (e.g., via system information for IDLE UEs, or via RRC signaling for INACTIVE / CONNECTED UEs), and only some (the remainder) of the information may be directed to the Msg4 or SA MAC-CE. For example, information on one or more PUCCH resources for CSI reporting is pre-configured in an RRC message, and trigger / activate / instruct the PUCCH resources and / or select / designate the PUCCH resource to be CSI reported among the multiple PUCCH resources via Msg4 or SA MAC-CE.
[0255] This method has the advantage of avoiding issues where reception errors occur for only some information, as CSI request information (i.e., the request / trigger for the CSI report) and UL resource allocation information for reporting the CSI exist within the same single message. However, compared to other methods, it requires managing physical layer resource allocation at a higher layer and necessitates modifying existing Msg4 or SA MAC-CE formats.
[0256] Method 2: A PUCCH resource for transmitting a HARQ-ACK for a PDSCH carrying a Msg4 or SA MAC-CE can be configured / regulated to report a CSI along with the HARQ-ACK. For example, a PUCCH resource designated through the PRI (PUCCH resource indicator) of a DL DCI (DCI that schedules PDSCH) can be configured / regulated to send a CSI along with the HARQ-ACK. Therefore, the PUCCH format and PUCCH resource size of the PUCCH for transmitting a HARQ-ACK for a PDSCH carrying a Msg4 or SA MAC-CE can be configured / instructed to transmit a CSI along with the HARQ-ACK, unlike the case where only the HARQ-ACK is transmitted.
[0257] Method 2 has the advantage of not requiring the definition of new messages / information, such as by reusing existing Msg4 or SA MAC-CE formats and not requiring a new DL DCI format. However, since the CSI payload size can be very large compared to the HARQ-ACK payload size, the PUCCH resources configured / specified for HARQ-ACK may not be suitable for transmitting the CSI together. Therefore, to overcome this, the following method(s) are additionally proposed.
[0258] Method 2-1: PUCCH resources (sets) can be set / defined separately for cases where CSI is triggered with HARQ-ACK and cases where it is not.
[0259] For example, the first PUCCH resource set and the second PUCCH resource set may be configured as RRC, and the mapping of the PRI code points of the DCI may be configured / defined to change depending on whether a CSI is triggered in the Msg4 / SA MAC-CE. For example, if a CSI is not triggered in the Msg4 / SA MAC-CE, the PRI code points may be mapped to the first PUCCH resource set, whereas if a CSI is triggered in the Msg4 / SA MAC-CE, the PRI code points may be mapped to the second PUCCH resource set. This allows the use of PUCCH resources that support a larger payload so that the HARQ-ACK and CSI can be sent together when the CSI is also triggered. And / or, PUCCH formats for cases where the CSI is triggered together with the HARQ-ACK and cases where it is not may also be configured / defined separately.
[0260] Method 2-2: Method 2 may be applied restrictively / conditionally depending on the CSI settings.
[0261] For example, Method 2 may be applied only to CSIs where the CSI payload size (e.g., a specific value) is not large. For example, Method 2 may be stipulated / defined to be applied only to CSIs where the CSI payload size is not large, such as CSIs that do not include PMI, Type 1 codebook CSIs, CSIs with a limited maximum number of CSI-RS ports and / or ranks, broadband CSI information, etc.
[0262] Method 3: can allocate / direct UL resources to report CSI in the scheduling DCI for the PDSCH that carries Msg4 or SA MAC-CE.
[0263] For example, UL grant information (i.e., uplink scheduling information) (or some of the UL grant information) can be directed in the scheduling DCI along with DL grant information (i.e., downlink scheduling information).
[0264] As another example, after pre-configuring PUCCH / PUSCH resources for CSI, the DCI may indicate whether to trigger / activate / assign the corresponding resources. Additionally, the DCI may indicate additional information regarding the corresponding UL resources (e.g., TCI, UL Power Control, etc.) along with whether to trigger / activate / assign the PUCCH / PUSCH resources for CSI. Here, the PUCCH resources for CSI may be resources configured / specified separately from the HARQ-ACK PUCCH resources. For example, the HARQ-ACK PUCCH resources may be indicated using existing PRI information, and the CSI PUCCH resources may be indicated using separately / newly defined / configured information. Alternatively, a mapping / connection relationship between the CSI PUCCH resource and the HARQ-ACK PUCCH resource can be established via a higher-level message (e.g., RRC), and the HARQ-ACK PUCCH resource and the CSI PUCCH resource mapped / connected to the HARQ-ACK PUCCH resource can be indicated together through the existing PRI field of the DCI.
[0265] In Method 3, the DCI indicating information about UL resources as well as DL resource information may be defined as a new DCI field / format. Alternatively, the existing DCI format may be used as is, but the UL resource information (part of it) may be indicated by utilizing specific code point combinations of some DCI fields in the existing DCI format or reserved code points of the existing DCI fields.
[0266] Method 3 has the advantage of being able to reuse existing Msg4 or SA MAC-CE formats, and potentially also reuse DCI formats. However, for the reuse of DCI formats, information regarding UL resources may be provided in a limited manner.
[0267] Method 4: Prior to the transmission of Msg4 or SA MAC-CE, UL resource information to report the CSI may be configured / instructed (in advance via RRC, etc.). For example, a PUCCH resource or a configured grant (CG) PUCCH resource to be used when transitioning from Scell Activation and / or IDLE / INACTIVE to CONNECTED may be configured in advance. Then, when CSI reporting is triggered by Msg4 or SA MAC-CE, the UE may report the CSI through the configured PUCCH / PUSCH resources. Here, the configuration information (i.e., including UL resource information to report the CSI) may be transmitted to the UE that was in the IDLE state via System Information (SI).
[0268] Here, ambiguity may arise regarding which slot a pre-configured PUCCH / PUSCH resource should be transmitted. To prevent this, the transmission time of the PUCCH / PUSCH for CSI reporting may be determined based on the reception time of Msg4 or SA MAC-CE (or the PDSCH in which the message is transmitted). For example, the PUCCH / PUSCH resource may be configured / defined to transmit the CSI at the first transmission period / occasion of a defined / configured interval (e.g., a specific number of slots (e.g., 4 or 5 slots) or a specific time) based on the slot of Msg4 or SA MAC-CE (or the PDSCH in which the message is transmitted). Alternatively, considering the possibility that a decoding error may occur for Msg4 or SA MAC-CE, the timing of the transmission of PUCCH / PUSCH for CSI reporting may be determined based on the time when the HARQ-ACK for Msg4 or SA MAC-CE (or the PDSCH in which the message is transmitted) is transmitted. For example, considering the possibility that a decoding error may occur for Msg4 or SA MAC-CE, the PUCCH / PUSCH resource may be configured / defined to transmit CSI at the first transmission period / occasion (occasion) after the slot in which the HARQ-ACK for Msg4 or SA MAC-CE (or the PDSCH in which the message is transmitted) is transmitted, or at a specified / configured interval (e.g., a specific number of slots (e.g., 4 or 5 slots) or a specific time).
[0269] As described above in Methods 1 / 2 / 3, Method 4 may be applied in conjunction with other method(s). For example, when Method 1 is applied in conjunction with Method 4, the transmission slot of an uplink transmission (i.e., a PUSCH scheduled for non-periodic CSI reporting) triggered by Msg4 or SA MAC-CE may be determined based on the time of transmitting the HARQ-ACK for the PDSCH carrying Msg4 or SA MAC-CE. For example, the transmission slot of an uplink transmission (i.e., a PUSCH scheduled for non-periodic CSI reporting) triggered by Msg4 or SA MAC-CE may be determined as a slot that is a specified / set interval (e.g., a specific number of slots (e.g., 4 or 5 slots) or a specific time) after the slot in which the HARQ-ACK for the PDSCH carrying Msg4 or SA MAC-CE is transmitted.
[0270] In addition, as an example of applying the aforementioned methods 1 / 2 / 3 and method 4 together, some of the UL resource information may be pre-set / instructed through method 4, and some may be set / instructed using methods 1 / 2 / 3. For example, regarding some information among the UL resource setting information (e.g., resource format information, frequency position information, symbol / slot position information, slot offset information, power-related information, MCS information, UL precoder / beam information, etc.) that is not pre-set through method 4, methods 1 / 2 / 3 may be used / applied (e.g., transmission timing information, slot offset information, (if multiple resources are set) resource index information).
[0271] Method 4 has the advantage of being able to reuse the existing DCI format and MAC-CE as is, but it may reduce the freedom to configure UL resources.
[0272] Method 5: A UL resource to report the CSI may be allocated / directed to a separate DCI after Msg4 or SA MAC-CE. For example, a UL DCI (i.e., an uplink scheduling DCI) may be transmitted separately after Msg4 or SA MAC-CE, and a PUSCH resource to transmit the CSI may be allocated in the UL DCI. Here, the CSI request message (i.e., the instruction to report the CSI) may be transmitted through Msg4 or SA MAC-CE or the said UL DCI. For example, the CSI request message (i.e., the instruction to report the CSI) is transmitted from Msg4 or SA MAC-CE, and the allocation of a PUSCH resource for transmitting the CSI report may be scheduled to a separate UL DCI.
[0273] Alternatively, a CSI report may be triggered using both messages / information. For example, only whether to report a CSI may be indicated via Msg4 or SA MAC-CE, and the CSI report setting ID (and PUSCH resource allocation information for sending the CSI report) may be indicated via UL DCI.
[0274] Method 5 has the advantage of not only reusing the existing DCI / MAC-CE format but also maximizing the reuse of the existing AP CSI reporting method over PUSCH. However, since UL DCI must be transmitted separately, the time delay for CSI reporting may be greater compared to other methods. Additionally, UEs that support fast / early CSI reporting may face the burden of calculating and storing related CSI measurements until the base station triggers the CSI report (e.g., memory / buffer capacity limitations). To minimize these disadvantages, the following method is additionally proposed to ensure that the transmission time of UL DCI or the terminal's PUSCH / CSI occurs within a certain timeframe relative to the transmission time of Msg4 or SA MAC-CE.
[0275] Method 5-1: When applying Method 5, the time of PUSCH / CSI transmission from the time of receiving Msg4 or SA MAC-CE may not exceed a certain amount of time. That is, the UE may not expect the time of PUSCH / CSI transmission to exceed a certain amount of time relative to the time of receiving Msg4 or SA MAC-CE.
[0276] Or / and, when applying Method 5, the time of UL UCI transmission from the time of receiving Msg4 or SA MAC-CE may not exceed a certain amount of time. That is, the UE may not expect the time of UL UCI transmission related to CSI reporting to exceed a certain amount of time relative to the time of receiving Msg4 or SA MAC-CE.
[0277] The above 'certain time' may be a value set by the base station, a value reported by the UE capability, or a value specified in the standard.
[0278] The above-described method can be extended and applied not only to CSI / CSI-RS triggers but also to cases where SRS triggers for early CSI are performed as separate DCIs. For example, the SRS triggering DCI time and / or SRS transmission time can be set / defined to be limited to within a certain time relative to the Msg4 or SA MAC-CE time.
[0279] When applying the methods proposed in the preceding methods 1 to 5, the form of information within the supported CSI (e.g., codebook type / parameter, PMI subsampling status / method), (max) number of CSI-RS ports, (max) rank, etc. may be defined / configured differently depending on the type (PUSCH or PUCCH), format, maximum payload size, etc. of the UL resource.
[0280] In addition, methods 1 to 5 proposed in this disclosure may be used together or in combination of two or more methods.
[0281] Furthermore, for the sake of convenience of explanation, the present disclosure describes an early CSI reporting operation targeting a UE changing from IDLE / INACTIVE mode / state to CONNECTED mode / state or a UE changing from Scell inactive / dormant state to active; however, the present disclosure is not limited thereto. That is, it can be applied to general / other-purpose RACH procedures (i.e., random access procedures) or MAC-CE-based CSI reporting procedures. In other words, the Msg4 or SA MAC-CE exemplified in the present disclosure can be extended and applied to other general MAC messages and / or RRC messages. For example, in addition to the case where CSI / CSI-RS is triggered in Msg4, the proposed methods of the present invention can also be applied when CSI is triggered through MsgB of a two-stage RACH procedure. Additionally, DL CSI can be estimated through SRS triggering, and in this case as well, the techniques of the present proposal can be applied / utilized.
[0282] FIG. 10 is a diagram illustrating the operation of a UE for a channel status information transmission and reception method according to one embodiment of the present disclosure.
[0283] FIG. 10 illustrates the operation of a UE based on the previously proposed method. The example in FIG. 10 is for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 10 may be omitted depending on the situation and / or configuration. Also, the UE in FIG. 10 is merely an example and may be implemented as the device illustrated in FIG. 3. For example, at least one processor (202) in FIG. 3 may control the transmission and reception of channels / signals / data / information, etc. using at least one transceiver (206), and may also control the storage of channels / signals / data / information, etc. to be transmitted or received in at least one memory (204).
[0284] Additionally, the operation of FIG. 10 may be processed by at least one processor (202) of FIG. 3. Additionally, the operation of FIG. 10 may be stored in memory (e.g., at least one memory (204) of FIG. 3) in the form of an instruction / program (e.g., instruction, executable code) for driving at least one processor (e.g., 202) of FIG. 3.
[0285] The UE receives a downlink transmission related to a random access procedure or Scell from the base station (S1001).
[0286] Here, a request may be made to report the CSI by the above downlink transmission.
[0287] For example, the downlink transmission may correspond to a message associated with the random access procedure (e.g., Msg1, Msg2, Msg3, or Msg4 for a 4-step random access procedure / MsgA or MsgB for a 2-step random access procedure). Here, message 4 (Msg 4) associated with the random access procedure may correspond to a message containing UE Contention Resolution Identity MAC CE or UE Contention Resolution Identity MAC CE.
[0288] As another example, the downlink transmission may include an Scell activation instruction or an instruction to switch out the dormancy of the Scell. For example, the downlink transmission may correspond to a SCell Activation / Deactivation MAC CE or an Enhanced SCell Activation / Deactivation MAC CE that includes a field indicating the activation / deactivation status of the Scell. Alternatively, the downlink transmission may correspond to a DCI that includes a SCell dormancy indication field.
[0289] The above UE receives CSI-RS from the base station (1002).
[0290] Based on the request to report CSI by the downlink transmission above, the UE transmits CSI to the base station (S1003).
[0291] Although not shown in FIG. 10, configuration information related to CSI reporting (e.g., CSI quatity, CSI codebook settings, etc.) and configuration information related to CSI-RS related to CSI reporting (e.g., a CSI-RS resource set without upper-level parameter repetition and without upper-level parameter trs-info) (e.g., an NZP CSI-RS resource set, a CSI-IM resource set, etc.) can be pre-configured.
[0292] For example, if a random access procedure is performed to switch a UE from an IDLE state to a CONNECTED state, the UE may have received configuration information related to CSI reporting and / or CSI-RS via system information while in the INACTIVE state. Additionally, if a random access procedure is performed to switch a UE from an INACTIVE state to a CONNECTED state, the UE may have received configuration information related to reference signals for CSI reporting and / or CSI-RS via RRC signaling while in the CONNECTED state prior to switching to the INACTIVE state. Furthermore, if the UE receives the downlink transmission containing an activation instruction for the Scell or a switching out instruction for the Scell, the UE may have received configuration information related to CSI reporting and / or CSI-RS via RRC signaling from the SpCell.
[0293] According to an embodiment of the present disclosure, an uplink resource for transmitting the CSI can be determined based on the downlink transmission.
[0294] For example, the downlink transmission corresponds to message 4 (Msg4) of the random access procedure, and message 4 may include information about an uplink resource for transmitting the CSI. As another example, the downlink transmission may include an activation instruction for the Scell or a switching out instruction for the Scell, and the downlink transmission may include information about an uplink resource for transmitting the CSI.
[0295] Here, the information regarding the uplink resources may include at least one of i) time / frequency domain allocation for physical layer UL channel resources (e.g., PUSCH / PUCCH) (e.g., slot / symbol location information, resource block (RB) location information), ii) resource format information (e.g., PUCCH format), iii) slot offset information, iv) DMRS / PTRS (phase tracking reference signal) information (e.g., port indicator), v) UL precoder information (e.g., SRI / TPMI), vi) UL transmit power control related information (e.g., transmit power control (TPC) command, path loss RS, power control parameters (e.g., P0, alpha)), vii) UL beam / TCI / spatial relationship information (e.g., TCI status applied through the indicated SRS resource), viii) UL timing advance (TA) information, and ix) modulation and coding scheme (MCS) information.
[0296] Additionally, the uplink resource for transmitting the CSI may be indicated by the downlink transmission among a plurality of uplink resource candidates available for transmitting the CSI.
[0297] Additionally, a slot for transmitting the CSI can be determined based on a slot for transmitting a HARQ-ACK for the PDSCH carrying the downlink transmission. For example, a slot for transmitting the CSI can be determined after a specific time interval from the slot for transmitting the HARQ-ACK.
[0298] Additionally, the CSI may be transmitted through a PUCCH resource that carries a HARQ-ACK (hybrid automatic repeat request-acknowledgement) for a PDSCH (physical downlink shared channel) carrying the downlink transmission. That is, the uplink resource (i.e., PUCCH resource) for transmitting the CSI may be indicated by the PRI field of the DCI that schedules the PDSCH. In this case, the PUCCH resource for transmitting the CSI may be selected from different sets of PUCCH resources depending on whether a report of the CSI is requested. That is, a separate set of PUCCH resources is configured depending on whether a report of the CSI is requested, and the set of PUCCH resources mapped to the code point of the PRI within the DCI may change depending on whether a report of the CSI is requested. Additionally, the CSI and the HARQ-ACK may be transmitted through the same PUCCH resource only if the CSI satisfies a predefined condition. That is, the CSI may be transmitted through a PUCCH resource carrying a HARQ-ACK only if the size of the CSI payload is less than or equal to a predefined size.
[0299] In addition, the downlink control information for scheduling the PDSCH (physical downlink shared channel) carrying the downlink transmission may include information regarding the uplink resource for transmitting the CSI. That is, while scheduling the PDSCH, the downlink control information may also schedule the uplink resource for CSI reporting together.
[0300] FIG. 11 is a diagram illustrating the operation of a base station for a channel status information transmission and reception method according to one embodiment of the present disclosure.
[0301] FIG. 11 illustrates the operation of a base station based on the previously proposed method. The example in FIG. 11 is for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 11 may be omitted depending on the situation and / or configuration. Also, the base station in FIG. 11 is merely an example and may be implemented as the device illustrated in FIG. 3. For example, at least one processor (202) in FIG. 3 may control at least one transceiver (206) to transmit and receive channels / signals / data / information, etc., and may also control at least one memory (204) to store the channels / signals / data / information, etc. to be transmitted or received.
[0302] Additionally, the operation of FIG. 11 may be processed by at least one processor (202) of FIG. 3. Additionally, the operation of FIG. 11 may be stored in memory (e.g., at least one memory (204) of FIG. 3) in the form of an instruction / program (e.g., instruction, executable code) for driving at least one processor (e.g., 202) of FIG. 3.
[0303] The base station transmits a random access procedure or a downlink transmission related to the Scell to the UE (S1101).
[0304] Here, a request may be made to report the CSI by the above downlink transmission.
[0305] For example, the downlink transmission may correspond to a message associated with the random access procedure (e.g., Msg1, Msg2, Msg3, or Msg4 for a 4-step random access procedure / MsgA or MsgB for a 2-step random access procedure). Here, message 4 (Msg 4) associated with the random access procedure may correspond to a message containing UE Contention Resolution Identity MAC CE or UE Contention Resolution Identity MAC CE.
[0306] As another example, the downlink transmission may include an Scell activation instruction or an instruction to switch out the dormancy of the Scell. For example, the downlink transmission may correspond to a SCell Activation / Deactivation MAC CE or an Enhanced SCell Activation / Deactivation MAC CE. Alternatively, the downlink transmission may correspond to a DCI containing a SCell dormancy indication field.
[0307] The base station transmits CSI-RS to the UE (1102).
[0308] Based on the request to report CSI by the downlink transmission above, the base station receives CSI from the UE (S1203).
[0309] Although not shown in FIG. 12, configuration information related to CSI reporting (e.g., CSI quatity, CSI codebook settings, etc.) and configuration information related to CSI-RS related to CSI reporting (e.g., a CSI-RS resource set without upper-level parameter repetition and without upper-level parameter trs-info) (e.g., an NZP CSI-RS resource set, a CSI-IM resource set, etc.) can be pre-configured.
[0310] For example, when a random access procedure is performed to switch a UE from an IDLE state to a CONNECTED state, the base station may have transmitted configuration information related to CSI reporting, CSI-RS, and / or reference signals for tracking to the UE in the INACTIVE state via system information. Additionally, when a random access procedure is performed to switch a UE from an INACTIVE state to a CONNECTED state, the base station may have transmitted configuration information related to CSI reporting, CSI-RS, and / or reference signals for tracking to the UE in the CONNECTED state via RRC signaling before the UE in the INACTIVE state switched to the INACTIVE state. Additionally, when transmitting the downlink transmission including an activation instruction for the Scell or a switching out instruction for the Scell to the UE, the base station may have transmitted configuration information related to CSI reporting, CSI-RS, and / or reference signals for tracking to the UE via RRC signaling in the SpCell.
[0311] According to an embodiment of the present disclosure, an uplink resource for transmitting the CSI can be determined based on the downlink transmission.
[0312] For example, the downlink transmission corresponds to message 4 (Msg4) of the random access procedure, and message 4 may include information about an uplink resource for transmitting the CSI. As another example, the downlink transmission may include an activation instruction for the Scell or a switching out instruction for the Scell, and the downlink transmission may include information about an uplink resource for transmitting the CSI.
[0313] Here, the information regarding the uplink resources may include at least one of i) time / frequency domain allocation for physical layer UL channel resources (e.g., PUSCH / PUCCH) (e.g., slot / symbol location information, resource block (RB) location information), ii) resource format information (e.g., PUCCH format), iii) slot offset information, iv) DMRS / PTRS (phase tracking reference signal) information (e.g., port indicator), v) UL precoder information (e.g., SRI / TPMI), vi) UL transmit power control related information (e.g., transmit power control (TPC) command, path loss RS, power control parameters (e.g., P0, alpha)), vii) UL beam / TCI / spatial relationship information (e.g., TCI status applied through the indicated SRS resource), viii) UL timing advance (TA) information, and ix) modulation and coding scheme (MCS) information.
[0314] Additionally, the uplink resource for transmitting the CSI may be indicated by the downlink transmission among a plurality of uplink resource candidates available for transmitting the CSI.
[0315] Additionally, a slot for transmitting the CSI can be determined based on a slot for transmitting a HARQ-ACK for the PDSCH carrying the downlink transmission. For example, a slot for transmitting the CSI can be determined after a specific time interval from the slot for transmitting the HARQ-ACK.
[0316] Additionally, the CSI may be transmitted through a PUCCH resource that carries a HARQ-ACK (hybrid automatic repeat request-acknowledgement) for a PDSCH (physical downlink shared channel) carrying the downlink transmission. That is, the uplink resource (i.e., PUCCH resource) for transmitting the CSI may be indicated by the PRI field of the DCI that schedules the PDSCH. In this case, the PUCCH resource for transmitting the CSI may be selected from different sets of PUCCH resources depending on whether a report of the CSI is requested. That is, a separate set of PUCCH resources is configured depending on whether a report of the CSI is requested, and the set of PUCCH resources mapped to the code point of the PRI within the DCI may change depending on whether a report of the CSI is requested. Additionally, the CSI and the HARQ-ACK may be transmitted through the same PUCCH resource only if the CSI satisfies a predefined condition. That is, the CSI may be transmitted through a PUCCH resource carrying a HARQ-ACK only if the size of the CSI payload is less than or equal to a predefined size.
[0317] In addition, the downlink control information for scheduling the PDSCH (physical downlink shared channel) carrying the downlink transmission may include information regarding the uplink resource for transmitting the CSI. That is, while scheduling the PDSCH, the downlink control information may also schedule the uplink resource for CSI reporting together.
[0318] 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.
[0319] 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.
[0320] 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.
[0321] 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.
[0322] 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. A step of receiving a downlink transmission related to a random access procedure or a secondary cell (Scell) from the base station by a user device (UE: user equipment); The step of receiving a channel state information-reference signal (CSI-RS) from the base station by the above UE; and The method includes the step of transmitting the CSI to the base station based on a request by the UE to report the CSI via the downlink transmission, and A method in which the uplink resource for transmitting the above CSI is determined based on the downlink transmission.
2. In Paragraph 1, The above downlink transmission corresponds to the message of the above random access procedure, and A method in which the above message includes information about an uplink resource for transmitting the above CSI.
3. In Paragraph 1, The above downlink transmission may include an activation instruction for the Scell or a switching out instruction for the Scell. A method in which the downlink transmission includes information about an uplink resource for transmitting the CSI.
4. In Paragraph 1, A method in which an uplink resource for transmitting the above CSI is indicated by the downlink transmission among a plurality of uplink resource candidates available for transmitting the above CSI.
5. In Paragraph 1, A method in which a slot for transmitting the CSI is determined based on a slot for transmitting a HARQ-ACK (hybrid automatic repeat request-acknowledgement) for a PDSCH (physical downlink shared channel) carrying the downlink transmission.
6. In Paragraph 5, A method in which a slot for transmitting the CSI is determined after a specific time interval from the slot transmitting the HARQ-ACK.
7. In Paragraph 1, A method in which the CSI is transmitted through a PUCCH resource carrying a HARQ-ACK (hybrid automatic repeat request-acknowledgement) for a PDSCH (physical downlink shared channel) carrying the downlink transmission.
8. In Paragraph 7, A method in which the PUCCH resource for transmitting the above CSI is selected from a different set of PUCCH resources depending on whether the reporting of the above CSI is requested.
9. In Paragraph 7, A method in which the CSI and the HARQ-ACK are transmitted through the same PUCCH resource only when the CSI satisfies a predefined condition.
10. In Paragraph 1, A method comprising downlink control information for scheduling a PDSCH (physical downlink shared channel) carrying the downlink transmission, the downlink control information including information about an uplink resource for transmitting the CSI.
11. In user equipment (UE), One or more transceivers for transmitting and receiving wireless signals; and It includes one or more processors that control the above one or more transmitting and receiving units, and The above one or more processors are: Receive a downlink transmission related to a random access procedure or a secondary cell (Scell) from the above base station, and Receive a channel state information-reference signal (CSI-RS) from the base station, and Based on the request to report the CSI by the above downlink transmission, the base station is configured to transmit the CSI, and A UE whose uplink resources for transmitting the above CSI are determined based on the downlink transmission.
12. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors, and user equipment (UE): Receive a downlink transmission related to a random access procedure or a secondary cell (Scell) from the above base station, and Receive a channel state information-reference signal (CSI-RS) from the base station, and Based on the request to report the CSI by the above downlink transmission, control the base station to transmit the CSI, and A computer-readable medium in which the uplink resource for transmitting the above CSI is determined based on the downlink transmission.
13. A processing device configured to control user equipment (UE), wherein the processing device: One or more processors; and It includes one or more computer memories that are operably connected to one or more processors and store instructions for performing operations based on execution by one or more processors, and The above operations are: A step of receiving a downlink transmission related to a random access procedure or a secondary cell (Scell) from the base station; A step of receiving a channel state information-reference signal (CSI-RS) from the base station; and Based on a request to report the CSI by the downlink transmission, the method includes the step of transmitting the CSI to the base station. A processing device for which the uplink resource for transmitting the above CSI is determined based on the downlink transmission.
14. A step of transmitting a downlink transmission associated with a random access procedure or a secondary cell (Scell) to a user device (UE) by a base station; The step of transmitting a channel state information-reference signal (CSI-RS) to the UE by the base station; and Based on a request to report the CSI by the downlink transmission, the base station receives the CSI from the UE, and A method in which the uplink resource for transmitting the above CSI is determined based on the downlink transmission.
15. One or more transceivers for transmitting and receiving wireless signals; and It includes one or more processors that control the above one or more transmitting and receiving units, and The above one or more processors are: A step of transmitting a downlink transmission associated with a random access procedure or a secondary cell (Scell) to a user device (UE: user equipment); A step of transmitting a channel state information-reference signal (CSI-RS) to the above UE; and Based on a request to report the CSI by the above downlink transmission, it is configured to receive the CSI from the UE, and A base station for transmitting the above CSI, the uplink resource determined based on the above downlink transmission.
