Terminal, wireless communication method, and base station

Abstract

One embodiment of the terminal disclosed herein comprises: a receiving unit for receiving a plurality of downlink control information respectively transmitted using a plurality of downlink control channels allocated in different time domains; and a control unit for controlling at least one of the reception and transmission of a physical shared channel scheduled by the plurality of downlink control information. When supporting a situation in which the contents of the timing association information respectively included in the plurality of downlink control information are different, the control unit uses the downlink control channel corresponding to each downlink control information as a time reference, and determines at least one of the reception timing and the transmission timing of the physical shared channel based on the timing association information included in each downlink control information.

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized to achieve even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) has been standardized to achieve even higher capacity and higher sophistication than LTE (Third Generation Partnership Project (3GPP) Releases (Rel.) 8 and 9).

[0003] Subsequent systems of LTE (for example, also known as the fifth generation mobile communication system (5G), 5G+ (plus), the sixth generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also discussed.

[0004] Prior art literature

[0005] Non-patent literature

[0006] 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

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (e.g., NR), one or more transmission / reception points (Transmission / Reception Point (TRP)) (multi-TRP) are being discussed to use one or more planes (multi-planes) to perform DL transmission (e.g., PDSCH transmission) to the terminal (user terminal, User Equipment (UE)).

[0009] In addition, in NR, it is envisioned that repetitive transmission is applied to specific channels (e.g., PDCCH). For example, it is considered to control the scheduling of DL transmission / UL transmission using multiple PDCCHs to which repetitive transmission is applied from multiple planes / TRP.

[0010] However, in the NR specifications to date, how to control repeated transmissions from more than one TRP has not been fully discussed.

[0011] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can properly communicate even when repeated transmission is applied to a DL channel sent from more than one TRP.

[0012] Means for solving problems

[0013] A terminal involved in one embodiment of the present invention is characterized in that it comprises: a receiving unit for receiving a plurality of downlink control information respectively transmitted using a plurality of downlink control channels allocated in different time domains; and a control unit for controlling at least one of reception and transmission of a physical shared channel scheduled by the plurality of downlink control information, and when supporting a situation in which the contents of the timing association information respectively included in the plurality of downlink control information are different, the control unit uses the downlink control channel corresponding to each downlink control information as a time reference, and determines at least one of the reception timing and transmission timing of the physical shared channel based on the timing association information included in each downlink control information.

[0014] Effects of the Invention

[0015] According to one embodiment of the present disclosure, communication can be performed appropriately even when repeated transmission is applied to a DL channel sent from more than one TRP. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 This is a diagram showing an example of scheduling control of a physical shared channel based on PDCCH / DCI.

[0017] Figures 2A to 2D This is a diagram showing an example of a multi-TRP scenario.

[0018] Figure 3This is a diagram showing an example of repeated PDCCH transmission.

[0019] Figure 4 This is a diagram showing an example of PDCCH repetitive transmission control in the second example.

[0020] Figure 5A as well as Figure 5B This is a diagram showing another example of PDCCH repetitive transmission control in the second example.

[0021] Figure 6A as well as Figure 6B This is a diagram showing another example of PDCCH repetitive transmission control in the second example.

[0022] Figure 7A as well as Figure 7B This is a diagram showing another example of PDCCH repetitive transmission control in the second example.

[0023] Figure 8 This is a diagram showing an example of PDCCH repetitive transmission control in the third example.

[0024] Figure 9 This is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.

[0025] Figure 10 This is a diagram showing an example of the configuration of a base station according to one embodiment.

[0026] Figure 11 This is a diagram showing an example of the configuration of a user terminal according to one embodiment.

[0027] Figure 12 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment. DETAILED DESCRIPTION

[0028] <Allocation of Time Domain Resources>

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

[0030] The information related to time domain resources may also include at least one of the following: for example, information indicating the offset between the DCI and the physical shared channel (e.g., time slot offset K0), information indicating the start codeword (e.g., start codeword S), and information indicating the length of the physical shared channel (e.g., length L).

[0031] Each bit of information (or code point) notified via the TDRA field is associated with a different time domain resource allocation candidate (or entry). For example, a table (e.g., a TDRA table) can be defined that associates each bit of information with a time domain resource allocation candidate (K0, S, L). The time domain resource allocation candidates can be pre-defined in the specification or notified / set to the UE via higher layer signaling.

[0032] [PDSCH]

[0033] The UE may also determine a row index (entry number or entry index) in a specific table based on the value of the TDRA field in the DCI (e.g., DCI format 1_0 / 1_1 / 1_2). The specific table may also include 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, a start symbol S of the PDSCH, and at least one of a duration L. The combination of the start symbol S of the PDSCH and the duration L may also be referred to as a Start and Length Indicator (SLIV).

[0034] The UE may also determine the time domain resource for which the PDSCH is scheduled based on the value of a specific field included in the DCI and at least one of the slot offset K0 information, mapping type, start symbol S, symbol length L, and SLIV specified in the table (see Figure 1 ). In addition, the reference points of the starting codeword S and the codeword length L can also be controlled based on the starting position (first codeword) of the time slot. In addition, the starting codeword S, the codeword length L, etc. can also be defined according to the mapping type of the PDSCH.

[0035] like Figure 1 As shown in FIG, the UE uses the DCI (or the PDCCH used in the transmission of the DCI) as the time domain reference point to determine the time slot to which the PDSCH is scheduled. For example, when receiving the DCI for scheduling the PDSCH in time slot #n, the UE can also determine the time slot to which the PDSCH is scheduled based on the number n of the time slot and the subcarrier spacing μ for the PDSCH. PDSCH , the subcarrier spacing μ used by PDCCH PDCCHAt least one of the time offset K0 and the above-mentioned time offset K0 determines the time slot for receiving the PDSCH (allocated to the PDSCH). Here, the case where the time slot offset K0=1 and the subcarrier spacing of the PDSCH and the PDCCH is the same is shown.

[0036] Furthermore, the UE determines the allocation of the PDSCH based on the resource allocation information (eg, SLIV) specified by the TDRA field, using the starting point of the slot to which the PDSCH is allocated as a reference.

[0037] [PUSCH]

[0038] The UE may also determine a row index (entry number or entry index) in a specific table based on the value of the TDRA field in the DCI (e.g., DCI format 0_0 / 0_1 / 0_2). The specific table may also include at least one of the following: 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 for the PUSCH, and a starting symbol and duration L of the PUSCH. The combination of the starting symbol S and duration L of the PUSCH may also be referred to as a Start and Length Indicator (SLIV).

[0039] The UE may also determine the time domain resource for which the PUSCH is scheduled based on the value of a specific field included in the DCI, the slot offset K2 information specified in the table, the mapping type, the starting symbol S, the symbol length L, and at least one of the SLIVs (see Figure 1 ). In addition, the reference point of the starting codeword S and the codeword length L can be controlled based on the starting position (first codeword) of the time slot. In addition, the starting codeword S, codeword length L, etc. can also be defined according to the mapping type of PDSCH.

[0040] like Figure 1 As shown in FIG, the UE uses the DCI (or the PDCCH used in the transmission of the DCI) as a reference point in the time domain to determine the time slot in which the PUSCH is scheduled. For example, when receiving the DCI for scheduling the PUSCH in time slot #n+4, the UE may also determine the time slot in which the PUSCH is scheduled based on the number of the time slot n+4 and at least one of the following: the subcarrier spacing μ for the PUSCH. PDSCH , PUCCH subcarrier spacing μ PDCCH At least one of the time offset K2 and the above-mentioned time offset K2 determines the time slot for transmitting the PUSCH (allocated to the PUSCH). Here, the case where the time slot offset K2 = 3 and the subcarrier spacing of the PDSCH and the PDCCH is the same is shown.

[0041] Furthermore, the UE determines the allocation of the PUSCH based on the starting point of the time slot to which the PUSCH is allocated, with respect to the resource allocation information (eg, SLIV) specified by the TDRA field.

[0042] (Multiple TRP)

[0043] In NR, one or more transmission / reception points (Transmission / Reception Point (TRP)) (multi-TRP) are being discussed to use one or more planes (multi-planes) to perform DL transmission to the UE. In addition, the UE is being discussed to perform UL transmission to one or more TRPs.

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

[0045] Figure 2A-2D The following are diagrams showing an example of a multi-TRP scenario. In these examples, it is assumed that each TRP can transmit four different beams, but this is not limited to this.

[0046] Figure 2A This example shows a situation where only one TRP (TRP1 in this example) among multiple TRPs transmits to the UE (also referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0047] Figure 2B This example shows a situation where only one TRP (TRP1 in this example) among multiple TRPs sends a control signal to the UE, and the multiple TRPs send data signals (also called single master mode). The UE receives each PDSCH sent from the multiple TRPs based on a single downlink control information (downlink control information (DCI)).

[0048] Figure 2C This example shows a scenario where each of multiple TRPs transmits a portion of a control signal to the UE, and the multiple TRPs transmit data signals (also known as 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 also depend on part 1. Based on these parts of the DCI, the UE receives each PDSCH transmitted from the multiple TRPs.

[0049] Figure 2DIndicates a situation where each of multiple TRPs sends its own control signal to the UE, and the multiple TRPs send data signals (also known as multi-master mode). A first control signal (DCI) can also be sent in TRP1, and a second control signal (DCI) can be sent in TRP2. Based on these DCIs, the UE receives each PDSCH sent from the multiple TRPs.

[0050] exist Figure 2B In the case where a single DCI is used to schedule multiple PDSCHs from multiple TRPs (also referred to as multiple PDSCHs), the DCI may also be referred to as a single DCI (S-DCI, single PDCCH). Figure 2D When multiple DCIs are used to schedule multiple PDSCHs from multiple TRPs, these multiple DCIs can also be called multi-DCI (M-DCI, multiple PDCCH).

[0051] From each TRP of the multi-TRP, different code words (Code Words (CW)) and different layers can be transmitted. As a method of multi-TRP transmission, non-coherent joint transmission (NCJT) is being discussed.

[0052] In NCJT, for example, TRP1 performs modulation mapping and layer mapping on a first codeword to transmit a first PDSCH using a first precoding for a first number of layers (e.g., 2 layers). Furthermore, TRP2 performs modulation mapping and layer mapping on a second codeword to transmit a second PDSCH using a second precoding for a second number of layers (e.g., 2 layers).

[0053] In addition, multiple PDSCHs (multi-PDSCHs) subjected to NCJT can also be defined as partially overlapping or fully overlapping in at least one of the time domain and the frequency domain. That is, the first PDSCH from the first TRP and the second PDSCH from the second TRP overlap in at least one of the time resources and the frequency resources.

[0054] It can also be assumed that these first PDSCHs and second PDSCHs are not quasi-co-located. Reception of multiple PDSCHs can also be interpreted as simultaneous reception of PDSCHs of a non-certain QCL type (eg, QCL type D).

[0055] In URLLC for multiple TRPs, support for PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is discussed. Support for repetition across multiple TRPs in the frequency domain, layer (space) domain, or time domain is discussed (URLLC schemes, for example, schemes 1, 2a, 2b, 3, and 4). In scheme 1, multiple PDSCHs from multiple TRPs are space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexing (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RV can be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexing (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are sent in one time slot. In scheme 4, multiple PDSCHs from multiple TRPs are sent in different time slots.

[0056] Based on such a multi-TRP scenario, more flexible transmission control can be achieved by utilizing channels with good quality.

[0057] NCJT with multiple TRPs / planes may be able to take advantage of high rank. In order to support ideal and non-ideal backhaul between multiple TRPs, a single DCI (single PDCCH, e.g. Figure 2B ) and multiple DCI (multiple PDCCH, e.g. Figure 2D ) For both single DCI and multi-DCI, the maximum number of TRPs can also be 2.

[0058] For single PDCCH designs (primarily for backhaul), TCI extensions are under discussion. Each TCI code point in the DCI can also correspond to one or two TCI states. The TCI field size can also be the same as the TCI field size in Rel.15.

[0059] However, after Rel.17, it is also envisaged to apply repeated transmission (PDCCH repetition) to PDCCH (or DCI) sent from more than one TRP. For example, it is considered to use multiple PDCCH (or DCI) sent from more than one TRP to schedule more than one signal / channel or send and receive instructions.

[0060] PDCCH / DCI to which repetitive transmission is applied may also be referred to as multi-PDCCH / multi-DCI. Repetitive transmission of PDCCH may also be interpreted as PDCCH repetition, multiple transmission of PDCCHs, multi-PDCCH transmission, or multiple PDCCH transmission.

[0061] Multiple PDCCHs / multiple DCIs can also be sent from different TRPs. The multiple PDCCHs / DCIs can be multiplexed using time division multiplexing (TDM), frequency division multiplexing (FDM), or space division multiplexing (SDM). For example, when PDCCH repetition is performed using time division multiplexing (TDM PDCCH repetition), PDCCHs sent from different TRPs are allocated to different time domains.

[0062] Consider the case where multiple PDCCH / DCI are used to schedule more than one physical shared channel. For example, the more than one physical shared channel can be the same (or one) physical shared channel, or multiple physical shared channels scheduled in the same time domain. In this case, the question arises how to control scheduling (e.g., the content of each DCI notification, the reference point for scheduling, etc.).

[0063] For example, when the content of DCI sent through PDCCHs in different time domains (e.g., DCI payload) is the same, how the UE applies / interprets the indication of the time relationship of each PDCCH / DCI (e.g., the same value) to control scheduling becomes a problem.

[0064] Alternatively, when the content of DCI (e.g., DCI payload) supported / allowed to be sent via PDCCHs in different time domains is set to be different, how the UE applies / interprets the indication of the time relationship of each PDCCH / DCI (e.g., different values) to control scheduling becomes a problem.

[0065] Figure 3 This figure shows an example of a situation where the PDCCH is repeatedly transmitted (or configured) in time slots #n to #n+1. The PDCCH (or control resource set) configured in each time slot can be configured in the entire time domain (e.g., all code elements) of the time slot, or in a portion of the time domain (e.g., a portion of consecutive or non-consecutive code elements).

[0066] In this case, the scheduling of the physical shared channel can also be controlled based on the timing-related information (e.g., time domain resource allocation information) contained in each PDCCH transmitted in different time domains (here, different time slots). The PDCCHs transmitted in different time domains can also be configured to schedule the same transport block (or the physical shared channel that transmits the same transport block).

[0067] However, when scheduling is performed using multiple PDCCHs / DCIs, how to control the configuration of timing-related information (eg, time domain resource allocation information) included in each PDCCH / DCI or how to interpret it in the UE becomes a problem.

[0068] The inventors of the present invention discussed how to configure time-related information included in each PDCCH / DCI or interpret the time-related information in a UE when scheduling is performed using multiple PDCCHs / DCIs, and arrived at the present embodiment.

[0069] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, each of the following aspects may be applied independently or in combination of at least two.

[0070] In addition, in the present disclosure, “A / B” can also be interpreted as at least one of A and B, and “A / B / C” can also be interpreted as at least one of A, B, and C.

[0071] (First Method)

[0072] In the first embodiment, notification / setting of information related to repeated transmission of the PDCCH will be described.

[0073] The information related to PDCCH repetition may be a transmission condition / transmission parameter applied to the PDCCH repetition. The transmission condition / transmission parameter applied to the PDCCH repetition may also be at least one of the number of PDCCH repetitions (e.g., the PDCCH repetition number), the time interval during which the PDCCH repetition is applied, and the interval / offset between each PDCCH in the PDCCH repetition.

[0074] A PDCCH to which repeated transmission is applied (e.g., multiple PDCCHs) can be sent separately from multiple TRPs. Multiple PDCCHs (or, PDCCHs sent from different TRPs) can also be applied with different QCLs (or, TCIs, beams). In the present disclosure, repeated transmission of PDCCHs can be applied in situations where transmission is from one or more TRPs.

[0075] Information related to PDCCH repetition (eg, the number of PDCCH repetitions) may also be notified / configured to the UE from the network (eg, base station). Information related to PDCCH repetition is notified / configured to the UE based on at least one of the following options 1-1 to 1-2.

[0076] <Option 1-1>

[0077] Information related to repeated PDCCH transmission may be notified / configured from the base station to the UE using higher layer signaling (eg, at least one of RRC parameters and MAC CE).

[0078] <Options 1-2>

[0079] Information on PDCCH repetition can also be notified from the base station to the UE in real time using downlink control information (eg, DCI). Information on PDCCH repetition can also be notified using a new field configured in DCI or a field configured in the existing system.

[0080] Information related to PDCCH repetition transmission may also be included in each PDCCH / DCI to which repetition transmission is applied. In this case, the number of PDCCH repetitions included in each PDCCH / DCI may be the same. Alternatively, the number of PDCCH repetitions included in each PDCCH / DCI may be set to a different value (e.g., the remaining number of repetitions).

[0081] The size of the field used to notify information related to repetitive transmission (eg, the number of bits) may be determined based on the maximum number of PDCCH repetitions. The UE may also determine the maximum number of PDCCH repetitions based on capability information reported by the UE (eg, UE capability).

[0082] Alternatively, the maximum number of PDCCH repetitions may be notified / set from the base station to the UE via higher-layer signaling. In this case, the base station may notify the UE of the actual number of PDCCH repetitions using DCI. The size (or number of bits) of the field used to notify the number of PDCCH repetitions may also be determined based on the maximum number of PDCCH repetitions notified / set via higher-layer signaling.

[0083] Whether to apply notification of the number of PDCCH repetitions to DCI using specific higher-layer signaling may also be configured. The UE may assume that a field for notifying the number of PDCCH repetitions is present in the DCI when specific higher-layer signaling is configured, and assume that a field for notifying the number of PDCCH repetitions is not present in the DCI when specific higher-layer signaling is not configured.

[0084] In this way, when PDCCH repetitive transmission is applied, by notifying / setting information related to PDCCH repetitive transmission from the base station to the UE, the UE can appropriately understand the transmission conditions / transmission parameters applied to PDCCH repetitive transmission.

[0085] (Second Method)

[0086] The second approach describes a scenario where the same DCI payload content is transmitted via PDCCH repetitions (TDMPDCCH repetitions) sent in different time domains. This is equivalent to notifying the UE of the same DCI payload content via multiple PDCCHs.

[0087] The same payload content may mean that the values of all fields included in each DCI are set to the same, or the values of some specific fields among the fields included in each DCI are set to the same.

[0088] The specific field may also be a notification field for time-related information. The time-related information may also be interpreted as timing-related information, time-related indication, or timing-related indication (e.g., timing-related indication). For example, the specific field may also be at least one of a time domain resource assignment field (e.g., a time domain resource assignment field) and a HARQ-ACK feedback timing indication field (e.g., a PDSCH-to-HARQ feedback timing indicator field).

[0089] When a specific physical shared channel is scheduled through multiple DCIs, and the multiple DCIs are sent separately through PDCCHs allocated to different time domains, and the content of the multiple DCIs (e.g., payload content) is the same, the UE can also interpret / apply the time association information (e.g., timing association information) contained in the DCI based on a specific time reference.

[0090] Time reference can also be interpreted as timing reference, reference timing, reference point, time reference point, reference in the time domain, or reference point in the time domain.

[0091] The specific time reference may be a specific PDCCH (or the transmission timing of a specific PDCCH) among multiple PDCCHs that are repeatedly transmitted. For example, it may be the first PDCCH transmitted (or received), or the first PDCCH allocated in the time domain. The UE may use the first symbol of the first transmitted PDCCH as the time reference, or the last symbol of the PDCCH as the time reference.

[0092] For example, the UE may also determine the time domain resources of the signal / channel (e.g., physical shared channel) scheduled by each DCI based on a specific time reference and a notification field of time association information contained in each DCI (or at least one DCI).

[0093] For example, it is assumed that the slot offset K0 specified by each DCI is the same value (for example, K0=2) (see Figure 4 ). The UE determines that the PDSCH is scheduled in a time slot (here #n+2) that is K0 away from a specific time reference (here, the transmission timing of the initially transmitted PDCCH#1 or DCI#1 (for example, time slot #n)).

[0094] exist Figure 4 The case of scheduling PDSCH using multiple PDCCHs / multiple DCIs is shown in the figure, but the present invention is not limited to this. When scheduling PUSCH using multiple PDCCHs / multiple DCIs, the UE determines that the PUSCH is scheduled in a time slot that is K2 away from a specific time reference (here, the transmission timing (e.g., time slot #n) of the initially transmitted PDCCH#1 or DCI#1). Alternatively, the same applies to operations that use PDCCH / DCI as a reference to determine the time domain (e.g., transmission timing / reception timing).

[0095] Figure 4 , multiple PDCCHs / multiple DCIs are allocated to different time slots (inter-slot PDCCH repetition), but the present invention is not limited thereto. Multiple PDCCHs / multiple DCIs may also be allocated to the same time slot (e.g., different subslots / minislots / symbols within the same time slot).

[0096] Figure 5AThis figure shows the case where multiple PDCCHs / multiple DCIs are allocated within the same time slot (intra-slot PDCCH repetition). Here, PDCCH #1 and PDCCH #2 are allocated to different symbols in time slot #n, and the slot offset K0 value indicated by DCI #1 transmitted on PDCCH #1 and DCI #2 transmitted on PDCCH #2 are the same (here, 2).

[0097] The UE may also interpret / apply the time-related information included in each DCI using a specific PDCCH (here, PDCCH#1) among multiple PDCCHs as a time reference.

[0098] Figure 5B This figure shows the case where multiple PDCCHs / multiple DCIs are allocated within the same mini-slot (intra-mini-slot PDCCH repetition). A mini-slot can be a time interval consisting of specific symbols (e.g., 2, 3, or 7 symbols). A mini-slot can also be interpreted as a sub-slot. Alternatively, a mini-slot can be set to a time unit shorter than a sub-slot.

[0099] Here, the following situation is shown: that is, different codewords (for example, adjacent codewords) contained in time slot #n are allocated to PDCCH#1 and PDCCH#2, and the time slot offset K0 value indicated by DCI#1 sent in PDCCH#1 and DCI#2 sent in PDCCH#2 is the same (here 2).

[0100] The UE may also interpret / apply the time-related information included in each DCI using a specific PDCCH (here, PDCCH#1) among multiple PDCCHs as a time reference.

[0101] Here, the case where the first transmitted PDCCH is used as the time reference is shown, but this is not limited to this. Another PDCCH (for example, the last transmitted PDCCH or the last configured PDCCH in the time domain) can be used as the time reference. In this case, the UE can also interpret / apply time-related information based on the last transmitted PDCCH.

[0102] Alternatively, the specific PDCCH / DCI serving as the time reference may be determined based on a specific parameter corresponding to each PDCCH (or the CORESET of each PDCCH). The specific parameter may be at least one of a TRP index, a CORESET pool index, and a TCI state ID.

[0103] For example, the specific PDCCH / DCI may be the PDCCH / DCI corresponding to the minimum / maximum TRP index (or CORESET pool index) in the repeatedly transmitted PDCCCH (eg, multiple PDCCH / multiple DCI).

[0104] Alternatively, the specific PDCCH / DCI may be the PDCCH / DCI corresponding to the minimum / maximum TCI state ID in the repeatedly transmitted PDCCCH (e.g., multi-PDCCH / multi-DCI). The TCI state corresponding to the PDCCH / DCI may also be the TCI state corresponding to the CORESET used in transmitting the PDCCH / DCI. In addition, when the CORESET pool index is set, the CORESET corresponding to the CORESET pool index with the minimum / maximum index may also be selected.

[0105] A specific transmission parameter (or one or more specific transmission parameters) may be associated and configured between multiple PDCCHs (or multiple DCIs) to which repeated transmission is applied. The specific transmission parameter may be at least one of a control channel element (CCE), a resource element group (REG), a search space, a search space set, and a CORESET.

[0106] For example, specific transmission parameters may be associated with the PDCCH that serves as the time reference (e.g., the first PDCCH transmitted in repeated transmission) and other PDCCHs. As an example, specific transmission parameters may be associated with the transmission parameters of multiple PDCCHs to which repeated transmission is applied, based on the repetition order (or associated with the transmission order). The UE can determine the transmission order of each PDCCH (e.g., the first PDCCH transmitted) based on information related to PDCCH repetition (e.g., the number of repetitions, the repetition period, etc.) and the transmission parameters corresponding to each PDCCH.

[0107] In this way, the UE is set to be able to identify / grasp the PDCCH that serves as the time reference based on other PDCCHs. Even if the UE detects the wrong PDCCH that serves as the time reference, it can properly interpret / apply the time-related information (for example, the same value) contained in each DCI to perform transmission and reception.

[0108] When scheduling DL / UL transmissions using repeated PDCCH transmissions, the transmission timing of each PDCCH may be restricted. For example, the transmission timing of each PDCCH may be controlled based on at least one of options 2-1 and 2-2.

[0109] <Option 2-1>

[0110] The repetition of PDCCHs allocated in different time domains (e.g., TDM PDCCH repetition) can also be set to not support inter-slot PDCCH repetition (see Figure 6A In other words, it can also be set to support at least one of intra-slot PDCCH repetition and intra-mini-slot PDCCH repetition (refer to Figure 6B ) structure.

[0111] Furthermore, a scenario is considered where a UE incorrectly detects the PDCCH serving as the time reference (e.g., the first transmitted PDCCH), mistakenly identifies another PDCCH as the time reference, and interprets / applies the time-related information contained in each DCI. If repeated PDCCH transmission is used within the same time slot, even if the UE incorrectly detects the PDCCH serving as the time reference and identifies another PDCCH as the time reference, the same time slot will be set as the time reference.

[0112] Therefore, even when the UE erroneously detects the PDCCH serving as a time reference, it is possible to appropriately determine the time domain resources of the physical shared channel whose scheduling is controlled based on the slot level offset.

[0113] <Option 2-2>

[0114] PDCCH repetitions allocated to different time domains (e.g., TDM PDCCH repetitions) may also be configured to support only intra-mini-slot PDCCH repetitions. In other words, PDCCH repetitions allocated to different time domains may also be configured to not support inter-slot PDCCH repetitions or intra-slot PDCCH repetitions.

[0115] In this case, if mini-slot level offset is supported, even if the UE erroneously detects the PDCCH serving as the time reference and misidentifies another PDCCH as the time reference, it can appropriately determine the time domain resources of the physical shared channel to which the mini-slot level offset is applied.

[0116] <Field settings related to time base>

[0117] In repeated transmission of PDCCHs allocated in different time domains (e.g., TDM PDCCH repetition), a field (e.g., a new field) for determining the PDCCH that serves as the time reference may also be set in the DCI. For example, a field may be added to each PDCCH to indicate whether the PDCCH is the PDCCH that serves as the time reference (e.g., whether it is the PDCCH that is initially transmitted in the repeated transmission).

[0118] For example, a 1-bit specific field may be set. When the specific field value is 1, it indicates that the PDCCH (or the first PDCCH) is the time reference. When the specific field value is 0, it indicates that the PDCCH (or the first PDCCH) is not the time reference (see Figure 7A ).

[0119] Alternatively, a specific field for indicating the order of transmission in the time direction in repeated transmission may be set in the DCI. For example, a 2-bit specific field may be set, where a value of 00 indicates that the PDCCH (or the first PDCCH) is the time reference, a value of 01 indicates that the second PDCCH is the time reference, a value of 10 indicates that the third PDCCH is the time reference, and a value of 11 indicates that the fourth PDCCH is the time reference (see Figure 7B ).

[0120] exist Figure 7B , the case where the specific field is set by 2 bits is shown, but the present invention is not limited to this. The size (or number of bits) of the specific field can also be determined based on the maximum number of repeated transmissions.

[0121] In this way, when repeatedly transmitting PDCCHs allocated in different time domains (e.g., TDM PDCCH repetition), the content of the time-related information notified by the DCI transmitted in each PDCCH is set to be the same, thereby suppressing the increase in DCI overhead. For example, consider a case where the slot offset is associated with other parameters (e.g., starting symbol S, length L) (e.g., set corresponding to the DCI code point). In this case, by making the slot offset of each DCI the same value, there is no need to increase the number of candidate combinations of the slot offset and other parameters.

[0122] (Third Method)

[0123] The third approach describes a scenario where PDCCH repetitions (TDM PDCCH repetitions) sent in different time domains support / allow the transmission of DCI with different payload contents (same DCI payload content). In other words, this is equivalent to a scenario where different DCI payload contents are separately notified to the UE via multiple PDCCHs.

[0124] The payload contents may be different, but the values of some specific fields among the fields included in each DCI may be set to the same.

[0125] The specific field may also be a notification field for time-related information (or timing-related information). For example, the specific field may also be at least one of a time domain resource assignment field (e.g., a time domain resource assignment field) and a HARQ-ACK feedback timing indication field (e.g., a PDSCH-to-HARQ feedback timing indicator field).

[0126] In the case of supporting the following scenario, namely, scheduling a specific physical shared channel by multiple DCIs respectively sent in PDCCHs allocated to different time domains, and the contents of the multiple DCIs (for example, payload contents) are different, in this case, the UE can also interpret / apply the time-related information (or timing-related information) contained in the DCI based on different time references for each PDCCH / DCI.

[0127] For example, the UE can also determine the time domain resources of the signal / channel (for example, physical shared channel) scheduled by each DCI based on the notification field of the time-related information contained in the DCI sent in each PDCCH, and the PDCCH corresponding to each DCI (or, the transmission timing of the PDCCH).

[0128] The value of the time-related information included in each DCI may be different. However, the actual timing (eg, scheduled timing) indicated by the time-related information (eg, time domain resource allocation of the physical shared channel) included in each DCI may also be the same.

[0129] For example, it is assumed that the value of the slot offset K0 included in each DCI is different (see Figure 8 The UE can also use the PDCCH corresponding to each DCI as a reference to determine the location and timing of the scheduled PDSCH. Here, the following case is shown: DCI #1 transmitted on PDCCH #1 allocated in time slot #n specifies time slot offset 2, and DCI #2 transmitted on PDCCH #2 allocated in time slot #n+1 specifies time slot offset 1.

[0130] The UE determines that the PDSCH is scheduled in a time slot two slots away from PDCCH #1 (here, time slot #n+2) and a time slot one slot away from PDCCH #2 (here, time slot #n+2). The UE may also assume that the same time resource (e.g., time slot) is specified by the DCI transmitted in the repeated PDCCH.

[0131] exist Figure 8 , the case where multiple PDCCHs / multiple DCIs are used to schedule PDSCHs is shown, but the present invention is not limited thereto. When multiple PDCCHs / multiple DCIs are used to schedule PUSCHs, the UE may also interpret / apply the time-related information contained in the DCIs based on the timing of the PDCCHs corresponding to the respective DCIs.

[0132] In inter-slot PDCCH repetition, when the slot-level timing notification in slot #n is p, the slot-level timing notification in slot #n+1 may be p-1.

[0133] In intra-slot PDCCH repetition, the slot-level timing notification included in all DCI transmitted in slot #n may be the same (e.g., all DCI may include p). On the other hand, in intra-slot PDCCH repetition, if the slot-level timing notification in subslot #m is p, the subslot-level timing notification in slot #m+1 may be p-1.

[0134] In intra-mini-slot PDCCH repetition, the slot-level timing notification included in all DCI transmitted in slot #n may be the same (e.g., all DCI may include "p"). In intra-mini-slot PDCCH repetition, the subslot-level timing notification included in all DCI transmitted in subslot #m may be the same (e.g., all DCI may include "p"). On the other hand, in intra-mini-slot PDCCH repetition, if the slot-level timing notification in mini-subslot #r is "p," the subslot-level timing notification in mini-subslot #r+1 may be "p-1."

[0135] Other fields other than the time-related information field (e.g., the time-domain resource allocation field) included in the DCI may also be set to the same content (e.g., the same value / same bit value). The UE may also assume that the values of other fields other than the time-related information field (e.g., the frequency-domain resource allocation field, etc.) included in multiple DCIs that are repeatedly transmitted may also be set to the same.

[0136] A specific transmission parameter (or one or more specific transmission parameters) may be associated with multiple PDCCHs (or multiple DCIs) to which repeated transmission is applied. The specific transmission parameter may also be at least one of a control channel element (CCE), a resource element group (REG), a search space, a search space set, and a CORESET.

[0137] <Field settings related to time base>

[0138] In repeated transmission of PDCCHs allocated in different time domains (e.g., TDM PDCCH repetition), a specific field (e.g., a new field) for determining the PDCCH serving as the time reference may be set in the DCI. For example, a specific field may be added to each PDCCH to indicate whether the PDCCH is the PDCCH serving as the time reference (e.g., whether it is the PDCCH initially transmitted in the repeated transmission).

[0139] For example, a 1-bit specific field can also be set. When the value of the specific field is 1, it indicates that it is the PDCCH that serves as the time reference (or, the initial PDCCH). When the value of the specific field is 0, it indicates that it is not the PDCCH that serves as the time reference (or, the initial PDCCH).

[0140] Alternatively, a specific field may be set in the DCI to indicate the order of transmission in the time direction during repeated transmission. For example, a 2-bit specific field may be set, where a value of 00 indicates the PDCCH serving as the time reference (or the first PDCCH), a value of 01 indicates the second PDCCH, a value of 10 indicates the third PDCCH, and a value of 11 indicates the fourth PDCCH.

[0141] (Variation 1)

[0142] For PDCCH repetition using frequency division multiplexing (FDM) / spatial division multiplexing (SDM), the UE can also assume that each PDCCH / DCI contains the same DCI payload content (e.g., at least time-related information). When PDCCH repetition uses FDM / SDM, it can be interpreted as multiple PDCCHs / multiple DCIs being transmitted in the same time domain (e.g., the same symbol).

[0143] In this case, the UE may interpret / apply the time-related information (or timing-related indication) included in the multi-PDCCH / multi-DCI based on at least one of the following options 3-1 to 3-2.

[0144] <Option 3-1>

[0145] The UE may also determine the scheduled time domain resources based on the time-related information notified by any one of the repeatedly transmitted PDCCCHs (eg, multiple PDCCHs / multiple DCIs).

[0146] <Option 3-2>

[0147] The UE may also determine the scheduled time domain resources based on the time-related information notified by a specific PDCCH / DCI among the repeatedly transmitted PDCCCHs (eg, multiple PDCCHs / multiple DCIs).

[0148] The specific PDCCH / DCI may be the PDCCH / DCI having the minimum / maximum frequency index (or CCE index) among repeatedly transmitted PDCCCHs (eg, multiple PDCCHs / multiple DCIs).

[0149] Alternatively, the specific PDCCH / DCI may be the PDCCH / DCI corresponding to the minimum / maximum TRP index (or CORESET pool index) in the repeatedly transmitted PDCCCH (e.g., multiple PDCCH / multiple DCI).

[0150] Alternatively, the specific PDCCH / DCI may be the PDCCH / DCI corresponding to the minimum / maximum TCI state ID in the repeatedly transmitted PDCCCH (e.g., multiple PDCCH / multi-DCI). The TCI state corresponding to the PDCCH / DCI may also be the TCI state corresponding to the CORESET used in transmitting the PDCCH / DCI. In addition, when the CORESET pool index is set, the CORESET corresponding to the CORESET pool index with the minimum / maximum index may also be selected.

[0151] The second and third schemes may be applied only to TDM PDCCH repetition schemes. Alternatively, the second and third schemes may be applied only to inter-slot / intra-slot / intra-mini-slot TDM PDCCH repetition schemes.

[0152] (Variation 2)

[0153] Sometimes, the DCI includes a DL assignment index (Downlink Assignment Indicator (DAI)). In addition, the DAI field can also be split into a counter DAI (cDAI) and a total DAI (tDAI).

[0154] The counter DAI may also represent the counter value of downlink transmissions (PDSCH, data, TB) scheduled within a specific period. For example, the counter DAI in the DCI for scheduling data within the specific period may also represent the number counted in the frequency domain (e.g., in CC index order) and then in the time domain (in time prime order) within the specific period.

[0155] The total DAI may also represent the total value (total number) of data scheduled within a specific period. For example, the total DAI within the DCI for data scheduled at a specific time unit (e.g., a PDCCH monitoring opportunity) within the specific period may also represent the total number of data scheduled within the specific period up to the specific time unit (also referred to as a point, timing, etc.).

[0156] In a multi-TRP scenario, when PDCCH is repeatedly sent from multiple TRPs, how to control the DAI field included in the DCI sent in each PDCCH (or how the UE interprets it) becomes a problem.

[0157] When the DAI included in each DCI transmitted in each PDCCH is set to the same value (for example, the same DCI payload is applied repeatedly to the PDCCH), the UE may interpret / apply the DAI field based on at least one of the following options 4-1 to 4-2.

[0158] <Option 4-1>

[0159] The DAI field in a repeated PDCCH (or multiple DCI) may also be determined based on a specific PDCCH (e.g., the PDCCH initially transmitted in the repetition). That is, the DAI field of each DCI may be counted (or counted up) only in the initial PDCCH (or DCI) and not counted in other PDCCHs.

[0160] In addition, the DCI field included in each DCI may also be set to the count value in the initial PDCCH / DCI. In addition, when the first PDCCH sent in the repetition is the first PDCCH in the counter DAI (for example, when DAI=0), the DAI included in each DCI may also be 0 (or may not be counted).

[0161] <Option 4-2>

[0162] The DAI field in a repeated PDCCH (or multiple DCI) may also be determined based on the PDCCH last transmitted in the repetition. In this case, the DCI field included in each DCI may also be set to the count value in the last PDCCH / DCI. For example, if the number of repetitions is n, the DCI field in each DCI may be set to a value that is at least the number of repetitions n.

[0163] When supporting repeated application of different DCI payloads to the PDCCH, the UE may interpret / apply the DAI field based on at least one of the following options 5-1 to 5-2.

[0164] <Option 5-1>

[0165] Each DAI field in the PDCCH / DCI to which repeated transmission is applied may be set to the same value. In this case, Option 4-1 or Option 4-2 may also be applied.

[0166] <Option 5-2>

[0167] The DAI field in repeated PDCCHs (or multiple DCIs) can also be set to different values. In this case, the count control of the DAI field in each DCI can also be controlled based on a combination of the serving cell and the PDCCH monitoring opportunity. Alternatively, it can be controlled based on a combination of at least one of the serving cell and the PDCCH monitoring opportunity and the TRP index.

[0168] When different values are set for the DAI fields included in each PDCCH / DCI (and the same value is set for the time domain resource allocation field), the UE can also determine the PDCCH that serves as the time reference based on the DAI field (for example, counter DAI).

[0169] (UE capability information)

[0170] The UE may also report to the base station whether it supports PDCCH repetition as UE capability information. For example, the UE may also report to the base station whether it supports a multiplexing scheme (TDM / SDM / FDM) applicable to PDCCH repetition.

[0171] The UE may also report to the base station whether the PDCCH repetition (TDM PDCCH repetition) sent in different time domains supports inter-slot PDCCH repetition, intra-slot PDCCH repetition, or intra-mini-slot PDCCH repetition.

[0172] In addition, the UE may report the UE capability related to the maximum number of repetitions to the base station. The maximum number of repetitions may be set separately for multiplexing schemes (TDM / SDM / FDM) or may be set commonly.

[0173] The UE may also report whether it supports the same DCI payload content scenario or the different DCI payload content scenario in the repetitive PDCCH (eg, inter-slot / intra-slot / intra-mini-slot TDM PDCCH repetition).

[0174] The UE may also report to the base station whether it supports the number of repetitions based on the DCI notification.

[0175] The base station may also control the repetitive transmission of the PDCCH based on the capability information reported from the UE. In addition, the base station may also notify / set the UE of the above-mentioned UE capability information using higher layer signaling or the like.

[0176] (Wireless Communication System)

[0177] The following describes a configuration of a wireless communication system according to an embodiment of the present disclosure. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure, or a combination thereof.

[0178] Figure 9This figure shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may also be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP) or the fifth generation mobile communication system New Radio (5G NR).

[0179] In addition, the wireless communication system 1 can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRAN-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

[0181] The wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) where both the MN and SN are NR base stations (gNB)).

[0182] The wireless communication system 1 may also include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form smaller cells C2 that are narrower than the macrocell C1. User terminals 20 may also be located within at least one of the cells. The arrangement and number of cells and user terminals 20 are not limited to those shown. Hereinafter, when not distinguishing between base stations 11 and 12, they are collectively referred to as base stations 10.

[0183] 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 (CCs) and dual connectivity (DC).

[0184] Each CC may also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the 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 below 6 GHz (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to this. For example, FR1 may correspond to a frequency band higher than FR2.

[0185] Furthermore, the user terminal 20 may communicate in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).

[0186] Multiple base stations 10 can be connected via wired (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11, which is equivalent to a high-level station, can be called an integrated access backhaul (IAB) host, and the base station 12, which is equivalent to a relay station (relay), can also be called an IAB node.

[0187] The base station 10 may also be connected to the core network 30 via other base stations 10, or directly connected to the core network 30. The core network 30 may also 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.

[0188] The user terminal 20 may also be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0189] In the wireless communication system 1, a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) may be used in at least one of the downlink (DL) and uplink (UP).

[0190] The radio access scheme may also be referred to as a waveform. In addition, 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 radio access schemes for UL and DL.

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

[0192] In addition, in the wireless communication system 1, as uplink channels, 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. can also be used.

[0193] The PDSCH transmits user data, higher-layer control information, and system information blocks (SIBs). The PUSCH also transmits user data, higher-layer control information, and the PBCH also transmits master information blocks (MIBs).

[0194] The PDCCH may also transmit lower layer control information, such as downlink control information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0195] Furthermore, the DCI that schedules the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI that schedules the PUSCH may also be referred to as UL grant, UL DCI, etc. Furthermore, the PDSCH may also be interpreted as DL data, and the PUSCH may also be interpreted as UL data.

[0196] In PDCCH detection, a control resource set (CORESET) and a search space can also be used. A CORESET corresponds to the resources for searching for DCI. A search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a search space based on the search space settings.

[0197] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. In addition, the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," and "CORESET setting" in this disclosure may be used interchangeably.

[0198] The PUCCH can also be used to transmit uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request acknowledgment (HARQ-ACK)), ACK / NACK, etc.), and a scheduling request (SR). The PRACH can also be used to transmit a random access preamble used to establish a connection with a cell.

[0199] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Furthermore, various channels may be expressed without adding "Physical" at the beginning.

[0200] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may also be transmitted. In the wireless communication system 1, as DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. may also be transmitted.

[0201] 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 containing SSs (PSS, SSS) and PBCHs (and DMRS for the PBCH) may also be referred to as an SS / PBCH block or an SS block (SSB). Furthermore, SSs and SSBs may also be referred to as reference signals.

[0202] In addition, in the wireless communication system 1, as an uplink reference signal (Uplink Reference Signal (UL-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. can also be transmitted. In addition, DMRS can also be called a user terminal specific reference signal (UE specific reference signal (UE-specific Reference Signal)).

[0203] (Base Station)

[0204] Figure 10 This figure shows an example of the configuration of a base station according to one embodiment. Base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Furthermore, each of control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may include more than one.

[0205] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also conceivable that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0206] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

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

[0208] The transceiver unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, as described based on common knowledge in the technical fields involved in this disclosure.

[0209] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be composed of a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0210] The transmitting / receiving antenna 130 can be formed of an antenna such as an array antenna, which is described based on common knowledge in the technical field to which the present disclosure relates.

[0211] The transmitting and receiving unit 120 may also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the aforementioned uplink channel, uplink reference signal, etc.

[0212] The transmitting and receiving unit 120 may also form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), and the like.

[0213] The sending and receiving unit 120 (sending processing unit 1211) can also perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 110, and generate a bit string to be sent.

[0214] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, discrete Fourier transform (DFT) processing (as needed), inverse fast Fourier transform (IFFT) processing), precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0215] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0216] On the other hand, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filtering, and demodulation into baseband signals on the radio frequency band signals received via the transmitting and receiving antenna 130 .

