Terminal, wireless communication method, base station and system

Abstract

The present invention appropriately performs communication using one DCI (or PDCCH), even if a plurality of DL transmissions are transmitted / scheduled from one or more TRPs. A terminal according to one aspect of the present disclosure comprises: a reception unit that receives information relating to the transmission direction of symbols included in a slot; and a control unit that, if a plurality of repeated transmissions of a downlink shared channel to which a time-division multiplexing (TDM) scheme is applied are set within the slot, assumes that at least one of the plurality of repeated transmissions does not overlap a UL symbol.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. 、 base station and systems Regarding. [Background technology]

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (e.g., NR), it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmission (e.g., downlink shared channel (e.g., PDSCH) transmission) to a terminal (user terminal, User Equipment (UE)).

[0006] In addition, in NR, it is also assumed that multiple signals / channels (e.g., multi-PDSCH) are transmitted / received from one or more transmission / reception points. For example, it is conceivable that multi-PDSCH transmission is controlled using one or more downlink control information (e.g., DCI) / downlink control channels (e.g., PDCCH) from one or more transmission / reception points.

[0007] However, there has been insufficient consideration as to how to control when multiple DL transmissions (e.g., multi-PDSCH) are transmitted / scheduled from one or more TRPs using one DCI (or PDCCH).

[0008] Therefore, the present disclosure provides a terminal and a wireless communication method that can appropriately perform communication even when multiple DL transmissions are transmitted / scheduled from one or more TRPs using one DCI (or PDCCH). 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0009] A terminal according to an aspect of the present disclosure includes a receiving unit that receives information regarding a transmission direction of a symbol included in a slot, and a control unit that sets multiple repeated transmissions of a downlink shared channel to which a time division multiplexing (TDM) scheme is applied within the slot. R, At least one of the plurality of repeated transmissions Uplink Symbols and Overlaps Push R If so, it is determined that the downlink shared channel scheduled in the slot is invalid. A control unit and When feedback of an acknowledgement signal for the downlink shared channel is performed using a semi-static acknowledgement signal codebook, the control unit controls generation of the acknowledgement signal codebook in consideration of an offset between the multiple repeated transmissions. do. [Effects of the Invention]

[0010] According to one aspect of the present disclosure, communication can be performed appropriately even when multiple DL transmissions are transmitted / scheduled from one or more TRPs using one DCI (or PDCCH). [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of scheduling control of a physical shared channel based on PDCCH / DCI. [Figure 2] 2A-2D illustrate an example of a multi-TRP scenario. [Figure 3] 3A to 3C are diagrams illustrating an example of generating a Type 1 HARQ-ACK codebook for Rel. 15 NR. [Figure 4] FIG. 4 is a diagram illustrating an example of repeated transmission of PDSCH in Rel. 16 NR. [Figure 5] FIG. 5 shows an example of a case where multi-PDSCH scheduling is performed in a single DCI-based multi-TRP (single DCI-based MTRP PDSCH with tdmschemeA+multi-PDSCH scheduling). [Figure 6] FIG. 6 is a diagram illustrating an example of Type 1 HARQ-ACK feedback. [Figure 7]FIG. 7 is a diagram showing an example of a method for determining whether a PDSCH is valid or invalid based on an SLIV and an UL symbol according to the present embodiment. [Figure 8] FIG. 8 is a diagram showing another example of a method for determining whether a PDSCH is valid or invalid based on an SLIV and an UL symbol according to the present embodiment. [Figure 9] 9A to 9C are diagrams showing other examples of the method of determining whether a PDSCH is valid or invalid based on the SLIV and UL symbol according to the present embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (Time domain resource allocation) In existing systems (e.g., Rel. 15), time-domain resource allocation information for a physical shared channel (at least one of a PDSCH and a PUSCH) is included in downlink control information (DCI). A network (e.g., a base station) uses a predetermined field (e.g., a TDRA field) included in the DCI to notify a UE of information regarding the time-domain resource in which the physical shared channel scheduled in the DCI is scheduled.

[0013] The information regarding the time domain resource may include, for example, at least one of information indicating the offset between the DCI and the physical shared channel (e.g., slot offset K0), information indicating the start symbol (e.g., start symbol S), and information indicating the length of the physical shared channel (e.g., length L).

[0014] Each bit information (or code point) notified in the TDRA field may be associated with a different time domain resource allocation candidate (or entry). For example, a table (e.g., a TDRA table) in which each bit information is associated with the time domain resource allocation candidates (K0, S, L) may be defined. The time domain resource allocation candidates may be predefined in a specification or may be notified / configured to the UE by higher layer signaling.

[0015] [PDSCH] The UE may determine a row index (entry number or entry index) in a predetermined table based on the value of the TDRA field in the DCI (e.g., DCI format 1_0 / 1_1 / 1_2). The predetermined table may include at least one of information indicating a time offset (e.g., slot offset K0) between the DCI and the PDSCH scheduled by the DCI, information indicating a mapping type of the PDSCH, and a start symbol S and a time length L of the PDSCH. The combination of the start symbol S and the time length L of the PDSCH may be referred to as a Start and Length Indicator (SLIV).

[0016] The UE may determine the time domain resource on which the PDSCH is scheduled based on the value of a predetermined field included in the DCI and at least one of slot offset K0 information, mapping type, start symbol S, symbol length L, and SLIV specified in the table (see FIG. 1). Note that the reference points of the start symbol S and symbol length L may be controlled based on the start position (first symbol) of the slot. Also, the start symbol S, symbol length L, etc. may be defined according to the mapping type of the PDSCH.

[0017] As shown in Figure 1, the UE determines the slot in which the PDSCH is scheduled, using the DCI (or the PDCCH used to transmit the DCI) as a reference point in the time domain. For example, when the UE receives DCI scheduling the PDSCH in slot #n, it determines the slot number n and the subcarrier spacing μ for the PDSCH. PDSCH , subcarrier spacing for PDCCH μ PDCCH The slot for receiving the PDSCH (allocated to the PDSCH) may be determined based on at least one of the time offsets K0. Here, the case is shown where the slot offset K0=1 and the subcarrier intervals of the PDSCH and PDCCH are the same.

[0018] Furthermore, the UE determines the allocation of the PDSCH based on the resource allocation information (e.g., SLIV) specified in the TDRA field, using the starting point of the slot to which the PDSCH is allocated as a reference point. Note that the reference point may also be called a reference point or a reference point.

[0019] [PUSCH] The UE may determine a row index (entry number or entry index) in a predetermined table based on the value of the TDRA field in the DCI (e.g., DCI format 0_0 / 0_1 / 0_2). The predetermined table may include at least one of information indicating a time offset (e.g., slot offset K2) between the DCI and the PUSCH scheduled by the DCI, information indicating a mapping type of the PUSCH, and a start symbol S and a duration L of the PUSCH. The combination of the start symbol S and duration L of the PUSCH may be referred to as a Start and Length Indicator (SLIV).

[0020] The UE may determine the time domain resource on which the PUSCH is scheduled based on the value of a predetermined field included in the DCI and at least one of slot offset K2 information, mapping type, start symbol S, symbol length L, and SLIV specified in the table (see FIG. 1). Note that the reference points of the start symbol S and symbol length L may be controlled based on the start position (first symbol) of the slot. Also, the start symbol S, symbol length L, etc. may be defined according to the mapping type of the PDSCH.

[0021] As shown in Figure 1, the UE determines the slot in which the PUSCH is scheduled, using the DCI (or the PDCCH used to transmit the DCI) as a reference point in the time domain. For example, when the UE receives DCI scheduling the PUSCH in slot #n+4, it determines the slot number n+4 and the subcarrier spacing μ for the PUSCH. PDSCH , subcarrier spacing for PUCCH μ PDCCH The slot for transmitting the PUSCH (allocated to the PUSCH) may be determined based on at least one of the time offsets K2. Here, the case is shown where the slot offset K2=3 and the subcarrier intervals of the PDSCH and PDCCH are the same.

[0022] Furthermore, the UE determines the allocation of the PUSCH based on the resource allocation information (for example, SLIV) specified in the TDRA field, using the start point of the slot to which the PUSCH is allocated as a reference.

[0023] (Multi-TRP) In NR, one or more Transmission / Reception Points (TRPs) (multi-TRP) are considered to perform DL transmission to a UE using one or more panels (multi-panel), and a UE is considered to perform UL transmission to one or more TRPs.

[0024] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0025] 2A-2D illustrate an example of a multi-TRP scenario, assuming, but not limited to, that each TRP is capable of transmitting four different beams.

