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

Abstract

According to one embodiment of the present disclosure, a terminal may receive first downlink control information (DCI) through a first physical downlink control channel (PDCCH), receive second DCI through a second PDCCH, and perform reception of at least one downlink signal or transmission of at least one uplink signal on the basis of the first DCI and the second DCI, wherein the terminal may obtain a downlink assignment index (DAI) on the basis of at least one of the first DCI or the second DCI.

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 or 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 NR, dynamic scheduling of PDSCH (physical downlink shared channel) or PUSCH (physical uplink shared channel) is instructed to the terminal through a single DCI (downlink control information), and polar coding is used for channel coding of the DCI. In the case of polar coding in NR, the configurable DCI payload size was limited, and as a result, DCI configurations of more than 142 bits were not supported.

[0004] Meanwhile, in next-generation wireless communication systems including 6G, more information may need to be provided through DCI, and depending on the size of the total payload, more than one DCI may be required.

[0005] 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. As an example, a structure for hierarchically dividing and transmitting downlink control information, for example, a 2-step / stage DCI structure, may be provided. As an example, scheduling information regarding at least one DL signal and / or at least one UL signal may be provided through a combination of the 1st DCI and the 2nd DCI. In addition, a HARQ-ACK codebook configuration and a HARQ-ACK feedback method related to the 2-step DCI may be provided.

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

[0007] A method performed by a terminal in one aspect of the present disclosure comprises receiving a first DCI (downlink control information) through a first PDCCH (physical downlink control channel); receiving a second DCI through a second PDCCH; and performing at least one downlink signal reception or at least one uplink signal transmission based on the first DCI and the second DCI, wherein the terminal may obtain a DAI (downlink assignment index) based on at least one of the first DCI or the second DCI.

[0008] The above DAI can be counted based on at least one of the first PDCCH MO (monitoring occasion) related to the first DCI or the second PDCCH MO related to the second DCI.

[0009] The above DAI can be counted based on the PDCCH MO related to the DCI containing the DAI among the above first DCI and the above second DCI.

[0010] The first DCI may include a part of the DAI, and the second DCI may include the remaining part of the DAI.

[0011] A portion of the above DAI is related to Total-DAI, and the remaining portion of the above DAI may be related to Counter-DAI.

[0012] The terminal may transmit a HARQ-ACK (hybrid automatic repeat request-acknowledgement) codebook based on the DAI. The HARQ-ACK codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0013] The above HARQ-ACK codebook may be configured based on the concatenation of a first sub-codebook and at least one second sub-codebook. The first sub-codebook includes a HARQ-ACK for the at least one downlink signal, and the at least one second sub-codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0014] The above DAI may include a first DAI and a second DAI. The first DAI may be included in the first DCI. The second DAI may be included in the second DCI.

[0015] A second subcodebook including a HARQ-ACK for the first DCI can be determined based on the first DAI.

[0016] A second subcodebook including a HARQ-ACK for the second DCI can be determined based on the second DAI.

[0017] The above HARQ-ACK codebook can be transmitted via a PUCCH (physical uplink control channel) resource. The PUCCH resource can be determined based on PRI (PUCCH resource indicator) information included in at least one of the first DCI or the second DCI.

[0018] The first DCI and the second DCI may be DCIs of a 2-step DCI. The at least one downlink signal may be at least one PDSCH (physical downlink shared channel). The at least one uplink signal may be at least one PUSCH (physical uplink shared channel).

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

[0020] 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 are executed by the at least one processor to cause the at least one processor to perform operations, wherein the operations of the processor include receiving a first DCI (downlink control information) through a first PDCCH (physical downlink control channel); receiving a second DCI through a second PDCCH; and performing at least one downlink signal reception or at least one uplink signal transmission based on the first DCI and the second DCI, and the apparatus may obtain a DAI (downlink assignment index) based on at least one of the first DCI or the second DCI.

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

[0022] According to another aspect of the present disclosure, a method performed by a base station comprises: transmitting a first DCI (downlink control information) to a terminal through a first PDCCH (physical downlink control channel); transmitting a second DCI to the terminal through a second PDCCH; and performing transmission of at least one downlink signal or reception of at least one uplink signal based on the first DCI and the second DCI, wherein the base station may provide a DAI (downlink assignment index) to the terminal based on at least one of the first DCI or the second DCI.

[0023] 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 include transmitting a first DCI (downlink control information) to a terminal through a first PDCCH (physical downlink control channel); transmitting a second DCI to the terminal through a second PDCCH; and transmitting at least one downlink signal or receiving at least one uplink signal based on the first DCI and the second DCI, and the base station may provide a DAI (downlink assignment index) to the terminal based on at least one of the first DCI or the second DCI.

[0024] According to the present disclosure, signal transmission and reception can be performed efficiently in a wireless communication system. According to one embodiment, by using a structure that hierarchically divides and transmits downlink control information, for example, a 2-step / stage DCI structure, the DCI payload size constraint can be overcome and a wider variety of DCI payload configurations can be supported. In addition, by providing a HARQ-ACK codebook configuration and a HARQ-ACK feedback method suitable for the 2-step DCI structure, more reliable and stable scheduling can be supported.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] Figure 13 illustrates the process of receiving PDSCH in NR and transmitting ACK / NACK therefor.

[0039] Figure 14 illustrates the PUSCH transmission process in NR.

[0040] Figure 15 is a diagram illustrating the total-DAI and counter-DAI counts in the NR standard.

[0041] FIG. 16 is a diagram illustrating the operation of a terminal and a base station according to one embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] <Symbols, Abbreviations, Terms>

[0059] - PDCCH: Physical Downlink Control CHannel

[0060] - DCI: Downlink Control Information

[0061] - PDSCH: Physical Downlink Shared CHannel

[0062] - PUSCH: Physical Uplink Shared CHannel

[0063] - CSI: Channel state information

[0064] - RRM: Radio resource management

[0065] - SCS: Sub-carrier spacing

[0066] - RLM: Radio link monitoring

[0067] - DCI: Downlink Control Information

[0068] - CAP: Channel Access Procedure

[0069] - Ucell: Unlicensed cell

[0070] - TBS: Transport Block Size

[0071] - TDRA: Time Domain Resource Allocation

[0072] - TDRA (Time domain resource assignment) table: Consists of multiple combinations of {K0, SLIV, mapping type} (configured by RRC) (one combination is mapped to each of the multiple rows within the table), and a specific row is indicated via DCI.

[0073] - K0 (DL assignment-to-PDSCH offset): Slot interval between a DCI transmission slot and a PDSCH transmission slot (scheduled from that DCI).

[0074] - 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.) (e.g., SLIV may correspond to a PDSCH / PUSCH occasion)

[0075] - Mapping type: Information regarding whether the DMRS symbol location in PDSCH is determined based on the symbol index within the slot duration or the symbol index within the PDSCH duration.

[0076] - K1 (PDSCH-to-HARQ_feedback timing indicator): Slot interval between the PDSCH transmission slot and the HARQ-ACK transmission slot (for the reception of the corresponding PDSCH).

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

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

[0079] - REG: Resource element group

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

[0081] - COT: Channel occupancy time

[0082] - SPS: Semi-persistent scheduling

[0083] - QCL: Quasi-Co-Location (The QCL relationship between two reference signals implies that QCL parameters, such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters obtained from one reference signal, can be applied to another reference signal (or the antenna port(s) of the corresponding RS). In NR systems, four QCL types are defined as follows: 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter}. For a certain DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y). It can be set to.)

[0084] - TCI: Transmission Configuration Indication (A single TCI state contains QCL relationships between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For 'Transmission Configuration Indication' among the fields within the DCI that schedule PDSCH, the TCI state index corresponding to each code point constituting the field is activated by MAC CE, and the TCI state setting for each TCI state index is configured via RRC signaling. In Rel-16 NR systems, the corresponding TCI state is configured between DL RSs, but configuration between DL RSs and UL RSs, or between UL RSs and UL RSs, may be permitted in future releases. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0085] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields within the DCI that schedule PUSCH. When transmitting a PUSCH, the terminal can transmit the PUSCH by utilizing the same spatial domain transmission filter used for transmitting and receiving the reference signal associated with the corresponding SRS resource. In this case, the reference RS is set by RRC signaling via the SRS-SpatialRelationInfo parameter for each SRS resource, and the SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0086] - TRP: Transmission and Reception Point

