Method for dynamic uplink TX DC subcarrier position reporting

Abstract

A method for wireless communication by a user equipment (UE) is described. Reporting UL Tx DC subcarrier position information may include decoding a radio resource control (RRC) message received from a base station. The RRC message may include a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information. A change associated with at least one previous UL Tx DC subcarrier position may be determined to have occurred, thereby creating at least one new UL Tx DC subcarrier position. In response to determining the change, a medium access control (MAC) control element (MAC CE) may be encoded for transmission to the base station. The MAC CE may include information corresponding to the at least one new UL Tx DC subcarrier position.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including transmit (Tx) direct current (DC) subcarrier position reporting. Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally 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 generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly 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 nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0003] 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 RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0004] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency Range 1 (FR1) includes frequency bands below 6 GHz, some of which may be used by previous standards but can potentially be expanded to cover potential new spectrum products from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) includes frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 have a shorter range but higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] 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.

[0006] Figure 1 A communication flow diagram associated with current signaling of Tx DC subcarrier position reporting is shown.

[0007] Figure 2A An example of the shortcomings of current Tx DC subcarrier position reporting is shown.

[0008] Figure 2B An example of the shortcomings of current Tx DC subcarrier position reporting is shown.

[0009] Figure 2C An example of the shortcomings of current Tx DC subcarrier position reporting is shown.

[0010] Figure 3 An exemplary embodiment of information that may be included in the Tx DC Subcarrier Position Report MAC CE is shown.

[0011] Figure 4 An exemplary embodiment of information that may be included in the Tx DC Subcarrier Position Report MAC CE is shown.

[0012] Figure 5 Exemplary embodiments of information that may be included in a reduced size MAC CE used in conjunction with an RRC Complete message for reporting Tx DC location information are shown.

[0013] Figure 6 A flow chart of a method for reporting UL Tx DC subcarrier position information is shown.

[0014] Figure 7 A flow chart of a method for reporting UL Tx DC subcarrier position information is shown.

[0015] Figure 8A flow chart of a method for reporting UL Tx DC subcarrier position information is shown.

[0016] Fig. 9 A system according to one embodiment is shown.

[0017] Fig.10 Infrastructure equipment according to one embodiment is shown.

[0018] Fig.11 A platform according to one embodiment is shown.

[0019] Fig.12 An apparatus according to one embodiment is shown.

[0020] Fig.13 An exemplary interface according to one embodiment is shown.

[0021] Fig.14 Components according to one embodiment are shown. DETAILED DESCRIPTION

[0022] Release 15 of 3GPP NR specifies that when the UE is transmitting in an uplink (UL) channel, the UE may report the current transmit (Tx) direct current (DC) subcarrier position to the network (NW). Such position information may help the NW process zero DC physical resource blocks (PRBs) for efficient demodulation and decoding. Specifically, the DC subcarrier position may include the center of the relevant frequency band and may allow the NW to know the position in the spectrum where the UE is allowed to transmit. The UE may report the current Tx DC subcarrier position for a cell group, where each of these carriers for which the UE is configured is in the cell group. In addition, with respect to each of the carriers in the carrier, the UE reports for each BWP in the configured bandwidth part (BWP).

[0023] The following include information elements (IEs) associated with the principles described herein:

[0024]

[0025]

[0026] Figure 1 A communication flow diagram associated with current signaling of Tx DC subcarrier position reporting is shown. As shown, UE 102 may be in connected mode relative to base station 104 (e.g., gNB) (shown by block 106). As shown by arrow 108, base station 104 may configure UE 102 to report Tx DC subcarrier position via radio resource control (RRC) configuration. Finally, as shown by arrow 110, UE 102 reports Tx DC subcarrier position via radio RRC configuration.

[0027] It is worth noting that the current signaling associated with Tx DC subcarrier position reporting has various disadvantages. Specifically, the UE only reports the Tx DC subcarrier position information as a response to an RRC configuration with a DC position request of the base station, which leads to a number of additional problems. First, the UE may not report the Tx DC subcarrier position automatically (i.e., only when triggered by the NW).

[0028] Second, depending on the given configuration of the UE, the Tx DC subcarrier position may change when there is an addition / removal of carriers, in response to activation / deactivation of carriers, or in response to a BWP switch in any active carrier. In addition, in the case of intra-band contiguous or non-contiguous carrier aggregation (CA) of multiple carriers handled by the UE using Tx chain hardware (HW) sharing, the switching of BWP in any of the carriers may result in a change in the UL Tx DC subcarrier position at the UE.

[0029] Third, the UE may not inform the NW of changes in such information unless the NW explicitly requests it via RRC messaging. Therefore, the NW may not always be aware of the Tx DC subcarrier position change, which may result in reduced UL Tx decoding performance at the NW, leading to inefficient use of resources. In addition, BWP switching may be done by the NW without RRC signaling (i.e., based on DCI), which may also result in changes in the Tx DC subcarrier position change.

[0030] FIG. 2A to FIG. 2C An example of the shortcomings of the current Tx DC subcarrier position reporting is shown. As shown in the figure, FIG. 2A to FIG. 2C Each of includes bit 2 218 having four BWPs (ie, BWP 202 to BWP 208) and carrier B 220 having four BWPs (ie, BWP 210 to BWP 216).

[0031] like Figure 2A As shown, Bit2 218 and Carrier B 220 comprise intra-band contiguous carrier aggregation (CA), where only Bit2 218 is activated (ie, Carrier B 220 is not currently activated). Additionally, both the active Tx DC position and the reported Tx DC position are the same (ie, within BWP 202).

[0032] like Figure 2BAs shown, at some point in time, carrier B 220 may also be activated. In this case, the active Tx DC position may be associated with a particular BWP for carrier B 220. As shown, the active Tx DC position associated with carrier B 220 is within BWP 214. However, despite having a current Tx DC position associated with bit 2 218 (i.e., within BWP 202), the NW may not be informed of this. It is noteworthy that the NW may simultaneously activate carrier B 220 associated with a given UE and still be unaware of the active Tx DC position associated with that carrier, because the activation may be performed by a different layer of the NW than the layer associated with receiving the Tx DC position report. For example, carrier activation may occur via downlink control information (DCI), while the Tx DC position report is performed via RRC. While some NWs may be configured to share information between various layers, other NWs may not be so.

