Method performed by terminal or network in wireless communication system, and device therefor

Abstract

A terminal according to an embodiment of the present disclosure may receive configuration information for control resource sets through higher layer signaling, receive a downlink signal including information on aggregation of at least two control resource sets among the control resource sets, and receive a downlink control channel on the basis of the aggregation of the at least two control resource sets.

Description

A method performed by a terminal or network in a wireless communication system and an apparatus for the same

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting or receiving uplink / downlink signals between terminals or networks in a wireless communication system.

[0002] The 5G mobile communication system is a successor technology to LTE (Long Term Evolution) and is a new clean-slate type of mobile communication system characterized by high performance, low latency, and high availability. In the case of 5G NR, 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 (millimeter wave) bands above 24 GHz. Based on the underlying technology of 5G mobile communication, 6G mobile communication systems are being developed.

[0003] In a 5G mobile communication system, the radio resource for PDCCH is defined as CORESET, and CORESET can be semi-statically set to 1, 2, or 3 symbol durations depending on the RRC settings. Through the RRC settings for the SS set, CORESET is linked with the SS set, and monitoring of PDCCH candidates within the CORESET is performed according to the SS monitoring period settings and AL settings of the linked SS set.

[0004] The technical problem to be solved by the present disclosure is to provide a method for efficiently performing a wireless signal transmission and reception process and an apparatus for doing so. According to one embodiment, an adaptation technique for a set of control resources may be provided for more adaptive and flexible control channel transmission and reception. For example, a method may be provided for dynamically adjusting time / frequency domain resources of a set of control resources set configured through upper-layer signaling through subsequent network signaling, e.g., DCI and / or MAC CE.

[0005] In addition to the technical challenges described above, other technical challenges can be inferred from the description below.

[0006] According to one aspect of the present disclosure, a method performed by a terminal may receive configuration information for sets of control resources through upper layer signaling; receive a downlink signal including information on the aggregation of at least two sets of control resources among the sets of control resources; and receive a downlink control channel based on the aggregation of at least two sets of control resources.

[0007] The above downlink signal may include at least one of DCI (downlink control information) or MAC (medium access control) CE (control element). Information regarding the combination of at least two sets of control resources may be included in at least one of the DCI or MAC CE.

[0008] The above at least two sets of control resources can be combined into one set of control resources.

[0009] The control channel can be received on the combined control resource set based on setting information for a search space set linked to a reference control resource set among the at least two control resource sets mentioned above.

[0010] Based on at least one of the number of symbols or symbol positions set in the reference control resource set, the remaining control resource sets among the at least two control resource sets can be aligned for combination.

[0011] Information regarding the combination of at least two sets of control resources mentioned above may include index information of the reference control resource set.

[0012] Based on the fact that the above at least two sets of control resources are monitored on the same time resource, the above at least two sets of control resources can be combined.

[0013] Information regarding the combination of at least two or more control resource sets may include active / inactive information for each control resource set.

[0014] The above downlink control channel can receive based on the combination of activated control resource sets.

[0015] The active / inactive information for each of the above control resource sets may be provided for each of one or more candidate control resource sets associated with the same search space set.

[0016] The above downlink signal is a first PDCCH (physical downlink control channel) for the first DCI among the two-step DCI (downlink control information), and the downlink control channel may be a second PDCCH for the second DCI among the two-step DCI.

[0017] The combination of at least two sets of control resources mentioned above can be performed on the USS (user-equipment specific search space) among the CSS (common search space) set and the USS set.

[0018] According to another aspect of the present disclosure, a computer-readable non-transitory recording medium may be provided that records a program for performing the method described above.

[0019] An apparatus according to another aspect of the present disclosure comprises: at least one processor; and at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, wherein the operations of the processor may include receiving configuration information for sets of control resources through upper layer signaling; receiving a downlink signal including information on the aggregation of at least two sets of control resources among the sets of control resources; and receiving a downlink control channel based on the aggregation of the at least two sets of control resources.

[0020] The above device may be a terminal including a transceiver or a processing device configured to control the terminal.

[0021] According to another aspect of the present disclosure, a method performed by a base station may include: transmitting configuration information for sets of control resources through upper layer signaling; transmitting a downlink signal comprising information on the aggregation of at least two sets of control resources among the sets of control resources; and transmitting a downlink control channel based on the aggregation of at least two sets of control resources.

[0022] A base station according to another aspect of the present disclosure comprises at least one processor; and at least one memory configured to store instructions that are executed by the at least one processor to cause the at least one processor to perform operations, wherein the operations of the processor may include transmitting configuration information for sets of control resources through upper layer signaling; transmitting a downlink signal including information on the aggregation of at least two sets of control resources among the sets of control resources; and transmitting a downlink control channel based on the aggregation of the at least two sets of control resources.

[0023] According to the present disclosure, signal transmission and reception can be performed efficiently in a wireless communication system. According to one embodiment, more reliable and efficient control channel transmission and reception can be performed through adaptation to a set of control resources. For example, since the time / frequency domain resources of a set of control resources set configured by upper-layer signaling can be dynamically adjusted through subsequent network signaling, e.g., DCI and / or MAC CE, resource usage efficiency can be improved and the system can respond quickly and flexibly to the wireless channel environment and various service requirements.

[0024] In addition to the technical effects described above, other technical effects can be inferred from the description below.

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

[0026] FIG. 2 illustrates an example of a communication system applicable to the present disclosure.

[0027] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.

[0028] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0029] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0030] FIG. 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0031] FIG. 7 shows an electromagnetic spectrum according to one embodiment of the present disclosure.

[0032] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies.

[0033] FIG. 9 illustrates a beam management procedure applicable to the present disclosure.

[0034] FIG. 10 shows an example of a sensing operation according to one embodiment of the present disclosure.

[0035] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification.

[0036] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification.

[0037] FIG. 13 illustrates the procedure for transmitting and receiving uplink / downlink signals between a base station and a terminal according to one embodiment.

[0038] FIG. 14 is a diagram illustrating the operation of a terminal and a base station regarding CORESET adaptation according to one embodiment.

[0039] FIG. 15 illustrates the flow of a method performed by a terminal according to one embodiment.

[0040] FIG. 16 illustrates the flow of a method performed by a base station according to one embodiment.

[0041] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0042] A slash ( / ) or a comma used in this specification 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."

[0043] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0044] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "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."

[0045] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (ABC)," "ABC" may be described as an example of "control information." For example, "control information" may include DEF as another example. In other words, "control information" in this specification is not limited to "ABC," and "ABC" may be described as an example of "control information." Also, when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0046] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor are they used to limit the order or importance of the components unless specifically limited. Accordingly, a first component in one embodiment of this specification 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.

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

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

[0049] In this specification, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / IAB node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. A terminal may be a fixed-location node or a non-fixed-location (or mobile) node.

[0050] In this specification, a Base Station (BS) is a device on the network side and may also be referred to as a second node / IAB node / x-NodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A Base Station may correspond to a physical node or a logical node. A Base Station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a Base Station may correspond to a serving node. A Base Station may be a node with a fixed location or a node with an indefinite location.

[0051] In this specification, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capability to the base station as higher layer parameters. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.

[0052] In this specification, information / state / parameters being "configured" or "pre-configured" may be interpreted as the information / state / parameters being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, information / state / parameters being "defined" or "pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.

[0053] The technology described in this specification 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.

[0054] The technology described in this specification 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.

[0055] <Symbols, Abbreviations, Terms>

[0056] - ACS: Adjacent Channel Selectivity

[0057] - ADC: Analog to Digital Converter

[0058] - ASCS: Adjacent Subcarrier selectivity

[0059] - ASK: Amplitude Shift Keying

[0060] - BB: Base Band

[0061] - BLER: Block Error Rate

[0062] - BPF: Band Pass Filter

[0063] - BWP: Bandwidth part

[0064] - CAP: Channel Access Procedure

[0065] - CFO: Center frequency offset

[0066] - CORESET: Control resource set

[0067] - CRC: Cyclic redundancy check

[0068] - CP-OFDMA: Cyclic Prefix-Orthogonal Frequency-Division Multiple Access

[0069] - CSI: Channel state information

[0070] - DCI: Downlink Control Information

[0071] - DCP: DCI with CRC scrambled by PS-RNTI

[0072] - DRX: Discontinuous Reception

[0073] - DFT-S-OFDMA: Discrete Fourier Transform-Spread-Orthogonal Frequency-Division Multiple Access

[0074] - eDRX: Extended DRX

[0075] - EPRE: Energy Per Resource Element

[0076] - FAR: False Alarm Rate

[0077] - FCS: Frame Check Sequence

[0078] - FSK: Frequency Shift Keying

[0079] - FLL: Frequency Locked Loop

[0080] - FFT: Fast Fourier Transform

[0081] - FR1: Frequency range 1

[0082] - FR2: Frequency range 2

[0083] - ICS: In-channel Selectivity

[0084] - IF: Intermediate Frequency

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

[0086] - LP-WUR: Low Power-Wake Up Receiver

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

[0088] - LO: Local Oscillator

[0089] - LNA: Low Noise Amplifier

[0090] - LPF: Low Pass Filter

[0091] - LR: LP-WUR

[0092] - MDR: Miss Detection Rate

[0093] - MC-ASK: Multiple Carrier-Amplitude Shift Keying

[0094] - MC-FSK: Multiple Carrier-Frequency Shift Keying

[0095] - MR: Main Radio

[0096] - NF: Noise Figure

[0097] - OOK: On-Off keying

[0098] - OFDM: Orthogonal Frequency Division Multiplexing

[0099] - PDCCH: Physical Downlink Control Channel

[0100] - PUCCH: Physical Uplink Control Channel

[0101] - PUSCH: Physical Uplink Shared Channel

[0102] - PDSCH: Physical Downlink Shared Channel

[0103] - PRACH: Physical Random-Access Channel

[0104] - PEI: Paging Early Indication

[0105] - PO: Paging Occasion

[0106] - PTW: Paging Time Window

[0107] - PLL: Phase Locked Loop

[0108] - PAPR: Peak to Average Power Ratio

[0109] - RRC: Radio Resource Control

[0110] - RRM: Radio Resource Management

[0111] - RLM: Radio Link Monitoring

[0112] - RS: Reference Signal

[0113] - RSRP: Reference Signal Received Power

[0114] - RSRQ: Reference Signal Received Quality

[0115] - RTC: Real Time Clock

[0116] - RF: Radio Frequency

[0117] - SCS: Sub-carrier spacing

[0118] - SSB: Synchronization Signal Block

[0119] - SSSG: Search Space Set Group

[0120] - SINR: Signal to Interference plus Noise Ratio