[0087] - TAG: Timing advance group

[0088] - PLMN: Public Land Mobile Network

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0123] 6G System Core Technology

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

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

[0126] artificial intelligence

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0170] THz communication

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

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

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

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

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

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

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

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

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

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

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

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

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

[0184] Integrated Sensing and Communication (ISAC)

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

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

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

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

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

[0190] - 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)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0209] Data transmission and HARQ-ACK process

[0210] FIG. 13 illustrates the process of receiving a PDSCH and transmitting an ACK / NACK therefor. Referring to FIG. 13, the terminal can detect a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH represents a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI format 1_0, 1_1 may include the following information.

[0211] - Frequency domain resource assignment: Represents the set of RBs assigned to PDSCH

[0212] - Time domain resource assignment: Indicates K0 (e.g., slot offset), the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., number of OFDM symbols). As described above, the row index of the pdsch-TimeDomainAllocationList provided common to the terminal or specific to the terminal may be indicated through the TDRA field.

[0213] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1

[0214] - HARQ process number (4 bits): Represents the HARQ process ID (Identity) for data (e.g., PDSCH, TB)

[0215] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources within the PUCCH resource set.

[0216] Subsequently, the terminal receives a PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and when the reception of the PDSCH ends in slot #n1 (where, n+K0 ≤ n1), it can transmit a UCI via a PUCCH in slot #(n1+K1). Here, the UCI may include a HARQ-ACK response to the PDSCH. In FIG. 13, for convenience, it was assumed that the SCS for the PDSCH and the SCS for the PUCCH are identical and that slot #n1 = slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 may be indicated / interpreted based on the SCS of the PUCCH.

[0217] If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response may consist of 1 bit. If the PDSCH is configured to transmit up to 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the time for transmitting HARQ-ACKs for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted at slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0218] Whether a terminal must perform spatial bundling for a HARQ-ACK response can be configured per cell group (e.g., RRC / upper layer signaling). For example, spatial bundling can be configured individually for each HARQ-ACK response transmitted via PUCCH and / or HARQ-ACK response transmitted via PUSCH.

[0219] Spatial bundling may be supported when the maximum number of TBs (or codewords) that can be received (or scheduled via 1 DCI) at once in the corresponding serving cell is 2 (or more than 2) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). Meanwhile, more than 4 layers may be used for 2-TB transmission, and up to 4 layers may be used for 1-TB transmission. Consequently, if spatial bundling is configured in the corresponding cell group, spatial bundling may be performed on serving cells within the cell group for which more than 4 layers are scheduleable. On the corresponding serving cell, a terminal that intends to transmit a HARQ-ACK response via spatial bundling may generate a HARQ-ACK response by performing a (bit-wise) logical AND operation on the A / N bits of multiple TBs.

[0220] For example, assuming that a terminal receives a DCI scheduling 2-TB and receives 2-TB through a PDSCH based on the said DCI, the terminal performing spatial bundling can generate a single A / N bit by performing a logical AND operation on the first A / N bit for the first TB and the second A / N bit for the second TB. Consequently, if both the first TB and the second TB are ACK, the terminal reports the ACK bit value to the base station, and if either TB is NACK, the terminal reports the NACK bit value to the base station.

[0221] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by performing a logical AND operation between the A / N bit for the 1-TB and the bit value 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0222] Multiple parallel DL HARQ processes exist in the base station / terminal for DL ​​transmission. These multiple parallel HARQ processes enable DL transmission to be performed continuously while waiting for HARQ feedback regarding the successful or unsuccessful reception of the previous DL transmission. Each HARQ process is associated with a HARQ buffer of the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables regarding the number of transmissions of MAC PDUs (Physical Data Blocks) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is distinguished by its HARQ process ID.

[0223] FIG. 14 illustrates a PUSCH transmission process. Referring to FIG. 14, the terminal can detect PDCCH in slot #n. Here, PDCCH includes uplink scheduling information (e.g., DCI format 0_0, 0_1). DCI format 0_0, 0_1 may include the following information.

[0224] - Frequency domain resource assignment: Indicates the set of RBs assigned to PUSCH

[0225] - Time domain resource assignment: Indicates slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of PUSCH within the slot. The starting symbol and length can be indicated via SLIV (Start and Length Indicator Value).

[0226] Subsequently, the terminal can transmit PUSCH at slot #(n+K2) according to the scheduling information of slot #n. Here, PUSCH includes UL-SCH TB.

[0227] Dynamic / Semi-static HARQ-ACK Codebook

[0228] NR supports dynamic HARQ-ACK codebooks and semi-static HARQ-ACK codebooks. HARQ-ACK (or A / N) codebooks can be replaced with HARQ-ACK payloads.

[0229] When the dynamic HARQ-ACK codebook method is configured, the size of the A / N payload varies according to the actual number of scheduled DL data. To this end, the PDCCH associated with DL scheduling includes the counter-DAI (Downlink Assignment Index) and the total-DAI. The counter-DAI represents the {CC, slot} scheduling order value calculated using the CC (Component Carrier) (or cell)-first method and is used to specify the position of the A / N bit within the A / N codebook. The total-DAI represents the slot-unit scheduling cumulative value up to the current slot and is used to determine the size of the A / N codebook.

[0230] When a semi-static A / N codebook method is configured, the size of the A / N codebook is fixed (to a maximum value) regardless of the actual number of scheduled DL data. Specifically, the (maximum) A / N payload (size) transmitted through one PUCCH within one slot can be determined by the number of A / N bits corresponding to the combination of all CCs configured to the terminal and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) where the A / N transmission timing can be indicated (hereinafter, bundling window). For example, the DL grant DCI (PDCCH) includes PDSCH-to-A / N timing information, and the PDSCH-to-A / N timing information may have one of a plurality of values ​​(e.g., k). For example, if a PDSCH is received in slot #m and the PDSCH-to-A / N timing information within the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, then the A / N information for the PDSCH may be transmitted in slot #(m+k). For example, k ∈ {1, 2, 3, 4, 5, 6, 7, 8}. Meanwhile, if the A / N information is transmitted in slot #n, the A / N information may include the maximum possible A / N based on the bundling window. That is, the A / N information in slot #n may include the A / N corresponding to slot #(nk). For example, if k∈{1, 2, 3, 4, 5, 6, 7, 8}, the A / N information of slot #n includes A / Ns corresponding to slots #(n-8) through #(n-1) regardless of actual DL data reception (i.e., the maximum number of A / Ns). Here, the A / N information can be substituted with an A / N codebook and an A / N payload. Additionally, a slot can be understood / substituted as a candidate occasion for DL ​​data reception.As shown in the example, the bundling window is determined based on the PDSCH-to-A / N timing relative to the A / N slot, and the PDSCH-to-A / N timing set may have predefined values ​​(e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or be set by upper layer (RRC) signaling.

[0231] In the NR standard, Type-1 HARQ-ACK codebook refers to a semi-static HARQ-ACK codebook, and Type-2 HARQ-ACK codebook refers to a dynamic HARQ-ACK codebook.

[0232] Meanwhile, "SLIV pruning" refers to the process of calculating combinations of all (non-overlapping) PDSCH occasions (SLIVs) that can be transmitted within the DL slot K1 prior to the A / N transmission slot for each K1 value (set in the corresponding cell for each serving cell) in the case of an existing Type-1 codebook, when a set of multiple (e.g., N) candidate K1 values ​​(e.g., a set of PDSCH-to-HARQ Feedback Timing Indicator values ​​that can be indicated via DCI) is established. In other words, the process of determining the set of (non-overlapping) PDSCH occasions (SLIVs) subject to HARQ-ACK reporting corresponds to SLIV pruning. The terminal constructs an A / N (sub-)payload for the set of PDSCH occasions (SLIVs) determined through SLIV pruning (including the determination of the A / N bit position / order corresponding to each SLIV).