[0033] like Figure 2C As shown, the UE may share UL Tx HW resources (e.g., for using wideband UL for both carriers A and B and a single PLL for Tx), which may result in the Tx DC carrier being shifted. Specifically, Figure 2C A wideband UL Tx 222 is shown spanning bit 2 218 and carrier B 220. In such a case, the NW may incorrectly assume different UL TxDC subcarrier locations for one or more carriers. More specifically, as Figure 2C As shown, the NW may expect the Tx DC position to be at a lower frequency within BWP 208 (as represented by arrow 224) and / or a lower frequency within BWP 210 (as represented by arrow 226) when the actual Tx DC subcarrier position may be at a higher frequency within BWP 208 (as represented by arrow 228).

[0034] Therefore, based on a combination of at least one or more of the following, RRC-based signaling may not be effective in conveying UL Tx DC subcarrier position information to the NW: 1. the location of the UL Tx DC may change based on the active configuration of the BWP of the activated carrier; 2. the location of the UL Tx DC may change based on the activation and deactivation of the carrier; and 3. the active BWP information is not always available via RRC.

[0035] One possible option to improve the current signaling may be to report the Tx DC subcarrier position information of all possible DC positions based on different BWP configurations of the active BWP. However, when there are 2 carriers with 4 BWP positions, there are at least 16 combinations in which the UE may report the UL Tx DC subcarrier position to the NW. Therefore, the signaling overhead may be prohibitively high because the combinations proliferate as the number of carriers increases (e.g., in the case of 3 carriers, there may be at least 64 combinations as a minimum).

[0036] Alternatively, this article provides three other detailed solutions. In the first detailed solution, the UE can use the medium access control (MAC) control element (MAC CE) to trigger the UL Tx DC subcarrier position report. Specifically, via RRC messaging, the NW can configure the UE to dynamically report the UL Tx DC subcarrier position information. In this way, the UE can know that the NW supports decoding the MAC CE.

[0037] The Tx DC subcarrier position report may allow the UE to report whenever there is a change in the UL Tx DC subcarrier position in any active carrier. For example, such a change may be in response to a switch of the BWP via RRC (or via DCI), due to a transition to an initial downlink (DL) BWP in time division duplex (TDD), and so on. It is worth noting that the NR MAC for the cell group may trigger the MAC CE. The triggering of the MAC CE may also reuse the logic of other MAC CE triggers, such as the buffer status report (BSR). Similarly, the MAC may reuse actions related to the triggering of the MAC CE. In addition, the DC position MAC CE may have a lower priority than the secondary cell (SCell) BFR MAC CE. As a sub-option associated with the first detailed solution, a timer may be used to delay the transmission of the MAC CE.

[0038] The MAC CE may contain at least the Tx DC subcarrier position for each of the carriers in the current BWP configuration. It should be noted that the MAC CE includes the DC position of the currently active BWP in all carriers in which the UE is assumed to be operating. When there is a BWP switch or a carrier is activated / deactivated, another MAC CE may be triggered if it results in a change in the Tx DC subcarrier position for any of the active carriers based on the internal implementation of the UE. As an option, more information related to this may also be sent as an option for each of the BWPs in the case of active carriers (e.g., 7.5kHz shift).

[0039] In another option, the MAC CE may be limited to the Tx DC subcarrier position of the current active BWP of the active carrier or the Tx DC subcarrier position of all configured BWPs in the configured BWP of the active carrier. When sending the Tx DC subcarrier position of all configured BWPs in the configured BWP of the active carrier, the UE may not have to trigger another MAC CE for BWP switching in the carrier if the Tx DC subcarrier position may not change, while the MAC CE may be large. The advantage of limiting the reporting of the Tx DC subcarrier position of the active BWP is to keep the MAC CE content concise and relevant to the current situation. However, doing so may also run the risk of triggering the MAC CE more frequently.

[0040] In another option, the UE may trigger UL Tx DC subcarrier position reporting with MAC CE for both the primary cell group (MCG) and the secondary cell group (SCG). The MAC CE may also include the Tx DC subcarrier position of each carrier from the other cell group if configured (i.e., when there is a change in the Tx DC subcarrier position of any carrier in the other cell group). This option may also be applicable to LTE-NR dual connectivity. For example, when the UE is in DC with LTE and NR, where LTE and NR form a continuous frequency band (i.e., intra-band continuous DC combination).

[0041] Furthermore, the UE may trigger a MAC CE on the MCG, and the primary cell (PCell) in the MCG may transmit such information to the SCG.This solution may be particularly useful in the in-band EN_DC case where the PCell and the primary SGC cell (PSCell) are typically co-located.

[0042] In contrast, the UE may be restricted to triggering MAC CE in the NR cell group (i.e., regardless of where the NR is located in the MCG or SCG). It is worth noting that this option does not require MCG-SCG coordination.

[0043] The UL Tx DC subcarrier location information MAC CE may also provide the location information of the supplementary UL (SUL) BWP of the same serving cell. The UE may provide the Tx DC subcarrier location of both the normal UL and SUL BWP of the active BWP in the active carrier. In addition, if either the normal UL (NUL) or SUL Tx DC subcarrier location information changes, the MAC CE may be triggered.

[0044] In addition, MAC CE signaling can be self-completion signaling or incremental-based signaling. In self-completion signaling, the UE can report UL Tx DC subcarrier location information using MAC CE, which can contain location information of all serving cells. In this way, the NW can have all relevant location information about the serving cells from this single MAC CE.

[0045] In delta-based signaling, the UE may only provide location information of serving cells (and corresponding BWPs) where this information has changed compared to the previous MAC CE transmission. If information for a specific serving cell does not exist, the NW may expect that the Tx DC subcarrier location information has not changed from the previous information transmitted by the UE.

[0046] Self-contained signaling can be beneficial because the UE does not have to remember previously provided information and the NW does not have to save the configuration or transmit the configuration to other network nodes. In contrast, delta-based signaling has the advantage of being based on the compact nature of associated MAC CE signaling.

[0047] Figure 3 An exemplary embodiment 300 of information that may be included in a MAC CE as discussed herein when a BWP ID is included is shown. In contrast, Figure 4 An example embodiment 400 of information that may be included in a MAC CE discussed herein when a BWP ID is not included is shown.

[0048] The second detailed solution involves dynamic signaling using MAC and semi-static signaling using RRC. The second detailed solution can reduce the content of MAC CE by having the UE pre-provide multiple combinations of Tx DC subcarrier position information as part of the RRC reconfiguration complete message. The MAC CE can then refer to one of the provided combinations as part of the dynamic update of the TxDC subcarrier position.

