System and method for auxiliary information for dynamic waveform switching

Abstract

Various embodiments herein provide techniques for assistance information to facilitate dynamic waveform switching. For example, a user equipment (UE) may generate and transmit a power headroom report with power headroom information with transform precoder disablement (e.g., for cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveforms) and with transform precoder enablement (e.g., for discrete Fourier transform-spread spectrum-OFDM (DFT-s-OFDM) waveforms). Other embodiments may be described and claimed.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 501,586, filed May 11, 2023, and U.S. Provisional Patent Application No. 63 / 517,287, filed August 2, 2023. Background Technology

[0003] For cellular systems, coverage is a critical factor for successful operation. Compared to Long Term Evolution (LTE), New Radio (NR) can be deployed at relatively high carrier frequencies (e.g., 3.5 GHz) within Frequency Range 1 (FR1). In this case, coverage loss is expected due to greater path loss, making it more challenging to maintain adequate quality of service. Typically, uplink coverage is a bottleneck for system operation, given the low transmit power at the User Equipment (UE) side. Attached Figure Description

[0004] The embodiments will be readily understood from the following detailed description taken in conjunction with the accompanying drawings. For ease of this description, similar reference numerals designate similar structural elements. The embodiments are illustrated in the accompanying drawings by way of example rather than limitation.

[0005] Figure 1 Examples of media access control-control element (MAC-CE) for power headroom report (PHR) for dynamic waveform switching are illustrated according to various embodiments.

[0006] Figure 2 Another example of a MAC-CE for a PHR used for dynamic waveform switching, according to various embodiments, is illustrated.

[0007] Figure 3 Another example of a MAC-CE for a PHR used for dynamic waveform switching, according to various embodiments, is illustrated.

[0008] Figure 4 Another example of a MAC-CE for a PHR used for dynamic waveform switching, according to various embodiments, is illustrated.

[0009] Figure 5 An example of a MAC-CE for a PHR used for dynamic waveform switching and multiple transmit / receive points (TRPs) is illustrated according to various embodiments.

[0010] Figure 6 Another example of a MAC-CE for a PHR used for dynamic waveform switching and multiple TRPs, according to various embodiments, is illustrated.

[0011] Figure 7Examples of multi-entry PHRs for dynamic waveform switching according to various embodiments are illustrated.

[0012] Figure 8 Wireless networks according to various embodiments are schematically illustrated.

[0013] Figure 9 The components of a wireless network according to various embodiments are schematically illustrated.

[0014] Figure 10 This is a block diagram illustrating any one or more components, according to some example embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-volatile machine-readable storage medium) and performing the methods discussed herein.

[0015] Figure 11 The diagram illustrates networks according to various embodiments.

[0016] Figure 12 Example flows for practicing the various embodiments discussed herein are described.

[0017] Figure 13 Another example flow is described for practicing the various embodiments discussed herein.

[0018] Figure 14 Another example flow is described for practicing the various embodiments discussed herein. Detailed Implementation

[0019] The following detailed description relates to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details (such as particular structures, architectures, interfaces, technologies, etc.) are set forth for purposes of explanation and non-limitation in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art who will benefit from this disclosure that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some instances, descriptions of well-known devices, circuits, and methods have been omitted to avoid unnecessary detail that could obscure the description of the various embodiments. For the purposes of this document, the phrases “A or B” and “A / B” mean (A), (B), or (A and B).

[0020] Various embodiments herein provide techniques for providing auxiliary information to facilitate dynamic waveform switching. For example, user equipment (UE) can generate and transmit a power headroom report with power headroom information when the transform precoder is disabled (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveforms) and when the transform precoder is enabled (e.g., for discrete Fourier transform-spread spectrum-OFDM (DFT-s-OFDM) waveforms).

[0021] In NR, system design is based on waveform selection: CP-OFDM for downlink (DL) or CP-OFDM or DFT-s-OFDM for uplink (UL). Note that DFT-s-OFDM waveforms are implemented by enabling transform precoding on the transmitter side. When transform precoding is disabled, CP-OFDM waveforms are used for PUSCH transmission. Typically, DFT-s-OFDM waveforms achieve better uplink coverage performance compared to CP-OFDM waveforms due to their lower peak-to-average power ratio (PAPR).

[0022] For cell-edge UEs with poor channel conditions, DFT-s-OFDM waveforms are more suitable for PUSCH transmission due to their low PAPR, thus achieving better coverage. However, for cell-center UEs with high SNR, CP-OFDM waveforms are more advantageous because they can support UL multiple-input multiple-output (MIMO) with high-order transmission, providing high data rates and improving system capacity.

[0023] To fully utilize the benefits of DFT-s-OFDM or CP-OFDM waveforms for PUSCH transmission, dynamic switching of waveform types is supported for PUSCH transmission. To enable dynamic waveform switching, auxiliary information regarding power headroom (PH) can be reported from the UE, allowing the gNB to make appropriate decisions for the UE's waveform selection.

[0024] Various embodiments herein provide systems and methods related to auxiliary information for dynamic waveform switching.

[0025] Auxiliary information for dynamic waveform switching

[0026] As mentioned above, for cell-edge UEs with poor channel conditions, the low PAPR makes DFT-s-OFDM waveforms more suitable for PUSCH transmission, thus achieving better coverage. Conversely, for cell-center UEs with high SNR, CP-OFDM waveforms are more advantageous because they can support UL MIMO with high-order transmission, providing high data rates and improving system capacity.

[0027] To fully utilize the benefits of DFT-s-OFDM or CP-OFDM waveforms for PUSCH transmission, dynamic switching of waveform types is supported for PUSCH transmission. To enable dynamic waveform switching, auxiliary information regarding power headroom (PH) can be reported from the UE, allowing the gNB to make appropriate decisions for the UE's waveform selection.

[0028] Examples of auxiliary information used for dynamic waveform switching are described further below.

[0029] In one embodiment, the power headroom report (PHR) for both CP-OFDM and DFT-s-OFDM waveforms may be included in a single media access control-control element (MAC-CE).

[0030] In some aspects, whether the PHR for both CP-OFDM and DFT-s-OFDM waveforms is included in a single MAC-CE can be configured by a higher layer via Radio Resource Control (RRC) signaling. Alternatively, whether the PHR for dynamic waveform switching is reported can be determined based on whether dynamic waveform switching for DCI formats 0_1 and / or 0_2 is configured in the active UL BWP. For example, when dynamic waveform switching is configured for one of DCI formats 0_1 and 0_2, the PHR for both CP-OFDM and DFT-s-OFDM waveforms is included in a single MAC-CE. This also applies to the case of dynamic waveform switching and multiple TRPs.

[0031] In one option, the existing process can be reused to determine whether the PHR is an actual PHR or a virtual PHR, regardless of whether the PUSCH transmission in slot n is based on a CP-OFDM waveform or a DFT-s-OFDM waveform. Furthermore, the determined PHR type (actual PHR or virtual PHR) can be applied to both CP-OFDM and DFT-s-OFDM waveforms.

[0032] In some respects, a real PHR refers to a PHR used for actual PUSCH transmission, while a virtual PHR refers to a PHR with a reference PUSCH.

[0033] In another option, existing procedures can be reused to determine whether the PHR is an actual PHR or a virtual PHR based on the indicator waveform used for PUSCH transmission in slot n. Furthermore, the determined PHR type (actual PHR or virtual PHR) can be applied to both CP-OFDM and DFT-s-OFDM waveforms.

[0034] In another option, existing procedures can be reused to determine whether a PHR is an actual PHR or a virtual PHR. Furthermore, when a PHR is determined to be a virtual PHR, only a single entry PHR is included in the MAC-CE. In one example, the virtual PHR is determined based on the indicator waveform used for PUSCH transmission in slot n.

[0035] Figure 1 The illustration shows an example of a PHR used for dynamic waveform switching MAC-CE. Figure 1The aspects of MAC-CE include:

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

[0037] · Figure 1 Other fields in the MAC-CE can be reused as defined in Clause 6.1.3.50 of TS 38.321.

[0038] In another example, only the actual PHR is included in MAC-CE. Figure 2 Another example of a PHR used for dynamic waveform switching MAC-CE is illustrated. Figure 2 The aspects of MAC-CE include:

[0039] • Power headroom i (PH i): This field indicates the power headroom level, where PH 1 is related to the DFT-s-OFDM waveform and PH 2 is related to the CP-OFDM waveform, or vice versa. The PH field used for the serving cell is based on i.

[0040] Ascending order is included. The field length is 6 digits. The reported pH and corresponding power margin level 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 MAC-CE can be reused as defined in Clause 6.1.3.50 of TS 38.321.

[0042] In another example, the different maximum transmit powers for CP-OFDM waveforms and DFT-s-OFDM waveforms can be included in the PHR within a single MAC-CE. Figure 3 Another example of a PHR used for dynamic waveform switching MAC-CE is illustrated. Figure 3 The aspects of MAC-CE include:

[0043] ·P CMAX,f,c i: This field indicates the previous calculations used for DFT-s-OFDM and CP-OFDM waveforms, respectively.

[0044] PCMAX,f,c of the PH field (as specified in TS 38.213[6]).

[0045] In another example, the actual PHR for a single waveform is included in the new MAC-CE for dynamic waveform switching.

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

[0047] In another option, the waveform used for PHR can be determined based on predefined rules. In one example, the waveform is the same as the waveform indicated or activated in the DCI or configured by a higher layer. In another example, the waveform is different from the waveform indicated or activated in the DCI or configured by a higher layer. In yet another example, the waveform is determined to have either the smaller or larger value of the PH from the CP-OFDM waveform and the DFT-s-OFDM waveform.

[0048] Figure 4 Another example of a PHR used for dynamic waveform switching MAC-CE is illustrated. Figure 4 The aspects of MAC-CE include:

[0049] • W: This field indicates the waveform type. If PH is used for a CP-OFDM waveform, the MAC entity should set the W field to 1, and if PH is used for a DFT-s-OFDM waveform, the MAC entity should set the W field to 0, or vice versa.

[0050] • Power margin i (PH i): This field indicates the power margin level used to indicate the waveform.

[0051] In one embodiment, a new Enhanced Logical Channel ID (eLCID) can be defined for a new MAC-CE carrying a PHR for dynamic waveform switching. In some aspects, the eLCID can be defined for a single-entry PHR for dynamic waveform switching, a multi-entry PHR for dynamic waveform switching, or a PHR1 for dynamic waveform switching and multiple TRPs.

[0052] In another embodiment, when multiple transmit-receive point (TRP) operation is used for PUSCH repetition (e.g., for configuring component carriers (CC) with multiple TRP PUSCH repetition), the PHR for both the CP-OFDM waveform and the DFT-s-OFDM waveform used for PUSCH transmission, targeting both the first TRP and the second TRP, can be reported in a single MAC-CE for dynamic waveform switching.

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

[0054] Figure 5 An example of a PHR used for dynamic waveform switching and multi-TRP MAC-CE is illustrated. Figure 5 The aspects of MAC-CE include:

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

[0056] Other fields in MAC-CE can be reused as defined in Clause 6.1.3.50 of TS38.321.

[0057] In another option, two power margin levels are included in a single PHR for both multi-TRP and dynamic waveform switching, which are used for PUSCH repetition of the first TRP and the second TRP for a waveform, respectively.

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

[0059] In another option, the waveform for the PHR used for each TRP can be determined based on predefined rules. In one example, the waveform is the same as the waveform indicated or activated in the DCI or configured by a higher layer. In another example, the waveform is different from the waveform indicated or activated in the DCI or configured by a higher layer. In yet another example, the waveform is determined to have either the smaller or larger value of the PH from the CP-OFDM waveform and the DFT-s-OFDM waveform.

[0060] Figure 6 An example of a PHR used for dynamic waveform switching and multi-TRP MAC-CE is illustrated. Figure 6 The aspects of MAC-CE include:

[0061] • W: This field indicates the waveform type. For each TRP, if the PH is used for a CP-OFDM waveform, the MAC entity should set the W field to 1, and if the PH is used for a DFT-s-OFDM waveform, the MAC entity should set the W field to 0, or vice versa.