[0233] To examine in more detail the process of determining combinations of PDSCH occasions (SLIVs) that can be transmitted in SLIV pruning, one or more non-overlapping PDSCHs may be scheduled to the terminal in each DL slot (e.g., index #N-candidate K1 value), and the number of non-overlapping PDSCHs (maximum number of times that can be scheduled within that slot) can be determined based on combinations of configured SLIV values ​​(e.g., combinations of SLIV values ​​configured via pdsch-TimeDomainAllocationList and indicated by the TDRA field of the DCI). Based on the SLIV values ​​configured to the terminal, overlapping potential PDSCHs are pruned (i.e., incompatible / mutually exclusive PDSCHs due to overlap are counted as at most one PDSCH transmission), and non-overlapping PDSCHs (potentially scheduled / compatible) are determined. In the case of the existing Type-1 codebook, the entire A / N codebook is constructed by concatenating the A / N sub-payloads formed through this SLIV pruning over N K1 values.

[0234] Meanwhile, in existing NR, scheduling multiple PDSCHs to a single terminal through 1 DCI was supported, and in this case, multiple SLIV entries may exist in the row of the TDRA table. Considering such multiple PDSCH scheduling DCI, the process of updating the set of K1 values ​​is necessary for SLIV pruning, and the terminal determines the set of PDSCH occasions (SLIVs) based on the updated set of K1 values.

[0235] HARQ-ACK related to Multi-step DCI

[0236] The following describes a scheduling method based on M-step DCI and the related HARQ-ACK feedback. For convenience, the case where M=2 is used as an example, but this is not limited to this case, and the proposed content can also be applied to the case where M > 2. Additionally, to aid understanding, the explanation regarding the HARQ-ACK codebook refers to the Type 1 / Type 2 terms of NR, but it may also be expressed as HARQ_ACK Semi-static / dynamic HARQ-ACK codebook.

[0237] To increase the transmission efficiency of scheduling DCIs for PDSCH and / or PUSCH, scheduling multiple PDSCHs or multiple PUSCHs (on the same or different carriers / BWPs / serving cells) can be considered through a single DCI. However, considering that allocated resources or MCS values ​​may differ for each shared channel, independent fields can be configured within the DCI (for each PDSCH or PUSCH), which can significantly increase the DCI payload size. Based on the current polar code-based PDCCH design of NR, the maximum supported DCI payload size is approximately 140 bits, but more bits may be required for scheduling. Furthermore, as the payload size increases, a high aggregation level—that is, a large amount of PDCCH time / frequency resources—is required to guarantee a certain coding rate, which can significantly increase the PDCCH blocking probability (interfering with DL signals / channels for other terminals). Accordingly, considering these points, a 2-step DCI design may be introduced for a DCI capable of supporting one or more PDSCH and / or PUSCH scheduling (PDSCH and / or PUSCH may be abbreviated as PXSCH in this specification). A base station divides the information carried in the DCI into a 1st DCI and a 2nd DCI and transmits them, and a terminal can obtain scheduling information for one or more PDSCH and / or PUSCH by combining the information contained in the 1st DCI and the information contained in the 2nd DCI.

[0238] Meanwhile, the 1st DCI and the 2nd DCI may be distinguished based on at least one of the following various methods, but are not limited thereto.

[0239] - The (CRC) of the 1st DCI and 2nd DCI can be distinguished by masking (or scrambling) different RNTI values.

[0240] - The 1st DCI and 2nd DCI can be distinguished through the flag bit within the corresponding DCI.

[0241] - 1st DCI and 2nd DCI can be distinguished by time / frequency resources (e.g., PDCCH monitoring occasions such as CORESET or search space set).

[0242] - 1st DCI and 2nd DCI can be distinguished by the DCI format.

[0243] As specific examples of 1st DCI and 2nd DCI structures, consider the following two cases of 2-step DCI design.

[0244] (1) Case 1: The terminal can receive the scheduled PDSCH or transmit the PUSCH when it successfully decodes both the 1st DCI and the 2nd DCI each time. For example, the base station can transmit the 1st DCI and the 2nd DCI each time during PXSCH(s) scheduling. If the terminal fails to successfully decode either the 1st DCI or the 2nd DCI, it may not be able to receive the PDSCH or transmit the PUSCH because it is difficult to obtain the scheduling information. If the terminal fails to successfully detect the 1st DCI, it may skip monitoring the 2nd DCI.

[0245] (2) Case 2: When the terminal succeeds in detecting the 2nd DCI, it may receive a scheduled PDSCH or transmit a PUSCH even if it does not detect the corresponding 1st DCI for each 2nd DCI detection. For example, the 1st DCI is transmitted once at a relatively long interval compared to the 2nd DCI, so that once the 1st DCI is successfully detected / decoded, it may be possible to receive a PDSCH or transmit a PUSCH by successfully detecting only the 2nd DCI until there is a specific time interval or a change in the information belonging to the 1st DCI. In this case, the 1st DCI may contain information that does not change over a relatively long-term period (e.g., modulation order, frequency domain resource allocation, etc.).

[0246] In this disclosure, we propose a HARQ-ACK feedback method and / or a HARQ-ACK codebook configuration method corresponding to a DCI when a 2-step DCI can schedule one or more PXSCHs.

[0247] [Proposal #1] 2-step DCI DAI Signaling and HARQ-ACK Feedback

[0248] In the current NR system, DAI (downlink assignment index) information can be signaled as follows.

[0249] - DCI format 0_0 (UL fallback DCI format): 0 bit DAI

[0250] - DCI format 0_1 / 0_2 / 0_3 (UL non-fallback DCI format): For terminals configured with Type-1 HARQ-ACK CB (codebook), 1-bit DAI is allocated. For terminals configured with Type-2 HARQ-ACK CB, 2*N bits may be allocated for DAI depending on the specific configuration. For example, N may represent the number of sub-codebooks, and if composed of only one sub-codebook, 2 total-DAI bits are allocated, and if composed of two sub-codebooks, 2 total-DAI bits are provided for each sub-codebook, so a total of 4 bits may be allocated for DAI.

[0251] - DCI format 1_0 (DL fallback DCI format): 2-bit counter-DAI

[0252] - DCI format 1_1 / 1_2 / 1_3 (DL non-fallback DCI format): For terminals configured with Type-1 HARQ-ACK CB (codebook), 0-bits are allocated for DAI. For terminals configured with Type-2 HARQ-ACK CB, K bits may be allocated depending on the specific configuration. For example, in the case of a single serving cell, 2-bits for counter-DAI are allocated, and in the case of two or more serving cells, 2-bits for counter-DAI and 2-bits for total-DAI are allocated, so a total of 4 bits may be allocated.

[0253] Figure 15 is a diagram illustrating the counting of total-DAI and counter-DAI in the NR standard. In Figure 15, the counting of total DAI (T-DAI) and counter-DAI (C-DAI) is illustrated assuming DL scheduling DCI (e.g., DCI format 1_x).

[0254] Referring to Fig. 15, T-DAI represents the cumulative total number of {serving cell, PDCCH monitoring occasion}-pairs requiring HARQ-ACK across multiple serving cells up to the current PDCCH monitoring occasion (MO), while C-DAI represents the relative order of {serving cell, PDCCH monitoring occasion}-pairs at the current PDCCH monitoring occasion according to the priority sorting order of Table 1.

[0255] Table 1 is an excerpt from NR TS 38.213 regarding C-DAI.

[0256] In DCI formats, the value of the counter DAI field in the same HARQ-ACK codebook, where each scheduling PDSCH receptions on respective single serving cells with associated HARQ-ACK information, or having associated HARQ-ACK information without scheduling a PDSCH reception, denotes the accumulative number of {serving cell, PDCCH monitoring occasion}-pairs in which a PDSCH reception providing a transmission block with HARQ-ACK information reporting enabled, or a HARQ-ACK information bit existing that is not a response to a PDSCH reception, up to the current serving cell and current PDCCH monitoring occasion. PDSCH receptions that provide transport blocks with enabled HARQ-ACK information report, or HARQ-ACK information bits that are not in response for PDSCH receptions, associated with the DCI formats, excluding the SPS activation DCI,is present up to the current serving cell and current PDCCH monitoring occasion,)- First, if the UE indicates by type2-HARQ-ACK-Codebook support for more than one PDSCH reception on a serving cell that are scheduled from a same PDCCH monitoring occasion, in increasing order of the PDSCH reception starting time for the same {serving cell, PDCCH monitoring occasion} pair,)- Second, in ascending order of serving cell index, (second in ascending order of serving cell index, and)- Third, 0≤m <M인 PDCCH 모니터링 기회 인덱스 m의 오름차순으로. (third in ascending order of PDCCH monitoring occasion index m, where 0≤m<M).동일한 HARQ-ACK 코드북에서, 각각 연관된 HARQ-ACK 정보와 함께 각각의 복수의 서빙 셀들에서 PDSCH 수신을 스케줄링하는 DCI 포맷들에서의 카운터 DAI 필드의 값은, 현재의 복수의 서빙 셀들과 현재 PDCCH 모니터링 기회에 이르기까지 PDSCH 수신이 존재하는 {복수의 서빙 셀들 중 가장 작은 인덱스를 갖는 서빙 셀, PDCCH 모니터링 기회} 쌍의 누적 개수를 나타내며, (A value of the counter DAI field in DCI formats,Each scheduling PDSCH receptions on respective more than one serving cells with associated HARQ-ACK information in the same HARQ-ACK codebook denotes the accumulative number of {serving cell with the smallest index from the more than one serving cells, PDCCH monitoring occasion}-pairs in which PDSCH receptions are present up to the current more than one serving cells and the current PDCCH monitoring occasion,)- First, if the UE indicates by type2-HARQ-ACK-Codebook support for more than one PDSCH receptions on a serving cell that are scheduled from the same PDCCH monitoring occasion, in increasing order of the PDSCH reception starting time for the same {serving cell with the smallest index among the multiple serving cells, PDCCH monitoring occasion} pair, (first, if the UE indicates by type2-HARQ-ACK-Codebook support for more than one PDSCH receptions on a serving cell that are scheduled from the same PDCCH monitoring occasion, in increasing order of the PDSCH reception starting time for the same {serving cell with the smallest index from the more than one serving cells, PDCCH monitoring occasion} pair,)- second,In ascending order of the smallest serving cell index among multiple serving cells (second in ascending order of the smallest serving cell index from the more than one serving cells, and)- third, 0≤m <M인 PDCCH 모니터링 기회 인덱스 m의 오름차순으로 (third in ascending order of PDCCH monitoring occasion index m, where 0≤m<M).,

