Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one embodiment of the present disclosure includes: a transmission unit for transmitting at least one of a random access channel and an uplink shared channel; and a control unit for performing control to detect downlink control information in a predetermined window period in response to transmission of at least one of the random access channel and the uplink shared channel. The control unit determines the predetermined window period on the basis of the presence or absence of repetitive transmission of a downlink control channel that provides the downlink control information.

Description

[Technical Field]

[0001] This disclosure relates to terminals and wireless communication methods in next-generation mobile communication systems. 、 base station and system Regarding. [Background technology]

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

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

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 [Overview of the project] [Problems that the invention aims to solve]

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

[0006] Furthermore, NR is expected to apply repeated transmission to a predetermined channel (e.g., PDCCH). For example, it is conceivable to control the DL transmission / UL transmission schedule using multiple PDCCHs to which repeated transmission is applied from a multi-panel / TRP.

[0007] However, current NR specifications have not adequately considered how to control repeated transmissions from one or more TRPs.

[0008] Therefore, this disclosure provides a terminal and wireless communication method that can properly perform communication even when repeated transmission is applied to DL channels transmitted from one or more TRPs. 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0009] A terminal relating to one aspect of this disclosure includes information about the search space type, information about the number of downlink control channel candidates for each aggregation level, and information about linking search space sets. All of the information A receiving unit that receives higher layer parameters, and when multiple linked search space sets are configured for a common search space based on the higher layer parameters, the LinkA control unit that controls monitoring of downlink control channel candidates corresponding to a plurality of search space sets, and the plurality of search space sets to be linked have the same number of downlink control channel candidates set for each aggregation level. The search space set, defined by at least one of the higher-level parameters, searchSpaceSIB1, searchSpaceOtherSystemInformation, ra-SearchSpace, and pagingSearchSpace, is a set of multiple linked search spaces. Search space set as It is characterized by not being set.

Effect of the invention

[0010] According to one aspect of the present disclosure, communication can be appropriately performed even when repeated transmission is applied to a DL channel transmitted from one or more TRPs.

Brief description of the drawings

[0011] [Figure 1] FIG. 1 is a diagram showing an example of scheduling control of a physical shared channel based on PDCCH / DCI. [Figure 2] FIGS. 2A-2D are diagrams showing an example of a multi-TRP scenario. [Figure 3] FIG. 3 is a diagram showing an example of PDCCH repeated transmission. [Figure 4] FIG. 4 is a diagram showing an example of communication control using PDCCH repeated transmission in the present embodiment. [Figure 5] FIG. 5 is a diagram showing another example of communication control using PDCCH repeated transmission in the present embodiment. [Figure 6] FIG. 6 is a diagram showing an example of upper layer parameters related to a search space. [Figure 7] FIG. 7 is a diagram showing an example of PDCCH repeated control. [Figure 8] FIG. 8 is a diagram showing an example of PDCCH repeated control in the first aspect. [Figure 9] FIG. 9 is a diagram showing an example of the transmission timing of a PDCCH instructing cancellation of PUSCH / SRS transmission and a PDCCH scheduling PUSCH / SRS transmission. [Figure 10]Figure 10 shows an example of PDCCH repetitive control in the second embodiment. [Figure 11] Figure 11 shows an example of DCI detection in response to PRACH transmission. [Figure 12] Figure 12 shows an example of PDCCH repetitive control in the third embodiment. [Figure 13] Figure 13 shows another example of PDCCH repetitive control in the third embodiment. [Figure 14] Figure 14 shows an example of a QCL assumption when DCI detection is performed in response to PRACH transmission. [Figure 15] Figure 15 shows an example of PDCCH repetitive control in the fourth embodiment. [Figure 16] Figure 16 shows another example of PDCCH repetitive control in the fourth embodiment. [Figure 17] Figure 17 shows another example of PDCCH repetitive control in the fourth embodiment. [Figure 18] Figure 18 shows another example of PDCCH repetitive control in the fourth embodiment. [Figure 19] Figures 19A and 19B show an example of the association between values ​​notified by higher-layer parameters and specific parameters. [Figure 20] Figures 20A-20D show an example of the settings in the PDCCH repeater in the fifth embodiment. [Figure 21] Figures 21A-21D show other examples of settings in the PDCCH iteration in the fifth embodiment. [Figure 22] Figure 22 shows another example of the settings in the PDCCH iteration in the fifth embodiment. [Figure 23] Figure 23 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 24] Figure 24 shows an example of the configuration of a base station according to one embodiment. [Figure 25]Figure 25 shows an example of the configuration of a user terminal according to one embodiment. [Figure 26] Figure 26 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Figure 27] Figure 27 shows an example of a vehicle according to one embodiment. [Modes for carrying out the invention]

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

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

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

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

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

[0017] As shown in Figure 1, the UE uses the DCI (or the PDCCH used to transmit the DCI) as a reference point in the time domain to determine the slot in which the PDSCH is scheduled. For example, when the UE receives a DCI that schedules a PDSCH in slot #n, it determines the slot number n and the subcarrier spacing μ for the PDSCH. PDSCH Subcarrier spacing μ for PDCCH PDCCH Alternatively, the slot to receive (be allocated to) the PDSCH may be determined based on at least one of the above time offsets K0. Here, we show the case where slot offset K0 = 1 and the subcarrier spacing between the PDSCH and PDCCH is the same.

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

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

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

[0021] As shown in Figure 1, the UE uses the DCI (or the PDCCH used to transmit the DCI) as a reference point in the time domain to determine the slot in which the PUSCH is scheduled. For example, when the UE receives a DCI that schedules a PUSCH in slot #n+4, it uses the slot number n+4 and the subcarrier spacing μ for the PUSCH. PDSCH Subcarrier spacing μ for PUCCH PDCCHAlternatively, the slot to which PUSCH is transmitted (assigned to PUSCH) may be determined based on at least one of the above time offsets K2. Here, we show the case where slot offset K2 = 3 and the subcarrier spacing between PDSCH and PDCCH is the same.

[0022] Furthermore, the UE determines the allocation of a PUSCH based on the starting point of the slot to which the PUSCH is allocated, using the resource allocation information (e.g., SLIV) specified in the TDRA field.

[0023] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmissions to the UE. Furthermore, it is being considered that the UE will perform UL transmissions to one or more TRPs.

[0024] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID or a virtual cell ID.

[0025] Figures 2A-2D illustrate examples of multi-TRP scenarios. In these examples, it is assumed, but not limited to, that each TRP can transmit four different beams.

[0026] Figure 2A shows an example of a case where only one of the multi-TRPs (TRP1 in this example) transmits to the UE (this may also be called single-mode or single-TRP). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

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

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

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

[0030] When scheduling multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) as shown in Figure 2B using a single DCI, that DCI may be called a single DCI (S-DCI, single PDCCH). Similarly, when scheduling multiple PDSCHs from a multi-TRP (as shown in Figure 2D) using multiple DCIs, these multiple DCIs may be called multi-DCIs (M-DCI, multi-PDCCH (multiple PDCCH)).

[0031] Each TRP in a multi-TRP system may transmit a different codeword (CW) and a different layer. Non-coherent joint transmission (NCJT) is being considered as one form of multi-TRP transmission.

[0032] In NCJT, for example, TRP1 modulates and layers a first codeword and transmits a first PDSCH using a first precode with a first number of layers (e.g., 2 layers). TRP2 modulates and layers a second codeword and transmits a second PDSCH using a second precode with a second number of layers (e.g., 2 layers).

[0033] Furthermore, multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

[0034] These first and second PDSCHs may be assumed not to be quasi-co-located. Reception of multiple PDSCHs may be reinterpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0035] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition spanning multiple TRPs is being considered. Support for repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) spanning multiple TRPs on the frequency domain, layer (spatial) domain, or time domain is being considered. In scheme 1, multiple PDSCHs from multiple TRPs are performed using space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are performed using frequency division multiplexing (FDM). In scheme 2a, the redundant version (RV) is the same for multiple TRPs. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are performed using time division multiplexing (TDM). In Scheme 3, multi-PDSCH signals from multi-TRPs are transmitted within a single slot. In Scheme 4, multi-PDSCH signals from multi-TRPs are transmitted within different slots.

[0036] Such multi-TRP scenarios allow for more flexible transmission control using high-quality channels.

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

[0038] An extension of the TCI is being considered for single PDCCH designs (primarily for ideal backhaul). Each TCI code point within the DCI may correspond to one or two TCI states. The TCI field size may be the same as that of Rel. 15.

[0039] Incidentally, in Rel.17 and later, it is also anticipated that PDCCH repetition may be applied to PDCCH (or DCI) transmitted from one or more TRPs. For example, it is conceivable to use multiple PDCCH (or DCI) transmitted from one or more TRPs to schedule or transmit / receive instructions for one or more signals / channels.

[0040] A PDCCH / DCI to which repeated transmission is applied may be called a multi-PDCCH / multi-DCI. Repeated transmission of a PDCCH may also be interpreted as PDCCH repetition, multiple PDCCH transmissions, multi-PDCCH transmission, or multiple PDCCH transmission.

[0041] A multi-PDCCH / multi-DCI may be transmitted from a single TRP. Alternatively, a multi-PDCCH / multi-DCI may be transmitted from different TRPs. The multi-PDCCH / DCI may be multiplexed using time multiplexing (TDM), frequency multiplexing (FDM), or spatial multiplexing (SDM). For example, when using time multiplexing to repeat a PDCCH (TDM PDCCH repetition), the PDCCHs transmitted from different TRPs are assigned to different time domains.

[0042] Let's consider a scenario where one or more physical shared channels (e.g., DL-SCH / transport blocks) are scheduled using the multi-PDCCH / DCI. These one or more physical shared channels could be, for example, the same / single physical shared channel (e.g., DL-SCH / transport blocks), or multiple physical shared channels scheduled within the same time domain. In such a case, the question arises as to how to control the scheduling (e.g., the content of notifications in each DCI, the reference point for scheduling, etc.).

[0043] For example, if the content of the DCI (e.g., DCI payload / coded bits / CCE count) transmitted in different time domains of PDCCHs is the same, the UE's challenge becomes how to apply / interpret each PDCCH / DCI to control the transmission or reception process. As an example, the UE's challenge becomes how to apply / interpret the time relationship indications (e.g., the same value) of each PDCCH / DCI to control the schedule.

[0044] Figure 3 shows an example of scheduling one PDSCH (e.g., the same PDSCH) using a PDCCH to which repeated transmission is applied.

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

[0046] However, when scheduling using multiple PDCCH / DCIs, the question arises as to how to control the settings of timing-related information (e.g., time domain resource allocation information) included in each PDCCH / DCI, or how to control its interpretation in the UE.

[0047] For example, if timing-related information contained in each PDCCH / DCI (e.g., the same value / same payload) is applied / interpreted based on each PDCCH / DCI, the UE may not be able to properly understand one PDSCH (e.g., transmit / receive timing) that is scheduled in a PDCCH repetition (see Figure 3).

[0048] The inventors conceived this embodiment by considering how to determine a reference PDCCH / DCI / control resource set, or how to perform control based on a reference PDCCH / DCI / control resource set, in one or more cases where transmission / reception processing is performed using PDCCH repetitions (e.g., multiple PDCCH / DCI).

[0049] Alternatively, repeated transmission may be applied to the downlink control channel (or CORESET / downlink control channel candidate / search space / search space set) used for transmitting DCI (or DCI transmitted using the common search space) common to the UE. The UE monitors the PDCCH candidate set in CORESET, but when repeated transmission is applied to the downlink control channel (or CORESET / downlink control channel candidate / search space / search space set), the question arises as to how to control the monitoring of PDCCH candidates in CORESET / common search space.

[0050] The inventors focused on the case where repeated transmission is supported for PDCCHs corresponding to a common DCI (e.g., at least one of DCI formats 2_0 to 2_6) / common search space set (e.g., type 0 / 0A / 1 / 2 / 3-PDCCH CSS set) common to the UE, and conceived this embodiment by considering the reception control of PDCCH in such cases.

[0051] The embodiments relating to this disclosure will be described in detail below with reference to the drawings. Each of the following embodiments (for example, each case) may be used individually or at least two may be applied in combination.

[0052] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0053] In this disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0054] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, information elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0055] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0056] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0057] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0058] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0059] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumptions, etc., may be interpreted interchangeably.

[0060] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information" may be interpreted as mutually exclusive as "a set of spatial relationship information," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive.

