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

Abstract

According to an embodiment of the present disclosure, a terminal may: receive at least one or two pieces of downlink control information (DCI); receive at least one or two physical downlink shared channels (PDSCHs) on the basis of the at least one or two pieces of DCI; and transmit a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook including HARQ-ACK information about the at least one or two PDSCHs, wherein the at least one or two pieces of DCI include at least one of first DCI for scheduling a PDSCH of the terminal and second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the terminal, the second DCI includes terminal-common downlink assignment index (DAI) information, the HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI or a second HARQ-ACK sub-codebook related to the second DCI, and the second HARQ-ACK sub-codebook may be determined on the basis of the terminal-common DAI information.

Description

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

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for transmitting or receiving an uplink or downlink signal between a terminal or a network in a wireless communication system.

[0002] The 5G mobile communications system, the successor to LTE (long-term evolution), is a new, clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, 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. 6G mobile communications systems are being developed based on the underlying technologies of 5G mobile communications.

[0003] NR introduces DCI for multi-PDSCH scheduling and a corresponding HARQ-ACK codebook. For multi-PDSCH scheduling, each row of the TDRA table for PDSCH time resources can be configured via RRC to include multiple SLIVs. When the TDRA field of the DCI indicates a row containing multiple SLIVs, the UE receives multiple PDSCHs using the indicated multiple SLIVs and transmits a corresponding HARQ-ACK.

[0004] DCI for such multi-PDSCH scheduling is limited to unicast transmission for one UE, and DCI for simultaneous scheduling of multiple PDSCHs for multiple UEs is not supported.

[0005] The technical task of the present disclosure is to provide a method and a device for efficiently performing a wireless signal transmission and reception process. For example, a method for transmitting and receiving DCI for scheduling multiple PDSCHs for multiple UEs and its configuration may be provided. In addition, a method for transmitting and receiving a HARQ-ACK codebook between a UE and a base station and its configuration may be provided when DCI scheduling multiple PDSCHs for multiple UEs is received.

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

[0007] According to one aspect of the present disclosure, a method performed by a terminal comprises: receiving one or more DCIs (downlink control information); receiving one or more PDSCHs (physical downlink shared channels) based on the one or more DCIs; And transmitting a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for the one or more PDSCHs, wherein the one or more DCIs include at least one of a first DCI for scheduling a PDSCH of the terminal or a second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the terminal, the second DCI including terminal common downlink assignment index (DAI) information, and the HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, and the second HARQ-ACK sub-codebook can be determined based on the terminal common DAI information.

[0008] The terminal may map NACK (Negative-ACK) to a specific HARQ-ACK bit within the second HARQ-ACK sub-codebook based on the fact that the plurality of PDSCHs scheduled through the second DCI do not include a PDSCH allocated to the terminal.

[0009] The above specific HARQ-ACK bit may be a HARQ-ACK bit linked to the terminal common DAI information.

[0010] The first DCI may include DAI information related to at least one of C-DAI (counter-DAI) or T-DAI (total-DAI). The DAI information included in the first DCI and the terminal common DAI information included in the second DCI may be counted independently of each other.

[0011] The first DCI may be received based on a first radio network temporary identifier (RNTI) specific to the terminal, and the second DCI may be received based on a second RNTI common to the plurality of terminals.

[0012] The above HARQ-ACK codebook can be generated based on the concatenation of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0013] The same type of HARQ-ACK codebook can be set for the above multiple terminals.

[0014] The above terminal common DAI information may be common to terminals for which the Type 2 HARQ-ACK codebook is set among the Type 1 HARQ-ACK codebook and the Type 2 HARQ-ACK codebook.

[0015] The first HARQ-ACK sub-codebook may be configured for PDSCH opportunities determined based on a first time domain resource allocation (TDRA) table related to the first DCI, and the second HARQ-ACK sub-codebook may be configured for PDSCH opportunities determined based on a second TDRA table related to the second DCI.

[0016] A row of the second TDRA table may include a plurality of SLIVs (slot length indication values) for the plurality of terminals.

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

[0018] According to another aspect of the present disclosure, a device 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 one or more downlink control information (DCI); receiving one or more physical downlink shared channel (PDSCH) based on the one or more DCIs; And transmitting a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for the one or more PDSCHs, wherein the one or more DCIs include at least one of a first DCI for scheduling a PDSCH of the device or a second DCI for scheduling a plurality of PDSCHs for a plurality of devices including the device, wherein the second DCI includes device common downlink assignment index (DAI) information, and the HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, wherein the second HARQ-ACK sub-codebook can be determined based on the device common DAI information.

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

[0020] According to another aspect of the present disclosure, a method performed by a base station comprises: transmitting one or more downlink control information (DCI); transmitting one or more physical downlink shared channel (PDSCH) related to the one or more DCI; And receiving a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for the one or more PDSCHs, wherein the one or more DCIs include at least one of a first DCI for scheduling a PDSCH of a first terminal or a second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the first terminal, wherein the second DCI includes terminal-common downlink assignment index (DAI) information, and the HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, wherein the second HARQ-ACK sub-codebook can be determined based on the terminal-common DAI information.

[0021] According to another aspect of the present disclosure, a base station 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 one or more downlink control information (DCI); transmitting one or more physical downlink shared channel (PDSCH) related to the one or more DCIs; And receiving a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for the one or more PDSCHs, wherein the one or more DCIs include at least one of a first DCI for scheduling a PDSCH of a first terminal or a second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the first terminal, wherein the second DCI includes terminal-common downlink assignment index (DAI) information, and the HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, wherein the second HARQ-ACK sub-codebook can be determined based on the terminal-common DAI information.

[0022] According to the present disclosure, signal transmission and reception can be efficiently performed in a wireless communication system. According to one embodiment, by scheduling multiple PDSCHs of multiple UEs together through a single DCI, the overhead of DCI signaling can be reduced, and operation can be performed more efficiently in terms of resources and energy. Furthermore, according to one embodiment, HARQ-ACK for PDSCHs received in a simultaneous scheduling scheme for multiple UEs can be reported together with existing HARQ-ACKs, thereby enabling more efficient HARQ-ACK feedback.

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

[0024] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

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

[0026] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

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

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

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

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

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

[0032] Figure 9 illustrates a beam management procedure applicable to the present disclosure.

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

[0034] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present specification.

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

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

[0037] Figure 14 illustrates a PUSCH transmission process.

[0038] FIG. 15 is a diagram for explaining the operation of a base station and a terminal according to one embodiment.

[0039] FIG. 16 is a diagram for explaining PDSCH scheduling through S-UE DCI / M-UE DCI and HARQ-ACK codebook generation therefor according to one embodiment.

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

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

[0042] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0043] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0044] 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 identically to "at least one of A and B".

[0045] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0046] Additionally, parentheses used herein may mean "for example." Specifically, when "control information (ABC)" is indicated, "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." Furthermore, even when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0047] Additionally, in this specification, terms such as “first,” “second,” etc. are used only for the purpose of distinguishing one component from another component and are not used to limit the components, and do not limit the order or importance between 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 similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0048] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

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

[0050] In this specification, a terminal is a user equipment (UE) or a consumer-side device, and may also be referred to as a base station / second node / IAB node / first node that receives / transmits signals from / to a Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to an endpoint on the user side, or may correspond to an intermediate point between other endpoints. In communication between two points that are 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 node with a fixed location, or a node with an unfixed location (or mobile).

[0051] In this specification, a base station (BS) is a device on the network side, and may also be called a second node / IAB node / x-NodeB (x-NodeB, x may be an abbreviation related to radio access technology (RAT)) / Transmission-Reception Point (TRP). A BS may correspond to a physical node or a logical node. A BS may correspond to an endpoint on the network side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a BS may correspond to a serving node. A BS may be a node with a fixed location, or a node with an unfixed location.

[0052] In this specification, higher layer parameters may be set for the terminal, preset, or predefined. For example, the base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capabilities to the base station as higher layer parameters. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0053] In this specification, the information / state / parameter being “configured or pre-configured” can be interpreted as the information / state / parameter being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, the information / state / parameter being “defined or pre-defined” can be interpreted as the information / state / parameter being known in advance or pre-stored at the base station and the terminal without signaling between the base station and the terminal.

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

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

[0056] <Symbols, Abbreviations, Terms>

[0057] - PDCCH: Physical Downlink Control CHannel

[0058] - DCI: Downlink Control Information

[0059] - PDSCH: Physical Downlink Shared CHannel

[0060] - PUSCH: Physical Uplink Shared CHannel

[0061] - CSI: Channel state information

[0062] - RRM: Radio resource management

[0063] - SCS: Sub-carrier spacing

[0064] - RLM: Radio link monitoring

[0065] - DCI: Downlink Control Information

[0066] - CAP: Channel Access Procedure

[0067] - Ucell: Unlicensed cell

[0068] - TBS: Transport Block Size

[0069] - TDRA: Time Domain Resource Allocation

