PDCCH monitoring span and DCI format set determination

Abstract

Embodiments of user equipment (UE) and communication methods are generally described herein. The UE may receive control signaling to configure one or more control resource sets (CORESETs). The CORESET may be configured to span a variable number of resource blocks (RBs) in the frequency domain. The CORESET may be configured to span a variable number of orthogonal frequency division multiplexing (OFDM) symbols in the time domain. Each CORESET may be allocated for reception of one or more physical downlink control channels (PDCCHs). The UE may determine the duration of a PDCCH monitoring span, which may indicate the number of consecutive OFDM symbols in which the UE is to monitor the PDCCH. The UE may determine the duration of the PDCCH monitoring span to be equal to the maximum value of the number of OFDM symbols spanned by the CORESET.

Description

[0001] Priority declaration

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 742,137 filed on October 5, 2018 and U.S. Provisional Patent Application No. 62 / 826,892 filed on March 29, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments relate to wireless communications. Some embodiments relate to wireless networks including 3GPP (3rd Generation Partnership Project) networks and 3GPP LTE (Long Term Evolution) networks, fifth generation (5G) networks, and / or new radio (NR) networks. Some embodiments relate to physical downlink control channels (PDCCH). Some embodiments relate to downlink control information (DCI) formats. Some embodiments relate to determining a set of PDCCH monitoring spans and DCI formats in an NR system. Background Art

[0004] Efficient utilization of the resources of a wireless network is important for providing bandwidth and acceptable response times for users of the wireless network. However, there are often many devices trying to share the same resources, and some devices may be limited by the communication protocols they use or by the bandwidth of their hardware. In addition, wireless devices may need to operate using both newer protocols and legacy device protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1A is a functional diagram of an example network according to some embodiments;

[0006] Figure 1B is a functional diagram of another example network according to some embodiments;

[0007] Figure 2 shows a block diagram of an example machine according to some embodiments;

[0008] Figure 3 Exemplary communication circuitry according to some aspects is shown; and

[0009] Figure 4 The operation of a communication method according to some embodiments is shown. DETAILED DESCRIPTION

[0010] The following description and the accompanying drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process and other changes. Portions and features of some embodiments may be included in or replace portions and features of other embodiments. The embodiments set forth in the claims encompass all available equivalents of those claims.

[0011] Figure 1A is a functional diagram of an example network according to some embodiments. Figure 1B is a functional diagram of another example network according to some embodiments. In references herein, "FIG. 1" may include Figure 1A and Figure 1B In some embodiments, network 100 may be a 3rd Generation Partnership Project (3GPP) network. In some embodiments, network 150 may be a 3GPP network, a New Radio (NR) network, and / or a fifth generation (5G) network. Other networks may be used in some embodiments. In some embodiments, the network may include one or more of the following: Figure 1A one or more components shown; Figure 1B One or more components shown; and one or more additional components. Some embodiments may not necessarily include Figure 1A and Figure 1B All components shown.

[0012] The network 100 may include a radio access network (RAN) 101 and a core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together via an S1 interface 115. For convenience and brevity, only the core network 120 and a portion of the RAN 101 are shown. In some embodiments, the RAN 101 may include one or more of the following: one or more components in an evolved universal terrestrial radio access network (E-EUTRAN), one or more components in a NR network, and / or one or more other components.

[0013] The core network 120 may include a mobility management entity (MME) 122, a serving gateway (serving GW) 124, and a packet data network gateway (PDN GW) 126. In some embodiments, the networks 100, 150 may include (and / or support) one or more evolved Node Bs (eNBs) 104 and / or one or more next generation Node Bs (gNBs) 105. The eNBs 104 and / or gNBs 105 may operate as base stations for communicating with user equipment (UE) 102. In some embodiments, one or more eNBs 104 may be configured to operate as gNBs 105. Embodiments are not limited to Figure 1A The number of eNBs 104 shown in Figure 1B The number of gNBs 105 shown is not limited to Figure 1A Connectivity of the components shown in .

[0014] It should be noted that references herein to eNB 104 or gNB 105 are not limiting. In some embodiments, one or more operations, methods, and / or techniques (such as those described herein) may be practiced by a base station component (and / or other components), including but not limited to gNB 105, eNB 104, serving cell, transmit reception point (TRP), etc. In some embodiments, the base station component may be configured to operate in accordance with one or more of the following: 3GPP LTE protocols / standards, NR protocols / standards, fifth generation (5G) protocols / standards, and / or other protocols / standards, but the scope of the embodiments is not limited in this respect.

[0015] The description herein of one or more operations, techniques and / or methods practiced by a component (e.g., UE 102, eNB 104, gNB 105, etc.) is not limiting. In some embodiments, one or more of those operations, techniques and / or methods may be practiced by another component.

[0016] The MME 122 manages mobility aspects in access such as gateway selection and tracking area list management. The Serving GW 124 terminates the interface towards the RAN 101 and routes data packets between the RAN 101 and the core network 120. In addition, it can be a local mobility anchor for inter-eNB handovers and can also provide an anchor for inter-3GPP mobility handovers. The Serving GW 124 and the MME 122 can be implemented in one physical node or in separate physical nodes.

[0017] In some embodiments, UE 102, eNB 104 and / or gNB 105 may be configured to communicate orthogonal frequency division multiplexing (OFDM) communication signals over a multi-carrier communication channel in accordance with an orthogonal frequency division multiple access (OFDMA) communication technique.

[0018] In some embodiments, network 150 may include one or more components configured to operate in accordance with one or more 3GPP standards including, but not limited to, NR standards. Figure 1BThe illustrated network 150 may include a next generation RAN (NG-RAN) 155, which may include one or more gNBs 105. In some embodiments, the network 150 may include an E-UTRAN 160, which may include one or more eNBs. The E-UTRAN 160 may be similar to the RAN 101 described herein, but the scope of the embodiments is not limited in this respect.

[0019] In some embodiments, network 150 may include an MME 165 that may be similar to MME 122 described herein, but the scope of the embodiments is not limited in this respect. In some embodiments, network 150 may include an SGW 170 that may be similar to SGW 124 described herein, but the scope of the embodiments is not limited in this respect.

