WO2023233603A1

WO2023233603A1 - Terminal, base station, and wireless communication method

Info

Publication number: WO2023233603A1
Application number: PCT/JP2022/022404
Authority: WO
Inventors: 優元 ▲高▼橋; 聡永田; チーピンピ; ジンワン; ランチン
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2022-06-01
Filing date: 2022-06-01
Publication date: 2023-12-07

Abstract

This terminal is equipped with: a control unit for controlling settings in a manner such that Configured Grant Physical Uplink Shared Channel (CG PUSCH) transmission and/or Semi-Persistent Scheduling Downlink Shared Channel (SPS PDSCH) receipt are performed via single-codeword execution or two-codeword execution; and a transmitting/receiving unit for executing the CG PUSCH transmission and/or SPS PDSCH receipt on the basis of the control unit settings.

Description

Terminal, base station, and wireless communication method

The present disclosure relates to a terminal, a base station, and a wireless communication method.

Long Term Evolution (LTE) has been specified in the Universal Mobile Telecommunication System (UMTS) network with the aim of achieving even higher data rates and lower latency. In addition, a successor system to LTE is also being considered with the aim of further increasing the bandwidth and speed of LTE. Successor systems to LTE include, for example, LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), New There is a system called Radio (NR).

In 5G, various wireless technologies and network architectures are being studied in order to meet the requirements of achieving a throughput of 10 Gbps or more and reducing the delay in the wireless section to 1 ms or less (for example, Non-Patent Document 1). .

In NR, as an example of various wireless technologies, a method that does not perform dynamic scheduling (no scheduling using dynamic grant) is being considered.

Methods for improving communication efficiency in cases where dynamic scheduling is not performed have not been sufficiently studied.

One aspect of the present disclosure provides a terminal, a base station, and a wireless communication method that can improve communication efficiency.

A terminal according to an aspect of the present disclosure transmits a CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or receives an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) using a single-codeword or a two-codeword. and a transmitting/receiving unit that transmits the CG PUSCH and/or receives the SPS PDSCH based on the settings of the control unit.

In a wireless communication method according to one aspect of the present disclosure, a terminal that transmits and receives Extended Reality (XR) data transmits a CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel). The CG PUSCH is transmitted and/or the SPS PDSCH is received based on the settings.

FIG. 1 is a diagram for explaining a wireless communication system according to an embodiment. FIG. 1 is a block diagram showing an example of the configuration of a base station according to an embodiment. 1 is a block diagram illustrating an example of the configuration of a terminal according to an embodiment. FIG. FIG. 3 is a diagram showing an example of HARQ-ACK CB. FIG. 7 is a diagram illustrating an example of HARQ-ACK CB of Proposal 2. FIG. 6 is a diagram illustrating an example of HARQ-ACK CB of Option 2 of Proposal 2. FIG. 6 is a diagram illustrating an example of HARQ-ACK CB of Option 2-1 of Proposal 2. FIG. 7 is a diagram illustrating an example of HARQ-ACK CB of option 2-2 of proposal 2. FIG. 7 is a diagram illustrating an example of HARQ-ACK CB of option 2-2A of proposal 2. FIG. 6 is a diagram showing an example of HARQ-ACK CB of Option 2-2B of Proposal 2. FIG. 6 is a diagram illustrating an example of HARQ-ACK CB of option 3 of proposal 2. FIG. 4 is a diagram illustrating an example of HARQ-ACK CB of Option 4 of Proposal 2. FIG. 4 is a diagram showing an example of proposal 4. FIG. 2 is a diagram illustrating an example of the hardware configuration of a terminal and a base station according to an embodiment. 1 is a diagram showing an example of the configuration of a vehicle in an embodiment of the present invention.

Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

Existing technologies are used as appropriate for the operation of the wireless communication system according to the embodiment of the present invention. The existing technology is, for example, an existing NR, but is not limited to an existing NR.

In addition, in this specification, terms used in existing NR or LTE specifications such as PUSCH, PDSCH, RRC (Radio Resource Control), MAC (Media Access Control), and DCI (Downlink Control Information) are used. However, the channel names, protocol names, signal names, function names, etc. used in this specification may be called by other names.

<System configuration>
FIG. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention. A wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in FIG. Although one base station 10 and one terminal 20 are shown in FIG. 1, this is just an example, and there may be a plurality of each.

The wireless communication system may be a wireless communication system compliant with New Radio (NR). Further, the wireless communication system may be a wireless communication system according to a method called 5G, Beyond 5G, 5G Evolution, or 6G. Illustratively, the wireless communication system may be a wireless communication system that follows a system called URLLC and/or IIoT.

Additionally, the wireless communication system may include Next Generation-Radio Access Network (hereinafter referred to as NG-RAN). NG-RAN includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN and 5GC may also be simply expressed as "networks."

The physical resources of a radio signal are defined in the time domain and the frequency domain, where the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. Furthermore, a TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe.

At least one of the base station 10 and the terminal 20 supports Massive MIMO (Multiple-Input Multiple-Output), which generates a highly directional beam (BM) by controlling radio signals transmitted from multiple antenna elements. You may respond. Furthermore, at least one of the base station 10 and the terminal 20 may support carrier aggregation (CA) in which a plurality of component carriers (CCs) are bundled together. Further, at least one of the base station 10 and the terminal 20 may support dual connectivity (DC) or the like in which communication is performed between the terminal 20 and each of the plurality of base stations 10.

A wireless communication system may support multiple frequency bands. For example, the wireless communication system supports Frequency Range (FR) 1 and FR2. For example, the frequency bands of each FR are as follows.
・FR1: 410MHz to 7.125GHz
・FR2: 24.25GHz to 52.6GHz

In FR1, Sub-Carrier Spacing (SCS) of 15kHz, 30kHz or 60kHz is used, and a bandwidth (BW) of 5MHz to 100MHz may be used. FR2 is, for example, a higher frequency than FR1. In FR2, a 60kHz or 120kHz SCS may be used and a bandwidth (BW) of 50MHz to 400MHz. Furthermore, FR2 may include a 240kHz SCS.

The wireless communication system in this embodiment may support a frequency band higher than the FR2 frequency band. For example, the wireless communication system in this embodiment can support frequency bands exceeding 52.6 GHz and up to 114.25 GHz. Such high frequency bands may be referred to as "FR2x."

In addition, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) than the above example is applied. It's okay. Further, DFT-S-OFDM may be applied to both the uplink and the downlink, or may be applied to either one.

In a wireless communication system, a time division duplex (TDD) slot configuration pattern may be set. For example, in the slot setting pattern, there are slots for transmitting DL signals, slots for transmitting UL signals, slots in which DL signals, UL signals, and guard symbols are mixed, and slots in which the signal to be transmitted is changed to flexible. A pattern indicating the order of two or more slots may be defined.

In addition, in wireless communication systems, channel estimation of PUSCH (or PUCCH (Physical Uplink Control Channel)) can be performed using demodulation reference signals (DMRS) for each slot, but in addition, DMRS assigned to each of multiple slots can be estimated. PUSCH (or PUCCH) channel estimation can be performed using Such channel estimation may be referred to as joint channel estimation. Alternatively, it may be called by another name such as cross-slot channel estimation. In this case, the terminal 20 may transmit DMRS assigned to each of the plurality of slots in a plurality of slots so that the base station 10 can perform joint channel estimation using DMRS.

Furthermore, in the wireless communication system, an enhanced function may be added to the feedback function from the terminal 20 to the base station 10. For example, enhanced functionality of terminal feedback for HARQ-ACK (Hybrid automatic repeat request acknowledgment) may be added.

The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The base station 10 may be called an NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). Furthermore, the base station 10 may be considered as a device included in a network to which the terminal 20 connects.

The base station 10 is capable of performing carrier aggregation in which multiple cells (multiple CCs (component carriers)) are bundled to communicate with the terminal 20. In carrier aggregation, one primary cell (PCell, Primary Cell) and one or more secondary cells (SCell, Secondary Cell) are used.

The base station 10 transmits a synchronization signal, system information, etc. to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. Further, the synchronization signal may be SSB. System information is transmitted, for example, on NR-PBCH or PDSCH, and is also referred to as broadcast information. As shown in FIG. 1, the base station 10 transmits control signals or data to the terminal 20 on the DL, and receives control signals or data from the terminal 20 on the UL. Note that here, what is transmitted on control channels such as PUCCH and PDCCH is called a control signal, and what is transmitted on shared channels such as PUSCH and PDSCH is called data. It is.

The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or a M2M (Machine-to-Machine) communication module. As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL, and transmits control signals or data to the base station 10 via UL, thereby receiving various types of information provided by the wireless communication system. Use communication services. Note that the terminal 20 may also be called user equipment (UE).

Note that the terminal 20 may notify the base station 10 of terminal capability information (UE capability) that defines information regarding the capability of the terminal.

Next, the configurations of the base station 10 and the terminal 20 will be explained. Note that the configurations of base station 10 and terminal 20 described below are examples of functions related to this embodiment. The base station 10 and the terminal 20 may have functions not shown. Further, as long as the function executes the operation according to the present embodiment, the functional division and/or the name of the functional unit is not limited.

<Base station configuration>
FIG. 2 is a block diagram showing an example of the configuration of base station 10 according to this embodiment. Base station 10 includes, for example, a transmitter 101, a receiver 102, and a controller 103. The base station 10 communicates with the terminal 20 (see FIG. 3) wirelessly.

The transmitter 101 transmits the DL signal to the terminal 20. For example, the transmitter 101 transmits a DL signal under the control of the controller 103.

The DL signal may include, for example, a downlink data signal and control information (for example, DCI). Further, the DL signal may include information indicating scheduling regarding signal transmission of the terminal 20 (for example, UL grant). Further, the DL signal may include upper layer control information (for example, Radio Resource Control (RRC) control information). Further, the DL signal may include a reference signal.

Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 10 transmits control information to the terminal 20 using the PDCCH, and transmits a downlink data signal using the PDSCH.

Examples of reference signals included in the DL signal include demodulation reference signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), and Sounding Reference Signal (SRS). ), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using PDSCH.

The receiving unit 102 receives the UL signal transmitted from the terminal 20. For example, the receiving unit 102 receives a UL signal under the control of the control unit 103.

The control unit 103 controls the communication operation of the base station 10, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102.

For example, the control unit 103 acquires information such as data and control information from an upper layer and outputs it to the transmission unit 101. Further, the control unit 103 outputs the data, control information, etc. received from the reception unit 102 to the upper layer.

For example, the control unit 103 determines the resources (or channels) used for transmitting and receiving DL signals based on the signals (for example, data and control information, etc.) received from the terminal 20 and/or the data and control information obtained from the upper layer. and/or allocate resources used for transmitting and receiving UL signals. Information regarding the allocated resources may be included in the control information transmitted to the terminal 20.

In particular, the control unit 103 determines the PDSCH transmission method and/or the PUSCH transmission method (reception method at the base station 10), generates information regarding the determined transmission method, and transmits the information from the transmission unit 101. . Further, the control unit 103 performs transmission control and/or reception control based on the determined PDSCH transmission method and/or PUSCH transmission method. For example, the control unit 103 may receive feedback information (for example, HARQ-ACK) generated based on the PDSCH transmission method via the reception unit 102, and may perform retransmission control based on the feedback information. .

<Terminal configuration>
FIG. 3 is a block diagram showing an example of the configuration of terminal 20 according to this embodiment. The terminal 20 includes, for example, a receiving section 201, a transmitting section 202, and a control section 203. The terminal 20 communicates with the base station 10 wirelessly, for example.

The receiving unit 201 receives the DL signal transmitted from the base station 10. For example, the receiving unit 201 receives a DL signal under the control of the control unit 203.

The transmitter 202 transmits the UL signal to the base station 10. For example, the transmitter 202 transmits a UL signal under the control of the controller 203.

The UL signal may include, for example, an uplink data signal and control information (for example, UCI). For example, information regarding the processing capability of the terminal 20 (eg, UE capability) may be included. Further, the UL signal may include a reference signal.

Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel includes PUSCH (Physical Uplink Shared Channel), and the control channel includes PUCCH (Physical Uplink Control Channel). For example, the terminal 20 receives control information from the base station 10 using the PUCCH, and transmits an uplink data signal using the PUSCH.

The reference signal included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, reference signals such as DMRS and PTRS are used for demodulating uplink data signals and are transmitted using an uplink channel (for example, PUSCH).

The control unit 203 controls communication operations of the terminal 20, including reception processing in the reception unit 201 and transmission processing in the transmission unit 202.

For example, the control unit 203 acquires information such as data and control information from an upper layer and outputs it to the transmission unit 202. Further, the control unit 203 outputs, for example, data and control information received from the reception unit 201 to an upper layer.

For example, the control unit 203 controls the transmission of information fed back to the base station 10. The information fed back to the base station 10 may include, for example, HARQ-ACK, channel state information (CSI), or scheduling request (SR). good. Information fed back to the base station 10 may be included in the UCI. The UCI is transmitted on PUCCH resources.

In particular, the control unit 203 acquires information regarding the PDSCH transmission method (the reception method in the terminal 20) and/or the PUSCH transmission method, and performs transmission control and/or reception control based on the acquired information. For example, the control section 203 may generate feedback information (for example, HARQ-ACK) based on the PDSCH transmission method, and perform control to transmit the generated feedback information via the transmission section 202.

Note that the channels used for transmitting DL signals and the channels used for transmitting UL signals are not limited to the examples described above. For example, channels used for transmitting DL signals and channels used for transmitting UL signals may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). The RACH may be used, for example, to transmit DCI including a Random Access Radio Network Temporary Identifier (RA-RNTI).

<CG PUSCH>
Next, CG PUSCH will be explained. CG PUSCH is a method of performing UL transmission using PUSCH based on a UL grant (for example, may be called a Configured Grant, Configured UL Grant, etc.) configured by an upper layer. For CG PUSCH, UL resources have already been allocated to the terminal 20, and the terminal 20 can spontaneously perform UL transmission using the configured resources, so low-delay communication can be expected.

In Release 16, two types of CG PUSCH, Type 1 and Type 2, were specified.

Activation/deactivation of Type 1 CG PUSCH depends only on RRC-configuration and does not depend on DCI. In Type 1 CG PUSCH, parameters used for uplink transmission (also referred to as CG parameters, CG configuration (Configured Grant Configuration) information, etc.) are set in the terminal 20 using only upper layer signaling. Specifically, the parameters of Type 1 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config" and "rrc-ConfiguredUplinkGrant". That is, the base station 10 uses "ConfiguredGrantConfig", "pusch-Config" and "rrc-ConfiguredUplinkGrant" to instruct the terminal 20 about parameters for uplink transmission. The terminal 20 stores the received parameters as a configuration grant.

When the Type 1 CG PUSCH is activated, the terminal 20 determines that one or more configuration grants have been triggered (or activated), and transmits the configured resources (referred to as CG resources, transmission occasions, etc.). ), PUSCH transmission may be performed without dynamic grants.

Activation/deactivation of Type 2 CG PUSCH depends on RRC-configuration and DCI. One DCI can only activate one CG PUSCH and can deactivate multiple CG PUSCHs. In Type 2 CG PUSCH, parameters used for uplink transmission are set in the terminal 20 using upper layer signaling. Further, some of the parameters used for uplink transmission are notified to the terminal by DCI. Specifically, the transmission parameters of Type 2 CG PUSCH are provided by “ConfiguredGrantConfig”, “pusch-Config” and “activation DCI”. That is, the base station 10 uses "ConfiguredGrantConfig," "pusch-Config," and "activation DCI" to instruct the terminal 20 about uplink transmission parameters. Terminal 20 stores the received parameters.

When the Type 2 CG PUSCH is activated and the activation DCI is notified, the terminal 20 determines that one or more configuration grants have been triggered (or activated), and uses the resources configured in the upper layer. may be used to perform PUSCH transmission without dynamic grants. The activation DCI may be CRC (Cyclic Redundancy Check) scrambled with a predetermined identifier (for example, CS-RNTI: Configured Scheduling RNTI). Note that the activation DCI may be used to control deactivation, retransmission, etc. of the configuration grant.

Furthermore, the terminal 20 releases or deactivates the resource (PUSCH) corresponding to the Configured Grant based on the DCI that deactivates the Configured Grant or the expiration of a predetermined timer (the elapse of a predetermined time). deactivate)). In addition, below, the configuration of CG PUSCH may be abbreviated as "CG configuration".

<SPS PDSCH>
Next, SPS PDSCH will be explained. In the SPS PDSCH, periodic resources for downlink (DL) Semi-Persistent Scheduling (SPS) are configured by an upper layer. Activation/deactivation (release) of transmission using the resource in the SPS PDSCH depends on the activation DCI. The activation DCI may be CRC (Cyclic Redundancy Check) scrambled using a predetermined identifier (for example, CS-RNTI: Configured Scheduling RNTI).

