Cross-carrier scheduling with different subcarrier spacing capability report

Abstract

Reporting a capability for cross-carrier scheduling (CCS) with different subcarrier spacings (SCSs) can include generating a message for transmission to a base station. The message can include an indication of a capability of a user equipment (UE) for CCS with different SCSs. Based on the capability of the UE for CCS with different SCSs, a plurality of unicast downlink control information (DCI) per span per physical downlink control channel (PDCCH) monitoring occasion can be processed to determine scheduling resources for downlink (DL) and uplink (UL) signaling or channels. The DL and UL signaling or channels can be processed using the scheduling resources.

Description

TECHNICAL FIELD

[0001] The present application relates generally to wireless communication systems, including cross-carrier scheduling and subcarrier spacing. BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly referred to by the industry organization name Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLANs), which is commonly referred to by the industry organization name Wi-Fi. In a 3GPP radio access network (RAN) in an LTE system, a base station can include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with wireless communication devices, known as user equipment (UE). In a fifth generation (5G) wireless RAN, a RAN node can include a 5G node, NR node (also referred to as a next generation Node B or g NodeB (gNB)).

[0003] A RAN uses a radio access technology (RAT) to communicate between RAN nodes and UEs. A RAN can include a global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), universal terrestrial radio access network (UTRAN), and / or E-UTRAN, which provide access to communication services through a core network. Each RAN in a RAN operates according to a particular 3GPP RAT. For example, a GERAN implements a GSM and / or EDGE RAT, a UTRAN implements a universal mobile telecommunications system (UMTS) RAT or other 3GPP RAT, an E-UTRAN implements an LTE RAT, and an NG-RAN implements a 5G RAT. In certain deployments, an E-UTRAN can also implement a 5G RAT.

[0004] The frequency bands of 5G NR can be split into two different frequency ranges. Frequency Range 1 (FR1) includes sub-6 GHz frequency bands, some of which can be used by previous standards but can potentially be extended to cover a new spectrum up to 7125 MHz. Frequency Range 2 (FR2) includes frequency bands in the mmWave range of 24.25 to 52.6 GHz. The frequency bands in the mmWave range of FR2 have shorter range but higher available bandwidth than the bands in FR1. The skilled person will recognize that the frequency ranges provided by way of example can vary over time or by region. BRIEF DESCRIPTION OF DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0006] Figure 1 Aspects of the subject matter are illustrated by way of example, not by way of limitation, in the accompanying drawings, wherein:

[0007] Figure 2 A flow diagram of a method is illustrated in accordance with an embodiment.

[0008] Figure 3 A flow diagram of a method is illustrated in accordance with an embodiment.

[0009] Figure 4 A system is illustrated in accordance with an embodiment.

[0010] Figure 5 Infrastructure equipment is illustrated in accordance with an embodiment.

[0011] Figure 6 A platform is illustrated in accordance with an embodiment.

[0012] Figure 7 An apparatus is illustrated in accordance with an embodiment.

[0013] Figure 8 An exemplary interface is illustrated in accordance with an embodiment.

[0014] Figure 9 A component is illustrated in accordance with an embodiment. DETAILED DESCRIPTION

[0015] Carrier aggregation (CA) allows for increased bandwidth (and bit rate) with multiple carriers, each referred to as a component carrier. In systems utilizing CA, cross-carrier scheduling (CCS) allows a UE connected to different nodes to receive a physical downlink control channel (PDCCH) on different carriers to eliminate inter-cell interference on the PDCCH. CCS can also be used to balance the load from scheduling and traffic across different component carriers (CCs). When CCS is utilized, a physical downlink shared channel (PDSCH) can be received on a different CC than the CC on which the corresponding PDCCH is received. Similarly, a physical uplink shared channel (PUSCH) can be transmitted on a different CC than the corresponding physical uplink control channel (PUCCH).

[0016] CCS can also allow for different subcarrier spacing (SCS), which occurs when a PDCCH carrying scheduling downlink control information (DCI) is received on a first carrier with a first subcarrier spacing (i.e., orthogonal frequency division multiplexing (OFDM) spacing) and a PDSCH to be received scheduled by the DCI is on a second, different carrier with a second, different subcarrier spacing. Thus, it can be particularly beneficial to define communications between entities in a wireless network (e.g., user equipment (UE) and base stations) with respect to CCS with different SCS capabilities to provide as much flexibility and efficiency as possible within the network.

[0017] Release 16 3GPP (Rel-16) has enhancements to support CCS with different SCS. In addition, processing time relaxations are specified. However, several issues with respect to CCS remain. For example, for CCS with different SCS, the minimum number of unicast DCIs that a UE can support (i.e., decode) per monitoring occasion with a span.

[0018] Currently, according to Release 15 3GPP (Rel-15), UE capabilities per monitoring occasion per span include the following: 1. basic PDCCH monitoring capability for feature group 3-1 (FG 3-1): a. for frequency division duplex (FDD): one unicast downlink (DL) DCI and one unicast uplink (UL) DCI, and b. for time division duplex (TDD): one unicast DL DCI and two unicast UL DCIs; and 2. span-based enhanced PDCCH monitoring capability for feature group 3-5b (FG 3-5b): a. for FDD: one unicast DL DCI and one unicast UL DCI, b. for TDD: one unicast DL DCI and two unicast UL DCIs, and c. for TDD: two unicast DL DCIs and one unicast UL DCI.

[0019] In other words, for FG3-1, the UE can monitor or decode one unicast DL DCI and one unicast UL DCI for FDD per monitoring occasion per span. Similarly, for FG3-1, the UE can monitor or decode one unicast DL DCI and two unicast UL DCIs for TDD per monitoring occasion per span. Further, for FG3-5b, the UE can monitor or decode one unicast DL DCI and one unicast UL DCI for FDD per monitoring occasion per span. Similarly, for FG3-5b, the UE can monitor or decode one unicast DL DCI and two unicast UL DCIs for TDD per monitoring occasion per span, or two unicast DL DCIs and one unicast UL DCI for TDD per monitoring occasion per span.

[0020] For CCS with different SCS, it can be most helpful for a first frequency range (FR1) to schedule a second frequency range (FR2). Notably, there can be some degree of compensation for scheduling opportunity loss due to slot duration differences: (15 kHz, 60 kHz), (15 kHz, 120 kHz), (30 kHz, 60 kHz), (30 kHz, 120 kHz). In some embodiments, FR1 SCS includes 15 kHz, 30 kHz, and 60 kHz, and FR2 SCS includes 60 kHz and 120 kHz (and 240 kHz, which is not applicable here). As an example, 15 kHz (e.g., FR1) can provide eight times the slot duration of that provided by 120 kHz (e.g., FR2), which can result in a 1 / 8 reduction in scheduling opportunities.

[0021] In response to these questions, in some embodiments, a UE can indicate CCS with different SCS support as an optional feature. In such embodiments, the CCS feature support of a UE can be reported / indicated independently according to the following options: 1. Define and indicate capability based on SCS, which provides two possibilities (i.e., between {small SCS schedules large SCS or large SCS schedules small SCS}); 2. Define and indicate capability based on FR, which provides four possibilities (i.e., between {FR1 schedules FR1, FR1 schedules FR2, FR2 schedules FR1, FR2 schedules FR2}); and 3. Define and indicate capability based on SCS frequency of any subcarrier spacing pair (i.e., between {15 / 30 / 60 / 120 kHz schedules 15 / 30 / 60 / 120 kHz}). Notably, each of these options (i.e., options 1-3) provides greater flexibility or granularity than the last (i.e., option 2 provides greater flexibility / granularity than option 1, and option 3 provides greater flexibility / granularity than option 2). However, it should also be noted that greater flexibility also requires greater overhead (e.g., sending a larger capability indication / message).

[0022] In other embodiments, a UE can indicate that it can support processing a larger number of unicast DCIs per monitoring occasion per span. Specifically, capability can be reported independently for each PDCCH monitoring capability or FG, including: 1. capability for FG3-1; 2. capability for FG3-5b; 3. capability for new Rel-16 span-based PDCCH monitoring capability; 4. capability for FG3-5a; and 5. capability for FG11-2. Thus, for each PDCCH monitoring capability or FG, a UE can report the maximum number of unicast DCIs that the UE can process per monitoring occasion per span (note that the minimum number that a UE can report is the number that has been specified according to Rel-15, as described in more detail above).

[0023] In other embodiments, the UE can indicate the number of unicast DCIs per monitoring occasion per span that it is capable of decoding or processing. In such embodiments, the following options can be used: 1. a single X number representing any unicast DCI. In such cases, the network can schedule unicast DL DCIs or unicast UL DCIs as long as the sum is not greater than X (e.g., if X = 2, the UE is capable of decoding zero unicast DL DCIs and two unicast UL DCIs, one unicast DL DCI and one unicast UL DCI, or two unicast DL DCIs and zero unicast UL DCIs); 2. XDLrepresenting the maximum number of unicast DL DCIs that the UE is capable of decoding and XULrepresenting the maximum number of unicast UL DCIs that the UE is capable of decoding; 3. {XDL, XUL} representing a list of possible combinations with a maximum number of total unicast DCIs and a maximum value of either or both total unicast DL DCIs and unicast UL DCIs (e.g., {{3, 3} {2, 4}, {4, 2}}, where the total maximum unicast DCIs <= 6 and the maximum unicast DL / UL DCIs <= 4). Determining the number of unicast DCIs per monitoring occasion per span that the UE is capable of decoding / processing in this manner can be particularly helpful when high (or higher) data rates are expected.

