Patent Grant
11343057
Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in uplink (UL). Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3GPP) long term evolution (LTE) Release 8, 9, 10, 11, 12 and 13, the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m), which is commonly known to industry groups as WiMAX (Worldwide interoperability for Microwave Access), and the IEEE 802.11 standard, which is commonly known to industry groups as WiFi.
In 3GPP radio access network (RAN) LTE systems (e.g., Release 13 and earlier), the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.
Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:
Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.
Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.
An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.
For Fifth Generation (5G) wireless communication systems that operate in the millimeter-wave range, a phase noise level of a “total” oscillator used can be higher than that of traditional wireless communication systems in an ultra-high frequency (UHF) and microwave bands. Here, the phase noise level of the “total oscillator” used can include a reference clock, a loop filter, and other phased-locked loop (PLL) components. For example, a phase noise can increase based on an increase of a carrier frequency. As a result, the performance of 5G wireless communication systems operating in the millimeter-wave range can be limited by phase noise when appropriate compensation mechanisms are not employed.
In one configuration, appropriate techniques to track and compensate the phase noise can be needed. For example, since phase noise can appear as phase rotations of signal samples in a time domain and because a bandwidth of a phase noise process is narrow (i.e., the phase noise is a time correlated process), time domain reference signals can be used to track and compensate the phase noise process. These time domain reference signals used to track and compensate the phase noise can be referred to as phase tracking reference signals (PT-RS). For example, these time domain reference signals can be used to measure a phase offset of the time domain reference signals, thereby providing a significant benefit to the 5G wireless communication systems operating in the millimeter-wave range. The PT-RS can be transmitted from a UE to a base station in an uplink, or alternatively, the PT-RS can be transmitted from the base station to the UE in a downlink. A receiver that receives the PT-RS (e.g., the UE or base station) can measure the phase offset of the PT-RS, and compensate for the phase offset when performing a channel estimation.
In a first scenario (e.g., a high signal-to-noise (SNR) scenario or a high signal-to-interference-plus-noise ratio (SINR) scenario), the phase noise can be a dominant factor in a wireless communication system, whereas in a second scenario (e.g., a low SNR scenario or a low SINIR scenario), a noise and Doppler frequency offset can be the dominant factor in the wireless communication system. The PT-RS pattern 1 (as shown above) may not perform well in low SNR scenarios, especially when a UE is scheduled with N PRBs, as a channel estimation error for the PT-RS can be increased. Therefore, an adaptive PT-RS pattern can be beneficial to adapt to difference types of scenarios,
In one configuration, an adaptive PT-RS pattern and control signaling for the adaptive PT-RS pattern can be utilized to enable a more robust PT-RS for difference types of scenarios, such as the first scenario (e.g., a high SNR scenario or a phase noise limited scenario), which indicates that phase noise is the dominant factor affecting the wireless communication system, or the second scenario (e.g., a low SNR scenario or a noise and Carrier Frequency Offset (CFO) limited scenario), which indicates that CFO is the dominant factor affecting the wireless communication system. The control signaling for the adaptive PT-RS pattern can be transmitted from the base station, and the UE (or the base station) can transmit PT-RS in accordance with the adaptive PT-RS pattern.
In past solutions, the PT-RS pattern 1 (as shown above) was effective in scenarios in which the phase noise was the dominant impact in the wireless communication system (e.g., a high SNR scenario). However, as compared to the PT-RS pattern 1, a novel PT-RS pattern (e.g., a PT-RS pattern 2, as further explained below) can provide improved performance in low SNR scenarios for both a high UE speed (e.g., 50 km/hour) and a low UE speed (e.g., 3 km/hour), when the noise and Doppler frequency offset can be the dominant factor.
In one configuration, an adaptive PT-RS pattern and its control signaling can be utilized that incorporates both the PT-RS pattern 1 and the PT-RS pattern 2, which can enable a more robust PT-RS for different kinds of scenarios (e.g., the high SNR scenario or the low SNR scenarios for both high UE speed and low UE speed), thereby providing additional flexibility and improved performance for the wireless communication system.
In one example, for the high SNR scenario in which the phase noise is the dominant factor affecting the wireless communication system, the PT-RS pattern 1 can be used to compensate for a phase rotation, and then a receiver (e.g., a UE or base station) can estimate a channel in symbols where a demodulation reference signal (DMRS) is not allocated. However, for the low SNR scenario in which the noise and CFO is the dominant factor affecting the wireless communication network, a density of the PT-RS pattern 1 can be insufficient, such that some channel estimation loss can be observed for the PT-RS. Therefore, it can be advantageous to use a PT-RS pattern (e.g., a PT-RS pattern 2, as described further below) other than the PT-RS pattern 1 for the low SNR scenario.
In one configuration, a base station can determine a resource mapping pattern for the PT-RS. The base station can transmit control signaling to the UE. The control signaling can indicate the resource mapping pattern for the PT-RS. The base station can receive one or more PT-RS from the UE in an uplink in accordance with the resource mapping pattern for the PT-RS. In one example, the base station can compensate for a phase rotation based on the one or more PT-RS received from the UE in the uplink in accordance with the resource mapping pattern for the PT-RS. The base station can estimate a channel quality of a channel between the base station and the UE after the phase rotation is compensated based on the one or more PT-RS received from the UE. In another example, the base station can send the resource mapping pattern for the PT-RS to the UE via higher layer signaling or RRC signaling. In yet another example, the base station can transmit the resource mapping pattern for the PT-RS to the UE via an enhanced master information block (xMIB) or an enhanced system information block (xSIB).
In one example, the base station can transmit the resource mapping pattern for the PT-RS to the UE via DCI, wherein the DCI includes one or more values to indicate different resource mapping patterns for the PT-RS. In another example, the base station can determine the resource mapping pattern for the PT-RS based on a modulation and coding scheme (MCS) utilized by the base station. In yet another example, the base station can determine the resource mapping pattern for the PT-RS with a subcarrier offset that is based on a cell identity (ID) or a virtual cell ID. In addition, the PT-RS for one antenna port can span one subcarrier every N PRBs, wherein N is an integer that is semi-statically or dynamically adjusted according to a UE capability or a use case, wherein the use case is dependent on one or more of: a MCS, an allocated bandwidth or a subcarrier spacing.
In one configuration, the UE can receive control signaling in a downlink from the base station. The control signaling can indicate the resource mapping pattern for the PT-RS. The UE can identify the resource mapping pattern for the PT-RS based on the control signaling received from the base station. The UE can receive one or more PT-RS from the base station in a downlink in accordance with the resource mapping pattern for the PT-RS. In one example, the UE can compensate for a phase rotation based on the one or more PT-RS received from the base station in the downlink in accordance with the resource mapping pattern for the PT-RS. The UE can estimate a channel quality of a channel between the UE and the base station after the phase rotation is compensated based on the one or more PT-RS received from the base station.
In one example, the UE can transmit the PT-RS to the base station in an uplink based on the adaptive PT-RS pattern received from the base station. Alternatively, the base station can transmit the PT-RS to the UE in a downlink based on the adaptive PT-RS pattern configured by the base station. In other words, the uplink and the downlink can be symmetric in terms of transmitting the PT-RS based on the adaptive PT-RS pattern. In other example, phase rotation compensation and channel quality estimation can be performed at a receiver (e.g., the UE or the base station). The receiver (e.g., the UE or the base station) can receive the PT-RS and then measure the phase offset of the PT-RS. In the downlink, the phase rotation compensation and channel quality estimation can be performed at the UE, whereas in the uplink, the phase rotation compensation and channel quality estimation can be performed at the base station.
In one configuration, a UE can receive control signaling in a downlink from the base station. The control signaling can indicate to the UE a resource mapping pattern for the PT-RS. The UE can identify the resource mapping pattern for the PT-RS based on the control signaling received from the base station. The UE can transmit one or more PT-RS to the base station in an uplink in accordance with the resource mapping pattern for the PT-RS. In one example, the UE can select a resource mapping pattern for the PT-RS from a set of resource mapping patterns for the PT-RS that are predefined at the UE, wherein the resource mapping pattern for the PT-RS is selected based on the control signaling received from the base station. In another example, the UE can receive the resource mapping pattern for the PT-RS from the base station via a higher layer signaling or a radio resource control (RRC) signaling. In yet another example, the UE can receive the resource mapping pattern for the PT-RS from the base station via DCI, wherein the DCI includes one or more values to indicate different resource mapping patterns for the PT-RS. In a further example, different resource mapping patterns for the PT-RS can create different time and frequency densities of the PT-RS. In yet a further example, the resource mapping pattern for the PT-RS can indicate that there is no PT-RS transmission from the UE. In addition, the resource mapping pattern for the PT-RS can be an adaptive pattern that is configured by the base station based on a presence of a phase noise limited scenario in the wireless network or a noise and CFO limited scenario in the wireless network. The phase noise limited scenario can indicate that phase noise is the dominant factor affecting a wireless network and the CFO limited scenario can indicate that CFO is the dominant factor affecting the wireless network.
In one example, downlink control information (DCI) transmitted from a base station to a UE can include an indicator of the PT-RS pattern, which can be useful for adjusting the PT-RS pattern being used in the wireless communication system. For example, the indicator can be a 1-bit value, in which a first value can indicate that the PT-RS pattern 1 is used (as shown in
In one example, the PT-RS pattern can be configured via semi-statically by high layer signaling from the base station to the UE. Alternatively, the PT-RS can be configured by the base station using a combination of DCI and high layer signaling. For example, a higher layer can define a subset of PT-RS patterns, and the DCI may be used to indicate to the UE which PT-RS pattern is used from the subset of PT-RS patterns. In another example, the PT-RS for one antenna port can span one subcarrier every N PRBs, wherein N can be semi-statically or dynamically adjusted according to a UE capability or based on a use case.
In one example, the nest structure can be extended to a multiple APs case. For instance, when two APs are defined for the PT-RS for N=4, a same subcarrier can be allocated for the PT-RS for N=2 and N=4. In other words, one AP for the PT-RS in N=2 can be defined as another AP for the PT-RS in N=4.
In one example, a PT-RS density can be semi-statically configured by higher layers via a 5G master information block (xMIB) or a 5G system information block (xSIB) transmitted from a base station. Alternatively, the PT-RS density can be configured via RRC signaling from the base station, or dynamically indicated in DCI transmitted from the base station. In one example, since a delay spread can be different when different transmit (Tx) or receive (Rx) beams are applied, the PT-RS density can be beam specific. In another example, K PT-RS density indicators can be configured by higher layers, where K is a number of beams maintained for one UE, e.g. K=4.
In one configuration, the PT-RS pattern can be determined based on a modulation and coding scheme (MCS) utilized at a UE, which can reflect the SINR. A threshold can be predefined by the wireless communication system or configured by higher layer signaling, which can cause some scheduling restriction on the MU-MIMO case, as co-scheduled UEs are to use a same PT-RS pattern. However, this can reduce an amount of control signaling overhead in the DCI.
As shown in
As shown in
In one configuration, a user equipment (UE) can receive control signaling for a phase tracking reference signal (PT-RS) and determine a resource mapping pattern for the PT-RS based on the control signaling. In one example, multiple PT-RS patterns can be predefined in a specification. In another example, the PT-RS patterns can be configured via higher layer signaling.
In one example, the UE can select a PT-RS pattern from all or a subset of predefined PT-RS patterns to generate the PT-RS. An indicator of the PT-RS pattern can be configured via downlink control information (DCI) or higher layer signaling. In another example, the PT-RS pattern can be determined based on a modulation and coding scheme (MCS) used at the UE. In yet another example, a density of the PT-RS can be configured via the DCI or the higher layer signaling. In a further example, a multiple PT-RS density can be configured and each can be used for one network beam. In yet a further example, a PT-RS subcarrier offset for a PT-RS can be determined based on a cell identity (ID) or a virtual cell ID.
Another example provides functionality 1200 of a UE operable to decode a resource mapping pattern of a phase tracking reference signal (PT-RS) received from a base station in a wireless network, as shown in
Another example provides functionality 1300 of a base station operable to encode a resource mapping pattern of a phase tracking reference signal (PT-RS) for transmission to a user equipment (UE) in a wireless network, as shown in
Another example provides at least one machine readable storage medium having instructions 1400 embodied thereon for decoding a resource mapping pattern of a phase tracking reference signal (PT-RS) received at a user equipment (UE) from a base station in a wireless network, as shown in
In some embodiments, any of the UEs 1501 and 1502 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
The UEs 1501 and 1502 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1510—the RAN 1510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 1501 and 1502 utilize connections 1503 and 1504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 1503 and 1504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
In this embodiment, the UEs 1501 and 1502 may further directly exchange communication data via a ProSe interface 1505. The ProSe interface 1505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
The UE 1502 is shown to be configured to access an access point (AP) 1506 via connection 1507. The connection 1507 can comprise a local wireless connection, such as a connection consistent with any IEEE 1602.15 protocol, wherein the AP 1506 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 1506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
The RAN 1510 can include one or more access nodes that enable the connections 1503 and 1504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 1510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1511, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1512.
Any of the RAN nodes 1511 and 1512 can terminate the air interface protocol and can be the first point of contact for the UEs 1501 and 1502. In some embodiments, any of the RAN nodes 1511 and 1512 can fulfill various logical functions for the RAN 1510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
In accordance with some embodiments, the UEs 1501 and 1502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1511 and 1512 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1511 and 1512 to the UEs 1501 and 1502, 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 is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs 1501 and 1502. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 1501 and 1502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 1502 within a cell) may be performed at any of the RAN nodes 1511 and 1512 based on channel quality information fed back from any of the UEs 1501 and 1502. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 1501 and 1502.
The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 16).
Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
The RAN 1510 is shown to be communicatively coupled to a core network (CN) 1520—via an S1 interface 1513. In embodiments, the CN 1520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface 1513 is split into two parts: the S1-U interface 1514, which carries traffic data between the RAN nodes 1511 and 1512 and the serving gateway (S-GW) 1522, and the S1-mobility management entity (MME) interface 1515, which is a signaling interface between the RAN nodes 1511 and 1512 and MMEs 1521.
In this embodiment, the CN 1520 comprises the MMEs 1521, the S-GW 1522, the Packet Data Network (PDN) Gateway (P-GW) 1523, and a home subscriber server (HSS) 1524. The MMEs 1521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 1521 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 1524 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 1520 may comprise one or several HSSs 1524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 1524 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
The S-GW 1522 may terminate the S1 interface 1513 towards the RAN 1510, and routes data packets between the RAN 1510 and the CN 1520. In addition, the S-GW 1522 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
The P-GW 1523 may terminate an SGi interface toward a PDN. The P-GW 1523 may route data packets between the EPC network 1523 and external networks such as a network including the application server 1530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 1525. Generally, the application server 1530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 1523 is shown to be communicatively coupled to an application server 1530 via an IP communications interface 1525. The application server 1530 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1501 and 1502 via the CN 1520.
The P-GW 1523 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 1526 is the policy and charging control element of the CN 1520. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 1526 may be communicatively coupled to the application server 1530 via the P-GW 1523. The application server 1530 may signal the PCRF 1526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 1526 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 1530.
The application circuitry 1602 may include one or more application processors. For example, the application circuitry 1602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1600. In some embodiments, processors of application circuitry 1602 may process IP data packets received from an EPC.
The baseband circuitry 1604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1606 and to generate baseband signals for a transmit signal path of the RF circuitry 1606. Baseband processing circuitry 1604 may interface with the application circuitry 1602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1606. For example, in some embodiments, the baseband circuitry 1604 may include a third generation (3G) baseband processor 1604a, a fourth generation (4G) baseband processor 1604b, a fifth generation (5G) baseband processor 1604c, or other baseband processor(s) 1604d for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 1604 (e.g., one or more of baseband processors 1604a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1606. In other embodiments, some or all of the functionality of baseband processors 1604a-d may be included in modules stored in the memory 1604g and executed via a Central Processing Unit (CPU) 1604e. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
In some embodiments, the baseband circuitry 1604 may include one or more audio digital signal processor(s) (DSP) 1604f. The audio DSP(s) 1604f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1604 and the application circuitry 1602 may be implemented together such as, for example, on a system on a chip (SOC).
In some embodiments, the baseband circuitry 1604 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
RF circuitry 1606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1608 and provide baseband signals to the baseband circuitry 1604. RF circuitry 1606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1604 and provide RF output signals to the FEM circuitry 1608 for transmission.
In some embodiments, the receive signal path of the RF circuitry 1606 may include mixer circuitry 1606a, amplifier circuitry 1606b and filter circuitry 1606c. In some embodiments, the transmit signal path of the RF circuitry 1606 may include filter circuitry 1606c and mixer circuitry 1606a. RF circuitry 1606 may also include synthesizer circuitry 1606d for synthesizing a frequency for use by the mixer circuitry 1606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1608 based on the synthesized frequency provided by synthesizer circuitry 1606d. The amplifier circuitry 1606b may be configured to amplify the down-converted signals and the filter circuitry 1606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1604 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
In some embodiments, the mixer circuitry 1606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1606d to generate RF output signals for the FEM circuitry 1608. The baseband signals may be provided by the baseband circuitry 1604 and may be filtered by filter circuitry 1606c.
In some embodiments, the mixer circuitry 1606a of the receive signal path and the mixer circuitry 1606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1606a of the receive signal path and the mixer circuitry 1606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1606a of the receive signal path and the mixer circuitry 1606a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1606a of the receive signal path and the mixer circuitry 1606a of the transmit signal path may be configured for super-heterodyne operation.
In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1604 may include a digital baseband interface to communicate with the RF circuitry 1606.
In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
In some embodiments, the synthesizer circuitry 1606d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
The synthesizer circuitry 1606d may be configured to synthesize an output frequency for use by the mixer circuitry 1606a of the RF circuitry 1606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1606d may be a fractional N/N+1 synthesizer.
In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1604 or the applications processor 1602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1602.
Synthesizer circuitry 1606d of the RF circuitry 1606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
In some embodiments, synthesizer circuitry 1606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1606 may include an IQ/polar converter.
FEM circuitry 1608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1606 for further processing. FEM circuitry 1608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1606 for transmission by one or more of the one or more antennas 1610. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1606, solely in the FEM 1608, or in both the RF circuitry 1606 and the FEM 1608.
In some embodiments, the FEM circuitry 1608 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1606). The transmit signal path of the FEM circuitry 1608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1610).
In some embodiments, the PMC 1612 may manage power provided to the baseband circuitry 1604. In particular, the PMC 1612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 1612 may often be included when the device 1600 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 1612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
While
In some embodiments, the PMC 1612 may control, or otherwise be part of, various power saving mechanisms of the device 1600. For example, if the device 1600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1600 may power down for brief intervals of time and thus save power.
If there is no data traffic activity for an extended period of time, then the device 1600 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1600 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
Processors of the application circuitry 1602 and processors of the baseband circuitry 1604 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1604, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
The baseband circuitry 1604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1604), an application circuitry interface 1714 (e.g., an interface to send/receive data to/from the application circuitry 1602 of
The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.
Example 1 includes an apparatus of a user equipment (UE) operable to decode a resource mapping pattern of a phase tracking reference signal (PT-RS) received from a base station in a wireless network, the apparatus comprising: one or more processors configured to: decode, at the UE, control signaling received in a downlink from the base station, wherein the control signaling indicates a resource mapping pattern for a PT-RS; identify, at the UE, the resource mapping pattern for the PT-RS based on the control signaling received from the base station; and encode, at the UE, one or more PT-RS for transmission to the base station in an uplink in accordance with the resource mapping pattern for the PT-RS; and a memory interface configured to send to a memory the resource mapping pattern for the PT-RS.
Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: receive, from the base station, the control signaling that indicates the resource mapping pattern for the PT-RS; and transmit the one or more PT-RS to the base station in accordance with the resource mapping pattern for the PT-RS.
Example 3 includes the apparatus of any of Examples 1 to 2, wherein the one or more processors are further configured to select a resource mapping pattern for the PT-RS from a set of resource mapping patterns for the PT-RS that are predefined at the UE, wherein the resource mapping pattern for the PT-RS is selected based on the control signaling received from the base station.
Example 4 includes the apparatus of any of Examples 1 to 3, wherein the one or more processors are configured to decode the resource mapping pattern for the PT-RS received from the base station via a higher layer signaling or a radio resource control (RRC) signaling.
Example 5 includes the apparatus of any of Examples 1 to 4, wherein the one or more processors are configured to decode the resource mapping pattern for the PT-RS received from the base station via downlink control information (DCI), wherein the DCI includes one or more values to indicate different resource mapping patterns for the PT-RS.
Example 6 includes the apparatus of any of Examples 1 to 5, wherein the resource mapping pattern for the PT-RS is based on one or more of: a modulation and coding scheme (MCS) utilized at the UE, an allocated bandwidth, a subcarrier spacing or a phase noise characteristic.
Example 7 includes the apparatus of any of Examples 1 to 6, wherein a subcarrier offset of the resource mapping pattern of the PT-RS is based on a cell identity (ID) or a virtual cell ID.
Example 8 includes the apparatus of any of Examples 1 to 7, wherein different resource mapping patterns for the PT-RS create different time and frequency densities of the PT-RS.
Example 9 includes the apparatus of any of Examples 1 to 8, wherein the resource mapping pattern for the PT-RS indicates that there is no PT-RS transmission from the UE.
Example 10 includes the apparatus of any of Examples 1 to 9, wherein the PT-RS for one antenna port spans one subcarrier every N physical resource blocks (PRBs), wherein N is an integer that is semi-statically or dynamically adjusted according to a UE capability or a use case, wherein the use case is dependent on one or more of: a modulation and coding schemes (MCS), an allocated bandwidth or a subcarrier spacing.
Example 11 includes the apparatus of any of Examples 1 to 10, wherein the resource mapping pattern for the PT-RS is an adaptive pattern that is configured by the base station based on a presence of a phase noise limited scenario in the wireless network or a noise and carrier frequency offset (CFO) limited scenario in the wireless network, wherein the phase noise limited scenario indicates that phase noise is a dominant factor affecting the wireless network and the CFO limited scenario indicates that CFO is a dominant factor affecting the wireless network.
Example 12 includes an apparatus of a base station operable to encode a resource mapping pattern of a phase tracking reference signal (PT-RS) for transmission to a user equipment (UE) in a wireless network, the apparatus comprising: one or more processors configured to: determine, at the base station, a resource mapping pattern for the PT-RS; encode, at the base station, control signaling for transmission to the UE, wherein the control signaling indicates the resource mapping pattern for the PT-RS; and decode, at the base station, one or more PT-RS received from the UE in an uplink in accordance with the resource mapping pattern for the PT-RS; and a memory interface configured to send to a memory the resource mapping pattern for the PT-RS.
Example 13 includes the apparatus of Example 12, wherein the one or more processors are further configured to: compensate for a phase rotation based on the one or more PT-RS received from the UE in the uplink in accordance with the resource mapping pattern for the PT-RS; and estimate a channel quality of a channel between the base station and the UE after the phase rotation is compensated based on the one or more PT-RS received from the UE.
Example 14 includes the apparatus of any of Examples 12 to 13, wherein the one or more processors are configured to encode the resource mapping pattern for the PT-RS for transmission to the UE via higher layer signaling or a radio resource control (RRC) signaling.
Example 15 includes the apparatus of any of Examples 12 to 14, wherein the one or more processors are configured to encode the resource mapping pattern for the PT-RS for transmission to the UE via an enhanced master information block (xMIB) or an enhanced system information block (xSIB).
Example 16 includes the apparatus of any of Examples 12 to 15, wherein the one or more processors are configured to encode the resource mapping pattern for the PT-RS for transmission to the UE via downlink control information (DCI), wherein the DCI includes one or more values to indicate different resource mapping patterns for the PT-RS.
Example 17 includes the apparatus of any of Examples 12 to 16, wherein the one or more processors are further configured to determine the resource mapping pattern for the PT-RS based on a modulation and coding scheme (MCS) utilized by the base station.
Example 18 includes the apparatus of any of Examples 12 to 17, wherein the one or more processors are further configured to determine the resource mapping pattern for the PT-RS with a subcarrier offset that is based on a cell identity (ID) or a virtual cell ID.
Example 19 includes the apparatus of any of Examples 12 to 18, wherein the one or more processors are further configured to determine the resource mapping pattern for the PT-RS based on a presence of a phase noise limited scenario in the wireless network or a noise and carrier frequency offset (CFO) limited scenario in the wireless network.
Example 20 includes at least one machine readable storage medium having instructions embodied thereon for decoding a resource mapping pattern of a phase tracking reference signal (PT-RS) received at a user equipment (UE) from a base station in a wireless network, the instructions when executed by one or more processors of the UE perform the following: decoding, at the UE, control signaling received in a downlink from the base station, wherein the control signaling indicates a resource mapping pattern for a PT-RS; identifying, at the UE, the resource mapping pattern for the PT-RS based on the control signaling received from the base station; and decoding, at the UE, one or more PT-RS received from the base station in a downlink in accordance with the resource mapping pattern for the PT-RS.
Example 21 includes the at least one machine readable storage medium of Example 20, further comprising instructions when executed perform the following: compensating for a phase rotation based on the one or more PT-RS received from the base station in the downlink in accordance with the resource mapping pattern for the PT-RS; and estimating a channel quality of a channel between the UE and the base station after the phase rotation is compensated based on the one or more PT-RS received from the base station.
Example 22 includes the at least one machine readable storage medium of any of Examples 20 to 21, further comprising instructions when executed perform the following: decoding the resource mapping pattern for the PT-RS received from the base station via a higher layer signaling or a radio resource control (RRC) signaling; or decoding the resource mapping pattern for the PT-RS received from the base station via downlink control information (DCI), wherein the DCI includes one or more values to indicate different resource mapping patterns for the PT-RS.
Example 23 includes the at least one machine readable storage medium of any of Examples 20 to 22, wherein: the resource mapping pattern for the PT-RS is based on one or more of: a modulation and coding scheme (MCS) utilized at the UE, an allocated bandwidth, a subcarrier spacing or a phase noise characteristic; or different resource mapping patterns for the PT-RS create different time and frequency densities of the PT-RS.
Example 24 includes the at least one machine readable storage medium of any of Examples 20 to 23, wherein the PT-RS for one antenna port spans one subcarrier every N physical resource blocks (PRBs), wherein N is an integer that is semi-statically or dynamically adjusted according to a UE capability or a use case, wherein the use case is dependent on one or more of: a modulation and coding schemes (MCS), an allocated bandwidth or a subcarrier spacing.
Example 25 includes the at least one machine readable storage medium of any of Examples 20 to 24, wherein the resource mapping pattern for the PT-RS is an adaptive pattern that is configured by the base station based on a presence of a phase noise limited scenario in the wireless network or a noise and carrier frequency offset (CFO) limited scenario in the wireless network, wherein the phase noise limited scenario indicates that phase noise is a dominant factor affecting the wireless network and the CFO limited scenario indicates that CFO is a dominant factor affecting the wireless network.
Example 26 includes a user equipment (UE) operable to decode a resource mapping pattern of a phase tracking reference signal (PT-RS) received at from a base station in a wireless network, the UE comprising: means for decoding, at the UE, control signaling received in a downlink from the base station, wherein the control signaling indicates a resource mapping pattern for a PT-RS; means for identifying, at the UE, the resource mapping pattern for the PT-RS based on the control signaling received from the base station; and means for decoding, at the UE, one or more PT-RS received from the base station in a downlink in accordance with the resource mapping pattern for the PT-RS.
Example 27 includes the UE of Example 26, further comprising: means for compensating for a phase rotation based on the one or more PT-RS received from the base station in the downlink in accordance with the resource mapping pattern for the PT-RS; and estimating a channel quality of a channel between the UE and the base station after the phase rotation is compensated based on the one or more PT-RS received from the base station.
Example 28 includes the UE of any of Examples 26 to 27, further comprising: means for decoding the resource mapping pattern for the PT-RS received from the base station via a higher layer signaling or a radio resource control (RRC) signaling; or decoding the resource mapping pattern for the PT-RS received from the base station via downlink control information (DCI), wherein the DCI includes one or more values to indicate different resource mapping patterns for the PT-RS.
Example 29 includes the UE of any of Examples 26 to 28, wherein: the resource mapping pattern for the PT-RS is based on one or more of: a modulation and coding scheme (MCS) utilized at the UE, an allocated bandwidth, a subcarrier spacing or a phase noise characteristic; or different resource mapping patterns for the PT-RS create different time and frequency densities of the PT-RS different resource mapping patterns for the PT-RS create different time and frequency densities of the PT-RS.
Example 30 includes the UE of any of Examples 26 to 29, wherein the PT-RS for one antenna port spans one subcarrier every N physical resource blocks (PRBs), wherein N is an integer that is semi-statically or dynamically adjusted according to a UE capability or a use case, wherein the use case is dependent on one or more of: a modulation and coding schemes (MCS), an allocated bandwidth or a subcarrier spacing.
Example 31 includes the UE of any of Examples 26 to 30, wherein the resource mapping pattern for the PT-RS is an adaptive pattern that is configured by the base station based on a presence of a phase noise limited scenario in the wireless network or a noise and carrier frequency offset (CFO) limited scenario in the wireless network, wherein the phase noise limited scenario indicates that phase noise is a dominant factor affecting the wireless network and the CFO limited scenario indicates that CFO is a dominant factor affecting the wireless network.
Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). In one example, selected components of the transceiver module can be located in a cloud radio access network (C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
As used herein, the term “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.
It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.
Reference throughout this specification to “an example” or “exemplary” means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases “in an example” or the word “exemplary” in various places throughout this specification are not necessarily all referring to the same embodiment.
As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.
While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/CN2016/093587 | Aug 2016 | WO | international |
The present application is a continuation of U.S. patent application Ser. No. 16/323,465 filed Feb. 5, 2019 which is a 371 Nationalization of PCT Application No. PCT/US2017/045748 filed Aug. 7, 2017, which claims priority to CN PCT Application No. PCT/CN2016/093587 filed Aug. 5, 2016, the entire specification of which is hereby incorporated by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20080101492 | Gregoire et al. | May 2008 | A1 |
| 20170294926 | Islam | Oct 2017 | A1 |
| 20170302352 | Islam | Oct 2017 | A1 |
| 20180041321 | Guo | Feb 2018 | A1 |
| 20190222385 | Hessler et al. | Jul 2019 | A1 |
| 20190356463 | Zhang | Nov 2019 | A1 |
| 20200235979 | Yokomakura et al. | Jul 2020 | A1 |
| 20210076389 | Zhang et al. | Mar 2021 | A1 |
| Entry |
|---|
| 3GPP TS 36.211 V12.4.0; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 12); Valbonne—France (Dec. 2014). |
| U.S. Appl. No. 16/323,465, Non-Final Office Action, dated Jan. 12, 2021 ,18 pages. |
| U.S. Appl. No. 16/323,465, et al., Notice of Allowance ,dated Apr. 23, 2021 ,9 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190356463 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16323465 | US | |
| Child | 16408003 | US |
