Method for fast serving cell activation through short channel state information reporting

Abstract

A method for communicating by a user equipment (UE) on a secondary cell (SCell) by fast activation or deactivation, the method comprising obtaining channel state information (CSI) configuration data, the CSI configuration data comprising a short CSI reporting scheme indicating a particular number of CSI reports for transmission by the UE on a physical uplink control channel (PUCCH) resource. The method comprises transmitting the particular number of CSI reports on the PUCCH resource in accordance with the CSI configuration data. The CSI configuration data can be received in a medium access control (MAC) control element (CE) from a serving cell of a new radio (NR) access node (gNB), the MAC CE indicating a status of a short CSI reporting configuration within a configuration list, and wherein the UE transmits one or more of the CSI reports in accordance with the status of the short CSI reporting configuration.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 868,484, filed June 28, 2019, entitled “METHODS FOR FAST SCELL ACTIVATION WITH SHORT CSI REPORTING”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates in general to timing adjustments for uplink transmissions in wireless communications. Background Technology

[0004] The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from voice communication only to include the transmission of data (such as the internet and multimedia content) to various devices. To accommodate the increasing number of devices transmitting both voice and data signals, many wireless communication systems share available communication channel resources between devices. Summary of the Invention

[0005] In 3GPP Rel-15 New Radio (NR) wireless communication networks, carrier aggregation (CA) activation or deactivation commands are sent in the Medium Access Control (MAC) control element (CE), as described in 3GPP TS38.321, NR, Medium Access Control (MAC) protocol specification (Release 15), version 15.4.0, released in April 2019, the entire contents of which are incorporated herein by reference. Typically, for a typical activation or deactivation scenario, the minimum required activation latency is approximately 5 milliseconds (ms). This 5-ms latency is relatively long compared to other NR procedures. Furthermore, the maximum permissible activation delay described in 3GPP TS 38.133, NR, Requirements for support of radio resource management (Release 15) (version 15.4.0, released in April 2019, the entire contents of which are incorporated herein by reference) raises concerns about CA operations for services with stringent latency requirements, and similar issues have existed in Long Term Evolution (LTE) CA operations. Due to such long delays, frequent deactivation of the serving cell (SCell) is risky for NR networks, as reconfiguring the UE back to the SCell active state can take anywhere from a minimum of approximately 5ms to the maximum permissible time of tens or hundreds of milliseconds, depending on the specific scenario and the UE implementation.

[0006] A new element in NR is enabling the use of a larger spectral bandwidth, ultimately achieving peak data rates approximately 10 times higher than LTE. Latency in accessing high-capacity (small) cells can degrade performance, and this can be even more pronounced in NR (e.g., especially if macros are still used in LTE). To fully leverage the potential of large bandwidth (BW), efficient and rapid utilization of the large BW should be ensured in all situations, including initial connection establishment, CA and dual connectivity (DC) reconfiguration, and the addition of secondary cells.

[0007] The implementation scheme described in this specification includes one or more of the following advantages. This specification describes a UE configured to communicate using SCells, where activation or deactivation uses only a few timing slots, and is much shorter than the 5ms time required to activate or deactivate the SCell. Specifically, the method described in this specification is configured to efficiently and dynamically signal rapid SCell activation or deactivation, and significantly reduce SCell activation and deactivation timing delays. Therefore, SCell activation and deactivation can be implemented at the timing slot level, allowing the NR carrier aggregation / dual connectivity (CA / DC) process to operate more efficiently based on traffic demand and bandwidth availability.

[0008] In a general sense, a process for communication by a User Equipment (UE) on a secondary cell (SCell) via fast activation or deactivation includes obtaining Channel State Information (CSI) configuration data, which includes a short CSI reporting scheme indicating a specific number of CSI reports to be transmitted by the UE on Physical Uplink Control Channel (PUCCH) resources. The process also includes transmitting the specified number of CSI reports on the PUCCH resources according to the CSI configuration data.

[0009] In some implementations, CSI configuration data is configured via Radio Resource Control (RRC) signaling. In some implementations, the specific number of CSI reports ranges from 1 to 16.

[0010] In the implementation, the process includes receiving a Media Access Control (MAC) element (CE) comprising multiple bits from the serving cell of a New Radio (NR) Access Node (gNB), wherein at least one individual bit of the multiple bits indicates the status of a short CSI report configuration within a configuration list, and wherein the UE transmits one or more CSI reports from the CSI report according to the status of the short CSI report configuration via the configuration list. In some implementations, the MAC CE also includes additional individual bits of multiple bits, each indicating whether the corresponding secondary cell (SCell) of the fifth-generation (5G) radio cellular network is activated or deactivated. In some implementations, the MAC CE also includes a report quantity field indicating a specific number of reports to be transmitted by the UE on the PUCCH.

[0011] In some specific implementations, the SCell activation delay is less than 10 milliseconds.

[0012] In a general sense, a process for a New Radio (NR) Access Node (gNB) to communicate with a User Equipment (UE) on a secondary cell (SCell) via fast activation or deactivation includes sending Channel State Information (CSI) configuration data including a short CSI reporting scheme indicating a specific number of CSI reports to be transmitted by the UE on Physical Uplink Control Channel (PUCCH) resources. The process also includes receiving a specific number of CSI reports on the PUCCH resources according to the CSI configuration data.

[0013] In some implementations, CSI configuration data is configured via Radio Resource Control (RRC) signaling. In some implementations, the specific number of CSI reports ranges from 1 to 16.

[0014] In some implementations, the process includes sending a Media Access Control (MAC) Control Element (CE) comprising multiple bits to the UE, wherein at least one of the individual bits indicates the status of a short CSI report configuration within a configuration list. In some implementations, the MAC CE also includes additional individual bits, each indicating whether a corresponding SCell is activated or deactivated. In some implementations, the MAC CE also includes a report quantity field indicating a specific number of reports to be transmitted by the UE on the PUCCH.

[0015] In some specific implementations, the SCell activation delay is less than 10 milliseconds.

[0016] In a general sense, a procedure for communication by a User Equipment (UE) on a secondary cell (SCell) via fast activation or deactivation includes sending a Media Access Control (MAC) Protocol Data Unit (PDU) to the UE, comprising at least two MAC Control Elements (CEs), wherein a first MAC CE specifies a CSI reporting configuration for the UE, and a second MAC CE specifies SCell activation. The procedure includes sending CSI resources associated with the CSI reporting configuration to the UE to enable the UE to perform CSI calculation and reporting. The procedure also includes receiving at least one CSI report generated by the UE's CSI calculation and reporting.

[0017] In some implementations, the process includes sending a MAC CE for deactivating the CSI report in response to receiving at least one CSI report. In some implementations, the CSI report is received on the Physical Uplink Control Channel (PUCCH). In some implementations, the CSI report configuration is a semi-persistent CSI (SP-CSI) report configuration. In some implementations, the periodicity specified in the CSI report configuration is one of two, four, or five time slots. In some implementations, the process includes performing channel-aware scheduling based on the CSI report.

[0018] In some implementations, one or more non-transitory computer-readable media are configured to store instructions for rapid CSI reporting. These instructions, when executed by one or more processing devices, cause the devices to perform operations including obtaining Channel State Information (CSI) configuration data. This CSI configuration data includes a short CSI reporting scheme indicating a specific number of CSI reports to be transmitted via the UE on the Physical Uplink Control Channel (PUCCH) resource. The process involves transmitting this specific number of CSI reports on the PUCCH resource according to the CSI configuration data.

[0019] In some implementations, one or more non-transitory computer-readable media are configured to store instructions for rapid CSI reporting. These instructions, when executed by one or more processing devices, cause the processing devices to perform operations including sending a Media Access Control (MAC) Protocol Data Unit (PDU) to the UE, comprising at least two MAC Control Elements (CEs), wherein a first MAC CE specifies a CSI reporting configuration for the UE, and a second MAC CE specifies SCell activation. The process includes sending CSI resources associated with the CSI reporting configuration to the UE to enable the UE to perform CSI calculation and reporting. The process also includes receiving at least one CSI report generated by the UE's CSI calculation and reporting.

[0020] Details of one or more specific embodiments are set forth in the following figures and description. Other features and advantages will become apparent from the detailed description, the figures, and the claims. Attached Figure Description

[0021] Figure 1 An example of a wireless communication system is shown.

[0022] Figure 2 An example of infrastructure equipment is shown.

[0023] Figure 3 Examples of platforms or devices are shown.

[0024] Figure 4 Exemplary components of the baseband circuit and radio front-end circuit are shown.

[0025] Figure 5 An exemplary protocol function that can be implemented in a wireless communication system is shown.

[0026] Figure 6 An exemplary system supporting network function virtualization is shown.

[0027] Figure 7 An exemplary computer system is shown.

[0028] Figure 8 An example of a MAC CE for SCell activation via a short CSI report is shown.

[0029] Figure 9 An example of MACCE for performing fast secondary service cell activation / deactivation and short CSI report activation / deactivation is shown.

[0030] Figure 10 The procedure for short CSI reporting based on parallel MAC CE for performing SCell activation and SP-CSI reporting for PUCCH activation / deactivation is shown.

[0031] Figure 11 , Figure 12 and Figure 13 An exemplary procedure for configuring short CSI reports via the UE is shown.

[0032] Similar reference symbols in the various figures indicate similar elements. Detailed Implementation

[0033] This specification describes the process for implementing fast SCell activation and / or deactivation. Fast SCell activation and / or deactivation reduces SCell activation and deactivation latency by at least tens of milliseconds (ms) to one or more time slots used for SCell transmission.

[0034] The Channel State Information (CSI) report type is configured to include short CSI reports. Short CSI reports can reduce the delay of SCell activation or deactivation by a few milliseconds. The short CSI report type has been added to the existing CSI report types in the CSI report configuration CSI-ReportConfig, a configuration described in 3GPP TS 38.331,NR; Radio Resource Control (RRC) Protocol Specification (Release 15), version 15.5.1 released in May 2019, the entire contents of which are incorporated herein by reference. CSI-ReportConfig is an Information Element (IE) used to configure periodic or semi-persistent reporting, which is transmitted on the Physical Uplink Control Channel (PUCCH) of the cell containing CSI-ReportConfig. In some implementations, the CSI-ReportConfig IE is used to configure semi-persistent or aperiodic reporting, which is transmitted on the PUSCH and triggered by downlink control information (DCI) received on a cell containing CSI-ReportConfig. In this case, the cell on which the report is transmitted is determined by the received DCI. This is further described in Clause 5.2.1 of 3GPP TS 38.214, version 15.5.0, released in May 2019, the entire contents of which are incorporated herein by reference.

[0035] The CSI report type is typically referred to as "short on PUCCH" or "shortOnPUCCH". The CSI report scheme is a short report scheme that enables User Equipment (UE) to apply short CSI report schemes. Therefore, a specific number of CSI reports can be transmitted on PUCCH resources. The number of CSI reports used for transmission on the PUCCH is configured via Radio Resource Control (RRC) signaling. As described now, short CSI reports corresponding to shortOnPUCCH can be triggered by a Media Access Control (MAC) control element (CE).

[0036] The MAC CE is configured to activate a SCell via short CSI reports. The MAC CE is configured to activate a SCell and trigger short CSI reports for the activated SCell. In some implementations, the MAC CE is configured to trigger CSI reports using the shortOnPUCCH report type. Typically, the triggered short CSI report scheme corresponds to a CSI report configuration that requests the UE to send a specific number of CSI reports, as configured by the RRC or MAC CE. The CSI reports are sent by the UE on the PUCCH. After sending a Hybrid Automatic Repeat Request Response (HARQ-ACK) to the new SCell activation MAC CE, the UE initiates the execution of short CSI reports. Upon receiving the first CSI report, the New Radio (NR) Access Node (gNB) initiates the scheduling of data transmission to the UE in the activated SCell.

[0037] In the implementation, short CSI reporting is configured based on parallel MAC CEs for semi-persistent SP-CSI reporting for SCell activation, PUCCH activation, or deactivation. Short CSI reporting during the initial phase of the SCell activation cycle can be implemented in two phases. The first phase includes two parallel MAC CEs for SCell activation and SP-CSI reporting for PUCCH activation. These parallel MAC CEs are described in Sections 5.9 and 6.1.3.18 of 3GPP TS 38.321. The second phase includes a MAC CE for SP-CSI reporting for PUCCH deactivation. Specifically, the MAC CE during the first phase is configured to initiate SCell activation and the start of short CSI reporting. The MAC CE in the second phase is configured to signal the end of short CSI reporting. This two-tiered short CSI reporting allows the gNB and UE to control SCell activation delay through the configuration of SP-CSI resources and a reporting periodicity dedicated to short CSI reporting. The reporting periodicity is independent of the Measurement Timing Configuration Periodicity (SMTC) based on the Synchronization Signal Block (SSB).

[0038] As previously described, these processes are configured to efficiently and dynamically signal rapid SCell activation / deactivation and significantly reduce SCell activation / deactivation latency (e.g., by tens of milliseconds). Therefore, SCell activation / deactivation can occur at the time slot level, allowing NR carrier aggregation / dual connectivity (CA / DC) processes to operate more efficiently based on traffic demand and bandwidth availability, compared to when activation / deactivation does not occur at the time slot level.