[0217] The transmitting and receiving unit 120 (receiving processing unit 1212) can also apply receiving processing such as analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal, and obtain user data, etc.

[0218] The transmitting and receiving unit 120 (measuring unit 123) may also perform measurements related to received signals. For example, the measuring unit 123 may perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc. based on the received signals. The measuring unit 123 may also 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 also be output to the control unit 110.

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

[0220] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0221] The transmitting and receiving unit 120 may also transmit a plurality of downlink control information, where the downlink control information is respectively transmitted using a plurality of downlink control channels allocated in different time domains.

[0222] The sending and receiving unit 120 can also use multiple downlink control information to control the scheduling of the physical shared channel. When the content of the timing association information contained in the multiple downlink control information is the same, a specific downlink control channel is used as the time reference and the timing association indication information is used to control the scheduling of the physical shared channel.

[0223] The sending / receiving unit 120 may also support the use of multiple downlink control information to control the scheduling of the physical shared channel, and the content of the timing association information contained in the multiple downlink control information is different. The downlink control channel corresponding to each downlink control information may be used as a time reference, and the timing association information contained in each downlink control information may be used to control the scheduling of the physical shared channel.

[0224] (User Terminal)

[0225] Figure 11 This figure shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Furthermore, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each include more than one.

[0226] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also conceivable that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0227] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

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