[0024] Alternatively, or additionally, the UE can indicate the number of unicast DCIs per monitoring occasion per span that the UE is capable of processing / decoding to reduce the UE peak data rate requirement (which can typically be less than one). For example, if M represents the unicast DCIs and N represents the spans, the number can be calculated by dividing M by N (or M / N, where M < N and N = 2, 4, 6, 8,...), which is indicated by the UE. In particular, for every N spans of consecutive monitoring occasions, the UE can only process M unicast DCIs. Notably, the spans are calculated from a reference time. As such, the first slot can be system frame number (SFN) = 0. In an example, if M = 1 and N = 4, the UE can decode one unicast DCI every fourth span (i.e., M / N = 1 / 4). Determining the number of unicast DCIs per monitoring occasion per span that the UE is capable of decoding / processing in this manner can be particularly useful when the data rate is going to be high anyway, but the battery life and / or thermal control associated with the UE can be a potential issue based on the high data rate.

[0025] Alternatively or additionally, a dormancy capability can also be considered, which can allow the gNB to, for example, inform the UE that the UE can remain dormant (i.e., can avoid monitoring) for a certain number of slots with respect to a component carrier (at which point the gNB can wake up the UE). However, before the gNB utilizes such capability of the UE, the UE can provide the gNB with UE capability regarding dormancy. In particular, such capability can be indicated using any of the following options: 1. per band combination (BC); 2. per BC, but the UE can also independently indicate: a. FR1 primary cell (PCell) dormancy FR2 secondary cell (SCell), and b. FR2 PCell dormancy FR1 SCell; 3. per BC, the UE can also independently indicate: a. FR1 PCell dormancy FR1 SCell, b. FR1 PCell dormancy FR2 SCell, c. FR2 PCell dormancy FR1 SCell, and d. FR2 PCell dormancy FR2 SCell.

[0026] Figure 1 A flow diagram 100 illustrating communications between a UE 102 and a gNB 104 (or base station) regarding reporting CCS with different SCS capabilities is shown. As shown, the UE 102 sends a capability message to the gNB 104 (represented by arrow 106). In particular, the capability message includes UE capabilities regarding CCS with different SCS. As an example, the capability message can indicate that the UE is capable of processing a certain number of unicast DCIs per monitoring occasion per span. In such an example, the certain number can include a single number representing a maximum sum of unicast DL DCIs and unicast UL DCIs. Alternatively, the certain number can include a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs. However, it should be noted that these are merely examples of capabilities that can be reported by the UE 102, and thus are not meant to be limiting in any way. Figure 1

[0027] Figure 2 A flow diagram of a method 200 for reporting capabilities regarding CCS with different SCS from the perspective of a UE is shown. In block 202, the method 200 generates a message to be sent to a base station. The message can include an indication of UE capabilities for cross-carrier scheduling (CCS) with different subcarrier spacing (SCS). In one embodiment, the indication in block 202 can include separate capabilities for supporting each of one or more feature groups (FGs). For example, the one or more feature groups can include at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

[0028] ​In another embodiment, the indication of block 202 can include that each span each monitoring occasion supports processing a particular number of unicast DCIs, where: the particular number includes a single number representing a maximum sum of unicast DL DCIs and unicast UL DCIs; or the particular number includes a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs.

[0029] In another embodiment, the indication of block 202 can include that each span each monitoring occasion supports processing a list of possible combinations of unicast DL DCIs and unicast UL DCIs, where each possible combination is generated based on a first number representing a maximum sum of unicast DL DCIs and unicast UL DCIs and a second number representing a maximum number of unicast DL DCIs or unicast UL DCIs.

[0030] In another embodiment, the indication of block 202 can include that each span each monitoring occasion supports processing a particular number of unicast DCIs, where: the particular number includes a fraction of a first number representing a number of unicast DCIs divided by a second number representing a number of spans, where the second number is greater than the first number.

[0031] In block 204, the method 200, based on the UE’s capability for CCSs with different SCSs, processes a number of unicast downlink control information (DCIs) per span per physical downlink control channel (PDCCH) monitoring occasion to determine scheduling resources for downlink (DL) and uplink (UL) signaling or channels. In one embodiment, the indication in block 202 can include that a first component carrier (CC) supports scheduling the scheduling resources of block 204 on a second CC, where: the first CC has a smaller SCS than the SCS of the second CC; the first CC has a larger SCS than the SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in FR1; the first CC is in FR1 and the second CC is in a second frequency range (FR2); the first CC is in FR2 and the second CC is in FR1; or the first CC is in FR2 and the second CC is in FR2.

[0032] In another embodiment, the indication in block 202 can include support of a first component carrier (CC) scheduling scheduling resources of block 204 on a second CC, where: the first CC has a SCS of 15 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 60 kHz; or the first CC has a SCS of 120 kHz and the second CC has a SCS of 120 kHz.

[0033] Finally, in block 206, the method 200 uses the scheduling resources to process DL and UL signaling or channels. Specifically, the UE can process the DL and UL signaling or channels according to the capabilities indicated in block 202. For example, channels such as PDSCH, PUSCH, etc., and signaling such as SRS, CSI-RS, etc.

[0034] Figure 3A flowchart showing method 300 for reporting capabilities regarding CCS with different SCS from the perspective of a gNB / base station. In block 302, the method 300 processes a message received from a user equipment (UE) including an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacing (SCS). In one embodiment, the indication in block 302 can include support for a first component carrier (CC) scheduling resources on a second CC, where: the first CC has a smaller SCS than the SCS of the second CC; the first CC has a larger SCS than the SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in FR1; the first CC is in FR1 and the second CC is in a second frequency range (FR2); the first CC is in FR2 and the second CC is in FR1; or the first CC is in FR2 and the second CC is in FR2.

[0035] In another embodiment, the indication in block 302 can include support for a first component carrier (CC) scheduling resources on a second CC, where: the first CC has a 15 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 60 kHz SCS; or the first CC has a 120 kHz SCS and the second CC has a 120 kHz SCS.

[0036] In another embodiment, the indication of block 302 can include a separate capability to support each of one or more feature groups (FGs). For example, the one or more feature groups can include at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2. In another embodiment, the indication of block 302 can include that each span each monitoring occasion supports processing a particular number of unicast DCIs, where the particular number includes a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs.

[0037] In another embodiment, the indication of block 302 can include a list of possible combinations of unicast DL DCIs and unicast UL DCIs that each span each monitoring occasion supports processing, where each possible combination is generated based on a first number representing a maximum sum of unicast DL DCIs and unicast UL DCIs and a second number representing a maximum number of unicast DL DCIs or unicast UL DCIs. In another embodiment, the indication of block 302 can include that each span each monitoring occasion supports processing a particular number of unicast DCIs, where the particular number includes a fraction of a first number representing a number of unicast DCIs divided by a second number representing a number of spans, where the second number is greater than the first number.

[0038] In block 304, the method 300 is based on the indication to schedule a particular number of unicast downlink control information (DCI) per physical downlink control channel (PDCCH) per monitoring occasion per span. For example, the number of unicast DCIs scheduled by the base station can include a single number that is less than or equal to a maximum sum of unicast DL DCIs and unicast UL DCIs included in the indication of the UE capability.

[0039] Figure 4 An exemplary architecture of a system 400 of a network in accordance with various embodiments is shown. The following description is provided for an example system 400 that operates in conjunction with the LTE system standards and 5G or NR system standards provided by 3GPP Technical Specifications. However, the example embodiments are not limited in this regard and the described embodiments can apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0040] As Figure 4As shown, system 400 includes UE 422 and UE 420. In this example, UE 422 and UE 420 are shown as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but can also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablet computers, wearable computer devices, Personal Digital Assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), Electronic Engine Management System (EEMS), electronic / engine control units (ECU), electronic / engine control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), networked or “smart” home- electronics devices, MTC devices, M2M, IoT devices, etc.

[0041] In some embodiments, UE 422 and / or UE 420 can be IoT UE, which can include a network access layer designed for low-power IoT applications using short-lived

[0042] UE 422 and UE 420 can be configured to connect, e.g., communicatively couple, with an access node or radio access node, shown as (R)AN 408. In embodiments, (R)AN 408 can be a NG RAN or a SG RAN, an E-UTRAN, or a legacy RAN such as a UTRAN or GERAN. As used herein, the term “NG RAN” or like terms can refer to (R)AN 408 operating in an NR or SG system, and the term “E-UTRAN” or like terms can refer to (R)AN 408 operating in an LTE or 4G system. UE 422 and UE 420 utilize connections (or channels) with (R)AN 408, shown as connections 404 and 402, respectively, which each comprise a physical communications interface or layer (discussed in further detail below).

[0043] In this example, connection 404 and connection 402 are air interfaces for enabling communicative coupling and can conform to a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3 GPP LTE protocol, a 5G NR protocol, and / or any other communication protocol discussed herein. In embodiments, UE 422 and UE 420 can also directly exchange communication data via a ProSe interface 410. The ProSe interface 410 can alternatively be referred to as a sidelink (SL) interface 110 and can include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0044] UE 420 is shown to be configured to access an AP 412 (also referred to as“WLAN node,”“WLAN,”“WLAN terminal,”“WT,” or the like) via connection 424. Connection 424 can include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 412 would include a wireless fidelity router. In this example, the AP 412 can be connected to the Internet without connecting to the core network (further described below) of the wireless system. In various embodiments, the UE 420, (R)AN 408, and AP 412 can be configured to utilize LWA operation and / or LWIP operation. The LWA operation can involve the UE 420 in RRC CONNECTED being configured to utilize radio resources of LTE and WLAN by the RAN node 414 or RAN node 416. The LWIP operation can involve the UE 420 using WLAN radio resources (e.g., connection 424) via IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over the connection 424. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0045] The (R)AN 408 can include one or more AN nodes that enable connectivity among the core network 404 and the access nodes, such as RAN nodes 414 and RAN nodes 416. As used herein, the term“access node,”“access point,” or the like can describe equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, among other examples, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage over a geographic area (e.g., a cell) or region. As used herein, the term“NG RAN node” or the like can refer to a RAN node (e.g., gNB) operating in an NR or SG system, while the term“E-UTRAN node” or the like can refer to a RAN node (e.g., eNB) operating in an LTE or 4G system 400. According to various embodiments, the RAN nodes 414 or 416 can be implemented as one or more of dedicated physical devices such as macrocell base stations and / or low-power (LP) base stations for providing femtocells, picocells, or other like cells with relatively small coverage areas, smaller user capacity, or higher bandwidth.

