Systems and methods for assistance information for dynamic waveform switching

Dynamic waveform switching in NR systems, facilitated by power headroom reporting, addresses the challenge of maintaining adequate uplink coverage by selecting the appropriate waveform for user equipment, enhancing both coverage and data rate.

WO2024233790A1PCT designated stage expired Publication Date: 2024-11-14INTEL CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/US2024/028598
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-08-02
Filing Date
2024-05-09
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

In cellular systems, particularly for New Radio (NR), maintaining adequate uplink coverage is challenging due to higher carrier frequencies, leading to issues with power headroom and waveform selection for user equipment (UE) in varying channel conditions, which affects the quality of service.

Method used

The implementation of assistance information for dynamic waveform switching, allowing user equipment (UE) to report power headroom information for both CP-OFDM and DFT-s-OFDM waveforms, enabling the gNB to dynamically select the appropriate waveform for PUSCH transmission based on channel conditions, thereby improving coverage and data rate.

Benefits of technology

This solution enhances uplink coverage by dynamically switching between waveforms, optimizing power headroom and data rate based on UE conditions, thereby improving overall system performance and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2024028598_14112024_PF_FP_ABST
    Figure US2024028598_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Various embodiments herein provide techniques for assistance information to facilitate dynamic waveform switching. For example, a user equipment (UE) may generate and send a power headroom report with power headroom information with a transform precoder disabled (e.g., for cyclic prefix - orthogonal frequency-division multiplexing (CP-OFDM) waveform) and with the transform precoder enabled (e.g., for Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform). Other embodiments may be described and claimed.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] SYSTEMS AND METHODS FOR ASSISTANCE INFORMATION FOR DYNAMIC WAVEFORM SWITCHING

[0002] CROSS REFERENCE TO RELATED APPLICATION

[0003] The present application claims priority to U.S. Provisional Patent Application No. 63 / 501,586, which was filed May 11, 2023; and to U.S. Provisional Patent Application No. 63 / 517,287, which was filed August 2, 2023.

[0004] BACKGROUND

[0005] For cellular systems, coverage is an important factor for successful operation. Compared to Long Term Evolution (LTE), New Radio (NR) can be deployed at relatively higher carrier frequency in frequency range 1 (FR1), e.g., at 3.5GHz. In this case, coverage loss is expected due to larger path loss, which makes it more challenging to maintain an adequate quality of service. Typically, uplink coverage is the bottleneck for system operation considering the low transmit power at the user equipment (UE) side.

[0006] BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

[0008] Figure 1 illustrates an example of a medium access control - control element (MAC-CE) for a power headroom report (PHR) for dynamic waveform switching, in accordance with various embodiments.

[0009] Figure 2 illustrates another example of a MAC-CE for a PHR for dynamic waveform switching, in accordance with various embodiments.

[0010] Figure 3 illustrates another example of a MAC-CE for a PHR for dynamic waveform switching, in accordance with various embodiments.

[0011] Figure 4 illustrates another example of a MAC-CE for a PHR for dynamic waveform switching, in accordance with various embodiments.

[0012] Figure 5 illustrates an example of a MAC-CE for a PHR for dynamic waveform switching and multiple transmit-receive points (TRPs), in accordance with various embodiments.

[0013] Figure 6 illustrates another example of a MAC-CE for a PHR for dynamic waveform switching and multiple TRPs, in accordance with various embodiments.

[0014] Figure 7 illustrates an example of a multiple entry PHR for dynamic waveform switching, in accordance with various embodiments.

[0015] Figure 8 schematically illustrates a wireless network in accordance with various embodiments.

[0016] Figure 9 schematically illustrates components of a wireless network in accordance with various embodiments.

[0017] Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0018] Figure 11 illustrates a network in accordance with various embodiments.

[0019] Figure 12 depicts an example procedure for practicing the various embodiments discussed herein.

[0020] Figure 13 depicts another example procedure for practicing the various embodiments discussed herein.

[0021] Figure 14 depicts another example procedure for practicing the various embodiments discussed herein.

[0022] DETAILED DESCRIPTION

[0023] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A / B” mean (A), (B), or (A and B).

[0024] Various embodiments herein provide techniques for assistance information to facilitate dynamic waveform switching. For example, a user equipment (UE) may generate and send a power headroom report with power headroom information with a transform precoder disabled (e.g., for cyclic prefix - orthogonal frequency-division multiplexing (CP-OFDM) waveform) and with the transform precoder enabled (e.g., for Discrete Fourier Transform-spread-OFDM (DFT- s-OFDM) waveform).

[0025] In NR, system design is based on waveform choice of CP-OFDM for downlink (DL) and CP-OFDM or DFT-s-OFDM for uplink (UL). Note that DFT-s-OFDM waveform is realized by enabling transform precoding at the transmitter side. When transform precoding is disabled, CP- OFDM waveform is employed for PUSCH transmission. Typically, DFT-s-OFDM waveform can achieve better uplink coverage performance due to its low Peak-to-Average Power Ratio (PAPR) compared to CP-OFDM waveform.

[0026] For cell edge UEs with poor channel conditions, it is more appropriate to utilize DFT-s- OFDM waveform for PUSCH transmission for better coverage due to low PAPR. However, for cell center UEs with high SNR, CP-OFDM waveform is more beneficial given that it can support UL multiple input, multiple output (MIMO) with high rank transmission to provide high data rate and improve system capacity.

[0027] To fully exploit the benefit of DFT-s-OFDM or CP-OFDM waveform for PUSCH transmission in a timely manner, dynamic switching of waveform type can be supported for PUSCH transmission. To enable dynamic waveform switching, assistance information regarding the power headroom (PH) may be reported from a UE to allow gNB to make proper decision on the selection of waveform for the UE.

[0028] Various embodiments herein provide systems and methods associated with assistance information for dynamic waveform switching.

[0029] Assistance information for dynamic waveform switching

[0030] As mentioned above, for cell edge UEs with poor channel conditions, it is more appropriate to utilize DFT-s-OFDM waveform for PUSCH transmission for better coverage due to low PAPR. On the contrary, for cell center UEs with high SNR, CP-OFDM waveform is more beneficial given the fact that it can support UL MIMO with high rank transmission so as to provide high data rate and improve system capacity.

[0031] To fully exploit the benefit of DFT-s-OFDM or CP-OFDM waveform for PUSCH transmission in a timely manner, dynamic switching of waveform type can be supported for PUSCH transmission. To enable dynamic waveform switching, assistance information regarding the power headroom (PH) may be reported from a UE to allow gNB to make proper decision on the selection of waveform for the UE.

[0032] Embodiments of assistance information for dynamic waveform switching are described further below.

[0033] In one embodiment, power headroom report (PHR) for both CP-OFDM and DFT-s-OFDM waveform may be included in a single Medium Access Control - Control Element (MAC-CE).

[0034] In some aspects, whether PHR for both CP-OFDM and DFT-s-OFDM waveform is included in a single MAC-CE can be configured by higher layers via radio resource control (RRC) signalling. In another option, whether PHR for dynamic waveform switching is reported can be determined depending on whether dynamic waveform switching is configured for DCI format 0_l and / or 0_2 in the active UL BWP. For instance, when dynamic waveform switching is configured for one of DCI format 0_l and 0_2, PHR for both CP-OFDM and DFT-s-OFDM waveform is included in a single MAC-CE. This may also apply for the case for dynamic waveform switching and multiple TRPs.

[0035] In one option, the existing procedure can be reused to determine whether the PHR is actual PHR or virtual PHR regardless of whether PUSCH transmission in slot n is based on CP-OFDM or DFT-s-OFDM waveform. Further, the determined PHR type (actual PHR or virtual PHR) can apply for both CP-OFDM and DFT-s-OFDM waveforms.

[0036] In some aspects, actual PHR refers to a PHR for a real PUSCH transmission, while virtual PHR refers to a PHR with a reference PUSCH.

[0037] In another option, the existing procedure can be reused to determine whether the PHR is actual PHR or virtual PHR in accordance with the indicated waveform for PUSCH transmission in slot n. Further, the determined PHR type (actual PHR or virtual PHR) can apply for both CP- OFDM and DFT-s-OFDM waveforms.

[0038] In another option, the existing procedure can be reused to determine whether the PHR is actual PHR or virtual PHR. Further, when PHR is determined as virtual PHR, only single entry PHR is included in the MAC-CE. In one example, the virtual PHR is determined in accordance with the indicated waveform for PUSCH transmission in slot n.

[0039] Figure 1 illustrates one example of PHR for dynamic waveform switching MAC-CE. Aspects of the MAC-CE in Figure 1 include:

[0040] • Power Headroom i (PH i): This field indicates the power headroom level, where PH 1 is associated with DFT-s-OFDM waveform and PH 2 is associated with CP- OFDM waveform, or vice versa. PH fields for a Serving Cell are included in ascending order based on i. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB are specified in TS 38.133);

[0041] • Other fields in the MAC-CE of Figure 1 can be reused as defined in Clause 6.1.3.50 in TS38.321.

[0042] In another example, only actual PHR is included in the MAC-CE. Figure 2 illustrates another example of PHR for dynamic waveform switching MAC-CE. Aspects of the MAC-CE in Figure 2 include:

[0043] • Power Headroom i (PH i): This field indicates the power headroom level, where PH 1 is associated with DFT-s-OFDM waveform and PH 2 is associated with CP- OFDM waveform, or vice versa. PH fields for a Serving Cell are included in ascending order based on i. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB are specified in TS 38.133);

[0044] • Other fields in the MAC-CE can be reused as defined in Clause 6.1.3.50 in TS38.321.

[0045] In another example, different maximum Tx power for CP-OFDM and DFT-s-OFDM waveform may be included in the PHR in a single MAC-CE. Figure 3 illustrates another example of PHR for dynamic waveform switching MAC-CE. Aspects of the MAC-CE in Figure 3 include:

[0046] • PcMAx.f.c i: This field indicates the PCMAX,f,c (as specified in TS 38.213 [6]) used for calculation of the preceding PH field for DFT-s-OFDM and CP-OFDM waveform, respectively.

[0047] In another example, only actual PHR for one waveform is included in a new MAC-CE for dynamic waveform switching.

[0048] In one option, one bit in the MAC-CE for dynamic waveform switching PHR may be included to indicate whether the waveform is CP-OFDM or DFT-s-OFDM waveform.

[0049] In another option, the waveform for PHR may be determined based on predefined rules. In one example, the waveform is same as the waveform that is indicated or activated in the DCI or configured by higher layer. In another example, the waveform is different from the waveform that is indicated or activated in the DCI or configured by higher layer. In another example, the waveform is determined as one with smaller or larger value of PH from CP-OFDM and DFT-s- OFDM waveform.

[0050] Figure 4 illustrates another example of PHR for dynamic waveform switching MAC-CE. Aspects of the MAC-CE of Figure 4 include:

