User equipment, base station and method

By configuring the search space set and optimizing the monitoring order of PDCCH candidates in the fifth generation cellular system, the problems of flexibility and low efficiency of multi-service communication are solved, and more efficient communication and resource usage are achieved, suitable for low latency and high reliability. Sexual communication.

CN114450915BActive Publication Date: 2024-11-08SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080069094.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-10-03
Filing Date
2020-10-02
Publication Date
2024-11-08
Estimated Expiration
2040-10-02

AI Technical Summary

Technical Problem

In existing fifth-generation cellular systems, the flexibility and efficiency of multi-service communication are limited, making it difficult to meet the needs of high-speed and large-capacity transmission, especially in low-latency and high-reliability communications and large-scale machine-type device connections.

Method used

By transmitting RRC parameters between the user equipment (UE) and the base station, the search space set is configured to determine the monitoring timing of PDCCH candidates, optimize the monitoring order of PDCCH candidates, improve the monitoring efficiency of PDCCH candidates, and enhance the carrier aggregation and dual-connection operations. Radio resource usage efficiency.

Benefits of technology

Improve communication flexibility and efficiency, enhance the number of PDCCH monitoring opportunities, reduce the latency of URLLC services, reduce complexity and power consumption, and improve the support capabilities for multi-service types of devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114450915B_ABST
    Figure CN114450915B_ABST
Patent Text Reader

Abstract

The present invention describes a method performed by a user equipment (UE). The method includes: transmitting to a base station a capability indicating a plurality of combinations (X, Y) for PDCCH monitoring, each combination (X, Y) being associated with a corresponding maximum number of monitored PDCCH candidates; determining spans in which PDCCH is monitored, and each span is a plurality of consecutive OFDM symbols up to Y; determining from the plurality of combinations one or more combinations (X, Y) in which the value of X is equal to or less than the minimum value of the gap distance between every two consecutive spans; determining from the one or more combinations (X, Y) a combination (X, Y) having a larger maximum number of monitored PDCCH candidates for PDCCH monitoring.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a terminal device, a base station device, a communication method, and an integrated circuit. Background Art

[0002] Currently, as radio access systems and radio network technologies for the fifth generation cellular system, as extension standards of Long Term Evolution (LTE), technical investigations and standard development are being conducted on Advanced LTE Pro (LTE-A Pro) and New Radio Technology (NR) in the 3rd Generation Partnership Project (3GPP).

[0003] In the fifth generation cellular system, three services of enhanced mobile broadband (eMBB) that enables high-speed and large-capacity transmission, ultra-reliability and low-latency communication (URLLC) that enables low-latency and high-reliability communication, and massive machine type communication (mMTC) that allows connection of a large number of machine type devices such as the Internet of Things (IoT) have been requested as hypothetical scenarios.

[0004] For example, a wireless communication device may communicate with one or more devices for multiple service types. However, currently existing systems and methods may only provide limited flexibility and efficiency for multiple service communications. As shown in this discussion, systems and methods according to the present invention support frequency PDCCH monitoring opportunities to monitor DCI formats in time slots, which can improve communication flexibility and efficiency and may be beneficial. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 is a block diagram illustrating one configuration of one or more base stations and one or more user equipment (UE) in which systems and methods for search space configuration and / or DCI alignment may be implemented;

[0006] Figure 2 is a diagram showing an RRC parameter SearchSpace having an information element structure A 200;

[0007] Figure 3 is a diagram showing an RRC parameter SearchSpace-v16 having an information element structure B 300;

[0008] Figure 4 is a diagram showing an RRC parameter SearchSpace-v16 having an information element structure C 400;

[0009] Figure 5 is a flow chart illustrating one specific implementation of a method 500 for determining PDCCH candidates monitored by a UE 102 .

[0010] Figure 6is a diagram showing one example 600 of how to determine PDCCH monitoring occasions for PDCCH candidates based on received RRC parameters related to a search space configuration.

[0011] Figure 7 An example 700 of PDCCH monitoring span determination is shown.

[0012] Figure 8 shows various components that may be utilized in a UE;

[0013] Fig. 9 shows various components that may be utilized in a base station; DETAILED DESCRIPTION

[0014] The present invention describes a method performed by a user equipment (UE). The method includes: receiving a first radio resource control (RRC) parameter from a base station to provide a search space set configuration; determining PDCCH candidates to be allocated for monitoring in a time slot in ascending order of the configured search space set index until the total number of counted PDCCH candidates to be allocated for monitoring in a duration reaches a first number; monitoring counted PDCCH candidates, wherein for each search space set with a configured search space set index, in a first case where the total number of counted PDCCH candidates does not exceed the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates configured for the search space set is counted as the total number of counted PDCCH candidates, and in a second case where the total number of counted PDCCH candidates exceeds the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates is counted in descending order of aggregation level as the total number of counted PDCCH candidates until the total number of counted PDCCH candidates reaches the first number.

[0015] The present invention describes a method performed by a base station. The method includes: transmitting a first radio resource control (RRC) parameter to a user equipment (UE) to provide a search space set configuration; determining PDCCH candidates to be allocated for monitoring in a time slot in ascending order of the configured search space set index until the total number of counted PDCCH candidates to be allocated for monitoring in a duration reaches a first number; transmitting counted PDCCH candidates, wherein for each search space set with a configured search space set index, in a first case where the total number of counted PDCCH candidates does not exceed the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates configured for the search space set is counted as the total number of counted PDCCH candidates, and in a second case where the total number of counted PDCCH candidates exceeds the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates is counted in descending order of aggregation level as the total number of counted PDCCH candidates until the total number of counted PDCCH candidates reaches the first number.

[0016] The present invention describes a user equipment (UE). The UE includes: a receiving circuit configured to receive a first radio resource control (RRC) parameter from a base station to provide a search space set configuration; a control circuit configured to determine PDCCH candidates to be allocated for monitoring in a time slot in ascending order of a configured search space set index until the total number of counted PDCCH candidates to be allocated for monitoring in a duration reaches a first number; a receiving circuit configured to monitor counted PDCCH candidates, wherein for each search space set with a configured search space set index, in a first case where the total number of counted PDCCH candidates does not exceed the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates configured for the search space set is counted as the total number of counted PDCCH candidates, and in a second case where the total number of counted PDCCH candidates exceeds the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates is counted in descending order of aggregation level as the total number of counted PDCCH candidates until the total number of counted PDCCH candidates reaches the first number.

[0017] The present invention describes a base station. The base station includes: a transmitting circuit configured to transmit a first radio resource control (RRC) parameter to a user equipment (UE) to provide a search space set configuration; a control circuit configured to determine PDCCH candidates to be allocated for monitoring in a time slot in ascending order of a configured search space set index until the total number of counted PDCCH candidates to be allocated for monitoring in a duration reaches a first number; a transmitting circuit configured to transmit counted PDCCH candidates, wherein for each search space set with a configured search space set index, in a first case where the total number of counted PDCCH candidates does not exceed the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates configured for the search space set is counted as the total number of counted PDCCH candidates, and in a second case where the total number of counted PDCCH candidates exceeds the first number when counting the number of PDCCH candidates configured for the search space set, the number of PDCCH candidates is counted in descending order of aggregation level as the total number of counted PDCCH candidates until the total number of counted PDCCH candidates reaches the first number.

[0018] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future needs. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). 3GPP NR (New Radio) is the name given to a project to improve the LTE mobile phone or device standard to cope with future needs. In one aspect, LTE has been modified to provide support and specifications for New Radio Access (NR) and Next Generation Radio Access Network (NG-RAN) (TS 38.331, 38.321, 38.300, 37.300, 38.211, 38.212, 38.213, 38.214, etc.).

[0019] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), Advanced LTE Pro, New Radio (NR), and other 3G / 4G / 5G standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15 and / or Narrowband Internet of Things (NB-IoT)). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0020] A wireless communication device may be an electronic device that is used to transmit voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE (user equipment), access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, relay node, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In the 3GPP specification, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device".

[0021] In the 3GPP specifications, base stations are often referred to as gNBs, Node Bs, eNBs, Home Enhanced or Evolved Node Bs (HeNBs), or some other similar terms. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station", "gNB", "Node B", "eNB", and "HeNB" may be used interchangeably herein to represent the more general term "base station". In addition, an example of a "base station" is an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent a wireless communication device and / or a base station.

[0022] It should be noted that, as used herein, a "cell" may be any communication channel that is specified by a standardization or regulatory body for use in International Mobile Telecommunications-Advanced (IMT-Advanced), IMT-2020 (5G), and all or a subset thereof, such that it is adopted by 3GPP as an authorized band (e.g., a frequency band) for communications between a base station and a UE. It should also be noted that in the NR, NG-RAN, E-UTRA, and E-UTRAN general descriptions, as used herein, a "cell" may be defined as "a combination of downlink resources and optional uplink resources." The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information sent on the downlink resources.

[0023] "Configured cells" are those cells that the UE is aware of and is permitted by the base station to transmit or receive information. "Configured cells" may be serving cells. The UE may receive system information and perform the required measurements on the configured cells. The "configured cells" for a radio connection may consist of a primary cell and / or zero, one or more secondary cells. "Activated cells" are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells on which the UE monitors its physical downlink control channel (PDCCH), and in the case of downlink transmissions, those cells on which the UE decodes its physical downlink shared channel (PDSCH). "Deactivated cells" are those configured cells on which the UE does not monitor the transmission PDCCH. It should be noted that "cells" may be described in different dimensions. For example, a "cell" may have time, space (e.g., geographic) and frequency characteristics.

[0024] The base station can be connected to the 5G core network (5G-CN) via the NG interface. 5G-CN may be referred to as the next generation core network (NGC) or the 5G core network (5GC). The base station may also be connected to the evolved packet core (EPC) via the S1 interface. For example, the base station may be connected to the next generation (NG) mobility management function via the NG-2 interface, and to the NG core user plane (UP) function via the NG-3 interface. The NG interface supports a many-to-many relationship between the NG mobility management function, the NG core UP function, and the base station. The NG-2 interface is an NG interface for the control plane, and the NG-3 interface is an NG interface for the user plane. For example, for an EPC connection, the base station may be connected to the MME via the S1-mobility management entity (MME) interface, and to the serving gateway (S-GW) via the S1-U interface. The S1 interface supports a many-to-many relationship between the MME, the serving gateway, and the base station. The S1-MME interface is an S1 interface for the control plane, and the S1-U interface is an S1 interface for the user plane. The Uu interface is a radio interface for a radio protocol between a UE and a base station.

[0025] The radio protocol architecture may include a user plane and a control plane. The user plane protocol stack may include a packet data convergence protocol (PDCP), a radio link control (RLC), a medium access control (MAC), and a physical (PHY) layer. A DRB (data radio bearer) is a radio bearer that carries user data (as opposed to control plane signaling). For example, a DRB may be mapped to a user plane protocol stack. The PDCP, RLC, MAC, and PHY sublayers (terminating at the base station 460a on the network) may perform user plane functions (e.g., header compression, encryption, scheduling, ARQ, and HARQ). The PDCP entity is located in the PDCP sublayer. The RLC entity may be located in the RLC sublayer. The MAC entity may be located in the MAC sublayer. The PHY entity may be located in the PHY sublayer.

[0026] The control plane may include a control plane protocol stack. The PDCP sublayer (terminated in the base station on the network side) may perform functions of the control plane (e.g., encryption and integrity protection). The RLC sublayer and the MAC sublayer (terminated in the base station on the network side) may perform the same functions as the user plane. The Radio Resource Control (RRC) (terminated in the base station on the network side) may perform the following functions. RRC may perform broadcast functions, paging, RRC connection management, radio bearer (RB) control, mobility functions, UE measurement reporting and control. The Non-Access Stratum (NAS) control protocol (terminated in the MME on the network side) may perform Evolved Packet System (EPS) bearer management, authentication, Evolved Packet System Connection Management (ECM)-IDLE mobility processing, paging initiation and security control in ECM-IDLE, etc.

[0027] A signaling radio bearer (SRB) is a radio bearer (RB) that can only be used to transmit RRC and NAS messages. Three SRBs can be defined. SRBO can be used for RRC messages using the common control channel (CCCH) logical channel. SRB1 can be used for RRC messages (which may include piggybacked NAS messages) and NAS messages before SRB2 is established, all of which use the dedicated control channel (DCCH) logical channel. SRB2 can be used for RRC messages including recorded measurement information and NAS messages, all of which use the DCCH logical channel. The priority of SRB2 is lower than that of SRB1, and it can be configured by the network (e.g., base station) after security activation. The broadcast control channel (BCCH) logical channel can be used to broadcast system information. Some BCCH logical channels can transmit system information that can be sent from the network to the UE via the BCH (broadcast channel) transport channel. BCH can be sent on the physical broadcast channel (PBCH). Some BCCH logical channels can transmit system information that can be sent from the network to the UE via the DL-SCH (downlink shared channel) transport channel. Paging can be provided by using the paging control channel (PCCH) logical channel.