[0026] 2A shows an example of a case where only one TRP (TRP1 in this example) of multiple TRPs transmits to the UE (this may be referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0027] 2B shows an example of a case where only one TRP (TRP1 in this example) transmits a control signal to a UE, and the TRP transmits a data signal (this case may be called a single master mode). The UE receives each PDSCH transmitted from the TRP based on one Downlink Control Information (DCI).

[0028] 2C shows an example of a case where each of the multiple TRPs transmits a part of the control signal to the UE and the multiple TRPs transmit data signals (this may be called a master-slave mode). Part 1 of the control signal (DCI) may be transmitted in TRP1, and Part 2 of the control signal (DCI) may be transmitted in TRP2. Part 2 of the control signal may depend on Part 1. The UE receives each PDSCH transmitted from the multiple TRPs based on these parts of DCI.

[0029] 2D shows an example of a case where each of the multiple TRPs transmits a separate control signal to the UE, and the multiple TRPs transmit data signals (this may be referred to as a multi-master mode). A first control signal (DCI) may be transmitted from TRP1, and a second control signal (DCI) may be transmitted from TRP2. The UE receives each PDSCH transmitted from the multiple TRPs based on these DCIs.

[0030] When multiple PDSCHs (which may be referred to as multiple PDSCHs) from multiple TRPs as in Figure 2B are scheduled using one DCI, the DCI may be referred to as a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from multiple TRPs as in Figure 2D are scheduled using multiple DCIs, these multiple DCIs may be referred to as multiple DCIs (M-DCI, multiple PDCCHs).

[0031] Each TRP in a multi-TRP may transmit a different transport block (TB) / code word (CW) / different layer, or each TRP in a multi-TRP may transmit the same TB / CW / layer.

[0032] Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 performs modulation mapping and layer mapping on a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding. TRP2 performs modulation mapping and layer mapping on a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

[0033] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in at least one of the time and frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

[0034] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (Quasi-Co-Location (QCL)). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0035] In URLLC for multiple TRPs, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is supported. Repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, and 4) across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain are supported. In scheme 1, multiple PDSCHs from multiple TRPs are space division multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexed (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RVs may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0036] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0037] An NCJT using multiple TRPs / panels may use a high rank. To support ideal and non-ideal backhaul between multiple TRPs, both single DCI (single PDCCH, e.g., FIG. 2B) and multiple DCI (multiple PDCCH, e.g., FIG. 2D) may be supported. For both single DCI and multi-DCI, the maximum number of TRPs may be two.

[0038] For single PDCCH design (mainly for ideal backhaul), TCI extensions are being considered. Each TCI codepoint in the DCI may correspond to a TCI state of 1 or 2. The TCI field size may be the same as that in Rel. 15.

[0039] (HARQ-ACK codebook) The UE may transmit HARQ-ACK feedback using one PUCCH resource for each HARQ-ACK codebook consisting of one or more acknowledgement information bits (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)). The HARQ-ACK bits may also be referred to as HARQ-ACK information, HARQ-ACK information bits, etc.

[0040] Here, the HARQ-ACK codebook may be configured to include bits for HARQ-ACK in at least one unit of the time domain (e.g., slot), the frequency domain (e.g., component carrier (CC)), the spatial domain (e.g., layer), the transport block (TB), and the code block group (CBG) constituting the TB. The HARQ-ACK codebook may be simply referred to as a codebook.

[0041] The number of bits (size) included in the HARQ-ACK codebook may be determined semi-statically or dynamically. An HARQ-ACK codebook whose size is determined semi-statically is also called a semi-static HARQ-ACK codebook, a type 1 HARQ-ACK codebook, etc. An HARQ-ACK codebook whose size is determined dynamically is also called a dynamic HARQ-ACK codebook, a type 2 HARQ-ACK codebook, etc.

[0042] Whether to use the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook may be configured in the UE using a higher layer parameter (for example, pdsch-HARQ-ACK-Codebook).

[0043] In the case of a Type 1 HARQ-ACK codebook, the UE may feed back HARQ-ACK bits for PDSCH candidates (or PDSCH occasions) corresponding to a certain range (e.g., a range set based on higher layer parameters), regardless of whether PDSCH is scheduled or not.

[0044] The range may be determined based on at least one of a certain period (e.g., a set of a certain number of candidate occasions for PDSCH reception or a certain number of monitoring occasions of a Physical Downlink Control Channel (PDCCH)), the number of CCs configured or activated in the UE, the number of TBs (number of layers or ranks), the number of CBGs per TB, and whether spatial bundling is applied. The specific range is also called a HARQ-ACK window, a HARQ-ACK bundling window, a HARQ-ACK feedback window, etc.

[0045] In the type 1 HARQ-ACK codebook, even if a PDSCH is not scheduled for the UE, the UE reserves a HARQ-ACK bit for the PDSCH in the codebook within a specific range. If the UE determines that the PDSCH is not actually scheduled, it can feed back the bit as a NACK bit.

[0046] Meanwhile, in the case of a Type 2 HARQ-ACK codebook, the UE may feed back HARQ-ACK bits for the scheduled PDSCH within the specified range.