In the SPS PDSCH, parameters used for downlink transmission (which may also be referred to as SPS parameters, semi-persistent scheduling configuration information, etc.) are set in the terminal 20 using upper layer signaling. Further, some of the parameters used for downlink transmission are notified to the terminal by DCI. Specifically, the transmission parameters of SPS PDSCH are provided by “sps-Config” and “activation DCI”. That is, the base station 10 uses "sps-Config" and "activation DCI" to instruct the terminal 20 about downlink transmission parameters. Terminal 20 stores the received parameters. In addition, below, the configuration of SPS PDSCH may be abbreviated as "SPS configuration".

<CG PUSCH parameters>
For example, the parameters in ConfiguredGrantConfig (hereinafter referred to as "CGC-CG parameters (group)") for Type 1 and/or Type 2 CG PUSCH are as follows. Note that when CGC-CG parameters are provided by both ConfiguredGrantConfig and pushch-Config, the terminal 20 may apply the CGC-CG parameters indicated in ConfiguredGrantConfig to PUSCH transmission. Furthermore, if there is a CGC-CG parameter that is not provided by ConfiguredGrantConfig, the terminal 20 may apply the CGC-CG parameter indicated by pushch-Config to PUSCH transmission.

(Example of CGC-CG parameters)
- periodicity: Used to indicate the period of PUSCH transmission corresponding to the set grant.
- repK: Used to indicate the number of repeated PUSCH transmissions.
- repK-RV: Used to indicate information regarding the redundancy version of repeated PUSCH transmission.
-frequencyHopping: Used to effectively set either intra-slot frequency hopping or inter-slot frequency hopping. If the field is not present, frequency hopping may not be applied.
- cg-DMRS-Configuration: Used to indicate the DMRS configuration of PUSCH corresponding to the set grant.
- mcs-Table: Used to indicate the MSC table that the terminal 20 uses for PUSCH without transform precoding. If the field is not present, terminal 20 may use a 64QAM table.
- mcs-TableTransformPrecoder: Used to indicate the MSC table used by the terminal 20 for PUSCH with transform precoding. If the field is not present, terminal 20 may use a 64QAM table.
- uci-OnPUSCH: Used to indicate information regarding UCI transmission using PUSCH.
-resourceAllocation: Used to indicate that one of 'resource allocation type 0', 'resource allocation type 1', and 'dynamic switch' is set.
- rbg-Size: Used to indicate the RBG size of PUSCH.
- powerControlLoopToUse: Used to indicate a closed control loop applied to PUSCH transmission.
- p0-PUSCH-Alpha: Used to calculate PUSCH transmission power.
- transformPrecoder: Used to indicate whether transform precoding is selected for PUSCH transmission.
- phy-PriorityIndex: Used to indicate the PHY priority of CG PUSCH in at least PHY layer collision processing. Note that value p0 indicates low priority, and value p1 indicates high priority.
- cg-nrofHARQ-Process: Used to indicate the HARQ process number.
・cg-nrofSlots: Used to indicate the number of allocated slots set in the grant period following the time instance set in the grant offset.
-betaOffsetCG-UCI: Used to indicate the beta offset of CG-UCI in CG-PUSCH.
・configuredGrantTimer: Used to indicate the initial value of the configured grant timer as a multiple of periodicity. If cg-RetransmissonTimer is set, and the HARQ process is shared between different configured grants on the same BWP, the periodicity of the configuredGrantTimer is set to the same value for the configurations that share the HARQ process on this BWP. .

For example, the parameters in rrc-ConfiguredUplinkGrant (hereinafter referred to as "rrc-CUG-CG parameters (group)") for Type 1 CG PUSCH are as follows. Note that rrc-ConfiguredUplinkGrant is used to indicate grant information configured in Type 1 CG PUSCH.

(Example of rrc-CUG-CG parameters)
- timeDomainOffset: Used to indicate the offset associated with the system frame numbered 0.
-timeDomainAllocation: Used to indicate the combination of the PUSCH mapping type, the PUSCH start symbol, and the number of consecutively allocated symbols.
-frequencyDomainAllocation: Used to indicate PUSCH frequency resource allocation.
- antennaPort: Used to indicate antenna port information for PUSCH transmission.
- dmrs-SeqInitialization: Identifier used for scrambling of DMRS sequence for PUSCH transmission.
- precodingAndNumberOfLayers: Used to indicate precoding and the number of layers for PUSCH transmission.
- srs-ResourceIndicator: Used to indicate the SRS (Sounding Reference Signal) resource used.
- mcsAndTBS: Used to indicate modulation order, target coding rate, and transport block size.
-frequencyHoppingOffset: Used to indicate the value of frequency hopping offset.
- pathlossReferenceIndex: Used to indicate the reference signal used for PUSCH path loss estimation.
- pushch-RepTypeIndicator: Used to indicate whether the terminal 20 follows the operation for PUSCH repetition type A or the operation for PUSCH repetition type B for each Type 1 configured grant configuration. value pusch-RepTypeA enables "PUSCH repetition type A", and value pusch-RepTypeB enables "PUSCH repetition type B".
-frequencyHoppingPUSCH-RepTypeB: Used to indicate the frequency hopping method of Type 1 CG when pushch-RepTypeIndicator is set to "pusch-RepTypeB". Value interRepetition enables "Inter-repetition frequency hopping" and value interSlot enables "Inter-slot frequency hopping". Note that if this field does not exist, frequency hopping will not be enabled in Type 1 CG.

For example, the parameters specified by the activation DCI for Type 2 CG PUSCH (hereinafter referred to as "DCI-CG parameters (group)") include the following:

(Example of DCI-CG parameters)
- timeDomainAllocation: Used to indicate the combination of starting symbol and length and PUSCH mapping type.
-frequencyDomainAllocation: Used to indicate frequency domain resource allocation.
・MCS index: Used to indicate the MCS (Modulation and Coding Scheme) index.
- antenna port indication: Used to indicate the antenna port.
- precoding and number of layers indication: Used to indicate precoding and the number of layers.
-SRS resource indicator: Used to indicate resources for SRS (Sounding Reference Signal).
- power control related parameter indication: Used to indicate parameters related to transmission power control.

<SPS PDSCH parameters>
For example, the parameters in SPS-Config (hereinafter referred to as "SC-SPS parameter(s)") for SPS PDSCH include the following.

(Example of SC-SPS parameters)
- periodicity: Used to indicate the period of SPS PDSCH.
- n1PUCCH-AN: HARQ-ACK (Hybrid automatic repeat request acknowledgment) for SPS PDSCH Used to indicate PUCCH resources.
- mcs-Table: Used to indicate the MCS table applied to reception of SPS PDSCH.
- pdsch-AggregationFactor: Used to indicate the number of repeated PDSCH transmissions.

For example, the parameters instructed by the activation DCI for the SPS PDSCH (hereinafter referred to as "DCI-SPS parameters (group)") include the following.

(Example of DCI-SPS parameters)
- timeDomainAllocation: Used to indicate the combination of starting symbol and length and PDSCH mapping type.
-frequencyDomainAllocation: Used to indicate frequency domain resource allocation.
・MCS index: Used to indicate the MCS (Modulation and Coding Scheme) index.
- TCI state indication: Used to indicate the state of TCI (Transmission Configuration Indicator) for PDSCH.
- antenna port indication: Used to indicate the antenna port.
-Priority of HARQ-ACK: Used to indicate the priority of HARQ-ACK.
- K1: Used to indicate the number of slots from the slot in which data is scheduled on the PDSCH to the slot in which HARQ-ACK for the PDSCH is transmitted.

<Other parameters>
Parameters other than the above (hereinafter referred to as "other-CG/SPS parameters (group)") that are notified from the base station 10 to the terminal 20 include, for example, the following.

(Example of other-CG/SPS parameters)
- PDSCH/PUSCH length: Used to indicate the length of PDSCH and/or PUSCH.
-number of PRBs: Used to indicate the number of PRBs (Physical Resource Blocks).

<The circumstances that led to this disclosure>
In NR, as an example of scheduling different from dynamic scheduling, PUSCH (CG PUSCH) based on CG (Configured Grant) is considered in uplink (UL), and SPS (Semi-Persistent (SPS PDSCH) is being considered.

In Release 16, the configuration of CG PUSCH (Configured Grant Physical Uplink Shared Channel) and the configuration of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) is defined (for example, Non-Patent Document 2).

Additionally, in Release 16, it is specified that the parameters of CG PUSCH and SPS PDSCH are determined by RRC (Radio Resource Control) configuration and activation DCI (Downlink Control Information).

Additionally, in Release 17, NR is considering various technologies for methods called Ultra-Reliable and Low Latency Communications (URLLC) and Industrial Internet of Things (IIoT).

In Release 17, extended reality (XR) such as virtual reality (VR) and mixed reality (MX) will be considered, and XR scenarios, requirements, key performance indicators (KPI) and Evaluation methods are being considered. The targeted requirements for XR are to consider aspects of capacity, latency, mobility, and energy savings. Furthermore, the above considerations are being continued in Release 18 as well.

As a consideration item regarding XR, matters related to improving the capacity specific to XR are being considered. This study considers mechanisms that provide more efficient resource allocation and scheduling for the characteristics of XR services. Here, the characteristics of the XR service include characteristics such as periodicity, multiflow, jitter, delay, and reliability. For example, this study calls for expansion of SPS and CG, and expansion of dynamic scheduling and grants.

Below, as examples of SPS and CG expansion, an expansion that applies CBG (Code Block Group) and an expansion that applies 2 TB (Transport Block) will be explained. Note that TB is a unit of an information bit sequence, and may be, for example, at least one of a unit of an information bit sequence allocated to one subframe or a unit of scheduling. If the TBS (Transport Block Size) exceeds a predetermined threshold (for example, 6144 bits), the TB is divided into one or more segments (Code Block), and encoding is performed in segment units (Code block division: Code Block Size). Block Segmentation). Each Code Block is concatenated as a CW (Code Word). Scrambling, data modulation, etc. are performed on the codeword. When a TB is composed of one or more Code Blocks, the retransmission control unit is assumed to be at least one of a Code Block, a CBG including multiple Code Blocks, a TB, and multiple bundled TBs. The terminal performs error detection for each retransmission control unit, generates a bit indicating A/N (hereinafter also referred to as HARQ-ACK bit), and feeds it back (transmits) to the radio base station.

First, we will explain downlink transmission and uplink transmission to which CBG is applied, and HARQ-ACK CB to which CBG is applied. Next, 2 TB and SPS HARQ-ACK will be explained. Note that in the following description, downlink transmission and uplink transmission to which CBG is applied are described as CBG based PDSCH transmission and CBG based PUSCH transmission, respectively. Note that while PDSCH transmission is an operation on the base station side, a terminal performs a PDSCH reception operation in the downlink. Therefore, PDSCH transmission may be considered as PDSCH reception at the terminal. For example, a terminal supporting CBG based PDSCH transmission may be considered to mean that the terminal supports CBG based PDSCH reception.

(CBG based PDSCH transmission)
Section 5.1.7 of TS 38.214 describes CBG based PDSCH transmission. CBG based PDSCH transmission and HARQ-ACK feedback for CBG based PDSCH transmission in the case of SPS PDSCH and the case of PDSCH scheduled by DCI 1_0 or DCI 1_2, and in the case of DCI 1_1 when DCI 1_1 can schedule multiple PDSCHs. It is not supported in three cases: one or more PDSCHs scheduled by

On the other hand, CBG-based PDSCH transmission and HARQ-ACK feedback for CBG-based PDSCH transmission are supported in the case of scheduling one PDSCH. The case of scheduling one PDSCH is, for example, the case where DCI 1_1 can schedule only one PDSCH, and the PDSCH is scheduled by DCI 1_1 when "PDSCH-CodeBlockGroupTransmission" is set in the serving cell. be.

(CBG based PUSCH transmission)
Section 6.1.5 of TS 38.214 describes CBG based PUSCH transmission. CBG based PUSCH transmission is divided into the case of CG PUSCH, the case of PUSCH scheduled by DCI 0_0 or DCI 0_2, and the case of PUSCH scheduled by DCI 0_1 when the SCS is 480kHz or 960kHz and DCI 0_1 can schedule multiple PUSCH. It is not supported in three cases: the case of one or more PUSCHs, and the case of multiple PUSCHs scheduled by DCI 0_1 when the SCS is 120kHz and DCI 0_1 schedules multiple PUSCHs.

On the other hand, CBG based PUSCH transmission is supported in the case of scheduling one specific PUSCH and in the case of scheduling multiple specific PUSCHs. The case of scheduling one specific PUSCH is, for example, when DCI 0_1 can schedule only one PDSCH and "PUSCH-CodeBlockGroupTransmission" is set in the serving cell. This is the case of PDSCH. In addition, the case where specific multiple PUSCHs are scheduled is, for example, when the SCS is 120kHz and DCI 0_1 can schedule multiple PUSCHs, but when DCI 0_1 schedules only one PUSCH and "PUSCH-CodeBlockGroupTransmission" is This is the case of one PUSCH scheduled by DCI 0_1 when configured in the serving cell.

(CBG based HARQ-ACK CB)
Section 9.1.1 of TS 38.213 describes the behavior of the CBG based HARQ-ACK codebook (CB) determination. When the terminal is given “PDSCH-CodeBlockGroupTransmission” for the serving cell, the terminal receives the PDSCH scheduled by DCI 1_1. The received PDSCH includes one or more CBGs of TB. Additionally, the terminal is given "maxCodeBlockGroupsPerTransportBlock". "maxCodeBlockGroupsPerTransportBlock" indicates the maximum number of CBGs for generating HARQ-ACK information bits for TB reception in the serving cell.

(two-TB)
Section 5.1.3.2 of TS 38.214 etc. describes two-TB. In Rel-15/16/17, two-codeword transmission is supported for PDSCH scheduled by DCI 1_1. On the other hand, two-codeword transmission is not supported for SPS PDSCH. Also, two-codeword transmission is not supported for PDSCHs scheduled by DCI 1_0 or DCI 1_2. Furthermore, two-codeword transmission for PUSCH is being considered in Rel-18 MIMO.

In the case where the upper layer parameter "maxNrofCodeWordsScheduledByDCI" indicates that two codeword transmission is enabled, for the corresponding TB, the parameter I indicating _MCS = 26 and the parameter rv _id = indicating RV. If 1, one of the two TBs is disabled by DCI 1_1. If both TBs are valid, the two TBs (TB1 and TB2) are mapped to CW0 and CW1, respectively. Also, if only one TB is valid, the valid TB is always mapped to the first CW. That is, if at most two codeword transmissions are enabled by RRC, the DCI may dynamically disable one TB. Note that DCI 1_1 has fields that indicate MCS, NDI, and RV for each TB.

(Type 2 SPS HARQ-ACK CB)
A case in which HARQ-ACK feedback for one or more SPS PDSCH receptions, with no corresponding PDCCH, is multiplexed with HARQ-ACK feedback for dynamically scheduled PDSCHs and/or SPS PDSCH releases. is assumed. In this case, HARQ-ACK feedback for one or more SPS PDSCH receptions with no corresponding PDCCH is different from HARQ-ACK feedback for dynamically scheduled PDSCH and/or SPS PDSCH release. Will be added later.

FIG. 4 is a diagram showing an example of HARQ-ACK CB. Figure 4 shows “HARQ-ACK for TB based DG PDSCH”, “HARQ-ACK for CBG based DG PDSCH”, and “HARQ-ACK for SPS PDSCH” included in HARQ-ACK CB. It will be done. Note that the horizontal direction in FIG. 4 represents the order (or arrangement order) defined in the data structure of the HARQ-ACK CB. For example, in the example of FIG. 4, in HARQ-ACK CB, "HARQ-ACK for TB based DG PDSCH" is listed first, and then "HARQ-ACK for CBG based DG PDSCH" is listed. Note that this order does not have to correspond to the HARQ-ACK processing order and the HARQ-ACK transmission order.

"HARQ-ACK for TB based DG PDSCH" corresponds to the HARQ-ACK codebook for TB based DG PDSCH, "HARQ-ACK for CBG based DG PDSCH" corresponds to the HARQ-ACK codebook for CBG based DG PDSCH However, "HARQ-ACK for SPS PDSCH" corresponds to the codebook of HARQ-ACK for SPS PDSCH.

Note that some CBs of the HARQ-ACK CB may be referred to as sub-codebooks. Also, for example, the configuration of a part of the HARQ-ACK CB and the configuration that includes HARQ-ACK information may be expressed in a different notation that indicates where the information is stored (for example, another notation such as field, segment, or slot). May be replaced. Note that below, the configuration included in the sub-codebook may be described as a field.

In addition, as shown in Figure 4, in "HARQ-ACK for SPS PDSCH", HARQ-ACK information (for example, bits) is stored in ascending order of DL slot index for each SPS configuration index of a certain serving cell index. ordered. In the example of FIG. 4, fields such as "DL slot index #n" and "DL slot index #n+i" are arranged in order in "SPS configuration index #1" of "Cell index #1". Note that "Cell index #1" is a field that includes HARQ-ACK corresponding to index #1 of the serving cell, and "SPS configuration index #1" includes HARQ-ACK that corresponds to index #1 of SPS configuration. "DL slot index #n" is a field that includes HARQ-ACK corresponding to DL slot index #n.