[0051] • W: This field indicates the waveform type. The MAC entity shall set the W field to

[0052] 1 if the PH is for CP-OFDM waveform and 0 if the PH is for DFT-s-OFDM waveform or vice versa.

[0053] • Power Headroom i (PH i): This field indicates the power headroom level for the indicated waveform.

[0054] In one embodiment, a new enhanced logic channel ID (eECID) can be defined for the new MAC-CE carrying PHR for dynamic waveform switching. In some aspects, the eECID may be separately defined for single entry PHR for dynamic waveform switching, multi-entry PHR for dynamic waveform switching or PHR for dynamic waveform switching and multiple TRP.

[0055] In another embodiment, in case of multiple transmit receive point (TRP) operation for PUSCH repetition, e.g., for a component carrier (CC) that is configured with multiple TRP PUSCH repetition, PHR for both CP-OFDM and DFT-s-OFDM waveform for PUSCH transmission which are targeted for both a first TRP and a second TRP can be reported in a single MAC-CE for dynamic waveform switching.

[0056] In this case, four power headroom levels are included in a single PHR for both multiple TRP and dynamic waveform switching, which are for the PUSCH repetition for a first and second TRP, and for CP-OFDM and DFT-s-OFDM waveform, respectively.

[0057] Figure 5 illustrates one example of PHR for dynamic waveform switching and multiple TRP MAC-CE. Aspects of the MAC-CE in Figure 5 include:

[0058] • Power Headroom i, j (PH i, j): This field indicates the power headroom level, where PH 1, 1 is associated with the SRS-ResourceSet with a lower srs-ResourceSetld and with DFT-s-OFDM waveform; PH 1, 2 is associated with the SRS-ResourceSet with a lower srs-ResourceSetld and with CP-OFDM waveform; PH 2, 1 is associated with the SRS-ResourceSet with a higher srs-ResourceSetld and with DFT-s-OFDM waveform and PH 2, 2 is associated with the SRS-ResourceSet with a higher srs-ResourceSetld and with CP-OFDM waveform; PH fields for a Serving Cell are included in ascending order based on i. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB are specified in TS 38.133);

[0059] • Other fields in the MAC-CE can be reused as defined in Clause 6.1.3.50 in TS38.321.

[0060] In another option, two power headroom levels are included in a single PHR for both multiple TRP and dynamic waveform switching, which are for the PUSCH repetition for a first and second TRP for one waveform, respectively.

[0061] In one option, one bit in the MAC-CE for each TRP for dynamic waveform switching PHR may be included to indicate whether the waveform is CP-OFDM or DFT-s-OFDM waveform. In another option, single bit in the MAC-CE for both TRPs for dynamic waveform switching PHR may be included to indicate whether the waveform is CP-OFDM or DFT-s-OFDM waveform. In this case, PHR for the same waveform for each TRP is reported for dynamic waveform switching.

[0062] In another option, the waveform for PHR for each TRP may be determined based on predefined rules. In one example, the waveform is same as the waveform that is indicated or activated in the DCI or configured by higher layer. In another example, the waveform is different from the waveform that is indicated or activated in the DCI or configured by higher layer. In another example, the waveform is determined as one with smaller or larger value of PH from CP- OFDM and DFT-s-OFDM waveform.

[0063] Figure 6 illustrates one example of PHR for dynamic waveform switching and multiple TRP MAC-CE. Aspects of the MAC-CE in Figure 6 include:

[0064] W: This field indicates the waveform type. The MAC entity shall set the W field to 1 if the PH is for CP-OFDM waveform and 0 if the PH is for DFT-s-OFDM waveform or vice versa for each TRP.

[0065] • Power Headroom i (PH i): This field indicates the power headroom level for the indicated waveform for each TRP, where PH 1 is associated with the SRSResourceSet with a lower srs-ResourceSetld and PH 2 is associated with the SRS-ResourceSet with a higher srsResourceSetld for the indicated waveform.

[0066] • Other fields in the figure can be reused as defined in Clause 6.1.3.50 in TS38.321.

[0067] In another embodiment, in case of multiple TRP operation for PUSCH repetition, e.g., for a CC that is configured with multiple TRP PUSCH repetition, and if UE does not support two PHRs for multiple TRP operation, and if the PHR reporting is actual PHR, the UE uses the uses the set of power control parameters corresponding to an earliest repetition that overlaps with the first slot in which the PUSCH that carries the PHR MAC-CE is transmitted. Further, UE includes PHRs for both CP-OFDM and DFT-s-OFDM waveform for dynamic waveform switching in the earliest repetition.

[0068] In another embodiment, in case of multiple TRP operation for PUSCH repetition, e.g., for a CC that is configured with multiple TRP PUSCH repetition, and if the PHR reporting is actual PHR, the UE uses the uses the set of power control parameters corresponding to an earliest repetition that overlaps with the first slot in which the PUSCH that carries the PHR MAC-CE is transmitted. Further, UE includes PHRs for both CP-OFDM and DFT-s-OFDM waveform for dynamic waveform switching in the earliest repetition.

[0069] In another embodiment, in case of multiple TRP operation for PUSCH repetition, e.g., for a CC that is configured with mTRP PUSCH repetition, the existing mechanism on the determination of actual PHR and virtual PHR for the PUSCH repetitions that are targeted for a first and second TRP, can be reused. Further, the determined PHR type (actual PHR or virtual PHR) can apply for both CP-OFDM and DFT-s-OFDM waveforms for the PUSCH for a first or second TRP, respectively.

[0070] In one example, if the first PHR value is determined as actual PHR corresponding to a repetition among multiple TRP PUSCH repetitions associated with a first TRP, then actual PHR is applied for both CP-OFDM and DFT-s-OFDM waveforms. Further, if the second PHR value is determined as virtual PHR corresponding to a repetition among multiple TRP PUSCH repetitions associated with a second TRP, then virtual PHR is applied for both CP-OFDM and DFT-s-OFDM waveforms.

[0071] In another embodiment, multiple entry PHR MAC CE may be extended to include PHR for both CP-OFDM and DFT-s-OFDM waveform for one or more carriers. In particular, for a carrier which is configured with dynamic waveform switching, the PHR in the carrier may include the PHR for both CP-OFDM and DFT-s-OFDM waveform in accordance with the aforementioned embodiments.

[0072] In another option, whether PHR for dynamic waveform switching is reported in a carrier can be determined depending on whether dynamic waveform switching is configured for DCI format 0_l and / or 0_2 in one of the UL BWP or active UL BWP, or in the carrier. In one example, in case when dynamic waveform switching is configured in one of DCI format 0_l or DCI format 0_2 in one of the UL BWP in a carrier, PHR for dynamic waveform switching is reported in the carrier.

[0073] Figure 7 illustrates one example of multiple entry PHR with dynamic waveform switching MAC CE. In Figure 7, PHR for both CP-OFDM and DFT-s-OFDM waveform for PCell is included in the MAC CE.

[0074] In one option, waveform indication and PH for the indicated or determined waveform can be included in a carrier for multiple Entry PHR with dynamic waveform switching. As mentioned above, the carrier may be configured with dynamic waveform switching or dynamic waveform switching is configured for DCI format 0_l and / or 0_2 in one of the UL BWP or active UL BWP, or in the carrier.

[0075] In another embodiment, enhanced Multiple Entry PHR for multiple TRP MAC CE may be extended to include PHR for both CP-OFDM and DFT-s-OFDM waveform for one or more carriers. In particular, for a carrier which is configured with dynamic waveform switching, the PHR in the carrier may include the PHR for both CP-OFDM and DFT-s-OFDM waveform in accordance with the aforementioned embodiments.

[0076] SYSTEMS AND IMPLEMENTATIONS

[0077] Figures 8-11 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

[0078] Figure 8 illustrates a network 800 in accordance with various embodiments. The network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.

[0079] The network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with a RAN 804 via an over-the-air connection. The UE 802 may be communicatively coupled with the RAN 804 by a Uu interface. The UE 802 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

[0080] In some embodiments, the network 800 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0081] In some embodiments, the UE 802 may additionally communicate with an AP 806 via an over-the-air connection. The AP 806 may manage a WLAN connection, which may serve to offload some / all network traffic from the RAN 804. The connection between the UE 802 and the AP 806 may be consistent with any IEEE 802.11 protocol, wherein the AP 806 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 802, RAN 804, and AP 806 may utilize cellular- WLAN aggregation (for example, LWA / LWIP). Cellular- WLAN aggregation may involve the UE 802 being configured by the RAN 804 to utilize both cellular radio resources and WLAN resources.

[0082] The RAN 804 may include one or more access nodes, for example, AN 808. AN 808 may terminate air-interface protocols for the UE 802 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 808 may enable data / voice connectivity between CN 820 and the UE 802. In some embodiments, the AN 808 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 808 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 808 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0083] In embodiments in which the RAN 804 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 804 is an LTE RAN) or an Xn interface (if the RAN 804 is a 5G RAN). The X2 / Xn interfaces, which may be separated into control / user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data / context transfers, mobility, load management, interference coordination, etc.

[0084] The ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 802 with an air interface for network access. The UE 802 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 804. For example, the UE 802 and RAN 804 may use carrier aggregation to allow the UE 802 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first / second ANs may be any combination of eNB, gNB, ng-eNB, etc.

[0085] The RAN 804 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium / carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

[0086] In V2X scenarios the UE 802 or AN 808 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications / software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communications services. The components of the RSU may be packaged in a weatherproof 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 or a backhaul network.

[0087] In some embodiments, the RAN 804 may be an LTE RAN 810 with eNBs, for example, eNB 812. The LTE RAN 810 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

[0088] In some embodiments, the RAN 804 may be an NG-RAN 814 with gNBs, for example, gNB 816, or ng-eNBs, for example, ng-eNB 818. The gNB 816 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 816 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 816 and the ng-eNB 818 may connect with each other over an Xn interface.

[0089] In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 814 and a UPF 848 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN814 and an AMF 844 (e.g., N2 interface).

[0090] The NG-RAN 814 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS / SSS / PBCH.

[0091] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 802 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 802, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 802 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 802 and in some cases at the gNB 816. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

[0092] The RAN 804 is communicatively coupled to CN 820 that includes network elements to provide various functions to support data and telecommunications services to customers / subscribers (for example, users of UE 802). The components of the CN 820 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 820 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 820 may be referred to as a network slice, and a logical instantiation of a portion of the CN 820 may be referred to as a network sub-slice. In some embodiments, the CN 820 may be an LTE CN 822, which may also be referred to as an EPC. The LTE CN 822 may include MME 824, SGW 826, SGSN 828, HSS 830, PGW 832, and PCRF 834 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 822 may be briefly introduced as follows.

[0093] The MME 824 may implement mobility management functions to track a current location of the UE 802 to facilitate paging, bearer activation / deactivation, handovers, gateway selection, authentication, etc.

