Terminal and communication method

Abstract

This terminal comprises: a reception unit that receives information indicating a first search space associated with first downlink control information and information indicating a first control resource set, and monitors a physical downlink control channel candidate on the basis of the information indicating the first search space and the information indicating the first control resource set; and a control unit that detects the first downlink control information on the basis of the physical downlink control channel candidate, and determines whether second downlink control information is present on the basis of the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set. When the second downlink control information is present, the control unit controls reception of the second downlink control information on the basis of the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set.

Description

Terminal and Communication Method

[0001] The present disclosure relates to a terminal and a communication method.

[0002] In 3GPP (registered trademark), the 5th generation mobile communication system (also referred to as 5G, New Radio (NR) or Next Generation (NG)) has been standardized, and further standardization of next-generation mobile communication systems called Beyond 5G, 5G Evolution or 6G is also in progress.

[0003] In NR (New Radio), a base station or a network can use one piece of DCI (Downlink Control Information) to perform scheduling of a plurality of PxSCHs (Physical Downlink / Uplink Shared Channels) from one CC (Component Carrier), or scheduling of a plurality of PxSCHs from a plurality of CCs by means of CA (Carrier Aggregation). Similarly, the base station or the network can also perform scheduling of a plurality of fragmented frequency bands for user equipment (UE) by means of one piece of DCI.

[0004] 3GPP TS 38.331 V18.4.0 (2024-12)3GPP TS 38.213 V18.5.0 (2024-12)3GPP TS 38.300 V18.2.0 (2024-06)3GPP TS 38.211 V18.3.0 (2024-06)

[0005] As mentioned above, when a base station or network schedules multiple fragmented frequency bands using a single DCI, the scheduling DCI can have a large payload size because it transmits specific individual instructions for multiple PxSCHs / CCs / frequency bands. When the payload size of a single DCI is large, scheduling can become difficult when the base station or network determines its position within the Control Resource Set (CORESET). Therefore, when a base station or network schedules multiple PxSCHs / CCs / frequency bands using a single DCI, if the DCI payload size exceeds a certain size, using a two-stage DCI method may be considered as one option.

[0006] However, sufficient concrete consideration has not been given to how to distinguish and set the two-stage DCI, and further consideration is needed.

[0007] One aspect of this disclosure relates to a search space corresponding to a DCI, a control resource set corresponding to said DCI, or a terminal that determines the presence or absence of a second DCI in a two-stage DCI based on said DCI.

[0008] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives information indicating a first search space and information indicating a first control resource set associated with first downlink control information, and monitors physical downlink control channel candidates based on the information indicating the first search space and the information indicating the first control resource set; and a control unit that detects the first downlink control information based on the physical downlink control channel candidates and determines whether or not second downlink control information exists based on the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set, wherein if the second downlink control information exists, the control unit controls the reception of the second downlink control information based on the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set.

[0009] This is a schematic diagram of the overall configuration of a wireless communication system. This is a diagram showing the frequency range used in the wireless communication system. This is a diagram showing an example of the configuration of wireless frames, subframes, slots, and symbols used in the wireless communication system. This is a diagram showing multi-carrier scheduling. This is a diagram showing cross-carrier scheduling. This is a diagram showing scheduling and reference cells in DCI format 1_3. This is a diagram showing multi-PDSCH scheduling. This is a diagram showing examples of BWP, CORESET, search space (SS), search space set, and PDCCH candidates. This is a diagram showing each information element of PDCCH, search space, and control resource set (CORESET) set by RRC. This is a diagram showing an example of the association between SearchSpace and ControlResourceSet in option 1-1-1. This is a diagram showing an example of the association between SearchSpace and ControlResourceSet in option 1-1-2. This is a diagram showing an example of the association between SearchSpace and ControlResourceSet in option 1-1-3. This is a diagram showing an example of the association between SearchSpace and ControlResourceSet in option 1-1-4. This is a diagram showing an example of the association between SearchSpace and ControlResourceSet in option 1-2-1. This is a diagram showing an example of the association between SearchSpace and ControlResourceSet in option 1-2-2. This figure shows an example of information for the second DCI indicated by the first DCI in Option 2-1-1. This figure shows an example of information for the second DCI indicated by a predefined rule in Option 2-1-2. This is a block diagram showing an example of a base station configuration. This is a block diagram showing an example of a terminal configuration. This figure shows an example of the hardware configuration of a base station and a terminal. This figure shows an example of a vehicle configuration.

[0010] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0011] (Embodiment) <Configuration of Wireless Communication System> The wireless communication system 10 shown in Figure 1 is a wireless communication system that conforms to a method called 5G. On the other hand, the wireless communication system 10 may also be a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G.

[0012] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates a more directional beam by controlling the radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CC:); and dual connectivity (DC), which enables simultaneous communication with two base stations. In this specification, "and / or" may be simply written as " / ".

[0013] As shown in Figure 1, the wireless communication system 10 includes a base station 100 (hereinafter also referred to as gNodeB (gNB) 100) that constitutes the Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as user equipment (UE) 200) that communicates wirelessly with the gNB 100. The NG-RAN 20 is connected to a core network (CN) which is not shown. The CN is composed of multiple network functions (NFs). Examples of NFs include the Access and Mobility Management Function (AMF) and the Network Data Analytics Function (NWDAF). The AMF performs, for example, the registration of the UE 200. The NWDAF performs, for example, the optimization of the CN. Note that the specific configuration of the wireless communication system 10, such as the number of gNB 100s and UE 200s, is not limited to the example shown in Figure 1. Also, the NG-RAN 20 and CN may simply be referred to as the "network".

[0014] gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration, having a Distributed Unit (DU) with the function of connecting to UE200 and a Central Unit (CU) with the function of connecting to the network. In this case, gNB100 may be interpreted as DU, as CU, or as DU and CU. When gNB100 is interpreted as DU, it may be called gNB-DU. When gNB100 is interpreted as CU, it may be called gNB-CU. When gNB100 is interpreted as DU and CU, the DU portion may be called gNB-DU and the CU portion may be called gNB-CU.

[0015] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FRs). That is, as shown in Figure 2, it may support the following FRs: • FR1: 410 MHz to 7.125 GHz • FR2-1: 24.25 GHz to 52.6 GHz • FR2-2: Over 52.6 GHz to 71 GHz

[0016] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used. In FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

[0017] Note that SCS may also be interpreted as numerology. Numerology is defined in §5.1 of Non-Patent Document 3, etc., and corresponds to a single subcarrier interval in the frequency domain.

[0018] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

[0019] Figure 3 shows an example of the configuration of wireless frames (system frames), subframes, and slots used in the wireless communication system 10. As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

[0020] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it could be 28 or 56 symbols, etc.). In addition, the number of slots per subframe may differ depending on the SCS.

