RU2784368C1 - User terminal and radio communication method - Google Patents

Abstract

FIELD: communication technology.

SUBSTANCE: invention relates to a user terminal and a method for radio communication in new generation mobile communication systems. According to the proposed solution, the user terminal contains a receiving section made with the possibility of receiving configuration information from a set of search spaces, and a control section made with the possibility of controlling the monitoring of downstream control information (DCI) of the first format other than the 0_0 and 0_1 formats used for planning the ascending common channel, and the second format other than the 1_0 and 1_1, used to plan the descending common channel, in a set of search spaces configured based on the specified configuration information. The control section is made with the possibility of determining that the monitoring priority is assigned in ascending order of the identifier of the set of search spaces.

EFFECT: possibility of proper management of monitoring of the downstream control information.

6 cl, 14 dwg

Description

The technical field to which the invention belongs

The present invention relates to a user terminal and a radio communication method in new generation mobile communication systems.

State of the art

To further increase data rates, reduce latency, etc. in a UMTS (Universal Mobile Telecommunications System) network, LTE (Long Term Evolution) scheme specifications are being developed (see Non-Patent Literature No. 1). Moreover, for additional throughput enhancement, improvement, etc. LTE Scheme (3rd ^Generation Partnership Project (3rd Generation Partnership Project) Version 8 and Version 9) specifications for the LTE-Advanced Scheme (LTE Advanced Scheme; 3GPP Versions 10-14) are being developed.

Legacy LTE systems are also being studied (e.g. referred to as “5th generation (5G) mobile communication system”, “5G+ (plus)”, “NR” (New Radio technology)”, “3GPP version 15 (or later) version)", etc.).

List of Cited Materials

Non-Patent Literature

Non-Patent Literature No. 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN) ); general description; stage 2 (version 8)”, April, 2010.

Disclosure of invention Technical problem

For future radio communication systems (hereinafter also referred to as NR systems), the possibility of introducing new formats other than the existing Downlink Control Information (DCI) formats (for example, DCI formats 1_0, 1_1, 0_0, 0_1, 2_0, 2_1, 2_2 and 2_3).

The new formats may be used, for example, for at least one of Ultra-Reliable and Low-Latency Communication (URLLC) and upstream preemption services.

However, as new formats are introduced, the sets of search spaces used for DCI monitoring (also referred to as blind decoding, etc.) may not be properly configured for the UE. As a result, the UE will be unable to properly manage DCI monitoring.

In this regard, it is the task of the inventors of the present invention to provide a user terminal and a radio communication method that can properly manage DCI monitoring.

Solution

According to one aspect of the present invention, a user terminal includes: a receiving section configured to receive configuration information of a set of search spaces; and a control section configured to control downlink control information (DCI) monitoring of a first format other than the 0_0 and 0_1 formats used for uplink common channel scheduling and a second format different from 1_0 and 1_1 formats used for downlink common channel scheduling, in a set of search spaces configured based on the specified configuration information.

Positive results of the invention

According to one aspect of the present invention, DCI monitoring can be properly managed.

Brief description of the drawings

In FIG. 1 is a diagram illustrating one example of SS configuration information.

In FIG. 2 is a diagram illustrating one example of the configuration information SS according to the first configuration example in the first aspect.

In FIG. 3 is a diagram illustrating one example of the second configuration information SS according to the second configuration example in the first aspect.

In FIG. 4 is a diagram illustrating another example of the second configuration information SS according to the second configuration example in the first aspect.

In FIG. 5A and 5B are diagrams illustrating examples of UE-specific PDCCH information according to the second aspect.

In FIG. 6 is a diagram illustrating one example of the configuration information SS according to the second aspect.

In FIG. 7 is a diagram illustrating another example of SS configuration information according to the second aspect.

In FIG. 8 is a diagram illustrating one example of the first prioritization of SSs according to the third aspect.

In FIG. 9 is a diagram illustrating one example of the second SS prioritization according to the third aspect.

In FIG. 10 is a diagram illustrating one example of a schematic structure of a radio communication system according to one embodiment.

In FIG. 11 is a diagram illustrating one example of a base station structure according to one embodiment.

In FIG. 12 is a diagram illustrating one example of the structure of a user terminal according to one embodiment.

In FIG. 13 is a diagram illustrating one example of a hardware structure of a base station and a user terminal according to one embodiment.

Implementation of the invention

Search space set

One or more sets of search spaces (SS) are configured for the UE. The SS set is also referred to as the PDCCH search space set, search space, and so on.

The UE monitors PDCCH candidates in one or more SSs. One or more sets of SSs may include at least one of a set of common SSs (a set of common search spaces (CSS) for one or more UEs) and a set of UE-specific SSs (a set of UE-specific spaces). search (USS, from English UE-specific Search Space)).

The UE may receive configuration information of each SS (configuration information SS, for example, Radio Resource Control (RRC) Information Element (IE, Radio Resource Control) (also referred to as an RRC parameter) "SearchSpace") . For example, the UE may receive each piece of SS configuration information with higher layer signaling. Each piece of SS configuration information may be contained in UE-specific PDCCH configuration information (eg, RRC IE "PDCCH-Config") or cell-specific PDCCH configuration information (eg, RRC IE "PDCCH-ConfigCommon").

Each piece of configuration information SS may contain, for example, at least one of the following parameters (or information related to at least one of the following parameters).

(1) SS Set ID (Search Space ID, e.g. RRC IE "SearchSpace ld")

(2) Identifier of the CORESET associated with the SS (Control Resource Set ID, e.g. RRC IE "ControlResourceSetld")

(3) Periodicity and offset of a monitoring event including a set of SSs (eg, RRC IE "monitoringSlotPeriodicityAndOffset")

(4) Time interval of the monitoring event (for example, RRC IE "duration")

(5) Number of PDCCH candidates for each aggregation level in the SS set (eg, RRC IE "nrofCandidates")

(6) SS set type, namely CSS set or USS set (search space type, e.g. RRC IE "searchSpaceType")

(7) CSS set related information (CSS set information, such as RRC IE "cottop")

(8) USS set related information (USS set information, such as RRC IE "ue-Specific")

Here, (7) the CSS set information may contain information related to the DCI format controlled (monitored) in the CSS set (DCI format information, for example, RRC information elements IE "dci-FormatO-0-AndFormat1-0" , "dci-Format2-0", "dci-Format2-1", "dci-Format2-2", and "dci-Format2-3"). The DCI format information for a CSS set may indicate, for example, at least one of the DCI format (at least one of DCI format 0_0 and 1_0, DCI format 2_0, DCI format 2-1, DCI format 2-2, and DCI format 2_3) monitored in the CSS set and the number of PDCCH candidates for each aggregation level used to monitor the DCI format.

The CSS set may, for example, be a Type 3 PDCCH CSS set used to monitor the DCI format used for scrambling in which Cyclic Redundancy Check (CRC) bits are scrambled (CRF scrambling) with slot format indicator (SFI, from the English. Slot Format Indicator) - temporary radio network identifier (RNTI, from the English. Radio Network Temporary Identifier), INT (Interruption; interruption) - RNTI, TPC (Transmit Power Control; transmission power control) - PUSCH - RNTI, TPC - PUCCH - RNTI, or TPC - SRS (Sounding Reference Symbols; sounding reference symbols) - RNTI.

In addition, (8) the USS set information may contain information related to the DCI format controlled in the USS set (DCI format information, eg, RRC IE "dci-Formats"). The DCI format information for the USS set may indicate, for example, the DCI format (one of DCI formats 0_0 and 1_0 and DCI formats 0_1 and 1_1) monitored in the USS set.

The USS set is used to monitor the DCI format subject to CRC scrambling with C-RNTI or CS-RNTI. The UE may be configured with at least one of the DCI 0_0 and 1_0 monitoring USS set and the DCI 0_1 and 1_1 monitoring USS set.

In this case, DCI formats 1_0 and 1_1 are used for scheduling a downlink shared channel (eg, Physical Downlink Shared Channel (PDSCH)). DCI formats 0_0 and 0_1 are used for scheduling an uplink shared channel (eg, Physical Uplink Shared Channel (PUSCH)).

DCI formats 0_0 and 1_0 may have the same size (payload). In addition, DCI formats 0_1 and 1_1 may have the same size. DCI formats 0_0 and 1_0 may be smaller than DCI formats 0_1 and 1_1, respectively. DCI formats 1_0 and 0_0 are also referred to as standby DCI, etc. In contrast, DCI formats 1_1 and 1_0 are also referred to as non-backup DCI, and so on.

In FIG. 1 is a diagram illustrating one example of SS configuration information. As shown in FIG. 1, the configuration information SS (eg, RRC IE "SearchSpace") may contain at least one of the above parameters (pieces of information) (1) - (8).

In addition, the DCI format information (eg, RRC IE "dci-Formats") for the USS set in the configuration information SS of FIG. 1 may indicate whether the USS set, denoted by the search space ID, is used to monitor DCI formats 0_0 and 1_0 or DCI formats 0_1 and 1_1.

The UE may be configured with each set of SSs based on each piece of SS configuration information. In addition, a predetermined time period of a predetermined periodicity for monitoring (blind decoding) of each set of SSs (PDCCH monitoring event, Monitoring Occasion, monitoring time period) can be configured based on each piece of SS configuration information (for example, , the above parameters (3) and (4)).

In particular, the UE may be configured with a monitoring event for each set of SSs. The UE may monitor (monitor) PDCCH candidates for the SS set in CORESET in a configured monitoring event. The monitoring event may include one or more slots.