[0039] Figure 1An exemplary wireless communication system 100 is illustrated. For convenience and not limitation, the exemplary system 100 is described in the context of LTE and 5G NR communication standards as defined by the 3GPP technical specifications. More specifically, the wireless communication system 100 is described in the context of a non-standalone (NSA) network combining both LTE and NR, such as an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network and a NE-DC network. However, the wireless communication system 100 could also be a standalone (SA) network combining only NR. Furthermore, other types of communication standards are also possible, including future 3GPP systems (e.g., sixth-generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0040] System 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). In other examples, any of the multiple UE 101s may include other mobile computing devices or non-mobile computing devices, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument panel (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, in-vehicle mobility equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine control unit (ECU), electronic / engine control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or “smart” appliances, machine-type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations thereof.

[0041] In some examples, any of the multiple UEs 101 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device, such as a Public Land Mobile Network (PLMN), Proximity Service (ProSe), Device-to-Device (D2D) communication, sensor networks, IoT networks, or combinations thereof. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of active messages or state updates) to facilitate connectivity within the IoT network.

[0042] UE 101 is configured to connect (e.g., communicatively coupled) to an access network (AN) or radio access network (RAN) 110. In some examples, RAN 110 may be a next-generation RAN (NG RAN), an evolved UMTS terrestrial radio access network (E-UTRAN), or a legacy RAN, such as a UMTS terrestrial radio access network (UTRAN) or a GSM EDGE radio access network (GERAN). As used herein, the term “NG RAN” may refer to RAN 110 operating in a 5G NR system 100, while the term “E-UTRAN” may refer to RAN 110 operating in an LTE or 4G system 100.

[0043] To connect to RAN 110, multiple UEs 101 utilize connections (or channels) 103 and 104, each of which may include a physical communication interface or layer, as described below. In this example, connections 103 and 104 are shown as air interfaces for communication coupling and may be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP LTE protocol, 5G NR protocol, or combinations thereof, as well as other communication protocols. In some examples, multiple UEs 101 may directly exchange communication data using interface 105, such as the ProSe interface. Interface 105 may alternatively be referred to as sidelink interface 105 and may include one or more logical channels, such as the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Downlink Channel (PSDCH), or Physical Sidelink Broadcast Channel (PSBCH), or combinations thereof.

[0044] The diagram shows UE 101b configured to access access point (AP) 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN termination 106", "WT106", etc.) using connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 106 will include Wireless Fibre. Router. In this example, AP 106 is shown connected to the Internet but not to the core network of the wireless system, as described in further detail below. In various examples, UE 101b, RAN 110, and AP 106 can be configured to operate using LTE-WLAN aggregation (LWA) or LTW / WLAN radio-level operation integrated with IPsec tunneling (LWIP). LWA operation may involve RAN nodes 111a and 111b configuring UE 101b, which is in the RRC_CONNECTED state, to utilize LTE and WLAN radio resources. LWIP operation may involve UE 101b using IPsec protocol tunneling to use WLAN radio resources (e.g., connection 107) to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0045] RAN 110 includes one or more AN nodes or RAN nodes 111a and 111b (collectively referred to as "RAN node 111") that enable connectivity between 103 and 104. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for a data or voice connection or both between the network and one or more users. These access nodes can be referred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs, RAN nodes, road-side units (RSUs), transmit-receive points (TRxPs or TRPs), etc., and can include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 111 (e.g., a gNB) operating in a 5G NR system 100, while the term "E-UT RAN node" can refer to RAN node 111 (e.g., an eNB) operating in an LTE or 4G system 100. In some examples, multiple RAN nodes 111 may be implemented as dedicated physical devices such as macro cell base stations or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells.

[0046] In some examples, some or all of the multiple RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a Cloud RAN (CRAN) or Virtual Baseband Unit Pool (vBBUP). The CRAN or vBBUP may implement RAN function partitioning, such as Packet Data Convergence Protocol (PDCP) partitioning, where the Radio Resource Control (RRC) and PDCP layers are operated by CRAN / vBBUP, and other Layer 2 (e.g., Data Link Layer) protocol entities are operated by the individual RAN nodes 111; Media Access Control (MAC) / Physical Layer (PHY) partitioning, where the RRC, PDCP, MAC, and Radio Link Control (RLC) layers are operated by CRAN / vBBUP, and the PHY layer is operated by the individual RAN nodes 111; or a “lower PHY” partitioning, where the RRC, PDCP, RLC, and MAC layers, as well as the upper portion of the PHY layer, are operated by CRAN / vBBUP, and the lower portion of the PHY layer is operated by the individual RAN nodes 111. This virtualization framework allows idle processor cores of the RAN nodes 111 to execute, for example, other virtualized applications. In some examples, a single RAN node 111 can represent the use of individual F1 interfaces ( Figure 1 (Not shown) to connect to the individual gNB distributed units (DUs) of the gNB central unit (CU). In some examples, a gNB-DU may include one or more remote radio head ends or RFEMs (see, for example, Figure 2 Furthermore, the gNB-CU can be operated by a server (not shown) located in RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. Alternatively, one or more RAN nodes in RAN 111 can be next-generation eNBs (ng-eNBs), including RAN nodes that provide E-UTRA user plane and control plane protocol terminals to UE 101 and connect to the 5G core network (e.g., core network 120) using next-generation interfaces.

[0047] In a Vehicle-to-Everything (V2X) scenario, one or more RAN nodes in RAN nodes 111 can be RSUs or act as RSUs. The term "roadside unit" or "RSU" refers to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU," an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU," and so on. In some examples, an RSU is a computing device coupled to radio frequency circuitry located on the roadside, which provides connectivity support to a passing vehicle UE 101 (vUE 101). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications or other software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to one or more cellular networks to provide uplink and downlink communication, or both. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks, or both.

[0048] Any of the RAN nodes 111 can serve as the endpoint of the air interface protocol and can be the first point of contact for UE 101. In some examples, any one of the multiple RAN nodes 111 can perform various logical functions of RAN 110, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0049] In some examples, multiple UEs 101 may be configured to communicate with each other or with any of multiple RAN nodes 111 on a multi-carrier communication channel using Orthogonal Frequency Division Multiplexing (OFDM) communication signals, according to various communication technologies such as, but not limited to, OFDMA communication technologies (e.g., for downlink communication) or SC-FDMA communication technologies (e.g., for uplink and ProSe or sidelink communication), although the scope of the technologies described herein is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0050] In some examples, a downlink resource grid can be used for downlink transmissions from any of the multiple RAN nodes 111 to multiple UEs 101, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of a resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0051] In some examples, multiple UEs 101 and multiple RAN nodes 111 transmit (e.g., transmit and receive) data via licensed media (also referred to as “licensed spectrum” or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band. NR in the unlicensed spectrum may be referred to as NR-U, and LTE in the unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0052] To operate in unlicensed spectrum, multiple UEs 101 and multiple RAN nodes 111 may use Licensed Assisted Access (LAA), Enhanced LAA (eLAA), or another Enhanced LAA (feLAA) mechanism. In these specific implementations, the multiple UEs 101 and multiple RAN nodes 111 may perform one or more known medium sensing operations or carrier sensing operations, or both, to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol. LBT is a mechanism by which equipment (e.g., multiple UEs 101, multiple RAN nodes 111) senses a medium (e.g., a channel or carrier frequency) and transmits when that medium is sensed to be idle (or when a specific channel in that medium is sensed to be unoccupied). Medium sensing operations may include Clear Channel Assessment (CCA), which uses energy detection to determine the presence of other signals on the channel in order to determine whether the channel is occupied or cleared. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. Energy detection may include sensing RF energy in a desired transmission band over a period of time and comparing the sensed RF energy with a predefined or configured threshold.

[0053] Existing systems in the 5GHz band can be WLANs based on IEEE 802.11 technology. WLANs employ contention-based channel access mechanisms (e.g., CSMA with collision avoidance (CSMA / CA)). In some examples, when WLAN nodes (e.g., mobile stations (MS) such as UE 101, APs...) When a WLAN node (e.g., 106) intends to transmit, it may first perform a Contention-Based Arrangement (CCA) before transmission. Additionally, if more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism may be a counter randomly drawn within a Contention Window Size (CWS), which increases exponentially upon collision and resets to a minimum value upon successful transmission. In some examples, the LBT mechanism designed for LAA is similar to CSMA / CA for WLAN. In some examples, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) may have a variable-length LAA contention window between CAA (ECCA) slots extended in X and Y, where X and Y are the minimum and maximum CWS of the LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and the maximum channel occupancy time (e.g., transmission burst) may be based on government regulatory requirements.

[0054] In some examples, the LAA mechanism is built on carrier aggregation technology in LTE-Advanced systems. In CA, each aggregated carrier is referred to as a component carrier. In some examples, component carriers can have bandwidths of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five component carriers can be aggregated to provide a maximum aggregated bandwidth of 100 MHz. In Frequency Division Duplex (FDD) systems, the number of aggregated carriers can differ for DL ​​and UL. For example, the number of UL component carriers can be equal to or less than the number of DL component carriers. In some cases, individual component carriers can have different bandwidths than the other component carriers. In Time Division Duplex (TDD) systems, the number of component carriers and the bandwidth of each component carrier are typically the same for DL ​​and UL.

[0055] Carrier aggregation can also include separate serving cells to provide separate component carriers. The coverage of serving cells can differ, for example, because component carriers in different frequency bands may experience different path losses. The primary serving cell (PCell) provides the primary component carrier for both UL and DL and handles RRC and non-access stratum (NAS) related activities. Other serving cells are referred to as secondary component carriers (SCells), and each SCell provides a separate secondary component carrier for both UL and DL. Secondary component carriers can be added and removed as needed, while changing the primary component carrier may require UE 101 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 LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0056] The PDSCH carries user data and higher-layer signaling to multiple UEs 101. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UEs 101 about the transmission format, resource allocation, and Hybrid Automatic Repeat Request (HARQ) information related to the uplink shared channel. Downlink scheduling (e.g., allocating control and shared channel resource blocks to UEs 101b within the cell) can be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each UE in UEs 101.

[0057] PDCCH uses Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. In some examples, one or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to a set of four physical resource elements (REGs) of nine. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the Downlink Control Information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. In LTE, four or more different PDCCH formats can exist, each defined with a different number of CCEs (e.g., aggregation level, L = 1, 2, 4, or 8).

[0058] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the concept described above. For example, some implementations may utilize an enhanced PDCCH (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced CCEs (ECCEs) may be used to transmit the EPDCCH. Similarly, each ECCE may correspond to a set of nine groups comprising four physical resource elements, collectively referred to as enhanced REGs (EREGs). In some examples, an ECCE may have a different number of EREGs.

[0059] RAN nodes 111 are configured to communicate with each other using interface 112. In examples, such as when system 100 is an LTE system (e.g., when core network 120 is an evolved packet core (EPC) network), interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 connected to EPC 120 (e.g., two or more eNBs, etc.), or between two eNBs connected to EPC 120, or both. In some examples, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U may provide flow control mechanisms for user packets transmitted via the X2 interface and may be used to transmit information about the delivery of user data between eNBs. For example, X2-U can provide specific sequence number information about user data transmitted from the primary eNB to the secondary eNB; information about the successful in-order delivery of PDCP Protocol Data Units (PDUs) from the secondary eNB to UE 101 for user data; information about PDCP PDUs not delivered to UE 101; information about the current minimum expected buffer size at the secondary eNB for transmitting user data to the UE; and so on. X2-C can provide in-LTE access mobility functions, including context transfer or user plane transmission control from the source eNB to the target eNB; load management functions; inter-cell interference coordination functions; and so on.

[0060] In some examples, such as when system 100 is a 5G NR system (e.g., when core network 120 is a 5G core network), interface 112 may be an Xn interface 112. The Xn interface may be defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5G core network 120, between a RAN node 111 (e.g., a gNB) connected to the 5G core network 120 and an eNB, or between two eNBs connected to the 5G core network 120, or a combination of the above. In some examples, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 101 in connected modes (e.g., CM-CONNECTED), including functions for managing UE mobility in connected modes between one or more RAN nodes 111; and so on. Mobility support may include context transfer from the old (source) serving RAN node 111 to the new (destination) serving RAN node 111, and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (destination) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GPRS Tunneling Protocol (GTP-U) layer on top of the User Datagram Protocol (UDP) or IP layer, or both, for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of the Flow Control Transport Protocol (SCTP). SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack or the Xn-C protocol stack, or both, may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0061] RAN 110 is shown communicatively coupled to core network 120 (referred to as “CN 120”). CN 120 includes one or more network elements 122 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 101) who utilize RAN 110 to connect to CN 120. Components of CN 120 may be implemented in a single physical node or separate physical nodes and may include components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some examples, network function virtualization (NFV) may be used to virtualize some or all of the network node functions described herein using executable instructions stored in one or more computer-readable storage media, as will be described in further detail below. A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network subslice. NFV architectures and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, performed by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more network components or functions, or both.

[0062] Generally, application server 130 may be an element that provides IP bearer resources for use with the core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). Application server 130 may also be configured to support one or more communication services for UE 101 using CN 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0063] In some examples, CN 120 can be a 5G core network (referred to as "5GC 120"), and RAN 110 can connect to CN 120 using Next Generation Interface 113. In some examples, Next Generation Interface 113 can be divided into two parts: Next Generation User Plane (NG-U) Interface 114, which carries traffic data between multiple RAN nodes 111 and User Plane Functions (UPFs); and S1 Control Plane (NG-C) Interface 115, which is the signaling interface between RAN nodes 111 and Access and Mobility Management Functions (AMFs).

[0064] In some examples, CN 120 may be an EPC (referred to as "EPC 120", etc.), and RAN 110 may connect to CN 120 using S1 interface 113. In some examples, S1 interface 113 may be divided into two parts: S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and the Serving Gateway (S-GW); and S1-MME interface 115, which is the signaling interface between RAN node 111 and the Mobility Management Entity (MME).