[0062] • Power margin i (PH i): For each TRP, this field indicates the power margin level used to indicate the waveform, wherein, for the indicated waveform, PH 1 is associated with an SRSResourceSet with a lower srs-ResourceSetId, and PH 2 is associated with an SRSResourceSet with a higher srsResourceSetId.

[0063] • Other fields in the diagram may be reused as defined in Clause 6.1.3.50 of TS 38.321.

[0064] In another embodiment, when multiple TRP operations are used for PUSCH repetition (e.g., for configuring a CC with multiple TRP PUSCH repetitions), and if the UE does not support two PHRs for multiple TRP operations, and if the PHR report is an actual PHR, the UE uses the set of power control parameters corresponding to the earliest repetition, which overlaps with the first slot, in which the PUSCH carrying the PHR MAC-CE is transmitted. Furthermore, the UE includes PHRs for both the CP-OFDM waveform and the DFT-s-OFDM waveform used for dynamic waveform switching in the earliest repetition.

[0065] In another embodiment, when multiple TRP operations are used for PUSCH repetition (e.g., for configuring a CC with multiple TRP PUSCH repetitions), and if the PHR report is an actual PHR, the UE uses the set of power control parameters corresponding to the earliest repetition, which overlaps with the first slot, in which the PUSCH carrying the PHR MAC-CE is transmitted. Furthermore, the UE includes the PHR in the earliest repetition for both the CP-OFDM waveform and the DFT-s-OFDM waveform used for dynamic waveform switching.

[0066] In another embodiment, when multiple TRP operations are used for PUSCH repetition (e.g., for a CC configured with mTRP PUSCH repetition), existing mechanisms can be reused to determine the actual and virtual PHRs for PUSCH repetition, targeting the first and second TRPs. Furthermore, the determined PHR type (actual or virtual PHR) can be tailored to both the CP-OFDM waveform and the DFT-s-OFDM waveform applicable to the PUSCH for the first or second TRP, respectively.

[0067] In one example, if the first PHR value is determined to be the actual PHR corresponding to a repetition among multiple TRP PUSCH repetitions associated with the first TRP, then the actual PHR applies to both the CP-OFDM waveform and the DFT-s-OFDM waveform. Furthermore, if the second PHR value is determined to be the virtual PHR corresponding to a repetition among multiple TRP PUSCH repetitions associated with the second TRP, then the virtual PHR applies to both the CP-OFDM waveform and the DFT-s-OFDM waveform.

[0068] In another embodiment, the multi-entry PHR MAC CE can be extended to include PHRs for both CP-OFDM and DFT-s-OFDM waveforms for one or more carriers. Specifically, for carriers configured with dynamic waveform switching, the PHR in the carrier can include PHRs for both CP-OFDM and DFT-s-OFDM waveforms according to the embodiments described above.

[0069] In another option, it is possible to determine whether the PHR for dynamic waveform switching is reported on the carrier, depending on whether dynamic waveform switching is configured for DCI format 0_1 ​​and / or 0_2 in one of the UL BWPs or the active UL BWP, or in the carrier. In one example, if dynamic waveform switching is configured in one of the UL BWPs on the carrier with either DCI format 0_1 ​​or DCI format 0_2, the PHR for dynamic waveform switching is reported on the carrier.

[0070] Figure 7The illustration shows an example of a multi-entry PHR with a dynamic waveform switching MAC CE. Figure 7 In the MAC CE, the PHR for both the CP-OFDM waveform and the DFT-s-OFDM waveform for PCell is included.

[0071] In one option, waveform indication and PH for indicating or determining waveforms can be included in a carrier for a multi-entry PHR with dynamic waveform switching. As described above, the carrier can be configured with dynamic waveform switching, or dynamic waveform switching can be configured in one of the UL BWP or active UL BWP or in the carrier for DCI formats 0_1 and / or 0_2.

[0072] In another embodiment, the enhanced multi-entry PHR for multiple TRP MAC CEs can be extended to include PHRs for both CP-OFDM and DFT-s-OFDM waveforms for one or more carriers. Specifically, for carriers configured with dynamic waveform switching, the PHR in the carrier can include PHRs for both CP-OFDM and DFT-s-OFDM waveforms according to the foregoing embodiments.

[0073] System and Implementation

[0074] Figures 8-11 Various systems, devices, and components that can implement aspects of the disclosed embodiments are illustrated.

[0075] Figure 8 The illustration depicts a network 800 according to various embodiments. The network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited to this, and the described embodiments are applicable to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0076] Network 800 may include UE 802, which may include any mobile or non-mobile computing device designed to communicate with RAN 804 via a wireless connection. UE 802 may be communicatively coupled to RAN 804 via a Uu interface. UE 802 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment systems, in-vehicle entertainment devices, dashboards, head-up displays, in-vehicle diagnostic equipment, desktop mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, connected appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0077] In some embodiments, network 800 may include multiple UEs that are directly coupled to each other via sidelink ports. 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.).

[0078] In some embodiments, UE 802 may also additionally communicate with AP 806 via a wireless connection. AP 806 can manage WLAN connections that can be used to offload some / all network traffic from RAN 804. The connection between UE 802 and AP 806 can conform to any IEEE 802.11 protocol, wherein AP 806 can provide wireless fidelity. Router. In some embodiments, UE 802, RAN 804, and AP 806 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE 802 configured by RAN 804 to utilize both cellular radio resources and WLAN resources simultaneously.

[0079] RAN 804 may include one or more access nodes, such as AN 808. AN 808 may terminate the air interface protocol for UE 802 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 808 enables data / voice connectivity between CN 820 and UE 802. In some embodiments, AN 808 may be implemented in discrete devices or as one or more software entities running on a server computer that is, for example, part of a virtual network, which may be referred to as CRAN or a virtual baseband unit pool. AN 808 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 808 may serve as a macro cell base station or as a low-power base station for providing smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells, such as femtocells, picocells, or other similar cells.

[0080] In embodiments where RAN 804 includes multiple ANs, the multiple ANs can be coupled to each other via an X2 interface (in the case of RAN 804 being an LTE RAN) or an Xn interface (in the case of RAN 804 being a 5G RAN). In some embodiments, the X2 interface / Xn interface, which can be divided into a control plane interface / user plane interface, allows ANs to transmit and handover, data / context transfer, mobility, load management, interference coordination, and other related information.

[0081] Multiple ANs within RAN 804 can each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 802. UE 802 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 804. For example, UE 802 and RAN 804 can use carrier aggregation to allow UE 802 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual-connectivity scenario, the first AN can be the primary node providing the MCG, and the second AN can be the secondary node providing the SCG. The first AN / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0082] RAN 804 provides an air interface via licensed or unlicensed spectrum. To operate on unlicensed spectrum, nodes can use LAA, eLAA, and / or feLAA mechanisms with PCell / Scell ​​based on CA technology. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-After-Speak (LBT) protocol.

[0083] In V2X scenarios, UE 802 or AN 808 can be or act as an RSU, where RSU can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," and an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside providing connectivity support for passing vehicle UEs. An RSU may also include: internal data storage circuitry for storing intersection map geometry, traffic statistics, and media; and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide very low-latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, an RSU can provide other cellular communication services / WLAN communication services. RSU components may be housed in a waterproof enclosure suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0084] In some embodiments, RAN 804 may be an LTE RAN 810 with an eNB (e.g., eNB 812). The LTE RAN 810 provides an LTE air interface with the following characteristics: a 15 kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbocodes for data and TBCCs 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 channel estimation for cell search and initial acquisition, channel quality measurement, and coherent demodulation / detection at the UE. The LTE air interface may operate in the sub-6 GHz band.

[0085] In some embodiments, RAN 804 may be an NG-RAN 814 having a gNB (e.g., gNB 816) or an ng-eNB (e.g., ng-eNB 818). gNB 816 can connect to a 5G-enabled UE using a 5G NR interface. gNB 816 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 818 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 816 and ng-eNB 818 can connect to each other via an Xn interface.

[0086] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between nodes of NG-RAN 814 and nodes of UPF 848; and an NG control plane (NG-C) interface (e.g., N2 interface) that serves as the signaling interface between nodes of NG-RAN 814 and nodes of AMF 844.

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

[0088] In some embodiments, the 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 802 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 802 for a change, the transmitted SCS also changes. Another example of BWP use cases relates to energy saving. Specifically, multiple BWPs can be configured for UE 802 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs containing a smaller number of PRBs can be used for data transmission with low traffic loads while allowing energy savings at UE 802, and in some cases, energy savings at gNB 816. BWPs containing a larger number of PRBs can be used for scenarios with high traffic loads.

[0089] RAN 804 is communicatively coupled to CN 820, which includes network elements that provide various functions to support the delivery of data and telecommunications services to customers / subscribers (e.g., users of UE 802). Components of CN 820 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of CN 820 onto physical compute / storage resources in servers, switches, etc. Logical instances of CN 820 may be referred to as network slices, and logical instances of a portion of CN 820 may be referred to as network subslices.

[0090] In some embodiments, CN 820 may be an LTE CN 822, also referred to as EPC. The LTE CN 822 may include MME 824, SGW 826, SGSN 828, HSS 830, PGW 832, and PCRF 834 coupled to each other via an interface (or “reference point”) as shown in the figure. The functions of the components of the LTE CN 822 can be briefly described below.

[0091] The MME 824 enables mobility management functions to track the current location of the UE 802, thereby facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0092] The SGW 826 can terminate the S1 interface to the RAN and route data packets between the RAN and the LTE CN 822. The SGW 826 can serve as a local mobility anchor for handover between RAN nodes and also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0093] The SGSN 828 can track the location of UE 802 and perform security functions and access control. Furthermore, the SGSN 828 can perform EPC inter-node signaling for movement between different RAT networks; such as PDN and S-GW selection as specified by MME 824; and MME selection for handover. The S3 reference point between MME 824 and SGSN 828 can enable user and bearer information exchange for 3GPP access network movement in idle / active states.

[0094] The HSS 830 may include a database for network users, including subscription-related information supporting communication session processing for network entities. The HSS 830 provides support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. The S6a reference point between the HSS 830 and the MME 824 enables the transmission of subscription and authentication data for authenticated / authorized user access to the LTE CN 820.

[0095] The PGW 832 can terminate the SGi interface to a data network (DN) 836, which may include an application / content server 838. The PGW 832 can route data packets between the LTE CN 822 and the data network 836. The PGW 832 can be coupled to the SGW 826 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 832 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Furthermore, the SGi reference point between the PGW 832 and the data network 836 can be an external public network, a private PDN, or an inter-carrier packet data network, for example, for providing IMS services. The PGW 832 can be coupled to the PCRF 834 via a Gx reference point.

[0096] PCRF 834 is the policy and charging control element of LTE CN 822. PCRF 834 can be communicatively coupled with application / content server 838 to determine appropriate QoS and charging parameters for service flows. PCRF 832 can provide relevant rules (via Gx reference point) to PCEF with appropriate TFT and QCI.

[0097] In some embodiments, CN 820 may be 5GC 840. 5GC 840 may include AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, and AF 860 coupled to each other via interfaces (or "reference points") as shown. The functionality of the components of 5GC 840 can be briefly described below.

[0098] The AUSF 842 stores data for UE 802 authentication and handles authentication-related functions. The AUSF 842 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC 840 via the reference point shown in the figure, the AUSF 842 also provides an interface based on Nausf services.

[0099] The AMF 844 allows the 5GC 840 to communicate with UE 802 and RAN 804, and to subscribe to notifications regarding mobility events related to UE 802, among other functions. The AMF 844 is responsible for registration management (e.g., for registering UE 802), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 844 provides for the transmission of SM messages between UE 802 and SMF 846, and acts as a transparent broker for routing SM messages. The AMF 844 also provides for the transmission of SMS messages between UE 802 and the SMSF. The AMF 844 can interact with AMF 842 and UE 802 to perform various security anchoring and context management functions. Furthermore, the AMF 844 can serve as the termination point for the RAN CP interface, which may include or be the N2 reference point between the RAN 804 and the AMF 844. The AMF 844 can also serve as the termination point for NAS (N1) signaling and performs NAS encryption and integrity protection. The AMF 844 can also support NAS signaling interaction with the UE 802 via the N3 IWF interface.