[0028] For example, the DL-DCCH logical channel may be used for (but not limited to) RRC reconfiguration message, RRC reestablishment message, RRC release, UE capability query message, DL information transfer message or security mode command message. The UL-DCCH logical channel may be used for (but not limited to) measurement report message, RRC reconfiguration complete message, RRC reestablishment complete message, RRC setup complete message, security mode complete message, security mode failure message, UE capability information message, UL handover preparation delivery message, UL information delivery message, counter check response message, UE information response message, neighbor indication message, RN (relay node) reconfiguration complete message, MBMS counting response message, inter-frequency RSTD measurement indication message, UE assistance information message, in-device coexistence indication message, MBMS interest indication message and SCG failure information message. The DL-CCCH logical channel may be used for (but not limited to) RRC reestablishment message, RRC reestablishment rejection message, RRC rejection message or RRC setup message. The UL-CCCH logical channel may be used for (but not limited to) RRC reestablishment request message or RRC setup request message.

[0029] The system information may be divided into a master information block (MIB) and a plurality of system information blocks (SIBs).

[0030] The UE may receive one or more RRC messages from the base station to obtain the RRC configuration or parameters. The RRC layer of the UE may configure the RRC layer and / or lower layers (e.g., PHY layer, MAC layer, RLC layer, and PDCP layer) of the UE according to the RRC configuration or parameters that may be configured by the RRC message, the broadcast system information, etc. The base station may transmit one or more RRC messages to the UE so that the UE configures the RRC layer and / or lower layers of the UE according to the RRC configuration or parameters that may be configured by the RRC message, the broadcast system information, etc.

[0031] When carrier aggregation is configured, the UE may have one RRC connection with the network. One radio interface may provide carrier aggregation. During RRC establishment, re-establishment, and handover, one serving cell may provide non-access stratum (NAS) mobility information (e.g., tracking area identity (TAI)). During RRC re-establishment and handover, one serving cell may provide security input. The cell may be referred to as a primary cell (PCell). In the downlink, the component carrier corresponding to the PCell may be a downlink primary component carrier (DL PCC), and in the uplink, the component carrier may be an uplink primary component carrier (UL PCC).

[0032] Depending on UE capabilities, one or more SCells may be configured to form a group of serving cells together with the PCell. In the downlink, the component carrier corresponding to the SCell may be a downlink secondary component carrier (DL SCC), and in the uplink, the component carrier may be an uplink secondary component carrier (UL SCC).

[0033] Thus, the configured set of serving cells for the UE may consist of one PCell and one or more SCells. For each SCell, the use of uplink resources (in addition to downlink resources) performed by the UE may be configurable. The number of configured DL SCCs may be greater than or equal to the number of UL SCCs, and the SCell may not be configured only for use of uplink resources.

[0034] From the perspective of the UE, each uplink resource may belong to one serving cell. The number of configurable serving cells depends on the aggregation capability of the UE. The PCell can only be changed using a switching process (for example, using a security key change and a random access process). The PCell can be used for the transmission of the PUCCH. The primary secondary cell (PSCell) can also be used for the transmission of the PUCCH. The PSCell may be referred to as the primary SCG cell or SpCell of the secondary cell group. The PCell or PSCell cannot be deactivated. Reestablishment may be triggered when the PCell experiences a radio link failure (RLF), not when the SCell experiences an RLF. In addition, NAS information may be obtained from the PCell.

[0035] Reconfiguration, addition, and removal of SCells may be performed by RRC. In case of synchronous handover or reconfiguration, the radio resource control (RRC) layer may also add, remove, or reconfigure SCells for use with the target PCell. When a new SCell is added, dedicated RRC signaling may be used to send all necessary system information for the SCell (e.g., when in connected mode, the UE does not need to obtain broadcast system information directly from the SCell).

[0036] The systems and methods described herein can enhance the efficient use of radio resources in carrier aggregation (CA) operations. Carrier aggregation refers to the simultaneous use of more than one component carrier (CC). In carrier aggregation, more than one cell can be aggregated into a UE. In one example, carrier aggregation can be used to increase the effective bandwidth available for use by the UE. In traditional carrier aggregation, it is assumed that a single base station provides multiple serving cells for the UE. Even in scenarios where two or more cells can be aggregated (e.g., a macro cell aggregated with a remote radio head (RRH) cell), the cells can be controlled (e.g., scheduled) by a single base station.

[0037] The systems and methods described herein can enhance the effective use of radio resources in carrier aggregation operations. Carrier aggregation refers to the simultaneous use of more than one component carrier (CC). In carrier aggregation, more than one cell can be aggregated into a UE. In one example, carrier aggregation can be used to increase the effective bandwidth available for UE. In traditional carrier aggregation, it is assumed that a single base station provides multiple service cells for the UE. Even in scenarios where two or more cells can be aggregated (e.g., macro cells aggregated with remote radio head (RRH) cells), the cells can be controlled (e.g., scheduled) by a single base station. However, in smaller cell deployment scenarios, each node (e.g., base station, RRH, etc.) can have its own independent scheduler. In order to maximize the efficiency of radio resource utilization of two nodes, the UE can be connected to two or more nodes with different schedulers. The systems and methods described herein can enhance the effective use of radio resources in dual-connection operations. The UE can configure multiple groups of service cells, each of which can have carrier aggregation operations (e.g., if the group includes more than one service cell).

[0038] In dual connectivity (DC), the UE may be required to be able to have UL-CA with simultaneous PUCCH / PUCCH and PUCCH / PUSCH transmissions across cell groups (CGs). In smaller cell deployment scenarios, each node (e.g., eNB, RRH, etc.) may have its own independent scheduler. In order to maximize the radio resource utilization efficiency of the two nodes, the UE may be connected to two or more nodes with different schedulers. The UE may be configured with multiple groups of service cells, each of which may have carrier aggregation operation (e.g., if the group includes more than one service cell). When configured with a primary cell group and a secondary cell group, a UE in RRC_CONNECTED may be configured with dual connectivity or MR-DC. A cell group (CG) may be a subset of the UE's service cells configured with dual connectivity (DC) or MR-DC, i.e., a primary cell group (MCG) or a secondary cell group (SCG). The primary cell group may be a UE's service cell group including a PCell and zero or more secondary cells. A secondary cell group (SCG) may be a secondary cell group of a UE configured with DC or MR-DC, which includes a PSCell and zero or more other secondary cells. A primary secondary cell (PSCell) may be an SCG cell in which the UE is instructed to perform random access when performing an SCG change procedure. "PSCell" may also be referred to as a primary SCG cell. In dual connectivity or MR-DC, two MAC entities may be configured in the UE: one for the MCG and one for the SCG. Each MAC entity may be configured by an RRC having a serving cell that supports PUCCH transmission and contention-based random access. In the MAC layer, the term "special cell" (SpCell) may refer to such a cell, while the term SCell may refer to other serving cells. The term SpCell may refer to a PCell of an MCG or a PSCell of an SCG, depending on whether the MAC entity is associated with an MCG or an SCG, respectively. The timing advance group (TAG) of the SpCell containing the MAC entity may be referred to as a primary TAG (pTAG), while the term secondary TAG (sTAG) refers to other TAGs.

[0039] DC can be further enhanced to support multi-RAT dual connectivity (MR-DC). MR-DC can be a generalization of dual connectivity (DC) within E-UTRA described in 36.300, where a multi-Rx / Tx UE can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, one providing E-UTRA access and the other providing NR access. One node acts as a master node (MN) and the other node acts as a secondary node (SN). MN and SN are connected via a network interface, and at least Mn is connected to the core network. In DC, the PSCell can be a primary and secondary cell. In EN-DC, the PSCell can be a primary SCG cell or SpCell of a secondary cell group.

[0040] E-UTRAN can support MR-DC via E-UTRA-NR dual connectivity (EN-DC), where the UE is connected to one eNB acting as MN and one en-gNB acting as SN. The en-gNB is the node that provides NR user plane and control plane protocol termination to the UE and acts as a secondary node in EN-DC. The eNB is connected to the EPC via the S1 interface and to the en-gNB via the X2 interface. The en-gNB can also be connected to the EPC via the S1-U interface and to other en-gNBs via the X2-U interface.

[0041] Once started, a timer runs until it is stopped or until it expires; otherwise, it does not run. You can start a timer if it is not running, or restart it if it is running. You can always start or restart a timer from its initial value.

[0042] For NR, technologies for aggregating NR carriers can be studied. Lower layer aggregation such as carrier aggregation (CA) for LTE and upper layer aggregation such as DC are studied. From a layer 2 / 3 perspective, aggregation of carriers with different numerologies can be supported in NR.

[0043] The main services and functions of the RRC sublayer may include the following:

[0044] - Broadcast of system information related to the Access Stratum (AS) and the Non-Access Stratum (NAS);

[0045] -Paging initiated by CN or RAN;

[0046] - Establishment, maintenance and release of the RRC connection between the UE and the NR RAN, including:

[0047] -Addition, modification and release of carrier aggregation;

[0048] - Addition, modification and release of dual connectivity in NR or between LTE and NR;

[0049] - Security features including key management;

[0050] - Establishment, configuration, maintenance and release of signalling radio bearers and data radio bearers;

[0051] - Mobility features, including:

[0052] - Switch;

[0053] -UE cell selection and reselection and control of cell selection and reselection;

[0054] -Context transfer during switching;

[0055] -QoS management function;

[0056] -UE measurement reporting and control of reporting;

[0057] - Message delivery from NAS / UE to UE / NAS.

[0058] Each MAC entity of the UE can be configured by RRC with a discontinuous reception (DRX) function, which controls the UE's PDCCH monitoring activities for the C-RNTI (Radio Network Temporary Identifier), CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and TPC-SRS-RNTI of the MAC entity. For cell-level scheduling, the following identifiers are used:

[0059] -C (Cell)-RNTI: a unique UE identity used as an identifier for the RRC connection and for scheduling;

[0060] -CS (Configured Scheduling)-RNTI: unique UE identity used for semi-persistent scheduling in downlink;

[0061] -INT-RNTI: downlink preemption identifier;

[0062] -P-RNTI: Identifier for paging and system information change notification in downlink;

[0063] -SI-RNTI: identification of broadcast and system information in downlink;

[0064] -SP-CSI-RNTI: unique UE identity used for semi-persistent CSI reporting on PUSCH;

[0065] For power and slot format control, the following flags are used:

[0066] -SFI-RNTI: identification of the timeslot format;

[0067] -TPC-PUCCH-RNTI: unique UE identifier used to control PUCCH power;

[0068] -TPC-PUSCH-RNTI: unique UE identifier used to control PUSCH power;

[0069] -TPC-SRS-RNTI: unique UE identifier used to control SRS power;

[0070] During random access, the following flags are also used:

[0071] -RA-RNTI: Random access response identifier in downlink;

[0072] - Temporary C-RNTI: UE identity temporarily used for scheduling during the random access procedure;

[0073] - Random value for contention resolution: UE identity temporarily used for contention resolution purposes during the random access procedure.

[0074] For NR connected to 5GC, the following UE identities are used at NG-RAN level:

[0075] -I-RNTI: used to identify the RRC_INACTIVE UE context.

[0076] The sizes of various fields in the time domain are expressed in time units T. c =1 / (Δf max -N f ) represents, where Δf max =480*10 3 Hz and N f =4096. Constant κ = T s / T c =64, where T s =1 / (Δf ref -N f,ref ), Δf ref =15*10 3 Hz and N f,ref =2048

[0077] As given in Table 4.2-1 of [TS 38.211], multiple OFDM parameters are supported, where μ and the cyclic prefix of the bandwidth part are obtained from the higher layer parameters sub carrier Spacing and cyclicPrefix respectively.

[0078] The size of each field in the time domain can be expressed as a time unit T s = 1 / (15000×2048) seconds. Downlink and uplink transmissions are organized into T f =(Δf max N f / 100)T c = 10ms duration frame, each consisting of ten T sf =(Δf max N f / 1000)T c =1ms duration subframe. The number of consecutive OFDM symbols per subframe is Each frame is divided into two equally sized half-frames of five sub-frames, with each frame having half-frame 0 including sub-frames 0-4 and half-frame 1 including sub-frames 5-9.

[0079] For the subcarrier spacing (SCS) configuration μ, the time slots are numbered in increasing order within the subframe as and are numbered in increasing order within the frame as is the number of time slots per subframe with subcarrier spacing configuration μ. Consecutive OFDM symbols, where Depends on the cyclic prefix given by Tables 4.3.2-1 and 4.3.2-2 of [TS 38.211]. Slots in a subframe The start of the OFDM symbol in the same subframe is in time Start alignment.

[0080] The OFDM symbols in a slot can be classified as "downlink", "flexible" or "uplink". The signaling of the slot format is described in subclause 11.1 of [TS 38.213].

[0081] In a slot in a downlink frame, the UE may assume that downlink transmissions occur only in "downlink" or "flexible" symbols. In a slot in an uplink frame, the UE may transmit only in "uplink" or "flexible" symbols.

[0082] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods as generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0083] Figure 1 1 is a block diagram illustrating one configuration of one or more base stations 160 (e.g., eNBs, gNBs) and one or more user equipment (UEs) 102 in which systems and methods for search space configuration (or searching for PDCCH candidates) and / or DCI size alignment may be implemented. One or more UEs 102 may use one or more antennas 122a-n to communicate with one or more base stations 160. For example, UE 102 transmits electromagnetic signals to and receives electromagnetic signals from base station 160 using one or more antennas 122a-n. Base station 160 communicates with UE 102 using one or more antennas 180a-n.