[0020] The embodiments are not limited to Figure 1B The embodiments are not limited to the number or type of components shown. Figure 1B Connectivity of the components shown in .

[0021] As used herein, the term "circuitry" may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or processor group) and / or memory (shared, dedicated, or memory group) executing one or more software or firmware programs, a combinational logic circuit, and / or other appropriate hardware components that provide the described functions. In some embodiments, the circuitry may be implemented with one or more software or firmware modules, or the functions associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, the circuitry may include logic that is at least partially operable in hardware. The embodiments described herein may be implemented into a system using any appropriately configured hardware and / or software.

[0022] Figure 2A block diagram of an example machine according to some embodiments is illustrated. Machine 200 is an example machine on which any one or more of the techniques and / or methodologies discussed herein may be executed. In alternative embodiments, machine 200 may operate as a standalone device, or may be connected (e.g., networked) to other machines. Machine 200 may be a UE 102, an eNB 104, a gNB 105, an access point (AP), a station (STA), a user, a device, a mobile device, a base station, another device, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be taken by the machine. In addition, although only a single machine is illustrated, the term "machine" should also be understood to include any collection of machines that individually or jointly execute a collection (or multiple collections) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0023] The examples described herein may include or may operate on logic or a number of components, modules, or mechanisms.

[0024] The machine (e.g., computer system) 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interconnect (e.g., a bus) 208. The machine 200 may further include one or more of 210-228.

[0025] The storage device 216 may include a machine-readable medium 222 having stored thereon one or more sets of data structures or instructions 224 (e.g., software) embodied or utilized by any one or more of the techniques or functionality described herein. The instructions 224 may also reside, in whole or in part, within the main memory 204, within the static memory 206, or within the hardware processor 202 during execution of the instructions 224 by the machine 200. In an example, one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the storage device 216 may constitute a machine-readable medium. In some embodiments, the machine-readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine-readable medium may be or may include a computer-readable storage medium.

[0026] Although the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224. The term "machine-readable medium" may include any medium that is capable of storing, encoding, or carrying instructions, or capable of storing, encoding, or carrying data structures used by or associated with the instructions, which are used for the machine 200 to execute and cause the machine 200 to perform any one or more of the techniques of the present disclosure. Non-limiting machine-readable medium examples may include solid-state memory and optical and magnetic media. Specific examples of machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the machine-readable medium may include non-transitory machine-readable media. In some examples, machine-readable media may include machine-readable media that is not a transitory propagating signal.

[0027] Instructions 224 may also be sent or received over a communication network 226 using a transmission medium via the network interface device 220 using any of a number of transmission protocols. In an example, a network interface such as 220 may include multiple antennas to communicate wirelessly using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. In some examples, a network interface such as 220 may communicate wirelessly using multi-user MIMO technology. The term "transmission medium" should be taken to include any intangible medium capable of storing, encoding, or carrying instructions for execution by the machine 200, and includes digital or analog communication signals or other intangible media to facilitate the communication of such software.

[0028] Figure 3An exemplary communication circuit according to some aspects is shown. It should be noted that in some aspects, devices such as UE 102, eNB 104, gNB 105, machine 200 and / or other devices may include one or more components in the communication circuit system 300. The communication circuit system 300 may include a protocol processing circuit system 305, which may implement one or more of the following items: media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and non-access stratum (NAS) functions. The communication circuit system 300 may also include a digital baseband circuit 310, which may implement one or more physical layer (PHY) functions. The communication circuit system 300 may also include a transmit circuit system 315, a receive circuit system 320 and / or an antenna array circuit system 330. The communication circuit system 300 may also include a radio frequency (RF) circuit system 325. In one aspect of the present disclosure, the RF circuit system 325 may include multiple parallel RF chains for one or more transmit or receive functions, each RF chain connected to one or more antennas in the antenna array 330.

[0029] In some embodiments, the processing circuit system may perform one or more operations described herein and / or (one or more) other operations. In a non-limiting example, the processing circuit system may include one or more components, such as processor 202, protocol processing circuit system 305, digital baseband circuit system 310, (one or more) similar components, and / or (one or more) other components.

[0030] In some embodiments, the transceiver may transmit one or more elements (including but not limited to those described herein) and / or receive one or more elements (including but not limited to those described herein). In a non-limiting example, the transceiver may include one or more components, such as transmit circuitry 315, receive circuitry 320, radio frequency circuitry 325, similar component(s), and / or other component(s).

[0031] Although the UE 102, eNB 104, gNB 105, machine 200 and / or other devices described herein may be respectively illustrated as elements having several separate functions, one or more functional elements may be combined together and may be implemented by a combination of software-configured elements, such as a processing element including a digital signal processor (DSP), one or more microprocessors, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), and a combination of various hardware and logic circuit systems for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes running on one or more processing elements.

[0032] Embodiments may be implemented in one or a combination of hardware, firmware, and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transient mechanism for storing information in a machine (e.g., computer) readable form. For example, a computer-readable storage device may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium, an optical storage medium, a flash memory device, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0033] It should be noted that in some embodiments, UE 102, eNB 104, gNB 105, machine 200 and / or other devices may include Figures 2 to 3 The various components shown, and / or other components. Thus, the techniques and operations described herein as being performed by a device may, in some embodiments, be performed by means of a device.

[0034] In accordance with some embodiments, UE 102 may receive control signaling configuring one or more control resource sets (CORESETs) from gNB 105. A CORESET may be configured to span a variable number of resource blocks (RBs) in the frequency domain. A CORESET may be configured to span a variable number of orthogonal frequency division multiplexing (OFDM) symbols in the time domain. Each CORESET may be allocated for receiving one or more physical downlink control channels (PDCCHs). UE 102 may determine a duration of a PDCCH monitoring span. The PDCCH monitoring span may indicate the number of consecutive OFDM symbols in which UE 102 is to monitor the PDCCH. UE 102 may determine the duration of the PDCCH monitoring span to be equal to a maximum value of the number of OFDM symbols spanned by the CORESET. These embodiments are described in more detail below.