[0070] - TDRA (Time domain resource assignment) table: Consists of multiple {K0, SLIV, mapping type} combinations (set as RRC) (one combination is mapped to each of the multiple rows in the table), and a specific row is indicated through DCI.

[0071] - K0 (DL assignment-to-PDSCH offset): Slot interval between DCI transmission slot and PDSCH transmission slot (scheduled from the corresponding DCI)

[0072] - SLIV: Starting and Length Indicator Value (This is an indicator value for the starting symbol index and number of symbols within the slot of the PDSCH and / or PUSCH, and can be set as a component of an entry that constitutes the TDRA field within the PDCCH that schedules the corresponding PDSCH and / or PUSCH.) (e.g., SLIV can correspond to a PDSCH / PUSCH occasion)

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

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

[0075] - BWP: BandWidth Part (can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). In addition, multiple BWPs can be configured on one carrier (the number of BWPs per carrier can also be limited), but the number of activated BWPs can be limited to a part of it (e.g., 1) per carrier.)

[0076] - CORESET: COntrol REsourse SET (refers to the time-frequency resource area where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0077] - REG: Resource element group

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

[0079] - COT: Channel occupancy time

[0080] - SPS: Semi-persistent scheduling

[0081] - QCL: Quasi-Co-Location (QCL relationship between two reference signals means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and Spatial Rx parameter obtained from one reference signal can be applied to another reference signal (or antenna port(s) of the corresponding RS). In the NR system, 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 any 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). (can be set as a reference for)

[0082] - TCI: Transmission Configuration Indication (A TCI state includes the QCL relationship 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 the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC CE, and the TCI state setting for each TCI state index is set through RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in future releases, setting between DL RS and UL RS or UL RS and UL RS may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0083] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields in the DCI that schedules the PUSCH. When transmitting a PUSCH, the UE can transmit the PUSCH using the same spatial domain transmission filter used for transmitting and receiving the reference signal linked to the corresponding SRS resource. At this time, the reference RS is set by RRC signaling through the SRS-SpatialRelationInfo parameter for each SRS resource, and SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0084] - TRP: Transmission and Reception Point

[0085] - TAG: Timing advance group

[0086] - PLMN: Public Land Mobile Network

[0087] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0088] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as IAB nodes, relays, and RF repeaters, as illustrated in the example in Figure 1, may be applied, or NTNs 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, or in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, while a network-controlled repeater may not only amplify and forward signals but also adjust transmission and reception settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

[0089] Referring to Figure 1, a split RAN can support the division of a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DUs, various intermediate points can be introduced to compensate for this.

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

[0091] In some examples of this specification, the description of a terminal can be equally applied not only to a user-side endpoint, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side endpoint. Similarly, in some examples of this specification, the description of a base station can be equally applied not only to a network-side endpoint, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side endpoint. However, in most cases where there is no additional description of the operations of three or more entities, the communicating entities in this specification are briefly described as terminals and / or base stations (or first nodes and / or second nodes), and the terms terminal and / or base stations (or first nodes and / or second nodes) are interpreted to include / replace any endpoint or any intermediate point in relation to other nodes.

[0092] That is, in some examples of this specification, for the sake of simplicity of explanation, the subjects of the operation may be referred to as a base station and / or a terminal (or a first node and / or a second node). In addition, the terms base station and / or terminal (or a first node and / or a second node) may also be interpreted / replaced as in the following examples: For example, the base station (or a first node) and the terminal (or a second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

[0093] In this specification, there may be zero or more intermediate points between the base station and the terminal. If intermediate points exist, they may be IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. An intermediate point may be a node with a fixed location or a node with an unfixed location.

[0094] Figure 2 illustrates a communication system applicable to the present disclosure.

[0095] 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 a wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G), and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Things) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may act as a network device (120) to another wireless device (110).

[0096] Wireless devices (110a to 110f) can be connected to a network (130) via a network device (120). AI technology can be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR), or a 6G network. The wireless devices (110a to 110f) can communicate with each other via the network device (120) / network (130), but can also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Additionally, IoT devices (110f) (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (110a to 110f).

[0097] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120), network devices (120) / network devices (120). Here, the wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless device and the network device / wireless device, and the network device and the network device can transmit / receive wireless signals to each other. For example, the wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various descriptions of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.

[0098] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0099] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).

[0100] The processor (202) controls the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including second information / signal via the transceiver (206), and then store information obtained from signal processing of the second information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may store software code including instructions for performing some or all of the processes controlled by the processor (202), or for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via at least one antenna (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF (radio frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0101] Hereinafter, the hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., a functional layer such as physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor (202) may generate at least one Protocol Data Unit (PDU) and / or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) may generate a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) can generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document.

[0102] At least one processor (202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The at least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in the at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be included in the at least one processor (202), or may be stored in at least one memory (204) and driven by the at least one processor (202). The descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

[0103] At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and / or a combination thereof. The at least one memory (204) can be located internally and / or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.

[0104] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. In addition, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts 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).For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

[0107] For example, the device may be a portable device such as a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., an audio input / output port, a video input / output port), and an input / output unit for inputting and outputting image information / signals, audio information / signals, data, and / or information input from a user.

[0108] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting, and a position measurement unit that obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

[0109] For example, the device may be an XR device such as an HMD, a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.

[0110] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc. types depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a driving unit that performs various physical actions, such as moving the robot joints.

[0111] For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcasting terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, digital signage, a robot, a vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a training unit that trains a model composed of an artificial neural network using learning data.

[0112] The structure of the wireless device illustrated in FIG. 3 may be understood as a part of a terminal (or first node), or as a part of an intermediate point, or as a part of a base station (or second node). If the device illustrated in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communications. However, if the front haul and / or back haul communications are based on wireless communications, at least one transceiver (206) illustrated in FIG. 3 may be used for front haul and / or back haul communications, and a wired transceiver may not be included.

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

[0114] The second node of FIG. 4 supports dynamic spectrum sharing (DSS), which can provide connectivity to both nodes implementing 6G technology and nodes implementing pre-6G wireless communication technologies (e.g., 5G, 4G). That is, the first node of FIG. 4 can implement either 6G technology or pre-6G wireless communication technologies (e.g., 5G, 4G). Furthermore, the first node and / or the second node can support full duplex mode as well as non-overlapping full duplex mode.

[0115] 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 operations of the terminal (110) and the base station (120) transmitting and / or receiving data and operations performed prior thereto are illustrated. However, the operations of Fig. 4 are not limited to operations between the terminal and the base station, and may be interpreted as operations between the first node and the second node. In addition, although Fig. 4 illustrates direct wireless signal transmission and reception operations between the terminal (110) and the base station (120), one or more intermediate points may exist between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0116] 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 connection to at least one base station transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals classified according to structure or purpose (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 confirm the boundary of a unit (e.g., a frame, a subframe, a slot, and / or a symbol) constituting a wireless signal transmission of the base station (120) and obtain information (e.g., a cell identifier) ​​about the base station (120).

[0117] The terminal (110) can obtain system information transmitted from the base station (120) (403). The system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., channel used, whether provided on-demand), etc., and can be classified into, for example, first system information (e.g., master information block (MIB), primary system information), second system information (e.g., system information block (SIB), secondary system information), etc. If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. However, the request and provision of system information can be performed after the random access procedure described below.

[0118] The terminal (110) and the base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for the random access procedure based on information related to a channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., a preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., an RAR message, MSG2), transmit a third message (e.g., MSG3) including 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 and third messages may be sent and received as one message, or the second and fourth messages may be sent and received as one message.

[0119] 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 a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0120] 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, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on 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, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0121] <6G System Core Technologies>

[0122] The 6G (wireless) system aims to provide (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0123] As core implementation technologies of the 6G system, 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.

[0124] artificial intelligence

[0125] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

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

[0127] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

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

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

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

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

[0132] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified by the network, and the network can direct the activation / deactivation / fallback / switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified by the network, and the network / terminal can activate / deactivate / select / switch AI / ML models based on the model ID.

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

[0134] In particular, Figure 5 illustrates a general functional architecture relevant to both Functionality-based LCM and Model-based LCM. Some of the functions or some of the data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.

[0135] Referring to FIG. 5, a general functional framework can 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).

[0136] 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) can perform data preparation based on raw data and 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.) or may be performed by multiple entities.

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

[0138] 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. 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) transferred from the Data Collection function (10), if necessary.

[0139] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to pass a trained, validated and tested AI / ML model to the Model Storage function (50) or to pass an updated version of the model to the Model Storage function (50).

[0140] The Management function (30) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the Management function (30) may perform 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)).

[0141] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include selection / (de)activation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (i.e., not relying on the inference process).

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

[0143] A Performance Feedback / Retraining Request (31) refers to information required as input to the Model Training function (20) (e.g., for the purpose of (re)training or updating the model).

[0144] 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 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 Data Collection (10). If necessary, the Inference function (40) may also perform data preparation (e.g., data preprocessing and cleaning, forming, and transformation) based on the Inference Data (13) provided by Data Collection function (10).