[0021] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0022] The wireless communication system 10 may support coverage enhancement (CE) to broaden the coverage of the cell (or physical channel) formed by the gNB100. Coverage enhancement may provide mechanisms to increase the success rate of reception of various physical channels, such as repetition (repeated transmission) of PRACH (physical random access channel).

[0023] For example, the UE200 receives information related to random access procedures from the gNB100 as a downlink signal (DL: Downlink) (e.g., SIB1 (System Information Block Type 1)).

[0024] Furthermore, for example, UE200 transmits PRACH to gNB100 using a RACH occasion, or RACH (transmit) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble as a UL signal. For example, UE200 replicates PRACH to gNB100 as a UL signal.

[0025] The UL signal may include, for example, UL data signals and control information. For example, the UL signal may include information about the processing capabilities of the UE200 (e.g., UE capability). The UL signal may also include reference signals.

[0026] The channels used to transmit UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, the UE200 transmits control information using PUCCH and transmits UL data signals using PUSCH. Note that PUSCH is an example of an uplink shared channel, and PUCCH is an example of an uplink control channel. Shared channels may also be called data channels.

[0027] The reference signals included in the UL signal may include, for example, at least one of the following: DMRS (Demodulation Reference Signal), PTRS (Phase Tracking Reference Signal), CSI-RS (Channel State Information - Reference Signal), SRS (Sounding Reference Signal), and PRS (Positioning Reference Signal) for positional information. For example, reference signals such as DMRS and PTRS are used to demodulate the UL data signal and are transmitted using PUSCH.

[0028] Meanwhile, the gNB100, in response to the operation of the UE200, sends information related to the RACH (Random Access Channel) procedure to the UE200 as a DL signal (e.g., SIB1).

[0029] For example, gNB100 receives PRACH from UE200 as a UL signal. For example, gNB100 receives PRACH from UE200 as a repetition signal.

[0030] The channels used to transmit DL signals include, for example, a data channel and a control channel. For example, the data channel may include a Physical Downlink Shared Channel (PDSCH), and the control channel may include a Physical Downlink Control Channel (PDCCH). For example, gNB100 transmits control information to UE200 using the PDCCH and transmits DL data signals using the PDSCH. Note that PDSCH is an example of a Downlink Shared Channel, and PDCCH is an example of a Downlink Control Channel. Note that PDCCH may be interpreted as Downlink Control Information (DCI), control information, etc., transmitted in the PDCCH.

[0031] The reference signals included in the DL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, RS, and PRS for location information. For example, reference signals such as DMRS and PTRS are used to demodulate the DL data signal and are transmitted using PDSCH.

[0032] <Multi-carrier extension> Rel-18 introduced support for multi-cell PxSCH (PDSCH / PUSCH) scheduling using a single DCI. Hereafter, multi-cell PDSCH / PUSCH scheduling will be referred to as multi-carrier scheduling.

[0033] <Multi-carrier scheduling> Figure 4 is a diagram illustrating multi-carrier scheduling. Figure 5 is a diagram illustrating cross-carrier scheduling. CC#1 to CC#3 shown in Figures 4 and 5 represent CCs (Component Carriers). CCs may also be called carriers or cells. As shown in Figure 4, in multi-carrier scheduling, one DCI in one CC#1 schedules PDSCH / PUSCH in multiple CC#1 to CC#3.

[0034] As shown in Figure 5, in cross-carrier scheduling, multiple DCIs in one CC#1 schedule PDSCH / PUSCH in multiple CC#1 to CC#3.

[0035] Multi-carrier scheduling can be understood as a single DCI scheduling PDSCH / PUSCH across multiple CCs. Because a single DCI schedules PDSCH / PUSCH across multiple CCs in multi-carrier scheduling, the load on DCI monitoring (PDCCH monitoring) at the terminal can be reduced compared to self-carrier scheduling and cross-carrier scheduling. For example, multi-carrier scheduling can reduce the number of PDCCH Blind Detections (BDs) at the terminal.

[0036] Furthermore, multi-carrier scheduling can reduce the total overhead in DCI compared to self-carrier scheduling and cross-carrier scheduling. For example, in scenarios where it is not necessary to notify each of CC#1 to CC#3 with different information, common information can be notified in a single DCI (DCI field), which can reduce the total overhead in DCI.

[0037] <DCI Format 0_3 / 1_3> The DCI format used in PUSCH's multi-carrier scheduling is called DCI Format 0_3. The DCI format used in PDSCH's multi-carrier scheduling is called DCI Format 1_3. DCI Format 0_3 / 1_3 can be used to schedule combinations of cells included in a Set of Cells simultaneously. In the following, a Set of Cells may be referred to as SoCs.

[0038] Figure 6 illustrates scheduling in DCI format 1_3. A single SoC consists of a maximum of four cells (CCs). Each cell is contained within only one SoC. In the example in Figure 6, Set of cells 1 contains CC#1 / 2 / 3 / 4, and Set of cells 2 contains CC#5 / 6 / 7. Information regarding the configuration of SoCs is communicated through higher-layer signaling, such as RRC (Radio Resource Control) signaling.

[0039] DCI format 0_3 / 1_3 can be scheduled simultaneously for combinations of cells included in SoCs.

[0040] For example, the PDCCH (DCI format 1_3) indicated by arrow A7a in FIG. 6 can simultaneously schedule PDSCH in the four CCs #1 / 2 / 3 / 4 of Set of cells 1. For example, the PDCCH (DCI format 1_3) indicated by arrow A7b in FIG. 6 can simultaneously schedule PDSCH in the three CCs #5 / 6 / 7 of Set of cells 2.

[0041] Similarly, PUSCH can also be scheduled simultaneously on PUCCH (DCI format 0_3).