[0049] As part of any RRC reconfiguration message where the carrier configuration or BWP configuration changes, the UE may provide the NW with combinations of Tx DC subcarrier positions that are feasible for different combinations of configured BWP / carriers. The Tx DC subcarrier position may be a value of an entry, where each entry has DC position information for each BWP / SUL BWP for each carrier. The MAC CE then references the entry ID, where the size of the MAC CE is significantly reduced. Thus, the size of the dynamic update is compact.

[0050] As part of the RRC reconfiguration complete message, the UE may provide an information element (IE) UplinkTxDirectConfiguration comprising the following: A list of Tx DC subcarrier positions for each configured BWP in each configured serving cell in the configured BWP. Each part of this list is a representation of the IE UplinkTxDirectCurrentList (from slider 3). The UE may attempt to provide a comprehensive list of such combinations and, in the MAC CE, only reference the combination that is being used at the UE. For design purposes, if it is assumed that the list UplinkTxDirectCurrentList is 512 entries, the MAC CE may reference an index from one of these entries. For example, the last row of the following IE may be added to the IE included above.

[0051]

[0052] Figure 5 An exemplary embodiment 500 is shown of information that may be included in a reduced size MAC CE used in conjunction with an RRC Complete message for reporting Tx DC location information, as further described with respect to the second detailed solution.

[0053] The third detailed solution involves dynamic signaling using RRC. Specifically, the third detailed solution uses only RRC messaging (i.e., no MAC CE) to provide Tx DC location information. Tx DC location information for all carriers and corresponding BWPs in UL / SUL of these carriers can be provided via RRC messaging without any request from the network.

[0054] In such an implementation, the UE may trigger an RRC message whenever there is a change in the Tx DC position in any of the carriers. In one example, the UE may use a UE Assistance Information (UAI) RRC message. In another example, the UE may create a new RRC message just for the purpose of Tx DC position reporting.

[0055] Furthermore, the first option of the third detailed solution may include a UE RRC message including a snapshot of all DC Tx positions of all carriers / BWPs in the RRC message. Thus, such a message may provide a complete picture for the NW without referring to any other information.

[0056] In the second option of the third detailed solution, the UE RRC message may be a quasi "incremental" configuration, since the NW must combine the content of this RRC message with the previous configuration provided by the UE using the same RRC message in order to derive the Tx DC position information. Thus, the second option may reduce the message size of the RRC message, but then adds the requirement for both the NW and the UE to remember the content of the last sent RRC message associated with the Tx DC position.

[0057] It is worth noting that the three detailed solutions discussed in this article can provide the following benefits: 1. The ability of the UE to trigger a message to the NW whenever the Tx DC subcarrier configuration has changed at the UE; 2. The ability of the UE to trigger the sending of location information without RRC involvement and accurately provide timely UE Tx DC subcarrier information for effective UL Tx decoding at the NW; 3. The ability to trigger such information without an explicit RRC transaction, where the NW does not have to respond with RRC signaling (i.e., acknowledgment); and 4. Avoiding additional UE and NW processing by skipping encryption and integrity procedures.

[0058] Figure 6 A flow chart of a method 600 for reporting UL Tx DC subcarrier position information is shown. In block 602, the method 600 decodes a radio resource control (RRC) message received from a base station. The RRC message may include a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information. In block 604, the method 600 determines that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position. For example, the new UL Tx DC subcarrier position may include a BWP of an active carrier that is different from a BWP of an active carrier associated with the previous UL Tx DC subcarrier. In block 606, the method 600 encodes a medium access control (MAC) control element (MAC CE) for transmission to the base station in response to determining the change. The MAC CE may include information corresponding to the at least one new UL Tx DC subcarrier position.

[0059] The method 600 may also include associating at least one previous UL Tx DC subcarrier position with a first bandwidth part (BWP) of a carrier, and associating at least one new UL Tx DC subcarrier position with a different second BWP of the carrier. The method 600 may also include information corresponding to the at least one new UL Tx DC subcarrier position including UL Tx DC subcarrier position information corresponding to each active carrier associated with the UE.

[0060] The method 600 may also include the UE including a bandwidth part (BWP) configuration, and the information corresponding to the at least one new UL Tx DC subcarrier position includes information associated with each BWP of each active carrier associated with the UE. The method 600 may also include including in the MACCE additional information associated with at least one of the BWPs of each active carrier associated with the UE. The additional information may include at least information associated with a frequency shift corresponding to the at least one BWP.

[0061] The method 600 may also include the information corresponding to the at least one new UL Tx DC subcarrier position including information corresponding only to the active BWP for each active carrier. The method 600 may also include the transmission of the encoded MAC CE being delayed by a timer. The method 600 may also include the MAC CE being encoded for transmission to both a primary cell group (MCG) and a secondary cell group (SCG) associated with the UE.

[0062] The method 600 may also include information corresponding to at least one new UL Tx DC subcarrier position including UL Tx DC subcarrier position information corresponding to at least one active carrier associated with the MCG and at least one active carrier associated with the SCG. The method 600 may also include transmitting the encoded MAC CE to the MCG, and the primary cell (PCell) of the MCG transmitting the encoded MAC CE to the SCG.

[0063] The method 600 may also include the information corresponding to the at least one new UL Tx DC subcarrier position also including UL Tx DC subcarrier position information of a UL BWP corresponding to a serving cell of the MCG or SCG. The method may also include the information corresponding to the at least one new UL Tx DC subcarrier position including UL Tx DC subcarrier position information of a supplementary UL (SUL) BWP corresponding to a serving cell of the MCG or SCG. The method 600 may also include the information corresponding to the at least one new UL Tx DC subcarrier position being limited to UL Tx DC subcarrier position information that has changed since at least one previous UL Tx DC subcarrier position.

[0064] Figure 7A flow chart of a method 700 for reporting UL Tx DC subcarrier position information is shown. In block 702, the method 700 decodes a radio resource control (RRC) message received from a base station. The RRC message may include a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information. In block 704, the method 700, in response to decoding the RRC message, encodes a message for transmission to the base station via RRC signaling. The message may include each combination of Tx DC subcarrier positions that are feasible for a configured bandwidth part (BWP) of a configured carrier associated with a UE.

[0065] In block 706, the method 700 determines that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position. For example, the new UL Tx DC subcarrier position may include a BWP of an active carrier that is different from a BWP of an active carrier associated with the previous UL Tx DC subcarrier. In block 708, the method 700 encodes a medium access control (MAC) control element (MAC CE) for transmission to a base station in response to determining the change. The MAC CE may include information corresponding to the at least one new UL Tx DC subcarrier position.