[0046] In some embodiments, all or part of the RAN nodes 414 or 416 can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP can implement a RAN function split, such as a PDCP split, where RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN nodes 414 or 416); a MAC / PHY split, where RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN nodes 414 or 416); or a“lower PHY” split, where RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layer are operated by the CRAN / vBBUP, and lower portions of the PHY layer are operated by individual RAN nodes. This virtualized framework allows the free Figure 4(not shown) connected to the gNB-CU. In these implementations the gNB-DU can include one or more remote radio head or RFEMs and the gNB-CU can be operated by a server (not shown) located in the (R)AN 408 or by a pool of servers in a similar manner as a CRAN / vBBUP. Additionally, or alternatively, one or more of RAN nodes 414 or RAN nodes 416 can be a next generation eNB (ng-eNB), which is a RAN node providing E-UTRA user plane and control plane protocol terminations and that is connected to a 5G-CN serving the UE 420 and UE 422 via an NG interface (discussed infra). In V2X scenarios, one or more of RAN nodes 414 or RAN nodes 416 can be a RSU or function as a RSU.

[0047] The term “road side unit” or “RSU” can refer to any transportation infrastructure entity used for V2X communications. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE can be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB can be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB can be referred to as a “gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a road side that provides connectivity support to passing vehicle UEs (vUEs). The RSU can also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can operate on 5.9 GHz direct short range communications (DSRC) band to provide extremely low latency communications required for high speed events such as crash avoidance, traffic warnings, etc. Additionally or alternatively, the RSU can operate on cellular V2X bands to provide the foregoing low latency communications as well as other cellular communications services. Additionally or alternatively, the RSU can operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and RSU’s radio frequency circuitry can be encapsulated in a weatherproof package suitable for outdoor installation and can include a network interface controller to provide wired connectivity (e.g., Ethernet) to a traffic signal controller and / or a backhaul network.

[0048] RAN nodes 414 and / or RAN nodes 416 can terminate the air interface protocol and can be the first point of contact for the UEs 422 and 420. In some embodiments, the RAN nodes 414 and / or 416 can perform various logical functions for the RAN 408 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.

[0049] In embodiments, the UEs 422 and 420 can be configured to communicate using OFDM communication signals with the RAN nodes 414 and / or 416 over a multicarrier communication channel, although the scope of the embodiments can not be limited in this respect. The technical effects of using OFDM communication signals can include one or more of the following: reduced intersymbol interference, enabling maintenance of low multipath tolerance, and enabling use of simple equalization techniques such as single-tap per receiver finger.

[0050] In some embodiments, a downlink resource grid can be used for downlink transmissions from the RAN nodes 414 and / or 416 to the UEs 422 and 420, while uplink transmissions can utilize a similar approach. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. For an OFDM system, such a time-frequency plane representation is a common practice and it makes it easy to describe and implement radio resource

[0051] According to various embodiments, the UEs 422 and 420 and the RAN nodes 414 and / or 416 transmit (e.g., and receive) data over a licensed medium (also referred to as “licensed spectrum” and / or “licensed band”) and an unlicensed shared medium (also referred to as “unlicensed spectrum” and / or “unlicensed band”). The licensed spectrum can include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum can include the 5 GHz band.

[0052] To operate in the unlicensed spectrum, UEs 422 and 420 and RAN node 414 or RAN node 416 can operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, UEs 422 and 420 and RAN node 414 or RAN node 416 can perform one or more known clear channel assessment (CCA) check operations and / or carrier sense operations to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The CCA / check operations can be performed in accordance with a listen before talk (LBT) protocol.

[0053] LBT is a mechanism by which equipment (e.g., UEs 422 and 420, RAN node 414 or RAN node 416, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operations can include a CCA that utilizes at least ED to determine if there are other signals on the channel in order to determine if the channel is occupied or clear. This LBT mechanism allows cellular / LAA networks to coexist with incumbent systems in the unlicensed spectrum, as well as with other LAA networks. The ED can include sensing RF energy in the expected transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

[0054] Generally, incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. The WLAN employs a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., mobile station (MS), such as UE 422, AP 412, etc.) intends to transmit, the WLAN node can first perform a CCA before transmission. Additionally, in cases where more than one WLAN node senses the channel to be idle and transmits at the same time, a backoff mechanism is used to avoid collisions. The backoff mechanism can be a counter that is randomly introduced within a CWS, which is increased exponentially upon a collision and reset to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some implementations, the LBT procedure for a DL or UL transmission burst (comprising PDSCH or PUSCH transmissions) can have a variable length LAA contention window between X and Y ECCA slots, where X and Y are the minimum and maximum values of the CWS for LAA. In one example, the minimum CWS for LAA transmissions can be 9 microseconds (ps); however, the size of the CWS and the MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0055] The LAA mechanisms build on the CA techniques of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregated bandwidth of 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, with the number of UL CCs being equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs and the bandwidth of each CC is normally the same for DL and UL.

[0056] CA also contains individual serving cells to provide individual CCs. The coverage of the serving cells can differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell can provide a PCC for both UL and DL, and can handle RRC and NAS related activities. Other serving cells are referred to as SCells, and each SCell can provide individual SCCs for both UL and DL. SCCs can be added and removed as required, while changing the PCC can require the UE 422 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as“LAA SCells”), and are assisted by a PCell operating in licensed spectrum. When a UE is configured with more than one LAA SCell, the UE can receive UL grants on configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0057] The PDSCH carries user data and higher-layer signaling to the UEs 422 and 420. Among other things, the PDCCH carries information about the transport format and resource allocations related to the PDSCH channel. It can also convey information about the transport format, resource allocation, and HARQ information related to the uplink shared channel to the UEs 422 and 420. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UEs 420 within a cell) can be performed at any of the RAN nodes 414 or 416 based on channel quality information fed back from any of the UEs 422 and 420. The downlink resource assignment information can be sent to a UE 420 on the PDCCH.

[0058] The PDCCH uses CCEs to deliver control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be permuted using a sub-block interleaver to provide rate matching. One or more of these CCEs can be used to transmit each PDCCH, with each CCE corresponding to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

[0059] Some implementations can use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some implementations can utilize an EPDCCH for control information transmission using PDSCH resources. The EPDCCH can be transmitted using one or more ECCEs. Similar to above, each ECCE can correspond to nine sets of four physical resource elements known as EREGs. In some cases, an ECCE can have other numbers of EREGs.

[0060] The RAN nodes 414 or the RAN nodes 416 can be configured to communicate with each other via an interface 430. In embodiments where the system 400 is an LTE system (e.g., when CN 406 is an EPC), the interface 430 can be an X2 interface. The X2 interface can be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface, and can be used to communicate information about the delivery of user data between eNBs. For example, the X2-U can provide specific sequence number information for user data transmitted from a MeNB to an SeNB; information about successful in-sequence delivery of PDCP PDUs to a UE 422 from the SeNB for user data; PDCP PDU information that was not delivered to the UE 422; information about a current minimum desired buffer size at the SeNB for transmitting user data to the UE; and the like. The X2-C can provide intra-LTE access mobility functions, including context transfer from a source eNB to a target eNB, user plane transport control, and the like; load management functions; and inter-cell interference coordination functions.

[0061] In implementations where the system 400 is an SG or NR system (e.g., when the CN 406 is an SGC), the interface 430 can be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to a SGC, between a RAN node 414 (e.g., gNB) and an eNB connected to a SGC, and / or between two eNBs connected to a 5GC (e.g., CN 406). In some implementations, the Xn interface can include an Xn-User plane (Xn-U) interface and an Xn-Control plane (Xn-C) interface. The Xn-U can provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and traffic control functionality. The Xn-C can provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 422 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the connected mode mobility of a UE 422 between one or more RAN nodes 414 or RAN nodes 416. The mobility support can include a context transfer from an old (source) serving RAN node 414 to new (target) serving RAN node 416 and control of user plane tunnels between the old (source) serving RAN node 414 to new (target) serving RAN node 416. A protocol stack of the Xn-U can include a transport network layer built on Internet Protocol (IP) transport layer and a GTP-U layer on top of UDP and / or IP layers to carry user plane PDUs. The Xn-C protocol stack can include an application layer signaling protocol (called Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. The SCTP can be on top of an IP layer, and can provide a guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack can be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0062] The (R)AN 408 is illustrated communicating with a core network— in this embodiment, the CN 406. The CN 406 can include one or more network elements 432 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UEs 422 and 420) connected to the CN 406 via the (R)AN 408. The components of the CN 406 can be implemented in one physical node or in separate physical nodes, including components to read and execute instructions stored on a machine- readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV can be used to virtualize any or all of the above-described network functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instantiation of the CN 406 can be referred to as a network slice, and a logical instantiation of a portion of the CN 406 can be referred to as a network sub-slice. NFV architectures and infrastructures can be used to virtualize one or more network functions on physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches, alternatively executed by specialized hardware. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components / functions.