[0084] It should be noted that in some configurations, one or more of the UEs 102 described herein may be implemented in a single device. For example, in some implementations, multiple UEs 102 may be combined into a single device. Additionally or alternatively, in some configurations, one or more of the base stations 160 described herein may be implemented in a single device. For example, in some implementations, multiple base stations 160 may be combined into a single device. Figure 1 In the context of, for example, according to the systems and methods described herein, a single device may include one or more UEs 102. Additionally or alternatively, according to the systems and methods described herein, one or more base stations 160 may be implemented as a single device or multiple devices.

[0085] UE 102 and base station 160 may use one or more channels 119, 121 to communicate with each other. For example, UE 102 may use one or more uplink (UL) channels 121 and signals to send information or data to base station 160. Examples of uplink channels 121 include physical uplink control channels (PUCCH) and physical uplink shared channels (PUSCH), etc. Examples of uplink signals include demodulation reference signals (DMRS) and sounding reference signals (SRS), etc. One or more base stations 160 may also use, for example, one or more downlink (DL) channels 119 and signals to transmit information or data to one or more UEs 102. Examples of downlink channels 119 include PDCCH, PDSCH, etc. Examples of downlink signals include primary synchronization signals (PSS), secondary synchronization signals (SSS), cell-specific reference signals (CRS), non-zero power channel state information reference signals (NZP CSI-RS), and zero power channel state information reference signals (ZP CSI-RS). Other types of channels or signals may also be used.

[0086] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, one or more data buffers 104, and one or more UE operation modules 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0087] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals (e.g., downlink channels, downlink signals) from the base station 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals (e.g., uplink channels, uplink signals) to the base station 160 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

[0088] The demodulator 114 may demodulate one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate one or more decoded signals 106, 110. For example, the first UE decoded signal 106 may include received payload data, which may be stored in the data buffer 104. The second UE decoded signal 110 may include overhead data and / or control data. For example, the second UE decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0089] As used herein, the term "module" may mean that a particular element or component may be implemented in hardware, software, or a combination of hardware and software. However, it should be noted that any element denoted as a "module" herein may alternatively be implemented in hardware. For example, the UE operation module 124 may be implemented in hardware, software, or a combination of the two.

[0090] In general, the UE operation module 124 may enable the UE 102 to communicate with one or more base stations 160. The UE operation module 124 may include a UE RRC information configuration module 126. The UE operation module 124 may include a UE DCI control module 128. In some embodiments, the UE operation module 124 may include a physical (PHY) entity, a medium access control (MAC) entity, a radio link control (RLC) entity, a packet data convergence protocol (PDCP) entity, and a radio resource control (RRC) entity. For example, the UE RRC information configuration module 126 may process RRC parameters for search space configurations with different information element structures. The UE DCI control module 128 may determine when and where to monitor or search for configured PDCCH candidates for each search space set based on the processed output from the UE RRC information configuration module 126. The UE DCI control module 128 may further determine the PDCCH candidates to be allocated for monitoring in the duration.

[0091] The UE operations module 124 may provide the benefit of efficiently performing PDCCH candidate searching and monitoring.

[0092] The UE operation module 124 may provide information 148 to one or more receivers 120. For example, the UE operation module 124 may inform the receiver 120 when to receive a transmission or when not to receive a transmission based on a radio resource control (RRC) message (e.g., broadcasted system information, RRC reconfiguration message), a MAC control element, and / or DCI (downlink control information). The UE operation module 124 may provide information 148 to one or more receivers 120, including a PDCCH monitoring opportunity and a DCI format size. The UE operation module 124 may inform the receiver 120 when or where to receive / monitor a PDCCH candidate of a DCI format with which DCI size.

[0093] The UE operations module 124 may provide the information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of the modulation pattern expected for transmissions from the base station 160.

[0094] The UE operation module 124 may provide information 136 to the decoder 108. For example, the UE operation module 124 may inform the decoder 108 of the expected encoding for the transmission from the base station 160. For example, the UE operation module 124 may inform the decoder 108 of the expected PDCCH candidate encoding with which DCI size for the transmission from the base station 160.

[0095] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142.

[0096] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0097] The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of the type of modulation (e.g., constellation mapping) to be used for transmission to the base station 160. The modulator 154 may modulate the coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0098] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit signals to the base station 160. The one or more transmitters 158 may upconvert the one or more modulated signals 156 and send the one or more modulated signals to the one or more base stations 160.

[0099] The base station 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, one or more data buffers 162, and one or more base station operation modules 182. For example, one or more receive paths and / or transmit paths may be implemented in the base station 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the base station 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0100] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals (e.g., uplink channels, uplink signals) from the UE 102 using one or more antennas 180a-n. For example, the receiver 178 may receive and downconvert the signals to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals (e.g., downlink channels, downlink signals) to the UE 102 using one or more antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0101] The demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The base station 160 may use the decoder 166 to decode the signal. The decoder 166 may produce one or more decoded signals 164, 168. For example, the signal 164 decoded by the first base station may include received payload data, which may be stored in the data buffer 162. The signal 168 decoded by the second base station may include overhead data and / or control data. For example, the signal 168 decoded by the second base station may provide data (e.g., PUSCH transmission data) that the base station operation module 182 may use to perform one or more operations.

[0102] In general, the base station operation module 182 can enable the base station 160 to communicate with one or more UEs 102. The base station operation module 182 can include a base station RRC information configuration module 194. The base station operation module 182 can include a base station DCI control module 196. The base station operation module 182 can include a PHY entity, a MAC entity, an RLC entity, a PDCP entity, and an RRC entity. For example, the base station operation module 196 can determine when and where to monitor or search for configured PDCCH candidates for each search space set for a UE.

[0103] The base station RRC information configuration module 194 may generate RRC parameters for search space configurations with different information element structures based on output from the base station DCI control module 196. The UE DCI control module 196 may further determine PDCCH candidates to be allocated for monitoring in the duration.

[0104] The base station operations module 182 may provide the benefit of efficiently performing PDCCH candidate searches and monitoring.

[0105] The base station operation module 182 should provide information 190 to one or more receivers 178. For example, the base station operation module 182 can inform the receiver 178 when to receive a transmission or when not to receive a transmission based on RRC messages (e.g., broadcasted system information, RRC reconfiguration messages), MAC control elements, and / or DCI (downlink control information).

[0106] The base station operations module 182 can provide information 188 to the demodulator 172. For example, the base station operations module 182 can inform the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.

[0107] The base station operations module 182 can provide information 186 to the decoder 166. For example, the base station operations module 182 can inform the decoder 166 of the encoding expected for transmissions from one or more UEs 102.

[0108] The base station operation module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the base station operation module 182 may instruct the encoder 109 to encode the transmission data 105 and / or other information 101.

[0109] Generally speaking, the base station operation module 182 can enable the base station 160 to communicate with one or more network nodes (e.g., NG mobility management function, NG core UP function, mobility management entity (MME), serving gateway (S-GW), gNB). The base station operation module 182 can also generate an RC reconfiguration message to be sent to the UE 102.

[0110] The encoder 109 may encode the transmission data 105 and / or other information 101 provided by the base station operation module 182. For example, encoding the data 105 and / or other information 101 may involve error detection and / or correction coding, mapping the data to space, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide the encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0111] The base station operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the base station operations module 182 may inform the modulator 113 of the type of modulation (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0112] The base station operation module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the base station operation module 182 may instruct the one or more transmitters 117 when (or when not) to send a signal to the one or more UEs 102. The base station operation module 182 may provide information 192 to the one or more transmitters 117, including PDCCH monitoring opportunities and DCI format sizes. The base station operation module 182 may inform the transmitter 117 when or where to transmit a PDCCH candidate with a DCI format of which DCI size. The one or more transmitters 117 may up-convert the one or more modulated signals 115 and send the one or more modulated signals to the one or more UEs 102.

[0113] It should be noted that one or more of the elements or components thereof included in the base station 160 and the UE 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc., and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0114] The base station may generate an RRC message including the one or more RRC parameters, and transmit the RRC message to the UE. The UE may receive an RRC message including one or more RRC parameters from the base station. The term "RRC parameter" in the present disclosure may alternatively be referred to as an "RRC information element". The RRC parameter may also include one or more RRC parameters. In the present disclosure, the RRC message may include system information, and the RRC message may include one or more RRC parameters. The RRC message may be sent on a broadcast control channel (BCCH) logical channel, a common control channel (CCCH) logical channel, or a dedicated control channel (DCCH) logical channel.

[0115] In the following, the description "the base station can configure the UE" may also imply / refer to "the base station can transmit an RRC message including one or more RRC parameters to the UE". Additionally or alternatively, "RRC parameters configure the UE" may also refer to "the base station can transmit an RRC message including one or more RRC parameters to the UE". Additionally or alternatively, "the UE is configured to" may also refer to "the UE may receive an RRC message including one or more RRC parameters from the base station". Additionally or alternatively, "RRC parameters are (not) provided" may also refer to "the base station may (not) transmit an RRC message including RRC parameters to the base station".

[0116] The base station may transmit an RRC message including one or more RRC parameters related to the BWP configuration to the UE. The UE may receive an RRC message including one or more RRC parameters related to the BWP configuration from the base station. For each cell, the base station may configure at least an initial DL BWP and an initial uplink bandwidth portion (initial UL BWP) to the UE. In addition, for a cell, the base station may configure additional UL and DL BWPs to the UE.

[0117] The RRC parameter initialDownlinkBWP may indicate the initial downlink BWP (initial DL BWP) configuration of the serving cell (e.g., SpCell and Scell). The base station may configure the RRC parameter locationAndBandwidth included in the initialDownlinkBWP so that the initial DL BWP contains the entire CORESET 0 of the serving cell in the frequency domain. locationAndBandwidth may be used to indicate the frequency domain location and bandwidth of the BWP. The RRC parameter initialUplinkBWP may indicate the initial uplink BWP (initial UL BWP) configuration of the serving cell (e.g., SpCell and Scell). The base station may transmit to the UE the initialDownlinkBWP and / or initialUplinkBWP, which may be included in SIB1, the RRC parameter ServingCellConfigCommon, or the RRC parameter ServingCellConfig.

[0118] SIB1 is a cell-specific system information block (SIB), which may contain information relevant to evaluating whether a UE is allowed to access a cell and defining the scheduling of other system information. SIB1 may also contain radio resource configuration information common to all UEs and prohibition information applied to unified access control. The RRC parameter ServingCellConfigCommon is used to configure the cell-specific parameters of the UE's serving cell. The RRC parameter ServingCellConfig is used to configure (add or modify) the UE with a serving cell, which may be a SpCell or SCell of an MCG or SCG. The RRC parameter ServingCellConfig in this article is mainly UE-specific, but also partially cell-specific.

[0119] The base station may configure the UE using the RRC parameter BWP-Downlink and the RRC parameter BWP-Uplink. The RRC parameter BWP-Downlink may be used to configure an additional DL BWP. The RRC parameter BWP-Uplink may be used to configure an additional UL BWP. The base station may transmit to the UE BWP-Downlink and BWP-Uplink, which may be included in the RRC parameter ServingCellConfig.

[0120] If the UE does not configure (provide) initialDownlinkBWP from the base station, the initial DL BWP is defined by the location and number of consecutive PRBs, starting from the PRB with the lowest index and ending at the PRB with the highest index in the CORESET (i.e., CORESET 0) for the Type0-PDCCH CSS set and the SCS and cyclic prefix received in the CORESET for the Type0-PDCCH CSS set. If the UE configures (provides) initialDownlinkBWP from the base station, the initial DLBWP is provided by initialDownlinkBWP. If the UE configures (provides) initialUplinkBWP from the base station, the initial ULBWP is provided by initialUplinkB WP.

[0121] The UE may be configured by a base station, at least one initial BWP and up to 4 additional BWPs. One of the initial BWP and the configured additional BWP may be activated as an active BWP. The UE may monitor the DCI format and / or receive the PDSCH in the active DL BWP. The UE may not monitor the DCI format and / or receive the PDSCH in a DL BWP other than the active DL BWP. The UE may transmit the PUSCH and / or PUCCH in the active UL BWP. The UE may not transmit the PUSCH and / or PUCCH in a BWP other than the active UL BWP.

[0122] The base station may transmit an RRC message including one or more RRC parameters related to the CORESET configuration. The base station may configure one or more CORESETs for each DL BWP in the serving cell for the UE. For example, the RRC parameter ControlResourceSetZero is used to configure CORESET 0 for the initial DL BWP. The RRC parameter ControlResourceSetZero corresponds to 4 bits. The base station may transmit to the UE ControlResourceSetZero, which may be included in the MIB or the RRC parameter ServingCellConfigCommon. The MIB may include system information transmitted on the BCH (PBCH). The RRC parameters related to the initial DL BWP configuration may also include the RRC parameter ControlResourceSetZero. The RRC parameter ControlResourceSet is used to configure a time and frequency CORESET other than CORESET0. The RRC parameter ControlResourceSetId included in the ControlResourceSet is a CORESET index used to identify the CORESET in the serving cell.