[0257] First, if the terminal can perform transmission and reception for the scheduled PXSCH when it successfully decodes both the 1st DCI and the 2nd DCI every time as in Case 1, the following DAI signaling method may be considered.

[0258] - DL DAI information may be carried identically in both the 1st DL DCI and the 2nd DL DCI (to increase reliability), or carried in only one of the 1st DL DCI or the 2nd DL DCI, or distributed. As an example of being distributed between the 1st DL DCI and the 2nd DL DCI, if an N-bit DAI was required in the existing DL DCI format, a K-bit DAI (e.g., total DAI) may be transmitted through the 1st DL DCI and a (NK)-bit DAI (e.g., counter-DAI) may be transmitted through the 2nd DL DCI. In this case, the terminal can perform HARQ-ACK codebook construction by combining the DL DAI values ​​of the 1st DL DCI and the 2nd DL DCI.

[0259] - UL DAI information may be carried identically in both the 1st UL DCI and the 2nd UL DCI (to increase reliability), or carried in only one of the 1st UL DCI or the 2nd UL DCI, or distributed. As an example of being distributed between the 1st UL DCI and the 2nd UL DCI, if an N-bit DAI was required in the existing UL DCI format, a K-bit DAI (e.g., total DAI of the first sub-codebook) may be transmitted through the 1st DCI and a (NK)-bit DAI (e.g., total DAI of the second sub-codebook) may be transmitted through the 2nd DCI. In this case, the terminal can perform HARQ-ACK codebook construction by combining the UL DAI values ​​of the 1st UL DCI and the 2nd UL DCI.

[0260] On the other hand, if the terminal succeeds in detecting the 2nd DCI as in Case 2, and can perform transmission and reception for the scheduled PXSCH even without detecting the corresponding 1st DCI for each 2nd DCI detection, the following DAI signaling method may be considered.

[0261] - DL DAI information can be carried only in the 2nd DL DCI, and the terminal can perform HARQ-ACK codebook configuration using the DL DAI value of the 2nd DL DCI.

[0262] - UL DAI information can be carried only in the 2nd UL DCI, and the terminal can perform HARQ-ACK codebook configuration using the UL DAI value of the 2nd UL DCI.

[0263] The counter-DAI value signaled in DL DCI refers to the accumulated value in pairs of serving cell and PDCCH monitoring occasion, and each pair can be counted according to the order defined in Table 1. For convenience, this process is referred to as DAI-counting.

[0264] As such, when a DL DAI is transmitted through the 1st DL DCI and / or 2nd DL DCI, it may be necessary to determine whether DAI-counting should be performed based on the PDCCH monitoring occasion corresponding to which DCI. One or a combination of the following methods may be applied.

[0265] - DAI-counting can be performed based on the PDCCH monitoring occasion when the 1st DL DCI is transmitted. For example, DAI-counting is performed based on the PDCCH MO of the 1st DCI, and the corresponding DAI may be included in at least one of the 1st DCI and / or 2nd DCI.

[0266] - DAI-counting can be performed based on the PDCCH monitoring occasion when the 2nd DL DCI is transmitted. For example, DAI-counting is performed based on the PDCCH MO of the 2nd DCI, and the corresponding DAI may be included in at least one of the 1st DCI and / or 2nd DCI.

[0267] - DAI-counting can be performed based on the PDCCH monitoring occasion of the DL DCI to which the DL DAI value is transmitted. If the DL DAI value is distributed and transmitted to the 1st DL DCI and the 2nd DL DCI, DAI-counting can be performed based on the PDCCH monitoring occasion of one of the DCIs.

[0268] - DAI-counting can be performed based on the PDCCH monitoring occasion of the DL DCI to which the Counter-DAI value is transmitted. If the Counter-DAI value is distributed and transmitted to the 1st DL DCI and the 2nd DL DCI, DAI-counting can be performed based on the PDCCH monitoring occasion of one of the DCIs.

[0269] - Whether DAI-counting can be performed based on the 1st DL DCI or the 2nd DL DCI can be set by higher layer signaling or indicated through DCI / MAC-CE.

[0270] The above DAI signaling method and DAI-counting method can be equally applied to the method proposed below.