[0065] Figure 2 An example of infrastructure equipment 400 is shown. Infrastructure equipment 400 (or "system 400") may be implemented as a base station, a radio head unit, a RAN node (such as RAN node 111 or AP 106 previously shown and described), an application server 130, or any other component or device described herein. In other examples, system 400 may be implemented in or by a UE.

[0066] System 400 includes: application circuitry 405, baseband circuitry 410, one or more radio front-end modules (RFEMs) 415, memory circuitry 420, power management integrated circuit (PMIC) 425, power tee circuitry 430, network controller circuitry 435, network interface connector 440, satellite positioning circuitry 445, and user interface circuitry 450. In some examples, system 400 may include additional components such as, for example, memory, storage devices, displays, cameras, one or more sensors, or input / output (I / O) interfaces or combinations thereof. In other examples, the components described with reference to system 400 may be included in more than one device. For example, various circuits may be separately included in more than one device for CRAN, vBBU, or other specific implementations.

[0067] Application circuitry 405 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, one or more of the following: a low-dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a universal 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 application circuitry 405 may be coupled to or may include memory or storage elements, and may be configured to execute instructions stored in the memory or storage elements to enable various applications or operating systems to run on system 400. In some examples, the memory or storage element may include on-chip memory circuitry, which may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or combinations thereof.

[0068] The processor of application circuit 405 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 combinations thereof. In some examples, application circuit 405 may include or may be a dedicated processor or controller configured to perform the various technologies described herein. As an example, the processor of application circuit 405 may include one or more Intel processors. 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 examples, system 400 may not utilize application circuitry 405 and may instead include a dedicated processor or controller to process IP data, for example, received from an EPC or 5GC.

[0069] In some examples, application circuitry 405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. These hardware accelerators may include, for example, computer vision (CV) or deep learning (DL) accelerators, or both. In some examples, the programmable processing device may be one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs) or high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); or combinations thereof, etc. In such specific implementations, the circuitry of application circuitry 405 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as the processes, methods, and functions described herein. In some examples, the circuitry of application circuit 405 may 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) or fuse)) for storing logic blocks, logic architectures, data, or other data in lookup tables (LUTs).

[0070] The baseband circuit 410 can be implemented, for example, as a soldered substrate, including one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. (See reference...) Figure 4 The various hardware electronic components of the baseband circuit 410 are discussed.

[0071] User interface circuitry 450 may include one or more user interfaces designed to enable a user to interact with system 400 or peripheral component interfaces, which are designed to enable peripheral components to interact with system 400. User interfaces may 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 transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, or combinations thereof. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power interfaces, etc.

[0072] The radio front-end module (RFEM) 415 may include a millimeter-wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some examples, the one or more sub-mmWave RFICs may be physically decoupled from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays (see, for example...). Figure 6 The antenna array 611 is used, and the RFEM can be connected to multiple antennas. In some examples, the radio functions of both millimeter wave and sub-millimeter wave are implemented in the same physical RFEM 415 that combines both millimeter wave antennas and sub-millimeter wave antennas.

[0073] Memory circuitry 420 may include one or more of the following: volatile memory, such as dynamic random access memory (DRAM) or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), such as electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or combinations thereof. In some examples, memory circuitry 420 may include memory derived from… and A three-dimensional (3D) xpoint memory. For example, the memory circuit 420 may be implemented as one or more of the following: a solder-in packaged integrated circuit, a socket memory module, and an insert memory card.

[0074] The PMIC 425 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. The power tee circuit 430 can provide power drawn from the network cable to provide both power and data connectivity to the infrastructure equipment 400 using a single cable.

[0075] Network controller circuitry 435 may use standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS)-based Ethernet, or some other suitable protocol to provide connectivity to the network. Network connectivity to and from infrastructure equipment 400 may be provided using a physical connection via network interface connector 440, which may be an electrical connection (typically referred to as a "copper interconnect"), an optical connection, or a wireless connection. Network controller circuitry 435 may include one or more dedicated processors or FPGAs, or both, for communicating using one or more of the aforementioned protocols. In some examples, network controller circuitry 435 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0076] Positioning circuit 445 includes circuitry for receiving and decoding signals transmitted or broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of GNSS include the U.S. Global Positioning System (GPS), Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., using the Indian constellation NAVIC, Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler orbit charts, and Satellite Integrated Radio Positioning (DORIS)). Positioning circuit 445 may include various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc., for facilitating OTA communication) to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some examples, positioning circuit 445 may include a micro-technology (micro PNT) IC for positioning, navigation, and timing, which performs position tracking and estimation using a master timing clock in the absence of GNSS assistance. Positioning circuit 445 may also be a part of or interact with baseband circuitry 410 or RFEM 415, or both, to communicate with nodes and components of the positioning network. The positioning circuit 445 can also provide data (e.g., location data, time data) to the application circuit 405, which can use the data to synchronize operations with various infrastructures (e.g., RAN node 111, etc.).

[0077] Figure 2 The components shown can communicate with each other using interface circuitry, which may include any number of bus or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extension (PCIx), PCI Express (PCIe), or any other technologies. The bus or IX may be a proprietary bus, for example, used in a SoC-based system. Other bus or IX systems may be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0078] Figure 3 An example of platform 500 (or “device 500”) is shown. In some examples, computer platform 500 may be adapted to function as UE 101, 201, 301, application server 130, or any other component or device discussed herein. Platform 500 may include any combination of the components shown in the examples. Components (or portions thereof) of platform 500 may be implemented as integrated circuits (ICs), discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 500, or may be implemented as components otherwise integrated into the rack of a larger system. Figure 5The block diagram is intended to show a high-level view of the components of platform 500. However, in some examples, platform 500 may include fewer, additional, or alternative components, or include... Figure 5 The different arrangements of the components are shown.

[0079] Application circuitry 505 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more LDOs, interrupt controllers, serial interfaces (such as SPI), I2C or general-purpose programmable serial interface modules, RTCs, timer-counters (including interval timers and watchdog timers), general-purpose I / O, memory card controllers (such as SD MMC or similar controllers), USB interfaces, MIPI interfaces, and JTAG test access ports. The processor (or core) of application circuitry 505 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in memory or storage devices to enable various applications or operating systems to run on system 500. In some examples, the memory or storage element may be on-chip memory circuitry, which may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or combinations thereof.

[0080] The processor of application circuit 405 may 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 DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some examples, application circuit 405 may include or may be a dedicated processor / controller for performing the techniques described herein.

[0081] As an example, the processor of application circuit 505 may include an Apple A-series processor. The processor of application circuit 505 may also be one or more of the following: based on... Architecture Core TM processors, such as Quark TM Atom TM i3, i5, i7 or MCU-level processors, or available from Santa Clara, California. company( Another processor of this type from [Company Name], Santa Clara, CA; and Advanced Micro Devices (AMD). Processor or Accelerated Processing Unit (APU); from Snapdragon by Technologies, Inc. TM Processor, Texas Instruments Open Multimedia ApplicationsPlatform(OMAP) TM Processors; MIPS-based designs from MIPS Technologies, Inc., such as the 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 series processors; etc. In some specific implementations, the application circuit 505 may be part of a system-on-a-chip (SoC), where the application circuit 505 and other components are formed as a single integrated circuit.

[0082] Additionally or alternatively, application circuitry 505 may include circuitry such as, but not limited to, one or more field-programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs) and high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs); or combinations thereof, etc. In some examples, application circuitry 505 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as the processes, methods, and functions described herein. In some examples, application circuitry 505 may 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) or fuses) for storing logic blocks, logic architectures, data, or other data in lookup tables (LUTs).

[0083] The baseband circuit 510 can be implemented, for example, as a soldered substrate, comprising one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. (See reference...) Figure 4 This paper discusses the various hardware electronic components of the 510 baseband circuit.

[0084] RFEM 515 may include a millimeter-wave (mmWave) RFEM and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some examples, the one or more sub-millimeter-wave RFICs may be physically decoupled from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays (see, for example...). Figure 4 The antenna array 611 is used, and the RFEM can be connected to multiple antennas. In some examples, the radio functions of both millimeter wave and sub-millimeter wave are implemented in the same physical RFEM 515 that combines both millimeter wave antennas and sub-millimeter wave antennas.

[0085] Memory circuitry 520 may include any number and type of memory devices for providing a fixed amount of system memory. As an example, memory circuitry 520 may include one or more of the following: volatile memory, such as random access memory (RAM), dynamic RAM (DRAM), or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), such as high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or combinations thereof. Memory circuitry 520 may be developed according to the Joint Electron Device Engineering Council (JEDEC) design based on low-power double data rate (LPDDR), such as LPDDR2, LPDDR3, LPDDR4, etc. Memory circuitry 520 may be implemented as one or more of the following: solder-in packaged integrated circuits, single-die package (SDP), dual-die package (DDP), or quad-die package (Q17P), socket memory modules, dual in-line memory modules (DIMMs) including micro-DIMMs or mini-DIMMs, or soldered to a motherboard using a ball grid array (BGA). In a low-power implementation, memory circuitry 520 may be an on-chip memory or register associated with application circuitry 505. To provide persistent storage for information such as data, applications, operating systems, etc., memory circuitry 520 may include one or more mass storage devices, such as solid-state drives (SSDDs), hard disk drives (HDDs), micro HDDs, resistance-changing memory, phase-change memory, holographic memory, or chemical memory. In some examples, computer platform 500 may be integrated with... and 3D XPOINT memory.

[0086] The removable memory circuitry 523 may include devices, circuitry, housings, enclosures, ports, or sockets for coupling portable data storage devices to platform 500. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, MicroSD cards, xD picture cards), as well as USB flash drives, optical discs, or external HDDs or combinations thereof.

[0087] Platform 500 may also include interface circuitry (not shown) for connecting external devices to platform 500. External devices connected to platform 500 via this interface circuitry include sensor circuitry 521 and electromechanical components (EMC) 522, as well as a removable memory device coupled to removable memory circuitry 523.

[0088] Sensor circuit 521 includes a device, module, or subsystem designed to detect events or changes in its environment and transmit information about the detected events (e.g., sensor data) to one or more other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units (IMUs), such as accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other audio capture devices, or combinations thereof, etc.

[0089] EMC 522 includes devices, modules, or subsystems intended to enable platform 500 to change its state, position, or orientation, or to move or control mechanisms, systems, or subsystems. Additionally, EMC 522 can be configured to generate messages or signaling and send messages or signaling to other components of platform 500 to indicate the current state of EMC 522. Examples of EMC 522, among other electromechanical components, include one or more power switches, relays (such as electromechanical relays (EMRs) or solid-state relays (SSRs)), actuators (e.g., valve actuators), audible generators, visual warning devices, motors (e.g., DC motors or stepper motors), wheels, propellers, propellers, claws, clamps, hooks, or combinations thereof. In some examples, platform 500 is configured to operate one or more EMC 522s based on one or more captured events, commands, or control signals received from a service provider or client, or both.

[0090] In some examples, the interface circuitry can connect platform 500 to positioning circuitry 545. Positioning circuitry 545 includes circuitry for receiving and decoding signals transmitted or broadcast by a GNSS positioning network. Examples of GNSS systems include GPS (USA), GLONASS (Russia), Galileo (EU), BeiDou (China), regional navigation systems or GNSS augmentation systems (e.g., NAVIC), QZSS (Japan), DORIS (France), etc. Positioning circuitry 545 includes various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc.) to facilitate OTA communication for communication with components of the positioning network, such as navigation satellite constellation nodes. In some examples, positioning circuitry 545 may include a miniature PNT IC that performs position tracking or estimation using a master timing clock without GNSS assistance. Positioning circuitry 545 may also be or interact with baseband circuitry 410 or RFEM 515, or a combination thereof, to communicate with nodes and components of the positioning network. The positioning circuit 545 can also provide data (e.g., location data, time data) to the application circuit 505, which can use the data to synchronize operations with various infrastructures (e.g., radio base stations) for applications such as turn-by-turn navigation.

[0091] In some examples, the interface circuitry can connect platform 500 to near-field communication (NFC) circuitry 540. NFC circuitry 540 is configured to provide contactless short-range communication based on radio frequency identification (RFID) standards, where magnetic field sensing is applied to enable communication between NFC circuitry 540 and NFC-enabled devices (e.g., “NFC contacts”) external to platform 500. NFC circuitry 540 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller can be a chip or IC that provides NFC functionality to NFC circuitry 540 by executing NFC controller firmware and an NFC stack. The NFC stack can be executed by the processor to control the NFC controller, and the NFC controller firmware can be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals can power passive NFC tags (e.g., microchips embedded in stickers or wristbands) to transfer stored data to NFC circuitry 540, or initiate data transfer between NFC circuitry 540 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) located near platform 500.

[0092] The driving circuit 546 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 500. The driving circuit 546 may include various drivers that allow other components of the platform 500 to interact with or control various input / output (I / O) devices that may exist within or be connected to the platform. For example, the driving circuit 546 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 500; a sensor driver for acquiring sensor readings of sensor circuit 521 and controlling and allowing access to sensor circuit 521; an EMC driver for acquiring actuator position of EMC 522 or controlling and allowing access to EMC 522; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0093] A power management integrated circuit (PMIC) 525 (also referred to as "power management circuit 525") manages the power supplied to various components of platform 500. Specifically, relative to baseband circuit 510, PMIC 525 controls power selection, voltage scaling, battery charging, or DC-DC conversion. PMIC 525 may be included when platform 500 can be powered by battery 530, for example, when the device is included in UE 101, 201, 301.