[0229] The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, which are described based on common knowledge in the technical fields involved in this disclosure.

[0230] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0231] The transmitting and receiving antenna 230 can be formed of an antenna such as an array antenna, which is described based on common knowledge in the technical field to which the present disclosure relates.

[0232] The transmitting and receiving unit 220 may also receive the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the aforementioned uplink channel, uplink reference signal, etc.

[0233] The transmitting and receiving unit 220 may also form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), and the like.

[0234] The sending and receiving unit 220 (sending processing unit 2211) can also perform PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 210, and generate a bit string to be sent.

[0235] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output the baseband signal.

[0236] Furthermore, whether or not to apply DFT processing may also be based on the transform precoding setting. When transform precoding is enabled for a channel (e.g., PUSCH), the transmitting / receiving unit 220 (transmitting processing unit 2211) may perform DFT processing as part of the aforementioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, DFT processing may not be performed as part of the aforementioned transmission processing.

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

[0238] On the other hand, the transmitting and receiving unit 220 (RF unit 222 ) may also perform amplification, filter processing, and demodulation into a baseband signal on the radio frequency band signal received via the transmitting and receiving antenna 230 .

[0239] The transmitting and receiving unit 220 (receiving processing unit 2212) can also perform receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing on the obtained baseband signal, and obtain user data, etc.