[0271] [Proposal #2] In addition to the A / N bit corresponding to PDSCH, provide feedback on whether the 2nd DCI reception was successful.

[0272] When a terminal feeds back a HARQ-ACK for a PDSCH scheduled via 2-step DCI as a NACK, the base station receiving the NACK information cannot distinguish whether the NACK is the result of the terminal missing the 1st / 2nd DCI or the result of a PDSCH decoding failure. If the terminal can distinguish between the success of receiving the 2nd DCI and the success of receiving the PDSCH and inform the base station of this, the base station can use this information to help determine whether to adjust the aggregation level and / or modulation order of the 2nd DCI (in the case of 2nd DCI reception failure) or the RV and / or MCS of the PDSCH (in the case of PDSCH reception failure).

[0273] In addition, 1 bit information can be added to the M HARQ-ACK bit(s) corresponding to a single PDSCH to provide feedback on whether the corresponding 2nd DCI was successfully received. If the 1 bit information is '1' (or '0'), it means that the terminal informs the base station that the 2nd DCI was successfully received, and conversely, if the 1 bit information is '0' (or '1'), it means that the terminal informs the base station that it failed to receive the 2nd DCI. Additionally, the 1 bit can be attached to the front or back of the M HARQ-ACK bit(s).

[0274] (1) Example #1: (In the case of Type-1 HARQ-ACK CB,) with a set of multiple (e.g., K_N) candidate K1 (PDSCH-to-HARQ-ACK slot-level offset) values ​​set, for each K1 value (set in each serving cell), all combinations of PDSCH occasions (SLIVs) that can be transmitted within K1 DL slot(s) prior to the HARQ-ACK transmission slot are calculated, and occasions for receiving candidate PDSCH corresponding to each DL slot are constructed (including determining the position / order of the HARQ-ACK bit corresponding to each SLIV) (this is defined as “SLIV pruning”). For each occasion included in the set of occasions for receiving candidate PDSCH obtained through this process, HARQ-ACK information bit(s) are constructed and concatenated to form the entire HARQ-ACK codebook. At this time, 1 bit can be added (prepend or append) for each occasion for receiving candidate PDSCH to provide feedback on whether the 2nd DCI reception was successful.

[0275] (2) Example #2: (In the case of Type-2 HARQ-ACK CB,) HARQ-ACK information bit(s) are configured for each DAI value (until the corresponding T-DAI value) and concatenated to form a HARQ-ACK codebook or a sub-codebook. At this time, 1 bit can be added (prepend or append) to the PDSCH HARQ-ACK information corresponding to each DAI value to provide feedback on whether the 2nd DCI was successfully received.

[0276] (3) Example #3: (In the case of Type-3 HARQ-ACK CB,) HARQ-ACK information bit(s) are configured for each HARQ process index and concatenated to form a HARQ-ACK codebook or a sub-codebook. At this time, 1 bit can be added (prepend or append) to the PDSCH HARQ-ACK information corresponding to each HARQ process index to provide feedback on whether the 2nd DCI was successfully received.

[0277] When the terminal adds 1 bit as described above, if the corresponding PDSCH is scheduled through a single DCI rather than a 2-step DCI, the added 1 bit may be configured to be identical to a specific bit (e.g., first / last bit) among the M HARQ-ACK bit(s) or configured to a specific value (e.g., '0' or '1').

[0278] When the terminal provides feedback that it failed to receive the 2nd DCI, the corresponding M HARQ-ACK bit(s) can be configured with a specific value (e.g., all zeros or all ones). Alternatively, it may be considered to transmit additional information using the M HARQ-ACK bit(s). For example, whether the 1st DCI was received successfully can be transmitted, and the M HARQ-ACK bit(s) can be configured with all ones if the 1st DCI was received successfully, and the M HARQ-ACK bit(s) can be configured with all zeros if the 1st DCI was not received failed.

[0279] First, regarding the method, if the terminal can perform transmission and reception for the scheduled PXSCH when it successfully decodes both the 1st DCI and the 2nd DCI every time as in Case 1, the DAI signaling method of Proposal #1 above or the following DAI signaling method may be considered.

[0280] - DL DAI information may be included only in the 1st DL DCI. In order to determine the success or failure of the 2nd DCI, it may be desirable to include all DL DAI information (without splitting) in at least the 1st DL DCI.

[0281] On the other hand, regarding the method, if the terminal succeeds in detecting the 2nd DCI as in Case 2, and can perform transmission and reception for the scheduled PXSCH even without detecting the corresponding 1st DCI for each 2nd DCI detection, then the DAI signaling method proposed in Proposal #1 may be applied, or Proposal #2 may not be applied to Case 2.

[0282] The DAI-counting method may be applied using the method proposed in Proposal #1 above.

[0283] In applying this method, the PRI field may be carried in the 1st DCI and / or 2nd DCI. If carried in the 1st DCI, the terminal has the advantage of knowing the PUCCH resources capable of transmitting the success / failure status of the 2nd DCI even if a missing 2nd DCI occurs. If the PRI is carried in the 2nd DCI, the reliability of the 1st DCI can be maximized by minimizing the payload size of the 1st DCI. Carrying the PRI in the 2nd DCI may be limited to cases where a Type-2 HARQ-ACK CB is configured / instructed to the terminal. This is because, while the terminal can determine the success / failure of the 2nd DCI (e.g., whether the terminal missed the 2nd DCI in the past) through the DAI value signaled for Type-2 HARQ-ACK CB, in the case of Type-1 HARQ-ACK CB, the DAI value is not signaled, so it may be difficult to distinguish whether the base station did not transmit the 1st / 2nd DCI or whether the terminal missed the 2nd DCI.

[0284] [Proposal #3] Configure the success status of 1st DCI reception through a separate sub-codebook to provide feedback

[0285] In cases where a terminal can perform transmission and reception for a scheduled PXSCH even if it does not detect the corresponding 1st DCI every time a 2nd DCI is detected, as in Case 2, if the 1st DCI is missed, a misalignment problem may occur between the terminal and the base station regarding the (long term) information transmitted through the 1st DCI. To solve this, we propose a method to provide feedback on whether the reception of the 1st DCI was successful.

[0286] Similar to the method of feedbacking the success or failure of receiving the 2nd DCI in Proposal #2 above, a method of feedbacking the success or failure of receiving the 1st DCI (e.g., a method of feedbacking the success or failure of receiving the 1st DCI in addition to the A / N bit corresponding to PDSCH) may be considered. However, considering that the 1st DCI may be transmitted intermittently compared to the 2nd DCI as in Case 2, a method of feedbacking the success / failure of the 1st DCI by configuring it as a separate sub-codebook may be more efficient.

[0287] (When configuring Type-2 HARQ-ACK CB) Configuring individual / separate sub-codebooks may mean a structure where counter / total-DAI values ​​are determined and signaled independently for each sub-codebook (e.g., the scheduled DCI / PDSCH sequence / total is determined and signaled independently for each sub-codebook). For example, configuring individual sub-codebooks for the 1st DCI and (2nd DCI and) PDSCH may mean a structure where counter / total-DAI values ​​are determined and signaled independently for the 1st DCI and (2nd DCI and) PDSCH, respectively (e.g., the scheduled DCI / PDSCH sequence / total is determined and signaled independently for each DCI format). In other words, it may be a structure where DAI values ​​are determined and signaled only for the 1st DCI(s), and DAI values ​​are determined and signaled only for the (2nd DCI and) PDSCH(s). In addition, a final HARQ-ACK codebook can be constructed by concatenating HARQ-ACK payloads corresponding to different sub-codebooks. Sub-codebook #1, composed of HARQ-ACK information corresponding to the 1st DCI, and sub-codebook #2, composed of HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s), can be created and concatenated (sub-codebook #1 may precede or follow sub-codebook #2).

[0288] (When configuring Type-1 HARQ-ACK CB) Configuring individual / separate sub-codebooks means concatenating each sub-codebook as if it were a separate serving cell. Sub-codebook #1, composed of HARQ-ACK information corresponding to the 1st DCI, and sub-codebook #2, composed of HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s), can be created and concatenated (sub-codebook #1 may precede or follow sub-codebook #2).

[0289] HARQ-ACK information corresponding to the 1st DCI is allocated 1 bit per individual DCI, and if the 1 bit information is '1' (or '0'), it means that the terminal notifies the base station that it has successfully received the 1st DCI, and conversely, if the 1 bit information is '0' (or '1'), it means that the terminal notifies the base station that it has failed to receive the 1st DCI. HARQ-ACK information corresponding to (2nd DCI and) PDSCH(s) can be configured by applying the above Proposal #1 or Proposal #2.

[0290] First, regarding the method, if the terminal can perform transmission and reception for the scheduled PXSCH when it successfully decodes both the 1st DCI and the 2nd DCI every time as in Case 1, the following DAI signaling method may be considered. Alternatively, the proposal #3 may not be applicable in the case of Case 1.

[0291] - DL DAI information may be included individually for the 1st DL DCI and the 2nd DL DCI. The 1st DL DCI may include a 1st DL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI, and the 2nd DL DCI may include a 2nd DL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s). Alternatively, the 2nd DL DCI (or the 1st DL DCI) may include not only the 1st DL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI, but also the 2nd DL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s).