[0047] In Rel. 15 / 16 NR, a UE determines a HARQ-ACK codebook for a PDSCH of one or more slots to be transmitted using a certain PUCCH based on the value of the HARQ-ACK timing.

[0048] The transmission timing of the HARQ-ACK for a dynamic PDSCH (which may be referred to as PDSCH-to-HARQ feedback timing, K1, etc.) may be indicated by a PDSCH-to-HARQ feedback timing indicator field included in the DCI (e.g., DCI format 1_0 / 1_1) that schedules the dynamic PDSCH. If the last slot in which a certain PDSCH was received is n, the UE transmits the HARQ-ACK corresponding to the PDSCH in n+K1 slots.

[0049] The UE may determine the size of the window (which may also be referred to as the HARQ-ACK window) of the semi-static HARQ-ACK codebook to transmit on the PUCCH in a certain slot based on the number of slots with the same value of n+K1.

[0050] Next, the UE determines candidate PDSCH reception opportunities (candidate PDSCH opportunities, or simply opportunities) for each slot corresponding to the HARQ-ACK window, and excludes candidate PDSCH opportunities that overlap with UL symbols from the semi-static HARQ-ACK codebook.

[0051] 3A-3C are diagrams illustrating an example of generating a Type 1 HARQ-ACK codebook for Rel. 15 NR. Figure 3A illustrates an example of a list of time domain resource allocations for PDSCH that a UE is configured with or that are specified in a specification. The row index r in the diagram corresponds to the value of the time domain resource allocation field included in the DCI.

[0052] K0 indicates the number of symbols from PDCCH (DCI) reception to PDSCH reception. Start indicates the index S of the start symbol in the PDSCH slot. Length indicates the length of the PDSCH (number of symbols). Mapping type indicates the PDSCH resource allocation type (A or B).

[0053] Figure 3B shows candidate PDSCH opportunities corresponding to the list in Figure 3 A. For example, the candidate PDSCH opportunity corresponding to r=0 corresponds to a period of length 4 symbols starting at symbol #2.

[0054] The UE excludes / deletes candidate PDSCH opportunities that overlap with UL symbols (e.g., symbols configured as UL by higher layer parameters). In this example, since the last two symbols of this slot are UL symbols, candidate PDSCH opportunities corresponding to r=2, 3, 8 are deleted, and r={0, 1, 4, 5, 6, 7} in Figure 3B correspond to j={0, 1, 0, 1, 2, 3}, respectively. Here, j is an index indicating which bit in the HARQ-ACK codebook to transmit corresponds to.

[0055] The UE can generate only one HARQ-ACK bit for the overlapping candidate PDSCH opportunities according to a predetermined rule. Therefore, the set of candidate PDSCH opportunities M A,c ={0, 1, 2, 3}.

[0056] Finally, the UE A,c The number of HARQ-ACK bits may be determined based on the number of elements (also called cardinality) of . FIG. 3C is a diagram showing each bit of the HARQ-ACK codebook corresponding to FIG. 3B. In FIG. 3C, o0 ACK From O3 ACK For simplicity, in this specification, k ACK Although the tilde (~) above the "o" in (k is an integer) is omitted, this can be read interchangeably with the notation with the tilde added as shown in the drawings.

[0057] The TB-based HARQ-ACK bits are arranged in the order of the CC index and the PDCCH monitoring period. ACK From O3 ACK are the above M A,c = {0, 1, 2, 3} respectively.

[0058] Note that Figure 3C shows the contents of the HARQ-ACK codebook corresponding to only one slot in Figure 3B, but of course, when transmitting HARQ-ACK codebooks corresponding to PDSCHs of multiple slots in the same slot, the number of bits of the HARQ-ACK codebook may differ from that in Figure 3C.

[0059] (Repeated PDSCH transmission) In Rel.15 / 16 NR and later, repeated transmission of PDSCH is being considered. For example, repeated transmission of PDSCH may be performed for PDSCH transmission using multiple transmission / reception points (TRPs) (multi-TRP) or multiple panels (multi-panels).

[0060] The UE may be configured with at least one of Frequency Division Multiplexing (FDM) scheme A ('FDMSchemeA'), FDM scheme B ('FDMSchemeB'), Time Division Multiplexing (TDM) scheme A ('TDMSchemeA'), etc. as the value of an upper layer parameter (RepSchemeEnabler) related to enabling the repetition transmission scheme of the PDSCH.

[0061] Furthermore, when two TCI states are specified in the codepoint of the Transmission Configuration Indication (TCI) field of the DCI, a UE configured with TDM scheme A receives two PDSCH transmission opportunities of the same TB in each TCI state associated with a PDSCH transmission opportunity, where one of the two PDSCH transmission opportunities has a non-overlapping time-domain resource allocation with respect to the other, and both of the two PDSCH transmission opportunities are received within a slot.

[0062] In the present disclosure, a PDSCH transmission opportunity may be read as a PDSCH reception opportunity.

[0063] A UE configured with TDM scheme A and assigned two TCI states expects to receive two PDSCH transmission opportunities, where the first TCI state applies to the first PDSCH transmission opportunity and the second TCI state applies to the second PDSCH transmission opportunity, and these two PDSCH transmission opportunities correspond to repeated transmissions of TDM scheme A.

[0064] The time-domain resource allocation for the first PDSCH transmission opportunity may be determined according to the time-domain resource allocation field of the DCI. The time-domain resource allocation for the second PDSCH transmission opportunity may have the same number of symbols as the first PDSCH transmission opportunity.

[0065] The UE may determine that the first symbol of the second PDSCH transmission opportunity starts a certain number of symbols after the last symbol of the first PDSCH transmission opportunity, which may be provided by a higher layer parameter (StartingSymbolOffsetK) or may be assumed to be 0 by the UE if the higher layer parameter is not provided.

[0066] The UE may not expect to receive more than two PDSCH transmission layers for each PDSCH transmission opportunity.

[0067] 4 is a diagram showing an example of repeated transmission of PDSCH in Rel.16 NR. In this example, a UE configured with TDM scheme A receives DCI in a certain slot that schedules repeated transmission of PDSCH (PDSCH #1, #2) in that slot, and receives these PDSCHs in accordance with the DCI. PDSCH #1 and #2 may be the same TB. Note that in this example, the StartingSymbolOffsetK is not provided to the UE, and transmission of PDSCH #2 starts from the symbol immediately after PDSCH #1.

[0068] (Multi-PDSCH) In Rel. 17 NR and later, support for multiple PDSCHs (multi-PDSCHs) scheduled by a single DCI is being considered. For example, it is expected that single-TRP-based multi-PDSCHs (S-TRP based multi-PDSCHs) and multi-TRP-based multi-PDSCHs (M-TRP based multi-PDSCHs) will be supported.

[0069] When scheduling multi-TRP-based multi-PDSCHs using DCI (e.g., single DCI), it is assumed that the DCI supports a single DCI field (e.g., Transmission Configuration Indication) for TCI notification. The single DCI field (or single DCI field) may reuse the TCI status indication mechanism for multi-TRPs in Rel. 16.

[0070] A single DCI field may indicate one or more (e.g., two) TCI states associated with a codepoint for a single DCI-based multi-TRP mechanism, where a multi-PDSCH using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH) is considered.