[0035] Figure 4 The operation of the communication method according to some embodiments is shown. Figure 4 Embodiments of method 400 may include additional or even fewer operations or processes than those shown in FIG. Embodiments of method 400 are not necessarily limited to Figure 4 The time sequence shown in .

[0036] In some embodiments, UE 102 may perform one or more operations of method 400, but embodiments are not limited to the execution of method 400 and / or the operations thereof by UE 102. In some embodiments, devices and / or components (including but not limited to UE 102, gNB 105 and / or eNB 104) may perform one or more operations that may be the same, similar, opposite and / or related to the operations of method 400.

[0037] Discussion of various operations, techniques, and / or concepts with respect to one method described herein (e.g., method 400 and / or other methods) may be applicable to other operations described herein and / or other methods described herein. One or more of the techniques, operations, and / or methods described herein may be performed by devices other than the eNB 104, gNB 105, and UE 102, including but not limited to Wi-Fi access points (APs), stations (STAs), and the like.

[0038] In some embodiments, an apparatus of a device (including but not limited to UE 102, eNB 104, gNB 105, etc.) may include a memory configurable to store one or more elements, and the apparatus may use them to perform one or more operations. The apparatus may include a processing circuit system that may perform one or more operations (including but not limited to the operations of method 400 and / or other methods described herein). The processing circuit system may include a baseband processor. The baseband circuit system and / or the processing circuit system may perform one or more operations described herein. The apparatus may include a transceiver for sending and / or receiving one or more blocks, messages, and / or other elements.

[0039] Embodiments are not limited to references herein to the transmission, reception and / or exchange of elements such as frames, messages, requests, indicators, signals or other elements. In some embodiments, such elements can be generated, encoded or otherwise processed by processing circuitry to be transmitted by a transceiver or other component box. In some embodiments, such elements can be received by a transceiver or other component and can be decoded, detected or otherwise processed by processing circuitry. In some embodiments, processing circuitry and transceiver can be included in the same device. In some embodiments, a transceiver can be separated from the manufacture including processing circuitry.

[0040] One or more elements described herein (e.g., messages, operations, etc.) may be included in 3GPP protocols, 3GPP LTE protocols, 4G protocols, 5G protocols, NR protocols, and / or other protocols, but the embodiments are not limited to the use of those elements. In some embodiments, other elements may be used, including other elements in the same standard / protocol, other elements in another standard / protocol, etc. In addition, the scope of the embodiments is not limited to the use of elements included in the standard.

[0041] In some embodiments, UE 102, eNB 104 and / or gNB 105 may be arranged to operate according to 3GPP protocols, NR protocols and / or other protocols.

[0042] At operation 405, UE 102 may exchange control signaling with gNB 105. It should be noted that in some embodiments, multiple instances of control signaling may be exchanged. In some embodiments, the exchange of control signaling may include one or more of: sending one or more elements (e.g., signaling, messages, etc.) by UE 102, sending one or more elements by UE 102 to gNB 105, receiving one or more elements by UE 102, receiving one or more elements by UE 102 from gNB 105, etc. In some embodiments, the control signaling may include multiple messages, multiple signaling instances, multiple types of signaling, multiple elements, etc.

[0043] In some embodiments, UE 102 may receive control signaling from gNB 105 and / or other components that configures one or more control resource sets (CORESETs). In some embodiments, the control signaling may include one or more additional elements.

[0044] In some embodiments, the CORESET may be configured for variable sizes in the frequency domain and / or time domain. In a non-limiting example, the CORESET may be configured to span one or more of the following: a variable number of resource blocks (RBs) in the frequency domain, a variable number of orthogonal frequency division multiplexing (OFDM) symbols in the time domain, etc. Embodiments are not limited to the example units (RBs and OFDM symbols) given above, but any suitable units of frequency and time may be used.

[0045] In some embodiments, the control signaling may indicate one or more of the following for each CORESET: the number of RBs spanned by the CORESET, the number of OFDM symbols spanned by the CORESET, etc. In some embodiments, the RBs of each CORESET may be non-overlapping. In some embodiments, the number of RBs of each CORESET is less than the total number of RBs of the channels allocated to the CORESET.

[0046] In some embodiments, each CORESET may be allocated for one or more physical downlink control channels (PDCCHs), although the scope of the embodiments is not limited in this respect. In some embodiments, each CORESET may be allocated for reception of one or more PDCCHs, although the scope of the embodiments is not limited in this respect.

[0047] At operation 410, UE 102 may determine a physical downlink control channel (PDCCH) monitoring span. In some embodiments, UE 102 may determine a duration of the PDCCH monitoring span. In some embodiments, the PDCCH monitoring span may indicate the number of consecutive OFDM symbols in which UE 102 is to monitor at least one PDCCH. Various techniques may be used to determine the PDCCH monitoring span.

[0048] In some embodiments, the UE 102 may determine the duration of the PDCCH monitoring span to be equal to the maximum value of the number of OFDM symbols spanned by each CORESET. For example, each CORESET may span multiple OFDM symbols (where one or more of those numbers may be the same, and one or more of those numbers may be different). Among the number of OFDM symbols spanned by each CORESET (for all CORESETs), the UE 102 may select the maximum value as the duration of the PDCCH monitoring span. In some embodiments, the UE 102 may determine the duration of the PDCCH monitoring span to be the maximum number of OFDM symbols spanned by any one CORESET.

[0049] In some embodiments, a PDCCH monitoring span may occur within a subframe comprising two slots, although embodiments are not limited to two slots per subframe.In some embodiments, a PDCCH monitoring span may include consecutive OFDM symbols that do not straddle a slot boundary between two slots of a subframe.

[0050] In some embodiments, UE 102 may receive UE capability signaling (and / or other signaling) from gNB 105 indicating the duration of the PDCCH monitoring span. In a non-limiting example, the indication may be expressed in terms of the number of OFDM symbols during which UE 102 is to monitor the CORESET for at least one PDCCH. Embodiments are not limited to the indication of the number of OFDM symbols, as other time units may be used in some embodiments.