Note that "#X" in each figure including FIG. 4 and in the following description indicates an index. X may be an integer of 0 or more, or an integer of 1 or more. Furthermore, in the following description, in an example where the index is not a number, the indexes of adjacent fields may be continuous values or non-consecutive values. Further, the number of fields in each figure including FIG. 4 is an example, and the present disclosure is not limited thereto. For example, the number of fields included in a certain CB or sub-codebook may be one.

Next, the HARQ-ACK information is ordered in ascending order of the SPS configuration index for each serving cell index. In the example of FIG. 4, fields such as "SPS configuration index #1" and "SPS configuration index #2" are lined up in order in "Cell index #1."

Next, the HARQ-ACK information is ordered in ascending order of serving cell index. In the example of FIG. 4, fields such as "Cell index #1" and "Cell index #2" are arranged in order in "HARQ-ACK for SPS PDSCH."

As mentioned above, NR supports CBG based PDSCH transmission, CBG based PUSCH transmission, and two-codeword PDSCH for dynamically scheduled PDSCH and PUSCH. As a result, communication efficiency can be expected to improve in the case of dynamically scheduled PDSCH and PUSCH.

Considering the case where SPS PDSCH is used for TB transmission with a large packet size for XR traffic in Rel-18, SPS PDSCH transmission with CBG applied or CBG applied It is desirable to support CG PUSCH transmission, SPS PDSCH transmission using two-codeword, or CG PUSCH transmission using two-codeword.

In addition, below, SPS PDSCH transmission to which CBG is applied may be described as "CBG based SPS PDSCH transmission", and CG PUSCH transmission to which CBG is applied may be described as "CBG based CG PUSCH transmission". In addition, these may be collectively written as "CBG based CG PUSCH/CG PUSCH transmission."

In addition, SPS PDSCH transmission to which two-codeword is applied may be written as "two-codeword SPS PDSCH transmission", and CG PUSCH transmission to which two-codeword is applied may be written to "two-codeword CG PUSCH transmission". be.

One aspect of the present disclosure describes how communication efficiency can be improved by applying CBG and/or 2 TB in SPS and CG as an example of scheduling different from dynamic scheduling.

<Proposal 1>
Proposal 1 proposes criteria for determining whether the terminal 20 should apply CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission.

(Alt 1)
In Alt 1, the terminal 20 uses existing upper layer parameters (RRC parameters) that are configuration information for enabling CBG based transmission in DG PDSCH/DG PUSCH, for example, PDSCH-CodeBlockGroupTransmission/CG PUSCH for SPS PDSCH. Set whether to apply CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission based on PUSCH-CodeBlockGroupTransmission for.

For example, if PDSCH-CodeBlockGroupTransmission is set in the serving cell, the terminal 20 applies CBG based SPS PDSCH transmission to every SPS configuration on the serving cell, and otherwise applies TB based SPS PDSCH transmission may also be applied. Similarly, if PUSCH-CodeBlockGroupTransmission is set in the serving cell, the terminal 20 applies CBG based CG PUSCH transmission to every CG configuration on the serving cell, and otherwise applies TB based CG PUSCH transmission may also be applied.

According to Alt 1, whether or not to apply CBG based SPS PDSCH/CG PUSCH transmission is determined using existing RRC parameters, so signaling overhead can be reduced.

(Alt 2)
In Alt 2, the terminal 20 sets another upper layer parameter (RRC parameter) that is configuration information for enabling CBG based transmission in SPS PDSCH/CG PUSCH in PDSCH-ServingCellConfig or PUSCH-ServingCellConfig, for example, Based on SPS-PDSCH-codeBlockGroupTransmission/CG-PUSCH-codeBlockGroupTransmission, set whether to apply CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission.

For example, if SPS-PDSCH-codeBlockGroupTransmission is set in the serving cell, the terminal 20 applies CBG based SPS PDSCH transmission to every SPS configuration on the serving cell, and otherwise applies TB based SPS PDSCH transmission may be applied. Similarly, if CG-PUSCH-codeBlockGroupTransmission is set in the serving cell, the terminal 20 applies CBG based CG PUSCH transmission to every CG configuration on the serving cell; based CG PUSCH transmission may be applied.

(Alt 3)
In Alt 3, the terminal 20 uses upper layer parameters (RRC parameters), which are individual information set for each SPS configuration or CG configuration, and are setting information for enabling CBG based transmission in SPS PDSCH/CG PUSCH. For example, based on SPS-PDSCH-codeBlockGroupTransmission/CG-PUSCH-codeBlockGroupTransmission, it is set whether to apply CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission.

For example, if SPS-PDSCH-codeBlockGroupTransmission is set to SPS configuration, the terminal 20 applies CBG based SPS PDSCH transmission to the SPS configuration, and otherwise applies TB based SPS PDSCH transmission may also be applied. Similarly, if CG-PUSCH-codeBlockGroupTransmission is set to CG configuration, the terminal 20 applies CBG based CG PUSCH transmission to the CG configuration; otherwise, TB based CG PUSCH transmission may also be applied.

(Alt 4)
Alt 4 is a combination of Alt 1 and Alt 2. That is, in Alt 4, the terminal 20 uses existing upper layer parameters (RRC parameters) that are configuration information for enabling CBG based transmission in DG PDSCH/DG PUSCH, and in PDSCH-ServingCellConfig or PUSCH-ServingCellConfig. Based on another upper layer parameter (RRC parameter) that is the configuration information for enabling DG PDSCH/DG PUSCH, it is possible to select between CBG based SPS PDSCH/CG PUSCH transmission and TB based SPS PDSCH/CG PUSCH transmission. Set whether to apply.

For example, if both PDSCH-CodeBlockGroupTransmission and SPS-PDSCH-codeBlockGroupTransmission are set in the serving cell, the terminal 20 applies CBG based SPS PDSCH transmission to all SPS configurations on the serving cell, and applies CBG based SPS PDSCH transmission to all SPS configurations on the serving cell. In some cases, TB based SPS PDSCH transmission may be applied. Similarly, if both PUSCH-CodeBlockGroupTransmission and CG-PUSCH-codeBlockGroupTransmission are set in the serving cell, the terminal 20 applies CBG based CG PUSCH transmission to all CG configurations on the serving cell, and applies CBG based CG PUSCH transmission to all CG configurations on the serving cell. In some cases, TB based CG PUSCH transmission may be applied.

Alternatively, if at least one of PDSCH-CodeBlockGroupTransmission and SPS-PDSCH-codeBlockGroupTransmission is set in the serving cell, the terminal 20 applies CBG based SPS PDSCH transmission to every SPS configuration on the serving cell, and otherwise In this case, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of PUSCH-CodeBlockGroupTransmission and CG-PUSCH-codeBlockGroupTransmission is set in the serving cell, the terminal 20 applies CBG based CG PUSCH transmission to every CG configuration on the serving cell, and In other cases, TB based CG PUSCH transmission may be applied.

(Alt 5)
Alt 5 is a combination of Alt 1 and Alt 3. That is, in Alt 5, the terminal 20 uses existing upper layer parameters (RRC parameters), which are configuration information for enabling CBG based transmission in DG PDSCH/DG PUSCH, and individual settings for each SPS configuration or CG configuration. CBG based SPS PDSCH/CG PUSCH transmission and TB based SPS PDSCH/CG PUSCH based on upper layer parameters (RRC parameters), which are configuration information for enabling CBG based transmission in SPS PDSCH/CG PUSCH. Set which transmission to apply.

For example, if PDSCH-CodeBlockGroupTransmission is set and the RRC parameter (for example, CbgEnable) in the SPS configuration is set (for example, as "enabled"), the terminal 20 transmits the CBG-based SPS PDSCH transmission may be applied; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if PUSCH-CodeBlockGroupTransmission is set and the RRC parameter (for example, CbgEnable) in the CG configuration is set (for example, as "enabled"), the terminal 20 transmits the CBG to the CG configuration. based CG PUSCH transmission, otherwise TB based CG PUSCH transmission may be applied.

Alternatively, if at least one of PDSCH-CodeBlockGroupTransmission and RRC parameters in the SPS configuration is set, the terminal 20 applies CBG based SPS PDSCH transmission to the SPS configuration; otherwise, , TB based SPS PDSCH transmission may be applied. Similarly, if at least one of PUSCH-CodeBlockGroupTransmission and RRC parameters in the CG configuration is set, the terminal 20 applies CBG based CG PUSCH transmission to the CG configuration; otherwise, may apply TB based CG PUSCH transmission.

(Alt 6)
Alt 6 may be a combination of any of Alts 1 to 5 and the activation DCI format.

For example, as a combination of Alt 1 and activation DCI format, if PDSCH-CodeBlockGroupTransmission is set and an SPS configuration is activated by DCI format 1_1 or DCI 0_1, the terminal 20 uses CBG for the SPS configuration. based SPS PDSCH transmission may be applied; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if PUSCH-CodeBlockGroupTransmission is set and CG configuration is activated by DCI format 1_1 or DCI 0_1, the terminal 20 applies CBG based CG PUSCH transmission to the CG configuration and applies it to the CG configuration. In other cases, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 1 and activation DCI format, if at least one of the PDSCH-CodeBlockGroupTransmission setting and the activation of the SPS configuration by DCI format 1_1 or DCI 0_1 is performed, the terminal 20 configures the SPS configuration. In other cases, CBG based SPS PDSCH transmission may be applied, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of the PUSCH-CodeBlockGroupTransmission setting and the activation of the CG configuration by DCI format 1_1 or DCI 0_1 is performed, the terminal 20 configures the CBG based CG PUSCH transmission for the CG configuration. In other cases, TB based CG PUSCH transmission may be applied.

In addition, as a combination of Alt 2 and activation DCI format, if PDSCH-ServingCellConfig is set and SPS configuration is activated by DCI format 1_1 or DCI 0_1, terminal 20 uses CBG based for SPS configuration. SPS PDSCH transmission may be applied; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if PUSCH-ServingCellConfig is set and CG configuration is activated by DCI format 1_1 or DCI 0_1, terminal 20 applies CBG based CG PUSCH transmission to CG configuration, and otherwise In this case, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 2 and activation DCI format, the terminal 20 configures the SPS configuration when at least one of the PDSCH-ServingCellConfig setting and the SPS configuration activation using DCI format 1_1 or DCI 0_1 is performed. In other cases, CBG based SPS PDSCH transmission may be applied, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of the PUSCH-ServingCellConfig setting and the activation of CG configuration by DCI format 1_1 or DCI 0_1 is performed, the terminal 20 configures CBG based CG PUSCH transmission for CG configuration. otherwise, TB based CG PUSCH transmission may be applied.

Additionally, as a combination of Alt 3 and activation DCI format, if SPS-PDSCH-codeBlockGroupTransmission is set to SPS configuration and SPS configuration is activated by DCI format 1_1 or DCI 0_1, the terminal 20 In other cases, CBG based SPS PDSCH transmission may be applied, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if CG-PUSCH-codeBlockGroupTransmission is set to CG configuration and CG configuration is activated by DCI format 1_1 or DCI 0_1, terminal 20 transmits CBG based CG PUSCH transmission for the CG configuration. In other cases, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 3 and activation DCI format, the terminal 20 has at least one of the following: setting SPS-PDSCH-codeBlockGroupTransmission to SPS configuration, and activating SPS configuration by DCI format 1_1 or DCI 0_1. In this case, CBG based SPS PDSCH transmission may be applied to the SPS configuration, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of the setting of CG-PUSCH-codeBlockGroupTransmission to the CG configuration and the activation of the CG configuration by DCI format 1_1 or DCI 0_1 is performed, the terminal 20 , CBG based CG PUSCH transmission may be applied; otherwise, TB based CG PUSCH transmission may be applied.

In addition, as a combination of Alt 4 and activation DCI format, the terminal 20 can perform For SPS configuration, CBG based SPS PDSCH transmission may be applied, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if both PUSCH-CodeBlockGroupTransmission and CG-PUSCH-codeBlockGroupTransmission are set in the serving cell and CG configuration is activated by DCI format 1_1 or DCI 0_1, terminal 20 configures CBG for CG configuration. based CG PUSCH transmission, otherwise TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 4 and activation DCI format, the terminal 20 configures at least one of the following: setting PDSCH-CodeBlockGroupTransmission, setting SPS-PDSCH-codeBlockGroupTransmission to the serving cell, and activating SPS configuration using DCI format 1_1 or DCI 0_1. is implemented, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, when at least one of the settings of PUSCH-CodeBlockGroupTransmission, the setting of CG-PUSCH-codeBlockGroupTransmission to the serving cell, and the activation of CG configuration by DCI format 1_1 or DCI 0_1 is performed, the terminal 20 performs CG For the configuration, CBG based CG PUSCH transmission may be applied, and in other cases, TB based CG PUSCH transmission may be applied.

In addition, as a combination of Alt 5 and activation DCI format, the terminal 20 is configured when both PDSCH-CodeBlockGroupTransmission and SPS-PDSCH-codeBlockGroupTransmission are set to SPS configuration, and SPS configuration is activated by DCI format 1_1 or DCI 0_1. In this case, CBG based SPS PDSCH transmission may be applied to the SPS configuration, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if both PUSCH-CodeBlockGroupTransmission and CG-PUSCH-codeBlockGroupTransmission are set in the CG configuration, and the CG configuration is activated by DCI format 1_1 or DCI 0_1, the terminal 20 , CBG based CG PUSCH transmission may be applied; otherwise, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 5 and activation DCI format, the terminal 20 can configure at least PDSCH-CodeBlockGroupTransmission, SPS-PDSCH-codeBlockGroupTransmission to SPS configuration, and activation of SPS configuration by DCI format 1_1 or DCI 0_1. If one is implemented, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, when at least one of the following is performed, the terminal 20 sets PUSCH-CodeBlockGroupTransmission, sets CG-PUSCH-codeBlockGroupTransmission to CG configuration, and activates CG configuration by DCI format 1_1 or DCI 0_1. CBG based CG PUSCH transmission may be applied to the CG configuration, and in other cases, TB based CG PUSCH transmission may be applied.

(Alt 7)
Alt 7 may be a combination of any of Alts 1 to 5 and the DCI field in activation DCI.

For example, as a combination of Alt 1 and the DCI field in the activation DCI, if the terminal 20 is configured with PDSCH-CodeBlockGroupTransmission and the SPS configuration is activated with a DCI format that has a DCI field indicating CBG based SPS PDSCH transmission. In this case, CBG based SPS PDSCH transmission may be applied to the SPS configuration, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if PUSCH-CodeBlockGroupTransmission is set and a CG configuration is activated using a DCI format that has a DCI field indicating CBG based CG PUSCH transmission, the terminal 20 transmits CBG based CG to the CG configuration. PUSCH transmission may be applied; otherwise, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 1 and the DCI field in the activation DCI, the terminal 20 configures at least one of the PDSCH-CodeBlockGroupTransmission and the activation of the SPS configuration in a DCI format with a DCI field indicating CBG based SPS PDSCH transmission. is implemented, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of the PUSCH-CodeBlockGroupTransmission setting and the activation of a CG configuration in a DCI format that has a DCI field indicating CBG based CG PUSCH transmission is performed, the terminal 20 configures the CG configuration. In other cases, CBG based CG PUSCH transmission may be applied; otherwise, TB based CG PUSCH transmission may be applied.

Also, as a combination of Alt 2 and the DCI field in the activation DCI, if the terminal 20 is configured with PDSCH-ServingCellConfig and the SPS configuration is activated with a DCI format that has a DCI field indicating CBG based SPS PDSCH transmission. In some cases, CBG based SPS PDSCH transmission may be applied to the SPS configuration, and in other cases, TB based SPS PDSCH transmission may be applied. Similarly, if PUSCH-ServingCellConfig is set and the CG configuration is activated using a DCI format that has a DCI field indicating CBG based CG PUSCH transmission, the terminal 20 transmits CBG based CG PUSCH to the CG configuration. In other cases, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 2 and the DCI field in the activation DCI, the terminal 20 configures at least one of the PDSCH-ServingCellConfig and the activation of the SPS configuration in the DCI format with the DCI field indicating CBG based SPS PDSCH transmission. is implemented, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of the PUSCH-ServingCellConfig setting and the activation of the CG configuration in the DCI format that has a DCI field indicating CBG based CG PUSCH transmission is performed, the terminal 20 configures the CG configuration. , CBG based CG PUSCH transmission may be applied; otherwise, TB based CG PUSCH transmission may be applied.

In addition, as a combination of Alt 3 and the DCI field in activation DCI, the terminal 20 is configured with SPS configuration according to the DCI format in which SPS-PDSCH-codeBlockGroupTransmission is set to SPS configuration and has a DCI field indicating CBG based SPS PDSCH transmission. If activated, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if CG-PUSCH-codeBlockGroupTransmission is set in a CG configuration and the CG configuration is activated using a DCI format that has a DCI field indicating CBG based CG PUSCH transmission, the terminal 20 In other cases, CBG based CG PUSCH transmission may be applied; otherwise, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 3 and the DCI field in the activation DCI, the terminal 20 sets SPS-PDSCH-codeBlockGroupTransmission to the SPS configuration, and configures the SPS configuration according to the DCI format with the DCI field indicating CBG based SPS PDSCH transmission. If at least one of the activations has been performed, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if at least one of the setting of CG-PUSCH-codeBlockGroupTransmission to the CG configuration and the activation of the CG configuration according to the DCI format having a DCI field indicating CBG based CG PUSCH transmission are performed, the terminal 20 , CBG based CG PUSCH transmission may be applied to the CG configuration, and in other cases, TB based CG PUSCH transmission may be applied.