[0121] - SNR: Signal to Noise Ratio

[0122] - SC: Subcarrier

[0123] - TBS: Transport Block Size

[0124] - TDRA: Time Domain Resource Allocation

[0125] - Ucell: Unlicensed cell

[0126] - UE: User Equipment

[0127] - XR: Extended reality

[0128] - TAG: Timing advance group

[0129] - AmIoT: Ambient Internet of Things

[0130] - CW: Carrier Wave

[0131] - BSC: Backscattering

[0132] - BSS: Backscattered signal

[0133] - SIC: Self-Interference Cancellation

[0134] - RFID: Radio Frequency Identifier

[0135] - IN: Intermediate Node

[0136] - SLIV: Starting and Length Indicator Value (An indicator value for the starting symbol index and number of symbols within a slot of a PDSCH and / or PUSCH; it can be set as a component of an entry constituting the TDRA field within the PDCCH scheduling the said PDSCH and / or PUSCH.)

[0137] - BWP: Bandwidth Part (It can consist of consecutive resource blocks (RBs) on the frequency axis and correspond to a single numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). Additionally, multiple BWPs can be configured on a single carrier (the number of BWPs per carrier may also be limited), but the number of activated BWPs per carrier may be limited to a fraction of them (e.g., 1).)

[0138] - CORESET: Control Resource Set (Refers to the time and frequency resource range where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0139] - REG: Resource element group

[0140] - SFI: Slot Format Indicator (An indicator that indicates the symbol level DL / UL direction within a specific slot(s), transmitted via the group common PDCCH.)

[0141] - COT: Channel occupancy time

[0142] - SPS: Semi-persistent scheduling

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

[0144] 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 IAB nodes, relays, and RF repeaters, as exemplified in Fig. 1, may be applied, and 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, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for a terrestrial network to provide. In addition to these examples, various intermediate points can be introduced to improve network topology.

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

[0146] 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 can 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. In other words, an IAB node may correspond to a base station in its relative relationship with user-side nodes and to a terminal in its relative relationship with network-side nodes.

[0147] In some examples of this specification, 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 this specification, 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. However, in most cases where there is no additional description of the operation of three or more entities, the communication entities in this specification 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.

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

[0149] In this specification, 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 (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.

[0150] FIG. 2 illustrates a communication system applicable to the present disclosure.

[0151] The communication system (100) of FIG. 2 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 smartpad, a wearable device (e.g., a smartwatch, 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).

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

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

[0154] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.

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

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

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

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

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

[0160] 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) may convert the processed user data, control information, wireless signals / channels, etc., from baseband signals to RF band signals using at least one processor (202).To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

[0163] 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., audio input / output port, 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.

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

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

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

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

[0168] The structure of the wireless device exemplified 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 exemplified 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. However, if the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) exemplified in FIG. 3 is used for front haul and / or back haul communication, and the wired transceiver may not be included.

[0169] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0170] The second node of FIG. 4 supports dynamic spectrum sharing (DSS) and can provide connectivity to both nodes where 6G technology is implemented and nodes where pre-6G wireless communication technology (e.g., 5G, 4G) is implemented. That is, the first node of FIG. 4 may have 6G technology implemented or pre-6G wireless communication technology (e.g., 5G, 4G) implemented. Additionally, the first node and / or the second node may support full duplex mode as well as non-overlapping full duplex mode.

[0171] In FIG. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and the operation of the terminal (110) and the base station (120) transmitting and / or receiving data, and the operation performed prior to this, are illustrated. However, the operation of FIG. 4 is not limited to the operation between the terminal and the base station, but can be interpreted as the operation between the first node and the second node. Additionally, FIG. 4 illustrates the operation of direct transmission and reception of wireless signals between the terminal (110) and the base station (120), but there may be one or more intermediate points between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0172] Referring to FIG. 4, the terminal (110) and the base station (120) can perform synchronization (401). For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect a synchronization signal for at least one base station connection transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals classified according to structure or use (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this, the terminal (110) can identify the boundary of the unit (e.g., frame, subframe, slot and / or symbol) constituting the wireless signal transmission of the base station (120) and obtain information about the base station (120) (e.g., cell identifier).

[0173] The terminal (110) can obtain system information transmitted from the base station (120) (403). 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., channel used, whether it is provided on-demand), etc., and can be classified, for example, into first system information (e.g., MIB (master information block), primary system information), second system information (e.g., SIB (system information block), secondary system information), etc. If necessary, the terminal (110) may transmit a signal requesting system information prior to receiving the system information. However, the request and provision of system information may be performed after the random access procedure described later.

[0174] A terminal (110) and a base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message for a random access procedure (e.g., random access preamble, RAR (random access response) message, etc.) based on information related to the channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., RAR message, MSG2), transmit a third message (e.g., MSG3) containing information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, the first message and the third message can be transmitted and received as a single message, or the second message and the fourth message can be transmitted and received as a single message.

[0175] The terminal (110) and the base station (120) can perform signaling of control information (407). Here, the control information can 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) can perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0176] The terminal (110) and the base station (120) can transmit and / or receive data (409). In other words, 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. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0177] 6G System Core Technology

[0178] The 6G (wireless communication) system aims for (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 the 6G system can be four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0179] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, FSO backhaul network, massive 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.

[0180] artificial intelligence

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

[0182] The following describes a functional framework for AI / ML operations.

[0183] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.

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

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

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

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

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

[0189] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0190] In particular, 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.

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

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

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

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

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

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

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

[0198] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

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

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

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

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

[0203] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.

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

[0205] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.

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

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

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

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

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

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

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

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

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

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

[0216] FIG. 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0217] The operations described below may be explained / interpreted based on an AI / ML model as shown in FIG. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for an AI / ML model). Furthermore, unless specifically limited, the AI / ML model may correspond to a one-side model in which inference is performed entirely by a single node or a two-side model in which joint inference is performed by multiple nodes.

[0218] First signaling (601): In the following description, the signaling (e.g., information / data / channel / signal, etc.) or 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 the first signaling (601) used to perform an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to training data for training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5, or to inference data used for inference of the AI / ML model, or to feedback for the AI / ML model. If, in this specification, signaling between nodes is not required prior to an operation based on an AI / ML model, the first signaling (601) may be omitted. In this specification, if a one-side model is used, the unidirectional / bidirectional signaling (set) in this specification may correspond to the signaling of the first signaling (601). Additionally, when a two-side model is used in the present specification, unidirectional / bidirectional signaling in the present specification may correspond to the first signaling (601), and repetitive signaling operation may also correspond to the first signaling (601).

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

[0220] AI / ML model-based operation (602): In the following description, an operation (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or a common operation (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., terminal, network, etc.) may correspond to an AI / ML model-based operation (602) based on one or more functions in the functional framework of the AI / ML model, even without separate mention. For example, it may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5 or to the inference of the AI / ML model. When a one-side model is used, an operation performed by a single node in this specification may correspond to an AI / ML model-based operation (602), and when a two-side model is used, a common operation performed by multiple nodes in this specification may correspond to an AI / ML model-based operation (602).

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

[0222] Second signaling (603): In the following description, 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 second signaling (603) or a set of signaling generated as a result of an operation based on an AI / ML model, even without separate mention. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 5. If signaling between nodes is not required as a result of an operation based on an AI / ML model in this specification, the second signaling (603) may be omitted. If a one-side model is used in this specification, the unidirectional / bidirectional signaling (set) in this specification may correspond to the second signaling (603). Additionally, when a two-side model is used in this specification, unidirectional / bidirectional signaling in this specification may correspond to the second signaling (603), and repetitive signaling operation may also correspond to the second signaling (603).

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

[0224] THz communication

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

[0226] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure. Key characteristics of THz communication include (i) a 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 techniques that can overcome range limitations.

[0227] Transmitting system information (i.e., information related to the attributes, characteristics, and / or capabilities of the BS required to use the service, etc.) (e.g., MIB, SIB, etc.) in the THz frequency band 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 narrow. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure as shown in FIG. 8 below may be used.

[0228] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies. Although this example is written with THz conditions in mind, it is also applicable to 6G communication environments where THz is not applied. Furthermore, the procedure exemplified in FIG. 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below may be performed based on the system information obtained by the procedure exemplified in FIG. 8.

[0229] Referring to FIG. 8, the base station can transmit system information of cell #1 through cell #2 (801). That is, the base station provides at least two cells, cell #1 uses the 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 information / state / parameter / setting generated at the higher layer and the physical layer, respectively. For example, at least one information / state / parameter / setting generated at the higher layer may include at least one of SFN, control information setting for SIB1 (e.g., PDCCH configuration for SIB1, etc.), information related to cell selection / entry (e.g., cell barring, cell re-selection, etc.), and subcarrier spacing, and at least one information / state / parameter / setting generated at the physical layer may include at least one of SFN, half frame indicator, and SSB index. However, this is merely an example, and system information may include information, status, parameters, and settings related to Cell #1 / Cell #2 generated at various types of physical layers / upper layers. To this end, as an example, Cell #1 and Cell #2 may have a secondary cell and primary cell relationship.

[0230] The UE can obtain synchronization for cell #1 (803). Synchronization can be obtained by detecting a synchronization signal. Generally, synchronization is obtained prior to receiving system information, but since the system information for cell #1 is received in cell #2, synchronization for cell #1 can be obtained after receiving system information. For example, the UE can obtain synchronization based on system information. However, unlike FIG. 8, synchronization may be obtained before step 801 according to other examples.

[0231] The UE can transmit a signal to connect to Cell #1 (805). For example, the signal may include information for connecting to Cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) can be identified through system information. Subsequently, the UE and the base station can perform a connection procedure to Cell #1 and perform communication (807). In this process, operations according to various embodiments described below may be performed.

[0232] The procedure described with reference to FIG. 8 may be performed when the UE (801) first connects to cell #1 of the base station. Alternatively, a similar procedure may be performed when the UE (801) handovers to cell #1 of the base station. However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station rather than cell #2 of the base station.

[0233] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations must use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control along with beamforming, and the number of beams used becomes very large. Therefore, it takes a very long time to align the transmit and receive beams between the base station and the terminal. In addition, if the beam alignment between the base station and the terminal is misaligned due to the movement of the terminal, time is frequently required to realign the beams, which may result in an unstable link. Accordingly, a beam management procedure as shown in Fig. 9 below may be used.

[0234] FIG. 9 illustrates a beam management procedure applicable to the present disclosure. FIG. 9 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment and is applicable to a 6G communication environment. Additionally, the procedure exemplified in FIG. 9 may be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (configuration) information', 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', or / and a term having an equivalent technical meaning capable of distinguishing a beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource-related information (e.g., CORESET (control resource set)-related information, etc.).

[0235] Referring to FIG. 9, the base station can configure resources for beam management (901). 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 spatially separated from existing downlink signals / channels 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 for transmitting existing downlink signals / channels (e.g., synchronization signals (e.g., SSB, etc.), data channels (e.g., PDSCH, 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. That is, a signal transmitted based on a dedicated port defined / configured for beam search may be included in the technical concept according to the present embodiment.

[0236] The base station can transmit measurement signals using multiple transmission beams (903). 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 required for 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, and a true time delay (TTD).

[0237] The UE can transmit a feedback signal to the base station (905). The feedback signal indicates at least one beam selected by the UE. The UE can select at least one preferred beam based on the received measurement signals. The UE and the base station can perform communication (907). At this time, the UE and the base station can perform communication using the previously selected beam. If channel reciprocity is established, the UE's transmission beam can also be determined through operations 903 and 905, so the UE's transmission can also be performed using the beam selected in operation 905. If channel reciprocity is not established, a procedure including the transmission of the UE's measurement signals and the transmission of the base station's feedback signal may be performed first to determine the UE's transmission beam. In operation 907, operations according to various embodiments described below may be performed.

[0238] Integrated Sensing and Communication (ISAC)

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

[0240] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure. Specifically, FIG. 10(a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same position (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

[0241] For example, in a wireless communication system based on a 6G network of the present specification, referring to FIG. 10(a), the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 10(b), the sensing transmitter and the sensing receiver may be configured to be included in different base stations, in different terminals, or in a terminal and a base station, respectively.

[0242] In this regard, based on whether the sensing transmitter and the sensing receiver are each included in a base station or a terminal, the following six types of sensing modes can be defined.

[0243] - Mode 1: A mode in which the sensing transmitter and sensing receiver are included in a single base station (e.g., base station-based sensing mode in monostatic mode)

[0244] - Second mode: A mode in which the sensing transmitter is included in the first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode)

[0245] - 3rd Mode: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode)

[0246] - 4th Mode: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode)

[0247] - 5th Mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode)

[0248] - 6th mode: A mode in which the sensing transmitter is included in the first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode)