[0240] The transmitting and receiving unit 220 (measuring unit 223) may also perform measurements related to received signals. For example, the measuring unit 223 may also perform RRM measurements and CSI measurements based on the received signals. The measuring unit 223 may also 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 also be output to the control unit 210.

[0241] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 , the transmitting and receiving antenna 230 , and the transmission path interface 240 .

[0242] The transmitting and receiving unit 220 may also receive a plurality of downlink control information, where the downlink control information is respectively transmitted using a plurality of downlink control channels allocated in different time domains.

[0243] The control unit 210 may also control the reception and transmission of at least one of the physical shared channels scheduled by multiple downlink control information. When the content of the timing association information respectively contained in the multiple downlink control information is the same, a specific downlink control channel is used as the time reference, and based on the timing association information, at least one of the reception timing and the transmission timing of the physical shared channel is determined.

[0244] The control unit 210 may also determine at least one of the reception timing and the transmission timing of the physical shared channel based on the timing-related information contained in each downlink control message, using the downlink control channel corresponding to each downlink control message as a time reference, when supporting control of at least one of the reception and transmission of a physical shared channel scheduled by multiple downlink control messages, and when the timing-related information contained in each downlink control message differs in content. The control unit 210 may also assume that the timing-related information contained in each downlink control message specifies the same time domain.