[0145] 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 the AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0146] The Model Storage function (50) stores a learned / updated model that can be used to perform the Inference function (40). The Model Storage function (50) illustrated in FIG. 5 can be used as a reference point (if any) when applicable to protocol termination, model transmission / delivery, and related processes. Furthermore, the Model Storage function (50) is merely an example and is not intended to limit the storage location of actual AI / ML models, and may be omitted.

[0147] Model Transfer / Delivery (51) is used to transfer AI / ML models to inference functions.

[0148] The level of cooperation can be defined as follows depending on the capability of AI / ML functions between multiple nodes, and variations due to combination of multiple levels or separation of any one level are also possible.

[0149] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0150] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

[0151] Category 1) involves inter-node support to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from another node (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0152] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0153] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and not all functions and / or all data / information / command signals illustrated in FIG. 5 may be performed within a specific node, but only some of them may be performed.

[0154] AI / ML models can be divided 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.

[0155] A one-side model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by a single node. AI / ML model training and inference can be performed by the same node, or they can be performed by separate nodes.

[0156] 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 refers to inference being performed jointly across multiple nodes. For example, the first part of the inference may be performed by a first node, and the remaining part by a second node. Two-side models can be categorized into several types depending on the training method of the AI / ML model, as follows:

[0157] - First type: AI / ML models 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 / objects.

[0158] - 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 part) and model reconstruction (CSI compression by sub-use case) 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).

[0159] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., networks and terminals). Separate training may mean that training begins sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

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

[0161] The operations described below can be described / interpreted based on the AI / ML model proposed in this specification, as shown in Fig. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for the AI / ML model). In addition, unless specifically limited, the AI / ML model can correspond to a one-side model in which inference is entirely performed by a single node, or a two-side model in which joint inference is performed by multiple nodes.

[0162] First signaling (601): In the description below, 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., generation and / or reconstruction) the AI / ML model of FIG. 5, or correspond to inference data used for inference of the AI / ML model, or correspond to feedback for the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present specification, the first signaling (601) may be omitted. If a one-side model is used in the present specification, the one-way / two-way signaling (set) in the present specification may correspond to the signaling of the first signaling (601). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the first signaling (601), and also, a repetitive signaling operation may correspond to the first signaling (601).

[0163] For example, in AI / ML model-based beam management (BM), if a base station predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from a terminal. Furthermore, if a terminal predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0164] AI / ML model-based operation (602): In the description below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., terminal, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in 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 if not mentioned separately. For example, it may correspond to training (i.e., generation and / or reconstruction) of the AI / ML model of FIG. 5 or inference of the AI / ML model, etc. When a one-side model is used, an operation performed by a single node in the present specification may correspond to an AI / ML model-based operation (602), and also, when a two-side model is used, a joint operation performed by multiple nodes in the present specification may correspond to an AI / ML model-based operation (602).

[0165] For example, in an AI / ML model-based BM, the base station can use quality / intensity information for multiple beams received from the terminal as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the terminal can measure multiple beams received from the base station and use the measurement results as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model.

[0166] Second signaling (603): In the description below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as a second signaling (603) or a set of signaling generated due to (as a result of) an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to an output resulting from inference of the AI / ML model in 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, a one-way / two-way signaling (set) in this specification may correspond to the second signaling (603). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the second signaling (603), and also, a repetitive signaling operation may correspond to the second signaling (603).

[0167] For example, in an AI / ML model-based BM, the base station can transmit to the terminal the beam(s) predicted based on the AI / ML model as candidates so that the terminal can determine the optimal beam. Furthermore, the terminal can report to the base station the beam(s) predicted based on the AI / ML model to request the base station to transmit the candidate beams as candidates for determining the optimal beam.

[0168] THz communication (terahertz communication)

[0169] Data rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0170] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0171] Transmitting system information (i.e., information related to the properties, characteristics, and / or capabilities of a BS required to use a service, such as MIB, SIB, etc.) in the THz frequency band may be inefficient because, as the beam width becomes narrower in high frequency bands, more beam sweeps must be performed to cover the entire area of ​​the cell. 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 such as that illustrated in FIG. 8 may be used.

[0172] Figure 8 illustrates an example of a procedure for transmitting system information for THz communications to which the present disclosure applies. While this example was developed with THz in mind, it is also applicable to 6G communication environments where THz is not applicable. Furthermore, the procedure illustrated in Figure 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Figure 8.

[0173] 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 a THz frequency band, and cell #2 uses a non-THz frequency band. Here, the system information can include at least one information / state / parameter / setting generated in each of a higher layer and a physical layer. For example, the at least one information / state / parameter / setting generated in the higher layer can include at least one of an 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 the at least one information / state / parameter / setting generated in the physical layer can include at least one of an SFN, a half frame indicator, and an SSB index. However, this is merely an example, and system information may include information / status / parameters / settings related to Cell #1 / Cell #2 generated from various types of physical layers / upper layers. For this purpose, as an example, Cell #1 and Cell #2 may have a relationship as a secondary cell and a primary cell.

[0174] The UE can acquire synchronization for cell #1 (803). Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information. However, since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the UE can acquire synchronization based on the system information. However, unlike FIG. 8, in another example, synchronization acquisition can be performed before step 801.

[0175] The UE may transmit a signal for accessing cell #1 (805). For example, the signal may include information for accessing cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) may be identified through system information. Thereafter, the UE and the base station may perform an access procedure for cell #1 and communicate (807). During this process, operations according to various embodiments described below may be performed.

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

[0177] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations must use extremely sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to the movement or movement of the terminals, frequent re-alignment of the beams is required, which can lead to link instability. Accordingly, a beam management procedure, as illustrated in FIG. 9 below, may be employed.

[0178] 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 the present disclosure is applicable to a 6G communication environment. In addition, the procedure illustrated in FIG. 9 can be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (setting) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning that can distinguish the 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.).

[0179] Referring to FIG. 9, a base station can configure resources for beam management (901). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from existing downlink signals / channels for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a port for transmitting 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 can be included in the technical concept according to the present embodiment.

[0180] The base station can transmit measurement signals using multiple transmission beams (903). For example, the measurement signals can include at least one of a reference signal and a synchronization signal. At this time, the measurement signals can be transmitted as many times as the number of beams that require measurement, and can be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, the multi-beam transmission can be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

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

[0182] Integrated Sensing and Communication (ISAC)

[0183] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, i.e., sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communications network to a wireless communication and sensing network.

[0184] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 can 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 location (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and sensing transmitter (e.g., bistatic sensing).

[0185] 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, different terminals, or each terminal and base station.

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

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

[0188] - Second mode: A mode in which the sensing transmitter is included in a 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).

[0189] - Mode 3: 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).

[0190] - Mode 4: 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).

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

[0192] - 6th mode: A mode in which the sensing transmitter is included in a 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).

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

[0194] 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 an environment around 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 scattered / reflected by one or more objects (and / or an environment around the objects) from a sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signals, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing results may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment around the objects). The sensing results generated / obtained in this way may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided in the wireless communication system based on the 6G network of the present specification, or may be provided / disclosed to a trusted third party.

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

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

[0197] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

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

[0199] For example, as illustrated in FIG. 11, sensing resources can be set / allocated in units of symbols in the time domain and / or resource blocks in the frequency domain. Resources other than those for which the sensing resources are set / allocated can be utilized as resources for general communication. That is, sensing resources and communication resources can be set / allocated based on a time-division multiplexing (TDM) scheme and / or a frequency-division multiplexing (FDM) scheme in terms of the operation of the base station / terminal. Additionally or alternatively, unlike what is illustrated in FIG. 10, sensing resources can also be set / allocated based on other units in the time domain (e.g., slots, frames, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarriers, carriers, absolute frequencies (MHz, GHz), etc.).

[0200] Additionally or alternatively, in connection with the setting / allocation / scheduling of resources for general communication as described herein, the relationship between the resources and the aforementioned sensing resources may need to be considered. For example, when setting / allocating resources for general communication according to the embodiment(s) of the present disclosure, the resources may be set / allocated to rate-match or puncture the resource region corresponding to the sensing resource. For example, when scheduling resources for general communication according to the embodiment(s) of the present disclosure, the resources may be scheduled so as not to overlap with the resource region corresponding to the sensing resource. If the resources for general communication according to the embodiment(s) of the present disclosure and the resource region corresponding to the sensing resource are set / allocated / scheduled to overlap, one or both operations may be dropped, skipped, or postponed based on priorities, predefined rules, etc. That is, in the embodiment(s) of the present specification, it may be desirable that resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) are set / allocated / scheduled so as not to overlap with the sensing resources described above.

[0201] Additionally, various channel modeling methods may be applied in connection with the wireless sensing described herein. Channel modeling related to sensing may refer to configuring a path for transmitting and receiving sensing signals and / or scattered / reflected signals, taking into account the object being sensed and / or the environment in which the object resides. Channel modeling may be related to the performance / requirements of sensing in wireless communication systems, and thus may be an important factor in validating the sensing function.