[0042] It should be noted that in FIG. 6, the PDCCH is transmitted in a cell (#0) different from the cells (CC#1 to CC#7) of Set of cells 1 and Set of cells 2, but the present invention is not limited thereto. The PDCCH may be transmitted in a cell of SoCs. For example, in FIG. 6, the PDCCH may be transmitted in the cell of CC#1. The same applies to PUCCH.

[0043] <Reference Cell> A cell that counts DCI size / number of PDCCH candidates (BD) / number of CCEs (Control Channel Elements) is called a reference cell. In multi-carrier scheduling, one reference cell is configured for each SoCs. The reference cell is notified by higher layer signaling such as RRC signaling, for example.

[0044] FIG. 6 is a diagram explaining a reference cell. For example, in FIG. 6, the reference cell of Set of cells 1 is configured as CC#1. In this case, the DCI size / number of PDCCH candidates (BD) / number of CCEs of the PDCCH (DCI for Set of cells 1) indicated by arrow A7a are counted in CC#1.

[0045] For example, in FIG. 6, the reference cell of Set of cells 2 is configured as CC#5. In this case, the DCI size / number of PDCCH candidates (BD) / number of CCEs of the PDCCH (DCI for Set of cells 2) indicated by arrow A7b are counted in CC#5.

[0046] <Multi-PUSCH Scheduling> When scheduling multiple PUSCHs, DCI 0_1 is used as the DCI format. For example, as shown in Figure 7, PUSCH #1 to #4 can be scheduled by a single DCI. Here, 120, 480, and 960 kHz SCS are supported, and the maximum number of PUSCHs that can be scheduled by a single DCI is specified to be 8. In addition, for TDRA (Time Domain Resource Allocation), a separate {SLIV (Start and Length Indicator Value), mapping type, scheduling offset K0} may be applied to each PUSCH in the TDRA table row. If a PUSCH conflicts with a semi-static UL symbol, that PUSCH will be canceled, but it is not expected that all PUSCHs will be canceled.

[0047] Furthermore, the MCS (Modulation and Coding Scheme), NDI (New Data Indicator), and RV (Redundancy Version) fields in the 1st TB (Transport Block) field appear only once and are applied to the first TB of each PUSCH. Additionally, the HPN (HARQ Process Number) field is applied to the first valid PUSCH and incremented by 1 for subsequent PUSCHs, but not for invalid PUSCHs (i.e., PUSCHs that conflict with semi-static DL symbols or SSB symbols).

[0048] <Search Space> A search space (PDCCH search space) refers to a region in a downlink resource grid where a PDCCH may be transmitted, and defines where and how a UE searches for PDCCH candidates. Each search space is associated with one CORESET. Additionally, a UE has a plurality of search spaces corresponding to a plurality of aggregation levels. A PDCCH search space set is a set of search spaces, and indicates a set of PDCCH candidates monitored by the UE. Search space sets include a common search space set (CSS), which is a region shared by multiple UEs, and a UE-specific search space set (USS), which is a region dedicated to each UE. The UE monitors PDCCH candidates in one or more of the CSS set and the USS set. For details of the procedure for monitoring search spaces in a UE, refer to §10.1 of Non-Patent Document 2.

[0049] <Blind Decoding> A UE performs blind decoding (blind detection) over these entire search spaces. For a UE to detect DCI, it is necessary to know accurate values such as CCE index, aggregation level, interleaving, and scrambling code (RNTI: Radio Network Temporary Identifier), but these values are not notified to the UE in advance, so the UE recognizes information on this specific range by using predefined rules or signaling messages. Within this range, the UE attempts blind decoding of DCI using many different types of parameters based on a trial-and-error method.

[0050] <CORESET> In NR, PDCCHs are transmitted within the CORESET. The NR CORESET can be located at any position within the slot and at any position within the carrier frequency range. The controlResourceSetId associates a search space set with the CORESET, and the UE monitors a set of PDCCH candidates defined in units of the search space set.

[0051] The initial CORESET is provided by the Master Information Block (MIB) as part of the initial bandwidth portion (BWP) configuration, enabling the network to receive the remaining system information and additional configuration information. After the connection is set up, the network can configure multiple CORESETs in the UE using RRC signaling.

[0052] Figure 8 shows examples of BWPs, CORESETs, search spaces, sets of search spaces, and PDCCH candidates that can be monitored by the UE. In Figure 8, one CORESET is shown for each BWP, but there may be two or more. Each CORESET has one or more search spaces corresponding to a specific aggregation level (e.g., AL2, 4, or 8). The search space sets may be grouped, for example, as a common search space set (CSS) and a UE-specific search space set (USS). For details on CORESETs, see §7.3.2.2 of Non-Patent Document 4.

[0053] NW / gNB can semi-statically configure the UE's search space and coreset settings via RRC signaling, with the corresponding RRC information elements being SearchSpace and ControlResourceSet.

[0054] <BWP and Carrier Aggregation> In Figure 8, the BWP is a subset of the total cell bandwidth of a cell, and is defined separately for uplinks and downlinks, for example, by the location and number of consecutive physical resource blocks (PRBs). Furthermore, each bandwidth portion can be associated with a specific OFDM neurology, such as subcarrier spacing and cyclic prefixes.

[0055] NR systems support a maximum channel bandwidth wider than that of LTE. Therefore, by defining a wide channel bandwidth, NR systems can dynamically allocate frequency resources through scheduling. Having a single broadband carrier has the advantage of low control overhead, as it requires only one control signaling event. However, carrier aggregation requires separate control signaling for each aggregated carrier. NR can also support the aggregation of multiple carriers via carrier aggregation or dual connectivity.

[0056] <RRC Information Elements> Figure 9 shows the information elements of the PDCCH, search space, and control resource set (CORESET) set by RRC, and their interrelationships. These information elements are described in §6.3.2 “Radio resource control information elements” of Non-Patent Literature 1.

[0057] (PDCCH-Config) The PDCCH-Config information element is used to configure UE-specific PDCCH parameters and MBS (Multicast Broadcast Services) multicast PDCCH parameters (e.g., Search Space, Control Resource Sets (CORESET), and additional parameters related to PDCCH acquisition). When this IE is used for a SCell to be scheduled in cross-carrier scheduling, all fields except searchSpacesToAddModList and searchSpacesToReleaseList are absent. When this IE is used for a dormant BWP, all fields except controlResourceSetToAddModList and controlResourceSetToReleaseList are absent. When this IE is used for an MBS CFR (Common Frequency Resource), the fields downlinkPreemption, tpc-PUSCH, tpc-SRS, uplinkCancellation, monitoringCapabilityConfig, and searchSpaceSwitchConfig are absent.

[0058] (SearchSpace) The SearchSpace information element defines how and where PDCCH candidates are searched. Each search space is associated with one ControlResourceSet. In cross-carrier scheduling, for scheduled SCells, all option fields except nrofCandidates do not exist (regardless of the conditions under which those fields exist). Also, in cross-carrier scheduling, if the search space of a scheduled SpCell (Special Cell) is linked to another search space within the SCell (Secondary Cell) that is scheduling, all option fields for this search space of the scheduled SpCell do not exist (regardless of the conditions under which they exist), except for nrofCandidates.

[0059] (ControlResourceSet) The information element ControlResourceSet configures a time / frequency control resource set (CORESET:ControlResourceSet) for retrieving downlink control information, which the UE uses to retrieve downlink control information (DCI) (see §10.1 of Non-Patent Literature 2). For a UE that does not support multiple CORESETs in FR1 to receive MBS multicast in the CFR within the UE's active BWP, if no CORESET is configured in PDCCH-ConfigMulticast, a CORESET other than CORESET#0 configured in the UE's active BWP for unicast scheduling can be used for MBS multicast scheduling. This CORESET is expected to be fully contained within the CFR, and furthermore, the parameters configured in this CORESET are expected to be supported by the UE for MBS multicast.

[0060] (controlResourceSetId) The information element controlResourceSetId indicates the CORESET applied to this search space. A value of 0 identifies the common CORESET#0 set by the MIB and ServingCellConfigCommon. Values ​​from 1 to maxNrofControlResourceSets - 1 identify the CORESET set by system information or dedicated signaling. CORESETs with a controlResourceSetId other than 0 are set within the same BWP as this search space, with the exception of commonControlResourceSetExt, which is set by SIB20. If the field controlResourceSetId-r16 exists, the UE ignores the controlResourceSetId field without a suffix.

[0061] The details related to each item are described in the respective sections of "PDCCH-Config," "SearchSpace," and "ControlResourceSet" in §6.3.2 of Non-Patent Document 1.

[0062] <Analysis> In NR (New Radio), a single DCI (Downlink Control Information) can be used to schedule multiple PxSCHs (Physical Downlink / Uplink Shared Channels) from a single CC (Component Carrier), or to schedule multiple PxSCHs from multiple CCs in a CA (Carrier Aggregation) scenario. For multiple fragmented frequency bands, a scheduling method using a single DCI may also be considered.

[0063] In the above scenario, a single DCI for scheduling may require a large payload size because it transmits specific, individual instructions for multiple PxSCHs / CCs / frequency bandwidths. A large payload size for a single DCI makes scheduling difficult when the Network determines its location in the Control Resource Set (CORESET). For example, a small number of PDCCH (Physical Downlink Control Channel) candidates may occupy a large aggregation level. DCI performance also degrades when using the same modulation scheme. If the DCI payload size exceeds a certain size, a two-stage DCI approach may be considered.

[0064] In this embodiment, the details of the two-stage DCI design will be described.

[0065] For the sake of explanation in this embodiment, the following expressions will be used: • 1-stage DCI: Same as conventional DCI • 2-stage DCI: When using two stages of DCI as follows: 1st DCI + 2nd DCI

[0066] <Consideration> When using a two-stage DCI, it is preferable for the first DCI to be small in size, allowing the second DCI to carry more information bits. There are generally two approaches to the UE's decoding operation for the first and second DCIs, as shown below.

[0067] (1) The first DCI is blind-decoded by the UE, just like a conventional DCI. The position of the second DCI is determined by the first DCI. Therefore, the second DCI does not need to be blind-decoded. This method is simpler and more efficient. (2) If both the first and second DCIs need to be blind-decoded by the UE, the advantages over a large single-stage DCI are reduced. In this approach, the number of blind-decoded attempts for the second DCI must be minimized to gain any advantages.

[0068] Regardless of which of the above approaches is adopted, the following points must be considered: • Search Space (SS) and Coreset configuration for two-stage DCI (for the first and second DCIs) • The relationship between SS and Coreset configuration for one-stage and two-stage DCI • Differences in DCI field display between one-stage and two-stage DCI, and how they differ from one-stage DCI • How to identify whether a DCI is a one-stage DCI, a one-stage DCI within a two-stage DCI, or a two-stage DCI within a two-stage DCI.

[0069] Therefore, in this embodiment, we will examine the following aspects 1 and 2 based on the approach described in (1) above. Perspective 1: SS / CORESET configuration. Perspective 2: DCI indication.

[0070] First, based on the above-mentioned perspective 1, we will explain proposals 1-1 to 1-3 regarding the configuration of SS / CORESET. It should be noted that all settings in proposals 1-1 to 1-3 are assumed to be pre-configured by RRC. Next, based on perspective 2, we will explain proposals 2-1 to 2-2 regarding DCI indication.

[0071] <Assumptions for Proposal 1-1> In the case of approach (1) described above, in a two-stage DCI, it is important that the UE decodes the first DCI first. This means that the PDCCH candidates for the first DCI are not used for the transmission of the second DCI. Also, the second DCI must be transmitted after the first DCI in the time domain. For example, if the second DCI is located in one of the PDCCH candidates for the first DCI, the UE may decode the second DCI first if it performs blind decoding. In such a case, the above design becomes meaningless. Therefore, in the SS and CORESET configurations, it is necessary to consider providing separate PDCCH resources for the first and second DCIs.

[0072] <Proposal 1-1> As shown in the following [Options 1-1-1] to [Options 1-1-4], separate configurations (SearchSpace / ControlResourceSet / some parameters) are set for the first and second DCIs of the two-stage DCI.

[0073] Information elements such as SearchSpace and ControlResourceSet are transmitted from the NW / gNB to the UE via RRC messages. The UE identifies the CORESET associated with the SearchSpace based on the SearchSpace received via the RRC message and monitors for PDCCH candidates. The UE performs blind decoding on the PDCCH candidates to detect valid DCIs. (The UE's operation remains the same in subsequent proposals.)

[0074] For example, the UE detects the first DCI of a two-stage DCI based on the SearchSpace and ControlResourceSet associated with the first DCI of the two-stage DCI. The UE may then estimate the location of the second DCI based on the information of the detected first DCI and detect the second DCI.

[0075] [Option 1-1-1] Separate ControlResourceSet configurations may be set for the first DCI and the second DCI, and one SearchSpace configuration may be associated with the two ControlResourceSet configurations of the first and second DCIs (see Figure 10).

[0076] For example, the ControlResourceSet configuration provides a new parameter called 'stage-type indication' to distinguish between "the first DCI of a two-stage DCI" and "the second DCI of a two-stage DCI."

[0077] For example, of the two ControlResourceSetIds set in the SearchSpace configuration, the first ControlResourceSetId is set for the first DCI, and the second ControlResourceSetId is set for the second DCI.

[0078] [Option 1-1-2] The first DCI and the second DCI may each have separate SearchSpace configurations, and these may be associated with the same ControlResourceSet (see Figure 11).

[0079] For example, the SearchSpace configuration will provide a new parameter called 'stage-type indication' to distinguish between "the first DCI of a two-stage DCI" and "the second DCI of a two-stage DCI."

[0080] [Option 1-1-3] The first and second DCIs may have separate SearchSpace configurations, and the first and second DCIs may have separate ControlResourceSet configurations. In addition to the association between the SearchSpace configuration and the ControlResourceSet configuration of the first DCI (and the second DCI), in the case of a two-stage DCI, an association between the two SearchSpace configurations or the two ControlResourceSet configurations of the first and second DCIs is also required (see Figure 12).

[0081] For example, the SearchSpace and / or ControlResourceSet configurations are provided with a new parameter called 'stage-type indication' to distinguish between "the first DCI of a two-stage DCI" and "the second DCI of a two-stage DCI."

[0082] [Option 1-1-4] For a two-stage DCI, one SearchSpace configuration and one ControlResourceSet configuration may be set. However, some parameters of each configuration may be in multiple sets, and different values ​​may be provided for the first DCI and the second DCI (see Figure 13).

[0083] For example, the first DCI and the second DCI may each have two sets of monitoringSymbolsWithinSlot.

[0084] For example, the first DCI and the second DCI can each have two sets of searchSpaceType.

[0085] For example, the first DCI and the second DCI may each have two sets of frequencyDomainResources.

[0086] (Variation of Proposal 1-1) The instructions for some parameters may be further divided to indicate whether they are for the first DCI or the second DCI. For example, in the case of a specified "period," it may be further indicated that a portion of the period is for either the first DCI or the second DCI.

[0087] The following points should be noted regarding each of the options mentioned above: • A single SearchSpace / ControlResourceSet configuration in the second DCI may be associated with multiple configurations in a different first DCI. • Since the second DCI does not require blind decoding, it is not necessary to use specific parameters in its configuration. • The values ​​supported by specific parameters in the SearchSpace / ControlResourceSet configurations of the first and second DCIs may differ. For example, certain DCI formats with small payload sizes (e.g., DCI format 1_0 / 0_0) may be supported in the first DCI, but only UE-specific SS may be supported in the second DCI.

[0088] (Effect) As explained above, according to Proposal 1-1, NW / gNB sets separate configurations (SearchSpace / ControlResourceSet / some parameters) for the first and second DCI of the two-stage DCI, so the UE does not risk blind-decoding the second DCI first, and the UE can properly distinguish between the "first DCI of the two-stage DCI" and the "second DCI of the two-stage DCI".

[0089] <Assumptions for Proposal 1-2> The first-stage DCI also needs to be set in the UE. Therefore, we will consider the relationship between the SS / CORESET settings of the first-stage DCI and the second-stage DCI. Blind decoding is also required for the first-stage DCI, so it is the same as the first DCI of the second-stage DCI. Therefore, it is beneficial that the configuration of the first-stage DCI and the first DCI of the second-stage DCI are the same.

[0090] <Proposal 1-2> The configuration of the first DCI in both the 1-stage DCI and the 2-stage DCI is the same, and the configuration (SearchSpace / ControlResourceSet / new parameters) is set as shown in the following [Option 1-2-0] to [Option 1-2-2-B].

[0091] For example, the UE detects the first DCI of a single-stage DCI or a two-stage DCI based on the SearchSpace and ControlResourceSet associated with the first DCI of a single-stage DCI or a two-stage DCI. The UE may then estimate the location of the second DCI of a two-stage DCI based on the information of the detected first DCI of a two-stage DCI and detect the second DCI of a two-stage DCI.

[0092] [Option 1-2-0] Single-stage DCI and double-stage DCI (or the first DCI of a double-stage DCI) cannot be set on the same CC / BWP (Bandwidth Part) (simultaneous support is not provided).

[0093] [Option 1-2-1] SearchSpace and / or ControlResourceSet configurations for a single-stage DCI are supported separately from a two-stage DCI (or the first DCI of a two-stage DCI) (see Figure 14).

[0094] For example, the new parameter 'stage-type indication' may indicate either "1-stage DCI", "the first DCI in a 2-stage DCI", or "the second DCI in a 2-stage DCI".

[0095] [Option 1-2-2] The SearchSpace and / or ControlResourceSet configurations of a single-stage DCI may share the configuration of the first DCI of a two-stage DCI (see Figure 15).

[0096] For example, a new parameter 'stage-type indication SEQUENCE' may be set. This may include "1-stage DCI" and / or "the first DCI of a 2-stage DCI".

[0097] For example, the new parameter 'stage-type indication' may indicate "the first DCI in a single-stage DCI and a two-stage DCI" and "the second DCI in a two-stage DCI".

[0098] For example, the RRC settings may not have a display that distinguishes between "single-stage DCI" and "the first DCI of a two-stage DCI."

[0099] [Option 1-2-2-A] If the first DCI of a single-stage DCI and a second-stage DCI share a common SearchSpace / ControlResourceSet configuration, some parameters may have two sets, one set for the single-stage DCI and the other set for the first DCI of the second-stage DCI.

[0100] [Option 1-2-2-B] In the case of a common SearchSpace / ControlResourceSet configuration for a single-stage DCI, the first DCI of a two-stage DCI, and the second DCI of a two-stage DCI (Option 1-1-4), some parameters may be in three sets, with one set for the single-stage DCI, another for the first DCI of the two-stage DCI, and another for the second DCI of the two-stage DCI. Alternatively, some parameters may be in two sets, with one set for the single-stage DCI and the first DCI of the two-stage DCI, and the other set for the second DCI of the two-stage DCI.

[0101] (Effect) As explained above, according to Proposal 1-2, if the configuration of the first DCI of the 1st stage DCI and the 2nd stage DCI is the same, the configuration (SearchSpace / ControlResourceSet / new parameter) is set separately or distinctly for the first DCI of the 1st stage DCI and the 2nd stage DCI, so that the UE can properly distinguish between the first DCI of the 1st stage DCI and the 2nd stage DCI while making the configuration of the first DCI of the 1st stage DCI and the 2nd stage DCI common.

[0102] <Proposal 1-3> Enabling / disabling two-stage DCI may be explicitly set by RRC using a new parameter (e.g., enableTwoStageDCI in PDCCH-Config), implicitly specified by a specific parameter in the SearchSpace / ControlResourceSet configuration (e.g., stageTypeIndication or a set of specific parameters), or specified by MAC (Medium Access Control) / DCI.

[0103] For example, the UE receives information about enabling / disabling two-stage DCI from the NW / gNB via RRC messages / MAC / DCI. Based on the received information about enabling / disabling two-stage DCI, the UE enables or disables two-stage DCI.

[0104] Two-stage DCI can be enabled or disabled for each BWP / CC, CORESET / SS, CSS (Common Search Space) / SS, DCI format, or other settings (e.g., multi-CC scheduling, multi-PxSCH scheduling, etc.).

[0105] (In the case of a multi-CC scenario) In the case of the multi-CC scheduling described above, a two-stage DCI may be set up by the methods shown in the following [Option 1-3-1] to [Option 1-3-2].

[0106] [Option 1-3-1] The configuration of the second DCI must be associated with the configuration of the first DCI on the same CC (or the same BWP). In other words, if the UE decodes the first DCI on CC#1, the second DCI must also reside on CC#1.

[0107] [Option 1-3-2] The configuration of the second DCI may be associated with the configuration of the first DCI on a different CC (or a different BWP). For example, the SS / CORESET configuration of the first DCI may be on CC#1 and associated with the SS / CORESET configuration of the second DCI on CC#2.

[0108] (Effects) As explained above, according to proposals 1-3, the NW / gNB can enable / disable two-stage DCI by explicitly setting it using new parameters via RRC, implicitly specifying it by specific parameters in the SearchSpace / ControlResourceSet configuration, or by MAC (Medium Access Control) / DCI. This increases the flexibility and freedom of control over two-stage DCI at the terminal, and also improves convenience.

[0109] Next, we will explain proposals 2-1 to 2-2 concerning the above-mentioned perspective 2: DCI indication.

[0110] <Assumptions for Proposal 2-1> Since blind coding is not required for the second DCI in a two-stage DCI, its position and specific parameters are indicated by the first DCI or determined by the position / parameters of the decoded first DCI.

[0111] <Proposal 2-1> The information for the second DCI of the two-stage DCI is shown according to the following [Option 2-1-1] to [Option 2-1-2].

[0112] For example, the UE detects the first DCI of a single-stage DCI or a two-stage DCI. The UE may estimate the position of the second DCI of a two-stage DCI based on the information of the detected first DCI of the two-stage DCI or predefined information, and detect the second DCI of the two-stage DCI.

[0113] [Option 2-1-1] In the first DCI of a two-stage DCI, one or more of the following DCI fields may be supported to indicate the information of the corresponding second DCI (see Figure 16).

[0114] (a) An indication that it is the first or second DCI. For example, if "1 bit" in the DCI field indicates that it is the second DCI of a two-stage DCI, the UE may ignore that DCI. (b) An indication of the time position of the second DCI, for example, a time offset from a reference time position related to the decoded first DCI and / or related to the SS / CORESET configuration of the second DCI. For example, the reference time position may be the first / last symbol of the decoded first DCI, the first symbol in the same slot of the decoded first DCI, the first symbol based on a subsequent SS / CORESET configuration of the decoded first DCI, etc. The UE assumes that the time position of the second DCI is later (or not earlier) than the first DCI. (c) Frequency position of the second DCI, e.g., a frequency offset indication from a reference frequency position related to the decoded first DCI and / or the SS / CORESET configuration of the second DCI - for example, the reference frequency position may be the lowest / highest frequency position of the decoded first DCI, the lowest frequency position of its configured CORESET. (d) Aggregation level indication, e.g., an indication from one or more predefined values ​​such as 1, 2, 4, 8, 16, 32, or an indication from a set of values ​​set from its SS / CORESET configuration. (e) DCI format indication, e.g., an indication from a part of the DCI format defined or set by the SS / CORESET configuration. (f) CC / BWP indication of the second DCI, if the second DCI associated with the first DCI is set to a different CC / BWP. (g) Indication of the presence or absence of a DCI field in the second DCI.

[0115] Furthermore, the candidate values ​​(ranges) for each instruction may be predefined or pre-configured within a limited range. DCI only needs to specify from a limited set of candidate values, reducing the overhead of DCI display. If only one candidate value is defined / configured for a particular instruction, a corresponding DCI field is not required.

[0116] [Option 2-1-2] One or more pieces of information for the second DCI above may be indicated according to the following predefined rules (fixed rules, or association rules related to the location / parameters of the decoded first DCI). In this case, DCI indication is not required (see Figure 17).

[0117] (Examples of fixed rules) - Time position of the second DCI: Predefined to be from the last symbol of the first DCI to the next symbol (e.g., after symbol X, where X is predefined or RRC set), or predefined to be the first symbol after the last symbol of the first DCI, based on the SS / CORESET configuration. - Frequency position of the second DCI: Predefined to be the same as the starting frequency position of the first DCI (e.g., within the ±Y PRB range, where Y is predefined or RRC set). - Aggregated level display: Predefined to be the same as the first DCI. - DCI format display: Predefined to be the same as the first DCI. - CC / BWP display: Same as the first DCI. - Presence or absence of DCI fields in the second DCI: Predefined by RRC / MAC CE (MAC Control Element).

[0118] (Examples of association rules) - Time position of the second DCI: The association between the time position of the second DCI and the time position of the first DCI is predefined / pre-configured (for example, if the first DCI is detected at the first symbol of its CORESET, and the first and second DCIs have separate CORESETs, the corresponding second DCI will be placed at the first symbol of the second DCI's CORESET). - Frequency position of the second DCI: The association between the frequency position of the second DCI and the frequency position of the first DCI is predefined / pre-configured. - DCI format indication: The association rules between the DCI format X of the first DCI and the DCI format Y of the second DCI are predefined (for example, if the first DCI is DCI format 0_0, the second DCI must be DCI format 0_1. Also, if the first DCI is DCI1_0, the second DCI must be DCI format 1_1).

[0119] Note that the second DCI SS / CORESET configuration does not require any specific parameters or candidate values.

[0120] (Effects) As explained above, according to Proposal 2-1, the NW / gNB instructs the UE on the information of the second DCI of the two-stage DCI based on the values ​​of each field of the first DCI of the two-stage DCI, or by predefined rules. This allows the UE to flexibly obtain information control for the second DCI of the two-stage DCI, improving convenience.

[0121] <Assumptions for Proposal 2-2> If there are no separate SS / CORESET configurations for the first DCI of a single-stage DCI and the first DCI of a two-stage DCI, a single common PDCCH candidate may apply to both the first DCI of a single-stage DCI and the first DCI of a two-stage DCI. In such cases, we will explain how to distinguish between the first DCI of a single-stage DCI and the first DCI of a two-stage DCI.

[0122] <Proposal 2-2> When a common SS / CORESET configuration is set for the first DCI of both a 1-stage DCI and a 2-stage DCI, the 1-stage DCI and the first DCI of a 2-stage DCI are distinguished according to the following [Options 2-2-1] to [Options 2-2-2].

[0123] For example, the UE detects either a single-stage DCI or the first DCI in a two-stage DCI. Based on the detected DCI information or certain parameters in the SS / CORESET configuration, the UE identifies whether it is a single-stage DCI or the first DCI in a two-stage DCI.

[0124] [Option 2-2-1] Even with a common SS / CORESET configuration, different settings (e.g., different DCI format, different aggregation level, etc.) are required for some parameters to distinguish between the first-stage DCI and the first DCI in overlapping PDCCH candidates.

[0125] [Option 2-2-2] If the first DCI of a single-stage DCI and a double-stage DCI are of the same DCI format, a field indicating the first DCI of both the single-stage DCI and the double-stage DCI is required. In other words, indicating the first DCI of a double-stage DCI by that field is equivalent to indicating whether a second DCI exists. If the field indicates that a second DCI does not exist, the DCI indicated by that field is a single-stage DCI.

[0126] Depending on this field, the existence / interpretation of other fields may differ. For example, if this field indicates the first DCI of a two-stage DCI, then the field from Proposal 2-1 exists in that DCI field.

[0127] In addition, with option 2-2-2, the same SS / CORESET configuration can be set for both the first DCI of the single-stage DCI and the first DCI of the double-stage DCI, so the PDCCH candidate can be used for both the single-stage DCI and the first DCI.

[0128] (Variation of Proposal 2-2) A "common field" may be provided to indicate whether it is a one-stage DCI, the first DCI of a two-stage DCI (followed by the second DCI), or the second DCI of a two-stage DCI.

[0129] (Effect) As explained above, according to Proposal 2-2, when NW / gNB sets a common SS / CORESET configuration for the first DCI of a single-stage DCI and the first DCI of a two-stage DCI, it sets different parameter settings (e.g., different DCI formats, different aggregation levels) for the first DCI of a single-stage DCI and the first DCI of a two-stage DCI, or it provides a field indicating the first DCI of a single-stage DCI and the first DCI of a two-stage DCI, and a DCI field indicating whether the second DCI of a two-stage DCI exists, so that the UE can properly distinguish between the first DCI of a single-stage DCI and the first DCI of a two-stage DCI.

[0130] <Variations of Proposals 1-2> (Combinations with Options) In Proposals 1-2 of this Disclosure, which proposal applies, or which option or alternative is used, may be determined by: - ​​Setting by higher-level parameters - Determining by relevant higher-level parameters - Indicated in MAC CE or DCI - Determining based on UE capabilities - Stated in the specification - Determining based on conditions stated in the specification - Determining by higher-level parameters / MAC CE / DCI configuration and reported UE capabilities (combinations of the above determinations)

[0131] In proposals 1 and 2 of this disclosure, multiple options, alternatives to related technologies, and alternatives may be combined as a single option / alternative. Throughout the proposal, the measured RS (reference signal) will be the QCL source RS in the active TCI state / indicated TCI state.

[0132] (Signals from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW). Throughout the proposal, the network (NW) may also be referred to as a gNB. • Information via upper-layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) • MAC CE subheader with a new LCID extending the existing MAC CE (e.g., introducing a new octet) • DCI DCI field: Existing DCI field or newly introduced DCI field RNTI: Existing RNTI or DCI with a scrambled CRC by the newly introduced RNTI DCI format: Existing DCI format or newly introduced DCI format • Combinations of the above information

[0133] In this disclosure, the UE may receive information from the network (NW) in the following periodic forms: Option 1: Receiving information periodically; Option 2: Receiving information semi-persistently (triggered by instructions from the UE or gNB); Option 3: Receiving information aperiodically (triggered by instructions from the UE or gNB).

[0134] In this disclosure, the UE may receive information from the network (NW) as the following QCL rules: • QCL Type A • QCL Type B • QCL Type C • QCL Type D

[0135] In this disclosure, the QCL resource RS for each QCL type may be configured as follows: • SSB (SS / PBCH Block) • CSI-RS with / without repetition • TRS (tracking reference signal) • PDCCH / PDSCH DMRS

[0136] In this disclosure, information from the network (NW) is configured / instructed as follows: • Common UE / Dedicated UE • Cell-specific / Common cell • Per UE / CC / BWP / Bandwidth / Cell / CG

[0137] In this disclosure, the UE may report the following types of information to the network (NW). Throughout the proposal, the network (NW) may be replaced by gNB. • Information via upper-layer signaling (e.g., RRC messages / LPP messages) • MAC CE subheader with a new LCID, extending an existing MAC CE (e.g., introduction of a new octet) • UCI on PUCCH or PUSCH • Combinations of the above information

[0138] In this disclosure, the UE may report information to the network (NW) in the following periodic forms: Option 1: Send information periodically Option 2: Send information semi-persistently (triggered by instructions from the UE or gNB) Option 3: Send information aperiodically (triggered by instructions from the UE or gNB)

[0139] <UE capability> The UE capability, which indicates the capabilities of the UE, may include the following information indicating the capabilities of the UE. For example, the following new UE capability and report signaling (and RRC settings) may be defined. Note that the information indicating the capabilities of the UE may correspond to the information defining the capabilities of the UE. The UE may report the following terminal capability information to the gNB: - Terminal capability for each proposal - Capability for each option or combination of options in each proposal - Capability for each alternative or combination of alternatives in each proposal The UE may report the above terminal capability information to the gNB for each frequency: - Capability for each UE / FR1 / FR2 / FR2-1 / FR2-2 / FR3 / SCS / band / BC / FC / FSPC, etc. The UE may report the above terminal capability information to the gNB for each cell: - Capability for each UE / cell / TDD / FDD, etc.

[0140] The capabilities of the UE described above and the configuration of this proposal are closely related, and if the functionality of each option in each proposal depends on the capabilities of the UE, the gNB may select or permit the functionality of each option based on the capabilities reported by the UE.

[0141] Next, the configurations of gNB100 and UE200 will be described. Note that the configurations of gNB100 and UE200 described below are examples of functions related to this embodiment. gNB100 and UE200 may have functions not shown. Furthermore, the function classification and / or the name of the function unit are not limited, as long as the function performs the operations related to this embodiment.

[0142] <Base Station Configuration> Figure 18 is a block diagram showing an example of the configuration of a base station 100 (gNodeB (gNB) 100) according to this embodiment. The gNB 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The gNB 100 communicates wirelessly with the UE 200 (see Figure 19).

[0143] The transmitter 101 transmits downlink (DL) signals to the UE200. For example, the transmitter 101 transmits DL signals (e.g., RRC, SIB, MAC CE, DCI, notification, acknowledgment, etc., as described above) under the control of the control unit 103.

[0144] The DL signal may include, for example, downlink data signals and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission for the UE200 (e.g., UL grants). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include reference signals.

[0145] The channels used to transmit DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, gNB100 transmits downlink control information to UE200 using the PDCCH and transmits downlink data signals using the PDSCH.

[0146] The reference signals included in the DL signal may include, for example, at least one of the following: Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS). For example, reference signals such as DMRS and PTRS are used for demodulating the downlink data signal and are transmitted using PDSCH.

[0147] The receiving unit 102 receives uplink (UL) signals transmitted from the UE200. For example, the receiving unit 102 receives UL signals (e.g., the requests and notifications mentioned above) under the control of the control unit 103.

[0148] The transmitting unit 101 and the receiving unit 102 may together be referred to as the communication unit.

[0149] The control unit 103 controls the communication operation of the gNB100, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102.

[0150] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101. The control unit 103 also outputs the data and control information received from the reception unit 102 to the upper layer.

[0151] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals received from the UE200 (e.g., data and control information, etc.) and / or data and control information, etc. acquired from higher layers. Information regarding the allocated resources may be included in the control information transmitted to the UE200.

[0152] <Terminal Configuration> Figure 19 is a block diagram showing an example of the configuration of the UE200 according to this embodiment. The UE200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The UE200 communicates with, for example, the gNB100 wirelessly.

[0153] The transmitting unit 202 transmits the UL signal to the gNB100. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

[0154] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of the UE200 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

[0155] The channels used to transmit UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes PUCCH (Physical Uplink Control Channel). For example, UE200 transmits uplink control information to gNB100 using PUCCH and transmits uplink data signals using PUSCH.

[0156] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (e.g., PUSCH).

[0157] For example, the receiving unit 201 may receive physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), and other signals from the NW or gNB 100.