[0094] The SGW 826 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 822. The SGW 826 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0095] The SGSN 828 may track a location of the UE 802 and perform security functions and access control. In addition, the SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 824; MME selection for handovers; etc. The S3 reference point between the MME 824 and the SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states.

[0096] The HSS 830 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 830 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 830 and the MME 824 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 820.

[0097] The PGW 832 may terminate an SGi interface toward a data network (DN) 836 that may include an application / content server 838. The PGW 832 may route data packets between the LTE CN 822 and the data network 836. The PGW 832 may be coupled with the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 832 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 832 and the data network 8 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 832 may be coupled with a PCRF 834 via a Gx reference point.

[0098] The PCRF 834 is the policy and charging control element of the LTE CN 822. The PCRF 834 may be communicatively coupled to the app / content server 838 to determine appropriate QoS and charging parameters for service flows. The PCRF 832 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

[0099] In some embodiments, the CN 820 may be a 5GC 840. The 5GC 840 may include an AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, and AF 860 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 840 may be briefly introduced as follows.

[0100] The AUSF 842 may store data for authentication of UE 802 and handle authentication- related functionality. The AUSF 842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 840 over reference points as shown, the AUSF 842 may exhibit an Nausf service-based interface.

[0101] The AMF 844 may allow other functions of the 5GC 840 to communicate with the UE 802 and the RAN 804 and to subscribe to notifications about mobility events with respect to the UE 802. The AMF 844 may be responsible for registration management (for example, for registering UE 802), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 844 may provide transport for SM messages between the UE 802 and the SMF 846, and act as a transparent proxy for routing SM messages. AMF 844 may also provide transport for SMS messages between UE 802 and an SMSF. AMF 844 may interact with the AUSF 842 and the UE 802 to perform various security anchor and context management functions. Furthermore, AMF 844 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 804 and the AMF 844; and the AMF 844 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 844 may also support NAS signaling with the UE 802 over an N3 IWF interface.

[0102] The SMF 846 may be responsible for SM (for example, session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 848 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 844 over N2 to AN 808; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 802 and the data network 836.

[0103] The UPF 848 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 836, and a branching point to support multi-homed PDU session. The UPF 848 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 848 may include an uplink classifier to support routing traffic flows to a data network.

[0104] The NSSF 850 may select a set of network slice instances serving the UE 802. The NSSF 850 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 850 may also determine the AMF set to be used to serve the UE 802, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 854. The selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 with which the UE 802 is registered by interacting with the NSSF 850, which may lead to a change of AMF. The NSSF 850 may interact with the AMF 844 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 850 may exhibit an Nnssf service-based interface.

[0105] The NEF 852 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, AFs (e.g., AF 860), edge computing or fog computing systems, etc. In such embodiments, the NEF 852 may authenticate, authorize, or throttle the AFs. NEF 852 may also translate information exchanged with the AF 860 and information exchanged with internal network functions. For example, the NEF 852 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 852 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 852 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 852 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 852 may exhibit an Nnef service-based interface.

[0106] The NRF 854 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 854 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 854 may exhibit the Nnrf service-based interface.

[0107] The PCF 856 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 856 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 858. In addition to communicating with functions over reference points as shown, the PCF 856 exhibit an Npcf service-based interface.

[0108] The UDM 858 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 802. For example, subscription data may be communicated via an N8 reference point between the UDM 858 and the AMF 844. The UDM 858 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 858 and the PCF 856, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 802) for the NEF 852. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 858, PCF 856, and NEF 852 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 858 may exhibit the Nudm service-based interface.

[0109] The AF 860 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0110] In some embodiments, the 5GC 840 may enable edge computing by selecting operator / 3rdparty services to be geographically close to a point that the UE 802 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 840 may select a UPF 848 close to the UE 802 and execute traffic steering from the UPF 848 to data network 836 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 860 is considered to be a trusted entity, the network operator may permit AF 860 to interact directly with relevant NFs. Additionally, the AF 860 may exhibit an Naf service-based interface.

[0111] The data network 836 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application / content server 838.

[0112] Figure 9 schematically illustrates a wireless network 900 in accordance with various embodiments. The wireless network 900 may include a UE 902 in wireless communication with an AN 904. The UE 902 and AN 904 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

[0113] The UE 902 may be communicatively coupled with the AN 904 via connection 906. The connection 906 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

[0114] The UE 902 may include a host platform 908 coupled with a modem platform 910. The host platform 908 may include application processing circuitry 912, which may be coupled with protocol processing circuitry 914 of the modem platform 910. The application processing circuitry 912 may run various applications for the UE 902 that source / sink application data. The application processing circuitry 912 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

[0115] The protocol processing circuitry 914 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 906. The layer operations implemented by the protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

[0116] The modem platform 910 may further include digital baseband circuitry 916 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 914 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0117] The modem platform 910 may further include transmit circuitry 918, receive circuitry 920, RF circuitry 922, and RF front end (RFFE) 924, which may include or connect to one or more antenna panels 926. Briefly, the transmit circuitry 918 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 920 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 922 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 924 may include filters (for example, surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 918, receive circuitry 920, RF circuitry 922, RFFE 924, and antenna panels 926 (referred generically as “transmit / receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed in the same or different chips / modules, etc.

[0118] In some embodiments, the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0119] A UE reception may be established by and via the antenna panels 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. In some embodiments, the antenna panels 926 may receive a transmission from the AN 904 by receive-beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 926.

[0120] A UE transmission may be established by and via the protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panels 926. In some embodiments, the transmit components of the UE 904 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 926.

[0121] Similar to the UE 902, the AN 904 may include a host platform 928 coupled with a modem platform 930. The host platform 928 may include application processing circuitry 932 coupled with protocol processing circuitry 934 of the modem platform 930. The modem platform may further include digital baseband circuitry 936, transmit circuitry 938, receive circuitry 940, RF circuitry 942, RFFE circuitry 944, and antenna panels 946. The components of the AN 904 may be similar to and substantially interchangeable with like-named components of the UE 902. In addition to performing data transmission / reception as described above, the components of the AN 908 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0122] Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices / sub- slices to utilize the hardware resources 1000.

[0123] The processors 1010 may include, for example, a processor 1012 and a processor 1014. The processors 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0124] The memory / storage devices 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 1020 may include, but are not limited to, any type of volatile, non-volatile, or semi-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.

[0125] The communication resources 1030 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via a network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0126] Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor’s cache memory), the memory / storage devices 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory / storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.

[0127] Figure 11 illustrates a network 1100 in accordance with various embodiments. The network 1100 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 1100 may operate concurrently with network 800. For example, in some embodiments, the network 1100 may share one or more frequency or bandwidth resources with network 800. As one specific example, a UE (e.g., UE 1102) may be configured to operate in both network 1100 and network 800. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 800 and 1100. In general, several elements of network 1100 may share one or more characteristics with elements of network 800. For the sake of brevity and clarity, such elements may not be repeated in the description of network 1100.

[0128] The network 1100 may include a UE 1102, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1108 via an over-the-air connection. The UE 1102 may be similar to, for example, UE 802. The UE 1102 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

[0129] Although not specifically shown in Figure 11, in some embodiments the network 1100 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 11, the UE 1102 may be communicatively coupled with an AP such as AP 806 as described with respect to Figure 8. Additionally, although not specifically shown in Figure 11, in some embodiments the RAN 1108 may include one or more ANss such as AN 808 as described with respect to Figure 8. The RAN 1108 and / or the AN of the RAN 1108 may be referred to as a base station (BS), a RAN node, or using some other term or name.

[0130] The UE 1102 and the RAN 1108 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.

[0131] The RAN 1108 may allow for communication between the UE 1102 and a 6G core network (CN) 1110. Specifically, the RAN 1108 may facilitate the transmission and reception of data between the UE 1102 and the 6G CN 1110. The 6G CN 1110 may include various functions such as NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, AF 860, SMF 846, and AUSF 842. The 6G CN 1110 may additional include UPF 848 and DN 836 as shown in Figure 11.

[0132] Additionally, the RAN 1108 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1124 and a Compute Service Function (Comp SF) 1136. The Comp CF 1124 and the Comp SF 1136 may be parts or functions of the Computing Service Plane. Comp CF 1124 may be a control plane function that provides functionalities such as management of the Comp SF 1136, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc.. Comp SF 1136 may be a user plane function that serves as the gateway to interface computing service users (such as UE 1102) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 1136 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1136 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 1124 instance may control one or more Comp SF 1136 instances.

[0133] Two other such functions may include a Communication Control Function (Comm CF) 1128 and a Communication Service Function (Comm SF) 1138, which may be parts of the Communication Service Plane. The Comm CF 1128 may be the control plane function for managing the Comm SF 1138, communication sessions creation / configuration / releasing, and managing communication session context. The Comm SF 1138 may be a user plane function for data transport. Comm CF 1128 and Comm SF 1138 may be considered as upgrades of SMF 846 and UPF 848, which were described with respect to a 5G system in Figure 8. The upgrades provided by the Comm CF 1128 and the Comm SF 1138 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 846 and UPF 848 may still be used.

[0134] Two other such functions may include a Data Control Function (Data CF) 1122 and Data Service Function (Data SF) 1132 may be parts of the Data Service Plane. Data CF 1122 may be a control plane function and provides functionalities such as Data SF 1132 management, Data service creation / configuration / releasing, Data service context management, etc. Data SF 1132 may be a user plane function and serve as the gateway between data service users (such as UE 1102 and the various functions of the 6G CN 1110) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status. Another such function may be the Service Orchestration and Chaining Function (SOCF) 1120, which may discover, orchestrate and chain up communication / computing / data services provided by functions in the network. Upon receiving service requests from users, SOCF 1120 may interact with one or more of Comp CF 1124, Comm CF 1128, and Data CF 1122 to identify Comp SF 1136, Comm SF 1138, and Data SF 1132 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 1136, Comm SF 1138, and Data SF 1132 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 1120 may also responsible for maintaining, updating, and releasing a created service chain.

[0135] Another such function may be the service registration function (SRF) 1114, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 1136 and Data SF 1132 gateways and services provided by the UE 1102. The SRF 1114 may be considered a counterpart of NRF 854, which may act as the registry for network functions.

[0136] Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 1126, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 1112 and eSCP- U 1134, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 1126 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0137] Another such function is the AMF 1144. The AMF 1144 may be similar to 844, but with additional functionality. Specifically, the AMF 1144 may include potential functional repartition, such as move the message forwarding functionality from the AMF 1144 to the RAN 1108.

[0138] Another such function is the service orchestration exposure function (SOEF) 1118. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.

[0139] The UE 1102 may include an additional function that is referred to as a computing client service function (comp CSF) 1104. The comp CSF 1104 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 1120, Comp CF 1124, Comp SF 1136, Data CF 1122, and / or Data SF 1132 for service discovery, request / response, compute task workload exchange, etc. The Comp CSF 1104 may also work with network side functions to decide on whether a computing task should be run on the UE 1102, the RAN 1108, and / or an element of the 6G CN 1110. The UE 1102 and / or the Comp CSF 1104 may include a service mesh proxy 1106. The service mesh proxy 1106 may act as a proxy for service-to- service communication in the user plane. Capabilities of the service mesh proxy 1106 may include one or more of addressing, security, load balancing, etc.

