System and method for transmitting a phase tracking reference signal for OFDM

By introducing adjacent subcarriers and guard subcarrier structures into the NR system, combined with Zadoff-Chu sequence modulation, the problem of insufficient phase noise estimation granularity in the NR system is solved, and the communication performance in the millimeter-wave band is improved.

CN113366806BActive Publication Date: 2024-11-19APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080011089.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-03-14
Filing Date
2020-03-13
Publication Date
2024-11-19
Estimated Expiration
2040-03-13

AI Technical Summary

Technical Problem

In existing NR systems, the PT-RS structure has insufficient granularity when estimating phase noise in the millimeter-wave band, making it difficult to meet the phase change requirements at higher frequencies. This results in insufficiently precise phase noise estimation, which affects communication performance.

Method used

In the resource allocation of PDSCH or PUSCH, one or more sets of adjacent subcarriers are introduced, including guard subcarriers and subcarriers for transmitting PT-RS signals. Zero-power or non-zero-power subcarriers are used, and the PT-RS signals are modulated by Zadoff-Chu sequences or pulse functions. Cyclic extension to guard subcarriers is used to improve the accuracy of phase noise estimation.

Benefits of technology

By using fine-grained phase noise estimation and compensation, the communication performance of the NR system in the millimeter-wave band is improved, inter-carrier interference is reduced, and the accuracy of the phase tracking reference signal is increased.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113366806B_ABST
    Figure CN113366806B_ABST
Patent Text Reader

Abstract

The present disclosure provides orthogonal frequency division multiplexing (OFDM) communication using a phase tracking reference signal (PT‑RS) in a wireless network, including: determining adjacent subcarriers of one or more PT‑RS groups in a resource allocation for a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH); encoding data in a data subcarrier within the resource allocation for the PUSCH or PDSCH for transmission by the PUSCH or PDSCH; and encoding a phase tracking reference signal within adjacent subcarriers of the one or more PT‑RS groups.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 818,611, filed on March 14, 2019, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present application relates generally to wireless communication systems, and more particularly to phase noise cancellation using a phase tracking reference signal. Background Art

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

[0005] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a Global System for Mobile Communications (GSM), an Enhanced Data Rate for GSM Evolution (EDGE) RAN (GERAN), a Universal Terrestrial Radio Access Network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, and the E-UTRAN implements the LTE RAT.

[0006] To support system access and services that provide different features and connectivity control for future services, 5G or NR systems are expected to use higher millimeter wave (mmWave) frequencies to significantly increase capacity. However, mmWave devices and network access points may suffer from severe phase noise due to mismatches in transmitter and receiver frequency oscillators. For example, phase noise can be caused by noise up-converted to the carrier frequency in active components and lossy elements. In NR systems, dedicated types of reference signals (RS) have been defined to estimate phase fluctuations of downlink (DL) or uplink (UL) signals that may occur due to transmit (Tx) or receive (Rx) phase noise or high mobility. In the NR technical specification, such signals are referred to as phase tracking reference signals (PT-RS). The phase can be estimated based on the PT-RS and subsequently compensated by the UE or gNB receiver, thereby improving the overall performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1 Resource blocks according to one embodiment are shown.

[0009] Figure 2 A PT-RS structure according to one embodiment is shown.

[0010] Figure 3 A pulse function according to one embodiment is shown.

[0011] Figure 4 A PT-RS group according to one embodiment is shown.

[0012] Figure 5 A method for transmitting a PT-RS for orthogonal frequency division multiplexing (OFDM) in a wireless communication system according to one embodiment is shown.

[0013] Figure 6 A system according to one embodiment is shown.

[0014] Figure 7 Infrastructure equipment according to one embodiment is shown.

[0015] Figure 8 A platform according to one embodiment is shown.

[0016] Fig. 9 An apparatus according to one embodiment is shown.

[0017] Fig.10 An exemplary interface according to one embodiment is shown.

[0018] Fig.11 Components according to one embodiment are shown. DETAILED DESCRIPTION

[0019] The current design of PT-RS in NR assumes that the RS is transmitted from the same logical antenna port as one of the UE-specific demodulation RSs (DM-RS) used for coherent demodulation of the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH). In addition, the associated PT-RS and DM-RS antenna ports share the same subcarrier in the physical resource block (PRB) used for PDSCH or PUSCH. For example, Figure 1 PT-RS mapping in the 3GPP Release 15 (Rel-15) NR specification is shown, where a resource block 100 includes a plurality of resource elements (corresponding to respective subcarriers) configured for control information subcarriers 102, demodulation reference signals 104, PT-RS 106, and data subcarriers 108.

[0020] like Figure 1 As shown, the existing PT-RS structure in Rel-15 NR supports uniform allocation of resource elements for PT-RS 106PDSCH or PUSCH resource allocation with equal spacing between PT-RS subcarriers in the frequency domain. Such a structure can be optimized to support common phase error estimation for the entire orthogonal frequency division multiplexing (OFDM) symbol containing PT-RS. However, this granularity of phase noise estimation may not be enough. Specifically, for higher carrier frequencies in the millimeter wave band, such as >52.6GHz, the changes in phase within OFDM become more obvious, which may require phase noise estimation with finer granularity, such as at the sub-OFDM symbol level. Therefore, the use of existing PT-RS structures may not allow estimation or may make it more difficult to estimate phase noise with finer granularity than OFDM symbols.

[0021] In certain embodiments disclosed herein, the PT-RS structure includes one or more groups of adjacent subcarriers within a resource allocation for a PDSCH or PUSCH. The subcarriers within a PT-RS group may include guard subcarriers and subcarriers that transmit PT-RS signals. The guard subcarriers may be used to prevent inter-carrier interference caused by the PDSCH or PUSCH. The guard subcarriers may be zero-power or non-zero-power. In certain such embodiments, the power of non-zero-power PT-RS subcarriers may be increased. In addition or in other embodiments, the PT-RS signals within the PT-RS group may be modulated with a sequence that provides an almost perfect or perfect autocorrelation characteristic (e.g., using a Zadoff-Chu or pulse sequence). In certain embodiments, cyclically extending the PT-RS sequence to the guard subcarriers may be used to further improve performance.

[0022] According to certain embodiments, the PT-RS structure allows for phase noise estimation with finer granularity than an OFDM symbol.More frequent phase noise compensation with sub-OFDM symbol duration improves performance.

[0023] PT-RS structure within a time slot

[0024] Figure 2 A PT-RS structure 200 according to one embodiment is shown. The PT-RS structure 200 includes one or more PT-RS groups 202 (three are shown) within a resource allocation 204 for a PDSCH or PUSCH. Within a resource allocation 204 for a PDSCH or PUSCH, one or more PT-RS groups 202 may be transmitted, wherein each PT-RS group 202 includes more than one adjacent subcarrier.

[0025] Depending on the implementation, the subcarriers within the PT-RS group 202 may have zero power or non-zero power assignments. If zero power subcarriers are used (denoted as guard subcarriers), the zero power subcarriers may be transmitted on the boundaries of the PT-RS group 202. For example, guard subcarrier 206 and guard subcarrier 208 are each on the boundary between a non-PT-RS subcarrier and a PT-RS subcarrier within the PT-RS group 202. In certain implementations, the unused power from the zero power subcarriers is used to increase the power of the non-zero power PT-RS subcarriers to improve performance. The guard subcarriers may be used to prevent inter-carrier interference (ICI) of the PDSCH or PUSCH that may occur, for example, if the phase within the OFDM symbol changes significantly.

