Terminal, wireless communication system, and wireless communication method

Abstract

To provide an apparatus, a system, and a method that can continue to receive a data channel normally even when collision between a PDSCH / PUSCH and a UL / DL symbol is permitted.SOLUTION: In a wireless communication system, a terminal 200 includes a receiving unit that receives single downlink control information that schedules a plurality of downlink data channels, and a control unit that determines a codebook in which feedback of automatic repeat requests for the downlink data channels is to be included based on receiving the plurality of downlink data channels scheduled by the single downlink control information.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a wireless communication system, and a wireless communication method that support multi-PDSCH / PUSCH scheduling. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, 3GPP Release-17 supports frequency bands exceeding 52.6 GHz up to 71 GHz, and one (single) piece of Downlink Control Information (DCI) enables scheduling of multiple data channels, specifically multiple PDSCHs (Physical Downlink Shared Channels) / PUSCHs (Physical Uplink Shared Channels) (multi-PDSCH / PUSCH scheduling) (Non-Patent Document 1).

[0004] In multi-PDSCH scheduling, collisions (overlapping radio resource allocations) with semi-static uplink (UL) symbols are permitted (in the case of Time Division Duplex (TDD)). In addition, in multi-PUSCH scheduling, collisions with semi-static downlink (DL) symbols are permitted. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "Final Report of 3GPP TSG RAN WG1 #104bis-e v1.0.0", R1-2104151, 3GPP TSG RAN WG1 Meeting #105-e, 3GPP, April 2021 Summary of the Invention

[0006] However, if collision between the PDSCH / PUSCH and UL / DL symbols as described above is permitted, the terminal (User Equipment, UE) needs to continue receiving the data channel normally even when such collision occurs.

[0007] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal, a wireless communication system, and a wireless communication method that can continue to receive the data channel normally even when collision between the PDSCH / PUSCH and the UL / DL symbols is allowed.

[0008] One aspect of the present disclosure is a terminal (UE200) including a receiver (data transmitter / receiver 260) that receives multiple downlink data channels scheduled by single downlink control information, and a controller (controller 270) that, when any of the downlink data channels collides with an uplink symbol, assumes that the downlink data channel canceled due to the collision is excluded from the target of specific scheduling.

[0009] One aspect of the present disclosure is a terminal including: a receiving unit that receives multiple downlink data channels scheduled by single downlink control information; and a control unit that determines whether or not there is information related to a code block group based on the scheduled downlink data channels or the valid downlink data channels.

[0010] One aspect of the present disclosure is a terminal including: a receiving unit that receives multiple downlink data channels scheduled by single downlink control information; and a control unit that determines a codebook to include feedback of automatic repeat requests for the downlink data channels based on the number of valid downlink data channels.

[0011] One aspect of the present disclosure is a terminal including: a receiving unit that receives multiple downlink data channels scheduled by single downlink control information; and a control unit that, when any of the downlink data channels collides with an uplink symbol, assumes reception of the downlink data channel by semi-static scheduling that has been canceled due to the collision.

[0012] One aspect of the present disclosure is a terminal (UE200) including a transmitter (data transmitter / receiver 260) that transmits multiple uplink data channels scheduled by single downlink control information, and a controller (controller 270) that, when any of the uplink data channels collides with a downlink symbol, assumes that the uplink data channel canceled due to the collision is excluded from the target of specific scheduling.

[0013] One aspect of the present disclosure is a terminal including a transmitter that transmits multiple uplink data channels scheduled by single downlink control information, and a controller that determines reporting of channel state information based on the scheduled uplink data channels or the valid uplink data channels.

[0014] One aspect of the present disclosure is a terminal including: a transmitter that transmits multiple uplink data channels scheduled by single downlink control information; and a controller that determines whether or not information related to a code block group is present based on the scheduled uplink data channels or the valid uplink data channels.

[0015] One aspect of the present disclosure is a terminal including: a transmitter that transmits multiple uplink data channels scheduled by single downlink control information; and a controller that, when any of the uplink data channels collides with a downlink symbol, stops transmission of the uplink data channel based on a configured grant that has been canceled due to the collision. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing frequency bands used in the wireless communication system 10. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 4] Figure 4 is a functional block diagram of gNB100 and UE200. [Figure 5] FIG. 5 is a diagram illustrating a configuration example of multi-PDSCH / PUSCH scheduling. [Figure 6] FIG. 6 is a diagram showing an example of a sequence relating to scheduling of a data channel. [Figure 7] FIG. 7 is a diagram illustrating an example of the TDRA table. [Figure 8] FIG. 8 is a diagram showing an example of the hardware configuration of gNB100 and UE200. [Figure 9] FIG. 9 is a diagram showing an example of the configuration of a vehicle 2001. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0018] (1) Overall configuration of wireless communication system 1 is a schematic diagram of the overall configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN 20) and a terminal 200 (hereinafter referred to as UE 200, User Equipment, UE). Note that the wireless communication system 10 may also be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0019] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.