Additionally, as a combination of the DCI fields in Alt 4 and activation DCI, the terminal 20 has both PDSCH-CodeBlockGroupTransmission and SPS-PDSCH-codeBlockGroupTransmission set in the serving cell, and has a DCI field indicating CBG based SPS PDSCH transmission. If the SPS configuration is activated by the DCI format, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, in the terminal 20, if both PUSCH-CodeBlockGroupTransmission and CG-PUSCH-codeBlockGroupTransmission are set in the serving cell, and the CG configuration is activated using a DCI format that has a DCI field indicating CBG based CG PUSCH transmission, For CG configuration, CBG based CG PUSCH transmission may be applied, and in other cases, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of the DCI field in Alt 4 and activation DCI, the terminal 20 has a DCI field indicating the setting of PDSCH-CodeBlockGroupTransmission, the setting of SPS-PDSCH-codeBlockGroupTransmission to the serving cell, and the CBG based SPS PDSCH transmission. If at least one of the activations of the SPS configuration in DCI format has been performed, apply CBG based SPS PDSCH transmission to the SPS configuration, otherwise apply TB based SPS PDSCH transmission. Good too. Similarly, the terminal 20 performs at least one of the following: setting PUSCH-CodeBlockGroupTransmission, setting CG-PUSCH-codeBlockGroupTransmission to the serving cell, and activating CG configuration in a DCI format with a DCI field indicating CBG based CG PUSCH transmission. If so, CBG based CG PUSCH transmission may be applied to the CG configuration; otherwise, TB based CG PUSCH transmission may be applied.

Furthermore, as a combination of the DCI field in Alt 5 and activation DCI, the terminal 20 has the DCI field indicating CBG based SPS PDSCH transmission that both PDSCH-CodeBlockGroupTransmission and SPS-PDSCH-codeBlockGroupTransmission are set to SPS configuration. If the SPS configuration is activated using the DCI format, CBG based SPS PDSCH transmission may be applied to the SPS configuration; otherwise, TB based SPS PDSCH transmission may be applied. Similarly, if both PUSCH-CodeBlockGroupTransmission and CG-PUSCH-codeBlockGroupTransmission are set in the CG configuration, and the CG configuration is activated using the DCI format that has a DCI field indicating CBG based CG PUSCH transmission, the terminal 20 , CBG based CG PUSCH transmission may be applied to the CG configuration, and in other cases, TB based CG PUSCH transmission may be applied.

Alternatively, as a combination of Alt 5 and the DCI field in the activation DCI, the terminal 20 configures the PDSCH-CodeBlockGroupTransmission, the SPS-PDSCH-codeBlockGroupTransmission to the SPS configuration, and the DCI field indicating CBG based SPS PDSCH transmission. If at least one activation of an SPS configuration with a DCI format has been performed, apply CBG based SPS PDSCH transmission to that SPS configuration, otherwise apply TB based SPS PDSCH transmission. You may. Similarly, the terminal 20 performs at least one of the following: setting PUSCH-CodeBlockGroupTransmission, setting CG-PUSCH-codeBlockGroupTransmission to CG configuration, and activating CG configuration in a DCI format with a DCI field indicating CBG based CG PUSCH transmission. If implemented, CBG based CG PUSCH transmission may be applied to the CG configuration; otherwise, TB based CG PUSCH transmission may be applied.

(About the number of CBG of SPS PDSCH/CG PUSCH)
The maximum value of CBG per 1 TB of SPS PDSCH or CG PUSCH may be set as follows.

(Option 1)
For SPS/CG configuration on the serving cell, if CBG based SPS PDSCH/CG PUSCH transmission is applied, the maximum value of CBG per 1 TB of SPS PDSCH or CG PUSCH depends on the parameters configured for each serving cell (e.g. N) may be determined by

(Option 2)
For each SPS/CG configuration, if CBG based SPS PDSCH/CG PUSCH transmission is applied, the maximum number of CBGs per 1 TB of SPS PDSCH or CG PUSCH depends on the parameters set in the SPS/CG configuration (e.g. SPS/ N_i) of CG configuration #i).

(effect)
According to Proposal 1 explained above, CBG based transmission can be supported even in SPS PDSCH/CG PUSCH, which is quasi-static scheduling, so it is possible to reduce retransmission frequency, reduce delay, improve transmission efficiency, and Reliability can be ensured. For example, when transmitting 1 TB divided into 4 code blocks, if an error occurs in only one code block, only that code block needs to be retransmitted, so the amount of data to be retransmitted can be calculated in TB units. This can be reduced compared to the case of transmission using

Furthermore, according to Proposal 1, it is possible to adaptively switch between CBG based transmission and TB based transmission in SPS PDSCH/CG PUSCH. For example, CBG based SPS PDSCH/CG PUSCH transmission can be applied to SPS/CG configuration for XR traffic, and TB based SPS PDSCH/CG PUSCH transmission can be applied to SPS/CG configuration for URLLC traffic.

<Proposal 2>
Proposal 2 describes HARQ-ACK CB for CBG based SPS PDSCH. In the following, the HARQ-ACK bit included in the HARQ-ACK CB for SPS PDSCH will be referred to as "SPS HARQ-ACK bit."

Note that TB based SPS PDSCH and CBG based SPS PDSCH may be collectively referred to as SPS PDSCH. Additionally, TB based DG PDSCH and CBG based DG PDSCH may be collectively referred to as DG PDSCH. Furthermore, TB based SPS PDSCH and TB based DG PDSCH may be collectively referred to as TB based PDSCH. CBG based SPS PDSCH and CBG based DG PDSCH may be collectively referred to as CBG based PDSCH.

FIG. 5 is a diagram showing an example of HARQ-ACK CB of Proposal 2. In the HARQ-ACK CB shown in Figure 5, “HARQ-ACK for TB based DG PDSCH” corresponds to a sub-codebook that includes HARQ-ACK for TB based DG PDSCH, and “HARQ-ACK for CBG based DG PDSCH” , corresponds to the sub-codebook including HARQ-ACK for CBG based DG PDSCH. In the HARQ-ACK CB shown in Figure 5, "HARQ-ACK for SPS PDSCH (including TB and CBG based SPS)" means HARQ-ACK for TB based SPS PDSCH and/or HARQ-ACK for CBG based SPS PDSCH. Supports sub-codebooks including ACK.

In the following explanation, "HARQ-ACK for SPS PDSCH (including TB and CBG based SPS)" refers to an example that includes both HARQ-ACK for TB based SPS PDSCH and HARQ-ACK for CBG based SPS PDSCH. However, "HARQ-ACK for SPS PDSCH (including TB and CBG based SPS)" does not need to include at least one of HARQ-ACK for TB based SPS PDSCH and HARQ-ACK for CBG based SPS PDSCH. . In addition, hereinafter, "HARQ-ACK for SPS PDSCH (including TB and CBG based SPS)" may be abbreviated as "HARQ-ACK for SPS PDSCH" or "SPS HARQ-ACK CB."

For the configuration of "HARQ-ACK for SPS PDSCH" shown in FIG. 5, a configuration based on one of the options shown below may be adopted.

(Option 1)
In option 1, the SPS HARQ-ACK CB construction procedure described using FIG. 4 is reused as the HARQ-ACK CB construction procedure for CBG based SPS PDSCH. Here, only the number of HARQ-ACK bits may differ between the HARQ-ACK CB for CBG based SPS PDSCH and the HARQ-ACK CB for TB based SPS PDSCH. In other words, while the number of HARQ-ACK bits is different between the HARQ-ACK CB for CBG based SPS PDSCH and the HARQ-ACK CB for TB based SPS PDSCH, elements other than the number of HARQ-ACK bits are It may be common between the HARQ-ACK CB for SPS PDSCH and the HARQ-ACK CB for TB based SPS PDSCH. Elements other than the number of HARQ-ACK bits include, for example, a convention regarding the order of HARQ-ACK information (eg, fields) in the HARQ-ACK CB.

The order of the SPS HARQ-ACK bits (field order) in the SPS HARQ-ACK CB is based first on the ascending order of the cell index of the serving cell, and then in the ascending order of the index of the SPS configuration in each of the serving cell indices. DL slots may then be based on ascending indexes of the DL slots in each of the indexes of the SPS configuration. This SPS HARQ-ACK bit order (field order) may be common between the HARQ-ACK CB for CBG-based SPS PDSCH and the HARQ-ACK CB for TB-based SPS PDSCH.

(Option 2)
In option 2, cells are classified into cells that perform TB based SPS PDSCH transmission and cells that perform CBG based SPS PDSCH transmission. For example, in option 2, in HARQ-ACK for SPS PDSCH, there is first a field corresponding to a cell that performs only TB based SPS PDSCH transmission, and then a field corresponding to a cell that performs only CBG based SPS PDSCH transmission. exists. Here, for example, a field corresponding to a cell that performs only TB based SPS PDSCH transmission may include only the HARQ-ACK bit for the TB based SPS PDSCH received from a cell that performs only TB based SPS PDSCH transmission. In addition, the field corresponding to a cell that only performs CBG based SPS PDSCH transmission may include only the HARQ-ACK bit for CBG based SPS PDSCH received from a cell that only performs CBG based SPS PDSCH transmission. handle.

Note that a cell that only performs TB based SPS PDSCH transmission may correspond to a cell that performs TB based SPS PDSCH transmission but does not perform CBG based SPS PDSCH transmission. Furthermore, a cell that only performs CBG based SPS PDSCH transmission may correspond to a cell that performs CBG based SPS PDSCH transmission but does not perform TB based SPS PDSCH transmission.

Note that the number of cells that perform only TB-based SPS PDSCH transmission may be one or multiple. Furthermore, if there are multiple cells that perform only TB based SPS PDSCH transmission, a set of multiple cells may be configured. There is no particular limitation on the order of cells that perform only TB based SPS PDSCH transmission.

For example, for the order of multiple cells that perform only TB-based SPS PDSCH transmission, the order of the SPS HARQ-ACK CB construction procedure described using FIG. 4 may be reused. For example, the order of multiple cells that only perform TB based SPS PDSCH transmission is first based on the order of cell index of the serving cell, then based on the order of index of SPS configuration, and then based on order of index of DL slot. good. Illustratively, the order of multiple cells that perform only TB based SPS PDSCH transmission is first based on the ascending cell index of the serving cell, then based on the ascending index of the SPS configuration, and then the order of the DL slots. May be based on ascending index order.

FIG. 6 is a diagram showing an example of HARQ-ACK CB of Option 2 of Proposal 2. In option 2, as shown in FIG. 6, in "HARQ-ACK for SPS PDSCH", "Cell with only TB based SPS" exists first, and then "Cell with only CBG based SPS" exists. Here, "Cell with only TB based SPS" corresponds to a field that only includes HARQ-ACK for TB based SPS PDSCH, and "Cell with only CBG based SPS" includes only HARQ-ACK for CBG based SPS PDSCH May correspond to the field.

In addition, in FIG. 6, "Cell with only TB based SPS" and "Cell with only CBG based SPS" each show an example, but "Cell with only TB based SPS" and "Cell with only CBG" based SPS" may be two or more.

As shown in Figure 6, the order of the fields included in "Cell with only TB based SPS" is first based on the order of the cell index of the serving cell, "Cell index #i_1" and "Cell index #i_2". There is. The order of the fields included in "Cell index #i_1" is based on the order of the SPS configuration index, as shown in "SPS configuration index #j_1" and "SPS configuration index #j_2." Next, the order of the cells included in "SPS configuration index #j_1" is based on the order of the DL slot index, as shown by "DL slot index #n_1" and "DL slot index #n_2".

Although omitted in FIG. 6, the order of the cells included in "Cell index #i_2" may be based on the order of the index of the SPS configuration. Further, the order of cells included in "SPS configuration index #j_2" may be based on the order of DL slot indexes.

Note that there may be multiple cells that perform only CBG-based SPS PDSCH transmission. Furthermore, a cell that performs only CBG-based SPS PDSCH transmission may be configured as a set of multiple cells. When a plurality of cells are included in a cell that only performs CBG-based SPS PDSCH transmission, the order of the cells is not particularly limited. For example, any of the following options 2-1 and 2-2 may be adopted.

(Option 2-1)
In option 2-1, the order of multiple fields included in a cell that only performs CBG based SPS PDSCH transmission reuses the existing ordering principle. The existing ordering principle may be the order of the SPS HARQ-ACK CB construction procedure described using FIG. 4. For example, the order of fields included in a cell that only performs CBG based SPS PDSCH transmission is first based on the order of the cell index of the serving cell, then based on the order of the index of the SPS configuration, and then the order of the index of the DL slot. May be based on the order of Illustratively, the order of multiple fields included in a cell that only performs CBG based SPS PDSCH transmission is first based on the ascending cell index of the serving cell, then based on the ascending index of the SPS configuration, and then , may be based on ascending order of DL slot index.

FIG. 7 is a diagram showing an example of HARQ-ACK CB of option 2-1 of proposal 2. In option 2-1, in "HARQ-ACK for SPS PDSCH", "Cell with only TB based SPS" exists first, and then "Cell with only CBG based SPS" exists, as in the example in Figure 6. exist. Here, "Cell with only TB based SPS" corresponds to a field that only includes HARQ-ACK for TB based SPS PDSCH, and "Cell with only CBG based SPS" includes only HARQ-ACK for CBG based SPS PDSCH May correspond to the field.

In addition, in FIG. 7, "Cell with only TB based SPS" and "Cell with only CBG based SPS" each show an example, but "Cell with only TB based SPS" and "Cell with only CBG based SPS" may be two or more.

As shown in Figure 7, the order of the fields included in "Cell with only CBG based SPS" is first based on the order of the cell index of the serving cell, "Cell index #i_1" and "Cell index #i_2". There is. The order of the fields included in "Cell index #i_1" is based on the order of the SPS configuration index, as shown in "SPS configuration index #j_1" and "SPS configuration index #j_2." Next, the order of the fields included in "SPS configuration index #j_1" is based on the order of the DL slot index, as indicated by "DL slot index #n_1" and "DL slot index #n_2."

Although omitted in FIG. 7, the order of the fields included in "Cell index #i_2" may be based on the order of the SPS configuration index. Further, the order of the fields included in “SPS configuration index #j_2” may be based on the order of the DL slot index.

(Option 2-2)
In option 2-2, the order of fields included in a cell performing CBG based SPS PDSCH transmission may be initially based on the order of the cell index of the serving cell. Next, the order of multiple fields included in a cell that performs CBG based SPS PDSCH transmission is that fields corresponding to the SPS configuration of TB based transmission are arranged first, and then fields corresponding to the SPS configuration of CBG based transmission are arranged. The fields are lined up. In this case, among the fields corresponding to the cell index of a certain serving cell, the SPS configuration field for TB based transmission is arranged first, and then the SPS configuration field for CBG based transmission is arranged next.

In the index of certain SPS configurations of TB based transmission, existing ordering principles may be reused. The existing ordering principle may be the order of the SPS HARQ-ACK CB construction procedure described using FIG. 4. For example, the order of fields among the fields corresponding to an index of a certain SPS configuration of a TB based transmission may be based first on the order of the index of the SPS configuration and then on the order of the index of the DL slot. Illustratively, the order of the fields within the fields corresponding to the index of a certain SPS configuration of a TB based transmission is first based on the ascending index of the SPS configuration, and then based on the ascending index of the DL slot. It's fine.

FIG. 8 is a diagram showing an example of HARQ-ACK CB of option 2-2 of proposal 2. In option 2-2, as shown in Figure 8, in "HARQ-ACK for SPS PDSCH", "Cell with only TB based SPS" exists first, and then "Cell with CBG based SPS" exists. . "Cell with only CBG based SPS" in FIG. 7 is replaced with "Cell with CBG based SPS" in FIG. 8. Here, "Cell with only TB based SPS" corresponds to the field that contains only HARQ-ACK for TB based SPS PDSCH, and "Cell with CBG based SPS" corresponds to the field that contains HARQ-ACK for CBG based SPS PDSCH. You can handle it.

In addition, in FIG. 8, "Cell with only TB based SPS" and "Cell with CBG based SPS" each show an example, but "Cell with only TB based SPS" and "Cell with CBG based SPS" ” may be two or more.

As shown in Figure 8, the order of the fields included in "Cell with CBG based SPS" is first based on the order of the cell index of the serving cell, "Cell index #i_1" and then "Cell index #i_2". . In the field corresponding to "Cell index #i_1", "TB based SPS configuration" is listed first, followed by "CBG based SPS configuration". Here, "TB based SPS configuration" corresponds to SPS configuration of TB based transmission, and "CBG based SPS configuration" corresponds to SPS configuration of CBG based transmission.