[0071] Figure 5 shows an example of multi-PDSCH scheduling in a single DCI-based multi-TRP system, where TDM scheme A (tdmschemeA) is applied as a multi-TRP PDSCH (e.g., PDSCH repetition) (single DCI-based MTRP PDSCH with tdmschemeA + multi-PDSCH scheduling).

[0072] A single DCI field (e.g., Transmission Configuration Indication) may indicate one or two TCI states associated with a codepoint of the single DCI-based multi-TRP mechanism. In this case, the UE needs to receive two PDSCH repetitions of the same transport block (TB) for each scheduled PDSCH. The two PDSCH repetitions (or the TBs corresponding to the two PDSCH repetitions, respectively) may have respective TCI states associated with PDSCH transmission opportunities within the same slot.

[0073] For example, the same TB may be repeatedly transmitted within the same slot using a first repetition (e.g., Rep#1) and a second repetition (e.g., Rep#2) corresponding to PDSCH#1. In the present disclosure, the first repetition (e.g., Rep#1) and the second repetition (e.g., Rep#2) within a slot may be interpreted as the first PDSCH transmission opportunity and the second PDSCH transmission opportunity within the slot.

[0074] In this case, the PDSCH corresponding to the second repetition (e.g., Rep#2) (second PDSCH repetition) may be configured with the same number of symbols as the PDSCH corresponding to the first repetition (e.g., Rep#1) (first PDSCH repetition). In other words, the number of symbols for the first PDSCH transmission opportunity and the number of symbols for the second PDSCH transmission opportunity may be configured to be the same within the same slot.

[0075] The UE receives a predetermined offset (e.g., a starting symbol offset (e.g., K - )) is set, the start symbol of the second PDSCH transmission opportunity is a predetermined symbol (e.g., K - symbols) after the starting symbol offset (e.g., K - ) may be notified / configured to the UE by the base station using an upper layer parameter (e.g., StartingSymbolOffsetK).

[0076] A predetermined offset (e.g., starting symbol offset (e.g., K - )) may be commonly applied to multiple PDSCHs scheduled in one DCI (for example, the first and second repetitions of each slot).

[0077] (HARQ-ACK feedback for multi-PDSCH schedule) For HARQ-ACK feedback for a multi-PDSCH schedule, a type 1 HARQ-ACK codebook without time domain bundling may be applied.

[0078] For a Type 1 HARQ-ACK codebook without time domain bundling, the set of DL slots may include all unique DL slots determined by considering all combinations of the configured K1 value and the configured rows of the TDRA table.

[0079] Furthermore, the set of SLIVs corresponding to a DL slot (or a DL slot belonging to a set of DL slots) may include all SLIVs of that slot, which are determined by considering all combinations of the configured value of K1 and the configured rows of the TDRA table, as described above. Figure 6 shows an example of performing HARQ-ACK feedback (or HARQ-ACK codebook generation) by considering SLIVs in multiple slots.

[0080] To determine candidate PDSCH reception occasions for a set of SLIVs corresponding to each DL slot in the set of DL slots, the Rel.16 procedures may be reused, which may include, for example, pruning of multiple SLIVs corresponding to DL slots for both UEs that can receive multiple PDSCHs per slot and UEs that cannot.

[0081] For example, when using the Rel.16 procedure, if an SLIV overlaps with a predetermined UL symbol, the SLIV may be deleted. The predetermined UL symbol may be, for example, a UL symbol (semi-static UL symbol) that is set quasi-statically by higher layer parameters or the like.

[0082] However, when multi-PDSCH scheduling is performed in a single DCI-based multi-TRP (for example, single DCI-based MTRP PDSCH with tdmschemeA + multi-PDSCH scheduling), how to control each PDSCH repeat transmission becomes an issue. For example, for each repeat transmission, how to determine whether to enable / disable the PDSCH taking into account TDD collision (for example, collision with a UL symbol) becomes an issue. Another issue is how to control HARQ-ACK feedback for the PDSCH.

[0083] Therefore, the present inventors have studied the relationship between each PDSCH and UL symbol when multi-PDSCH scheduling is performed in single DCI-based multi-TRP, and have conceived the present embodiment.

[0084] Each PDSCH may be included in the same symbol (or may be used to transmit the same TB). The UL symbol may be a UL symbol that is set semi-statically (for example, by a higher layer parameter).

[0085] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0086] In the present disclosure, "A / B" may mean "at least one of A and B." Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0087] In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be interchangeable.

[0088] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0089] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), and RRC messages may be interchangeable.

[0090] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0091] In the present disclosure, MAC CE and activation / deactivation command may be read interchangeably.

[0092] In this disclosure, the terms panel, beam, spatial-domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial-domain receive filter, UE spatial-domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS for QCL type D in TCI state / QCL assumption, RS for QCL type A in TCI state / QCL assumption, spatial relationship, spatial-domain transmit filter, UE spatial-domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be interchangeable. In this disclosure, the terms QCL type X-RS, DL-RS associated with QCL type X, DL-RS with QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be interchangeable.

[0093] In the present disclosure, the terms panel, Uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (CORESET), PDSCH, codeword, base station, antenna port of a certain signal (e.g., Demodulation Reference Signal (DMRS) port), antenna port group of a certain signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV), and layer (MIMO layer, transmission layer, spatial layer) may be interchangeable. Also, panel identifier (ID) and panel may be interchangeable. In the present disclosure, the terms TRP ID, TRP related ID, CORESET pool index, the position of one of two TCI states corresponding to one code point in a field in a DCI (ordinal number, first TCI state or second TCI state), and TRP may be read interchangeably.

[0094] In the present disclosure, panel, UE panel, RS port group, DMRS port group, SRS port group, RS resource group, DMRS resource group, SRS resource group, beam group, TCI state group, spatial relationship group, SRS resource indicator (SRI) group, antenna port group, antenna group, and CORESET group may be read as interchangeable.

[0095] The panel may be associated with at least one of a panel ID, a UL TCI state, a UL beam, an L beam, a DL RS resource, and spatial relationship information.