[0051] In a non-limiting example, the duration of the PDCCH monitoring span may be based on the duration indicated by the UE capability report indicating support for a feature group (FG), where the FG is one of the following: a FG of format 3-5 (corresponding to the capability indication parameter pdcch-MonitoringAnyOccasions) and a FG of format 3-5b (corresponding to the capability indication parameter pdcch-MonitoringAnyOccasionsWithSpanGap). Embodiments are not limited to these FG formats, as one or more other FG formats may be used in some embodiments. In some embodiments, the FG of format 3-5 may be based on a type 1 common search space (CSS), a type 3 CSS, or a UE search space (UE-SS) with a dedicated radio resource control (RRC) configuration. In some embodiments, the monitoring opportunity may be any OFDM symbol of a time slot. In some embodiments, the FG of format 3-5b may be based on a type 1 CSS, a type 3 CSS, or a UE-SS with a dedicated RRC configuration. In some embodiments, the monitoring opportunity is any OFDM symbol of a time slot and is based on a span gap.

[0052] It should be noted that the duration of the PDCCH monitoring span in the above example may be included in UE capability signaling and / or other signaling, although the scope of the embodiments is not limited in this respect. In some embodiments, another technique (including but not limited to the techniques described herein) may be used to determine the duration.

[0053] In some embodiments, the PDCCH monitoring span may indicate the number of consecutive OFDM symbols that the UE 102 is to monitor for at least one PDCCH. The UE 102 may determine the duration of the PDCCH monitoring span as the number of OFDM symbols that ensures a span gap including an OFDM symbol. In some embodiments, the span gap may be based on a gap of OFDM symbols between two spans including a PDCCH monitoring opportunity. In some embodiments, among the two PDCCH monitoring opportunities, at least one PDCCH monitoring opportunity is not a monitoring opportunity of feature group (FG) #3-1, which defines a mandatory UE capability for PDCCH monitoring. In some embodiments, the monitoring opportunity of FG#3-1 may include a monitoring opportunity in a span of type A or a span of type B.

[0054] In some embodiments, the monitoring opportunity for a span of type A may be within the first three symbols of a slot. In some embodiments, the monitoring opportunity for a span of type A may start at the first symbol of the slot in which the PDCCH is to be monitored. The PDCCH to be monitored may be used for one of the following: a type 1 common search space (CSS), a type 3 CSS, and a UE search space (UE-SS) with a dedicated radio resource control (RRC) configuration.

[0055] In some embodiments, the monitoring opportunity of the span of type B may be within three consecutive OFDM symbols. In some embodiments, the monitoring opportunity of the span of type B may start at the first symbol of the slot in which the PDCCH of type 0, type 0A or type 2 CSS is to be monitored.

[0056] At operation 415, UE 102 may determine one or more sets of downlink control information (DCI) formats. In some embodiments, UE 102 may determine one or more sets of DCI formats. In some embodiments, UE 102 may determine one or more sets of DCI formats that UE 102 is to attempt to decode, store, and process from among the PDCCHs detected during the PDCCH monitoring span. In some embodiments, for each of the one or more sets of DCI formats, a maximum limit on the number of such DCI formats that the UE may expect to receive within the monitoring span is specified. Here, a DCI format may also be referred to as a "valid DCI format" or a "consistent DCI format" or a "PDCCH with consistent control information," etc., implying that this refers to a dedicated DCI format that UE 102 may consider in transmitting consistent layer 1 control information and may need to act upon receiving such control information.

[0057] In some embodiments, UE 102 may restrict one or more sets of DCI formats to: a DCI format for scheduling a unicast physical downlink shared channel (PDSCH) and a DCI format for scheduling a physical uplink shared channel (PUSCH). In some embodiments, one or more sets of DCI formats may include: a DCI format for scheduling a unicast physical downlink shared channel (PDSCH) and a DCI format for scheduling a physical uplink shared channel (PUSCH).

[0058] In some embodiments, UE 102 may restrict one or more sets of DCI formats to: a DCI format for scheduling a unicast physical downlink shared channel (PDSCH), and a DCI format for scheduling a physical uplink shared channel (PUSCH), where the corresponding PDCCH carries a cyclic redundancy check (CRC) scrambled with a radio network temporary identifier (RNTI), which is one of the following: a cell RNTI (C-RNTI); a configured scheduling (CS) RNTI (CS-RNTI), if a CS-RNTI is configured; or a modulation and coding scheme (MCS) cell RNTI (MCS-C-RNTI), if a MCS-C-RNTI is configured. Embodiments are not limited to the above RNTIs, as any suitable RNTI may be used.

[0059] In some embodiments, one or more sets of DCI formats may include: a DCI format for scheduling a unicast physical downlink shared channel (PDSCH), and a DCI format for scheduling a physical uplink shared channel (PUSCH), and wherein the corresponding PDCCH carries a cyclic redundancy check (CRC) scrambled by an RNTI, the RNTI being one of the following: a cell RNTI (C-RNTI); a configured scheduling (CS) RNTI (CS-RNTI), if a CS-RNTI is configured; or a modulation and coding scheme (MCS) cell RNTI (MCS-C-RNTI), if a MCS-C-RNTI is configured. Embodiments are not limited to the above RNTIs, as any suitable RNTI may be used.

[0060] In some embodiments, one or more sets of DCI formats may include a DCI format that triggers uplink (UL) transmission or unicast downlink (DL) reception.

[0061] At operation 420, the UE 102 may monitor one or more control resource sets (CORESETs) for the PDCCH. At operation 425, the UE 102 may attempt to decode a DCI format from one or more sets of DCI formats.

[0062] In some embodiments, UE 102 may monitor the CORESET for the PDCCH during the PDCCH monitoring span. In some embodiments, UE 102 may monitor the CORESET for at least one PDCCH during the PDCCH monitoring span. Embodiments are not limited to the performance of the above operations during the PDCCH monitoring span.