[0026] For the PT-RS group 202, according to some embodiments, the total subcarriers and / or the number of non-zero power subcarriers within the PT-RS group used by the PT-RS may be predefined or configured by high-layer signaling (e.g., radio resource control (RRC)) or downlink control information (DCI). In other embodiments, the number of subcarriers may be determined by at least one parameter, the at least one parameter including: cell identifier (ID), virtual cell ID, PT-RS port index, radio network temporary identifier (RNTI), symbol / slot index, subcarrier spacing, modulation and coding scheme (MCS), number of PRBs, etc. In some embodiments, the frequency offset of the PT-RS group 202 and / or the number of PT-RS groups may be predefined or configured by high-layer signaling (e.g., RRC) or DCI, or determined by parameters including at least one of the following: cell ID, virtual cell ID, PT-RS port index, RNTI, symbol / slot index, etc.

[0027] PT-RS sequence

[0028] In certain embodiments, the non-zero PT-RS subcarriers are modulated with a sequence that provides perfect or nearly perfect autocorrelation properties. Examples of sequences that may be used to modulate subcarriers within a PT-RS group are provided below.

[0029] According to a first example, a pulse function may be used to modulate the PT-RS subcarriers within a PT-RS group. The PT-RS modulation sequence may be given by the following equation:

[0030] n=0,1,...,N-1,where Where N is the number of subcarriers in the PT-RS group. Figure 3 An exemplary pulse function 300 for PT-RS group modulation is shown according to an exemplary embodiment.

[0031] In another example, the PT-RS is modulated by a Zadoff-Chu sequence. In some such embodiments, the Zadoff-Chu sequence is also cyclically extended to the guard subcarriers. According to this example, the modulation sequence can be given by the following equation:

[0032] s(n)=x q ({n+N 0}mod N ZC ), n=0,1,...,N-1,

[0033] Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers in the PT-RS group, and No determines the length of the cyclic extension. In some embodiments, m can be an integer between zero and Nzc.

[0034] Figure 4 The cyclic extension of the Zadoff-Chu sequence according to one embodiment is shown. Figure 4 In the example shown, the PT-RS group 400 includes a plurality of adjacent subcarriers, including six non-zero power PT-RS subcarriers between the guard subcarrier 402 and the guard subcarrier 404. Applying a Zadoff-Chu sequence (ZC sequence) to the non-zero power PT-RS subcarriers causes the ZC sequence to be cyclically extended to the guard subcarrier 402 and the guard subcarrier 404. The cyclic extension is from the non-zero power subcarrier 406 to the guard subcarrier 402, and from the non-zero power subcarrier 408 to the guard subcarrier 404. The cyclic extension of the ZC sequence to the guard subcarrier 402 and the guard subcarrier 404 prevents ICI of the PDSCH and the PUSCH, and can guarantee a perfect or near-perfect autocorrelation property of the sequence through a cyclic convention.

[0035] In certain embodiments, the root of the Zadoff-Chu sequence q may be the same or different across PT-RS groups, OFDM symbols, time slots, physical cell IDs, RNTIs, etc. to provide inter-cell interference randomization.

[0036] Indications for PT-RS

[0037] PT-RS transmission according to certain embodiments disclosed herein may be more useful for higher order modulation. Therefore, according to one embodiment, a base station (e.g., (gNB)) is configured to indicate an MCS threshold and / or an allocated bandwidth threshold to a UE when using the PT-RS structure disclosed herein (e.g., using RRC signaling). If the MCS in the DCI scheduling the PDSCH or PUSCH is higher than the MCS threshold and / or the allocated bandwidth threshold, the UE assumes PT-RS according to the present disclosure. Otherwise, a conventional PT-RS structure (e.g., according to Rel-15) may be used. In certain such embodiments, the MCS threshold may be different for different MCS tables.

[0038] To facilitate such PT-RS signaling decisions, according to certain embodiments, the UE signals the corresponding MCS threshold and / or allocated bandwidth threshold to the gNB as part of UE capability signaling. In certain such embodiments, the signaled PT-RS parameters may include at least one or more of the following parameters: the number of non-zero power subcarriers within a PT-RS group, the number of PT-RS groups, and the frequency offset of the PT-RS groups.

[0039] Conflict handling with other reference signals

[0040] In certain embodiments, if a subset or all of the non-zero power PT-RS subcarriers within a PT-RS group are punctured due to collision with other downlink signals (e.g., channel state information (CSI) reference signal (CSI-RS)), the subcarriers used as PT-RS subcarriers within the same PT-RS group may be used for data channel transmission.

[0041] Figure 5A flow chart of a method 500 for transmitting a PT-RS for OFDM in a wireless communication system according to one embodiment is shown. In block 502, the method 500 determines adjacent subcarriers of one or more PT-RS groups in a resource allocation for a PUSCH or a PDSCH. The adjacent subcarriers of the one or more PT-RS groups may include, for example, at least two PT-RS groups separated from each other by one or more data subcarriers in a data subcarrier. In block 504, the method 500 encodes data in a data subcarrier within the resource allocation for the PUSCH or the PDSCH for transmission by the PUSCH or the PDSCH. In block 506, the method 500 encodes a phase tracking reference signal within the adjacent subcarriers of the one or more PT-RS groups.

[0042] In certain embodiments, at block 508, method 500 configures guard subcarriers within adjacent subcarriers of the one or more PT-RS groups to prevent inter-carrier interference caused by PUSCH or PDSCH. The guard subcarriers may be configured to have zero power at the boundaries of adjacent subcarriers of the one or more PT-RS groups. In certain such embodiments, unused power of the guard subcarriers configured to have zero power is used to boost power of non-zero power PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups.

[0043] In addition or in other embodiments, in block 510, method 500 modulates PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence. The predetermined PT-RS modulation sequence may be based on a pulse function or a Zadoff-Chu sequence, for example. Method 500 may also include cyclically extending the Zadoff-Chu sequence to a zero power guard subcarrier.

[0044] Figure 6 An exemplary architecture of a network system 600 according to various embodiments is shown. The following description is provided for an example system 600 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0045] like Figure 6As shown, system 600 includes UE 602 and UE 604. In this example, UE 602 and UE 604 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0046] In some embodiments, UE 602 and / or UE 604 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. 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., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0047] UE 602 and UE 604 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R) AN 616). In an embodiment, (R) AN 616 may be an NG RAN or SG RAN, an E-UTRAN, or a traditional RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to an (R) AN 616 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (R) AN 616 operating in an LTE or 4G system. UE 602 and UE 604 utilize connections (or channels) (shown as connection 606 and connection 608, respectively), each connection comprising a physical communication interface or layer (discussed in further detail below).