[0202] Channels related to sensing can be divided into channels between objects (e.g., targets of interest) and sensing transmitters / receivers, and channels between the environment to which the object belongs and sensing transmitters / receivers. In this regard, channel modeling related to sensing can be divided based on sensing mode (e.g., the six types of modes described above), whether there is an object / 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 the environment in a base station / terminal-based monostatic sensing mode, and channel modeling for the environment in a base station / terminal-based bistatic sensing mode can be configured and optimized differently. For example, when various sensing scenarios are classified, channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios can be divided, etc. 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 the present disclosure may be based on stochastic geometric channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometric 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, a method can be applied in which the channel for the object (e.g., the target of interest) that requires high accuracy and consistency is modeled using a ray tracing technique, and the channel for the environment is modeled using a probabilistic technique.

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

[0204] 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 confirm (1205) the capability of the terminal for the sensing operation. In this regard, the terminal may be configured to report capability information on whether it supports the sensing operation to the base station. Additionally or alternatively, if the terminal is defined in advance in the standard as supporting the sensing operation, the procedure may be omitted. In addition, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information on whether it supports the sensing operation to an entity that configures / controls its sensing operation (e.g., a network entity at an upper level / layer of the base station).

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

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

[0207] Data transmission and HARQ-ACK process

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

[0209] - Frequency domain resource assignment: Indicates the set of RBs allocated to the PDSCH.

[0210] - 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 in a common or terminal-specific manner can be indicated through the TDRA field.

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

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

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

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

[0215] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and may consist of 1 bit if spatial bundling is configured. When the HARQ-ACK transmission timing for multiple PDSCHs is designated as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0216] Whether a UE should perform spatial bundling for a HARQ-ACK response can be configured (e.g., via RRC / higher layer signaling) for each cell group. For example, spatial bundling can be individually configured for each HARQ-ACK response transmitted over the PUCCH and / or each HARQ-ACK response transmitted over the PUSCH.

[0217] Spatial bundling can be supported when the maximum number of TBs (or codewords) that can be received at a time (or scheduled via 1 DCI) in the 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 can be used for 2-TB transmission, and up to 4 layers can be used for 1-TB transmission. Consequently, when spatial bundling is configured for the cell group, spatial bundling can be performed for serving cells that can schedule more than 4 layers among the serving cells in the cell group. On the serving cell, a UE that wishes to transmit a HARQ-ACK response via spatial bundling can generate the HARQ-ACK response by performing a (bit-wise) logical AND operation on the A / N bits for multiple TBs.

[0218] For example, assuming that a terminal receives a DCI scheduling 2 TB and receives 2 TB via PDSCH based on the DCI, the terminal performing spatial bundling can generate a single A / N bit by logically ANDing 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 ACKs, 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.

[0219] 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 logically ANDing the A / N bit for the 1-TB with bit value 1. Consequently, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0220] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. These multiple parallel HARQ processes allow DL transmissions to be performed continuously while waiting for HARQ feedback regarding the success or failure of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables such as the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

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

[0222] - Frequency domain resource assignment: Indicates the set of RBs allocated to PUSCH.

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

[0224] Thereafter, the terminal can transmit a PUSCH in slot #(n+K2) according to the scheduling information of slot #n. Here, the PUSCH includes a UL-SCH TB.

[0225] Dynamic / semi-static HARQ-ACK codebook

[0226] NR supports dynamic and semi-static HARQ-ACK codebook schemes. The HARQ-ACK (or A / N) codebook can be replaced by the HARQ-ACK payload.

[0227] When a dynamic HARQ-ACK codebook scheme is configured, the size of the A / N payload varies depending on the number of actually scheduled DL data. For this purpose, the PDCCH related to DL scheduling includes a counter-DAI (Downlink Assignment Index) and a total-DAI. The counter-DAI represents a {CC, slot} scheduling order value calculated in a CC (Component Carrier) (or cell)-first manner, and is used to designate the position of the A / N bit within the A / N codebook. The total-DAI represents a slot-wise scheduling accumulation value up to the current slot, and is used to determine the size of the A / N codebook.

[0228] When a semi-static A / N codebook scheme is configured, the size of the A / N codebook is fixed (to a maximum value) regardless of the number of actually scheduled DL data. Specifically, the (maximum) A / N payload (size) transmitted through one PUCCH in one slot can be determined by the number of A / N bits corresponding to a combination (hereinafter, bundling window) of all CCs configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) for which the A / N transmission timing can be indicated. For example, a DL grant DCI (PDCCH) includes PDSCH-to-A / N timing information, and the PDSCH-to-A / N timing information can have one of a plurality of values ​​(e.g., k). For example, if a PDSCH is received in slot #m and PDSCH-to-A / N timing information in a DL grant DCI (PDCCH) scheduling the PDSCH indicates k, A / N information for the PDSCH may be transmitted in slot #(m+k). For example, k ∈ {1, 2, 3, 4, 5, 6, 7, 8} may be given. Meanwhile, if 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 of 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 the A / N corresponding to slot #(n-8) to slot #(n-1) regardless of the actual DL data reception (i.e., the maximum number of A / N). Here, the A / N information can be replaced with the A / N codebook and A / N payload. In addition, the slot can be understood / replaced as a candidate opportunity (occasion) for DL ​​data reception.As an 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 can have a pre-defined value (e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or can be set by higher layer (RRC) signaling.

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

[0230] Meanwhile, "SLIV pruning" refers to the process of calculating a combination of all (non-overlapping) PDSCH occasions (SLIVs) that can be transmitted within K1 DL slots prior to the A / N transmission slot for each K1 value (set for each serving cell) in the case of the 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 set. In other words, SLIV pruning refers to the process of determining the set of (non-overlapping) PDSCH occasions (SLIVs) that are the target of HARQ-ACK reporting. The UE configures the A / N (sub-)payload (including determining the A / N bit position / order corresponding to each SLIV) for the set of PDSCH occasions (SLIVs) determined through SLIV pruning.

[0231] Looking more specifically at the process of determining combinations of transmittable PDSCH occasions (SLIVs) in SLIV pruning, one or more non-overlapping PDSCHs can be scheduled to the UE in each DL slot (e.g., index #N-candidate K1 value), and the number of (maximum) non-overlapping PDSCHs that can be scheduled within the slot can be determined based on a combination of configured SLIV values ​​(e.g., a combination of SLIV values ​​that can be configured via pdsch-TimeDomainAllocationList and indicated by the TDRA field of the DCI). Based on the SLIV values ​​configured in the UE, potential overlapping PDSCHs are pruned (i.e., incompatible / mutually exclusive PDSCHs due to overlap are counted as at most one PDSCH transmission), and (potential schedulable / compatible) non-overlapping PDSCHs are determined. In the case of the existing Type-1 codebook, the A / N sub-payload constructed through this SLIV pruning is concatenated for N K1 values ​​to construct the entire A / N codebook.

[0232] Meanwhile, existing NR supports scheduling multiple PDSCHs to a single UE through a single DCI, in which case multiple SLIV entries may exist in a row of the TDRA table. Considering such multiple PDSCH scheduling DCIs, SLIV pruning requires a process of updating a set of K1 values, and the UE determines a set of PDSCH occasions (SLIVs) based on the updated set of K1 values. Table 1 summarizes part of the SLIV pruning process for a Type 1 codebook considering multiple PDSCH scheduling DCIs, as defined in Section 9.1.2.1 of TS38.213.

[0233] [Table 1]

[0234]

[0235] HARQ-ACK codebook for DCI scheduling multiple data channels

[0236] To increase transmission efficiency of scheduling DCI for downlink data channels (e.g., PDSCH) and / or uplink data channels (e.g., PUSCH), scheduling of multiple PDSCHs or multiple PUSCHs may be supported through a single DCI. In this case, the multiple PDSCHs (or multiple PUSCHs) may be allocated to one terminal (Opt. 1) or to multiple terminals (Opt. 2).

[0237] DCI for scheduling multiple PDSCHs (or multiple PUSCHs) to one terminal, such as Opt 1), is conveniently called M-TB-DCI, and the corresponding PDSCHs (or PUSCHs) can be scheduled within the same carrier / cell / BWP or can be scheduled within different carriers / cells / BWPs.

[0238] In the case of being allocated to multiple terminals, such as Opt2, one PDSCH (or PUSCH) is mapped one-to-one with a specific terminal, and the DCI that schedules multiple PDSCHs (or multiple PUSCHs) to multiple terminals in this way is conveniently named M-UE-DCI.

[0239] In this disclosure, we propose a HARQ-ACK feedback method and a HARQ-ACK codebook configuration method corresponding to M-TB-DCI and M-UE-DCI.