Next, the order of the fields included in "TB based SPS configuration" is based on the order of the index of SPS configuration, as shown in "SPS configuration index #j_1" and "SPS configuration index #j_2". Next, the order of the cells included in "SPS configuration index #j_1" is based on the order of the DL slot index, as shown by "DL slot index #m_1" and "DL slot index #m_2".

Although it is omitted in Figure 8, in "Cell index #i_2", "TB based SPS configuration" may be listed in the same way as in "Cell index #i_1", followed by "CBG based SPS configuration". . Further, the order of the fields included in “SPS configuration index #j_2” may be based on the order of the DL slot index.

Note that the order of cells included in "CBG based SPS configuration", which is omitted in FIG. 8, is not particularly limited. For example, any order of option 2-2A and option 2-2B below may be adopted.

(Option 2-2A)
In option 2-2A, the order of the fields included in "CBG based SPS configuration" may be based first on the index order of the SPS configuration and then on the order of the DL slot index. For example, the order of the SPS configuration indexes may be in ascending order or in descending order. Further, the order of the indexes of the DL slots may be in ascending order of the indexes or may be in descending order.

FIG. 9 is a diagram showing an example of option 2-2A of proposal 2. In FIG. 9, as in FIG. 8, "TB based SPS configuration" is listed, followed by "CBG based SPS configuration". Note that "TB based SPS configuration" and "CBG based SPS configuration" shown in FIG. 9 are fields corresponding to the cell index of a certain serving cell (for example, corresponding to "Cell index #i_1") field).

As shown in Figure 9, the order of the fields included in "CBG based SPS configuration" is based on the order of the SPS configuration index, as shown in "SPS configuration index #k_1", "SPS configuration index #k_2", and so on. There is. Next, the order of the fields included in "SPS configuration index #k_1" is based on the order of the DL slot index, as indicated by "DL slot index #n_1" and "DL slot index #n_2."

Although omitted in FIG. 9, the order of the fields included in "SPS configuration index #j_2" may be based on the order of the DL slot index. For example, the order of the SPS configuration index may be ascending index order or descending index order. Further, the order of the indexes of the DL slots may be in ascending order of the indexes or may be in descending order.

(Option 2-2B)
In option 2-2B, the order of the fields included in "CBG based SPS configuration" is first based on the specific number order for the HARQ-ACK CB, then based on the index order of the SPS configuration, and then based on the order of the index of the DL May be based on slot index order. For example, the order of the specific numbers regarding HARQ-ACK may be in ascending order or in descending order of the specific numbers regarding HARQ-ACK. Further, the order of the indexes of the SPS configuration may be in ascending order of the index or may be in descending order. Further, the order of the indexes of the DL slots may be in ascending order of the indexes or may be in descending order.

Here, the specific number regarding HARQ-ACK CB may be, for example, the number of CBGs, the number of CBGs per TB, or the number of HARQ-ACK bits. . For example, the number of CBGs is the number of CBGs per PDSCH for the SPS configuration. For example, the number of CBGs per TB is the number of CBGs per TB per PDSCH for the SPS configuration. The number of CBGs may be replaced by the maximum number of CBGs. For example, the number of HARQ-ACK bits is the number of HARQ-ACK bits per PDSCH for the SPS configuration.

FIG. 10 is a diagram showing an example of option 2-2B of proposal 2. In FIG. 10, similarly to FIG. 8, "TB based SPS configuration" is lined up, followed by "CBG based SPS configuration". Note that "TB based SPS configuration" and "CBG based SPS configuration" shown in FIG. 10 are fields corresponding to the cell index of a certain serving cell (for example, corresponding to "Cell index #i_1") field).

As shown in FIG. 10, cells indicated as "SPS configuration with (maximum) N_1 CBGs" and "SPS configuration with (maximum) N_1 CBGs" are arranged in order in "CBG based SPS configuration". Here, "SPS configuration with (maximum) N_1 CBGs" corresponds to the field where the maximum number of CBGs for the SPS configuration is N_1 and "SPS configuration with (maximum) N_2 CBGs" corresponds to the field where the maximum number of CBGs for the SPS configuration is N_1 corresponds to the field where is N_2. Note that, for example, in the case of ascending order of the maximum number of CBGs, N_2 may be larger than N_1.

The order of the fields in "SPS configuration with (maximum) N_1 CBGs" is then based on the order of the SPS configuration index, as shown in "SPS configuration index #k_1", "SPS configuration index #k_2", and so on. There is. Next, the order of the cells included in "SPS configuration index #k_1" is based on the order of the DL slot index, as indicated by "DL slot index #n_1" and "DL slot index #n_2."

(Option 3)
In option 3, the order is first based on the cell index of the serving cell, but the field corresponding to TB based SPS configuration exists before the field corresponding to CBG based SPS configuration in the ordering within the same cell. . In the TB based SPS configuration, they are ordered in the order of the index of the SPS configuration, and then in the order of the index of the DL slot. Furthermore, in the CBG based SPS configuration, the order is placed in the order of the index of the SPS configuration, and then in the order of the index of the DL slot.

FIG. 11 is a diagram showing an example of option 3 of proposal 2. The order of the fields in "HARQ-ACK for SPS PDSCH" in FIG. 11 is first based on the order of the cell index of the serving cell. In "Cell index #i_1", "TB based SPS configuration" exists before "CBG based SPS configuration". “TB based SPS configuration” and “CBG based SPS configuration” are included in the field whose cell index is #i_1. The order of the fields included in "TB based SPS configuration" is based on the order of the SPS configuration index, as shown in "SPS configuration index #j_1" and "SPS configuration index #j_2". Next, the order of the fields included in "SPS configuration index #j_1" is based on the order of the DL slot index, as indicated by "DL slot index #m_1" and "DL slot index #m_2."

Although omitted in FIG. 11, the order of fields included in "CBG based SPS configuration" may be the same as the order of fields included in "TB based SPS configuration". For example, the order of the fields included in “CBG based SPS configuration” may be based first on the order of the index of the SPS configuration and then on the order of the index of the DL slot.

The differences between option 3 and option 2 will be explained. As mentioned above, in option 2, in Figure 6, "Cell with only TB based SPS" corresponds to a cell that performs only TB based SPS PDSCH transmission, and "Cell with only TB based SPS" corresponds to a cell that performs only CBG based SPS PDSCH transmission. Differences in cell behavior are first taken into account and classified, and then ordered according to the index of each cell, as shown in “only CBG based SPS”. On the other hand, option 3 does not take cell differences into account when ordering based on the order of cell indexes.

(Option 4)
In options 1 to 3 above, the codebook for SPS PDSCH (codebook "HARQ-ACK for SPS PDSCH") includes one or both of HARQ-ACK for TB based SPS PDSCH and HARQ-ACK for CBG based SPS PDSCH. Included examples are shown. In option 4, a sub-codebook for TB based SPS PDSCH and a sub-codebook for CBG based SPS PDSCH are distinguished. The sub-codebook for TB based SPS PDSCH includes HARQ-ACK for TB based SPS PDSCH. The sub-codebook for CBG based SPS PDSCH includes HARQ-ACK for CBG based SPS PDSCH.

The sub-codebook for TB based SPS PDSCH may be written as TB based SPS sub-codebook, or may be written in other notations. The sub-codebook for CBG based SPS PDSCH may be written as CBG based SPS sub-codebook, or may be written using other notations.

The positional relationship (for example, order) of the sub-codebook for TB based SPS PDSCH, the sub-codebook for CBG based SPS PDSCH, the sub-codebook for TB based DG PDSCH, and the sub-codebook for CBG based DG PDSCH is particularly , but not limited to. For example, either option 4-1 or option 4-2 below may be adopted.

(Option 4-1)
In option 4-1, the sub-codebook for TB based SPS PDSCH and the sub-codebook for CBG based SPS PDSCH are added after the codebook for DG PDSCH. The codebook for DG PDSCH corresponds to both the codebook for TB based DG PDSCH and the codebook for CBG based DG PDSCH. The codebook for DG PDSCH includes HARQ-ACK for DG PDSCH. In other words, the sub-codebook for TB based SPS PDSCH and the sub-codebook for CBG based SPS PDSCH are added after the HARQ-ACK for DG PDSCH (which may be referred to as DG HARQ-ACK).

In option 4-1, a configuration may be adopted in which a sub-codebook for SPS PDSCH is added after the codebook for DG PDSCH. In option 4-1, for example, the codebook for TB based DG PDSCH is arranged first, followed by the codebook for CBG based DG PDSCH, the sub-codebook for TB based SPS PDSCH, and the sub-codebook for CBG based SPS PDSCH. codebooks are arranged in order.

(Option 4-2)
In option 4-2, the sub-codebook for TB based SPS PDSCH is added after the codebook for TB based DG PDSCH, and the sub-codebook for CBG based SPS PDSCH is added after the codebook for CBG based DG PDSCH. In this case, the sub-codebook for TB based SPS PDSCH may be added before the codebook for CBG based DG PDSCH.

Option 4-2 may adopt a configuration in which a sub-codebook for CBG based PDSCH is added after the sub-codebook for TB based PDSCH. In option 4-2, for example, the codebook for TB based DG PDSCH is arranged first, followed by the sub-codebook for TB based SPS PDSCH, the codebook for CBG based DG PDSCH, and the sub-codebook for CBG based SPS PDSCH. codebooks are arranged in order.

FIG. 12 is a diagram showing an example of option 4 of proposal 2. FIG. 12 shows an example of the order in the CB of each of the above-mentioned options 4-1 and 4-2.

In the example of option 4-1 in Figure 12, similar to Figure 5, in the HARQ-ACK CB, "HARQ-ACK for TB based DG PDSCH" and "HARQ-ACK for CBG based DG PDSCH" are placed first. "HARQ-ACK for CBG based DG PDSCH" is followed by "HARQ-ACK for TB based SPS PDSCH" and "HARQ-ACK for CBG based SPS PDSCH".

Note that in the configuration of option 4, the construction method of the TB based SPS sub-codebook and the CBG based SPS sub-codebook is not particularly limited. For example, in constructing a TB based SPS sub-codebook, any of the methods shown in options 2 and/or 3 may be utilized. Also, in constructing the CBG based SPS sub-codebook, any of the methods shown in options 2 and/or 3 may be used.

(About the number of HARQ-ACK bits in proposal 2)
In each option of Proposal 2 described above, the number of HARQ-ACK bits per SPS PDSCH is 1 for the TB based SPS configuration.

In each option of Proposal 2 described above, the number of HARQ-ACK bits per SPS PDSCH or the number of HARQ-ACK bits per TB is M for the CBG based SPS configuration. M may be an integer greater than or equal to 0. Further, M may be defined by any of Alt.1 to Alt.3 below.

(Alt.1)
In Alt.1, M may be the same for all CBG based SPS configurations of all serving cells.

In Alt.1, M may be the maximum value in a particular set of values. For example, the specific set of values is the set of number of CBGs (or maximum number of CBGs) for SPS of all serving cells. Also, for example, the specific set of values is a set of the number of CBGs (or the maximum number of CBGs) for the SPS of all serving cells and all CBG-based SPS configurations of each cell.

Note that the set of specific values does not have to be limited to these. Further, the number of values included in the specific value set may be one or more.

Note that in Alt.1, M is not limited to the maximum value in a specific set of values. M may be a value determined based on a specific set of values. M may be one of the minimum value, average value, and median value in a particular set of values. Alternatively, M may be defined by arithmetic processing based on the values included in a specific value set and/or the number of included values.

(Alt.2)
In Alt.2, M may be the same value for CBG based SPS configurations of the same serving cell. In this case, M may be different or the same for CBG based SPS configurations of different serving cells.

In Alt.2, in each serving cell, M may be the maximum value among a certain set of values. For example, the particular set of values is a set of the number of CBGs (or maximum number of CBGs) for SPS configured for a certain cell. If option 1 of proposal 1 above is applied, even if the particular set of values is the set of number of CBGs (or maximum number of CBGs) for SPS configured for a certain cell. good.

Also, for example, the set of specific values in a certain cell is a set of the number of CBGs (or the maximum number of CBGs) for SPS of all CBG-based SPS configurations of the cell. If option 2 of proposal 1 above is applied, the set of specific values may be the set of the number of CBGs (or the maximum number of CBGs) for the SPS of all CBG-based SPS configurations of the cell. .

(Alt.3)
In Alt.3, M may be different from each other or the same for each CBG based SPS configuration of the same serving cell. Furthermore, M may be different or the same for each of the CBG based SPS configurations of different serving cells.

For each CBG-based SPS configuration of each serving cell, M may be the number of CBGs (or the maximum number of CBGs) for the SPS configuration.

(effect)
According to Proposal 2 described above, the HARQ-ACK CB including the HARQ-ACK for the CBG based SPS PDSCH can be constructed in an appropriate format, so the feedback of the HARQ-ACK can be efficiently performed. For example, if CBG based SPS PDSCH transmission is performed in a certain cell, HARQ-ACK for CBG based SPS PDSCH may be It is distinguished from ACK and included in HARQ-ACK CB. A base station that receives such a HARQ-ACK CB can perform appropriate retransmission control, etc., thereby improving communication efficiency.

Note that the example of the order described as ascending order in each option of proposal 2 described above may be replaced with descending order. Further, in each option of proposal 2, ascending order and descending order may be mixed. For example, the order of a plurality of cells may be based on the ascending order of the SPS configuration index and the descending order of the DL slots.

Furthermore, although the HARQ-ACK CB is generated by the terminal, which construction procedure in Proposal 2 above is used to generate it may be determined by the terminal or may be instructed by the base station. However, it may be defined by the specifications.

<Proposal 3>
Proposal 3 proposes dynamic/adaptive updating of the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission.

The terminal 20 may dynamically update the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH according to instructions from the base station 10, or update the application of CBG based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH according to instructions from the base station 10. It may be updated adaptively according to a semi-static pattern.

(1) Dynamic update Below, (1-1) update instruction method and (1- 2) Explain the range of SPS/CG configuration that is subject to update.

(1-1) Update instruction method In this application, the following describes how to instruct dynamic update of application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH. Suggest options.

(Opt. 1) Instructions by DCI The base station 10 updates the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH to the terminal 20 by DCI. may be instructed. In this case, the following variations are possible.

(Opt. 1-1)
A new DCI format is prepared, and the base station 10 uses this new DCI format to apply CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH. You can instruct updates. In this case, the new DCI format may have a new RNTI (Radio Network Temporary Identifier), or may have an existing RNTI without a new RNTI.

(Opt. 1-2)
Alternatively, the base station 10 updates the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH using an existing DCI format with a new RNTI. You may give instructions.

(Opt. 1-3)
Alternatively, the base station 10 updates the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH using an existing DCI format with an existing RNTI. You may give instructions.

(Opt. 1-3A)
In this case, a new field may be provided, and information indicating update of application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission may be written in the new field. Further, there may be a plurality of new fields.

(Opt. 1-3B)
Alternatively, information indicating an update of the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission may be written in an unused field among the existing fields. Further, there may be a plurality of unused fields. In this case, the values of certain fields among the existing unused fields may be used to re-format the DCI format for the purpose of dynamically updating the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission. Used to indicate whether or not to interpret. The terminal 20 can determine whether to update the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission by reinterpreting the DCI format.

(Opt 2) Instructions by MAC CE The base station 10 instructs the terminal 20, by MAC CE, of application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH. You can instruct updates. In this case, the following variations are possible.

(Opt. 2-1)
A new MAC CE is prepared, and the base station 10 uses this new MAC CE to apply CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH. You can instruct updates.

(Opt. 2-2)
Alternatively, the base station 10 updates the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH using the existing MAC CE with new octets. You may give instructions.

(Opt. 2-3)
Alternatively, the base station 10 updates the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission to SPS PDSCH/CG PUSCH using the existing MAC CE with existing octets. You may give instructions. In this case, the reserved bit is used to indicate whether the MAC CE is interpreted for the purpose of updating CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission.

(1-2) Range of SPS/CG configurations subject to update In this application, we propose the range of SPS/CG configurations to which the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission is updated. do.

(Alt 1)
The range in which the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission is dynamically updated may be for each SPS/CG configuration by one DCI/MAC CE.

In this case, the base station 10 applies CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission in the SPS/CG configuration to the terminal 20 using an index indicating the target SPS/CG configuration. You may also instruct the update of .

(Alt 1-1)
The index may be explicitly indicated to the terminal 20 in a field/bit of the DCI or MAC CE.

(Alt 1-2)
Alternatively, the index may be implicitly indicated to the terminal 20. For example, when indicating dynamic updating of SPS PDSCH parameters by MAC CE, the target SPS configuration index is the SPS configuration index of the SPS PDSCH occasion that conveys the MAC CE.

(Alt 2)
The scope in which the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission is dynamically updated is for all (activated) SPS/CG configurations by one DCI/MAC CE. Good too.

(Alt 2-1)
In this case, common indication fields/bits may be set for all SPS/CG configurations.

(Alt 2-2)
Alternatively, a separate indication field/bit may be set for every SPS/CG configuration.