The maximum number of PDCCH candidates that the UE is able to monitor per cell and per slot may be limited. The maximum number can be defined for each spacing and subcarrier. For example, when the spacing and subcarrier is 15 kHz, 30 kHz, 60 kHz, and 120 kHz, the specified maximum number may be 44, 36, 22, and 20, respectively.

In addition, the maximum number of non-overlapping Control Channel Elements (CCE) per cell and per slot per UE may be limited. The maximum number can be determined for each subcarrier spacing μ. For example, when the spacing and subcarrier is 15 kHz, 30 kHz, 60 kHz, and 120 kHz, the specified maximum number is 56, 56, 48, and 32, respectively.

Incidentally, in NR, a communication implementation is allowed in which the required conditions are consistent with a plurality of different services (also referred to as use cases, traffic types, etc.) in the same cell. The set of services may, for example, include more advanced broadband access (enhanced mobile broadband access (eMBV, from the English enhanced Mobile Broadband)) and ultra-reliable communication with low latency (URLLC)). For example, URLLC requires lower latency and higher reliability than eMBV.

Thus, in NR, in addition to the existing DCI formats (eg DCI formats 1_0, 1_1, 0_0, 0_1, 2_0, 2_1, 2_2 and 2_3), the possibility of introducing new DCI formats is also being explored. The new DCI formats may, for example, be used for PUSCH or PDSCH scheduling and preemption (eg, upstream preemption).

Here, the new DCI format used for PDSCH scheduling is also referred to as DCI format 1_2, and so on. The new DCI format used for PUSCH scheduling may be referred to as DCI format 0_2, and so on. In addition, the new DCI format used for upstream preemption is also referred to as DCI format 2_4, etc.

It should be noted that the expressions regarding the new DCI formats are not limited to these examples. For example, expressions for the new DCI formats for PDSCH and PUSCH scheduling may be expressions in which "2" in DCI 1_2 format and DCI 0_2 format is replaced by any character sequence other than "0" or "1", or may be other expressions. In addition, the new DCI format for upstream preemption may be an expression in which "4" in DCI 2_4 format is replaced by any sequence of characters other than "0", "1", "2", or "3", or may be another expression.

Thus, when introducing a new DCI format (eg, at least one of DCI formats 0_2, 1_2, and 2_4) used for PUSCH or PDSCH scheduling or for preemption (eg, upstream preemption), it is assumed that the UE the SS set is configured to monitor the new DCI format. However, the problem is how to signal the configuration of the SS set.

In particular, the problem is how to configure the SS configuration information used to configure the SS set. Accordingly, the inventors of the present invention came up with the idea of properly configuring the SS configuration information used to configure the SS set to monitor the new DCI format, which allows DCI monitoring to be properly managed even when the new DCI format is introduced.

Below, with reference to the accompanying drawings, embodiments of the present invention are disclosed in detail.

The following description illustrates an example in which the new DCI format used for PUSCH scheduling is DCI 0_2, the new DCI format used for PDSCH scheduling is DCI 1_2, and the new DCI format for upstream preemption is new format 2_4. However, as disclosed above, the expressions for these new DCI formats are not limited to these examples illustrated here.

First aspect

In a first aspect, configuring an SS set (eg, a USS set) to monitor at least one (DCI 0_2/1_2 format) DCI 0_2 format used for PUSCH scheduling and DCI 1_2 format used for PDSCH scheduling is disclosed.

The SS set for DCI format 0_2/1_2 may be one of the USS sets configured based on the SS configuration information (eg, RRC IE "SearchSpace") (first configuration example), or may be a specific USS set configured based on the configuration information SS (second configuration information SS) which is different from the configuration information SS (first configuration information SS) disclosed above (second configuration example).

First configuration example

The UE may be configured with one or more USS sets. Each USS set configured for the UE may be associated with DCI formats 0_0 and 1_0 (DCI format 0_0/1_0), DCI formats 0_1 and 1_1 (DCI format 0_1/1_1), or DCI format 0_2/1_2.

Each USS set may be configured based on the SS configuration information (eg, RRC IE "SearchSpace"). It should be noted that the DCI format information (eg, RRC IE "dci-Formats") for the USS set in the SS configuration information may selectively point to one of DCI format 0_0/1_0, DCI format 0_1/1_1, and format 0_2/1_2 as DCI format controlled in the USS set.

In FIG. 2 is a diagram illustrating one example of the configuration information SS according to the first configuration example in the first aspect. It should be noted that although in FIG. 2 shows some of the parameters, the SS configuration information (eg, RRC IE "SearchSpace") may contain at least one of the above parameters from (1) to (8).

As shown in FIG. 2, the DCI format information (for example, RRC IE "dci-Formats") for the USS set in the SS configuration information (for example, RRC IE "SearchSpace") differs from that shown in Fig. 1 in that not only the format DCI 0_0/1_0 or DCI format 0_1 /1_1, but also DCI format 0_2/1_2 can be set as the DCI format controlled in the USS set.

As shown in FIG. 2, when configuring the SS set #1 for the UE as the USS for DCI format 0_0/1_0, the SS configuration information (for example, RRC IE "SearchSpace") of the SS set #1 may contain DCI format information (for example, RRC IE "dci -Formats") pointing to DCI format 0_0/1_0.

In addition, when configuring the SS set #2 for the UE as the USS for DCI format 0_1 /1_1, the SS configuration information (eg, RRC IE "SearchSpace") of the SS set #2 may contain DCI format information (eg, RRC IE " dci-Formats") pointing to DCI format 0_1/1_1.

Moreover, when configuring the SS set #3 for the UE as the USS for the new DCI format 0_2/1_2, the SS configuration information (for example, RRC IE "SearchSpace") of the SS set #3 may contain DCI format information (for example, RRC IE "dci-Formats") indicating the DCI 0_2/1_2 format.

Thus, the USS set for DCI format 0_2/1_2 can be configured with the configuration information SS (for example, RRC IE "SearchSpace") having the same configuration as the USS set for DCI format 0_0/1_0 or DCI format 0_1/1_1 .

The UE may control the DCI format indicated by the DCI format information in the SS #1 to #3 configured by the SS configuration information.

In the first configuration example, the DCI format information for the USS set in the configuration information SS specifies one of DCI format 0_0/0_1, DCI format 0_1/1_1, and DCI format 0_2/1_2, and thus the USS set for the new DCI format 0_2/ 1_2 can be configured without adding a new parameter to the existing configuration information SS (eg, FIG. 1).

In addition, the USS for DCI format 0_0/1_0, the USS for DCI format 0_1/1_1, and the USS for DCI format 0_2/1_2 can be configured with the configuration information SS having the same configuration.

Second configuration example

The USS set for DCI format 0_2/1_2 may be configured based on the second configuration information SS set separately from the specified configuration information SS (for example, RRC IE "SearchSpace", the first configuration information SS, for example, in Fig. 1). The second SS configuration information may be used to configure only a specific SS (eg, USS for DCI 0_2/1_2 format), or may be used to configure a specific SS or another SS other than the specific SS.

In FIG. 3 is a diagram illustrating one example of the second configuration information SS according to the second configuration example of the first aspect. As shown in FIG. 3, the second SS configuration information (for example, RRC IE "SearchSpace formats0-2-And-1-2" or "SearchSpace DCI0-2-And-1-2") can be used to configure a specific SS set (for example, USS set for DCI format 0_2/1_2).

The second configuration information SS may contain at least one of the above parameters (1) - (5). It should be noted that the second configuration information SS may or may not include the above parameters (6) to (8). The second configuration information SS is for configuring the USS for DCI 0_2/1_2 format, thereby eliminating the need to set the search space type, etc.

As shown in FIG. 3, when configuring the USS SS #3 as the USS for the new DCI format 0_2/1_2, the UE may determine at least one of the search space ID "3", the control resource set ID for CORESET associated from SS #3, monitoring event periodicity including SS #3, offset and time period, and number of PDCCH candidates for each aggregation level in SS #3 using the second SS configuration information.

In contrast, although not shown in the drawings, when configuring SSs #1 and #2 for the UE as USSs for DCI format 0_0/0_1 and DCI format 0_1/1_1, respectively, the UE may use the first SS configuration information ( eg RRC IE "SearchSpace", see Fig. 1).

Thus, the USS set for DCI format 0_2/1_2 can be configured by the second configuration information SS (for example, RRC IE "SearchSpace formats0-2-And-1-2" or "SearchSpace DCI 0-2-And-1-2" ) that has a configuration different from the first SS configuration information (eg, RRC IE "SearchSpace") used to configure the USS set for DCI format 0_0/1_0 or DCI format 0_1/1_1.

The UE may monitor the DCI format (DCI format 0_0/1_0 or DCI format 0_1/1_1) indicated by the DCI format information (eg, RRC IE "dci-Formats" of FIG. 1) for the USS set in the first SS configuration information in SS sets #1 and #2 configured by the first SS configuration information. In contrast, the UE may control the DCI format 0_2/1_2 in the SS #3 configured by the second SS configuration information.

As shown in FIG. 3, by specifying the second SS configuration information used to configure a specific SS set (for example, the USS set for DCI 0_2/1_2 format), the USS set for the new DCI 0_2/1_2 format can be configured without making changes to the existing first SS configuration information. (for example, Fig. 1).

In FIG. 4 is a diagram illustrating another example of the second configuration information SS according to the second configuration example in the first aspect. The second SS configuration information (eg, RRC IE "SearchSpace-v16") can be used not only to configure a specific SS set (eg, USS set for DCI 0_2/1_2 format), but also to configure another SS set (eg, at least at least one of the CSS set and the USS set).