[0020] The NG-RAN 20 actually includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0021] The gNB 100 is a 5G-compliant radio base station that performs 5G-compliant radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional antenna beam (hereinafter referred to as beam BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and two NG-RAN nodes.

[0022] The gNB 100 can transmit multiple beams BM with different transmission directions (which may also be simply referred to as directions, or radiation directions, or coverages) in a space- and time-division manner. Note that the gNB 100 may transmit multiple beams BM simultaneously.

[0023] The wireless communication system 10 may also support a plurality of frequency ranges (FR).

[0024] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz~52.6 GHz FR1 may use a sub-carrier spacing (SCS) of 15, 30, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use a sub-carrier spacing (SCS) of 60 or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

[0025] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0026] Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 71 GHz. For convenience, such high frequency bands may be referred to as "FR2x."

[0027] To solve this problem, when using a band above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied.

[0028] Furthermore, in high frequency bands such as FR2x, as mentioned above, increased phase noise between carriers becomes an issue, which may necessitate the application of a larger (wider) SCS or a single carrier waveform.

[0029] The larger the SCS, the shorter the symbol / CP (Cyclic Prefix) period and slot period (assuming a 14 symbol / slot configuration is maintained). Figure 3 shows an example of the configuration of a radio frame, subframe, and slot used in the wireless communication system 10. Table 1 also shows the relationship between the SCS and the symbol period.

[0030] [Table 1]

[0031] As shown in Table 1, if the 14 symbols / slot configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period). The symbol period may also be called the symbol length, time direction, or time domain. The frequency direction may also be called the frequency domain, resource block, subcarrier, BWP (Bandwidth part), etc.

[0032] The number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Also, the number of slots per subframe may differ depending on the SCS.

[0033] Furthermore, the wireless communication system 10 may use an SSB (SS / PBCH Block) that is configured from a synchronization signal (SS) and a downlink physical broadcast channel (PBCH).

[0034] SSBs are mainly transmitted periodically from the network to allow UE 200 to detect cell IDs and reception timings when starting communication. In NR, SSBs are also used to measure the reception quality of each cell. The SSB transmission periodicity may be specified as 5, 10, 20, 40, 80, 160 milliseconds, etc. Note that the initial access UE 200 may assume a transmission period of 20 milliseconds.

[0035] The network (NG-RAN 20) can notify the UE 200 of the index indication (ssb-PositionsInBurst) of the actually transmitted SSBs by system information (SIB1) or signaling of the radio resource control layer (RRC).

[0036] The SS is composed of a primary synchronization signal (PSS: Primary SS) and a secondary synchronization signal (SSS: Secondary SS).

[0037] The PSS is a known signal that the UE 200 first attempts to detect in the cell search procedure, and the SSS is a known signal that is transmitted to detect a physical cell ID in the cell search procedure.

[0038] The PBCH includes information necessary for UE200 to establish frame synchronization with the NR cell formed by gNB100 after detecting the SS / PBCH block, such as the radio frame number (SFN: System Frame Number) and an index for identifying the symbol positions of multiple SS / PBCH blocks within a half frame (5 milliseconds).

[0039] The PBCH can also include system parameters required for receiving system information (SIB). Furthermore, the SSB also includes a broadcast channel demodulation reference signal (DMRS for PBCH). The DMRS for PBCH is a known signal transmitted to measure the wireless channel conditions for PBCH demodulation.

[0040] If the UE 200 determines, based on the received Master Information Block (MIB), that a CORESET for the Type 0-PDCCH CSS exists, the UE 200 determines several consecutive resource blocks (RBs) and symbols for the CORESET (which may also be referred to as CORESET 0 or Remaining Minimum System Information (RMSI) CORESET). Based on the determined RBs and symbols, the UE 200 sets a PDCCH (Physical Downlink Control Channel), specifically, a monitoring occasion (MO) of the Type 0 PDCCH for decoding the system information block (SIB).

[0041] CORESET 0 is a special CORESET that is different from a normal CORESET. Such a specific CORESET may be interpreted as a CORESET that transmits a PDCCH for SIB1 scheduling. CORESET 0 cannot be specified by RRC because it is used before RRC signaling is transmitted.

[0042] RMSI may be interpreted as meaning System Information Block 1 (SIB1). RMSI may consist of system information that a device (UE 200) needs to know before accessing the system. SIB1 may be broadcast periodically throughout the cell at all times. SIB1 may provide information that UE 200 needs to perform an initial random access (RA).

[0043] SIB1 is provided by a regular scheduled Physical Downlink Shared Channel (PDSCH) transmission with a periodicity of 160 ms. The PBCH / MIB may provide information about the numerology used for SIB1 transmission and the search space and corresponding CORESET used for scheduling SIB1. Within this CORESET, UE 200 may monitor the scheduling of SIB1, indicated by a special System Information RNTI (SI-RNTI).