[0249] In a wireless communication system based on a 6G network of the present specification, one or more of the six types of sensing modes described above may be utilized independently or in combination.

[0250] In relation to the sensing operation in FIG. 10, the sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on a 6G network of the present specification. The sensing receiver may receive a signal that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on a 6G network of the present specification, or may be provided / disclosed to a trusted third party.

[0251] Additionally, the sensing operation in FIG. 10 is described using a representative example of operation in a wireless communication system based on a 6G network, but it can be extended and applied to cases where terminals / base stations / signals based on previous generations (e.g., 4G, 5G, etc.) networks are utilized.

[0252] Additionally, with respect to the wireless sensing described in this specification, in a wireless communication system based on a 6G network of this specification, time / frequency resources for sensing operations and time / frequency resources for general communication (e.g., UL / DL / sidelink-based communication, etc.) may be scheduled / configured separately.

[0253] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0254] Referring to FIG. 11, the time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 10) can be set / assigned separately from the time / frequency resources (hereinafter, communication resources) for general communication.

[0255] For example, as illustrated in FIG. 11, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally or alternatively, unlike that illustrated in FIG. 10, sensing resources may be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).

[0256] Additionally or alternatively, in relation to the setup / allocation / scheduling of resources for general communication described herein, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when setting / allocating resources for general communication according to the embodiments of the present disclosure, said resources may be set / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to the embodiments of the present disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources are set / allocated / scheduled to overlap according to the embodiments of the present disclosure, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in the embodiments of this specification, resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) may be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.

[0257] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described herein. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.

[0258] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be optimized and configured differently. For example, when various sensing scenarios are classified, they can be divided into channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of this specification may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.

[0259] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0260] For example, in a wireless communication system based on a 6G network of the present specification, in the case of a sensing operation in which a terminal participates, the base station may need to verify (1205) the terminal's capability for the sensing operation. In this regard, the terminal may be configured to report capability information to the base station regarding whether it supports the sensing operation. Additionally, or alternatively, if the terminal is defined in advance in the specification as supporting the sensing operation, the procedure may be omitted. Furthermore, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to the entity setting / controlling its sensing operation (e.g., a network entity at the upper level / layer of the base station).

[0261] For example, a base station may perform signaling with a terminal to exchange configuration information related to a sensing operation. For example, the base station may set / instruct the terminal information regarding the mode of the sensing operation (e.g., based on the six types of modes mentioned above), the subject of the sensing operation (e.g., a sensing transmitter, a sensing receiver), the resource of the sensing operation (e.g., a sensing resource as shown in FIG. 11), the target of utilization of the sensing result (e.g., a type of wireless sensing service based on a 6G network, a trusted third party), and channel modeling for sensing (e.g., a channel between the base station / terminal and an object / environment) (1210). For example, the base station may receive such information from a network entity at the upper level / layer of the base station.

[0262] For example, a base station and / or terminal may perform a sensing operation on information set / instructed (1215). For example, the base station and / or terminal may perform procedures such as transmitting a sensing signal as in FIG. 9 described above, receiving scattered / reflected signals, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as a role of a sensing transmitter and / or sensing receiver. For example, in the operation of the base station / terminal described in this specification, the sensing result provided through the sensing operation may be utilized.

[0263] FIG. 13 illustrates an example of a procedure between a base station and a terminal to perform FR1, FR2, or FR2-2 transmission and reception of one or more physical channels / signals to which the method proposed in this specification may be applied.

[0264] FIG. 13 (a) is an example of the transmission and reception of UL data / channel. A base station can transmit configuration information related to UL data / channel to a terminal through upper layer signaling (1301). The terminal can receive information from the base station for DCI for UL data scheduling and / or for UL channel transmission (1302). Based on this, the terminal can transmit UL data / channel to the base station (1303).

[0265] FIG. 13 (b) is an example of the transmission and reception of DL data / channel. A base station may transmit configuration information related to the DL data / channel to a terminal via upper layer signaling (1304). The terminal may receive DCI for DL ​​data scheduling and / or information for DL ​​channel transmission from the base station (1305). Based on this, the terminal may receive the DL data / channel from the base station (1306). If a HARQ-ACK is set for the reception of the DL data / channel, the terminal may transmit the HARQ-ACK to the base station (1307).

[0266] NR DL control channel and configuration

[0267] (1) PDCCH

[0268] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation for the DL-SCH (downlink shared channel), resource allocation information for the UL-SCH (uplink shared channel), paging information for the PCH (paging channel), system information on the DL-SCH, resource allocation information for higher-layer control messages such as random connection acknowledgments transmitted over the PDSCH, transmission power control commands, and the activation / deactivation of the CS (Configured Scheduling). The DCI includes a Cyclic Redundancy Check (CRC), which is masked or scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with the terminal identifier (e.g., Cell-RNTI, C-RNTI). If PDCCH is for paging, the CRC is masked by P-RNTI (Paging-RNTI). If PDCCH is for system information (e.g., System Information Block, SIB), the CRC is masked by SI-RNTI (System Information RNTI). If PDCCH is for a random access response, the CRC is masked by RA-RNTI (Random Access-RNTI).

[0269] (2) CORESET configuration

[0270] The base station may transmit a CORESET (Control Resource Set) configuration to the terminal (S502). A CORESET is defined as a set of REGs (Resource Element Groups) having a given neuromonology (e.g., SCS, CP length, etc.). A REG is defined by one OFDM symbol and one (P)RB. Multiple CORESETs for a single terminal may overlap in the time / frequency domain. A CORESET may be configured via system information (e.g., Master Information Block, MIB) or terminal-specific (UE-specific) upper-layer (e.g., Radio Resource Control, RRC, layer) signaling. Terminal-specific RRC signaling may include, for example, RRC setup messages, BWP configuration information, etc. Specifically, the CORESET configuration may include the following information / fields.

[0271] - controlResourceSetId: Represents the ID of the CORESET.

[0272] - frequencyDomainResources: Represents the frequency domain resources of the CORESET. It is indicated by a bitmap, where each bit corresponds to an RB group (= 6 (consecutive) RBs). For example, the MSB (Most Significant Bit) of the bitmap corresponds to the first RB group within the BWP. The RB group corresponding to the bit with a value of 1 is allocated as the frequency domain resource of the CORESET.

[0273] - duration: Represents the time-domain resources of the CORESET. It indicates the number of consecutive OFDM symbols that make up the CORESET. The duration has a value of 1 to 3.

[0274] - cce-REG-MappingType: Indicates the mapping type between CCE (Control Channel Element) and REG. Interleaved and non-interleaved types are supported.

[0275] - interleaverSize: Indicates the interleaver size.

[0276] - pdcch-DMRS-ScramblingID: Represents the value used for initializing the PDCCH DMRS. If pdcch-DMRS-ScramblingID is not included, the physical cell ID of the serving cell is used.

[0277] - precoderGranularity: Represents the precoder granularity in the frequency domain.

[0278] - reg-BundleSize: Represents the REG bundle size.

[0279] - tci-PresentInDCI: Indicates whether the TCI (Transmission Configuration Index) field is included in the DL-related DCI.

[0280] - tci-StatesPDCCH-ToAddList: Represents a subset of TCI states defined in the PDCCH configuration. TCI states are used to provide the Quasi-Co-Location (QCL) relationship between the DL RS(s) within the RS set (TCI-states) and the PDCCH DMRS ports.

[0281] (3) Search Space Set

[0282] Additionally, the base station may transmit a PDCCH SS (Search Space) Set configuration to the terminal (S504). The PDCCH SS set contains PDCCH candidates. A PDCCH candidate represents a CCE(s) that the terminal monitors for PDCCH reception / detection. Here, monitoring includes blind decoding (BD) the PDCCH candidates. A single PDCCH (candidate) consists of 1, 2, 4, 8, or 16 CCEs depending on the AL (Aggregation Level). A single CCE consists of 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with one COREST configuration. One SS is defined based on one SS configuration, and the SS configuration may include the following information / fields.

[0283] - searchSpaceId: Represents the ID of the SS.

[0284] - controlResourceSetId: Represents the CORESET associated with SS.

[0285] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period interval (in slots) and the PDCCH monitoring interval offset (in slots).

[0286] - monitoringSymbolsWithinSlot: Represents the first OFDM symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is configured. It is indicated by a bitmap, where each bit corresponds to each OFDM symbol within the slot. The MSB of the bitmap corresponds to the first OFDM symbol within the slot. The OFDM symbol(s) corresponding to bit(s) with a bit value of 1 correspond to the first symbol(s) of the CORESET within the slot.