It should be noted that although in FIG. 4 shows some of these parameters, the second configuration information SS (for example, RRC IE "SearchSpace-r16") may contain at least one parameter from the above parameters (1) - (8). The DCI format information (eg, RRC IE "dci-Formats") for the USS set in the second SS configuration information (eg, RRC IE "SearchSpace-r16") is different from the first SS configuration information (eg, RRC IE "SearchSpace"), as shown in FIG. 1 in that not only DCI format 0_0/1_0 or DCI format 0_1 /1_1 but also DCI format 0_2/1_2 can be set as the DCI format controlled in the USS set.

The first configuration information SS (for example, RRC IE "SearchSpace"), as shown in FIG. 1 may be used to configure an SS for a UE that does not allow SS for DCI 0_2/1_2 format configuration (eg, a UE that supports up to version 15). In contrast, the second configuration information SS (for example, RRC IE "SearchSpace-r16"), as shown in FIG. 4 may be used to configure an SS for a UE that is capable of configuring an SS for DCI 0_2/1_2 format (eg, a UE that supports version 16).

Thus, depending on whether or not the UE supports the new DCI format, different parts of the SS configuration information (eg, the first SS configuration information of FIG. 1 and the second SS configuration information of FIG. 4) can be used to configure the SS set.

As shown in FIG. 4, when configuring the SS #1 for the UE as the USS for the DCI format 0_0/1_0, the second SS configuration information (eg, RRC IE "SearchSpace-r16") for the SS set #1 may contain DC format information (eg, RRC IE "dci-Formats") indicating DCI format 0_0/1_0.

In addition, when configuring the SS #2 for the UE as the USS for the DCI format 0_1/1_1, the second SS configuration information (for example, RRC IE "SearchSpace-r16") for the SS #2 may contain DCI format information (for example , RRC IE "dci-Formats") indicating DCI format 0_1/1_1.

Moreover, when configuring the SS #3 for the UE as the USS for the new DCI format 0_2/1_2, the second SS configuration information (eg, RRC IE "SearchSpace-r16") for the SS #3 may contain DCI format information ( e.g. RRC IE "dci-Formats") indicating DCI format 0_2/1_2.

The UE may monitor the DCI format indicated by the DCI format information in the SS #1 to #3 configured by the second SS configuration information.

As shown in FIG. 4, by specifying the second configuration information SS (eg, RRC IE "SearchSpace-r16") for a UE that supports the new DCI format (eg, DCI format 0_2/1_2), its operation may differ from that of a UE that does not support the new DCI format (for example, DCI format 0_2/1_2).

In the second configuration example, by redefining the second configuration information SS, it is possible to properly configure the SS set for the new DCI format (for example, the USS set for DCI format 0_2/1_2).

Second aspect

In a second aspect, the configuration of the DCI 2_4 format monitoring SS used for upstream preemption is disclosed.

Each field in the DCI 2_4 format may have an upstream preemption indication (Preemption Indication). Each field may contain a given number of bits (eg 14 bits).

The DCI format 2_4 may be a generic DCI for a group of one or more UEs (also referred to as a generic DCI for a group, a generic for a UE group DCI, etc.) or a UE-specific DCI. The DCI 2_4 format monitoring SS set may be a CSS set (eg, a CSS set for PDCCH type 3) or a USS set.

Uplink preemption related information (uplink preemption information, eg, RRC IE "UplinkPreemption") may be contained in UE-specific PDCCH information (eg, RRC IE "PDCCH-Config").

In addition, the SS set for the DCI 2_4 format can be configured with the SS configuration information (eg, RRC IE "SearchSpace"). The SS configuration information may be contained in the UE-specific PDCCH information.

In FIG. 5A and 5B are diagrams illustrating examples of UE-specific PDCCH information according to the second aspect. As shown in FIG. 5A, the UE-specific PDCCH information (e.g., "PDCCH-Config" RRC IE) may contain at least one of the following kinds of information: upstream preemption related information (upstream preemption information, e.g., RRC IE "UplinkPreemption"), and a list (list SS, eg RRC IE "searchSpacesToAddModl_ist") of one or more pieces of SS configuration information (eg RRC IE "SearchSpace").

As shown in FIG. 5B, the uplink preemption information (eg, RRC IE "UplinkPreemption") may include at least one of the following types of information.

- Information (eg, RRC IE "int-RNTI") indicating the RNTI (eg, INT-RNTI) used for CRC scrambling of the DCI 2_4 format

- Information (e.g., RRC IE "dci-PayloadSize") indicating a DCI 2_4 format payload subject to CRC scrambling with INT-RNTI

- Information (preemption resource information, eg, RRC IE "timeFrequencySet") related to resources with preemption set (eg, at least one of frequency domain resources and time domain resources)

For example, the preemption resource information may indicate a relationship between bits of a given field in DCI 2_4 format and one or more symbols.

The SS set for the DCI 2_4 format may be configured based on the SS configuration information in the SS list. The SS set may be a CSS set or may be a USS set.

In FIG. 6 is a diagram illustrating one example of the configuration information SS according to the second aspect. In FIG. 6 shows one example of SS configuration information that can configure a CSS for DCI 2_4 format. As shown in FIG. 6, the configuration information SS may contain at least one of the above parameters (1) to (8).

As shown in FIG. 6, the CSS set information (eg, RRC IE "commtype") is different from that shown in FIG. 1 in that information relating to the DCI 2_4 format (DCI 2_4 format information such as RRC IE "dci-Format2-4") controlled in the CSS set is contained as the DCI format information for the CSS set.

The DCI format information for the CSS set shown in FIG. 6 may indicate, for example, at least one of the DCI formats (at least one of DCI formats 0_0 and 1_0, DCI format 2_0, DCI format 2-1, DCI format 2-2, DCI format 2_3, and DCI format 2_4 ) controlled in the CSS, and the number of PDCCH candidates for each aggregation level used to control the DCI format.

When the CSS set information in the SS configuration information contains DCI 2_4 format information (eg, RRC IE "dci-Format2-4"), the UE can control the DCI 2_4 format in the CSS configured by the SS configuration information.

In FIG. 7 is a diagram illustrating another example of SS configuration information according to the second aspect. In FIG. 7 shows an example of SS configuration information that can configure the USS set for DCI 2_4 format. As shown in FIG. 7, the configuration information SS may contain at least one of the above parameters (1) to (8).

As shown in FIG. 7, the USS set information (eg, RRC IE "ue-Specific") may contain DCI format information (eg, RRC IE "dci-Formats"), which may specify DCI format 0_0/1_0, DCI format 0_1/1_1, or DCI 2-4.

The UE may control the USS set configured by the SS configuration information in the DCI format indicated by the DCI format information in the USS set information.

In a second aspect, if the DCI 2_3 format for upstream preemption is supported, then the SS set for the DCI 2_3 format can be properly configured for the UE.

Third aspect

Predetermined limits (eg, the maximum number of PDCCH candidates that can be monitored per cell and per slot, as discussed above, and the number of CCEs that can overlap per cell and per slot, as discussed above) are assumed to be set by monitoring. DCI (also referred to as PDCCH monitoring, DCI monitoring, monitoring, blind decoding, etc.) performed by the UE.

Thus, when reintroducing the DCI 0_2/1_2 format, the UE may, if possible, reset at least one of the following processes: (monitoring/processing of the DCI 0_2/1_2 format) monitoring of the DCI 0_2/1_2 format, and processing based on the DCI 0_2 format /1_2. In addition, a similar problem also occurs when the DCI 2_4 format is reintroduced.

In this regard, the UE may prioritize one or more SSs configured for the UE. In particular, the UE may prioritize one or more SSs whether or not each SS is an SS (eg, a USS) to monitor the DCI format 0_2/1_2 (first prioritization). Alternatively, the UE may prioritize one or more SSs based on whether or not each SS is an SS (eg, USS) to monitor DCI format 0_2/1_2 (second prioritization).

First prioritization

When prioritizing for the first time, the priority of SSs can be determined based on search space IDs (SS-set indexes), regardless of whether each SS is an SS (eg, USS) for DCI format monitoring 0_2/1_2. For example, the priority of an SS having a lower (lower) search space ID may be defined to override the priority of an SS having a larger (higher) search space ID.

In FIG. 8 is a diagram illustrating one example of the first prioritization of SSs according to the third aspect. Although in FIG. 8 shows SS sets #1 to #5 configured for UE, number, ID, etc. the SS sets configured for the UE are not limited to those shown in the drawing. For example, SS set #0 may be configured for the UE.

For example, in FIG. 8, SS set #1 is a CSS set, SS set #2 is a USS set for DCI 0_0/1_0 format, SS set #3 is a USS set for DCI 0_1/1_1 format, SS set #4 is a USS set for DCI 0_1/1_1 format, DCI 0_2/1_2 format, and SS set #5 is the USS set for DCI 0_2/1_2 format.

As shown in FIG. 8, in the first prioritization, the priority of the SSs can be configured based on the search space IDs whether or not each SS is a USS for the DCI 0_2/1_2 format. For example, in FIG. 8, a higher priority is configured for the SS having a smaller (lower) search space ID.

When at least some of the monitoring events of the respective SSs #1 to #5 overlap in the same time unit (eg, slot), the UE may control the monitoring of the SSs #1 to #5 based on the search space IDs. In particular, the UE may prioritize monitoring an SS having a small search space ID over monitoring an SS having some search space ID.