[0063] Generally, the application server 418 can be an element of a network infrastructure that provides content or services via a web site to UEs 422, 420. For example, the application server 418 can provide contextually relevant content to UEs 422, 420 as part of an application, such as a social media app, a streaming app, a content consumption app, or a content generation app. The application server 418 can also be configured to support one or more communication services for UEs 422, 420 via the EPC, such as VoIP sessions, PTT sessions, group communication sessions, social networking services, and the like. The application server 418 can communicate with the CN 406 through an IP communications interface 436.

[0064] In embodiments, the CN 406 can be an SGC, and the (R)AN 116 can connect with the CN 406 via an NG interface 434. In embodiments, the NG interface 434 can split into two parts: an NG user plane (NG-U) interface 426, which carries traffic data between the RAN node 414 or 416 and a UPF; and an SI control plane (NG-C) interface 428, which is a signaling interface between the RAN node 414 or 416 and an AMF.

[0065] In embodiments, the CN 406 can be a 5GCN, and in other embodiments, the CN 406 can be an EPC. Where the CN 406 is an EPC, the (R)AN 116 can interface with the CN 406 via an S1 interface 434. In embodiments, the S1 interface 434 can split into two parts: the S1 user plane (S1-U) interface 426, which carries traffic data between the RAN node 414 or 416 and the S-GW; and the S1-MME interface 428, which is the signaling interface between the RAN node 414 or 416 and MMEs.

[0066] Figure 5 An example of infrastructure equipment 500 is shown in accordance with various embodiments. The infrastructure equipment 500 can be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any of the other elements / devices discussed herein. In other examples, the infrastructure equipment 500 can be implemented in or by a UE.

[0067] The infrastructure equipment 500 includes application circuitry 502, baseband circuitry 504, one or more radio front end modules (RFEMs) 506, memory circuitry 508, power management integrated circuitry (PMIC 510), power control circuitry 512, network controller circuitry 514, network interface connector 520, satellite positioning circuitry 516, and user interface circuitry 518. In some embodiments, the infrastructure equipment 500 can include additional elements such as memory / storage, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components can be included in more than one device. For example, said circuitries can be individually included in more than one device for CRAN, vBBU, or other like implementations. The application circuitry 502 includes one or more processors 522, shown as processor A 504 and processor B 506, and a memory 530. The processor(s) 522 can be a general-purpose microprocessor, a microcontroller, a reduced instruction set computer (RISC) processor, a complex instruction set computer (CISC) processor, a graphics processor unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a programmable logic array (PLA), a field programmable gate array (FPGA), or the like. The processor(s) 522 can each execute a portion of the instructions or all of the instructions of the application logic 532, the operating system 534, and / or the user interface 536. The application circuitry 502 can further include a bus interface 524 to couple the application circuitry 502 to a bus 528. The bus 528 can interconnect the application circuitry 502, the baseband circuitry 504, and other components of the infrastructure equipment 500. The bus interface 524 can include a bus bridge, an input / output (I / O) controller, and a memory controller, among others. The application circuitry 502 can include one or more memory interfaces 530 to couple the application circuitry 502 to memory. The memory interfaces 530 can include a memory controller. 2The application circuit 502 may include a C or general-purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuit 502 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure apparatus 500. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0068] The processor of application circuit 502 may include, for example, one or more processor cores (CPU), one or more application processors, one or more graphics processing units (GPUs), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuit 502 may include or may be a dedicated processor / controller for operation according to the various embodiments herein. As an example, the processor of application circuit 502 may include one or more Intel processors / controllers. or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium™, Inc. MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some implementations, the infrastructure equipment 500 may not utilize the application circuitry 502 and may instead include a dedicated processor / controller to process, for example, IP data received from the EPC or 5GC.

[0069] In some implementations, the application circuitry 502 can include one or more hardware accelerators, which can be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators can include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing devices can be one or more field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), or the like; ASICs, such as structured ASICs, or the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuitry 502 can include logic blocks or logic fabric, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and so on, of the various embodiments discussed herein. In

[0070] The user interface circuitry 518 can include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 500 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 500. User interfaces can include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display or display screen, etc. Peripheral component interfaces can include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, a audio jack, a power supply interface, etc.

[0071] The radio front end modules 506 can include millimeter wave (mmWave) radio front end modules (RFEMs) and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs can be physically separated from the mmWave RFEMs. The RFICs can include connections to one or more antennas or antenna arrays, and the RFEMs can be connected to multiple antennas. In alternative implementations, radio functions for both mmWave and sub-mmWave can be implemented in the same physical radio front end module 506 that incorporates both mmWave and sub-mmWave antennas.

[0072] The memory circuit 508 can include one or more of the following: volatile memory, including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), including flash memory, phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and can be implemented in conjunction with and three-dimensional (3D) Crosspoint (XPOINT) memory of Intel® and Micron®. The memory circuit 508 can be implemented as one or more of a solder-down package integrated circuit, a socketed memory module, and a plug-in memory card.

[0073] The PMIC 510 can include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry can detect one or more of brown out (under-voltage) and power surge (over-voltage) conditions. The power tee circuit 512 can provide for electrical power drawn from a network cable to provide both power supply and data connectivity using a single cable for the infrastructure equipment 500.

[0074] The network controller circuit 514 can provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol

[0075] The positioning circuitry 516 includes circuitry to receive and decode signals transmitted / broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include United States’ Global Positioning System (GPS), Russia’s Global Navigation System (GLONASS), the European Union’s Galileo system, China’s BeiDou Navigation Satellite System, a regional navigation system, or GNSS augmentation system (e.g., NavIC utilizing the Indian constellation, the Japanese QZSS, the French DORIS, etc.), or the like. The positioning circuitry 516 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of a positioning network, such as navigation satellite constellations. In some embodiments, the positioning circuitry 516 can include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuitry 516 can also be part of, or interact with, the baseband circuitry 504 and / or radio front end modules 506 to communicate with the nodes and components of the positioning network. The positioning circuitry 516 can also provide location Figure 5 The illustrated components may 2 C interface, SPI interface, point-to-point interface, and power supply bus, among others.

[0076] Figure 6 An example of a platform 600, in accordance with various embodiments, is shown. In embodiments, the computer platform 600 can be suitable to operate as a UE, application server, and / or any of the other elements / devices discussed herein. The platform 600 can include any combination of the components shown in the example. The components of platform 600 may Figure 6 The block diagram of the computer platform 600 is intended to illustrate a high-level view of the components of the computer platform 600. However, some of the components shown can be omitted in some embodiments, additional components can be present, and different arrangements of the components shown can occur in other embodiments.

[0077] Application circuitry 602 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces (such as SPI), I / O circuitry, memory 2 C or general purpose programmable serial interface modules, RTC, timers-counters (including interval and watchdog timers), general purpose IO, memory card controllers (such as SDMMC or similar), USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 602 can be coupled with or include memory / storage elements and can be configured to TM execute instructions stored in the memory / storage elements to enable various applications or operating systems to run on the platform 600. In some implementations, the memory / storage elements can be on-chip memory circuitry, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and / or any other type of memory

[0078] The processors of the application circuitry 602 can include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-core processing devices, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuitry 602 can comprise or be a special-purpose processor / controller to operate

[0079] As examples, the processors of the application circuitry 602 can include Intel Architecture Core TM processors, such as Quark TM , Atom TM , i3, i5, i7, or MCU-class processors, or another such processor available from Intel Corporation. The processors of the application circuitry 602 can also be one or more of Advanced Micro Devices (AMD) Ryzen processors or Accelerated Processing Units (APUs); AS-A9 processors from ARM Holdings; Artisan Inc. InterAptiv Qualcomm® Snapdragon TM processors from Texas Instruments, Inc. Open Multimedia Applications Platform (OMAP) TM processors from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd. such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; and the like. In some implementations, the application circuitry 602 can be a part of a system on a chip (SoC) that includes other components such as a graphics processing unit (GPU), a digital signal processor (DSP), a modem, a Edison TM or Galileo TM SoC board.

[0080] Additionally or alternatively, the application circuitry 602 can include circuitry such as, but not limited to, one or more field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuitry 602 can include logic blocks or logic fabric, as well as other interconnected resources that can be programmed to perform various functionalities, such as the procedures, methods, functions and so on, of the various embodiments discussed herein. In such implementations, the circuitry of the application circuitry 602 can include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse, etc.)) used to store logic blocks, logic fabric, data, and the like in look-up tables (LUTs) and the like.

[0081] The baseband circuitry 604 can be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module including two or more integrated circuits.

[0082] The radio front end modules 606 can include millimeter wave (mmWave) radio front end modules (RFEMs) and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs can be physically separated from the mmWave RFEMs. The RFICs can include connections to one or more antennas or antenna arrays, and the RFEMs can be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions can be implemented in the same physical radio front end module 606 that incorporates both mmWave antennas and sub-mmWave.

[0083] The memory circuit 608 can include any number and type of memory devices to provide a given amount of system memory. For example, the memory circuit 608 can include one or more of volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), including flash memory, phase change RAM (PRAM), magnetoresistive RAM (MRAM), etc. The memory circuit 608 can be developed according to Joint Electron Devices and Three-dimensional (3D) Crosspoint (XPOINT) memory from Intel® and Micron®.

[0084] The removable memory circuitry 626 can include devices, circuitry, enclosures / housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 600. These portable data storage devices can be used for mass storage and can include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, etc.), and USB flash drives, optical discs, external HDDs, etc.

[0085] The platform 600 can also include interface circuitry (not shown) for connecting external devices with the platform 600. The external devices connected to the platform 600 via the interface circuitry include sensors 622 and electro-mechanical components (shown as EMC 624), as well as removable memory devices coupled to the removable memory 626.

[0086] The sensors 622 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a micro-electro-mechanical system (MEMS) or nano-electromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric sensor; a gravimeter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other like audio capture device; etc.