[0292] - UL DAI information may be included only in the 2nd UL DCI. Both the first UL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI and the second UL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s) may be included in the 2nd UL DCI (or the 1st UL DCI). Alternatively, they may be distributed and included in the 1st UL DCI or the 2nd UL DCI. For example, the first UL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI may be included in the 1st UL DCI, and the second UL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s) may be included in the 2nd UL DCI. In this case, the terminal can perform HARQ-ACK codebook configuration by combining the UL DAI values ​​of the 1st UL DCI and the 2nd UL DCI.

[0293] On the other hand, if the terminal succeeds in detecting the 2nd DCI as in Case 2, and can perform transmission and reception for the scheduled PXSCH even without detecting the corresponding 1st DCI for each 2nd DCI detection, the following DAI signaling method may be considered.

[0294] - DL DAI information may be included individually for the 1st DL DCI and the 2nd DL DCI. The 1st DL DCI may include a 1st DL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI, and the 2nd DL DCI may include a 2nd DL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s). Alternatively, the 2nd DL DCI may include not only the 1st DL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI, but also the 2nd DL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s), in which case the 1st DCI may not include a DL DAI value.

[0295] - UL DAI information can be included only in the 2nd UL DCI. Not only the 1st UL DAI value for configuring HARQ-ACK information corresponding to the 1st DCI, but also the 2nd UL DAI value for configuring HARQ-ACK information corresponding to (the 2nd DCI and) PDSCH(s) can all be included in the 2nd UL DCI.

[0296] DAI-counting may be applied using one or a combination of the following methods.

[0297] - DAI-counting based on the PDCCH monitoring occasion where the 1st DL DCI is transmitted, and DAI-counting based on the PDCCH monitoring occasion where the 2nd DL DCI is transmitted can be performed individually.

[0298] [Proposal #4] After separately feeding back ACK / NACK information for the 1st DCI (and / or 2nd DCI) (via PUCH), the base station transmits the next DL signal upon receiving such information.

[0299] When scheduling PXSCH based on 2-step DCI, the probability of DCI missing may increase because the terminal must successfully receive both DCIs. Therefore, according to one embodiment, the terminal may first transmit whether it has successfully received the DCI, and then perform transmission and reception for the scheduled PXSCH.

[0300] Specifically, a terminal allocated a separate PUCCH resource can transmit ACK / NACK information for the 1st DCI (and / or 2nd DCI) through the allocated PUCCH. The PUCCH resource may be linked to an individual (candidate) monitoring occasion or a group of candidate monitoring occasions for the 1st DCI (and / or 2nd DCI). A terminal that has successfully received the 1st DCI (and / or 2nd DCI) can transmit ACK information through the PUCCH resource linked to the monitoring occasion where the DCI was received. In this case, the PUCCH may be ACK-only (a PUCCH resource that transmits only in the case of an ACK). Alternatively, the terminal may attempt to decode the 1st DCI (and / or 2nd DCI) for every (candidate) monitoring occasion and transmit ACK / NACK information regarding the success or failure through the PUCCH resource linked to the corresponding monitoring occasion. Alternatively, the terminal may attempt to decode the 1st DCI (and / or 2nd DCI) at every candidate monitoring occasion and, only if it fails, transmit NACK information through a PUCCH resource associated with the monitoring occasion, in which case the PUCCH may be NACK-only (a PUCCH resource transmitted only when NACK occurs).

[0301] In this way, only when the terminal transmits ACK information via PUCCH, it may receive a PDSCH scheduled via 1st / 2nd DCI or transmit a PUSCH. If the terminal transmits NACK information via PUCCH, it may not perform the corresponding PDSCH reception or PUSCH transmission, or it may ignore the DCI information.

[0302] [Proposal #5] When one or more PXSCHs can be scheduled via 2-step DCI, DAI signaling and HARQ-ACK feedback on the said 2-step DCI

[0303] When one or more PXSCHs can be scheduled through 2-step DCI, specifically, the following methods may be used.

[0304] (i) A method in which a 1st DCI is linked to a single 2nd DCI, and multiple M PXSCHs are scheduled through the single 2nd DCI (named the 1-1-M structure for convenience)

[0305] (ii) A method in which a 1st DCI is linked with multiple M 2nd DCIs, and one PXSCH is scheduled through each 2nd DCI (referred to as a 1-MM structure for convenience)

[0306] (iii) A method in which, as a combination of the two methods above, a 1st DCI is linked with multiple 2nd DCIs, and multiple PXSCHs are scheduled through a single 2nd DCI.

[0307] For convenience, a 2-step DCI that schedules multiple PXSCHs in this way is named M-TB-DCI, and we propose a DAI and PRI signaling method and a HARQ-ACK feedback method for the said M-TB-DCI.

[0308] For example, the following two methods can be considered for a DAI structure (e.g., DAI count method).

[0309] - DAI-Method #1: Define one DAI value per 1st DCI. For example, a DAI value can be counted for every 1st DCI MO.

[0310] - DAI-Method #2: Define one DAI value for each 2nd DCI. For example, a DAI value can be counted for every 2nd DCI MO.

[0311] For example, the following two options can be considered for DAI / PRI signaling (particularly for M-TB-DCI with a 1-MM structure).

[0312] (1) Opt-1: DAI can be included in each 2nd DCI. PRI can be included only in the 1st DCI. In this case, since the number of DAIs / information within the 2nd DCI must be known to construct the HARQ-ACK payload even if the 1st DCI is missed, the terminal can continue to attempt reception (or blink detection) for the 2nd DCI even if scheduled PDSCH reception (or scheduled PUSCH transmission) is omitted when the 1st DCI is missed. This option may be applicable to both Case 1 and Case 2 above. In particular, in the case of Case 2, since the aftermath of missing the 1st DCI will persist for multiple (2nd DCI monitoring) slots (linked to the 1st DCI), HARQ-ACK feedback may be performed only on the previous DCIs (ignoring subsequent DCIs) while missing the 1st DCI.

[0313] (2) Opt-2: DAI can be included only in the 1st DCI. PRI can also be included only in the 1st DCI. In this case, if the 1st DCI is missing, the number of associated 2nd DCIs cannot be accurately determined (if the terminal also misses some 2nd DCIs at the same time), so it may be additionally necessary to signal the number of associated 2nd DCIs through the 1st DCI. When performing DAI-counting, it may be performed based on the PDCCH monitoring occasion when the 2nd DCI is transmitted. If PDSCHs can be scheduled on different cells, DAI-counting may be performed in the order of cell index (e.g., ordering in ascending order from the lowest cell index); if there are multiple PDSCHs on the same cell, in the order of the start timing of each PDSCH (e.g., ordering in ascending order of PDSCH reception starting time); or if PDSCHs can be scheduled on different cells and multiple PDSCHs can be scheduled per cell, in the order of cell index first - start timing second. This option may be applicable only to Case 1 above.

[0314] Opt-1 may be applied when the above DAI-Method #2 (a method of defining one DAI value per 2nd DCI) is used. The terminal can configure a HARQ-ACK CB based on the DAI value carried in the 2nd DCI. Alternatively, if Opt-2 is applied, when there are M 2nd DCIs corresponding to a single 1st DCI, only the DAI value corresponding to the last (or starting) 2nd DCI among the multiple DAI values ​​corresponding to the 2nd DCIs can be signaled at the 1st DCI. In this case, the value M may be a pre-set value or a value indicated through the 1st DCI, and when the 1st DCI indicates that the last DAI value is N, the terminal can recognize that the DAI values ​​corresponding to the M 2nd DCIs linked to the 1st DCI range from N-M+1 to N.

[0315] When Opt-1 is applied in the above DAI-Method #1 (a method defining a single DAI value per 1st DCI), the same DAI value (for the 1st DCI) can be signaled through each 2nd DCI. Alternatively, Opt-2 can be applied. The common DAI value through each 2nd DCI (i.e., when Opt-1 is applied) or the DAI value carried on the 1st DCI (i.e., when Opt-2 is applied) may specifically carry the following DAI values.

[0316] (1) Alt-1: With the maximum number of 2nd DCIs that can be linked to a single 1st DCI set to M, a DAI value between 1st DCIs (e.g., a DAI value obtained by counting the MOs of 1st DCIs) can be signaled to the 2nd DCI (in Opt-1) or the 1st DCI (in Opt-2). Additionally, a DAI value between the corresponding 2nd DCIs (e.g., a DAI value obtained by counting the MOs of 2nd DCIs) can be signaled to each 2nd DCI linked to the 1st DCI. In this case, M HARQ-ACK information (corresponding to M 2nd DCI DAIs) can be configured per 1st DCI.

[0317] (2) Alt-2: (In Opt-1) the 2nd DCI or (In Opt-2) the 1st DCI may be signaled with a DAI value between 1st DCIs (e.g., a DAI value obtained by counting the MOs of 1st DCIs). Additionally, the number of 2nd DCIs (M_act) associated with the 1st DCI may be signaled on the 1st DCI (in Opt-2), and the number of 2nd DCIs (M_act) associated with the 1st DCI may be signaled on the 2nd DCI along with a DAI value between 2nd DCIs (e.g., a DAI value obtained by counting the MOs of 2nd DCIs) associated with the 1st DCI. In this case, M_act HARQ-ACK information may be configured for each 1st DCI (corresponding to M_act 2nd DCI DAIs). However, if both the 1st DCI and the associated 2nd DCIs are missing, the system may operate by 1) constructing / feeding HARQ-ACK only for the previously received 1st DCI / 2nd DCIs, or 2) omitting the entire HARQ-ACK construction / feedback.