(Alt 3)
The range in which the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission is dynamically updated may be for each group of SPS/CG configuration by one DCI/MAC CE.

(Alt 3-1A)
In this case, a common indication field/bit for the group of SPS/CG configurations may be set.

(Alt 3-1B)
Alternatively, separate indication fields/bits for groups of SPS/CG configurations may be set.

In this case, the base station 10 informs the terminal 20 of the CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG transmission in the SPS/CG configuration, using an index indicating the group of the target SPS/CG configuration. Dynamic updating of the application of PUSCH transmission may be instructed.

(Alt 3-2A)
The index may be explicitly indicated to the terminal 20 in a field/bit of the DCI or MAC CE.

(Alt 3-2B)
Alternatively, the index may be implicitly indicated to the terminal 20. For example, when indicating dynamic updating of SPS PDSCH parameters by MAC CE, the target SPS configuration index is the SPS configuration index of the SPS PDSCH occasion that conveys the MAC CE.

(2) Update based on semi-static pattern Hereinafter, a case will be described in which the application of CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission is updated based on a semi-static pattern.

(Alt 1)
In Alt 1, the terminal 20 applies CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission based on the index value of SPS/CG occasion.

For example, if the index value N of SPS/CGoccasion satisfies N mod X1 = {Y1_1, Y1_2, ...}, the terminal 20 applies CBG based SPS PDSCH/CG PUSCH transmission, and N mod X1 = { If Y2_1, Y2_2, ...} is satisfied, TB based SPS PDSCH/CG PUSCH transmission may be applied. Here, N is an integer greater than or equal to 1, X1 is an integer greater than or equal to 2, and Y1_1, Y1_2, ... and Y2_1, Y2_2, ... are integers greater than or equal to 1 and less than or equal to (X1-1), respectively. , are different numbers from each other.

Note that the values of X1, Y1_1, Y1_2, Y2_1, Y2_2, etc. may be defined in advance in specifications or the like, or may be notified to the terminal 20 by upper layer signaling such as RRC.

If predefined in the specifications, different combinations of values may be defined for each XR service. Furthermore, when notification is made by upper layer signaling, different combinations of values may be configured for each XR service and/or each SPS/CG configuration.

(Alt 2)
In Alt 2, the terminal 20 applies CBG based SPS PDSCH/CG PUSCH transmission or TB based SPS PDSCH/CG PUSCH transmission based on the index value of the slot of SPS/CG occasion.

For example, if the index value M of the SPS/CGoccasion slot satisfies M mod X1 = {Y1_1, Y1_2, ...}, the terminal 20 applies CBG based SPS PDSCH/CG PUSCH transmission, and M mod = {Y2_1, Y2_2, ...}, TB based SPS PDSCH/CG PUSCH transmission may be applied. Here, M is an integer greater than or equal to 1, X1 is an integer greater than or equal to 2, and Y1_1, Y1_2, ... and Y2_1, Y2_2, ... are each an integer greater than or equal to 0 and less than or equal to (X1-1). and are different numbers from each other.

(3) Impact of update on HARQ-ACK CB The following describes the possible impact on HARQ-ACK CB when the application of CBG based SPS PDSCH transmission or TB based SPS PDSCH transmission is dynamically updated.

(3-1)
The HARQ-ACK CB described in at least Option 1 and Option 2-1 of Proposal 2 above can be reused as is even when the application of CBG based SPS PDSCH transmission or TB based SPS PDSCH transmission is dynamically updated.

(3-2)
Also, the order of the SPS HARQ-ACK bits in Option 2-2 and Option 3 of Proposal 2 above may be reused. However, it needs to be clarified whether SPS configuration should be included in "TB based SPS configuration" or "CBG based SPS configuration". Regarding this point, we propose the following alternatives.

(Alt 1)
In Alt 1, the terminal 20 may include one SPS configuration only in either the "TB based SPS configuration" part or the "CBG based SPS configuration" part.

(Alt 1-1)
The terminal 20 may determine which portion includes the SPS configuration based on whether CBG based SPS PDSCH transmission is enabled in the SPS configuration.

For example, if CBG based SPS PDSCH transmission is enabled for an SPS configuration, then the current SPS PDSCH of the SPS configuration with HARQ-ACK reported in the HARQ-ACK CB is either CBG based SPS PDSCH transmission or TB based SPS PDSCH transmission Regardless, the terminal 20 may include the SPS configuration in the "CBG based SPS configuration". In addition, the terminal 20 may include the SPS configuration in the "TB based SPS configuration" in other cases.

(Alt 1-2)
Furthermore, the terminal 20 determines the part to include the SPS configuration of HARQ-ACK reported in the HARQ-ACK CB, based on the presence or absence of CBG based SPS PDSCH transmission or TB based SPS PDSCH transmission for SPS PDSCH. It's okay.

For example, if there is a HARQ-ACK for CBG based SPS PDSCH transmission or TB based SPS PDSCH transmission in at least one SPS PDSCH of an SPS configuration to be reported in HARQ-ACK PUCCH, then that SPS configuration is configuration”. Then, the terminal 20 transmits the SPS PDSCH of the SPS configuration with the HARQ-ACK included in the same HARQ-ACK PUCCH to the TB based SPS PDSCH transmission or the SPS with the HARQ-ACK that should be reported to the same HARQ-ACK CB. Report in the "CBG/TB based SPS configuration" block, regardless of whether there is a configuration. In addition, the terminal 20 may include the SPS configuration in the "TB/CBG based SPS configuration" in other cases. That is, if there is a HARQ-ACK for CBG based SPS PDSCH transmission, the SPS PDSCH of the SPS configuration is reported in the CBG based SPS configuration block, and if there is no HARQ-ACK, the SPS PDSCH of the SPS configuration is reported. Report within a TB based SPS configuration block. Similarly, if there is a HARQ-ACK for TB based SPS PDSCH transmission, the SPS PDSCH of the SPS configuration is reported in the TB based SPS configuration block, and if there is no HARQ-ACK, the SPS PDSCH of the SPS configuration is reported. in a CBG based SPS configuration block.

(Alt 2)
In Alt 2, if there is a TB based SPS PDSCH and a CBG based SPS PDSCH of an SPS configuration that has HARQ-ACK to be reported in the HARQ-ACK CB, the terminal 20 converts the SPS configuration into the "TB based SPS configuration" part. and “CBG based SPS configuration” part.

For example, when including SPS configuration in the "TB based SPS configuration" part, HARQ-ACK of only SPS PDSCH with TB based SPS PDSCH transmission is included. In addition, when including SPS configuration in the "TB based SPS configuration" part, HARQ-ACK only for SPS PDSCH with CBG based SPS PDSCH transmission is included.

(3-3)
Separate sub-codebooks may also be reused, as described in option 4 of proposal 2 above. However, it needs to be clarified whether SPS PDSCH HARQ-ACK is included in the TB based sub-codebook or the CBG based sub-codebook. Regarding this point, we propose the following alternatives.

(Alt 1)
In Alt 1, the terminal 20 includes HARQ-ACKs for SPS PDSCHs of the same SPS configuration reported on the same PUCCH in the same sub-codebook.

(Alt 1-1)
The terminal 20 includes SPS PDSCH HARQ-ACK in the TB based sub-codebook or in the CBG based sub-codebook based on whether CBG based SPS PDSCH/CG PUSCH transmission is enabled in the SPS configuration. set.

For example, if CBG based SPS PDSCH/CG PUSCH transmission is enabled for an SPS configuration, the terminal 20 includes HARQ-ACK of SPS PDSCH in the CBG based sub-codebook. Otherwise, the terminal 20 includes the HARQ-ACK of the SPS PDSCH in the TB based sub-codebook.

(Alt 1-2)
The terminal 20 determines the HARQ-ACK of the SPS PDSCH based on whether there is a CBG based SPS PDSCH transmission/TB based SPS PDSCH transmission for the SPS PDSCH in the SPS configuration that has the HARQ-ACK that should be reported in the HARQ-ACK CB. Set whether to include ACK in TB based sub-codebook or CBG based sub-codebook.

For example, if there is a CBG based SPS PDSCH transmission for at least one SPS PDSCH to be reported in the HARQ-ACK PUCCH, the terminal 20 includes the HARQ-ACK for the SPS PDSCH in the SPS configuration in the CBG based sub-codebook. Otherwise, the terminal 20 includes HARQ-ACK for SPS PDSCH in the TB based sub-codebook.

Conversely, if there is a TB based SPS PDSCH transmission for at least one SPS PDSCH to be reported in the HARQ-ACK PUCCH, the terminal 20 includes the HARQ-ACK for the SPS PDSCH of the SPS configuration in the TB based sub-codebook. Otherwise, the terminal 20 includes HARQ-ACK for SPS PDSCH in the CBG based sub-codebook.

(Alt 2)
In Alt 2, the terminal 20 includes HARQ-ACKs for SPS PDSCHs of the same SPS configuration reported on the same PUCCH in separate sub-codebooks.

For example, the terminal 20 includes HARQ-ACK for SPS PDSCH of TB based SPS PDSCH transmission in the TB based sub-codebook, and includes HARQ-ACK for SPS PDSCH of CBG based SPS PDSCH transmission in the CBG based sub-codebook.

(4) Number of HARQ-ACK bits for each SPS PDSCH If the SPS configuration is valid for CBG based SPS PDSCH transmission, the terminal 20 takes into account the change in TB based SPS PDSCH transmission or CBG based SPS PDSCH transmission. Set the number of HARQ-ACK bits for each SPS PDSCH.

For example, for the CBG based SPS PDSCH in the SPS configuration, the number of HARQ-ACK bits in the CBG based SPS configuration described in Proposal 2 may be reused to set the number of HARQ-ACK bits (i.e., M bits).

Also, for TB based SPS PDSCH in SPS configuration, set the number of HARQ-ACK bits in CBG based SPS configuration to 1 bit or M bits (i.e., the same as the number of HARQ-ACK bits in CBG based SPS DSCH in the same SPS configuration). May be set.

Hereinafter, specific examples of Alt 1 and Alt 2 will be explained using FIG. 13.

In Alt 1-1 or Alt 1-2 above, in FIG. 13, SPS config#1 is included in the CBG based SPS configuration part. Also, both SPS PDSCHs in the two slots are in the position of SPS config#1.

In addition, in Alt 2 above, SPS config#1 is included in both the TB based SPS configuration part and the CBG based SPS configuration part in FIG. 13. In the TB based SPS configuration part, only the first PDSCH slot exists in the SPS config#1 position. Further, in the CBG based SPS configuration part, only the second PDSCH slot exists at the position of SPS config#1.

(effect)
According to Proposal 3 described above, when applying either CBG based transmission or TB based transmission to SPS PDSCH/CG PUSCH, it is possible to perform dynamic/adaptive updating of these. When CBG based SPS PDSCH/CG PUSCH transmission is applied, the application may be dynamically switched to TB based SPS PDSCH/CG PUSCH transmission according to instructions from the base station 10. Further, CBG based SPS PDSCH/CG PUSCH transmission and TB based SPS PDSCH/CG PUSCH transmission may be adaptively switched and applied according to a preset semi-static pattern.

<Proposal 4>
In Proposal 4, when supporting up to two codewords per 1 TB in SPS PDSCH or CG PUSCH, whether the terminal 20 applies single-codeword or two-codeword to SPS PDSCH/CG PUSCH. We propose the criteria for setting the criteria.

As a specific example of Proposal 4, we propose the following alternation.

(Alt 1)
In Alt 1, the terminal 20 uses upper layer parameters (RRC parameters) that are setting information for the maximum number of codewords set for each SPS/CG configuration or settings for the maximum number of codewords set for all SPS/CG configurations. Based on upper layer parameters (RRC parameters) that are information, for example, maxNrofCodeWordsSpsPdsch/maxNrofCodeWordsCgPusch, it is set whether to apply single-codeword or two-codeword to the SPS/CG configuration.

For example, if maxNrofCodeWordsSpsPdsch indicates two-codeword, the terminal 20 may receive two-codeword for the SPS configuration, and otherwise may receive single-codeword. Similarly, the terminal 20 may transmit two-codewords for the CG configuration if maxNrofCodeWordsCgPusch indicates two-codewords, and otherwise transmit single-codewords.

(Alt 2)
In Alt 2, the terminal 20 uses upper layer parameters (RRC parameters) that are setting information for the maximum number of codewords set for each SPS/CG configuration or settings for the maximum number of codewords set for all SPS/CG configurations. Based on the combination of upper layer parameters (RRC parameters) and activation DCI format, it is set whether to apply single-codeword or two-codeword to the SPS/CG configuration.

For example, the terminal 20 receives a two-codeword for the SPS configuration if maxNrofCodeWordsSpsPdsch indicates two-codeword and a specific field of the activation DCI format indicates a specific DCI format (e.g., DCI 1_1); In other cases, a single-codeword may be received. Similarly, the terminal 20 sends two-codeword for CG configuration if maxNrofCodeWordsCgPusch indicates two-codeword and a specific field of activation DCI format indicates a specific DCI format (e.g., DCI 1_1). , otherwise a single-codeword may be sent.

Alternatively, if at least one of maxNrofCodeWordsSpsPdsch indicates two-codeword and a specific field of the activation DCI format indicates a specific DCI format (for example, DCI 1_1), the terminal 20 configures the SPS configuration A two-codeword may be received for each case, and a single-codeword may be received for all other cases. Similarly, if at least one of maxNrofCodeWordsCgPusch indicates two-codeword and a specific field of the activation DCI format indicates a specific DCI format (e.g., DCI 1_1), the terminal 20 uses the CG Two-codewords may be sent for configuration, and single-codewords may be sent in other cases.

(Alt 3)
In Alt 3, the terminal 20 uses upper layer parameters (RRC parameters) that are setting information for the maximum number of codewords set for each SPS/CG configuration or settings for the maximum number of codewords set for all SPS/CG configurations. Set whether to apply single-codeword or two-codeword to the SPS/CG configuration based on the combination of upper layer parameters (RRC parameters) that are information and DCI field in activation DCI.

For example, the terminal 20 will receive two-codeword for the SPS configuration if maxNrofCodeWordsSpsPdsch indicates two-codeword and a specific field in the activation DCI indicates activation of two-codeword, otherwise may receive a single-codeword. Similarly, if maxNrofCodeWordsCgPusch indicates two-codeword and a specific field in the activation DCI indicates activation of two-codeword, the terminal 20 sends two-codeword for the CG configuration; In some cases, a single-codeword may be sent.

Alternatively, if at least one of maxNrofCodeWordsSpsPdsch indicates two-codeword and a specific field in the activation DCI indicates activation of two-codeword is satisfied, then the terminal 20 configures two-codeword for the SPS configuration. otherwise, a single-codeword may be received. Similarly, if at least one of maxNrofCodeWordsCgPusch indicates two-codeword and a specific field in the activation DCI indicates activation of two-codeword is satisfied, the terminal 20 determines that the CG configuration is two-codeword. codeword, otherwise a single-codeword may be sent.

Note that the specific field within the activation DCI may be a new DCI field, an existing DCI field, or a combination of fields indicating predefined values (for example, the MCS field and the RV field).

If the terminal 20 configures SPS/CG configuration with two-codeword transmission, the MCS/NDI/RV fields of the 1st TB and 2nd TB in the activation DCI are set for each codeword of SPS PDSCH/CG PUSCH. Each applies.

(effect)
According to Proposal 4 explained above, two-codeword can be supported even in SPS PDSCH/CG PUSCH, which is quasi-static scheduling, so it is possible to reduce retransmission frequency, reduce delay, improve transmission efficiency, and Reliability can be ensured.

<Proposal 5>
Proposal 5 describes HARQ-ACK CB in SPS PDSCH to which two transport blocks (2-TB) are applied, for example, HARQ-ACK CB for 2-TB based SPS PDSCH. Note that 2-TB may be replaced with 2-codeword (CW).

(Option 1)
In option 1, the SPS HARQ-ACK CB construction procedure described using FIG. 4 is reused as the HARQ-ACK CB construction procedure for 2-TB based SPS PDSCH. Here, only the number of HARQ-ACK bits may differ between the HARQ-ACK CB for 2-TB based SPS PDSCH and the HARQ-ACK CB for 1-TB based SPS PDSCH. In other words, while the number of HARQ-ACK bits differs between the HARQ-ACK CB for 2-TB based SPS PDSCH and the HARQ-ACK CB for 1-TB based SPS PDSCH, factors other than the number of HARQ-ACK bits may be common between the HARQ-ACK CB for 2-TB based SPS PDSCH and the HARQ-ACK CB for 1-TB based SPS PDSCH. Elements other than the number of HARQ-ACK bits include, for example, a convention regarding the order of fields (or HARQ-ACKs included in the fields) constituting the CB.

The SPS HARQ-ACK bit order (field order) in the 2-TB SPS HARQ-ACK CB is first based on the ascending cell index of the serving cell, then based on the ascending index of the SPS configuration, and then: May be based on ascending order of DL slot index. The order of the SPS HARQ-ACK bits may be the same between the HARQ-ACK CB for 2-TB based SPS PDSCH and the HARQ-ACK CB for 1-TB based SPS PDSCH.