[0245] A plurality of downlink control channels may be associated and configured with respect to specific transmission parameters.

[0246] Multiple downlink control channels may also be allocated within the same time slot, the same sub-time slot, or the same mini-time slot.

[0247] Each of the plurality of downlink control information may include information related to specific downlink control information or information related to the transmission order in the time domain.

[0248] It can also support the allocation of multiple downlink control channels to different time slots.

[0249] (Hardware Structure)

[0250] In addition, the block diagram used in the description of the above embodiment shows a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using one device that is physically or logically combined, or two or more devices that are physically or logically separated can be directly or indirectly (for example, using wired, wireless, etc.) connected and implemented using these multiple devices. The functional block can also be implemented by combining software for the above-mentioned one device or the above-mentioned multiple devices.

[0251] Here, functions include, but are not limited to, judging, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that performs a transmitting function may also be referred to as a transmitting unit, a transmitter, or the like. Regardless of which one, as described above, the implementation method is not particularly limited.

[0252] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 12 This figure shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 can 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, and a bus 1007.

[0253] In this disclosure, the terms device, circuit, equipment, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or may exclude some of the devices.

[0254] For example, although only one processor 1001 is shown, multiple processors may be provided. Furthermore, processing may be performed by a single processor, or by two or more processors simultaneously, sequentially, or using other methods. Furthermore, processor 1001 may be implemented by one or more chips.