[0066] The method 700 may also include the encoded message including a list of Tx DC subcarrier positions for each configured BWP for each configured serving cell associated with the UE. The method 700 may also include the information corresponding to at least one new UL Tx DC subcarrier position within the MAC CE including an index associated with the entry within the encoded message.

[0067] Figure 8 A flow chart of a method 800 for reporting UL Tx DC subcarrier position information is shown. In block 802, the method 800 decodes a radio resource control (RRC) message received from a base station. The RRC message may include a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information. In block 804, the method 800 determines that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position. For example, the new UL Tx DC subcarrier position may include a BWP of an active carrier that is different from a BWP of an active carrier associated with the previous UL Tx DC subcarrier. In block 806, the method 800, in response to determining the change, encodes a message for transmission to the base station via RRC signaling. The message may include information corresponding to the at least one new UL Tx DC subcarrier position.

[0068] The method 800 may also include transmitting the encoded message using a UE Assistance Information (UAI) RRC message. The method 800 may also include the information corresponding to the at least one new UL Tx DC subcarrier position including a snapshot of all Tx DC subcarrier position information associated with each configured bandwidth part (BWP) of each configured carrier associated with the UE. The method 800 may also include limiting the information corresponding to the at least one new UL Tx DC subcarrier position to the UL Tx DC subcarrier position information that has changed since at least one previous UL Tx DC subcarrier position.

[0069] Fig. 9 An exemplary architecture of a system 900 of a network according to various embodiments is shown. The following description is provided for an exemplary system 900 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.

[0070] If Fig. 9 As shown, system 900 includes UE 922 and UE 920. In this example, UE 922 and UE 920 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 control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0071] In some embodiments, UE 922 and / or UE 920 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.

[0072] UE 922 and UE 920 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R) AN 908). In an embodiment, (R) AN 908 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 908 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (R) AN 908 operating in an LTE or 4G system. UE 922 and UE 920 utilize connections (or channels) (shown as connection 904 and connection 902, respectively), each of which includes a physical communication interface or layer (discussed in further detail below).

[0073] In this example, connection 904 and connection 902 are air interfaces for enabling communication coupling, and may conform to a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 922 and UE 920 may exchange communication data directly via a ProSe interface 910. The ProSe interface 910 may alternatively be referred to as a sidelink (SL) interface 110, and may include one or more logical channels, including, but not limited to, PSCCH, PSSCH, PSDCH, and PSBCH.

[0074] UE 920 is shown as being configured to access AP 912 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 924. Connection 924 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 912 would include Wireless Fidelity. router. In this example, AP 912 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 920, (R) AN 908, and AP 912 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 920 in RRC_CONNECTED being configured by RAN node 914 or RAN node 916 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 920 using WLAN radio resources (e.g., connection 924) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 924. 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.

[0075] (R)AN 908 may include one or more AN nodes, such as RAN node 914 and RAN node 916, that enable connection 904 and connection 902. 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 900. According to various embodiments, the RAN node 914 or the RAN node 916 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.

[0076] In some embodiments, all or part of RAN node 914 or RAN node 916 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 914 or RAN node 916); 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 914 or RAN node 916); 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 914 or RAN node 916 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Fig. 9 In 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 908 or by a server pool in a manner similar to the CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 914 or 916 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE 922 and UE 920 and is connected to the SGC via an NG interface (discussed below). In a V2X scenario, the RAN node 914 or one or more of the RAN nodes 916 may be an RSU or act as an RSU.

[0077] 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.

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

[0079] In an embodiment, UE 922 and UE 920 may be configured to communicate with each other or with RAN node 914 and / or RAN node 916 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 communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0080] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 914 and / or RAN node 916 to UE 922 and UE 920, 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 radio 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.

[0081] According to various embodiments, UE 922 and UE 920 and RAN node 914 and / or RAN node 916 communicate data (e.g., transmission and reception) 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.

[0082] To operate in the unlicensed spectrum, the UE 922 and UE 920 and the RAN node 914 or RAN node 916 may operate using LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, the UE 922 and UE 920 and the RAN node 914 or RAN node 916 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.

[0083] LBT is a mechanism by which equipment (e.g., UE 922 and UE 920, RAN node 914 or RAN node 916, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing 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.

[0084] 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 922, AP 912, 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 Y ECCA 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.

[0085] 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.

[0086] 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 922 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.

[0087] The PDSCH carries user data and higher layer signaling to UE 922 and UE 920. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform UE 922 and UE 920 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 UE 920 within a cell) may be performed at either RAN node 914 or RAN node 916 based on channel quality information fed back from either UE 922 and UE 920. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 922 and UE 920.

[0088] 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, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0089] 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.

[0090] The RAN node 914 or the RAN node 916 may be configured to communicate with each other via the interface 930. In an embodiment where the system 900 is an LTE system (e.g., when the CN 906 is an EPC), the interface 930 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 922 in sequence for user data; information about PDCP PDUs not delivered to the UE 922; 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.

[0091] In an embodiment where the system 900 is a SG or NR system (e.g., when the CN 906 is an SGC), the interface 930 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 914 (e.g., a gNB) and an eNB connected to the SGC, and / or between two eNBs connected to a 5GC (e.g., CN 906). 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 the UE 922 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 914 or RAN nodes 916. Mobility support may include context transfer from the old (source) service RAN node 914 to the new (target) service RAN node 916, and control of the user plane tunnel between the old (source) service RAN node 914 and the new (target) service RAN node 916. The protocol stack of Xn-U may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the 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.

[0092] (R)AN 908 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to CN 906. CN 906 may include one or more network elements 932 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 922 and UE 920) connected to CN 906 via (R)AN 908. The components of CN 906 may be implemented in one physical node or in 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). The logical instantiation of CN 906 may be referred to as a network slice, and the logical instantiation of a portion of CN 906 may be referred to as a network sub-slice. The 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.

[0093] In general, the application server 918 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 918 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 UE 922 and UE 920 via the EPC. The application server 918 may communicate with the CN 906 via the IP communication interface 936.

[0094] In an embodiment, CN 906 may be an SGC, and (R)AN 116 may be connected to CN 906 via an NG interface 934. In an embodiment, NG interface 934 may be divided into two parts: an NG user plane (NG-U) interface 926, which carries service data between RAN node 914 or RAN node 916 and UPF; and an S1 control plane (NG-C) interface 928, which is a signaling interface between RAN node 914 or RAN node 916 and AMF.