[0096] In the present disclosure, the terms "multi-TRP," "multi-TRP system," "multi-TRP transmission," "multi-PDSCH," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, the terms "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, the terms "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0097] In the present disclosure, the following may be read interchangeably: single TRP, single DCI, single PDCCH, multi-TRP based on single DCI, single TRP system, single TRP transmission, single PDSCH, channel using single TRP, channel using one TCI state / spatial relationship, multi-TRP not being enabled by RRC / DCI, multiple TCI states / spatial relationships not being enabled by RRC / DCI, a CORESET pool index (CORESETPoolIndex) value of 1 not being set for any CORESET and no code point in the TCI field being mapped to two TCI states, and two TCI states on at least one TCI code point being activated.

[0098] In the present disclosure, the terms "switch," "decide," and "select" may be read interchangeably.

[0099] (Wireless communication method) First Embodiment In the first embodiment, when intra-slot multi-TRP PDSCH repetition (e.g., intra-slot M-TRP PDSCH repetition) is applied, a PDSCH scheduled by a DCI for multi-PDSCH scheduling (e.g., multi-PDSCH scheduling DCI) will be described. The DCI may be a single DCI (but is not limited to this).

[0100] In the following description, a multi-TRP of a single DCI in which a predetermined scheme (here, a time multiplexing scheme (e.g., tdmschemeA)) is set as the PDSCH repetition of the multi-TRP in a slot will be described as an example, but this is not limited to this.

[0101] The PDSCH repetition for intra-slot multi-TRP (e.g., intra-slot M-TRP PDSCH repetition) may be configured in the UE by higher layer signaling from the base station. The PDSCH repetition scheme for intra-slot multi-TRP (e.g., tdmschemeA) may be configured by higher layer parameters (e.g., RepSchemeEnabler). This embodiment may also be suitably applied when two TCI states are specified by the "Transmission Configuration Indication" of the DCI field (or when at least one code point is mapped to two TCI states).

[0102] For a PDSCH scheduled by DCI for multi-PDSCH scheduling, at least one of the following options 1-1 to 1-7 (or a combination of two or more options) may be applied / supported.