[0123] The base station may transmit an RRC message including one or more RRC parameters related to the search space configuration. The base station may determine one or more RRC parameters related to the search space configuration of the UE. The UE may receive an RRC message including one or more RRC parameters related to the search space configuration from the base station. The RRC parameters related to the search space configuration (e.g., SearchSpace or SearchSpace-v16) define how and where to search for PDCCH candidates. The RRC parameters related to the search space configuration (e.g., SearchSpace, SearchSpace-v 16) may have different information element structures, and "Search / Monitor PDCCH Candidates in DCI Format" may also be referred to as "Monitor / Search DCI Format".

[0124] Figure 2 is a diagram showing an RRC parameter (RRC Information) SearchSpace having an information element structure A 200 .

[0125] The RRC parameter SearchSpace with information element structure A is related to the search space configuration. Figure 2As shown, the RRC parameter search space may include multiple RRC parameters, such as searchSpaceId, controlResourceSetId, monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, nrofCandidates, and searchSpaceType. Some of the above RRC parameters may or may not exist in the RRC parameter SearchSpace. That is, the RRC parameter SearchSpace may include all of the above RRC parameters. That is, the RRC parameter SearchSpace may include one or more of the above RRC parameters. If some of the parameters do not exist in the RRC parameter SearchSpace, the UE 102 may apply default values ​​for each of those parameters.

[0126] Here, the RRC parameter searchSpaceId is an identifier or index of the search space. The RRC parameter searchSpaceId is used to identify the search space. More specifically, the RRC parameter searchSpaceId provides a search space set index s, 0<=s<40. Then, the search space s in the following text may refer to the search space identified by the index s indicated by the RRC parameter searchSpaceId. The RRC parameter controlResourceSetId relates to the identifier of the CORESET and is used to identify the CORESET. The RRC parameter controlResourceSetId indicates the association between the search space s and the CORESET identified by the controlResourceSetId. The RRC parameter controlResourceSetId indicates the CORESET applicable to the search space. The CORESET p in the following text may refer to the CORESET identified by the index p indicated by the RRC parameter controlResourceSetId. Each search space is associated with a CORESET. The RRC parameter monitoringSlotPeriodicityAndOffset indicates the time slot for PDCCH monitoring that is configured as periodicity and offset. Specifically, the RRC parameter monioringSlotPeriodicityAndOffset indicates k s The PDCCH monitoring period of the time slot and o sPDCCH monitoring offset of the time slot. The UE can determine which time slot is configured for PDCCH monitoring based on the RRC parameter monitoringSlotPeriodicityAndOffset. The RRC parameter monitoringSymbolsWithinSlot is used to indicate the first symbol used for PDCCH monitoring in the time slot configured for PDCCH monitoring. That is, the parameter monitoringSymbolsWithinSlot provides a PDCCH monitoring pattern within a time slot, thereby indicating the first symbol of the CORESET within the time slot (configured time slot) used for PDCCH monitoring. The RRC parameter duration indicates the number of consecutive time slots T that the search space lasts (or exists) at each opportunity (PDCCH opportunity, PDCCH monitoring opportunity). s The number of

[0127] The RRC parameters may include aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16. For CCE aggregation level 1, CCE aggregation level 2, aggregation level 4, aggregation level 8, and aggregation level 16, respectively, the RRC parameter nrofCandidates may provide multiple PDCCH candidates for each CCE aggregation level L through aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16. In other words, the value L may be set to any one of the set {1,2,4,8,16}. The number of PDCCH candidates for each CCE aggregation level L may be configured to be 0, 1, 2, 3, 4, 5, 6, or 8. For example, in the case where the number of PDCCH candidates for each CCE aggregation level L is configured to be 0, the UE may not search for PDCCH candidates for CCE aggregation L. That is, in this case, the UE may not monitor the PDCCH candidates for CCE aggregation L of the search space set s. For example, the number of PDCCH candidates per CCE aggregation level L is configured as 4, and the UE may monitor 4 PDCCH candidates of the CCE aggregation level L in the search space set s.

[0128] The RRC parameter searchSpaceType is used to indicate whether the search space set s is a CSS set or a USS set. The RRC parameter searchSpaceType may include common or ue-Specific. The RRC parameter common configures the search space set s as a CSS set and the monitored DCI format. The RRC parameter ue-Specific configures the search space set s as a USS set. The RRC parameter ue-Specific may include dci-Format. The RRC parameter dci-Format indicates that PDCCH candidates are monitored in the search space set for DCI format 0 0 and DCI format 1_0, or for DCI format 0_1 ​​and DCI format 1_1. That is, the RRC parameter searchSpaceType type indicates whether the search space set s is a CSS set or a USS set, and the DCI format to be monitored.

[0129] The USS at CCE aggregation level L is defined by the PDCCH candidate set for CCE aggregation L. The USS set may be constructed by a plurality of USSs corresponding to the corresponding CCE aggregation level L. The USS set may include one or more USSs corresponding to the corresponding CCE aggregation level L. The CSS at CCE aggregation level L is defined by the PDCCH candidate set for CCE aggregation L. The CSS set may be constructed by a plurality of USSs corresponding to the corresponding CCE aggregation level L. The CSS set may include one or more CSSs corresponding to the corresponding CCE aggregation level L.

[0130] As described above, the RRC parameter SearchSpace with the information element structure A can indicate whether the search space set s is a CSS (e.g., a CSS set) or a USS (e.g., a USS set). The base station may configure the UE to monitor PDCCH candidates of DCI format 0 0 and DCI format 1 0 or DCI format 0_1 ​​and DCI format 1_1 in the USS set via the RRC parameter SearchSpace with the information element structure A. That is, the base station may not configure the UE to monitor PDCCH candidates of different DCI formats other than the existing DCI format {DCI format 0_0, DCI format 1_0, DCI format 0_1, DCI format 1_1} in the USS via the RRC parameter SearchSpace with the information element structure. In other words, the UE may monitor PDCCH candidates of DCI format 0_0 and DCI format 1_0 or DCI format 0_1 ​​and DCI format 1_1 in the USS based on the RRC parameter SearchSpace received from the base station. The UE may not be configured to monitor PDCCH candidates of different DCI formats other than the existing DCI formats {DCI format 0_0, DCI format 1_0, DCI format 0_1, DCI format 1_1} in the USS.

[0131] Communication with new service traffic types similar to (but not limited to) URLLC may require a new DCI format design in addition to the existing DCI format. For example, some new fields may be introduced in the new DCI format to achieve different communication features. For example, some fields included in the existing DCI format may no longer be needed to adapt to different communication features. In order to achieve communication features with different service traffic types, different DCI formats can be generated according to different service traffic types. The introduction of a new DCI format in addition to the existing DCI format will be beneficial and effective for communicating with new service traffic types similar to URLLC between the base station and the UE. Therefore, the RRC parameter SearchSpace with the current information element structure A may be problematic, which cannot indicate the new DCI format. It would be beneficial to introduce RRC parameters related to the search space configuration with a new information element structure so that the base station can instruct / configure the UE to monitor PDCCH candidates of the new DCI format in addition to the existing DCI format in the USS.

[0132] Figure 3 is a diagram showing the RRC parameter SearchSpace-v16 having an information element structure B 300 .

[0133] The RRC parameter SearchSpace-v16 with information element structure B is related to the search space configuration. As an example 302, the RRC parameter SearchSpace-v16 with information element structure B may include multiple RRC parameters, such as searchSpaceId, controlResourceSetId, monitoringSlotPeriodicityAndOffset, duration, monitoringSymboIsWithinSlot, nrofCandidates, and searchSpaceType. Some of the above RRC parameters may or may not exist in the RRC parameter SearchSpace-v16. The searchSpaceType-v16 included in the RRC parameter SearchSpace-v16 with information element structure B may be different from the searchSpaceType included in the RRC parameter SearchSpace with information element structure A. searchSpaceType-v16 may only indicate that the search space set s is a USS set. searchSpaceType-v16 may not be used to indicate that the search space set s is a CSS set. The RRC parameter searchSpaceType-v16 may include ue-Specific. The RRC parameter searchSpaceType-v16 may not include common. The RRC parameter searchSpaceType-v16 may also include dci-Format-v16. dci-Format-v16 may be used to indicate whether the UE monitors PDCCH candidates of DCI formats 0_0 and 1_0 or DCI formats 0_2 and 1_2 in the USS. That is, dci-Format-v16 may be used to indicate which PDCCH candidates of DCI formats 0_0 and 1_0 or DCI formats 0_2 and 1_2 the UE monitors in the USS. Additionally or alternatively, dci-Format-v16 may be used to indicate which PDCCH candidates of DCI formats 0_0 and 1_0 or DCI formats 0_1 and 1_1 or DCI formats 0_2 and 1_2 the UE monitors in the USS. Additionally or alternatively, dci-Format-v16 may be used to indicate which PDCCH candidates of DCI formats 0_2 or DCI formats 1_2 the UE monitors in the USS. Additionally or alternatively, the RRC parameter searchSpaceType-v16 may not include an RR.C parameter (e.g., dci-Format-v16). That is, if the USS is configured / provided by the RRC parameter SearchSpace-v16, the UE may implicitly determine to monitor PDCCH candidates of DCI formats 0_2 and / or 1_2 in the USS.

[0134] As an example 304, the RRC parameter SearchSpace-v16 with information element structure B may include the RRC parameter ue-Specific-v16. ue-Specific-v16 is used to configure the search space as a USS set. The RRC parameter SearchSpace-v16 with information element structure B may not include the RRC parameter common for configuring the search space set s as a CSS set. The RRC parameter ue-Specific-v16 may include the RRC parameter formats0-2-And-1-2. The RRC parameter formats0-2-And-1-2 may configure the UE to monitor PDCCH candidates of DCI format 0_2 and DCI format 1_2 in the USS set. Additionally or alternatively, the RRC parameter formats 0-2-And-1-2 may configure the UE to monitor PDCCH candidates of DCI format 0_2 or DCI format 1_2 in the USS set.

[0135] As described in both 302 and 304, the RRC parameter SearchSpace-v16 with information element structure B cannot indicate that the search space set s is a CSS (e.g., a CSS set). The RRC parameter SearchSpace-v16 with information element structure B can indicate that the search space set s is a USS. As described in 202, the RRC parameter SearchSpace with information element structure A can indicate that the search space set s is a CSS (e.g., a CSS set) or a USS (e.g., a USS set).

[0136] Figure 4 is a diagram showing the RRC parameter SearchSpace-v16 having an information element structure C 400 .

[0137] The RRC parameter SearchSpace-v16 with information element structure C is related to the search space configuration. As shown in 402, the RRC parameter SearchSpace-v16 with information element structure C may include the RRC parameter searchSpaceType-v16. The RRC parameters common, ue-Specific, ue-Specific-v16 included in searchSpaceType-v16 may be used to indicate that the search space set s is a CSS set, a USS set A, or a USS set B, respectively. USS set A (ue-Specific) may indicate whether the UE monitor monitors DCI formats 0_0 and 1_0 or DCI formats 0_1 and 1_1 in USS set A. The RRC parameter nrofCandidates-v16, which may be included in SearchSpace-v16 but may not be included in ue-Specific, may provide multiple PDCCH candidates for each CCE aggregation level L of DCI formats 0_0 and 1_0 or DCI formats 0_1 and 1_1. USS set B (ue-Specific-v16) may indicate DCI formats 0_2 and 1_2 that the UE may monitor in the USS set. In addition, ue-Specific-v16 may also include an RRC parameter nrofCandidates-v16, which may provide multiple PDCCH candidates for each CCE aggregation level L of DCI formats 0_2 and 1_2. Therefore, the RRC parameter SearchSpace-v16 with the information element structure C is able to indicate that the search space set is a CSS set, a first USS set (USS set A), or a second USS set (USS set B). The CSS set (common) may indicate that the UE may monitor DCI formats 0_0 and 1_0 in the CSS set.

[0138] According to another example, the RRC parameter searchSpaceType-v16 in 402 may include common or ue-Specific, and may not include ue-Specific-v16. In this case, the RRC parameter dci-Format included in the ue-Specific may indicate whether the UE can monitor PDCCH candidates of DCI format 0 0 and DCI format 10, DCI format 0_1 ​​and DCI format 1_1, or DCI format 0_2 and DCI format 1_2 in the USS set. In addition, in the case where dci-Format indicates that the UE monitors PDCCH candidates of DCI format 0_2 and DCI format 1_2, dci-Format may also include an RRC parameter nrofCandidates-v16, which may provide multiple PDCCH candidates for each CCE aggregation level L of DCI format 0_2 and DCI format 1_2. Otherwise, the RRC parameter nrofCandidates-v16 may not be present in dci-Format.

[0139] The RRC parameters in 302, 304 and 402 such as searchSpaceld, controlResourceSetld, monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, nrofCandidates may have the same usage as those in 202. Some of the above RRC parameters may or may not exist in the RRC parameter SearchSpace-v16.