[0094] In some examples, the PMIC 525 can be controlled or otherwise integrated into various power-saving mechanisms of the platform 500. For instance, if the platform 500 is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the platform 500 can power down for short intervals to conserve power. If there is no data traffic activity for a longer period, the platform 500 can transition to the RRC_Idle state, where it is disconnected from the network and does not perform operations such as channel quality feedback or handover. This allows the platform 500 to enter a very low-power state in which it periodically wakes up to listen to the network and then powers down again. In some examples, the platform 500 may not receive data in the RRC_Idle state and must instead transition back to the RRC_Connected state to receive data. Additional power-saving modes can render the device unable to use the network for longer than the paging interval (ranging from seconds to hours). During this time, the device may be unable to connect to the network and may lose power completely. Any data sent during this period may experience significant delays, and it is assumed that the delays are acceptable.

[0095] Battery 530 can power platform 500, but in some examples, platform 500 may be deployed in a fixed location and may have a power source coupled to the grid. Battery 530 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery. In some examples, such as in V2X applications, battery 530 may be a typical lead-acid automotive battery.

[0096] In some examples, battery 530 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in platform 500 to track the state of charge (SoCh) of battery 530. The BMS can be used to monitor other parameters of battery 530, such as the state of health (SoH) and state of function (SoF) of battery 530, to provide fault prediction. The BMS can transmit information about battery 530 to application circuitry 505 or other components of platform 500. The BMS may also include an analog-to-digital converter (ADC) that allows application circuitry 505 to directly monitor the voltage of battery 530 or the current from battery 530. Battery parameters can be used to determine actions that platform 500 can perform, such as transmission frequency, network operation, sensing frequency, etc.

[0097] A power block coupled to the grid or other power source can be coupled to the BMS to charge the battery 530. In some examples, a wireless power receiver can replace the power block 530 to wirelessly obtain power, for example, via a loop antenna in the computer platform 500. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuitry chosen may depend on the size of the battery 530 and therefore on the required current. Charging can be performed using the aviation fuel standards published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Radio Power Alliance, or the Rezence charging standard published by the Radio Power Alliance.

[0098] User interface circuitry 550 includes various input / output (I / O) devices present within or connected to platform 500, and includes one or more user interfaces designed to enable user interaction with platform 500 or peripheral component interfaces designed to enable interaction with peripheral components of platform 500. User interface circuitry 550 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual device for accepting input, including 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, or a headset, or combinations thereof. Output device circuitry includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other information). Output device circuitry may include any number or combination of audio or visual displays, including one or more simple visual outputs or indicators (e.g., binary status indicators (e.g., light-emitting diodes (LEDs)), multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, or projectors), wherein the output of characters, graphics, or multimedia objects is generated or produced by the operation of platform 500. Output device circuitry may also include speakers or other audio transmitting devices, or printers. In some examples, sensor circuitry 521 may be used as input device circuitry (e.g., image capture devices or motion capture devices), and one or more EMCs may be used as output device circuitry (e.g., actuators for providing haptic feedback). In another example, NFC circuitry may be included for reading electronic tags or connecting to another NFC-enabled device, the NFC circuitry including an NFC controller and processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, or power interfaces.

[0099] Although not shown, components of platform 500 may communicate with each other using suitable bus or interconnect (IX) technologies, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, Time Triggered Protocol (TTP) systems, FlexRay systems, or any other technologies. The bus or IX may be a proprietary bus or IX, for example, used in a SoC-based system. Other bus or IX systems may be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0100] Figure 4 Exemplary components of the baseband circuitry 610 and the radio front-end module (RFEM) 615 are shown. The baseband circuitry 610 may correspond to... Figure 4 The baseband circuit 410 and Figure 5The baseband circuit 510. RFEM 615 can respectively correspond to Figure 4 RFEM415 and Figure 5 The RFEM 515. As shown in the figure, the RFEM 615 may include a radio frequency (RF) circuit 606, a front-end module (FEM) circuit 608, and an antenna array 611 coupled together.

[0101] Baseband circuit 610 includes circuitry or control logic components, or both, configured to perform various radio or network protocols and control functions that enable communication with one or more radio networks using RF circuitry 606. Radio control functions may include, but are not limited to, signal modulation and demodulation, encoding and decoding, and radio frequency shifting. In some examples, the modulation and demodulation circuitry of baseband circuitry 610 may include Fast Fourier Transform (FFT), precoding, or constellation mapping and demapping functions. In some examples, the encoding and decoding circuitry of baseband circuitry 610 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder and decoder functions. Modulation and demodulation, as well as encoder and decoder functions, are not limited to these examples, and other suitable functions may be included in other examples. Baseband circuitry 610 is configured to process baseband signals received from the receive signal path of RF circuitry 606 and to generate baseband signals for the transmit signal path of RF circuitry 606. Baseband circuitry 610 is configured to interact with application circuitry (e.g., Figure 2 and Figure 3 The application circuits 405 and 505 shown interact to generate and process baseband signals and control the operation of RF circuit 606. Baseband circuit 610 can handle various radio control functions.

[0102] The aforementioned circuitry and control logic components of the baseband circuitry 610 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 604A, a 4G or LTE baseband processor 604B, a 5G or NR baseband processor 604C, or other baseband processors 604D for other existing, under development, or future generations (e.g., sixth generation (6G)). In some examples, some or all of the functionality of the baseband processors 604A-D may be included in modules stored in memory 604G and executed using a central processing unit (CPU) 604E. In some examples, some or all of the functionality of the baseband processors 604A-D may be provided as hardware accelerators (e.g., FPGAs or ASICs) loaded with appropriate bitstreams or logic blocks stored in the respective memory cells. In some examples, memory 604G may store program code for a real-time operating system (RTOS), which, when executed by CPU 604E (or other baseband processor), enables CPU 604E (or other baseband processor) to manage resources of baseband circuitry 610, schedule tasks, or perform other operations. Examples of RTOS may include those derived from... The provided Operating System Embedded (OSE) TM By Mentor Nucleus RTOS provided TM By Mentor Versatile Real-Time Executive (VRTX) is provided by Express. ThreadX provided TM ,Depend on The provided FreeRTOS and REX OS are from OpenKernel (OK). The provided OKL4, or any other suitable RTOS, such as those discussed herein. Furthermore, the baseband circuitry 610 includes one or more audio digital signal processors (DSPs) 604F. The audio DSP 604F includes elements for compression and decompression and echo cancellation, and in some examples may include other suitable processing elements.

[0103] In some examples, each processor in processors 604A-604E includes a corresponding memory interface for sending data to and receiving data from memory 604G. Baseband circuitry 610 may also include one or more interfaces for communicatively coupling to other circuitry or devices, such as interfaces for sending data to and receiving data from memory external to baseband circuitry 610; and interfaces for sending data to... Figure 2 and Figure 3Application circuit interfaces for sending and receiving data from application circuits 405 and 505; used for sending data to and receiving data from application circuits. Figure 4 The RF circuit 606 transmits data and receives data from the RF circuit; it is used for transmitting data from one or more wireless hardware components (e.g., near field communication (NFC) components, Low power components The PMIC 525 has a wireless hardware connection interface for transmitting data to and receiving data from the PMIC and other components; and a power management interface for transmitting power or control signals to and receiving power or control signals from the PMIC.

[0104] In some examples (which may be combined with the examples described above), baseband circuitry 610 includes one or more digital baseband systems that are coupled to each other and to a CPU subsystem, an audio subsystem, and an interface subsystem using interconnect subsystems. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem using another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, a network-on-chip (NOC) architecture, or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital converter circuitry and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, etc. In some examples, baseband circuitry 610 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry or radio frequency circuitry (e.g., radio front-end module 615).

[0105] although Figure 4Not shown, but in some examples, baseband circuitry 610 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In some examples, PHY layer functions include the aforementioned radio control functions. In some examples, the protocol processing circuit operates or implements various protocol layers or entities of one or more wireless communication protocols. For example, when baseband circuitry 610 or RF circuitry 606, or both, are part of millimeter-wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuit may operate an LTE protocol entity or a 5G NR protocol entity, or both. In this example, the protocol processing circuit may operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In some examples, when baseband circuitry 610 or RF circuitry 606, or both, are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In this example, the protocol processing circuit may operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 604G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using the data. The baseband circuitry 610 may also support radio communication using more than one wireless protocol.

[0106] The various hardware components of the baseband circuit 610 discussed herein can be implemented, for example, as a soldered substrate comprising one or more integrated circuits (ICs), a single-packaged IC soldered to a main board, or a multi-chip module containing two or more ICs. In some examples, components of the baseband circuit 610 may be suitably combined in a single chip or a single chipset, or disposed on the same board. In some examples, some or all of the components of the baseband circuit 610 and the RF circuit 606 may be implemented together, such as, for example, a system-on-a-chip (SoC) or a system-in-package (SiP). In some examples, some or all of the components of the baseband circuit 610 may be implemented as a separate SoC communicatively coupled to the RF circuit 606 (or multiple instances of the RF circuit 606). In some examples, some or all of the components of the baseband circuit 610 and the application circuits 405, 505 may be implemented together as a separate SoC mounted to the same board (e.g., a “multi-chip package”).

[0107] In some examples, baseband circuit 610 can provide communication compatible with one or more radio technologies. For example, baseband circuit 610 can support communication with E-UTRAN or other WMAN, WLAN, or WPAN. Examples in which baseband circuit 610 is configured to support radio communication with more than one wireless protocol may be referred to as a multi-mode baseband circuit.

[0108] RF circuit 606 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In some examples, RF circuit 606 may include components such as switches, filters, or amplifiers to facilitate communication with the wireless network. RF circuit 606 may include a receive signal path that includes circuitry for down-converting the RF signal received from FEM circuit 608 and providing a baseband signal to baseband circuit 610. RF circuit 606 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 610 and providing an RF output signal for transmission to FEM circuit 608.

[0109] The receive signal path of RF circuit 606 includes mixer circuit 606a, amplifier circuit 606b, and filter circuit 606c. In some examples, the transmit signal path of RF circuit 606 may include filter circuit 606c and mixer circuit 606a. RF circuit 606 also includes synthesizer circuit 606d for synthesizing frequencies used by mixer circuit 606a in both the receive and transmit signal paths. In some examples, mixer circuit 606a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 608 based on the synthesized frequency provided by synthesizer circuit 606d. Amplifier circuit 606b may be configured to amplify the down-converted signal, and filter circuit 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 610 for further processing. In some examples, although this is not required, the output baseband signal may be a zero-frequency baseband signal. In some examples, the mixer circuit 606a of the receive signal path may include a passive mixer.

[0110] In some examples, the mixer circuit 606a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 606d to generate an RF output signal for the FEM circuit 608. The baseband signal can be provided by the baseband circuit 610 and can be filtered by the filter circuit 606c.

[0111] In some examples, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some examples, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some examples, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some examples, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may be configured for superheterodyne operation.

[0112] In some examples, the output baseband signal and the input baseband signal can be analog baseband signals. In some examples, the output baseband signal and the input baseband signal can be electronic baseband signals, and the RF circuit 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 610 may include a digital baseband interface for communicating with the RF circuit 606.

[0113] In some dual-mode examples, separate radio IC circuits can be provided to process the signal for each spectrum, but the techniques described herein are not limited in this respect.

[0114] In some examples, synthesizer circuit 606d may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but other types of frequency synthesizers may be used. For example, synthesizer circuit 606d may be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer that includes a phase-locked loop with a frequency divider.

[0115] Synthesizer circuit 606d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 606a of RF circuit 606. In some examples, synthesizer circuit 606d can be a fractional N / N+1 synthesizer.

[0116] In some examples, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 610 or the application circuits 405 / 505 according to the desired output frequency. In some examples, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuits 405, 505.

[0117] The synthesizer circuit 606d of the RF circuit 606 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some examples, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some examples, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some examples, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. The delay elements may be configured to divide the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0118] In some examples, synthesizer circuit 606d may be configured to generate a carrier frequency as the output frequency, while in other examples, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used with quadrature generator and frequency divider circuitry to generate multiple signals with multiple different phases relative to each other at that carrier frequency. In some examples, the output frequency may be the LO frequency (fLO). In some examples, RF circuit 606 may include an IQ or polarity converter.

[0119] FEM circuit 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 611, amplify the received signals, and provide an amplified version of the received signals to RF circuit 606 for further processing. FEM circuit 608 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 606 for transmission by one or more antenna elements in antenna array 611. Amplification via the transmit or receive signal path may be performed solely in RF circuit 606, solely in FEM circuit 608, or in both RF circuit 606 and FEM circuit 608.

[0120] In some examples, FEM circuit 608 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 608 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 608 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 606). The transmit signal path of FEM circuit 608 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 606), and one or more filters for generating the RF signal for subsequent transmission by one or more antenna elements of antenna array 611.

[0121] Antenna array 611 includes one or more antenna elements, each configured to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. For example, a digital baseband signal provided by baseband circuit 610 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted using the antenna elements of antenna array 611, which includes one or more antenna elements (not shown). Antenna elements can be omnidirectional, directional, or a combination thereof. Antenna elements can be arranged in various configurations as known and / or discussed herein. Antenna array 611 may include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. Antenna array 611 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to RF circuit 606 and / or FEM circuit 608 using metal transmission lines, etc.

[0122] The processors of application circuits 405 / 505 and baseband circuits 610 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuit 610 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processors of application circuits 405 and 505 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include the MAC layer, RLC layer, and PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which will be described in further detail below.

[0123] Figure 5 This illustrates various protocol functions that can be implemented in wireless communication devices. Specifically, Figure 5 This includes an arrangement 800 illustrating the interconnections between various protocol layers / entities. It provides various protocol layers and entities operating in conjunction with 5G NR system standards and LTE system standards. Figure 5 The following description, but Figure 5 Some or all of these aspects may also be applicable to other wireless communication network systems.