It should be noted that in FIG. 8, SS #1 to #5 are prioritized based on search space IDs regardless of search space types, but this option is not restrictive. The priority of SS #1 - #5 may be determined based on the search space IDs and search space types. For example, the CSS set priority may be defined to be higher than the USS set priority, and among SSs having the same search space type, the SS set priority may be determined in ascending order or in descending order of search space IDs.

Second prioritization

In the second prioritization, the priority of the SSs may be determined based on whether or not each SS is an SS (eg, a USS) for DCI format monitoring 0_2/1_2. For example, the priority of the DCI format monitoring SS 0_2/1_2 may be defined to be higher than the priority of the monitoring SS for other DCI formats.

In FIG. 9 is a diagram illustrating one example of the second SS prioritization according to the third aspect. With reference to FIG. 9 mainly discloses the differences from FIG. eight.

As shown in FIG. 9, in the second prioritization, the priority of the SSs may be configured based on whether or not each SS is a USS for DCI format 0_2/1_2. For example, in FIG. 9, the priority of SSs #4 and #5, each of which is a USS for DCI format 0_2/1_2, is determined to be higher than the priority of other SSs #1 to #3.

In addition, in the second prioritization, among the SSs #4 and #5, each of which is the USS for DCI format 0_2/1_2, the priority of the SSs #4 and #5 can be determined based on the search space IDs. For example, in FIG. 9, SS #4 having a lower search space ID takes precedence over SS #5 having a larger search space ID.

By analogy, among SSs #1 to #3 other than the USSs for DCI format 0_2/1_2, the priority of SSs #1 to #3 can be determined based on search space IDs. For example, in FIG. 9, the priority of SSs #1 to #3 is determined to be assigned in ascending order of search space IDs.

When at least some of the monitoring events of the respective SSs #1 to #5 overlap in the same time unit (eg, slot), the UE may control monitoring of the SSs #1 to #4 based on whether or not each SS set by USS set for DCI format 0_2/1_2, and search space IDs.

It should be noted that in FIG. 9, the priority of SS #1 to #3 is determined based on search space IDs regardless of search space types; but this option is not limiting. The priority of SSs #1 - #3 can be determined based on the IDs of the search spaces and the types of search spaces. For example, the CSS set priority may be defined to be higher than the USS set priority, and among SSs having the same search space type, the SS set priority may be assigned in ascending or descending order of search space IDs.

As disclosed above, in the third aspect, even if the DCI format 0_2/1_2 is introduced, and the monitoring events of one or more SSs configured for the UE are overridden, the monitoring can be properly managed according to the priority of the SSs.

Other aspects

It should be noted that the first aspect and the second aspect can be combined with each other. For example, the configuration information SS of FIG. 2 or the second configuration information SS of FIG. 4 and the configuration information SS of FIG. 6 or FIG. 7 can be combined.

In particular, when combining parts of the configuration information SS in FIG. 2 and 6, the DCI format information (eg, RRC IE "dci-Formats") in the USS set information (eg, RRC IE "ue-Specific") of FIG. 6 may indicate one of DCI format 0_0/1_0, DCI format 0_1/1_1, and DCI format 0_2/1_2.

In addition, when combining parts of the configuration information SS in FIG. 2 and 7, the DCI format information (eg, RRC IE "dci-Formats") in the USS set information (eg, RRC IE "ue-Specific") of FIG. 7 may indicate one of DCI format 0_0/1_0, DCI format 0_1/1_1, DCI format 0_2/1_2, and DCI format 2_4.

In addition, when combining the second configuration information SS in FIG. 4 and the configuration information SS of FIG. 6, the CSS set information (eg, RRC IE "sottop") in the second configuration information SS (eg, RRC IE "SearchSpace-v16") of FIG. 4 may contain DCI 2_4 format information (eg RRC IE "dci-Format2-4").

In addition, when combining the second configuration information SS in FIG. 4 and the configuration information SS of FIG. 7, the DCI format information (eg, RRC IE "dci-Formats") in the USS set information (eg, RRC IE "ue-Specific") in the second SS configuration information (eg, RRC IE "SearchSpace-v16") of FIG. . 4B may point to one of DCI format 0_0/1_0, DCI format 0_1/1_1, DCI format 0_2/1_2, and DCI format 2_4.

In addition, the second aspect and the third aspect, or the first to third aspects, can be combined with each other. For example, although the SS set for the DCI 2_4 format is not explicitly shown in FIG. 8 and 9, the SS set priority for the DCI 2_4 format may also be determined according to the first or second prioritization.

Radio communication system

Further, the structure of a radio communication system according to one embodiment of the present invention is disclosed. In this radio communication system, the radio communication method according to each embodiment of the present invention disclosed above may be used alone or may be used in combination to provide communication.

In FIG. 10 is a diagram illustrating one example of a schematic structure of a radio communication system according to one embodiment. The radio communication system 1 may be a system implementing communication using an LTE (Long Term Evolution) scheme, a 5th generation New Radio (5G NR) mobile communication system, etc., the specifications of which are developed by Third Generation Partnership Project (3GPP).

The radio communication system 1 may support dual connectivity (MR-DC, Multi-RAT Dual Connectivity) between multiple RATs (Radio Access Technology; radio access technology). The MR-DC may include dual connectivity EN-DC (E-UTRA-NR dual connection) between LTE (E-UTRA: Evolved Universal Terrestrial Radio Access) and NR scheme, NE-DC dual connection capability (NR-E-UTRA dual connection) between NR and LTE scheme, etc.

Under EN-DC, the base station (eNB) of the LTE scheme (E-UTRA) is the Master Node (MN), and the base station (gNB) of the NR scheme is the Secondary Node (SN). .Secondary Node). In NE-DC, the base station (gNB) of the NR scheme is MN, and the base station (eNB) of the LTE (E-UTRA) scheme is SN.

The radio communication system 1 can support dual connectivity between multiple base stations in the same RAT (for example, NN-DC dual connectivity (NR-NR Dual Connectivity) when both MNs and SNs are both base stations (nodes gNB) according to NR).

The radio communication system 1 may comprise a base station 11 which forms a macro cell C1 with a relatively wide coverage, and base stations 12 (12a to 12c) which form small cells C2 and are located within the macro cell C1 and which are already macro cells C1. The user terminal 20 may reside in at least one cell. Location, quantity, etc. each cell and the user terminal 20 are in no way limited to the aspect illustrated in this diagram. Hereinafter, base stations 11 and 12 are collectively referred to as "base stations 10" unless otherwise indicated.

The user terminal 20 may be connected to at least one of a plurality of base stations 10. The user terminal 20 may use at least one of the following procedures: carrier aggregation (CA, from the English Carrier Aggregation) and double connection (DC), using set of component carriers (CC, from the English Component Carrier).

Each CC may be contained in at least one of a first frequency band (FR1: frequency band 1) and a second frequency band (FR2: frequency band 2). Macro cell C1 may be contained in FR1 and small cells C2 may be contained in FR2. For example, FR1 may represent a frequency range of 6 GHz or less ("sub-6" GHz), and FR2 may represent a frequency range greater than 24 GHz ("above-24" GHz). It should be noted that frequency ranges, definitions, etc. for FR1 and FR2 are not limited to this description in any way, and, for example, FR1 may correspond to a frequency range greater than FR2.

The user terminal 20 may communicate using at least one of the following types of communication, for example, time division duplex (TDD) and frequency division duplex (FDD). in each SS.

The plurality of base stations 10 may be connected via a wired connection (eg, using optical fibers conforming to CPRI (Common Public Radio Interface), X2 interface, etc.) or wirelessly (eg, NR communications). For example, if the NR link is used as a backhaul between base stations 11 and 12, base station 11 corresponding to the higher level station may be referred to as "IAB (Integrated Access Backhaul) donor" and base station 12 , corresponding to the relay station (relay), may be referred to as "IAB node".

The base station 10 may be connected to the core network 30 through another base station 10 or directly. For example, the backbone network 30 may include at least one of the following devices, namely, an Evolved Packet Core (EPC), a 5G backbone network (5GCN), a Next Generation Core (NGC). Core), etc.

The user terminal 20 may be a terminal supporting at least one of the following communication schemes, namely, LTE, LTE-A, 5G, and so on.

In the radio communication system 1, it is possible to use a radio access scheme based on Orthogonal Frequency Division Multiplexing (OFDM). For example, at least one of the following links: downlink (DL) communication line and uplink (UL) communication can be applied OFDM with a cyclic prefix (CP-OFDM, from the English. Cyclic Prefix OFDM), OFDM with a discrete Fourier transform ( DFT-s-OFDM, Discrete Fourier Transform Spread OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA, from Single Carrier Frequency Division Multiple Access), etc.

The radio access scheme may be referred to as a "waveform". It should be noted that, in the radio communication system 1, it is possible to use another radio access scheme (eg, another single carrier transmission scheme, another multi-carrier transmission scheme) as the uplink (UL) and downlink (DL) radio access scheme.

In the radio communication system 1, downlink channels (PDSCH: Physical Downlink Shared Channel) shared by each user terminal 20, Broadcast Channel (PBCN: Physical Broadcast Channel), Downlink Control Channel (PDCCH: Physical Downlink Control Channel) can be used as downlink channels. ) etc.

In the radio communication system 1, uplink channels (PUSCH: Physical Uplink Common Channel) shared by each user terminal 20, Uplink Control Channel (PUCCH: Physical Uplink Control Channel), Random Access Channel (PRACH: Physical Uplink random access), etc.