[0044] The wireless communication system 10 may support Time Domain Resource Allocation (TDRA). TDRA may be interpreted as resource allocation in the time domain of a Physical Uplink Shared Channel (PUSCH) defined in 3GPP TS38.214. TDRA of the PUSCH may be interpreted as being defined by an information element (IE) of a radio resource control layer (RRC), specifically, PDSCH-Config or PDSCH-ConfigCommon.

[0045] The TDRA may be interpreted as a resource allocation in the time domain for the PUSCH specified by the Downlink Control Information (DCI).

[0046] Furthermore, in the wireless communication system 10, one (single) DCI may support scheduling of multiple data channels, specifically, multiple PDSCHs (Physical Downlink Shared Channels) / PUSCHs (Physical Uplink Shared Channels) (multi-PDSCH / PUSCH scheduling).

[0047] (2) Functional block configuration of wireless communication system Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described. FIG. 4 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0048] As shown in FIG. 4, UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0049] It should be noted that Fig. 4 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the UE 200, and for the hardware configuration, please refer to Fig. 8.

[0050] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.

[0051] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0052] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).

[0053] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0054] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0055] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0056] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0057] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0058] The channels include a control channel and a data channel. The control channels may include a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0059] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel), a PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via a data channel.

[0060] Furthermore, the control signal and reference signal processor 240 may transmit capability information of the UE 200 regarding scheduling of the data channel to the network.

[0061] Specifically, the control signal and reference signal processing unit 240 can transmit UE capability information related to scheduling of the PDSCH and PUSCH to the gNB 100. Details of the UE capability information will be described later.

[0062] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0063] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0064] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0065] The data transceiver 260 can receive multiple downlink data channels (PDSCHs) scheduled by one (single) downlink control information (DCI). The data transceiver 260 can also transmit multiple uplink data channels (uplink data channels) scheduled by a single downlink control information (DCI). In this embodiment, the data transceiver 260 may be configured as a receiver for receiving downlink data channels and a transmitter for transmitting uplink data channels.

[0066] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 can execute control related to multi-PDSCH / PUSCH scheduling.

[0067] First, control related to multi-PDSCH scheduling will be described. When one of the multiple PDSCHs in multi-PDSCH scheduling collides with a UL symbol, control unit 270 may assume that the PDSCH canceled due to the collision is excluded from the targets of specific scheduling.

[0068] Here, the UL symbol may be interpreted as a symbol that is semi-statically allocated in a slot. In multi-PDSCH scheduling, collisions with such semi-static UL symbols, specifically, overlapping of resources in the time direction, may be permitted. In other words, in multi-PDSCH scheduling, collisions between PDSCH and semi-static UL symbols may occur in Time Division Duplex (TDD).

[0069] Furthermore, the specific scheduling may refer to out-of-order scheduling (OoO scheduling). In OoO scheduling, the UE 200 may operate as follows.

[0070] · For any two HARQ process IDs in a given scheduled cell, if UE 200 is scheduled to start receiving a PDCCH starting at symbol j and ending at symbol i with the first PDSCH starting at symbol j, then UE 200 does not expect to be scheduled to receive a PDSCH starting before the end of the first PDSCH with a PDCCH ending after symbol i.

[0071] For any two HARQ process IDs in a given scheduled cell, if UE 200 is scheduled to start its first PUSCH transmission with a PDCCH starting at symbol j and ending at symbol i, then UE 200 does not expect to be scheduled to transmit a PUSCH that starts before the end of the first PUSCH with a PDCCH that ends after symbol i.

[0072] In multi-PDSCH scheduling, the control unit 270 may determine whether or not there is information about a code block group (CBG) based on a scheduled or valid PDSCH.

[0073] Specifically, in the case of a DL grant DCI configured based on a TDRA table including multiple SLIVs (Start and Length Indicator Values), the control unit 270 may determine the presence or absence (existence) of the CBGTI (transmission information) and / or CBGFI (flushing out information) fields of the DCI based on the scheduled PDSCH or the valid PDSCH.

[0074] Note that a valid PDSCH may be interpreted as a PDSCH that does not collide with a semi-static UL symbol.

[0075] Furthermore, the control unit 270 may determine a codebook to include feedback of a hybrid automatic repeat request (HARQ) of the PDSCH based on the number of valid PDSCHs.

[0076] Specifically, in the case of a DL grant DCI set based on a TDRA table including multiple SLIVs (Start and Length Indicator Values), in the type 2 HARQ-ACK (Acknowledgement) feedback, the control unit 270 may include the HARQ-ACK in one of the sub-codebooks (first sub-codebook or second sub-codebook) based on the number of valid PDSCHs.

[0077] Alternatively, the control unit 270 may include the HARQ-ACK in the second sub-codebook regardless of the number of enabled or disabled PDSCHs.