[0087] The EMCs 624 include devices, modules, or subsystems configured to change the state, position, and / or orientation of the platform 600, move or control movement of mechanisms or (sub)systems, and / or control one or more functions of the platform 600. The EMCs 624 can be configured to generate and send messages / signals to other components of the platform 600 in order to alter the state, position, and / or orientation of the platform 600. Examples of EMCs 624 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electro-mechanical components. In embodiments, the platform 600 is configured to operate one or more EMCs 624 based on one or more captured events and / or instructions or control signals received from a service provider and / or various clients. In some implementations, the interface circuitry can connect the platform 600 with the positioning circuitry 616. The positioning circuitry 616 includes circuitry to receive and decode signals transmitted / broadcasted by a positioning network of GNSSs. Examples of navigation satellite constellations (or GNSSs) can include United States’ GPS, Russia’s GLONASS, the European Union’s Galileo system, China’s BeiDou Navigation Satellite System, a regional navigation system, or a GNSS augmentation system (e.g., NAVIC, Japan’s QZSS, France’s DORIS, etc.), among others. The positioning circuitry 616 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 616 can include a Micro-PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuitry 616 can also be part of, or interact with, the baseband circuitry 604 and / or radio front end modules 606 to communicate with the nodes and components of the positioning network. The positioning circuitry 616 can also provide location and / or time data to the application circuitry 602, which can use this data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, etc.

[0088] In some implementations, the interface circuitry can connect the platform 600 with near-field communication circuitry (shown as NFC circuitry 612). The NFC circuitry 612 is configured to provide contactless proximity communications based on radio-frequency identification (RFID) standards, with magnetic field induction being used to enable communication between the NFC circuitry 612 and an external NFC-enabled device (e.g., an “NFC touchpoint”) outside of the platform 600. The NFC circuitry 612 includes an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller can be a chip / IC that provides NFC functionality to the NFC circuitry 612 by executing NFC controller firmware and an NFC stack. The NFC stack is executable by the processor to control the NFC controller, and the NFC controller firmware is executable by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals can power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 612, or initiate a data transfer between the NFC circuitry 612 and another active NFC device (e.g., a smartphone or NFC-enabled POS terminal) that is proximate to the platform 600.

[0089] The drive circuits 618 can include software and hardware elements that are configured to control particular devices embedded in or otherwise coupled with the platform 600. The drive circuits 618 can include individual drivers that allow the other components of the platform 600 to interact with or control various input / output (I / O) devices that can be present in or connected to the platform 600. For example, the drive circuits 618 can include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 600, a sensor driver to obtain sensor readings of sensors 622 and control and allow access to the sensors 622, an EMC driver to obtain actuator positions of the EMCs 624 and / or control and allow access to the EMCs 624, a camera driver to control and allow access to an embedded image capture device, an audio driver to control and allow access to one or more audio devices.

[0090] A power management integrated circuit (shown as PMIC 610) (also referred to as a “power management circuitry”) can manage power for the various components of the platform 600. In particular, with respect to the baseband circuitry 604, the PMIC 610 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 610 can typically be included on the device when the platform 600 is capable of being powered by a battery 614, for example, when the device is included in a UE.

[0091] In some embodiments, the PMIC 610 can control, or otherwise be part of, various power-saving mechanisms of the platform 600. For example, if the platform 600 is in an RRC_Connected state, in which it is still connected to the RAN node as it expects to receive traffic shortly, then the platform 600 can enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 600 can power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 600 can transition off to an RRC_Idle state in which it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 600 goes into a very low power state and

[0092] The battery 614 can power the platform 600, although in some examples the platform 600 can be mounted deployed in a fixed location, and can have a power supply coupled to an electrical grid. The battery 614 can be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and so forth. In some implementations, such as in V2X applications, the battery 614 can be a typical lead- acid automotive battery.

[0093] In some implementations, the battery 614 can be a“smart battery” that includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS can be included in the platform 600 to track the state of charge (SoCh) of the battery 614. The BMS can be used to monitor other parameters of the battery 614 such as the state of health (SoH) and the state of function (SoF) of the battery 614 to provide fault predictions. The BMS can communicate the information of the battery 614 to the application circuitry 602 or other components of the platform 600. The BMS can also include an analog-to-digital (ADC) converter that allows the application circuitry 602 to directly monitor the voltage of the battery 614 or the current flow from the battery 614. The battery parameters can be used by the

[0094] A power block or other power source coupled to the electrical grid can be coupled with the BMS to charge the battery 614. In some examples, the power block can be replaced with a wireless power receiver to wirelessly acquire power, e.g., through a loop antenna in the computer platform 600. In these examples, a wireless battery charging circuit can be included in the BMS. The particular charging circuit chosen can depend on the size of the battery 614, and thus the current required. Charging can be performed using the aviation fuel standard published by the Airline Fuel Consortium, the Qi wireless charging standard published by the Wireless Power Consortium, or the Rezence charging standard published by the Alliance for Wireless Power.

[0095] The user interface circuitry 620 includes various input / output (I / O) devices found within or connected to the platform 600 and includes one or more user interfaces designed to enable user interaction with the platform 600 and / or peripheral component interfaces designed to enable peripheral component interaction with the platform 600. The user interface circuitry 620 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual means for entering or providing input to the platform 600 including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. The output device circuitry can include any number and / or combinations of audio or visual display, including inter alia one or more simple visual output / indicators, such as binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCD), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced from the operation of the platform 600. The output device circuitry can also include a speaker or other audio emission device, a printer, etc. In some embodiments, the sensors 622 can function as input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs can function as output device circuitry (e.g., actuators to provide tactile feedback, etc.). In another example, NFC circuitry can be included to read electronic tags and / or connect with another NFC-enabled device, the NFC circuitry including an NFC controller coupled with an antenna element and a processing device. The peripheral component interface can include, without limitation, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

[0096] Although not shown, the components of platform 600 can communicate using suitable buses or interconnects (IX) technologies which can include any number of technologies, including ISA, EISA, PCI, PCIx, PCI Express, a Time-Triggered Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX can be a proprietary bus / IX, such as that used in a bus / IX system designed for SoC or other purposes. Other bus / IX systems can be used, such as I 2 C interface, SPI interface, point-to-point interface, and power supply bus, among others.

[0097] Figure 7 Example components of the device 700 are illustrated. In some embodiments, the device 700 can include application circuitry 706, baseband circuitry 704, radio frequency (RF) circuitry (shown as RF circuitry 702), front-end module (FEM) circuitry (shown as FEM circuitry 732), one or more antennas 730, and power management circuitry (PMC) (shown as PMC 734) coupled together as shown in the figure. The components of the illustrated device 700 can include in a UE or a RAN node. In some embodiments, the device 700 can include fewer elements (for example, a RAN node can not utilize application circuitry 706, and instead include a processor / controller to process IP data

[0098] The application circuitry 706 can include one or more application processors. For example, the application circuitry 706 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The one or more processors of the application circuitry 706 can include any combination of general-purpose processors, multi-core processors, dedicated processors, and graphics processors. These 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 and / or operating systems to run on the device 700. In some embodiments, the processors of the application circuitry 706 can process IP data packets received from the EPC.

[0099] The baseband circuitry 704 can include circuitry such as one or more single-core or multi-core processors. The baseband circuitry 704 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 702 and to generate baseband signals for a transmit signal path of the RF circuitry 702. The baseband circuitry 704 can interface with the application circuitry 706 for generation and processing of the baseband signals and for control of at least

[0100] In some embodiments, the baseband circuitry 704 can include a digital signal processor (DSP), such as one or more audio DSPs 718. The audio DSP(s) 718 can include elements for compression / decompression and echo cancellation, and can include other suitable processing elements in other embodiments. In some embodiments, components of the baseband circuitry can be combined on a single chip or set of chips, or set on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuitry 704 and the application circuitry 706 can be implemented together in a system on a chip (SoC).

[0101] In some embodiments, the baseband circuitry 704 can provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 704 can support communication with 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). Baseband circuitry 704 in which the baseband circuitry 704 is configured to support wireless communication according to more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0102] RF circuitry 702 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 702 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 702 can include a receive signal path, which can include circuitry to down-convert RF signals received from the FEM circuitry 732 and provide baseband signals to the baseband circuitry 704. RF circuitry 702 can also include a transmit signal path, which can include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 732 for transmission.

[0103] In some embodiments, the receive signal path of the RF circuitry 702 can include mixer circuitry 722, amplifier circuitry 724 and filter circuitry 726. In some embodiments, the transmit signal path of the RF circuitry 702 can include filter circuitry 726 and mixer circuitry 722. RF circuitry 702 can also include synthesizer circuitry 728 for synthesizing a frequency for use by the mixer circuitry 722 of the receive signal path and / or the transmit signal path. In some embodiments, the mixer circuitry 722 of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 732 based on the synthesized frequency provided by synthesizer circuitry 728. The amplifier circuitry 724 can be configured to amplify the down-converted signals, and the filter circuitry 726 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 704 for further processing. In some embodiments, the output baseband signals can be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 722 of the receive signal path can include passive mixers, although the scope of the embodiments is not limited in this respect.

[0104] In some embodiments, the mixer circuitry 722 of the transmit signal path can be configured to up-convert input baseband signals based on synthesis frequencies provided by the synthesizer circuitry 728 to generate RF output signals for the FEM circuitry 732. The baseband signals can be provided by the baseband circuitry 704 and can be filtered by filter circuitry 726.

[0105] In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 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 embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 can be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path can be configured for superheterodye operation.

[0106] In some embodiments, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternative embodiments, the RF circuitry 702 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 can include a digital baseband interface to communicate with the RF circuitry 702.

[0107] In some dual-mode embodiments, separate radio ICs can be provided for processing signals for the