[0287] - nrofCandidates: AL={1, 2, 4, 8, 16} represents the number of star PDCCH candidates (one of the values ​​0, 1, 2, 3, 4, 5, 6, 8).

[0288] - searchSpaceType: Indicates CSS (Common Search Space) or USS (UE-specific search space), and the DCI format used in the corresponding SS type.

[0289] Subsequently, the base station generates and transmits the PDCCH to the terminal (S506), and the terminal can monitor PDCCH candidates in one or more SSs for PDCCH reception / detection (S508). An occasion (e.g., time / frequency resources) for monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities may be configured within a slot.

[0290] Table 1 illustrates the characteristics of each SS type.

[0291] TypeSearch SpaceRNTIUse CaseType0-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType0A-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType1-PDCCHCommonRA-RNTI or TC-RNTI on a primary cellMsg2, Msg4 decoding in RACHType2-PDCCHCommonP-RNTI on a primary cellPaging DecodingType3-PDCCHCommonINT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI(s)UE SpecificC-RNTI, or MCS-C-RNTI, or CS-RNTI(s)User specific PDSCH decoding

[0292] (4) DMRS for PDCCH

[0293] In this specification, DMRS for PDCCH may be referred to as PDCCH DMRS or simply DMRS.

[0294] PDCCH DMRS is based on a pseudo-random sequence and can be initialized based on PCI or pdcch-DMRS-ScramblingId (provided via ControlResourceSet). However, DMRS for PDCCH in Type-0 CSS (e.g., SIB1 scheduling) is always initialized with PCI.

[0295] The PDCCH DMRS is transmitted using Port 2000, which is the same antenna port as the PDCCH. The UE uses the PDCCH DMRS (demodulation reference signal) to estimate / measure the radio channel characteristics (e.g., Doppler shift / spread, delay characteristics, spatial reception parameters, etc.) over which the PDCCH is transmitted and received, and based on this, demodulates the PDCCH to decode the DCI. Basically, the UE assumes that the PDCCH DMRS is in a QCL relationship with the SS / PBCH block (e.g., in terms of Doppler / delay / spatial parameters). For example, the PDCCH and its DMRS can be received under the assumption that they are beamformed in the same way as the SS / PBCH block.

[0296] DMRS occupies 25% of the total frequency resources allocated for PDCCH. That is, the frequency axis density of DMRS is fixed at 1 / 4 (e.g., a 4-subcarrier spacing pattern such as subcarrier indices 1, 5, 9, 13, 17, ...). Regardless of the number of OFDM symbols in CORESET (e.g., 1 / 2 / 3), DMRS is mapped to the frequency axis according to the above frequency axis pattern for every symbol included in CORESET.

[0297] CORESET configuration / adaptation for PDCCH

[0298] To improve resource utilization efficiency for PDCCH transmission and base station scheduling efficiency, a method for more flexibly adapting the resources used for PDCCH transmission may be considered. Unlike the method in which the CORESET (control resource set) is fixed semi-statically as in conventional NR, at least some parameters of the CORESET, such as size (e.g., CORESET duration, CORESET RBs), structure, resources, intervals, periods, and offsets on the time / frequency axis, may be adjusted differently from the values ​​originally set by RRC for at least a certain period of time (e.g., a time resource interval such as a few slots or milliseconds) (and / or a certain number of monitoring cycles) through specific instruction(s) (e.g., DCI and / or MAC CE). In this disclosure, this is referred to as CORESET adaptation or CORESET adjustment. Upon receiving a CORESET adaptation instruction, the terminal may perform PDCCH monitoring based on values ​​different from the previously set CORESET for at least a certain period of time. As such, the PDCCH candidates to which CORESET adaptation is applied may be all PDCCH candidates, or some PDCCH candidates related to a specific RNTI and / or specific DCI format, and instructions / settings for this may be provided.

[0299] If the terminal fails to receive these CORESET adaptation instructions, the resources on the time / frequency axis for PDCCH transmission between the base station and the terminal will not match, which can significantly affect the terminal's PDCCH reception performance; therefore, it may be necessary to ensure that the terminal does not miss or incorrectly receive the CORESET adaptation instructions.

[0300] For example, as one method to ensure that the terminal fully receives the CORESET adaptation instruction, it can be assumed that the instruction is transmitted repeatedly for a certain period of time, and that the CORESET adaptation is actually applied after a certain amount of time has passed since the initial transmission (after a certain amount of repeated transmission has been performed).

[0301] Alternatively, if the terminal fails to receive the CORESET adaptation instruction and thus fails to properly receive the PDCCH transmitted through the resources of the changed time / frequency axis, or if there is a problem with receiving the subsequent scheduled PDSCH or transmitting the PUSCH, the previously instructed CORESET adaptation may be canceled and a fallback operation of the terminal may be expected to be performed so that PDCCH monitoring based on the original higher layer parameter settings is performed. To this end, the base station may make a decision indirectly through ACK / NACK feedback for the scheduled PDSCH (or transmission of the scheduled PUSCH) or consider (direct) ACK / NACK for the CORESET adaptation instruction.

[0302] This CORESET adaptation operation can be effective in a two-stage control structure. A two-stage control structure refers to a structure where the first control information transmits instructions for the second control information, and the second control information is received based on these instructions. By transmitting instructions (including adaptation) for a CORESET capable of receiving the second control information (typically DCI) from the first control information, the terminal can receive the second control information more efficiently.

[0303] Specifically, in the present disclosure, at least one of the following CORESET adaptations may be used.

[0304] - A CORESET is connected to the SS set configuration. Depending on the SS set configuration, the conditions for CORESETs that can be combined can be determined, and the PDCCH monitoring operation after the combination of CORESETs can be considered.

[0305] - Multiple candidate resources may be configured for CORESET adaptation, and adaptation to the resources / configuration of the CORESET may be performed by specifying at least some of the multiple candidate resources through a CORESET adaptation instruction. The candidate resources may be candidate time resources or candidate frequency resources, and / or candidate time-frequency (combination) resources. For example, candidate frequency resources may be signaled through candidate FDRAs (frequency domain resource allocations). Each candidate FDRA information may be configured as a bitmap, and each bit in the bitmap may correspond to N-RB, for example, N=6, but is not limited thereto. For example, multiple candidate FDRAs (e.g., multiple 6-RB bitmaps) may be provided in a single CORESET configuration, and a single FDRA (e.g., bitmap) may be specified through a specific dynamic signal. All candidate FDRAs (e.g., bitmaps) may have the same symbol duration, or the symbol duration may be configured individually for each candidate FDRA (e.g., bitmap).

[0306] A specific example of this form may be a sub-CORESET (candidate CORESET) structure. Candidate FDRAs (e.g., bitmaps) may be in the form of sub-CORESETs composed of mutually exclusive frequency resources, and a specific dynamic signal may indicate which sub-CORESET(s) will be activated.

[0307] As a specific example, a CORESET can be constructed by introducing the concept of a candidate CORESET. Multiple candidate CORESETs capable of forming a single CORESET can be configured, and instructions can be given to construct a complete CORESET based on them. In this case, a CORESET adaptation effect can be expected, in which resources on the time and frequency axes of the complete CORESET are modified through the number of candidate CORESETs and their combinations. This structure can be considered for use in a two-stage control structure.

[0308] When a terminal receives a CORESET adaptation instruction, the resource area of ​​the frequency / time axis of the CORESET set through the Higher layer parameter can be directly changed. The resource unit area of ​​the frequency axis (e.g., RB) of the CORESET set can be changed, or the parameter configuring the CORESET can be changed.

[0309] - The on / off status of a CORESET can be instructed based on the structure of the SS set connected to the CORESET. If a CORESET connected to a specific SS set is turned off, monitoring of that SS set may not be performed. By configuring multiple candidate CORESETs to be connected to a single SS set, the resources on the time / frequency axis where PDCCH monitoring based on the SS set settings is performed can be changed via CORESET on / off. An operation such as CORESET (group) switching can be proposed to consider an operation that simultaneously instructs the on / off status of multiple CORESETs (groups).

[0310] The proposed CORESET adaptation methods consider ways in which a two-stage control structure can be applied. It proposes how instructions for CORESET adaptation and instructions related to the two-stage control structure are configured and transmitted. Additionally, it proposes a method for splitting and transmitting RNTI in the two-stage control structure and a method for the operation in the case where the terminal fails to receive the first control information.

[0311] The present disclosure proposes an operation in which the resource domains of the time / frequency axis of a CORESET, in which a terminal performs PDCCH monitoring for a certain period of time, are adapted through control information (e.g., DCI, MAC CE, etc.) from a base station.

[0312] The distinction between the proposals described below is for the convenience of explanation, and each proposal may be implemented individually or, depending on the implementation, multiple proposals may be implemented in a form at least partially combined.

[0313] Proposal 1: CORESET adaptation for specific RB area settings

[0314] In a 5G NR system, CORESET configuration information indicates resource areas in the time / frequency axes through information on consecutive symbols (up to 3 symbols) in the time domain and a bit string of up to 45 bits representing 6 RBs as one bit in the frequency domain. In the case of the resource areas in the frequency axis, they are configured discontinuously starting from the reference lowest frequency axis position, such that 6 RBs are allocated if the bit is 1 and not allocated if the bit is 0. Therefore, a method for CORESET adaptation based on the configuration of specific RB areas constituting the CORESET can be considered. For example, the base station can pre-configure the resource areas in the frequency axis that can be adapted and adjust the CORESET area that the terminal can utilize for PDCCH reception through instructions.

[0315] Puncturing of resource regions in the frequency axis of a CORESET may be considered. In this disclosure, puncturing of a CORESET frequency region means excluding some RB regions among the RBs in the frequency region set in the CORESET. If a base station makes a directive and a terminal receives it and commonly knows that a specific RB region has been punctured, the terminal can expect that a PDCCH candidate will not be transmitted in the punctured RB region, and can expect that a PDCCH candidate that could be transmitted including the corresponding RB region before puncturing will be transmitted after puncturing by rate-matching excluding the corresponding RB region. The base station may set a specific RB region that can be used for puncturing purposes along with the CORESET setting in the terminal. Such a specific RB region may be set individually for each CORESET or may be set in the terminal so that multiple CORESETs can share it. By setting a specific RB region, the base station may reduce the resource region in the frequency axis where a PDCCH candidate can be transmitted, or utilize an RB region that should originally be used for PDCCH transmission for transmitting other signals.