[0140] The PDCCH may consist of one or more control channel elements (CCEs). A CCE may consist of 6 resource element groups (REGs). A REG may be equal to one resource block during one OFDM symbol. The REGs within a control resource set are numbered in ascending order, starting from the first OFDM symbol and the smallest numbered resource block in the control resource set as 0, in a time-first manner. The UE may be configured with multiple control resource sets. Each control resource set is associated with only one CCE to REG mapping. The CCE to REG mapping of a control resource set may be interleaved or non-interleaved and is described by a REG bundle in [TS 38.211]. The PDCCH is used to transmit downlink control information (DCI) in the case of downlink radio communication (radio communication from a base station to a UE). Here, one or more DCIs (which may be referred to as DCI formats) are defined for the transmission of downlink control information. Information bits are mapped to one or more fields defined in a DCI format. The UE may monitor a PDCCH candidate set in one or more control resource sets (CORESETs) on an active DL BWP on an activated cell. Monitoring means decoding each PDCCH candidate according to the monitored DCI format. The number of CCEs used for PDCCH channel estimation may refer to the number of CCEs of the PDCCH candidates to be monitored. As described above, the PDCCH candidate may be composed of one or more CCEs according to the corresponding CCE aggregation level L. That is, the PDCCH candidate per CCE aggregation level L may be composed of L CCEs. For example, a PDCCH candidate configured for CCE aggregation level 16 may be composed of 16 CCEs.

[0141] The PDCCH candidate set to be monitored by the UE is defined according to the PDCCH search space set. The PDCCH candidates of the search space set s may correspond to the CCE set in the CORESET associated with the search space set s. In the present disclosure, the term "PDCCH search space set" may also refer to "PDCCH search space". In the present disclosure, the term "search space set" may also refer to "search space". The UE monitors the PDCCH candidates in one or more of the search space sets. The search space set may be a common search space (CSS) set or a UE-specific search space (USS) set. In some specific implementations, the CSS set may be shared / configured between multiple UEs. The multiple UEs may search for PDCCH candidates in the CSS set. In some specific implementations, the USS set is configured for a specific UE. The UE may search for one or more PDCCH candidates in the USS set. In some specific implementations, the USS set may be derived from at least the value of the C-RNTI addressed to the UE. In other words, the UE may determine the CCE index of the aggregation level L of the PDCCH candidate corresponding to the USS of the USS set based on the value of the C-RNTI addressed to the UE. The UE may determine the CCE index of aggregation level L corresponding to the PDCCH candidate of the CSS of the CSS set without having the C-RNTI value addressed to the UE.

[0142] The UE may monitor the PDCCH candidate set in one or more of the following search space sets:

[0143] -Type0-PDCCH CSS set, configured via pdcch-ConfigSIB1 in MIB or via searchSpaceSIB1 in PDCCH-ConfigCommon or via searchSpaceZero in PDCCH-ConfigCommon for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG

[0144] -Type0A-PDCCH CSS set, configured via searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI format with CRC scrambled by SI-RNTI on the primary cell of the MCG

[0145] -Type1-PDCCH CSS set, if ra-SearchSpace in PDCCH-ConfigCommon is configured for a DCI format with CRC scrambled by RA-RNTI or TC-RNTI on the primary cell

[0146] -Type2-PDCCH CSS set, configured via pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by the P-RNTI on the primary cell of the MCG

[0147] - Type3-PDCCH CSS set, configured via SearchSpace in PDCCH-Config for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI or TPC-SRS-RNTI (and for primary cell only, with CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI), where searchSpaceType=common, and

[0148] - USS set, configured by SearchSpace in PDCCH-Config as a DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI or CS-RNTI, where searchSpaceType=ue-Specific.

[0149] UE 102 may receive an RRC message including one or more RRC parameters related to the search space configuration from base station 160. UE 102 may determine a PDCCH monitoring opportunity for PDCCH candidates of each search space set s based on the received RRC parameters. UE 102 may monitor the PDCCH candidates of each search space set s in the determined PDCCH monitoring opportunity. As described above, for example, an RRC parameter (e.g., SearchSpace or SearchSpace-v16) may provide search space sets s, k to UE 102. s The PDCCH monitoring periodicity of the time slot is s The PDCCH monitoring offset of the time slot, T s duration, PDCCH monitoring mode within the time slot, etc.

[0150] Figure 6 is a diagram showing one example 600 of how to determine PDCCH monitoring occasions for PDCCH candidates based on received RRC parameters related to a search space configuration.

[0151] exist Figure 6 In the PDCCH monitoring period k s Configured as 6 time slots. PDCCH monitoring offset o s Configured as 2 time slots. Duration T sis configured as 2 time slots. The subcarrier spacing configuration u is configured as 0, which means the subcarrier spacing of the active DL BWP is 15kHz. In this case, u=0, N frame,u slot is equal to 10. That is, when u=0, the number of time slots per frame is 10. u s,f is the number of time slots in a radio frame. That is, n u s,f The value of {0,…,N frame,u slot -1}.

[0152] UE 102 may determine the PDCCH monitoring occasions on the active DL BWP according to the PDCCH monitoring periodicity, PDCCH monitoring offset, and PDCCH monitoring pattern within the time slots of each configured search space set s. u s,f Satisfying formula (1)(n f* N frame,u slot +n u sf -o s )modk s = 0, UE 102 can determine that the PDCCH monitoring opportunity exists at the nth f The frame numbered n u s,f According to equation (1), UE 102 can determine the number n f = 0 in the frame numbered n u sf =2 and n u s,f =8 time slots and numbered n f = 1 in the frame numbered n u sf =4 is a time slot in which there is a PDCCH monitoring opportunity. Assume that T s is configured as 2 time slots, UE 102 can s =2 consecutive time slots monitor the PDCCH candidates of the search space set s, from the determined number n u s,f In other words, UE 102 may not monitor the time slot for the next (k s -T s ) consecutive time slots of the search space set s of PDCCH candidates. Figure 7 As shown, UE 102 may f = 0 in the frame numbered n us,f = 2, 3, 8 and 9 time slots and numbered n f = 1 in the frame numbered n u s,f =4 and 5 are determined as time slots with PDCCH monitoring opportunities. UE 102 may monitor PDCCH candidates of search space set s in the determined time slots configured for PDCCH monitoring. Time slots with PDCCH monitoring opportunities may also refer to time slots configured for PDCCH monitoring.

[0153] In addition, a time slot determined (or configured) for PDCCH monitoring may have one or more PDCCH monitoring opportunities. The PDCCH monitoring mode within a time slot configured for PDCCH monitoring is indicated by a 14-bit string (monitoringSymbolsWithinSlot). Each bit within the 14-bit string may correspond to a symbol within the time slot. The most significant (left) bit (MSB) may represent the first OFDM in the time slot, and the second most significant (left) bit may represent the second OFDM symbol in the time slot, and so on. A bit set to one may identify the first OFDM symbol of a control resource set within the time slot. Figure 6 As shown, a time slot configured for PDCCH monitoring may have two PDCCH monitoring opportunities. The first PDCCH monitoring opportunity may be located on the first consecutive symbol, the second consecutive symbol, and the third consecutive symbol. The second PDCCH monitoring opportunity may be located on the 8th consecutive symbol, the 9th consecutive symbol, and the 10th consecutive symbol. The duration of one PDCCH monitoring opportunity may be the duration of the CORESET associated with the search space set s.

[0154] Figure 6 is an example of how to determine the PDCCH monitoring timing of search space set s. As described above, the base station can configure the UE to have more than one search space set via RRC parameters related to the search space configuration. These search space sets can be associated with the same or different CORESETs. The UE can then determine the PDCCH monitoring timing of the corresponding search space set s based on the received RRC parameters. The PDCCH monitoring timing can be any OFDM symbol of a time slot. Therefore, according to the search space configuration received from the base station, the PDCCH monitoring timing of a search space set may not overlap or partially overlap with the PDCCH monitoring timing of another search space set in terms of OFDM symbols in the time domain.

[0155] A UE supporting URLLC services may support increased PDCCH monitoring capabilities for a base station. A UE supporting increased PDCCH monitoring capabilities may report a combination (X, Y) with a corresponding limit C and / or limit B for the SCS configuration μ. Limit C refers to the maximum number of non-overlapping CCEs used for channel estimation per PDCCH monitoring span per SCS configuration μ. Limit B refers to the maximum number of monitored PDCCH candidates per PDCCH monitoring span per SCS configuration μ. Different combinations (X, Y) may have the same or different numbers of limit C and / or limit B. The same combination (X, Y) with different SCS configurations μ may also have the same or different numbers of limit C and / or limit B. The candidate values ​​of the combination (X, Y) may be (7, 3), (4, 3), or (2, 2). The UE may report a candidate value for the combination (X, Y). In addition, the UE may report a set of candidate values ​​for (X, Y). The candidate value set of (X,Y) can be {(7,3), (4,3) and (7,3), (2,2) and (4,3) and (7,3)}.

[0156] The PDCCH monitoring span is determined based at least on a reported candidate value of (X, Y) or a set of candidate values ​​of (X, Y). There is a minimum time distance of X OFDM symbols between the beginnings of two different PDCCH monitoring spans, including cross-slot boundary conditions. The PDCCH monitoring span has a length of up to Y consecutive OFDM symbols of a time slot. The PDCCH monitoring spans do not overlap. Each PDCCH monitoring span is contained in a single time slot. The same span pattern is repeated in each time slot. The distances between consecutive spans within a time slot and across time slots may not be equal, but all PDCCH monitoring spans must meet the same (X, Y) limit. Each PDCCH monitoring opportunity is completely contained in one PDCCH monitoring span.

[0157] In order to determine the appropriate span pattern, a bitmap b(l) is first generated, 0<=1<=13, where b(l)=1 if the symbol l of any time slot is part of the monitoring opportunity, otherwise b(l)=0. b(l)=1 means that the corresponding symbol l of any time slot is part of the PDCCH monitoring opportunity. Alternatively or additionally, the bitmap b(l) can be generated regardless of the PDCCH monitoring opportunity of the common search space set A. That is, the bitmap b(l) can be generated based on the PDCCH monitoring opportunity of the search space set that does not belong to the common search space set A. The common search space set A may refer to a Type 0-PDCCH CSS set, a Type OA-PDCCH CSS set, a Type 2-PDCCH CSS set, and a Type 1-PDCCH CSS set without a dedicated RRC configuration. In other words, if symbol l is only part of the PDCCH monitoring opportunity for the CSS set in the common search space set A, b(l) can be regarded as b(l)=0.

[0158] The first PDCCH monitoring span in a span pattern starts at the smallest 1 for b(l)=1. The next PDCCH monitoring span in a span pattern starts at the smallest 1 for b(l)=1 that is not included in the previous PDCCH monitoring span. The PDCCH monitoring span duration is max{maximum of all CORESET durations, minimum of Y among the candidate values ​​reported by the UE}, with the possible exception of the last span in a slot which has a shorter duration. Figure 7 is an example showing how to determine the span pattern based on (X,Y) reported by the UE.

[0159] Figure 7 An example 700 of PDCCH monitoring span determination is shown.

[0160] like Figure 7 As depicted in , PDCCH monitoring opportunity 1 (701) of the search space set is associated with a CORESET having a duration of 3 symbols. PDCCH monitoring opportunity 2 (702) of the search space set is associated with a CORESET having a duration of 2 symbols. PDCCH monitoring opportunity 3 (703, 704, 705) of the search space set is associated with a CORESET having a duration of 1 symbol. The UE may indicate an increased PDCCH monitoring capability to support combinations (X, Y) of (2, 2) and (4, 3) and (7, 3). The UE may further report a limit value C and / or a limit value B of the combination (X, Y), respectively. For example, the UE may report a limit value C1 and / or a limit value B1 of the combination (2, 2). The UE may report a limit value C2 and / or a limit value B2 of the combination (4, 3). The UE may report a limit value C3 and / or a limit value B3 of the combination (7, 3).

[0161] exist Figure 7 In the example, the minimum value of Y among the candidate values ​​reported by the UE is 2. Therefore, according to the condition that the PDCCH monitoring span duration is max{the maximum value of all CORESET durations, the minimum value of Y among the candidate values ​​reported by the UE}, the PDCCH monitoring span duration is determined to be 2 except for the last span in the time slot with a shorter duration. Figure 7 For the symbols occupied by the PDCCH monitoring opportunity, the bitmap b(l) with a 14-bit string is generated as {11001000110000}.

[0162] The span pattern is determined based on the bitmap b(l) and the PDCCH monitoring span duration. The first PDCCH monitoring span (706) in the span pattern starts at symbol #0. The second PDCCH monitoring span (707) in the span pattern starts at symbol #4. The third PDCCH monitoring span (708) in the span pattern starts at symbol #8.

[0163] exist Figure 7 , the UE reports C1, C2, and C3 of (2,2), (4,3), and (7,3), respectively. The UE may determine a limit value C from C1, C2, and C3 of the span pattern. First, the UE may calculate the gap distance between two consecutive spans including the cross slot boundary within the span pattern. The gap distance between the first span (706) and the second span (707) is 4 symbols. The gap distance between the second span (707) and the third span (708) is 4 symbols. The gap distance between the last span (third) span (708) and the first span (706) is 6 symbols. Secondly, the UE may select the minimum value of the gap distance. Figure 7 , the minimum value of the gap distance is 4 symbols. Third, the UE may compare the reported X with the minimum value of the gap distance to select one or more applicable limit values ​​C. If the value of the reported X is equal to or less than the minimum value of the gap distance, the UE may regard the limit value C of (X,Y) as the applicable limit value C of the PDCCH monitoring span. That is, the limit value C1 of (2,2) and the limit value C2 of (4,3) are both applicable to the PDCCH monitoring span. In other words, the applicable limit value C set for the PDCCH monitoring span consists of the limit value C1 and the limit value C2. In addition, if its corresponding Y is less than the duration of the PDCCH monitoring span, the UE may or may not remove the limit value C from the applicable limit value C set. In this way, if there is more than one applicable limit value C in the applicable limit value C set, the UE may select a larger number from the applicable limit value C set. The selected limit value C is the same across different PDCCH monitoring spans within a time slot. In addition, the same procedure can be applied to select the limit value B.