[0078] The first sub-codebook may refer to a sub-codebook for DCI that schedules only one PDSCH (i.e., the TDRA table includes only one SLIV). Note that types 1 and 2 are based on different codebook determination algorithms, and in type 2, the HARQ-ACK codebook may be dynamically set.

[0079] When any PDSCH in multi-PDSCH scheduling collides with an UL symbol, the control unit 270 may assume reception of the PDSCH in semi-static scheduling that has been canceled due to the collision.

[0080] Specifically, the control unit 270 may assume reception of a semi-persistent scheduling (SPS) PDSCH that overlaps with (i.e., uses the same radio resources as) the PDSCH that has been canceled due to collision.

[0081] Next, control related to multi-PUSCH scheduling will be described. When one of multiple PUSCHs in multi-PUSCH scheduling collides with a DL symbol, control unit 270 may assume that the PUSCH canceled due to the collision is excluded from the targets of specific scheduling (OoO scheduling).

[0082] Here, DL symbols may be interpreted as symbols that are semi-statically allocated in a slot. In multi-PUSCH scheduling, collisions with such semi-static DL symbols, SSB symbols, and / or CORESET 0 symbols, specifically, overlapping of resources in the time direction, may be permitted. That is, in multi-PUSCH scheduling, collisions may occur between multi-PUSCH scheduling and semi-static UL symbols in Time Division Duplex (TDD).

[0083] In multi-PUSCH scheduling, the control unit 270 may determine whether to report Channel State Information (CSI) based on a scheduled PUSCH or a valid PUSCH. Specifically, in the case of A-CSI (Aperiodic-CSI) reporting triggered by a UL grant DCI set based on a TDRA table including a number of Start and Length Indicator Values ​​(SLIVs), the control unit 270 may report a CSI report based on a scheduled PUSCH or a valid PUSCH.

[0084] Note that a valid PUSCH may be interpreted as a PUSCH that does not collide with semi-static UL symbols, SSBs, and / or symbols set to CORESET 0.

[0085] In multi-PUSCH scheduling, the control unit 270 may determine whether or not there is information about a code block group (CBG) based on a scheduled PUSCH or a valid PUSCH.

[0086] Specifically, in the case of a UL grant DCI configured based on a TDRA table including multiple SLIVs, the control unit 270 may determine the presence or absence (existence) of the CBGTI and / or CBGFI fields of the DCI based on a scheduled PUSCH or a valid PUSCH.

[0087] The control unit 270 may enable transmission of a configured grant (CG) PUSCH that overlaps with the canceled PUSCH, and may also enable transmission of a CG PUSCH that has the same HARQ process ID as the canceled PUSCH.

[0088] Here, in multi-PUSCH scheduling, if any PUSCH collides with a DL symbol, the control unit 270 may stop transmission of the PUSCH by the CG that has been canceled due to the collision.

[0089] Specifically, the control unit 270 may apply the operations described in Chapters 11 and 11.1 (Release 15 and 16) of 3GPP TS 38.213 for PUSCHs that do not use DCI to the CG PUSCH as well. In other words, if the CG PUSCH overlaps with a DL symbol, the CG PUSCH does not need to be transmitted.

[0090] Alternatively, the control unit 270 may not transmit a CG PUSCH that overlaps with a canceled PUSCH and / or a CG PUSCH that has the same HARQ process ID.

[0091] In addition, the gNB100 (data transceiver unit 260) may include a transmitter unit that transmits multiple downlink data channels (PDSCHs) scheduled by a single downlink control information (DCI) according to multi-PDSCH / PUSCH scheduling, and a receiver unit that receives multiple uplink data channels (PUSCHs).

[0092] (3) Operation of the wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, the description will be given of the operation related to multi-PDSCH / PUSCH scheduling, particularly the operation in the case where PDSCH / PUSCH collides with semi-static UL / DL symbols or the like (overlapping radio resource allocation) in TDD.

[0093] (3.1) Premise In 3GPP Release-17, multi-PDSCH / PUSCH scheduling may be supported and the following collisions may be allowed:

[0094] In multi-PDSCH scheduling, collisions with quasi-static UL symbols occur. In multi-PUSCH scheduling, collisions with quasi-static DL symbols, SSB symbols, and CORESET 0 symbols occur. Fig. 5 shows a configuration example of multi-PDSCH / PUSCH scheduling. As shown in Fig. 5, multi-PDSCH / PUSCH scheduling allows multiple PDSCHs / PUSCHs to be scheduled using one (single) DCI. Meanwhile, the slot format includes semi-static symbols (UL or DL ​​symbols, and may also include guard (G) symbols).

[0095] For this reason, in TDD, collisions between the PDSCH / PUSCH and the relevant symbols may occur. Although scheduling of the PDSCH / PUSCH (see the hatched box in the figure) where such collisions may occur is permitted, in reality, the relevant data channel cannot be transmitted.

[0096] Considering this situation, the following issues are considered to exist:

[0097] (Issue 1): It is not clear whether PDSCH / PUSCH canceled due to collision with semi-static UL / DL symbols is taken into account in OoO scheduling.