[0240] [Proposal #1] DAI Signaling over M-UE-DCI

[0241] In the current NR system, the DAI value can be signaled as follows:

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

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

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

[0245] - 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 terminals configured with Type-2 HARQ-ACK CB, N bits may be allocated depending on the specific settings. For example, in case of a single serving cell, 2 bits may be allocated for counter-DAI, and in case of two or more serving cells, 2 bits each for counter-DAI / total-DAI, for a total of 4 bits may be allocated.

[0246] Meanwhile, DCI format 0_x is DCI related to UL scheduling, and DCI format 1_x is DCI related to DL scheduling.

[0247] Meanwhile, even when a Type 1 HARQ-ACK codebook is configured, the DCI may include 1 bit of DAI. For example, the 1 bit of DAI included in the UL grant DCI may be used to indicate whether the HARQ-ACK codebook should be included on the PUSCH scheduled through the UL grant.

[0248] In this proposal #1, we propose a method to signal DAI values ​​on DL or UL M-UE-DCI.

[0249] [Proposal #1-1] Individually signaling DAI values ​​for each terminal

[0250] Even if it is configured / determined that up to N terminals can be scheduled through a single DL / UL M-UE-DCI, terminals that have transmission / reception data and terminals that do not may coexist at the actual scheduling time of the DCI. Therefore, in order to perform DAI counting only for terminals that are actually scheduled, a method of individually signaling the DAI value for each terminal may be considered.

[0251] Specifically, for each terminal, the location of the DAI value corresponding to the terminal in a specific M-UE-DCI format can be set. For example, the DAI starting bit location L_A value can be set in advance for terminal #A from the base station (by MAC CE or higher layer signaling). In this case, when terminal #A receives the M-UE-DCI format, it can recognize that the DAI value corresponding to it is signaled from the L_A-th bit location within the corresponding DCI. When terminal #B receives the M-UE-DCI format, it can recognize that the DAI value corresponding to it is signaled from the L_B-th bit location (set in advance by the base station) within the corresponding DCI. The bit-width (size) of the corresponding DAI value can also be set in advance by the base station (by MAC CE or higher layer signaling), or similarly, the bit-width can be determined (without prior configuration from the base station) based on the number of serving cells / Type-2 HARQ-ACK CB related higher layer parameters / number of sub-codebooks, etc. Notably, for a terminal configured with Type-1 HARQ-ACK CB, the corresponding DAI starting bit location (for DL ​​M-UE-DCI) may not be set.

[0252] Alternatively, given the starting bit location of the DAI field in the M-UE-DCI format, a structure may be applied in which the corresponding DAI starting bit location L_X for each terminal varies depending on which terminal is scheduled. For example, if it is known through another field or combination of fields in the M-UE-DCI that a terminal is the first scheduled terminal, it can be recognized that the DAI value corresponding to the terminal is signaled from the starting bit location of the DAI field. If it is known that another terminal is the second scheduled terminal, it can be recognized that the DAI value corresponding to the terminal is signaled K bits after the starting bit location of the DAI field. If it is known that another terminal is the nth scheduled terminal, it can be recognized that the DAI value corresponding to the terminal is signaled (n-1)*K bits after the starting bit location of the DAI field. Here, the K value is the DAI bit-width signaled for a single terminal and can be set in advance by the base station (via MAC CE or higher layer signaling). If the DAI bit-width required for a specific terminal is 2 bits and a K value greater than 2 is set, only the MSB or LSB 2 bits are considered valid and the remaining bits can be ignored.

[0253] For example, L_X of L_A, L_B, etc. may mean the starting bit position within the corresponding DCI, or when there is one DCI field composed of multiple blocks in the corresponding DCI, it may mean the starting position (or order, index) of the block for the corresponding terminal within the DCI field.

[0254] In the case where the DAI value is signaled for each terminal as in the proposal #1-1, a terminal that is not actually scheduled through M-UE-DCI may not perform the corresponding HARQ-ACK feedback and / or HARQ-ACK CB configuration. Conversely, a terminal that is actually scheduled through M-UE-DCI may configure the HARQ-ACK CB configured based on the corresponding DAI value or feedback HARQ-ACK information through the scheduled PUSCH.

[0255] Each terminal may be configured with a different Type-1 HARQ-ACK CB or Type-2 HARQ-ACK CB. When a set of terminals that can be scheduled through a single M-UE-DCI is named UE_set, a constraint may be added that terminals belonging to Opt A) UE_set are configured with the same Type of HARQ-ACK CB. Or, even among terminals belonging to Opt B) UE_set, it may be allowed that some terminals are configured with Type-1 HARQ-ACK CB and other terminals are configured with Type-2 HARQ-ACK CB. For Opt A) and / or Opt B), in the case of UL M-UE-DCI format, 1 bit is allocated to each terminal configured with Type-1 HARQ-ACK CB in the DAI field, and in the case of DL M-UE-DCI format, 0 bit, i.e., no bit, may be allocated to terminal(s) configured with Type-1 HARQ-ACK CB in the DAI field.

[0256] [Proposal #1-2] Signaling a common DAI value for all terminals

[0257] If independent DAI values ​​are signaled for each terminal, as in Proposal #1-1 above, the signaling overhead within M-UE-DCI could significantly increase. For example, if up to four terminals can be scheduled, and each terminal requires 4 bits of DAI, 16 bits of signaling may be required just for DAI signaling. Considering this, common DAI signaling for each terminal could be considered.

[0258] In one way (especially for Type-2 HARQ-ACK CB), it can be recognized as the closest DAI value after the DAI value that has been counted for each terminal. For example, when there are terminals #1 and #2 that can be scheduled through one M-UE-DCI, if the counter-DAI value of terminal #1 is 1 and the counter-DAI value of terminal #2 is 2 (until immediately before the M-UE-DCI scheduling), both terminals can be scheduled simultaneously through the M-UE-DCI and the counter-DAI value can be signaled as 3. At this time, terminal #1 did not receive the scheduling DCI corresponding to the counter-DAI value of 2, but it can feed back the HARQ-ACK information corresponding to the counter-DAI value 2 as a NACK and receive the PDSCH corresponding to the counter-DAI value 3 (scheduled through the M-UE-DCI) and feed back the HARQ-ACK information depending on the success or failure. However, this method has a disadvantage in that it may not make full use of the 4-state DAI, as in the case of the above terminal #1, and thus may be a structure vulnerable to DCI missing.

[0259] Alternatively (especially for Type-2 HARQ-ACK CB), a separate sub-codebook for M-UE-DCI can be configured. In the present disclosure, configuring separate sub-codebooks may mean a structure in which counter / total-DAI values ​​are independently determined and signaled for each sub-codebook (e.g., the scheduled DCI / PDSCH order / sum for each sub-codebook is independently determined / signaled). For example, configuring separate sub-codebooks for S-UE-DCI (one or more PDSCHs are scheduled through one DCI) and M-UE-DCI may mean a structure in which counter / total-DAI values ​​are independently determined and signaled for each of S-UE-DCI and M-UE-DCI (e.g., the scheduled DCI / PDSCH order / sum for each DCI format is independently determined / signaled). In other words, it may be a structure in which the DAI value is determined and signaled only for the DCI(s) corresponding to the S-UE-DCI, and the DAI value is determined and signaled only for the DCI(s) corresponding to the M-UE-DCI. In addition, the final HARQ-ACK codebook may be configured by concatenating HARQ-ACK payloads corresponding to different sub-codebooks. The S-UE-DCI and the M-UE-DCI may be distinguished by having different RNTIs and / or DCI formats. For example, the UE may use sub-codebook #1, which is configured with HARQ-ACK information corresponding to the scheduled PDSCH(s) through DCIs scrambled (CRC) with the RNTI (e.g., C-RNTI) for the S-UE-DCI, and the RNTI (e.g.,, MultiUE-RNTI) can be concatenated by generating sub-codebook #2, which consists of HARQ-ACK information corresponding to the scheduled PDSCH(s) through DCIs scrambled with (CRC). (Sub-codebook #1 can precede or follow sub-codebook #2.)

[0260] In the case where a common DAI value of the terminals is signaled as in the proposal #1-2, even if a terminal has not actually scheduled a PDSCH through M-UE-DCI, the HARQ-ACK information corresponding to the DAI can map NACK to configure a HARQ-ACK payload. Conversely, a terminal that has actually scheduled a PDSCH through M-UE-DCI can configure the HARQ-ACK CB configured based on the DAI value. In addition, a terminal that has not actually scheduled a PUSCH through M-UE-DCI may not perform the corresponding HARQ-ACK feedback because there is no allocated PUSCH. However, the counter / total-DAI value can be updated based on the DAI information signaled through the M-UE-DCI. Conversely, a terminal that has actually scheduled a PUSCH through M-UE-DCI can feedback HARQ-ACK information through the PUSCH.

[0261] Each terminal may be configured with a different Type-1 HARQ-ACK CB or Type-2 HARQ-ACK CB. When a set of terminals that can be scheduled through a single M-UE-DCI is named a UE_set, a constraint may be added that terminals belonging to the UE_set are configured with the same Type of HARQ-ACK CB. When this constraint is applied (or when only terminals configured with Type-1 HARQ-ACK CB are included in the UE_set even if there is no constraint), in the case of the UL M-UE-DCI format for scheduling a terminal configured with Type-1 HARQ-ACK CB, 1 bit is allocated to the DAI field, and in the case of the DL M-UE-DCI format for scheduling a terminal configured with Type-1 HARQ-ACK CB, 0 bits, i.e., no bits may be allocated to the DAI field. Or, even if the terminals are within a UE_set, it may be allowed for some terminals to have Type-1 HARQ-ACK CB set and other terminals to have Type-2 HARQ-ACK CB set. At this time, Alt 1) (especially in the case of UL M-UE-DCI format) the DAI field for a terminal configured with Type-1 HARQ-ACK CB and the DAI field for a terminal configured with Type-2 HARQ-ACK CB can be configured separately, or Alt 2) in a state where a common DAI field is allocated, Alt 2-1) a terminal configured with Type-1 HARQ-ACK CB (especially in the case of UL M-UE-DCI format) recognizes the DAI value as 0 if the counter / total-DAI value is 0, and recognizes the DAI value as 1 if the counter / total-DAI value is not 0, or Alt 2-2) a terminal configured with Type-1 HARQ-ACK CB (especially in the case of DL M-UE-DCI format) can ignore the allocated DAI field.