[0316] It may be considered to allocate additional RBs to the resource area of ​​the frequency axis of the CORESET. The method of designating these additional RB areas can be configured similarly to the method of designating specific RB areas for puncturing as described above. Through this, the base station can ensure that more resources are allocated to PDCCH candidates that can be transmitted using a specific CORESET (or multiple CORESETs). By allocating more resources to a single PDCCH candidate, one can expect to lower the code rate to increase the transmission success rate, or increase the number of PDCCH candidates with a low code rate (utilizing more CCEs (control channel elements)). Through this, the terminal can expect a higher reception success rate when PDCCHs utilizing more resources are transmitted from the base station during poor channel conditions.

[0317] For example, you can use a hashing function to configure specific RB areas not to be allocated to CORESET.

[0318] Regarding CORESET, in 5G NR systems, the placement of a PDCCH candidate at aggregation level L into a specific CCE index is determined through a hashing function. The hashing function extracted from the NR standard document TS.38.213 is shown in Table 2 below. A hashing function for placing a PDCCH candidate into CORESET can be constructed based on similar principles.

[0319]

[0320] According to one embodiment, a hashing function can be used to configure a specific RB area not to be allocated to the CORESET. For example, the total number of CCEs (N CCE,pYou can reduce ) and add an offset. Through this offset, you can adjust / configure the RB range where a PDCCH candidate may not be assigned. Additionally, you can pre-configure a range of specific CCE indices so that they are not assigned to a PDCCH candidate.

[0321] For CORESET adaptation instructions for the RB region, one or more sub-CORESET(s) may be assigned to and configured within a single CORESET. In this case, a sub-CORESET index (or a combination of indices) may be indicated via a specific adaptation signal (e.g., at least one of DCI, MAC CE, and / or LP WUS). For example, if a CORESET is configured with sub-CORESET #1 and sub-CORESET #2, and the default setting is sub-CORESET #1 + sub-CORESET #2, then if only sub-CORESET #1 is indicated via the specific adaptation signal, the adapted CORESET may be configured with the frequency axis region of sub-CORESET #2 punctured. If the default setting is sub-CORESET #1, then if sub-CORESET #1 + sub-CORESET #2 is indicated via the specific adaptation signal, then the adapted CORESET may be configured with the frequency axis region of sub-CORESET #2 additionally assigned.

[0322] In such cases, some of the parameters constituting the CORESET may be set commonly for the sub-CORESETs, while the remaining parameters may be set individually for each sub-CORESET. At least one of two options may be considered for the adaptation instructions for the CORESET configuration based on these sub-CORESETs.

[0323] (1) Option 1: Regardless of the change in the number of (aggregated) sub-CORESETs constituting a single CORESET through the above adaptation signal, REG bundle and / or mapping such as CCE-to-REG is performed individually for each sub-CORESET resource.

[0324] In this case, CCE indexing is performed sequentially so that the CCE index extends across the specified sub-CORESETs (rather than per sub-CORESET). For example, CCE indices 0 through N are allocated for the first sub-CORESET, CCE indices N+1 through N+1+K are allocated for the next second sub-CORESET, and this process is repeated similarly up to the nth sub-CORESET. Therefore, with this Option, sub-CORESETs can be configured in a way that their resources do not overlap.

[0325] (2) Option 2: Perform mapping of REG bundles and / or CCE-to-REG, etc., according to the number of sub-CORESETs indicated by the adaptation signal, e.g., the total resources of multiple aggregated sub-CORESETs.

[0326] In this case, CCE indexing can also be performed based on the entire resources of multiple aggregated sub-CORESETs. A CCE index number is set for the resource area of ​​the entire CORESET without distinguishing between sub-CORESETs. Alternatively, in this case, while the sub-CORESETs are configured with resources that overlap (or do not overlap), only a specific sub-CORESET index may be indicated through the adaptation signal, and mapping / indexing of REG / CCE may be performed based on this.

[0327] Proposal 2: Combine CORESET(s)

[0328] CORESET adaptation can be performed by combining multiple CORESETs to form a single CORESET based on instructions from a base station (e.g., at least one of DCI, MAC CE, or LP WUS) or requests from a terminal. By combining multiple CORESETs to form a single CORESET larger than the existing configured resource area, more resources can be allocated for transmitting PDCCH. To this end, the following three options may be considered.

[0329] (1) Option 1: Combination of CORESETs that perform PDCCH monitoring at the same time based on SS set settings

[0330] A terminal may be instructed to combine multiple CORESETs monitoring within the same time resource (e.g., slot) into a single CORESET. Since the actual monitoring operation for a configured CORESET follows the settings of the SS set, restricting the combination to only CORESETs monitoring at the same time may eliminate the need for additional configuration or instructions regarding the actual monitoring operation performed by the terminal. For example, if the terminal is configured via the SS set to monitor PDCCH in CORESET #1 and CORESET #2 for a specific period slot / symbol, it may be instructed to combine only CORESET #1 and CORESET #2 to form one large CORESET. As an example, the combined CORESET #1 and CORESET #2 may be CORESETs of the same size. The configuration of CORESET #1 and CORESET #2 monitoring within the same time resource may be a complete overlap of CORESET #1 and CORESET #2 in the time domain, but is not limited to this, and may also be a partial overlap of CORESET #1 and CORESET #2. Alternatively, cases may be included where CORESET #1 and CORESET #2 belong to the same time resource / time window and are separated by less than a certain time interval in the time domain, even if CORESET #1 and CORESET #2 do not overlap. For example, when SS set #1 and SS #2 are linked to CORESET #1 and CORESET #2 respectively, a CORESET adaptation instruction may be used to instruct SS set #1 to be monitored in a combined form of CORESET #1 + CORESET #2, and for SS set #1, which has more CORESET resources, PDCCH transmission and reception with a larger AL (than the AL provided in the SS set #1 configuration) may also be supported.Through this, it is expected that the reception performance of the terminal will be improved by allocating more resources to transmit PDCCH, similar to the methods proposed above, thereby lowering the code rate and increasing coverage.

[0331] For example, PDCCH monitoring in a combined CORESET can be performed in the same way as PDCCH monitoring in the SS set to which the CORESET was connected before combination. Since the CORESETs are combined at the same point in time, PDCCH monitoring in the combined CORESET can be performed based on the monitoring occasion of the SS set. In this case, the number of PDCCH candidates per AL can be separately pre-configured for the combined CORESET, or it can be composed of the sum of the parameters of each SS set for the CORESETs before combination.

[0332] (2) Option 2: Multiple CORESETs may be combined (without restriction), and operations related to PDCCH monitoring follow the settings of the single SS set connected to the CORESET prior to combination.

[0333] As described above, instructions for CORESET adaptation may be provided through dynamic signaling (e.g., at least one of DCI, MAC CE and / or LP WUS), and instructions for CORESET adaptation may be instructions for combining multiple (sub-)CORESETs through CORESET addition and / or instructions for changing at least some of the parameters / configurations / structures of the (combined) CORESET.

[0334] When multiple CORESETs are combined, the terminal's PDCCH monitoring can be performed based on the SS set connected to a specific CORESET prior to combination. In this case, if the CORESET symbol positions differ, the combined CORESETs can be aligned based on the starting symbol of the specific CORESET serving as the reference for PDCCH monitoring. If they have different symbol sizes or durations, the symbol durations of the remaining CORESETs can be increased or decreased to match the symbol duration of the specific CORESET. The specific CORESET serving as the reference can be the CORESET connected to the SS set where PDCCH monitoring is performed, or it can be directly set or specified via the CORESET ID. The number of PDCCH candidates per AL can be separately pre-configured for the CORESET combination, or it can be composed of the sum of the parameters of the respective SS sets for the CORESETs prior to combination.

[0335] In cases where multiple CORESETs are combined in this manner, PDCCH monitoring operations based on SS set settings connected to other CORESETs may not be performed, in addition to the PDCCH monitoring configured to be performed as described above. For example, PDCCH monitoring operations based on settings of other SS sets that overlap or duplicate with the PDCCH monitoring predetermined for the combined CORESETs may not be performed.

[0336] (3) Option 3: Combination of PDCCH candidate units for each CORESET

[0337] The PDCCH monitoring operation of the terminal based on the SS set setting can be performed in the same way as Option 1 or Option 2.

[0338] Alternatively, since the combination is performed on a PDCCH candidate basis, PDCCH monitoring can be separated for each individual PDCCH candidate. If the starting symbol positions of the CORESETs are not the same before combination, and PDCCH reception is successful in the CORESET with the preceding symbol position before combination, PDCCH monitoring for the same AL may be omitted for the CORESET with the following symbol position before combination. The priority of the blind decoding order can be determined based on the starting symbol positions of the CORESETs before combination.

[0339] If a PDCCH candidate transmitted from a combined CORESET utilizes all resource regions of the pre-combination CORESETs, the PDCCH candidate transmitted through each pre-combination CORESET may be a codeword that is identically encoded and transmitted repeatedly, or a structure in which a single codeword is divided and transmitted across the resource regions of two CORESETs. Alternatively, the structure may consider incremental redundancy, where the codeword being decoded first is self-decodable, but if decoding fails, an additional codeword transmitted through resources in a subsequent time region can be received and decoded together.

[0340] Combined only when the supported ALs are the same, or the mapping relationship of PDCCH candidates per AL can be pre-set / instructed. For example, if CORESET #1 before combining is configured to transmit up to AL8 and CORESET #2 before combining is configured to transmit up to AL16, then, depending on the configured / instructed mapping relationship, PDCCH transmission of AL24 can also be considered as practically possible. For example, it can be configured to utilize a total of 24 CCEs—combining the 8 CCEs of CORESET #1 and the 16 CCEs of CORESET #2—for a single PDCCH transmission. Alternatively, CORESET #1 may be combined only for the same AL8, and the PDCCH candidate of AL16 of CORESET #2 may not have a combination relationship set. In this case, the PDCCH candidates of the same AL may have a structure of repeated transmission as proposed above, or a structure that constitutes a single codeword. If a large CORESET is configured through CORESET combination, it can be configured so that PDCCH candidates from smaller ALs are excluded and PDCCH candidates from larger ALs are included.

[0341] When CORESETs are combined, the associated parameters may be newly specified or follow the settings of a specific CORESET prior to combination. The determination of a specific CORESET may be, for example, based on CORESET IDs (e.g., following the smallest CORESET ID), by pre-setting priorities for each CORESET, or by explicitly specifying which CORESET settings to follow. For example, the interleaving method (CCE-to-REG mapping) and / or DMRS method (precoder granularity) may be pre-set or specified to follow the settings of a specific CORESET.

[0342] The TCI state of the combined CORESET can follow the settings of one of the CORESETs prior to combination. As with the other parameters mentioned above, a specific CORESET may be set to have a higher priority, or it may be set / instructed to follow the TCI state of the CORESET with a lower ID.