[0063] In some embodiments, if one or more PDCCHs are detected, the UE 102 may: attempt to decode a DCI format in the determined set of DCI formats within the detected PDCCH. In some embodiments, if at least one PDCCH is detected, the UE 102 may attempt to decode a DCI format in the determined set of DCI formats. Embodiments are not limited to attempting to decode a DCI format in the set of DCI formats, as in some embodiments, the UE 102 may attempt to decode other DCI formats and / or other elements.

[0064] In some embodiments, upon receiving one or more sets of DCI formats via a decoded PDCCH during a PDCCH monitoring span, the UE 102 may determine one or more sets of DCI formats to be stored and processed by the UE 102. The UE 102 may monitor the CORESET for the PDCCH during the PDCCH monitoring span. If one or more PDCCHs are decoded, the UE 102 may store and process a DCI format in the one or more sets of determined DCI formats within the decoded PDCCH.

[0065] In some embodiments, for each of the one or more sets of DCI formats, a maximum limit on the number of DCI formats for each set of DCI formats may be predefined. In some embodiments, a maximum limit on the number of DCI formats may be predefined for each of the one or more sets of DCI formats. For example, the maximum limit may be included in a standard such as a 3GPP standard, an NR standard, a 5G standard, and / or other standards.

[0066] In some embodiments, the UE 102 may determine and / or receive control signaling that indicates, for each of one or more sets of DCI formats, a maximum limit on the number of DCI formats for each set of DCI formats. In some embodiments, the maximum limit on the number of DCI formats for each set of DCI formats (and / or related information) may be one or more of the following: part of a criterion received (at least in part) in control signaling, determined (at least in part) by the UE 102, and / or otherwise. In a non-limiting example, the UE 102 may determine a first set of DCI formats that includes DCI formats for scheduling unicast PDSCH based on a first maximum limit on the number of DCI formats for each set of DCI formats. The UE 102 may determine a second set of DCI formats that includes DCI formats for scheduling PUSCH based on a second maximum limit on the number of DCI formats for each set of DCI formats.

[0067] In some embodiments, the PDCCH monitoring span may occur within a subframe comprising a plurality of time slots. The number of time slots may be based at least in part on a subcarrier spacing (SCS) of a downlink bandwidth part (BWP). The PDCCH monitoring span may include consecutive OFDM symbols that do not span a time slot boundary between any two consecutive time slots of the subframe.

[0068] In some embodiments, the PDCCH monitoring span may occur within a subframe comprising a plurality of time slots. In a non-limiting example, the number of time slots may be determined by a number such as in the 3GPP standard and / or the NR standard. , but other parameters may be used. In some embodiments, the parameters It may be defined in Table 4.3.2-1 of TS 38.211 v15.6.0, but the scope of the embodiments is not limited in this regard. In some embodiments, the parameter μ may indicate a subcarrier spacing (SCS) in a DL bandwidth part (BWP), but the scope of the embodiments is not limited in this regard.

[0069] In some embodiments, the duration of the PDCCH monitoring span can be a function of the PDCCH monitoring duration "Y" corresponding to the span gap value "X", as indicated by a UE capability report indicating support for a feature group (FG) of format 3-5b (corresponding to a capability indication parameter pdcch-MonitoringAnyOccasionsWithSpanGap) for monitoring PDCCH candidates belonging to a type 1 CSS, type 3 CSS, or UE-SS with a dedicated RRC configuration, where the monitoring occasion is any OFDM symbol of a timeslot and is based on the span gap.

[0070] In some embodiments, the UE 102 may determine the duration of the PDCCH monitoring span as the number of OFDM symbols as the PDCCH monitoring duration corresponding to the span gap value as indicated by the UE capability report using the pdcch-MonitoringAnyOccasionsWithSpanGap parameter, and the maximum duration of all CORESETs for which the UE 102 is configured for PDCCH monitoring. In some embodiments, among two PDCCH monitoring occasions, at least one PDCCH monitoring occasion is not a monitoring occasion belonging to a monitoring span of type A or type B. The monitoring occasion of the span of type A may be within the first three symbols of a timeslot. The monitoring occasion of the span of type A may start at the first symbol of a timeslot in which the PDCCH is to be monitored, wherein the PDCCH to be monitored is for one of the following: a type 1 common search space (CSS), a type 3 CSS, and a UE search space (UE-SS) with a dedicated radio resource control (RRC) configuration. The monitoring opportunity of the span of type B may be within three consecutive OFDM symbols, wherein the monitoring opportunity of the span of type B may start at the first symbol of the slot in which the PDCCH of type 0, type 0A or type 2 CSS is to be monitored.

[0071] It should be noted that the description below (and elsewhere in this article) may illustrate some or all of the concepts and techniques described herein in some cases. However, the scope of the embodiments is not limited by such description. For example, the embodiments are not limited by the name, quantity, type, size, order, arrangement or other aspects of the elements (such as devices, operations, messages and / or other elements) described below and elsewhere in this article. Although some elements described below (and elsewhere in this article) may be included in 3GPP standards, NR standards, 5G standards and / or other standards, the embodiments are not limited to using these elements included in the standards.

[0072] Some embodiments may relate to possible features of minimum UE requirements for a maximum number of valid downlink control information (DCI) formats. Herein, "valid DCI formats" may also be referred to as "consistent DCI formats" or "PDCCH with consistent control information", etc., suggesting that this refers to a dedicated DCI format that the UE 102 may consider when transmitting consistent layer 1 control information and may need to act upon receiving such control information.

[0073] In addition to the current restrictions / minimum requirements on BD / CCEs for PDCCH monitoring, in some cases the maximum number of valid DCI formats that a UE 102 may expect may impact the overall resource size in the UE 102. This may be due to factors such as the impact on achievable processing latency due to parsing and pruning effects in detecting consistent DCI formats, as well as memory access requirements and UE scheduler (control processing) considerations that may otherwise be required to support a very large number of unicast scheduling instances, all of which are subject to tight processing time constraints in the absence of any restrictions.

[0074] Some embodiments may be related to methods of characterizing a minimum requirement for the number of valid DCI formats that a UE 102 may need to store and / or process. This, in turn, may imply a characterization of the maximum number of valid DCIs that a UE 102 may expect on a certain time scale.