[0108] In some embodiments, the synthesizer circuitry 728 can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 728 can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer that includes a phase-locked loop with a frequency divider.

[0109] The synthesizer circuitry 728 can be configured to synthesize an output frequency for use by the mixer circuitry 722 of the RF circuitry 702 based on a frequency input and a divider control input. In some embodiments, synthesizer circuitry 728 can be a fractional N / N+1 synthesizer.

[0110] In some embodiments, the frequency input can be provided by a voltage-controlled oscillator (VCO), although this is not a requirement. The divider control input can be provided by the baseband circuitry 704 or application circuitry 706, such as an application processor, in accordance with the desired output frequency. In some embodiments, the divider control input (e.g., N) can be determined from a look-up table based on the channel indicated by the application circuitry 706.

[0111] Synthesizer circuitry 728 of the RF circuitry 702 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, 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 embodiments, 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 embodiments, the delay elements can be configured to divide the VCO period by Nd, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help assure that the total delay through the delay line is one VCO cycle.

[0112] In some embodiments, synthesizer circuitry 728 can be configured to generate a carrier frequency as an output frequency, while in other embodiments, 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 embodiments, the output frequency can be a LO frequency (fLO). In some embodiments, the RF circuitry 702 can include an IQ / polar converter.

[0113] FEM circuitry 732 can include a receive signal path, which can include circuitry configured to operate on RF signals received from one or more antennas 730, amplify the received signal and provide the amplified version of the received signal to the RF circuitry 702 for further processing. FEM circuitry 732 can also include a transmit signal path, which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 702 for transmission by one or more of the one or more antennas 730. In various embodiments, the amplification through the transmit or receive signal paths can be done solely in the RF circuitry 702, solely in the FEM circuitry 732, or in both the RF circuitry 702 and the FEM circuitry 732.

[0114] In some embodiments, the FEM circuitry 732 can include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 732 can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 732 can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 702). The transmit signal path of the FEM circuitry 732 can include a power amplifier (PA) to amplify signals for transmission (e.g., by one or more of the antennas 730) and one or more filters to generate RF signals for subsequent transmission.

[0115] In some embodiments, the PMC 734 can manage power provided to the baseband circuitry 704. In particular, the PMC 734 can control power-source selection, voltage scaling, battery-charging, or DC-to-DC conversion. The PMC 734 can typically be included on the device 700 when the device 700 is capable of being powered by a battery, for example when the device 700 is included in a UE. The PMC 734 can increase the power conversion efficiency in providing the desired implementation size and heat dissipation characteristics.

[0116] Figure 7 The PMC 734 is shown to be coupled to only the baseband circuitry 704. However, in other embodiments, the PMC 734 can be coupled to and perform similar power management operations for other components such as, but not limited to, the application circuitry 706, the RF circuitry 702, or the FEM circuitry 732.

[0117] In some embodiments, the PMC 734 can control, or otherwise be part of, various power saving mechanisms of the device 700. For example, if the device 700 is in an RRC_Connected state, where it is still connected to a RAN node as it expects a traffic shortly, after a period of inactivity, the device 700 can enter a state known as Discontinuous Reception Mode (DRX) during which it periodically wakes up to receive data while it sleeps in between. During that state, the device 700 can power down for periods of time which can save power.

[0118] If there is no data traffic activity for an extended period of time, the device 700 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 700 in this state wakes up periodically to listen to the network and then powers down, which can be a power saving mechanism. While in RRC_Idle state, the device 700 can transition quickly to RRC_Connected state, if there is data traffic activity to process.

[0119] An additional power saving mode can leave a device unable to use the network for longer than a paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network, and can be completely powered off. Any data sent during this time incurs a large delay, and the delay is assumed to be acceptable.

