English:
[0002]As the number of mobile devices within wireless networks, and the demand for mobile data traffic, continue to increase, changes are made to system requirements and architectures to better address current and anticipated demands. For example, some wireless communication networks may be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and so on. An aspect of such technology includes addressing how wireless devices wireless resources may be allocated to communications between user equipment (UEs) and base stations (which may include one or more cells) .
[0003]The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals may designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and may mean at least one, one or more, etc.
[0004]Fig. 1 is a diagram of an example network according to one or more implementations described herein.
[0005]Fig. 2 is a diagram of a master cell group (MCG) and a secondary cell group (SCG) of a wireless communication network.
[0006]Fig. 3 is a flowchart of an example process for managing dynamic spectrum sharing (DSS) in one or more cell groups.
[0007]Figs. 4-5 are diagrams of example slots for a special primary cell (SpCell) and a special scheduling cell (sSCell) along a timeline.
[0008]Figs. 6 and 7 are diagrams of example configurations of cell groups (CGs) .
[0009]Fig. 8 is a diagram of an example configuration of a CG.
[0010]Fig. 9 is a diagram of an example of deactivating a sSCell.
[0011]Fig. 10 is a diagram of an example of activating a sSCell.
[0012]Fig. 11 is a diagram of an example process for monitoring search spaces for downlink control information (DCI) .
[0013]Fig. 12 is a diagram of an example of components of a device according to one or more implementations described herein.
[0014]Fig. 13 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.
[0015]The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings may identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations may be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.
[0016]Mobile communication networks may include one or more types and/or generations of wireless communication networks, such as 4th generation (4G) (e.g., Long-Term Evolution (LTE) ) networks, 5th generation (5G) or new radio (NR) networks, etc. Such networks may include user equipment (UEs) and base stations that communicate with one another wirelessly. In some implementations, a network may simultaneously implement more than one type of network technology (e.g., 4G and 5G) such that UEs may operate within the network based on 4G technology or 5G technology. An aspect of such networks may include dynamic spectrum sharing (DSS) . DSS may include a technique whereby similar features of wireless communication (e.g., subcarrier spacing, time domain structures, etc. ) , may be used for both 4G or 5G technology, such that UEs and base stations are able to communicate with one another in the same network and via the same radio spectrum (s) . However, while currently available DSS techniques may enable both 4G and 5G technologies to be implemented simultaneously (e.g., using the same network and radio spectrum) , current DSS techniques include certain limitations.
[0017]For example, current DSS techniques may limit 5G implementations due to certain 4G constructions and implementations. In one example, current DSS techniques (e.g., 4G or LTE techniques) may limit 5G due to cell reference signal (CRS) transmissions from LTE. For example, in LTE, when 1 or 2 port CRS is implemented, the CRS may occupy symbols 0, 4, 7, and 11, and when 4 port CRS is implemented, the CRS may occupy symbols 0, 1, 4, 7, 8, and 11. As such, current DSS techniques may forego benefits, efficiencies, and flexibilities enabled by  5G technology, which limits the number of symbols, the frequency and time location for 5G control resource set (e.g., CORESET) configurations.
[0018]Additionally, current 4G or LTE techniques may limit 5G implementations in terms of cross carrier scheduling (CCS) (e.g., no scheduling between different groups of cells, a primary cell only being scheduled by itself, each scheduled cell only having one scheduling cell configurable via radio resource control (RRC) messaging, etc. ) . Current 4G or LTE techniques may further limit 5G implementations in terms of downlink control information (DCI) . For example, 4G or LTE techniques may limit 5G DCI to certain DCI formats (e.g., DCI formats 0_0, 1_0, etc., of LTE for fallback DCI. Similarly, current 4G or LTE techniques may impose certain search space restriction, such as common search space (CSS) restrictions for fallback DCI. Current 4G or LTE techniques may further limit 5G implementations in terms of cell grouping, cell scheduling, cell activation and deactivation, cell dormancy and wakeup, etc. For example, current 4G or LTE techniques may not provide for adequate cell activation and deactivation, cell dormancy and wakeup, etc.
[0019]Techniques described herein may include solutions to the aforementioned limitations. In some implementations, a special scheduling cell (sSCell) may be provided for DSS. The sSCell may be configured to schedule a primary cell of a master cell group (MCG) or a primary cell of a secondary cell group (SCG) . Such a primary cell may be referred to herein as a special cell or SpCell. In some implementations, the sSCell may be activated and/or deactivated, enter in or exit from a state of dormancy, and radio link monitoring (RLM) , beam failure recovery (BFR) , and cell grouping parameters may be provided. Techniques described herein may include solutions for configuring a UE-specific search spaces (USS) with non-fallback DCI, USS with fallback DCI, and overall search space for DSS enhancement.
[0020]Fig. 1 is an example network 100 according to one or more implementations described herein. Example network 100 may include UEs 110-1, 110-2, etc. (referred to collectively as “UEs 110” and individually as “UE 110” ) , a radio access network (RAN) 120, a core network (CN) 130, application servers 140, external networks 150, and satellites 160-1, 160-2, etc. (referred to collectively as “satellites 160” and individually as “satellite 160” ) . As shown, network 100 may include a non-terrestrial network (NTN) comprising one or more satellites 160 (e.g., of a global navigation satellite system (GNSS) ) in communication with UEs 110 and RAN 120.
[0021]The systems and devices of example network 100 may operate in accordance with one or more communication standards, such as 2nd generation (2G) , 3rd generation (3G) , 4th generation (4G) (e.g., long-term evolution (LTE) ) , and/or 5th generation (5G) (e.g., new radio  (NR) ) communication standards of the 3rd generation partnership project (3GPP) . Additionally, or alternatively, one or more of the systems and devices of network 100 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc. ) , institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN) , worldwide interoperability for microwave access (WiMAX) , etc. ) , and more.
[0022]As shown, UEs 110 may include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks) . Additionally, or alternatively, UEs 110 may include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 110 may include internet of things (IoT) devices (or IoT UEs) that may comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. Additionally, or alternatively, an IoT UE may utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN) ) , proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, IoT networks, and more. Depending on the scenario, an M2M or MTC exchange of data may be a machine-initiated exchange, and an IoT network may include interconnecting IoT UEs (which may include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections. In some scenarios, IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
[0023]UEs 110 may communicate and establish a connection with (e.g., be communicatively coupled) with RAN 120, which may involve one or more wireless channels 114-1 and 114-2, each of which may comprise a physical communications interface /layer. In some implementations, a UE may be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC) , where a multiple receive and transmit (Rx/Tx) capable UE may use resources provided by different network nodes (e.g., 122-1 and 122-2) that may be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G) . In such a scenario, one network node may operate as a master node (MN) and the other as the secondary node (SN) . The MN and SN may be connected via a network interface, and at least the MN may be connected to the CN 130. Additionally, at least one of the MN or the  SN may be operated with shared spectrum channel access, and functions specified for UE 110 can be used for an integrated access and backhaul mobile termination (IAB-MT) . Similar for UE 101, the IAB-MT may access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like. In some implementations, a base station (as described herein) may be an example of network nod 122.
[0024]As shown, UE 110 may also, or alternatively, connect to access point (AP) 116 via interface 118, which may include an air interface enabling UE 110 to communicatively couple with AP 116. AP 116 may comprise a wireless local area network (WLAN) , WLAN node, WLAN termination point, etc. The connection 1207 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 116 may comprise a wireless fidelityrouter or other AP. While not explicitly depicted in Fig. 1, AP 116 may be connected to another network (e.g., the Internet) without connecting to RAN 120 or CN 130. In some scenarios, UE 110, RAN 120, and AP 116 may be configured to utilize LTE-WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA may involve UE 110 in RRC_CONNECTED being configured by RAN 120 to utilize radio resources of LTE and WLAN. LWIP may involve UE 110 using WLAN radio resources (e.g., connection interface 118) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 118. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
[0025]RAN 120 may include one or more RAN nodes 122-1 and 122-2 (referred to collectively as RAN nodes 122, and individually as RAN node 122) that enable the connections 114-1 and 114-2 to be established between UEs 110 and RAN 120. RAN nodes 122 may include network access points configured to provide radio baseband functions for data and/or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc. ) . As examples therefore, a RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc. ) , a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB) , etc. ) . RAN nodes 122 may include a roadside unit (RSU) , a transmission reception point (TRxP or TRP) , and one or more other types of ground stations (e.g., terrestrial access points) . In some scenarios, RAN node 122 may be a dedicated physical device, such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like having smaller coverage areas, smaller user capacity, or higher bandwidth compared  to macrocells. As described below, in some implementations, satellites 160 may operate as bases stations (e.g., RAN nodes 122) with respect to UEs 110. As such, references herein to a base station, RAN node 122, etc., may involve implementations where the base station, RAN node 122, etc., is a terrestrial network node and also to implementation where the base station, RAN node 122, etc., is a non-terrestrial network node (e.g., satellite 160) .
[0026]Some or all of RAN nodes 120 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a centralized RAN (CRAN) and/or a virtual baseband unit pool (vBBUP) . In these implementations, the CRAN or vBBUP may implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers may be operated by the CRAN/vBBUP and other Layer 2 (L2) protocol entities may be operated by individual RAN nodes 122; a media access control (MAC) /physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC) , and MAC layers may be operated by the CRAN/vBBUP and the PHY layer may be operated by individual RAN nodes 122; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer may be operated by the CRAN/vBBUP and lower portions of the PHY layer may be operated by individual RAN nodes 122. This virtualized framework may allow freed-up processor cores of RAN nodes 122 to perform or execute other virtualized applications.
[0027]In some implementations, an individual RAN node 122 may represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual F1 interfaces. In such implementations, the gNB-DUs may include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs) , and the gNB-CU may be operated by a server (not shown) located in RAN 120 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN/vBBUP. Additionally, or alternatively, one or more of RAN nodes 120 may be next generation eNBs (i.e., gNBs) that may provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 110, and that may be connected to a 5G core network (5GC) 130 via an NG interface.
[0028]Any of the RAN nodes 122 may terminate an air interface protocol and may be the first point of contact for UEs 110. In some implementations, any of the RAN nodes 122 may fulfill various logical functions for the RAN 120 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 110 may be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 122 over a multicarrier  communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications) , although the scope of such implementations may not be limited in this regard. The OFDM signals may comprise a plurality of orthogonal subcarriers.
[0029]In some implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 122 to UEs 110, and uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block may comprise a collection of resource elements (REs) ; in the frequency domain, this may represent the smallest quantity of resources that currently may be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
[0030]Further, RAN nodes 122 may be configured to wirelessly communicate with UEs 110, and/or one another, over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band” ) , an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band” ) , or combination thereof. A licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band. A licensed spectrum may correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity) , whereas an unlicensed spectrum may correspond to one or more frequency bands that are not restricted for certain types of wireless activity. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium may depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc. ) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.
[0031]To operate in the unlicensed spectrum, UEs 110 and the RAN nodes 122 may operate using licensed assisted access (LAA) , eLAA, and/or feLAA mechanisms. In these implementations, UEs 110 and the RAN nodes 122 may perform one or more known medium-sensing operations or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
[0032]The LAA mechanisms may be built upon carrier aggregation (CA) technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a component carrier (CC) . In some cases, individual CCs may have a different bandwidth than other CCs. In time division duplex (TDD) systems, the number of CCs as well as the bandwidths of each CC may be the same for DL and UL. CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a primary component carrier (PCC) for both UL and DL, and may handle radio resource control (RRC) and non-access stratum (NAS) related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual secondary component carrier (SCC) for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require UE 110 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells” ) , and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.
[0033]The PDSCH may carry user data and higher layer signaling to UEs 110. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDCCH may also inform UEs 110 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 110-2 within a cell) may be performed at any of the RAN nodes 122 based on channel quality information fed back from any of UEs 110. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of UEs 110.
[0034]The PDCCH uses control channel elements (CCEs) to convey the control information, wherein a number of CCEs (e.g., 6 or the like) may consists of a resource element  groups (REGs) , where a REG is defined as a physical resource block (PRB) in an OFDM symbol. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching, for example. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, 8, or 16) .
[0035]Some implementations may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some implementations may utilize an extended (E) -PDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.
[0036]The RAN nodes 122 may be configured to communicate with one another via interface 123. In implementations where the system 100 is an LTE system, interface 123 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes 122 (e.g., two or more eNBs /gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 130, or between two eNBs connecting to an EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C) . The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface and may be used to communicate information about the delivery of user data between eNBs or gNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB) ; information about successful in sequence delivery of PDCP packet data units (PDUs) to a UE 110 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 110; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality (e.g., including context transfers from source to target eNBs, user plane transport control, etc. ) , load management functionality, and inter-cell interference coordination functionality.
[0037]As shown, RAN 120 may be connected (e.g., communicatively coupled) to CN 130. CN 130 may comprise a plurality of network elements 132, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 110) who are  connected to the CN 130 via the RAN 120. In some implementations, CN 130 may include an evolved packet core (EPC) , a 5G CN, and/or one or more additional or alternative types of CNs. The components of the CN 130 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) . In some implementations, network function virtualization (NFV) may be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below) . A logical instantiation of the CN 130 may be referred to as a network slice, and a logical instantiation of a portion of the CN 130 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems may be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
[0038]As shown, CN 130, application servers (ASs) 140, and external networks 150 may be connected to one another via interfaces 134, 136, and 138, which may include IP network interfaces. Application servers 140 may include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CM 130 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc. ) . Application server 140 may also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc. ) for UEs 110 via the CN 130. Similarly, external networks 150 may include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 110 of the network access to a variety of additional services, information, interconnectivity, and other network features.
[0039]As shown, example network 100 may include an NTN that may comprise one or more satellites 160-1 and 160-2 (collectively, “satellites 160” ) . Satellites 160 may be in communication with UEs 110 via service link or wireless interface 162 and/or RAN 120 via feeder links or wireless interfaces 164 (depicted individually as 164-1 and 164) . In some implementations, satellite 160 may operate as a passive or transparent network relay node regarding communications between UE 110 and the terrestrial network (e.g., RAN 120) . In some implementations, satellite 160 may operate as an active or regenerative network node such that  satellite 160 may operate as a base station to UEs 110 (e.g., as a gNB of RAN 120) regarding communications between UE 110 and RAN 120. In some implementations, satellites 160 may communicate with one another via a direct wireless interface (e.g., 166) or an indirect wireless interface (e.g., via RAN 120 using interfaces 164-1 and 164-2) .
[0040]Additionally, or alternatively, satellite 160 may include a GEO satellite, LEO satellite, or another type of satellite. Satellite 160 may also, or alternatively pertain to one or more satellite systems or architectures, such as a global navigation satellite system (GNSS) , global positioning system (GPS) , global navigation satellite system (GLONASS) , BeiDou navigation satellite system (BDS) , etc. In some implementations, satellites 160 may operate as bases stations (e.g., RAN nodes 122) with respect to UEs 110. As such, references herein to a base station, RAN node 122, etc., may involve implementations where the base station, RAN node 122, etc., is a terrestrial network node and implementation, where the base station, RAN node 122, etc., is a non-terrestrial network node (e.g., satellite 160) .
[0041]Fig. 2 is a diagram of an example 200 of a master cell group (MCG) 210 and a secondary cell group (SCG) 220 of a wireless communication network. An MCG may include a group of cells associated with a master node, comprising a primary cell (PCell) and one or more secondary cells (SCells) . An SCG may include a group of serving cells associated with a secondary node, comprising a primary cell of the secondary cell group (PSCell) and optionally one or more secondary cells (SCells) .
[0042]MCG 210 may be implemented by one or more base stations and may include one or more layers. Examples of such layers may include a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and multiple physical (PHY) layers. Each PHY layer may correspond to a different implementation of a cell with respect to UE 110. Additionally, or alternatively, the PHY layers may operate in combination (e.g., be managed, controlled by, etc. ) the PDCP, layer RL: C, layer, and MAC layers. In some implementations, one PHY layer 240 may operate as a primary cell (PCell) or a special cell (SpCell) and other PHY layers 242 and 244 may operate to secondary cells (SCells) to the PCell.
[0043]SCG 220 may include multiple layers as well, including an RLC layer, a MAC layer, and multiple PHY layers. SCG 220 may not include a PDCP layer, but instead may rely on the PDCP layer of MCG 210 via connection 230. Similar to the PHY layers of MCG 210, the PHY layers of SCG 220 may each function or operate as a cell with respect to UE 110. In some implementations, one PHY layer 250 may operate as a primary cell (PCell) to PHY layers 252 and 254 operating as secondary cells to the PCell of PHY layer 250. As such, a special cell  (SpCell) as described herein, may include a PCell of MCG 210 or a PCell of SCG 220. A scheduling secondary cell (sSCell) , as described herein, may include a secondary cell (SCell) to any SpCell, which may each reside in the same cell group or different cell groups. Further, while Fig. 2 includes only 2 cell groups, implementation discussed herein may be applied to multiple cell groups operating in synchronization or collaboration with one another to perform the techniques described herein. Furthermore, each cell group (e.g., MCG and/or SCG) may be implemented on one or more base station, and a cell group operating as either an MCG or SCG may change, and cells within a cell group (e.g., a SpCell, SCell, sSCell, etc. ) may be changed by activation, deactivation, dormancy, etc.
[0044]MCG 210 and SCG 220 may be involved in a dual connectivity scenario with UE 110, in which case a random access channel (RACH) procedure, and the like, may be directed to MCG 210. Additionally, MCG 210 and SCG 220 may each include a PCell (e.g., 240 and 250) , and a PCell may be referred to herein as a special cell or special primary cell, represented as SpCell. Further, a secondary cell (SCell) of either MCG 210 or SCG 220 may operate as a scheduling secondary cell (sSCell) configured to provide configuration, scheduling, activation, deactivation, and other functions or commands toward a SpCell of either MCG 210 or SCG 220. As such, a base station, a baseband processor of a base station, etc., may include a base station of MCG 210 and/or SCG 220 controlling, managing, enabling, etc., a sSCell, of either MCG 210 and/or SCG 220, and/or a SpCell of either MCG 210 and/or SCG 220, which may include additional SCells or SpCells within either MCG 210 and/or SCG 220.
[0045]Fig. 3 is a flowchart of an example process 300 for managing dynamic spectrum sharing (DSS) in one or more cell groups. Process 300 may be implemented by a base station comprising an SpCell and/or sSCell (e.g., of either MCG 210 or SCG 220) . For example, process 300 may be implemented by an sSCell implemented by a base station (which may be an example of RAN 120, described above with reference to Fig. 1) . In some implementations, some or all of process 300 may be performed by one or more other systems or devices, including one or more of the devices of Fig. 1. Additionally, process 300 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in Fig. 3. In some implementations, some or all of the operations of process 300 may be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 300. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or process depicted in Fig. 3.
[0046]As shown, process 300 may include receiving capability information and determining a DCI format and USS based on the capability information (block 310) . For example, a base  station may receive UE capability information, from UE 110. The capability information may indicate whether UE 110 is capable of receiving non-fallback DCI during a USS in either SpCell or sSCell. In some implementations, the UE capability information may also, or alternatively, indicate whether UE 110 is capable of receiving fallback DCI in either SpCell or sSCell. Additionally, or alternatively, the base station may determine, based on the capability information, a DCI format and USS for communicating with UE 110. In some implementations, the capacity information may inform the base station, which cells (e.g., SpCell and/or sSCell may be scheduled to send non-fallback DCI during a USS of UE 110. As such, as described herein, the capacity information may enable, cause, etc., the base station to determine, identify, configure, etc., cells for communicating the non-fallback DCI during a USS of UE 110.
[0047]Process 300 may also include indicating, during CCS involving SpCell and sSCell, the DCI format and USS to UE 110 (block 320) . For example, the base station may engage in CCS procedure involving SpCell and sSCell, which may also involve communications to UE 110. In some implementations, as part of the CCS procedure, the base station may indicate the DCI format and/or USS to UE 110. In some implementations, this may enable UE 110 to monitor an appropriate search space (e.g., the USS) in accordance with the DCI format used by the base station to communicate with UE 110.
[0048]Process 300 may include causing non-fallback DCI to be communicated to UE 110 based on the DCI format and USS (block 330) . For example, the base station may cause no-fallback DCI to be communicated to UE 110. In doing so, the base station may be operating as a SpCell and/or sSCell. The non-fallback DCI may be communicated in a manner consistent with the USS, such that UE 110 may be monitoring the USS when the non-fallback DCI is communicated. As described herein, the non-fallback DCI may enable UE 110 to communicate with the base station (e.g., SpCell and sSCell) in accordance with DCI or fallback DCI that might otherwise be used for enabling communication between UE 110 and the base station.
[0049]Process 300 may include configuring radio link monitoring (RLM) for a SpCell and/or sSCell (block 340) . Radio Link Monitoring (RLM) may include a procedure to monitor a quality level of a radio link, such as a physical downlink control channel (PDCCH) transmission in new radio (NR) . In some implementations, the base station may configure RLM for a SpCell and/or sSCell. For example, the base station may cause an RRC message to be communicated to the SpCell, sSCell, and/or UE 110, which may indicate whether a reference signal for RLM (e.g., a RadioLinkMonitoringRS element) is associated with the SpCell and/or the sSCell. In some implementations, this may be indicated by a particular RRC field or value, such as a ServCellIndex field or value.
[0050]In some implementations, when RLM reference signal (e.g., a RadioLinkMonitoringRS element) is not configured, UE 110 may use a reference signal provided for a transmission configuration indicator state for PDCCH reception in the SpCell and/or sSCell. Additionally, when UE 110 uses the RS provided for the active TCI state for PDCCH reception in both SpCell and sSCell, if a total number of reference signals exceeds a reference signal capacity or threshold of UE 110, UE 110 may select a reference signal based on a pre-determined reference signal priority. In some implementations, UE 110 may first select the PDCCH of the SpCell instead of the sSCell. Additionally, or alternatively, UE 110 may select search space sets in an order from a shortest monitoring periodicity, and if more than one CORESETs are associated with search space sets having the same monitoring periodicity, UE 110 may determine an order of the CORESET from a highest CORESET index, which may, e.g., be indicated to UE 110 by the base station during the CCS procedure, via an RRC message, etc.
[0051]Process 300 may include configuring beam failure recovery (BFR) for a SpCell and/or sSCell (block 350) . For example, a base station may configure UE to monitor reference signals for BFR from sSCell instead of, or in addition to, for example, the reference signals from SpCell. In some implementations, BFR may be configured using a BeamFailureRecoverySCellConfig IE of the SCell. In some implementations, BFR may be based on a list or configuration of candidate beams or reference signals of the SpCell and/or the sSCell, which may include an index (e.g., a ServCellIndex) introduced in a particular IE, such as a PRACH-ResourceDedicatedBFR configuration IE. In some implementations, BFR may be based on one or more recovery spaces of BFRPs (Beam Failure Request resPonse) and/or recoverySearchSpaceIds for the SpCell, the sSCell, or both the SpCell and sSCell.
[0052]Process 300 may include activating and/or deactivating the SpCell and/or sSCell (block 360) . For example, at some point, a base station may communicate an indication (e.g., a MAC CE) from of a change (e.g., activation or deactivation) of the SpCell and/or sSCell, and UE 110 may change the UE monitoring for DCI. For example, when sSCell is deactivated, UE 110 may switch from monitoring a USS of the sSCell to monitoring a USS of the SpCell. Similarly, the base station may cause the sSCell to enter a state of dormancy or transition back to an awake state. When USS with non-fallback DCI is configured both in sSCell and SpCell, if the sSCell is dormant, UE 110 may monitor USS with non-fallback DCI the on SpCell. Additionally, or alternatively, if the sSCell is woken up, UE 110 may monitor USS with non-fallback DCI configured on the sSCell, not configured on SpCell (if, for example, UE 110 does not support simultaneous SpCell and sSCell non-fallback DCI monitoring) . Depending on the implementations, the at least on SpCell, optionally on sSCell DCI that can trigger SCell  dormancy can be configured: only on SpCell, not on sSCell; either on SpCell or sSCell, but not both; or either on SpCell or sSCell or both. Additionally, or alternatively, DCI Format 2_6, DL DCI Format 1_1, UL DCI Format 0_1 may be used to enforce any one or combination of the configurations.
[0053]Fig. 4 is a diagram of an example 400 of slots for an SpCell and sSCell. As shown, timeline 410-1 of SpCell may include slots 420-1 with corresponding USS 430-1, 430-2, etc. Similarly, timeline 410-2 of sSCell may include slots 420-2, 420-3, etc., with corresponding USS 430-3, 430-4, etc. In some implementations, when CCS from sSCell to SpCell is configured, and UE 110 is configured to monitor USS with non-fallback DCI on both SpCell and sSCell, a base station (or other type of network device) may configure search spaces to ensure that in each slot. UE 110 is configured to monitor USS with non-fallback DCI on at most one of the SpCell or sSCell. Additionally, or alternatively, when the SpCell and sSCell have different subcarrier spacing (SCS) , the base station or other type of network device may configure a duration of a monitoring occasion (e.g., a slot with a USS) to determine a slot overlapping between slots of the SpCell and sSCell. Additionally, or alternatively, when the SpCell and sSCell have different subcarrier spacing (SCS) , the base station or other type of network device may determine slot overlapping based on which slot (e.g., between slots of the SpCell and sSCell) contains the monitoring occasion (e.g., the USS) .
[0054]Fig. 5 is a diagram of an example 500 of slots for an SpCell and sSCell. As shown, timeline 510-1 of SpCell may include slots 520-1 with corresponding USS 530-1, 530-2, etc. Similarly, timeline 510-2 of sSCell may include slots 520-2, 520-3, etc., with corresponding USS 530-3, 530-4, etc. In some implementations, when CCS from sSCell to SpCell is configured, and UE 110 is configured to monitor USS with non-fallback DCI on both SpCell and sSCell, a base station (or other type of network device) may configure search spaces to ensure that in each slot. UE 110 is configured to monitor USS with non-fallback DCI on at most one of the SpCell or sSCell. Additionally, or alternatively, when the SpCell and sSCell have different subcarrier spacing (SCS) , the base station or other type of network device may configure a duration of a monitoring occasion (e.g., a slot with a USS) to determine a slot overlapping between slots of the SpCell and sSCell.
[0055]Figs. 6 and 7 are diagram of example configurations of a cell groups (CG) 600 and 700. As shown, a CG 600 may include SpCell 610 and sSCell 620. SpCell 610 may be configured for USS regarding only non-fallback uplink (UL) DCI, which may correspond to certain DCI formats (e.g., DCI format 0_1, 0_2, etc. ) . sSCell 620 may be configured for USS regarding only non-fallback downlink (DL) DCI, which may correspond to certain DCI formats  (e.g., DCI format 1_1, 1_2, etc. ) . By contrast, in other implementations, a CG 700 may include SpCell 710 and sSCell 720, where SpCell 710 may be configured for USS regarding only non-fallback DL DCI, which may correspond to certain DCI formats (e.g., DCI format 1_1, 1_2, etc. ) , and sSCell 720 may be configured for USS regarding only non-fallback UL DCI, which may correspond to certain DCI formats (e.g., DCI format 0_1, 0_2, etc. ) .
[0056]Fig. 8 is a diagram of an example configuration of a CG 800. As shown, a CG 800 may include SpCell 810 and sSCell 820 may each include one or more information fields or information elements. Examples of such fields or elements may include a serving cell configuration (ServignCellConfig) field, a DL bandwidth part (BWP) (BWP-DownlinkDedicated) field, a PDCCH configuration PDCCH-Config) field, and a search spaces to add mod list (searchSpacesToAddModList) field. In some implementations, when CCS from sSCell to SpCell is configured, a search space may be configured per DL BWP per cell search. In some implementations, when CCS from sSCell to SpCell is configured, a CCS configuration (e.g., CrossCarrierSchedulingConfig) information element for the SpCell may indicate whether the SpCell may be configured (e.g., by the sSCell) , may indicate whether the SpCell has already been configured (e.g., by the sSCell) , may indicate whether the SpCell can be configured to schedule any other cell, may include a carrier indicator field (CIF-presence ) to indicate a grant or assignment for the cell, etc. In some implementations, a search space configuration (SearchSpace information element) of the SpCell may include configurable fields, which may indicate the PDCCH monitoring occasions for the SpCell as both the scheduling cell and the scheduled cell. In some implementations, the search space configuration may also include other fields, such as a nrofCandidates field, for the sSCell as the scheduling cell and for the SpCell as the scheduled cell.
[0057]Fig. 9 is a diagram of an example of deactivating a sSCell. As shown, a timeline 910 for the sSCell and a timeline 920 for the SpCell may include USS periods 930, and 940, respectively. UE 110 may monitor USS periods 930 of the sSCell without monitoring USS periods 940 of the SpCell. At some point, the sSCell may be deactivated, which may include a procedure that involves sending a media access control (MAC) control element (CE) 950 to UE 110 indicating that the sSCell is to be deactivated. In response, UE 110 may send a HARQ acknowledgement message 960 for the corresponding MAC CE and may switch from monitoring the USS 930 of the sSCell to monitoring the USS 940 of the SpCell after a specified period of time (e.g., 3 milliseconds) from sending the acknowledgement message.
[0058]Fig. 10 is a diagram of an example of activating a sSCell. As shown, a timeline 1010 for the sSCell and a timeline 1020 for the SpCell may include USS periods 1030, and 1040,  respectively. UE 110 may monitor USS periods 1040 of the SpCell without monitoring USS periods 1030 of the SpCell. At some point, the sSCell may be activated, which may include a procedure that involves sending a MAC CE 1050 to UE 110 indicating that the sSCell is to be activated. In response, UE 110 may send a HARQ acknowledgement message 1060 for the corresponding MAC CE 1050 and may switch from monitoring the USS 1040 of the SpCell to monitoring the USS 1030 of the sSCell after a specified period of time (e.g., 3 milliseconds) from sending the acknowledgement message.
[0059]Fig. 11 is a diagram of an example process 1100 for monitoring search spaces for downlink control information (DCI) . Process 1100 may be implemented by UE 110, which may be in communication with an SpCell and/or sSCell (e.g., of either MCG 210 or SCG 220) . In some implementations, some or all of process 1100 may be performed by one or more other systems or devices, including one or more of the devices of Fig. 1. Additionally, process 1100 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in Fig. 11. In some implementations, some or all of the operations of process 1100 may be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1100. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or process depicted in Fig. 11.
[0060]As shown, process 1100 may include communicating capability information regarding USS non-fallback DCI (block 1110) . For example, UE 110 may indicate, to a base station, whether UE 110 is capable of receiving non-fallback DCI in a USS in either SpCell or sSCell. Additionally, or alternatively, UE 110 may indicate, to the base station, whether UE 110 is capable of receiving fallback DCI in a USS in either SpCell or sSCell.
[0061]Process 1100 may also include receiving information indicating a DCI format for receiving DCI and/or a corresponding USS for an SpCell and/or sSCell (block 1120) . For example, UE 110 may receive, from the base station, an indication of a DCI format for the SpCell and/or sSCell. In some implementations, the information may indicate a USS for monitoring for non-fallback DCI. In some implementations, this information by received from the base station via another communication or procedure.
[0062]Process 1100 may include monitoring a search space for DCI information (block 1130) . For example, UE 110 may monitor a USS for non-fallback DCI in accordance with a DCI format, and/or another type of information (e.g., specifying the SpCell and/or sSCell) , received from the base station. In some implementation, UE 110 may also, or alternatively, monitor for fallback DCI (e.g., DCI transmitted at a standardized, pre-selected, default, or pre-specified time and place) .
[0063]Process 1100 may also include updating monitoring based on cell activation, dormancy, RLM configurations, and/or BFR configuration (block 1140) . For example, at some point, UE 110 may receive an indication (e.g., a MAC CE) from the base station of a change (e.g., activation or deactivation) of the SpCell and/or sSCell, and UE 110 may change the UE monitoring for DCI. For example, when sSCell is deactivated, UE 110 may switch from monitoring a USS of the sSCell to monitoring a USS of the SpCell. Similarly, when UE 110 receives an indication of an sSCell being activated, UE 110 may switch from monitoring the USS of the SpCell to monitoring the USS of the sSCell. Additionally, or alternatively, UE 110 may similarly update USS monitoring based on an indication that the SpCell and/or sSCell has entered into a dormant state of operation or an awake state of operation.
[0064]In some implementations, when RLM reference signal (e.g., a RadioLinkMonitoringRS element) is not configured, UE 110 may use a reference signal provided for a transmission configuration indicator state for PDCCH reception in the SpCell and/or sSCell. Additionally, when UE 110 uses the RS provided for the active TCI state for PDCCH reception in both SpCell and sSCell, if a total number of reference signals exceeds a reference signal capacity or threshold of UE 110, UE 110 may select a reference signal based on a pre-determined reference signal priority. In some implementations, UE 110 may first select the PDCCH of the SpCell instead of the sSCell. Additionally, or alternatively, UE 110 may select search space sets in an order from a shortest monitoring periodicity, and if more than one CORESETs are associated with search space sets having the same monitoring periodicity, UE 110 may determine an order of the CORESET from a highest CORESET index, which may, e.g., be indicated to UE 110 by the base station during the CCS procedure, via an RRC message, etc.
[0065]In some implementations, UE 110 may be configured to perform BFR based on the reference signals transmitted from instead of, or in addition to, for example, the reference signal transmitted from SpCell. In some implementations, UE 110 may be configured using a BeamFailureRecoverySCellConfig IE of the SCell. In some implementations, UE 110 may be configured to perform BFR based on a list or configuration of candidate beams or reference signals of the SpCell and/or the sSCell, which may include UE 110 receiving an index (e.g., a ServCellIndex) introduced in a particular IE, such as a PRACH-ResourceDedicatedBFR configuration IE. In some implementations, UE 110 may be configured to perform BFR on a SpCell based on one or more recovery spaces of BFRPs (Beam Failure Request resPonse) and/or recoverySearchSpaceIds for the SpCell, the sSCell, or both the SpCell and sSCell.
[0066]Fig. 12 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 1200 can include  application circuitry 1202, baseband circuitry 1204, Radio Frequency (RF) circuitry 1206, front-end module (FEM) circuitry 1208, one or more antennas 1210, and power management circuitry (PMC) 1212 coupled together at least as shown. The components of the illustrated device 1200 can be included in a UE or a RAN node. In some implementations, the device 1200 can include fewer elements (e.g., a RAN node may not utilize application circuitry 1202, and instead include a processor/controller to process IP data received from a CN such as 5GC 130 or an Evolved Packet Core (EPC) ) . In some implementations, the device 1200 can include additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 1200, etc. ) , or input/output (I/O) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
[0067]The application circuitry 1202 can include one or more application processors. For example, the application circuitry 1202 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor (s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) . The processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1200. In some implementations, processors of application circuitry 1202 can process IP data packets received from an EPC.
[0068]The baseband circuitry 1204 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1204 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1206 and to generate baseband signals for a transmit signal path of the RF circuitry 1206. Baseband processing circuity 1204 can interface with the application circuitry 1202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1206. For example, in some implementations, the baseband circuitry 1204 can include a third generation (3G) baseband processor 1204A, a fourth generation (4G) baseband processor 1204B, a fifth generation (5G) baseband processor 1204C, or other baseband processor (s) 1204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G) , sixth generation (6G) , etc. ) . The baseband circuitry 1204 (e.g., one or more of baseband processors 1204A-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1206. In other implementations, some or all of the functionality of baseband processors  1204A-D can be included in modules stored in the memory 1204G and executed via a Central Processing Unit (CPU) 1204E. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some implementations, modulation/demodulation circuitry of the baseband circuitry 1204 can include Fast-Fourier Transform (FFT) , precoding, or constellation mapping/demapping functionality. In some implementations, encoding/decoding circuitry of the baseband circuitry 1204 can include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Implementations of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.
[0069]In some implementations, the baseband circuitry 1204 can include one or more audio digital signal processor (s) (DSP) 1204F. The audio DSP (s) 1204F can include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitry 1204 and the application circuitry 1202 can be implemented together such as, for example, on a system on a chip (SOC) .
[0070]In some implementations, the baseband circuitry 1204 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 1204 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) , etc. Implementations in which the baseband circuitry 1204 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.
[0071]RF circuitry 1206 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, the RF circuitry 1206 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1206 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 1208 and provide baseband signals to the baseband circuitry 1204. RF circuitry 1206 can also include a transmit signal path which can include circuitry to up-convert baseband signals  provided by the baseband circuitry 1204 and provide RF output signals to the FEM circuitry 1208 for transmission.
[0072]In some implementations, the receive signal path of the RF circuitry 1206 can include mixer circuitry 1206A, amplifier circuitry 1206B and filter circuitry 1206C. In some implementations, the transmit signal path of the RF circuitry 1206 can include filter circuitry 1206C and mixer circuitry 1206A. RF circuitry 1206 can also include synthesizer circuitry 1206d for synthesizing a frequency for use by the mixer circuitry 1206A of the receive signal path and the transmit signal path. In some implementations, the mixer circuitry 1206A of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 1208 based on the synthesized frequency provided by synthesizer circuitry 1206D. The amplifier circuitry 1206B can be configured to amplify the down-converted signals and the filter circuitry 1206C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry 1204 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this is not a requirement. In some implementations, mixer circuitry 1206A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.
[0073]In some implementations, the mixer circuitry 1206A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1206D to generate RF output signals for the FEM circuitry 1208. The baseband signals can be provided by the baseband circuitry 1204 and can be filtered by filter circuitry 1206c.
[0074]In some implementations, the mixer circuitry 1206A of the receive signal path and the mixer circuitry 1206A of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and upconversion, respectively. In some implementations, the mixer circuitry 1206A of the receive signal path and the mixer circuitry 1206A of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection) . In some implementations, the mixer circuitry 1206A of the receive signal path and the mixer circuitry`1206A can be arranged for direct downconversion and direct upconversion, respectively. In some implementations, the mixer circuitry 1206A of the receive signal path and the mixer circuitry 1206A of the transmit signal path can be configured for super-heterodyne operation.
[0075]In some implementations, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternate implementations, the RF circuitry 1206 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1204 can include a digital baseband interface to communicate with the RF circuitry 1206.
[0076]In some dual-mode implementations, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect.
[0077]In some implementations, the synthesizer circuitry 1206d can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 1206d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
[0078]The synthesizer circuitry 1206d can be configured to synthesize an output frequency for use by the mixer circuitry 1206A of the RF circuitry 1206 based on a frequency input and a divider control input. In some implementations, the synthesizer circuitry 1206d can be a fractional N/N+1 synthesizer.
[0079]In some implementations, frequency input can be provided by a voltage controlled oscillator (VCO) , although that is not a requirement. Divider control input can be provided by either the baseband circuitry 1204 or the applications processor 1202 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 1202.
[0080]Synthesizer circuitry 1206d of the RF circuitry 1206 can include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA) . In some implementations, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0081]In some implementations, synthesizer circuitry 1206d can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO) . In some implementations, the RF circuitry 1206 can include an IQ/polar converter.
[0082]FEM circuitry 1208 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 1210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1206 for further processing. FEM circuitry 1208 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 1206 for transmission by one or more of the one or more antennas 1210. In various implementations, the amplification through the transmit or receive signal paths can be done solely in the RF circuitry 1206, solely in the FEM 1208, or in both the RF circuitry 1206 and the FEM 1208.
[0083]In some implementations, the FEM circuitry 1208 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1206) . The transmit signal path of the FEM circuitry 1208 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1206) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1210) .
[0084]In some implementations, the PMC 1212 can manage power provided to the baseband circuitry 1204. In particular, the PMC 1212 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 1212 can often be included when the device 1200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 1212 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
[0085]While Fig. 12 shows the PMC 1212 coupled only with the baseband circuitry 1204. However, in other implementations, the PMC 1212 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1202, RF circuitry 1206, or FEM 1208.
[0086]In some implementations, the PMC 1212 can control, or otherwise be part of, various power saving mechanisms of the device 1200. For example, if the device 1200 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1200 can power down for brief intervals of time and thus save power.
[0087]If there is no data traffic activity for an extended period of time, then the device 1200 can transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1200 may not receive data in this state; in order to receive data, it can transition back to RRC_Connected state.
[0089]Processors of the application circuitry 1202 and processors of the baseband circuitry 1204 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1204, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1204 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) . As referred to herein, Layer 3 can comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
[0090]Fig. 13 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein. As discussed above, the baseband circuitry 1204 of Fig. 12 can comprise processors 1204A-1204E and a memory 1204G utilized by said processors. Each of the processors 1204A-1204E can include a memory interface, 1304A-1304E, respectively, to send/receive data to/from the memory 1204G.
[0091]The baseband circuitry 1204 can further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1312 (e.g., an  interface to send/receive data to/from memory external to the baseband circuitry 1204) , an application circuitry interface 1314 (e.g., an interface to send/receive data to/from the application circuitry 1202 of Fig. 12) , an RF circuitry interface 1316 (e.g., an interface to send/receive data to/from RF circuitry 1206 of Fig. 12) , a wireless hardware connectivity interface 1318 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, components (e.g., Low Energy) , components, and other communication components) , and a power management interface 1320 (e.g., an interface to send/receive power or control signals to/from the PMC `1212) .
[0092]Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor , etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
[0093]In example 1, a baseband processor of a base station may comprise one or more processors configured to: receive, from a user equipment (UE) , capability information indicating which cell can be configured to schedule non-fallback downlink control information (DCI) in a UE-specific search space (USS) for special cell (SpCell) scheduling; determine, based on the capability information, a DCI format and USS for communicating non-fallback DCI to the UE; indicate, during cross carrier scheduling (CCS) involving the (SpCell) and a scheduling special cell (sSCell) , the DCI format and the USS to the UE; and cause the non-fallback DCI to be communicated to the UE in accordance with the DCI format and the USS.
[0094]In example 2, when the UE supports USS with non-fallback DCI in both the SpCell and the sSCell, both the SpCell and the sSCell are configured to communicate the non-fallback DCI in the USS, and when the UE does not support USS with non-fallback DCI in both SpCell and sSCell, only the sSCell is configured to communicate the non-fallback DCI in the USS. In example 3, the capability information further indicates whether the UE supports monitoring, in a same slot, the USS with non-fallback DCI from the SpCell and the sSCell, when the UE supports the monitoring of the SpCell and the sSCell, in the same slot, both the SpCell and the sSCell are configured to communicate the non-fallback DCI, and when the UE does not support the monitoring of the SpCell and the sSCell, in the same slot, only one of the SpCell and the sSCell is configured to communicate the non-fallback DCI.
[0095]In example 4, when the UE supports the monitoring of the SpCell and the sSCell, and both the SpCell and the sSCell are configured to communicate the non-fallback DCI, the USS is configured to cause the UE to monitor for the non-fallback DCI by alternating between slots of the SpCell or the sSCell. In example 5, when the SpCell and sSCell have different subcarrier spacing (SCS) , slot overlap, between slots of the SpCell and the sSCell, is determined based on a duration of a monitoring occasion of the USS. In example 6, when the SpCell and sSCell have different subcarrier spacing (SCS) , slot overlap, between slots of the SpCell and the sSCell, is determined based on slots including monitoring occasions of the USS.
[0096]In example 7, when the UE supports the monitoring of the SpCell and the sSCell, and both the SpCell and the sSCell are configured to communicate the non-fallback DCI, the USS is configured so that the SpCell is only associated with downlink (DL) DCI and the sSCell is only associated with an uplink (UL) DCI, or the USS is configured so that the SpCell is only associated with the UL DCI and the sSCell is only associated with the DL DCI. In example 8, the one or more processors is further configured to: activate USS with non-fallback DCI monitoring for at least one of the SpCell or the sSCell, and deactivate the USS with non-fallback DCI monitoring for at least one of the SpCell or the sSCell. In example 9, activation of the USS with non-fallback DCI monitoring on one cell automatically deactivates the USS with non-fallback DCI monitoring active on any other cells. In example 10, activation or deactivation of the USS with non-fallback DCI monitoring for the SpCell or the sSCell involves a communication, regarding the activation or deactivation, to be communicated to the UE, the communication comprising at least one of: a radio resource control (RRC) message; a media access control (MAC) control element (CE) ; or DCI.
[0097]In example 11, the one or more processors is further configured to: receive, from a user equipment (UE) , capability information indicating whether the UE supports USS with fallback DCI. In example 12, the SpCell is configured to communicate the fallback DCI but not the sSCell. In example 13, when both the SpCell and the sSCell are configured to communicate the fallback DCI, the UE is configured to monitor only one of the SpCell or the sSCell. In example 14, when both the SpCell and the sSCell are configured to communicate the fallback DCI, the SpCell is configured to communicate downlink (DL) DCI and the sSCell is configured to communicate uplink (UL) DCI, or the SpCell is configured to communicate the UL DCI and the sSCell is configured to communicate DL DCI.
[0098]In example 15, when only one of the SpCell or the sSCell is activated to communicate fallback DCI to the UE, a communication regarding the activation, is communicated to the UE, via at least one of: a radio resource control (RRC) message; a media  access control (MAC) control element (CE) ; or DCI. In example 16, the USS is configured to indicate fallback DCI being from the sSCell or the SpCell. In example 17, a physical downlink control channel (PDCCH) of the USS is configured to indicate fallback DCI being from the sSCell or the SpCell. In example 18, the CCS of the sSCell and SpCell includes a CCS information element IE configured by the network to the UE. In example 19, when CCS of the sSCell to the SpCell is performed, the USS is configured on a per-DL bandwidth part (BWP) basis for each scheduling cell.
[0099]In example 20, when CCS of the sSCell to the SpCell is performed, the USS of the SpCell, the sSCell, or each of the SpCell and sSCell is configured with an information element (IE) indicating a PDCCH monitoring occasion for the USS. In example 21, the one or more processors is further configured to: cause the SpCell or the sSCell to enter a dormant state from an active state and cause the SpCell or the sSCell to enter an active state from a dormant state. In example 22, the one or more processors is further configured to: prior to causing the sSCell to enter the dormant state, verify at least one of: dormancy of the sSCell is permitted; the non-fallback DCI is configured on at least the SpCell; or DCI format 2_6 is not configured on the sSCell only. In example 23, radio link monitoring (RLM) is configured, via radio resource control (RRC) , in at least one of the SpCell or sSCell.
[0100]In example 24, radio link monitoring (RLM) reference signals are not configured in the SpCell or sSCell, reference signals (RS) is provided to be used by the UE, for active transmission configuration indicators (TCIs) for PDCCH reception in at least one of the SpCell or sSCell are used for RLM. In example 25, when the number of RS of active TCIs exceeds a capability of the UE, the UE selects RSs based on the following order: 1) selecting RSs of the PDCCH of the SpCell before RSs of the PDCCHs of the sSCell; 2) selecting search space sets in an order from a shortest monitoring periodicity to longer monitoring periodicity; 3) selecting search spaces with higher CORESET indexes before search spaces with lower CORESET indexes.
[0101]In example 26, when the sSCell configures the SpCell for beam failure recovery (BFR) during the CCS, and configuration of the SpCell for BFR includes a reference signal (RS) for BFR in at least one of the SpCell, the sSCell, or both the SpCell and sSCell. In example 27, when the sSCell configures the SpCell for beam failure recovery (BFR) during the CCS, and configuration of the SpCell for BFR includes indicating a recovery search space identifier for BFR in at least one of the SpCell, the sSCell, or both the SpCell and sSCell. In example 28, when the sSCell configures the SpCell for beam failure recovery (BFR) during the CCS, and configuration of the SpCell for BFR includes indicating an additional search space identifier for  BFR in at least one of the SpCell, the sSCell, or both the SpCell and sSCell. In example 29, when the sSCell configures the SpCell during the CSS, the sSCell and SpCell are configured as being part of a same cell group. In example 30, bandwidth part (BWP) switching on the SpCell is triggered by at least one of: the DCI scheduled in the sSCell, or the DCI scheduled in the SpCell.
[0102]In example 31, a baseband processor of a User Equipment (UE) may comprise: one or more processors configured to: communicate, to a base station, capability information indicating which cell can be configured to schedule non-fallback downlink control information (DCI) in a UE-specific search space (USS) for special cell (SpCell) scheduling; receive, based on the capability information and during a cross carrier scheduling (CCS) procedure involving a special cell (SpCell) and a scheduling special cell (sSCell) , a downlink control information (DCI) format and the USS; and monitor, based on the DCI format, the USS for the non-fallback DCI.
[0103]In example 32, the one or more processors are configured to monitor for the non-fallback DCI on both the SpCell and the sSCell simultaneously. In example 33, the one or more processors are configured to monitor for fallback DCI on the SpCell when non-fallback DCI is only configured on the sSCell and the sSCell is deactivated or put to dormant. In example 34, the one or more processors are configured to monitor for the non-fallback DCI on the sSCell when non-fallback DCI is configured on both the sSCell and the sSCell, and the sSCell is active. In example 35, the one or more processors are configured to: detect activation or deactivation of the sSCell; when the sSCell is activated, begin monitoring the USS of the sSCell after a predetermine interval measured from acknowledging the activation of the sSCell; when the sSCell is deactivated, stop monitoring the USS of the SpCell after the predetermine interval measured from acknowledging the activation of the sSCell.
[0104]In example 36, a base station substantially as shown and described herein. In example 37, a computer-readable medium, of a base station, substantially as shown and described. In example 38, a method, performed by a base station, substantially as shown and described. In example 39, a User Equipment (UE) substantially as shown and described. In example 40, a computer-readable medium, of a User Equipment (UE) , substantially as shown and described. In example 41, a method, performed by a User Equipment (UE) , substantially as shown and described.
[0105]The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.
[0106]In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.
[0107]In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc. ) , the terms (including a reference to a “means” ) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent) , even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.
[0108]As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or” . That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including” , “includes” , “having” , “has” , “with” , or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising. ” Additionally, in situations wherein one or more numbered items are  discussed (e.g., a “first X” , a “second X” , etc. ) , in general the one or more numbered items can be distinct or they can be the same, although in some situations the context may indicate that they are distinct or that they are the same.