[0255] The various functions in the base station 10 and the user terminal 20 are implemented, for example, in the following manner: by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0256] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may be composed of a central processing unit (CPU) including interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, at least a portion of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may also be implemented by the processor 1001.

[0257] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and performs various processes based on them. As the program, a program that causes the computer to execute at least a portion of the operations described in the above embodiments is used. For example, the control unit 110 (210) can be implemented by a control program stored in the memory 1002 and operated by the processor 1001. The other functional blocks can also be implemented similarly.

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

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

[0260] The communication device 1004 is hardware (a transmitting and receiving device) used to communicate between computers via at least one of a wired network and a wireless network. For example, it is also called a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the aforementioned transmitting and receiving unit 120 (220) and the transmitting and receiving antenna 130 (230) may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated by the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0261] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to the outside (e.g., a display, speaker, light emitting diode (LED) lamp, etc.). Alternatively, the input device 1005 and the output device 1006 may be integrated (e.g., a touch panel).

[0262] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for information communication. The bus 1007 may be configured as a single bus or may be configured as separate buses between the devices.

[0263] Furthermore, the base station 10 and user terminal 20 may be configured using hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). These hardware components may also be used to implement some or all of the functional blocks. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0264] (Variation)

[0265] In addition, the terms described in this disclosure and the terms required for understanding this disclosure can be replaced with terms having the same or similar meanings. For example, channel, code element, and signal (signal or signaling) can also be replaced with each other. In addition, the signal can also be a message. The reference signal can also be referred to as RS, and depending on the applied standard, it can also be called a pilot, a pilot signal, etc. In addition, a component carrier (CC) can also be called a cell, a frequency carrier, a carrier frequency, etc.