[0164] The goal of the increased PDCCH monitoring capability is to enhance the number of PDCCH monitoring opportunities for URLLC and reduce the delay in URLLC service scheduling. Therefore, the increased PDCCH monitoring capability can ensure that the URLLC UE has more frequent opportunities to monitor the DCI format that schedules the URLLC service in a time slot. For each PDCCH monitoring span, the limit C can ensure that the URLLC UE monitors at least one PDCCH candidate. In addition, the reasonable configuration of the limit C (and / or limit B) can help the URLLCUE reduce complexity and power consumption.

[0165] UE 102 may indicate an increased PDCCH monitoring capability to base station 160. Base station 160 may configure UE 102 or schedule UE 102 according to the signaled UE capability. After receiving capability information from UE 102, base station 160 may configure UE 102 to use the increased PDCCH monitoring capability. In this case, UE 102 configured with the increased PDCCH monitoring capability may use the capability to monitor PDCCH candidates. After receiving capability information from UE 102, base station 160 may not configure UE 102 to use the increased PDCCH monitoring capability. In other words, if the UE is configured with an increased PDCCH monitoring capability, the UE may determine the PDCCH candidates to be monitored per PDCCH monitoring span based on span limit C and / or limit B. If the UE is not configured with an increased PDCCH monitoring capability, the UE may determine the PDCCH candidates to be monitored based on the slot-level maximum number of non-overlapping CCEs and / or the slot-level maximum number of monitored PDCCH candidates. The slot-level maximum number of non-overlapping CCEs or the slot-level maximum number of monitored PDCCH candidates in this article may be predefined in the 3GPP specification, and the UE may report the span-level maximum number of non-overlapping CCEs (limit C) or the span-level maximum number of monitored PDCCH candidates (limit B) as capability.

[0166] Alternatively or additionally, the limit value B may be determined based on the slot-level maximum number of monitored PDCCH candidates and the number of spans within a slot. For example, the remaining number of PDCCH candidates (the slot-level maximum number of monitored PDCCH candidates—the number of PDCCH candidates configured for the CSS set in the first duration) may be equally distributed to these spans according to the number of PDCCH monitoring spans within a slot. The limit value B of the PDCCH monitoring span covering the CSS and USS is the sum of the number of PDCCH candidates configured for the CSS set within the PDCCH monitoring span and the distributed remaining number. The limit value B of the PDCCH monitoring span covering only the USS is the distributed remaining number.

[0167] Two PDCCH candidates with different DCI sizes will be counted separately as two monitored PDCCH candidates. Two PDCCH candidates associated with different CORESETs will be counted separately as two monitored PDCCH candidates. Two PDCCH candidates with the same DCI size and the same scrambling code using the same CCE set will be counted as one monitored PDCCH candidate.

[0168] If two CCEs of a PDCCH candidate correspond to different CORESET indices, they are non-overlapping. If two CCEs of a PDCCH candidate correspond to the same CORESET but have different first symbols for receiving the corresponding PDCCH candidates, they are non-overlapping. In other words, in the case where two CCEs overlap but are associated with different CORESETs, the two CCEs are counted as two non-overlapping CCEs. In the case where two CCEs overlap but are associated with the same or different search space sets, and these same or different search space sets have the same PDCCH start symbol associated with the same CORESET, the two CCEs are counted as one non-overlapping CCE. In the case where two CCEs overlap but are associated with the same or different search space sets, and these same or different search space sets have different PDCCH start symbols associated with the same CORESET, the two CCEs are counted as two non-overlapping CCEs. In the case where two CCEs do not overlap, the two CCEs are counted as two non-overlapping CCEs.

[0169] Figure 5 is a flow chart illustrating one specific implementation of a method 500 for determining PDCCH candidates monitored by a UE 102 .

[0170] The UE 102 may receive 502 an RRC message including one or more RRC parameters from the base station 160. The one or more RRC parameters may be used to configure a search space set s, respectively. The one or more RRC parameters providing the search space set configuration define how or where the UE 102 searches for PDCCH candidates.

[0171] UE 102 may determine the PDCCH candidates for monitoring the DCI format in the corresponding CSS set or USS set based on the received RRC parameters. Here, the DCI format to be monitored for the determination (or configuration) of the search space set may be DCI format 0_1 ​​and / or DCI format 1_1. The DCI format to be monitored for the determination (or configuration) of the search space set may be DCI format 0_2 and / or DCI format 1_2. The DCI format to be monitored for the determination (or configuration) of the search space set may be DCI format 0 0 and / or DCI format 1_0.

[0172] At 504, a search space set index s for each configured search space set may be provided to the UE 102. At 504, an association between the search space set s and CORESET p may be provided to the UE 102. At 504, a plurality of PDCCH candidates per CCE aggregation level L for each configured search space set may be provided to the UE 102. At 504, the UE 102 may determine a PDCCH monitoring opportunity for each configured search space set.

[0173] UE 102 may perform 506 to determine the PDCCH candidates to be allocated for monitoring based on the first duration. Depending on whether the UE is configured with an increased PDCCH monitoring capability, the first duration may be a time slot or a monitoring span. UE 102 may determine the PDCCH candidates to be allocated for the search space set monitored per time slot or per monitoring span. Due to the maximum number of non-overlapping CCEs and / or the maximum number of monitored PDCCH candidates, UE 102 may not monitor all PDCCH candidates configured for all search space sets within the first duration. UE 102 may determine the PDCCH candidates to be allocated for monitoring in the first duration until the total number of counted PDCCH candidates to be allocated for monitoring reaches the first number and / or the total number of counted non-overlapping CCEs for monitoring in the first duration reaches the second number. The first number is the maximum number of monitored PDCCH candidates that UE 102 can monitor in the first duration. The second number is the maximum number of non-overlapping CCEs that UE 102 can monitor in the first duration. Herein, if the first duration is determined as a time slot, the first number is the maximum number of time slots of monitored PDCCH candidates per time slot, and the second number is the maximum number of time slots of non-overlapping CCEs per time slot. If the first duration is determined as a PDCCH monitoring span, the first number is the maximum number of spans of monitored PDCCH candidates (e.g., limit value B) and the second number is the maximum number of spans of non-overlapping CCEs (e.g., limit value C).

[0174] Counting PDCCH candidates refers to PDCCH candidates of the search space set to be allocated for monitoring. UE 102 may monitor counted (e.g., allocated) PDCCH candidates in the first duration. UE 102 may not monitor uncounted (e.g., unallocated) PDCCH candidates in the first duration. UE may monitor PDCCH in a search space set with allocated (counted) PDCCH candidates for monitoring in the first duration. UE 102 may not monitor PDCCH in a search space set without allocated (counted) PDCCH candidates for monitoring in the first duration.

[0175] Next, a specific implementation of how to allocate or count the PDCCH candidates for monitoring of a search space set and the number of non-overlapping CCEs for monitoring is shown.

[0176] As described above, the first duration may be a time slot or a PDCCH monitoring span (or monitoring span). In the case where the UE 102 is configured with an increased PDCCH monitoring capability, the first duration may refer to a monitoring span. In this case, the counting of PDCCH candidates and the counting of non-overlapping CCEs may be performed per PDCCH monitoring span. In the case where the UE 102 is not configured with an increased PDCCH monitoring capability, the first duration may refer to a time slot. In this case, the counting of PDCCH candidates and the counting of non-overlapping CCEs may be performed per time slot.

[0177] The maximum number of PDCCH candidates per time slot may be different from the maximum number of PDCCH candidates per monitoring span. The maximum number of non-overlapping CCEs per time slot may be different from the maximum number of non-overlapping CCEs per monitoring span. As described above, the maximum number of monitored PDCCH candidates per time slot may be a predefined value in the 3GPP specification. The maximum number of non-overlapping CCEs per time slot may be a predefined value in the 3GPP specification. The maximum number of PDCCH candidates per monitoring span (limit B) and the maximum number of non-overlapping CCEs per monitoring span (limit C) may be reported separately by UE 102.

[0178] For each time slot or each PDCCH monitoring span, the base station 160 may not configure UE 102 in which the total number of PDCCH candidates configured for all CSS sets and the total number of non-overlapping CCEs configured for all CSS sets exceed the corresponding maximum number. That is, the total number of PDCCH candidates configured for all CSS sets per time slot or per PDCCH monitoring span may be equal to or less than the maximum number of monitored PDCCH candidates per time slot or per PDCCH monitoring span. The total number of non-overlapping CCEs configured for all CSS sets per time slot or per monitoring span may be equal to or less than the maximum number of non-overlapping CCEs per time slot or per PDCCH monitoring span. UE 102 may allocate (count) all PDCCH candidates configured for monitoring for all CCS sets. Therefore, UE 102 may not discard PDCCH candidates configured for monitoring for CSS sets.

[0179] As described above, all PDCCH candidates configured for the CSS set are determined as counted PDCCH candidates for monitoring. Then, UE 102 can determine the PDCCH candidates to be allocated for monitoring for each USS set. Note that before UE 102 starts determining the PDCCH candidates to be allocated for monitoring in the first duration for each USS set, if a CSS set exists in the first duration, the total number of counted PDCCH candidates is set to the number of PDCCH candidates configured for the CSS set. If there is no CSS set in the first duration, the total number of counted PDCCH candidates starts from 0. Similarly, the total number of counted non-overlapping CCEs is set to the number of non-overlapping CCEs required for the PDCCH candidates configured for the CSS set. If there is no CSS set in the first duration, the total number of counted non-overlapping CCEs starts from 0.

[0180] For UE 102 that is not configured with an increased PDCCH monitoring capability, UE 102 may determine the PDCCH candidates allocated for monitoring per time slot. For all USS sets within a time slot, UE 102 may arrange each USS set in a set of USS sets (e.g., set A) in ascending order of the USS set index. The position of the corresponding USS set in a set of USS sets is based on the corresponding USS set index. For example, the USS set with the lowest USS set index may be positioned in the first position of a set of USS sets. The USS set with the largest USS set index may be positioned in the last position of a set of USS sets.

[0181] UE 102 may determine the PDCCH candidates to be allocated for monitoring in the time slot in ascending order of the USS set index configured in the time slot until the total number of counted PDCCH candidates to be allocated for monitoring in the time slot reaches a first number and / or the total number of counted non-overlapping CCEs to be allocated for monitoring in the time slot reaches a second number. The counted non-overlapping CCEs are CCEs required by the corresponding counted PDCCH candidates. In other words, UE 102 may monitor the number of counted PDCCH candidates that require a corresponding number of counted non-overlapping CCEs.

[0182] UE 102 may determine the PDCCH candidates to be allocated for monitoring for each USS according to the order of the USSs in set A in the time slot. For each USS set with a configured search space set index, when counting the number of PDCCH candidates configured for the USS set, the total number of PDCCH candidates counted does not exceed the first number and when counting the number of non-overlapping CCEs configured for the USS set, the total number of non-overlapping CCEs counted does not exceed the second number, the number of PDCCH candidates configured for the USS set is counted as the total number of PDCCH candidates counted, and the number of non-overlapping CCEs configured for the USS set is counted as the total number of non-overlapping CCEs counted. "The number of PDCCH candidates configured for the USS set is counted as the total number of PDCCH candidates counted, and the number of non-overlapping CCEs configured for the USS set is counted as the total number of non-overlapping CCEs counted" means that UE 102 can allocate all the number of PDCCH candidates configured for the USS set for monitoring. That is, in this case, UE 102 can monitor PDCCH in the USS set with the allocated PDCCH candidates for monitoring. In this case, UE 102 may then determine the PDCCH candidates to be allocated for monitoring for a subsequent USS set in a group of USS sets. Here, the number of non-overlapping CCEs configured for a USS set means the number of non-overlapping CCEs required for the number of PDCCH candidates configured for the USS set. The number of non-overlapping CCEs may be further determined based on the CCEs required for the PDCCH candidates that have been allocated for monitoring for all search space sets.

[0183] In any case where the total number of PDCCH candidates counted when counting the number of PDCCH candidates configured for a USS set exceeds a first number or the total number of non-overlapping CCEs counted when counting the number of non-overlapping CCEs configured for a USS set exceeds a second number, the number of PDCCH candidates configured for a USS set is not counted as the total number of PDCCH candidates counted, and the number of non-overlapping CCEs configured for a USS set is not counted as the total number of non-overlapping CCEs counted. "The number of PDCCH candidates configured for a USS set is not counted as the total number of PDCCH candidates counted, and the number of non-overlapping CCEs configured for a USS set is not counted as the total number of non-overlapping CCEs counted" means that the UE 102 may not allocate multiple PDCCH candidates configured for a USS set for monitoring for the USS set. That is, in this case, the UE 102 may not monitor the PDCCH in the USS set because there is no allocated PDCCH candidate for monitoring for the USS set. Furthermore, the UE 102 may not monitor for a subsequent USS set whose location is after the USS set in a group of USS sets to further determine the PDCCH candidates to be allocated.