[0343] When CORESET coupling is performed based on a single terminal, instructions or settings for other terminals that have been configured to share resources with the CORESET may need to be considered. Even if a CORESET is configured to be terminal-specific for a single terminal, the resource domains in the actual time / frequency axis may be configured to be utilized commonly by other terminals. For example, if the combined CORESET is fully utilized for the resources of a PDCCH transmitted to a single terminal, other terminals configured with a CORESET that (partially) shares resources with the CORESET prior to coupling may fail to perform blind decoding (e.g., PDCCH detection attempts / monitoring) for that CORESET. Therefore, even if CORESET coupling is performed for other terminals, it may be desirable to instruct that blind decoding for that CORESET should not be performed from the beginning if a CORESET that shares (partially) resources is configured. When CORESET coupling is performed, the base station may simultaneously perform an action to instruct other terminals to turn off a specific CORESET. When a base station instructs a specific terminal to combine CORESET, it may instruct a terminal configured with a CORESET that shares a resource domain in the time / frequency axis to turn CORESET off. A terminal instructed to turn CORESET off may not perform PDCCH monitoring according to the SS set configuration connected to the corresponding CORESET.

[0344] Proposal 3: CORESET configuration / adaptation based on Candidate CORESET(s)

[0345] Multiple candidate CORESETs can be configured to form a single CORESET, and the CORESET can be adapted through the on / off of candidate CORESETs and / or the combination of CORESETs (as described above). Each candidate CORESET can be configured to be identical to an independent CORESET.

[0346] (1) Option 1: For a single SS set configuration, a single CORESET is configured based on multiple candidate CORESETs.

[0347] Multiple candidate CORESETs can constitute a single CORESET. Based on multiple candidate CORESETs, a single CORESET can be configured with different forms for each monitoring resource (e.g., slot) configured in the SS set. For example, a CORESET with a specific pattern can be configured by utilizing this. As a specific example, for an SS set with a period of 1 slot, PDCCH monitoring can be configured to be performed on CORESETs with different structures for each slot. When the first candidate CORESET and the second candidate CORESET are located in different slots and have different structures, if the two candidate CORESETs form a single CORESET and are configured in a single SS set, the terminal may be configured with different CORESET structures to be monitored in odd slots and even slots. However, in this example, "slot" is an example of a time resource unit and may be replaced with other time resource units (e.g., sub-slot, N symbols, subframe, or frame), and the period may also be configured with M time resource units instead of 1 time resource unit. Option 1 is an example of a pattern in which the configuration of a CORESET is changed in the time domain, and other forms of CORESET configuration patterns may also be used. By configuring the pattern in this way, the monitoring load can be adjusted for each time resource where PDCCH monitoring is performed, and resource utilization and scheduling can be performed more flexibly. Using this pattern, the CORESET combination can vary for each time resource where PDCCH monitoring is performed.

[0348] (2) Option 2: Multiple candidate CORESETs are connected to form a single SS set configuration.

[0349] When multiple candidate CORESETs are connected to and configured in a single SS set, a CORESET adaptation effect can be expected through on / off instructions for the candidate CORESETs. For example, candidate CORESET#1 and candidate CORESET#2 are configured in a single SS set, each with 2 symbol durations and resource areas on different frequency axes, and the initial configuration may be that both candidate CORESETs are on (e.g., active). In this case, if candidate CORESET#1 is instructed to be off (e.g., inactive) through a dynamic instruction, from the terminal's perspective, it can be equivalent to instructing a CORESET adaptation with a reduced specific RB area without separate reconfiguration.

[0350] The SS set may be configured so that multiple TDM (and / or FDM) candidate CORESETs are monitored within the same slot. In this case, if the first candidate CORESET fails to successfully receive the PDCCH, the system may be configured to perform PDCCH monitoring on the second candidate CORESET. PDCCH monitoring for the second candidate CORESET may be additionally allocated within the range where the reception of CCE for the terminal's blind decoding and channel estimation is permitted.

[0351] In addition, it may be considered that PDCCH is repeatedly transmitted through multiple candidate CORESETs. This may be an operation similar to the methods proposed above and may be intended to resolve the PDCCH blocking problem for the first candidate CORESET.

[0352] In the case of Proposal 3, multiple candidate CORESETs are connected to a single SS set, so that the index of the candidate CORESET connected to each monitoring occasion or monitoring occasion group can be set differently depending on the SS set configuration. Although the above proposal assumes that each candidate CORESET is configured as an individual CORESET, it can be applied in the same way even when multiple candidate CORESETs are configured for a single CORESET configuration.

[0353] Proposal 4: Two-stage control structure

[0354] A two-stage control structure can be understood as a structure in which control information is transmitted over two stages. Even when both the first and second control information are transmitted in the form of DCI, the proposed candidate CORESET-based CORESET structure can be utilized. For example, it can be assumed that the first candidate CORESET is used to transmit the first control information, and the second candidate CORESET is used to transmit the second control information.

[0355] In this structure, the first control information may include resource allocation information for the second control information, and, for example, at least one of the following information may be considered.

[0356] (i) Adaptation instructions for the CORESET capable of receiving the second control information

[0357] For example, it may include at least one of the following.

[0358] - Specific RB regions targeted for adaptation in CORESET

[0359] - Adjust CORESET parameter

[0360] - CORESET on / off

[0361] - CORESET combined configuration

[0362] - CORESET candidate structure, etc.

[0363] (ii) MCS and / or DMRS information for the CORESET capable of receiving the second control information

[0364] For example, it may include at least one of the following.

[0365] - PDCCH modulation order

[0366] - DMRS pattern / density

[0367] The first control information may include information related to PDCCH monitoring based on the second candidate CORESET as described above. For example, it may include the modulation order of the transmitted PDCCH (second control information) or instructions that help the terminal perform blind decoding by restricting the AL of the PDCCH candidate. Additionally, it may include adaptation information for the CORESET receiving the second control information.

[0368] Based on this structure, a structure can be considered in which multiple second candidate CORESETs are configured, linked, or mapped to a single first candidate CORESET. The first control information can indicate the CORESET index(es) among the multiple candidate CORESETs that require actual PDCCH monitoring. The terminal can expect improved PDCCH reception performance by reducing the range of blind decoding for the PDCCH that can actually be transmitted. Alternatively, a method of individually instructing the on / off status of multiple second candidate CORESETs can also be considered.

[0369] The second control information may be considered to include at least one of the following information.

[0370] (i) PDSCH / PUSCH scheduling information, for example, part of the PDSCH / PUSCH scheduling information may be provided in the first control information and the remainder in the second control information. Or the entire PDSCH / PUSCH scheduling information may be provided in the second control information.

[0371] (ii) TCI state based on the first control information (and / or mTRP information)

[0372] Generally, the second control information is the DCI (2 for subsequent PDSCH (PUSCH) scheduling). nd It can be considered as DCI, but at least one of the following various signals can be considered as the first control information.

[0373] (1) DCI

[0374] - When this is referred to as the 1st DCI, it can be configured to always be paired with the 2nd DCI. Based on the proposed candidate CORESET structure above, it is possible to consider including dynamic instructions for the 2nd DCI in the 1st DCI.

[0375] - It can be considered that the 1st DCI is transmitted at a relatively long interval. Once the first control information is transmitted, the instruction is maintained for a certain period of time, and it can be expected that the instruction of the first control information will be applied to all 2nd DCI transmissions within that time period.

[0376] - (candidate) A CORESET structure or CCE and / or AL, etc. can be set / instructed. For the 2nd DCI, terminal operation that receives information instructed by the 1st DCI in priority can be expected.

[0377] (2) RRC or MAC CE

[0378] - It can be a relatively static instruction compared to DCI, or it can operate similarly to a 1st DCI transmission with a long period.

[0379] - In the case of MAC CE, the base station can receive the ACK / NACK feedback transmitted by the terminal after receiving MAC CE, so it may be advantageous to issue instructions regarding the second control information.

[0380] (3) Preamble (e.g., LP-WUS)

[0381] - LP-WUS can be easily transmitted with a shorter period as a received signal by utilizing a low-power receiver different from the existing receiver. Therefore, similar to a structure where the 1st DCI and 2nd DCI are paired, the structure may be such that the LP-WUS is received (always) before the reception of the 2nd DCI.

[0382] (4) Two or more combination signals

[0383] Based on signals such as RRC, MAC CE, and / or long-period DCI, set candidate values ​​for a specific time interval are indicated, and some of the candidate values ​​set as dynamic indications through DCI can be directly indicated.

[0384] - For parts that are not specified, pre-set default values ​​may be applied.

[0385] Proposal 5: RNTI-based CRC Scrambling / Masking in a Two-stage Control Structure

[0386] When a two-stage control structure consists of a 1st DCI and a 2nd DCI, sending a 16-bit RNTI to both DCIs (e.g., scrambling / masking each DCI CRC with the entire 16-bit RNTI) can be burdensome for actual transmission. Therefore, a method of splitting a single RNTI between the 1st DCI and the 2nd DCI for transmission (e.g., CRC scrambling / masking) is considered. For convenience, the explanation assumes that the RNTI is 16 bits in total, but the total number of RNTI bits is not limited to this.

[0387] A structure can be considered in which x bits of RNTI and a CRC are transmitted to the 1st DCI, and (16-x) bits of RNTI and a CRC are transmitted to the 2nd DCI. It is assumed that terminals can be distinguished to some extent through the x bits, thereby determining which terminal the 1st DCI can be transmitted to. Based on the proposed candidate CORESET structure and the information regarding the 2nd DCI indicated by the 1st DCI, it is assumed that the reception of the 2nd DCI can be fully performed using a portion of the (16-x) bits of RNTI. For example, by limiting the number of PDCCH candidates per AL for the 2nd DCI or by indicating the candidate CORESET structure, it can be expected that the terminal will be able to fully distinguish and receive the 2nd DCI.

[0388] A structure can be considered in which the 1st DCI contains the entire 16-bit RNTI, and the 2nd DCI transmits only some bits of the RNTI. The 2nd DCI can be transmitted with only some RNTI bits CRC masked. It can be considered that the target terminal to which the 2nd DCI is transmitted is distinguished based on the information within the 1st DCI and some RNTIs. The RNTI transmitted to the 2nd DCI may be a compressed RNTI that can be verified based on the control information within the 1st DCI for the entire 16-bit RNTI.

[0389] In a more general structure, it can be considered that the 1st DCI contains / indicates UE ID type #1 and the 2nd DCI contains / indicates UE ID type #2. The UE ID types may be the proposed full RNTI and partial RNTI, or the divided RNTIs, respectively. Alternatively, UE ID type #1 and UE ID type #2 may be the (local) UE index and RNTI, or the RNTI and (local) UE index, respectively, separately set by the base station on the terminal.