[0140] EXAMPLE PROCEDURES

[0141] In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 8-11, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process 1200 is depicted in Figure 12. In some embodiments, the process 1200 may be performed by a UE or a portion thereof. At 1202, the process 1200 includes receiving configuration information to indicate that dynamic transform precoder indication is enabled for an active uplink (UE) bandwidth part (BWP) of a serving cell. At 1204, the process 1200 may further include generating, based on the configuration information, first power headroom information associated with a transform precoder being disabled and second power headroom information associated with the transform precoder being enabled. At 1206, the process 1200 may further include reporting the first and second power headroom information to a next generation Node B (gNB).

[0142] Figure 13 illustrates another example process 1300 in accordance with various embodiments. The process 1300 may be performed by a UE or a portion thereof. At 1302, the process 1300 includes receiving receive a configuration information to indicate that a downlink control information (DCI) is to include an indication of whether a transform precoder is enabled or disabled. At 1304, the process 1300 further includes generating first power headroom information based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information. At 1306, the process 1300 further includes generating second power headroom information based on the assumed PUSCH information, wherein the second power headroom information is generated based on the transform precoder being disabled if the transform precoder is enabled for the actual PUSCH transmission and is generated based on the transform precoder being enabled if the transform precoder is disabled for the actual PUSCH transmission. At 1308, the process 1300 further includes reporting the first and second power headroom information to a next generation Node B (gNB).

[0143] Figure 14 illustrates another example process 1400 in accordance with various embodiments. The process 1400 may be performed by a gNB or a portion thereof. At 1402, the process 1400 includes encoding, for transmission to a user equipment (UE), configuration information to indicate that a downlink control information (DCI) is to include an indication of whether a transform precoder is enabled or disabled. At 1404, the process 1400 further includes receiving, from the UE, first power headroom information based on the PUSCH transmission and second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on the transform precoder being disabled if the transform precoder is enabled for the PUSCH transmission and is generated based on the transform precoder being enabled if the transform precoder is disabled for the PUSCH transmission.

[0144] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0145] EXAMPLES

[0146] Example 1 may include a method of wireless communication in a wireless cellular network (e.g., for a fifth generation (5G) or new radio (NR) system), the method comprising: receiving, by a UE from a gNodeB, a configuration of a power headroom report (PHR) for CP-OFDM and DFT-s-OFDM waveform in a single Medium Access Control - Control Element (MAC-CE); and reporting, by the UE, the PHR for CP-OFDM and DFT-s-OFDM waveform in a MAC CE.

[0147] Example 2 may include the method of example 1 or some other example herein, wherein the existing procedure can be reused to determine whether the PHR is actual PHR or virtual PHR regardless of whether PUSCH transmission in slot n is based on CP-OFDM or DFT-s- OFDM waveform; wherein the determined PHR type (actual PHR or virtual PHR) can apply for both CP-OFDM and DFT-s-OFDM waveforms.

[0148] Example 3 may include the method of example 1 or some other example herein, wherein the existing procedure can be reused to determine whether the PHR is actual PHR or virtual PHR in accordance with the indicated waveform for PUSCH transmission in slot n; wherein the determined PHR type (actual PHR or virtual PHR) can apply for both CP-OFDM and DFT-s-

[0149] OFDM waveforms.

[0150] Example 4 may include the method of example 1 or some other example herein, wherein when PHR is determined as virtual PHR, only single entry PHR is included in the MAC-CE.

[0151] Example 5 may include the method of example 1 or some other example herein, wherein in case of multiple transmit receive point (TRP) operation for PUSCH repetition, e.g., for a CC that is configured with multiple TRP PUSCH repetition, PHR for both CP-OFDM and DFT-s- OFDM waveform for PUSCH transmission which are targeted for both a first TRP and a second TRP can be reported in a single MAC-CE for dynamic waveform switching.

[0152] Example 6 may include the method of example 1 or some other example herein, wherein in case of multiple TRP operation for PUSCH repetition, e.g., for a CC that is configured with multiple TRP PUSCH repetition, and if UE does not support two PHRs for multiple TRP operation, and if the PHR reporting is actual PHR, the UE uses the uses the set of power control parameters corresponding to an earliest repetition that overlaps with the first slot in which the PUSCH that carries the PHR MAC-CE is transmitted.

[0153] Example 7 may include the method of example 1 or some other example herein, wherein UE includes PHRs for both CP-OFDM and DFT-s-OFDM waveform for dynamic waveform switching in the earliest repetition.

[0154] Example 8 may include the method of example 1 or some other example herein, wherein in case of multiple TRP operation for PUSCH repetition, e.g., for a CC that is configured with multiple TRP PUSCH repetition, and if the PHR reporting is actual PHR, the UE uses the uses the set of power control parameters corresponding to an earliest repetition that overlaps with the first slot in which the PUSCH that carries the PHR MAC-CE is transmitted.

[0155] Example 9 may include the method of example 1 or some other example herein, wherein UE includes PHRs for both CP-OFDM and DFT-s-OFDM waveform for dynamic waveform switching in the earliest repetition.

[0156] Example 10 may include the method of example 1 or some other example herein, wherein the determined PHR type (actual PHR or virtual PHR) can apply for both CP-OFDM and DFT-s-OFDM waveforms for the PUSCH for a first or second TRP, respectively.

[0157] Example 11 may include the method of example 1 or some other example herein, wherein multiple Entry PHR MAC CE may be extended to include PHR for both CP-OFDM and DFT-s-OFDM waveform for one or more carriers.

[0158] Example 12 may include the method of example 1 or some other example herein, wherein for a carrier which is configured with dynamic waveform switching, the PHR in the carrier may include the PHR for both CP-OFDM and DFT-s-OFDM waveform in accordance with the aforementioned embodiments.

[0159] Example 13 may include the method of example 1 or some other example herein, wherein enhanced Multiple Entry PHR for multiple TRP MAC CE may be extended to include PHR for both CP-OFDM and DFT-s-OFDM waveform for one or more carriers.

[0160] Example 14 may include the method of example 1 or some other example herein, wherein for a carrier which is configured with dynamic waveform switching, the PHR in the carrier may include the PHR for both CP-OFDM and DFT-s-OFDM waveform in accordance with the aforementioned embodiments.

[0161] Example 15 may include the method of example 1 or some other example herein, wherein whether PHR for dynamic waveform switching is reported can be determined depending on whether dynamic waveform switching is configured for DCI format 0_l and / or 0_2 in the active UL BWP

[0162] Example 16 may include the method of example 1 or some other example herein, wherein only actual PHR for one waveform is included in a new MAC-CE for dynamic waveform switching.

[0163] Example 17 may include the method of example 1 or some other example herein, wherein one bit in the MAC-CE for dynamic waveform switching PHR may be included to indicate whether the waveform is CP-OFDM or DFT-s-OFDM waveform.

[0164] Example 18 may include the method of example 1 or some other example herein, wherein the waveform for PHR may be determined based on predefined rules.

[0165] Example 19 may include the method of example 1 or some other example herein, wherein new enhanced logic channel ID (eLCID) can be defined for the new MAC-CE carrying PHR for dynamic waveform switching.

[0166] Example 20 may include the method of example 1 or some other example herein, wherein two power headroom levels are included in a single PHR for both multiple TRP and dynamic waveform switching, which are for the PUSCH repetition for a first and second TRP for one waveform, respectively.

[0167] Example 21 may include the method of example 1 or some other example herein, wherein waveform indication and PH for the indicated or determined waveform can be included in a carrier for multiple Entry PHR with dynamic waveform switching.

[0168] Example 22 may include a method of a user equipment (UE), the method comprising: receiving a configuration for a power headroom report (PHR) for a cyclic prefix (CP)- orthogonal frequency division multiplexing (OFDM) waveform and a discrete Fourier transform (DFT)-spread (s)-OFDM waveform in a single Medium Access Control - Control Element (MAC-CE); and generating the MAC-CE for transmission based on the configuration.

[0169] Example 23 may include the method of example 22 or some other example herein, further comprising: determining whether a PHR type is an actual PHR or a virtual PHR; and applying the determined PHR type for both the CP-OFDM and DFT-s-OFDM waveforms in the PHR.

[0170] Example 24 may include the method of example 22-23 or some other example herein, wherein the PHR corresponds to a virtual PHR, and wherein a single entry PHR is included in the MAC-CE for both the CP-OFDM and DFT-s-OFDM waveforms.

[0171] Example 25 may include the method of example 22-24 or some other example herein, wherein the MAC-CE includes PHR information for both CP-OFDM and DFT-s-OFDM waveform for a physical uplink shared channel (PUSCH) transmission targeted to both a first transmission-reception point (TRP) and a second TRP.

[0172] Example 26 may include the method of example 22-25 or some other example herein, wherein the PHR corresponds to a component carrier that is configured with PUSCH repetitions using multiple TRPs.

[0173] Example 27 may include the method of example 26 or some other example herein, wherein, if the UE does not support two PHRs for multiple TRP operation, and if the PHR corresponds to actual PHR, the PHR is based on a set of power control parameters that correspond to an earliest PUSCH repetition that overlaps with a first slot in which the a PUSCH that carries the MAC-CE is transmitted.

[0174] Example 28 may include the method of example 26 or some other example herein, wherein the PHR corresponds to an actual PHR, and wherein the PHR is based on a set of power control parameters corresponding to an earliest PUSCH repetition that overlaps with the first slot in which the PUSCH that carries the MAC-CE is transmitted.

[0175] Example 29 may include the method of example 22-28 or some other example herein, wherein the MAC-CE includes a multiple entry MAC-CE. may be extended to include PHR for both CP-OFDM and DFT-s-OFDM waveform for one or more carriers.

[0176] Example 30 may include the method of example 22-29 or some other example herein, wherein the PHR corresponds to a carrier that is configured with dynamic waveform switching.

[0177] Example 31 may include the method of example 22-30 or some other example herein, wherein the PHR is transmitted based on a determination that dynamic waveform switching is configured for DCI format 0_l and / or 0_2 in an active UL BWP.

[0178] Example 32 may include the method of example 22-31 or some other example herein, wherein the MAC-CE includes an actual PHR for only one waveform.

[0179] Example 33 may include the method of example 32 or some other example herein, wherein the MAC-CE includes an indication of whether the waveform associated with the PHR is CP-OFDM or DFT-s-OFDM waveform. Example 34 may include the method of example 32-33 or some other example herein, further comprising determining the waveform for the PHR based on one or more predefined rules.