[0100] SMF 846 may be responsible for: SM (e.g., session establishment and tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic orientation at UPF 848 to route traffic to the appropriate destination; termination of interfaces for policy control functions; control policy enforcement, charging, and QoS portions; lawful interception (interfaces for SM events and LI systems); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN 808 via AMF 844 through N2; and determining the SSC mode of the session. SM may refer to the management of PDU sessions, and a PDU session or "session" may refer to the PDU connectivity service that provides or enables the exchange of PDUs between UE 802 and data network 836.

[0101] The UPF 848 can serve as an anchor point for movement within and between RATs, an external PDU session point for interconnection with the data network 836, and a branch point supporting multihomed PDU sessions. The UPF 848 can also perform packet routing and forwarding, packet inspection, enforcement of policy rules in the user plane portion, lawful packet interception (UP collection), traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gate control, UL / DL rate enforcement), uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport class packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 848 may include an uplink classifier that supports routing traffic flows to the data network.

[0102] The NSSF 850 ​​can select the set of network slice instances serving UE 802. If needed, the NSSF 850 ​​can also determine the allowed NSSAIs and the mapping to subscribed S-NSSAIs. The NSSF 850 ​​can also determine the set of AMFs used to serve UE 802, or determine a list of candidate AMFs based on appropriate configuration and probabilities by querying the NRF 854. The selection of the set of network slice instances for UE 802 can be triggered by the AMF 844, with which UE 802 is registered by interacting with the NSSF 850, which may result in a change of AMF. The NSSF 850 ​​can interact with the AMF 844 via the N22 reference point and can communicate with another NSSF in the access network via the N31 reference point (not shown). Furthermore, the NSSF 850 ​​can provide an interface based on NNSSF services.

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

[0104] NRF 854 supports service discovery, receives NF discovery requests from NF instances, and provides information about discovered NF instances to the NF instances. NRF 854 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiation," "instantiation process," etc., may refer to the creation of an instance, and "instance" may refer to the concrete occurrence of an object, such as during the execution of program code. Additionally, NRF 854 provides an interface to Nnrf-based services.

[0105] The PCF 856 can provide policy rules to control plane functions to enforce policy rules and also supports a unified policy framework for managing network behavior. The PCF 856 also provides a front-end for accessing subscription information related to policy decisions in the UDR of the UDM 858. In addition to communicating with functions via reference points as shown in the figure, the PCF 856 also provides an interface based on Npcf services.

[0106] UDM 858 can process subscription-related information to support communication session processing for network entities and can store subscription data for UE 802. For example, subscription data can be communicated between UDM 858 and AMF 844 via the N8 reference point. UDM 858 may include two parts: an application front-end and a UDR. The UDR can store subscription and policy data for UDM 858 and PCF 856, and / or structured data for exposure and application data for NEF 852 (including PFD for application detection and application request information for multiple UE 802). An interface based on the Nudr service may be provided by UDR 221 to allow UDM 858, PCF 856, and NEF 852 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. UDM may include UDM-FE responsible for handling certificates, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication certificate processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via the reference point shown in the figure, the UDM 858 also provides an interface based on Nudm services.

[0107] The AF860 can provide application impact on traffic routing, provide access to NEF, and interact with the policy framework to achieve policy control.

[0108] In some embodiments, the 5GC 840 can implement edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 802 is attached to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC 840 can select a UPF 848 close to the UE 802 and perform traffic routing from the UPF 848 to the data network 836 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 can influence UPF (re)selection and traffic routing. Based on operator deployment, when the AF 860 is considered a trusted entity, the network operator can allow the AF 860 to interact directly with the associated NF. Additionally, the AF 860 can provide an interface based on Naf services.

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

[0110] Figure 9 A wireless network 900 according to various embodiments is schematically illustrated. The wireless network 900 may include a UE 902 that communicates wirelessly with an AN 904. The UE 902 and the AN 904 may be similar to, and are substantially interchangeable with, similarly named components described elsewhere herein.

[0111] UE 902 can be communicatively coupled to AN 904 via connection 906. Connection 906 is illustrated as an air interface for communication coupling and is compliant with cellular communication protocols such as LTE or 5G NR protocols operating at millimeter wave or sub-6 GHz frequencies.

[0112] UE 902 may include a host platform 908 coupled to a modem platform 910. Host platform 908 may include application processing circuitry 912, which may be coupled to protocol processing circuitry 914 of modem platform 910. Application processing circuitry 912 may run various applications for UE 902, with application data originating from / aggregated from various applications. Application processing circuitry 912 may also implement one or more layer operations to transmit application data to / receive application data from a data network. These layer operations may include transport (e.g., UDP) operations and Internet (e.g., IP) operations.

[0113] Protocol processing circuitry 914 can implement one or more layer operations to facilitate data transmission or reception via connection 906. Layer operations implemented by protocol processing circuitry 914 may include, for example, MAC operations, RLC operations, PDCP operations, RRC operations, and NAS operations.

[0114] The modem platform 910 may also include digital baseband circuitry 916, which may be implemented as one or more layer operations of "lower" layer operations performed by protocol processing circuitry 914 in the network protocol stack. These operations may include, for example, PHY operations, which include one or more of the following functions: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, 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, blind decoding of control channel signals, and other related functions.

[0115] The modem platform 910 may also include a transmitting circuit 918, a receiving circuit 920, an RF circuit 922, and an RF front-end (RFFE) 924 that may be included in or connected to one or more antenna panels 926. In short, the transmitting circuit 918 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 920 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 922 may include a low-noise amplifier, a power amplifier, a power point tracking component, etc.; and the RFFE 924 may include filters (e.g., surface acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components of the transmitting circuit 918, the receiving circuit 920, the RF circuit 922, the RFFE 924, and the antenna panel 926 (collectively referred to as the "transmit / receive assembly") may be specific to the details of the specific implementation, such as whether the communication is TDM or FDM, or whether the communication is at millimeter wave or sub-6 GHz frequencies. In some embodiments, the transmit / receive components may be arranged into multiple parallel transmit / receive links, which may be located in the same or different chips / modules, etc.

[0116] In some embodiments, the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) that provides control functions over the transmit / receive components.

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

[0118] UE transmission can be established via and through protocol processing circuitry 914, digital baseband circuitry 916, transmission circuitry 918, RF circuitry 922, RFFE 924, and antenna panel 926. In some embodiments, the transmission assembly of UE 904 may apply a spatial filter to the data to be transmitted to form a transmission beam transmitted by the antenna elements of antenna panel 926.

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

[0120] Figure 10 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-volatile machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. Specifically, Figure 10 A schematic representation of hardware resource 1000 is shown, comprising 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 is communicatively coupled via bus 1040 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), an executable hypervisor 1002 provides an execution environment for one or more network slices / subslices, thereby utilizing hardware resource 1000.

[0121] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 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 radio frequency integrated circuit (RFIC), another processor (including the processors discussed herein), or any suitable combination thereof.

[0122] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 may include, but is 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 memory, etc.