[0061] In this disclosure, the PDSCH (or DL-SCH / CW / TB) / PUSCH (or UL-SCH) scheduled / transmitted in a PDCCH to which repeated transmission applies may have the same content or may have different content.

[0062] In the following embodiments, DCI may be limited to a specific DCI format (e.g., DCI formats 0_0, 0_1, 0_2) for scheduling PUSCH, or it may apply to multiple DCI formats. If it applies to multiple DCI formats, common control (the same control, the same processing) may be performed for all DCI formats, or different control may be performed for each DCI format.

[0063] In the following embodiments, "multiple" and "two" may be interchangeable.

[0064] (Wireless communication method) In this disclosure, multiple PDCCH / DCIs (e.g., multi-PDCCH / multi-DCI) to which repeated transmission is applied may be associated and configured with respect to a predetermined transmission parameter (or between one or more predetermined transmission parameters). The predetermined transmission parameter may be at least one of a control channel element (CCE), a PDCCH candidate, a resource element group (REG), a search space, a search space set, and a CORESET.

[0065] For example, predetermined transmission parameters may be associated and set between a time-based PDCCH (e.g., the first PDCCH transmitted in a repeat transmission) and other PDCCHs. As an example, predetermined transmission parameters may be set between the transmission parameters of multiple PDCCHs to which repetition applies, based on the repetition order (or in association with the transmission order). The UE can determine the transmission order of each PDCCH (e.g., the first PDCCH transmitted) based on information about the PDCCH repetition (e.g., the number of repetitions, the repetition period, etc.) and the transmission parameters corresponding to each PDCCH.

[0066] In this disclosure, a PDCCH to which repeated transmission applies may be interpreted as a CORESET / PDCCH candidate / search space / search space set to which repeated transmission applies. In other words, when repeated transmission applies to a PDCCH, it may be interpreted as repeated transmission applying to a CORESET / PDCCH candidate / search space / search space set. Furthermore, in this disclosure, PDCCH, CORESET, PDCCH candidate, search space, and search space set may be interpreted as mutually interchangeable.

[0067] When recurring transmissions are applied to a PDCCH, different CORESETs / PDCCH candidates / searchspace sets may be associated or linked to each of the different recurring transmissions. Multiple (e.g., two) linked PDCCH candidates, or multiple (e.g., two) linked searchspace sets, may correspond to one CORESET or each may correspond to a different CORESET.

[0068] Furthermore, if repeated transmissions occur due to PDCCHs being sent from multiple TRPs (e.g., two TRPs), the CORESET / PDCCH candidate / search space / search space set corresponding to each TRP may be configured in association. Multiple (e.g., two) associated CORESETs / PDCCH candidate / search space / search space sets may be called linked CORESETs / linked PDCCH candidate / linked search space / linked search space sets.

[0069] This embodiment explains the case where the same DCI payload content is transmitted by PDCCH repetitions transmitted in different time domains (TDM PDCCH repetitions). In other words, it corresponds to the case where the same DCI payload content is notified to each UE by multiple PDCCHs. However, this embodiment is not limited to this and may also be applied when the transmission of DCIs with different payload content is supported / allowed by PDCCH repetitions transmitted in different time domains.

[0070] The payload content being the same may mean that the values ​​of all fields included in each DCI are set to the same value. Alternatively, it may mean that the values ​​of some of the predetermined fields included in each DCI are set to the same value.

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

[0072] If a given physical shared channel is scheduled by multiple DCIs transmitted on PDCCHs assigned to different time domains, and the contents of the multiple DCIs (e.g., payload contents) are the same, the UE may interpret / apply the time-related information (or timing-related information) contained in the DCIs based on a specific time criterion.

[0073] The time criterion may be interpreted as a timing criterion, reference timing, reference point, time criterion point, criterion in the time domain, or criterion point in the time domain. Furthermore, the time criterion may be interpreted as a criterion for parameters other than time.

[0074] The specific time criterion may be a specific PDCCH (or the transmission timing of a specific PDCCH) among multiple PDCCHs that are repeatedly transmitted. For example, in one or more cases where transmission / reception processing is performed using PDCCH repetition (e.g., multiple PDCCH / DCI), the UE may apply at least one of the following criteria A1 to A8 as a specific time criterion for the detection / reception of the PDCCH corresponding to the DCI, or for the scheduling of the DL channel / UL channel / RS. In other words, the UE may determine which PDCCH / DCI to refer to (which DCI value to indicate) among multiple PDCCH / DCIs that are repeatedly received, based on at least one of the following criteria A1 to A8.

[0075] Criterion A1: First / last PDCCH repetition in the time domain Criterion A2: First / last PDCCH repetition in the frequency domain Criterion A3: PDCCH repetition with lowest / highest TCI state ID Criterion A4: PDCCH repetition with the lowest / highest CORESET Pool ID (TRP ID) / highest CORESET Pool ID (TRP ID) Criterion A5: PDCCH repetition with lowest / highest CORESET ID Criterion A6: PDCCH repetition with lowest / highest search space index. Criterion A7: PDCCH repetition with lowest / highest minoring occasion. Criterion A8: Any combination of A1-A7

[0076] The first / last PDCCH iteration in the time domain may be any of the PDCCHs to which the repeated transmission applies: an end-later PDCCH, an end-earlier PDCCH, a start-later PDCCH, or a start-earlier PDCCH.

[0077] Criterion A1 corresponds, for example, to the case where the first PDCCH transmitted (or received) in a PDCCH repeat, or the first PDCCH allocated in the time domain, is the specific time criterion. The UE may use the first symbol of the first transmitted PDCCH as the specific time criterion, or the last symbol of that PDCCH as the specific time criterion. Alternatively, the last PDCCH transmitted (or received) in a PDCCH repeat, or the last PDCCH allocated in the time domain, may be the specific time criterion.

[0078] Criterion A2 may define a specific time criterion as the PDCCH having the smallest control channel element (CCE) index / largest CCE index among the PDCCH repeats. Alternatively, the specific time criterion may define a PDCCH having the smallest PDCCH candidate index / largest PDCCH candidate index among the PDCCH repeats.

[0079] Criterion A8 may, for example, combine A1 and A4 to determine a specific time criterion, where the PDCCH with the smallest CORESET pool ID is the first PDCCH transmitted in the time domain.