[0180] Example 35 may include the method of example 22-34 or some other example herein, wherein the MAC-CE uses an enhanced logic channel ID (eLCID) that is designated for PHR for dynamic waveform switching.

[0181] Example 36 may include the method of example 22-35 or some other example herein, wherein two power headroom levels are included in a single PHR for both multiple TRP and dynamic waveform switching.

[0182] Example 37 may include the method of example 36 or some other example herein, wherein the two power headroom levels are for PUSCH repetition for a first and second TRP for one waveform, respectively.

[0183] Example 38 may include the method of example 22-37 or some other example herein, wherein the PHR includes a multiple entry PHR for dynamic waveform switching, and wherein the PHR indicates a power headroom and associated waveform.

[0184] Example 39 may include the method of example 38 or some other example herein, wherein the multiple entry PHR is transmitted on a carrier configured with dynamic waveform switching.

[0185] Example 40 may include a method of a next generation Node B (gNB), the method comprising: encoding, for transmission to a user equipment (UE), a configuration for a power headroom report (PHR) for a cyclic prefix (CP) -orthogonal frequency division multiplexing (OFDM) waveform and a discrete Fourier transform (DFT)-spread (s)-OFDM waveform in a single Medium Access Control - Control Element (MAC-CE); and receiving the MAC-CE from the UE based on the configuration.

[0186] Example 41 may include the method of example 40 or some other example herein, wherein a same PHR type (e.g., actual PHR or virtual PHR) is applied for both the CP-OFDM and DFT-s-OFDM waveforms in the MAC-CE.

[0187] Example 42 may include the method of example 40-41 or some other example herein, wherein the PHR corresponds to a virtual PHR, and wherein a single entry PHR is included in the MAC-CE for both the CP-OFDM and DFT-s-OFDM waveforms.

[0188] Example 43 may include the method of example 40-42 or some other example herein, wherein the MAC-CE includes PHR information for both CP-OFDM and DFT-s-OFDM waveform for a physical uplink shared channel (PUSCH) transmission targeted to both a first transmission-reception point (TRP) and a second TRP. Example 44 may include the method of example 40-43 or some other example herein, wherein the PHR corresponds to a component carrier that is configured with PUSCH repetitions using multiple TRPs.

[0189] Example 45 may include the method of example 44 or some other example herein, wherein, if the UE does not support two PHRs for multiple TRP operation, and if the PHR corresponds to actual PHR, the PHR is based on a set of power control parameters that correspond to an earliest PUSCH repetition that overlaps with a first slot in which the a PUSCH that carries the MAC-CE is received.

[0190] Example 46 may include the method of example 44 or some other example herein, wherein the PHR corresponds to an actual PHR, and wherein the PHR is based on a set of power control parameters corresponding to an earliest PUSCH repetition that overlaps with the first slot in which the PUSCH that carries the MAC-CE is received.

[0191] Example 47 may include the method of example 40-46 or some other example herein, wherein the MAC-CE includes a multiple entry MAC-CE.

[0192] Example 48 may include the method of example 40-47 or some other example herein, wherein the PHR corresponds to a carrier that is configured with dynamic waveform switching.

[0193] Example 49 may include the method of example 40-48 or some other example herein, wherein the PHR is received if dynamic waveform switching is configured for DCI format 0_l and / or 0_2 in an active UL BWP.

[0194] Example 50 may include the method of example 40-49 or some other example herein, wherein the MAC-CE includes an actual PHR for only one waveform.

[0195] Example 51 may include the method of example 50 or some other example herein, wherein the MAC-CE includes an indication of whether the waveform associated with the PHR is CP-OFDM or DFT-s-OFDM waveform.

[0196] Example 52 may include the method of example 50-51 or some other example herein, further comprising determining the waveform for the PHR based on one or more predefined rules.

[0197] Example 53 may include the method of example 40-52 or some other example herein, wherein the MAC-CE uses an enhanced logic channel ID (eLCID) that is designated for PHR for dynamic waveform switching.

[0198] Example 54 may include the method of example 40-53 or some other example herein, wherein two power headroom levels are included in a single PHR for both multiple TRP and dynamic waveform switching.

[0199] Example 55 may include the method of example 54 or some other example herein, wherein the two power headroom levels are for PUSCH repetition for a first and second TRP for one waveform, respectively.

[0200] Example 56 may include the method of example 40-55 or some other example herein, wherein the PHR includes a multiple entry PHR for dynamic waveform switching, and wherein the PHR indicates a power headroom and associated waveform.

[0201] Example 57 may include the method of example 56 or some other example herein, wherein the multiple entry PHR is received on a carrier configured with dynamic waveform switching.

[0202] Example 58 may include an apparatus of a user equipment (UE), the apparatus comprising: a memory to store configuration information to indicate that dynamic transform precoder indication is present in a downlink control information (DCI) format for an active uplink (UL) bandwidth part (BWP) of a serving cell; and processor circuity coupled to the memory. The processor circuitry is to: generate, based on the configuration information, first power headroom information associated with a transform precoder being disabled and second power headroom information associated with the transform precoder being enabled; and report the first and second power headroom information to a next generation Node B (gNB).

[0203] Example 59 may include the apparatus of example 58 or some other example herein, wherein a first one of the first or second power headroom information is generated based on an actual physical uplink shared channel (PUSCH) transmission and a second one of the first or second power headroom information is generated based on an assumed PUSCH transmission.

[0204] Example 60 may include the apparatus of example 59 or some other example herein, wherein the processor circuitry is further to decode a DCI that includes an indication of whether the transform precoder is enabled for the actual PUSCH transmission.

[0205] Example 61 may include the apparatus of example 60 or some other example herein, wherein the DCI is a DCI format 0_l or 0_2.

[0206] Example 62 may include the apparatus of example 58-61 or some other example herein, wherein the first and second power headroom information is reported in a same medium access control - control element (MAC-CE).

[0207] Example 63 may include the apparatus of example 58-62 or some other example herein, wherein at least one of the first or second power headroom information includes a maximum output power reduction value, PCMAX .C (i).

[0208] Example 64 may include the apparatus of example 58-63 or some other example herein, wherein the processor circuitry is to disable the transform precoder to transmit a cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) waveform, and is to enable the transform precoder to transmit a discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform. Example 65 may include one or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE), configure the UE to: receive configuration information to indicate that a downlink control information (DCI) is to include an indication of whether a transform precoder is enabled or disabled; generate first power headroom information based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information; generate second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on the transform precoder being disabled if the transform precoder is enabled for the actual PUSCH transmission and is generated based on the transform precoder being enabled if the transform precoder is disabled for the actual PUSCH transmission; and report the first and second power headroom information to a next generation Node B (gNB).

[0209] Example 66 may include the one or more computer-readable media of example 65 or some other example herein, wherein the DCI is a DCI format 0_l or 0_2.

[0210] Example 67 may include the one or more computer-readable media of example 65-66 or some other example herein, wherein the first and second power headroom information is reported in a same medium access control - control element (MAC-CE).

[0211] Example 68 may include the one or more computer-readable media of example 65-67 or some other example herein, wherein the transform precoder is disabled to transmit the PUSCH transmission with a cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) waveform, and is to enabled to transmit the PUSCH transmission with a discrete Fourier Transform- spread-OFDM (DFT-s-OFDM) waveform.

[0212] Example 69 may include the one or more computer-readable media of example 65-68 or some other example herein, wherein the instructions, when executed, further configure the UE to decode the DCI including the indication of whether the transform precoder is enabled or disabled.

[0213] Example 70 may include the one or more computer-readable media of example 65-69 or some other example herein, wherein the instructions, when executed, further configure the UE to receive the assumed PUSCH information from the gNB.

[0214] Example 71 may include the one or more computer-readable media of example 66-70 or some other example herein, wherein the second power headroom information includes a maximum output power reduction value, PCMAX .C (i).

[0215] Example 72 may include one or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB), configure the gNB to: encode, for transmission to a user equipment (UE), configuration information to indicate that a downlink control information (DCI) is to include an indication of whether a transform precoder is enabled or disabled; and receive, from the UE, first power headroom information based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information, and second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on the transform precoder being disabled if the transform precoder is enabled for the actual PUSCH transmission and is generated based on the transform precoder being enabled if the transform precoder is disabled for the actual PUSCH transmission.

[0216] Example 73 may include the one or more computer-readable media of example 72 or some other example herein, wherein the DCI is a DCI format 0_l or 0_2.

[0217] Example 74 may include the one or more computer-readable media of example 72-73 or some other example herein, wherein the first and second power headroom information is received in a same medium access control - control element (MAC-CE).

[0218] Example 75 may include the one or more computer-readable media of example 72-74 or some other example herein, wherein when the DCI indicates that the transform precoder is disabled the UE is to transmit the PUSCH transmission with a cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) waveform, and wherein when the DCI indicates that the transform precoder is enabled the UE is to transmit the PUSCH transmission with a discrete Fourier Transform- spread-OFDM (DFT-s-OFDM) waveform.

[0219] Example 76 may include the one or more computer-readable media of example 72-75 or some other example herein, wherein the instructions, when executed, further configure the gNB to transmit, to the UE, the DCI with the indication of whether the transform precoder is enabled or disabled.

[0220] Example 77 may include the one or more computer-readable media of example 72-76 or some other example herein, wherein the instructions, when executed, further configure the gNB to transmit, to the UE, the assumed PUSCH information.

[0221] Example 78 may include the one or more computer-readable media of example 72-77 or some other example herein, wherein the second power headroom information includes a maximum output power reduction value, PCMAX .C (i).

[0222] Example 79 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-78, or any other method or process described herein.

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

[0224] Example 81 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-78, or any other method or process described herein.

[0225] Example 82 may include a method, technique, or process as described in or related to any of examples 1-78, or portions or parts thereof.

[0226] Example 83 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-78, or portions thereof.

[0227] Example 84 may include a signal as described in or related to any of examples 1-78, or portions or parts thereof.

[0228] Example 85 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-78, or portions or parts thereof, or otherwise described in the present disclosure.

[0229] Example 86 may include a signal encoded with data as described in or related to any of examples 1-78, or portions or parts thereof, or otherwise described in the present disclosure.

[0230] Example 87 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-78, or portions or parts thereof, or otherwise described in the present disclosure.

[0231] Example 88 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-78, or portions thereof.

[0232] Example 89 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-78, or portions thereof.

[0233] Example 90 may include a signal in a wireless network as shown and described herein.

[0234] Example 91 may include a method of communicating in a wireless network as shown and described herein.

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

[0236] Example 93 may include a device for providing wireless communication as shown and described herein. Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0237] Abbreviations

[0238] Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

[0239] 3 GPP Third Generation ANR Automatic BPSK Binary Phase

[0240] Partnership Neighbour Relation Shift Keying

[0241] Project AOA Angle of BRAS Broadband

[0242] 4G Fourth Arrival Remote Access

[0243] Generation 40 AP Application 75 Server

[0244] 5G Fifth Generation Protocol, Antenna BSS Business