[0124] In addition to other higher-layer functions not shown, the protocol layers of arrangement 800 may also include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857. These protocol layers may include one or more service access points (e.g., providing communication between two or more protocol layers). Figure 5Items 859, 856, 850, 849, 845, 835, 825, and 815.

[0125] The PHY 810 can transmit and receive physical layer signals 805, which can be received from or transmitted to one or more other communication devices. Physical layer signals 805 may include one or more physical channels, such as those discussed herein. The PHY 810 can also perform link adaptive or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., RRC 855). The PHY 810 can further perform error detection on transport channels, forward error correction (FEC) coding and decoding of transport channels, modulation and demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In some examples, instances of the PHY 810 may use one or more PHY-SAP 815s to process requests from instances of the MAC 820 and provide them with indications. In some examples, requests and indications transmitted using the PHY-SAP 815 may include one or more transport channels.

[0126] An instance of MAC 820 can utilize one or more MAC-SAP 825s to process requests from instances of RLC 830 and provide them with instructions. These requests and instructions transmitted using MAC-SAP 825s may include one or more logical channels. MAC 820 can perform mapping between logical channels and transport channels, multiplexing MAC Service Data Units (SDUs) from one or more logical channels onto a transport block (TB) delivered to PHY 810 via a transport channel to be utilized, demultiplexing MAC SDUs from TBs delivered from PHY 810 via transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0127] An instance of the RLC 830 can utilize one or more Radio Link Control Service Access Points (RLC-SAP) 835s to process requests from instances of the PDCP 840 and provide them with instructions. These requests and instructions transmitted using the RLC-SAP 835 can include one or more logical channels. The RLC 830 can operate in several modes, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 830 can perform the transmission of Upper Layer Protocol Data Units (PDUs), error correction via Automatic Repeat Requests (ARQs) for AM data transmission, and concatenation, segmentation, and reassembly of RLCSDUs for UM and AM data transmission. The RLC 830 can also perform resegmentation of RLC data PDUs for AM data transmission, reordering of RLC data PDUs for UM and AM data transmission, detection of duplicate data for UM and AM data transmission, discarding of RLC SDUs for UM and AM data transmission, detection of protocol errors for AM data transmission, and RLC re-establishment.

[0128] An instance of PDCP 840 can utilize one or more Packet Data Convergence Protocol Service Access Points (PDCP-SAP) 845s to process requests from instances of RRC 855 or SDAP 847, or both, and provide them with instructions. These requests and instructions transmitted using PDCP-SAP 845 may include one or more radio bearers. PDCP 840 can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform sequential delivery of higher-layer PDUs during lower-layer re-establishment, eliminate duplication of lower-layer SDUs during lower-layer re-establishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discarding, and perform security operations (e.g., encryption, decryption, integrity protection, or integrity verification).

[0129] Instances of SDAP 847 can utilize one or more SDAP-SAP 849s to process requests from one or more higher-layer protocol entities and provide them with indications. These requests and indications transmitted using SDAP-SAP 849 can include one or more QoS flows. SDAP 847 can map QoS flows to Data Radio Bearers (DRBs) and vice versa, and can also tag QoS Flow Identifiers (QFIs) in DL and UL packets. A single SDAP entity 847 can be configured for a single PDU session. In the UL direction, NG-RAN 110 can control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, UE 101's SDAP 847 can monitor the QFI of DL packets for each DRB and can apply the same mapping for packets flowing in the UL direction. For DRBs, UE 101's SDAP 847 can map UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflection mapping, the NG-RAN310 can tag DL packets with QoS flow IDs via the Uu interface. Explicit mapping may involve configuring SDAP 847 with explicit mapping rules from QoS flows to DRBs using RRC 855; these rules can be stored and followed by SDAP 847. In some examples, SDAP 847 may be used only in NR implementations and not in LTE implementations.

[0130] RRC 855 can configure aspects of one or more protocol layers using one or more Management Service Access Points (M-SAPs), which may include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840, and SDAP 847. In some examples, instances of RRC 855 may use one or more RRC-SAP 856s to process requests from one or more NAS entities 857 and provide them with instructions. Key services and functions of RRC 855 may include broadcasting system information (e.g., included in NAS-related Master Information Block (MIB) or System Information Block (SIB)), broadcasting system information related to the Access Layer (AS), paging, establishment, maintenance, and release of RRC connections between UE 101 and RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. MIBs and SIBs may include one or more information elements, each of which may include a separate data field or data structure.

[0131] The NAS 857 forms the highest layer of the control plane between UE 101 and AMF 321. The NAS 857 supports the mobility and session management procedures of UE 101 to establish and maintain IP connections between UE 101 and the P-GW in an LTE system.

[0132] In some examples, one or more protocol entities of deployment 800 may be implemented in UE 101, RAN node 111, AMF 321 in the NR implementation or MME 221 in the LTE implementation, UPF 302 in the NR implementation or S-GW 222 and P-GW 223 in the LTE implementation, etc., for use in the control plane or user plane communication protocol stack between the aforementioned devices. In some examples, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 321, etc., may communicate with corresponding peer protocol entities that may be implemented in another device or on another device (using the services of the corresponding lower-level protocol entity to perform such communication). In some examples, the gNB-CU of gNB 111 can host the RRC 855, SDAP 847, and PDCP 840 of gNB 111 that control one or more gNB-DU operations, and the gNB-DU of gNB 111 can each host the RLC 830, MAC 820, and PHY 810 of gNB 111.

[0133] In some examples, the control plane protocol stack may include NAS 857, RRC855, PDCP 840, RLC 830, MAC 820, and PHY 810 in order from the highest to the lowest layer. In this example, the upper layer 860 may be built on top of NAS 857, which includes IP layer 861, SCTP 862, and application layer signaling protocol (AP) 863.

[0134] In some examples, such as NR implementations, AP 863 may be an NG application protocol layer (NGAP or NG-AP) 863 for an NG interface 113 defined between NG-RAN node 111 and AMF321, or AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863 for an Xn interface 112 defined between two or more RAN nodes 111.

[0135] NG-AP 863 can support the functionality of NG interface 113 and may include an initial procedure (EP). The NG-AP EP can be the interaction unit between NG-RAN node 111 and AMF 321. NG-AP 863 services may include two groups: UE-related services (e.g., services related to UE 101) and non-UE-related services (e.g., services related to the entire NG interface instance between NG-RAN node 111 and AMF 321). These services may include, but are not limited to: paging functions for sending paging requests to NG-RAN node 111 involved in a specific paging area; UE context management functions for allowing AMF 321 to establish, modify, or release UE contexts in AMF 321 and NG-RAN node 111; mobility functions for UE 101 in ECM-CONNECTED mode, for intra-system HO support of mobility within NG-RAN, and for inter-system HO support of mobility from / to EPS systems; NAS signaling transmission functions for transmitting or rerouting NAS messages between UE 101 and AMF 321; NAS node selection functions for determining the association between AMF 321 and UE 101; NG interface management functions for setting up the NG interface and monitoring errors through the NG interface; warning message transmission functions for providing means of transmitting warning messages or canceling ongoing warning message broadcasts using the NG interface; and functions for utilizing CN... 120 is a configuration transfer function that requests and transfers RAN configuration information (e.g., SON information, or performance measurement (PM) data) between two RAN nodes 111; or a combination thereof, etc.

[0136] XnAP 863 supports the functions of Xn interface 112 and may include XnAP basic mobility procedures and XnAP global procedures. XnAP basic mobility procedures may include procedures for handling UE mobility within NG RAN 111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN state transmission procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity. XnAP global procedures may include procedures not associated with a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, or cell activation procedures.

[0137] In a specific LTE implementation, AP 863 can be an S1 application protocol layer (S1-AP) 863 for an S1 interface 113 limited between E-UTRAN node 111 and MME, or AP 863 can be an X2 application protocol layer (X2AP or X2-AP) 863 for an X2 interface 112 limited between two or more E-UTRAN nodes 111.

[0138] The S1 Application Protocol Layer (S1-AP) 863 supports the functions of the S1 interface and, similar to the previously discussed NG-AP, may include an S1-AP EP. The S1-AP EP can be the interaction unit between the E-UTRAN node 111 and the MME 221 within the LTE CN 120. S1-AP 863 services may include two sets: UE-associated services and non-UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0139] X2AP 863 supports the functions of X2 interface 112 and may include X2AP basic mobility procedures and X2AP global procedures. X2AP basic mobility procedures may include procedures for handling UE mobility within E-UTRAN 120, such as handover preparation and cancellation procedures, SN state transmission procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity. X2AP global procedures may include procedures not associated with a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, or cell activation procedures.

[0140] The SCTP layer (optionally referred to as the SCTP / IP layer) 862 provides guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). SCTP 862 can ensure reliable delivery of signaling messages between RAN node 111 and AMF 321 / MME 221, based in part on the IP protocol supported by IP 861. The Internet Protocol layer (IP) 861 can be used to perform packet addressing and routing functions. In some implementations, IP layer 861 can use point-to-point transmission to deliver and transmit PDUs. In this regard, RAN node 111 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0141] In some examples, the user plane protocol stack may include SDAP 847, PDCP 840, RLC 830, MAC 820, and PHY 810 in order from the highest to the lowest layer. The user plane protocol stack can be used for communication between UE 101, RAN node 111, and UPF 302 in an NR implementation, or between S-GW 222 and P-GW 223 in an LTE implementation. In this example, the upper layer 851 may be built on top of SDAP 847 and may include User Datagram Protocol (UDP) and IP Security Layer (UDP / IP) 852, General Packet Radio Service (GPRS) Tunneling Protocol Layer for User Plane (GTP-U) 853, and User Plane PDU Layer (UP PDU) 863.

[0142] The transport network layer 854 (also known as the "transport layer") can be built on top of IP transport, and the GTP-U 853 can be used on top of the UDP / IP layer 852 (which includes the UDP and IP layers) to carry user plane PDUs (UP-PDUs). The IP layer (also known as the "Internet layer") can be used to perform packet addressing and routing functions. The IP layer can assign IP addresses to user data packets in any of the formats, such as IPv4, IPv6, or PPP.

[0143] The GTP-U 853 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be packets in any of the IPv4, IPv6, or PPP formats. The UDP / IP 852 provides checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data streams. RAN node 111 and S-GW 222 can utilize the S1-U interface to exchange user plane data using a protocol stack including L1 layer (e.g., PHY 810), L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and / or SDAP 847), UDP / IP layer 852, and GTP-U 853. S-GW 222 and P-GW 223 can utilize the S5 / S8a interface to exchange user plane data using a protocol stack including L1 layer, L2 layer, UDP / IP layer 852, and GTP-U 853. As previously discussed, the NAS protocol supports the mobility and session management process of UE 101 to establish and maintain the IP connection between UE 101 and P-GW 223.

[0144] Furthermore, despite Figure 5Not shown, but the application layer may exist above AP 863 and / or transport network layer 854. The application layer may be a layer where users of UE 101, RAN node 111, or other network elements interact with software applications, such as those executed by application circuitry 405 or 505, respectively. The application layer may also provide one or more interfaces for software applications to interact with the communication systems of UE 101 or RAN node 111, such as baseband circuitry 610. In some examples, the IP layer or the application layer, or both, may provide the same or similar functionality as layers 5 through 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0145] Figure 6 This is a block diagram showing the components of a system 1000 that supports NFV. The system 1000 is shown as including a Virtualization Infrastructure Manager (VIM) 1002, a Network Functions Virtualization Infrastructure (NFVI) 1004, a Virtualization Network Functions Manager (VNFM) 1006, a Virtualization Network Function (VNF) 1008, an Element Manager (EM) 1010, a Network Functions Virtualization Orchestrator (NFVO) 1012, and a Network Manager (NM) 1014.

[0146] VIM 1002 manages the resources of NFVI 1004. NFVI 1004 may include physical or virtual resources and applications (including hypervisors) used to execute System 1000. VIM 1002 can utilize NFVI 1004 to manage the lifecycle of virtual resources (e.g., the creation, maintenance, and teardown of VMs associated with one or more physical resources), track VM instances, track the performance, failure, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0147] VNFM 1006 manages VNF 1008. VNF 1008 can be used to perform, for example, EPC components and functions. VNFM 1006 manages the lifecycle of VNF 1008 and tracks the performance, faults, and security of the virtual aspects of VNF 1008. EM 1010 tracks the performance, faults, and security of the functional aspects of VNF 1008. Tracking data from VNFM 1006 and EM 1010 may include, for example, PM data used by VIM 1002 or NFVI 1004. Both VNFM 1006 and EM 1010 can scale up or down the number of VNFs in System 1000.

[0148] NFVO 1012 can coordinate, authorize, release, and engage the resources of NFVI 1004 to provide requested services (e.g., to perform EPC functions, components, or slices). NM 1014 can provide end-user function packages responsible for network management, which may include network elements with VNFs, non-virtualized network functions, or both (management of VNFs can occur using EM 1010).

[0149] Figure 7 This is a block diagram illustrating components for reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the techniques described herein. Specifically, Figure 7 A schematic diagram of hardware resource 1100 is shown, including one or more processors (or processor cores) 1110, one or more memory or storage devices 1120, and one or more communication resources 1130, each of which can be communicatively coupled via bus 1140. For a specific implementation utilizing node virtualization (e.g., NFV), an executable hypervisor 1102 provides an execution environment for one or more network slices or subslices to utilize hardware resource 1100.