[0123] Communication resource 1030 may include an interconnect or network interface controller, component, or other suitable device that communicates via network 1008 with one or more peripheral devices 1004 or one or more databases 1006 or other network elements. For example, communication resource 1030 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, etc. (or Low-power components Components and other communication components.

[0124] Instructions 1050 may include software, programs, applications, applets, apps, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methods discussed herein. Instructions 1050 may reside wholly or partially within at least one of the processors 1010 (e.g., within the processor's buffer memory), memory / storage device 1020, or any suitable combination thereof. Furthermore, any portion of instructions 1050 may be transferred to hardware resource 1000 from any combination of peripheral device 1004 or database 1006. Therefore, the memory of processor 1010, memory / storage device 1020, peripheral device 1004, and database 1006 are examples of computer-readable and machine-readable media.

[0125] Figure 11A network 1100 is illustrated according to various embodiments. Network 1100 may operate in accordance with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, network 1100 may operate simultaneously with network 800. For example, in some embodiments, network 1100 may share one or more frequency or bandwidth resources with network 800. As a specific example, a UE (e.g., UE 1102) may be configured to operate in both network 1100 and network 800. This configuration may be based on a UE including circuitry configured to communicate with the frequency and bandwidth resources of both network 800 and network 1100. Generally, 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.

[0126] Network 1100 may include UE 1102, which may include any mobile or non-mobile computing device designed to communicate with RNA 1108 via a wireless connection. UE 1102 may be similar to, for example, UE 802. UE 1102 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment systems, in-vehicle entertainment devices, dashboards, head-up displays, in-vehicle diagnostic equipment, desktop mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, connected appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0127] Despite Figure 11 Not specifically shown, but in some embodiments, network 1100 may include multiple UEs directly coupled to each other via sidelink ports. The UEs may be M2M / D2D devices communicating using physical sidelink channels (such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.). Similarly, although in Figure 11 Not specifically shown, but UE 1102 can be used with AP (such as regarding Figure 8 The AP 806 described is communicatively coupled. Furthermore, although in Figure 11 Not specifically shown, but in some embodiments, RAN 1108 may include one or more ANs, such as those described above. Figure 8 The AP 808 described. RAN 1108 and / or the AN of RAN 1108 may be referred to as a base station (BS), RAN node, or other terms or names.

[0128] UE 1102 and RAN 1108 can 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 terahertz (THz) or Asia-Pacific (APH) bandwidth, or joint communication and sensing. As used herein, the term "joint communication and sensing" may refer to a system that allows wireless communication and radar-based sensing via various types of multiplexing. As used herein, terahertz or APH bandwidth may refer to communication in the frequency range of 80 GHz and above. This frequency range may additionally or alternatively be referred to as the "millimeter wave" or "mmWave" frequency range.

[0129] RAN 1108 enables communication between UE 1102 and 6G core network (CN) 1110. Specifically, RAN 1108 facilitates the transmission and reception of data between UE 1102 and 6G CN 1110. 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. 6G CN 1110 may additionally include features such as... Figure 11 UPF 848 and DN 836 are shown in the figure.

[0130] Additionally, RAN 1108 may include various additional functions beyond or replacing those of traditional cellular networks, such as 4G or 5G networks. Two such functions may include a Computation Control Function (Comp CF) 1124 and a Computation Service Function (Comp SF) 1136. Comp CF 1124 and Comp SF 1136 may be portions or functions of the Computation Service Plane. Comp CF 1124 may be a control plane function providing functions such as management of Comp SF 1136, computation task context generation and management (e.g., creation, reading, modification, deletion), and interaction with the underlying computation infrastructure used for computation resource management. Comp SF 1136 may be a user plane function acting as a gateway to connect computation service users (such as UE 1102) and computation nodes behind the Comp SF instance. Some functionalities of Comp SF 1136 may include: parsing compute service data received from users to compute tasks that can be performed by compute nodes; maintaining the service mesh ingress gateway or service API gateway; enforcing service and billing policies; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1136 instance may be used as a user plane gateway for a cluster of compute nodes. A Comp CF1124 instance may control one or more Comp SF 1136 instances.

[0131] Two other such functions may include a communication control function (Comm CF) 1128 and a communication service function (Comm SF) 1138, which may be part of the communication service plane. Comm CF 1128 may be a control plane function for managing Comm SF 1138, creating / configuring / releasing communication sessions, and managing the communication session context. Comm SF 1138 may be a user plane function for data transmission. Comm CF 1128 and Comm SF 1138 can be considered as... Figure 8 Upgrades to the SMF846 and UPF848 described in the 5G system specification. Upgrades provided by Comm CF 1128 and Comm SF 1138 enable service-aware transport. For legacy (e.g., 4G or 5G) data transmission, the SMF846 and UPF848 remain usable.

[0132] Two other such functions may include a data control function (Data CF) 1122 and a data service function (Data SF) 1132, which may be part of the data service plane. Data CF 1122 may be a control plane function and provides functions such as DataSF 1132 management, data service creation / configuration / release, and data service context management. Data SF 1132 may be a user plane function and acts as a gateway between data service users (such as various functions of UE 1102 and 6G CN 1110) and the data service endpoints behind the gateway. Specific functions may include: parsing data service user data and forwarding it to the appropriate data service endpoint, generating billing data, and reporting data service status.

[0133] Another such function is the Service Orchestration and Linking Function (SOCF) 1120, which discovers, orchestrates, and links communication services / computing services / data services provided by functions within the network. Upon receiving a service request from a user, SOCF 1120 can interact with one or more of Comp CF 1124, Comm CF 1128, and Data CF 1122 to identify CompSF 1136 instances, Comm SF 1138 instances, and Data SF 1132 instances, configure service resources, and generate a service chain. This service chain can contain multiple Comp SF 1136 instances, Comm SF 1138 instances, and Data SF 1132 instances, as well as their associated compute endpoints. Workload processing and data movement can occur within the generated service chain. SOCF 1120 is also responsible for maintaining, updating, and releasing the created service chains.

[0134] Another such function is Service Registration Function (SRF) 1114, which can be used for registration of system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 1136 gateway and the Data SF 1132 gateway, and services provided by UE 1102. SRF 1114 can be considered as the counterpart of NRF 854 that can be used for registration of network functions.

[0135] Other such functionalities may include the Evolved Serving Communication Proxy (eSCP) and the Service Infrastructure Control Function (SICF) 1126, which provides the service communication infrastructure for control plane services and user plane services. With the addition of user plane service communication proxy capabilities, the eSCP can be associated with the 5G service communication proxy (SCP). Therefore, the eSCP is divided into two parts: eCSP-C 1112 and eSCP-U1134, used for the control plane service communication proxy and the user plane service communication proxy, respectively. SICF 1126 can control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configuration, and performance monitoring.

[0136] Another such function is AMF 1144. AMF 1144 can be similar to 844, but with additional functions. Specifically, AMF 1144 can include potential function reassignment, such as transferring message forwarding functions from AMF 1144 to RAN 1108.

[0137] Another such feature is the Service Orchestration Exposure Feature (SOEF) 1118. SOEF can be configured to expose service orchestration and linking services to external users, such as applications.

[0138] UE 1102 may include additional functionality known as Computational Client Service Function (comp CSF) 1104. compCSF 1104 may have both control plane and user plane functions 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) to perform service discovery, request / response, compute task workload exchange, etc. Comp CSF 1104 may also cooperate with network-side functions to determine whether compute tasks should run on elements of UE 1102, RAN 1108, and / or 6G CN 1110.

[0139] UE 1102 and / or Comp CSF 1104 may include a service mesh proxy 1106. The service mesh proxy 1106 can be used as a proxy for service-to-service communication in the user plane. The capabilities of the service mesh proxy 1106 may include one or more of addressing, security, load balancing, etc.

[0140] Example Process

[0141] In some embodiments, Figures 8-11 Or, in some other figures herein, multiple electronic devices, multiple networks, multiple systems, multiple chips, or multiple components, or portions thereof, or implementations thereof, may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein. One such process 1200 in Figure 12 The process 1200 is described in the following description. In some embodiments, process 1200 may be performed by the UE or a portion thereof. At 1202, process 1200 includes receiving configuration information indicating the active uplink (UL) bandwidth portion (BWP) for the serving cell, with a dynamic transformation precoder indicated as enabled. At 1204, process 1200 may further include generating first power margin information related to transformation precoder disabling and second power margin information related to transformation precoder enabling, based on the configuration information. At 1206, process 1200 may further include reporting the first power margin information and the second power margin information to the next-generation node B (gNB).

[0142] Figure 13 Another example process 1300 according to various embodiments is illustrated. Process 1300 may be performed by a UE or a portion thereof. At 1302, process 1300 includes receiving configuration information indicating whether downlink control information (DCI), including a transformation precoder, is enabled or disabled. At 1304, process 1300 further includes generating first power headroom information based on actual physical uplink shared channel (PUSCH) transmissions and configuration information. At 1306, process 1300 further includes generating second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on the transformation precoder being disabled if the transformation precoder is enabled for actual PUSCH transmissions, and based on the transformation precoder being enabled if the transformation precoder is disabled for actual PUSCH transmissions. At 1308, process 1300 further includes reporting the first power headroom information and the second power headroom information to the next-generation node B (gNB).

[0143] Figure 14Another example process 1400 according to various embodiments is illustrated. Process 1400 may be performed by a gNB or a portion thereof. At 1402, process 1400 includes decoding configuration information for a transmission to a user equipment (UE), the configuration information indicating whether downlink control information (DCI) including a transformation precoder is enabled or disabled. At 1404, process 1400 further includes receiving first power margin information based on a PUSCH transmission and second power margin information based on assumed PUSCH information from the UE, wherein the second power margin information is generated based on the transformation precoder being disabled if the transformation precoder is enabled for the PUSCH transmission, and is generated based on the transformation precoder being enabled if the transformation precoder is disabled for the PUSCH transmission.

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

[0145] Example

[0146] Example 1 may include a method for wireless communication in a wireless cellular network (e.g., for a fifth-generation (5G) or new radio (NR) system), the method comprising:

[0147] Configuration of the power headroom report (PHR) in a single Media Access Control-Control Element (MAC-CE) for the UE to receive CP-OFDM and DFT-s-OFDM waveforms from the gNodeB; and

[0148] The UE reports the CP-OFDM waveform and DFT-s-OFDM waveform in the PHR of the MAC-CE.

[0149] Example 2 may include the method of Example 1 or some other examples in this document, wherein an existing process can be reused to determine whether a PHR is an actual PHR or a virtual PHR, regardless of whether the PUSCH transmission in slot n is based on a CP-OFDM waveform or a DFT-s-OFDM waveform, wherein the determined PHR type (actual PHR or virtual PHR) can be applied to both CP-OFDM waveforms and DFT-s-OFDM waveforms.

[0150] Example 3 may include the method of Example 1 or some other examples herein, wherein an existing process can be reused to determine whether a PHR is an actual PHR or a virtual PHR based on the indication waveform for the PUSCH transfer in slot n, wherein the determined PHR type (actual PHR or virtual PHR) can be applied to both CP-OFDM waveforms and DFT-s-OFDM waveforms.

[0151] Example 4 may include the method of Example 1 or some other examples in this document, wherein when the PHR is determined to be a virtual PHR, only a single PHR entry is included in MAC-CE.

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

[0153] Example 6 may include the method of Example 1 or some other examples herein, wherein, in the case of multiple TRP operations for PUSCH repetition (e.g., for configuring a CC with multiple TRP PUSCH repetitions), and if the UE does not support two PHRs for multiple TRP operations, and if the PHR report is the actual PHR, the UE uses the set of power control parameters corresponding to the earliest repetition, which overlaps with the first slot, in which the PUSCH carrying the PHR MAC-CE is transmitted.

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

[0155] Example 8 may include the method of Example 1 or some other examples herein, wherein, in the case of multiple TRP operations for PUSCH repetition (e.g., for configuring a CC with multiple TRP PUSCH repetitions), and if the PHR report is an actual PHR, the UE uses the set of power control parameters corresponding to the earliest repetition, which overlaps with the first slot, in which the PUSCH carrying the PHR MAC-CE is transmitted.

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

[0157] Example 10 may include the method of Example 1 or some other examples herein, wherein the determined PHR type (actual PHR or virtual PHR) is capable of being applied to both the CP-OFDM waveform and the DFT-s-OFDM waveform of the PUSCH for the first TRP or the second TRP, respectively.

[0158] Example 11 may include the method of Example 1 or some other examples in this document, wherein the multi-entry PHR MAC CE may be extended to include both CP-OFDM waveforms and DFT-s-OFDM waveforms for one or more carriers.

[0159] Example 12 may include the method of Example 1 or some other examples herein, wherein, for a carrier configured with dynamic waveform switching, the PHR in the carrier may include the PHR for both CP-OFDM waveforms and DFT-s-OFDM waveforms according to the foregoing embodiments.

[0160] Example 13 may include the method of Example 1 or some other examples herein, wherein the enhanced multi-entry PHR for multi-TRP MAC CE may be extended to include PHR for both CP-OFDM waveforms and DFT-s-OFDM waveforms for one or more carriers.

[0161] Example 14 may include the method of Example 1 or some other examples herein, wherein, for a carrier configured with dynamic waveform switching, the PHR in the carrier may include the PHR for both CP-OFDM waveforms and DFT-s-OFDM waveforms according to the foregoing embodiments.

[0162] Example 15 may include the method of Example 1 or some other examples herein, wherein whether the PHR for dynamic waveform switching is reported can be determined based on whether dynamic waveform switching for DCI formats 0_1 and / or 0_2 is configured in the active UL BWP.

[0163] Example 16 may include the method of Example 1 or some other examples in this document, wherein only the actual PHR for a waveform is included in the new MAC-CE for dynamic waveform switching.

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

[0165] Example 18 may include the method of Example 1 or some other examples in this document, wherein the waveform used for PHR may be determined based on predefined rules.

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

[0167] Example 20 may include the method of Example 1 or some other examples herein, wherein two power margin levels may be included in a single PHR for both multi-TRP and dynamic waveform switching, which are respectively used for PUSCH repetition of the first TRP and the second TRP for a waveform.

[0168] Example 21 may include the method of Example 1 or some other examples herein, wherein the waveform indicator and PH used to indicate or determine the waveform can be included in a carrier for a multi-entry PHR with dynamic waveform switching.

[0169] Example 22 may include a method for a user equipment (UE) that includes:

[0170] Configuration of power headroom report (PHR) in a single Medium Access Control-Control Element (MAC-CE) for receiving cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveforms and discrete Fourier transform (DFT)-spread spectrum-OFDM waveforms; and

[0171] Based on this configuration, a MAC-CE is generated for transmission.

[0172] Example 23 may include the method of Example 22 or some other examples in this document, and also includes:

[0173] Determine whether the PHR type is an actual PHR or a virtual PHR; and

[0174] The determined PHR type is applied to both the CP-OFDM waveform and the DFT-s-OFDM waveform in the PHR.

[0175] Example 24 may include the methods of Examples 22-23 or some other examples herein, wherein the PHR corresponds to the virtual PHR and the single-entry PHR is included in the MAC-CE for both the CP-OFDM waveform and the DFT-s-OFDM waveform.

[0176] Example 25 may include the methods of Examples 22-24 or some other examples herein, wherein the MAC-CE includes PHR information for both CP-OFDM waveforms and DFT-s-OFDM waveforms for Physical Uplink Shared Channel (PUSCH) transmissions targeting both a first Transmit Receive Point (TRP) and a second TRP.

[0177] Example 26 may include the methods of Examples 22-25 or some other examples in this document, wherein the PHR corresponds to a component carrier configured with PUSCH repetition using multiple TRPs.

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

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

[0180] Example 29 may include the methods of Examples 22-28 or some other examples herein, wherein the MAC-CE includes a multi-entry MAC-CE, which may be extended to include PHR for both CP-OFDM waveforms and DFT-s-OFDM waveforms for one or more carriers.

[0181] Example 30 may include the methods of Examples 22-29 or some other examples in this document, wherein the PHR corresponds to a carrier configured with dynamic waveform switching.

[0182] Example 31 may include the methods of Examples 22-30 or some other examples herein, wherein the PHR is transmitted based on determining that the dynamic waveform switching is configured in the active UL BWP for DCI formats 0_1 and / or 0_2.

[0183] Example 32 may include the methods of Examples 22-31 or some other examples in this document, wherein the MAC-CE includes the actual PHR for only one waveform.

[0184] Example 33 may include the method of Example 32 or some other examples herein, wherein MAC-CE includes an indication of whether the waveform associated with PHR is a CP-OFDM waveform or a DFT-s-OFDM waveform.

[0185] Example 34 may include the methods of Examples 32-33 or some other examples in this document, and may also include: determining the waveform for PHR based on one or more predefined rules.

[0186] Example 35 may include the methods of Examples 22-34 or some other examples in this document, wherein the MAC-CE uses an enhanced logical channel ID (eLCID) specifically designed for PHR for dynamic waveform switching.

[0187] Example 36 may include the methods of Examples 22-35 or some other examples herein, wherein two power margin levels are included in a single PHR for both multi-TRP and dynamic waveform switching.

[0188] Example 37 may include the method of Example 36 or some other examples herein, wherein two power margin levels are used for PUSCH repetition for a first TRP and a second TRP of a waveform, respectively.

[0189] Example 38 may include the methods of Examples 22-37 or some other examples herein, wherein the PHR includes a multi-entry PHR for dynamic waveform switching, and wherein the PHR indicates power margin and associated waveform.

[0190] Example 39 may include the method of Example 38 or some other examples herein, wherein multiple entry PHRs are transmitted on a carrier configured with dynamic waveform switching.

[0191] Example 40 may include a method for a next-generation node B (gNB) that includes:

[0192] For transmissions to User Equipment (UE), the configuration of the Power Headroom Report (PHR) for Cyclic Prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM) waveforms and Discrete Fourier Transform (DFT)-Spread Spectrum-OFDM waveforms in a single Media Access Control-Control Element (MAC-CE) is decoded; and