[0080] Furthermore, a specific time criterion may be determined based on the control resource set corresponding to the PDCCH, rather than the PDCCH / DCI itself. For example, in one or more cases where transmission / reception processing is performed using PDCCH repetitions in multiple control resource sets, the UE may apply at least one of the following criteria B1 to B8 as the control resource set that serves as the basis for detecting / receiving the PDCCH corresponding to the DCI, or for scheduling the DL channel / UL channel / RS. In other words, the UE may determine which control resource set to refer to (which control resource set's DCI value to be indicated) among the PDCCH / DCIs that are received repeatedly multiple times (e.g., in the case of control resource set repetitions) based on at least one of the following criteria B1 to B8.

[0081] Criterion B1: Coreset of first / last PDCCH repetition in time domain Criterion B2: CORESET of first / last PDCCH repetition in frequency domain Criterion B3: Control resource set with lowest / highest resource block (or resource block group) / highest resource block (or resource block group) (CORESET with lowest / highest RB / RBG) Criterion B4: CORESET with lowest / highest TCI state ID Criterion B5: Control resource set with the lowest / highest CORESET Pool ID (TRP ID) / highest CORESET Pool ID (TRP ID) Criterion B6: Control resource set with the lowest / highest control resource set ID (CORESET with lowest / highest CORESET ID) Criterion B7: CORESET associated with the lowest / highest search space index. Criterion B8: Any combination of B1-B7

[0082] The CORESET for the first / last PDCCH iteration in the time domain may be any of the CORESETs corresponding to the PDCCH to which the repeated transmission applies: the CORESET corresponding to the last-ending PDCCH, the CORESET corresponding to the first-ending PDCCH, the CORESET corresponding to the last-starting PDCCH, or the CORESET corresponding to the first-starting PDCCH. Alternatively, the CORESET for the first / last PDCCH iteration in the time domain may be any of the CORESETs corresponding to the PDCCH to which the repeated transmission applies: the CORESET corresponding to the last-ending PDCCH, the CORESET corresponding to the first-ending PDCCH, the CORESET corresponding to the last-starting PDCCH, or the CORESET corresponding to the first-starting PDCCH.

[0083] In criterion B8, for example, B5 and B6 may be combined to determine the control resource set with the smallest control resource set ID among the PDCCHs with the smallest CORESET pool ID as the criterion (e.g., a specific time criterion).

[0084] <Application Cases> This embodiment may be applied to at least one of the following cases 0 to 13 as one or more cases in which transmission / reception processing is performed using PDCCH repetition (e.g., multiple PDCCH / DCI).

[0085] Case 0 Criteria A1-A8 (hereinafter simply referred to as Criteria A) / Criteria B1-B8 (hereinafter simply referred to as Criteria B) may be applied to control the transmission timing (e.g., time-domain resources) of a physical shared channel (e.g., PDSCH / PUSCH) scheduled using PDCCH / DCI repetition.

[0086] For example, a UE may determine the time domain resources of a signal / channel (e.g., a physical shared channel) scheduled in each DCI based on a specific time criterion and notification fields of time-related information contained in each DCI (or at least one DCI).

[0087] For example, if the slot offsets K0 / K2 specified in each DCI are the same value (e.g., K0=2), the UE can determine that PDSCH / PUSCH is scheduled for a slot that is K0 / K2 away from a given time reference.

[0088] [Group Common DCI] Criterion A / Criterion B may be applied to the control of transmit / receive processing based on a group common DCI (e.g., group common DCI). The group common DCI may be, for example, DCI format 2_0 (Case 1), DCI format 2_1 (Case 2), DCI format 2_4 (Case 3), or DCI format 2_5 in Rel. 16 and later. Of course, the applicable group common DCI formats are not limited to these.

[0089] Case 1 DCI Format 2_0 is used to notify the slot format. For example, the UE determines the slot format for a given number of slots in a DL BWP / UL BWP (e.g., the transmission direction of each symbol (e.g., UL / DL / flexible)) based on the value of a field in DCI Format 2_0 (e.g., the SFI index field).

[0090] Thus, when multiple DCI format 2_0s are transmitted using PDCCH repetition, the question arises as to where (for example, which slot) the slot format information notified in the DCI format 2_0 should begin.

[0091] Therefore, in this embodiment, when multiple DCI format 2_0s are transmitted using PDCCH repetition (or PDCCHs that are transmitted repeatedly), the UE may control the transmission / reception process based on criterion A / criterion B.

[0092] For example, the UE may control the transmit / receive process by applying / interpreting slot format information notified in DCI format 2_0 based on a specific time criterion (e.g., criterion A / criterion B) (see Figure 4). Figure 4 shows a case in a PDCCH iteration (here, PDCCH#1 (DCI#1) and PDCCH#2 (DCI#2)) where PDCCH#1 (DCI#1) is a specific criterion (e.g., the first iteration PDCCH in criterion A1).

[0093] This allows the UE to correctly determine the slot format even when multiple DCI format 2_0s are repeatedly transmitted.

[0094] Case 2 DCI format 2_1 is used for the notification of resource blocks (e.g., PRBs) and symbols that may be assumed that the UE does not intend to transmit. For example, the UE may determine resource blocks (e.g., PRBs) and symbols for which transmission is not intended based on the information included in DCI format 2_1 (e.g., pre-emption indication). For example, when the UE detects DCI format 2_1, it may assume that there is no transmission to the UE in the set of symbols notified by DCI format 2_1 from the set of PRBs and symbols in the last monitoring period.

[0095] When the UE detects DCI format 2_1 in a PDCCH transmitted in a control resource set within a slot, the set of symbols is the last N symbols before the first symbol of the control resource set within the slot. symb slot ·T INT ·2 μ-μINT symbols. T INT is the PDCCH monitoring period provided by upper layer signaling, N symb slot is the number of symbols per slot, μ is the differential subcarrier spacing configuration (SCS configuration) of the serving cell mapped to each field of DCI format 2_1, μ INT corresponds to the subcarrier spacing configuration of the DL BWP in which the UE receives the PDCCH in DCI format 2_1.

[0096] Thus, when multiple DCI format 2_1s are transmitted using PDCCH repetition, the problem becomes which control resource set to apply / interpret the information notified by DCI format 2_1 based on.

[0097] Therefore, in this embodiment, when multiple DCI format 2_1s are transmitted using PDCCH repetition (or repeatedly transmitted PDCCH), the UE may control transmission processing / reception processing based on reference A / reference B.

[0098] For example, the UE controls the transmission / reception process by applying / interpreting the information notified in DCI format 2_1 based on a specific set of control resources (e.g., criterion B). This allows the UE to properly control the communication even when multiple DCI format 2_1 messages are repeatedly transmitted.

[0099] Case 3 DCI format 2_4 is used to notify PRBs and symbols that cancel the corresponding UL transmission. For example, a UE may determine which PRBs and symbols will cancel the UL transmission based on the information contained in DCI format 2_4 (e.g., a cancellation indication).

[0100] Instructions in DCI format 2_4 may be applied to push transmits / SRS transmits. If a push transmit / SRS transmit is scheduled in DCI format, instructions in DCI format 2_4 will only be applied to a push transmit or SRS transmit if the last symbol of a PDCCH receive corresponding to DCI format is earlier than the first symbol of a PDCCH receive corresponding to DCI format 2_4.

[0101] Alternatively, the UE may control PUSCH transmission / SRS transmission by applying / interpreting the information notified in DCI format 2_4 based on the last timing of PDCCH reception that detected DCI format 2_4 / the last symbol in the control resource set that detected DCI format 2_4 / .

[0102] Furthermore, the UE does not expect to cancel a PUSCH or SRS transmission after the last symbol of the control resource set that detected DCI format 2_4 and before a predetermined symbol.

[0103] Thus, when multiple DCI format 2_4 messages are sent using PDCCH repetitions, the question arises as to which PDCCH repetition / control resource set should be used to apply / interpret the information notified in DCI format 2_4.

[0104] Therefore, in this embodiment, when multiple DCI format 2_4 are transmitted using PDCCH repetition (or PDCCH that is transmitted repeatedly), the UE may control the transmission / reception process based on criterion A / criterion B.

[0105] For example, the UE controls the transmission / reception process by applying / interpreting the information notified in DCI Format 2_4 based on a specific time criterion (e.g., Criterion A / Criterion B). This allows the UE to properly control the communication even when multiple DCI Format 2_4 messages are repeatedly transmitted.

[0106] Separate time standards may be applied to PDCCH reception corresponding to the DCI format for scheduling PUSCH transmission / SRS transmission, and to PDCCH reception corresponding to DCI format 2_4.

[0107] Case 4 DCI Format 2_5 is used to notify the availability of soft resources. For example, a UE may determine which soft resources are available based on the information contained in DCI Format 2_5 (e.g., the Availability Indicator (AI)).

[0108] The use of Integrated Access Backhaul (IAB) technology, which utilizes NR communication as backhaul between base stations (or between base stations and relay stations), is being considered. In particular, IAB using millimeter-wave NR communication is expected to expand coverage areas at low cost.

[0109] An IAB node may have at least one function, such as a DU (Distribution Unit), CU (Central Unit), or MT (Mobile Termination). Therefore, an IAB node may function as a base station or as a user terminal (UE: User Equipment).

[0110] The value of the DCI Format 2_5 Availability Notification (e.g., AI Index) field indicates to the IAB-DU the availability of soft symbols in each slot, starting from the earliest slot in the IAB-DT that temporally overlaps with the slot of the IAB node where the IAB-DU detected DCI Format 2_5. This number of slots is equal to or greater than the PDCCH monitoring period for DCI Format 2_5 provided by the higher-layer parameters for the search space.

[0111] Thus, when multiple DCI format 2_5 messages are transmitted using PDCCH repetition, the question arises as to which slot the DCI format 2_5 message is located.

[0112] Therefore, in this embodiment, when multiple DCI format 2_5 are transmitted using PDCCH repetition (or PDCCH that is transmitted repeatedly), the UE may control the transmission / reception process based on criterion A / criterion B.

[0113] For example, the UE controls the transmission / reception process by applying / interpreting the information notified in DCI Format 2_5 based on a specific time criterion (e.g., Criterion A / Criterion B). This allows the UE to properly control the communication even when multiple DCI Format 2_5 messages are repeatedly transmitted.

[0114] [PDSCH / PUSCH scheduling] Criterion A / Criterion B may be applied to the control of transmit / receive processing based on DCI / PDCCH used in the scheduling operation of PDSCH / PUSCH. The scheduling operation of PDSCH / PUSCH may be resource allocation (e.g., frequency resources) (Case 5), scheduling restrictions on PDSCH (Case 6), or in / out-of-order for PDSCH / PUSCH (Case 7).

[0115] Case 5 PDSCH resource (e.g., RB) allocation is determined based on the control resource set from which the UE receives the DCI. For example, if a PDSCH is scheduled by DCI format 1_0 in a PDCCH common search space of a certain type, resource block numbering (RB numbering) starts with the smallest RB in the control resource set from which the DCI is received, regardless of which bandwidth portion is the active BWP. Otherwise, RB numbering starts with the smallest RB in the determined DL BWP (given BWP).

[0116] Thus, when multiple DCI formats containing frequency domain resource allocation information are transmitted using PDCCH repetition, the question arises as to which DCI (or control resource set) should be used to control resource allocation, for example, which DCI / control resource set's RB should be used to initiate RB numbering.

[0117] Therefore, in this embodiment, when multiple DCI formats containing frequency domain resource allocation information are transmitted using PDCCH repetition (or repeatedly transmitted PDCCH), the UE may control the transmission / reception process (for example, determine the allocated resources) based on criterion A / criterion B.

[0118] For example, a UE may determine frequency-domain resource allocation based on a PDCCH / DCI / control resource set determined on a specific time reference (e.g., Reference A / Reference B). This allows the UE to properly determine the frequency-domain resources of a PDSCH even when multiple DCI formats containing frequency-domain resource-related information for the PDSCH are repeatedly transmitted.

[0119] PUSCH resource (e.g., RB) allocation is determined based on the CCE index of the PDCCH in the DCI detected by the UE. For example, for DCI format 0_0 monitored in a common search space scrambled by an RNTI other than a predetermined RNTI (e.g., TC-RNTI), the upstream RB set may be the upstream RB set with the smallest index among those upstream RB sets that intersect with the CCE of the smallest index of the PDCCH in which the UE detected DCI format 0_0 in the active DL BWP. If there is no intersection, the upstream RB set may be RB set 0 in the active UL BWP.

[0120] When multiple DCI formats containing frequency domain resource allocation information are transmitted using PDCCH repetition, the question arises as to which DCI corresponds to which PDCCH to control resource allocation, for example, which DCI corresponds to which PDCCH and based the RB set on the minimum CCE.

[0121] Therefore, in this embodiment, when multiple DCI formats containing frequency domain resource allocation information are transmitted using PDCCH repetition (or repeatedly transmitted PDCCH), the UE may control the transmission / reception process (for example, determine the allocated resources) based on criterion A / criterion B.

[0122] For example, a UE may determine frequency-domain resource allocation (e.g., RB sets) based on PDCCH / DCI determined on a specific time criterion (e.g., criterion A / criterion B). This allows the UE to properly determine PUSCH's frequency-domain resources even when multiple DCI formats containing frequency-domain resource-related information for PDSCH are repeatedly transmitted.

[0123] Case 6 Depending on the reception timing of the PDCCH scheduling the PDSCH (e.g., in relation to the PDSCH's time allocation), reception of the PDSCH for a given mapping type may be restricted. For example, if the UE receives the first symbol of the PDCCH scheduling the PDSCH at a later time than the first symbol indicated by the PDSCH's time domain resource allocation, it does not expect to receive the PDSCH with mapping type B in the slot.

[0124] Thus, when scheduling a PDSCH using PDCCH iterations, the question arises as to which PDCCH symbol should be used to control resource limits—for example, which PDCCH's first symbol should be compared to the first symbol of the PDSCH's time-domain resource.

[0125] Therefore, in this embodiment, when multiple DCI formats that schedule PDSCH are transmitted using PDCCH repetition (or PDCCH that is transmitted repeatedly) are transmitted, the UE may control the transmission / reception process based on criterion A / criterion B.

[0126] For example, a UE may control the reception of a PDSCH having a predetermined mapping type (e.g., mapping type B) based on the symbol of the PDCCH (the first symbol) determined based on a specific time criterion (e.g., criterion A / criterion B). This allows the UE to properly determine the reception of a PDSCH even when multiple DCI formats used for scheduling PDSCHs are repeatedly transmitted.

[0127] Case 7 The receiving and transmitting processes for PDSCH based on DCI are executed in / out-of-order. In-order processing is when PDSCH / PUSCH transmission and reception are performed in the order of DCI reception, while out-of-order processing is when PDSCH / PUSCH transmission and reception are performed regardless of the DCI reception order. An example of PDSCH receiving and PUSCH transmission processing based on DCI is described below.

[0128] For example, suppose that for two HARQ process IDs in a given scheduled cell, the UE is scheduled to start receiving a first PDSCH beginning with symbol j, starting with a PDCCH ending with symbol i. In this case, the UE does not need to anticipate that a PDSCH beginning earlier than the end of the first PDSCH will be scheduled to be received by a PDCCH ending after symbol i.

[0129] Furthermore, under certain conditions, the UE may control the PDCCH scheduling the PDSCH to decode the PDSCH scheduled by the PDCCH, except in cases where the PDCCH ends at least 14 symbols before the earliest start symbol of the PDSCH that does not have a corresponding PDCCH transmission.

[0130] Furthermore, consider a scenario where, for two HARQ process IDs within a scheduled cell, the UE is scheduled to begin receiving a first PDSCH that starts with symbol j, associated with a PDCCH related to a CORESET pool index value ending with symbol i. In this case, the UE may also be scheduled to receive a PDSCH that starts earlier than the end of the first PDSCH, associated with a different CORESET pool index value ending after symbol i.

[0131] Furthermore, consider a scenario where, for two HARQ process IDs within a scheduled cell, the UE is scheduled to initiate the transmission of a first PUSCH that begins with symbol j, triggered by a PDCCH ending with symbol i. In this case, the UE does not need to anticipate the scheduling of any PUSCH transmissions that begin earlier than the end of the first PUSCH, triggered by a PDCCH ending after symbol i.

[0132] Furthermore, consider a scenario where, for two HARQ process IDs within a scheduled cell, the UE is scheduled to initiate a first PUSCH transmission that begins with symbol j, associated with a CORESET pool index value ending in symbol i. In this case, the UE may also schedule a PUSCH transmission that begins earlier than the end of the first PDSCH, associated with a different CORESET pool index value ending after symbol i.

[0133] Furthermore, the UE may assume that if the end of symbol i is not at least N2 symbols prior to the start of symbol j, then a PDCCH ending with symbol i will not schedule the transmission of a PUSCH in overlapping serving cells during a predetermined transmission occasion. The predetermined transmission occasion may begin with symbol j in the same serving cell. N2 may be a value determined based on the UE's capabilities.

[0134] Furthermore, under certain conditions, the UE may assume that if the gap between the end of the PDCCH of symbol i and the start of the PUSCH transmission of symbol j is N2 symbols or greater, it will terminate the repetition of the transport block in the PUSCH transmission starting from symbol j. The certain conditions may also be that the UE receives an ACK for a predetermined HARQ process in the CG-DFI in the PDCCH ending at symbol i, in order to terminate the repetition of a setting grant-based PUSCH transmission on a predetermined serving cell having the same HARQ process after symbol i.

[0135] Furthermore, under certain conditions, the UE does not have to assume that a PDCCH ending with symbol i is scheduled to send a PUSCH in a serving cell corresponding to a certain HARQ process. The certain conditions may be that there is an opportunity to send a setting grant-based PUSCH having the same HARQ process on the same serving cell, which begins with symbol j after symbol i, and the gap between the ending symbol of the PDCCH and the beginning of symbol j is less than N2 symbols.

[0136] As mentioned above, in PDSCH reception processing and PUSCH transmission processing based on DCI, the UE controls based on PDCCH / DCI (for example, based on time). When using PDCCH repetition to perform PDSCH reception processing and PUSCH reception processing, the question arises as to which PDCCH / DCI to use as the basis for control.

[0137] Therefore, in this embodiment, when controlling PDSCH reception / PUSCH transmission based on in / out-of-order using PDCCH repetition (or repeatedly transmitted PDCCH), the UE may control the transmission / reception process based on criterion A / criterion B. This allows the UE to appropriately control the PDSCH reception process / PUSCH transmission process even when multiple PDCCH / DCI are repeatedly transmitted.

[0138] Case 8 Resources for the uplink control channel (e.g., PUCCH) are determined based on the CCE index corresponding to the PDCCH. For example, if a UE uses PUCCH to send a HARQ-ACK in response to the detection of a DCI format for scheduling PDSCH receive / SPS PDSCH release, the UE will use a predetermined index (r PUCCH Determine the PUCCH resource that has a predetermined index (0≦r). PUCCH ≤15) may also be expressed by the following equation (1).

[0139]

number

[0140] Furthermore, if the size of the resource list for the first set of PUCCH resources is greater than a predetermined value (e.g., 8), the UE will send a HARQ-ACK in response to detecting the last DCI format in the PDCCH iteration, with a predetermined index (r PUCCH Determine the PUCCH resource that has a predetermined index (0≦r). PUCCH ≤R PUCCH -1) may also be expressed by the following equation (2). The transmission of HARQ-ACK may correspond to the transmission of PUCCH in the same slot.

[0141]

number

[0142] Thus, when multiple PDCCH / DCI / control resource sets containing PUCCH resource information (e.g., CCE index information) are transmitted using PDCCH iteration, the question arises as to which PDCCH / DCI / control resource set should be used to determine the PUCCH resource.

[0143] Therefore, in this embodiment, when determining a PUCCH resource corresponding to a PDSCH scheduled using a PDCCH repetition (or a PDCCH that is repeatedly transmitted) (for example, a PUCCH for transmitting a HARQ-ACK corresponding to a PDSCH), the UE may control the transmit / receive process (for example, determine the PUCCH resource) based on criterion A / criterion B. A PUCCH corresponding to a PDSCH scheduled using a PDCCH repetition may be rephrased as a PUCCH triggered using a PDCCH repetition.

[0144] For example, a UE may determine the PUCCH resource based on a PDCCH / DCI / control resource set determined based on a specific time criterion (e.g., Criterion A / Criterion B). Alternatively, a UE may determine the PUCCH resource using a CCE corresponding to a PDCCH / control resource set determined based on a specific time criterion. This allows the UE to properly determine the PUCCH resource even if the PDCCH / DCI / control resource set is transmitted repeatedly.

[0145] Case 9 The resources for the Sounding Reference Signal (SRS) are determined based on the Sounding Reference Indicator (SRI) or a PDCCH having an SRI. For example, the SRI indicated in slot n may be associated with the most recent transmission of the SRS resource identified by the SRI. The SRS resources are positioned / configured before the PDCCH that transmits the SRI.

[0146] Thus, when multiple PDCCH / DCIs containing SRI information are transmitted using PDCCH repetition, the question arises as to which PDCCH / DCI should be used to determine the SRS resource.

[0147] Therefore, in this embodiment, when controlling SRS transmission based on PDCCH repetition (or PDCCH that is repeatedly transmitted), the UE may control the SRS transmission process (e.g., determining the SRS resource) / reception process (e.g., receiving the DCI including the SRI) based on criterion A / criterion B.

[0148] For example, the UE may determine SRS resources based on PDCCH / DCI determined on a specific time criterion (e.g., Criterion A / Criterion B). This allows the UE to properly determine SRS resources even when PDCCH / DCI / control resource sets are repeatedly transmitted.

[0149] Case 10 In intermittent reception (DRX) control, a predetermined timer (e.g., a DRX timer) is controlled based on whether or not a new transmission is notified by the PDCCH. For example, if the PDCCH notifies of a new transmission (DL or UL) on a serving cell of a predetermined DRX group, the UE starts / restarts the timer for that DRX group (e.g., drx-InactivityTimer) in the first symbol after the PDCCH reception ends.

[0150] Thus, when controlling a predetermined timer in DRX control based on a PDCCH transmitted via PDCCH repetition, the question arises as to which PDCCH / DCI should be used to control the predetermined timer (e.g., start / restart).

[0151] Therefore, in this embodiment, when controlling the DRX based on PDCCH repetition (or PDCCH that is repeatedly transmitted), the UE may control the DRX (e.g., timer start / restart) based on reference A / reference B.

[0152] For example, the UE may control the start / restart of a timer in the DRX group (e.g., drx-InactivityTimer) at the first symbol after the end of reception of the PDCCH, which is determined based on a specific time criterion (e.g., criterion A / criterion B).

[0153] Case 11 Bandwidth portion (BWP) changes / switching / transitions are controlled based on the reception timing of PDCCH / DCI. For example, if a UE detects a DCI format indicating a change in the active DL BWP (DL BWP change) of a cell, the UE does not need to be requested to receive or transmit in the cell between the end of the third symbol of the slot in which the UE receives the PDCCH containing the DCI format in the scheduling cell and the start of the slot indicated by the slot offset value in the time domain resource allocation field of the DCI format.

[0154] Furthermore, if the UE detects a DCI format indicating an active UL BWP change in a cell, the UE does not need to be requested to receive or transmit in the cell from the end of the third symbol of the slot in which the UE receives the PDCCH containing the DCI format in the scheduling cell until the start of the slot indicated by the slot offset value in the time domain resource allocation field of the DCI format.

[0155] Thus, when controlling BWP changes / switching / transitions based on PDCCH transmitted via PDCCH repetition, the question arises as to which PDCCH / DCI should be used as the basis for control.

[0156] Therefore, in this embodiment, when controlling BWP changes / switching / transitions based on PDCCH repetition (or PDCCH that is repeatedly transmitted), the UE may control based on the PDCCH determined based on criterion A / criterion B.

[0157] For example, the UE may control the change / switching / transition of the BWP based on the PDCCH, which is determined based on a specific time criterion (e.g., Criterion A / Criterion B).

[0158] Case 12 The resources used by a PDSCH are restricted depending on whether they overlap with resources in the control resource set corresponding to the PDCCH / DCI that schedules the PDSCH. For example, if a PDSCH scheduled by a PDCCH overlaps with resources in the control resource set that includes the PDCCH, the resources corresponding to the PDCCH that scheduled the PDSCH (e.g., a PDCCH detected by the UE) and the associated DMRS for the PDCC cannot be used for the PDSCH.

[0159] Thus, in cases where there are multiple PDCCH candidates for a PDCCH repeat, if some PDCCH repeats are not detected by the UE, the question arises whether all PDCCH candidates for the PDCCH repeats are unusable for PDSCH, or whether only the detected PDCCHs are unusable for PDSCH.

[0160] In this embodiment, if a PDCCH scheduled by a PDCCH overlaps with a resource in the control resource set that includes the PDCCH repeat, either option 12-1 or option 12-2 below may be applied.

[0161] [Option 12-1] The UE may determine / assume that the resources corresponding to the PDCCH that scheduled the PDSCH (e.g., a PDCCH detected by the UE) and the associated DMRS union for the PDCCH will not be used for the PDSCH and control accordingly.

[0162] [Option 12-2] The UE may control resources corresponding to a PDCCH that scheduled a PDSCH (e.g., a PDCCH detected by the UE) and its associated DMRS for that PDCCH, so that they are not used for the PDSCH. Furthermore, the UE may determine / assume that resources corresponding to a candidate PDCCH associated with a PDCCH detected as a PDCCH repeat, and its associated DMRS for that PDCCH, will not be used for the PDSCH.

[0163] The association between PDCCH candidates / control resource sets / PDCCH iteration search space sets may be defined in the specification or configured by the base station to the UE through higher-layer signaling, etc.

[0164] Case 13 A MAC entity (e.g., UE) monitors PDCCH occasions, for example, in DRX control, but does not need (or is not required) to monitor PDCCH if it is not a complete PDCCH occasion. A case of not being a complete PDCCH occasion may be, for example, when the Active Time starts / stops in the middle of a PDCCH occasion.

[0165] Thus, in the case of PDCCH iterations, if the active time starts / stops in the middle of two PDCCH iterations, the question arises whether the MAC entity needs to monitor the PDCCH occasions (or how to control the monitoring).

[0166] In this embodiment, in DRX control, when a PDCCH repetition is applied, if the PDCCH repetition is not a complete PDCCH repetition, at least one of the following options 13-1 to 13-4 may be applied. A case where the PDCCH repetition is not a complete PDCCH repetition is, for example, when the active time starts / stops in the middle of the PDCCH repetition.

[0167] [Option 13-1] The MAC entity may be configured not to monitor all PDCCH repeats (or not to require monitoring all PDCCH repeats) (see Figure 5). Figure 5 shows a case where active time starts / stops between the occasions of PDCCH repeat #1 and PDCCH repeat #2. In this case, the MAC entity may be configured not to require monitoring of PDCCH during the occasions of PDCCH repeat #1 and PDCCH repeat #2.

[0168] [Option 13-2] The MAC entity may be configured to monitor all PDCCH repeats (or be required to monitor all PDCCH repeats) (see Figure 5). In Figure 5, the MAC entity may be configured to require monitoring of PDCCH in the occasions of PDCCH repeat #1 and PDCCH repeat #2.

[0169] [Option 13-3] The MAC entity may be configured to monitor PDCCH repetitions after the active time has started / stopped (or to only monitor PDCCH repetitions after the active time has started / stopped) (see Figure 5). In Figure 5, the MAC entity may be configured so that monitoring of PDCCH is not required in the occasion of PDCCH repetition #1, but monitoring of PDCCH is required in the occasion of PDCCH repetition #2.

[0170] [Option 13-4] The MAC entity may be configured to monitor PDCCH repetitions before the active time starts / stops (or to only monitor PDCCH repetitions before the active time starts / stops) (see Figure 5). In Figure 5, the MAC entity may be configured to require monitoring of PDCCH in the occasion of PDCCH repetition #1, but not in the occasion of PDCCH repetition #2.

[0171] [Variations] The application of separate options may be supported / allowed for cases where the active time starts in the middle of a PDCCH repetition and cases where the active time stops in the middle of a PDCCH repetition. This allows for more flexible control of monitoring the PDCCH repetition.

[0172] The association between PDCCH candidates / control resource sets / PDCCH iteration search space sets may be defined in the specification or configured by the base station to the UE through higher-layer signaling, etc.

[0173] (UE capability information) The UE may report to the base station as UE capability information whether or not it supports PDCCH repetition. For example, the UE may report to the base station whether or not it supports the multiplexing schemes (TDM / SDM / FDM) applicable to PDCCH repetition.

[0174] The UE may report to the base station whether it supports inter-slot, intra-slot, or intra-mini-slot PDCCH repetitions for PDCCH repetitions transmitted in different time domains (TDM PDCCH repetitions).

[0175] Furthermore, the UE may report its capability regarding the number of repetitions (e.g., the maximum number) to the base station. The maximum number of repetitions may be set separately for multiple multiplexing schemes (TDM / SDM / FDM) or it may be set commonly for all of them.

[0176] The UE may report whether it supports cases where the DCI payload content is the same or different in repeated PDCCHs (e.g., inter-slot / intra-slot / intra-mini-slot TDM PDCCH repetitions).

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

[0178] The UE may report to the base station whether or not it supports PDCCH repetition with soft combining. Alternatively, the UE may report to the base station whether or not it supports PDCCH repetition without soft combining.

[0179] The base station may control the repeated transmission of PDCCH based on capability information reported by the UE. The base station may also notify / set the UE of the aforementioned UE capability information using higher-layer signaling or the like.

[0180] Furthermore, this embodiment may be applied to multi-chance PDCCH transmissions. For example, DCIs that schedule the same PDSCH / PUSCH / RS / TB etc. may be distinguished from DCIs that produce the same outcome.

[0181] (Related information / configuration information for PDCCH repetition) Information / configuration information regarding PDCCH repetition transmission may also be transmission conditions / transmission parameters applied to PDCCH repetition transmission. The transmission conditions / transmission parameters applied to PDCCH repetition transmission may be at least one of the PDCCH repetition number (e.g., PDCCH repetition number), the time interval to which PDCCH repetition is applied, and the interval / offset between each PDCCH in PDCCH repetition transmission.

[0182] A PDCCH to which repeated transmission is applied (e.g., a multi-PDCCH) may be transmitted from multiple TRPs. A multi-PDCCH (or a PDCCH transmitted from different TRPs) may be subject to different QCLs (or TCIs, beams). In this disclosure, repeated PDCCH transmission is applicable to cases where the PDCCH is transmitted from one or more TRPs.

[0183] Information regarding PDCCH repetition transmissions (e.g., PDCCH repetition count) may be notified / configured to the UE from the network (e.g., base station). Information regarding PDCCH repetition transmissions may be notified / configured to the UE based on at least one of the following options 1-A to 1-B.

[0184] <Option 1-A> Information regarding PDCCH repetition transmissions may be communicated / configured from the base station to the UE using higher-layer signaling (e.g., RRC parameters and at least one of MAC CEs).

[0185] <Option 1-B> Information regarding PDCCH repetition transmissions may be dynamically communicated from the base station to the UE using downlink control information (e.g., DCI). Information regarding PDCCH repetition transmissions may be communicated using a new field set in the DCI, or using a field set in an existing system.

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

[0187] The size (e.g., number of bits) of the field used to notify information about repeated transmissions may be determined based on the maximum number of PDCCH repeats. The UE may determine the maximum number of PDCCH repeats based on capability information reported by the UE (e.g., UE capability).

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

[0189] Whether or not notification of the PDCCH repetition count using DCI is applied may be determined by predetermined upper-layer signaling. The UE may assume that a field for notifying the PDCCH repetition count exists in DCI if predetermined upper-layer signaling is set, and that a field for notifying the PDCCH repetition count does not exist in DCI if predetermined upper-layer signaling is not set.

[0190] Thus, when applying PDCCH repeat transmission, the base station notifies / configures information regarding PDCCH repeat transmission to the UE, allowing the UE to properly understand the transmission conditions / transmission parameters applied to PDCCH repeat transmission.

[0191] (PDCCH iterative control corresponding to the common search space) When repeated transmissions are applied to a downlink control channel (or CORESET / downlink control channel candidate / search space / search space set) used for transmitting a DCI common to the UE (or a DCI transmitted using the common search space set), the UE may apply at least one of the following first to fifth embodiments:

[0192] The first to fifth embodiments may be applied to DCI formats that utilize a common search space set. The DCI format may be, for example, DCI format 2_0 / 2_1 / 2_4 / 2_5 or other DCI formats. The common search space set (e.g., CSS PDCCH) may be, for example, type 0 / 0A / 1 / 2 / 3-PDCCH CSS set.

[0193] The first to fifth embodiments may be applied separately, or some or all of them may be applied in combination. Furthermore, the first to fifth embodiments may be applied separately from the above cases 1 to 13, or some or all of them may be applied in combination.

[0194] <First aspect> The first aspect describes how to set the aggregation level and the number of PDCCH candidates for one or more search spaces (e.g., linked SS sets) applied / configured for a PDCCH iteration. The aggregation level may correspond to the aggregation level of the CCE (Control Channel Element).

[0195] The following explanation uses the example of two associated / linked search space sets, but there may be three or more linked search space sets.

[0196] For a given DCI format (e.g., DCI format 2_0 / 2_4 / 2_5), a search space set and a corresponding CORESET are set by a higher-level parameter (e.g., SearchSpace). Furthermore, this higher-level parameter sets the aggregation level for the search space set and the number of PDCCH candidates for each aggregation level (see Figure 6).

[0197] Figure 6 shows an example of a higher-level parameter (e.g., SearchSpace) used to configure the search space in an existing system (e.g., Rel.15 / 16). When Common is set as the search space type by the higher-level parameter, the number of PDCCH candidates for each aggregation level is set for a given DCI format (here, DCI formats 2_0, 2_4, 2_5).

[0198] Assume that multiple (e.g., two) related / linked search space sets (SS sets) are supported for a PDCCH repeat (or when a PDCCH repeat is applied / configured) (see Figure 7). Figure 7 shows the case where a first search space set (SS set #1) corresponding to a first PDCCH #1 is linked to a second search space set (SS set #2) corresponding to a second PDCCH #2.

[0199] In this case, the multiple search space sets / CORESETs to be linked may be configured based on at least one of Alt.1-1 and Alt.1-2 below.

[0200] [Alt.1-1] For a given DCI format (e.g., DCI format 2_0 / 2_4 / 2_5), two linked search space sets may have the same aggregation level (see Figure 8). Alternatively, the two linked search space sets may have the same number of PDCCH candidates for each aggregation level. A search space set may be interpreted as a CORESET.

[0201] In other words, when PDCCH repetition is applied / configured, the aggregation level / number of PDCCH candidates per aggregation level may be set to be the same for multiple search space sets.

[0202] The UE does not need to assume that different aggregation levels are set for two search space sets (e.g., linked SS sets) configured for a PDCCH iteration. Alternatively, the UE does not need to assume that the number of PDCCH candidates corresponding to each aggregation level is different for two search space sets (e.g., linked SS sets) configured for a PDCCH iteration.

[0203] If two search space sets (search space IDs) are set in the higher-level parameters, the aggregation level and the number of PDCCH candidates per aggregation level corresponding to each search space ID may be set to the same value.

[0204] Thus, when PDCCH repeated transmission is applied, setting a common search space / number of PDCCH candidates for each PDCCH suppresses the increase in overhead of higher-layer parameters and reduces the load on the UE's monitoring process.

[0205] [Alt.1-2] For a given DCI format (e.g., DCI format 2_0 / 2_4 / 2_5), the two linked search space sets may be set to the same aggregation level or different aggregation levels. Also, for the two linked search space sets, the same number or different numbers of PDCCH candidates may be set for each aggregation level. The search space set may be read as a CORESET.

[0206] That is, when PDCCH repetition is applied / set, the aggregation level / number of PDCCH candidates for each aggregation level may be set separately for multiple search space sets.

[0207] When two search space sets (search space IDs) are set by upper layer parameters, the aggregation level / number of PDCCH candidates for each search space ID may be set separately (e.g., to different values).

[0208] In each search space set, if the number of PDCCH candidates is different, for example, the first search space set may correspond to X PDCCH candidates and the second search space set may correspond to Y candidates (X≠Y). If X < Y, the X PDCCH candidates corresponding to the first search space set may be included in the Y PDCCH candidates corresponding to the second search space set. In this case, the X PDCCH candidates corresponding to the first search space set may be linked one-to-one with the first X PDCCH candidates corresponding to the second search space set.

[0209] In this way, when PDCCH repeated transmission is applied, by enabling separate setting of the search space / number of PDCCH candidates corresponding to each PDCCH, flexible control of PDCCH repetition can be achieved.

[0210] <Second aspect> In the second aspect, when a PDCCH repetition is applied / configured, the case in which one of several PDCCHs is used as the reference / reference is determined based on predetermined conditions.

[0211] When PDCCH repetition is applied / configured, multiple related / linked coresets / multiple PDCCH candidates / multiple search spaces / multiple search space sets may be configured. In this case, it may be determined, based on predetermined rules, which of the linked coresets / multiple PDCCH candidates / multiple search spaces / multiple search space sets will be referenced / used as the basis.

[0212] DCI format 2_4 (e.g., the first DCI format) is used by the UE to notify the PRB and OFDM symbols that cancel the corresponding UL transmission. If the UE cancels a PUSCH transmission / SRS transmission based on the instructions in DCI format 2_4, the UE does not expect / expect, by the second DCI format, that the PUSCH transmission / SRS transmission will be scheduled on a symbol containing the symbol of the canceled PUSCH transmission / SRS transmission. Here, the last symbol of the second PDCCH reception providing the second DCI format (or used to transmit the second DCI format) is placed after (or later than) the first symbol of the first PDCCH reception providing DCI format 2_4 (see Figure 9).

[0213] The second DCI format may be a DCI format that schedules PUSCH transmissions / SRS transmissions (for example, DCI format 0_0 / 0_1 / 0_2).

[0214] When repeated transmission is applied / configured / supported for at least one of the first PDCCH and the second PDCCH used for DCI format 2_4 transmission, the question arises as to which PDCCH (or PDCCH candidate) from among multiple PDCCHs (or multiple linked PDCCH candidates) should be referenced / used as the basis.

[0215] Therefore, the reference PDCCH / reference PDCCH may be determined based on at least one of the following: whether or not repeated transmission is applied to / configured for the first PDCCH, and whether or not repeated transmission is applied to / configured for the second PDCCH.

[0216] If repeated transmission is applied / configured to a second PDCCH#2 that provides a second DCI format #2 (see Figure 10), the reference second PDCCH (or PDCCH candidate) among multiple PDCCHs (or multiple linked PDCCH candidates) may be determined based on the following predetermined rules (for example, at least one of Alt.2-1-1 to Alt.2-1-5). Note that PDCCH may be read as PDCCH candidate.

[0217] Alt.2-1-1: Of multiple (e.g., 2) PDCCHs linked in the time domain, the PDCCH that terminates the latest in time. Alt.2-1-2: Of multiple (e.g., two) PDCCHs linked in the time domain, the PDCCH that terminates earliest in time. Alt.2-1-3: Of multiple (e.g., 2) PDCCHs linked in the time domain, the PDCCH that starts the latest in time. Alt.2-1-4: Of multiple (e.g., two) PDCCHs linked in the time domain, the PDCCH that starts earliest in time. Alt.2-1-5: PDCCH with relatively high (or low) searchspace set ID / CORESET pool ID / TCI state ID

[0218] If repeated transmission is applied / configured to a first PDCCH#1 that provides a first DCI format #1 (e.g., DCI format 2_4) (see Figure 10), a second PDCCH (or PDCCH candidate) that serves as the basis for a reference among multiple PDCCHs (or multiple linked PDCCH candidates) may be determined based on the following predetermined rules (e.g., at least one of Alt.2-2-1 to Alt.2-2-5). Note that PDCCH may be read as PDCCH candidate.

[0219] Alt.2-2-1: Of multiple (e.g., 2) PDCCHs linked in the time domain, the PDCCH that terminates the latest in time. Alt.2-2-2: Of multiple (e.g., two) PDCCHs linked in the time domain, the PDCCH that terminates earliest in time. Alt.2-2-3: Of multiple (e.g., two) PDCCHs linked in the time domain, the PDCCH that starts the latest in time. Alt.2-2-4: Of multiple (e.g., two) PDCCHs linked in the time domain, the PDCCH that starts earliest in time. Alt.2-2-5: PDCCH with relatively high (or low) searchspace set ID / CORESET pool ID / TCI state ID

[0220] Repeat transmission may be applied to only one of the first PDCCH or the second PDCCH, or a configuration in which repeat transmission is applied to both the first PDCCH and the second PDCCH may be supported.

[0221] The prescribed rules used to determine the reference PDCCH when repeated transmission is applied to the first PDCCH and the prescribed rules used to determine the reference PDCCH when repeated transmission is applied to the second PDCCH may be the same or different.

[0222] For example, consider a case where PDCCH repetitions are set in both the first and second PDCCH, and Alt.2-1-1 and Alt.2-2-4 (different predetermined rules) are applied.

[0223] In this case, if the UE cancels a PUSCH transmit / SRS transmit based on the instructions of the first DCI format (e.g., DCI format 2_4), the UE does not need to assume / expect, by the second DCI format, that the PUSCH transmit / SRS transmit will be scheduled on a symbol containing the symbol of the canceled PUSCH transmit / SRS transmit. Here, for a second PDCCH receiver providing the second DCI format, the last symbol of the time-last ending PDCCH candidate among the two linked PDCCH candidates in the time domain is placed after (or later than) the first symbol of the time-first starting PDCCH candidate among the two linked PDCCH candidates in the time domain for a first PDCCH receiver providing DCI format 2_4.

[0224] In this way, the reference PDCCH (or PDCCH candidate) is determined based on at least one of the following: whether or not repeated transmission is applied to / configured for the first PDCCH, and whether or not repeated transmission is applied to / configured for the second PDCCH. Furthermore, if repeated transmission of a PDCCH is applied / configured, the reference PDCCH (or PDCCH candidate) is determined based on predetermined rules. This makes it possible to appropriately control the reception of a PDCCH (or the monitoring / detection of PDCCH candidates) even when repeated transmission is applied to a PDCCH.

[0225] <Third aspect> In the third aspect, a control method is described for when a random access procedure (e.g., a 4-step / 2-step random access procedure) supports PDCCH repetitions.

[0226] In a four-step random access procedure, if the UE sends a PRACH, in response to the PRACH transmission, the UE operates to detect a DCI format (e.g., DCI format 1_0) scrambled by RA-RNTI within a predetermined window / period. The predetermined window / period may be set / notified by upper-layer signaling.

[0227] The predetermined window begins after the last symbol of the PRACH occasion corresponding to the PRACH transmission, with the first symbol of the earliest CORESET (at least one symbol) configured to receive a PDCCH of type 1-PDCCH CSS set (see Figure 11).

[0228] Alternatively, in a two-step random access procedure, if the UE sends PRACH / PUSCH (Message A), in response to the PRACH / PUSCH transmission (or in response to the PRACH transmission only if the PRACH preamble is mapped to a valid PUSCH occasion), the UE operates to detect a DCI format (e.g., DCI format 1_0) scrambled by MsgB-RNTI within a predetermined window / period. The predetermined window / period may be set / notified by higher-layer signaling.

[0229] The predetermined window begins after the last symbol of the PUSCH occasion corresponding to the PRACH transmission, with the first symbol of the earliest CORESET (at least one symbol) configured to receive a PDCCH of type 1-PDCCH CSS set.

[0230] Alternatively, in a two-step random access procedure, if the UE sends PRACH (Message A) and the PRACH preamble is not mapped to a valid PUSCH occasion, in response to the PRACH transmission, the UE operates to detect a DCI format (e.g., DCI format 1_0) scrambled by MsgB-RNTI within a predetermined window / period. The predetermined window / period may be set / notified by higher-layer signaling.

[0231] The predetermined window begins after the last symbol of the PRACH occasion corresponding to the PRACH transmission, with the first symbol of the earliest CORESET (at least one symbol) configured to receive a PDCCH of type 1-PDCCH CSS set.

[0232] When PDCCH repetition transmission is applied / configured / supported for a Type 1 PDCCH, the question arises as to which of the multiple PDCCHs (or linked PDCCH candidates / CORESETs) should be used as the reference / reference.

[0233] Therefore, the reference PDCCH / reference PDCCH may be determined based on whether PDCCH repetition transmission is applied / configured for Type 1-PDCCH.

[0234] Assume that repeated transmissions are applied / configured to a PDCCH (e.g., a PDCCH for a Type 1-PDCCH common search space set) that provides a DCI format to attempt detection in response to a PRACH transmission (see Figure 12). In this case, the reference PDCCH (or CORESET / PDCCH candidate) may be determined based on the following predetermined rules (e.g., at least one of Alt.3-1 to Alt.3-5).

[0235] Alt.3-1: Of the multiple (e.g., 2) CORESET / PDCCH candidates linked in the time domain, the CORESET / PDCCH candidate that terminates the latest in time. Alt.3-2: Among multiple (e.g., 2) CORESET / PDCCH candidates linked in the time domain, the CORESET / PDCCH candidate that terminates earliest in time. Alt.3-3: Of the multiple (e.g., two) CORESET / PDCCH candidates linked in the time domain, the CORESET / PDCCH candidate that starts the latest in time. Alt.3-4: Of the multiple (e.g., 2) CORESET / PDCCH candidates linked in the time domain, the CORESET / PDCCH candidate that starts earliest in time. Alt.3-5: CORESET / PDCCH candidates with relatively high (or low) Searchspace Set ID / CORESET ID / CORESET Pool ID / TCI State ID

[0236] For example, consider a case where a PDCCH iteration is set for a Type 1-PDCCH common search space set, and Alt.3-3 is applied.

[0237] In this case, if the UE sends a PRACH in the 4-step random access procedure, in response to the PRACH transmission, the UE operates to detect a DCI format (e.g., DCI format 1_0) scrambled by RA-RNTI within a predetermined window / period. The predetermined window / period may be set / notified by upper-layer signaling.

[0238] Also, the predetermined window starts from the first symbol of the earliest CORESET (at least 1 symbol) that is set to receive the PDCCH of the type 1-PDCCH CSS set after the last symbol of the PRACH occasion corresponding to the PRACH transmission. If the earliest CORESET is linked to other CORESETs for repeated transmission, the predetermined window may start from the first symbol of the CORESET (here, CORESET #2) that starts later in time among the two linked CORESETs (see FIG. 13).

[0239] Thus, the reference PDCCH (or CORESET) is determined based on whether repeated transmission is applied / set for the PDCCH of the type 1-PDCCH CSS set. Also, when PDCCH repeated transmission is applied / set, the reference PDCCH (or CORESET) is determined based on a predetermined rule. Thereby, even when PDCCH repeated transmission is applied, it becomes possible to appropriately control the reception of the PDCCH (or the monitoring of PDCCH candidates / detection of DCI).

[0240] The third aspect may also be applied when PDCCH repeated transmission (or a plurality of linked PDCCH candidates / a plurality of linked CORESETs) is applied / set. For example, the UE may be controlled to apply the third aspect based on RRC / MAC CE / DCI settings / instructions. Alternatively, the UE may apply the third aspect when a plurality (for example, two) of CORESET / search space sets are set for the PDCCH of the type 1-PDCCH common search space and are linked for PDCCH repeated transmission.

[0241] Alternatively, the UE may apply the third aspect when the CORESET / search space set set for the PDCCH of the type 1-PDCCH common search space is set / notified as being linked / related to other CORESET / search space sets.

[0242] <Fourth Aspect> In the fourth aspect, a control method is described for random access procedures that utilize the PDCCH order (for example, non-collision 4-step / 2-step random access procedures) when PDCCH repetitions are supported.

[0243] When a PRACH transmission is triggered by a PDCCH order, the UE will send a PRACH transmission and attempt to detect the DCI format in response to that PRACH transmission. Specifically, the UE will operate to detect the CRC-scrambled DCI format (e.g., DCI format 1_0) by RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a non-collision random access procedure to the SpCell.

[0244] In this case, the UE may assume that the PDCCH containing the DCI format (e.g., a second PDCCH) and the PDCCH order (e.g., a first PDCCH) have the same pseudo-collocation characteristics (e.g., DMRS antenna port pseudo-collocation characteristics) (see Figure 14).

[0245] For example, when a UE detects the DCI format in response to a PRACH transmission, it may perform reception processing assuming that the second PDCCH used to transmit the DCI format is a PDCCH order (first PDCCH) and a QCL.

[0246] If repeated transmission is applied / configured / supported for at least one of the PDCCH orders (e.g., the first PDCCH) and the second PDCCH, the question arises as to which of the multiple PDCCHs (or linked PDCCH candidates / CORESETs) should be used as the reference / criteria for determining the QCL.

[0247] Therefore, the PDCCH to be referenced in the QCL decision may be determined based on at least one of the following: whether or not repeated transmission is applied to / configured for the first PDCCH, and whether or not repeated transmission is applied to / configured for the second PDCCH (see Figure 15).

[0248] ≪When repeated transmission is applied / configured for both PDCCHs≫ Assume that repeated transmissions are applied to both the PDCCH order (first PDCCH) and the second PDCCH, which provides a DCI format to attempt detection in response to a PRACH transmission. In such a case, at least one of Alt.4-1-0 to Alt.4-1-2 below may apply.

[0249] [Alt.4-1-0] The configuration may be one in which repeated transmission is not applied / configured to both the first and second PDCCH. The UE does not need to anticipate the case in which repeated transmission is applied / configured to both the first and second PDCCH.

[0250] For example, the UE does not need to assume that PDCCH repetition transmission is applied to a PDCCH containing DCI format 1_0 (the second PDCCH). Alternatively, the UE does not need to assume that PDCCH repetition transmission is applied to a PDCCH order (the first PDCCH).

[0251] [Alt.4-1-1] The UE may assume that multiple (e.g., two) linked PDCCH candidates / CORESETs corresponding to a second PDCCH and multiple (e.g., two) linked PDCCH candidates / CORESETs corresponding to a PDCCH order (first PDCCH) each have the same pseudo-collocation characteristics for the DMRS antenna port.

[0252] For example, among the linked PDCCH candidates / CORESETs corresponding to the second PDCCH#2, the PDCCH candidates / CORESETs that start / end earlier (or later) in time may have the same QCL as the linked PDCCH candidates / CORESETs corresponding to the PDCCH order that start / end earlier (or later) in time (see Figure 16).

[0253] Alternatively, a linked PDCCH candidate / CORESET corresponding to a second PDCCH that has a relatively high (or low) search space set ID / CORESET ID / CORESET pool ID may have the same QCL as a linked PDCCH candidate / CORESET corresponding to a PDCCH order that has a relatively high (or low) search space set ID / CORESET ID / CORESET pool ID.

[0254] [Alt.4-1-2] The UE may assume that one of several (e.g., two) linked PDCCH candidates / CORESETs corresponding to a second PDCCH and one of several (e.g., two) linked PDCCH candidates / CORESETs corresponding to a PDCCH order (first PDCCH) each have the same pseudo-collocation characteristics for the same DMRS antenna port.

[0255] One of the linked PDCCH candidates / CORESETs may be determined by applying the predetermined rules shown in the third aspect. For example, a reference / criteria PDCCH candidate / CORESET determined based on at least one of Alt.3-1 to Alt.3-5 shown in the third aspect may be selected as the one PDCCH candidate / CORESET. Note that different predetermined rules (e.g., Alt) may be applied to the first PDCCH (e.g., PDCCH order) and the second PDCCH.

[0256] In Alt.4-1-1 / Alt.4-1-2, a plurality of linked PDCCH candidates / CORESETs corresponding to the first PDCCH (e.g., PDCCH order) may have the same DMRS antenna port quasi-collocation characteristics. Also, a plurality of linked PDCCH candidates / CORESETs corresponding to the second PDCCH may have the same DMRS antenna port quasi-collocation characteristics.

[0257] [[When repeated transmission is applied / set to the first PDCCH]] Assume that repeated transmission is applied to the PDCCH order (the first PDCCH), and repeated transmission is not applied to the second PDCCH that provides a DCI format for attempting detection in response to PRACH transmission. The second PDCCH may be a single transmission. In such a case, at least one of the following Alt.4-2-0 to Alt.4-2-2 may be applied.

[0258] [Alt.4-2-0] It may be configured such that repeated transmission is not applied / set to the first PDCCH. The UE may not assume a case where repeated transmission is applied / set to the first PDCCH.

[0259] [Alt.4-2-1] The UE may assume that the second PDCCH (the PDCCH including DCI format 1_0) and a plurality (e.g., two) of linked PDCCH candidates / CORESETs corresponding to the PDCCH order have the same DMRS antenna port quasi-collocation characteristics (see FIG. 17). That is, it may be assumed that the second PDCCH with single transmission is QCL with a plurality of first PDCCHs (or, CORESET / PDCCH candidates) to which repeated transmission is applied. In this case, it may mean that the repetition of the PDCCH (e.g., a plurality of first PDCCHs) has the same QCL.

[0260] [Alt.4-2-2] The UE may assume that a second PDCCH (a PDCCH containing DCI format 1_0) and a specific one of several (e.g., two) linked PDCCH candidates / CORESETs corresponding to the PDCCH order have the same pseudo-collocation characteristics for the same DMRS antenna port. In other words, a second PDCCH that is single-transmit may be assumed to be QCL with one of several first PDCCHs (or CORESET / PDCCH candidates) to which repeated transmission is applied. In this case, the same QCL may be applied to the PDCCH repetitions (e.g., several first PDCCHs), or different QCLs may be applied.

[0261] One particular PDCCH candidate / CORESET among several (e.g., two) linked PDCCH candidates / CORESETs corresponding to a PDCCH order may be determined by applying the predetermined rules shown in the third aspect. For example, a reference / criteria PDCCH candidate / CORESET determined based on at least one of Alt.3-1 to Alt.3-5 shown in the third aspect may be selected as that one PDCCH candidate / CORESET.

[0262] ≪When repeated transmission is applied / configured for the second PDCCH≫ Assume that repeated transmissions are applied to a second PDCCH that provides a DCI format to attempt detection in response to a PRACH transmission, but not to the PDCCH order (first PDCCH). The first PDCCH may be a single transmission. In such a case, at least one of Alt.4-3-0 to Alt.4-3-2 below may apply.

[0263] [Alt.4-3-0] The configuration may be one in which repeated transmission is not applied / configured to the second PDCCH. The UE does not need to anticipate the case in which repeated transmission is applied / configured to the second PDCCH.

[0264] [Alt.4-3-1] The UE may assume that multiple (e.g., two) linked PDCCH candidates / CORESETs corresponding to a second PDCCH (a PDCCH containing DCI format 1_0), along with the PDCCH order, have the same pseudo-collocation characteristics for the DMRS antenna port (see Figure 18). In other words, it may be assumed that multiple second PDCCHs (or CORESETs / PDCCH candidates) to which repeated transmission is applied become the same QCL as the first PDCCH that is single-transmitted. In this case, it may mean that the repetitions of the PDCCH (e.g., multiple second PDCCHs) are the same QCL.

[0265] [Alt.4-3-2] The UE may assume that one of several (e.g., two) linked PDCCH candidates / CORESETs corresponding to a second PDCCH (a PDCCH containing DCI format 1_0), along with the PDCCH order, has the same pseudo-collocation characteristics for the same DMRS antenna port. In other words, one of several second PDCCHs (or CORESETs / PDCCH candidates) to which repeated transmissions are applied may be assumed to be a second PDCCH and QCL that are single-transmit. In this case, the same QCL may be applied to the PDCCH repetitions (e.g., multiple second PDCCHs), or different QCLs may be applied.

[0266] One particular PDCCH candidate / CORESET among several (e.g., two) linked PDCCH candidates / CORESETs corresponding to a second PDCCH may be determined by applying the predetermined rules shown in the third aspect. For example, a reference / criteria PDCCH candidate / CORESET determined based on at least one of Alt.3-1 to Alt.3-5 shown in the third aspect may be selected as that one PDCCH candidate / CORESET.

[0267] For each of the above cases, UE capability may be defined to determine whether the first PDCCH, which is a second PDCCH / PDCCH order including DCI format 1_0, is a PDCCH repeat.

[0268] <Fifth aspect> A fifth aspect describes how to configure multiple linked search space sets corresponding to (or configured for) each PDCCH to which repeated transmissions apply. The fifth aspect may apply, for example, to a common search space (e.g., type 0 / 0A / 1 / 2 PDCCH-CSS).

[0269] If repeated transmission to PDCCH is applied / configured / supported, multiple (e.g., two) linked search space sets may be configured. Multiple linked search space sets may have the same search space set type (e.g., UE-specific SS search space (USS) / common search space (CSS)). Multiple linked search space sets may correspond to the same DCI format.

[0270] When PDCCH repetition is performed within a slot (e.g., intra-slot PDCCH repetition), multiple search space sets may have the same period (e.g., period), the same offset (e.g., offset), and the same duration (e.g., duration). The period and offset may be set by higher-layer parameters (e.g., monitoringSlotPeriodicityAndOffset).

[0271] Multiple PDCCH candidates may be linked and configured across multiple search space sets. A number of linked search space sets may have the same number of PDCCH candidates configured for each aggregation level.

[0272] In existing systems (e.g., Rel.16 and earlier), the search space set corresponding to type 0-PDCCH (e.g., a PDCCH that schedules a PDSCH containing SIB1) is set by a first higher-level parameter (e.g., SearchSpaceZero). Furthermore, the CORESET corresponding to type 0-PDCCH (e.g., a CORESET for a PDCCH that schedules a PDSCH containing SIB1) is set by a second higher-level parameter (e.g., ControlResourceSetZero).

[0273] The UE determines the CORESET corresponding to a type 0-PDCCH search space set based on the association between the index (entry candidate) which may be indicated by a second higher-layer parameter and the resource block and symbol set of the CORESET (for example, the table in Figure 19A).

[0274] Furthermore, the UE determines the parameters for the PDCCH monitoring occasion corresponding to the type 0-PDCCH search space set based on the association (for example, the table in Figure 19B) between the index (entry candidate) that may be indicated by the first higher-layer parameter and the number of search spaces and starting symbol index per slot.

[0275] The question is whether the first higher-level parameter (e.g., SearchSpaceZero) can be set in relation to / linked with other search space sets, and if so, how to control this setting. Alternatively, the question is whether the second higher-level parameter (e.g., ControlResourceSetZero) can be set in relation to / linked with other CORESETs, and if so, how to control this setting.

[0276] Furthermore, in existing systems (e.g., Rel.15 / 16), the search space set for a common search space is configured by a higher-level parameter that indicates the search space ID.

[0277] Search space sets corresponding to type 0-PDCCH are supported to be configured by a higher-layer parameter (e.g., searchSpaceSIB1) that indicates the search space ID (e.g., SearchSpaceID).

[0278] Search space sets corresponding to type 0A-PDCCH are supported to be configured by a higher-layer parameter (e.g., searchSpaceOtherSystemInformation) that indicates the search space ID.

[0279] The search space set corresponding to Type 1-PDCCH is supported to be configured by a higher-layer parameter (e.g., ra-SearchSpace) that indicates the search space ID.

[0280] Search space sets corresponding to Type 2-PDCCH are supported to be configured by a higher-layer parameter (e.g., pagingSearchSpace) that indicates the search space ID.

[0281] Thus, the UE can determine the search space set to be configured for type 0 / 0A / 1 / 2-PDCCH by referring to the search space set configured by predetermined higher-layer parameters (searchSpaceSIB1 / searchSpaceOtherSystemInformation / ra-SearchSpace / pagingSearchSpace).

[0282] The question is whether the search space set configured for type 0 / 0A / 1 / 2-PDCCH can be configured in relation to / linked to other search space sets, and if so, how to control this configuration.

[0283] ≪SearchSpaceZero≫ If a search space set is configured for a meter (e.g., SearchSpaceZero) in the first upper layer parameter, at least one of the following Alt.5-1-1 to Alt.5-1-2 may be applied.

[0284] [Alt.5-1-1] The first higher-level parameter (e.g., SearchSpaceZero) may be configured to link with other search space sets configured by RRC / MAC CE.

[0285] With respect to SearchSpaceZero, multiple (e.g., two) search space sets configured / determined by options 5-1-1A to 5-1-1C below may be considered linked to the PDCCH iteration.

[0286] [[Option 5-1-1A]] Multiple (e.g., two) values ​​may be set / notified by a higher-level parameter (e.g., SearchSpaceZero), with each value corresponding to a linked set of search spaces (see Figure 20A). Each value may also indicate an index from a predefined association (e.g., a table) corresponding to the parameter set of the PDCCH monitoring occasion.

[0287] A predetermined association (e.g., a table) may be a table that reuses an association defined in an existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19B) with new entries added. Alternatively, a predetermined association (e.g., a table) may be obtained by defining a new association (e.g., a table) that includes the same parameters as the association defined in an existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19B).

[0288] Alternatively, one set of search spaces may be configured using a first higher-level parameter (e.g., SearchSpaceZero), and another set of search spaces may be configured using other higher-level parameters (e.g., SearchSpaceZero-link) (see Figure 20B).

[0289] [[Option 5-1-1B]] A single value may be set / notified by a higher-layer parameter (e.g., SearchSpaceZero), and this value may indicate an index from a predefined association (e.g., a table) corresponding to multiple (e.g., two) parameter sets of the PDCCH monitoring occasion (see Figure 20C). In other words, a single index set / notified by a higher-layer parameter and multiple search space sets may be determined by predetermined associations.

[0290] A predetermined association (e.g., a table) may be obtained by defining a new association (e.g., a table) that includes parameters similar to those of an association defined in an existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19B).

[0291] [[Option 5-1-1C]] A single value may be set / notified by a higher-layer parameter (e.g., SearchSpaceZero), which may indicate an index from a predefined association (e.g., a table) corresponding to a set of parameters for a PDCCH monitoring occasion for a single search space set. Other search space sets (or parameters for PDCCH monitoring occasions of other search space sets) linked to the single search space set obtained from the higher-layer parameter and the predetermined association may be determined based on predetermined rules (see Figure 20D).

[0292] The predetermined association (e.g., a table) may utilize an association defined in an existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19B).

[0293] The prescribed rule may be, for example, that the monitoring occasions for other search space sets are determined from at least one of the slot / symbol offsets of the search space set set by the higher-level parameters and the PDCCH monitoring occasions.

[0294] [Alt.5-1-2] Alternatively, the first higher-level parameter (e.g., SearchSpaceZero) may be configured not to be linked to other search space sets. The UE does not need to assume that SearchSpaceZero is configured to be linked to other search space sets.

[0295] ≪ControlResourceSetZero≫ If one or more CORESETs (e.g., linked CORESETs) are set for a meter (e.g., ControlResourceSetZero) in the second upper layer parameter, at least one of the following Alt.5-2-1 to Alt.5-2-2 may be applied.

[0296] [Alt.5-2-1] A single CORESET may be configured. This single CORESET may be configured as a CORESET used in an existing system. Multiple (e.g., two) linked search space sets determined in SearchSpaceZero as described above may be associated with the same CORESET.

[0297] [Alt.5-2-2] Multiple (e.g., two) CORESETs set / determined by options 5-2-1A to 5-2-1C below may be considered linked / associated with each other to a PDCCH iteration (or multiple (e.g., two) linked search space sets determined in SearchSpaceZero as described above).

[0298] [[Option 5-2-1A]] Multiple (e.g., two) values ​​may be set / notified by a higher-level parameter (e.g., ControlResourceSetZero), with each value corresponding to a linked CORESET (see Figure 21A). Each value may also indicate an index from a predefined association (e.g., a table) corresponding to the parameter set of the CORESET.

[0299] A predetermined association (e.g., a table) may be a table that reuses an association defined in the existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19A) with new entries added. Alternatively, a predetermined association (e.g., a table) may be obtained by defining a new association (e.g., a table) that includes the same parameters as the association defined in the existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19A).