[0245] 5GC 5G Core Port, Access Point Support System network API Application BS Base Station

[0246] AC Programming Interface BSR Buffer Status

[0247] Application 45 APN Access Point 80 Report

[0248] Client Name BW Bandwidth

[0249] ACR Application ARP Allocation and BWP Bandwidth Part

[0250] Context Relocation Retention Priority C-RNTI Cell

[0251] ACK ARQ Automatic Radio Network

[0252] Acknowledgeme 50 Repeat Request 85 Temporary nt AS Access Stratum Identity

[0253] ACID ASP CA Carrier

[0254] Application Application Service Aggregation,

[0255] Client Identification Provider Certification

[0256] ADRF Analytics Data 55 90 Authority

[0257] Repository ASN.l Abstract Syntax CAPEX CAPital

[0258] Function Notation One Expenditure

[0259] AF Application AUSF Authentication CBD Candidate Beam

[0260] Function Server Function Detection

[0261] AM Acknowledged 60 AWGN Additive 95 CBRA Contention

[0262] Mode White Gaussian Based Random

[0263] AMBR Aggregate Noise Access

[0264] Maximum Bit Rate BAP Backhaul CC Component

[0265] AMF Access and Adaptation Protocol Carrier, Country

[0266] Mobility 65 BCH Broadcast 100 Code, Cryptographic

[0267] Management Channel Checksum

[0268] Function BER Bit Error Ratio CCA Clear Channel

[0269] AN Access Network BFD Beam Assessment

[0270] AnLF Analytics Failure Detection CCE Control Channel

[0271] Logical Function 70 BLER Block Error Rate 105 Element CCCH Common CMS Cloud Redundancy Check Control Channel Management System CRI Channel-State CE Coverage CO Conditional Information Resource Enhancement Optional Indicator, CSI-RS CDM Content Delivery 40 CoMP Coordinated 75 Resource Network Multi-Point Indicator

[0272] CDMA Code- CORESET Control C-RNTI Cell Division Multiple Resource Set RNTI

[0273] Access COTS Commercial Off- CS Circuit Switched

[0274] CDR Charging Data 45 The-Shelf 80 CSCF call Request CP Control Plane, session control function

[0275] CDR Charging Data Cyclic Prefix, CSAR Cloud Service Response Connection Archive

[0276] CFRA Contention Free Point CSI Channel-State Random Access 50 CPD Connection 85 Information CG Cell Group Point Descriptor CSI-IM CSI CGF Charging CPE Customer Interference

[0277] Gateway Function Premise Measurement CHF Charging Equipment CSI-RS CSI

[0278] Function 55 CPICH Common Pilot 90 Reference Signal

[0279] CI Cell Identity Channel CSI-RSRP CSI CID Cell-ID (e.g., CQI Channel Quality reference signal positioning method) Indicator received power CIM Common CPU CSI processing CSI-RSRQ CSI Information Model 60 unit, Central 95 reference signal CIR Carrier to Processing Unit received quality Interference Ratio C / R CSI-SINR CSI CK Cipher Key Command / Resp signal-to-noise and CM Connection onse field bit interference ratio Management, 65 CRAN Cloud Radio 100 CSMA Carrier Sense

[0280] Conditional Access Network, Multiple Access Mandatory Cloud RAN CSMA / CA CSMA CMAS Commercial CRB Common with collision Mobile Alert Service Resource Block avoidance CMD Command 70 CRC Cyclic 105 CSS Common Search Space, Cell- specific DRS Discovery Identification

[0281] Search Space Reference Signal ECS Edge

[0282] CTF Charging DRX Discontinuous Configuration Server

[0283] Trigger Function Reception ECSP Edge

[0284] CTS Clear-to-Send 40 DSL Domain Specific 75 Computing Service

[0285] CW Codeword Language. Digital Provider

[0286] CWS Contention Subscriber Line EDN Edge

[0287] Window Size DSLAM DSL Data Network

[0288] D2D Device-to- Access Multiplexer EEC Edge

[0289] Device 45 DwPTS 80 Enabler Client

[0290] DC Dual Downlink Pilot EECID Edge

[0291] Connectivity, Direct Time Slot Enabler Client

[0292] Current E-LAN Ethernet Identification

[0293] DCI Downlink Local Area Network EES Edge

[0294] Control 50 E2E End-to-End 85 Enabler Server

[0295] Information EAS Edge EESID Edge

[0296] DF Deployment Application Server Enabler Server

[0297] Flavour ECCA extended clear Identification

[0298] DL Downlink channel EHE Edge

[0299] DMTF Distributed 55 assessment, 90 Hosting Environment

[0300] Management Task extended CCA EGMF Exposure

[0301] Force ECCE Enhanced Governance

[0302] DPDK Data Plane Control Channel Management

[0303] Development Kit Element, Function

[0304] DM-RS, DMRS 60 Enhanced CCE 95 EGPRS

[0305] Demodulation ED Energy Enhanced GPRS

[0306] Reference Signal Detection EIR Equipment

[0307] DN Data network EDGE Enhanced Identity Register

[0308] DNN Data Network Datarates for GSM eLAA enhanced

[0309] Name 65 Evolution (GSM 100 Licensed Assisted

[0310] DNAI Data Network Evolution) Access,

[0311] Access Identifier EAS Edge enhanced LAA

[0312] Application Server EM Element

[0313] DRB Data Radio EASID Edge Manager

[0314] Bearer 70 Application Server 105 eMBB Enhanced Mobile E-UTRA Evolved FDD Frequency

[0315] Broadband UTRA Division Duplex

[0316] EMS Element E-UTRAN Evolved FDM Frequency

[0317] Management System UTRAN Division eNB evolved NodeB, 40 EV2X Enhanced V2X 75 Multiplex E-UTRAN Node B F1AP Fl Application FDMA Frequency EN-DC E- Protocol Division Multiple UTRA-NR Dual Fl-C Fl Control plane Access

[0318] Connectivity interface FE Front End EPC Evolved Packet 45 Fl-U Fl User plane 80 FEC Forward Error Core interface Correction

[0319] EPDCCH enhanced FACCH Fast FFS For Further

[0320] PDCCH, enhanced Associated Control Study

[0321] Physical CHannel FFT Fast Fourier

[0322] Downlink Control 50 FACCH / F Fast 85 Transformation Cannel Associated Control feEAA further enhanced

[0323] EPRE Energy per Channel / Full Eicensed Assisted resource element rate Access, further EPS Evolved Packet FACCH / H Fast enhanced EAA System 55 Associated Control 90 FN Frame Number

[0324] EREG enhanced REG, Channel / Half FPGA Field- enhanced resource rate Programmable Gate element groups FACH Forward Access Array ETSI European Channel FR Frequency

[0325] Telecommunicat 60 FAUSCH Fast 95 Range ions Standards Uplink Signalling FQDN Fully Qualified Institute Channel Domain Name

[0326] ETWS Earthquake and FB Functional Block G-RNTI GERAN Tsunami Warning FBI Feedback Radio Network System 65 Information 100 Temporary eUICC embedded FCC Federal Identity UICC, embedded Communications GERAN

[0327] Universal Commission GSM EDGE Integrated Circuit FCCH Frequency RAN, GSM EDGE Card 70 Correction CHannel 105 Radio Access Network GTP GPRS Tunneling HSS Home

[0328] GGSN Gateway GPRS Protocol Subscriber Server Support Node GTP-UGPRS HSUPA High GLONASS Tunnelling Protocol Speed Uplink Packet

[0329] GLObal'naya 40 for User Plane 75 Access

[0330] NAvigatsionnay GTS Go To Sleep HTTP Hyper Text a Sputnikovaya Signal (related to Transfer Protocol Sistema (Engl.: WUS) HTTPS Hyper Global Navigation GUMMEI Globally Text Transfer Protocol

[0331] Satellite System) 45 Unique MME Identifier 80 Secure (https is gNB Next Generation GUTI Globally Unique http / 1.1 over NodeB Temporary UE SSL, i.e. port 443) gNB-CU gNB- Identity I-Block centralized unit, Next HARQ Hybrid ARQ, Information

[0332] Generation 50 Hybrid 85 Block

[0333] NodeB Automatic ICCID Integrated centralized unit Repeat Request Circuit Card gNB-DU gNB- HANDO Handover Identification distributed unit, Next HFN HyperFrame IAB Integrated

[0334] Generation 55 Number 90 Access and Backhaul

[0335] NodeB HHO Hard Handover ICIC Inter-Cell distributed unit HLR Home Location Interference

[0336] GNSS Global Register Coordination Navigation Satellite HN Home Network ID Identity,

[0337] System 60 HO Handover 95 identifier

[0338] GPRS General Packet HPLMN Home IDFT Inverse Discrete Radio Service Public Land Mobile Fourier

[0339] GPSI Generic Network Transform

[0340] Public Subscription HSDPA High IE Information

[0341] Identifier 65 Speed Downlink 100 element

[0342] GSM Global System Packet Access IBE In-Band for Mobile HSN Hopping Emission

[0343] Communications Sequence Number IEEE Institute of , Groupe Special HSPA High Speed Electrical and Mobile 70 Packet Access 105 Electronics Engineers IP Internet Protocol kB Kilobyte (1000

[0344] IEI Information Ipsec IP Security, bytes)

[0345] Element Identifier Internet Protocol kbps kilo-bits per

[0346] IEIDL Information Security second

[0347] Element Identifier 40 IP-CAN IP- 75 Kc Ciphering key

[0348] Data Length Connectivity Access Ki Individual

[0349] IETF Internet Network subscriber

[0350] Engineering Task IP-M IP Multicast authentication

[0351] Force IPv4 Internet Protocol key

[0352] IF Infrastructure 45 Version 4 80 KPI Key

[0353] IIOT Industrial IPv6 Internet Protocol Performance Indicator

[0354] Internet of Things Version 6 KQI Key Quality

[0355] IM Interference IR Infrared Indicator

[0356] Measurement, IS In Sync KSI Key Set

[0357] Intermodulation, 50 IRP Integration 85 Identifier

[0358] IP Multimedia Reference Point ksps kilo-symbols per

[0359] IMC IMS Credentials ISDN Integrated second

[0360] IMEI International Services Digital KVM Kernel Virtual

[0361] Mobile Network Machine

[0362] Equipment 55 IS IM IM Services 90 LI Layer 1

[0363] Identity Identity Module (physical layer)

[0364] IMGI International ISO International Ll-RSRP Layer 1 mobile group identity Organisation for reference signal IMPI IP Multimedia Standardisation received power

[0365] Private Identity 60 ISP Internet Service 95 L2 Layer 2 (data

[0366] IMPU IP Multimedia Provider link layer)

[0367] PUblic identity IWF Interworking- L3 Layer 3

[0368] IMS IP Multimedia Function (network layer)

[0369] Subsystem I-WLAN LAA Licensed