[0158] For example, the receiving unit 201 may receive values ​​related to PDCCH-Config (controlResourceSetToAddModList, controlResourceSetToReleaseList, searchSpacesToAddModList, searchSpacesToReleaseList), values ​​related to SearchSpace (searchSpaceId, controlResourceSetId, monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, nrofCandidates {aggregationLevel}, searchSpaceType {CSS, USS, DCI format}), or values ​​related to ControlResourceSet (controlResourceSetId, frequencyDomainResources, duration, cce-REG-MappingType, precoderGranularity, tci-StatesPDCCH, tci-PresentInDCI, pdcch-DMRS-ScramblingID, rb-Offset) from the NW or gNB100 as RRC (Radio Resource Control) signaling.

[0159] For example, the receiving unit 201 may monitor and decode the target DCI based on information indicating the search space associated with the DCI and information indicating the control resource set (CORESET) in response to a command from the control unit 203.

[0160] The receiving unit 201 and the transmitting unit 202 may together be referred to as the communication unit.

[0161] The control unit 203 controls the communication operation of the UE200, including the receiving process in the receiving unit 201 and the transmitting process in the transmitting unit 202.

[0162] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.

[0163] For example, the control unit 203 may perform control based on DCI and RRC signaling.

[0164] For example, the control unit 203 may monitor candidate physical downlink control channels (PDCCHs) based on information indicating the search space associated with the DCI and information indicating the control resource set (CORESET), and issue a command to the receiving unit 201 to decode the target DCI.