[0150] Processor 1110 may include processor 1112 and processor 1114. Processor 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0151] The memory / storage device 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1120 may include, but is not limited to, any type of volatile or non-volatile 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, or solid-state storage devices, or combinations thereof.

[0152] Communication resource 1130 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 using network 1108. For example, communication resource 1130 may include wired communication components (e.g., for coupling using USB), cellular communication components, NFC components, etc. (or Low-power components Components and other communication components.

[0153] Instructions 1150 may include software, programs, applications, applets, or other executable code for causing at least any one of processors 1110 to perform any or more of the methods discussed herein. Instructions 1150 may reside wholly or partially within processor 1110 (e.g., within the processor's cache memory), memory / storage device 1120, or any suitable combination thereof. Furthermore, any portion of instructions 1150 may be transferred to hardware resource 1100 from any combination of peripheral device 1104 or database 1106. Thus, the memory of processor 1110, memory / storage device 1120, peripheral device 1104, and database 1106 are examples of computer-readable and machine-readable media.

[0154] Figure 8 An example of a MAC CE 1200 for SCell activation via short CSI reports is shown. The MAC CE 1200 is configured to activate a SCell and trigger a short CSI report for the activated SCell. The triggered short CSI report scheme corresponds to a new CSI report configuration that requests the UE to send a specific number of CSI reports on the PUCCH. In some specific implementations, the RRC configures the short CSI report scheme.

[0155] A CSI report type called "shortOnPUCCH" is added to the CSI report configuration, CSI-ReportConfig. This CSI report scheme is configured to enable the UE to apply the short CSI report scheme. The UE is configured to transmit a specific number of CSI reports on PUCCH resources. The number of CSI reports to be transmitted on the PUCCH is configured via RRC signaling. Short CSI reports corresponding to shortOnPUCCH can be generated by... Figure 8 MAC CE 1200 or Figure 9 The MAC CE 1300 triggers, as described below. Specifically, the enhanced CSI-ReportConfig with the shortOnPUCCH report type can be specified as shown in the following IE.

[0156] Structure 1: CSI-ReportConfig IE

[0157]

[0158] In CSI-ReportConfig, the shortOnPUCCH element includes three parameters. The parameter numberofReports defines the number of CSI reports transmitted by the UE on the PUCCH for triggering short CSI reports. In some implementations, the number of reports can be from 1 to 16. The parameter reportSlotConfig defines the periodicity and offset value of the CSI-Report. The parameter PUCCH-CSI-ResourceList defines the sequence size of the PUCCH CSI resources. Further description is provided for MAC CE 1200 and MAC CE 1300.

[0159] Figure 8 The MAC CE 1200 is sent to the UE. After sending a HARQ-ACK response to the newly activated SCell to the MAC CE 1200, the UE initiates a short CSI report. In some specific implementations, after receiving the first CQI report, the gNB initiates the scheduling of data transmission to the UE in the activated SCell.

[0160] The MAC CE 1200, which activates SCell and short CSI reports, is configured to activate SCell and initiate short CSI reports with the configured number of CSI reports for RRC. The field definitions for the MAC CE 1200 are as follows.

[0161] The Ci fields (e.g., C1-C7) in line 1202 are associated with SCells. SCells are configured for MAC entities using SCellIndexi, as specified in Section 6.2 of 3GPP TS 38.331. i Each field indicates the active or deactivated state of the SCell with SCellIndex i; otherwise, the MAC entity ignores the Ci field. The Ci field is set to "1" to indicate that the SCell with SCellIndex i should be active. The Ci field is set to "0" to indicate that the SCell with SCellIndex i should be deactivated.

[0162] The Bandwidth Part (BWP) identifier 1206 indicates the Upload (UL) BWP applicable to MAC CE 1200. In some implementations, the BWP ID field is 2 bits long.

[0163] The S field in line 1204 (represented as S) iEach indicates the active or deactivated state of a short CSI report configuration. Typically, this state indicates the short CSI report configuration within the csi-ReportConfigToAddModList. The csi-ReportConfigToAddModList includes a list of report configurations to be added or modified, as specified in Section 6.3.2 of TS 38.331. Specifically, S0 indicates the report configuration that includes the PUCCH resource for short CSI reporting in the indicated BWP and has the lowest CSI-ReportConfigId in the list with type set to "shortOnPUCCH.". S1 indicates the PUCCH resource for short CSI reporting in the indicated BWP and for each S... i+1 Reporting configurations with a second minimum CSI-ReportConfigId, etc. If the number of reporting configurations in the list with type "shortOnPUCCH" set in the indicated BWP is less than i+1, the MAC entity ignores unused S... i Field. Typically, S i The field is set to "1" to indicate that the corresponding short CSI report configuration should be activated. i The field is set to "0" to indicate that the corresponding short CSI report configuration i should be deactivated. The R bit is a reserved bit and is set to "0".

[0164] Figure 9 An example of the MACCE 1300 for fast secondary servicing cell activation / deactivation and short CSI report activation / deactivation is shown. The MAC CE 1300 includes the number of reports notified by signaling. The MAC CE activates SCell and short CSI reports based on the number of reports notified by signaling. (Except for...) Figure 8 In addition to the fields defined in MAC CE 1200, the additional field nrOfReports 1310 is included in MAC CE 1300. The nrOfReports 1310 field is signaled to indicate the number of CSI reports transmitted by the UE on the PUCCH. Because the report count is notified by MAC CE 1300 via signaling, the parameter defining the report count can be removed from the shortOnPUCCH report type definition in the CSI-ReportConfig IE.

[0165] Similar to MAC CE 1200, MAC CE 1300 includes a Bandwidth Part (BWP) identifier 1306, which indicates the Upload (UL) BWP applicable to MAC CE 1300. In some implementations, the BWP ID field is 2 bits long.

[0166] The Ci field (e.g., C1-C7) in row 1302 is associated with the SCell. Use SCellIndex. i The SCell is configured for the MAC entity as specified in Section 6.2 of 3GPP TS 38.331. i Each field indicates the active or deactivated state of the SCell with SCellIndex i; otherwise, the MAC entity ignores the SCell. i Field. C i The field is set to "1" to indicate that the SCell with SCellIndexi should be activated. i The field is set to "0" to indicate that SCellIndex is present. i The SCell should be deactivated.

[0167] The S field in line 1304 (represented as S) i Each indicates the active or deactivated state of a short CSI report configuration. Typically, this state indicates the short CSI report configuration within the csi-ReportConfigToAddModList. The csi-ReportConfigToAddModList includes a list of report configurations to be added or modified, as specified in Section 6.3.2 of TS 38.331. Specifically, S0 indicates the report configuration that includes the PUCCH resource for short CSI reporting in the indicated BWP and has the lowest CSI-ReportConfigId in the list with type set to "shortOnPUCCH.". S1 indicates the PUCCH resource for short CSI reporting in the indicated BWP and for each S... i+1 Reporting configurations with a second minimum CSI-ReportConfigId, etc. If the number of reporting configurations in the list with type "shortOnPUCCH" set in the indicated BWP is less than i+1, the MAC entity ignores unused S... i Field. Typically, S i The field is set to "1" to indicate that the corresponding short CSI report configuration should be activated. i The field is set to "0" to indicate that the corresponding short CSI report configuration i should be deactivated. The R bits in rows 1304 and 1306 are reserved bits and set to "0".

[0168] Figure 10A procedure 1400 for short CSI reporting based on parallel MAC CEs performing SCell activation and SP-CSI reporting for PUCCH activation / deactivation is illustrated. Short CSI reporting during the initial phase of the SCell activation cycle can be implemented in two phases. The first phase includes two parallel MAC CEs for performing SCell activation and SP-CSI reporting for PUCCH activation. The parallel MAC CEs include MAC CE 1406, which includes sending the SCell activation CE. The parallel MAC CEs include MAC CE 1408, which includes sending an SCI report on the PUCCH activation CE. gNB 1402 is configured to send parallel MAC CE 1406 and MAC CE 1408 to UE 1404. Parallel MAC CEs are described in Section 6.1.3.18 of 3GPP TS 38.321. Specifically, the MAC CEs during the first phase are configured to initiate the start of SCell activation and short CSI reporting.

[0169] The second phase includes a MAC CE for SP-CSI reporting of PUCCH deactivation. MAC CE 1424 includes an SP-CSI report for PUCCH deactivation sent from gNB 1402 to UE 1404. MAC CE 1424 in the second phase is configured to signal the end of the short CSI report to gNB 1402 via signaling from UE 1404. This two-stage short CSI reporting allows gNB 1402 and UE 1404 to control SCell activation delay through the configuration of SP-CSI resources and a reporting periodicity dedicated to short CSI reporting. The reporting periodicity is independent of the SMTC.

[0170] UE 1404 is configured to perform a short CSI report after sending HARQ-ACK 1410 back to gNB 1402. HARQ-ACK 1410 acknowledges receipt of the parallel MAC CE 1406 configured to activate the SCell and MAC CE 1408 for SP-CSI reporting on the PUCCH. When performing a short CSI report during the short CSI report duration 1420, UE 1404 is configured to receive (1412) the SP-CSI / IM resources associated with the SP-CSI report and prepare (1414) the CSI report for transmission to gNB 1402. UE 1404 performs (1418) periodic CSI reporting on the PUCCH as configured by MAC CE 1408 and MAC CE 1406.

[0171] gNB 1402 receives the (1422) CSI report. Upon receiving a valid CSI report instructing UE 1404 to be ready for data reception, gNB sends MAC CE 1424 to deactivate the SP-CSI report on the PUCCH. UE 1404 sends an acknowledgment message HARQ-ACK 1426, and the short CSI report duration ends in 1420.

[0172] In some specific implementations, procedure 1400 is executed as a series of actions between gNB 1402 and UE 1404 based on specific timings, as now described. At a given timeslot n, the gNB transmits a MAC Protocol Data Unit (PDU) comprising at least two MAC CEs, including MAC CE 1406 for performing SCell activation and MAC CE 1408 for reporting SP CSI on the PUCCH. At timeslot n+k1, it is used in the downlink control information (DCI) for signaling notification and indicating the delay from HARQ-ACK response 1410 to scheduling the DCI, and UE 1404 sends HARQ-ACK response 1410 to gNB 1402.

[0173] After receiving HARQ-ACK response 1410 from UE 1404, gNB 1402 initiates the transmission of CSI resources associated with the activated SP CSI reporting configuration. This enables UE 1404 to perform CSI calculations and reporting. The periodicity of SP-CSI resources is typically small, such as 2, 4, or 5 time slots. However, larger periodicities can be used.

[0174] Based on the activated SP CSI report configuration and the received SP CSI resources, the UE performs (1412) CSI calculation and prepares (1414) CSI report. UE 1404 transmits (1418) SP-CSI report on the PUCCH. The periodicity of PUCCH CSI reports is typically small, such as 2, 4, or 5 slots. In some specific implementations, larger periodicities are used. After transmitting the first CSI report on the PUCCH, UE 1404 can begin monitoring data scheduling in the SCell.

[0175] When one or more UE 1404 CSI reports are received on the PUCCH, the gNB is notified that UE 1404 SCell activation is complete. The gNB 1402 obtains (1422) sufficient CSI knowledge for channel-aware scheduling of data transmissions for UE 1404 by the gNB. Upon this, the gNB 1402 sends MAC CE 1424 to deactivate the SP-CSI report for UE 1404 on the PUCCH. This deactivates the short CSI report duration 1420. UE 1404 transmits a HARQ-ACK response 1426 to the gNB 1402 and stops the associated short CSI report on the PUCCH.

[0176] In some implementations, gNB 1402 cannot schedule data transmission to UE 1404 until gNB receives a valid CSI report (1422). When the SCell activation MAC CE is sent by gNB 1402, this timing may require approximately 10 time slots after a given time slot n. Depending on the subcarrier spacing of the SCell being activated, the resulting SCell activation delay can be reduced to less than 10 milliseconds (e.g., reduced to 5 milliseconds or less).

[0177] In some specific implementations, the delay time depends on the function f = 15kHz * 2 in NR. n The subcarrier spacing is given by , where n is the subcarrier spacing step size of the parameter set. Therefore, the parameter set includes the subcarrier spacing and / or symbol length used by the serving cell. The delay depends on the HARQ-ACK response delay, which can be less than 5ms, down to several timing slots. The delay time is based on the serving cell's parameter set. The exact delay time can be indicated by the MAC CE.

[0178] Figure 11 , Figure 12 and Figure 13 An exemplary procedure for configuring short CSI reports via the UE is shown. Figure 11 A procedure 1500 for configuring a UE to perform fast short CSI reporting via MAC CE is illustrated. This can reduce the delay of SCell activation or deactivation to less than 5 ms or at most a few time slots, depending on the parameter set of the serving cell. Procedure 1500 includes obtaining (1502) Channel State Information (CSI) configuration data including a short CSI reporting scheme indicating a specific number of CSI reports to be transmitted by the UE on Physical Uplink Control Channel (PUCCH) resources. In some implementations, the CSI configuration data is configured via Radio Resource Control (RRC) signaling. In some implementations, the specific number of CSI reports is 1 to 16.

[0179] Procedure 1500 may include receiving a Media Access Control (MAC) control element (CE) comprising multiple bits from the serving cell of a New Radio (NR) Access Node (gNB). In some implementations, at least one individual bit of the multiple bits indicates the status of a short CSI report configuration within a configuration list. The UE transmits one or more CSI reports from the CSI reports via the configuration list according to the status of the short CSI report configuration. In some implementations, the MAC CE also includes additional individual bits of multiple bits, each indicating whether the corresponding secondary cell (SCell) of the fifth-generation (5G) radio cellular network is activated or deactivated. In some implementations, the MAC CE also includes a report quantity field indicating a specific number of reports to be transmitted by the UE on the PUCCH.

[0180] Procedure 1500 includes sending (1504) a specific number of CSI reports on the PUCCH resource based on CSI configuration data. In some implementations, the SCell activation delay is less than 10 milliseconds.

[0181] Figure 12 A procedure 1600 for configuring a UE to perform fast short CSI reporting via MAC CE is illustrated. This can reduce the delay for SCell activation or deactivation to less than 5 ms or at most a few time slots, depending on the parameter set of the serving cell. Procedure 1600 includes transmitting (1602) Channel State Information (CSI) configuration data including a short CSI reporting scheme indicating a specific number of CSI reports to be transmitted by the UE on Physical Uplink Control Channel (PUCCH) resources. In some implementations, the CSI configuration data is configured via Radio Resource Control (RRC) signaling. In some implementations, the specific number of CSI reports is 1 to 16.

[0182] Procedure 1600 may include receiving a Media Access Control (MAC) control element (CE) comprising multiple bits from the serving cell of a New Radio (NR) Access Node (gNB). In some implementations, at least one individual bit of the multiple bits indicates the status of a short CSI report configuration within a configuration list. The UE transmits one or more CSI reports from the CSI reports via the configuration list according to the status of the short CSI report configuration. In some implementations, the MAC CE also includes additional individual bits of multiple bits, each indicating whether the corresponding secondary cell (SCell) of the fifth-generation (5G) radio cellular network is activated or deactivated. In some implementations, the MAC CE also includes a report quantity field indicating a specific number of reports to be transmitted by the UE on the PUCCH.

[0183] Procedure 1600 includes receiving (1604) a specific number of CSI reports on the PUCCH resource based on CSI configuration data. In some implementations, the SCell activation delay is less than 10 milliseconds.

[0184] Figure 13 A procedure 1700 is illustrated for communication by a User Equipment (UE) on a secondary cell (SCell) via fast activation or deactivation. Procedure 1700 includes sending (1702) a Media Access Control (MAC) Protocol Data Unit (PDU) to the UE, comprising at least two MAC Control Elements (CEs). A first MAC CE specifies a CSI reporting configuration for the UE. A second MAC CE specifies SCell activation. Procedure 1700 includes sending (1704) CSI resources associated with the CSI reporting configuration to the UE to enable the UE to perform CSI calculation and reporting. Procedure 1700 includes receiving (1706) at least one CSI report generated by the UE's CSI calculation and reporting.

[0185] In some implementations, process 1700 includes sending a MAC CE for deactivating the CSI report in response to receiving at least one CSI report. In some implementations, the CSI report is received on the Physical Uplink Control Channel (PUCCH). In some implementations, the CSI report configuration is a semi-persistent CSI (SP-CSI) report configuration. In some implementations, the periodicity specified in the CSI report configuration is one of two, four, or five time slots. In some implementations, the process includes performing channel-aware scheduling based on the CSI report.

[0186] The techniques described herein can be performed by means of devices that are implemented in or employed in one or more types of network components, user equipment, or both. In some embodiments, one or more non-transitory computer-readable media include instructions for causing an electronic device to perform one or more of the techniques described herein when executed by one or more processors of the electronic device. An apparatus may include one or more processors and one or more computer-readable media, the computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more of the techniques.

[0187] In various specific embodiments, the methods described herein can be implemented in software, hardware, or a combination thereof. Furthermore, the order of the blocks of the method can be changed, and various elements can be added, reordered, combined, omitted, modified, etc. Various modifications and changes can be made, which will be apparent to those skilled in the art who benefit from this disclosure. The various specific embodiments described herein are intended to be illustrative and not restrictive. Many variations, modifications, additions, and improvements are possible. Thus, multiple examples may be provided for a component described herein as a single example. The boundaries between various components, operations, and data repositories are somewhat arbitrary, and specific operations are shown in the context of a particular exemplary configuration. Other assignments of functionality are contemplated, which may fall within the scope of the appended claims. Finally, the structure and functionality of the discrete components presented in the exemplary configuration can be implemented as combined structures or components.

[0188] The methods described herein can be implemented in circuits such as one or more of the following: integrated circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), ASICs, field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), or some combination thereof. Examples of processors may include Apple A-series processors, Architecture Core TM Processors, including ARM, AMD, and Qualcomm processors, are possible. Other types of processors are also possible. In some implementations, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions described (or a combination of circuits used in an electrical or electronic system). In these implementations, the combination of hardware elements and program code may be referred to as a particular type of circuit. The circuit may also include radio circuits, such as transmitters, receivers, or transceivers.