[0300] Alternatively, one CORESET may be configured using a second higher-level parameter (e.g., ControlResourceSetZero), and another CORESET may be configured using another higher-level parameter (e.g., ControlResourceSetZero-link) (see Figure 21B).

[0301] [[Option 5-1-1B]] A single value may be set / notified by a higher-layer parameter (e.g., ControlResourceSetZero), and this value may indicate an index from a predefined association (e.g., a table) corresponding to multiple (e.g., two) parameter sets of a CORESET (see Figure 21C). In other words, multiple CORESETs may be determined by a single index set / notified by a higher-layer parameter and a predetermined association.

[0302] A predetermined association (e.g., a table) may be obtained by defining a new association (e.g., a table) that includes parameters similar to those of an association defined in an existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19A).

[0303] [[Option 5-1-1C]] A single value may be set / notified by a higher-layer parameter (e.g., ControlResourceSetZero), and this value may indicate an index from a predefined association (e.g., a table) corresponding to a single parameter set of a single CORESET. Other CORESETs (or parameters of other CORESETs) linked to the single CORESET obtained from the higher-layer parameter and the predetermined association may be determined based on predetermined rules (see Figure 21D).

[0304] The predetermined association (e.g., a table) may utilize an association defined in an existing system (Rel.15 / Rel.16) (e.g., the table in Figure 19A).