[0165] For example, the control unit 203 may monitor PDCCH candidates based on the first DCI of a two-stage DCI and issue a command to the receiving unit 201 to decode the target DCI.

[0166] For example, the control unit 203 may perform discrimination, recognition, and control of the first and second DCIs of a two-stage DCI, as well as distinguishing and identifying them from normal DCIs, and other arbitrary controls, based on information indicating the SearchSpace associated with the DC and DCI, and information indicating the Control Resource Set (CORESET).

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

[0168] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

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

[0170] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of gNB100 and UE200 may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0171] Each function in the gNB100 and UE200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0172] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may be implemented by the processor 1001.

[0173] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 203 of the UE200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

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

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

[0176] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 may be implemented by the communication device 1004.

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

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

[0179] Furthermore, gNB100 and UE200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0180] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0181] <Applicable Systems> The embodiments described herein may be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as at least one of the next-generation systems that are extended, modified, created, or defined based on these. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0182] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged in order, as long as they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0183] <Base Station Operation> The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides the base station, but it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0184] <Direction of Input / Output> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes.

[0185] <Handling of Input / Output Information, etc.> Input and output information, etc. may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, etc. may be overwritten, updated, or appended to. Output information, etc. may be deleted. Input information, etc. may be transmitted to other devices.

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