[0098] Issue 2: Regarding A-CSI reports triggered by DCI that schedules multiple PUSCHs in multi-PUSCH scheduling, the 3GPP Release-16 regulations are expected to be applied, but the regulations do not take into account cancellation of PUSCHs due to collisions with DL symbols.

[0099] (Problem 3): When the number of PUSCHs is used to determine the presence of the CBGTI field, it is unclear whether it should be based on the number of scheduled PUSCHs or the number of valid PUSCHs. Also, when the number of PDSCHs is used to determine the presence of the CBGTI / CBGFI field, it is unclear whether it should be based on the number of scheduled PDSCHs or the number of valid PDSCHs.

[0100] Issue 4: PDSCH cancellation due to collision with quasi-static UL symbols is not considered. For example, if DCI schedules multiple PDSCHs and only one PDSCH is valid, it is unclear whether the HARQ-ACK feedback should be included in the first or second sub-codebook.

[0101] Issue 5: In multi-PDSCH scheduling, when one of multiple PDSCHs scheduled by a single DCI is canceled due to a collision with a quasi-static UL symbol, if the timeline is met, it is unclear whether the SPS PDSCH can be received or whether it is permissible to schedule another PDSCH that overlaps with the canceled PDSCH.

[0102] (Problem 6): In multi-PUSCH scheduling, when one of multiple PUSCHs scheduled by a single DCI is canceled due to a collision with a quasi-static UL symbol, it is unclear whether a CG PUSCH that overlaps with the canceled PUSCH can be transmitted if the timeline is met, and whether a CG PUSCH that overlaps with the same HARQ process as the canceled PUSCH can be transmitted if the timeline is met. It is also unclear whether another PUSCH that overlaps with the canceled PUSCH can be scheduled.

[0103] (3.2) Example of operation Next, a description will be given of operational examples 1 to 6 corresponding to the above-mentioned problems 1 to 6. First, a description will be given of an example sequence relating to scheduling of data channels (PDSCH / PUSCH).

[0104] Fig. 6 shows an example of a sequence related to scheduling of a data channel. As shown in Fig. 6, the UE 200 may transmit UE Capability Information to the network, specifically, the gNB 100. In particular, an example of the UE Capability Information related to this operation example will be described later.

[0105] The gNB 100 may perform RRC configuration based on the capability of the UE 200. The gNB 100 may also transmit DCI to the UE 200. As described above, in multi-PDSCH / PUSCH scheduling, multiple PDSCHs / PUSCHs may be scheduled by a single DCI.

[0106] The gNB 100 may transmit multiple PDSCHs to the UE 200 in accordance with scheduling by the DCI. The UE 200 may transmit HARQ feedback (ACK or NACK) in response to reception of the PDSCHs to the gNB 100. As described above, types 1 and 2 may be supported for HARQ-ACK feedback.

[0107] Furthermore, UE200 may transmit multiple PUSCHs to gNB100 in accordance with multi-PUSCH scheduling.

[0108] (3.2.1) Example 1 This operation example corresponds to Problem 1 and relates to OoO scheduling. When a PDSCH according to multi-PDSCH scheduling is canceled due to a collision with a quasi-static UL symbol, one of the following operations may be applied to a PDSCH included in multiple PDSCHs scheduled by multi-PDSCH scheduling.

[0109] (Option 1-1): Cancelled PDSCHs are not taken into account in OoO scheduling decisions.

[0110] The behavior of UE 200 may be tolerant to the case where a PDSCH scheduled and canceled by an earlier DCI ends later than the start of a PDSCH scheduled by a later DCI.

[0111] In 3GPP specification terms, for any two HARQ process IDs in a given scheduled cell, if a UE is scheduled to start receiving a first PDSCH with a PDCCH starting in symbol j and ending in symbol i, and the first PDSCH does not overlap with any semi-static UL symbol, the UE is not expected to be scheduled to receive a second PDSCH that starts earlier than the end of the first PDSCH with a PDCCH ending in symbol i, where the first PDSCH does not overlap with any semi-static UL symbol.

[0112] (Option 1-2): Cancelled PDSCHs continue to be considered in OoO scheduling decisions.

[0113] As a behavior of the UE 200, the start of the PDSCH scheduled by the later DCI must be later than the end of the PDSCH scheduled by the earlier DCI.

[0114] Furthermore, when a PUSCH according to multi-PUSCH scheduling is canceled due to a collision with a quasi-static DL symbol, SSB symbol, and / or CORESET 0 symbol, any of the following operations may be applied to a PUSCH included in multiple PUSCHs scheduled by multi-PUSCH scheduling.

[0115] (Option 2-1): Cancelled PUSCHs are not taken into account in OoO scheduling decisions.

[0116] The behavior of UE 200 may be such that a PUSCH scheduled and canceled by an earlier DCI ends later than a PUSCH scheduled by a later DCI begins.