[0103] [Option 1-1] Any repetition of the scheduled PDSCH may be controlled so as not to overlap with a configured UL symbol. The scheduled repetition of the PDSCH corresponds to repeated transmission (e.g., Rep#1, Rep#2) in the same slot. The configured UL symbol may be interpreted as a semi-static UL symbol, a quasi-static UL symbol, or an UL symbol configured by higher layer parameters.

[0104] The UE may not expect / assume that the scheduled PDSCH repetition overlaps with the configured UL symbol. The base station may control not to schedule the PDSCH repetition transmission for the time domain in which the UL symbol is configured in the higher layer parameters. Alternatively, the base station may control to schedule the PDSCH repetition transmission for a domain different from the time domain in which the UL symbol is configured.

[0105] [Option 1-2] Both repetitions of the scheduled PDSCH may be controlled so as not to overlap with the configured UL symbol. For example, both repetitions of the PDSCH may be both the first repetition (Rep#1) and the second repetition (Rep#2) corresponding to PDSCH#x in the same symbol.

[0106] The UE may not expect / assume that both repetitions of the scheduled PDSCH overlap with the configured UL symbol. The base station may control not to schedule both repetitions of the PDSCH for the time domain in which the UL symbol is configured in the higher layer parameters. Alternatively, the base station may control to schedule both repetitions of the PDSCH for a time domain different from the time domain in which the UL symbol is configured.

[0107] [Options 1-3] A specific repetition of the scheduled PDSCH may be controlled so as not to overlap with the configured UL symbol. The specific repetition may be, for example, the first repetition (Rep#1) or the second repetition (Rep#2) corresponding to PDSCH#x in the same symbol.

[0108] The UE may not expect / assume that a specific repetition (e.g., the first repetition / second repetition) of the scheduled PDSCH overlaps with a configured UL symbol. The base station may control not to schedule a specific repetition transmission of the PDSCH for a time domain in which the UL symbol is configured in the higher layer parameters. Alternatively, the base station may control to schedule a specific repetition transmission of the PDSCH for a time domain different from the time domain in which the UL symbol is configured.

[0109] [Options 1-4] One repetition of the scheduled PDSCH may be controlled to overlap with the configured UL symbol, and the other repetition may be controlled not to overlap with the configured UL symbol.

[0110] The UE may expect / assume that one repetition of the scheduled PDSCH overlaps with the configured UL symbol and the other repetition does not overlap with the configured UL symbol. The base station may control to schedule one repetition of the PDSCH transmission and not schedule the other repetition for the time domain in which the UL symbol is configured in the higher layer parameters.

[0111] For example, the UE may expect / assume that the first repetition (Rep#1) of the PDSCH repetitions overlaps with the configured UL symbol and the second repetition (Rep#2) does not overlap with the configured UL symbol. Alternatively, the UE may expect / assume that the first repetition (Rep#1) of the PDSCH repetitions does not overlap with the configured UL symbol and the second repetition (Rep#2) overlaps with the configured UL symbol.

[0112] [Options 1-5] If any repetition of a scheduled PDSCH overlaps with a configured UL symbol, the scheduled PDSCH may be disabled.

[0113] The UE may determine that a scheduled PDSCH is invalid if any repetition of the scheduled PDSCH overlaps with a configured UL symbol.

[0114] In the present disclosure, an UL symbol and a PDSCH overlap may mean that at least one symbol corresponding to the PDSCH overlaps with the UL symbol, or that a predetermined number (or a predetermined ratio) of symbols corresponding to the PDSCH overlap with the UL symbol.

[0115] [Options 1-6] If a particular repetition (eg, first repetition / second repetition) of a scheduled PDSCH overlaps with a configured UL symbol, the scheduled PDSCH may be invalid.

[0116] The UE may determine that a particular repetition of a scheduled PDSCH is invalid if the particular repetition overlaps with a configured UL symbol.

[0117] [Options 1-7] If both repetitions (eg, both the first and second repetitions) of a scheduled PDSCH overlap with a configured UL symbol, the scheduled PDSCH may be disabled.

[0118] The UE may determine that a scheduled PDSCH is invalid if both repetitions of the scheduled PDSCH overlap with a configured UL symbol, whereas the UE may determine that a scheduled PDSCH is valid if only one repetition of the scheduled PDSCH overlaps with an UL symbol (or if there is a PDSCH repetition that does not overlap with an UL symbol).

[0119] In the first embodiment, at least one of the following variations 1 to 5 may be applied.

[0120] Variation 1 When a semi-static (e.g., type 1) HARQ-ACK codebook / feedback is configured, multi-PDSCH scheduling and single DCI-based multi-TRP slot PDSCH repetition may be controlled not to be configured at the same time.

[0121] For example, when a Type 1 HARQ-ACK codebook / feedback is configured, the UE does not need to assume that conditions 1-1 to 1-3 are satisfied simultaneously. Condition 1-1 may be that multi-PDSCH scheduling is configured for the serving cell / BWP, condition 1-2 may be that TCI codepoints (at least one codepoint) are mapped to two TCI states / QCLs simultaneously in the serving cell / BWP, and condition 1-3 may be that tdmAchemeA is configured.

[0122] Variation 2 If a semi-static (eg, type 1) HARQ-ACK codebook / feedback is configured, any scheduled PDSCH repetitions may be controlled to not overlap with the semi-static UL symbols.

[0123] For example, for joint operation of multi-PDSCH scheduling and PDSCH repetitions within a single DCI-based multi-TRP slot, if Type 1 HARQ-ACK codebook / feedback is configured, the UE may not assume that any scheduled PDSCH repetitions overlap with semi-static UL symbols.

[0124] Variation 3 If a semi-static (eg, type 1) HARQ-ACK codebook / feedback is configured, both scheduled PDSCH repetitions may be controlled to not overlap with the semi-static UL symbol.

[0125] For example, for joint operation of multi-PDSCH scheduling and PDSCH repetitions within a single DCI-based multi-TRP slot, if Type 1 HARQ-ACK codebook / feedback is configured, the UE may not assume that both scheduled PDSCH repetitions overlap with the semi-static UL symbol.

[0126] Variation 4 When a semi-static (e.g., Type 1) HARQ-ACK codebook / feedback is configured, a specific repetition (e.g., first repetition / second repetition) of the scheduled PDSCH may be controlled not to overlap with the semi-static UL symbol.

[0127] For example, for joint operation of multi-PDSCH scheduling and PDSCH repetitions within a single DCI-based multi-TRP slot, if Type 1 HARQ-ACK codebook / feedback is configured, the UE may not assume that a particular repetition of the scheduled PDSCH overlaps with a semi-static UL symbol.

[0128] Variation 5 When a semi-static (e.g., Type 1) HARQ-ACK codebook / feedback is configured, one repetition of the scheduled PDSCH may be controlled to not overlap with the semi-static UL symbol, and the other repetition may be controlled to overlap with the semi-static UL symbol.

[0129] For example, for joint operation of multi-PDSCH scheduling and PDSCH repetitions within a single DCI-based multi-TRP slot, if Type 1 HARQ-ACK codebook / feedback is configured, the UE may assume that one repetition of the scheduled PDSCH does not overlap with a semi-static UL symbol and the other repetition overlaps with a semi-static UL symbol.

[0130] <Second embodiment> In the second embodiment, when intra-slot multi-TRP PDSCH repetition (for example, intra-slot M-TRP PDSCH repetition) is applied, an example of control of HARQ-ACK feedback (or HARQ-ACK codebook generation) for the PDSCH repetition will be described. The second embodiment may be applied in combination with the first embodiment.

[0131] In the following description, a multi-TRP of a single DCI in which a predetermined scheme (here, tdmschemeA) is configured as the PDSCH repetition of the multi-TRP in a slot is taken as an example, but is not limited to this. Also, in the following description, a case in which a semi-statically configured HARQ-ACK codebook (e.g., a type 1 HARQ-ACK codebook) is applied to the HARQ-ACK feedback is taken as an example, but is not limited to this.

[0132] For a PDSCH scheduled by DCI for multi-PDSCH scheduling, at least one of the following options 2-1 to 2-3 may be applied / supported.

[0133] For multiple (e.g., two) PDSCH repetitions in the same slot, the SLIV#x corresponding to the first repetition is indicated by DCI / higher layer signaling, and the SLIV#x' corresponding to the second repetition is the SLIV#x plus a predetermined offset (e.g., K - ) may be determined based on the

[0134] [Option 2-1] The generation of the HARQ-ACK codebook may be controlled based on whether any repetition of the scheduled PDSCH overlaps with a configured UL symbol. For example, option 2-1 may be suitably applied to the case where the scheduled PDSCH is invalid if any repetition of the scheduled PDSCH overlaps with a configured UL symbol (the above option 1-5).

[0135] In this case, time domain resource allocation (TDRA) pruning optimization (eg, TDRA pruning optimization) may be performed.

[0136] As a modification of the TDRA pruning, in the TDRA pruning in each DL slot candidate, an SLIV having a start symbol S and a length L may be removed. For example, if an SLIV having a start symbol S and a length L overlaps with a UL symbol (e.g., a semi-static UL symbol), the SLIV may be removed.

[0137] In the present disclosure, deleting an SLIV may mean that a PDSCH corresponding to the SLIV (e.g., a PDSCH repetition corresponding to the SLIV, or a PDSCH schedule including a PDSCH repetition corresponding to the SLIV) is deleted / ignored in HARQ-ACK codebook generation.

[0138] Assume that SLIV cannot be scheduled for intra-slot M-TRP PDSCH repetition. SLIV cannot be scheduled for intra-slot M-TRP PDSCH repetition, for example, when S+L+offset(K - )+L may be greater than 14. In this case, if an SLIV overlaps with a UL symbol (eg, a semi-static UL symbol), the SLIV may be deleted.

[0139] Assume that SLIV can be scheduled for intra-slot M-TRP PDSCH repetition. For example, SLIV can be scheduled for intra-slot M-TRP PDSCH repetition when S+L+offset(K - )+L is not greater than 14. In this case, the SLIV overlaps with the UL symbol (e.g., a semi-static UL symbol), or S+L+K - From S+L+K - If any symbol up to +L overlaps with the UL symbol, that SLIV may be deleted.

[0140] That is, if at least one of the first and second repetitions is invalid (or overlaps with a UL symbol), the UE controls the HARQ-ACK codebook / feedback not to include (or remove) the HARQ-ACK for the PDSCH in that slot.

[0141] Note that if the SLIV overlaps with a UL symbol (e.g., a semi-static UL symbol), or if S+L+K - From S+L+K - If any symbol from S to S+L overlaps with a UL symbol, it means any symbol from S to S+L or S+L+K. - From S+L+K - This may be interpreted as when any symbol up to +L overlaps with a UL symbol.

[0142] In this way, if SLIV#1 corresponding to the first repetition Rep#1 is valid (e.g., does not overlap with an UL symbol), while SLIV#1' corresponding to the second repetition Rep#2 is invalid (e.g., overlaps with an UL symbol), it may be determined to be invalid (see FIG. 7). In this case, taking into account that the second repetition (SLIV#1') overlaps with an UL symbol, SLIV#1 may be deleted for TDRA pruning.

[0143] [Option 2-2] The generation of the HARQ-ACK codebook may be controlled based on whether a specific repetition of the scheduled PDSCH overlaps with a configured UL symbol. For example, Option 2-2 may be suitably applied to the case where a specific repetition of the scheduled PDSCH overlaps with a configured UL symbol, in which the scheduled PDSCH is invalid (Options 1-6 above).

[0144] For example, if a particular repetition is the first repetition of a scheduled PDSCH, the scheduled PDSCH may be determined to be invalid if the first repetition overlaps with an UL symbol.

[0145] Alternatively, if a particular repetition is the second repetition of a scheduled PDSCH, the scheduled PDSCH may be determined to be invalid if the second repetition overlaps with an UL symbol.

[0146] In this case, time domain resource allocation (TDRA) pruning optimization (eg, TDRA pruning optimization) may be performed.

[0147] As a modification of the TDRA pruning, in the TDRA pruning in each DL slot candidate, an SLIV having a start symbol S and a length L may be removed. For example, if an SLIV having a start symbol S and a length L overlaps with a UL symbol (e.g., a semi-static UL symbol), the SLIV may be removed.

[0148] Assume that SLIV cannot be scheduled for intra-slot M-TRP PDSCH repetition. SLIV cannot be scheduled for intra-slot M-TRP PDSCH repetition, for example, when S+L+offset(K - )+L may be greater than 14. In this case, if an SLIV overlaps with a UL symbol (eg, a semi-static UL symbol), the SLIV may be deleted.

[0149] Assume that SLIV can be scheduled for intra-slot M-TRP PDSCH repetition. For example, SLIV can be scheduled for intra-slot M-TRP PDSCH repetition when S+L+offset(K - )+L is not greater than 14. If the particular iteration is the second iteration, then S+L+K- From S+L+K - If any symbol up to +L overlaps with the UL symbol, that SLIV may be deleted.

[0150] That is, if a particular repetition is invalid (or overlaps with a UL symbol), the UE controls the HARQ-ACK codebook / feedback not to include (or delete) the HARQ-ACK for the PDSCH in that slot.

[0151] If a particular repetition is the second repetition, the SLIV#1 corresponding to the first repetition Rep#1 may be invalid (e.g., overlaps with the UL symbol), while the SLIV#1' corresponding to the second repetition Rep#2 may be valid (e.g., does not overlap with the UL symbol), and may be determined to be valid (see Figure 8).

[0152] In this case, the UE may decide to delete the SLIV (or the scheduled PDSCH) only based on the validity of the second repetition. In Figure 8, considering that the second repetition (SLIV#1') does not overlap with the UL symbol, SLIV#1 (or the PDSCH corresponding to SLIV#1 / SLIV#'1) may not be deleted due to TDRA pruning.

[0153] [Option 2-3] The generation of the HARQ-ACK codebook may be controlled based on whether all (e.g., both) repetitions of the scheduled PDSCH overlap with the configured UL symbol. For example, options 2-3 may be suitably applied to the case where the scheduled PDSCH is disabled if both repetitions of the scheduled PDSCH overlap with the configured UL symbol (options 1-7 above).

[0154] In this case, time domain resource allocation (TDRA) pruning optimization (eg, TDRA pruning optimization) may be performed.

[0155] As a modification of the TDRA pruning, in the TDRA pruning in each DL slot candidate, an SLIV having a start symbol S and a length L may be removed. For example, if an SLIV having a start symbol S and a length L overlaps with a UL symbol (e.g., a semi-static UL symbol), the SLIV may be removed.

[0156] Assume that SLIV cannot be scheduled for intra-slot M-TRP PDSCH repetition. SLIV cannot be scheduled for intra-slot M-TRP PDSCH repetition, for example, when S+L+offset(K - )+L may be greater than 14. In this case, if an SLIV overlaps with a UL symbol (eg, a semi-static UL symbol), the SLIV may be deleted.

[0157] Assume that SLIV can be scheduled for intra-slot M-TRP PDSCH repetition. For example, SLIV can be scheduled for intra-slot M-TRP PDSCH repetition when S+L+offset(K - )+L is not greater than 14. In this case, the SLIV overlaps with the UL symbol (e.g., a semi-static UL symbol) and S+L+K - From S+L+K - If any symbol up to +L overlaps with the UL symbol, that SLIV may be deleted.

[0158] That is, if both the first and second repetitions are invalid (or overlap with an UL symbol), the UE controls the HARQ-ACK codebook / feedback not to include (or remove) the HARQ-ACK for the PDSCH in that slot.

[0159] Note that if the SLIV overlaps with the UL symbol (e.g., a semi-static UL symbol) and S+L+K - From S+L+K - If any symbol from S to S+L overlaps with a UL symbol, then any symbol from S to S+L and S+L+K - From S+L+K - This may be interpreted as when any symbol up to +L overlaps with a UL symbol.

[0160] In this way, if either SLIV#1 corresponding to the first repetition Rep#1 or SLIV#1' corresponding to the second repetition Rep#2 is valid (e.g., does not overlap with a UL symbol), it may be determined to be valid (see Figures 9A-9C).

[0161] If SLIV#1 corresponding to the first repetition Rep#1 is valid (e.g., does not overlap with an UL symbol) and SLIV#1' corresponding to the second repetition Rep#2 is invalid (e.g., overlaps with an UL symbol), it may be determined to be valid (see FIG. 9A). In this case, SLIV#1 (or PDSCH corresponding to SLIV#1 / SLIV#'1) may not be deleted due to TDRA pruning.

[0162] Also, if SLIV#1 corresponding to the first repetition Rep#1 is invalid (e.g., overlaps with an UL symbol) and SLIV#1' corresponding to the second repetition Rep#2 is valid (e.g., does not overlap with an UL symbol), it may be determined to be valid (see FIG. 9B). A configuration may be adopted in which SLIV#1 (or PDSCH corresponding to SLIV#1 / SLIV#'1) is not deleted due to TDRA pruning.

[0163] Also, if SLIV#1 corresponding to the first repetition Rep#1 is invalid (for example, overlaps with an UL symbol) and SLIV#1' corresponding to the second repetition Rep#2 is also invalid (for example, overlaps with an UL symbol), it may be determined to be invalid (see FIG. 9C). SLIV#1 (or PDSCH corresponding to SLIV#1 / SLIV#'1) may be configured to be deleted for TDRA pruning.

[0164] <Variations> If the scheduled PDSCH is determined to be invalid, the rules defined for multi-PDSCH scheduling for a single TRP may be applied, e.g., HPN may be skipped, and a NACK may be reported for dynamic (e.g., Type 2) HARQ-ACK codebook / feedback.

[0165] DCI for multi-PDSCH scheduling (for example, multi-PDSCH scheduling DCI) may be in a DCI format of a DL grant in which a TDRA table including a plurality of SLIVs in at least one row is set.

[0166] (UE capability information) In the above-described embodiments (for example, the first embodiment and the second embodiment), the following UE capabilities may be set. Note that the following UE capabilities may be interpreted as parameters (for example, higher layer parameters) set in the UE from the network (for example, the base station).

[0167] UE capability information regarding whether the UE supports joint operation of intra-slot PDSCH repetition and multi-PDSCH scheduling for single DCI multi-TRP may be defined.

[0168] UE capability information may be defined regarding whether the UE supports determining whether PDSCH is enabled / disabled based on the first / second repetition for joint operation of PDSCH repetition within a slot of single DCI multi-TRP and multi-PDSCH scheduling.

[0169] UE capability information may be defined regarding whether the UE supports determining whether PDSCH is enabled / disabled based on both repetitions for joint operation of PDSCH repetition within a slot of single DCI multi-TRP and multi-PDSCH scheduling.

[0170] When Type 1 HARQ-ACK codebook / feedback is configured, UE capability information regarding whether the UE supports joint operation of intra-slot PDSCH repetition and multi-PDSCH scheduling for single DCI multi-TRP may be defined.

[0171] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0172] 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0173] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0174] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0175] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0176] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0177] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0178] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