User data, higher-level control information, System Information Blocks (SIBs), etc. transmitted over the PDSCH. User data, higher level management information, etc. may be transmitted on PUSCH. Blocks of basic information (MIB, from the English Master Information Block) can be transmitted over the Strategic Missile Forces.

The lower layer control information may be transmitted on the PDCCH. For example, the lower layer control information may comprise downlink control information (DCI), including scheduling information of at least one of the PDSCH and PUSCH.

Note that the DCI for PDSCH scheduling may be referred to as "DL assignment", "DL DCI", etc., and the DCI for PUSCH scheduling may be referred to as "UL grant", "UL DCI", etc. It should be noted that PDSCH can be interpreted as "DL data" and PUSCH can be interpreted as "UL data".

To detect PDCCH, you can use the control resource set (CORESET, from the English Control Resource Set) and the search space. CORESET corresponds to a resource for DCI lookup. The search space corresponds to the search area and the search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may control the CORESET associated with the given search space based on the search space configuration.

One search space may correspond to a PDCCH candidate corresponding to one or more levels of aggregation. One or more search spaces may be referred to as a "set of search spaces". It should be noted that "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc., can be interpreted as synonyms in the present description.

Uplink Control Information (UCI), including at least one of the following types of information, namely, Channel State Information (CSI), Transmission Acknowledgment Information (which is also may be referred to, for example, as an acknowledgment of a hybrid automatic repeat request (HARQ-ACK, from the English. Hybrid Automatic Repeat Request Acknowledgment), ACK / NACK, etc.), and a scheduling request (SR, from the English. Scheduling Request) can be transmitted on PUCCH. Through the PRACH, random access preambles can be transmitted to establish connections with cells.

It should be noted that the concepts of "descending", "ascending", etc. in the present description can be used without adding the words "link" to them. Also, different channels can be expressed without adding the word "physical" to the title.

In the radio communication system 1, it is possible to transmit a synchronization signal (SS, from the English Synchronization Signal), a downlink reference signal (DL-RS, from the English Downlink Reference Signal), etc. In the radio communication system 1, as DL-RS, it is possible to transmit a cell-specific reference signal (CRS, from the English Cell-specific Reference Signal), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS, from the English. Demodulation Reference Signal), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc.

For example, the synchronization signal may be at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The signal block containing the SS (PSS, SSS) and the Strategic Missile Forces (and DMRS for the Strategic Missile Forces) may be referred to as "SS block/RVSN", "SS block (SSB)", etc. Also, SS, SSB, etc. may also be referred to as a "reference signal".

In the radio communication system 1, as an uplink reference signal (UL-RS, from the English Uplink Reference Signal), it is possible to transmit a sounding reference signal (SRS, from the English Sounding Reference Signal), a demodulation reference signal (DMRS), etc. It should be noted that DMRS may be referred to as "user terminal specific reference signal (UE specific reference signal)".

Base station

In FIG. 11 is a diagram illustrating one example of the structure of a base station according to the present embodiment. The base station 10 includes a control section 110, a transmitting/receiving section 120, transmitting/receiving antennas 130, and a transmission line interface 140. It should be noted that base station 10 may include one or more control sections 110, one or more transmit/receive sections 120, one or more transmit/receive antennas 130, and one or more transmission line interfaces 140.

It should be noted that in this example, the functional blocks corresponding to the characteristic parts according to this embodiment are mainly illustrated, and it is assumed that the base station 10 may also contain other functional blocks that are necessary for radio communication. Some of the processes of each section disclosed below may be omitted.

The control section 110 controls the entire base station 10. The control section 110 may be formed by a controller, a control loop, etc., which can be disclosed based on public knowledge in the technical field to which the present invention pertains.

The control section 110 may control signal generation, scheduling (eg, resource allocation, display), and so on. The control section 110 can control transmission and reception, measurement, etc., using the transmission/reception section 120, the transmission/reception antennas 130, and the transmission line interface 140. The control section 110 may create data, control information, a sequence, and so on. as a signal for transmission, and forward the created elements to the transmitting/receiving section 120. The control section 110 can perform call processing (configuration, disconnection) for communication channels, state control of the base station 10, and radio resource control.

Transmitting/receiving section 120 may include a baseband section 121, a radio frequency (RF) section 122, and a measurement section 123. Baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212. The transmit/receive section 120 may be formed by a transmitter/receiver, RF loop, baseband loop, filter, phase shifter, measurement loop, transmit/receive loop, etc., which may be disclosed based on public knowledge in the art, to to which the present invention relates.

The transmitting/receiving section 120 may be formed as an integrated transmitting/receiving section, or may be composed of a transmitting section and a receiving section. The transmitting section may consist of a transmit processing section 1211 and an RF section 122. The receiving section may consist of a receive processing section 1212, an RF section 122, and a measurement section 123.

Transmitting/receiving antennas 130 may be composed of antennas such as a trellis antenna, etc., which may be disclosed based on public knowledge in the technical field to which the present invention pertains.

The transmitting/receiving section 120 may transmit the downlink, synchronization signal, downlink reference signal, etc. disclosed above. The transmit/receive section 120 may receive the uplink, uplink reference signal, etc. disclosed above.

The transmit/receive section 120 may shape at least one of a transmit beam and a receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase sequence), and so on.

The transmitting/receiving section 120 (transmission processing section 1211) can perform Packet Data Convergence Protocol (PDCP) layer processing, RLC (Radio Link Control; radio link control) layer processing (for example, retransmission control with RLC), MAC (Medium Access Control) layer processing (for example, HARQ retransmission control), etc., for example, with respect to data and control information, etc. obtained from the control section 110 , and can create a sequence of bits to transmit.

The transmit/receive section 120 (transmit processing section 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary) , processing with inverse fast Fourier transform (IFFT, from the English. Inverse Fast Fourier Transform), precoding, digital-to-analog conversion, etc. with respect to the bit sequence to be transmitted, and outputs a baseband signal.

The transmitting/receiving section 120 (RF section 122) can perform RF modulation, filtering, amplification, and so on. with respect to the baseband signal, and transmit the RF signal through the transmit/receive antennas 130.

On the other hand, the transmit/receive section 120 (RF section 122) may perform amplification, filtering, demodulation to baseband, etc., on the RF signal received via the transmit/receive antennas 130.

The transmitting/receiving section 120 (reception processing section 1212) may apply reception processing such as A/D conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT), .Inverse Discrete Fourier Transform) (if necessary), filtering, reconstruction, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, PDCP layer processing, etc. regarding the received baseband signal, and receive user data, etc.

The transmitting/receiving section 120 (measuring section 123) may perform a measurement on the received signal. For example, the measurement section 123 can perform Radio Resource Management (PRM) measurement, Channel State Information (CSI) measurement, and so on. based on the received signal. The measuring section 123 can measure the received power (for example, the power of the received reference signal (RSRP, from the English Reference Signal Received Power)), the received quality (for example, the quality of the received reference signal (RSRQ, from the English Reference Signal Received Quality)), the ratio signal-mixture of interference with noise (SINR, from the English Signal to Interference plus Noise Ratio), the ratio of signal to interference (SNR, from the English Signal to Noise Ratio)), signal intensity (for example, the indicator of the received signal level (RSSI, from Received Signal Strength Indicator)), channel information (for example, CSI), etc. The measurement results may be output to the control section 110 .

The transmission line interface 106 can transmit/receive (signaling in the reverse direction) a signal with a machine included in the core network 30 or other base stations 10, etc., and receive or transmit user data (user plane data) control plane data, etc. for user terminal 20.

It should be noted that the transmitting section and receiving section of the base station 10 according to the present invention may be composed of at least one of the following devices: the transmitting/receiving section 120, the transmitting/receiving antennas 130, and the interface 140 of the transmission line.

It should be noted that the transmitting/receiving section 120 transmits downstream control information. Transmitting/receiving section 120 may receive an uplink signal (eg, an uplink common channel) and transmit a downlink signal (eg, a downlink common channel). Transmitting/receiving section 120 transmits search space set configuration information. The transmitting/receiving section 120 may transmit configuration information (eg, UE-specific PDCCH information or cell-specific PDCCH information) of the downlink control channel.

User terminal

In FIG. 12 is a diagram illustrating one example of the structure of a user terminal according to the present embodiment. The user terminal 20 includes a control section 210, a transmitting/receiving section 220, and transmitting/receiving antennas 230. It should be noted that the user terminal 20 may include one or more control sections 210, one or more transmitting/receiving sections 220, and one or more transmitting/receiving receiving antennas 230.

It should be noted that in this example, functional blocks are mainly illustrated that correspond to the characteristic parts of the considered embodiment, and it is assumed that the user terminal 20 may also contain other functional blocks that are necessary for radio communication. Some of the processes of each section disclosed below may be omitted.

The control section 210 controls the entire user terminal 20. The control section 210 may be formed by a controller, a control loop, etc., which may be disclosed based on public knowledge in the technical field to which the present invention pertains.

The control section 210 may control signal generation, display, and so on. The control section 210 can control transmission/reception, measurement, etc., using the transmitting/receiving section 220 and the transmitting/receiving antennas 230. The control section 210 generates data, control information, sequence, etc., as a signal for transmission, and may direct the created elements to the transmit/receive section 220.

The transmitting/receiving section 220 may include a baseband section 221, an RF section 222, and a measurement section 223. The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212. The transmit/receive section 220 may be formed by a transmitter/receiver, RF loop, baseband loop, filter, phase shifter, measurement loop, transmit/receive loop, etc., which may be disclosed based on public knowledge in the art, to to which the present invention relates.