[0095] In an embodiment, CN 906 may be an SG CN, while in other embodiments, CN 906 may be an EPC. In the case where CN 906 is an EPC, (R)AN 116 may be connected to CN 906 via an S1 interface 934. In an embodiment, S1 interface 934 may be divided into two parts: an S1 user plane (S1-U) interface 926, which carries service data between RAN node 914 or RAN node 916 and S-GW; and an S1-MME interface 928, which is a signaling interface between RAN node 914 or RAN node 916 and MME.

[0096] Fig.10 An example of infrastructure equipment 1000 according to various embodiments is shown. The infrastructure equipment 1000 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 1000 can be implemented in or by a UE.

[0097] The infrastructure equipment 1000 includes application circuits 1002, baseband circuits 1004, one or more radio front end modules 1006 (RFEM), memory circuits 1008, power management integrated circuits (shown as PMIC 1010), power tee circuits 1012, network controller circuits 1014, network interface connectors 1020, satellite positioning circuits 1016, and user interface circuits 1018. In some embodiments, the infrastructure equipment 1000 may include additional elements such as, for example, 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 included separately in more than one device for a CRAN, vBBU, or other similar implementation. The application circuits 1002 include circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface (such as SPI, l 2C or universal programmable serial interface module), a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, a general purpose input / output (I / O or IO), a memory card controller (such as a secure digital (SD) multimedia card (MMC) or similar controller), a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 1002 can be coupled to or can include a memory / storage element and can be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure equipment 1000. In some specific implementations, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0098] The processor of the application circuit 1002 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 1002 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 1002 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 MIPS Warrior P-class processor; etc. In some embodiments, the infrastructure equipment 1000 may not utilize application circuits 1002, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0099] In some implementations, the application circuit 1002 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 1002 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 1002 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 1004 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.

[0100] The user interface circuit 1018 may include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 1000 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 1000. 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.

[0101] The radio front end module 1006 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 1006 that combines both millimeter wave antennas and sub-millimeter waves.

[0102] The memory circuit 1008 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 a "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 1008 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0103] The PMIC 1010 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources such as batteries or capacitors. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 1012 may provide electrical power extracted from a network cable to provide both power and data connections for the infrastructure equipment 1000 using a single cable.

[0104] The network controller circuit 1014 may provide connectivity 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 1000 via a network interface connector 1020, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 1014 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 1014 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0105] The positioning circuit 1016 includes circuits 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 1016 includes various hardware elements (e.g., including hardware devices for facilitating OTA communications, such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 1016 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 1016 may also be part of or interact with the baseband circuit 1004 and / or the radio front end module 1006 to communicate with nodes and components of the positioning network. The positioning circuit 1016 may also provide location data and / or time data to the application circuit 1002, which may use the data to synchronize operations with various infrastructures, etc. Fig.10 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.

[0106] Fig.11 Examples of platforms 1100 according to various embodiments are shown. In an embodiment, computer platform 1100 may be suitable for use as a UE, an application server, and / or any other element / device discussed herein. Platform 1100 may include any combination of components shown in the examples. The components of platform 1100 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 computer platform 1100, or as components otherwise incorporated within a chassis of a larger system. Fig.11The block diagram is intended to show a high-level view of the components of computer platform 1100. 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.

[0107] Application circuit 1102 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: LDO, interrupt controller, serial interface (such as SPI, I 2 C or general purpose programmable serial interface module), RTC, timers including interval timers and watchdog timers, general purpose I / O, memory card controller (such as SD MMC or similar controller), USB interface, MIPI interface, and JTAG test access port. The processor (or core) of the application circuit 1102 can be coupled to or can include a memory / storage element and can be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the platform 1100. In some specific implementations, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

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

[0109] As an example, the processor of the application circuit 1102 may include a processor based on ArchitectureCore TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU-class processors, or can be purchased from The processor of the application circuit 1102 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 1102 can be part of a system on a chip (SoC), in which the application circuit 1102 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0110] Additionally or alternatively, the application circuit 1102 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 1102 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 1102 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.

[0111] Baseband circuitry 1104 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.

[0112] The radio front end module 1106 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 1106 that combines both millimeter wave antennas and sub-millimeter waves.

[0113] The memory circuit 1108 may include any number and type of memory devices for providing a quantitative system memory. As an example, the memory circuit 1108 may include one or more of the following items: 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 1108 may be developed according to a Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design (such as LPDDR2, LPDDR3, LPDDR4, etc.). The memory circuit 1108 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 1108 may be an on-chip memory or register associated with the application circuit 1102. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 1108 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 1100 may be combined with a memory device obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0114] Removable memory 1126 may include devices, circuits, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 1100. 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.

[0115] Platform 1100 may also include interface circuitry (not shown) for connecting external devices to platform 1100. External devices connected to platform 1100 via the interface circuitry include sensors 1122 and electromechanical components (shown as EMC 1124), as well as removable memory devices coupled to removable memory 1126.

[0116] Sensors 1122 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.

[0117] EMC 1124 includes devices, modules or subsystems for the purpose of enabling platform 1100 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 1124 may be configured to generate messages / signaling and send messages / signaling to other components of platform 1100 to indicate the current state of EMC 1124. Examples of EMC 1124 include 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 1100 is configured to operate one or more EMC 1124 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 may connect platform 1100 to positioning circuit 1116. The positioning circuit 1116 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 1116 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 1116 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 1116 may also be part of or interact with the baseband circuit 1104 and / or the radio front-end module 1106 to communicate with nodes and components of the positioning network. Positioning circuitry 1116 may also provide location data and / or time data to application circuitry 1102 , 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.

[0118] In some implementations, the interface circuit may connect the platform 1100 with a near field communication circuit (shown as NFC circuit 1112). The NFC circuit 1112 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuit 1112 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 1100. The NFC circuit 1112 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 1112 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 1112, or initiate data transfer between the NFC circuit 1112 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) near the platform 1100.

[0119] The driver circuit 1118 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1100. The driver circuit 1118 may include various drivers to allow other components of the platform 1100 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 1100. For example, the driver circuit 1118 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 1100, a sensor driver for obtaining sensor readings of the sensor 1122 and controlling and allowing access to the sensor 1122, an EMC driver for obtaining an actuator position of the EMC 1124 and / or controlling and allowing access to the EMC 1124, 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.

[0120] A power management integrated circuit (shown as PMIC 1110) (also referred to as a "power management circuit") may manage power provided to various components of the platform 1100. Specifically, the PMIC 1110 may control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 1104. The PMIC 1110 may typically be included when the platform 1100 is capable of being powered by a battery 1114, for example, when the device is included in a UE.