[0370] IMS I International 65 Interworking 100 Assisted Access

[0371] Mobile WLAN LAN Local Area

[0372] Subscriber Constraint length Network

[0373] Identity of the convolutional LADN Local loT Internet of code, USIM Area Data Network

[0374] Things 70 Individual key 105 LBT Listen Before Talk Control (protocol Occupancy Time

[0375] LCM LifeCycle layering context) MCS Modulation and

[0376] Management MAC Message coding scheme

[0377] LCR Low Chip Rate authentication code MD AF Management

[0378] LCS Location 40 (security / encryption 75 Data Analytics

[0379] Services context) Function

[0380] LCID Logical MAC-A MAC MDAS Management

[0381] Channel ID used for Data Analytics

[0382] LI Layer Indicator authentication Service

[0383] LLC Logical Link 45 and key 80 MDT Minimization of

[0384] Control, Low Layer agreement (TSG Drive Tests

[0385] Compatibility T WG3 context) ME Mobile

[0386] LME Location MAC-IMAC used for Equipment

[0387] Management Eunction data integrity of MeNB master eNB

[0388] LOS Line of 50 signalling messages 85 MER Message Error

[0389] Sight (TSG T WG3 context) Ratio

[0390] LPLMN Local MANO MGL Measurement

[0391] PLMN Management and Gap Length

[0392] LPP LTE Positioning Orchestration MGRP Measurement

[0393] Protocol 55 MBMS 90 Gap Repetition

[0394] LSB Least Significant Multimedia Period

[0395] Bit Broadcast and Multicast MIB Master

[0396] LTE Long Term Service Information Block,

[0397] Evolution MBSFN Management

[0398] LWA LTE- WLAN 60 Multimedia 95 Information Base aggregation Broadcast multicast MIMO Multiple Input

[0399] LWIP LTE / WLAN service Single Multiple Output

[0400] Radio Level Frequency MLC Mobile Location

[0401] Integration with Network Centre

[0402] IPsec Tunnel 65 MCC Mobile Country 100 MM Mobility

[0403] LTE Long Term Code Management

[0404] Evolution MCG Master Cell MME Mobility

[0405] M2M Machine-to- Group Management Entity

[0406] Machine MCOT Maximum MN Master Node

[0407] MAC Medium Access 70 Channel 105 MNO Mobile Network Operator Number UTRA Dual MO Measurement MSISDN Mobile Connectivity Object, Mobile Subscriber ISDN NEF Network

[0408] Originated Number Exposure Function

[0409] MPBCH MTC 40 MT Mobile 75 NF Network

[0410] Physical Broadcast Terminated, Mobile Function

[0411] CHannel Termination NFP Network MPDCCH MTC MTC Machine-Type Forwarding Path Physical Downlink Communications NFPD Network

[0412] Control CHannel 45 MTLF Model Training 80 Forwarding Path MPDSCH MTC Logical Descriptor Physical Downlink Functions NFV Network

[0413] Shared CHannel mMTCmassive MTC, Functions MPRACH MTC massive Machine- Virtualization Physical Random 50 Type Communications 85 NFVI NFV

[0414] Access CHannel MU-MIMO Multi Infrastructure MPUSCH MTC User MIMO NFVO NFV Physical Uplink Shared MWUS MTC Orchestrator

[0415] Channel wake-up signal, MTC NG Next Generation,

[0416] MPLS MultiProtocol 55 WUS 90 Next Gen Label Switching NACK Negative NGEN-DC NG-RAN MS Mobile Station Acknowledgement E-UTRA-NR Dual MSB Most Significant NAI Network Access Connectivity Bit Identifier NM Network

[0417] MSC Mobile 60 NAS Non-Access 95 Manager Switching Centre Stratum, Non- Access NMS Network MSI Minimum Stratum layer Management System System NCT Network N-PoP Network Point

[0418] Information, Connectivity Topology of Presence MCH Scheduling 65 NC-JT Non100 NMIB, N-MIB Information coherent Joint Narrowband MIB MSID Mobile Station Transmission NPBCH Identifier NEC Network Narrowband

[0419] MSIN Mobile Station Capability Exposure Physical

[0420] Identification 70 NE-DC NR-E- 105 Broadcast CHannel operation mode EXpense

[0421] NPDCCH NSD Network Service OSI Other System

[0422] Narrowband Descriptor Information

[0423] Physical NSR Network Service OSS Operations

[0424] Downlink 40 Record 75 Support System

[0425] Control CHannel NSS Al Network Slice OTA over-the-air

[0426] NPDSCH Selection PAPR Peak-to-Average

[0427] Narrowband Assistance Power Ratio

[0428] Physical Information PAR Peak to Average

[0429] Downlink 45 S-NNSAI Single- 80 Ratio

[0430] Shared CHannel NSSAI PBCH Physical

[0431] NPRACH NSSF Network Slice Broadcast Channel

[0432] Narrowband Selection Function PC Power Control,

[0433] Physical Random NW Network Personal

[0434] Access CHannel 50 NWDAF Network 85 Computer

[0435] NPUSCH Data Analytics PCC Primary

[0436] Narrowband Function Component Carrier,

[0437] Physical Uplink NWUSNarrowband Primary CC Shared CHannel wake-up signal, P-CSCF Proxy

[0438] NPSS Narrowband 55 Narrowband WUS 90 CSCF

[0439] Primary NZP Non-Zero Power PCell Primary Cell

[0440] Synchronization O&M Operation and PCI Physical Cell ID, Signal Maintenance Physical Cell

[0441] NSSS Narrowband ODU2 Optical channel Identity Secondary 60 Data Unit - type 2 95 PCEF Policy and

[0442] Synchronization OFDM Orthogonal Charging Signal Frequency Division Enforcement

[0443] NR New Radio, Multiplexing Function Neighbour Relation OFDMA PCF Policy Control NRF NF Repository 65 Orthogonal 100 Function Function Frequency Division PCRF Policy Control

[0444] NRS Narrowband Multiple Access and Charging Rules

[0445] Reference Signal OOB Out-of-band Function NS Network Service OOS Out of Sync PDCP Packet Data NSA Non-Standalone 70 OPEX OPerating 105 Convergence Protocol, Packet Data Network Function PSCCH Physical

[0446] Convergence PNFD Physical Sidelink Control Protocol layer Network Function Channel

[0447] PDCCH Physical Descriptor PSSCH Physical

[0448] Downlink Control 40 PNFR Physical 75 Sidelink Shared

[0449] Channel Network Function Channel

[0450] PDCP Packet Data Record PSFCH physical Convergence Protocol POC PTT over sidelink feedback PDN Packet Data Cellular channel Network, Public 45 PP, PTP Point-to- 80 PSCell Primary SCell

[0451] Data Network Point PSS Primary

[0452] PDSCH Physical PPP Point-to-Point Synchronization

[0453] Downlink Shared Protocol Signal

[0454] Channel PRACH Physical PSTN Public Switched

[0455] PDU Protocol Data 50 RACH 85 Telephone Network Unit PRB Physical PT-RS Phase-tracking

[0456] PEI Permanent resource block reference signal Equipment PRG Physical PTT Push-to-Talk

[0457] Identifiers resource block PUCCH Physical

[0458] PFD Packet Flow 55 group 90 Uplink Control Description ProSe Proximity Channel

[0459] P-GW PDN Gateway Services, PUSCH Physical

[0460] PHICH Physical Proximity-Based Uplink Shared hybrid-ARQ indicator Service Channel channel 60 PRS Positioning 95 QAM Quadrature

[0461] PHY Physical layer Reference Signal Amplitude PLMN Public Land PRR Packet Modulation Mobile Network Reception Radio QCI QoS class of

[0462] PIN Personal PS Packet Services identifier

[0463] Identification Number 65 PSBCH Physical 100 QCL Quasi coPM Performance Sidelink Broadcast location Measurement Channel QFI QoS Flow ID,

[0464] PMI Precoding PSDCH Physical QoS Flow Identifier Matrix Indicator Sidelink Downlink QoS Quality of

[0465] PNF Physical 70 Channel 105 Service QPSK Quadrature RI Rank Indicator ROHC RObust Header (Quaternary) Phase RIV Resource Compression Shift Keying indicator value RRC Radio Resource

[0466] QZSS Quasi-Zenith RL Radio Link Control, Radio

[0467] Satellite System 40 RLC Radio Link 75 Resource Control

[0468] RA-RNTI Random Control, Radio layer

[0469] Access RNTI Link Control RRM Radio Resource

[0470] RAB Radio Access layer Management

[0471] Bearer, Random RLC AM RLC RS Reference Signal

[0472] Access Burst 45 Acknowledged Mode 80 RSRP Reference Signal

[0473] RACH Random Access RLC UM RLC Received Power

[0474] Channel Unacknowledged Mode RSRQ Reference Signal

[0475] RADIUS Remote RLF Radio Link Received Quality

[0476] Authentication Dial In Failure RSSI Received Signal User Service 50 RLM Radio Link 85 Strength Indicator

[0477] RAN Radio Access Monitoring RSU Road Side Unit

[0478] Network RLM-RS RSTD Reference Signal

[0479] RAND RANDom Reference Signal Time difference number (used for for RLM RTP Real Time authentication) 55 RM Registration 90 Protocol

[0480] RAR Random Access Management RTS Ready-To-Send Response RMC Reference RTT Round Trip

[0481] RAT Radio Access Measurement Channel Time

[0482] Technology RMSI Remaining MSI, Rx Reception,

[0483] RAU Routing Area 60 Remaining 95 Receiving, Receiver Update Minimum S1AP SI Application

[0484] RB Resource block, System Protocol Radio Bearer Information SI -MME SI for

[0485] RBG Resource block RN Relay Node the control plane group 65 RNC Radio Network 100 Sl-U SI for the user

[0486] REG Resource Controller plane

[0487] Element Group RNL Radio Network S-CSCF serving

[0488] Rel Release Layer CSCF

[0489] REQ REQuest RNTI Radio Network S-GW Serving Gateway RF Radio Frequency 70 Temporary Identifier 105 S-RNTI SRNC Radio Network Transmission SGSN Serving GPRS Temporary Protocol Support Node

[0490] Identity SDAP Service Data S-GW Serving Gateway

[0491] S-TMSI SAE Adaptation Protocol, SI System

[0492] Temporary Mobile 40 Service Data 75 Information

[0493] Station Identifier Adaptation SI-RNTI System

[0494] SA Standalone Protocol layer Information RNTI operation mode SDL Supplementary SIB System SAE System Downlink Information Block Architecture 45 SDNF Structured Data 80 SIM Subscriber

[0495] Evolution Storage Network Identity Module

[0496] SAP Service Access Function SIP Session Initiated Point SDP Session Protocol

[0497] SAPD Service Access Description Protocol SiP System in

[0498] Point Descriptor 50 SDSF Structured Data 85 Package

[0499] SAPI Service Access Storage Function SL Sidelink