[0048] In this example, connection 606 and connection 608 are air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 602 and UE 604 may also directly exchange communication data via a ProSe interface 610. The ProSe interface 610 may alternatively be referred to as a side link (SL) interface 110, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0049] UE 604 is shown as being configured to access AP 612 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 614. Connection 614 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 612 would include Wireless Fidelity. router. In this example, AP 612 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 604, (R) AN 616, and AP 612 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 604 in RRC_CONNECTED configured by RAN node 618 or RAN node 620 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 604 using WLAN radio resources (e.g., connection 614) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 614. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0050] (R)AN 616 may include one or more nodes that implement connection 606 and connection 608, such as RAN node 618 and RAN node 620. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may 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" and the like may refer to RAN nodes (e.g., gNBs) operating in NR or SG systems, while the terms "E-UTRAN nodes" and the like may refer to RAN nodes (e.g., eNBs) operating in LTE or 4G systems 600. According to various embodiments, the RAN node 618 or the RAN node 620 may be implemented as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0051] In some embodiments, all or part of the RAN node 618 or RAN node 620 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 618 or RAN node 620); MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 618 or RAN node 620); or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes. This virtualization framework allows idle processor cores of the RAN node 618 or RAN node 620 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Figure 6In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CUs may be operated by a server (not shown) located in the (R)AN 616 or by a server pool in a manner similar to the CRAN / vBBUP. In addition or alternatively, the RAN node 618 or one or more of the RAN nodes 620 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to the UE 602 and the UE 604 and is connected to the SGC via an NG interface (discussed below). In a V2X scenario, the RAN node 618 or one or more of the RAN nodes 620 may be an RSU or act as an RSU.

[0052] The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communications. The RSU may 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 one example, the RSU is a computing device coupled to a radio frequency circuit located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz direct short range communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0053] The RAN node 618 and / or the RAN node 620 may terminate the air interface protocol and may be the first point of contact for the UE 602 and the UE 604. In some embodiments, the RAN node 618 and / or the RAN node 620 may perform various logical functions of the (R)AN 616, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0054] In an embodiment, UE 602 and UE 604 may be configured to communicate with each other or with RAN node 618 and / or RAN node 620 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0055] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 618 and / or RAN node 620 to UE 602 and UE 604, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the 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 includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0056] According to various embodiments, UE 602 and UE 604 and RAN node 618 and / or RAN node 620 communicate (e.g., transmit and receive) data through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0057] To operate in the unlicensed spectrum, UE 602 and UE 604 and RAN node 618 or RAN node 620 may operate using LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 602 and UE 604 and RAN node 618 or RAN node 620 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0058] LBT is a mechanism for equipment (e.g., UE 602 and UE 604, RAN node 618 or RAN node 620, etc.) to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band, and comparing the sensed RF energy to a predefined or configured threshold.

[0059] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 602, AP 612, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and YECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0060] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0061] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require the UE 602 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0062] The PDSCH carries user data and higher layer signaling to the UE 602 and UE 604. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform the UE 602 and UE 604 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to the UE 604 within the cell) may be performed at either the RAN node 618 or the RAN node 620 based on channel quality information fed back from either the UE 602 and UE 604. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UE 602 and UE 604.

[0063] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There can be four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8) in LTE.

[0064] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0065] The RAN node 618 or the RAN node 620 may be configured to communicate with each other via an interface 622. In an embodiment where the system 600 is an LTE system (e.g., when the CN 630 is an EPC), the interface 622 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful delivery of PDCP PDUs from the SeNB to the UE 602 in sequence for user data; information about PDCP PDUs that are not delivered to the UE 602; information about the current minimum expected buffer size at the Se NB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0066] In an embodiment where the system 600 is a SG or NR system (e.g., when the CN 630 is an SGC), the interface 622 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to the SGC, between a RAN node 618 (e.g., a gNB) and an eNB connected to the SGC, and / or between two eNBs connected to a 5GC (e.g., CN 630). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 602 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 618 or RAN nodes 620. The mobility support may include context transfer from the old (source) serving RAN node 618 to the new (target) serving RAN node 620; and control of the user plane tunnel between the old (source) serving RAN node 618 and the new (target) serving RAN node 620. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer 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 SCTP. SCTP may be on top of the IP layer and may provide 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 and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0067] (R)AN 616 is shown as being communicatively coupled to the core network—in this embodiment, communicatively coupled to CN 630. CN 630 may include one or more network elements 632 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 602 and UE 604) connected to CN 630 via (R)AN 616. The components of CN 630 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 630 may be referred to as a network slice, and a logical instance of a portion of CN 630 may be referred to as a network sub-slice. NFV architecture 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 (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0068] In general, the application server 634 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 634 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for the UE 602 and UE 604 via the EPC. The application server 634 may communicate with the CN 630 via the IP communication interface 636.

[0069] In an embodiment, CN 630 may be an SGC, and (R)AN 616 may be connected to CN 630 via an NG interface 624. In an embodiment, NG interface 624 may be divided into two parts: an NG user plane (NG-U) interface 626, which carries traffic data between RAN node 618 or RAN node 620 and UPF; and an S1 control plane (NG-C) interface 628, which is a signaling interface between RAN node 618 or RAN node 620 and AMF.

[0070] In an embodiment, CN 630 may be an SG CN, while in other embodiments, CN 630 may be an EPC. In the case where CN 630 is an EPC, (R) AN 616 may be connected to CN 630 via an S1 interface 624. In an embodiment, S1 interface 624 may be divided into two parts: an S1 user plane (S1-U) interface 626, which carries traffic data between RAN node 618 or RAN node 620 and S-GW; and an S1-MME interface 628, which is a signaling interface between RAN node 618 or RAN node 620 and MME.

[0071] Figure 7 An example of infrastructure equipment 700 according to various embodiments is shown. The infrastructure equipment 700 can be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any other element / device discussed herein. In other examples, the infrastructure equipment 700 can be implemented in or by a UE.

[0072] The infrastructure equipment 700 includes application circuits 702, baseband circuits 704, one or more radio front end modules 706 (RFEM), memory circuits 708, power management integrated circuits (shown as PMIC 710), power tee circuits 712, network controller circuits 714, network interface connectors 720, satellite positioning circuits 716, and user interface circuits 718. In some embodiments, the infrastructure equipment 700 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuits may be separately included in more than one device for CRAN, vBBU, or other similar implementations. The application circuits 702 include, for example, but not limited to, one or more processors (or processor cores), cache memory, and one or more low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, l 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of the application circuit 702 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure equipment 700. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0073] The processor of the application circuit 702 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 702 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 702 may include one or more Intel FPGAs. or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPSWarrior P-class processor; etc. In some embodiments, the infrastructure equipment 700 may not utilize the application circuit 702, and instead may include a dedicated processor / controller to process IP data received, for example, from the EPC or 5GC.

[0074] In some implementations, the application circuit 702 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs, such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such implementations, the circuits of the application circuit 702 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 702 may include a memory unit (e.g., an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a static memory (e.g., a static random access memory (SRAM), an anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a look-up table (LUT), etc. The baseband circuit 704 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0075] The user interface circuitry 718 may include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 700 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 700. The user interface may include, but is 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 touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0076] The radio front end module 706 may include a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 106 that combines both millimeter wave antennas and sub-millimeter waves.

[0077] The memory circuit 708 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM); and a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as “flash memory”), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 708 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0078] The PMIC 710 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 712 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 700 using a single cable.