[0305] The predetermined rule may be, for example, that the frequency position of another CORESET is determined from at least one of the CORESET's resource block (RB) offset and frequency position set by the higher-layer parameters.

[0306] The two CORESETs may each be associated with two search space sets according to predefined rules. For example, the first CORESET may be associated with the first search space set, and the second CORESET with the second search space set. Alternatively, the two CORESETs may be associated with two search space sets through explicit configuration (e.g., RRC / MAC CE).

[0307] ≪Type 0 / 0A / 1 / 2-PDCCH≫ When a search space set is configured for type 0 / 0A / 1 / 2-PDCCH, at least one of the following Alt.5-3-1 to Alt.5-3-2 may apply.

[0308] [Alt.5-3-1] The search space set configured for type 0 / 0A / 1 / 2-PDCCH may be configured to link with other search space sets by RRC / MAC CE.

[0309] For types 0 / 0A / 1 / 2-PDCCH, multiple (e.g., two) search space sets may be configured using predetermined upper-layer parameters. These predetermined upper-layer parameters may include searchSpaceSIB1 / searchSpaceOtherSystemInformation / ra-SearchSpace / pagingSearchSpace. In this case, the predetermined upper-layer parameters may include information indicating multiple (e.g., two) search space IDs (see Figure 22).

[0310] Alternatively, for type 0 / 0A / 1 / 2-PDCCH, multiple (e.g., two) search space sets may be configured using multiple higher-layer parameters. For example, one search space set configured using the higher-layer parameters supported by the existing system (searchSpaceSIB1 / searchSpaceOtherSystemInformation / ra-SearchSpace / pagingSearchSpace) may be linked to another search space set configured using other higher-layer parameters. The other higher-layer parameters may be, for example, searchSpaceSIB1-link / searchSpaceOtherSystemInformation-link / ra-SearchSpace-link / pagingSearchSpace-link.