[0117] In 3GPP specification terms, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving the first PUSCH with a PDCCH starting in symbol j and ending in symbol i, and the first PUSCH does not overlap with any semi-static UL symbol, SSB symbol, or CORESET#0 symbol, the UE is not expected to be scheduled to receive a second PUSCH that starts earlier than the end of the first PUSCH with a PDCCH ending in symbol i, where the second PUSCH does not overlap with any semi-static UL symbol, SSB symbol, or CORESET#0 symbol. PUSCH by a PDCCH that ends later than symbol I, where the second PUSCH doesn't overlap with any with semi-static DL symbol, and / or symbol configured for SSB or CORESET#0.).

[0118] (Option 2-2): Cancelled PUSCHs continue to be taken into account in OoO scheduling decisions.

[0119] The behavior of UE 200 is such that the start of any PUSCH scheduled by a later DCI must be later than the end of any PUSCH scheduled by an earlier DCI.

[0120] (3.2.2) Example 2 This operation example corresponds to issue 2 and relates to A-CSI reporting. Fig. 7 shows an example of the TDRA table.

[0121] For an A-CSI report triggered by a UL grant DCI configured according to a TDRA table that includes multiple SLIVs in at least one row, such as the TDRA table of FIG. 7, any of the following operations may be applied.

[0122] (Option 1): A-CSI reporting is determined based on the scheduled PUSCH.

[0123] As for the behavior of UE 200, assuming that the number of scheduled PUSCHs is M, if M≦2, UE 200 may report an A-CSI report in the Mth scheduled PUSCH.

[0124] If M>2, the UE 200 may report the A-CSI report in the (M-1)th scheduled PUSCH.

[0125] In addition, the PUSCH used for the A-CSI report may be canceled due to collision with a semi-static DL symbol, an SSB symbol, and / or a symbol set to CORESET 0.

[0126] Furthermore, if the PUSCH determined for the A-CSI report is canceled due to a collision with the DL symbol, SSB symbol, and / or a symbol set to CORESET 0, one of the following operations may be applied.

[0127] · (Alt 1): The last valid PUSCH before the determined PUSCH is used for the A-CSI report.

[0128] (Alt 2): The last scheduled PUSCH is used for the A-CSI report.

[0129] (Alt 3): No A-CSI report is made.

[0130] (Option 2): A-CSI report is determined based on valid PUSCH.

[0131] Assuming that the number of scheduled PUSCHs is M and the number of valid PUSCHs is N, and N≦2, the behavior of UE 200 may be as follows: UE 200 may report an A-CSI report in the Nth valid PUSCH.

[0132] If N>2, the UE 200 may report the A-CSI report in the (N-1)th valid PUSCH.

[0133] As mentioned above, a valid PUSCH may be interpreted as a PUSCH that does not collide with semi-static UL symbols, SSBs and / or symbols set to CORESET 0.

[0134] With this option, the PUSCH used for the A-CSI report may be canceled due to collision with DL symbols, SSBs, or symbols set to CORESET 0.

[0135] (3.2.3) Example 3 This operation example corresponds to Problem 3 and relates to CBG-based transmission. For a DL grant DCI configured according to a TDRA table including multiple SLIVs in at least one row, such as the TDRA table in Fig. 7, any of the following operations may be applied.

[0136] (Option 1-1): The presence of the CBGTI / CBGFI fields is determined based on the scheduled PDSCH.

[0137] The CBGTI / CBGFI field may be assumed to be present if the number of scheduled PDSCHs by DCI is 1. If the number of scheduled PDSCHs by DCI is greater than 1, the CBGTI / CBGFI field may be assumed to be absent.

[0138] · (Option 1-2): The presence of the CBGTI / CBGFI fields is determined based on the valid PDSCH.

[0139] If the number of scheduled PDSCHs due to DCI is 1, it may be assumed that the CBGTI / CBGFI field is present. If the number of scheduled PDSCHs due to DCI is greater than 1, the following operation may be performed.

[0140] If the number of valid PDSCHs is one, the CBGTI / CBGFI field may be assumed to be present.

[0141] If the number of valid PDSCHs is greater than 1, the CBGTI / CBGFI fields may be assumed not to be present.

[0142] Furthermore, for a UL grant DCI configured according to a TDRA table that includes multiple SLIVs in at least one row, any of the following operations may be applied.

[0143] (Option 2-1): The presence of the CBGTI field is determined based on the scheduled PUSCH.

[0144] The CBGTI field may be assumed to be present if the number of scheduled PUSCHs due to DCI is 1. If the number of scheduled PUSCHs due to DCI is greater than 1, the CBGTI field may be assumed not to be present.

[0145] (Option 2-2): The presence of the CBGTI field is determined based on the valid PUSCH. If the number of PUSCHs scheduled by DCI is 1, the CBGTI field may be assumed to be present. If the number of PUSCHs scheduled by DCI is greater than 1, the following behavior may occur:

[0146] If the number of valid PUSCHs is one, the CBGTI field may be assumed to be present.

[0147] If the number of valid PUSCHs is greater than 1, the CBGTI field may be assumed not to be present.

[0148] (3.2.4) Example 4 This operation example corresponds to Problem 4 and relates to type 2 HARQ-ACK feedback. For a DL grant DCI that is configured according to a TDRA table including multiple SLIVs in at least one row, such as the TDRA table in Fig. 7, and schedules multiple PDSCHs, any of the following operations may be applied.

[0149] (Option 1): HARQ-ACK information is included in the second sub-codebook regardless of the number of invalid / valid PDSCHs.

[0150] · (Option 2): HARQ-ACK information may be included in the first or second sub-codebook based on the number of valid PDSCHs.

[0151] In this case, if there is only one valid PDSCH among the multiple scheduled PDSCHs, the HARQ-ACK information of the DCI may be included in the first sub-codebook, and if there are multiple valid PDSCHs among the multiple scheduled PDSCHs, the HARQ-ACK information of the DCI may be included in the second sub-codebook.

[0152] Note that the first sub-codebook may refer to a sub-codebook for DCI that schedules only one PDSCH (i.e., means that a TDRA row includes only one SLIV).

[0153] (3.2.5) Example 5 This operation example corresponds to Problem 5 and relates to handling of SPS / DG PDSCH collision. A PDSCH included in multiple PDSCHs scheduled by a single DCI is canceled due to a collision with a semi-static UL symbol. In this case, if the timeline specified in 3GPP Release-16 is met, the PDSCH may be overwritten by an SPS (rescheduling of the PDSCH). Specifically, any of the following operations may be applied:

[0154] (Option 1-1): It may be assumed that the SPS PDSCH that overlaps with the cancelled PDSCH can be received.

[0155] The behavior described in 3GPP TS 38.213, Chapters 11 and 11.1 (Release 15, 16) for PDSCH without DCI may also apply to SPS PDSCH, i.e., if the SPS PDSCH overlaps with an UL symbol, the SPS PDSCH may not be received.

[0156] · (Option 1-2): It may be assumed that the SPS PDSCH that overlaps with the cancelled PDSCH is not received.

[0157] Furthermore, for the canceled PDSCH resources, one of the following operations may be applied.

[0158] · (Option 2-1): DCI can schedule another dynamic PDSCH for the remaining valid symbols of the canceled PDSCH.

[0159] · (Option 2-2): Do not expect another dynamic PDSCH to be scheduled by DCI for the remaining valid symbols of the cancelled PDSCH.

[0160] (3.2.6) Example 6 This operation example corresponds to Problem 6 and relates to handling of CG / DG PUSCH collision. A PUSCH included in multiple PUSCHs scheduled by a single DCI is canceled due to collision with a semi-static DL symbol, SSB symbol, and / or a symbol set to CORESET 0. In this case, if the timeline specified in 3GPP Release-16 is met, the PUSCH may be overwritten by the CG (PUSCH rescheduling). Specifically, any of the following operations may be applied.

[0161] (Option 1-1): It may be assumed that a CG PUSCH that overlaps with a cancelled PUSCH can be transmitted.

[0162] The operations described in 3GPP TS 38.213, Chapters 11 and 11.1 (Release 15, 16) for PUSCH without DCI may also be applied for CG PUSCH, i.e., if the CG PUSCH overlaps with a DL symbol, the CG PUSCH may not be transmitted.

[0163] · (Option 1-2): It may be assumed that CG PUSCHs that overlap with cancelled PUSCHs are not transmitted.

[0164] Furthermore, if the timeline specified in 3GPP Release-16 is met, one of the following behaviors may be applied regarding DG / CG HARQ process collisions.

[0165] (Option 2-1): It may be assumed that a CG PUSCH with the same HARQ process ID as the canceled PUSCH can be transmitted.

[0166] The operations described in 3GPP TS 38.213, Chapters 11 and 11.1 (Release 15, 16) for PUSCH without DCI may also be applied for CG PUSCH, i.e., if the CG PUSCH overlaps with a DL symbol, the CG PUSCH may not be transmitted.

[0167] (Option 2-2): A CG PUSCH with the same HARQ process ID as the canceled PUSCH may not be transmitted.

[0168] Furthermore, for the canceled PUSCH resources, one of the following operations may be applied.

[0169] (Option 3-1): DCI can schedule another dynamic PUSCH for the remaining valid symbols of the canceled PUSCH.

[0170] (Option 3-2): Do not expect another dynamic PUSCH to be scheduled by DCI for the remaining valid symbols of the canceled PUSCH.

[0171] (3.2.7) Example of change The following modifications may be further applied to the above-described operation examples. Specifically, which operation example (option) to apply may be determined based on any of the following:

[0172] Higher layer (RRC, etc.) parameters UE capability report from UE200 3GPP specifications Combining higher layer parameter settings with reported UE capabilities The operational example may also be limited to the following conditions.