[0079] The network controller circuit 714 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 700 via a network interface connector 720, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 714 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 714 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0080] The positioning circuit 716 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (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 Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 716 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 716 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 716 may also be part of or interact with the baseband circuit 704 and / or the radio front end module 706 to communicate with nodes and components of the positioning network. The positioning circuit 716 may also provide location data and / or time data to the application circuit 702, which may use the data to synchronize operations with various infrastructures, etc. Figure 7 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCix), PCI express (PCie), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0081] Figure 8 An example of a platform 800 according to various embodiments is shown. In an embodiment, the computer platform 800 may be suitable for use as a UE, an application server, and / or any other element / device discussed herein. The platform 800 may include any combination of components shown in the example. The components of the platform 800 may be implemented as an integrated circuit (IC), part of an IC, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 800, or implemented as components otherwise incorporated within the chassis of a larger system. Figure 8 The block diagram is intended to show a high-level view of the components of computer platform 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0082] Application circuit 802 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The processor (or core) of the application circuit 802 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the platform 800. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0083] The processor of the application circuit 802 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 embodiments, the application circuit 802 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0084] As an example, the processor of the application circuit 802 may include a processor based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU-class processors, or can be purchased from The processor of application circuit 802 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s AS-A9 processor, Snapdragon by Technologies, Inc.TM Processor, Texas Instruments, OpenMultimedia Applications Platform(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 implementations, the application circuit 802 can be part of a system on a chip (SoC), in which the application circuit 802 and other components are formed as a single integrated circuit or a single package, such as available from Edison Corporation TM or Galileo TM SoC board.

[0085] Additionally or alternatively, the application circuit 802 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 802 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 802 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), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in a lookup table (LUT), etc.

[0086] Baseband circuitry 804 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0087] The radio front end module 806 may include a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 806 that combines both millimeter wave antennas and sub-millimeter waves.

[0088] The memory circuit 808 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 808 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SD RAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 808 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 808 may be implemented as one or more of a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 808 may be an on-chip memory or register associated with the application circuit 802. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 808 may include one or more mass storage devices, which may include, among others, a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 800 may be combined with a computer system obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0089] Removable memory circuitry 814 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 800. 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, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0090] Platform 800 may also include interface circuitry (not shown) for connecting external devices to platform 800. External devices connected to platform 800 via the interface circuitry include sensor circuitry 210 and electromechanical components (shown as EMC 812), as well as removable memory devices coupled to removable memory 814.

[0091] Sensors 810 include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0092] EMC 812 includes the equipment, module or subsystem that purpose is to enable platform 800 to change its state, position and / or orientation or move or control mechanism or (sub) system. In addition, EMC 212 can be configured to generate message / signaling and send message / signaling to other components of platform 800 to indicate the current state of EMC 812. The example of EMC 812 includes one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, platform 800 is configured to operate one or more EMC812 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients. In some specific implementations, the interface circuit can connect platform 800 with positioning circuit 822. The positioning circuit 822 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) may include the United States' 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., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuit 822 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 822 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 822 may also be part of or interact with the baseband circuit 804 and / or the radio front-end module 806 to communicate with nodes and components of the positioning network. Positioning circuitry 822 may also provide position data and / or time data to application circuitry 802 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.

[0093] In some implementations, the interface circuit may connect the platform 800 to a near field communication circuit (shown as NFC circuit 820). The NFC circuit 820 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 820 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 800. The NFC circuit 820 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 820 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 820, or initiate data transfer between the NFC circuit 820 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) near the platform 800.

[0094] The driver circuit 824 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 800. The driver circuit 824 may include various drivers to allow other components of the platform 800 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 800. For example, the driver circuit 824 may include a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 800, a sensor driver for obtaining sensor readings of the sensor 810 and controlling and allowing access to the sensor 810, an EMC driver for obtaining actuator positions of the EMC 812 and / or controlling and allowing access to the EMC 812, 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.

[0095] A power management integrated circuit (shown as PMIC 816) (also referred to as a "power management circuit") can manage the power provided to various components of the platform 800. In particular, the PMIC 816 can control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 804. The PMIC 816 can typically be included when the platform 800 is capable of being powered by a battery 818, such as when the device is included in a UE.

[0096] In some embodiments, the PMIC 816 may control or otherwise be part of various power saving mechanisms of the platform 800. For example, if the platform 800 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 800 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 800 may transition to the RRC_Idle state, in which the platform is disconnected from the network and no operations such as channel quality feedback, handovers, etc. are performed. The platform 800 enters an extremely low power state and performs paging, in which the platform periodically wakes up to listen to the network and then powers off again. The platform 800 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0097] The battery 818 can provide power to the platform 800, but in some examples, the platform 800 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 818 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 818 can be a typical lead-acid car battery.

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

[0099] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 818. In some examples, the power block can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 800. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 818 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0100] The user interface circuit 826 includes various input / output (I / O) devices present in or connected to the platform 800, and includes one or more user interfaces designed to implement user interaction with the platform 800 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 800. The user interface circuit 826 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators such as binary status indicators (e.g., light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 800. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuit 210 may be used as an input device circuit (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuits (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuit including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0101] Although not shown, the components of platform 800 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCix, PCie, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0102] Fig. 9 Example components of a device 900 according to some embodiments are shown. In some embodiments, the device 900 may include at least an application circuit 902, a baseband circuit 904, a radio frequency (RF) circuit (shown as RF circuit 920), a front-end module (FEM) circuit (shown as FEM circuit 930), one or more antennas 932, and a power management circuit (PMC) (shown as PMC 934) coupled together as shown. The components of the exemplary device 900 may be included in a UE or a RAN node. In some embodiments, the device 900 may include fewer elements (for example, the RAN node may not utilize the application circuit 902, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 900 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (for example, the circuit may be separately included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0103] The application circuit 902 may include one or more application processors. For example, the application circuit 902 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 900. In some embodiments, the processor of the application circuit 902 may process IP data packets received from the EPC.

[0104] The baseband circuit 904 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 904 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 920 and generate baseband signals for the transmit signal path of the RF circuit 920. The baseband circuit 904 may interact with the application circuit 902 to generate and process baseband signals and control the operation of the RF circuit 920. For example, in some embodiments, the baseband circuit 904 may include a third generation (3G) baseband processor (3G baseband processor 906), a fourth generation (4G) baseband processor (4G baseband processor 908), a fifth generation (5G) baseband processor (5G baseband processor 910) or other baseband processors 912 of other existing generations, under development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 904 (e.g., one or more of the baseband processors) may handle various radio control functions that implement communication with one or more radio networks via the RF circuit 920. In other embodiments, some or all of the functions of the exemplary baseband processor may be included in a module stored in the memory 918 and executed via the central processing unit (CPU 914). The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 904 may include a fast Fourier transform (FFT), precoding, or constellation mapping / demapping function. In some embodiments, the encoding / decoding circuit of the baseband circuit 904 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0105] In some embodiments, the baseband circuit 904 may include a digital signal processor (DSP), such as one or more audio DSPs 916. The one or more audio DSPs 916 may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 904 and the application circuit 902 may be implemented together, such as on a system on a chip (SOC).

[0106] In some embodiments, the baseband circuit 904 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 904 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 904 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0107] RF circuit 920 may communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 920 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 920 may include a receive signal path, which may include circuitry for down-converting an RF signal received from FEM circuit 930 and providing a baseband signal to baseband circuit 904. RF circuit 920 may also include a transmit signal path, which may include circuitry for up-converting a baseband signal provided by baseband circuit 904 and providing an RF output signal for transmission to FEM circuit 930.