[0121] In some embodiments, the PMIC 1110 may control or otherwise be part of various power saving mechanisms of the platform 1100. For example, if the platform 1100 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 1100 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 1100 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 1100 enters a very low power state and performs paging, in which the device wakes up periodically again to listen to the network and then powers off again. The platform 1100 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 a few 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.

[0122] The battery 1114 can provide power to the platform 1100, but in some examples, the platform 1100 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 1114 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 1114 can be a typical lead-acid car battery.

[0123] In some implementations, the battery 1114 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 1100 to track the state of charge (SoCh) of the battery 1114. The BMS may be used to monitor other parameters of the battery 1114, such as the state of health (SoH) and state of function (SoF) of the battery 1114 to provide fault prediction. The BMS may transmit information about the battery 1114 to the application circuit 1102 or other components of the platform 1100. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 1102 to directly monitor the voltage of the battery 1114 or the current from the battery 1114. The battery parameters may be used to determine actions that the platform 1100 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0124] A power block or other power source coupled to the grid may be coupled to the BMS to charge the battery 1114. In some examples, the power block may be replaced with a wireless power receiver to wirelessly obtain power, for example, through a loop antenna in the computer platform 1100. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuit selected may depend on the size of the battery 1114 and, therefore, the current required. Charging may 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.

[0125] The user interface circuit 1120 includes various input / output (I / O) devices present in or connected to the platform 1100, and includes one or more user interfaces designed to implement user interaction with the platform 1100 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 1100. The user interface circuit 1120 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, including, in particular, 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 a display device or touch screen (e.g., a liquid crystal display (LCD), LED display, quantum dot display, projector, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the platform 1100. The output device circuitry may also include a speaker or other audio emitting device, a printer, etc. In some embodiments, the sensor 1122 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 an output device circuit (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.

[0126] Although not shown, the components of platform 1100 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.

[0127] Fig.12 Exemplary components of a device 1200 according to some embodiments are shown. In some embodiments, the device 1200 may include an application circuit 1206, a baseband circuit 1204, a radio frequency (RF) circuit (shown as RF circuit 1202), a front-end module (FEM) circuit (shown as FEM circuit 1232), one or more antennas 1230, and a power management circuit (PMC) (shown as PMC 1234) (at least coupled together as shown). The components of the illustrated device 1200 may be included in a UE or a RAN node. In some embodiments, the device 1200 may include fewer elements (e.g., the RAN node may not utilize the application circuit 1206, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 1200 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 (e.g., the circuit may be separately included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0128] The application circuit 1206 may include one or more application processors. For example, the application circuit 1206 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 1200. In some embodiments, the processor of the application circuit 1206 may process IP data packets received from the EPC.

[0129] The baseband circuit 1204 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1204 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 1202 and generate baseband signals for the transmit signal path of the RF circuit 1202. The baseband circuit 1204 may interact with the application circuit 1206 to generate and process baseband signals and control the operation of the RF circuit 1202. For example, in some embodiments, the baseband circuit 1204 may include a third generation (3G) baseband processor (3G baseband processor 1208), a fourth generation (4G) baseband processor (4G baseband processor 1210), a fifth generation (5G) baseband processor (5G baseband processor 1212), or other baseband processors 1214 of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 1204 (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 1202. In other embodiments, some or all of the functions of the baseband processor shown may be included in a module stored in the memory 1220 and may be performed via the central processing unit (CPU 1216). 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 1204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 1204 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.

[0130] In some embodiments, the baseband circuit 1204 may include a digital signal processor (DSP), such as one or more audio DSPs 1218. The one or more audio DSPs 1218 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 1204 and the application circuit 1206 may be implemented, such as, for example, on a system on a chip (SOC).

[0131] In some embodiments, the baseband circuit 1204 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1204 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 1204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

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

[0133] In some embodiments, the receive signal path of the RF circuit 1202 may include a mixer circuit 1222, an amplifier circuit 1224, and a filter circuit 1226. In some embodiments, the transmit signal path of the RF circuit 1202 may include a filter circuit 1226 and a mixer circuit 1222. The RF circuit 1202 may also include a synthesizer circuit 1228 for synthesizing frequencies used by the mixer circuit 1222 of the receive signal path and / or the transmit signal path. In some embodiments, the mixer circuit 1222 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1232 based on the synthesized frequency provided by the synthesizer circuit 1228. The amplifier circuit 1224 may be configured to amplify the down-converted signal, and the filter circuit 1226 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 1204 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, mixer circuit 1222 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0134] In some embodiments, mixer circuit 1222 of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1228 to generate an RF output signal for FEM circuit 1232. The baseband signal can be provided by baseband circuit 1204 and can be filtered by filter circuit 1226.

[0135] In some embodiments, the mixer circuit 1222 of the receive signal path and the mixer circuit 1222 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 1222 of the receive signal path and the mixer circuit 1222 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1222 of the receive signal path and the mixer circuit 1222 may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1222 of the receive signal path and the mixer circuit 1222 of the transmit signal path may be configured for superheterodyne operation.

[0136] 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, RF circuit 1202 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1204 may include a digital baseband interface to communicate with RF circuit 1202.

[0137] 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.

[0138] In some embodiments, synthesizer circuit 1228 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 1228 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0140] 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 1204 or application circuitry 1206 (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 1206.

[0141] The synthesizer circuit 1228 of the RF circuit 1202 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 a 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 set of D-type flip-flops. 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.

[0142] In some embodiments, the synthesizer circuit 1228 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 1202 can include an IQ / polarity converter.

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

[0144] In some embodiments, the FEM circuit 1232 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 1232 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 1232 may include an LNA to amplify a received RF signal and provide an amplified received RF signal as an output (e.g., provided to the RF circuit 1202). The transmit signal path of the FEM circuit 1232 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 1202), 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 1230).

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

[0146] Fig.12 PMC 1234 is shown coupled only to baseband circuitry 1204. However, in other embodiments, PMC 1234 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 1206, RF circuitry 1202, or FEM circuitry 1232) and perform similar power management operations for these components.

[0147] In some embodiments, the PMC 1234 may control or otherwise be part of various power saving mechanisms of the device 1200. For example, if the device 1200 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 1200 may be powered off for short time intervals, thereby saving power.

[0148] If there is no data traffic activity for an extended period of time, the device 1200 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, handovers, etc. The device 1200 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 1200 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.

[0149] 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.