[0187] <Variations of Embodiments, etc.> Each embodiment / appearance described in this disclosure may be used individually, in combination, or switched between during implementation. Furthermore, notification of predetermined information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0188] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

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

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

[0191] <Information, Signals> The information, signals, etc. described herein may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0192] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0193] <Systems and Networks> The terms “systems” and “networks” as used in this disclosure are interchangeable.

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

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

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

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

[0198] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

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

[0200] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0201] <Base Station / Mobile Station> At least one of a base station and a mobile station may be called a transmitting device, receiving device, communication device, etc. At least one of a base station and a mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes cases where the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and those mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

[0204] Figure 21 shows an example of the configuration of vehicle 2001. As shown in Figure 21, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

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

[0206] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0208] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0209] The Information Services Unit 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

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

[0211] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029 provided in the vehicle 2001.

[0212] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0213] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0214] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0215] <Meaning and Interpretation of Terms> The terms “determining” and “decision” as used in this disclosure may encompass a wide variety of actions. “Determining” and “decision” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), ascertaining, etc. “Determining” and “decision” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc. “Determining” and “decision” may also include resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering that some action has been "judged" or "decided." Furthermore, "judgment (decision)" can be reinterpreted as "assuming," "expecting," "considering," etc.

[0216] The terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0218] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on".

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

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

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