[0318] Even if the number of 2nd DCIs linked through the 1st DCI is signaled, if the terminal misses the 1st DCI, a problem may arise where the number of 2nd DCIs linked to the 1st DCI cannot be known (unless additional signaling is introduced to the 2nd DCI), so the above Alt-1 / 2 can be applied to solve this problem.

[0319] Even if M > 1, if the number of PDSCHs actually scheduled through the 2-step DCI is one, the CBs corresponding to the DCIs scheduling a single PDSCH and the CBs corresponding to the DCIs scheduling multiple PDSCHs may be composed of different sub-codebooks. In this case, whether the number of M is 1 or greater than 1 can be determined by a specific field (e.g., TDRA field) or a combination of fields within the 1st DCI and / or 2nd DCI. For example, when scheduling a single PDSCH through a 2-step DCI and / or a single DCI, a sub-codebook #1 is created with HARQ-ACK information corresponding to the DCIs (or based on the DAI value for the DCIs), and when scheduling multiple PDSCHs through a 2-step DCI (and / or a single DCI), a sub-codebook #2 is created with HARQ-ACK information corresponding to the DCIs (or based on the DAI value for the DCIs) and concatenated (sub-codebook #1 may precede or follow sub-codebook #2).

[0320] In a situation where both the DAI and PRI fields are indicated as the 1st DCI (as in the Opt-2 above), if the terminal receives the 1st DCI containing the last (counter-)DAI value but fails to receive the corresponding 2nd DCI (or the corresponding 2nd DCI is missing), the terminal may apply one of the following feedback methods. When the terminal receives multiple DCIs scheduled to carry HARQ-ACK information on a PUCCH belonging to the same (sub-)slot, the last (counter-)DAI value (calculated by applying the DAI counting method described above) among the multiple DAI values ​​indicated from the DCIs may be named the last (counter-)DAI value.

[0321] (1) Feedback Method #1: Feedback the entire codebook information, including HARQ-ACK information (e.g., filled with NACK) for the corresponding last DAI.

[0322] (2) Feedback Method #2: Feedback only up to the DAI that excludes the HARQ-ACK information for the corresponding last DAI (e.g., the DAI corresponding to the last DCI for which not only the 1st DCI but also the 2nd DCI was received).

[0323] One of the above feedback methods may be applied even in a situation where only one of the DAI and PRI fields is indicated as the 1st DCI and the other field is indicated as the 2nd DCI. However, considering that the DAI and PRI fields are distributed and indicated as different DCIs, in such a situation (where only one of the DAI and PRI fields is indicated as the 1st DCI and the other field is indicated as the 2nd DCI), if only the 1st DCI is received for the last (counter-)DAI and only the 2nd DCI is missed, it may be more stable to apply feedback method #2.

[0324] This method can be applied when the value of M is 1 or greater than 1.

[0325] According to one embodiment of the present disclosure, when one or more PDSCH / PUSCH(s) can be scheduled through a plurality of DCIs (or 2-step DCIs), a stable scheduling method can be supported by supporting a HARQ-ACK feedback method corresponding to the DCIs.

[0326] FIG. 16 is a diagram illustrating the operation of a terminal and a base station according to one embodiment. For example, the terminal may receive 1st DCI and 2nd DCI from the base station to receive PDSCH scheduling information and perform reception for the corresponding PDSCH. By applying the proposed methods, the terminal may generate a HARQ-ACK codebook corresponding to the DCI and / or PDSCH and feed it back to the base station.

[0327] Referring to FIG. 16, the terminal may receive at least one upper layer signaling (e.g., RRC signaling) from the base station (A05). The upper layer signaling may include configuration information for receiving PDCCH / DCI, e.g., CORESET configuration information, Search Space set configuration information. The upper layer signaling may include configuration information for PDSCH and / or configuration information for PUSCH / PUCCH. The upper layer signaling may include information for HARQ-ACK codebook configuration and transmission.

[0328] The terminal can monitor the first PDCCH candidates and receive the first DCI among the 2-step DCIs (A10).

[0329] The terminal can monitor the second PDCCH candidates and receive the second DCI among the 2 step DCIs (A15).

[0330] At least one PDSCH and / or at least one PUSCH may be scheduled based on the first DCI and the second DCI. For convenience, the configuration is set assuming the case where PDSCH(s) are scheduled.

[0331] The terminal can obtain at least one DL DAI based on at least one of the first DCI and the second DCI.

[0332] The terminal can receive PDSCH(s) based on the first DCI and the second DCI (A20).

[0333] Based on at least one acquired DL DAI, the terminal can generate a HARQ-ACK codebook containing HARQ-ACK(s) for PDSCH(s) (A25).

[0334] The terminal can transmit the HARQ-ACK codebook to the base station (A30).

[0335] At least one DL DAI can be counted based on at least one of the first PDCCH MO (monitoring occasion) related to the first DCI or the second PDCCH MO related to the second DCI.

[0336] At least one DL DAI may be related to at least one of Total-DAI and Counter-DAI.

[0337] The HARQ-ACK codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0338] A HARQ-ACK codebook may be constructed based on the concatenation of a first sub-codebook and at least one second sub-codebook. The first sub-codebook includes HARQ-ACKs for PDSCH(s), and at least one second sub-codebook may include HARQ-ACKs for at least one of a first DCI or a second DCI.

[0339] FIG. 17 illustrates the flow of a method performed by a terminal according to one embodiment. FIG. 17 is an embodiment relating to at least some of the proposals described above, and the description of the proposals may be referenced without separate mention.

[0340] Referring to FIG. 17, the terminal can receive the first DCI (downlink control information) through the first PDCCH (physical downlink control channel) (B05).

[0341] The terminal can receive the second DCI through the second PDCCH (B10).