[0150] The processor of the application circuit 1206 and the processor of the baseband circuit 1204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1204 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 1206 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.

[0151] Fig.13 An exemplary interface 1300 of a baseband circuit according to some embodiments is shown. As discussed above, Fig.12 The baseband circuit 1204 may include a 3G baseband processor 1208, a 4G baseband processor 1210, a 5G baseband processor 1212, other baseband processors 1214, a CPU 1216, and a memory 1220 used by the processors. As shown, each of the processors may include a memory interface 1302 for sending / receiving data to / from the memory 1220.

[0152] The baseband circuit 1204 may also include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1304 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1204); an application circuit interface 1306 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1204); Fig.12 RF circuit interface 1308 (for example, for sending / receiving data to / from the application circuit 1206); Fig.12 an interface for sending / receiving data to / from a RF circuit 1202); a wireless hardware connection interface 1310 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. LowEnergy), components and other communication components to send / receive data); and a power management interface 1312 (for example, an interface for sending / receiving power or control signals to / from PMC 1234).

[0153] Fig.14 1 is a block diagram illustrating a component 1400 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.14 A schematic diagram of hardware resources 1402 is shown, which includes one or more processors 1406 (or processor cores), one or more memory / storage devices 1414, and one or more communication resources 1424, each of which can be communicatively coupled via a bus 1416. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1422 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1402.

[0154] Processor 1406 (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 1408 and processor 1410.

[0155] The memory / storage device 1414 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1414 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.

[0156] The communication resources 1424 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1404 or one or more databases 1420 via the network 1418. For example, the communication resources 1424 may include wired communication components (e.g., for coupling via a universal serial bus (USB)), cellular communication components, NFC components, Parts (such as Low power consumption), components and other communication components.

[0157] The instructions 1412 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1406 to perform any one or more of the methods discussed herein. The instructions 1412 may reside completely or partially within at least one of the processors 1406 (e.g., within a cache memory of a processor), the memory / storage device 1414, or any suitable combination thereof. In addition, any portion of the instructions 1412 may be transferred to the hardware resources 1402 from any combination of the peripheral device 1404 or the database 1420. Therefore, the memory of the processor 1406, the memory / storage device 1414, the peripheral device 1404, and the database 1420 are examples of computer-readable and machine-readable media.

[0158] 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 examples. 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 examples shown in the examples section below.

[0159] Examples

[0160] The following examples relate to additional embodiments.

[0161] Embodiment 1 may include a method for wireless communication by a user equipment (UE), comprising: decoding a radio resource control (RRC) message received from a base station, the RRC message including a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information; determining that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position; and in response to determining the change, encoding a medium access control (MAC) control element (MAC CE) for transmission to the base station, the MAC CE including information corresponding to the at least one new UL Tx DC subcarrier position.

[0162] Embodiment 2 may include the method of embodiment 1, wherein the at least one previous UL Tx DC subcarrier position is associated with a first bandwidth part (BWP) of the carrier and the at least one new UL Tx DC subcarrier position is associated with a second, different BWP of the carrier.

[0163] Embodiment 3 may include the method of embodiment 1, wherein the information corresponding to the at least one new UL Tx DC subcarrier position includes UL Tx DC subcarrier position information corresponding to each active carrier associated with the UE.

[0164] Embodiment 4 may include the method of embodiment 1, wherein the UE includes a bandwidth part (BWP) configuration, and the information corresponding to the at least one new UL Tx DC subcarrier position includes information associated with each BWP for each active carrier associated with the UE.

[0165] Embodiment 5 may include the method according to embodiment 4, wherein additional information associated with at least one of the BWPs for each active carrier associated with the UE is included in the MAC CE, the additional information including at least information associated with a frequency shift corresponding to the at least one BWP.

[0166] Embodiment 6 may include the method of embodiment 1, wherein the information corresponding to the at least one new UL Tx DC subcarrier position includes information corresponding only to an active BWP for each active carrier.

[0167] Embodiment 7 may include the method of embodiment 1, wherein transmission of the encoded MAC CE is delayed by a timer.

[0168] Embodiment 8 may include the method of embodiment 1, wherein the MAC CE is encoded for transmission to both a primary cell group (MCG) and a secondary cell group (SCG) associated with the UE.

[0169] Embodiment 9 may include a method according to embodiment 8, wherein the information corresponding to the at least one new UL Tx DC subcarrier position includes UL Tx DC subcarrier position information corresponding to at least one active carrier associated with the MCG and at least one active carrier associated with the SCG.

[0170] Embodiment 10 may include the method of embodiment 8, wherein the encoded MAC CE is transmitted to the MCG, and a primary cell (PCell) of the MCG transmits the encoded MAC CE to the SCG.

[0171] Embodiment 11 may include the method according to embodiment 10, wherein the information corresponding to the at least one new UL Tx DC subcarrier position further includes UL Tx DC subcarrier position information corresponding to the UL BWP of the serving cell of the MCG or the SCG.

[0172] Embodiment 12 may include the method according to embodiment 8, wherein the information corresponding to the at least one new UL Tx DC subcarrier position includes UL Tx DC subcarrier position information corresponding to a supplementary UL (SUL) BWP of a serving cell of the MCG or the SCG.

[0173] Embodiment 13 may include the method of embodiment 1, wherein the information corresponding to the at least one new UL Tx DC subcarrier position is limited to UL Tx DC subcarrier position information that has changed since the at least one previous UL Tx DC subcarrier position.

[0174] Embodiment 14 may include a method for wireless communication by a user equipment (UE), comprising: decoding a radio resource control (RRC) message received from a base station, the RRC message including a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information; in response to decoding the RRC message, encoding a message for transmission to the base station via RRC signaling, the message including each combination of Tx DC subcarrier positions feasible for a configured bandwidth part (BWP) of a configured carrier associated with the UE; determining that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position; and in response to determining the change, encoding a medium access control (MAC) control element (MAC CE) for transmission to the base station, the MAC CE including information corresponding to the at least one new UL Tx DC subcarrier position.

[0175] Embodiment 15 may include the method of embodiment 14, wherein the encoded message includes a list of Tx DC subcarrier positions for each configured BWP for each configured serving cell associated with the UE.

[0176] Embodiment 16 may include the method of embodiment 14, wherein the information corresponding to the at least one new UL Tx DC subcarrier position within the MAC CE comprises an index associated with an entry within the encoded message.

[0177] Embodiment 17 may include a method for wireless communication by a user equipment (UE), comprising: decoding a radio resource control (RRC) message received from a base station, the RRC message including a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information; determining that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position; and in response to determining the change, encoding a message for transmission to the base station via RRC signaling, the message including information corresponding to the at least one new UL Tx DC subcarrier position.

[0178] Embodiment 18 may include the method of Embodiment 17, wherein the encoded message is transmitted using UE Assistance Information (UAI) RRC messaging.

[0179] Embodiment 19 may include a method according to embodiment 17, wherein the information corresponding to the at least one new UL Tx DC subcarrier position comprises a snapshot of all Tx DC subcarrier position information associated with each configured bandwidth part (BWP) of each configured carrier associated with the UE.

[0180] Embodiment 20 may include the method of Embodiment 17, wherein the information corresponding to the at least one new UL Tx DC subcarrier position is limited to UL Tx DC subcarrier position information that has changed since the at least one previous UL Tx DC subcarrier position.

[0181] Embodiment 21 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.

[0182] Embodiment 22 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.

[0183] Embodiment 23 may include a device comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of the above embodiments or any other method or process described herein.

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

[0185] Embodiment 25 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.

[0186] Embodiment 26 may include signals or parts or components thereof as described in or related to any of the above embodiments.

[0187] Embodiment 27 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 content otherwise described in the present disclosure.

[0188] Embodiment 28 may include a signal encoded with data or a portion or component thereof as described in or related to any of the above embodiments, or content described in other ways in this disclosure.

[0189] Embodiment 29 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 content described in other ways in the present disclosure.

[0190] Embodiment 30 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.

[0191] Embodiment 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes 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.

[0192] Embodiment 32 may include signals in a wireless network as shown and described herein.

[0193] Embodiment 33 may include a method of communicating in a wireless network as shown and described herein.

[0194] Embodiment 34 may include a system for providing wireless communications as shown and described herein.

[0195] Embodiment 35 may include an apparatus for providing wireless communications as shown and described herein.

[0196] 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.

[0197] 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.

[0198] 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, aspects, etc. of another embodiment.

[0199] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0200] 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 method for wireless communication by a user equipment (UE), comprising: decoding a radio resource control (RRC) message received from a base station, the RRC message including a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information; determining that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position; and In response to determining the change, a Medium Access Control (MAC) Control Element (MAC CE) is encoded for transmission to the base station, the MAC CE including information corresponding to the at least one new UL Tx DC subcarrier position.