[0189] As stated above, some aspects of the subject matter of this specification include the collection and use of data from various sources to improve services that mobile devices can provide to users. This disclosure contemplates that, in some cases, the collected data may be used to identify specific locations or addresses based on device usage. Such personal information data may include location-based data, addresses, subscriber account identifiers, or other identifying information.

[0190] This disclosure also envisions that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. For example, personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate purposes. Furthermore, such collection should only be conducted with the user's informed consent. Additionally, such entities should take any necessary steps to safeguard and protect access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and procedures. Furthermore, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices.

[0191] With regard to advertising delivery services, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with regard to advertising delivery services, the technology of the present invention can be configured to allow users to choose "option-in" or "option-out" to participate in the collection of personal information data during service registration.

[0192] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, preferences can be inferred based on non-personal information data or an absolute minimum of personal information, such as content requested by a device associated with a user, other non-personal information available to the content delivery service, or publicly available information, thereby selecting content and delivering it to the user.

[0193] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0194] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as networked computers, network hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized virtual networks (VNFs), NFVIs, etc.

[0195] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0196] As used herein, the terms “appliance,” “computer appliance,” etc., refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide particular computing resources. A “virtual device” is a virtual machine image implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance, or otherwise dedicates itself to providing particular computing resources.

[0197] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resources" can refer to computing, storage, and / or networking resources provided by physical hardware components. "Virtualized resources" can refer to computing, storage, and / or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" can refer to resources accessible to computer devices / systems via a communication network. The term "system resources" can refer to any kind of shared entity providing services and can include computing resources and / or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0198] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term denoteing a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices via a RAT for transmitting and receiving information.

[0199] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0200] This document uses the terms “coupled,” “communicably coupled,” and their derivatives. The term “coupled” can mean two or more elements in direct physical or electrical contact with each other, or two or more elements in indirect contact but still interacting or cooperating with each other, and / or one or more other elements coupled or connected between elements that are said to be coupled to each other. The term “directly coupled” can mean two or more elements in direct contact with each other. The term “communicably coupled” can mean two or more elements that can be in contact with each other by means of communication, including via wires or other interconnections, via wireless communication channels or links, etc.

[0201] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0202] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or a data element that contains content.

[0203] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0204] The term "SSB" refers to the SS / PBCH block.

[0205] The term "primary cell" refers to an MCG cell operating on the primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection reconstruction procedure.

[0206] The term "primary SCG cell" refers to the SCG cell in which the UE performs random access when reconfiguration is performed using the synchronization process used for DC operation.

[0207] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell of a UE configured with a CA.

[0208] The term "secondary cell group" refers to a subset of serving cells that includes the PSCell of the UE configured with DC and zero or more secondary cells.

[0209] The term "serving cell" refers to the primary cell for a UE that is not configured with CA / DC in RRC_CONNECTED, where there is only one serving cell including the primary cell.

[0210] The term "serving cell" refers to a group of cells that includes the special cell used for UEs configured with CA / DC and in RRC_CONNECTED, and all secondary cells.

[0211] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG used for DC operation; otherwise, the term "special cell" refers to the PCell.

[0212] Several specific embodiments have been described. However, it should be understood that various modifications can be made. Elements in one or more embodiments may be combined, deleted, modified, or supplemented to form other embodiments. As another example, the logical flow shown in the figures does not require a specific order or sequence to achieve the desired result. Furthermore, additional steps may be provided or steps may be eliminated from the process, and other components may be added to or removed from the system. Therefore, other embodiments are within the scope of the following claims.

[0213] Example

[0214] Example 1 may include a method comprising: generating a message to indicate fast SCell activation / deactivation relative to a UE; and transmitting the message to the UE.

[0215] Example 2 may include a method comprising: decoding a message to indicate a fast SCell activation / deactivation configuration transmitted by a gNB; and performing one or more actions based on the decoded configuration. The following examples describe various exemplary implementations of the fast SCell activation / deactivation configuration.

[0216] Examples of short CSI report configurations include at least the following.

[0217] Example 3 may include a method that includes adding a new CSI report type, namely "shortOnPUCCH", to the CSI report configuration, CSI-ReportConfig, enabling the UE to apply a short CSI report scheme, thereby allowing a specific number of CSI reports to be transmitted on PUCCH resources.

[0218] Example 4 may include a method comprising: generating a message to include a CSI report configuration, wherein the CSI report configuration, in addition to other configurations, is configured with "shortOnPUCCH" to implement a short CSI report scheme, enabling the number of CSI reports that can be transmitted on PUCCH resources; and transmitting the generated message to the UE.

[0219] Example 5 may include the method described according to Examples 3 to 4 or some other embodiments herein, wherein the number of CSI reports to be transmitted on the PUCCH is configured via RRC signaling.

[0220] Example 6 may include the method described according to Examples 3 to 4 or some other embodiments herein, wherein the short CSI report corresponding to the shortOnPUCCH may be triggered by one or more MAC CEs.

[0221] Example 7 may include the method of enhanced CSI-ReportConfig according to Example 1.X or some other embodiments herein, wherein the shortOnPUCCH report type may be specified as shown in Structure 1: CSI-ReportConfigIE.

[0222] Example 8 may include the method described according to Example 7 or some other embodiments herein, wherein numberofReports defines the number of CSI reports that should be transmitted on the PUCCH for the triggered short CSI report.

[0223] Example 9 may include the method according to Examples 3 to 8, wherein the method is performed by gNB.

[0224] Example 10 may include a method comprising: decoding a message to include a CSI report configuration, the CSI report configuration being configured, in addition to other configurations, to implement a "shortOnPUCCH" scheme to enable a short CSI report scheme, such that a number of CSI reports can be transmitted on PUCCH resources; and generating one or more CSI reports based on the CSI report configuration.

[0225] Example 11 may include the method according to Example 10 or some other embodiments herein, wherein the number of CSI reports to be transmitted on the PUCCH is configured via RRC signaling.

[0226] Example 12 may include the method described according to Example 10 or some other embodiments herein, wherein the short CSI report corresponding to the shortOnPUCCH may be triggered by one or more MAC CEs.

[0227] Example 13 may include the method of enhanced CSI-ReportConfig according to Example 10 or some other embodiments herein, wherein the shortOnPUCCH report type may be specified as shown in Structure 1: CSI-ReportConfigIE.

[0228] Example 14 may include the method described according to Example 13 or some other embodiments herein, wherein numberofReports defines the number of CSI reports that should be transmitted on the PUCCH for the triggered short CSI report.

[0229] Example 15 may include the method according to Examples 10 to 13, wherein the method is performed by the UE.

[0230] Examples of MAC CEs for SCell activation with short CSI reports include at least the following.

[0231] Example 16 may include a method for configuring a new MAC CE, which may be designed to activate the SCell and trigger a short CSI report on the activated SCell.

[0232] Example 17 may include the method according to Examples 1 and 10, wherein a new MAC CE is configured for the fast SCell activation / deactivation.

[0233] Example 18 may include the method according to Examples 16 to 17, wherein the new MAC CE is used to indicate the activation of the SCell and the short CSI report on the activated SCell.

[0234] Example 19 may include Example 16, wherein the triggered short CSI report scheme corresponds to a new CSI report configuration that requests the UE to send a specific number of CSI reports on the PUCCH as described in Example 4.0 or configured by the MAC CE.

[0235] Example 20 may include Examples 16 to 19, wherein the short CSI report scheme corresponds to a new CSI report configuration that requests the UE to send a specific number of CSI reports.

[0236] Example 21 may include Example 20, wherein the specific number of CSI reports on PUCCH is configured by RRC or MAC CE.

[0237] Example 22 may include the method according to Examples 16 to 19, wherein after sending a HARQ-ACK response to the new SCell Activation MAC CE, the UE begins to perform a short CSI report.

[0238] Example 23 may include the method according to Examples 10 and 16 through 19, wherein the execution includes executing a short CSI report.

[0239] Example 24 may include the method according to Examples 2 and 23, wherein the execution includes generating a HARQ-ACK response and transmitting the HARQ-ACK response to the new SCell activation MAC CE.

[0240] Example 25 may include the method described in Examples 16 to 19, wherein upon receiving a first CQI report, the gNB may begin scheduling data transmission to the UE in the SCell that is being activated.

[0241] Example 26 may include the method according to Examples 16 to 19, and further includes: receiving or decoding a first CQI report.

[0242] Example 27 may include the method according to Example 26, and further includes: scheduling data transmission to the UE in the activated SCell.

[0243] An embodiment of the MAC CE for activating SCell and short CSI reports with RRC configuration may include at least the following.