[0108] In some embodiments, the receive signal path of the RF circuit 920 may include a mixer circuit 922, an amplifier circuit 924, and a filter circuit 926. In some embodiments, the transmit signal path of the RF circuit 920 may include a filter circuit 926 and a mixer circuit 922. The RF circuit 920 may also include a synthesizer circuit 928 for synthesizing frequencies used by the mixer circuit 922 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 922 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 930 based on the synthesized frequency provided by the synthesizer circuit 928. The amplifier circuit 924 may be configured to amplify the down-converted signal, and the filter circuit 926 may be a low pass filter (LPF) or a 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 the baseband circuit 904 for further processing. In some embodiments, although this is not required, the output baseband signal may be a zero frequency baseband signal. In some embodiments, mixer circuit 922 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0109] In some embodiments, mixer circuit 922 of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 928 to generate an RF output signal for FEM circuit 930. The baseband signal may be provided by baseband circuit 904 and may be filtered by filter circuit 926.

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

[0111] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 920 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 904 may include a digital baseband interface to communicate with the RF circuit 920.

[0112] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0113] In some embodiments, synthesizer circuit 928 may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 928 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0114] Synthesizer circuit 928 may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 922 of RF circuit 920. In some embodiments, synthesizer circuit 928 may be a fractional-N / N+1 synthesizer.

[0115] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 904 or application circuitry 902 (such as an application processor) according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 902.

[0116] The synthesizer circuit 928 of the RF circuit 920 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency 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 N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle 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 cycle.

[0117] In some embodiments, the synthesizer circuit 928 can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 920 can include an IQ / polarity converter.

[0118] The FEM circuitry 930 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 932, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 920 for further processing. The FEM circuitry 930 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 920 for transmission by one or more of the one or more antennas 932. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 920, only in the FEM circuitry 930, or in both the RF circuitry 920 and the FEM circuitry 930.

[0119] In some embodiments, the FEM circuit 930 may include a TX / RX switch to switch between transmission mode and reception mode operation. The FEM circuit 930 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 930 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 920). The transmit signal path of the FEM circuit 930 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 920), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 932).

[0120] In some embodiments, the PMC 934 can manage the power provided to the baseband circuit 904. Specifically, the PMC 934 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 900 is capable of being powered by a battery, for example, when the device 900 is included in a UE, the PMC 934 can generally be included. The PMC 934 can improve power conversion efficiency while providing a desired specific implementation size and heat dissipation characteristics.

[0121] Fig. 9 PMC 934 is shown coupled only to baseband circuitry 904. However, in other embodiments, PMC 934 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 902, RF circuitry 920, or FEM circuitry 930) and perform similar power management operations for these components.

[0122] In some embodiments, the PMC 934 may control or otherwise be part of various power saving mechanisms of the device 900. For example, if the device 900 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 900 may be powered off for short time intervals, thereby saving power.

[0123] If there is no data traffic activity for an extended period of time, the device 900 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 900 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 900 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.

[0124] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0125] The processor of the application circuit 902 and the processor of the baseband circuit 904 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 904 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 902 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0126] Fig.10 An exemplary interface 1000 of a baseband circuit according to some embodiments is shown. As described above, Fig. 9 The baseband circuit 904 may include a 3G baseband processor 906, a 4G baseband processor 908, a 5G baseband processor 910, other baseband processors 912, a CPU 914, and a memory 918 used by the processor. As shown, each of these processors may include a corresponding memory interface 1002 to send data to / receive data from the memory 918.

[0127] The baseband circuit 904 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 1004 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 904), an application circuit interface 1006 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 904), and an application circuit interface 1007 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 904). Fig. 9 1008 (for example, an interface for sending / receiving data to / from the application circuit 902) and an RF circuit interface 1008 (for example, an interface for sending / receiving data to / from the application circuit 902). Fig. 9 an interface for sending / receiving data to / from a RF circuit 920), a wireless hardware connection interface 1010 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low power consumption), components and other communication components to send / receive data) and a power management interface 1012 (for example, an interface for sending / receiving power or control signals to / from the PMC 934).

[0128] Fig.11 1 is a block diagram illustrating a component 1100 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig.11 A diagrammatic representation of hardware resources 1102 is shown including one or more processors 1112 (or processor cores), one or more memory / storage devices 1118, and one or more communication resources 1120, each of which may be communicatively coupled via a bus 1122. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1104 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1102.