[0311] Multiple search space sets may be linked / associated with a PDCCH iteration using explicit RRC / MAC CE. Alternatively, if multiple search space sets are configured, they may be assumed to be linked / associated with a PDCCH iteration without explicit configuration / instruction.

[0312] [Alt.5-3-2] The search space set configured for type 0 / 0A / 1 / 2-PDCCH may be configured not to be linked to other search space sets. The UE does not need to assume that the search space set configured for type 0 / 0A / 1 / 2-PDCCH will be configured to be linked to other search space sets.

[0313] (UE capability information) In the above embodiments (for example, the first to fifth embodiments), the following UE capabilities may be set. Note that the following UE capabilities may be interpreted as parameters (for example, upper-layer parameters) set for the UE from the network (for example, base stations).

[0314] UE capability information regarding whether or not it supports PDCCH repetition may be defined.

[0315] UE capability information regarding whether or not a given type of common search space (e.g., CSS) supports PDCCH iterations may be defined. A given type of common search space may be, for example, at least one of type 0 CSS, type 0A CSS, type 1 CSS, type 2 CSS, and type 3 CSS.

[0316] UE capability information regarding whether or not a given DCI format supports PDCCH iterations may be defined. The given DCI format may be, for example, at least one of DCI formats 2_0, 2_1, 2_4, and 2_5.