[0222] <Time units such as TTI, frequency units such as RB, and radio frame configuration> A radio frame may consist of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

[0226] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

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

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

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

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

[0231] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

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

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

[0234] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

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

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

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

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

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

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

[0241] <Maximum Transmit Power> The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0242] <Articles> In this disclosure, if articles are added by translation, such as A, An, and the in English, this disclosure may also include the fact that the noun following these articles is plural.

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

[0244] One aspect of this disclosure is useful for wireless communication systems.

[0245] 10 Wireless communication system 20 NG-RAN A7a PDCCH (Set of cells 1) A7b PDCCH (Set of cells 2) 100 Base station (gNB) 200 Terminal (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit

Claims

1. A terminal comprising: a receiving unit that receives information indicating a first search space and information indicating a first control resource set (CORESET) associated with a first downlink control information (DCI), and monitors candidate physical downlink control channels (PDCCH) based on the information indicating the first search space and the information indicating the first control resource set; and a control unit that detects the first downlink control information based on the candidate physical downlink control channel, and determines whether or not there is second downlink control information based on the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set, wherein if the second downlink control information exists, the control unit controls the reception of the second downlink control information based on the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set.

2. The receiving unit receives information indicating a second search space associated with the second downlink control information, and the information indicating the first search space and the information indicating the second search space are set separately, as described in claim 1.

3. The receiving unit receives information indicating a second control resource set associated with the second downlink control information, and the information indicating the first control resource set and the information indicating the second control resource set are set separately, as described in claim 1.

4. The terminal according to claim 1, wherein the information indicating the first search space and the information indicating the first control resource set associated with the first downlink control information when the second downlink control information does not exist, and the information indicating the first search space and the information indicating the first control resource set associated with the first downlink control information when the second downlink control information exists, are each set separately.

5. The terminal according to claim 1, wherein the receiving unit receives a radio resource control signal that enables or disables the transmission of the second downlink control information.

6. A communication method comprising: a terminal receiving information indicating a first search space and information indicating a first control resource set (CORESET) associated with a first downlink control information (DCI); monitoring candidate physical downlink control channels (PDCCH) based on the information indicating the first search space and the information indicating the first control resource set; detecting the first downlink control information based on the candidate physical downlink control channel; determining the presence or absence of second downlink control information based on the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set; and, if the second downlink control information exists, controlling the reception of the second downlink control information based on the first downlink control information, the information indicating the first search space, or the information indicating the first control resource set.

Images