(Option 2)
Option 2 of proposal 5 may adopt a similar order as option 2 of proposal 2. For example, in option 2 of proposal 5, in option 2 of proposal 2, "TB based SPS configuration" is replaced with "single-codeword based SPS configuration" and "CBG based SPS configuration" is replaced with "two-codeword based SPS configuration". A replaced configuration may be adopted.

(Option 3)
Option 3 of proposal 5 may adopt a similar order as option 3 of proposal 2. For example, in option 3 of proposal 5, in option 3 of proposal 2, "TB based SPS configuration" is replaced with "single-codeword based SPS configuration", and "CBG based SPS configuration" is replaced with "two-codeword based SPS configuration". A replaced configuration may be adopted.

(About the number of HARQ-ACK bits in proposal 5)
The number of HARQ-ACK bits for each SPS PDSCH in each option of Proposal 5 described above will be explained. The number of HARQ-ACK bits for each SPS PDSCH may be defined by any of Alt.1 to Alt.3 below.

(Alt.1)
In Alt.1, the number of HARQ-ACK bits per SPS PDSCH may be the same value for all SPS PDSCHs in all cells. The number of HARQ-ACK bits for any SPS PDSCH in any cell may be 2 if there is at least one SPS PDSCH configured to transmit at most 2 codewords across all cells. Otherwise, the number of HARQ-ACK bits for any SPS PDSCH in any cell may be 1. This may not be the case, for example, if there is no SPS PDSCH configured to transmit a maximum of 2 codewords across all cells.

(Alt.2)
In Alt.2, the number of HARQ-ACK bits for each SPS PDSCH may have the same value for SPS configurations of the same serving cell. In this case, M may be different or the same for SPS configurations of different serving cells. If there is at least one SPS PDSCH configured to transmit a maximum of two codewords in a certain cell, the number of HARQ-ACK bits for any SPS PDSCH in the cell may be two. Otherwise, the number of HARQ-ACK bits for any SPS PDSCH of the cell may be 1. A case where this is not the case may be, for example, a case where there is no SPS PDSCH configured to transmit a maximum of two codewords in the cell.

(Alt.3)
In Alt.3, the number of HARQ-ACK bits for each SPS PDSCH may be different or the same for different SPS configurations. For example, if an SPS configuration is configured to transmit a maximum of 2 codewords, the number of HARQ-ACK bits for the SPS PDSCH of the SPS configuration may be 2. Otherwise, the number of HARQ-ACK bits for the SPS PDSCH of the SPS configuration may be 1. Otherwise, for example, the SPS configuration may not be configured to transmit a maximum of 2 codewords.

(effect)
According to Proposal 5 described above, a HARQ-ACK CB including HARQ-ACK in a 2-TB SPS PDSCH can be constructed in an appropriate format, so that feedback of HARQ-ACK can be performed efficiently. For example, if different TB numbers of SPS PDSCH transmissions are performed in a cell, HARQ-ACK for 2 TB SPS PDSCH transmission may ) and is included in the HARQ-ACK CB. A base station that receives such a HARQ-ACK CB can perform appropriate retransmission control, etc., thereby improving communication efficiency.

Furthermore, although the HARQ-ACK CB is generated by the terminal, which construction procedure in Proposal 5 above is used to generate it may be determined by the terminal or may be instructed by the base station. However, it may be defined by the specifications.

<Proposal 6>
Proposal 6 proposes dynamic/adaptive updating of single-codeword or two-codeword application for SPS PDSCH/CG PUSCH.

The terminal 20 may dynamically update the application of a single-codeword or two-codeword to the SPS PDSCH/CG PUSCH according to instructions from the base station 10, or may update the application of a single-codeword or two-codeword to the SPS PDSCH/CG PUSCH adaptively according to a preset semi-static pattern. May be updated.

(1) Dynamic update Below, when dynamically updating the application of single-codeword or two-codeword, (1-1) update instruction method and (1-2) SPS/CG to be updated. The range of configuration will be explained.

(1-1) Method of instructing update In this application, the following options are proposed for a method of instructing dynamic update of application of single-codeword or two-codeword to SPS PDSCH/CG PUSCH.

(Opt. 1) Instruction by DCI The base station 10 may instruct the terminal 20 to update the application of single-codeword or two-codeword to SPS PDSCH/CG PUSCH by using DCI. In this case, the following variations are possible.

(Opt. 1-1)
A new DCI format is prepared, and the base station 10 may use this new DCI format to instruct the update of single-codeword or two-codeword application for SPS PDSCH/CG PUSCH. In this case, the new DCI format may have a new RNTI (Radio Network Temporary Identifier), or may have an existing RNTI without a new RNTI.

(Opt. 1-2)
Alternatively, the base station 10 may use the existing DCI format with a new RNTI to indicate the update of single-codeword or two-codeword application for SPS PDSCH/CG PUSCH.

(Opt. 1-3)
Alternatively, the base station 10 may use the existing DCI format with the existing RNTI to indicate the update of single-codeword or two-codeword application for the SPS PDSCH/CG PUSCH.

(Opt. 1-3A)
In this case, a new field may be provided, and information indicating update of application of single-codeword or two-codeword may be written in the new field. Further, there may be a plurality of new fields.

(Opt. 1-3B)
Alternatively, information indicating the update of the application of a single-codeword or two-codeword may be written into an unused field among the existing fields. Further, there may be a plurality of unused fields. In this case, the value of a particular field among the existing unused fields is used to indicate whether to reinterpret the DCI format for the purpose of dynamically updating single-codeword or two-codeword applications. Ru. The terminal 20 can determine whether to update the application of a single-codeword or two-codeword by reinterpreting the DCI format.

(Opt 2) Instruction by MAC CE The base station 10 may instruct the terminal 20 to update the application of single-codeword or two-codeword to SPS PDSCH/CG PUSCH by using MAC CE. In this case, the following variations are possible.

(Opt. 2-1)
A new MAC CE is prepared, and the base station 10 may use this new MAC CE to instruct update of single-codeword or two-codeword application to SPS PDSCH/CG PUSCH.

(Opt. 2-2)
Alternatively, the base station 10 may use the existing MAC CE with new octets to indicate update of single-codeword or two-codeword application for SPS PDSCH/CG PUSCH.

(Opt. 2-3)
Alternatively, the base station 10 may use the existing MAC CE with existing octets to indicate the update of single-codeword or two-codeword application for the SPS PDSCH/CG PUSCH. In this case, reserved bits are used to indicate whether the MAC CE is interpreted for single-codeword or two-codeword update purposes.

(1-2) Range of SPS/CG configuration to be updated This application proposes the range of SPS/CG configuration to which the application of single-codeword or two-codeword is updated.

(Alt 1)
The range in which the application of single-codeword or two-codeword is dynamically updated may be for each SPS/CG configuration by one DCI/MAC CE.

In this case, the base station 10 may instruct the terminal 20 to update the application of single-codeword or two-codeword in the target SPS/CG configuration using an index indicating the target SPS/CG configuration.

(Alt 2)
The range in which the application of single-codeword or two-codeword is dynamically updated may be all (activated) SPS/CG configurations by one DCI/MAC CE.

(Alt 3)
The range in which the application of single-codeword or two-codeword is dynamically updated may be for each group of SPS/CG configuration by one DCI/MAC CE.

Additionally, in this case, the base station 10 dynamically updates the application of single-codeword or two-codeword in the SPS/CG configuration to the terminal 20 using the index indicating the group of the target SPS/CG configuration. You may give instructions.

(2) Update based on semi-static pattern Below, we will explain the case where the application of single-codeword or two-codeword is updated based on semi-static pattern.

(Alt 1)
In Alt 1, the terminal 20 applies a single-codeword or two-codeword based on the index value of SPS/CG occasion.

For example, the terminal 20 applies a single-codeword when the index value N of the SPS/CG occasion satisfies N mod X1 = {Y1_1, Y1_2, ...}, and N mod X1 = {Y2_1, Y2_2, ...}, two-codeword may be applied. Here, N is an integer greater than or equal to 1, X1 is an integer greater than or equal to 2, and Y1_1, Y1_2, ... and Y2_1, Y2_2, ... are integers greater than or equal to 1 and less than or equal to (X1-1), respectively. , are different numbers from each other.

(Alt 2)
In Alt 2, the terminal 20 applies a single-codeword or two-codeword based on the index value of the SPS/CG occasion slot.

For example, the terminal 20 applies a single-codeword when the index value M of the SPS/CG occasion slot satisfies M mod X1 = {Y1_1, Y1_2, ...}, and M mod X1 = {Y2_1, Two-codeword may be applied if Y2_2, ...} is satisfied. Here, M is an integer greater than or equal to 1, X1 is an integer greater than or equal to 2, and Y1_1, Y1_2, ... and Y2_1, Y2_2, ... are each an integer greater than or equal to 0 and less than or equal to (X1-1). and are different numbers from each other.

(3) Impact of updates on HARQ-ACK CB In the construction of HARQ-ACK CB in Rel-15/16, when maximum two-codeword transmission is enabled (on the serving cell), the actually scheduled PDSCH is Regardless of whether it is a TB or two-TB transmission, two-TB HARQ-ACK positions are reserved. Therefore, there is no need to further consider the different behavior for dynamic updates of single-codeword and two-codeword SPS transmissions. In other words, it is considered that the HARQ-ACK CB described in Proposal 5 has the highest possibility of being reused.

(effect)
According to Proposal 6 described above, when applying either a single-codeword or two-codeword in SPS PDSCH/CG PUSCH, these can be dynamically/adaptive updated. For example, when a single-codeword is applied, the application may be dynamically switched to a two-codeword according to an instruction from the base station 10. Furthermore, single-codeword and two-codeword may be adaptively switched and applied according to a preset semi-static pattern.

(variation)
Furthermore, in the above description, it has been shown that one of a plurality of options is applied to one setting. For example, which of a plurality of options and/or which of a plurality of choices is applied may be determined in the following manner.
- Set by upper layer parameters.
- UE reports as UE capability(ies).
- Described in the specifications.
- Determined based on upper layer parameter settings and reported UE capability.
- Determined by a combination of two or more of the above decisions.
Note that the upper layer parameters may be RRC parameters, MAC CE (Media Access Control Control Element), or a combination thereof.

Note that it is possible for the terminal not to assume that CBG based SPS transmission and two-codeword SPS transmission are enabled at the same time. In other words, if one of CBG based SPS transmission and two-codeword SPS transmission is enabled, the terminal does not have to assume that the other will be enabled. Additionally, the terminal may assume that CBG based SPS transmission and two-codeword SPS transmission are enabled at the same time.

Note that the terminal may not assume that CBG based CG PUSCH transmission and two-codeword CG PUSCH transmission are enabled at the same time. In other words, if one of CBG based CG PUSCH transmission and two-codeword CG PUSCH transmission is enabled, the terminal does not need to assume that the other will be enabled. Furthermore, the terminal may assume that CBG based CG PUSCH transmission and two-codeword CG PUSCH transmission are enabled at the same time.

Additionally, CBG based SPS transmission and two-codeword SPS transmission may be supported simultaneously. The number of HARQ-ACK bits for SPS PDSCH when two codewords SPS transmission and CBG based transmission are enabled at the same time may be 2×M. Here, M may be determined in the same manner as the number M of HARQ-ACK bits shown in Proposal 2 above, for example. Alternatively, the number of HARQ-ACK bits for SPS PDSCH when two codeword SPS transmission and CBG-based transmission are enabled at the same time is the number of HARQ-ACK bits for CBG-based transmission shown in Proposal 2 and the number of HARQ-ACK bits for CBG-based transmission shown in Proposal 5. It may be determined based on two codewords and the number of HARQ-ACK bits for SPS transmission.

Additionally, CBG based CG PUSCH transmission and two-codeword CG PUSCH transmission may be supported simultaneously.

<UE capability>
The UE capability indicating the capability of the UE may include the following information indicating the capability of the UE. Note that the information indicating the capability of the UE may correspond to information defining the capability of the UE. Note that one UE capability indicating one of the following items may be notified, or one UE capability indicating multiple items may be notified.
- Information defining whether the UE supports CBG based SPS PDSCH transmission.
- Information that defines whether the UE supports CBG based CG PUSCH transmission.
- Information defining whether the UE supports two-codeword SPS PDSCH transmission.
- Information defining whether the UE supports two-codeword CG PUSCH transmission.
- Information defining whether the UE supports enabling CBG based SPS PDSCH transmission and two-codeword SPS PDSCH transmission simultaneously.
- Information defining whether the UE supports enabling CBG based CG PUSCH transmission and two-codeword CG PUSCH transmission at the same time.

The present disclosure has been described above. Note that the division of items in the above explanation is not essential to the present disclosure, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be used in another. may be applied to the matters described in the section (unless they conflict with each other).

<Hardware configuration, etc.>
It should be noted that the block diagram used to explain the above embodiment shows blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't do it. For example, a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 14 is a diagram illustrating an example of the hardware configuration of base station 100 and terminal 200 according to an embodiment of the present disclosure. The base station 100 and terminal 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

Note that in the following description, the word "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configurations of the base station 100 and the terminal 200 may be configured to include one or more of each device shown in the figure, or may be configured not to include some of the devices.

Each function in the base station 100 and the terminal 200 is performed by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of data reading and writing in the memory 1002 and the storage 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, the above-mentioned

control units

103, 203, etc. may be realized by the processor 1001.

Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 103 of the base station 100, the control unit 203 of the terminal 200, etc. may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may also be realized in the same way. Good too. Although the various processes described above have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.

The memory 1002 is a computer-readable recording medium, and includes at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be done. Memory 1002 may be called a register, cache, main memory, or the like. The memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (such as a compact disk, a digital versatile disk, or a Blu-ray disk). (registered trademark disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The storage medium mentioned above may be, for example, a database including at least one of memory 1002 and storage 1003, a server, or other suitable medium.

The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of. For example, the above-mentioned transmitting section 101, receiving section 102, receiving section 201, transmitting section 202, etc. may be realized by the communication device 1004. The communication device 1004 may have a transmitter and a receiver that are physically or logically separated.

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

Further, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each device.

The base station 100 and the terminal 200 also include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). A part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

(Supplementary information on the embodiment)
Although the embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, modifications, alternatives, replacements, etc. Probably. Although the invention has been explained using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above explanation is not essential to the present disclosure, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be used in another item. may be applied to the matters described in (unless inconsistent). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. The operations of a plurality of functional sections may be physically performed by one component, or the operations of one functional section may be physically performed by a plurality of components. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as there is no contradiction. Although the base station 100 and the terminal 200 have been described using functional block diagrams for convenience of processing description, such devices may be implemented in hardware, software, or a combination thereof. Software operated by a processor included in base station 100 according to an embodiment of the present disclosure and software operated by a processor included in terminal 200 according to an embodiment of this disclosure are respectively random access memory (RAM), flash memory, and read-only memory. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

<Information notification, signaling>
Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information may include physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented using broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or a combination thereof. Further, RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