[0120] The processors of application circuitry 706 and the processors of baseband circuitry 704 can be used to execute instructions for one or more instances of a protocol stack. For example, the processors of baseband circuitry 704 can individually or in combination be used to execute layer 3, layer 2, or layer 1 functions of the protocol stack, while the processors of application circuitry 706 can utilize data received by these layers (e.g., packet data) and further execute layer 4 functions (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, layer 3 can include a radio resource control (RRC) layer, described in further detail below. As referred to herein, layer 2 can include 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 include a physical (PHY) layer of a UE / RAN node, described in further detail below.

[0121] Figure 8 An exemplary interface 800 of baseband circuitry, in accordance with some embodiments, is shown. As described above, Figure 7 The baseband circuitry 704 of FIG. 9 can include a 3G baseband processor 708, a 4G baseband processor 710, a 5G baseband processor 712, other baseband processor(s) 714, a CPU 716, and memory 720 for the processors. As shown, each of the processors can include a respective memory interface 802 to send / receive data to / from the memory 720.

[0122] The baseband circuitry 704 can also include one or more interfaces to communicate with other circuitries / devices, such as a memory interface 804 (e.g., an interface to send / receive data, addresses, and control signals to / from memory external to the baseband circuitry 704), an application circuitry interface 806 (e.g. an interface to send / receive data, addresses, and control signals to / from an application circuitry 706 external to the baseband circuitry 704), an RF circuitry interface 808 (e.g. an interface to send / receive data, addresses, and control signals to / from an RF circuitry 702 external to the baseband circuitry 704), a wireless hardware connectivity interface 810 (e.g. an interface to send / receive data, addresses, and control signals to / from near-field communication (NFC) components, Bluetooth® components, Wi-Fi® components, and other communication components), a power management interface 812 (e.g. an interface to send / receive power or control signals to / from a power management circuitry 734), and a power control interface 814 (e.g. an interface to send / receive data, addresses, and control signals to / from a power control circuitry 736). Figure 7 The application circuitry 706 can include one or more application processors 718, which can be implemented as one or more cores of a single processing unit or as multiple processing units. The application circuitry 706 can handle a variety of applications including operating systems, user applications, platform services, and so on. The application circuitry 706 can also include a memory controller 720 to operate on and communicate with the memory 704. The memory controller 720 can include a processor to operate on and communicate with the memory 704. Figure 7 The RF circuitry 702 can include a receive signal path, which can include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704. The RF circuitry 702 can also include a transmit signal path, which can include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission. The RF circuitry 702 can include a receive signal path, which can include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704. The RF circuitry 702 can also include a transmit signal path, which can include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission. The RF circuitry 702 can include a receive signal path, which can include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704. The RF circuitry 702 can also include a transmit signal path, which can include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission. The RF circuitry 702 can include a receive signal path, which can include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704. The RF circuitry 702 can also include a transmit signal path, which can include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.

[0123] Figure 9 is a block diagram illustrating a component 900 that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and that can perform any one or more of the methodologies discussed herein, according to some example embodiments. Specifically, Figure 9 A diagram is shown illustrating a high-level architecture of a hardware resource 902, including one or more processors 906 (or processor cores), one or more memory / storage devices 914, and one or more communication resources 924, each of which can be communicatively coupled via a bus 916. For embodiments wherein node virtualization (e.g., NFV) is utilized, a hypervisor 922 can be executed to provide an execution environment for one or more network slices / substrlices to utilize the hardware resources 902.

[0124] The processors 906 (e.g., a central processing unit (CPU), a reduced instruction set computer (RISC) processor, a complex instruction set computer (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor 908 and a processor 910.

[0125] The memory / storage devices 914 can include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 914 can include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0126] The communication resources 924 can include interconnection devices or network interface components or other suitable devices to communicate with one or more peripheral devices 904 or one or more databases 920 via a network 918. For example, the communication resources 924 can include wired communication devices (e.g., for coupling via a universal serial bus (USB)), cellular communication devices, NFC devices, components (e.g., low-power), components, and other communication devices.

[0127] The instructions 912 can include software, programs, applications, applets, applications, or other executable code that when executed by at least one of the processors 906 perform any of the methods discussed herein. The instructions 912 can reside entirely or a portion of the instructions 912 can reside entirely or a portion of the instructions 912 can reside entirely within at least one of the processors 906 (e.g., within the cache memory of the processor), the memory / storage devices 914, or any suitable combination thereof. Furthermore, any portion of the instructions 912 can be transferred between or among any combination of the hardware resources 902, the peripheral devices 904, and the databases 920. Accordingly, the memory of processors 906, the memory / storage devices 914, the peripheral devices 904, and the databases 920 are examples of computer-readable and machine-readable media.

[0128] For one or more embodiments, at least one of the components illustrated in one or more of the preceding figures can be configured to perform one or more operations, techniques, processes, and / or methods described in the Example section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures can be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the preceding figures can be configured to operate according to one or more of the examples illustrated in the Example section below.

[0129] Example section

[0130] The following embodiments relate to additional embodiments.

[0131] Example 1A can include an apparatus of a user equipment (UE), the apparatus comprising: one or more processors; and a memory storing instructions that when executed by the one or more processors configure the apparatus to: generate a message for transmission to a base station, the message comprising an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacings (SCS); process, based on the capability of the UE for CCS with different SCS, a plurality of unicast downlink control information (DCI) per physical downlink control channel (PDCCH) monitoring occasion per span to determine scheduling resources for downlink (DL) and uplink (UL) signaling or channels; and process the DL and UL signaling or channels using the scheduling resources.

[0132] Example 2A can include the apparatus of Example 1A, wherein the indication comprises support for a first component carrier (CC) scheduling the scheduled resources on a second CC, wherein: the first CC has a smaller SCS than the SCS of the second CC; the first CC has a larger SCS than the SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

[0133] Example 3A can include the apparatus of Example 1A, wherein the indication comprises support for a first component carrier (CC) scheduling the scheduled resources on a second CC, wherein: the first CC has a 15 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 60 kHz SCS; or the first CC has a 120 kHz SCS and the second CC has a 120 kHz SCS.

[0134] Example 4A can include the apparatus of Example 1A, wherein the indication comprises a separate capability to support each of one or more feature groups (FGs).

[0135] Example 5A can include the apparatus of Example 4A, wherein the one or more feature groups comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

[0136] Example 6A can include the apparatus of Example 1A, wherein the indication comprises a support of a particular number of unicast DCIs per span per monitoring occasion, wherein: the particular number comprises a single number representing a maximum sum of unicast DL DCIs and unicast UL DCIs; or the particular number comprises a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs.

[0137] Example 7A can include the apparatus of Example 1A, wherein the indication comprises a support of a list of possible combinations of unicast DL DCIs and unicast UL DCIs per span per monitoring occasion, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL DCIs and unicast UL DCIs and a second number representing a maximum number of unicast DL DCIs or unicast UL DCIs.

[0138] Example 8A can include the apparatus of Example 1A, wherein the indication comprises a support of a particular number of unicast DCIs per span per monitoring occasion, wherein: the particular number comprises a fraction of a first number representing a number of unicast DCIs divided by a second number representing a number of spans, wherein the second number is greater than the first number.

[0139] Example 9A can include a method of wireless communication by a user equipment (UE), the method comprising: generating a message for transmission to a base station, the message comprising an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacings (SCS); processing, based on the capability of the UE for CCS with different SCS, a number of unicast downlink control information (DCIs) per span per physical downlink control channel (PDCCH) monitoring occasion to determine scheduling resources for downlink (DL) and uplink (UL) signaling or channels; and processing the DL and UL signaling or channels using the scheduling resources.

[0140] Example 10A can include a method as described in example 9A, wherein the indication comprises support for a first component carrier (CC) scheduling the scheduled resources on a second CC, wherein: the first CC has a smaller SCS than the SCS of the second CC; the first CC has a larger SCS than the SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

[0141] Example 11A can include a method as described in example 9A, wherein the indication comprises support for a first component carrier (CC) scheduling the scheduled resources on a second CC, wherein: the first CC has a 15 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 60 kHz SCS; or the first CC has a 120 kHz SCS and the second CC has a 120 kHz SCS.

[0142] Example 12A can include a method as described in example 9A, wherein the indication comprises a separate capability to support each of one or more feature groups (FGs).

[0143] Example 13A can include a method as described in example 12A, wherein the one or more feature groups comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

[0144] Example 14A can include a method as described in example 9A, wherein the indication comprises a support of a particular number of unicast DCIs per span per monitoring occasion, wherein: the particular number comprises a single number representing a maximum sum of unicast DL DCIs and unicast UL DCIs; or the particular number comprises a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs.

[0145] Example 15A can include a method as described in example 9A, wherein the indication comprises a support of a list of possible combinations of unicast DL DCIs and unicast UL DCIs per span per monitoring occasion, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL DCIs and unicast UL DCIs and a second number representing a maximum number of unicast DL DCIs or unicast UL DCIs.

[0146] Example 16A can include a method as described in example 9A, wherein the indication comprises a support of a particular number of unicast DCIs per span per monitoring occasion, wherein: the particular number comprises a fraction of a first number representing a number of unicast DCIs divided by a second number representing a number of spans, wherein the second number is greater than the first number.

[0147] Example 17A can include a computer-readable storage medium comprising instructions that, when executed by one or more processors of a user equipment (UE) configured to recover the UE from limited service due to misconfiguration, cause the one or more processors to: process a message received from a user equipment (UE), the message comprising an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacings (SCS); and schedule, based on the indication, a plurality of unicast downlink control information (DCI) per physical downlink control channel (PDCCH) per monitoring occasion per span.

[0148] Example 18A can include the computer-readable storage medium of Example 17A, wherein the indication comprises support for a first component carrier (CC) to schedule resources on a second CC, wherein: the first CC has a smaller SCS than the SCS of the second CC; the first CC has a larger SCS than the SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

[0149] Example 19A can include the computer-readable storage medium of Example 17A, wherein the indication comprises support for a first component carrier (CC) to schedule resources on a second CC, wherein: the first CC has a 15 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 60 kHz SCS; or the first CC has a 120 kHz SCS and the second CC has a 120 kHz SCS.

[0150] Example 20A can include the computer-readable storage medium of Example 17A, wherein the indication comprises a separate capability to support each of one or more feature groups (FGs).

[0151] Example 21A can include the computer-readable storage medium of Example 20A, wherein the one or more feature groups comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

[0152] Example 22A can include the computer-readable storage medium of Example 17A, wherein a number of unicast DCIs scheduled by the base station comprises a single number that is less than or equal to a maximum sum of unicast DL DCIs and unicast UL DCIs included in the indication of the UE capability.

[0153] Example 23A can include the computer-readable storage medium of Example 17A, wherein the indication comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein the particular number comprises a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs.

[0154] Example 24A can include the computer-readable storage medium of Example 17A, wherein the indication comprises a support of a list of possible combinations of unicast DL DCIs and unicast UL DCIs per monitoring occasion per span, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL DCIs and unicast UL DCIs and a second number representing a maximum number of unicast DL DCIs or unicast UL DCIs.

[0155] Example 25A can include the computer-readable storage medium of Example 17A, wherein the indication comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number comprises a fraction of a first number representing a number of unicast DCIs divided by a second number representing a number of spans, wherein the second number is greater than the first number.

[0156] Example 26A can include a method of wireless communication by a base station, the method comprising: processing a message received from a user equipment (UE), the message comprising an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacings (SCS); and scheduling a plurality of unicast downlink control information (DCI) per physical downlink control channel (PDCCH) per monitoring occasion per span based on the indication.

[0157] Example 27A can include the method of Example 26A, wherein the indication comprises support for a first component carrier (CC) scheduling resources on a second CC, wherein: the first CC has a smaller SCS than the SCS of the second CC; the first CC has a larger SCS than the SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

[0158] Example 28A can include the method of Example 26A, wherein the indication comprises support for a first component carrier (CC) scheduling resources on a second CC, wherein: the first CC has a 15 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 60 kHz SCS; or the first CC has a 120 kHz SCS and the second CC has a 120 kHz SCS.

[0159] Example 29A can include a method as described in or related to any of example 26A, wherein the indication includes a separate capability to support each of one or more feature groups (FGs).

[0160] Example 30A can include a method as described in or related to example 29A, wherein the one or more feature groups include at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

[0161] Example 31A can include a method as described in or related to example 26A, wherein the number of unicast DCIs scheduled by the base station includes a single number that is less than or equal to a maximum sum of unicast DL DCIs and unicast UL DCIs included in the indication of the UE capability.

[0162] Example 32A can include a method as described in or related to example 26A, wherein the indication includes support for processing a particular number of unicast DCIs per monitoring occasion per span, wherein the particular number includes a first number representing a maximum number of unicast DL DCIs and a second number representing a maximum number of unicast UL DCIs.

[0163] Example 33A can include a method as described in or related to example 26A, wherein the indication includes support for processing a list of possible combinations of unicast DL DCIs and unicast UL DCIs per monitoring occasion per span, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL DCIs and unicast UL DCIs and a second number representing a maximum number of unicast DL DCIs or unicast UL DCIs.

[0164] Example 34A can include a method as described in or related to example 26A, wherein the indication includes support for processing a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number includes a fraction of a first number representing a number of unicast DCIs divided by a second number representing a number of spans, wherein the second number is greater than the first number.

[0165] Example 1B can include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above examples or any other method or process described herein.

[0166] Example 2B can include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of the above examples or any other method or process described herein.

[0167] Example 3B can include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of the preceding examples or any other method or process described herein.

[0168] Example 4B can include a method, technique, or process as described in or related to any of the preceding examples or portions or parts thereof.

[0169] Example 5B can include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process as described in or related to any of the preceding examples or portions thereof.

[0170] Example 6B can include a signal as described in or related to any of the preceding examples or portions thereof.

[0171] Example 7B can include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of the preceding examples or portions thereof, or otherwise described in the present disclosure.

[0172] Example 8B can include a signal encoded with data as described in or related to any of the preceding examples or portions thereof, or otherwise described in the present disclosure.

[0173] Example 9C can include a signal encoded with a datagram, packet, frame, segment, PDU, or message as described in or related to any of the preceding examples or portions thereof, or otherwise described in the present disclosure.

[0174] Example 10B can include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process as described in or related to any of the preceding examples or portions thereof.

[0175] Example 11B can include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process as described in or related to any of the preceding examples or portions thereof.

[0176] Example 12B can include a signal in a wireless network as shown and described herein.

[0177] Example 13B can include a method of communicating in a wireless network as shown and described herein.

[0178] Example 14B can include a system for providing wireless communication as shown and described herein.

[0179] Example 15B can include a device for providing wireless communication as shown and described herein.

[0180] Any of the above-described embodiments can be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides functionality and / or technical advantages, but do not limit the implementations to the precise form described. Modifications and variations are possible in light of the above teachings or can be acquired from practice of the implementations. Numerous specific implementations have been discussed herein for purposes of illustration. Various modifications and changes can be made to these implementations, in light of the above teachings.

[0181] Embodiments and implementations of the systems and methods described herein can include various operations, which can be embodied in machine-executable instructions to be executed by a computer system. The computer system can include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system can include hardware components, including specific logic for performing the operations, or can include a combination of hardware, software, and / or firmware.

[0182] It will be recognized that the systems described herein include descriptions of specific implementations. These implementations can be combined, partially combined, separated into multiple systems, or otherwise divided or combined in other ways. Further, it is contemplated that parameters, attributes, aspects, etc. of one implementation can be used in another implementation. For clarity, these parameters, attributes, aspects, etc. are only described in one or more implementations, and it will be recognized that these parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another implementation unless specifically stated otherwise.

[0183] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a way to minimize risk of unintentional or unauthorized access or use, and the nature of authorization should be clearly expressed to the users.

[0184] While the foregoing is directed to implementations, alternatives and modifications will be apparent to those skilled in the art from consideration of the specification and / or practice of the implementations. Therefore, it is intended that the claims be interpreted as including all such alternatives and modifications.

Claims

1. An apparatus of a user equipment (UE), the apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, configure the apparatus to: generate a message for transmission to a base station, the message including an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacing (SCS), wherein the indication includes a list of possible combinations of per-span per-monitoring occasion processing of unicast downlink (DL) scheduling downlink control information (DCI) and unicast uplink (UL) scheduling DCI, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL scheduling DCI and unicast UL scheduling DCI and a second number representing a maximum number of unicast DL scheduling DCI or unicast UL scheduling DCI; process, based on the capability of the UE for CCS with different SCS, multiple unicast DCIs per physical downlink control channel (PDCCH) monitoring occasion per span to determine scheduling resources for DL and UL signaling or channels; and process the DL and UL signaling or channels using the scheduling resources.

2. The apparatus of claim 1, wherein the indication further includes support for a first component carrier (CC) scheduling the scheduling resources on a second CC, wherein: the first CC has a smaller SCS than a SCS of the second CC; the first CC has a larger SCS than a SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

3. The apparatus of claim 1, wherein the indication further includes support for a first component carrier (CC) scheduling the scheduling resources on a second CC, wherein: the first CC has a SCS of 15 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 15 kHz; ​ the first CC has a SCS of 60 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 60 kHz; or the first CC has a SCS of 120 kHz and the second CC has a SCS of 120 kHz.

4. The apparatus of claim 1, wherein the indication further comprises a separate capability to support each of one or more feature groups (FGs).

5. The apparatus of claim 4, wherein the one or more FGs comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

6. The apparatus of claim 1, wherein the indication further comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number comprises a single number representing a maximum sum of the unicast DL scheduling DCIs and unicast UL scheduling DCIs; or the particular number comprises a third number representing a maximum number of the unicast DL scheduling DCIs and a fourth number representing a maximum number of the unicast UL scheduling DCIs.

7. The apparatus of claim 1, wherein the indication further comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number comprises a fraction of a fifth number representing a number of unicast DCIs divided by a sixth number representing a number of spans, wherein the sixth number is greater than the fifth number.

8. A method for wireless communications by a user equipment (UE), comprising: generating a message for transmission to a base station, the message comprising an indication of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacings (SCSs), wherein the indication comprises a list of possible combinations of unicast downlink (DL) scheduling downlink control information (DCI) and unicast uplink (UL) scheduling DCI that the UE supports per monitoring occasion per span, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL scheduling DCI and unicast UL scheduling DCI and a second number representing a maximum number of unicast DL scheduling DCI or unicast UL scheduling DCI; processing a number of unicast DCIs per physical downlink control channel (PDCCH) monitoring occasion per span based on the capability of the UE for CCS with different SCSs to determine scheduling resources for DL and UL signaling or channels; and processing the DL and UL signaling or channels using the scheduling resources.

9. The method of claim 8, wherein the indication further comprises support for a first component carrier (CC) to schedule the scheduled resources on a second CC, wherein: the first CC has a smaller SCS than a SCS of the second CC; the first CC has a larger SCS than a SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

10. The method of claim 8, wherein the indication further comprises support for a first component carrier (CC) to schedule the scheduled resources on a second CC, wherein: the first CC has a 15 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 15 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 30 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 60 kHz SCS; the first CC has a 60 kHz SCS and the second CC has a 120 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 15 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 30 kHz SCS; the first CC has a 120 kHz SCS and the second CC has a 60 kHz SCS; or the first CC has a 120 kHz SCS and the second CC has a 120 kHz SCS.

11. The method of claim 8, wherein the indication further comprises support for individual capabilities of each of one or more feature groups (FGs).

12. The method of claim 11, wherein the one or more feature groups comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

13. The method of claim 8, wherein the indication further comprises support for a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number comprises a single number representing a maximum sum of the unicast DL scheduling DCIs and unicast UL scheduling DCIs; or the particular number comprises a third number representing a maximum number of the unicast DL scheduling DCIs and a fourth number representing a maximum number of unicast UL scheduling DCIs.

14. The method of claim 8, wherein the indication further comprises support for a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number comprises a fifth number representing a number of unicast DCIs divided by a sixth number representing a number of spans, wherein the sixth number is greater than the fifth number.

15. A non-transitory computer-readable storage medium comprising instructions that, when executed by one or more processors of a user equipment (UE) configured to schedule resources in response to a reporting capability for cross-carrier scheduling (CCS) with different subcarrier spacing (SCS), cause the one or more processors to: process a message received from a user equipment (UE), the message comprising an indication of a capability of the UE for CCS with different SCS, wherein the indication comprises a list of possible combinations of unicast downlink (DL) scheduling downlink control information (DCI) and unicast uplink (UL) scheduling DCI per monitoring occasion per span that the UE supports, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL scheduling DCI and unicast UL scheduling DCI and a second number representing a maximum number of unicast DL scheduling DCI or unicast UL scheduling DCI; and schedule a plurality of unicast DCIs per physical downlink control channel (PDCCH) per monitoring occasion per span based on the indication.

16. The non-transitory computer-readable storage medium of claim 15, wherein the indication further comprises support for a first component carrier (CC) to schedule resources on a second CC, wherein: the first CC has a smaller SCS than a SCS of the second CC; the first CC has a larger SCS than a SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

17. The non-transitory computer-readable storage medium of claim 15, wherein the indication further comprises support for a first component carrier (CC) to schedule resources on a second CC, wherein: the first CC has a SCS of 15 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 15 kHz; or the first CC has a SCS of 30 kHz and the second CC has a SCS of 30 kHz. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ the first CC has a SCS of 15 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 60 kHz; or the first CC has a SCS of 120 kHz and the second CC has a SCS of 120 kHz.

18. The non-transitory computer-readable storage medium of claim 15, wherein the indication further comprises a separate capability to support each of one or more feature groups (FGs).

19. The non-transitory computer-readable storage medium of claim 18, wherein the one or more feature groups comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

20. The non-transitory computer-readable storage medium of claim 15, wherein a number of unicast DCIs scheduled by a base station comprises a single number that is less than or equal to a maximum sum of unicast DL scheduling DCIs and unicast UL scheduling DCIs included in the indication of the UE capability.

21. The non-transitory computer-readable storage medium of claim 15, wherein the indication further comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein the particular number comprises a third number representing a maximum number of the unicast DL scheduling DCIs and a fourth number representing a maximum number of the unicast UL scheduling DCIs.

22. The non-transitory computer-readable storage medium of claim 15, wherein the indication further comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein: The particular number includes a fraction of a fifth number representing a number of unicast DCIs divided by a sixth number representing a number of spans, where the sixth number is greater than the fifth number.

23. A method for wireless communications by a base station, comprising: processing a message received from a user equipment (UE), the message including an indication by the UE of a capability of the UE for cross-carrier scheduling (CCS) with different subcarrier spacing (SCS), wherein the indication includes a list of possible combinations of per-span per-monitoring occasion processing of unicast downlink (DL) scheduling downlink control information (DCI) and unicast uplink (UL) scheduling DCI, wherein each of the possible combinations is generated based on both a first number representing a maximum sum of unicast DL scheduling DCI and unicast UL scheduling DCI and a second number representing a maximum number of unicast DL scheduling DCI or unicast UL scheduling DCI; and scheduling, based on the indication, multiple unicast DCIs per physical downlink control channel (PDCCH) per monitoring occasion per span.

24. The method of claim 23, wherein the indication further includes support for a first component carrier (CC) scheduling resources on a second CC, wherein: the first CC has a smaller SCS than a SCS of the second CC; the first CC has a larger SCS than a SCS of the second CC; the first CC is in a first frequency range (FR1) and the second CC is in the FR1; the first CC is in the FR1 and the second CC is in a second frequency range (FR2); the first CC is in the FR2 and the second CC is in the FR1; or the first CC is in the FR2 and the second CC is in the FR2.

25. The method of claim 23, wherein the indication further includes support for a first component carrier (CC) scheduling resources on a second CC, wherein: the first CC has a SCS of 15 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 15 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 30 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 60 kHz; the first CC has a SCS of 60 kHz and the second CC has a SCS of 120 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 15 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 30 kHz; the first CC has a SCS of 120 kHz and the second CC has a SCS of 60 kHz; or the first CC has a SCS of 120 kHz and the second CC has a SCS of 120 kHz.

26. The method of claim 23, wherein the indication further comprises a separate capability to support each of one or more feature groups (FGs).

27. The method of claim 26, wherein the one or more FGs comprise at least one of FG3-1, FG3-5b, FG3-5a, and FG11-2.

28. The method of claim 23, wherein a number of unicast DCIs scheduled by the base station comprises a single number that is less than or equal to a maximum sum of unicast DL scheduling DCIs and unicast UL scheduling DCIs included in the indication of the UE capability.

29. The method of claim 23, wherein the indication further comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein the particular number comprises a third number representing a maximum number of the unicast DL scheduling DCIs and a fourth number representing a maximum number of the unicast UL scheduling DCIs.

30. The method of claim 23, wherein the indication further comprises a support of a particular number of unicast DCIs per monitoring occasion per span, wherein: the particular number comprises a fifth number representing a number of unicast DCIs divided by a sixth number representing a number of spans, wherein the sixth number is greater than the fifth number.

31. An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: means for performing operations included in the method of any of claims 8-14.

32. A non-transitory computer-readable medium storing instructions that, when executed by a user equipment (UE), cause the UE to perform operations including: performing operations included in the method of any of claims 8-14.

Images