The transmitting/receiving section 220 may be formed as an integrated transmitting/receiving section, or may be composed of a transmitting section and a receiving section. The transmitting section may consist of a transmit processing section 2211 and an RF section 222. The receiving section may consist of a receive processing section 2212, an RF section 222, and a measurement section 223.

Transmitting/receiving antennas 230 may be comprised of antennas such as a trellis antenna, etc. disclosed based on public knowledge in the art to which the present invention pertains.

The transmitting/receiving section 220 may receive the downlink, synchronization signal, downlink reference signal, etc. disclosed above.

The transmit/receive section 220 may transmit the uplink, uplink reference signal, etc. disclosed above.

The transmit/receive section 220 may shape at least one of the transmit beam and the receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase sequence), and so on.

The transmitting/receiving section 220 (transmission processing section 2211) may perform PDCP layer processing, RLC layer processing (eg, RLC retransmission control), MAC layer processing (eg, HARQ retransmission control), etc., for example, with respect to data, control information, etc. received from the control section 210, and may create a bit sequence for transmission.

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

It should be noted that the choice of whether or not to apply DFT processing may be based on a transform precoding configuration. If transform precoding is enabled, then the transmitting/receiving section 220 (transmission processing section 2211) may perform, for a given channel (eg, PUSCH), DFT processing as the transmission processing disclosed above to transmit the indicated channel using the DFT-s waveform. -OFDM, otherwise, it may not perform DFT processing as the transfer processing disclosed above.

The transmitting/receiving section 220 (RF section 222) can perform RF modulation, filtering, amplification, and so on. with respect to the baseband signal, and transmit the RF signal through the transmit/receive antennas 230.

On the other hand, the transmit/receive section 220 (RF section 222) may perform amplification, filtering, demodulation to baseband, etc., on the RF signal received via the transmit/receive antennas 230.

The transmit/receive section 220 (receive processing section 2212) may apply receive processing such as A/D conversion, FFT processing, IDFT processing (if necessary), filtering, reconstruction, demodulation, decoding (which may include error correction decoding ), MAC layer processing, RLC layer processing, PDCP layer processing, etc. regarding the received baseband signal, and receive user data, etc.

The transmitting/receiving section 220 (measuring section 223) may perform a measurement on the received signal. For example, the measurement section 223 may perform a PRM measurement, a CSI measurement, and so on. based on the received signal. Measurement section 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and so on. The measurement results may be output to the control section 210 .

It should be noted that the transmitting section and receiving section of the user terminal 20 according to the present invention may be composed of at least one of the following: a transmitting/receiving section 220, transmitting/receiving antennas 230, and a transmission line interface 240.

It should be noted that the transmitting/receiving section 220 receives downstream control information. Transmitting/receiving section 220 may receive an uplink signal (eg, an uplink common channel) and receive a downlink signal (eg, a downlink common channel). The transmitting/receiving section 220 receives configuration information (configuration information SS) of a set of search spaces. The transmitting/receiving section 220 may receive configuration information (eg, UE-specific PDCCH information or cell-specific PDCCH information) of the downlink control channel.

The control section 210 may control the monitoring of downlink control information (DCI) of a first format (eg, DCI format 0_2) other than the 0_0 and 0_1 formats used for uplink common channel scheduling, and a second format (eg, DCI format 1_2) other than the formats 1_0 and 1_1 used for scheduling a downlink common channel in a search space set configured based on the configuration information (first aspect).

The configuration information may include information for specifying one of the 0_0 and 1_0 formats, the 0_1 and 1_1 formats, and the first and second formats as the DCI format controlled in the search space set (eg, FIGS. 2 and 4).

The configuration information may be for a specific set of search spaces for monitoring the first and second formats (eg, FIG. 3), or for a user terminal 20 that allows monitoring of the first and second formats (eg, FIG. 4).

The control section 210 may prioritize the search space set based on at least one of the search space set IDs and whether or not the first and second formats in the search space set are controlled (third aspect).

The control section 210 may control monitoring of a third DCI format (eg, DCI format 2_4) including an upstream preempt indication in a search space set configured based on the configuration information (second aspect).

Hardware structure

It should be noted that the block diagrams used to describe the above embodiments illustrate blocks in functional units. These functional blocks (components) may be implemented by arbitrary combinations of at least one of hardware and software. In addition, the implementation method of each function block is not limited to a specific method. That is, each functional block may be implemented by a single physically or logically connected apparatus, or may be implemented by connecting two or more physically or logically independent apparatuses directly or indirectly (via, for example, a wired connection, a wireless connection, etc.). ) and using many of these devices. The functional blocks may be implemented by combination of software with one apparatus mentioned above or a plurality of apparatuses mentioned above.

In this case, the functions include evaluating, determining, deciding, calculating, calculating, processing, receiving, examining, searching, confirming, receiving, transmitting, inferring, accessing, resolving, selecting, setting, establishing, comparing, assuming, waiting, consideration, broadcast, notification, communication, forwarding, configuration, reconfiguration, allocation (display), assignment, etc., however, the functions are not limited to these examples. For example, the functional block(s) for implementing the transmission function may be referred to as "transmitting section (transmitting block)", "transmitter", etc. As disclosed above, the method for implementing each component is not limited to the specific method disclosed above.

For example, base station, user terminal, etc. according to one embodiment of the present invention, may function as a computer that executes processes in accordance with the radio communication method of the present invention. In FIG. 13 is a diagram illustrating one example of a hardware structure of a base station and a user terminal according to the present embodiment. Physically, each of the following devices, namely the above-mentioned base station 10 and the user terminal 20, can be formed as a computing device containing a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007 etc.

It should be noted that in the following description, concepts such as apparatus, circuit, device, section, block, etc. can be interpreted as synonyms. The hardware structure of base station 10 and user terminal 20 may be configured to include one or more of the apparatuses illustrated in the drawings, or may be configured without some of these apparatuses.

For example, although only one processor 1001 is shown in the drawings, multiple processors may be provided. In addition, the processes may be executed by a single processor, or may be implemented simultaneously, sequentially, or otherwise by two or more processors. It should be noted that processor 1001 may be implemented with one or more chips.

Each function of base station 10 and user terminals 20 is implemented, for example, by having hardware such as processor 1001 and memory 1002 read predetermined software(s), whereby processor 1001 can perform calculations to control communication by the apparatus. 1004 communication and control of at least one of the following processes: reading and writing data to the memory 1002 and the drive 1003.

Processor 1001, for example, employs an operating system to control the entire computer. The processor 1001 may be formed by a central processing unit (CPU, from the English Central Processing Unit) containing interfaces for peripheral devices, a control apparatus, a computing apparatus, a register, etc. For example, at least some of the control section 110 (210) mentioned above, the transmitting/receiving section 120 (220), etc. may be implemented by the processor 1001.

In addition, the processor 1001 reads programs (program codes), program modules, data, and so on. from at least one of the storage 1003 and the communication apparatus 1044 to the memory 1002, and performs various processes in accordance therewith. With respect to programs, programs are used that cause computers to perform at least some of the operations disclosed in the above embodiments. For example, control section 110 (210) may be implemented by means of program codes stored in memory 1002 and executed in processor 1001, and other functional blocks may be implemented in a similar manner.

The memory 1002 is a computer-readable storage medium, and may be formed, for example, by at least one of the following: read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), random access memory (RAM) ) and other suitable storage media. The memory 1002 may be referred to as "register", "cache", "main memory (main storage)", etc., for example. The memory 1002 may store executable programs (program codes), program modules, etc., for implementing the radio communication method according to the exemplary embodiment of the present invention.

The drive 1003 is a computer-readable storage medium and may be formed by, for example, at least one of the following: a floppy disk, a floppy disk (registered trademark), a magneto-optical disk (for example, a compact disc (CD-ROM ), etc.), digital versatile disc, Blu-ray Disc (registered trademark)), removable disc, hard disk drive, smart card, flash memory device (such as a card, storage band, database, server, and other suitable storage medium. The drive 1003 may be referred to as "backup storage".

The communication apparatus 1004 is a hardware (transmitter/receiver) that enables communication between computers via at least one of wired and wireless networks, and which is also referred to as, for example, "network device", "network controller", " network card", "communication module", etc. The communication apparatus 1004 may be configured to include a high frequency switch, a duplexer, a filter, a frequency synthesizer, and so on. to implement at least one of the following types of communication, for example, frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmit/receive section 120 (220), transmit/receive antennas 130 (230), etc. may be implemented by the communications apparatus 1004. In the transmitting/receiving section 120 (220), the transmitting section 120a (220a) and the receiving section 120b (220b) may be implemented as physically or logically separate devices.

The input apparatus 1005 is an input device that receives input from outside (eg, keyboard, mouse, microphone, switch, button, sensor, etc.). The output apparatus 1006 is an output device that allows output data to be sent to the outside (for example, a display, a speaker, a light emitting diode (LED, Light Emitting Diode), etc.). It should be noted that the input apparatus 1005 and the output apparatus 1006 may be implemented as an integrated structure (eg, a touch panel).

In addition, these types of apparatuses, including the processor 1001, the memory 1002, and other apparatuses, are connected via a bus 1007 to transmit information. Bus 1007 may be made using a single bus or may be formed with tires that differ between devices.

In addition, the base station 10 and the user terminals 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP, Digital Signal Processor), an application-specific integrated circuit (ASIC). Specific Integrated Circuit), a programmable logic device (PLD, from the English Programmable Logic Device), a user-programmable gate array (FPGA, from the English Field Programmable Gate Array), etc., and some or all of the functional blocks can be implemented through hardware. For example, processor 1001 may be implemented with at least one of these hardware components.