中文:
[0002]当无线网络内移动设备的数量以及对移动数据流量的需求不断增加时,对系统要求和架构进行改变,以更好地解决当前和预期的需求。例如,可以开发一些无线通信网络以实现第五代(5G)或新空口(NR)技术、第六代(6G)技术等。这种技术的一个方面包括解决如何能够将无线设备的无线资源分配给用户装备(UE)和基站(该基站可以包括一个或多个小区)之间的通信。
[0003]通过附图的详细描述和附图将容易理解和实现本公开。相同的附图标记可以指定相同的特征和结构元件。附图和对应的描述被提供为本公开的方面、具体实施等的非限制性示例,并且对“一”或“一个”方面、具体实施等的引用可能不一定指相同的方面、具体实施等,并且可以表示至少一个、一个或多个等。
[0004]图1是根据本文所述的一个或多个具体实施的示例性网络的图。
[0005]图2是无线通信网络的主小区组(MCG)和辅小区组(SCG)的图。
[0006]图3是用于管理一个或多个小区组中的动态频谱共享(DSS)的示例性过程的流程图。
[0007]图4至图5是沿时间线的特殊主小区(SpCell)和特殊调度小区(sSCell)的示例性时隙的图。
[0008]图6和图7是小区组(CG)的示例性配置的图。
[0009]图8是CG的示例性配置的图。
[0010]图9是去激活sSCell的示例的图。
[0011]图10是激活sSCell的示例的图。
[0012]图11是用于监测下行链路控制信息(DCI)的搜索空间的示例性过程的图。
[0013]图12是根据本文所述的一个或多个具体实施的设备的部件的示例的图。
[0014]图13是根据本文所述的一个或多个具体实施的基带电路的示例性接口的图。
[0015]以下具体实施方式涉及附图。不同附图中的相同附图标号可以标识相同或类似的特征、元件、操作等。另外,本公开不限于以下描述,因为可以利用其他具体实施,并且在不背离本公开的范围的情况下进行结构或逻辑改变。
[0016]移动通信网络可以包括一种或多种类型和/或几代无线通信网络,诸如第4代(4G)(例如,长期演进(LTE))网络、第5代(5G)或新空口(NR)网络等。此类网络可以包括彼此无线通信的用户装备(UE)和基站。在一些具体实施中,网络可以同时实现多于一种类型的网络技术(例如,4G和5G),使得UE可以在基于4G技术或5G技术的网络内操作。此类网络的一个方面可包括动态频谱共享(DSS)。DSS可包括一种技术,其中无线通信的类似特征(例如,子载波间隔、时域结构等)可以用于4G或5G技术,使得UE和基站能够在相同的网络中并且经由相同的无线电频谱彼此通信。然而,虽然当前可用的DSS技术可以同时实现4G和5G技术(例如,使用相同的网络和无线电频谱),但当前的DSS技术包括某些限制。
[0017]例如,当前的DSS技术可由于某些4G构造和具体实施而限制5G具体实施。在一个示例中,由于来自LTE的小区参考信号(CRS)传输,当前的DSS技术(例如,4G或LTE技术)可限制5G。例如,在LTE中,当实施1或2端口CRS时,CRS可占用符号0、4、7和11,当实施4端口CRS时,CRS可占用符号0、1、4、7、8和11。因此,当前的DSS技术可放弃5G技术带来的益处、效率和灵活性,这限制了5G控制资源集(例如,CORESET)配置的符号数量、频率和时间位置。
[0018]另外,当前的4G或LTE技术可在跨载波调度(CCS)方面限制5G具体实施(例如,不同组的小区之间没有调度,主小区仅由其自身调度,每个被调度小区仅具有能够经由无线电资源控制(RRC)消息配置的一个调度小区等)。当前的4G或LTE技术可在下行链路控制信息(DCI)方面进一步限制5G具体实施。例如,4G或LTE技术可以将5G DCI限制为某些DCI格式(例如,用于回退DCI的LTE的DCI格式0_0、1_0等)。类似地,当前的4G或LTE技术可施加某些搜索空间限制,诸如用于回退DCI的公共搜索空间(CSS)限制。当前的4G或LTE技术可在小区分组、小区调度、小区激活和去激活、小区休眠和唤醒等方面进一步限制5G具体实施。例如,当前的4G或LTE技术可能无法提供足够的小区激活和去激活、小区休眠和唤醒等。
[0019]本文所述的技术可以包括对上述限制的解决方案。在一些具体实施中,可以为DSS提供特殊调度小区(sSCell)。该sSCell可以被配置为调度主小区组(MCG)的主小区或辅小区组(SCG)的主小区。此类主小区在本文中可被称为特殊小区或SpCell。在一些具体实施中,sSCell可以被激活和/或去激活,进入或退出休眠状态,并且可以提供无线电链路监测(RLM)、波束故障恢复(BFR)和小区分组参数。本文所述的技术可以包括用于配置具有非回退DCI的UE特定搜索空间(USS)、具有回退DCI的USS,以及用于DSS增强的整体搜索空间的解决方案。
[0020]图1是根据本文所述的一个或多个具体实施的示例性网络100。示例性网络100可包括UE 110-1、110-2等(统称为“(多个UE 110”并且单独称为“UE 110”)、无线电接入网络(RAN)120、核心网络(CN)130、应用服务器140、外部网络150和卫星160-1、160-2等(统称为“多个卫星160”,单独称为“卫星160”)。如图所示,网络100可以包括非地面网络(NTN),该NTN包括与UE 110和RAN 120通信的(例如,全球导航卫星系统(GNSS)的)一个或多个卫星160。
[0021]示例性网络100的系统和设备可以根据一个或多个通信标准,诸如第3代合作伙伴项目(3GPP)的第2代(2G)、第3代(3G)、第4代(4G)(例如,长期演进(LTE)),以及/或者第5代(5G)(例如,新空口(NR))通信标准来操作。另外或另选地,网络100的系统和设备中的一个或多个系统和设备可以根据本文所讨论的其他通信标准和协议来操作,包括未来版本或几代3GPP标准(例如,第六代(6G)标准、第七代(7G)标准等)、电气和电子工程师协会(IEEE)标准(例如,无线城域网(WMAN)、全球微波接入互操作性(WiMAX)等),等等。
[0022]如图所示,UE 110可以包括智能电话(例如,能够连接到一个或多个无线通信网络的手持式触摸屏移动计算设备)。另外或另选地,UE 110可以包括能够进行无线通信的其他类型的移动或非移动计算设备,诸如个人数据助理(PDA)、寻呼机、膝上型计算机、台式计算机、无线电话等。在一些具体实施中,UE 110可以包括物联网(IoT)设备(或IoT UE),IoT UE可以包括被设计用于利用短暂UE连接的低功率IoT应用程序的网络接入层。另外或另选地,IoT UE可以利用一种或多种类型的技术,诸如机器对机器(M2M)通信或机器类型通信(MTC)(例如,经由公共陆地移动网络(PLMN)与MTC服务器或其他设备交换数据),基于邻近的服务(ProSe)或设备到设备(D2D)通信、传感器网络、IoT网络等。根据场景的不同,M2M或MTC数据交换可以是机器发起的交换,IoT网络可包括互连的IoT UE(可包括互联网基础设施内唯一可标识的嵌入式计算设备)和短时连接。在一些场景中,IoT UE可执行后台应用程序(例如,保持活动消息、状态更新等)以促进IoT网络的连接。
[0023]UE 110可以与RAN 120通信并且建立连接(例如,通信地耦接),该RAN可涉及一个或多个无线信道114-1和114-2,其中每一个无线信道可以包括物理通信接口/层。在一些具体实施中,UE可以配置有双连接(DC)作为多无线电接入技术(多RAT)或多无线电双连接(MR-DC),其中能够进行多个接收和发射(Rx/Tx)的UE可以使用由可经由非理想回程连接的不同网络节点(例如,122-1和122-2)提供的资源(例如,其中一个网络节点提供NR接入,并且另一个网络节点为LTE提供E-UTRA或为5G提供NR接入)。在这种情况下,一个网络节点可以作为主节点(MN)操作,并且另一个作为辅助节点(SN)操作。MN和SN可经由网络接口连接,并且至少MN可以连接到CN 130。另外,MN或SN中的至少一者可以用共享频谱信道接入来操作,并且为UE 110指定的功能可以用于集成接入和回程移动终端(IAB-MT)。类似于UE 101,IAB-MT可使用一个网络节点或使用具有增强型双连接(EN-DC)架构、新空口双连接(NR-DC)架构等的两个不同节点来接入网络。在一些具体实施中,基站(如本文所述)可以是网络节点122的示例。
[0024]如图所示,UE 110还可以或另选地经由接口118连接到接入点(AP)116,该接口可以包括使UE 110能够与AP 116通信地耦接的空中接口。AP 116可以包括无线局域网(WLAN)、WLAN节点、WLAN终端点等。连接1207可以包括本地无线连接,诸如符合任何IEEE702.11协议的连接,并且AP 116可以包括无线保真路由器或其他AP。虽然图1中未明确描绘,但AP 116可以连接到另一网络(例如,互联网)而不连接到RAN 120或CN 130。在一些场景中,UE 110、RAN 120和AP 116可以被配置为利用LTE-WLAN聚合(LWA)技术或LTEWLAN与IPsec隧道(LWIP)的无线电级别集成技术。LWA可涉及处于RRC_CONNECTED中的UE110被RAN 120配置为利用LTE和WLAN的无线电资源。LWIP可涉及UE 110经由IPsec协议隧道使用WLAN无线电资源(例如,连接接口118)来认证和加密经由连接接口118传送的分组(例如,互联网协议(IP)分组)。IPsec隧道传送可包括封装整个原始IP分组并添加新的分组头,从而保护IP分组的原始头。
[0025]RAN 120可包括一个或多个RAN节点122-1和122-2(统称为多个RAN节点122,并且单独称为RAN节点122),使得能够在UE 110和RAN 120之间建立连接114-1和114-2。RAN节点122可包括网络接入点,这些网络接入点被配置为基于本文所述的通信技术中的一种或多种(例如,2G、3G、4G、5G、WiFi等)提供用于用户和网络之间的数据和/或语音连接的无线电基带功能。因此,作为示例,RAN节点可以是E-UTRAN节点B(例如,增强型节点B、eNodeB、eNB、4G基站等)、下一代基站(例如,5G基站、NR基站、下一代eNB(gNB)等)。RAN节点122可以包括路边单元(RSU)、发射接收点(TRxP或TRP)以及一种或多种其他类型的地面站(例如,地面接入点)。在一些场景中,RAN节点122可以是专用物理设备,诸如宏小区基站和/或用于提供与宏小区相比具有较小覆盖区域、较小用户容量或较高带宽的毫微微小区、微微小区或其他类似小区的低功率(LP)基站。如下所述,在一些具体实施中,卫星160可以作为相对于UE110的基站(例如,RAN节点122)来操作。因此,本文对基站、RAN节点122等的引用可涉及其中基站、RAN节点122等是地面网络节点的具体实施,以及基站、RAN节点122等是非地面网络节点(例如,卫星160)的具体实施。
[0026]RAN节点120中的一些或全部可被实施为作为虚拟网络的一部分在服务器计算机上运行的一个或多个软件实体,该虚拟网络可被称为集中式RAN(CRAN)和/或虚拟基带单元池(vBBUP)。在这些具体实施中,CRAN或vBBUP可以实施RAN功能划分,诸如分组数据汇聚协议(PDCP)划分,其中无线电资源控制(RRC)和PDCP层可以由CRAN/vBBUP操作,并且其他第2层(L2)协议实体可以由单独的RAN节点122操作;介质访问控制(MAC)/物理(PHY)层划分,其中RRC、PDCP、无线电链路控制(RLC)和MAC层可以由CRAN/vBBUP操作,并且PHY层可以由单独的RAN节点122操作;或“下部PHY”划分,其中RRC、PDCP、RLC、MAC层和PHY层的上部部分可以由CRAN/vBBUP操作,并且PHY层的下部部分可以由各个RAN节点122操作。该虚拟化框架可以允许RAN节点122的空闲的处理器核心执行或实行其他虚拟化应用程序。
[0027]在一些具体实施中,单独的RAN节点122可以表示经由单独的F1接口连接到gNB控制单元(CU)的单独的gNB分布式单元(DU)。在此类具体实施中,gNB-DU可以包括一个或多个远程无线电头端或射频(RF)前端模块(RFEM),并且gNB-CU可以由位于RAN 120中的服务器(未示出)或由服务器池(例如,被配置为共享资源的一组服务器)以与CRAN/vBBUP类似的方式来操作。另外或另选地,RAN节点120中的一个或多个节点可以是下一代eNB(即,gNB),可以向UE 110提供演进的通用地面无线电接入(E-UTRA)用户平面和控制平面协议终端,并且可以经由NG接口连接到5G核心网络(5GC)130。
[0028]RAN节点122中的任一个节点都可作为空中接口协议的终点,并且可以是UE 110的第一联系点。在一些具体实施中,RAN节点122中的任一者都可以执行RAN 120的各种逻辑功能,包括但不限于无线电网络控制器(RNC)的功能,诸如无线电承载管理、上行链路和下行链路动态无线电资源管理和数据分组调度,以及移动性管理。UE 110可被配置为根据各种通信技术,使用正交频分复用(OFDM)通信信号在多载波通信信道上彼此或者与RAN节点122中的任一个进行通信,所述通信技术诸如但不限于OFDMA通信技术(例如,用于下行链路通信)或单载波频分多址(SC-FDMA)通信技术(例如,用于上行链路和ProSe或侧链路(SL)通信),但是此类具体实施的范围在这方面可不受限制。OFDM信号可包括多个正交子载波。
[0029]在一些具体实施中,下行链路资源网格可以用于从RAN节点122中的任何节点到UE110的下行链路传输,并且上行链路传输可以利用类似的技术。网格可以是表示每个时隙中下行链路的物理资源的时频网格(例如,资源网格或时频资源网格)。对于OFDM系统,此类时频平面表示是常见的做法,这使得无线资源分配变得直观。资源网格的每一列和每一行分别对应一个OFDM符号和一个OFDM子载波。时域中资源网格的持续时间与无线电帧中的一个时隙对应。资源网格中最小的时频单位表示为资源元素。每个资源网格包括资源块,这些资源块描述了某些物理信道到资源元素的映射。每个资源块可包括资源元素(RE)的集合;在频域中,这可以表示当前可以分配的最少量资源。使用此类资源块来传送几个不同的物理下行链路信道。
[0030]此外,RAN节点122可被配置为通过许可介质(也称为“许可频谱”和/或“许可频段”)、未许可共享介质(也称为“未许可频谱”和/或“未许可频段”)或它们的组合与UE 110和/或彼此进行无线通信。许可频谱可包括在大约400MHz至大约3.8GHz的频率范围内操作的信道,而未许可频谱可包括5GHz频带。许可频谱可以对应于为某些类型的无线活动(例如,无线电信网络活动)选择、保留、调节等的信道或频带,而未许可频谱可对应于不受某些类型的无线活动的限制的一个或多个频带。特定频带对应于许可介质还是未许可介质可取决于一个或多个因素,诸如由公共部门组织(例如,政府机构、监管机构等)确定的频率分配或由参与制定无线通信标准和协议的私营部门组织确定的频率分配等。
[0031]为了在未许可频谱中操作,UE 110和RAN节点122可使用许可辅助接入(LAA)、eLAA和/或feLAA机制来操作。在这些具体实施中,UE 110和RAN节点122可执行一个或多个已知的介质感测操作或载波感测操作,以便确定未许可频谱中的一个或多个信道当在未许可频谱中传输之前是否不可用或以其他方式被占用。可根据先听后说(LBT)协议来执行介质/载波感测操作。
[0032]LAA机制可以建立在LTE-Advanced系统的载波聚合(CA)技术上。在CA中,每个聚合载波都被称为分量载波(CC)。在一些情况下,各个CC可具有与其他CC不同的带宽。在时分双工(TDD)系统中,CC的数量以及每个CC的带宽可对于DL和UL相同。CA还包含各个服务小区以提供各个CC。服务小区的覆盖范围可不同,例如,因为不同频带上的CC将经历不同的路径损耗。主服务小区或PCell可以为UL和DL两者提供主分量载波(PCC),并且可处理无线电资源控制(RRC)和非接入层面(NAS)相关活动。其他服务小区被称为SCell,并且每个SCell可提供UL和DL两者的单个辅分量载波(SCC)。可按需要添加和移除SCC,而改变PCC可能需要UE110经历切换。在LAA、eLAA和feLAA中,SCell中的一些或全部可在未许可频谱(称为“LAASCell”)中操作,并且LAA SCell由在许可频谱中操作的PCell协助。当UE被配置为具有多于一个LAA SCell时,UE可在配置的LAA SCell上接收UL授权,指示同一子帧内的不同PUSCH起始位置。
[0033]PDSCH将用户数据和较高层信令承载到多个UE 110。物理下行链路控制信道(PDCCH)可携带关于与PDSCH信道有关的传输格式和资源分配的信息等。PDCCH还可以向UE110通知关于与上行链路共享信道有关的传输格式、资源分配和混合自动重传请求(HARQ)信息。通常,可以基于从UE 110中的任一者反馈的信道质量信息在RAN节点122中的任一者处执行下行链路调度(例如,将控制和共享信道资源块分配给小区内的UE 110-2)。可以在用于(例如,分配给)UE 110中的每个UE的PDCCH上发送下行链路资源分配信息。
[0034]PDCCH使用控制信道元素(CCE)来传送控制信息,其中许多CCE(例如,6,等等)可以由资源元素组(REG)组成,其中REG被定义为OFDM符号中的物理资源块(PRB)。例如,在被映射到资源元素之前,可首先将PDCCH复数值符号组织为四元组,然后可使用子块交织器对其进行排列以进行速率匹配。可以使用这些CCE中的一个或多个来传输每个PDCCH,其中每个CCE可以对应于分别具有四个物理资源元素的九个集合,称为REG。四个正交相移键控(QPSK)符号可以映射到每个REG。根据DCI的大小和信道条件,可以使用一个或多个CCE来传输PDCCH。LTE中可以存在具有不同数量的CCE(例如,聚合等级,L=1、2、4、8或16)的四个或更多个不同的PDCCH格式被定义。
[0035]一些具体实施可将针对资源分配的概念用于控制信道信息,资源分配的概念是上述概念的扩展。例如,一些具体实施可利用将PDSCH资源用于控制信息传输的扩展的(E)-PDCCH。可使用一个或多个ECCE来传输EPDCCH。与以上类似,每个ECCE可以对应于被称为EREG的九组四个物理资源元素。在一些情况下,ECCE可以具有其他数量的EREG。
[0036]RAN节点122可以被配置为经由接口123彼此通信。在系统100是LTE系统的具体实施中,接口123可以为X2接口。X2接口可以被限定在连接到演进分组核心(EPC)或CN 130的两个或更多个RAN节点122(例如,两个或更多个eNB/gNB或它们的组合)之间,或者在连接到EPC的两个eNB之间。在一些具体实施中,X2接口可包括X2用户平面接口(X2-U)和X2控制平面接口(X2-C)。X2-U可以为通过X2接口传输的用户分组提供流控制机制,并且可用于传送关于eNB或gNB之间的用户数据的递送的信息。例如,X2-U可提供关于从主eNB(MeNB)传输到辅eNB(SeNB)的用户数据的特定序号信息;关于针对用户数据成功将PDCP分组数据单元(PDU)从SeNB按序递送到UE 110的信息;未递送到UE 110的PDCP PDU的信息;关于SeNB处用于向UE传输用户数据的当前最小期望缓冲器大小的信息;等等。X2-C可提供LTE内接入移动性功能(例如,包括从源eNB到目标eNB的上下文传输、用户平面传输控制等),负载管理功能,以及小区间干扰协调功能。
[0037]如图所示,RAN 120可以连接(例如,通信地耦接)到CN 130。CN 130可包括多个网络元件132,该多个网络元件被配置为向经由RAN 120连接到CN 130的客户/订阅者(例如,UE 110的用户)提供各种数据和电信服务。在一些具体实施中,CN 130可以包括演进分组核心(EPC)、5GCN和/或一种或多种附加或另选类型的CN。CN 130的部件可在一个物理节点或单独的物理节点中实施,包括用于从机器可读或计算机可读介质(例如,非暂态机器可读存储介质)读取和执行指令的部件。在一些具体实施中,网络功能虚拟化(NFV)可用于经由存储在一个或多个计算机可读存储介质中的可执行指令来使上述网络节点角色或功能中的任一者或全部虚拟化(下面将进一步详细描述)。CN 130的逻辑实例可被称为网络切片,并且CN 130的一部分的逻辑实例可被称为网络子切片。网络功能虚拟化(NFV)架构和基础设施可用于将一个或多个网络功能虚拟化到包含行业标准服务器硬件、存储硬件或交换机的组合的物理资源上(另选地由专有硬件执行)。换句话讲,NFV系统可用于执行一个或多个EPC部件/功能的虚拟或可重新配置的具体实施。
[0038]如图所示,CN 130、应用服务器(AS)140和外部网络150可以经由接口134、136和138彼此连接,这些接口可以包括IP网络接口。应用服务器140可以包括一个或多个服务器设备或网络元件(例如,提供使用具有CM 130的IP承载资源的应用程序的虚拟网络功能(VNF)(例如,通用移动电信系统分组服务(UMTS PS)域、LTE PS数据服务等)。应用服务器140还可以或另选地被配置为经由CN 130支持UE 110的一个或多个通信服务(例如,IP语音(VoIP会话、一键通(PTT)会话、群组通信会话、社交网络服务等)。类似地,外部网络150可以包括各种网络中的一个或多个网络,包括互联网,从而向移动通信网络和网络的UE 110提供对多种附加服务、信息、互连性和其他网络特征的访问。
[0039]如图所示,示例性网络100可以包括NTN,该NTN可以包括一个或多个卫星160-1和160-2(统称为“多个卫星160”)。卫星160可以经由服务链路或无线接口162和/或RAN 120经由馈线链路或无线接口164(分别描绘为164-1和164)与UE 110通信。在一些具体实施中,卫星160可以作为关于UE 110和地面网络(例如,RAN 120)之间的通信的无源或透明网络中继节点来操作。在一些具体实施中,卫星160可以作为有源或再生网络节点来操作,使得卫星160可作为关于UE 110和RAN 120之间的通信的UE 110(例如,作为RAN 120的gNB)的基站来操作。在一些具体实施中,卫星160可以经由直接无线接口(例如,166)或间接无线接口(例如,经由使用接口164-1和164-2的RAN 120)彼此通信。
[0040]另外或另选地,卫星160可包括GEO卫星、LEO卫星或另一种类型的卫星。卫星160还可以,或另选地涉及一个或多个卫星系统或架构,诸如全球导航卫星系统(GNSS)、全球定位系统(GPS)、全球导航卫星系统(GLONASS)、北斗导航卫星系统(BDS)等。在一些具体实施中,卫星160可以作为相对于UE 110的基站(例如,RAN节点122)来操作。因此,本文对基站、RAN节点122等的引用可涉及其中基站、RAN节点122等是地面网络节点的具体实施,以及基站、RAN节点122等是非地面网络节点(例如,卫星160)的具体实施。
[0041]图2是无线通信网络的主小区组(MCG)210和辅小区组(SCG)220的示例200的图。MCG可以包括与主节点相关联的一组小区,包括主小区(PCell)和一个或多个辅小区(SCell)。SCG可以包括与辅节点相关联的一组服务小区,包括辅小区组的主小区(PSCell),并且可选地包括一个或多个辅小区(SCell)。
[0042]MCG 210可以由一个或多个基站实施并且可以包括一个或多个层。此类层的示例可以包括分组数据汇聚协议(PDCP)层、无线电链路控制(RLC)层、介质访问控制(MAC)层和多个物理(PHY)层。每个PHY层可以对应于关于UE 110的小区的不同具体实施。另外或另选地,PHY层可以结合PDCP、RL:C层、层和MAC层来操作(例如,由其管理、控制等)。在一些具体实施中,一个PHY层240可以作为主小区(PCell)或特殊小区(SpCell)操作,并且其他PHY层242和244可以对PCell的辅小区(SCell)进行操作。
[0043]SCG 220还可以包括多个层,包括RLC层、MAC层和多个PHY层。SCG 220可以不包括PDCP层,而是可以经由连接230依赖于MCG 210的PDCP层。类似于MCG 210的PHY层,SCG 220的PHY层可以各自作为相对于UE 110的小区起作用或操作。在一些具体实施中,一个PHY层250可以作为对PHY层252和254的主小区(PCell)进行操作,作为对PHY层250的PCell的辅小区进行操作。因此,如本文所述的特殊小区(SpCell)可以包括MCG 210的PCell或SCG 220的PCell。如本文所述,调度辅小区(sSCell)可以包括到任何SpCell的辅小区(SCell),每个SpCell可以驻留在相同的小区组或不同的小区组中。此外,虽然图2仅包括2个小区组,但本文所讨论的具体实施可以应用于同步或彼此协作操作的多个小区组以执行本文所述的技术。此外,每个小区组(例如,MCG和/或SCG)可以在一个或多个基站上实施,并且作为MCG或SCG操作的小区组可以改变,并且小区组内的小区(例如,SpCell、SCell、sSCell等)可以通过激活、去激活、休眠等来改变。
[0044]MCG 210和SCG 220可涉及与UE 110的双连接场景,在这种情况下,随机接入信道(RACH)过程等可以被引导至MCG 210。另外,MCG 210和SCG 220可以各自包括PCell(例如,240和250),并且PCell在本文中可以被称为特殊小区或特殊主小区,表示为SpCell。此外,MCG 210或SCG 220的辅小区(SCell)可以作为调度辅小区(sSCell)操作,该调度辅小区被配置为向MCG 210或SCG 220的SpCell提供配置、调度、激活、去激活和其他功能或命令。因此,基站、基站的基带处理器等可以包括MCG 210和/或SCG 220的基站,控制、管理、启用等,MCG 210和/或SCG 220的sSCell,以及/或者MCG 210和/或SCG 220的SpCell,其中可包括MCG 210和/或SCG 220内的附加SCell或SpCell。
[0045]图3是用于管理一个或多个小区组中的动态频谱共享(DSS)的示例性过程300的流程图。过程300可以由包括(例如,MCG 210或SCG 220的)SpCell和/或sSCell的基站来实施。例如,过程300可以由基站实施的sSCell来实施(该基站可以是上文参考图1描述的RAN 120的示例)。在一些具体实施中,过程300中的一些或全部可以由一个或多个其他系统或设备执行,包括图1的设备中的一个或多个设备。另外,过程300可以包括比图3中所示的操作更少的、附加的、不同排序和/或排列的操作。在一些具体实施中,过程300的一些或所有操作相对于过程300的一个或多个其他操作中的一个或多个操作可以独立地、连续地、同时地等执行。因此,本文所述的技术不限于图3中描绘的操作或过程的数量、顺序、排列、定时等。
[0046]如图所示,过程300可以包括接收能力信息并且基于该能力信息来确定DCI格式和USS(框310)。例如,基站可以从UE 110接收UE能力信息。该能力信息可以指示UE 110是否能够在SPCell或sSCell中在USS期间接收非回退DCI。在一些具体实施中,UE能力信息还可以或另选地指示UE 110是否能够在SpCell或sSCell中接收回退DCI。另外或另选地,基站可以基于该能力信息来确定DCI格式和用于与UE 110通信的USS。在一些具体实施中,容量信息可以通知基站哪些小区(例如,SpCell和/或sSCell可以被调度以在UE 110的USS期间发送非回退DCI。因此,如本文所述,容量信息可以使基站能够确定、标识、配置等用于在UE 110的USS期间传送非回退DCI的小区。
[0047]过程300还可以包括在涉及SpCell和sSCell的CCS期间向UE 110指示DCI格式和USS(框320)。例如,基站可以参与涉及SpCell和sSCell的CCS过程,该过程还可以涉及到UE110的传送。在一些具体实施中,作为CCS过程的一部分,基站可以向UE 110指示DCI格式和/或USS。在一些具体实施中,这可以使UE 110能够根据基站用来与UE 110通信的DCI格式来监测适当的搜索空间(例如,USS)。
[0048]过程300可以包括使非回退DCI基于DCI格式和USS被传送到UE 110(框330)。例如,基站可以使非回退DCI被传送到UE 110。在这样做时,基站可以作为SpCell和/或sSCell进行操作。可以按与USS一致的方式来传送非回退DCI,使得UE 110可以在传送非回退DCI时监测USS。如本文所述,非回退DCI可以使UE 110能够根据DCI或回退DCI与基站(例如,SpCell和sSCell)通信,否则该DCI或回退DCI可用于实现UE 110和基站之间的通信。
[0049]过程300可以包括为SpCell和/或sSCell配置无线电链路监测(RLM)(框340)。无线电链路监测(RLM)可包括用于监测无线电链路诸如新空口(NR)中的物理下行链路控制信道(PDCCH)传输的质量等级的过程。在一些具体实施中,基站可以为SpCell和/或sSCell配置RLM。例如,基站可以使RRC消息被传送到SpCell、sSCell和/或UE 110,这可以指示用于RLM的参考信号(例如,RadioLinkMonitoringRS元素)是否与SpCell和/或sSCell相关联。在一些具体实施中,这可以由特定RRC字段或值来指示,诸如ServCellIndex字段或值。
[0050]在一些具体实施中,当未配置RLM参考信号(例如,RadioLinkMonitoringRS元素)时,UE 110可以使用为用于在SpCell和/或sSCell中的PDCCH接收的传输配置指示符状态提供的参考信号。另外,当UE 110使用针对SpCell和sSCell两者中的PDCCH接收的活动TCI状态提供的RS时,如果参考信号的总数超过UE 110的参考信号容量或阈值,则UE 110可以基于预先确定的参考信号优先级来选择参考信号。在一些具体实施中,UE 110可以首先选择SpCell的PDCCH而不是sSCell。另外或另选地,UE 110可以从最短的监测周期性开始按顺序选择搜索空间集,如果一个以上的CORESET与具有相同监测周期性的搜索空间集相关联,则UE110可以根据最高CORESET索引来确定CORESET的顺序,该索引可以例如由基站在CCS过程期间经由RRC消息等向UE 110指示。
[0051]过程300可以包括为SpCell和/或sSCell配置波束故障恢复(BFR)(框350)。例如,基站可以配置UE来监测来自sSCell的BFR的参考信号,而不是或者除了例如来自SpCell的参考信号。在一些具体实施中,可以使用SCell的BeamFailureRecoverySCellConfig IE来配置BFR。在一些具体实施中,BFR可以基于SpCell和/或sSCell的候选波束或参考信号的列表或配置,其中可以包括在特定IE,诸如PRACH-ResourceDedicatedBFR配置IE中引入的索引(例如,ServCellIndex)。在一些具体实施中,BFR可以基于用于SpCell、sSCell或SpCell和sSCell两者的BFRP(波束故障请求响应)和/或recoverySearchSpaceId的一个或多个恢复空间。
[0052]过程300可以包括激活和/或去激活SpCell和/或sSCell(框360)。例如,在某个时间点,基站可以传送来自SpCell和/或sSCell的改变(例如,激活或去激活)的指示(例如,MAC CE),并且UE 110可以改变UE对DCI的监测。例如,当sSCell被去激活时,UE 110可以从监测sSCell的USS切换到监测SpCell的USS。类似地,基站可以使sSCell进入休眠状态或转换回唤醒状态。当在sSCell和SpCell中配置具有非回退DCI的USS时,如果sSCell处于休眠状态,则UE 110可以在SpCell上监测具有非回退DCI的USS。另外或另选地,如果sSCell被唤醒,则UE 110可以监测具有在sSCell上配置而不是在SpCell上配置的非回退DCI的USS(例如,如果UE 110不支持同时的SpCell和sSCell非回退DCI监测)。根据具体实施,至少在SpCell上,可选地在可以触发SCell休眠的sSCell DCI上可以被配置为:仅在SpCell上,不在sSCell上;在SpCell或sSCell上,但不是在两者上;或者在SpCell或sSCell上,或者在两者上。另外或另选地,DCI格式2_6、DL DCI格式1_1、UL DCI格式0_1可用于强制实施配置中的任何一种或组合。
[0053]图4是SpCell和sSCell的时隙的示例400的图。如图所示,SpCell的时间线410-1可以包括具有对应的USS 430-1、430-2等的时隙420-1。类似地,sSCell的时间线410-2可以包括具有对应的USS 430-3、430-4等的时隙420-2、420-3等。在一些具体实施中,当配置从sSCell到SpCell的CCS,并且UE 110被配置为在SpCell和sSCell上监测具有非回退DCI的USS时,基站(或其他类型的网络设备)可以配置搜索空间以确保在每个时隙中。UE 110被配置为在SpCell或sSCell中的最多一个上使用非回退DCI来监测USS。附加地或另选地,当SpCell和sSCell具有不同的子载波间隔(SCS)时,基站或其他类型的网络设备可以配置监测时机(例如,具有USS的时隙)的持续时间以确定SpCell和sSCell的时隙之间的时隙重叠。附加地或另选地,当SpCell和sSCell具有不同的子载波间隔(SCS)时,基站或其他类型的网络设备可以基于哪个时隙(例如,在SpCell和sSCell的时隙之间)包含监测时机(例如,USS)来确定时隙重叠。
[0054]图5是SpCell和sSCell的时隙的示例500的图。如图所示,SpCell的时间线510-1可以包括具有对应的USS 530-1、530-2等的时隙520-1。类似地,sSCell的时间线510-2可以包括具有对应的USS 530-3、530-4等的时隙520-2、520-3等。在一些具体实施中,当配置从sSCell到SpCell的CCS,并且UE 110被配置为在SpCell和sSCell上监测具有非回退DCI的USS时,基站(或其他类型的网络设备)可以配置搜索空间以确保在每个时隙中。UE 110被配置为在SpCell或sSCell中的最多一个上使用非回退DCI来监测USS。附加地或另选地,当SpCell和sSCell具有不同的子载波间隔(SCS)时,基站或其他类型的网络设备可以配置监测时机(例如,具有USS的时隙)的持续时间以确定SpCell和sSCell的时隙之间的时隙重叠。
[0055]图6和图7是小区组(CG)600和700的示例性配置的图。如图所示,CG 600可以包括SpCell 610和sSCell 620。SpCell 610可以被配置用于仅关于非回退上行链路(UL)DCI的USS,该非回退UL DCI可以对应于某些DCI格式(例如,DCI格式0_1、0_2等)。sSCell 620可以被配置用于仅关于非回退下行链路(DL)DCI的USS,该非回退DL DCI可以对应于某些DCI格式(例如,DCI格式1_1、1_2等)。相反,在其他具体实施中,CG 700可以包括SpCell 710和sSCell 720,其中SpCell 710可被配置用于仅关于非回退DL DCI的USS,该非回退DL DCI可对应于某些DCI格式(例如,DCI格式1_1、1_2等),并且sSCell 720可被配置用于仅关于非回退UL DCI的USS,该非回退UL DCI可对应于某些DCI格式(例如,DCI格式0_1、0_2等)。
[0056]图8是CG 800的示例性配置的图。如图所示,CG 800可以包括SpCell 810,并且sSCell 820可以各自包括一个或多个信息字段或信息元素。此类字段或元素的示例可以包括服务小区配置(ServignCellConfig)字段、DL带宽部分(BWP)(BWP-DownlinkDedicated)字段、PDCCH配置PDCCH-Config)字段和搜索空间添加模块列表(searchSpacesToAddModList)字段。在一些具体实施中,当配置来自sSCell至SpCell的CCS时,可针对每个DL BWP对于每个小区搜索配置搜索空间。在一些具体实施中,当从sSCell到SpCell的CCS被配置时,SpCell的CCS配置(例如,CrossCarrierSchedulingConfig)信息元素可以指示SpCell是否可以被(例如,由sSCell)配置,可以指示SpCell是否已经被(例如,由sSCell)配置,可以指示SpCell是否可以被配置为调度任何其他小区,可以包括载波指示字段(CIF-存在)来指示小区的授权或分配等。在一些具体实施中,SpCell的搜索空间配置(SearchSpace信息元素)可以包括可配置字段,这些可配置字段可以指示SpCell既作为调度小区又作为被调度小区的PDCCH监测时机。在一些具体实施中,搜索空间配置还可以包括其他字段,诸如nrofCandidates字段,用于作为调度小区的sSCell和作为被调度小区的SpCell。
[0057]图9是去激活sSCell的示例的图。如图所示,sSCell的时间线910和SpCell的时间线920可以分别包括USS周期930和940。UE 110可以监测sSCell的USS周期930而不监测SpCell的USS周期940。在某个时间点,sSCell可以被去激活,这可以包括涉及向UE 110发送介质访问控制(MAC)控制元素(CE)950以指示sSCell将被去激活的过程。作为响应,UE 110可以为对应的MAC CE发送HARQ确认消息960,并且可以在从发送确认消息的指定时间段(例如,3毫秒)之后从监测sSCell的USS 930切换为监测SpCell的USS 940。
[0058]图10是激活sSCell的示例的图。如图所示,sSCell的时间线1010和SpCell的时间线1020可以分别包括USS周期1030和1040。UE 110可以监测SpCell的USS周期1040而不监测SpCell的USS周期1030。在某个时间点,可以激活sSCell,这可以包括涉及向UE 110发送MACCE 1050以指示激活sSCell将被激活的过程。作为响应,UE 110可以为对应的MAC CE 1050发送HARQ确认消息1060,并且可以在从发送确认消息开始的指定时间段(例如,3毫秒)之后从监测SpCell的USS 1040切换为监测sSCell的USS 1030。
[0059]图11是用于监测下行链路控制信息(DCI)的搜索空间的示例性过程1100的图。过程1100可以由UE 110实施,该UE可以与(例如,MCG 210或SCG 220的)SpCell和/或sSCell通信。在一些具体实施中,过程1100中的一些或全部可以由一个或多个其他系统或设备执行,包括图1的设备中的一个或多个设备。另外,过程1100可以包括比图11中所示的操作更少的、附加的、不同排序和/或排列的操作。在一些具体实施中,过程1100的一些或所有操作相对于过程1100的一个或多个其他操作中的一个或多个操作可以独立地、连续地、同时地等执行。因此,本文所述的技术不限于图11中描绘的操作或过程的数量、顺序、排列、定时等。
[0060]如图所示,过程1100可以包括传达关于USS非回退DCI的能力信息(框1110)。例如,UE 110可以向基站指示UE 110是否能够在SpCell或sSCell中的USS中接收非回退DCI。另外或另选地,UE 110可以向基站指示UE 110是否能够在SpCell或sSCell中的USS中接收非回退DCI。
[0061]过程1100还可以包括接收指示用于接收DCI的DCI格式和/或SpCell和/或sSCell的对应的USS的信息(框1120)。例如,UE 110可以从基站接收对SpCell和/或sSCell的DCI格式的指示。在一些具体实施中,该信息可以指示用于监测非回退DCI的USS。在一些具体实施中,经由另一个通信或过程从基站接收该信息。
[0062]过程1100可以包括监测DCI信息的搜索空间(框1130)。例如,UE110可以根据从基站接收的DCI格式和/或另一类型的信息(例如,指定SpCell和/或sSCell)来监测USS以获得非回退DCI。在一些具体实施中,UE 110还可以或另选地,监测回退DCI(例如,在标准化的、预先选择的、默认的或预先指定的时间和地点传输的DCI)。
[0063]过程1100还可以包括基于小区激活、休眠、RLM配置和/或BFR配置来更新监测(框1140)。例如,在某个时间点,UE 110可以从基站接收关于SpCell和/或sSCell的改变(例如,激活或去激活)的指示(例如,MAC CE),并且UE 110可以改变UE对DCI的监测。例如,当sSCell被去激活时,UE 110可以从监测sSCell的USS切换到监测SpCell的USS。类似地,当UE110接收到激活sSCell的指示时,UE 110可以从监测SpCell的USS切换到监测sSCell的USS。另外或另选地,UE 110可以类似地基于SpCell和/或sSCell已经进入休眠操作状态或唤醒操作状态的指示来更新USS监测。
[0064]在一些具体实施中,当未配置RLM参考信号(例如,RadioLinkMonitoringRS元素)时,UE 110可以使用为用于在SpCell和/或sSCell中的PDCCH接收的传输配置指示符状态提供的参考信号。另外,当UE 110使用针对SpCell和sSCell两者中的PDCCH接收的活动TCI状态提供的RS时,如果参考信号的总数超过UE 110的参考信号容量或阈值,则UE 110可以基于预先确定的参考信号优先级来选择参考信号。在一些具体实施中,UE 110可以首先选择SpCell的PDCCH而不是sSCell。另外或另选地,UE 110可以从最短的监测周期性开始按顺序选择搜索空间集,如果一个以上的CORESET与具有相同监测周期性的搜索空间集相关联,则UE 110可以根据最高CORESET索引来确定CORESET的顺序,该索引可以例如由基站在CCS过程期间经由RRC消息等向UE 110指示。
[0065]在一些具体实施中,UE 110可以被配置为基于(而不是或者除了)从例如从SpCell传输的参考信号传输的参考信号来执行BFR。在一些具体实施中,可以使用SCell的BeamFailureRecoverySCellConfig IE来配置UE 110。在一些具体实施中,UE 110可以被配置为基于SpCell和/或sSCell的候选波束或参考信号的列表或配置来执行BFR,这可以包括UE 110接收在特定IE,诸如PRACH-ResourceDedicatedBFR配置IE中引入的索引(例如,ServCellIndex)。在一些具体实施中,UE 110可以被配置为基于用于SpCell、sSCell或SpCell和sSCell两者的BFRP(波束故障请求响应)和/或recoverySearchSpaceId的一个或多个恢复空间在SpCell上执行BFR。
[0066]图12是根据本文所述的一个或多个具体实施的设备的部件的示例的图。在一些具体实施中,设备1200可包括应用电路1202、基带电路1204、射频(RF)电路1206、前端模块(FEM)电路1208、一个或多个天线1210和电源管理电路(PMC)1212(至少如图所示耦接在一起)。图示设备1200的部件可以被包括在UE或RAN节点中。在一些具体实施中,设备1200可包括更少的元件(例如,RAN节点可不利用应用电路1202,而是包括处理器/控制器来处理从CN诸如5GC 130或演进分组核心(EPC)处接收的IP数据)。在一些具体实施中,设备1200可以包括附加元件,诸如存储器/存储装置、显示器、相机、传感器(包括一个或多个温度传感器,诸如单个温度传感器、设备1200中不同位置处的多个温度传感器等),或输入/输出(I/O)接口。在其他具体实施中,下文所述的部件可以包括在一个以上的设备中(例如,所述电路可以单独包括在一个以上的设备中用于云-RAN(C-RAN)具体实施)。
[0067]应用电路1202可包括一个或多个应用处理器。例如,应用电路1202可包括电路,诸如但不限于一个或多个单核或多核处理器。处理器可包括通用处理器和专用处理器(例如,图形处理器、应用处理器等)的任意组合。处理器可以与存储器/存储装置耦接或可包括存储器/存储装置,并且可以被配置为执行存储在存储器/存储装置中的指令,以使各种应用程序或操作系统能够在设备1200上运行。在一些具体实施中,应用电路1202的处理器可以处理从EPC接收的IP数据分组。
[0068]基带电路1204可包括电路,诸如但不限于一个或多个单核或多核处理器。基带电路1204可包括一个或多个基带处理器或控制逻辑部件,以处理从RF电路1206的接收信号路径接收到的基带信号,以及生成用于RF电路1206的发射信号路径的基带信号。基带处理电路1204可与应用电路1202进行交互,以生成和处理基带信号并且控制RF电路1206的操作。例如,在一些具体实施中,基带电路1204可包括第三代(3G)基带处理器1204A、第四代(4G)基带处理器1204B、第五代(5G)基带处理器1204C、或其他现有代、正在开发或将来待开发的代的其他基带处理器1204D(例如,第二代(2G)、第六代(6G)等)。基带电路1204(例如,一个或多个基带处理器1204A-D)可以处理各种无线电控制功能,这些功能使得经由RF电路1206与一个或多个无线电网络进行通信。在其他具体实施中,基带处理器1204A-D的一部分或全部功能可包括在存储器1204G中存储的模块中,并且经由中央处理单元(CPU)1204E来执行。无线电控制功能可包括但不限于信号调制/解调、编码/解码、射频移位等。在一些具体实施中,基带电路1204的调制/解调电路可包括快速傅里叶变换(FFT)、预编码或星座映射/解映射功能。在一些具体实施中,基带电路1204的编码/解码电路可包括卷积、咬尾卷积、turbo、维特比或低密度奇偶校验(LDPC)编码器/解码器功能。调制/解调和编码器/解码器功能的具体实施不限于这些示例,并且在其他方面可包括其他合适的功能。
[0069]在一些具体实施中,基带电路1204可包括一个或多个音频数字信号处理器(DSP)1204F。音频DSP 1204F可以包括用于压缩/解压缩和回声消除的元件,并且在其他具体实施中可包括其他合适的处理元件。在一些具体实施中,基带电路的部件可以适当地组合在单个芯片、单个芯片组中,或设置在同一电路板上。在一些具体实施中,基带电路1204和应用电路1202的一些或全部组成部件可以一起实现,诸如(例如)在片上系统(SOC)上。
[0070]在一些具体实施中,基带电路1204可提供与一种或多种无线电技术兼容的通信。例如,在一些具体实施中,基带电路1204可支持与NG-RAN、演进通用地面无线接入网(EUTRAN)或其他无线城域网(WMAN)、无线局域网(WLAN)、无线个域网(WPAN)等的通信。基带电路1204被配置为支持超过一个无线协议的无线电通信的具体实施可被称为多模基带电路。
[0071]RF电路1206可以使用调制的电磁辐射通过非固体介质与无线网络进行通信。在各种具体实施中,RF电路1206可包括开关、滤波器、放大器等,以促进与无线网络的通信。RF电路1206可包括接收信号路径,该接收信号路径可包括对从FEM电路1208处接收的RF信号进行下变频并且将基带信号提供给基带电路1204的电路。RF电路1206还可包括传输信号路径,该传输信号路径可包括对由基带电路1204提供的基带信号进行上变频并且将RF输出信号提供给FEM电路1208以进行传输的电路。
[0072]在一些具体实施中,RF电路1206的接收信号路径可包括混频器电路1206A、放大器电路1206B和滤波器电路1206C。在一些具体实施中,RF电路1206的发射信号路径可包括滤波器电路1206C和混频器电路1206A。RF电路1206还可包括合成器电路1206d,用于合成由接收信号路径和发射信号路径的混频器电路1206A使用的频率。在一些具体实施中,接收信号路径的混频器电路1206A可以被配置为基于合成器电路1206D提供的合成频率来将从FEM电路1208接收的RF信号下变频。放大器电路1206B可以被配置为放大下变频的信号,并且滤波器电路1206C可以是低通滤波器(LPF)或带通滤波器(BPF),其被配置为从下变频信号中移除不想要的信号以生成输出基带信号。可以将输出基带信号提供给基带电路1204以进行进一步处理。在一些具体实施中,输出基带信号可以是零频率基带信号,但这不是必需的。在一些具体实施中,接收信号路径的混频器电路1206A可包括无源混频器,但是具体实施的范围在这方面不受限制。
[0073]在一些具体实施中,发射信号路径的混频器电路1206A可以被配置为基于由合成器电路1206D提供的合成频率来上变频输入基带信号,以生成用于FEM电路1208的RF输出信号。基带信号可以由基带电路1204提供,并且可以由滤波器电路1206c滤波。
[0074]在一些具体实施中,接收信号路径的混频器电路1206A和发射信号路径的混频器电路1206A可包括两个或更多个混频器,并且可以被分别布置用于正交下变频和上变频。在一些具体实施中,接收信号路径的混频器电路1206A和发射信号路径的混频器电路1206A可包括两个或更多个混频器,并且可被布置用于图像抑制(例如,Hartley图像抑制)。在一些具体实施中,接收信号路径的混频器电路1206A和混频器电路`1206A可以被布置为分别用于直接下变频和直接上变频。在一些具体实施中,接收信号路径的混频器电路1206A和发射信号路径的混频器电路1206A可被配置用于超外差操作。
[0075]在一些具体实施中,输出基带信号和输入基带信号可以是模拟基带信号,尽管具体实施的范围在这方面不受限制。在一些另选的具体实施中,输出基带信号和输入基带信号可以是数字基带信号。在这些另选具体实施中,RF电路1206可包括模数转换器(ADC)和数模转换器(DAC)电路,并且基带电路1204可包括数字基带接口以与RF电路1206进行通信。
[0076]在一些双模式具体实施中,可以提供单独的无线电IC电路来处理每个频谱的信号,但是具体实施的范围在这方面不受限制。
[0077]在一些具体实施中,合成器电路1206d可以是分数-N合成器或分数N/N+1合成器,但具体实施的范围在这方面不受限制,因为其他类型的频率合成器也可以是合适的。例如,合成器电路1206d可以是Δ-∑合成器、倍频器或包括具有分频器的锁相环路的合成器。
[0078]合成器电路1206d可以被配置为基于频率输入和分频器控制输入来合成输出频率,以供RF电路1206的混频器电路1206A使用。在一些具体实施中,合成器电路1206d可以是分数N/N+1合成器。
[0079]在一些具体实施中,频率输入可以由电压控制振荡器(VCO)提供,尽管这不是必须的。分频器控制输入可以由基带电路1204或应用处理器1202根据所需的输出频率提供。在一些具体实施中,可以基于由应用处理器1202指示的信道,从查找表中确定分频器控制输入(例如,N)。
[0080]RF电路1206的合成器电路1206d可包括分频器、延迟锁定环路(DLL)、复用器和相位累加器。在一些具体实施中,分频器可以是双模分频器(DMD),并且相位累加器可以是数字相位累加器(DPA)。在一些具体实施中,DMD可被配置为通过N或N+1(例如,基于进位输出)来划分输入信号,以提供分数分频比。在一些示例性具体实施中,DLL可包括级联的、可调谐的、延迟元件、鉴相器、电荷泵和D型触发器集。在这些具体实施中,延迟元件可以被配置为将VCO周期分成Nd个相等的相位分组,其中Nd是延迟线中的延迟元件的数量。这样,DLL提供了负反馈,以帮助确保通过延迟线的总延迟为一个VCO周期。
[0081]在一些具体实施中,合成器电路1206d可被配置为生成载波频率作为输出频率,而在其他具体实施中,输出频率可以是载波频率的倍数(例如,载波频率的两倍,载波频率的四倍)并且可与正交发生器和分频器电路一起使用以在该载波频率处生成相对于彼此具有多个不同相位的多个信号。在一些具体实施中,输出频率可以是LO频率(fLO)。在一些具体实施中,RF电路1206可包括IQ/极性转换器。
[0082]FEM电路1208可包括接收信号路径,该接收信号路径可包括电路,该电路被配置为对从一个或多个天线1210接收的RF信号进行操作,放大接收到的信号并且将接收到的信号的放大版本提供给RF电路1206以进行进一步处理。FEM电路1208还可包括传输信号路径,该传输信号路径可包括电路,该电路被配置为放大由RF电路1206提供的、用于通过一个或多个天线1210中的一个或多个天线进行传输的传输信号。在各种具体实施中,通过发射或接收信号路径的放大可仅在RF电路1206中、仅在FEM 1208中或者在RF电路1206和FEM 1208两者中完成。
[0083]在一些具体实施中,FEM电路1208可包括TX/RX开关,以在发射模式与接收模式操作之间切换。FEM电路可包括接收信号路径和传输信号路径。FEM电路的接收信号路径可包括LNA,以放大接收到的RF信号并且提供放大后的接收到的RF信号作为输出(例如,提供给RF电路1206)。FEM电路1208的传输信号路径可包括功率放大器(PA),以放大输入RF信号(例如,由RF电路1206提供),以及一个或多个滤波器,以生成RF信号用于随后的传输(例如,通过一个或多个天线1210中的一个或多个天线)。
[0084]在一些具体实施中,PMC 1212可管理提供给基带电路1204的功率。具体地,PMC1212可以控制电源选择、电压缩放、电池充电或DC-DC转换。当设备1200能够由电池供电时,例如,当设备包括在UE中时,通常可包括PMC 1212。PMC 1212可以在提供期望的具体实施大小和散热特性时提高功率转换效率。
[0085]而图12示出了仅与基带电路1204耦接的PMC 1212。然而,在其他具体实施中,PMC1212可以与其他部件(诸如但不限于应用电路1202、RF电路1206或FEM 1208)附加地或另选地耦接,并且执行类似的电源管理操作。
[0086]在一些具体实施中,PMC 1212可以控制或以其他方式成为设备1200的各种省电机制的一部分。例如,如果设备1200处于RRC_Connected状态,其中该设备仍连接到RAN节点,因为它期望立即接收流量,则在一段时间不活动之后,该设备可进入被称为不连续接收模式(DRX)的状态。在该状态期间,设备1200可以在短时间间隔内断电,从而节省功率。
[0087]如果在延长的时间段内不存在数据流量活动,则设备1200可以转换到RRC_Idle状态,其中该设备与网络断开连接,并且不执行操作诸如信道质量反馈、切换等。设备1200进入非常低的功率状态,并且执行寻呼,其中该设备再次周期性地唤醒以收听网络,然后再次断电。设备1200在该状态下可不接收数据;为了接收数据,该设备可转换回RRC_Connected状态。
[0089]应用电路1202的处理器和基带电路1204的处理器可以用于执行协议栈的一个或多个实例的元素。例如,可单独或组合使用基带电路1204的处理器来执行第3层、第2层或第1层的功能,而应用电路1204的处理器可以利用从这些层接收的数据(例如,分组数据)并且进一步执行第4层的功能(例如,传输通信协议(TCP)和用户数据报协议(UDP)层)。如本文所提到的,第3层可包括无线电资源控制(RRC)层,下文将进一步详细描述。如本文所提到的,第2层可包括介质访问控制(MAC)层、无线电链路控制(RLC)层和分组数据会聚协议(PDCP)层,下文将进一步详细描述。如本文所提到的,第1层可包括UE/RAN节点的物理(PHY)层,下文将进一步详细描述。
[0090]图13是根据本文所述的一个或多个具体实施的基带电路的示例性接口的图。如上所讨论的,图12的基带电路1204可包括处理器1204A至1204E和由所述处理器利用的存储器1204G。处理器1204A至1204E中的每一个处理器可分别包括用于向/从存储器1204G发送/接收数据的存储器接口1304A至1304E。
[0091]基带电路1204还可包括一个或多个接口以通信地耦接到其他电路/设备,所述一个或多个接口诸如存储器接口1312(例如,用于向/从基带电路1204外部的存储器发送/接收数据的接口)、应用电路接口1314(例如,用于向/从图12的应用电路1202发送/接收数据的接口)、RF电路接口1316(例如,用于向/从图12的RF电路1206发送/接收数据的接口)、无线硬件连接接口1318(例如,用于向/从近场通信(NFC)部件、部件(例如,低能耗)、部件和其他通信部件发送/接收数据的接口)以及电源管理接口1320(例如,用于向/从PMC 1212发送/接收电源或控制信号的接口)。
[0092]本文的示例可包括主题,诸如方法,用于执行该方法的动作或框的构件,至少一个包括可执行指令的机器可读介质,这些指令当由机器(例如,具有存储器的处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)等)执行时使得机器执行根据所述的具体实施和示例的使用多种通信技术的并发通信的方法或装置或系统的动作。
[0093]在示例1中,基站的基带处理器可以包括一个或多个处理器,该一个或多个处理器被配置为:从用户装备(UE)接收能力信息,该能力信息指示哪个小区能够被配置为在用于特殊小区(SpCell)调度的UE特定搜索空间(USS)中调度非回退下行链路控制信息(DCI);基于所述能力信息,确定DCI格式和用于将非回退DCI传送到所述UE的USS;在涉及所述(SpCell)和调度特殊小区(sSCell)的跨载波调度(CCS)期间,向所述UE指示所述DCI格式和所述USS;并且根据DCI格式和USS使非回退DCI被传送到UE。
[0094]在示例2中,当UE在SpCell和sSCell两者中支持具有非回退DCI的USS时,SpCell和sSCell两者均被配置为在USS中传送非回退DCI,并且当UE在SpCell和sSCell两者中均不支持具有非回退DCI的USS时,仅sSCell被配置为在USS中传送非回退DCI。在示例3中,能力信息进一步指示UE是否支持在相同的时隙中监测来自SpCell和sSCell的具有非回退DCI的USS,当UE支持对SpCell和sSCell的监测时,在相同的时隙中,SpCell和sSCell两者均被配置为传送非回退DCI,并且当UE不支持对SpCell和sSCell的监测时,在相同的时隙中,SpCell和sSCell中仅一者被配置为传送非回退DCI。
[0095]在示例4中,当UE支持对SpCell和sSCell的监测,并且SpCell和sSCell两者均被配置为传送非回退DCI时,USS被配置为使UE通过在SpCell或sSCell的时隙之间交替来监测非回退DCI。在示例5中,当SpCell和sSCell具有不同的子载波间隔(SCS)时,基于USS的监测时机的持续时间来确定SpCell和sSCell的时隙之间的时隙重叠。在示例6中,当SpCell和sSCell具有不同的子载波间隔(SCS)时,基于包括USS的监测时机的时隙来确定SpCell和sSCell的时隙之间的时隙重叠。
[0096]在示例7中,当UE支持对SpCell和sSCell的监测,并且SpCell和sSCell两者均被配置为传送非回退DCI时,USS被配置为使得SpCell仅与下行链路(DL)DCI相关联,并且sSCell仅与上行链路(UL)DCI相关联,或者USS被配置为使得SpCell仅与UL DCI相关联,并且sSCell仅与DL DCI相关联。在示例8中,一个或多个处理器进一步被配置为:激活针对SpCell或sSCell中的至少一者具有非回退DCI监测的USS,并且去激活针对SpCell或sSCell中的至少一者具有非回退DCI监测的USS。在示例9中,激活在一个小区上具有非回退DCI监测的USS自动去激活在任何其他小区上具有活动的非回退DCI监测的USS。在示例10中,激活或去激活针对SpCell或sSCell具有非回退DCI监测的USS涉及关于激活或去激活的待传送到UE的通信,该通信包括以下项中的至少一者:无线电资源控制(RRC)消息;介质访问控制(MAC)控制元素(CE);或DCI。
[0097]在示例11中,一个或多个处理器被进一步配置为:从用户装备(UE)接收指示UE是否支持具有回退DCI的USS的能力信息。在示例12中,SpCell被配置为传送回退DCI而不是sSCell。在示例13中,当SpCell和sSCell两者均被配置为传送回退DCI时,UE被配置为仅监测SpCell或sSCell中的一者。在示例14中,当SpCell和sSCell两者均被配置为传送回退DCI时,SpCell被配置为传送下行链路(DL)DCI并且sSCell被配置为传送上行链路(UL)DCI,或者SpCell被配置为传送UL DCI并且sSCell被配置为传送DL DCI。
[0098]在示例15中,当仅激活SpCell或sSCell中的一者以将回退DCI传送到UE时,经由以下项中的至少一者将关于激活的通信传送到UE:无线电资源控制(RRC)消息;介质访问控制(MAC)控制元素(CE);或DCI。在示例16中,USS被配置为指示回退DCI来自sSCell或SpCell。在示例17中,USS的物理下行链路控制信道(PDCCH)被配置为指示回退DCI来自sSCell或SpCell。在示例18中,sSCell和SpCell的CCS包括由网络配置给UE的CCS信息元素IE。在示例19中,当执行sSCell到SpCell的CCS时,针对每个调度小区在每个DL带宽部分(BWP)的基础上配置USS。
[0099]在示例20中,当执行sSCell到SpCell的CCS时,SpCell、sSCell或者SpCell和sSCell中的每一者的USS被配置有指示用于USS的PDCCH监测时机的信息元素(IE)。在示例21中,一个或多个处理器被进一步配置为:使SpCell或sSCell从激活状态进入休眠状态,并且使SpCell或sSCell从休眠状态进入活动状态。在示例22中,一个或多个处理器被进一步配置为:在使sSCell进入休眠状态之前,验证以下项中的至少一者:准许sSCell的休眠;至少在所述SpCell上配置所述非回退DCI;或者并非仅在sSCell上配置DCI格式2_6。在示例23中,无线电链路监测(RLM)经由无线电资源控制(RRC)被配置在SpCell或sSCell中的至少一者中。
[0100]在示例24中,无线电链路监测(RLM)参考信号未在SpCell或sSCell中配置,参考信号(RS)被提供为供UE使用,用于在SpCell或sSCell中的至少一者中的PDCCH接收的活动传输配置指示符(TCI)用于RLM。在示例25中,当活动TCI的RS数量超过UE的能力时,UE基于如下顺序选择RS:1)在选择sSCell的PDCCH的RS之前,选择SpCell的PDCCH的RS;2)按照从最短的监测周期性到更长的监测周期性的顺序选择搜索空间集;3)在具有较低CORESET索引的搜索空间之前,选择具有较高CORESET索引的搜索空间。
[0101]在示例26中,当sSCell在CCS期间配置SpCell用于波束故障恢复(BFR)时,用于BFR的SpCell的配置包括在SpCell、sSCell中的至少一者或SpCell和sSCell两者中的用于BFR的参考信号(RS)。在示例27中,当sSCell在CCS期间配置SpCell用于波束故障恢复(BFR)时,用于BFR的SpCell的配置包括在SpCell、sSCell中的至少一者或SpCell和sSCell两者中指示用于BFR的恢复搜索空间标识符。在示例28中,当sSCell在CCS期间配置SpCell用于波束故障恢复(BFR)时,用于BFR的SpCell的配置包括在SpCell、sSCell中的至少一者或SpCell和sSCell两者中指示用于BFR的附加的搜索空间标识符。在示例29中,当sSCell在CSS期间配置SpCell时,sSCell和SpCell被配置为相同的小区组的一部分。在示例30中,SpCell上的带宽部分(BWP)切换由以下项中的至少一者触发:sSCell中调度的DCI,或SpCell中调度的DCI。
[0102]在示例31中,用户装备(UE)的基带处理器可以包括:一个或多个处理器,该一个或多个处理器被配置为:向基站传送能力信息,该能力信息指示哪个小区能够被配置为在用于特殊小区(SpCell)调度的UE特定搜索空间(USS)中调度非回退下行链路控制信息(DCI);基于所述能力信息并且在涉及特殊小区(SpCell)和调度特殊小区(sSCell)的跨载波调度(CCS)过程期间,接收下行链路控制信息(DCI)格式和所述USS;以及基于DCI格式来监测USS以获得非回退DCI。
[0103]在示例32中,一个或多个处理器被配置为同时监测SpCell和sSCell两者上的非回退DCI。在示例33中,一个或多个处理器被配置为当仅在sSCell上配置非回退DCI并且sSCell被去激活或处于休眠状态时监测SpCell上的回退DCI。在示例34中,一个或多个处理器被配置为当在sSCell和sSCell两者上配置非回退DCI并且sSCell为活动时监测sSCell上的非回退DCI。在示例35中,一个或多个处理器被配置为:检测sSCell的激活或去激活;当所述sSCell被激活时,在从确认所述sSCell的所述激活开始测量的预先确定的间隔之后开始监测所述sSCell的所述USS;当所述sSCell被去激活时,在从确认所述sSCell的所述激活开始测量的所述预先确定的间隔之后停止监测所述SpCell的所述USS。
[0104]在示例36中,基站基本如本文所示和描述。在示例37中,基站的计算机可读介质基本如所示和所描述。在示例38中,由基站执行的方法基本上如所示和所描述。在示例39中,用户装备(UE)基本上如所示和所描述。在示例40中,用户装备(UE)的计算机可读介质基本上如所示和所描述。在示例41中,由用户装备(UE)执行的方法基本上如所示和所描述。
[0105]包括说明书摘要中所述的内容的本公开主题的例示示例、具体实施、方面等的以上描述并不旨在是详尽的或将所公开的方面限制为所公开的精确形式。虽然本文出于说明性目的描述了特定的示例、具体实施、方面等,但是如相关领域的技术人员可以认识到的,在此类示例、具体实施、方面等的范围内可以考虑各种修改。
[0106]就这一点而言,虽然已结合各种示例、具体实施、方面等和对应的附图描述了本发明所公开的主题,但是应当理解,可使用其他类似的方面或者可对所公开的主题进行修改和添加,以用于执行主题的相同、类似、另选或替代功能而不偏离所述实施方案。因此,所公开的主题不应当限于本文所述的任何单个示例、具体实施或方面,而应当根据以下所附权利要求书的广度和范围来解释。
[0107]特别是关于上述部件或结构(组件、设备、电路、系统等)执行的各种功能,除非另有说明,否则用于描述此类部件的术语(包括对“构件”的引用)旨在与执行所述部件(例如,功能上等效)的指定功能的任何部件或结构对应,即使在结构上不等同于执行本文示出的示例性具体实施中的功能的公开结构。另外,虽然已经相对于多个具体实施中的仅一个公开了特定特征,但是对于任何给定的或特定的应用程序,此类特征可以与其他具体实施的一个或多个其他特征组合,这可能是期望的并且是有利的。
[0108]如本文所用,术语“或”旨在表示包括性的“或”而不是排他性的“或”。也就是说,除非另有说明或从上下文可以清楚看出,否则“X采用A或B”旨在表示任何自然的包含性排列。也就是说,如果X采用A;X采用B;或者X采用A和B两者,则在任何前述情况下都满足“X采用A或B”。另外,在本申请和所附权利要求书中使用的冠词“一”和“一个”通常应被解释为表示“一个或多个”,除非另有说明或从上下文中清楚地是指向单数形式。此外,就在具体实施方式和权利要求中使用术语“包括有”、“包括”、“具有”、“有”、“带有”或其变体的程度而言,此类术语旨在以类似于术语“包含”的方式包括在内。此外,在讨论一个或多个编号项目(例如,“第一X”、“第二X”等)的情况下,通常,一个或多个编号项目可以是不同的或者它们可以是相同的,但在一些情况下,上下文可指示它们是不同的或指示它们是相同的。