[0500] Point Identifier SDT Small Data SLA Service Level

[0501] SCC Secondary Transmission Agreement Component Carrier, SDU Service Data SM Session Secondary CC 55 Unit 90 Management

[0502] SCell Secondary Cell SEAF Security Anchor SMF Session

[0503] SCEF Service Function Management Function

[0504] Capability Exposure SeNB secondary eNB SMS Short Message Function SEPP Security Edge Service

[0505] SC-FDMA Single 60 Protection Proxy 95 SMSF SMS Function Carrier Frequency SFI Slot format SMTC SSB-based Division indication Measurement Timing

[0506] Multiple Access SFTD Space- Configuration

[0507] SCG Secondary Cell Frequency Time SN Secondary Node, Group 65 Diversity, SFN 100 Sequence Number

[0508] SCM Security Context and frame timing SoC System on Chip Management difference SON Self-Organizing

[0509] SCS Subcarrier SFN System Frame Network Spacing Number SpCell Special Cell

[0510] SCTP Stream Control 70 SgNB Secondary gNB 105 SP-CSI-RNTISemi- Persistent CSI RNTI Received Quality Configuration Indicator

[0511] SPS Semi-Persistent SS-SINR TCP Transmission

[0512] Scheduling Synchronization Communication

[0513] SQN Sequence Signal based Signal to Protocol number 40 Noise and Interference 75 TDD Time Division

[0514] SR Scheduling Ratio Duplex

[0515] Request SSS Secondary TDM Time Division

[0516] SRB Signalling Radio Synchronization Multiplexing Bearer Signal TDMATime Division

[0517] SRS Sounding 45 SSSG Search Space Set 80 Multiple Access

[0518] Reference Signal Group TE Terminal

[0519] SS Synchronization SSSIF Search Space Set Equipment

[0520] Signal Indicator TEID Tunnel End

[0521] SSB Synchronization SST Slice / Service Point Identifier

[0522] Signal Block 50 Types 85 TFT Traffic Flow

[0523] SSID Service Set SU-MIMO Single Template

[0524] Identifier User MIMO TMSI Temporary

[0525] SS / PBCH Block SUL Supplementary Mobile

[0526] SSBRI SS / PBCH Block Uplink Subscriber

[0527] Resource Indicator, 55 TA Timing 90 Identity

[0528] Synchronization Advance, Tracking TNL Transport

[0529] Signal Block Area Network Layer

[0530] Resource Indicator TAC Tracking Area TPC Transmit Power

[0531] SSC Session and Code Control

[0532] Service 60 TAG Timing Advance 95 TPMI Transmitted

[0533] Continuity Group Precoding Matrix

[0534] SS-RSRP TAI Tracking Indicator

[0535] Synchronization Area Identity TR Technical Report

[0536] Signal based TAU Tracking Area TRP, TRxP

[0537] Reference Signal 65 Update 100 Transmission

[0538] Received Power TB Transport Block Reception Point

[0539] SS-RSRQ TBS Transport Block TRS Tracking

[0540] Synchronization Size Reference Signal

[0541] Signal based TBD To Be Defined TRx Transceiver

[0542] Reference Signal 70 TCI Transmission 105 TS Technical Specifications, UMTS Universal V2X Vehicle-to-

[0543] Technical Mobile everything

[0544] Standard Telecommunicat VIM Virtualized

[0545] TTI Transmission ions System Infrastructure Manager

[0546] Time Interval 40 UP User Plane 75 VL Virtual Link,

[0547] Tx Transmission, UPF User Plane VLAN Virtual LAN,

[0548] Transmitting, Function Virtual Local Area

[0549] Transmitter URI Uniform Network

[0550] U-RNTI UTRAN Resource Identifier VM Virtual Machine

[0551] Radio Network 45 URL Uniform 80 VNF Virtualized

[0552] Temporary Resource Locator Network Function

[0553] Identity URLLC UltraVNFFG VNF

[0554] UART Universal Reliable and Low Forwarding Graph

[0555] Asynchronous Latency VNFFGD VNF

[0556] Receiver and 50 USB Universal Serial 85 Forwarding Graph

[0557] Transmitter Bus Descriptor

[0558] UCI Uplink Control USIM Universal VNFMVNF Manager Information Subscriber Identity VoIP Voice-over- IP,

[0559] UE User Equipment Module Voice-over- Internet

[0560] UDM Unified Data 55 USS UE- specific 90 Protocol

[0561] Management search space VPLMN Visited

[0562] UDP User Datagram UTRA UMTS Public Land Mobile

[0563] Protocol Terrestrial Radio Network

[0564] UDSF Unstructured Access VPN Virtual Private

[0565] Data Storage Network 60 UTRAN Universal 95 Network Function Terrestrial Radio VRB Virtual Resource

[0566] UICC Universal Access Network Block

[0567] Integrated Circuit UwPTS Uplink WiMAX

[0568] Card Pilot Time Slot Worldwide

[0569] UL Uplink 65 V2I Vehicle-to- 100 Interoperability

[0570] UM Infrastruction for Microwave

[0571] Unacknowledge V2P Vehicle-to- Access d Mode Pedestrian WLANWireless Local

[0572] UML Unified V2V Vehicle-to- Area Network

[0573] Modelling Language 70 Vehicle 105 WMAN Wireless Metropolitan Area

[0574] Network

[0575] WPANWireless

[0576] Personal Area Network X2-C X2-Control plane

[0577] X2-U X2-User plane

[0578] XML extensible

[0579] Markup Language

[0580] XRES EXpected user

[0581] RESponse

[0582] XOR exclusive OR

[0583] ZC Zadoff-Chu ZP Zero Power

[0584] Terminology

[0585] For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0586] The term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment. The term “AFML application” or the like may be an application that contains some AI / ML models and application-level descriptions.

[0587] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0588] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and / or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

[0589] The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I / O interfaces, peripheral component interfaces, network interface cards, and / or the like.

[0590] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless / wired device or any computing device including a wireless communications interface.

[0591] The term “network element” as used herein refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

[0592] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and / or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled with one another and configured to share computing and / or networking resources.

[0593] The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

[0594] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and applications, workload units, and / or the like. A “hardware resource” may refer to compute, storage, and / or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and / or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices / systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0595] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and / or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and / or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0596] The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

[0597] The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and / or the like.

[0598] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

[0599] The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

[0600] The term “SSB” refers to an SS / PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0601] The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

[0602] The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

[0603] The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.

[0604] The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA / DC there is only one serving cell comprising of the primary cell.

[0605] The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA / .

[0606] The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

[0607] The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and / or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.

[0608] The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

Claims

CLAIMS1. An apparatus of a user equipment (UE), the apparatus comprising: a memory to store configuration information to indicate that dynamic transform precoder indication is present in a downlink control information (DCI) format for an active uplink (UL) bandwidth part (BWP) of a serving cell; and processor circuity coupled to the memory, the processor circuitry to: generate, based on the configuration information, first power headroom information associated with a transform precoder being disabled and second power headroom information associated with the transform precoder being enabled; and report the first and second power headroom information to a next generation Node B (gNB).

2. The apparatus of claim 1, wherein a first one of the first or second power headroom information is generated based on an actual physical uplink shared channel (PUSCH) transmission and a second one of the first or second power headroom information is generated based on an assumed PUSCH transmission.

3. The apparatus of claim 2, wherein the processor circuitry is further to decode a DCI that includes an indication of whether the transform precoder is enabled for the actual PUSCH transmission.

4. The apparatus of claim 3, wherein the DCI is a DCI format 0_l or 0_2.

5. The apparatus of claim 1, wherein the first and second power headroom information is reported in a same medium access control - control element (MAC-CE).

6. The apparatus of claim 1, wherein at least one of the first or second power headroom information includes a maximum output power reduction value, PCMAX C (i).

7. The apparatus of any one of claims 1-6, wherein the processor circuitry is to disable the transform precoder to transmit a cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) waveform, and is to enable the transform precoder to transmit a discrete Fourier Transform- spread-OFDM (DFT-s-OFDM) waveform.

8. One or more computer-readable media having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE), configure the UE to: receive configuration information to indicate that a downlink control information (DCI) is to include an indication of whether a transform precoder is enabled or disabled; generate first power headroom information based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information; generate second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on the transform precoder being disabled if the transform precoder is enabled for the actual PUSCH transmission and is generated based on the transform precoder being enabled if the transform precoder is disabled for the actual PUSCH transmission; and report the first and second power headroom information to a next generation Node B (gNB).

9. The one or more computer-readable media of claim 7, wherein the DCI is a DCI format 0_l or 0_2.

10. The one or more computer-readable media of claim 7, wherein the first and second power headroom information is reported in a same medium access control - control element (MAC-CE).

11. The one or more computer-readable media of claim 7, wherein the transform precoder is disabled to transmit the PUSCH transmission with a cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) waveform, and is to enabled to transmit the PUSCH transmission with a discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform.

12. The one or more computer-readable media of claim 7, wherein the instructions, when executed, further configure the UE to receive the assumed PUSCH information from the gNB.

13. The one or more computer-readable media of any one of claims 7-12, wherein the second power headroom information includes a maximum output power reduction value, PcMAX.f.c (i).

14. One or more computer-readable media having instructions, stored thereon, thatwhen executed by one or more processors of a next generation Node B (gNB), configure the gNB to: encode, for transmission to a user equipment (UE), configuration information to indicate that a downlink control information (DCI) is to include an indication of whether a transform precoder is enabled or disabled; and receive, from the UE, first power headroom information based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information, and second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on the transform precoder being disabled if the transform precoder is enabled for the actual PUSCH transmission and is generated based on the transform precoder being enabled if the transform precoder is disabled for the actual PUSCH transmission.

15. The one or more computer-readable media of claim 14, wherein the DCI is a DCI format 0_l or 0_2.

16. The one or more computer-readable media of claim 14, wherein the first and second power headroom information is received in a same medium access control - control element (MAC-CE).

17. The one or more computer-readable media of claim 14, wherein when the DCI indicates that the transform precoder is disabled the UE is to transmit the PUSCH transmission with a cyclic prefix (CP) - orthogonal frequency-division multiplexing (OFDM) waveform, and wherein when the DCI indicates that the transform precoder is enabled the UE is to transmit the PUSCH transmission with a discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform.

18. The one or more computer-readable media of claim 14, wherein the instructions, when executed, further configure the gNB to transmit, to the UE, the DCI with the indication of whether the transform precoder is enabled or disabled.

19. The one or more computer-readable media of any one of claims 14-18, wherein the instructions, when executed, further configure the gNB to transmit, to the UE, the assumed PUSCH information.

20. The one or more computer-readable media of any one of claims 14-18, wherein the second power headroom information includes a maximum output power reduction value,PcMAX.f.c (1).

Citation Information

Patent Citations

  • Methods for communication, terminal device, network device and computer-readable media

    WO2022027485A1