[0193] Based on this configuration, MAC-CE is received from the UE.

[0194] Example 41 may include the method of Example 40 or some other examples in this document, wherein the same PHR type (e.g., actual PHR or virtual PHR) applies to both CP-OFDM waveforms and DFT-s-OFDM waveforms in MAC-CE.

[0195] Example 42 may include the methods of Examples 40-41 or some other examples herein, wherein the PHR corresponds to the virtual PHR and the single-entry PHR is included in the MAC-CE for both the CP-OFDM waveform and the DFT-s-OFDM waveform.

[0196] Example 43 may include the methods of Examples 40-42 or some other examples herein, wherein the MAC-CE includes PHR information for both CP-OFDM waveforms and DFT-s-OFDM waveforms for Physical Uplink Shared Channel (PUSCH) transmissions targeting both a first Transmit Receive Point (TRP) and a second TRP.

[0197] Example 44 may include the methods of Examples 40-43 or some other examples in this document, wherein the PHR corresponds to a component carrier configured with PUSCH repetition using multiple TRPs.

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

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

[0200] Example 47 may include the methods of Examples 40-46 or some other examples in this document, wherein MAC-CE includes multiple entries of MAC-CE.

[0201] Example 48 may include the methods of Examples 40-47 or some other examples in this document, wherein the PHR corresponds to a carrier configured with dynamic waveform switching.

[0202] Example 49 may include the methods of Examples 40-48 or some other examples herein, wherein a PHR is received if dynamic waveform switching is configured in the active UL BWP for DCI formats 0_1 and / or 0_2.

[0203] Example 50 may include the methods of Examples 40-49 or some other examples in this document, wherein the MAC-CE includes the actual PHR for only one waveform.

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

[0205] Example 52 may include the methods of Examples 50-51 or some other examples in this document, and may also include: determining the waveform for PHR based on one or more predefined rules.

[0206] Example 53 may include the methods of Examples 40-52 or some other examples in this document, wherein the MAC-CE uses an Enhanced Logical Channel ID (eLCID) specifically designed for PHR for dynamic waveform switching.

[0207] Example 54 may include the methods of Examples 40-53 or some other examples herein, wherein two power margin levels are included in a single PHR for both multi-TRP and dynamic waveform switching.

[0208] Example 55 may include the method of Example 54 or some other examples herein, wherein two power margin levels are used for PUSCH repetition for a first TRP and a second TRP of a waveform, respectively.

[0209] Example 56 may include the methods of Examples 40-55 or some other examples herein, wherein the PHR includes a multi-entry PHR for dynamic waveform switching, and wherein the PHR indicates power margin and associated waveform.

[0210] Example 57 may include the method of Example 56 or some other examples in this document, wherein a multi-entry PHR is received on a carrier configured with dynamic waveform switching.

[0211] Example 58 may include an apparatus for a user equipment (UE) comprising: a memory storing configuration information indicating that a dynamic transformation precoder indicates the presence of an active uplink (UL) bandwidth portion (BWP) for the serving cell in the form of downlink control information (DCI); and processor circuitry coupled to the memory. The processor circuitry is configured to: generate, based on the configuration information, first power margin information related to transformation precoder disabling and second power margin information related to transformation precoder enabling; and report the first power margin information and the second power margin information to a next-generation node B (gNB).

[0212] Example 59 may include the apparatus of Example 58 or some other examples herein, wherein the first of the first power margin information or the second power margin information is generated based on actual physical uplink shared channel (PUSCH) transmissions, and the second of the first power margin information or the second power margin information is generated based on assumed PUSCH transmissions.

[0213] Example 60 may include the apparatus of Example 59 or some other examples herein, wherein the processor circuitry is also configured to decode the DCI, including an indication from the transformation precoder as to whether actual PUSCH transmission is enabled.

[0214] Example 61 may include the apparatus of Example 60 or some other examples herein, wherein the DCI is in DCI format 0_1 ​​or 0_2.

[0215] Example 62 may include the apparatus of Examples 58-61 or some other examples herein, wherein the first power margin information and the second power margin information are reported in the same Media Access Control-Control Element (MAC-CE).

[0216] Example 63 may include the apparatus of Examples 58-62 or some other examples herein, wherein at least one of the first power margin information or the second power margin information includes a maximum output power reduction value, P. CMAX,f,c (i).

[0217] Example 64 may include the apparatus of Examples 58-63 or some other examples herein, wherein the processor circuitry is configured to disable the transform precoder for transmitting cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveforms and to enable the transform precoder for transmitting discrete Fourier transform-spread spectrum-OFDM (DFT-s-OFDM) waveforms.

[0218] Example 65 may include one or more computer-readable media storing instructions that, when executed by one or more processors of a user equipment (UE), configure the UE to: receive configuration information indicating whether downlink control information (DCI) including a transformation precoder is enabled or disabled; generate first power headroom information based on actual physical uplink shared channel (PUSCH) transmissions and configuration information; generate second power headroom information based on assumed PUSCH information, wherein the second power headroom information is generated based on transformation precoder disabling if transformation precoder is enabled for actual PUSCH transmissions, and based on transformation precoder enabling if transformation precoder is disabled for actual PUSCH transmissions; and report the first and second power headroom information to a next-generation node B (gNB).

[0219] Example 66 may include one or more computer-readable media of Example 65 or some other examples herein, wherein the DCI is in DCI format 0_1 ​​or 0_2.

[0220] Example 67 may include one or more computer-readable media of Examples 65-66 or some other examples herein, wherein the first power margin information and the second power margin information are reported in the same Media Access Control-Control Element (MAC-CE).

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

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

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

[0224] Example 71 may include one or more computer-readable media of Examples 66-70 or some other examples herein, wherein the second power margin information includes a maximum output power reduction value, PCMAX,f,c (i).

[0225] Example 72 may include one or more computer-readable media storing instructions that, when executed by one or more processors of a next-generation node B (gNB), configure the gNB to: encode configuration information for transmissions to a user equipment (UE) indicating whether downlink control information (DCI), including a transformation precoder, is enabled or disabled; and receive first power margin information from the UE based on actual physical uplink shared channel (PUSCH) transmissions and configuration information, and receive second power margin information from the UE based on assumed PUSCH information, wherein the second power margin information is generated based on transformation precoder disabling if transformation precoder is enabled for actual PUSCH transmissions, and is generated based on transformation precoder enabling if transformation precoder is disabled for actual PUSCH transmissions.

[0226] Example 73 may include one or more computer-readable media of Example 72 or some other examples herein, wherein the DCI is DCI format 0_1 ​​or 0_2.

[0227] Example 74 may include one or more computer-readable media of Examples 72-73 or some other examples herein, wherein the first power margin information and the second power margin information are received in the same Media Access Control-Control Element (MAC-CE).

[0228] Example 75 may include one or more computer-readable media of Examples 72-74 or some other examples herein, wherein when the DCI indicates that the transform precoder is disabled, the UE transmits a 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 transmits a PUSCH transmission with a discrete Fourier transform-spread spectrum-OFDM (DFT-s-OFDM) waveform.

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

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

[0231] Example 78 may include one or more computer-readable media of Examples 72-77 or some other examples herein, wherein the second power margin information includes a maximum output power reduction value, P CMAX,f,c (i).

[0232] Example 79 may include an apparatus comprising one or more elements performing a method described in or associated with any of Examples 1-78, or any other method or process described herein.

[0233] Example 80 may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described in or associated with any of Examples 1-78, or any other methods or processes described herein.

[0234] Example 81 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the methods described in or associated with any of Examples 1-78, or any other methods or processes described herein.

[0235] Example 82 may include methods, techniques, or processes, or parts thereof, as described in or related to any of Examples 1-78.

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

[0237] Example 84 may include a signal, or a portion thereof, as described in any of Examples 1-78 or associated with any of Examples 1-78.

[0238] Example 85 may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described in or associated with any of Examples 1-78, or parts or portions thereof, or otherwise described in this disclosure.

[0239] Example 86 may include a data-encoded signal, or part or portion thereof, as described in or associated with any of Examples 1-78, or otherwise described in this disclosure.

[0240] Example 87 may include signals encoded as datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described in or associated with any of Examples 1-78, or other content described in this disclosure.

[0241] Example 88 may include an electromagnetic signal carrying computer-readable instructions, wherein the computer-readable instructions are executed by one or more processors to cause one or more processors to perform a method, technique or process, or a portion thereof, as described in or related to any of Examples 1-78.

[0242] Example 89 may include a computer program comprising instructions, wherein the program is executed by a processing element to cause the processing element to perform a method, technique, or process, or a portion thereof, as described in or related to any of Examples 1-78.

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

[0244] Example 91 may include methods of communication in a wireless network as shown and described herein.

[0245] Example 92 may include systems for providing wireless communication, as shown and described herein.

[0246] Example 93 may include devices for providing wireless communication, as shown and described herein.

[0247] Unless otherwise expressly stated, any of the examples above may be combined with any other examples (or combinations of examples). 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 the embodiments to the precise form disclosed. Modifications and variations are possible in accordance with the above teachings, or may be obtained from practice with various embodiments.

[0248] abbreviation

[0249] Unless used differently herein, the terms, definitions, and abbreviations are consistent with those defined in 3GPP TR 21.905v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may be applied to the examples and embodiments discussed herein.

[0250] 3GPP: Third Generation Partnership Project

[0251] 4G: Fourth Generation

[0252] 5G: Fifth Generation

[0253] 5GC: 5G Core Network

[0254] AC: Application Client

[0255] ACR: Application Context Relocation

[0256] ACK: Confirmation

[0257] ACID: Application Client Identifier

[0258] ADRF: Analysis Data Repository Function

[0259] AF: Application Functions

[0260] AM: Confirmation Mode

[0261] AMBR: Aggregate Maximum Bit Rate

[0262] AMF: Access and Mobility Management Functions

[0263] AN: Accessing the network

[0264] AnLF: Analysis Logic Function

[0265] ANR: Automatic Neighbor Relations

[0266] AOA: Angle of Arrival

[0267] AP: Application Protocol, Antenna Port, Access Point

[0268] API: Application Programming Interface

[0269] APN: Access Point Name

[0270] ARP: Assign and reserve priority

[0271] ARQ: Automatic Repeat Request

[0272] AS: Access Layer

[0273] ASP: Application Service Provider

[0274] ASN.1: Abstract Syntax Representation 1

[0275] AUS: Authentication Server Function

[0276] AWGN: Additive White Gaussian Noise

[0277] BAP: Backhaul Adaptation Protocol

[0278] BCH: Broadcast Channel

[0279] BER: Bit Error Rate

[0280] BFD: Beam Failure Detection

[0281] BLER: Block Error Rate

[0282] BPSK: Binary Phase Shift Keying

[0283] BRAS: Broadband Remote Access Server

[0284] BSS: Business Support System

[0285] BS: Base Station

[0286] BSR: Buffer Status Report

[0287] BW: Bandwidth