Variations

It should be noted that the terminology disclosed in this specification and the terminology necessary for understanding the present invention may be replaced by other terms having the same or similar meanings. For example, "channel", "symbol" and "signal" (or signaling information) can be interpreted as synonyms. In addition, "signals" may be "messages". The reference signal may also be abbreviated to "RS" (Reference Signal; reference signal) or may be referred to as "pilot signal", "pilot signal", etc., depending on the applicable standards. Moreover, "component carrier (CC)" may be referred to as "cell", "carrier", "carrier frequency", etc.

A radio frame may consist of one or multiple periods (frames) in the time domain. Each of the one or multiple periods (frames) that make up a radio frame may be referred to as a "subframe". In addition, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time duration (eg, 1 ms) that is independent of numerology.

In this case, numerology may be a communication parameter applicable to at least one of the following processes: the transmission and reception of a particular signal or channel. For example, numerology can indicate at least one of the following parameters, for example, subcarrier spacing (SCS, from English Subcarrier Spacing), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI, from English. Transmission Time Interval ), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, specific framing processing performed by the transceiver in the time domain, and so on.

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

A slot may contain a plurality of minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may be referred to as a "subslot". A minislot can contain fewer symbols than slots. A PDSCH (or PUSCH) to be transmitted in larger units of time compared to a minislot may be referred to as "PDSCH Mapping Type A (PUSCH)". The PDSCH (or PUSCH) to be transmitted with the minislot may be referred to as "PDSCH Map Type B (PUSCH)".

All of the following terms: radio frame, subframe, slot, minislot, and symbol, denote units of time for signaling. Other suitable names may be used to refer to a radio frame, subframe, slot, minislot, and symbol. It should be noted that time units such as frame, subframe, slot, minislot, and symbol can be interpreted as synonyms in the present description.

For example, one subframe may be referred to as "TT1", multiple adjacent subframes may be referred to as "TT1", or one slot or one minislot may be referred to as "TT1". That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the current LTE scheme, may be a period shorter than 1 ms (eg, 1 to 13 symbols), or may be a period longer than 1 ms. It should be noted that the unit that reflects the TTI may be referred to as "slot", "minislot", etc. instead of "subframe".

In this case, TTI refers to, for example, the minimum unit of time for radio scheduling. For example, in LTE systems, a base station performs scheduling to allocate radio resources (eg, frequency bandwidth and transmit power that are available for each user terminal) in units of TTI for the user terminal. It should be noted that the definition of TTI is not limited to the given example.

TTIs may be units of transmission time of data packets (transport blocks) that undergo channel coding, code blocks, or code words, or may be processing units in scheduling, link adaptation, and so on. It should be noted that given TTIs, the time interval (eg, number of symbols) in which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

It should be noted that when one slot or one minislot is referred to as a TTI, one or more TTIs (ie, one or more slots or one or more minislots) may represent a minimum unit of scheduling time. In addition, the number of slots (number of minislots) that constitutes the minimum unit of scheduling time can be controlled.

A TTI having a time duration of 1 ms may be referred to, for example, as "normal TTI" (TTI according to 3GPP draft versions 8-12), "long TT1", "normal subframe", "long subframe", "slot" etc. A TTI shorter than a normal TTI may be referred to, for example, as "short TT1", "short TT1", "partial or fractional TT1", "short subframe", "short subframe", "minislot", "subslot", "slot", etc. d.

It should be noted that a long TTI (eg, normal TTI, subframe, etc.) may be interpreted as a TTI having a time duration greater than 1 ms, and a short TTI (eg, short TTI, etc.) may be interpreted as a TTI , having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

A resource block (RB) is a unit of resource allocation in the time domain and frequency domain, and may contain one or more contiguous sub-carriers in the frequency domain. The number of sub-carriers contained in the RB may be the same regardless of the numerology, and may, for example, be 12. The number of sub-carriers contained in the RB may be determined based on the numerology.

In addition, a RB may comprise one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc., each may contain one or more resource blocks.

It should be noted that one or a plurality of RBs may be referred to as, for example, "Physical Resource Block (PRB)", "Sub-Carrier Group (SCG)", "Resource Element Group". (REG, from the English Resource Element Group)”, “PRB pair”, “RB pair”, etc.

In addition, a resource block may contain one or more resource elements (RE, Resource Element). For example, one RE may correspond to a radio resource area of one subcarrier and one symbol.

Partial bandwidth (BWP) (which may be referred to as "partial bandwidth", etc.) may denote a subset of contiguous common resource blocks (common RBs) for a particular numerology in a particular carrier. Here, the common RB may be set by the RB index based on the common carrier reference point. The PRB may be defined by a particular BWP and may be numbered in the specified BWP.

The BWP may comprise an uplink BWP (UL BWP) and a downlink BWP (DL BWP). A UE may be configured with one or multiple BWPs on a single carrier.

At least one of the configured BWPs may be active and the UE may prevent a given signal/channel from being transmitted/received outside of the active BWPs. It should be noted that "cell", "carrier", etc. in this description can be interpreted as "BWP".

It should be noted that the above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are just examples. For example, structures such as the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in a RB, the number of symbols in a TTI , character length, cyclic prefix length (CP, from the English Cyclic Prefix), etc., can vary in various ways.

In addition, the information, parameters, etc. disclosed in this specification may be expressed in absolute terms or in relative terms with respect to predetermined values, or may be expressed in terms of other relevant information. For example, radio resources may be designated by specific indexes.

Names used for parameters, etc. in this description are by no means limiting. In addition, mathematical expressions that use these parameters, etc. may differ from those explicitly disclosed in this specification. For example, since the various channels (PUCCH, PDCCH, etc.) and information elements may be designated by any suitable names, the various names associated with these various channels and information elements are in no way limiting.

The information, signals, etc. set forth in this specification may be expressed using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, microcircuits, etc. mentioned throughout the above description may be expressed as voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields, or photons, or any combination of them.

In addition, information, signals, etc. may be issued in at least one of the following ways: from high levels to low levels and from low levels to high levels. Information, signals, etc. may be entered and/or withdrawn by a plurality of network nodes.

Input and/or output information, signals, etc. may be stored in a specific location (eg memory) or may be controlled by a control table. Input and/or output information, signals, etc. can be overwritten, updated, or overwritten. Output information, signals, etc. can be removed. Input information, signals, etc. can be transferred to other devices.

Notification of information is in no way limited to the aspects/embodiments disclosed in this specification, and may be implemented using other methods. For example, information notification can be implemented in the present invention 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 (basic information block (MIB), system information blocks (SIB), etc.), medium access control (MAC) signaling), and other signals, or combinations thereof.

It should be noted that the physical layer signaling may be referred to as "layer 1/layer 2 (L1/L2) control information (L1/L2 control signals)", "L1 control information (L1 control signal)", etc. In addition, the RRC signaling may be referred to as an "RRC message" and may be, for example, an "RRCConnectionSetup" message, an "RRCConnectionReconfiguration" message, and so on. In addition, notification of MAC signaling can be sent using, for example, MAC control elements (MAC CE).

Moreover, notification of predetermined information (eg, notification that "X supports") is not limited to explicit notification, and may be sent implicitly (eg, without notification of this predetermined information or by notification of other information).

Decisions can be made as values expressed as a single bit (0 or 1), can be made as boolean values expressed as true or false values, or can be made by comparing numerical values (e.g., comparing with a given value).

Software, whether referred to as "software", "firmware", "middleware", "microcode" or "hardware description language", or referred to by other names, is to be construed broadly. sense to refer to instructions, instruction sets, code, code segments, program codes, programs, subroutines, program modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc. .d.

Also, software, commands, information, etc. can be transmitted and received via the transmission medium. When, for example, software is transferred from a website, server, or other remote source using at least one of the wired technologies (coaxial cables, fiber optic cables, twisted-pair cables, Digital Subscriber Lines (DSL), etc.) etc.) and wireless technologies (infrared, microwaves, etc.), at least one of these wired technologies and wireless technologies is also part of the transmission medium definition.

The terms "system" and "network" as used herein may be used interchangeably. The term "network" may refer to a device (eg, base station) included in the network.

In this specification, terms such as "precoding", "precoder", "weight (precoding weight)", "quasi-co-location (QCL)," "transmission configuration indication status" (TCI, from the English Transmission Configuration Indication) (or TCI state)”, “spatial relation”, “spatial domain filter”, “transmit power”, “phase rotation”, “antenna port”, “antenna port group”, “ level", "number of levels", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", " panel”, etc. can be used interchangeably.

In this description, terms such as "base station (BS)", "radio base station", "fixed station", node "NodeB", node "eNodeB (eNB)", node "gNodeB (gNB)", "access point ”, “transmission point (TP, from the Transmission Point)”, “reception point” (RP, from the English Reception Point), “transmission / reception point (TRP)”, “panel”, “cell”, “sector”, "cell group", "carrier", "component carrier", etc. can be used interchangeably. A base station may also be referred to as "macro cell", "small cell", "femto cell", "pico cell", etc.

The base station may contain one or multiple (eg, three) cells. If the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of small areas, each small area can also provide communication services through the base station subsystems (for example, indoor small base stations (PRH: Remote Radio Node)). The term "cell" or "sector" refers to part of the coverage area or the entire coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

In this description, the terms "mobile station (MS)", "user terminal", "user equipment (UE, from the English. User Equipment)" and "terminal" can be used interchangeably.