[0262] Proposals #1-1 and #1-2 may be applied differently depending on whether it is UL M-UE-DCI or DL ​​M-UE-DCI. For example, Proposal #1-1 may be applied to UL M-UE-DCI, and Proposal #1-2 may be applied to DL M-UE-DCI.

[0263] [Proposal #2] Type-1 HARQ-ACK Codebook Configuration for PDSCHs Scheduled via M-UE-DCI

[0264] As described above in Table 1, in the case of the Type-1 HARQ-ACK codebook configuration of the existing NR system, when a set of multiple (e.g., K_N) candidate K1 (PDSCH-to-HARQ-ACK slot-level offset) values ​​is set, a combination of all PDSCH occasions (SLIVs) that can be transmitted within the K1 DL slot(s) preceding the HARQ-ACK transmission slot is calculated for each K1 value (set for each serving cell) to configure occasions for candidate PDSCH receptions corresponding to each DL slot (including determining the HARQ-ACK bit position / order corresponding to each SLIV) (this is defined as “SLIV pruning”). Through this process, HARQ-ACK information bit(s) are configured for each occasion included in the set of occasions for candidate PDSCH receptions and concatenated to configure the entire HARQ-ACK codebook.

[0265] When one or more PDSCHs can be scheduled (on the same serving cell) via S-UE-DCI and M-UE-DCI from a specific terminal's perspective, the SLIV pruning method for configuring Type-1 HARQ-ACK CB can be determined by one of the following options.

[0266] (1) Option 1: By performing SLIV pruning using both SLIVs belonging to the TDRA table set in M-UE-DCI and SLIVs belonging to the TDRA table set in S-UE-DCI, the terminal can generate a single integrated codebook and feed it back to the base station.

[0267] (2) Option 2: When there is a set #A of SLIVs belonging to the TDRA table configured in M-UE-DCI and a set #B of SLIVs belonging to the TDRA table configured in S-UE-DCI, (considering that the serving cell to which the PDSCHs scheduled through M-UE-DCI belong is different from the serving cell to which the PDSCHs scheduled through S-UE-DCI belong) sub-codebook #1 is generated through SLIV pruning based on set #A and sub-codebook #2 is generated through SLIV pruning based on set #B, and then they are concatenated (sub-codebook #1 may precede or follow sub-codebook #2) to form a single codebook that the terminal can feed back to the base station. If there is no HARQ-ACK corresponding to a specific sub-codebook among the two sub-codebooks, the terminal can configure the entire codebook using only the remaining sub-codebook and feed it back to the base station.

[0268] At this time, one of the following methods can be applied to configure SLIV corresponding to each TDRA row index within the TDRA table set in M-UE-DCI. It is assumed that the number of terminals belonging to the UE_set set of terminals that can be scheduled through the corresponding M-UE-DCI is N.

[0269] (a) Option A: Each terminal receives an individual TDRA table (consisting of a single SLIV for each TDRA row index), and each terminal interprets / applies the codepoint indicated by the TDRA field of M-UE-DCI as a row value in its own TDRA table. In this case, the TDRA field may be individually allocated to each terminal, or only the common TDRA field may be allocated. The SLIV set utilized for Type-1 HARQ-ACK CB configuration is the set of SLIVs for all TDRA row indices allocated to each terminal.

[0270] (b) Option B: It is configured with N SLIVs for each TDRA row index, and the UE corresponding to each SLIV is fixed. For example, a certain UE can be configured in advance whether the nth (n=1, 2, 쪋, N) SLIV corresponds to it, and if n=2, it can recognize that the 2nd SLIV among the N SLIVs linked to the TDRA row index #k indicated in the M-UE-DCI corresponds to it. In addition, the SLIV set utilized for the Type-1 HARQ-ACK CB configuration is a set of all nth SLIVs of each TDRA row index.

[0271] (c) Option C: It is configured with N SLIVs for each TDRA row index, and the UE corresponding to each SLIV is variable. For example, when only K terminals out of N terminals are actually scheduled, a terminal can recognize that it is the kth (n=1, 2, 쪋, K)th scheduled terminal through a specific field or a combination of fields. At this time, it can recognize that the kth SLIV among the N SLIVs linked to the TDRA row index #m indicated in the M-UE-DCI corresponds to it. In addition, the SLIV set utilized for configuring Type-1 HARQ-ACK CB can be a set of all SLIVs of each TDRA row index, or a set of all the first P SLIVs. For example, when indicating a scheduled UE through an N-bit bitmap, the terminal corresponding to the first bit of the bitmap can always be associated only with the first SLIV (among multiple SLIVs set to one TDRA row index), so P=1. As another example, when indicating a scheduled UE through an N-bit bitmap, the terminal corresponding to the second bit of the bitmap can always be associated only with the first or second SLIV (among multiple SLIVs set to one TDRA row index), so P=2.

[0272] Meanwhile, depending on which of the above Option A / B / C options is used to configure TDRA, other options among Option 1 / 2 may be applied. For example, if only a single SLIV is linked per terminal, such as Option A / B, or if P=1 in Option C, Option 1 may be applied. Alternatively, in the case of Option C, since multiple SLIVs may be linked to one terminal, Option 2 may be applied to configure individual sub-codebooks. Alternatively, which option between Option 1 and Option 2 is applied may be defined in advance or configured (by MAC CE or higher layer signaling).

[0273] [Proposal #3] HARQ-ACK feedback for PDSCHs scheduled via M-TB-DCI

[0274] [Proposal #3-1] Compress and transmit HARQ-ACK information

[0275] When more than one PDSCH can be scheduled via M-TB-DCI, providing HARQ-ACK feedback for each PDSCH can significantly increase the UCI payload size. Therefore, we propose a method to compress and transmit HARQ-ACK information as a way to reduce the UCI payload size.

[0276] (1) Method 1: The terminal can provide feedback on the PDSCH location and NACK length for failed decoding, or conversely, the PDSCH location and ACK length for successful decoding. In this case, a method similar to the RIV (resource indication value) used in NR downlink resource type 1 can be applied for signaling the starting point and interval.

[0277] When the terminal signals the NACK length, it can be a method of feeding back the length between the first NACK and the last NACK (for example, the base station can consider all PDSCHs between the two NACKs as NACKs). For example, if 8 PDSCHs are scheduled via M-TB-DCI and the decoding result is ANAANNNA (when ACK is indicated as "A" and NACK is indicated as "N"), the terminal can signal to the base station in the form of RIV that PDSCHs from the second to the seventh are NACKs. The base station that receives this information can perform retransmission for the remaining 6 PDSCHs, excluding the first and the last PDSCHs.

[0278] Conversely, when the terminal signals the ACK length, it may be a method of feeding back the length of consecutive ACKs from the first ACK (i.e., the base station may regard all PDSCHs except for the consecutive ACKs as NACKs). For example, if 8 PDSCHs are scheduled via M-TB-DCI and the decoding result is NAANAAAA (when ACK is indicated as "A" and NACK is indicated as "N"), the terminal may signal to the base station in the form of RIV that the second PDSCH to the third PDSCH are ACKs. The base station that receives this information may perform retransmission for the remaining 6 PDSCHs except for the second and third PDSCHs. Alternatively, the length of consecutive ACKs from the first ACK that belongs to the set of PDSCHs with the longest consecutive ACK length may be fed back. In the above example, if the decoding result is NAANAAAA, the terminal can signal to the base station in RIV format that ACKs are received from the fifth PDSCH to the last PDSCH, thereby informing the base station of the success or failure of more PDSCHs. In this case, if there are multiple sets of PDSCHs with the longest consecutive ACK lengths, the terminal can randomly select one of them or feed back the length of consecutive ACKs starting from the first ACK in the most preceding (or succeeding) set.

[0279] Whether the terminal signals the NACK length or the ACK length can be indicated via M-TB-DCI, predefined, or configured (via MAC CE or higher layer signaling).

[0280] (2) Method 2: The terminal maps only the start of NACK (or ACK) as a codepoint in the HARQ-ACK codebook, and the base station can regard this as feedback that “all subsequent / previous PDSCHs are NACK (or ACK).”

[0281] When a terminal signals the NACK length, it can signal the position of the first (or last) NACK. This allows the base station to perform retransmissions for subsequent (or previous) PDSCHs, including the PDSCH at that position. For example, if the decoding result is ANAANNNA, the terminal can map the start of the NACK to the second PDSCH as a codepoint in the HARQ-ACK codebook, thereby causing the base station to perform retransmissions for the remaining PDSCHs, excluding the first.

[0282] When the terminal signals the ACK length, it can signal the location of the starting PDSCH of consecutive ACK bursts including the last (or first) ACK. This allows the base station to perform retransmissions for PDSCHs before (or after) the PDSCH at that location. For example, if the decoding result is NAANAAAA, the terminal can map the fact that the start of the ACK is the fifth PDSCH to a codepoint in the HARQ-ACK codebook, thereby causing the base station to perform retransmissions for the first to fourth PDSCHs.

[0283] Whether the terminal signals the NACK length or the ACK length can be indicated via M-TB-DCI, predefined, or configured (via MAC CE or higher layer signaling).

[0284] Meanwhile, which Method is applied between Method 1 and Method 2 can be defined in advance or set (by MAC CE or higher layer signaling).

[0285] The above Method 1 and / or Method 2 is a method for configuring HARQ-ACK bit(s) for bit locations corresponding to one or more PDSCH occasions in the case of a Type-1 HARQ-ACK codebook, and a method for configuring HARQ-ACK bit(s) corresponding to one DAI (signaled on the corresponding M-TB-DCI) in the case of a Type-2 HARQ-ACK codebook.

[0286] The above Method 1 and / or Method 2 can also be applied when transmitting CBG-level HARQ-ACK. That is, since there are multiple CBGs that constitute one TB (or PDSCH) and the payload size can increase significantly if a codebook is configured with HARQ-ACK bits for each CBG, (like Method 1) the UE can feedback the position and NACK length of the CBG that failed to decode, or conversely, the position and ACK length of the CBG that succeeded in decoding, or (like Method 2) the UE can map only the starting CBG of the NACK (or ACK) among the multiple CBGs as a codepoint on the HARQ-ACK codebook, and the base station can regard this as feedback that “all subsequent / previous CBGs are NACK (or ACK).”

[0287] [Proposal #3-2] In addition to HARQ-ACK information, feed back delta MCS and / or multi-bit A / N information.

[0288] HARQ-ACK information, which consists of 1 bit per PDSCH, can only express ACK or NACK information. If more levels of NACK information are fed back (for example, if the degree of decoding failure is reported based on the received energy of the PDSCH), it can help the base station adjust the amount of time / frequency resources and / or the MCS value for future retransmissions or supertransmissions. This process can be done without the help of the UE's CSI report, making it more suitable for URLLC services. Sending more detailed NACK information in this way is conveniently referred to as multi-bit A / N, and the degree of decoding failure based on the received energy of the PDSCH can be quantified and mapped to each code-point. Alternatively, when providing HARQ-ACK feedback, if decoding fails after PDSCH reception, the UE can report an appropriate MCS value (i.e., a change or delta value from the MCS applied when the PDSCH was received) for future PDSCH (re)transmission, thereby helping the base station adjust the MCS value for future retransmissions or initial transmissions. This reporting method is referred to as delta MCS, and the change or delta value from the MCS applied when the PDSCH was received can be mapped to each code-point.

[0289] For Method 1 and Method 2 of the above-mentioned Proposal #3-1, common delta MCS or multi-bit A / N information can be reported in addition to the HARQ-ACK information proposed in Method 1 and Method 2. Alternatively, when time domain bundling is configured as in Table F1 (e.g., can be configured with the timeDomainHARQ-BundlingType1 or nrofHARQ-BundlingGroups parameters), delta MCS or multi-bit A / N information can be reported for each bundling group or for the bundling group in common.

[0290] Figure 15 is a diagram illustrating the operation of a base station and a terminal according to one embodiment. Figure 15 is an implementation example related to at least some of the above-described proposals, and reference may be made to the descriptions of the above proposals even if not otherwise stated.

[0291] Referring to Figure 15, a terminal can receive configuration information from a base station via upper layer signaling (1505). The configuration information may include configuration information for DCI. For example, the terminal can receive M-UE-DCI and / or M-TB-DCI configuration.

[0292] The terminal can receive DCI(s) (1510). The DCI(s) may be M-UE-DCI and / or M-TB-DCI scheduling PDSCH(s) or PUSCH(s).

[0293] A terminal that receives DCI(s) can check whether scheduling is performed and perform transmission and / or reception operations based on the DCI.

[0294] Additionally, the terminal can configure HARQ-ACK codebook information based on at least some of proposals #1 / 2 / 3 (1515).

[0295] The terminal can report the HARQ-ACK codebook to the base station (1520).

[0296] According to the present disclosure, by supporting scheduling and HARQ-ACK feedback methods for multiple PDSCH transmissions through one DCI, transmission efficiency of scheduling DCI for PDSCH and / or PUSCH can be increased.

[0297] FIG. 16 is a diagram illustrating PDSCH scheduling via S-UE DCI / M-UE DCI and HARQ-ACK codebook generation therefor according to one embodiment. FIG. 16 is an implementation example related to at least some of the above-described proposals, and the descriptions of the above-described proposals may be referenced even if not otherwise stated.

[0298] Referring to FIG. 16, the base station can receive configuration information via upper layer signaling (A05). The configuration information can include at least one of configuration information for S-UE-DCI, configuration information for M-UE-DCI, and / or configuration information for M-TB-DCI. The configuration information for each DCI can include at least one of RNTI configuration, search space configuration, AL level information, CORESET configuration, and / or TDRA table configuration for each DCI.

[0299] The terminal can attempt to detect DCI by monitoring PDCCH candidates based on configuration information. For convenience, the detection of S-UE DCI and M-UE DCI is described.

[0300] The terminal can receive S-UE DCI from the base station (A10). The S-UE DCI can schedule at least one first PDSCH to the terminal.

[0301] The terminal may receive at least one first DCI based on the S-UE DCI (A15). The S-UE DCI may include DAI information related to at least one of C-DAI (counter-DAI) or T-DAI (total-DAI).

[0302] A terminal may receive M-UE DCI from a base station (A20). The M-UE DCI may schedule multiple second PDSCHs for multiple UEs. The M-UE DCI may include terminal-common DAI (e.g., C-DAI and / or T-DAI) information. The DAI information included in the S-UE DCI and the terminal-common DAI information included in the M-UE DCI may be counted independently.

[0303] The terminal can receive at least one second PDSCH among a plurality of second PDSCHs based on the M-UE DCI (A25).

[0304] The terminal may generate a HARQ-ACK codebook (A35). The HARQ-ACK codebook may include a first HARQ-ACK for at least one first PDSCH and a second HARQ-ACK for at least one second PDSCH. The first HARQ-ACK may be included in a first HARQ-ACK sub-codebook, and the second HARQ-ACK may be included in a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook may be determined based on DAI information included in S-UE DCI, and the second HARQ-ACK sub-codebook may be determined based on DAI information included in M-UE DCI. The HARQ-ACK codebook may include the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook, and may further include another HARQ-ACK sub-codebook according to an embodiment. The HARQ-ACK sub-codebooks may be concatenated with each other. For example, a Type 2 HARQ-ACK codebook may be configured for a terminal, and the payload of each HARQ-ACK sub-codebook may be determined based on the corresponding DAI information. The mapping position / order of HARQ-ACK bits within each HARQ-ACK sub-codebook may be determined based on the corresponding DAI information.

[0305] The terminal can transmit a HARQ-ACK codebook to the base station (A40).

[0306] Figure 17 illustrates a flowchart of a method performed by a terminal according to one embodiment. Figure 17 is an implementation example related to at least some of the above-described proposals, and reference may be made to the descriptions of the above proposals even if not otherwise stated.

[0307] Referring to FIG. 17, the terminal can receive one or more DCI (downlink control information) (B05).

[0308] The terminal can receive one or more PDSCHs (physical downlink shared channels) based on one or more of the above DCIs (B10).

[0309] The terminal may transmit a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for one or more of the PDSCHs (B15).

[0310] The one or more DCIs may include at least one of a first DCI (e.g., S-UE-DCI) that schedules a PDSCH of the terminal or a second DCI (e.g., M-UE-DCI) that schedules a plurality of PDSCHs for a plurality of terminals including the terminal.

[0311] The above second DCI may include terminal common DAI (downlink assignment index) information.

[0312] The HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, and the second HARQ-ACK sub-codebook can be determined based on the terminal common DAI information.

[0313] For example, if the plurality of PDSCHs scheduled through the second DCI include a specific PDSCH allocated to the terminal, the terminal may receive the specific PDSCH and map an A / N value (e.g., a binary value depending on whether decoding succeeds / fails) for the specific PDSCH to a specific HARQ-ACK bit included in the second HARQ-ACK sub-codebook. Conversely, if none of the plurality of PDSCHs scheduled through the second DCI is allocated to the terminal, the terminal may map a NACK to a specific HARQ-ACK bit included in the second HARQ-ACK sub-codebook. The specific HARQ-ACK bit may be a HARQ-ACK bit linked to DAI information common to the terminal.

[0314] The first DCI may include DAI information related to at least one of C-DAI (counter-DAI) or T-DAI (total-DAI). The DAI information included in the first DCI and the terminal common DAI information included in the second DCI may be counted independently of each other.

[0315] The first DCI may be received based on a first radio network temporary identifier (RNTI) specific to the terminal, and the second DCI may be received based on a second RNTI common to the plurality of terminals.

[0316] The above HARQ-ACK codebook can be generated based on the concatenation of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0317] The same type of HARQ-ACK codebook can be set for the above multiple terminals.

[0318] The above terminal common DAI information may be common to terminals for which the Type 2 HARQ-ACK codebook is set among the Type 1 HARQ-ACK codebook and the Type 2 HARQ-ACK codebook.

[0319] The first HARQ-ACK sub-codebook may be configured for PDSCH opportunities determined based on a first time domain resource allocation (TDRA) table related to the first DCI, and the second HARQ-ACK sub-codebook may be configured for PDSCH opportunities determined based on a second TDRA table related to the second DCI.

[0320] A row of the second TDRA table may include a plurality of SLIVs (slot length indication values) for the plurality of terminals.

[0321] Figure 18 illustrates a flowchart of a method performed by a base station according to one embodiment. Figure 18 is an implementation example related to at least some of the above-described proposals, and reference may be made to the description of the above proposals even if not otherwise stated.

[0322] Referring to FIG. 18, the base station can transmit one or more DCIs (downlink control information) (C05).

[0323] The base station can transmit one or more PDSCHs (physical downlink shared channels) related to one or more of the above DCIs (C10).

[0324] The base station can receive a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for one or more of the PDSCHs (C15).

[0325] The one or more DCIs may include at least one of a first DCI scheduling a PDSCH of a first terminal or a second DCI scheduling a plurality of PDSCHs for a plurality of terminals including the first terminal.

[0326] The above second DCI may include terminal common DAI (downlink assignment index) information.

[0327] The HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI (e.g., S-UE-DCI) and a second HARQ-ACK sub-codebook related to the second DCI (e.g., M-UE-DCI), and the second HARQ-ACK sub-codebook can be determined based on the terminal common DAI information.

[0328] For example, if the plurality of PDSCHs scheduled through the second DCI include a specific PDSCH allocated to the first terminal, the base station can transmit the specific PDSCH to the first terminal and obtain an A / N value (e.g., a binary value depending on whether the first terminal succeeds / fails in decoding) for the specific PDSCH through a specific HARQ-ACK bit included in the second HARQ-ACK sub-codebook from the first terminal. Conversely, if none of the plurality of PDSCHs scheduled through the second DCI is allocated to the first terminal, the base station can obtain a NACK through a specific HARQ-ACK bit included in the second HARQ-ACK sub-codebook from the first terminal. The specific HARQ-ACK bit may be a HARQ-ACK bit linked to DAI information common to the terminals.

[0329] The first DCI may include DAI information related to at least one of C-DAI (counter-DAI) or T-DAI (total-DAI). The DAI information included in the first DCI and the terminal common DAI information included in the second DCI may be counted independently of each other.

[0330] The first DCI may be transmitted based on a first radio network temporary identifier (RNTI) specific to the terminal, and the second DCI may be transmitted based on a second RNTI common to the plurality of terminals.

[0331] The above HARQ-ACK codebook can be generated based on the concatenation of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0332] The same type of HARQ-ACK codebook can be set for the above multiple terminals.

[0333] The above terminal common DAI information may be common to terminals for which the Type 2 HARQ-ACK codebook is set among the Type 1 HARQ-ACK codebook and the Type 2 HARQ-ACK codebook.

[0334] The first HARQ-ACK sub-codebook may be configured for PDSCH opportunities determined based on a first time domain resource allocation (TDRA) table related to the first DCI, and the second HARQ-ACK sub-codebook may be configured for PDSCH opportunities determined based on a second TDRA table related to the second DCI.

[0335] A row of the second TDRA table may include a plurality of SLIVs (slot length indication values) for the plurality of terminals.

[0336] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form 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 self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0337] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the scope of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

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

Claims

There is a method performed by the terminal, Receive one or more DCI (downlink control information); Receiving one or more PDSCHs (physical downlink shared channels) based on one or more of the above DCIs; and Including transmitting a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for one or more of the PDSCHs, The one or more DCIs include at least one of a first DCI for scheduling a PDSCH of the terminal or a second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the terminal, The above second DCI includes terminal common DAI (downlink assignment index) information, The HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, A method in which the second HARQ-ACK sub-codebook is determined based on the common DAI information of the terminal. In the first paragraph, A method in which the terminal maps NACK (Negative-ACK) to a specific HARQ-ACK bit within the second HARQ-ACK sub-codebook based on the plurality of PDSCHs scheduled through the second DCI not including a PDSCH allocated to the terminal. In the second paragraph, A method wherein the above specific HARQ-ACK bit is a HARQ-ACK bit linked to the common DAI information of the terminal. In the first paragraph, The above first DCI includes DAI information related to at least one of C-DAI (counter-DAI) or T-DAI (total-DAI), A method wherein the DAI information included in the first DCI and the terminal common DAI information included in the second DCI are counted independently of each other. In the first paragraph, The first DCI is received based on the terminal-specific first RNTI (radio network temporary identifier), A method wherein the second DCI is received based on a second RNTI common to the plurality of terminals. In the first paragraph, A method in which the above HARQ-ACK codebook is generated based on the concatenation of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook. In the first paragraph, A method in which the same type of HARQ-ACK codebook is set for the above plurality of terminals. In the first paragraph, The above terminal common DAI information is a method that is common to terminals for which the Type 2 HARQ-ACK codebook is set among the Type 1 HARQ-ACK codebook and the Type 2 HARQ-ACK codebook. In the first paragraph, The first HARQ-ACK sub-codebook is configured for PDSCH opportunities determined based on a first TDRA (time domain resource allocation) table related to the first DCI, A method wherein the second HARQ-ACK sub-codebook is configured for PDSCH opportunities determined based on a second TDRA table related to the second DCI. In paragraph 9, A method wherein a row of the second TDRA table includes a plurality of SLIVs (slot length indication values) for the plurality of terminals. A non-transitory computer-readable recording medium having recorded thereon a program for performing the method described in claim 1. In the device, at least one processor; and At least one memory configured to store instructions that are executed by said at least one processor to cause said at least one processor to perform operations, The operations of the above processor are: Receive one or more DCI (downlink control information); Receiving one or more PDSCHs (physical downlink shared channels) based on one or more of the above DCIs; and Including transmitting a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for one or more of the PDSCHs, The one or more DCIs include at least one of a first DCI for scheduling a PDSCH of the device or a second DCI for scheduling a plurality of PDSCHs for a plurality of devices including the device, The above second DCI includes device common DAI (downlink assignment index) information, The HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, The above second HARQ-ACK sub-codebook is determined based on the common DAI information of the device. In paragraph 12, A device wherein the above device is a terminal including a transceiver or a processing device configured to control the terminal. In a method performed by a base station, Transmit one or more DCI (downlink control information); Transmitting one or more PDSCHs (physical downlink shared channels) related to one or more of the above DCIs; and Including receiving a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for one or more of the PDSCHs, The one or more DCIs include at least one of a first DCI for scheduling a PDSCH of a first terminal or a second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the first terminal, The above second DCI includes terminal common DAI (downlink assignment index) information, The HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, A method in which the second HARQ-ACK sub-codebook is determined based on the common DAI information of the terminal. At the base station, at least one processor; and At least one memory configured to store instructions that are executed by said at least one processor to cause said at least one processor to perform operations, The operations of the above processor are: Transmit one or more DCI (downlink control information); Transmitting one or more PDSCHs (physical downlink shared channels) related to one or more of the above DCIs; and Including receiving a HARQ-ACK codebook including HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for one or more of the PDSCHs, The one or more DCIs include at least one of a first DCI for scheduling a PDSCH of a first terminal or a second DCI for scheduling a plurality of PDSCHs for a plurality of terminals including the first terminal, The above second DCI includes terminal common DAI (downlink assignment index) information, The HARQ-ACK codebook includes at least one of a first HARQ-ACK sub-codebook related to the first DCI and a second HARQ-ACK sub-codebook related to the second DCI, The above second HARQ-ACK sub-codebook is determined based on the terminal common DAI information of the base station.

Images