[0184] Next, a specific implementation of how the UE 102 determines how to count the PDCCH candidates to be allocated for monitoring per PDCCH monitoring span is shown. For a UE 102 configured with an increased PDCCH monitoring capability, the UE 102 may determine the PDCCH candidates to be allocated for monitoring per PDCCH monitoring span. For all USS sets present within the PDCCH monitoring span, the UE 102 may arrange the position of each USS set in a group (a set of USS sets).

[0185] The position order (priority order) of the corresponding USS sets in the group is determined in ascending order of the USS set index. Alternatively or additionally, the position order of the corresponding USS sets in the group can be determined based on RRC information. The RRC information may indicate the position order of each USS set in the group. Alternatively or additionally, the position order of each USS set can be determined first according to the ascending order of the search space set index associated with the first group of search space sets and then according to the ascending order of the search space set index associated with the second group of search space sets. The first group of search space sets are those search space sets in which the PDCCH candidates of DCI format 1_2 / DCI format 0_2 are configured to be monitored. The second group of search space sets are those search space sets in which the PDCCH candidates of DCI formats other than DCI format 1_2 / DCI format 0_2 are configured to be monitored.

[0186] UE 102 may sequentially determine the PDCCH candidates to be allocated for monitoring according to the position order of the groups within the PDCCH monitoring span until the total number of counted PDCCH candidates to be allocated for monitoring in the PDCCH monitoring span reaches a first number and / or the total number of counted non-overlapping CCEs to be allocated for monitoring in the PDCCH monitoring span reaches a second number. The counted non-overlapping CCEs are CCEs required by the corresponding counted PDCCH candidates. In other words, UE 102 may monitor the number of counted PDCCH candidates that require a corresponding number of counted non-overlapping CCEs.

[0187] UE 102 can determine the PDCCH candidates to be allocated for monitoring for each USS set according to the position order of the USS sets in a group of USS sets in the PDCCH monitoring span. For each USS set with a configured search space set index, when counting the number of PDCCH candidates configured for the USS set, the total number of PDCCH candidates counted does not exceed the first number and when counting the number of non-overlapping CCEs configured for the USS set, the total number of non-overlapping CCEs counted does not exceed the second number, the number of PDCCH candidates configured for the USS set is counted as the total number of PDCCH candidates counted, and the number of non-overlapping CCEs configured for the USS set is counted as the total number of non-overlapping CCEs counted. In this case, UE 102 can allocate all the numbers of PDCCH candidates configured for the USS set for monitoring. Next, UE 102 can determine the PDCCH candidates to be allocated for monitoring for the subsequent positions of the USS sets in the group.

[0188] In any case where the total number of counted PDCCH candidates exceeds the first number when counting the number of PDCCH candidates configured for the USS set or the total number of counted non-overlapping CCEs exceeds the second number when counting the number of non-overlapping CCEs configured for the USS set, the number of PDCCH candidates configured for the USS set is not counted as the total number of counted PDCCH candidates, and the number of non-overlapping CCEs configured for the USS set is not counted as the total number of counted non-overlapping CCEs. In this case, the UE 102 may determine the PDCCH candidates to be allocated for monitoring for each aggregation level L of the USS set. In descending order of the value of the aggregation level L, the number of PDCCH candidates per aggregation level L of the USS set is counted as the total number of counted PDCCH candidates and the number of non-overlapping CCEs per aggregation level L of the USS set is counted as the total number of counted non-overlapping CCEs until the total number of counted PDCCH candidates reaches the first number and / or the total number of counted non-overlapping CCEs reaches the second number.

[0189] In other words, in the case where the total number of PDCCH candidates counted does not exceed the first number when counting the number of PDCCH candidates of aggregation level L of the USS set and the total number of non-overlapping CCEs counted does not exceed the second number when counting the number of non-overlapping CCEs configured for aggregation level L of the USS set, the number of PDCCH candidates with aggregation level L configured for the USS set is counted as the total number of counted PDCCH candidates, and the number of corresponding non-overlapping CCEs for the number of PDCCH candidates with aggregation level L configured for the USS set is counted as the total number of counted non-overlapping CCEs. The UE 102 may allocate PDCCH candidates of aggregation level L for the USS set for monitoring. The UE 102 may monitor the PDCCH in the USS set with the allocated PDCCH candidates of aggregation level L for monitoring. However, in any case where the total number of counted PDCCH candidates exceeds the first number when counting the number of PDCCH candidates of aggregation level L for the USS set or the total number of counted non-overlapping CCEs exceeds the second number when counting the number of non-overlapping CCEs configured for aggregation level L for the USS set, the number of PDCCH candidates with aggregation level L configured for the USS set is not counted as the total number of counted PDCCH candidates, and the number of corresponding non-overlapping CCEs for the number of PDCCH candidates with aggregation level L configured for the USS set is not counted as the total number of counted non-overlapping CCEs. In this case, the UE 102 may not monitor the PDCCH candidates with aggregation level L allocated to the USS set.

[0190] Alternatively or additionally, UE 102 may determine the position of a (USS set index, aggregation level (AL) L) combination in the group. The position order of each (USS set index, L) combination in the group may be determined as follows: first, for each search space set, in descending order of the value of the aggregation level L; second, in ascending order of the search space set index. For example, the maximum aggregation level of the USS set with the lowest USS set index may be positioned in the first position in the group. The second maximum aggregation level of the USS set with the lowest USS set index may be positioned in the second position in the group. The USS set with the maximum USS set index may be positioned in the last position of a group of USS sets. In this document, aggregation level L means the aggregation level provided for non-zero numbered PDCCH candidates.

[0191] Then, UE 102 can sequentially determine the PDCCH candidates to be allocated for monitoring in the PDCCH monitoring span corresponding to each (USS set index, L) combination according to the position order of the (USS set index, aggregation level L) combination in the group. For each (USS set index, L) combination in the group, when counting the number of PDCCH candidates corresponding to the (USS set index, L) combination, the total number of PDCCH candidates counted does not exceed the first number and when counting the number of non-overlapping CCEs corresponding to the (USS set index, L) combination, the total number of non-overlapping CCEs counted does not exceed the second number, the number of PDCCH candidates corresponding to the (USS set index, L) combination is counted as the total number of counted PDCCH candidates, and the number of non-overlapping CCEs corresponding to the (USS set index, L) combination is counted as the total number of counted non-overlapping CCEs. In this case, UE 102 can allocate multiple PDCCH candidates corresponding to the (USS set index, L) combination for monitoring for the USS set. Next, UE 102 may determine PDCCH candidates to be allocated for monitoring for subsequent positions of the (USS set index, L) combination in the group.

[0192] In any case where the total number of PDCCH candidates counted when counting the number of PDCCH candidates corresponding to the (USS set index, L) combination exceeds the first number or the total number of non-overlapping CCEs counted when counting the number of non-overlapping CCEs corresponding to the (USS set index, L) combination exceeds the second number, the number of PDCCH candidates corresponding to the (USS set index, L) combination is not counted as the total number of PDCCH candidates counted, and the number of non-overlapping CCEs corresponding to the (USS set index, L) combination is not counted as the total number of non-overlapping CCEs counted. UE 102 may not allocate PDCCH candidates corresponding to the (USS set index, L) combination for monitoring for the USS set. UE 102 may discard (not monitor) PDCCH candidates corresponding to any subsequent position of the (USS set index, L) combination in the group.

[0193] The UE 102 may perform 508 to monitor the allocated PDCCH candidates of the corresponding search space set for the first duration. Based on 506, the allocated PDCCH candidates of the corresponding search space set are determined.

[0194] As described above, for each DL BWP configured to the UE 102 in the serving cell, the UE 102 may receive an RRC message including one or more RRC parameters related to the search space configuration from the base station. RRC parameters related to the search space configuration. The number of search space sets per DL BWP in the serving cell is limited to the number A. In other words, the base station may not configure a number of search space sets greater than the number A for the UE. The UE 102 may indicate support for the ability to count the search space sets having the same PDCCH monitoring opportunity within a time slot as one. That is, the UE 102 may indicate support for the ability that the actual number of configured search space sets may be greater than the number A and may be increased to the number B. In other words, the UE 102 may indicate to the base station 160 that the number of configured search space sets may be greater than the number A in the case where the search space sets have the same PDCCH monitoring opportunity within the time slot. In this case, after receiving the capability reported from the UE 102, the base station 160 may configure a number of search space sets greater than the number A for the UE by configuring the search space sets having the same PDCCH monitoring opportunity within the time slot.

[0195] Search space sets with the same PDCCH monitoring occasion may be associated with the same CORESET.Search space sets with the same PDCCH monitoring occasion may occupy the same symbol within a slot.

[0196] The DCI format (or DCI) may be clarified as DCI format 0_0, DCI format 1_0, DCI format 1_1 (DCI format C), DCI format 0_1 ​​(DCI format D), DCI format 1_2 (DCI format E), DCI format 0_2 (DCI format F), and the like.

[0197] DCI format 1_0 may be used for PDSCH scheduling in one cell. The UE may monitor DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI or P-RNTI or SI-RNTI or RA-RNTI or TC-RNTI. The UE may monitor DCI format 0_0 in a CSS (e.g., a CSS set) or a USS (e.g., a USS set). DCI format 0_0 may be used for PUSCH scheduling in one cell. The UE may monitor DCI format 0_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI or TC-RNTI. The UE may monitor DCI format 0_0 in a CSS (e.g., a CSS set) or a USS (e.g., a USS set).

[0198] In addition, DCI format 1_0 monitored in the CSS may be used for scheduling broadcast data. DCI format 1_0 monitored in the CSS may also be used for scheduling UE-specific data. DCI format 0_0 may be used for scheduling UE-specific data.

[0199] DCI format 0_0 may include predefined fields with fixed bits except for the "frequency domain resource allocation" field. The fields of DCI format 0_0 correspond sequentially to a 1-bit "DCI format identifier" field, a "frequency domain resource allocation" field, a 4-bit "time domain resource allocation" field, a 1-bit "frequency hopping flag" field, a 5-bit "modulation and coding scheme" field, a 1-bit "new data indicator" field, a 2-bit "redundancy version" field, a 4-bit "HARQ process number" field, a 2-bit "TPC command for scheduled PUSCH" field, and a 1-bit "UL / SUL indicator" field. The size of the "frequency domain resource allocation" field of DCI format 0_0 may be determined based on the size of the UL bandwidth portion. For example, the size of the "frequency domain resource allocation" field may be based on the formula (1) ceil(log2(N RB UL,BWP (N RB UL,BWP +1) / 2)) to determine, where N RB UL,BWP is the size of the UL bandwidth portion. Function ceil(x) means a function that takes a real number x as input and gives as output the smallest integer greater than or equal to x.

[0200] DCI format 1_0 may include predefined fields with fixed bits except for the "frequency domain resource allocation" field. The fields of DCI format 1_0 correspond sequentially to a 1-bit "DCI format identifier" field, a "frequency domain resource allocation" field, a 4-bit "time domain resource allocation" field, a 1-bit "VRB to PRB mapping" field, a 5-bit "modulation and coding scheme" field, a 1-bit "new data indicator" field, a 2-bit "redundancy version" field, a 4-bit "HARQ process number" field, a 2-bit "downlink allocation index" field, a 2-bit "TPC command for scheduled PUCCH" field, a 3-bit "PUCCH resource indicator" field, and a 3-bit "PDSCH to HARQ_feedback timing indicator" field. The size of the "frequency domain resource allocation" field of DCI format 1_0 may be determined based on the size of the DL bandwidth portion and / or the size of CORESET 0. For example, the size of the "frequency domain resource allocation" field may be based on formula (2) ceil(log2(N RB UL,BWP (N RB DL,BWP +1) / 2)) to determine, where N RB DL,BWPIt is the size of the UL bandwidth portion or the size of CORESET 0.

[0201] DCI format 0_0 and DCI format 1_0 may be configured to be monitored in a CSS (e.g., a CSS set) or a USS (e.g., a USS set). DCI format 0_0 and DCI format 1_0 monitored in a CSS may also be referred to as a default DCI format. In other words, DCI format 0_0 and DCI format 1_0 monitored in a USS may not be referred to as a default DCI format.

[0202] DCI format C may refer to a DCI format (e.g., DCI format 1_1) monitored in the USS. DCI format C (DCI format 1_1) may be used for PDSCH scheduling in one cell. DCI format 1_1 may schedule up to two transport blocks for one PDSCH. The UE may monitor DCI format 1_1 with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. The UE may monitor DCI format 1_1 in the USS. The UE may not monitor DCI format 1_1 in the CSS. DCI format 1_1 may be used to schedule UE-specific data. DCI format 1_1 may include multiple fields with fixed bits and multiple fields with variable bits. The size of the field with variable bits is determined based on the corresponding RRC configuration.