[0129] Processor 1112 (e.g., 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 digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1114 and processor 1116.

[0130] The memory / storage device 1118 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1118 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, solid-state storage, etc.

[0131] The communication resources 1120 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1106 or one or more databases 1108 via the network 1110. For example, the communication resources 1120 may include wired communication components (e.g., for coupling via a universal serial bus (USB)), cellular communication components, NFC components, Parts (e.g. Low power consumption), components and other communication components.

[0132] The instructions 1124 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1112 to perform any one or more of the methodologies discussed herein. The instructions 1124 may reside in whole or in part within at least one of the processor 1112 (e.g., within a cache memory of the processor), the memory / storage device 1118, or any suitable combination thereof. In addition, any portion of the instructions 1124 may be transmitted to the hardware resources 1102 from any combination of the peripheral device 1106 or the database 1108. Thus, the memory of the processor 1112, the memory / storage device 1118, the peripheral device 1106, and the database 1108 are examples of computer-readable and machine-readable media.

[0133] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the examples section below.

[0134] Examples

[0135] The following examples relate to additional embodiments.

[0136] Embodiment 1A is an apparatus for transmitting PT-RS for OFDM in a wireless communication system. The apparatus includes a processor and a memory. The memory stores instructions that, when executed by the processor, configure the apparatus to: determine adjacent subcarriers of one or more PT-RS groups in a resource allocation for PUSCH or PDSCH; encode data in a data subcarrier within the resource allocation for PUSCH or PDSCH for transmission by PUSCH or PDSCH; and encode a phase tracking reference signal within adjacent subcarriers of the one or more PT-RS groups.

[0137] Embodiment 2A includes an apparatus according to embodiment 1A, wherein the apparatus is configured for a UE or a gNB, and wherein the adjacent subcarriers of the one or more PT-RS groups include at least two PT-RS groups separated from each other by one or more data subcarriers in the data subcarriers.

[0138] Embodiment 3A includes the apparatus of embodiment 1A, wherein the instructions further configure the apparatus to configure guard subcarriers within adjacent subcarriers of the one or more PT-RS groups to prevent inter-carrier interference caused by PUSCH or PDSCH.

[0139] Embodiment 4A includes the apparatus of embodiment 3A, wherein the instructions further configure the apparatus to configure guard subcarriers with zero power at boundaries of adjacent subcarriers of the one or more PT-RS groups.

[0140] Embodiment 5A includes an apparatus according to embodiment 4A, wherein the instructions further configure the apparatus to use unused power of guard subcarriers configured to have zero power to increase the power of non-zero power PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups.

[0141] Embodiment 6A includes the apparatus of Embodiment 1A, wherein the instructions further configure the apparatus to modulate the PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence.

[0142] Embodiment 7A includes the apparatus of embodiment 6A, wherein the predetermined PT-RS modulation sequence is based on a pulse function or a Zadoff-Chu sequence.

[0143] Embodiment 8A includes the apparatus of embodiment 7A, wherein for the pulse function, the predetermined PT-RS modulation sequence comprises:

[0144] n=0,1,...,N-1,where Where N is the number of non-zero subcarriers in the PT-RS group.

[0145] Embodiment 9A includes the apparatus of embodiment 7A, wherein the instructions further configure the apparatus to cyclically extend the Zadoff-Chu sequence to the zero power guard subcarrier, wherein the predetermined PT-RS modulation sequence comprises:

[0146] s(n)=x q ({n+N 0}mod N ZC ), n=0,1,...,N-1,

[0147] Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers in the PT-RS group, and No determines the length of the cyclic extension.

[0148] Embodiment 10A includes an apparatus according to embodiment 1A, wherein determining the adjacent subcarriers of the one or more PT-RS groups in resource allocation includes determining the total number of adjacent subcarriers in the one or more PT-RS groups or the number of non-zero power subcarriers within the one or more PT-RS groups based on at least one of the following: RRC signal, DCI, cell ID, virtual cell ID, PT-RS port index, RNTI, symbol index, time slot index, subcarrier spacing, MCS, and the number of PRBs.

[0149] Embodiment 11A includes an apparatus according to embodiment 1A, wherein determining adjacent subcarriers of the one or more PT-RS groups in resource allocation includes determining a frequency offset of the PTRS group based on at least one of: an RRC signal, a DCI, a cell ID, a virtual cell ID, a PT-RS port index, an RNTI, a symbol index, a time slot index, a subcarrier spacing, an MCS, and the number of PRBs.

[0150] Embodiment 12A includes the apparatus of embodiment 1A, wherein adjacent subcarriers of the one or more PT-RS groups are determined in the resource allocation in response to determining that the MCS indicated by the DCI is above an MCS threshold.

[0151] Embodiment 13A includes the apparatus of embodiment 1A, wherein adjacent subcarriers of the one or more PT-RS groups are determined in the resource allocation in response to determining that the allocated bandwidth is above an allocated bandwidth threshold.

[0152] Embodiment 14A includes the apparatus of embodiment 1A, wherein the instructions further configure the apparatus to generate, at the UE, UE capability signaling for the base station, the UE capability signaling comprising at least one of an MCS threshold and an allocated bandwidth threshold.

[0153] Embodiment 15A includes an apparatus according to Embodiment 1A, wherein the instructions further configure the apparatus to use the PT-RS subcarriers within the PT-RS group for data channel transmission in response to determining that at least a subset of non-zero power PT-RS subcarriers within a particular PT-RS group among the one or more PT-RS groups are punctured due to a conflict with another downlink signal.

[0154] Embodiment 16A is a method for transmitting PT-RS for OFDM in a wireless communication system. The method includes determining adjacent subcarriers of one or more PT-RS groups in a resource allocation for PUSCH or PDSCH; transmitting data in a data subcarrier within the resource allocation for PUSCH or PDSCH; and transmitting a phase tracking reference signal within adjacent subcarriers of the one or more PT-RS groups.

[0155] Embodiment 17A includes the method according to embodiment 16A, further comprising configuring a guard subcarrier with zero power at a boundary of adjacent subcarriers of the one or more PT-RS groups.

[0156] Embodiment 18A includes the method according to embodiment 17A, further comprising using unused power of guard subcarriers configured to have zero power to boost the power of non-zero power PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups.

[0157] Embodiment 19A includes the method according to embodiment 16A, further comprising modulating the PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence.

[0158] Embodiment 20A includes the method according to embodiment 19A, wherein the predetermined PT-RS modulation sequence is based on a pulse function or a Zadoff-Chu sequence.

[0159] Embodiment 21A includes the method according to embodiment 20A, further comprising cyclically extending the Zadoff-Chu sequence to the zero power guard subcarriers.

[0160] Embodiment 22A includes the method according to embodiment 16A, and also includes using the PT-RS subcarriers within the PT-RS group for data channel transmission in response to determining that at least a subset of non-zero power PT-RS subcarriers within a specific PT-RS group among the one or more PT-RS groups are deleted due to a conflict with another downlink signal.

[0161] Embodiment 23A is a non-transitory computer-readable storage medium. The computer-readable storage medium includes instructions that, when executed by a processor, cause the processor to: determine adjacent subcarriers of one or more PT-RS groups in a resource allocation for a PUSCH or a PDSCH; encode data in a data subcarrier within the resource allocation for the PUSCH or the PDSCH; and encode a phase tracking reference signal within adjacent subcarriers of the one or more PT-RS groups.

[0162] Embodiment 24A includes a computer-readable storage medium according to embodiment 23A, wherein the instructions further configure the processor to: configure protection subcarriers with zero power at the boundaries of adjacent subcarriers of the one or more PT-RS groups; and use unused power of the protection subcarriers configured with zero power to increase the power of non-zero power PT-RS subcarriers within the adjacent subcarriers of the one or more PT-RS groups.

[0163] Embodiment 25A includes a computer-readable storage medium according to embodiment 23A, wherein the instructions further configure the processor to modulate the PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence based on an impulse function or a Zadoff-Chu sequence.

[0164] Embodiment 1B may include a method for transmitting PT-RS using one or more groups of adjacent subcarriers within a resource allocation of OFDM, wherein the method includes: indicating a PDSCH or PUSCH allocation to a UE or a PUSCH from a UE, wherein one or more PT-RS groups include two or more adjacent subcarriers; determining at the UE the number of PT-RS groups, the number of subcarriers in the PT-RS groups, and the location of the PT-RS groups within the resource allocation based on parameters provided to the UE from a serving cell; modulating all or a subset of the PT-RS subcarriers in the group according to a predetermined sequence; or receiving or transmitting a PDSCH or PUSCH with PT-RS according to a configuration.

[0165] Embodiment 2B may include a method according to embodiment 1B or some other embodiments herein, wherein DCI bits are used to explicitly indicate the use of PT-RS groups.

[0166] Embodiment 3B may include a method according to embodiment 1B or some other embodiments herein, wherein the use of PT-RS groups is implicitly indicated by using existing DCI bits.

[0167] Embodiment 4B may include a method according to embodiment 3B or some other embodiments herein, wherein the existing field is an MCS index, wherein PT-RS group transmission is used when the used MCS is above a certain threshold and a conventional Rel-15 PT-RS is used when the MCS is below the threshold.

[0168] Embodiment 5B may include a method according to embodiment 3B or some other embodiments herein, wherein the existing field is the number of allocated PRBs in the resource allocation indication, wherein PT-RS group transmission is used when the resource allocation size used is above a certain threshold, and conventional Rel-15 PT-RS is used when the resource allocation size is below the threshold.

[0169] Embodiment 6B may include a method according to embodiment 1B or some other embodiments herein, wherein a subset of subcarriers not used for PT-RS transmission (guard subcarriers or zero-power PT-RS) is located on subcarriers on the boundary of subcarriers allocated to the PT-RS group.

[0170] Embodiment 7B may include a method according to embodiment 6B or some other embodiments herein, wherein power from unused subcarriers is utilized to increase the power on used subcarriers of the PT-RS group, and the power ratio of the used PT-RS subcarriers to the power of the DM-RS or the power of the PDSCH is known to the UE and the serving cell.

[0171] Embodiment 8B may include a method according to embodiment 1B or some other embodiments herein, wherein the PT-RS groups are uniformly distributed in the frequency domain.

[0172] Embodiment 9B may include a method as described in embodiment 1B or some other embodiments herein, wherein a PT-RS group is present in each OFDM symbol of the indicated resource allocation.

[0173] Embodiment 10B may include a method according to embodiment 1B or some other embodiments herein, wherein the PT-RS subcarrier is modulated with a pulse function according to the following equation.

[0174] n=0,1,...,N-1,where

[0175] Where N is the number of subcarriers in the PT-RS group.

[0176] Embodiment 11B may include a method according to embodiment 1B or some other embodiments herein, wherein the used PT-RS subcarriers are modulated with a Zadoff-Chu sequence.

[0177] Embodiment 12B may include a method according to embodiment 1B or some other embodiments herein, wherein the used PT-RS subcarriers are modulated with a cyclically extended Zadoff-Chu sequence according to the following equation:

[0178] s(n)=x q ({n+N 0}mod N ZC ), n=0,1,...,N-1,

[0179] Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers within the PT-RS group, and No and N-Nzc determine the length of the low-frequency and high-frequency subcarriers of the PT-RS group that are cyclically extended.

[0180] Embodiment 13B may include a method according to embodiments 11B and 12B or some other embodiments herein, wherein the root of the Zadoff-Chu sequence may depend on at least one of the following parameters: such as PT-RS group index, OFDM symbol, time slot index, cell ID, RRC configuration ID, RNTI.

[0181] Embodiment 14B may include a method according to embodiments 10B and 11B or some other embodiments herein, wherein all PT-RS subcarriers in a PT-RS group may be additionally modulated by a DM-RS signal transmitted on one of the subcarriers occupied by the PT-RS group (e.g., the first subcarrier).

[0182] Embodiment 15B may include a method according to embodiments 4B and 5B or some other embodiments herein, wherein the UE signals the MCS threshold and / or allocated bandwidth threshold to the gNB as part of UE capability signaling.

[0183] Embodiment 16B may include a method according to embodiment 1B or some other embodiments herein, wherein non-zero power PT-RS subcarriers within a PT-RS group are truncated due to conflicts with other downlink signals (e.g., CSI-RS), so that subcarriers used as PT-RS subcarriers within the same PT-RS group can be used for data channel transmission.

[0184] Embodiment 17B may include a method according to embodiment 1B or some other embodiments herein, wherein at least one of the following parameters is used to determine parameters of the PT-RS group such as the number of subcarriers used: such as cell ID, virtual cell ID, PT-RS port index, RNTI, symbol / slot index, subcarrier spacing, MCS, number of PRBs.

[0185] Embodiment 18B may include a method according to embodiment 1B or some other embodiments herein, wherein parameters of the PT-RS group such as the frequency offset of the PT-RS group and / or the number of PT-RS groups may be predefined or configured by higher layer signaling (e.g., RRC) or DCI, or determined by at least one of the following parameters: cell ID, virtual cell ID, PT-RS port index, RNTI, symbol / slot index.

[0186] Embodiment 19B may include a method comprising: within a resource allocation for a PUSCH or a PDSCH, encoding a PT-RS in a PT-RS group comprising a plurality of adjacent subcarriers; and within a resource allocation for the PUSCH or the PDSCH, encoding data for transmission by the PUSCH or the PDSCH.

[0187] Embodiment 20B may include a method according to embodiment 19B or some other embodiments herein, wherein the encoding includes providing a subcarrier within a PT-RS group as a zero-power protection subcarrier.

[0188] Embodiment 21B may include a method according to embodiment 20B or some other embodiments herein, wherein the encoding includes increasing the power of non-zero power subcarriers within the PT-RS group.

[0189] Embodiment 22B may include the method described in embodiment 19B or some other embodiments of the present invention, and further include: determining the number of non-zero power subcarriers within a PT-RS group based on: RRC signal; DCI; cell identifier; virtual cell identifier; PT-RS port index; RNTI; symbol index; time slot index; subcarrier spacing; MCS; or the number of PRBs.

[0190] Embodiment 23B may include the method described in embodiment 19B or some other embodiments herein, further including: determining the frequency offset of the PT-RS group based on: RRC signal; DCI; cell identifier; virtual cell identifier; PT-RS port index; RNTI; symbol index; time slot index; subcarrier spacing; MCS; or the number of PRBs.

[0191] Embodiment 24B may include a method according to Embodiment 19B or some other embodiments herein, further comprising encoding PT-RSs in a plurality of PT-RS groups.

[0192] Embodiment 25B may include the method described in embodiment 24B or some other embodiments herein, further including: determining the number of multiple PT-RS groups based on: RRC signal; DCI; cell identifier; virtual cell identifier; PT-RS port index; RNTI; symbol index; time slot index; subcarrier spacing; MCS; or the number of PRBs.

[0193] Embodiment 26B may include a method according to embodiment 19B or some other embodiments herein, wherein one or more subcarriers of the PT-RS group are modulated with a pulse function according to the following equation:

[0194] n=0,1,...,N-1,where

[0195] Where N is the number of subcarriers in the PT-RS group.

[0196] Embodiment 27B may include a method according to embodiment 26B or some other embodiments herein, wherein the one or more subcarriers include all non-zero subcarriers of the PT-RS group, and N is the number of non-zero subcarriers.

[0197] Embodiment 28B may include a method according to embodiment 19B or some other embodiments herein, wherein one or more PT-RS subcarriers of the PT-RS group are modulated with a Zadoff-Chu sequence.

[0198] Embodiment 29B may include a method according to embodiment 19B or some other embodiments herein, wherein one or more PT-RS subcarriers of the PT-RS group are modulated with a cyclically extended Zadoff-Chu sequence according to the following equation:

[0199] s(n)=x q ({n+N 0}mod N ZC ), n=0,1,...,N-1,

[0200] Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers within the PT-RS group, and No and N-Nzc determine the length of the low-frequency and high-frequency subcarriers of the PT-RS group that are cyclically extended.

[0201] Embodiment 30B may include a method according to embodiment 28B or 29B or some other embodiments herein, wherein the root of the Zadoff-Chu sequence may depend on a PT-RS group index, an OFDM symbol, a time slot index, a cell ID, an RRC configuration ID, or an RNTI.

[0202] Embodiment 31B may include a method according to embodiment 28B or 29B or some other embodiments herein, wherein all PT-RS subcarriers in a PT-RS group may be additionally modulated by a DM-RS signal transmitted on a subcarrier occupied by the PT-RS group (e.g., the first subcarrier).

[0203] Embodiment 32B may include a method according to embodiment 19B or some other embodiments herein, wherein non-zero power PT-RS subcarriers within a PT-RS group are truncated due to conflicts with other downlink signals (e.g., CSI-RS), and one or more of the subcarriers used as PT-RS subcarriers within the same PT-RS group are used for data channel transmission.

[0204] Embodiment 1C may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0205] Embodiment 2C may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0206] Embodiment 3C may include a device comprising logic components, modules, or circuits for performing one or more elements of the methods described in or related to any of the above embodiments or any other methods or processes described herein.

