Scheduling of control signaling from the secondary cell to the primary cell
Patent Information
- Application Number
- CN202180012487.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-04
- Publication Date
- 2026-09-01
- Estimated Expiration
- 2041-08-04
AI Technical Summary
然而,用于5G通信的CORESET的传输可能干扰LTE网络上的小区参考信号(CRS)传输
Smart Images

Figure CN115943704B_ABST
Abstract
Description
Background Technology
[0001] When establishing network connections, such as connections to 5G New Radio (NR) networks, the next-generation NodeB (gNB) transmits downlink channel information (DCI) to the UE via the Physical Downlink Control Channel (PDCCH). The PDCCH is transmitted to the UE via one or more control resource sets (CORESETs). Because 5G NR spectrum is difficult to obtain and expensive, operators have utilized Dynamic Spectrum Sharing (DSS) to allow 5G NR and LTE transmissions to coexist on the same spectrum. However, the transmission of CORESETs used for 5G communications may interfere with the transmission of Cell Reference Signals (CRS) on the LTE network. Summary of the Invention
[0002] Some exemplary embodiments relate to a processor of a base station configured to perform operations. These operations include configuring a first search space in a special cell (SpCell) having a first search space identifier (SearchSpaceId) and a second search space in a secondary cell (SCell) having a second search space identifier (SearchSpaceId) for monitoring and scheduling operations on the SpCell; and transmitting a Radio Resource Control (RRC) configuration including a first SSID and a second SSID to a User Equipment (UE), wherein the RRC configuration configures the UE to monitor the first search space with the first SSID for scheduling a first type of control signaling and to monitor the second search space with the second SSID for scheduling a second type of control signaling.
[0003] Other exemplary embodiments relate to a base station having: a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver and configured to perform operations. The operations include configuring a first search space in a special cell (SpCell) having a first search space identifier (SearchSpaceId) and a second search space in a secondary cell (SCell) having a second search space identifier (SearchSpaceId) for monitoring and scheduling operations on the SpCell; and transmitting a Radio Resource Control (RRC) configuration including a first SSID and a second SSID to the UE, wherein the RRC configuration configures the UE to monitor the first search space with the first SSID for scheduling a first type of control signaling and to monitor the second search space with the second SSID for scheduling a second type of control signaling. Attached Figure Description
[0004] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.
[0005] Figure 2 Exemplary user equipment (UE) according to various exemplary embodiments are shown.
[0006] Figure 3 An exemplary base station according to various exemplary embodiments is shown.
[0007] Figure 4 A method for scheduling transmissions on a special cell (SpCell) by configuring the search space (SS) of a secondary cell (SCell) according to various exemplary embodiments is shown.
[0008] Figure 5 The diagram illustrates a method for deactivating an SCell that is configured to schedule transmissions on a SpCell, according to various exemplary embodiments. Detailed Implementation
[0009] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments relate to the configuration of the search space when, in addition to a special cell (SpCell) being configured to schedule its own operation, a secondary cell (SCell) is also configured to schedule UE operations on the SpCell. In the following description, SpCell may refer to the primary cell (PCell) or the primary SCell (PSCell).
[0010] The exemplary embodiments are described with respect to the UE. However, reference to the UE is provided for illustrative purposes only. The exemplary embodiments can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE as described herein is used to represent any suitable electronic component.
[0011] Furthermore, exemplary embodiments are described with reference to 5G New Radio (NR) networks. However, the reference to 5G NR networks is provided for illustrative purposes only. Exemplary embodiments can be used with any network that implements the functionality described herein.
[0012] To leverage Dynamic Spectrum Sharing (DSS) to provide 5G NR networks with greater flexibility in scheduling control data to be transmitted, it has been proposed that, in addition to configuring SpCells (e.g., 5G cells) to schedule their own transmissions, SCells (e.g., 5G cells) should also be configured to schedule operations on the SpCell. However, one issue that arises is how the search space (SS) should be configured to facilitate the scheduling of these transmissions on the SpCell by both cells (SpCell and SCell).
[0013] According to some exemplary implementations, the network configures one or more search spaces, at least one of SpCell and SCell, for scheduling control data transmission on SpCell. The network instructs the UE which search space(s)(s) should be monitored for this scheduling.
[0014] Another issue that arises is how the UE should handle the deactivation or hibernation of the SCell when the scheduling of control data transmission on the SpCell is performed by both the SpCell and the SCell.
[0015] According to other exemplary embodiments, the network configures one or more search spaces for each of SpCell and SCell. The network then explicitly or implicitly instructs the UE which search space the UE should monitor when an SCell is deactivated or put to sleep.
[0016] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is illustrated. The exemplary network arrangement 100 includes a UE 110. It should be noted that any number of UEs can be used in the network arrangement 100. Those skilled in the art will understand that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. It should also be understood that a real network arrangement can include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.
[0017] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 can wirelessly communicate are 5G New Radio (NR) Radio Access Network (5G NR-RAN) 120, LTE Radio Access Network (LTE-RAN) 122, and Wireless Local Area Network (WLAN) 124. However, it should be understood that UE 110 can also communicate with other types of networks, and UE 110 can also communicate with networks via wired connections. Therefore, UE 110 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124.
[0018] 5G NR-RAN 120 and LTE-RAN 122 may be portions of a cellular network that can be deployed by a cellular provider (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).
[0019] UE 110 can connect to 5G NR-RAN 120 via gNB 120A and / or gNB 120B. gNBs 120A and 120B can be configured with the necessary hardware (e.g., antenna arrays), software, and / or firmware to perform massive MIMO functionality. Massive MIMO can refer to a base station configured to generate multiple beams for multiple UEs. During operation, UE 110 can be within range of multiple gNBs. Reference to the two gNBs 120A and 120B is for illustrative purposes only. Exemplary implementations can be applied to any suitable number of gNBs. Additionally, UE 110 can communicate with eNB 122A of LTE-RAN 122 to transmit and receive control information for downlink and / or uplink synchronization relative to the 5G NR-RAN 120 connection.
[0020] Those skilled in the art will understand that any relevant procedures can be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 can be associated with a specific cellular provider, where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 can transmit the corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 can be associated with a specific base station (e.g., gNB 120A of 5G NR-RAN 120).
[0021] In addition to networks 120, 122, and 124, network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.
[0022] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 can represent any electronic device and may include processor 205, memory layout 210, display device 215, input / output (I / O) device 220, transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, batteries providing a limited power source, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, one or more antenna panels, etc. For example, UE 110 may be coupled to industrial equipment via one or more ports.
[0023] Processor 205 may be configured to execute multiple engines of UE 110. For example, an engine may include search space management engine 235. Search space management engine 235 may perform various operations related to determining which search space(s)(s) should be monitored for control data scheduling for SpCell, as will be described in more detail below.
[0024] The engine described above, as an application (e.g., a program) executed by processor 205, is merely exemplary. The functionality associated with the engine may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as a single application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.
[0025] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with 5G NR-RAN 120, LTE-RAN 122, WLAN 124, etc. Therefore, transceiver 225 may operate on multiple different frequencies or channels (e.g., a continuous set of frequencies).
[0026] Figure 3 An exemplary network base station according to various exemplary embodiments is shown, in this example being gNB 120A. gNB 120A can represent any access node that a UE 110 in a 5G NR network can use to establish a connection. Figure 3 The gNB 120A shown can also represent gNB 120B.
[0027] The gNB 120A may include a processor 305, a memory arrangement 310, input / output (I / O) devices 320, a transceiver 325, and other components 330. These other components 330 may include, for example, a power supply, data acquisition devices, and ports for electrically connecting the gNB 120A to other electronic devices.
[0028] Processor 305 can be configured to execute multiple engines of gNB 120A. For example, an engine may include search space management engine 335 for performing operations including configuring one or more search spaces when both SpCell and SCell are configured to schedule control data transmission on SpCell and configuring UE 110 to handle deactivation or hibernation of SCell. An example of this process will be described in more detail below.
[0029] The engine described above, as an application (e.g., a program) executed by processor 305, is merely exemplary. The functionality associated with the engine may also be represented as a separate integrated component of gNB 120A, or as a modular component coupled to gNB 120A, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some gNBs, the functionality described for processor 305 is split among multiple processors (e.g., a baseband processor, an application processor, etc.). Exemplary aspects may be implemented according to any of these or other configurations of the gNB.
[0030] Memory 310 may be a hardware component configured to store data related to operations performed by UEs 110 and 112. I / O device 320 may be a hardware component or port enabling a user to interact with gNB 120A. Transceiver 325 may be a hardware component configured to exchange data with UE 110 and any other UE in system 100. Transceiver 325 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). Therefore, transceiver 325 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.
[0031] Figure 4 A method 400 is illustrated for configuring the search space of an SCell (e.g., a 5G cell) for scheduling transmissions on an SpCell (e.g., a 5G cell) according to various exemplary embodiments. At 405, a gNB 120A (or 120B) configures the SpCell (e.g., gNB 120A) and SCell (e.g., eNB 122A) to schedule control data transmissions (e.g., DCI, PDCCH, etc.) for the SpCell. In some embodiments, the SCell cannot be configured in frequency range 2 (FR2). In some embodiments, whether the SCell can be configured in FR2 depends on the capabilities of the UE. In some embodiments, the SCell cannot be configured in non-terrestrial network (NTN) spectrum. In some embodiments, the SCell cannot be configured in NR unlicensed (NR-U) spectrum. In some embodiments, whether the SCell can be configured in NR-U spectrum depends on the capabilities of the UE.
[0032] At 410, the gNB 120A configures a first search space in the SpCell and a second search space in the SCell. In some implementations, the first and second search spaces have the same SearchSpaceId. In such implementations, the two search spaces are automatically linked because when the gNB 120A configures the UE 110 with a SearchSpaceId for monitoring, that SearchSpaceId corresponds to both the first and second search spaces. In some implementations, when the first and second SearchSpaceIds are the same, the nrofCandidates information element (IE) is in the first search space of the SpCell, and all other control signal configurations (e.g., non-fallback DCI, remaining PDCCH configuration) are in the second search space of the SCell. In some implementations, when the first and second SearchSpaceIds are the same, nrofCandidates IE and certain other control signal configurations (e.g., monitoringSlotPeriodicityAndOffset, monitoringSymbolsWithinSlot, duration) are in the first search space of SpCell, and all other control signal configurations (e.g., non-back-off DCI, remaining PDCCH configuration) are in the second search space of SCell.
[0033] In some implementations, the first search space and the second search space, along with their corresponding SearchSpaceIds, are different. In such implementations, the first search space of the SpCell includes the fallback DCI scheduling (e.g., formats 0_0 and 1_0), and the second search space includes the scheduling of all other control signaling (e.g., non-fallback DCI, all PDCCH configurations). In such implementations, because the SearchSpaceIds of the two search spaces are different, the gNB 120A explicitly indicates the second SSID to the UE 110, enabling the UE 110 to know which search space to monitor for non-fallback DCI and all PDCCH configurations. In some implementations, the second search space is counted as one of the standard-defined maximum values for ten search spaces per cell. In some implementations, the second search space is optionally not counted as one of the standard-defined maximum values for ten search spaces per cell.
[0034] At position 415, the gNB 120A configures the Beam Fault Recovery (BFR) search space. In some implementations, the BFR search space (recoverySearchSpaceId) is configured only in the SpCell. In some implementations, the BFR search space (recoverySearchSpaceId) is configured only in the SCell. In some implementations, the gNB 120A can select which cell to configure the BFR search space (recoverySearchSpaceId).
[0035] At 420, the gNB 120A configures whether downlink (DL) and / or uplink (UL) DCI transmissions are scheduled by the second search space of the SCell. In some implementations, both the first search space of the SpCell and the second search space of the SCell schedule DL and UL DCIs for UE operation on the SpCell. In some implementations, the gNB 120A alternatively restricts which DCI (DL or UL) the UE 110 is configured to monitor on the SCell.
[0036] At 425, gNB 120A transmits the RRC configuration to UE 110. This RRC configuration includes a first SearchSpaceId corresponding to a first search space and a second SearchSpaceId corresponding to a second search space, enabling UE 110 to know which search space(s)(s) the control signals for scheduling operations on the SpCell(s) are monitoring. In some implementations, the RRC configuration also includes a BFR search space ID.
[0037] As currently defined by the 3GPP standard, the total number of different DCI sizes monitored by UE 110 is four. The total number of different DCI sizes monitored by UE 110 that are scrambled by the Cell Radio Network Temporary Identifier (C-RNTI) is three. In some implementations, UE 110 is limited to these maximum values in both the first and second search spaces. In some implementations, UE 110 is alternatively limited to these maximum values in each of the first and second search spaces. In such implementations, UE 110 may report to gNB 120A whether it supports additional DCI size monitoring limits associated with per-cell application size limits.
[0038] Figure 5 A method 500 for deactivating an SCell configured to schedule transmissions on an SpCell is illustrated according to various exemplary embodiments of the UE 110. The following description assumes that both the SpCell and the SCell are 5G cells.
[0039] At 505, gNB 120A (or 120B) configures SpCell (e.g., gNB 120A) and SCell (e.g., eNB 122A) to schedule control data transmission (e.g., DCI) for SpCell. At 510, gNB 120A configures a first search space in SpCell with a first SearchSpaceId and a second search space in SCell with a second SearchSpaceId. At 515, gNB 120A transmits an RRC configuration including the SearchSpaceIds of the first and second search spaces to UE 110. At 520, gNB 120A provides UE 110 with an indication of which search space is monitored (which search space is active) when SCell is deactivated or hibernating.
[0040] In some implementations, the indication provided by gNB 120A at 520 is an implicit indication. In such implementations, when UE 110 receives an indication that a SCell has been deactivated or is in sleep mode, UE 110 implicitly knows that the second search space has been deactivated and the first search space has been activated. Similarly, when UE 110 receives an indication that a SCell has been activated, UE 110 implicitly knows that the second search space has been activated and the first search space has been deactivated.
[0041] In some implementations, the indication provided by gNB 120A at 520 may be an explicit indication. In such implementations, gNB 120A may transmit a DCI or Media Access Control (MAC) control element (CE) to indicate to UE 110 which search space UE 110 should monitor. In some implementations, gNB 120A may be configured with a timer to handle scenarios where the DCI / MAC CE is not received or is incorrectly decoded by UE 110. The timer starts when the DCI / MAC CE is received. When the timer expires, UE 110 begins monitoring the default search space. For example, if the DCI / MAC CE indicates that UE 110 should monitor a second search space, then UE 110 monitors the second search space until the timer expires, at which point UE 110 monitors the first search space, which is configured as the default search space. If gNB 120A intends for UE 110 to continue monitoring the second search space, then gNB 120A sends another DCI / MAC CE indicating that UE 110 should monitor the second search space. The timer is reset upon receiving the second DCI / MAC CE. In some implementations, the timer is set to 100ms. It should be noted that the default search space can be configured to be either the first or the second search space.
[0042] In some implementations, the SCell configured at 505 can be multiple SCells. In such implementations, at any given time, only one of the multiple SCells is active for monitoring control signaling on the scheduled SpCell. In some implementations, when an SCell is deactivated or dormant, the active SCell can be explicitly indicated to the UE 110 by the gNB 120A, via, for example, DCI or MAC CE. In some implementations, the active SCell can be determined based on priority based on several predetermined factors, such as, for example, the periodicity of the search space in each SCell configured to schedule control data signaling on the SpCell, the SearchSpaceId of each search space in each SCell configured to schedule control data signaling on the SpCell, and the cell index (ServCellIndex) of each SCell. For example, a search space with a smaller periodicity will have a higher priority compared to a search space with a larger periodicity.
[0043] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. Exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.
[0044] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.
[0045] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.
[0046] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.
Claims
1. An apparatus for a base station, the apparatus comprising a processor configured to perform operations including: Configure a first search space with a first search space identifier (SearchSpaceId) in a special cell (SpCell) and a second search space with a second search space identifier (SearchSpaceId) in a secondary cell (SCell) for monitoring and scheduling control signaling on the SpCell, wherein the first search space identifier (SearchSpaceId) and the second search space identifier (SearchSpaceId) are the same; and The Radio Resource Control (RRC) configuration is transmitted to the User Equipment (UE), wherein the RRC configuration configures the UE to monitor the first search space for scheduling a first type of control signaling and to monitor the second search space for scheduling a second type of control signaling, wherein the first type of control signaling includes downlink control information (DCI) format 0_0 transmissions, DCI format 1_0 transmissions, and nrofCandidates information elements (IEs) from physical downlink control channel (PDCCH) transmissions, and the second type of control signaling includes all other DCI transmissions and PDCCH IEs not included in the first type of control signaling.
2. The apparatus according to claim 1, wherein the operation further comprises: Configure the beam fault recovery (BFR) search space in the SpCell.
3. The apparatus according to claim 1, wherein the operation further comprises: Configure the beam fault recovery (BFR) search space in the SCell.
4. The apparatus of claim 1, wherein the second type of control signaling includes both downlink DCI signals and uplink DCI signals.
5. The apparatus of claim 1, wherein the second type of signaling includes either a downlink DCI signal or an uplink DCI signal.
6. The apparatus of claim 1, wherein the UE is configured to monitor up to four different DCI sizes for both the first search space on the SpCell and the second search space on the SCell.
7. The apparatus of claim 1, wherein the UE is configured to monitor up to four different DCI sizes for each of the first search space on the SpCell and the second search space on the SCell.
8. The apparatus of claim 1, wherein the operation further comprises: Send an indication to the UE, the indication identifying which search space to monitor when the SCell is deactivated or hibernating.
9. The apparatus of claim 8, wherein the indication is an implicit indication of whether the SCell is activated or deactivated. When the SCell is activated or wakes from sleep, the second search space is activated and the first search space is deactivated. When the SCell is deactivated or hibernated, the first search space is activated and the second search space is deactivated.
10. The apparatus of claim 8, wherein the indication is an explicit indication, including one of a DCI or a Media Access Control (MAC) control element (CE), indicating which of the first search space or the second search space is activated.
11. The apparatus of claim 10, wherein the UE is configured to monitor a default search space after a timer expires, wherein the timer starts upon receiving the DCI or the MAC CE, and wherein the default search space is one of the first search space or the second search space.
12. The apparatus of claim 8, wherein the SCell is one of a plurality of SCells that configure the UE to monitor and schedule operations on the SpCell, and wherein the operations further include: Indicate to the UE which of the plurality of SCells is activated.
13. The apparatus of claim 12, wherein the activated SCell among the plurality of SCells is explicitly indicated in a DCI or MAC CE.
14. The apparatus of claim 12, wherein the activated SCell among the plurality of SCells is implicitly indicated based on a plurality of predetermined factors.
15. The apparatus of claim 14, wherein the predetermined factors include the periodicity of the search space in each of the plurality of SCells, the SearchSpaceId of each search space in the plurality of SCells, and the cell index (ServCellIndex) of each of the plurality of SCells.
16. A base station, comprising: A transceiver configured to communicate with user equipment (UE); as well as A processor, communicatively coupled to the transceiver and configured to perform operations including: Configure a first search space with a first search space identifier (SearchSpaceId) in a special cell (SpCell) and a second search space with a second search space identifier (SearchSpaceId) in a secondary cell (SCell) for monitoring control signaling that schedules operations on the SpCell, wherein the first search space identifier (SearchSpaceId) and the second search space identifier (SearchSpaceId) are the same; as well as The Radio Resource Control (RRC) configuration is transmitted to the UE, wherein the RRC configuration configures the UE to monitor the first search space for scheduling a first type of control signaling and to monitor the second search space for scheduling a second type of control signaling, wherein the first type of control signaling includes downlink control information (DCI) format 0_0 transmissions, DCI format 1_0 transmissions, and nrofCandidates information elements (IEs) from physical downlink control channel (PDCCH) transmissions, and the second type of control signaling includes all other DCI transmissions and PDCCH IEs not included in the first type of control signaling.
17. The base station according to claim 16, wherein the operation further comprises one of the following: Configure the beam fault recovery (BFR) search space in the SpCell; or Configure the beam fault recovery (BFR) search space in the SCell.
18. The base station of claim 16, wherein the second type of control signaling includes one of the following: (i) both downlink DCI signal and uplink DCI signal, (ii) downlink DCI signal, or (iii) uplink DCI signal.
19. The base station of claim 16, wherein the UE is configured to monitor up to four different DCI sizes for both the first search space on the SpCell and the second search space on the SCell.
20. The base station of claim 16, wherein the UE is configured to monitor up to four different DCI sizes for each of the first search space on the SpCell and the second search space on the SCell.
21. The base station according to claim 16, wherein the operation further comprises: Send an indication to the UE, the indication identifying which search space to monitor when the SCell is deactivated or hibernating.
Citation Information
Patent Citations
Cross Carrier Scheduling
US20210045147A1