[0203] DCI format D may refer to a DCI format (e.g., DCI format 0_1) monitored in the USS. DCI format 0_1 ​​may be used for PUSCH scheduling in one cell. DCI format 0_1 ​​may schedule up to two transport blocks for one PUSCH. The UE may monitor DCI format 0_1 ​​with a CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI. The UE may monitor DCI format 0_1 ​​in the USS. The UE may not monitor DCI format 0_1 ​​in the CSS. DCI format 0_1 ​​may be used to schedule UE-specific data. DCI format 0_1 ​​may include multiple fields with fixed bits and multiple fields with variable bits. The size of the field with variable bits is determined based on the corresponding RRC configuration.

[0204] DCI format E may refer to a DCI format monitored in the USS (e.g., DCI format 1_2). DCI format 1_2 may be used for PDSCH scheduling in a cell. DCI format 1_2 may schedule one transport block for one PDSCH. The UE may monitor DCI format 1_2 in the USS. The UE may not monitor DCI format 1_2 in the CSS. DCI format 1_2 may be used to schedule UE-specific data. DCI format 1_2 may include multiple fields with fixed bits and multiple fields with variable bits. The size of the field with variable bits is determined based on the corresponding RRC configuration. DCI format 1_2 may not include some fields (e.g., the "CBG transmission information" field), which may exist in DCI format 1_1.

[0205] DCI format F may refer to a DCI format (e.g., DCI format 0_2) monitored in the USS. DCI format 0_2 may be used to schedule PUSCH in one cell. DCI format 0_2 may schedule one transport block for one PUSCH. In addition, the UE may monitor DCI format F with a CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI. The UE may monitor DCI format 0_2 in the USS. The UE may not monitor DCI format 0_2 in the CSS. DCI format 0_2 may be used to schedule UE-specific data. DCI format 0_2 may include multiple fields with fixed bits and multiple fields with variable bits. The size of the field with variable bits is determined based on the corresponding RRC configuration. DCI format 0_2 may not include some fields (e.g., the "CBG transmission information" field), which may exist in DCI format 0_1.

[0206] DCI formats C and D may be used to schedule traffic service data (e.g., eMBB). For example, DCI format C may be used to schedule the first PDSCH for transmitting eMBB data. DCI format D may be used to schedule the first PUSCH for transmitting eMBB data.

[0207] DCI formats E and F may be used to schedule traffic service data (e.g., URLLC). For example, DCI format E may be used to schedule a second PDSCH for transmitting URLLC data. DCI format F may be used to schedule a second PUSCH for transmitting URLLC data. Additionally or alternatively, DCI formats E and F may be DCI formats with a CRC scrambled by a second RNTI different from the first RNTI used for DCI formats C and D. That is, DCI format E may be DCI format 1_1 with a CRC scrambled by a second RNTI. DCI format C may be DCI format 1_1 with a CRC scrambled by a first RNTI (e.g., C-RNTI). DCI format F may be DCI format 0_1 ​​with a CRC scrambled by a second RNTI. DCI format D may be DCI format 0_1 ​​with a CRC scrambled by a first RNTI (e.g., C-RNTI).

[0208] Additionally or alternatively, DCI formats C and D may be transmitted in a first CORESET, while DCI formats E and F may be transmitted in a second CORESET different from the first CORESET. An RRC parameter for identifying that the DCI format configured by dci-Format is DCI format C and D or DCI format E and F may be present (or set to "enabled") in the CORESET configuration of the second CORESET. The RRC parameter may not exist (or be set to "disabled") in the CORESET configuration of the first CORESET. As described above, a CORESET is associated with a search space set S, where the DCI format is configured to be monitored. For example, dci-Format may indicate monitoring of PDCCH candidates for DCI format 0_1 ​​and DCI format 1_1 in search space set S. If the RRC parameter does not exist in the CORESET configuration of the relevant CORESET, the DCI format 0_1 ​​and DCI format 1_1 monitored in the CORESET may refer to DCI formats C and D. If there is an RRC parameter in the CORESET configuration of the relevant CORESET, the DCI format 0_1 ​​and DCI format 1_1 monitored in the CORESET may refer to DCI formats E and F. That is, DCI formats C and D may be DCI formats 0_1 and DCI format 1_1 monitored in the first CORESET. DCI formats C and D may be DCI formats 0_1 and DCI format 1_1 monitored in the second CORESET.

[0209] Additionally or alternatively, DCI formats C and D may be transmitted in a first search space set S, while DCI formats E and F may be transmitted in a second search space set S that is different from the first search space set S. The RRC parameters for identifying that the DCI formats configured by dci-Format are DCI formats C and D or DCI formats E and F may be present (or set to "enabled") in the ue-Specific (SearchSpace or SearchSpace-v16) of the second search space set S. The RRC parameters may not be present (or set to "disabled") in the ue-Specific (SearchSpace or SearchSpace-v16) of the first search space set S. For example, dci-Format may indicate that PDCCH candidates for monitoring DCI format 0_1 ​​and DCI format 1_1 are monitored. If the RRC parameters do not exist in the ue-Specific of the search space set S, the DCI format 0_1 ​​and DCI format 1_1 monitored in the search space set S may refer to DCI formats C and D. If there is an RRC parameter in the UE-Specific of the search space set s, the DCI format 0_1 ​​and DCI format 1_1 monitored in the search space set s may refer to DCI formats E and F. That is, DCI formats C and D may be DCI formats 0_1 and DCI formats 1_1 configured in the first search space set s. DCI formats E and F may be DCI formats 0_1 and DCI formats 1_1 configured in the second search space set s.

[0210] The DCI (format) used for downlink scheduling is also called a downlink grant or a downlink allocation. The DCI (format) used for uplink scheduling is also called an uplink grant or an uplink allocation.

[0211] Different DCI formats (DCI) may consist of different fields. The fields defined in the DCI format may be mapped to multiple information bits. Each field may be mapped to 0, 1 or more bits of information bits. That is, the field may include 0, 1 or more bits of information bits. In the case where the field is mapped to 0 bits, the UE may determine that the field does not exist in the DCI format. In other words, if the field is mapped to 1 or more bits, the UE may determine that the field exists in the DCI format. In addition, the field may also include 0, 1 or more zero padding bits. If the number of information bits in the DCI format is less than 12 bits, zeros may be appended to the DCI format until the payload size is equal to 12. The DCI format may include multiple fields and 0, 1 or more zero padding bits. The payload size of the DCI format may be equal to the amount of information bits and zero padding bits. For the DCI format, the number of zero padding bits may be 0, 1 or more bits. In this article, the size of the DCI format (DCI format size, DCI size) may refer to the payload size of the DCI format.

[0212] Alternatively or additionally, the size of a DCI format may also refer to the size of information bits of the DCI format.

[0213] Figure 8 Various components that may be used in a UE 802 are shown. Figure 8 The UE 802 described may be based on the combination of Figure 1 802 is implemented by the UE 102 described in the specification. The UE 802 includes a processor 881 that controls the operation of the UE 802. The processor 881 may also be referred to as a central processing unit (CPU). The memory 887 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 883a and data 885a to the processor 881. A portion of the memory 887 may also include a non-volatile random access memory (NVRAM). Instructions 883b and data 885b may also reside in the processor 881. The instructions 883b and / or data 885b loaded into the processor 881 may also include instructions 883a and / or data 885a from the memory 887, which are loaded for execution or processing by the processor 881. The instruction 883b may be executed by the processor 881 to implement one or more of the above-mentioned methods 200.

[0214] The UE 802 may also include a housing that houses one or more transmitters 858 and one or more receivers 820 to allow for transmission and reception of data. The transmitters 858 and receivers 820 may be combined into one or more transceivers 818. One or more antennas 822a-n are attached to the housing and electrically coupled to the transceiver 818.

[0215] The various components of UE 802 are coupled together via a bus system 889 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Figure 8 802 is shown as bus system 889. UE 802 may also include a digital signal processor (DSP) 891 for processing signals. UE 802 may also include a communication interface 893 that provides user access to the functions of UE 802. Figure 8 The UE 802 is shown as a functional block diagram rather than a listing of specific components.

[0216] Fig. 9 Various components that may be utilized in base station 960 are shown. Fig. 9 The base station 960 described may be based on the combination of Figure 1The base station 160 described in the foregoing description is implemented. The base station 960 includes a processor 981 that controls the operation of the base station 960. The processor 981 may also be referred to as a central processing unit (CPU). The memory 987 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 983a and data 985a to the processor 981. A portion of the memory 987 may also include a non-volatile random access memory (NVRAM). The instructions 983b and data 985b may also reside in the processor 981. The instructions 983b and / or data 985b loaded into the processor 981 may also include instructions 983a and / or data 985a from the memory 987, which are loaded for execution or processing by the processor 981. The instructions 983b may be executed by the processor 981 to implement one or more of the above-mentioned methods 300.

[0217] The base station 960 may also include a housing that houses one or more transmitters 917 and one or more receivers 978 to allow transmission and reception of data. The transmitters 917 and receivers 978 may be combined into one or more transceivers 976. One or more antennas 980a-n are attached to the housing and electrically coupled to the transceivers 976.

[0218] The various components of the base station 960 are coupled together via a bus system 989 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the figure. Fig. 9 The base station 960 may also include a digital signal processor (DSP) 991 for processing signals. The base station 960 may also include a communication interface 993 that provides user access to the functions of the base station 960. Fig. 9 The base station 960 is shown as a functional block diagram rather than a listing of specific components.

[0219] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example, and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Optical disks, where magnetic disks usually reproduce data magnetically, optical disks reproduce data optically using lasers.

[0220] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a circuit, a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0221] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with each other and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0222] It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

Claims

1. A user equipment UE, comprising: a transmitting unit configured to send capability information indicating a plurality of combinations (X, Y) for PDCCH monitoring to a base station, wherein each combination (X, Y) is associated with a corresponding maximum number of PDCCH candidates, a span is a number of consecutive OFDM symbols in a time slot that the UE is configured to monitor the PDCCH, and Y is a maximum number of spans that the UE can configure; A receiving unit configured to receive a configuration of a search space set to determine a span set, wherein the search space set includes a CSS set and a USS set; and a control unit configured to determine one or more combinations (X, Y) from the plurality of combinations (X, Y), wherein each X value of the one or more combinations (X, Y) is equal to or less than a value in an interval between every two consecutive spans in the span set; and determining a combination (X, Y) with the largest number of PDCCH candidates from the one or more combinations (X, Y) for PDCCH monitoring, wherein The receiving unit is further configured to: monitor the PDCCH candidates of the CCS set configured in the span for PDCCH monitoring in the span, and Based on the maximum number of PDCCH candidates of the combination (X, Y) of each span and the number of PDCCH candidates of the CSS set configured in the span, it is determined whether to monitor the PDCCH candidates of the USS set configured in the span.

2. The UE according to claim 1, wherein: The same combination (X, Y) with different subcarrier spacing SCS configurations is associated with different maximum numbers of PDCCH candidates.

3. A base station, comprising: A receiving unit configured to receive capability information indicating a plurality of combinations (X, Y) for PDCCH monitoring from a user equipment UE, wherein each combination (X, Y) is associated with a corresponding maximum number of PDCCH candidates, a span is the number of consecutive OFDM symbols in a time slot that the UE is configured to monitor the PDCCH, and Y is the maximum number of spans that the UE can configure; A transmitting unit configured to send a configuration of a search space set to determine a span set, wherein the search space set includes a CSS set and a USS set; a control unit configured to determine one or more combinations (X, Y) from the plurality of combinations (X, Y), wherein each X value of the one or more combinations (X, Y) is equal to or less than a value in an interval between every two consecutive spans in the span set; and determining a combination (X, Y) with the largest number of PDCCH candidates from the one or more combinations (X, Y) for PDCCH monitoring, wherein The transmitting unit is further configured to: for PDCCH monitoring in a span, send a PDCCH candidate of a CCS set configured in the span, and Based on the maximum number of PDCCH candidates of the combination (X, Y) of each span and the number of PDCCH candidates of the CSS set configured in the span, it is determined whether to transmit the PDCCH candidates of the USS set configured in the span.

4. The base station according to claim 3, wherein: The same combination (X, Y) with different subcarrier spacing SCS configurations are associated with different maximum numbers of PDCCH candidates.

5. A method of a user equipment UE, the method comprising: Send capability information indicating a plurality of combinations (X, Y) for PDCCH monitoring to the base station, wherein each combination (X, Y) is associated with a corresponding maximum number of PDCCH candidates, the span is the number of consecutive OFDM symbols in a time slot that the UE is configured to monitor PDCCH, and Y is the maximum number of spans that the UE can configure; receiving a configuration of a search space set to determine a span set, the search space set comprising a CSS set and a USS set; Determine one or more combinations (X, Y) from the plurality of combinations (X, Y), wherein each X value of the one or more combinations (X, Y) is equal to or less than a value in an interval between every two consecutive spans in the span set; Determine a combination (X, Y) having a maximum number of PDCCH candidates from the one or more combinations (X, Y) for PDCCH monitoring; For PDCCH monitoring in a span, monitoring PDCCH candidates of a CCS set configured in the span; and Based on the maximum number of PDCCH candidates of the combination (X, Y) of each span and the number of PDCCH candidates of the CSS set configured in the span, it is determined whether to monitor the PDCCH candidates of the USS set configured in the span.