[0207] Embodiment 4C may include any of the methods, techniques or processes or parts or components thereof described in or related to the above embodiments.

[0208] Embodiment 5C may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, process, or portion thereof described in or related to any one of the above embodiments.

[0209] Embodiment 6C may include a signal or a portion or component thereof as described in or related to any of the above embodiments.

[0210] Embodiment 7C may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in or related to any of the above embodiments, or as otherwise described in the present disclosure.

[0211] Embodiment 8C may include a signal encoded with data or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in this disclosure.

[0212] Embodiment 9C may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in or related to any of the above embodiments, or described in other ways in the present disclosure.

[0213] Embodiment 10C 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, described in or related to any of the above embodiments.

[0214] Embodiment 11C 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, described in or related to any one of the above embodiments.

[0215] Embodiment 12C may include signals in a wireless network as shown and described herein.

[0216] Embodiment 13C may include a method of communicating in a wireless network as shown and described herein.

[0217] Embodiment 14C may include a system for providing wireless communications as shown and described herein.

[0218] Embodiment 15C may include an apparatus for providing wireless communications as shown and described herein.

[0219] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

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

[0221] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters / attributes / aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters / attributes / aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters / attributes / aspects, etc. may be combined with or substituted for parameters / attributes, etc. of another embodiment.