[0288] BWP: Bandwidth section

[0289] C-RNTI: Temporary Identity for Cellular Wireless Network

[0290] CA: Carrier Aggregation, Certification Authority

[0291] CAPEX: Capital Expenditure

[0292] CBD: Candidate Beam Detection

[0293] CBRA: Competition-Based Random Access

[0294] CC: Component carrier, country code, cryptographic verification and

[0295] CCA: Free Channel Assessment

[0296] CCE: Control Channel Element

[0297] CCCH: Common Control Channel

[0298] CE: Coverage Enhancement

[0299] CDM: Content Delivery Network

[0300] CDMA: Code Division Multiple Access

[0301] CDR: Billing Data Request

[0302] CDR: Billing Data Response

[0303] CFRA: Competition for Freedom Random Access

[0304] CG: Community Group

[0305] CGF: Billing Gateway Function

[0306] CHF: Billing Function

[0307] CI: Community Identity

[0308] CID: Cell ID (e.g., location method)

[0309] CIM: Public Information Model

[0310] CIR: Carrier Interference Ratio

[0311] CK: Password key

[0312] CM: Connection Management, conditionally mandatory.

[0313] CMAS: Commercial Mobile Alarm Service

[0314] CMD: Commands

[0315] CMS: Cloud Management System

[0316] CO: Optional under certain conditions

[0317] CoMP: Collaborative Multi-Point

[0318] CORESET: Control resource set

[0319] COTS: Commercial Spot

[0320] CP: Control plane, Cyclic prefix, Connector point

[0321] CPD: Join Point Descriptor

[0322] CPE: Customer Premises Equipment

[0323] CPICH: Common Pilot Channel

[0324] CQI: Channel Quality Indicator

[0325] CPU: CSI processing unit, Central Processing Unit

[0326] C / R: Command / Response Fields

[0327] CRAN: Cloud Radio Access Network, Cloud RAN

[0328] CRB: Public Resource Block

[0329] CRC: Cyclic Redundancy Check

[0330] CRI: Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0331] C-RNTI: Cell RNTI

[0332] CS: Circuit Switching

[0333] CSCF: Call Session Control Function

[0334] CSAR: Cloud Service Archives

[0335] CSI: Channel State Information

[0336] CSI-IM: CSI Interference Measurement

[0337] CSI-RS: CSI Reference Signal

[0338] CSI-RSRP: CSI Reference Signal Received Power

[0339] CSI-RSRQ: CSI Reference Signal Reception Quality

[0340] CSI-SINR: CSI signal-to-noise ratio

[0341] CSMA: Carrier-Sense Multiple Access

[0342] CSMA / CA: CSMA with conflict avoidance

[0343] CSS: Public search space, community-specific search space

[0344] CTF: Billing Trigger Function

[0345] CTS: Allow transmission

[0346] CW: Code Word

[0347] CWS: Competition Window Size

[0348] D2D: Device to Device

[0349] DC: Dual connection, direct current

[0350] DCI: Downlink Control Information

[0351] DF: Deployment Type

[0352] DL: Downlink

[0353] DMTF: Distributed Management Task Grouping

[0354] DPDK: Data Panel Development Kit

[0355] DM-RS: DMRD demodulation reference signal

[0356] DN: Data Network

[0357] DNN: Data Network Name

[0358] DNAI: Data Network Access Identifier

[0359] DRB: Data Radio Bearer

[0360] DRS: Reference Signal Detection

[0361] DRX: Discontinuous Receiver

[0362] DSL: Domain-Specific Language, Digital Subscriber Line

[0363] DSLAM: DSL Access Multiplexer

[0364] DwPTS: Downlink Pilot Slot

[0365] E-LAN: Ethernet Local Area Network

[0366] E2E: End-to-End

[0367] EAS: Edge Application Server

[0368] ECCA: Extended Idle Channel Assessment, Extended CCA

[0369] ECCE: Enhanced Control Channel Element, Enhanced CCE

[0370] ED: Energy Detection

[0371] EDGE: Enhanced Data Rate for GSM Evolution (Enhanced Data Rate GSM Evolution)

[0372] EAS: Edge Application Server

[0373] EASID: Edge Application Server Identifier

[0374] ECS: Edge Configuration Server

[0375] ECSP: Edge Computing Service Provider

[0376] EDN: Edge Data Network

[0377] EEC: Edge Enabler Client

[0378] EECID: Edge Enabler Client Identifier

[0379] EES: Edge Enabler Server

[0380] EESID: Edge Enabler Server Identifier

[0381] EHE: Edge Host Environment

[0382] EGMF: Exposing governance management functions

[0383] EGPRS: Enhanced GPRS

[0384] EIR: Device Identity Registration

[0385] eLAA: Enhanced Authorized Access, Enhanced LAA

[0386] EM: Component Manager

[0387] eMBB: Enhanced Mobile Broadband

[0388] EMS: Component Management System

[0389] eNB: Evolved Node B, E-UTRAN Node B

[0390] EN-DC: EUTRA-NR Dual Connection

[0391] EPC: Evolved Packet Core

[0392] EPDCCH: Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0393] EPRE: Energy per resource element

[0394] EPS: Evolved Package System

[0395] EREG: Enhanced REG, Enhanced Resource Element Group

[0396] ETSI: European Telecommunications Standards Institute

[0397] ETWS: Earthquake and Tsunami Warning System

[0398] eUICC: Embedded UICC, Embedded Universal Integrated Circuit Card

[0399] E-UTRA: The Evolution of UTRA

[0400] E-UTRAN: Evolved UTRAN

[0401] EV2X: Enhanced V2X

[0402] F1AP: F1 Application Protocol

[0403] F1-C: F1 Control Plane Interface

[0404] F1-U: F1 User Plane Interface

[0405] FACCH: Fast Correlation Control Channel

[0406] FACCH / F: Fast Correlation Control Channel / Full Rate

[0407] FACCH / H: Fast Correlation Control Channel / Half Rate

[0408] FACH: Forward Access Channel

[0409] FAUSCH: Fast Uplink Signaling Channel

[0410] FB: Function Block

[0411] FBI: Feedback Information

[0412] FCC: Federal Communications Commission

[0413] FCCH: Frequency Correction Channel

[0414] FDD: Frequency Division Duplex

[0415] FDM: Frequency Division Multiplexing

[0416] FDMA: Frequency Division Multiple Access

[0417] FE: Frontend

[0418] FEC: Forward Error Correction

[0419] FFS: For further research

[0420] FFT: Fast Fourier Transform

[0421] feLAA: Further enhanced authorized auxiliary access, further enhanced LAA

[0422] FN: Frame Number

[0423] FPGA: Field Programmable Gate Array

[0424] FR: Frequency range

[0425] FQDN: Fully Qualified Domain Name

[0426] G-RNTI: Temporary Identity for GERAN Wireless Network

[0427] GERAN: GSM EDGE RAN, GSM EDGE Radio Access Network

[0428] GGSN: Gateway GPRS Support Node

[0429] GLONASS: Global Navigation Satellite System; gNB: Next-Generation Node B; gNB-CU: Central Unit of gNB, Central Unit of Next-Generation Node B; gNB-DU: Distribution Unit of gNB, Distribution Unit of Next-Generation Node B.

[0430] GNSS: Global Navigation Satellite System

[0431] GPRS: Universal Package Wireless Service

[0432] GPSI: General Public Subscription Identifier

[0433] GSM: Global System for Mobile Communications, Mobile Special Group

[0434] GTP: GPRS Tunneling Protocol; GTP-U: GPRS Tunneling Protocol for User Plane; GTS: Sleep Signal (related to WUS).

[0435] GUMMEI: A globally unique MME identifier

[0436] GUTI: The world's only temporary UE identity

[0437] HARQ: Hybrid ARQ, a combination of automatic repeating requests.

[0438] HANDO: Switch

[0439] HFN: High Frame Rate

[0440] HHO: Hard Switch

[0441] HLR: Home Location Register

[0442] HN: Home Network

[0443] HO: Switch

[0444] HPLMN: Home Public Land Mobile Network

[0445] HSDPA: High-speed downlink packet access

[0446] HSN: Frequency Hopping Serial Number

[0447] HSPA: High-speed package access

[0448] HSS: Home Subscriber Server

[0449] HSUPA: High-speed uplink packet access; HTTP: Hypertext Transfer Protocol; HTTPS: Hypertext Transfer Protocol Secure (HTTP over SSL (i.e., port 443) HTTP / 1.1); I-Block: Message Block

[0450] ICCID: Integrated Circuit Card Identifier

[0451] IAB: Integrated Access and Backhaul

[0452] ICIC: Inter-cell Interference Coordination

[0453] ID: Identity, identifier

[0454] IDFT: Inverse Discrete Fourier Transform

[0455] IE: Information Elements

[0456] IBE: In-band firing

[0457] IEEE: Institute of Electrical and Electronics Engineers

[0458] IEI: Information Element Identifier

[0459] IEIDL: Information Element Identifier Data Length

[0460] IETF: Internet Engineering Task Force

[0461] IF: Infrastructure

[0462] IIoT: Industrial Internet of Things

[0463] IM: Interference Measurement, Intermodulation, IP Multimedia

[0464] IMC: IMS Certificate

[0465] IMEI: International Mobile Equipment Identity

[0466] IMGI: International Mobile Group

[0467] IMPI: IP Multimedia Private Identity

[0468] IMPU: IP Multimedia Public Identity

[0469] IMS: IP Multimedia Subsystem

[0470] IMSI: International Mobile Subscriber Identity

[0471] IoT: Internet of Things

[0472] IP: Internet Protocol

[0473] IPsec: IP security, Internet Protocol security

[0474] IP-CAN: IP-Connectivity Access Network

[0475] IP-M: IP Multicast

[0476] IPv4: Internet Protocol version 4

[0477] IPv6: Internet Protocol version 6

[0478] IR: Infrared

[0479] IS: Synchronization

[0480] IRP: Integration Reference Point

[0481] ISDN: Integrated Services Digital Network

[0482] ISIM: Identity Module for IM Services

[0483] ISO: International Organization for Standardization

[0484] ISP: Internet Service Provider

[0485] IWF: Interoperability

[0486] I-WLAN: WLAN constraint length for interoperable convolutional codes and USIM personal keys.

[0487] kB: kilobyte (1000 bytes)

[0488] kbps: kilobits per second

[0489] Kc: Encryption key

[0490] Ki: Personal subscriber authentication key

[0491] KPI: Key Performance Indicators

[0492] KQI: Key Quality Indicator

[0493] KSI: Key Set Identifier

[0494] Ksps: kilosperms per second

[0495] KVM: Kernel Virtual Machine

[0496] L1: Layer 1 (Physical Layer)

[0497] L1-RSRP: Layer 1 Reference Signal Received Power

[0498] L2: Layer 2 (Data Link Layer)

[0499] L3: Layer 3 (Network Layer)

[0500] LAA: Authorized Assistant Access

[0501] LAN: Local Area Network

[0502] LADN: Local Area Data Network

[0503] LBT: Listen first, then speak

[0504] LCM: Lifecycle Management

[0505] LCR: Low Chip Rate

[0506] LCS: Location Services

[0507] LCID: Logical Channel ID

[0508] LI: Layer Indicator

[0509] LLC: Logical Link Control, Low-Level Compatibility

[0510] LMF: Location Management Function

[0511] LOS: Line of Sight LPLMN: Local PLMN

[0512] LPP: LTE Location Protocol

[0513] LSB: Least Significant Bit

[0514] LTE: Long Term Evolution

[0515] LWA: LTE-WLAN aggregation

[0516] LWIP: Horizontal integration with IPsec tunnels for LTE / WLAN wireless communication

[0517] LTE: Long Term Evolution; M2M: Machine-to-Machine

[0518] MAC: Media Access Control (Protocol Layer Context)

[0519] MAC: Message Authentication Code (Security / Encryption Context)

[0520] MAC-A: MAC for authentication and key negotiation (TSG T WG3 context) MAC-I: MAC for data integrity of signaling messages (TSG T WG3 context) MANO: Management and orchestration