[0179] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

[0180] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0181] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0182] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0183] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0184] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0185] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0186] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0187] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

[0188] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0189] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0190] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0191] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0192] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0193] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0194] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0195] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[0196] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0197] (base station) 11 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0198] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0199] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0200] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0201] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0202] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0203] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0204] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0205] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0206] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0207] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0208] The transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .

[0209] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna .

[0210] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0211] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0212] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0213] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0214] The transmitting / receiving unit 120 may transmit information regarding the transmission direction of the symbols included in the slot.

[0215] When multiple repeat transmissions of a downlink shared channel to which a Time Division Multiplexing (TDM) scheme is applied within a slot are configured, the control unit 110 may control the multiple repeat transmissions so that at least one of the multiple repeat transmissions does not overlap with a UL symbol.

[0216] (user terminal) 12 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0217] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0218] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0219] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.

[0220] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0221] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0222] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0223] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0224] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0225] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0226] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0227] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

[0228] The transmitting / receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna 230.

[0229] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0230] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0231] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0232] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0233] The transceiver 220 may receive information regarding the transmission direction of the symbols included in the slot.

[0234] When multiple repeated transmissions of a downlink shared channel to which a Time Division Multiplexing (TDM) scheme is applied are configured within a slot, the control unit 210 may assume (or may control the generation of the HARQ-ACK codebook based on) that at least one of the multiple repeated transmissions does not overlap with a UL symbol.