[0222] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A device for transmitting a phase tracking reference signal PT-RS for orthogonal frequency division multiplexing (OFDM) in a wireless communication system, the device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: determining adjacent subcarriers of one or more PT-RS groups in a resource allocation for a physical uplink shared channel (PUSCH), wherein the adjacent subcarriers of the one or more PT-RS groups are determined in the resource allocation in response to determining that a modulation and coding scheme (MCS) indicated by downlink control information (DCI) is above an MCS threshold; encoding data in a data subcarrier within the resource allocation for the PUSCH for transmission by the PUSCH; modulating PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence, wherein the predetermined PT-RS modulation sequence is based on an impulse function or a Zadoff-Chu sequence; cyclically extending the Zadoff-Chu sequence to zero-power protection subcarriers; and encoding phase tracking reference signals within adjacent subcarriers of the one or more PT-RS groups, The predetermined PT-RS modulation sequence includes: Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers in the PT-RS group, and No determines the length of the cyclic extension.

2. The apparatus according to claim 1, wherein the apparatus is configured for a user equipment UE or a g Node B (gNB), and wherein the adjacent subcarriers of the one or more PT-RS groups include at least two PT-RS groups separated from each other by one or more data subcarriers among the data subcarriers.

3. The apparatus of claim 1, wherein the instructions further configure the apparatus to configure guard subcarriers within adjacent subcarriers of the one or more PT-RS groups to prevent inter-carrier interference caused by the PUSCH. 4 . The apparatus of claim 3 , wherein the instructions further configure the apparatus to configure the guard subcarriers with zero power at boundaries of adjacent subcarriers of the one or more PT-RS groups.

5. The apparatus of claim 4, wherein the instructions further configure the apparatus to use unused power of the guard subcarriers configured to have zero power to boost power of non-zero power PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups.

6. The apparatus of claim 1 , wherein for the pulse function, the predetermined PT-RS modulation sequence comprises: in Where N is the number of non-zero subcarriers in the PT-RS group.

7. An apparatus according to claim 1, wherein determining the adjacent subcarriers of the one or more PT-RS groups in the resource allocation includes determining the total number of the adjacent subcarriers in the one or more PT-RS groups or the number of non-zero power subcarriers within the one or more PT-RS groups based on at least one of the following: a radio resource control (RRC) signal, a DCI, a cell identifier (ID), a virtual cell ID, a PT-RS port index, a radio network temporary identifier (RNTI), a symbol index, a time slot index, a subcarrier spacing, the MCS, and the number of physical resource blocks (PRBs).

8. The apparatus of claim 1, wherein determining adjacent subcarriers of the one or more PT-RS groups in the resource allocation comprises determining a frequency offset of the PTRS group based on at least one of: a radio resource control (RRC) signal, a DCI, a cell identifier (ID), a virtual cell ID, a PT-RS port index, a radio network temporary identifier (RNTI), a symbol index, a time slot index, a subcarrier spacing, the MCS, and a number of physical resource blocks (PRBs).

9. The apparatus of claim 1, wherein adjacent subcarriers of the one or more PT-RS groups are determined in the resource allocation in response to determining that an allocated bandwidth is above an allocated bandwidth threshold.

10. The apparatus of claim 1, wherein the instructions further configure the apparatus to generate, at a user equipment (UE), UE capability signaling for a base station, the UE capability signaling comprising at least one of a modulation and coding scheme (MCS) threshold and an allocated bandwidth threshold.

11. The apparatus of claim 1 , wherein the instructions further configure the apparatus to, in response to determining that at least a subset of non-zero-power PT-RS subcarriers within a particular PT-RS group among the one or more PT-RS groups is deleted due to a conflict with another downlink signal, use the PT-RS subcarriers within the PT-RS group for data channel transmission.

12. A method for transmitting a phase tracking reference signal PT-RS for orthogonal frequency division multiplexing (OFDM) in a wireless communication system, the method comprising: determining adjacent subcarriers of one or more PT-RS groups in a resource allocation for a physical uplink shared channel (PUSCH), wherein the adjacent subcarriers of the one or more PT-RS groups are determined in the resource allocation in response to determining that a modulation and coding scheme (MCS) indicated by downlink control information (DCI) is above an MCS threshold; modulating PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence, wherein the predetermined PT-RS modulation sequence is based on an impulse function or a Zadoff-Chu sequence; cyclically extending the Zadoff-Chu sequence to a zero power protection subcarrier; transmitting data in a data subcarrier within the resource allocation for the PUSCH; as well as transmitting a phase tracking reference signal within adjacent subcarriers of the one or more PT-RS groups, The predetermined PT-RS modulation sequence includes: Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers in the PT-RS group, and No determines the length of the cyclic extension. 13 . The method according to claim 12 , further comprising configuring a guard subcarrier with zero power at a boundary of adjacent subcarriers of the one or more PT-RS groups.

14. The method of claim 13, further comprising using unused power of the guard subcarriers configured to have zero power to boost power of non-zero power PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups.

15. The method of claim 12, further comprising modulating PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence.

16. The method of claim 12, further comprising, in response to determining that at least a subset of non-zero power PT-RS subcarriers within a specific PT-RS group among the one or more PT-RS groups is deleted due to a conflict with another downlink signal, using the PT-RS subcarriers within the PT-RS group for data channel transmission.

17. A computer-readable storage medium comprising instructions which, when executed by a processor, cause the processor to: determining adjacent subcarriers of one or more PT-RS groups in a resource allocation for a physical uplink shared channel (PUSCH), wherein the adjacent subcarriers of the one or more PT-RS groups are determined in the resource allocation in response to determining that a modulation and coding scheme (MCS) indicated by downlink control information (DCI) is above an MCS threshold; modulating PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups with a predetermined PT-RS modulation sequence based on an impulse function or a Zadoff-Chu sequence; encoding data in data subcarriers within the resource allocation for the PUSCH; and encoding phase tracking reference signals within adjacent subcarriers of the one or more PT-RS groups, The predetermined PT-RS modulation sequence includes: Where q is the root of the Zadoff-Chu sequence, Nzc is the length of the Zadoff-Chu sequence, N is the number of non-zero subcarriers in the PT-RS group, and No determines the length of the cyclic extension.

18. The computer-readable storage medium of claim 17, wherein the instructions further configure the processor to: configuring a guard subcarrier with zero power at a boundary of adjacent subcarriers of the one or more PT-RS groups; and Unused power of the guard subcarriers configured to have zero power is used to boost power of non-zero power PT-RS subcarriers within adjacent subcarriers of the one or more PT-RS groups.