[0521] MBMS: Multimedia Playback and Multicast Service

[0522] MBSFN: Multimedia Playback Multicast Service Single Frequency Network

[0523] MCC: Country Code for Mobile

[0524] MCG: Main Cell Group

[0525] MCOT: Maximum Channel Occupancy Time

[0526] MCS: Modulation and Coding Scheme

[0527] MDAF: Management Data Analysis Function

[0528] MDAS: Managed Data Analytics Service

[0529] MDT: Minimum Driven Testing

[0530] ME: Mobile Device

[0531] MeNB: Main eNB

[0532] MER: Message Error Rate

[0533] MGL: Measurement gap length

[0534] MGRP: Measurement Interval Repetition Period

[0535] MIB: Master Information Block, Management Information Base

[0536] MIMO: Multiple Input Multiple Output

[0537] MLC: Mobile Location Center

[0538] MM: Mobility Management

[0539] MME: Mobility Management Entity

[0540] MN: Master Node

[0541] MNO: Mobile Network Operator

[0542] MO: Measurement object, movement initiated.

[0543] MPBCH MTC: Physical Broadcast Channel

[0544] MPDCCH MTC: Physical Downlink Control Channel

[0545] MPDSCH MTC: Physical Downlink Shared Channel

[0546] MPRACH MTC: Physical Random Access Channel

[0547] MPUSCH: Physical Uplink Shared Channel

[0548] MPLS: Multiprotocol Label Switching

[0549] MS: Mobile Station

[0550] MSB: Most significant bit

[0551] MSC: Mobile Handover Center

[0552] MSI: Minimal System Information, MCH Scheduling Information

[0553] MSID: Mobile Station Identifier

[0554] MSIN: Mobile Site Identification Number

[0555] MSISDN: Mobile Subscriber ISDN Number

[0556] MT: Terminated movement, terminated movement

[0557] MTC: Machine Type Communication

[0558] MTLF: Model Training Logic Function

[0559] mMTC: Massive MTC, Massive Machine Type Communication

[0560] MU-MIMO: Multi-user MIMO

[0561] MWUS: MTC wake-up signal, MTC WUS

[0562] NACK: Negative Acknowledgment

[0563] NAI: Network Access Identifier

[0564] NAS: Non-access layer, Non-access access layer

[0565] NCT: Network Connectivity Topology

[0566] NC-JT: Non-coherent joint transmission

[0567] NEC: Network Capability Exposure

[0568] NE-DC: NR-E-UTRA Dual Connectivity

[0569] NEF: Network Exposure Function

[0570] NF: Network Functions

[0571] NFP: Network Forwarding Path

[0572] NFPD: Network Forwarding Path Descriptor

[0573] NFV: Network Functions Virtualization

[0574] NFVI: NFV Infrastructure

[0575] NFVO: NFV orchestrator

[0576] NG: the next generation, the next generation

[0577] NGEN-DC: NG-RAN E-UTRA-NR Dual Connectivity

[0578] NM: Network Manager

[0579] NMS: Network Management System

[0580] N-PoP: Existing network points

[0581] NMIB: N-MIB, Narrow-band MIB

[0582] NPBCH: Narrowband Physical Broadcast Channel

[0583] NPDCCH: Narrowband Physical Downlink Control Channel

[0584] NPDSCH: Narrowband Physical Downlink Shared Channel

[0585] NPRACH: Narrowband Physical Random Access Channel

[0586] NPUSCH: Narrowband Physical Uplink Shared Channel

[0587] NPSS: Narrowband Master Synchronization Signal

[0588] NSSS: Narrowband Subsynchronous Signal

[0589] NR: New Radio, Neighborhood Relations

[0590] NRF: NR Storage Function

[0591] NRS: Narrowband Reference Signal

[0592] NS: Network Services

[0593] NSA: Non-standalone operation mode

[0594] NSD: Network Service Descriptor

[0595] NSR: Network Service Record

[0596] NSSAI: Network Slice Selection Auxiliary Information

[0597] S-NNSAI: Single NSSAI

[0598] NSSF: Network Slice Selection Function

[0599] NW: Network

[0600] NWDAF: Network Data Analysis Function

[0601] NWUS: Narrowband Wake-up Signal, Narrowband WUS

[0602] NZP: Non-zero power

[0603] O&M: Operations and Maintenance

[0604] ODU2: Optical Channel Data Unit - Type 2

[0605] OFDM: Orthogonal Frequency Division Multiplexing

[0606] OFDMA: Orthogonal Frequency Division Multiple Access

[0607] OOB: Out-of-band

[0608] OOS: out of sync

[0609] OPEX: Operating Expenses

[0610] OSI: Other System Information

[0611] OSS: Operation Support System

[0612] OTA: Over-the-air (OTA)

[0613] PAPR: Peak-to-average power ratio

[0614] PAR: Peak-to-Match Ratio

[0615] PBCH: Physical Broadcast Channel

[0616] PC: Power control, personal computer

[0617] PCC: Primary Component Carrier, Primary CC

[0618] P-CSCF: Proxy CSCF

[0619] PCell: Main Cell

[0620] PCI: Physical Cell ID, Physical Cell Identity

[0621] PCEF: Policy and Accounting Enforcement Functionality

[0622] PCF: Policy Control Function

[0623] PCRF: Policy Control and Accounting Rules Functionality

[0624] PDCP: Packet Data Aggregation Protocol, Packet Data Aggregation Protocol Layer

[0625] PDCCH: Physical Downlink Control Channel

[0626] PDCP: Packet Data Aggregation Protocol

[0627] PDN: Packet Data Network, Public Data Network

[0628] PDSCH: Physical Downlink Shared Channel

[0629] PDU: Protocol Data Unit

[0630] PEI: Permanent Device Identifier

[0631] PFD: Packet Flow Description

[0632] P-GW: PDN Gateway

[0633] PHICH: Physical Hybrid-ARQ Indicator Channel

[0634] PHY: Physical Layer

[0635] PLMN: Public Land Mobile Network

[0636] PIN: Personal Identifier

[0637] PM: Performance Measurement

[0638] PMI: Precoding Matrix Indicator

[0639] PNF: Physical Network Function

[0640] PNFD: Physical Network Function Descriptor

[0641] PNFR: Physical Network Function Record

[0642] POC: PTT via cellular network

[0643] PP, PTP: Point-to-point

[0644] PPP: Point-to-Point Protocol

[0645] PRACH: Physical RACH

[0646] PRB: Physical Resource Block

[0647] PRG: Physical Resource Block Group

[0648] ProSe: Proximity service, based on proximity.

[0649] PRS: Positioning Reference Signal

[0650] PRR: Packet Receiver Radio

[0651] PS: Service included

[0652] PSBCH: Physical Sidechain Broadcast Channel

[0653] PSDCH: Physical Sidechain Downlink Channel

[0654] PSCCH: Physical Sidechain Control Channel

[0655] PSSCH: Physical Sidechain Shared Channel

[0656] PSFCH: Physical Sidechain Feedback Channel

[0657] PSCell: Main SCell

[0658] PSS: Master Synchronization Signal

[0659] PSTN: Public Switched Telephone Network

[0660] PT-RS: Phase Tracking Reference Signal

[0661] PTT: Press and Talk

[0662] PUCCH: Physical Uplink Control Channel

[0663] PUSCH: Physical Uplink Shared Channel

[0664] QAM: Quadrature Amplitude Modulation

[0665] QCI: Identifier for QoS class

[0666] QCL: Quasi-co-position

[0667] QFI: QoS Flow ID, QoS Flow Identifier

[0668] QoS: Quality of Service

[0669] QPSK: Quadrature Phase Shift Keying

[0670] QZSS: Quasi-Zenith Satellite System

[0671] RA-RNTI: Random Access RNTI

[0672] RAB: Radio Access Bearer, Random Access Burst

[0673] RACH: Random Access Channel

[0674] RADIUS: Remote authentication dialing in user services

[0675] RAN: Wireless Access Network

[0676] RAND: Random number (used for authentication)

[0677] RAR: Random Access Response

[0678] RAT: Random Access Technology

[0679] RAU: Routing Area Update

[0680] RB: Resource Block, Radio Bearer

[0681] RBG: Resource Block Group

[0682] REG: Resource Element Group

[0683] Rel: Release

[0684] REQ: Request

[0685] RF: Radio Frequency

[0686] RI: Level Indicator

[0687] RIV: Resource Indicator Value

[0688] RL: Wireless Link

[0689] RLC: Radio Link Control, Radio Link Control Layer

[0690] RLC AM: RLC Confirmation Mode

[0691] RLC UM: RLC Unconfirmed Mode

[0692] RLF: Wireless Link Failure

[0693] RLM: Radio Link Monitoring

[0694] RLM-RS: Reference signal used for RLM

[0695] RM: Registration Management

[0696] RMC: Reference Measurement Channel

[0697] RMSI: Remaining MSI, Remaining Minimum System Information

[0698] RN: Delayed Node

[0699] RNC: Wireless Network Controller

[0700] RNL: Wireless Network Layer

[0701] RNTI: Temporary Identity for Wireless Networks

[0702] ROHC: Robust header compression

[0703] RRC: Radio Resource Control (RRC)

[0704] RRM: Unlimited Resource Management

[0705] RS: Reference signal

[0706] RSRP: Reference Signal Received Power

[0707] RSRQ: Reference Signal Reception Quality

[0708] RSSI: Received Signal Strength Indicator

[0709] RSU: Road Test Unit

[0710] RSTD: Reference Signal Time Difference

[0711] RTP: Real-Time Protocol

[0712] RTS: Ready to Send

[0713] RTT: Round Trip Time

[0714] Rx: Receiving, receiving, receiver

[0715] S1AP: S1 Application Protocol

[0716] S1-MME: S1 used for the control plane

[0717] S1-U: S1 used for the user plane

[0718] S-CSCF: Service CSCF

[0719] S-GW: Service Gateway

[0720] S-RNTI: Temporary Identity for SRNC Wireless Network

[0721] S-TMSI: SAE Temporary Mobile Station Identifier

[0722] SA: Standalone operation mode

[0723] SAE: System Architecture Evolution

[0724] SAP: Service Access Points

[0725] SAPD: Service Access Point Descriptor

[0726] SAPI: Service Access Point Identifier

[0727] SCC: Subcomponent Carrier, SubCC

[0728] SCell: Sub-cell

[0729] SCEF: Service Capability Exposure Functionality

[0730] SC-FDMA: Single-Carrier Frequency Division Multiple Access

[0731] SCG: Sub-cell Group

[0732] SCM: Security Context Management

[0733] SCS: Subcarrier Spacing

[0734] SCTP: Stream Control Transport Protocol

[0735] SDAP: Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0736] SDL: Supplementing the downlink

[0737] SDNF: Structured Data Storage Network Function

[0738] SDP: Session Description Protocol

[0739] SDSF: Structured Data Storage Function

[0740] SDT: Small Data Transfer

[0741] SDU: Service Data Unit

[0742] SEAF: Safety Anchor Function

[0743] SeNB: Sub-eNB

[0744] SEPP: Secure Edge Protection Agent

[0745] SFI: Slot Format Indicator

[0746] SFTD: Space Frequency Time Diversity, SFN, and Frame Timing Difference

[0747] SFN: System Frame Number

[0748] SgNB: Sub-gNB

[0749] SGSN: Serving GPRS Support Node

[0750] S-GW: Service Gateway; SI: System Information; SI-RNTI: System Information; RNTI

[0751] SIB: System Information Block

[0752] SIM: Subscriber Identity Module

[0753] SIP: Session Initiation Protocol

[0754] SiP: System-in-Package

[0755] SL: Sidechain

[0756] SLA: Service Level Agreement

[0757] SM: Session Management

[0758] SMF: Session Management Function

[0759] SMS: Short Message Service

[0760] SMSF: SMS Function

[0761] SMTC: Measurement Timing Configuration Based on SSB

[0762] SN: Secondary node, serial number

[0763] SoC: System on a Chip

[0764] SON: Self-Organizing Network; SpCell: Specific Cell; SP-CSI-RNTI: Semi-Persistent CSI; RNTI