[0235] The control unit 210 may determine that the downlink shared channel scheduled in the slot is invalid if a predetermined repeated transmission among the multiple repeated transmissions overlaps with a UL symbol.

[0236] When feedback of an acknowledgement signal for a downlink shared channel is performed using a semi-static acknowledgement signal codebook, the control unit 210 may control generation of the acknowledgement signal codebook by taking into account an offset between multiple repeated transmissions (e.g., a start offset corresponding to the second repetition).

[0237] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. 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 a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0238] Here, the 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, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0239] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 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, etc.

[0240] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0241] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0242] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0243] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0244] 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-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0245] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0246] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

[0247] 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, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0248] 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, a light emitting diode (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).

[0249] Furthermore, 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 between each device.

[0250] Furthermore, the base station 10 and the user terminal 20 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 using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0251] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0252] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may 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.

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

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

[0255] A slot may include multiple minislots. Each minislot may consist of one or multiple 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 (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0256] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0257] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.

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

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

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

[0261] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP 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.

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

[0263] A resource block (RB) is a resource allocation unit in the time domain and the 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.

[0264] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

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

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

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

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

[0270] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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, etc. may be changed in various ways.

[0271] 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 a predetermined index.

[0272] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (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.

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

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

[0275] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0276] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0277] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0278] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

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

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

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

[0282] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0283] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

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

[0285] A base station can accommodate one or more (e.g., three) cells. 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 service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

[0287] A mobile station may also be referred to 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.

[0288] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0289] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0290] 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). Note that 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.

[0291] 14 is a diagram showing an example of a vehicle according to an embodiment. Vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0292] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0293] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0294] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0295] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0296] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0297] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0298] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0299] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 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 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the above-mentioned base station 10 or user terminal 20. Furthermore, the communication module 60 may be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (or may function as at least one of the base station 10 and user terminal 20).

[0300] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0301] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0302] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

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

[0304] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0305] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0306] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0307] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

[0309] 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 or that the first element must in some way precede the second element.

[0310] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0311] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0312] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0313] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[0314] As used in this disclosure, 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."

[0315] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

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

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

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

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

[0320] This application is based on Japanese Patent Application No. 2022-025284, filed February 22, 2022, the contents of which are incorporated herein in their entirety.

Claims

1. a receiving unit that receives information regarding the transmission direction of symbols included in a slot; a control unit that determines that the downlink shared channel scheduled in the slot is invalid when multiple repeated transmissions of a downlink shared channel to which a Time Division Multiplexing (TDM) scheme is applied are configured in the slot and at least one of the multiple repeated transmissions overlaps with an uplink symbol; The control unit controls generation of the acknowledgement signal codebook in consideration of an offset between the multiple repeated transmissions when feedback of an acknowledgement signal for the downlink shared channel is performed using a semi-static acknowledgement signal codebook.

2. receiving information regarding the direction of transmission of symbols contained in the slot; determining that the downlink shared channel scheduled in the slot is invalid when multiple repeated transmissions of the downlink shared channel to which a time division multiplexing (TDM) scheme is applied are configured in the slot and at least one of the multiple repeated transmissions overlaps with an uplink symbol; and when feedback of an acknowledgement signal for the downlink shared channel is performed using a semi-static acknowledgement signal codebook, controlling generation of the acknowledgement signal codebook in consideration of an offset between the multiple repeated transmissions.

3. a transmitter that transmits information regarding the transmission direction of symbols included in a slot; a control unit that configures multiple repeated transmissions of a downlink shared channel to which a time division multiplexing (TDM) scheme is applied within the slot, and determines that the downlink shared channel scheduled in the slot is invalid when at least one of the multiple repeated transmissions overlaps with an uplink symbol; a receiving unit that receives an acknowledgement signal for the downlink shared channel that is fed back by a terminal using a semi-static acknowledgement signal codebook that is generated in consideration of an offset between the multiple repeated transmissions.

4. A system having a terminal and a base station, the terminal includes a receiving unit that receives information about a transmission direction of a symbol included in a slot; a control unit that determines that the downlink shared channel scheduled in the slot is invalid when multiple repeated transmissions of a downlink shared channel to which a Time Division Multiplexing (TDM) scheme is applied are configured in the slot and at least one of the multiple repeated transmissions overlaps with an uplink symbol; when feedback of an acknowledgement signal for the downlink shared channel is performed using a semi-static acknowledgement signal codebook, the control unit controls generation of the acknowledgement signal codebook in consideration of an offset between the plurality of repeated transmissions; The base station includes a transmitter that transmits the information; a control unit that configures the plurality of repeated transmissions within the slot, and determines that the downlink shared channel is invalid when at least one of the plurality of repeated transmissions overlaps with the uplink symbol; a receiving unit that receives the acknowledgement signal fed back by the terminal using the semi-static acknowledgement signal codebook.

Images