[0075] In some cases, it may be beneficial to define some limits on the maximum number of valid DCI formats that a UE 102 may expect to receive within a certain time scale, for the determination of UE size. In some cases, per-slot limits may need to take into account various possible configurations of PDCCH monitoring opportunities and scheduling options, and may still result in an overly stringent solution from a network perspective. This is due to the fact that a UE 102 may be configured to monitor according to a wide range of PDCCH monitoring configurations, spanning from a single PDCCH monitoring opportunity within a slot to multiple partially / non / fully overlapping PDCCH monitoring opportunities. For example, considering multiple non-overlapping PDCCH monitoring opportunities in a slot, it may not be necessary to enforce an "overall limit" as the impact on the UE implementation from the possible many unicast scheduled DCI triggers is primarily in the form of memory accesses and UE scheduler operations subject to a tight processing time budget.

[0076] In some cases, where a per-monitoring-occasion restriction may seem attractive for a single search space monitoring perspective, there is the possibility that a UE 102 may be configured with multiple (up to 10) search space sets with completely overlapping monitoring occasions, and the UE sizing may result in an unnecessary amount of excess budget to cover the “most extreme” case.

[0077] In some embodiments, a per-PDCCH monitoring span may be used. In some cases, a PDCCH monitoring span may be defined as: "The length of the (PDCCH monitoring) span is Y consecutive OFDM symbols in which the PDCCH is configured to be monitored". Note that the span of consecutive symbols is such that they do not cross slot boundaries.

[0078] Compared to options regarding per-timeslot limits and per-monitoring opportunity limits, embodiments using per-PDCCH monitoring span may provide a convenient and appropriate way to characterize the overall demand on UE processing from a temporal perspective by defining a duration during which one or more PDCCH search space sets may be monitored.

[0079] In some embodiments, from the perspective of UE size, the number of valid DCI formats that trigger unicast reception / transmission events will have substantial value, and defining such a limit can be meaningful for UE implementation. In some embodiments, the value of "Y" can be defined. In some embodiments, for the definition of the span duration "Y" for feature group (FG) #3-5b, it can be indicated as part of the UE capability signaling. In some embodiments, the duration of the PDCCH monitoring span (in "Y" consecutive OFDM symbols) follows the UE capability indicated for FG#3-5b. However, in some cases, this may not be enough for most conventional monitoring configurations (according to FG#3-5). Taking this into account, in some embodiments, the duration Y of the PDCCH monitoring span can be defined as the maximum duration of the CORESET in which the UE 102 is configured to monitor the PDCCH on all configured search space sets. In some embodiments, the duration Y of the PDCCH monitoring span can be defined as the minimum duration of the CORESET in which the UE 102 is configured to monitor the PDCCH on all configured search space sets.

[0080] However, there may be cases where the UE 102 may be configured to monitor the PDCCH using one of the CORESETs of symbols "n" and "n+2", such that symbols n, n+1, and n+2 form a PDCCH monitoring span. To support such use cases, the definition of the span needs to be generalized, and the value of the span duration (Y) should not be limited to the maximum or minimum duration of all CORESETs configured to the UE. Therefore, in some embodiments, the PDCCH monitoring span is defined as a set of Y consecutive OFDM symbols, where the PDCCH is configured to be monitored in at least the first of the Y symbols.

[0081] In some embodiments, the value "Y" may be defined as the maximum number of symbols (e.g., between 2 and 3) that satisfies the constraint of ensuring a minimum span gap of X symbols (as specified or indicated by a UE capability report corresponding to the value of Y). Here, a "span gap" is considered between any two spans containing PDCCH monitoring opportunities, where at least one of them is not a monitoring opportunity of FG (feature group) #3-1 in the same or different search space, and the constraint is such that there is a minimum time separation of X OFDM symbols (including across time slot boundaries) between the start of the two spans. Note that the MO (monitoring opportunity) of FG #3-1 includes MOs within the following spans: span A) includes MOs within the first 3 symbols of the time slot and starts at the first symbol in which PDCCHs of type 1 CSS, type 3 CSS, and UE-SS with dedicated RRC configuration need to be monitored; and span B) includes MOs within three consecutive symbols and starts at the first symbol in which PDCCHs of type 0, 0A, and 2CSS need to be monitored. In some embodiments, each set of monitoring opportunities with the same starting symbol may be used. Considering the case of overlapping PDCCH spans, e.g., for PDCCH monitoring according to FG#3-5, the option of defining the PDCCH monitoring span as a time scale to define the minimum requirement for the UE to store / process the maximum number of valid DCI formats does not achieve a good balance between scheduling flexibility (blocking performance) and UE complexity. To address this, in some embodiments, it is expected that the UE 102 will not store or process more than a certain number of valid DCI formats on each set of PDCCH monitoring opportunities (over all configured PDCCH search space sets) with the same starting symbol. From the perspective of the gNB scheduler, each start system for a monitoring opportunity can be mapped to a scheduling opportunity in time, and therefore, defining the maximum # of valid DCIs meaningfully achieves a balance between characterizing the valid DCIs from the perspective of scheduling opportunities / flexibility and UE processing requirements.

[0082] In some embodiments, the UE 102 is not expected to store or process more than a certain number of valid DCI formats on each set of PDCCH monitoring occasions (over all configured PDCCH search space sets) with the same end symbol.

[0083] Some embodiments may relate to which DCI formats should be considered. First, in some cases, it may not be necessary to limit the maximum number of DCI formats for all types of DCI formats. In this regard, in some cases, it may be important to limit the number of DCI formats that schedule unicast services due to tight processing timeline requirements. In some embodiments, the number of broadcast DCI formats may be limited based on processing no more than one DCI per RNTI in a type 0 CSS, a type 0A CSS, a type 1 CSS, a type 2 CSS, a type 3 CSS other than unicast DCI per slot, etc.