[0244] Example 28 may include the method according to Examples 16 to 19 or some other embodiments herein, wherein the MAC CE activates the SCell and the short CSI report with the number of reports configured for RRC. Figure 1As shown, the fields of the MAC CE are defined as follows: Ci: If a SCell is configured for the MAC entity with SCellIndex i as specified in TS 38.331, this field indicates the activation / deactivation status of the SCell with SCellIndex i; otherwise, the MAC entity should ignore the Ci field. The Ci field is set to "1" to indicate that the SCell with SCellIndex i should be activated. The Ci field is set to "0" to indicate that the SCell with SCellIndex i should be deactivated; BWP ID: This field indicates the UL BWP to which the MAC CE is applied. The BWP ID field has a length of 2 characters; Si: This field indicates the activation / deactivation status configured in the short CSI report within csi-ReportConfigToAddModList, as specified in TS 38.331. S0 refers to a report configuration that includes a PUCCH resource for short CSI reporting in the indicated BWP and has the lowest CSI-ReportConfigId in the list with type "shortOnPUCCH". S1 refers to a report configuration that includes a PUCCH resource for short CSI reporting in the indicated BWP and has a second lowest CSI-ReportConfigId, etc. If the number of report configurations in the list with type "shortOnPUCCH" in the indicated BWP is less than i+1, the MAC entity should ignore the Si field. The Si field is set to "1" to indicate that the corresponding short CSI report configuration should be activated. The Si field is set to "0" to indicate that the corresponding short CSI report configuration i should be deactivated; and R: reserved bit, set to "0".

[0245] An embodiment of a MAC CE for activating SCell and short CSI reports by signaling the number of reports may include at least the following.

[0246] Example 29 may include the method according to Examples 16 to 19 or some other embodiments herein, wherein the new MAC CE activates the SCell and short CSI reports by signaling the number of reports.

[0247] Example 30 may include the method described according to Example 10 or some other embodiments herein, in addition to the fields defined in Example 28, wherein a new field nrOfReports is provided to the signaling notification MAC CE to indicate the number of CSI reports to be transmitted by the UE on the PUCCH.

[0248] Example 31 may include the method described according to Example 28 or some other embodiments herein, wherein the MAC CE field further includes a new field nrOfReports to indicate the number of CSI reports to be transmitted by the UE on the PUCCH.

[0249] Example 32 may include the method described according to Examples 30 to 31 or some other examples herein, and further includes removing the parameter defining the number of reports in the shortOnPUCCH report type, since the number of reports is notified by the MAC CE signaling.

[0250] Example 33 may include the method described according to Examples 30 to 31 or some other examples herein, wherein the number of reports in the shortOnPUCCH report type is removed.

[0251] An embodiment for short CSI reporting based on parallel MAC CE for SP-CSI reporting of SCell activation and PUCCH activation / deactivation may include at least the following.

[0252] Example 34 may be the method according to Examples 1 to 2 or some other examples herein, wherein the short CSI report during the initial phase of the SCell activation cycle may be implemented by including two phases: 1) a parallel MAC CE for performing SCell activation and SP-CSI reporting for PUCCH activation / deactivation; and 2) a MAC CE for SP-CSI reporting for PUCCH deactivation.

[0253] Example 35 may be the method according to Examples 1 to 2 or some other examples herein, further comprising: generating two parallel MACCEs for performing the SCell activation and for semi-persistent (SP)CSI reporting of PUCCH activation; and generating a MAC CE for performing the SP-CSI reporting of PUCCH deactivation.

[0254] Example 36 may include the method according to Examples 34 to 35 or some other examples herein, wherein the two parallel MAC CEs in phase 1 initiate the start of the SCell activation and short CSI reporting, and the MAC CE signaling in phase 2 notifies the end of the short CSI reporting.

[0255] Example 37 may include the method described according to Examples 34 to 36 or some other examples herein, wherein the SCell activation delay can be fully controlled by the configuration of SP CSI resources and the reporting periodicity dedicated to short CSI reports, both independent of SMTC periodicity, through two-level short CSI reporting.

[0256] Example 38 may include the method according to Example 37 or some other examples herein, wherein at time slot n, the gNB transmits a MAC PDU (protocol data unit) consisting of at least two MAC CEs: 1) a MAC CE for performing SCell activation; and 2) a MAC CE for performing SP CSI reporting on the PUCCH.

[0257] Example 39 may include the method according to Examples 1 to 37 or some other examples herein, and further includes transmitting, at time slot n, a MAC PDU comprising at least two MAC CEs: 1) a MAC CE for performing SCell activation; and 2) a MAC CE for performing SP CSI reporting on the PUCCH.

[0258] Example 40 may include the method according to Examples 2 and 38 to 39 or some other examples herein, wherein at time slot n+k1, it is signaled in the DCI and indicates the delay from the HARQ-ACK response to the scheduling DCI, and the UE generates a HARQ-ACK response for the gNB.

[0259] Example 41 may include the method according to Examples 2 and 38 to 39 or some other examples herein, and further includes generating a HARQ-ACK response for the gNB at time slot n+k1, the time slot being signaled in the DCI and indicating the delay from the HARQ-ACK response to the scheduling DCI.

[0260] Example 42 may include the method according to Examples 40-41 or some other embodiments herein, wherein upon receiving a HARQ-ACK response from the UE, the gNB begins transmitting the CSI resources associated with the activated SP CSI reporting configuration to enable the UE to perform the CSI calculation and reporting. The periodicity of the SP CSI resources may be very small, such as 2, 4, or 5 time slots.

[0261] Example 43 may include the method described in Examples 1 and 38 to 41 or some other embodiments herein, and further includes transmitting the CSI resource associated with the activated SP CSI reporting configuration to enable the UE to perform the CSI calculation and reporting based on the HARQ-ACK response received from the UE, wherein the periodicity of the SP CSI resource may be very small, such as 2, 4 or 5 time slots.

[0262] Example 44 may include the method according to Examples 42 to 43 or some other embodiments herein, wherein the UE performs the CSI calculation and prepares the CSI report based on the activated SP CSI report configuration and with the received SP CSI resources.

[0263] Example 45 may include the method described according to Examples 2 and 39 to 43 or some other embodiments herein, further including: performing CSI calculation; and preparing the CSI report.

[0264] Example 45 may include the method described according to Examples 44-45 or some other embodiments herein, wherein the UE transmits an SP CSI report on the PUCCH. The periodicity of the PUCCH CSI report may be very small, for example, 2, 4, or 5 time slots. After transmitting the first CSI report on the PUCCH, the UE may begin monitoring data scheduling in the SCell.

[0265] Example 46 may include the method described in Examples 44 to 45 or some other embodiments herein, further comprising: transmitting the SP CSI report on the PUCCH, wherein the periodicity of the PUCCH CSI report may be very small, such as 2, 4 or 5 time slots.

[0266] Example 47 may include the method described according to Example 46 or some other embodiments herein, and further includes starting to monitor data scheduling in the SCell after transmitting the first CSI report on the PUCCH.

[0267] Example 48 may include the method described according to Examples 46-47 or some other embodiments herein, wherein after receiving one or more UE CSI reports on the PUCCH, the gNB is notified that UE SCell activation is complete and sufficient CSI knowledge is also obtained. Therefore, channel-aware scheduling can be performed by the gNB for UE data transmission.

[0268] Example 49 may include the method described in accordance with Examples 1, 42 to 43 and 45 to 47 or some other embodiments herein, and may also include receiving information to indicate that UE SCell activation is complete based on receiving one or more UE CSI reports on the PUCCH.

[0269] Example 50 may include the method described according to Examples 1, 42 to 43 and 45 to 47 or some other embodiments herein, the method further comprising: obtaining CSI knowledge; and performing channel-aware scheduling for UE data transmission.

[0270] Example 51 may include the method according to Examples 48 to 50 or some other embodiments herein, wherein the gNB sends a MAC CE to the UE for SP CSI reporting of PUCCH deactivation to deactivate the short CSI report.

[0271] Example 52 may include the method described according to Examples 48 to 50 or some other embodiments herein, and further includes generating and transmitting a MAC CE to the UE for reporting SP CSI to deactivate the PUCCH, thereby deactivating the short CSI report.

[0272] Example 53 may include the method described according to Examples 51 to 52 or some other embodiments herein, wherein the UE transmits a HARQ-ACK response to the gNB and stops the associated short CSI report on the PUCCH.

[0273] Example 54 may include the method described in Examples 2, 45 to 47 and Examples 51 to 52 or some other examples herein, and further includes transmitting the HARQ-ACK response to the gNB; and stopping the associated short CSI report on the PUCCH.

[0274] Example 55 may include an apparatus comprising means for performing one or more elements of the method described or associated with any of Examples 1 to 54 or any other method or process described herein.

[0275] Example 56 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein according to any one of Examples 1 to 54.

[0276] Example 57 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the method described or associated with any of Examples 1.X / 1a.X-24.X or any other method or process described herein.

[0277] Example 58 may include methods, techniques or processes, or parts or components thereof, as described or associated with any of Examples 1 to 54.

[0278] Example 59 may include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process or a portion thereof described or associated with any of Examples 1 to 54.

[0279] Example 60 may include a signal, or a portion thereof, as described or associated with any of Examples 1 to 54.

[0280] Example 61 may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described or associated with any of Examples 1 to 54, or portions or components thereof, or otherwise described in this disclosure.

[0281] Example 62 may include a data-encoded signal, or a portion or component thereof, as described or associated with any of Examples 1 to 54, or otherwise described in this disclosure.

[0282] Example 63 may include signals, or portions or components thereof, encoded as datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described or associated with any of Examples 1 to 54, or otherwise described in this disclosure.

[0283] Example 64 may 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, or a portion thereof, as described or associated with any of Examples 1 to 54.

[0284] Example 65 may 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, or a portion thereof, as described or associated with any of Examples 1 to 54.

[0285] Example 66 may include signals in a wireless network as shown and described herein.

[0286] Example 67 may include methods for communicating in a wireless network as shown and described herein.

[0287] Example 68 may include a system for providing wireless communication as shown and described herein.

[0288] Example 69 may include a device for providing wireless communication as shown and described herein.

[0289] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

Claims

1. A method for wireless communication, the method comprising: Parallel Media Access Control (MAC) control element CE, which receives the Indicator Channel Status Information (CSI) report from the New Radio Access Node (gNB) and is used for secondary cell (Scell) activation and physical uplink control channel (PUCCH) activation, starting during the duration of the semi-persistent SP CSI report. Obtain CSI configuration data, which includes a short CSI reporting scheme that indicates a specific number of CSI reports to be transmitted by the user equipment (UE) on PUCCH resources, an offset of the CSI reports at the time slot level, and the periodicity of the CSI reports. The reporting scheme is specified by a MACCE field included in the CSI configuration data to control CSI reporting at the time slot level. as well as The specific number of CSI reports are sent on the PUCCH resource according to the CSI configuration data. The gNB receives a MAC CE indicating the end of the duration of the short CSI report and deactivating the PUCCH, wherein the MAC CE deactivating the PUCCH is sent by the gNB in ​​response to receiving a valid CSI report indicating that the UE is ready to receive data. The SCell activation delay is less than 10 milliseconds.

2. The method of claim 1, wherein the CSI configuration data is configured via Radio Resource Control (RRC) signaling.

3. The method of claim 1, wherein the specific number of CSI reports is 1 to 16.

4. The method according to claim 1, further comprising: The UE receives a Medium Access Control (MAC) control element (CE) comprising multiple bits from the serving cell of the gNB, wherein at least one individual bit of the multiple bits indicates the status of a short CSI report configuration within a configuration list, and wherein the UE transmits one or more CSI reports from the CSI reports through the configuration list according to the status of the short CSI report configuration.

5. The method of claim 4, wherein the MAC CE further comprises an additional single bit of the plurality of bits, each of the additional single bits indicating whether a corresponding secondary cell SCell of the fifth-generation 5G wireless cellular network is activated or deactivated.

6. The method of claim 4, wherein the MAC CE further includes a report quantity field indicating the specific number of reports to be transmitted by the UE on the PUCCH.

7. A method for wireless communication, the method comprising: The Parallel Media Access Control (MAC) control element CE is used for the semi-persistent SP CSI report, which begins during the duration of the instruction SMS channel status information (CSI) report and is used for secondary cell Scell ​​activation and physical uplink control channel (PUCCH) activation. Send CSI configuration data, which includes a short CSI reporting scheme that indicates a specific number of CSI reports to be transmitted by the user equipment (UE) on PUCCH resources, an offset value of the CSI reports at the time slot level, and the periodicity of the CSI reports. The reporting scheme is specified by a MACCE field included in the CSI configuration data to control CSI reporting at the time slot level. as well as Receive the specific number of CSI reports on the PUCCH resource according to the CSI configuration data. In response to receiving a valid CSI report indicating that the UE is ready to receive data, a MAC CE is sent to deactivate the PUCCH for an SP CSI report indicating the end of the duration of the short CSI report; The activation delay of the secondary cell SCell is less than 10 milliseconds.

8. The method of claim 7, wherein the CSI configuration data is configured via Radio Resource Control (RRC) signaling.

9. The method of claim 7, wherein the specific number of CSI reports is from 1 to 16.

10. The method of claim 7, further comprising: The UE is sent a Media Access Control (MAC) Control Element (CE) comprising multiple bits, wherein at least one of the individual bits indicates the status of a Short CSI Report configuration within a configuration list.

11. The method of claim 10, wherein the MAC CE further comprises an additional single bit of the plurality of bits, each of the additional single bits indicating whether the corresponding secondary cell SCell is activated or deactivated.

12. The method of claim 10, wherein the MAC CE further includes a report quantity field indicating the specific number of reports to be transmitted by the UE on the PUCCH.

13. An apparatus for wireless communication, comprising one or more processors configured to perform the method according to any one of claims 1-12.

14. A non-transitory computer-readable medium comprising instructions for causing an electronic device to perform the method according to any one of claims 1-12 when the instructions are executed by one or more processors of the electronic device.

15. A computer program product comprising instructions for causing an electronic device to perform the method according to any one of claims 1-12 when the instructions are executed by one or more processors of the electronic device.

Images