[0317] UE capability information regarding whether or not to support PDCCH iterations may be defined for searchspace set 0.

[0318] UE capability information may be defined regarding whether or not a PDCCH order that initiates / triggers a PRACH transmission supports PDCCH repetition.

[0319] The above embodiment may be configured to apply to a UE that supports / reports at least one of the UE capabilities described above. Alternatively, the above embodiment may be configured to apply to a UE configured from a network.

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

[0321] Figure 23 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

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

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

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

[0325] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0326] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

[0328] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0329] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0330] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0331] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0332] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0333] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0335] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), etc., shared by each user terminal 20.

[0336] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0338] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0339] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0340] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0341] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0342] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

[0344] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0345] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0346] (base station) Figure 24 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

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

[0348] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0350] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0352] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0354] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0355] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.

[0356] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

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

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

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

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

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

[0362] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0363] The transmitting / receiving unit 120 may transmit information about search space sets to which predetermined conditions are set commonly or separately for multiple downlink control channels to which repeated transmission is applied. The control unit 110 may control the transmission of multiple downlink control information based on the information about the search space sets.

[0364] The transmitting / receiving unit 120 may transmit first downlink control information instructing the cancellation of UL transmission. The control unit 110 may control whether or not to schedule uplink shared channel transmission based on the symbol position of the first downlink control channel that provides the first downlink control information and the symbol position of the second downlink control channel that provides second downlink control information that schedules uplink shared channel transmission. The control unit 110 may also determine the symbol position of the first downlink control channel and the symbol position of the second downlink control channel based on at least one of whether or not the first downlink control channel is repeatedly transmitted and whether or not the second downlink control channel is repeatedly transmitted.