[0765] SPS: Semi-persistent scheduling

[0766] SQN: Serial Number

[0767] SR: Scheduling Request

[0768] SRB: Signaling Radio Bearer

[0769] SRS: Detection Reference Signal

[0770] SS: Synchronization signal

[0771] SSB: Synchronization Signal Block

[0772] SSID: Service Set Identifier; SS / PBCH Block: SSBRI; SS / PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator

[0773] SSC: Session and Service Continuity

[0774] SS-RSRP: Reference Signal Received Power Based on Synchronization Signal

[0775] SS-RSRQ: Reference signal reception quality based on synchronization signal

[0776] SS-SINR: Signal-to-noise ratio based on synchronization signal

[0777] SSS: Subsynchronous Signal

[0778] SSSG: Search Space Set Group

[0779] SSSIF: Search Space Set Indicator

[0780] SST: Slice / Service Type

[0781] SU-MIMO: Single-user MIMO

[0782] SUL: Supplemental Uplink

[0783] TA: Time sequence advanced, tracking area

[0784] TAC: Tracking Region Code

[0785] TAG: Timing Advancement Group

[0786] TAI: Tracking Regional Identity

[0787] TAU: Tracking Area Updates

[0788] TB: Transport Block

[0789] TBS: Transport Block Size

[0790] TBD: To be defined

[0791] TCI: Transport Configuration Indicator

[0792] TCP: Transmission and Communication Protocol

[0793] TDD: Time Division Duplex

[0794] TDM: Time Division Multiplexing

[0795] TDMA: Time Division Multiple Access

[0796] TE: Terminal Equipment

[0797] TEID: Tunnel Endpoint Identifier

[0798] TFT: Business Flow Template

[0799] TMSI: Temporary Mobile Subscriber Identity

[0800] TNL: Transport Network Layer

[0801] TPC: Transmission Power Control

[0802] TPMI: Transmit Precoding Matrix Indicator

[0803] TR: Technical Report

[0804] TRP, TRxP: Transmitter / Receiver Point

[0805] TRS: Tracking Reference Signal

[0806] TRx: Transceiver

[0807] TS: Technical Specifications, Technical Standards

[0808] TTI: Transmission Time Interval

[0809] Tx: Transmission, transmission, transmitter

[0810] U-RNTI: Temporary Identity for UTRAN Wireless Network

[0811] UART: Universal Asynchronous Receiver / Transmitter

[0812] UCI: Uplink Control Information

[0813] UE: User Equipment

[0814] UDM: Unified Data Management

[0815] UDP: User Datagram Protocol

[0816] UDSF: Unstructured Data Storage Network Function

[0817] UICC: General Purpose Integrated Circuit Card

[0818] UL: Uplink

[0819] UM: Unconfirmed Mode

[0820] UML: Unified Modeling Language

[0821] UMTS: Universal Mobile Telecommunications System

[0822] UP: User plane

[0823] UPF: User Plane System

[0824] URI: Uniform Resource Identifier

[0825] URL: Uniform Resource Locator

[0826] URLLC: Ultra-reliable and low-latency

[0827] USB: Universal Serial Bus

[0828] USIM: Universal Subscriber Identity Module

[0829] USS: UE-specific search space

[0830] UTRA: UMTS Terrestrial Wireless Access

[0831] UTRAN: Universal Terrestrial Radio Access Network

[0832] UwPTS: Uplink Pilot Slot

[0833] V2I: Vehicle to Infrastructure

[0834] V2P: Vehicle to Pedestrian

[0835] V2V: Vehicle to Vehicle

[0836] V2X: Vehicles to Everything

[0837] VIM: Virtual Infrastructure Manager

[0838] VL: Virtual Link

[0839] VLAN: Virtual LAN, Virtual Local Area Network

[0840] VM: Virtual Machine

[0841] VNF: Virtualized Network Function

[0842] VNFFG: VNF forwarding image

[0843] VNFFGD: VNF forwarding graph descriptor

[0844] VNFM: VNF Manager

[0845] VoIP: Voice over IP, Voice over Internet Protocol (IoT)

[0846] VPLMN: Accessed Public Land Mobile Network

[0847] VPN: Virtual Private Network

[0848] VRB: Virtual Resource Block

[0849] WiMAX: Global Microwave Access Interoperability

[0850] WLAN: Wireless Local Area Network

[0851] WMAN: Wireless Metropolitan Area Network

[0852] WPAN: Wireless Personal Area Network

[0853] X2-C: X2-Control Plane

[0854] X2-U: X2-User Plane

[0855] XML: Extensible Markup Language

[0856] XRES: Expected User Response

[0857] XOR: Exclusive OR

[0858] ZC: Zadoff-Chu sequence

[0859] ZP: Zero Power

[0860] the term

[0861] For the purposes of this document, the following terms and definitions may be used in the examples and embodiments discussed herein.

[0862] The term "application" can refer to a complete and deployable package or environment that implements specific functions within an operating environment. Terms such as "AI / ML application" can refer to applications that include some AI / ML models and application-level descriptions.

[0863] As used herein, the term "circuit" refers to a hardware component (such as electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc.), which is part of or includes a hardware component configured to provide the described functionality. In some embodiments, a circuit may execute one or more software programs or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical / electronic system) and program code for performing the functionality. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0864] As used herein, the term "processor circuit" refers to, is part of, or includes circuitry capable of sequentially and automatically performing a sequence of arithmetic or logical operations, or recording, storing, and / or transmitting digital data. Processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing 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 computer-executable instructions (such as program code, software modules, and / or functional flows). Processing circuitry may include multiple hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) accelerators and / or deep learning (DL) accelerators. The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry."

[0865] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as a bus, I / O interface, peripheral component interface, network interface card, etc.

[0866] As used herein, the term "User Equipment" or "UE" refers to a device with wireless communication capabilities and can describe a remote user of network resources in a communication network. The term "User Equipment" or "UE" may be considered synonymous with and may be referred to as: client, mobile terminal, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, reconfigurable mobile device, etc. Furthermore, "User Equipment" or "UE" can include any type of wireless / wired device or any computing device containing a wireless communication interface.

[0867] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or refers to the following terms: network computer, network hardware, network device, network node, router, switch, hub, bridge, wireless network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc.

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

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

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

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

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

[0873] The terms “coupling,” “communicationally coupled,” and their derivatives are used herein. The term “coupling” can mean two or more elements in direct physical or electrical contact with each other, can mean two or more elements in indirect contact but still cooperating or interacting with each other, and / or can mean one or more other elements coupled or connected between elements considered to be coupled. The term “direct coupling” can mean two or more elements in direct contact with each other. The term “communicationally coupled” can mean two or more elements in contact with each other through a communication means, including via wires or other interconnections, via wireless communication channels or links, etc.

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

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

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

[0877] The term "primary cell" refers to an MCG cell operating on the primary frequency, in which the user equipment (UE) performs the initial connection establishment procedure or initiates a connection reconstruction procedure.

[0878] The term "primary SCG cell" refers to an SCG cell in which the UE performs random access during reconfiguration in a synchronization process used for DC operation.

[0879] The term "subcell" refers to a cell that provides additional radio resources on top of a specific cell used by a UE configured with CA.

[0880] The term "subcell group" refers to a subset of serving cells, including the PSCell used by the UE with DC configured and zero or more subcells.

[0881] The term "serving cell" refers to the primary cell of a UE that is in RRC_CONNECTED and has not been configured with CA / DC. There is only one serving cell consisting of the primary cell.

[0882] The term “serving cell” or “multiple serving cells” refers to a collection of cells, including (multiple) specific cells and all subcells for a UE that is in RRC_CONNECTED and configured with CA / .

[0883] The term “specific cell” refers to the PCell of the MCG or the PSCell of the SCG used for DC operation; otherwise, “specific cell” refers to the Pcell.

[0884] The term "machine learning" or "ML" refers to the use of a computer system that implements algorithms and / or statistical models to perform (multiple) specific tasks without using explicit instructions but instead relying on patterns and reasoning. ML algorithms build or estimate (multiple) mathematical models (called "ML models," etc.) based on sample data (referred to as "training data," "model training information," etc.) to make predictions or decisions without explicit programming to perform such tasks. Typically, an ML algorithm is a computer program that learns from experience related to some tasks and some performance measures, and an ML model is any object or data structure generated after the ML algorithm has been trained with one or more training datasets. After training, the ML model can be used to make predictions on new datasets. Although the term "ML algorithm" refers to a different concept than the term "ML model," these terms are used interchangeably for the purposes of this disclosure, as discussed herein.

[0885] The terms "machine learning model," "ML model," etc., can also refer to ML methods and concepts used by ML-assisted solutions. An "ML-assisted solution" is a solution that uses ML algorithms to solve a specific use case during the operational process. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithms, support vector machines, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., k-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, deep reinforcement learning, etc.), neural networks, etc. Depending on the implementation, a specific ML model may have multiple sub-models as components, and the ML model can train all sub-models together. Individually trained ML models can also be chained together in an ML pipeline during inference. An "ML pipeline" is a collection of functional, feature, or functional entities specifically used in an ML-assisted solution. An ML pipeline may include one or more data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an executor. An "executor" is an entity that pipelines the ML-assisted solution using the output of the ML model for inference. The term "ML training host" refers to an entity that hosts the training of the model, such as a network function. The term "ML inference host" refers to an entity, such as a network function, that hosts the model during inference mode (if applicable, including both model execution and any online learning). The ML host informs the executor about the output of the ML algorithm, and the executor makes decisions about actions ("actions" are performed by the executor as a result of the output of the ML-assisted solution). The term "model inference information" refers to information used as input to the ML model used to determine inference. The data used to train the ML model and the data used to determine inference may overlap, but "training data" and "inference data" refer to different concepts.

Claims

1. An apparatus of a user equipment (UE), the apparatus comprising: a memory to store configuration information to indicate a presence of a dynamic transform precoder indication for a downlink control information (DCI) format for an active uplink (UL) bandwidth part (BWP) of a serving cell; and a processor circuit coupled to the memory, the processor circuit to: generate, based on the configuration information, first power headroom information related to transform precoder disable and second power headroom information related to the transform precoder enable; and report the first power headroom information and the second power headroom information to a next generation node B (gNB).

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

3. The apparatus of claim 2, wherein, the processor circuit is further to decode a DCI, the DCI including 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_1 or 0_2.

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

6. The apparatus of claim 1, wherein, At least one of the first power headroom information or the second power headroom information includes a maximum output power reduction value, P CMAX,f,c (i).

7. The apparatus of any of claims 1-6, wherein, the processor circuit is to disable the transform precoder to transmit a cyclic prefix (CP)-orthogonal frequency-division multiplexing (OFDM) waveform and 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, the instructions, 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) includes an indication of whether a transform precoder is enabled or disabled; generate, based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information, first power headroom information; generate second power headroom information based on the assumed PUSCH information, wherein generate, if the transform precoder is enabled for the actual PUSCH transmission, second power headroom information based on transform precoder disable and, if the transform precoder is disabled for the actual PUSCH transmission, the second power headroom information based on transform precoder enable; and report the first power headroom information and the 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_1 or 0_2.

10. The one or more computer-readable media of claim 7, wherein, the first power headroom information and the second power headroom information are 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 for transmission of the PUSCH transmission having a cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) waveform and is enabled for transmission of the PUSCH transmission having 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, from the gNB, the hypothetical PUSCH information.

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

14. One or more computer-readable media having instructions stored thereon, the instructions, when executed by one or more processors of a next generation NodeB (gNB), configure the gNB to: encode, for transmission to a user equipment (UE), configuration information indicating that downlink control information (DCI) includes an indication of whether a transform precoder is enabled or disabled; and receiving first power headroom information from the UE based on an actual physical uplink shared channel (PUSCH) transmission and the configuration information, and receiving second power headroom information from the UE based on an assumed PUSCH transmission, 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 the second power headroom information 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 DCI format 0_1 or 0_2.

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

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

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 having the indication of whether the transform precoder is enabled or disabled.

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

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

Images