[0084] In some cases, limiting other DCI formats (e.g., group common DCI formats) may not be so critical from a UE implementation perspective. Therefore, in some embodiments, a minimum requirement for the (maximum) number of valid DCI formats is defined for DCI formats scheduling unicast PDSCH or PUSCH (with CRC scrambled with C-RNTI, CS-RNTI (if configured) or MCS-C-RNTI (if configured)). These include DCI formats for DL / UL scheduling of unicast PDSCH / PUSCH (respectively) based on dynamic scheduling, activation DCI for grant (CG) PUSCH of type 2 configuration, and activation DCI for DL ​​SPS PDSCH.

[0085] In some embodiments, for DCI formats scheduling unicast PDSCH or PUSCH (with CRC scrambled with C-RNTI, CS-RNTI (if configured) or MCS-C-RNTI (if configured)), or broadcast PDSCH (with CRC scrambled with one or more of SI-RNTI, RA-RNTI, TC-RNTI), a minimum requirement for the (maximum) number of valid DCI formats is defined. In this case, the maximum number of valid DCI formats may be determined as: one for DCI scheduling unicast PDSCH (FDD and TDD); one (or two) for DCI scheduling unicast PUSCH for FDD (or TDD); one for each RNTI used for broadcast PDSCH scheduling (FDD and TDD); and so on.

[0086] In some embodiments, one or more of the following constraints on the number of unicast scheduled DCI formats may be relevant. In some embodiments, Feature Group (FG) #3-1 (mandatory w / o capability signaling), the following components (which may be referred to as "5" and "6" below without limitation) may be relevant: 5) For FDD, each scheduled CC processes one unicast DCI scheduled DL and one unicast DCI scheduled UL per time slot; 6) For TDD, each scheduled CC processes one unicast DCI scheduled DL and 2 unicast DCI scheduled UL per time slot. In some embodiments, FG#3-5a (optional w / o capability signaling), for type 1 CSS, type 3 CSS, and UE-SS with dedicated RRC configuration, the monitoring opportunity can be any OFDM symbol of the slot for case 2, with a minimum time separation (including cross-slot boundary cases) between two DL unicast DCIs, between two UL unicast DCIs, or between DL and UL unicast DCIs in different monitoring opportunities for the same UE: 2 OFDM symbols for 15kHz; 4 OFDM symbols for 30kHz; 7 OFDM symbols for 60kHz with NCP; 14 OFDM symbols for 120kHz; etc. In addition, for TDD, the minimum separation between the first two UL unicast DCIs in the first monitoring opportunity within the first 3 OFDM symbols of the slot can be zero OFDM symbols. Therefore, the remaining cases for PDCCH monitoring configuration include FG#3-5 and FG#3-5b. In FG#3-5: For Type 1 CSS, Type 3 CSS and UE-SS with dedicated RRC configuration, the monitoring opportunity can be any OFDM symbol of the time slot used for case 2. In FG#3-5b, for Type 1 CSS, Type 3 CSS and UE-SS with dedicated RRC configuration, the monitoring opportunity can be any OFDM symbol of the time slot used in case 2 with a span gap.

[0087] Some embodiments may be related to many PDSCH / PUSCH TBs within a timeslot. If a limit on the maximum number of valid unicast scheduled DCIs is defined per timeslot, the case where multiple PDSCH / PUSCH TBs are scheduled within a timeslot may be included. However, for characterizing the limit per PDCCH monitoring span or per set of monitoring opportunities with the same starting symbol, special consideration may not be needed for the feature of multiple TBs within a timeslot, considering the fact that the feature of multiple TBs within a timeslot is mainly motivated by the "mini-slot based scheduling" approach with low latency objectives in mind, implying a reliance on multiple PDCCH monitoring opportunities TDMed within a timeslot. If all scheduled DCIs are to be sent within a single span of PDCCH monitoring opportunities, there will not be much practical benefit in scheduling the UE 102 with multiple PDSCH / PUSCH TBs TDMed within a timeslot.

[0088] Based on the above considerations, it can be seen that defining a limit on the maximum number of valid unicast scheduling DCI formats should allow for a meaningful resolution of the PDCCH monitoring cases for FG#3-5 and FG#3-5b. In this regard, defining a limit on the maximum number of valid unicast scheduling DCI formats per PDCCH monitoring span provides the best balance between scheduling flexibility and impact on UE implementation.

[0089] In some embodiments, for the exact limitations, considering the above discussion and the target use cases and the impact on the UE implementation, in one embodiment, the maximum number can be defined as follows: 1) The maximum number of valid DCIs for scheduling unicast PDSCH on each set of monitoring opportunities with the same starting symbol per scheduled CC = 1 (for TDD and FDD), 2) The maximum number of valid DCIs for scheduling unicast PUSCH on each set of monitoring opportunities with the same starting symbol per scheduled CC = 1 (FDD), 3) The maximum number of valid DCIs for scheduling unicast PUSCH on each set of monitoring opportunities with the same starting symbol per scheduled CC = 2 (TDD).

[0090] In some embodiments, for carrier aggregation (CA) configuration, the above numbers are scaled up to four DL / ULCCs, respectively, and when the number of configured DL / UL CCs is greater than four, the UE capability for BD / CCE scaling (y) is used to scale the above number of the maximum number of valid DCIs for scheduling unicast PDSCH / PUSCH.

[0091] In some embodiments, in a method for new radio (NR) communications, a minimum requirement for the number of valid DCI formats that a UE 102 may need to store or process may be determined (and / or defined) per time unit. In some embodiments, a time unit may correspond to a PDCCH monitoring span of Y consecutive OFDM symbols that does not cross a slot boundary. In some embodiments, for UEs indicating support for NR UE feature group #3-5b, the duration of the PDCCH monitoring span (in "Y" consecutive OFDM symbols) may follow the UE capabilities indicated for FG #3-5b.

[0092] In some embodiments, the duration Y of the PDCCH monitoring span may be defined as the maximum duration in which the UE 102 is configured to search the CORESET for PDCCH over all configured search space sets. In some embodiments, the duration Y of the PDCCH monitoring span may be defined as the minimum duration in which the UE 102 is configured to search the CORESET for PDCCH over all configured search space sets.