2. The method of claim 1, wherein the at least one previous UL Tx DC subcarrier position is associated with a first bandwidth part (BWP) of a carrier, and the at least one new UL Tx DC subcarrier position is associated with a different second BWP of the carrier.

3. The method of claim 1, wherein the information corresponding to the at least one new UL Tx DC subcarrier position comprises UL Tx DC subcarrier position information corresponding to each active carrier associated with the UE.

4. The method of claim 1, wherein the UE includes a bandwidth part (BWP) configuration, and the information corresponding to the at least one new UL Tx DC subcarrier position includes information associated with each BWP for each active carrier associated with the UE.

5. The method of claim 4, wherein additional information associated with at least one of the BWPs for each active carrier associated with the UE is included in the MAC CE, the additional information comprising at least information associated with a frequency shift corresponding to the at least one BWP.

6. The method of claim 1, wherein the information corresponding to the at least one new UL Tx DC subcarrier position comprises information corresponding only to an active BWP for each active carrier. The method of claim 1 , wherein transmission of the encoded MAC CE is delayed by a timer.

8. The method of claim 1, wherein the MAC CE is encoded for transmission to both a primary cell group (MCG) and a secondary cell group (SCG) associated with the UE.

9. The method of claim 8, wherein the information corresponding to the at least one new UL Tx DC subcarrier position comprises UL Tx DC subcarrier position information corresponding to at least one active carrier associated with the MCG and at least one active carrier associated with the SCG.

10. The method of claim 8, wherein the coded MAC CE is transmitted to the MCG, and a primary cell (PCell) of the MCG transmits the coded MAC CE to the SCG. 11 . The method according to claim 10 , wherein the information corresponding to the at least one new UL Tx DC subcarrier position further comprises UL Tx DC subcarrier position information corresponding to a UL BWP of a serving cell of the MCG or the SCG.

12. The method of claim 8, wherein the information corresponding to the at least one new UL Tx DC subcarrier position comprises UL Tx DC subcarrier position information corresponding to a supplementary UL (SUL) BWP of a serving cell of the MCG or the SCG.

13. The method of claim 1, wherein the information corresponding to the at least one new UL Tx DC subcarrier position is limited to UL Tx DC subcarrier position information that has changed since the at least one previous UL Tx DC subcarrier position.

14. A method for wireless communication by a user equipment (UE), comprising: decoding a radio resource control (RRC) message received from a base station, the RRC message including a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information; responsive to decoding the RRC message, encoding a message for transmission to the base station via RRC signaling, the message including each combination of Tx DC subcarrier positions feasible for a configured bandwidth part (BWP) of a configured carrier associated with the UE; determining that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position; and In response to determining the change, a Medium Access Control (MAC) Control Element (MAC CE) is encoded for transmission to the base station, the MAC CE including information corresponding to the at least one new UL Tx DC subcarrier position.

15. The method of claim 14, wherein the encoded message comprises a list of Tx DC subcarrier positions for each configured BWP for each configured serving cell associated with the UE.

16. The method of claim 14, wherein the information corresponding to the at least one new UL TxDC subcarrier position within the MAC CE comprises an index associated with an entry within the encoded message.

17. A method for wireless communication by a user equipment (UE), comprising: decoding a radio resource control (RRC) message received from a base station, the RRC message including a configuration for dynamically reporting uplink (UL) transmit (Tx) direct current (DC) subcarrier position information; determining that a change associated with at least one previous UL Tx DC subcarrier position has occurred, thereby creating at least one new UL Tx DC subcarrier position; and In response to determining the change, a message is encoded for transmission to the base station via RRC signaling, the message including information corresponding to the at least one new UL Tx DC subcarrier position.

18. The method of claim 17, wherein the encoded message utilizes UE Assistance Information (UAI) RRC messaging.

19. The method of claim 17, wherein the information corresponding to the at least one new UL Tx DC subcarrier position comprises a snapshot of all Tx DC subcarrier position information associated with each configured bandwidth part (BWP) of each configured carrier associated with the UE.

20. The method of claim 17, wherein the information corresponding to the at least one new UL Tx DC subcarrier position is limited to UL Tx DC subcarrier position information that has changed since the at least one previous UL Tx DC subcarrier position.

Images