[0365] The transmitting / receiving unit 120 may receive at least one of the random access channel and the uplink shared channel. The control unit 110 may, in response to the reception of at least one of the random access channel and the uplink shared channel, control the transmission of downlink control information within a predetermined window period. The control unit 110 may also determine the predetermined window period based on whether or not the downlink control channel providing the downlink control information is repeatedly transmitted.

[0366] The transmitting / receiving unit 120 may transmit a first downlink control channel that triggers the transmission of a random access channel. When the control unit 110 transmits downlink control information in response to the reception of a random access channel, it may control the first downlink control channel and the second downlink control channel that provides the downlink control information to have pseudo-collocation (for example, the pseudo-collocation characteristics of a DMRS antenna port). The control unit 110 may also determine which first downlink control channel and which second downlink control channel have pseudo-collocation based on at least one of whether the first downlink control channel is repeatedly transmitted and whether the second downlink control channel is repeatedly transmitted.

[0367] The transmitting / receiving unit 120 may transmit information relating to at least one of the search space set and control resource set for repeated transmission of the downlink control channel. The control unit 110 may use at least one of a plurality of associated search space sets and a plurality of associated control resource sets obtained based on said information to control the transmission of the downlink control channel to which repeated transmission is applied.

[0368] (User terminal) Figure 25 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. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0369] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0370] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0372] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0374] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0376] The transmitting / receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0377] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

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

[0379] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

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

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

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

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

[0384] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0385] The transmitting / receiving unit 220 may receive information about a search space set to which predetermined conditions are set commonly or separately for multiple downlink control channels to which repeated transmission is applied. The control unit 210 may control the reception of multiple downlink control information based on the information about the search space set. The predetermined conditions may be at least one of the aggregation level and the number of downlink control channel candidates for each aggregation level. At least one of the aggregation level (e.g., CCE AL) and the number of downlink control channel candidates for each aggregation level may be set differently for multiple downlink control channels. If the number of downlink control channel candidates for each aggregation level is set differently for multiple downlink control channels, at least some of the downlink control channel candidates set for each downlink control channel may be associated.

[0386] The transmitting / receiving unit 220 may receive first downlink control information instructing the cancellation of UL transmission. The control unit 210 may determine whether or not to schedule uplink shared channel transmission based on the symbol position of the first downlink control channel that provides the first downlink control information and the symbol position of the second downlink control channel that provides second downlink control information that schedules uplink shared channel transmission. The control unit 210 may also determine the symbol positions of the first downlink control channel and the symbol positions of the second downlink control channel based on at least one of whether or not the first downlink control channel is repeatedly transmitted and whether or not the second downlink control channel is repeatedly transmitted.

[0387] Furthermore, when repeated transmission is applied to the second downlink control channel, the control unit 210 may determine whether to schedule uplink shared channel transmission based on the symbol position of a specific second downlink control channel selected from among multiple second downlink control channels based on the first criterion. Furthermore, when repeated transmission is applied to the first downlink control channel, the control unit 210 may determine whether to schedule uplink shared channel transmission based on the symbol position of a specific first downlink control channel selected from among multiple first downlink control channels based on the second criterion. It may be supported that the first criterion and the second criterion are applied / set differently.

[0388] The transmitting / receiving unit 220 may transmit at least one of the random access channel and the uplink shared channel. The control unit 210 may, in response to the transmission of at least one of the random access channel and the uplink shared channel, control the system to detect downlink control information within a predetermined window period. The control unit 210 may also determine the predetermined window period based on whether or not the downlink control channel providing downlink control information is repeatedly transmitted.

[0389] Furthermore, when repeated transmission is applied to a downlink control channel that provides downlink control information, the control unit 210 may determine a predetermined window period based on a specific control resource set or a specific downlink control channel candidate from among the control resource sets or downlink control channel candidates corresponding to each downlink control channel. The predetermined period may start from the first symbol of the specific control resource set or the specific downlink control channel candidate after the last symbol of the random access channel occasion or uplink shared channel occasion corresponding to the transmission of the random access channel. The control resource sets or downlink control channel candidates corresponding to each downlink control channel may be set in association.

[0390] The transmitting / receiving unit 220 may transmit a random access channel based on the first downlink control channel. When the control unit 210 detects downlink control information in response to the transmission of a random access channel, it may assume that the first downlink control channel and the second downlink control channel providing the downlink control information are pseudo-collocations. The control unit 210 may also determine whether the first downlink control channel and the second downlink control channel have pseudo-collocations based on at least one of whether the first downlink control channel is repeatedly transmitted and whether the second downlink control channel is repeatedly transmitted.

[0391] When repeated transmission is applied to the first downlink control channel and the second downlink control channel, at least one of the multiple first downlink control channels to which repeated transmission is applied and at least one of the multiple second downlink control channels to which repeated transmission is applied may have pseudo-collocation. When repeated transmission is applied to the first downlink control channel and not to the second downlink control channel, all or a specific of the multiple first downlink control channels to which repeated transmission is applied may have pseudo-collocation with the second downlink control channel. When repeated transmission is applied to the second downlink control channel and not to the first downlink control channel, all or a specific of the multiple second downlink control channels to which repeated transmission is applied may have pseudo-collocation with the first downlink control channel.

[0392] The transmitting / receiving unit 220 may receive information regarding at least one of the search space set and control resource set for repeated transmission of the downlink control channel. The control unit 210 may control the reception of the downlink control channel to which repeated transmission is applied based on at least one of a plurality of associated search space sets and a plurality of associated control resource sets obtained based on said information.

[0393] Furthermore, the control unit 210 may determine at least one of a plurality of associated search space sets and a plurality of associated control resource sets based on the values ​​notified by upper-layer signaling and predefined associations. Multiple search space sets may be associated with the same control resource set. Also, the control unit 210 may determine one search space set and one control resource set based on this information, and determine other search space sets associated with one search space set and other control resource sets associated with one control resource set based on predetermined conditions / rules.

[0394] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0395] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0396] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 26 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0397] In this disclosure, terms such as apparatus, circuit, device, 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 it may be configured to omit some of the devices.

[0398] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

[0400] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0401] 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 executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0402] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0403] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.

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

[0405] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

[0408] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0409] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0410] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

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

[0412] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0413] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0414] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0415] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0416] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0417] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0418] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0419] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0420] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0421] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0422] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0423] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0424] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0425] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0426] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0427] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0428] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0429] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0430] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0431] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0432] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0433] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0434] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0435] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0436] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0437] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0439] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0440] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "quasi-co-location (QCL)," "transmission configuration indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0441] 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" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0442] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0443] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0444] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

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

[0446] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0447] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0448] Figure 27 shows an example of a vehicle according to one embodiment. As shown in Figure 27, the vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

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

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

[0451] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression signal of accelerator pedal 43 acquired by accelerator pedal sensor 55, brake pedal depression signal of brake pedal 44 acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by object detection sensor 58.

[0452] The information service unit 59 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0453] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0455] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0456] The communication module 60 may transmit at least one of the signals from the various sensors 50-58 input to the electronic control unit 49 and the information obtained based on those signals to an external device via wireless communication.

[0457] The communication module 60 receives various information (traffic information, signal information, distance information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The communication module 60 also stores the various information received from the external device in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., installed in the vehicle 40.

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

[0459] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0460] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0461] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0462] Each aspect / embodiment described in this disclosure includes 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 (where x is, for example, an integer or 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0463] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0464] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0465] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0466] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0467] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0468] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0469] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0470] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0471] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0472] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0473] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0474] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiver that receives upper-layer parameters including information about the search space type, information about the number of downlink control channel candidates for each aggregation level, and information about linking search space sets, When multiple linked search space sets are configured for a common search space based on the aforementioned upper-layer parameters, the system includes a control unit that controls monitoring of downlink control channel candidates corresponding to the multiple linked search space sets, The aforementioned linked sets of search spaces are configured with the same number of downlink control channel candidates for each aggregation level. A terminal characterized in that the search space set configured by at least one of the higher-layer parameters, searchSpaceSIB1, searchSpaceOtherSystemInformation, ra-SearchSpace, and pagingSearchSpace, is not configured as one of the linked search space sets.

2. The terminal according to claim 1, wherein the linked sets of search spaces correspond to the same search space type and the same downlink control information format.

3. The steps include receiving upper-layer parameters that include information about the search space type, information about the number of downlink control channel candidates for each aggregation level, and information about linking search space sets, If, based on the aforementioned higher-layer parameters, multiple linked search space sets are configured for a common search space, the process includes the step of controlling the monitoring of downlink control channel candidates corresponding to the multiple linked search space sets. The aforementioned linked sets of search spaces are configured with the same number of downlink control channel candidates for each aggregation level. A wireless communication method for a terminal, characterized in that a search space set configured by at least one of the higher-layer parameters, searchSpaceSIB1, searchSpaceOtherSystemInformation, ra-SearchSpace, and pagingSearchSpace, is not configured as one of the linked search space sets.

4. A transmitter that transmits upper-layer parameters including information about the search space type, information about the number of downlink control channel candidates for each aggregation level, and information about linking search space sets, The system includes a control unit that controls the setting of multiple linked search space sets for a common search space based on the aforementioned upper-layer parameters, The aforementioned linked sets of search spaces are configured with the same number of downlink control channel candidates for each aggregation level. A base station characterized in that the search space set, configured by at least one of the higher-layer parameters searchSpaceSIB1, searchSpaceOtherSystemInformation, ra-SearchSpace, and pagingSearchSpace, is not configured as one of the linked search space sets.

5. A system having terminals and base stations, The terminal includes a receiving unit that receives upper-layer parameters including information about the search space type, information about the number of downlink control channel candidates for each aggregation level, and information about linking search space sets; and a control unit that controls monitoring of downlink control channel candidates corresponding to the linked search space sets when multiple linked search space sets are configured for a common search space based on the upper-layer parameters. The base station comprises a transmitting unit that transmits the upper layer parameters, and a control unit that controls the setting of multiple linked search space sets for the common search space based on the upper layer parameters. The aforementioned linked sets of search spaces are configured with the same number of downlink control channel candidates for each aggregation level. A system characterized in that a search space set, configured by at least one of the higher-level parameters, searchSpaceSIB1, searchSpaceOtherSystemInformation, ra-SearchSpace, and pagingSearchSpace, is not configured as one of the linked search space sets.

Images