[0390] In this structure, the CRC length of the 2nd DCI may be considered to vary depending on the payload. For example, if the payload of the 2nd DCI is directly indicated by the 1st DCI, or if its candidate value (or range) can be indicated, the CRC length may be indicated accordingly. Considering the structure in which the RNTI is masked in the CRC, the CRC length of the 2nd DCI may be set / indicated to be equal to or greater than the length of the RNTI or UE index included in the 2nd DCI.

[0391] Proposal 6: Operation of the terminal when it fails to receive the first control information in a two-stage control structure

[0392] At least one of the following terminal actions can be considered in the case where the terminal fails to receive the first control information.

[0393] (1) Option 1: Attempt to receive 2nd DCI

[0394] Since the terminal is configured with a two-stage control structure, even if it fails to receive the first control information, it attempts to receive the 2nd DCI based on the CORESET and SS set for the configured 2nd DCI. Although it failed to receive CORESET adaptation information for the 2nd DCI from the first control information, it can attempt to receive the 2nd DCI based on pre-configured information. For example, if multiple candidate CORESETs for the 2nd DCI are configured and indicated in the first control information, even if the first control information is not received, blind decoding for the multiple candidate CORESETs can be performed according to the BD / CCE limit.

[0395] (2) Option 2: Do not receive 2nd DCI

[0396] Since the first control information was not received, subsequent 2nd DCIs are not received. For example, if DCIs were not received from the first candidate CORESET, blind decoding is not performed for the configured multiple candidate CORESETs.

[0397] (3) Option 3: Fallback action

[0398] If no DCI is detected in the first candidate CORESET for a certain period of time or number of times without specific instructions, priority is given to SS set monitoring based on the existing CORESET structure, rather than a structure based on multiple candidate CORESETs. In other words, it falls back to a configuration for a structure that receives a single DCI rather than a two-stage control structure, and monitors MOs based on the configured SS set to perform blind decoding to determine if there is a DCI that the terminal can receive.

[0399] Proposal 7: Adjusting the parameter(s) configuring the CORESET

[0400] The parameters of CORESET may include 1 CCE composed of 6 REGs (resource element groups), the REG bundle size which is the minimum unit of interleaving, and the symbol duration which is the size on the time axis. Interleaving at the REG bundle level allows for frequency-selective gain by spreading the frequency axis regions constituting the PDCCH candidate within a single CORESET.

[0401] Basically, PDCCH candidates assigned to a CORESET are configured in units of CCEs. For example, if a PDCCH candidate is configured with 1 CCE, it becomes AL1 (aggregation level 1), and if a PDCCH candidate is configured with 2 CCEs, it becomes AL2. Based on NR, a PDCCH candidate can be configured with up to 16 CCEs.

[0402] According to one embodiment, the number of REGs that can configure CCE can be changed to a number other than 6 to adjust the resource area of ​​the time / frequency axis allocated to a single PDCCH candidate.

[0403] - For example, 1 CCE can be configured as 6*N REG. As an example, N can be a number greater than 1. Upon receiving instructions for CORESET adaptation, the resources in the time / frequency axis for configuring a single PDCCH candidate increase, and on the terminal side, the total number of blind decoding operations required for PDCCH reception (e.g., the number of PDCCH candidates to attempt detection) can be reduced. In this case, the configured value M, the number of PDCCH candidates per AL s (L) can be adjusted to match the increased size of the CCE. For example, the number of PDCCH candidates per AL after the CORESET adaptation instruction is floor(M s (L) It can be defined as / N). If N=2, and the number of PDCCH candidates in AL4 was 4, then after the CORESET adaptation instruction, the number of PDCCH candidates in AL4 can become 2. Since the resource area of ​​the minimum unit time / frequency axis allocated to a single PDCCH candidate increases, the number of PDCCH candidates per AL can be automatically reduced.

[0404] For example, 1 CCE can be configured with n REGs. Here, n can represent the symbol duration of the CORESET. By configuring the CCE, the smallest unit of a PDCCH candidate, with REGs in the same frequency range, the configuration can be smaller than the existing 6 REG configuration, and interleaving can be performed in the same way as before. Since the minimum configuration unit of a PDCCH candidate has been reduced, a reduction in blocking probability can be expected by instructing it when the channel is good. Interleaving following this CORESET adaptation instruction can be performed at the REG bundle level as before, or it can be changed to interleaving at the 1 CCE level of n REGs. This can be pre-configured and instructed. This can be understood as allowing N to have a value of 1 / 2 or 1 / 3, which is less than 1, when configuring 1 CCE with 6*N REGs as mentioned earlier.

[0405] You can adjust the REG bundle size, which is the unit of interleaving.

[0406] Based on the current NR, the REG bundle size has a value of {2, 6} when the symbol duration of the CORESET is 1 or 2, and {3, 6} when the symbol duration is 3. REGs located in the same frequency range always form the same CCE.

[0407] Based on this, according to one embodiment, the REG bundle size can be adjusted to be smaller or larger than the existing size through a CORESET adaptation instruction. Candidate REG bundle sizes for each symbol duration can be configured / set and adjusted according to the CORESET adaptation instruction. For example, if the symbol duration is 2, the candidate REG bundle size can be configured / defined as {2, 4, 6, 12} and the REG bundle size can be changed by instructing a value different from the RRC-set value.

[0408] You can instruct the adjustment of the CORESET's symbol duration. By instructing CORESET adaptation, you can adjust the CORESET symbol duration to increase or decrease. If the CORESET symbol duration is at its maximum, it may be temporarily allowed to exceed the maximum value when an adaptation instruction is received. For example, if the maximum settable value for CORESET symbol duration is defined as 3, and a CORESET adaptation instruction is received to increase the symbol duration when the instructed symbol duration via RRC is 3, the symbol duration may temporarily become 4, while the matching and interleaving of the PRB and CCE indices may remain unchanged. To achieve this, the REG bundle size may change to 4 if the duration is 3, and to 8 if the duration is 6. If the CORESET adaptation instruction instructs the symbol duration to decrease, the REG bundle size may be adjusted based on the existing REG bundle size. For example, if the symbol duration is adapted from 3 to 2, the REG bundle size may change from 3 to 2. If the REG bundle size is 6, it may not change.

[0409] It may be instructed to adjust the RB unit of the parameter (frequencyDomainResources) that sets the RB set of the CORESET. According to the current NR, the frequencyDomainResources parameter is composed of a bitmap, and each bit corresponds to 6 RB. As an example of the present disclosure, the frequency domain of the CORESET configured in 6 RB units may be changed to 12 RB units. In this case, even if other parameters are utilized as they are, only the frequency axis area of ​​the CORESET may be doubled. Among other parameters, the frequency axis area may be applied as double. 1 REG may be applied as 24 REs of 1 symbol, and the REG, REG bundle, and CCE-based operation may not be changed. For example, according to the current NR, 1 REG corresponds to 1 symbol and 12 subcarriers (i.e., 12 REs), but in a situation where the adaptation of the present disclosure is applied, 1 REG may be changed to 1 symbol and 24 subcarriers (i.e., 24 REs).

[0410] When such CORESET adaptation instructions are received, parameters regarding the precoding and interleaving of the CORESET may be implicitly or directly modified according to the RB adaptation. For example, if the adaptation instruction is to reduce the RB region of the CORESET, it may be modified to be fixed as non-interleaved. Or, if the RB size of the CORESET is adapted to be less than a certain size and the RB region is continuous, it may be modified to be fixed as wideband DMRS (i.e., when precoderGranularity is allContiguousRBs).

[0411] Proposal 8: CORESET on / off (e.g., enable / disable) instruction

[0412] Multiple CORESETs for a single BWP can be configured on the terminal. Each CORESET can be distinguished by an ID. For example, control information can be used to instruct a CORESET with a specific ID to turn on or off (e.g., active or inactive). A terminal that receives an instruction to turn off a CORESET may not perform PDCCH monitoring based on the SS set configured to that CORESET.

[0413] When CORESET off is instructed to a terminal, the duration of the operation may be pre-set. When a base station sets a specific CORESET, the CORESET may be set to be off for a certain period of time T (or for N time resources) when the terminal receives the instruction. For example, if the CORESET off duration T for CORESET A is set to 10 slots (or 10ms), the terminal may not perform PDCCH monitoring based on the SS set associated with CORESET A for 10 slots (or 10ms) upon receiving control information containing the CORESET off instruction.

[0414] Along with CORESET on / off operations, CORESET (group) switching operations can be considered. For example, assuming that CORESET group index 1 containing multiple CORESETs and CORESET group index 2 containing multiple CORESETs are configured, the terminal can monitor PDCCH based on SS sets connected to CORESETs within CORESET group index 1 during initial operation or until a CORESET switching instruction is received. Upon receiving a CORESET switching instruction, all CORESETs within CORESET group index 1 are turned off, and the CORESETs in CORESET group index 2 are turned on. Therefore, the terminal monitors PDCCH based on SS sets connected to CORESETs within CORESET group index 2. More generally, a method can also be considered in which two or more CORESET groups are defined and the terminal directly instructs the CORESET group index to operate based on a specific CORESET(s).

[0415] It is possible to consider the on / off operation of a CORESET being instructed from the perspective of a single SS set. Multiple candidate CORESETs can be configured to be connected to and instructed by a single SS set, and the base station can dynamically instruct which actual CORESET the SS set operates based on. For example, an SS set may be configured for different candidate CORESETs. Until a dynamic instruction is given, the SS set operates as the default CORESET. When the terminal receives a CORESET adaptation instruction for the SS set, it changes to (at least) one of the previously configured candidate CORESETs in accordance with the instruction and can perform PDCCH monitoring operations based on the changed CORESET. The base station may instruct switching between candidate CORESETs for a single SS set, or instruct operation based on a candidate CORESET of a specific ID.

[0416] These candidate CORESETs can each be based on individual CORESET configurations. In other words, multiple CORESETs with individual IDs are configured, a default CORESET ID is configured for a single SS set, and candidate CORESETs that can be indicated through CORESET adaptation can be configured separately or additionally via each CORESET ID. SS set #1 is configured by default in conjunction with CORESET #1, and CORESET #2 and #3 may be pre-configured as candidate CORESETs.

[0417] Alternatively, the structure may include multiple candidate CORESETs within a single CORESET configuration. A single CORESET can be configured based on multiple candidate CORESETs with different parameters. For example, SS set #1 operates by default connected to CORESET #1. In this case, CORESET #1 is configured based on candidate CORESETs #1-1, #1-2, and #1-3. Candidate CORESETs #1-1, #1-2, and #1-3 each have different parameters, and a CORESET adaptation instruction can be used to specify which candidate CORESET will be connected to SS set #1 for operation.