[0266] A radio frame can also be composed of one or more time periods (frames) in the time domain. The one or more time periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can be a fixed duration (e.g., 1 ms) that is independent of the parameter set (numerology).

[0267] Here, a parameter set may also be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. For example, the parameter set may also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, specific windowing processing performed by the transmitter and receiver in the time domain, etc.

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

[0269] A time slot may also include multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Furthermore, a mini-slot may also be referred to as a sub-slot. Compared to a time slot, a mini-slot may also be composed of a smaller number of symbols. A PDSCH (or PUSCH) transmitted using a time unit larger than a mini-slot may also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as PDSCH (PUSCH) mapping type B.

[0270] Radio frames, subframes, time slots, mini-slots, and symbols all represent time units used for signal transmission. Radio frames, subframes, time slots, mini-slots, and symbols may also be referred to by their respective equivalents. Furthermore, the terms frame, subframe, time slot, mini-slot, and symbol may be used interchangeably in this disclosure.

[0271] For example, a subframe can be called a TTI, multiple consecutive subframes can be called a TTI, and a slot or mini-slot can be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Furthermore, the unit representing a TTI can be called a slot, a mini-slot, or the like, rather than a subframe.

[0272] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communications. For example, in the LTE system, a base station schedules each user terminal by allocating radio resources (such as the frequency bandwidth and transmit power available to each user terminal) in units of TTI. The definition of TTI is not limited to this.

[0273] A TTI can be a time unit for transmitting channel-coded data packets (transport blocks), code blocks, code words, etc., and can also be a processing unit for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0274] In addition, when one time slot or one mini-time slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini-time slots) can be the minimum time unit for scheduling. In addition, the number of time slots (the number of mini-time slots) that constitute the minimum time unit for scheduling can also be controlled.

[0275] A TTI with a duration of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a time slot, etc.

[0276] In addition, long TTI (e.g., normal TTI, subframe, etc.) can also be interpreted as TTI with a duration exceeding 1ms, and short TTI (e.g., shortened TTI, etc.) can also be interpreted as TTI with a TTI length less than that of long TTI and greater than 1ms.

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

[0278] In addition, an RB may contain one or more symbols in the time domain, and may be the length of one slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, etc. may also be composed of one or more resource blocks.

[0279] In addition, one or more RBs may also be referred to as a physical resource block (Physical RB (PRB))), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, and the like.

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

[0281] A Bandwidth Part (BWP) (also referred to as a fractional bandwidth) can also represent a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a carrier. Common RBs can also be identified by their index relative to a common reference point for that carrier. PRBs can also be defined within a BWP and numbered within that BWP.

[0282] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured within one carrier.

[0283] At least one of the configured BWPs may be activated, and the UE may not assume that a specific signal / channel is transmitted or received outside the activated BWP.

[0284] The above-described structures of radio frames, subframes, slots, mini-slots, and symbols are merely examples. For example, various modifications may be made to structures such as the number of subframes in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots within a slot, the number of symbols and RBs within a slot or mini-slot, the number of subcarriers within an RB, the number of symbols within a TTI, the symbol length, and the cyclic prefix (CP) length.

[0285] In addition, the information, parameters, etc. described in this disclosure may be represented by absolute values, relative values relative to a specific value, or other corresponding information. For example, wireless resources may also be indicated by a specific index.

[0286] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, mathematical formulas using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any appropriate name, and thus the names assigned to these channels and information elements are not limiting in any way.

[0287] The information, signals, and the like described in this disclosure may be represented using any of a variety of different technologies. For example, references to data, instructions, commands, information, signals, bits, symbols, and chips throughout the foregoing description may also be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0288] Furthermore, information, signals, etc. may be output in at least one direction: from a higher layer to a lower layer, and from a lower layer to a higher layer. Information, signals, etc. may also be input and output via multiple network nodes.

[0289] Input and output information, signals, etc. can be stored in a specific area (e.g., memory) or managed using a management table. Input and output information, signals, etc. can also be overwritten, updated, or appended. Output information, signals, etc. can also be deleted. Input information, signals, etc. can also be sent to other devices.

[0290] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be performed using other methods. For example, the notification of information in this disclosure may be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), high-layer signaling (e.g., Radio Resource Control (RRC)) signaling, broadcast information (Master Information Block (MIB)), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0291] In addition, physical layer signaling may also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. In addition, MAC signaling may also be notified using, for example, a MAC Control Element (CE).

[0292] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0293] The determination can be made by a value represented by one bit (0 or 1), a true or false value (boolean) represented by true (true) or false (false), or by comparison of numerical values (for example, comparison with a specific value).

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

[0295] Furthermore, software, instructions, information, and the like may be transmitted and received via a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, and Digital Subscriber Line (DSL)), and wireless technologies (infrared, microwave, and the like), then at least one of these wired and wireless technologies is included in the definition of transmission medium.

[0296] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may also refer to a device included in the network (eg, a base station).

[0297] 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", "transmission 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", and "panel" may also be used interchangeably.

[0298] In this disclosure, terms such as "base station (BS)", "wireless 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", and "component carrier" are used interchangeably. Base stations may also be referred to as macrocells, small cells, femtocells, and picocells.