<Applicable system>
Each aspect/embodiment described in this disclosure applies to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), and 5G (5th generation mobile communication system). system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is an integer, decimal, for example)), FRA (Future Radio Access), NR (new Radio), New radio access ( NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802 .16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems and systems that are extended, modified, created, and defined based on these. The present invention may be applied to at least one of the next generation systems. Furthermore, a combination of a plurality of systems may be applied (for example, a combination of at least one of LTE and LTE-A and 5G).

<Processing procedures, etc.>
The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.

<Base station operation>
The specific operations performed by the base station in this disclosure may be performed by its upper node in some cases. In a network consisting of one or more network nodes including a base station, various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (e.g., MME or It is clear that this could be done by at least one of the following: (conceivable, but not limited to) S-GW, etc.). In the above example, there is one network node other than the base station, but it may be a combination of multiple other network nodes (for example, MME and S-GW).

<Input/output direction>
Information etc. (see the item <Information, Signal>) can be output from an upper layer (or lower layer) to a lower layer (or upper layer). It may be input/output via multiple network nodes.

<Handling of input/output information, etc.>
The input/output information may be stored in a specific location (eg, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.

<Judgment method>
Judgment may be made using a value expressed by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (for example, a predetermined value). (comparison with a value).

<Variations of aspects, etc.>
Each aspect/embodiment described in this disclosure may be used alone, may be used in combination, or may be switched and used in accordance with execution. Furthermore, notification of prescribed information (for example, notification of "X") is not limited to being done explicitly, but may also be done implicitly (for example, by not notifying the prescribed information). Good too.

Although the present disclosure has been described in detail above, it is clear for those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as determined by the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and is not intended to have any limiting meaning on the present disclosure.

<Software>
Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.

<Information, signals>
The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of

Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal. Also, the signal may be a message. Further, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, or the like.

<System, network>
As used in this disclosure, the terms "system" and "network" are used interchangeably.

<Parameter, channel name>
In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by an index.

The names used for the parameters mentioned above are not restrictive in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (e.g. PUCCH, PDCCH, etc.) and information elements may be identified by any suitable designation, the various names assigned to these various channels and information elements are in no way exclusive designations. isn't it.

<Base station>
In this disclosure, "Base Station (BS),""wireless base station,""fixedstation,""NodeB,""eNodeB(eNB),""gNodeB(gNB),"""accesspoint","transmissionpoint","receptionpoint","transmission/receptionpoint","cell","sector","cellgroup"," The terms "carrier", "component carrier", etc. may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services may also be provided by a remote radio head).The term "cell" or "sector" refers to a portion or the entire coverage area of a base station and/or base station subsystem that provides communication services in this coverage. refers to

In the present disclosure, the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.

<Mobile station>
In this disclosure, terms such as "Mobile Station (MS),""userterminal,""User Equipment (UE)," and "terminal" may be used interchangeably. .

A mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

<Base station/mobile station>
At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, or the like. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving object is stopped. Examples of such moving objects include vehicles, transportation vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships and other watercraft. , including, but not limited to, airplanes, rockets, artificial satellites, drones (registered trademarks), multicopters, quadcopters, balloons, and objects mounted thereon. Furthermore, the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good. Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Additionally, the base station in the present disclosure may be replaced by a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 200 may have the functions that the base station 100 described above has. Further, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be replaced with side channels.

Similarly, the user terminal in the present disclosure may be replaced with a base station. In this case, the base station 100 may have the functions that the terminal 200 described above has.

FIG. 15 shows an example of the configuration of the vehicle 2001. As shown in FIG. 15, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, a front wheel 2007, a rear wheel 2008, an axle 2009, an electronic control unit 2010, and various sensors 2021 to 2029. , an information service section 2012 and a communication module 2013. Each aspect/embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, may be applied to communication module 2013.

The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

Signals from various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, and a front wheel rotation speed signal obtained by an air pressure sensor 2023. and rear wheel air pressure signals, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression amount signals acquired by accelerator pedal sensor 2029, and brake pedal sensor 2026. These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028, and the like.

The information service department 2012 controls various devices such as car navigation systems, audio systems, speakers, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs. The information service unit 2012 provides various multimedia information and multimedia services to the occupants of the vehicle 2001 using information acquired from an external device via the communication module 2013 and the like.

The information service department 2012 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, (display, speaker, LED lamp, touch panel, etc.).

The driving support system unit 2030 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden. The system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.

Communication module 2013 can communicate with microprocessor 2031 and components of vehicle 2001 via a communication port. For example, the communication module 2013 communicates with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, electronic Data is transmitted and received between the microprocessor 2031, memory (ROM, RAM) 2032, and sensors 2021 to 2029 in the control unit 2010.

The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

The communication module 2013 receives signals from the various sensors 2021 to 2029 described above that are input to the electronic control unit 2010, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 2012. At least one of the information based on the information may be transmitted to an external device via wireless communication. The electronic control unit 2010, various sensors 2021 to 2029, information service unit 2012, etc. may be called an input unit that receives input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 2012 provided in the vehicle 2001. The information service unit 2012 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 2013). may be called. Communication module 2013 also stores various information received from external devices into memory 2032 that can be used by microprocessor 2031 . Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive section 2002, steering section 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheel 2007, rear wheel 2008, and axle 2009 provided in the vehicle 2001. , sensors 2021 to 2029, etc. may be controlled.

(Summary of embodiments)
As described above, according to one aspect of the present disclosure, transmission of CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or reception of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) is a control unit that controls the setting of whether to perform based on Block) or CBG (Code Block Group); and a transmitting/receiving unit that transmits the CG PUSCH and/or receives the SPS PDSCH based on the settings of the control unit. A terminal is provided that includes the following.

With the above configuration, CBG based transmission can be supported even in SPS PDSCH/CG PUSCH, which has quasi-static scheduling, so the retransmission frequency can be reduced, reducing delay, improving transmission efficiency, and ensuring reliability. be able to.

In one embodiment, the control unit may control the setting of whether to transmit the CG PUSCH and/or receive the SPS PDSCH based on the TB standard or the CBG standard based on upper layer parameters. good. According to this embodiment, in cooperation with the base station, it is possible to control the setting of whether to use the TB standard or the CBG standard.

In one embodiment, the control unit controls the transmission of the CG PUSCH and/or the reception of the SPS PDSCH based on the TB standard based on upper layer parameters and/or the format or DCI field of activation DCI (Downlink Control Information). You may control the settings as to whether this is done or based on the CBG standard. According to this embodiment, in cooperation with the base station, it is possible to control the setting of whether to use the TB standard or the CBG standard.

In one embodiment, the control unit may dynamically/adaptively update the set TB standard or the CBG standard. According to the present embodiment, when applying either CBG based transmission or TB based transmission in SPS PDSCH/CG PUSCH, these can be dynamically/adaptive updated.

Further, according to one aspect of the present disclosure, transmission of CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or reception of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) is performed on a TB (Transport Block) basis. A base station is provided that includes a control unit that configures whether the data is to be transmitted or based on a CBG (Code Block Group) standard, and a transmitter that notifies information indicating the setting.

Further, according to one aspect of the present disclosure, a terminal that transmits and receives Extended Reality (XR) data transmits a CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel). ) on the basis of TB (Transport Block) or CBG (Code Block Group), and transmits the CG PUSCH and/or receives the SPS PDSCH based on the settings. A communication method is provided.

Further, according to one aspect of the present disclosure, transmission of CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or reception of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) is performed using a single-codeword or two-codeword. A terminal is provided that includes a control unit that controls settings for codewords, and a transmitting and receiving unit that transmits the CG PUSCH and/or receives the SPS PDSCH based on the settings of the control unit.

In one embodiment, the control unit controls settings of whether to transmit the CG PUSCH and/or receive the SPS PDSCH using the single-codeword or the two-codeword based on upper layer parameters. It's okay. According to this embodiment, in cooperation with the base station, it is possible to control the setting of whether to use a single-codeword or based on the CBG standard.

In one embodiment, the control unit controls the transmission of the CG PUSCH and/or the reception of the SPS PDSCH based on the upper layer parameters and/or the format or DCI field of activation DCI (Downlink Control Information). You may control the setting of whether to perform this with or with the above-mentioned two-codeword. According to this embodiment, in cooperation with the base station, it is possible to control the setting of whether to use a single-codeword or based on the CBG standard.

In one embodiment, the control unit may dynamically/adaptively update the set single-codeword or two-codeword. According to this embodiment, when applying either a single-codeword or two-codeword in SPS PDSCH/CG PUSCH, these can be dynamically/adaptive updated.

Further, according to one aspect of the present disclosure, transmission of CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or reception of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) is performed using a single-codeword or two-codeword. A base station is provided that includes a control unit that sets whether to perform the codeword, and a transmitter that notifies information indicating the setting.

Further, according to one aspect of the present disclosure, a terminal that transmits and receives Extended Reality (XR) data transmits a CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel). ) is set as whether to be received using a single-codeword or two-codeword, and based on the setting, the CG PUSCH is transmitted and/or the SPS PDSCH is received.

Further, according to one aspect of the present disclosure, a control unit that generates an acknowledgment for a transmission signal transmitted based on quasi-static scheduling in a format according to a transmission method of the transmission signal; A terminal is provided, including a transmitter that transmits data.

With the above configuration, depending on whether the transmission method of a transmission signal transmitted based on quasi-static scheduling (e.g. SPS) is a method applying CBG or a method applying TB, an acknowledgment response (e.g. HARQ -ACK CB) can be constructed in an appropriate format, HARQ-ACK feedback and retransmission control based on HARQ-ACK can be appropriately performed, and communication efficiency can be improved. Note that in the embodiments described above, examples of the transmission method of the transmission signal are a method of applying CBG and a method of applying TB, but the present disclosure is not limited to these.

In one embodiment, the control unit may generate the acknowledgment in a differentiated format depending on the cell using the transmission method. According to this embodiment, the serving cells are classified into cells that perform TB based SPS PDSCH transmission and cells that perform CBG based SPS PDSCH transmission, and then, in HARQ-ACK CB, the HARQ corresponding to each of the classified cells is -HARQ-ACK CB can be constructed in a format that differentiates ACK. Thereby, feedback of HARQ-ACK and retransmission control based on HARQ-ACK can be appropriately performed, so communication efficiency can be improved.

In one embodiment, the acknowledgment includes a first cell that uses a first transmission method and does not use a second transmission method among the transmission methods, and a first cell that does not use the first transmission method; The second cell using the second transmission method may have a different format. According to this embodiment, the serving cell is a cell that performs only TB based SPS PDSCH transmission (for example, a cell that performs TB based SPS PDSCH transmission and does not perform CBG based SPS PDSCH transmission), and a cell that performs only CBG based SPS PDSCH transmission. cells (for example, cells that do not perform TB based SPS PDSCH transmission but perform CBG based SPS PDSCH transmission), and in the HARQ-ACK CB, distinguish HARQ-ACK corresponding to each classified cell. You can build a HARQ-ACK CB in the format. Thereby, feedback of HARQ-ACK and retransmission control based on HARQ-ACK can be appropriately performed, so communication efficiency can be improved.

In one embodiment, the acknowledgment includes a third cell using a first transmission method and not using a second transmission method, and at least one of the first transmission method and the second transmission method. It may have a format differentiated into a fourth cell using . According to this embodiment, the serving cell is divided into a cell that performs only TB based SPS PDSCH transmission (for example, a cell that performs TB based SPS PDSCH transmission but not CBG based SPS PDSCH transmission) and a cell that does not perform this (for example, a cell that performs TB based SPS PDSCH transmission). based SPS PDSCH transmission and CBG based SPS PDSCH transmission (cells that perform at least one of CBG based SPS PDSCH transmission), and then in HARQ-ACK CB, HARQ -ACK CB can be constructed. Thereby, feedback of HARQ-ACK and retransmission control based on HARQ-ACK can be appropriately performed, so communication efficiency can be improved.

Further, according to one aspect of the present disclosure, the receiving unit receives an acknowledgment for a transmission signal transmitted based on quasi-static scheduling, the acknowledgment having a format according to a transmission method of the transmission signal. and a control unit that controls retransmission based on the acknowledgment.

With the above configuration, the acknowledgment can be constructed in an appropriate format depending on whether the transmission method of the transmission signal transmitted based on quasi-static scheduling is applying CBG or applying TB. Since HARQ-ACK feedback and retransmission control based on HARQ-ACK can be appropriately performed, communication efficiency can be improved.

Further, according to one aspect of the present disclosure, an acknowledgment for a transmission signal transmitted based on quasi-static scheduling is generated in a format according to a transmission method of the transmission signal, and the acknowledgment is transmitted. A wireless communication method is provided.

Further, according to one aspect of the present disclosure, the control unit generates an acknowledgment response to a transmission signal transmitted based on quasi-static scheduling in a format according to the number of transport blocks of the transmission signal; A terminal is provided, including a transmitter that transmits an acknowledgment.

The above configuration allows acknowledgments (e.g. HARQ-ACK CB) to be sent in an appropriate format depending on the number of transport blocks (TB) of transmitted signals based on quasi-static scheduling (e.g. SPS). As a result, it is possible to appropriately perform HARQ-ACK feedback and retransmission control based on HARQ-ACK, thereby improving communication efficiency.

In one embodiment, the control unit may generate the acknowledgment having a differentiated format depending on a cell using the number of transport blocks. According to this embodiment, the serving cells are classified according to the number of TBs used, and then the HARQ-ACK CB is transmitted in a format that distinguishes HARQ-ACKs corresponding to each of the classified cells. Can be built. Thereby, feedback of HARQ-ACK and retransmission control based on HARQ-ACK can be appropriately performed, so communication efficiency can be improved. Note that in the embodiments described above, the number of TBs was 1 or 2, but the present disclosure is not limited thereto. For example, the number of TBs may be 3 or more.

In one embodiment, the acknowledgment includes a first cell using a first number of transport blocks and a second cell using a second number of transport blocks different from the first number of transport blocks. It may have a format differentiated into two cells. According to this embodiment, the serving cell is divided into a cell that uses 1 TB (for example, a cell that performs 1 TB based SPS PDSCH transmission) and a cell that uses 2 TB (for example, a cell that performs 2 TB based SPS PDSCH transmission). The HARQ-ACK CB can be constructed in a format that differentiates the HARQ-ACK corresponding to each of the classified cells. Thereby, feedback of HARQ-ACK and retransmission control based on HARQ-ACK can be appropriately performed, so communication efficiency can be improved.

In one embodiment, in the transmission method, a size of an acknowledgment for the transmitted signal of a first number of transport blocks is less than or equal to a size of an acknowledgment for the transmitted signal of a second number of transport blocks. It's okay. According to this embodiment, the serving cell is adjusted such that the size of the HARQ-ACK for a 1 TB based SPS PDSCH using 1 TB is smaller than the HARQ-ACK size for a 2 TB based SPS PDSCH using 2 TB. Therefore, HARQ-ACK CB can be constructed according to the size of the transmitted data. Thereby, it is possible to appropriately perform HARQ-ACK feedback according to the size of the transmitted data, thereby improving communication efficiency.

Further, according to one aspect of the present disclosure, an acknowledgment for a transmission signal transmitted based on quasi-static scheduling, the acknowledgment having a format according to the number of transport blocks of the transmission signal is received. and a control unit that controls retransmission based on the acknowledgment.

With the above configuration, the acknowledgment can be constructed in an appropriate format according to the number of transport blocks of the transmitted signal transmitted based on quasi-static scheduling, so that feedback of HARQ-ACK and retransmission based on HARQ-ACK can be achieved. Since control can be performed appropriately, communication efficiency can be improved.

Further, according to one aspect of the present disclosure, an acknowledgment for a transmission signal transmitted based on quasi-static scheduling is generated in a format according to the number of transport blocks of the transmission signal, and the acknowledgment is A wireless communication method is provided for transmitting.

<Meaning and interpretation of terms>
As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of operations. "Judgment" and "decision" include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a "judgment" or "decision." In addition, "judgment" and "decision" refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access. (accessing) (for example, accessing data in memory) may include considering something as a "judgment" or "decision." In addition, "judgment" and "decision" refer to resolving, selecting, choosing, establishing, comparing, etc. as "judgment" and "decision". may be included. In other words, "judgment" and "decision" may include regarding some action as having been "judged" or "determined." Further, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

The terms "connected", "coupled", or any variations thereof, mean any connection or coupling, direct or indirect, between two or more elements and each other. It may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled." The bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access." As used in this disclosure, two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.

<Reference signal>
The reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applied standard.

<Meaning of “based on”>
As used in this disclosure, the phrase "based on" does not mean "based solely on" unless explicitly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

<“first”, “second”>
As used in this disclosure, any reference to elements using the designations "first,""second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.

<Means>
"Means" in the configurations of each of the above devices may be replaced with "unit", "circuit", "device", etc.

<Open format>
Where "include", "including" and variations thereof are used in this disclosure, these terms, like the term "comprising," are inclusive. It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.

<Time units such as TTI, frequency units such as RB, radio frame configuration>
A radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe. A subframe may also be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

The numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception. It may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

A slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.

For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, and one slot or minislot may be called a TTI. It's okay. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers included in an RB may be determined based on numerology.

Additionally, the time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

Note that one or more RBs are defined as physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. May be called.

Additionally, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (also referred to as partial bandwidth) refers to a subset of consecutive common resource blocks (RBs) for a certain numerology in a certain carrier. good. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a UL BWP (UL BWP) and a DL BWP (DL BWP). One or more BWPs may be configured within one carrier for a UE.

At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

The structures of radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, The number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

<Maximum transmission power>
"Maximum transmit power" as described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power ( It may also mean the rated UE maximum transmit power.

<Article>
In this disclosure, when articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are plural.

<“Different”>
In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."

The present disclosure is useful for wireless communication systems.

10 base station 20

terminal

101, 202

transmitter

102, 201

receiver

103, 203 controller 1001 processor 1002 memory 1003 storage 1004 communication device 1005 input device 1006 output device

Claims

A control unit that controls the setting of whether to transmit CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or receive SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) using single-codeword or two-codeword. and,
a transmitting/receiving unit that transmits the CG PUSCH and/or receives the SPS PDSCH based on the settings of the control unit;
A terminal equipped with.
The control unit controls settings of whether to transmit the CG PUSCH and/or receive the SPS PDSCH using the single-codeword or the two-codeword, based on upper layer parameters.
The terminal according to claim 1.
The control unit transmits the CG PUSCH and/or receives the SPS PDSCH using the single-codeword or the two -Control what settings are done with codeword,
The terminal according to claim 1.
The control unit dynamically/adaptively updates the set single-codeword or the two-codeword.
The terminal according to claim 1.
A control unit that sets whether to transmit a CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or receive an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) using a single-codeword or two-codeword;
a transmitting unit that notifies information indicating the settings;
A base station equipped with.
The terminal that sends and receives Extended Reality (XR) data is
Set whether to transmit CG PUSCH (Configured Grant Physical Uplink Schered Channel) and/or receive SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) using single-codeword or two-codeword,
transmitting the CG PUSCH and/or receiving the SPS PDSCH based on the settings;
Wireless communication method.