[0093] In some embodiments, it is not expected that the UE 102 will store or process more than a certain number of valid DCI formats on each set of PDCCH monitoring opportunities (over all configured PDCCH search space sets) with the same starting symbol. In some embodiments, it is not expected that the UE 102 will store or process more than a certain number of valid DCI formats on each set of PDCCH monitoring opportunities (over all configured PDCCH search space sets) with the same ending symbol.

[0094] In some embodiments, for DCI formats scheduling unicast PDSCH or PUSCH (with CRC scrambled with C-RNTI, CS-RNTI (if configured) or MCS-C-RNTI (if configured)), a minimum requirement for the (maximum) number of valid DCI formats is defined. In some embodiments, for DCI formats scheduling unicast PDSCH or PUSCH (with CRC scrambled with C-RNTI, CS-RNTI (if configured) or MCS-C-RNTI (if configured)), or broadcast PDSCH (with CRC scrambled with one or more of SI-RNTI, RA-RNTI, TC-RNTI), a minimum requirement for the (maximum) number of valid DCI formats is defined. In some embodiments, the PDCCH monitoring span is a set of Y consecutive OFDM symbols, where the PDCCH is configured to be monitored in at least the first symbol of the Y symbols. In some embodiments, the span duration (Y) is the maximum number of symbols (e.g., between 2 and 3) that satisfies the following constraint: between any two spans containing monitoring opportunities for PDCCH, a minimum span gap of X symbols (with a value of X corresponding to the value of Y as specified or indicated by the UE capability report) is ensured to include cross-slot boundary cases, where at least one monitoring opportunity for PDCCH is not a monitoring opportunity for FG (feature group) #3-1 in the same or different search space.

[0095] The Abstract is provided to comply with 37 CFR Section 1.72(b) requiring an abstract that allows the reader to ascertain the nature and gist of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

1. A device of a user equipment (UE), the device comprising: Memory; and a processing circuit system configured to: Decode control signaling from the next generation Node B (gNB) that configures one or more control resource sets (CORESETs), wherein each of the one or more CORESETs is configurable to span a variable number of resource blocks (RBs) in the frequency domain, wherein each of the one or more CORESETs is configurable to span a variable number of orthogonal frequency division multiplexing (OFDM) symbols in the time domain, wherein each of the CORESETs is allocated for reception of one or more physical downlink control channels (PDCCHs); and determining a duration of a PDCCH monitoring span, wherein the PDCCH monitoring span indicates a number of consecutive OFDM symbols in which the UE is to monitor the PDCCH; The processing circuit system is configured to determine the duration of the PDCCH monitoring span based on: The maximum number of OFDM symbols spanned by the one or more CORESETs; or A function of the PDCCH monitoring duration corresponding to the span gap value indicated by the UE capability report, The memory is configured to store information related to the one or more CORESETs.

2. The apparatus of claim 1 , wherein the processing circuit system is configured to: determining one or more sets of downlink control information (DCI) formats to be stored and processed by the UE upon reception of a decoded PDCCH during the PDCCH monitoring span; During the PDCCH monitoring span, monitoring the CORESET for PDCCH; as well as If one or more PDCCHs are decoded, DCI formats in the one or more sets of determined DCI formats within the decoded PDCCHs are stored and processed.

3. The device as claimed in claim 2, wherein: For each of the one or more sets of DCI formats, a maximum limit on the number of DCI formats for each set of DCI formats is predefined.

4. The apparatus of claim 2, wherein the processing circuit system is configured to: The one or more sets of DCI formats are determined to include a DCI format that triggers uplink (UL) transmission or unicast downlink (DL) reception.

5. The apparatus of claim 4, wherein the processing circuit system is configured to: Determining the one or more sets of DCI formats to include: The DCI format for scheduling the unicast Physical Downlink Shared Channel (PDSCH), and A DCI format for scheduling a physical uplink shared channel (PUSCH), wherein the corresponding PDCCH carries a cyclic redundancy check (CRC) scrambled with a radio network temporary identifier (RNTI), the RNTI being one of: a cell RNTI (C-RNTI); a configured scheduling (CS) RNTI (CS-RNTI), if a CS-RNTI is configured; and the Modulation and Coding Scheme (MCS) Cell-RNTI (MCS-C-RNTI), if MCS-C-RNTI is configured.

6. The apparatus of claim 2, wherein the processing circuit system is further configured to: determining a first set of DCI formats according to a first maximum limit on the number of DCI formats for each set of DCI formats, the first set of DCI formats including a DCI format for scheduling a unicast PDSCH; and According to a second maximum limit on the number of DCI formats for each set of DCI formats, a second set of DCI formats is determined, the second set of DCI formats including a DCI format for scheduling a PUSCH.

7. The device of claim 1, wherein: The PDCCH monitoring span occurs within a subframe comprising a plurality of time slots, wherein the number of time slots is based at least in part on a subcarrier spacing (SCS) of a downlink bandwidth part (BWP), and The PDCCH monitoring span includes consecutive OFDM symbols that do not cross a slot boundary between any two consecutive slots of a subframe.

8. The device of claim 1, wherein: The UE is arranged to operate according to a New Radio (NR) protocol.

9. The apparatus of claim 1, wherein: The processing circuitry includes a baseband processor for decoding the control signaling, and The device also includes a transceiver, configured to receive the control signaling.

10. The apparatus of claim 1, wherein: At least one of the two PDCCH monitoring occasions is not a monitoring occasion belonging to a monitoring span of type A or type B. wherein the monitoring opportunity of the span of type A is within the first three symbols of the time slot, wherein the monitoring opportunity of the span of type A starts at the first symbol of the time slot in which the PDCCH is to be monitored, wherein the PDCCH to be monitored is for one of the following: Type 1 Common Search Space (CSS) with dedicated Radio Resource Control (RRC) configuration, Type 3 CSS, and UE search space (UE-SS); And wherein the monitoring opportunity of the span of type B is within three consecutive OFDM symbols, wherein the monitoring opportunity of the span of type B starts at the first symbol of the time slot in which the PDCCH of type 0, type 0A or type 2 CSS is to be monitored.

Images