[0342] Based on the first DCI and the second DCI, the terminal can receive at least one downlink signal or transmit at least one uplink signal (B15).

[0343] The above terminal can obtain a DAI (downlink assignment index) based on at least one of the first DCI or the second DCI.

[0344] The above DAI can be counted based on at least one of the first PDCCH MO (monitoring occasion) related to the first DCI or the second PDCCH MO related to the second DCI.

[0345] The above DAI can be counted based on the PDCCH MO related to the DCI containing the DAI among the above first DCI and the above second DCI.

[0346] The first DCI may include a part of the DAI, and the second DCI may include the remaining part of the DAI.

[0347] A portion of the above DAI is related to Total-DAI, and the remaining portion of the above DAI may be related to Counter-DAI.

[0348] The terminal may transmit a HARQ-ACK (hybrid automatic repeat request-acknowledgement) codebook based on the DAI. The HARQ-ACK codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0349] The above HARQ-ACK codebook may be configured based on the concatenation of a first sub-codebook and at least one second sub-codebook. The first sub-codebook includes a HARQ-ACK for the at least one downlink signal, and the at least one second sub-codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0350] The above DAI may include a first DAI and a second DAI. The first DAI may be included in the first DCI. The second DAI may be included in the second DCI.

[0351] A second subcodebook including a HARQ-ACK for the first DCI can be determined based on the first DAI.

[0352] A second subcodebook including a HARQ-ACK for the second DCI can be determined based on the second DAI.

[0353] The above HARQ-ACK codebook can be transmitted via a PUCCH (physical uplink control channel) resource. The PUCCH resource can be determined based on PRI (PUCCH resource indicator) information included in at least one of the first DCI or the second DCI.

[0354] The first DCI and the second DCI may be DCIs of a 2-step DCI. The at least one downlink signal may be at least one PDSCH (physical downlink shared channel). The at least one uplink signal may be at least one PUSCH (physical uplink shared channel).

[0355] FIG. 18 illustrates the flow of a method performed by a base station according to one embodiment. FIG. 18 is an embodiment relating to at least some of the proposals described above, and the description of the proposals may be referenced without separate mention.

[0356] Referring to FIG. 18, the base station can transmit the first DCI (downlink control information) to the terminal through the first PDCCH (physical downlink control channel) (C05).

[0357] The base station can transmit the second DCI to the terminal through the second PDCCH (C10).

[0358] Based on the first DCI and the second DCI, the base station can transmit at least one downlink signal or receive at least one uplink signal (C15).

[0359] The base station may provide a DAI (downlink assignment index) to the terminal based on at least one of the first DCI or the second DCI.

[0360] The above DAI can be counted based on at least one of the first PDCCH MO (monitoring occasion) related to the first DCI or the second PDCCH MO related to the second DCI.

[0361] The above DAI can be counted based on the PDCCH MO related to the DCI containing the DAI among the above first DCI and the above second DCI.

[0362] The first DCI may include a part of the DAI, and the second DCI may include the remaining part of the DAI.

[0363] A portion of the above DAI is related to Total-DAI, and the remaining portion of the above DAI may be related to Counter-DAI.

[0364] The base station may receive a HARQ-ACK (hybrid automatic repeat request-acknowledgement) codebook configured based on the DAI. The HARQ-ACK codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0365] The above HARQ-ACK codebook may be configured based on the concatenation of a first sub-codebook and at least one second sub-codebook. The first sub-codebook includes a HARQ-ACK for the at least one downlink signal, and the at least one second sub-codebook may include a HARQ-ACK for at least one of the first DCI or the second DCI.

[0366] The above DAI may include a first DAI and a second DAI. The first DAI may be included in the first DCI. The second DAI may be included in the second DCI.

[0367] A second subcodebook including a HARQ-ACK for the first DCI can be determined based on the first DAI.

[0368] A second subcodebook including a HARQ-ACK for the second DCI can be determined based on the second DAI.

[0369] The above HARQ-ACK codebook can be received through a PUCCH (physical uplink control channel) resource. The above PUCCH resource can be determined based on PRI (PUCCH resource indicator) information included in at least one of the first DCI or the second DCI.

[0370] The first DCI and the second DCI may be DCIs of a 2-step DCI. The at least one downlink signal may be at least one PDSCH (physical downlink shared channel). The at least one uplink signal may be at least one PUSCH (physical uplink shared channel).

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

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

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

Claims

In a method performed by a terminal, Receive the first DCI (downlink control information) through the first PDCCH (physical downlink control channel); Receive the second DCI through the second PDCCH; and Based on the first DCI and the second DCI, it includes receiving at least one downlink signal or transmitting at least one uplink signal, and A method in which the above terminal obtains a DAI (downlink assignment index) based on at least one of the first DCI or the second DCI. In Article 1, A method in which the above DAI is counted based on at least one of a first PDCCH MO (monitoring occasion) related to the first DCI or a second PDCCH MO related to the second DCI. In Article 2, A method in which the above DAI is counted based on the PDCCH MO related to the DCI containing the DAI among the first DCI and the second DCI. In Article 1, A method in which the first DCI comprises a portion of the DAI, and the second DCI comprises the remainder of the DAI. In Article 4, A method in which a portion of the above DAI is related to Total-DAI and the remainder of the above DAI is related to Counter-DAI. In Article 1, It further includes transmitting a HARQ-ACK (hybrid automatic repeat request-acknowledgement) codebook based on the above DAI, and A method in which the above HARQ-ACK codebook includes a HARQ-ACK for at least one of the first DCI or the second DCI. In Article 6, The above HARQ-ACK codebook is constructed based on the concatenation of a first sub-codebook and at least one second sub-codebook, and The first subcodebook above includes a HARQ-ACK for the at least one downlink signal, and A method in which at least one second subcodebook comprises a HARQ-ACK for at least one of the first DCI or the second DCI. In Article 7, The above DAI includes a first DAI and a second DAI, the first DAI is included in the first DCI, and the second DAI is included in the second DCI, and A second subcodebook including a HARQ-ACK for the first DCI is determined based on the first DAI, and A method in which a second subcodebook including a HARQ-ACK for the second DCI is determined based on the second DAI. In Article 6, The above HARQ-ACK codebook is transmitted via the PUCCH (physical uplink control channel) resource, and A method in which the above PUCCH resource is determined based on PRI (PUCCH resource indicator) information included in at least one of the first DCI or the second DCI. In Article 1, The above first DCI and the above second DCI are DCIs of the 2-step DCI, and The above at least one downlink signal is at least one PDSCH (physical downlink shared channel), and A method in which at least one uplink signal is at least one PUSCH (physical uplink shared channel). A computer-readable non-transitory recording medium storing a program for performing the method described in claim 1. 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 the first DCI (downlink control information) through the first PDCCH (physical downlink control channel); Receive the second DCI through the second PDCCH; and Based on the first DCI and the second DCI, it includes receiving at least one downlink signal or transmitting at least one uplink signal, and The above device is a device that obtains a DAI (downlink assignment index) based on at least one of the first DCI or the second DCI. In Article 12, The above device is a device that is a terminal including a transceiver or a processing device configured to control the terminal. In a method performed by a base station, Transmit the first DCI (downlink control information) to the terminal through the first PDCCH (physical downlink control channel); Transmitting the second DCI to the terminal via the second PDCCH; and Based on the first DCI and the second DCI, the method includes transmitting at least one downlink signal or receiving at least one uplink signal, and A method in which the base station provides a DAI (downlink assignment index) to the terminal based on at least one of the first DCI or the second DCI. In the case of a base station, 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 the first DCI (downlink control information) to the terminal through the first PDCCH (physical downlink control channel); Transmitting the second DCI to the terminal via the second PDCCH; and Based on the first DCI and the second DCI, the method includes transmitting at least one downlink signal or receiving at least one uplink signal, and The base station provides a DAI (downlink assignment index) to the terminal based on at least one of the first DCI or the second DCI.

Images