A mobile station may in some cases also be referred to by one of skill in the art as a "user terminal", "mobile unit", "subscriber station", "wireless unit", "remote unit", "mobile device", "wireless device", " wireless device", "remote device", "mobile subscriber terminal", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client" , "client" or other appropriate names.

At least one of the base station and the mobile station may be referred to as "transmitter", "receiver", "communication unit", etc., for example. It should be noted that at least one of the base station and the mobile station may, for example, be a device mounted on a mobile object or the mobile object itself, etc. The movable object may be a vehicle (for example, a car, an aircraft, etc.), may be a movable object that moves without a crew (for example, an unmanned aerial vehicle, a self-driving vehicle, etc.), or may be a robot (with or without an operator). It should be noted that at least one of the base station and the mobile station also includes an apparatus that need not move during communication. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor, etc.

In addition, the base station in this description can be interpreted as a user terminal. For example, each aspect/embodiment of the present invention can be applied to a structure in which communication between a base station and a user terminal is replaced by communication between a plurality of user terminals (which may be referred to, for example, as D2D: device-with-device, V2X (Vehicle- to-Everything; connection of the car with "everything"), etc.). In this case, the user terminals 20 may have the functions of the above-mentioned base stations 10. Words such as "uplink" and "downlink" can be interpreted as words corresponding to communication between terminals (eg, "lateral"). For example, uplink, downlink, etc. can be interpreted as a lateral channel.

By analogy, the user terminal in this description can be interpreted as a base station. In this case, the base station 10 may have the functions of the user terminal 20 mentioned above.

In this description, operations performed by the base station may be performed by upper nodes in some cases. Obviously, in a network containing one or a plurality of network nodes having base stations, various operations carried out for communication with terminals can be performed by base stations, one or more network nodes (for example, it is possible to use mobility management nodes (MME, from Eng. Mobility Management Entity), serving gateways (S-GW, from Eng. Serving-Gateways), etc., without limitation to these examples), other than base stations, or combinations thereof.

Aspects/embodiments illustrated in this description may be used alone or in combination, which can be switched depending on the mode of implementation. The order of processes, sequences, flowcharts, etc. used to describe the aspects/embodiments disclosed in this specification may be changed, provided there are no conflicts. For example, although the various methods illustrated herein have various components of the steps given in exemplary orders, the specific orders presented here are in no way limiting.

Aspects/embodiments disclosed herein can be applied to the LTE scheme, LTE-Advanced (LTE-A) scheme, LTE-B (LTE-Beyond) scheme, SUPER 3G scheme, IMT-Advanced scheme, mobile communication system 4 5th generation (4G), 5th generation (5G) mobile communication systems, future radio access system (FRA), "New-Radio Access Technology (RAT)" systems, NR ("New Radio") technologies, NX technologies (" New Radio Access”), FX technologies (next generation radio access systems), global system for mobile communications (GSM, from the English Global System for Mobile communications) (registered trademark), CDMA2000, broadband network for ultra mobile communications (UMB, from the English. Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark) ), systems that use other suitable radio communication professionals, and the next generation systems that are expanding on top of those systems. Multiple systems can be combined (eg, a combination of LTE or LTE-A and 5G, etc.) and applied.

The expression "based on" (or "on the basis of"), used in this description, does not mean "based only on" (or "on the basis of only"), unless otherwise indicated. In other words, the expression "based on" (or "based on") means both "based only on" and "based on at least" ("based on only" and "based on at least").

Reference to the elements for which the present invention uses terms such as "first", "second", etc., in General, does not limit the number or order of these elements. These designations are used here for convenience only, as a way to distinguish between two or more elements. Thus, referring to the first and second elements does not mean that only two elements can be used, or that the first element must precede the second element in some way.

The term "decision (determination)" used in the present description may include a variety of actions. For example, "deciding (defining)" can be interpreted as meaning "deciding (determining)" about evaluating, calculating, calculating, processing, obtaining, examining, searching, browsing, and querying (for example, searching in a table, database, or other data structures), detection, etc.

In addition, "decision-making (determining)" can be interpreted as meaning "decision-making (determining)" about receiving (for example, receiving information), transmitting (for example, transmitting information), input, output, accessing (for example, obtaining access to data in memory), etc.

In addition, as used herein, the expression "decision (determination)" can be interpreted as meaning "decision making (determination)" about resolution, selection, selection, establishment, comparison, etc. In other words, "decision-making (determination)" can be interpreted as meaning "decision-making (determination)" in relation to a transaction.

Moreover, "making a decision (determining)" can be interpreted as meaning "assumption", "expectation", "consideration", etc.

"Maximum transmit power" according to the present invention may refer to a maximum transmit power value, may refer to a nominal maximum transmit power (nominal maximum transmit power of a UE), or may refer to a design maximum transmit power (design maximum transmit power of a UE).

The words "connected" and "connected" or variations of these words used in this description may refer to all direct or indirect connections or connections between two or more elements, and may include one or more intermediate elements between two elements, "connected" or "linked" to each other. A relationship or connection between elements can be physical, logical, or a combination of both. For example, "connection" can be interpreted as "access".

It should be understood that in this description, in the case of connecting two elements, these two elements are "connected" or "connected" to each other using one or more electrical cables, wires and printed electrical connections, and in some non-limiting and non-limiting examples, with using electromagnetic energy having wavelengths in the radio frequency bands, microwave bands, (both visible and invisible) optical regions, etc.

In this description, the phrase that "A and B are different" may mean that "A and B are different from each other." It should be noted that this phrase may mean that "A and B are each different from C". Concepts such as "separate", "connected", etc., can be interpreted by analogy with the word "different".

If words such as "includes", "including" and variations of these words are used in the present description, then these words should be understood as comprehensive, by analogy with the word "comprising". In addition, the word "or" used in the present description is not an exclusive "or".

For example, in the present description, if in the text, when translated into English, articles are added to words, for example, "a", "an" and "the", then the present description may cover cases where the noun following these articles is in plural.

Although the present invention has been described in detail above, it will be apparent to a person skilled in the art that the present invention is not limited to the embodiments disclosed herein. The present invention may be implemented with various corrections and various modifications without departing from the spirit and protection scope of the present invention as defined by the appended claims. Accordingly, the foregoing description is for the purpose of illustrating examples only and should not be construed as limiting the present invention in any way.

Claims (25)

1. Terminal containing: a receiving section configured to receive configuration information of the search space set; and a control section configured to control monitoring, in said set of search spaces, of at least one of a first downlink control information (DCI) format used for uplink common channel scheduling and a second downlink control information (DCI) format used for downlink scheduling. common channel, based on the search space set ID and the search space set type, wherein the first downlink control information (DCI) format is different from the downlink control information (DCI) formats 0_0 and 0_1, and the second downlink control information (DCI) format is different from the downlink control information (DCI) formats 1_0 and 1_1, and the control section is configured to determine that the monitoring priority is assigned in ascending order of the search space set identifier. 2. The terminal of claim 1, wherein the control section is configured to determine that for a type of search space set, the monitoring priority in the common search space set (CSS) is higher than in the UE specific search space set (USS). 3. The terminal of claim 1, wherein the control section is configured to control monitoring of the third DCI format for upstream preemption notification in the search space set, and wherein the configuration information indicates the number of downlink control channel (PDCCH) candidates for each layer aggregation used to monitor the third DCI format. 4. A radio communication method for a terminal, including: receiving configuration information of the set of search spaces; and controlling monitoring, in a specified set of search spaces, of at least one of a first Downlink Control Information (DCI) format used for scheduling an uplink common channel and a second Downlink Control Information (DCI) format used for scheduling a downlink common channel, based on an identifier search space set and search space set type, wherein the first downlink control information (DCI) format is different from the downlink control information (DCI) formats 0_0 and 0_1, and the second downlink control information (DCI) format is different from the downlink control information (DCI) formats 1_0 and 1_1, and during said control, it is determined that the monitoring priority is assigned in ascending order of the search space set identifier. 5. Base station, containing: a transmitting section configured to transmit configuration information of a set of search spaces; and a control section configured to be controlled to monitor, in said set of search spaces, at least one of a first downlink control information (DCI) format used for uplink common channel scheduling and a second downlink control information (DCI) format used for scheduling downlink common channel, based on the search space set identifier and the search space set type, in the terminal, wherein the first downlink control information (DCI) format is different from the downlink control information (DCI) formats 0_0 and 0_1, and the second downlink control information (DCI) format is different from the downlink control information (DCI) formats 1_0 and 1_1, and the control section is configured to determine that the monitoring priority is assigned in ascending order of the search space set identifier. 6. A radio communication system comprising a terminal and a base station, in which: terminal contains: a receiving section configured to receive configuration information of the search space set; and a control section configured to control monitoring, in said set of search spaces, of at least one of a first downlink control information (DCI) format used for uplink common channel scheduling and a second downlink control information (DCI) format used for downlink scheduling. a common channel based on a search space set ID and a search space set type, the control section being configured to determine that a monitoring priority is assigned in ascending order of the search space set ID; a base station contains: a transmitting section configured to transmit said configuration information; and a control section configured to be controlled to monitor, in said search space set, at least one of a first downstream control information (DCI) format and a second downstream control information (DCI) format based on the search space set identifier and the search space set type, in the terminal wherein the first downlink control information (DCI) format is different from the downlink control information (DCI) formats 0_0 and 0_1, and the second downlink control information (DCI) format is different from the downlink control information (DCI) formats 1_0 and 1_1.

Images