[0173] 52.6~71 GHz(FR2x) Unlicensed frequency bands Specific SCS Any combination of the above

[0174] (3.2.8) UE capability The capabilities of the UE 200 regarding multi-PDSCH / PUSCH scheduling (UE capability) may include at least one of the following.

[0175] - Support for OoO scheduling that takes into account canceled PDSCH - Support for OoO scheduling that takes into account canceled PUSCH Support for A-CSI reports that take into account canceled PUSCH Support for CBG-based scheduling that takes into account canceled PDSCH Support for CBG-based scheduling that takes into account canceled PUSCH Support for type 2 HARQ-ACK CB generation taking into account canceled PDSCH Support for overwriting SPS PDSCH considering cancelled PDSCH - Support for allocating the resources of a cancelled PDSCH to another dynamic grant PDSCH Support for overwriting CG PDSCH considering canceled PUSCH Support for allocating canceled PUSCH resources to another dynamic grant PUSCH

[0176] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained: Specifically, according to the above-described gNB 100 and UE 200, even when multi-PDSCH / PUSCH scheduling is applied and collision between the PDSCH / PUSCH and UL / DL symbols is allowed, operations according to operation examples 1 to 6 can be performed, and therefore, reception of the PDSCH / PUSCH can be continued normally.

[0177] That is, gNB100 and UE200 can realize appropriate multi-PDSCH / PUSCH scheduling that takes into account collisions in TDD.

[0178] (5) Other embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments and that various modifications and improvements are possible.

[0179] For example, in the above-described embodiment, PDSCH / PUSCH has been described as an example, but similar operations may be applied to multiple data channels scheduled by a single DCI.

[0180] Also, in the above description, "configure," "activate," "update," "indicate," "enable," "specify," and "select" may be interchangeable. Similarly, "link," "associate," "correspond," and "map" may be interchangeable, and "allocate," "assign," "monitor," and "map" may also be interchangeable.

[0181] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0182] Furthermore, the block diagram (FIG. 4) used in the description of the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

[0183] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0184] Furthermore, the above-described gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 8 is a diagram showing an example of the hardware configuration of the device. As shown in Figure 8, the device may be 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, etc.

[0185] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0186] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0187] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0188] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0189] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0190] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

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

[0192] 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 called, for example, a network device, a network controller, a network card, or a communication module.

[0193] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0194] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0195] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0196] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0197] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0198] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0199] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0200] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0201] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0202] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be sent to another device.

[0203] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0204] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0205] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0206] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0207] 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. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0208] 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0209] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0210] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0211] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0212] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0213] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0214] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0215] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0216] A mobile station may also be referred to by those 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 terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0217] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include 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 Internet of Things (IoT) device such as a sensor.

[0218] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as uplink channel and downlink channel may be read as side channel.

[0219] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station. A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0220] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

[0221] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based time unit.

[0222] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0223] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0224] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0225] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0226] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0227] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

[0229] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0231] 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. Each TTI, subframe, etc. may be composed of one or more resource blocks.

[0232] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0233] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0234] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

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

[0236] 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 the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0237] The above-described structures of the radio frame, subframe, slot, minislot, and symbol 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 subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

[0238] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0239] The reference signal may also be abbreviated as Reference Signal (RS), and may also be called a pilot depending on the applicable standard.

[0240] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0241] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0242] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0243] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0244] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0245] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0246] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0247] 9 shows an example of the configuration of a vehicle 2001. As shown in Fig. 9, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0248] 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 called a handle), 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 are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0250] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0251] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0252] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0253] 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 an external device. For example, it transmits and receives various information to and from the 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.

[0254] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0255] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0256] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0257] 10. Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 communication port

Claims

1. a receiving unit for receiving a single downlink control information for scheduling a plurality of downlink data channels; a control unit that determines a codebook including feedback of automatic repeat requests for the downlink data channels based on receiving a plurality of downlink data channels scheduled by the single downlink control information; A terminal comprising:

2. 2. The terminal according to claim 1, wherein the control unit determines a second sub-codebook as the codebook, and the second sub-codebook is different from a first sub-codebook that includes feedback of an automatic repeat request for a downlink data channel scheduled by downlink control information that schedules one downlink data channel.

3. A wireless communication system including a wireless base station and a terminal, the radio base station includes a transmitter that transmits single downlink control information for scheduling a plurality of downlink data channels; The terminal a receiving unit for receiving the single downlink control information; a control unit that determines a codebook including feedback of automatic repeat requests for the downlink data channels based on receiving a plurality of downlink data channels scheduled by the single downlink control information; A wireless communication system comprising:

4. receiving a single downlink control information scheduling a plurality of downlink data channels; determining a codebook including feedback of automatic repeat requests for the downlink data channels based on receiving a plurality of downlink data channels scheduled by the single downlink control information; A wireless communication method for a terminal including:

Images