[0299] A base station can accommodate one or more (for example, 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 also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to part or all of the coverage area of at least one of the base station and the base station subsystem that provide communication services within the coverage area.

[0300] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” may be used interchangeably.

[0301] 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, handheld device, user agent, mobile client, client, or some other appropriate terminology.

[0302] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Furthermore, at least one of the base station and the mobile station may also be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may also be a vehicle (e.g., a car, an airplane, etc.), a mobile object that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an Internet of Things (IoT) device such as a sensor.

[0303] In addition, the base station in the present disclosure can also be interpreted as a user terminal. For example, for a structure in which the communication between a base station and a user terminal is replaced by communication between multiple user terminals (for example, it can also be called device-to-device (D2D)), vehicle-to-everything (V2X), etc.), the various methods / implementations of the present disclosure can also be applied. In this case, it can be set as a structure in which the user terminal 20 has the functions of the above-mentioned base station 10. In addition, words such as "uplink" and "downlink" can also be interpreted as words corresponding to communication between terminals (for example, "side". For example, uplink channel, downlink channel, etc. can also be interpreted as side channel.

[0304] Likewise, the user terminal in this disclosure can also be interpreted as a base station. In this case, the base station 10 can be configured to have the functions of the user terminal 20 described above.

[0305] In this disclosure, operations performed by a base station may also be performed by its upper node depending on the circumstances. In a network including one or more network nodes including a base station, various operations performed for communication with a terminal may obviously be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW), but not limited thereto), or a combination thereof.

[0306] The various methods / implementations described in this disclosure may be used individually, in combination, or switched as they are executed. Furthermore, the processing procedures, timings, flow charts, and the like of the various methods / implementations described in this disclosure may be swapped in order as long as they do not conflict. For example, the methods described in this disclosure present elements of various steps in an illustrative order, but are not limited to the specific order presented.

[0307] The various modes and embodiments described in the present disclosure can be applied to 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)) (xG (x is, for example, an integer or a decimal)), 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 (Ultra Mobile Broadband), and other technologies. Broadband (UMB)), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB)), Bluetooth (registered trademark), and systems utilizing other appropriate wireless communication methods, as well as next-generation systems expanded upon these methods. Furthermore, multiple systems may be applied in combination (for example, LTE or LTE-A, in combination with 5G, etc.).

[0308] As used in this disclosure, the phrase “based on” does not mean “based only on.” Unless explicitly stated otherwise, the phrase “based on” means both “based only on” and “based at least on.”

[0309] Any reference to an element using the designations "first," "second," etc., as used in this disclosure is not intended to be a comprehensive limitation on the number or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and a second element does not necessarily mean that only two elements may be used or that the first element must precede the second element in some manner.

[0310] The term "determining" as used in this disclosure sometimes encompasses a variety of operations. For example, "determining" can be considered to be "judging," calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, etc.

[0311] In addition, "judgment (decision)" can also be regarded as "judgment (decision)" on receiving (for example, receiving information), transmitting (for example, sending information), input (input), output (output), accessing (for example, accessing data in a memory), etc.

[0312] Furthermore, “judgment (decision)” can also be considered as “judgment (decision)” on resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” can be considered as “judgment (decision)” on certain operations.

[0313] In addition, "judgment (decision)" can also be interpreted as "assuming", "expecting", "considering", etc.

[0314] The "maximum transmit power" recorded in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0315] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include situations where one or more intermediate elements exist between the two elements being "connected" or "coupled." The connection or coupling between elements may be physical, logical, or a combination thereof. For example, "connected" may also be interpreted as "accessed."

[0316] In the present disclosure, when two elements are connected, it can be considered that they are "connected" or "combined" to each other using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, they are "connected" or "combined" to each other using electromagnetic energy with a wavelength in the wireless frequency domain, microwave region, light (both visible and invisible light) region, etc.

[0317] In this disclosure, the term "A and B are different" may also mean "A and B are different from each other." Alternatively, the term may mean "A and B are each different from C." Terms such as "separated" and "bound" may be interpreted in the same manner as "different."

[0318] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" as used in this disclosure does not constitute an exclusive logical OR.

[0319] In the present disclosure, when an article is added due to translation, such as a, an, and the in English, the present disclosure may also include cases where the noun followed by the article is in plural form.

[0320] While the invention disclosed herein has been described in detail above, it will be apparent to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein. The invention disclosed herein can be implemented in the form of modifications and variations without departing from the spirit and scope of the invention as determined by the claims. Therefore, the descriptions in this disclosure are for illustrative purposes only and are not intended to limit the invention disclosed herein in any way.

Claims

1. A terminal, characterized in that: have: a receiving unit, receiving a plurality of downlink control information DCIs respectively transmitted by using a plurality of physical downlink control channels PDCCHs allocated in different time domains; as well as A control unit controls the counting of counter downlink allocation indicators (DAIs) respectively included in the plurality of DCIs based on a specific PDCCH among the plurality of PDCCHs, The control unit counts the counter DAI in the DCI sent in the specific PDCCH, The control unit uses a PDCCH that is later in time among the plurality of PDCCHs as a time reference corresponding to terminal processing based on the plurality of PDCCHs, The control unit controls the counting of the counter DAI included in each of the plurality of DCIs, assuming that the counters DAI included in each of the plurality of DCIs have the same value.

2. The terminal according to claim 1, wherein The counter DAI of other PDCCHs is determined by the counter DAI counted in the specific PDCCH.

3. The terminal according to claim 1, wherein The specific PDCCH is a PDCCH that is earlier in time among the multiple PDCCHs.

4. A wireless communication method, used for a terminal, characterized in that: The wireless communication method comprises: receiving a plurality of downlink control information DCIs respectively transmitted using a plurality of physical downlink control channels PDCCHs allocated in different time domains; and Based on a specific PDCCH among the plurality of PDCCHs, a step of controlling the counting of a counter downlink allocation indicator (DAI) respectively included in the plurality of DCIs, In the step of controlling, the counter DAI is counted in the DCI sent in the specific PDCCH, The wireless communication method further includes the step of using a PDCCH that is later in time among the plurality of PDCCHs as a time reference corresponding to terminal processing based on the plurality of PDCCHs. In the step of controlling, it is assumed that the counters DAI included in the plurality of DCIs have the same value, and thus the counts of the counters DAI included in the plurality of DCIs are controlled.

5. A base station, characterized in that: have: A sending unit, sending a plurality of downlink control information DCIs by using a plurality of physical downlink control channels PDCCHs allocated in different time domains; as well as a control unit that instructs the terminal to control the counting of the counter downlink allocation indicator (DAI) respectively included in the plurality of DCIs based on a specific PDCCH among the plurality of PDCCHs; The control unit instructs the terminal to count the counter DAI in the DCI sent in the specific PDCCH, The control unit instructs the terminal to use a PDCCH that is later in time among the plurality of PDCCHs as a time reference corresponding to terminal processing based on the plurality of PDCCHs, The control unit instructs the terminal to assume that the counters DAI respectively included in the plurality of DCIs have the same value, thereby controlling the counting of the counters DAI respectively included in the plurality of DCIs.

6. A system having a base station and a terminal, characterized in that: The base station: A sending unit, sending a plurality of downlink control information DCIs by using a plurality of physical downlink control channels PDCCHs allocated in different time domains; as well as a control unit that instructs the terminal to control the counting of the counter downlink allocation indicator (DAI) respectively included in the plurality of DCIs based on a specific PDCCH among the plurality of PDCCHs; The control unit instructs the terminal to assume that the counters DAI respectively included in the plurality of DCIs have the same value, thereby controlling the count of the counters DAI respectively included in the plurality of DCIs. The terminal has: A receiving unit, receiving the multiple DCIs respectively sent using the multiple PDCCHs; as well as A control unit controls the counting of the counters DAI respectively included in the plurality of DCIs based on the specific PDCCH among the plurality of PDCCHs, The control unit counts the counter DAI in the DCI sent in the specific PDCCH, The control unit uses a PDCCH that is later in time among the plurality of PDCCHs as a time reference corresponding to terminal processing based on the plurality of PDCCHs, The control unit controls the counting of the counter DAI included in each of the plurality of DCIs, assuming that the counters DAI included in each of the plurality of DCIs have the same value.

Images