[0418] Proposal 9: Adaptation of a CORESET common to multiple SS sets

[0419] When an adaptation to a CORESET is performed according to at least one of the proposals, if the CORESET is commonly connected to multiple SS sets, one can consider how the CORESET adaptation will be performed.

[0420] (1) Option 1: Individual adaptation for each SS set connected to CORESET

[0421] Through CORESET adaptation instructions for a specific terminal, individual adaptation instructions may or may not be applied for each SS set connected to the CORESET. In other words, when performing PDCCH monitoring that follows the settings of the SS sets connected to the CORESET, the application of the instructed CORESET adaptation may vary depending on the SS set. For example, if multiple SS sets are connected to and configured within a CORESET and a terminal receives a CORESET adaptation instruction, the SS set for which PDCCH monitoring is performed with the CORESET adaptation applied may be pre-configured by SS set ID, or the CORESET adaptation instruction may include information on which SS set will follow the instruction. In other words, even if a specific SS set is connected to and configured within the CORESET that received the instruction, the adaptation may not (always) be applied even upon receiving the instruction.

[0422] (2) Option 2: Common adaptation for all SS sets connected to CORESET

[0423] When a terminal performs PDCCH monitoring based on the settings of all SS sets connected to the CORESET, the instructed CORESET adaptation may be applied to all SS sets. If the SS set connected to the CORESET is a CSS, it may need to be applied commonly to multiple terminals; therefore, such adaptation instructions must always be instructed commonly to multiple terminals, similar to group common DCI.

[0424] (3) Option 3: CORESET linked to Common SS set (CSS) does not expect adaptation instructions

[0425] For CORESETs connected to CSSs that are commonly configured for multiple terminals, adaptation instructions may not be expected. For example, even if an adaptation instruction is given for CORESET#0, that instruction may not be applied to Type0 / 0A / 1 / 2-CSS sets that can be connected to CORESET#0. As another example, if CORESET#1 is connected to CSS and USS and a terminal receives an adaptation instruction for CORESET#1, the terminal may perform PDCCH monitoring in CORESET#1 without adaptation when performing according to the CSS settings, and perform PDCCH monitoring in CORESET#1 with adaptation when performing according to the USS settings.

[0426] FIG. 14 is a diagram illustrating the operation of a terminal and a base station regarding CORESET adaptation according to one embodiment. Since FIG. 14 is an example of implementation for at least some of the proposals described above, the previously described content may be referenced without further separate mention.

[0427] Referring to FIG. 14, the terminal can receive at least one upper layer signaling (e.g., RRC signaling) from a base station. The upper layer signaling may include at least one of CORESET(s) setting information, SS (search space) set(s) setting information, UL channel / signal (e.g., PUSCH, PUCCH, UL RS) setting information, or DL ​​channel / signal (e.g., PDSCH, PDCCH, DMRS, etc. DL RS) setting information.

[0428] The terminal may receive information from the base station instructing CORESET adaptation (A10). CORESET adaptation may be related, for example, to the activation / deactivation of CORESET, the combination / addition / modification / switching of CORESET, etc., and may be an instruction related to at least one of proposals 1 to 9 described above. Information instructing CORESET adaptation may be received, for example, through at least one of DCI, MAC CE, or LP WUS. DCI may correspond to the 1st DCI among 2-step DCI.

[0429] The terminal can determine a CORESET adapted for PDCCH monitoring based on the CORESET adaptation instruction and perform PDCCH monitoring (A15).

[0430] The base station may transmit a PDCCH to a terminal on an adapted CORESET (A20). For example, the PDCCH may include a 2nd DCI of a 2-step DCI. The 2-step DCI may be related to at least one of PDSCH(s) scheduling or PUSCH(s) scheduling.

[0431] The terminal can perform at least one of receiving PDSCH(s) or transmitting PUSCH(s) (A25).

[0432] FIG. 15 illustrates the flow of a method performed by a terminal according to one embodiment. Since FIG. 15 is an example of implementation for at least some of the proposals described above, the previously described content may be referenced without further separate mention.

[0433] Referring to FIG. 15, the terminal can receive configuration information for control resource sets through upper layer signaling (B05).

[0434] The terminal can receive a downlink signal containing information about the aggregation of at least two of the control resource sets (B10).

[0435] The terminal can receive a downlink control channel based on the combination of at least two sets of control resources (B15).

[0436] The above downlink signal may include at least one of DCI (downlink control information) or MAC (medium access control) CE (control element). Information regarding the combination of at least two sets of control resources may be included in at least one of the DCI or MAC CE.

[0437] The above at least two sets of control resources can be combined into one set of control resources.

[0438] The control channel can be received on the combined control resource set based on setting information for a search space set linked to a reference control resource set among the at least two control resource sets mentioned above.

[0439] Based on at least one of the number of symbols or symbol positions set in the reference control resource set, the remaining control resource sets among the at least two control resource sets can be aligned for combination.

[0440] Information regarding the combination of at least two sets of control resources mentioned above may include index information of the reference control resource set.

[0441] Based on the fact that the above at least two sets of control resources are monitored on the same time resource, the above at least two sets of control resources can be combined.

[0442] Information regarding the combination of at least two or more control resource sets may include active / inactive information for each control resource set.

[0443] The above downlink control channel can receive based on the combination of activated control resource sets.

[0444] The active / inactive information for each of the above control resource sets may be provided for each of one or more candidate control resource sets associated with the same search space set.

[0445] The above downlink signal is a first PDCCH (physical downlink control channel) for the first DCI among the two-step DCI (downlink control information), and the downlink control channel may be a second PDCCH for the second DCI among the two-step DCI.

[0446] The combination of at least two sets of control resources mentioned above can be performed on the USS (user-equipment specific search space) among the CSS (common search space) set and the USS set.

[0447] FIG. 16 illustrates the flow of a method performed by a base station according to one embodiment. Since FIG. 16 is an example of implementation for at least some of the proposals described above, the previously described content may be referenced without further separate mention.

[0448] Referring to FIG. 16, the base station can transmit configuration information for sets of control resources through upper layer signaling (C05).

[0449] The base station may transmit a downlink signal containing information about the aggregation of at least two of the control resource sets (C10).

[0450] The base station can transmit a downlink control channel based on the combination of at least two sets of control resources (C15).

[0451] The above downlink signal may include at least one of DCI (downlink control information) or MAC (medium access control) CE (control element). Information regarding the combination of at least two sets of control resources may be included in at least one of the DCI or MAC CE.

[0452] The above at least two sets of control resources can be combined into one set of control resources.

[0453] The control channel can be transmitted on the combined control resource set based on setting information for a search space set linked to a reference control resource set among the at least two control resource sets mentioned above.

[0454] Based on at least one of the number of symbols or symbol positions set in the reference control resource set, the remaining control resource sets among the at least two control resource sets can be aligned for combination.

[0455] Information regarding the combination of at least two sets of control resources mentioned above may include index information of the reference control resource set.

[0456] Based on the fact that the above at least two sets of control resources are configured on the same time resource, the above at least two sets of control resources can be combined.

[0457] Information regarding the combination of at least two or more control resource sets may include active / inactive information for each control resource set.

[0458] The above downlink control channel can be transmitted based on the combination of activated control resource sets.

[0459] The active / inactive information for each of the above control resource sets may be provided for each of one or more candidate control resource sets associated with the same search space set.

[0460] The above downlink signal is a first PDCCH (physical downlink control channel) for the first DCI among the two-step DCI (downlink control information), and the downlink control channel may be a second PDCCH for the second DCI among the two-step DCI.

[0461] The combination of at least two sets of control resources mentioned above can be performed on the USS (user-equipment specific search space) among the CSS (common search space) set and the USS set.

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

[0463] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the features of the present disclosure. Accordingly, the foregoing detailed description should not be interpreted restrictively in all respects and should be considered illustrative. 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.

[0464] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed by a terminal, Receive configuration information for control resource sets through upper-level signaling; Receiving a downlink signal including information on the aggregation of at least two of the above control resource sets; and A method comprising receiving a downlink control channel based on the combination of at least two sets of control resources.

2. In Paragraph 1, The above downlink signal includes at least one of DCI (downlink control information) or MAC (medium access control) CE (control element), and Information regarding the combination of at least two sets of control resources is included in at least one of the DCI or the MAC CE, in a method.

3. In Paragraph 1, The above at least two sets of control resources are combined into one set of control resources, and A method in which the control channel is received on the combined control resource set based on configuration information for a search space set associated with a reference control resource set among at least two control resource sets.

4. In Paragraph 3, A method in which the remaining control resource sets among the at least two control resource sets are aligned for combination based on at least one of the number of symbols or the symbol positions set in the reference control resource set.

5. In Paragraph 3, A method in which information regarding the combination of at least two sets of control resources includes index information of the reference set of control resources.

6. In Paragraph 1, A method in which at least two sets of control resources are combined based on the fact that the at least two sets of control resources are monitored on the same time resource.

7. In Paragraph 1, Information regarding the combination of at least two or more control resource sets includes active / inactive information for each control resource set, and The above downlink control channel is received based on the combination of activated control resource sets, a method.

8. In Paragraph 7, A method in which active / inactive information for each of the above control resource sets is provided for each of one or more candidate control resource sets associated with the same search space set.

9. In Paragraph 1, The above downlink signal is a first PDCCH (physical downlink control channel) for the first DCI among the 2-step DCI (downlink control information), and The method wherein the downlink control channel is a second PDCCH for the second DCI among the two-stage DCIs.

10. In Paragraph 1, A method in which the combination of at least two sets of control resources is performed with respect to the USS (user-equipment specific search space) among the CSS (common search space) set and the USS (user-equipment specific search space) set.

11. A computer-readable non-transitory recording medium storing a program for performing the method described in claim 1.

12. Regarding the device, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Receive configuration information for control resource sets through upper-level signaling; Receiving a downlink signal including information on the aggregation of at least two of the above control resource sets; and A device comprising receiving a downlink control channel based on the combination of at least two sets of control resources.

13. In Paragraph 12, The above device is a device that is a terminal including a transceiver or a processing device configured to control the terminal.

14. In a method performed by a base station, Transmit configuration information for control resource sets through upper-layer signaling; Transmitting a downlink signal including information on the aggregation of at least two of the above control resource sets; and A method comprising transmitting a downlink control channel based on the combination of at least two sets of control resources.

15. Regarding base stations, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Transmit configuration information for control resource sets through upper-layer signaling; Transmitting a downlink signal including information on the aggregation of at least two of the above control resource sets; and A base station comprising transmitting a downlink control channel based on the combination of at least two sets of control resources.

Images