Quality of service management for protocol data unit sets

Abstract

Apparatus and methods for managing quality of service for a protocol data unit (PDU) set include providing alternative service requirements for a protocol data unit (PDU) set supporting data traffic of an application executing on a user equipment (UE), wherein alternative service requirements for the PDU set include one or more Quality of Service (QoS) reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value that the application can adapt. The apparatus and method also include adapting parameters of the set of PDUs in response to an indication that the link between the UE and the network is no longer capable of ensuring QoS streaming of the set of PDUs.

Description

[0001] Related Applications

[0002] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 370,916, filed on August 9, 2022, entitled “Quality of Service Management for Protocol Data Unit Sets,” and U.S. Provisional Patent Application No. 63 / 370,900, filed on August 9, 2022, entitled “Coordinating Rate Adaptation in Wireless Communications,” the entire contents of both applications are incorporated herein by reference for all purposes. Background Art

[0003] The following relates generally to wireless communications, and more particularly to quality of service (QoS) management for sets of protocol data units.

[0004] In 5G communication systems, the QoS model is based on QoS flows. QoS flows are the finest level of granularity within 5G communication systems and are the level at which policies and charging are implemented. QoS flow protocol data units (PDUs, e.g., packets) are classified and marked using unique QoS flow identifiers to enable QoS requirements to be applied to data flows.

[0005] Some applications executed on network computing devices (such as application servers) and corresponding applications executed on user equipment (UE) (such as application clients (AC)) may send and receive large amounts of information that cannot be conveyed in a single PDU, such as large amounts of audio, video, or multimedia information. For such applications, a PDU set may carry a payload of information units generated by the application. Such applications may be sensitive to QoS requirements, and changes in network conditions that reduce the ability of the network to meet the QoS requirements of QoS flows may degrade the performance of such applications. Summary of the invention

[0006] The present invention summary is a simplified summary of one or more aspects presented to provide a basic understanding of these aspects. The present invention summary is not a broad overview of all aspects contemplated, is not intended to identify the key or decisive elements of all aspects, and is not meant to delimit the scope of any or all aspects. The sole purpose of the present invention summary is to present some aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] Various aspects may include a method performed by a first communication network element, such as at an application function (AF). The method may include providing, such as to a core network (CN) element, an alternative service requirement for a protocol data unit (PDU) set for a data service supporting an application, wherein the alternative service requirement for the PDU set includes a combination of one or more quality of service (QoS) reference parameters and an application-adaptable PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value.

[0008] An AF is described. The AF may include a memory and a processor configured to send to a CN element an alternative service requirement of a protocol data unit (PDU) set supporting a data service of an application, wherein the alternative service requirement of the PDU set includes one or more quality of service (QoS) reference parameters and a combination of an application-adaptable PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value.

[0009] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, different alternative service requirements for a PDU set may include different combinations of PSDB, PSER, and GFBR values ​​to which an application may adapt.

[0010] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, different combinations of PSDB, PSER, and GFBR values ​​may be prioritized in each of the alternative service requirements.

[0011] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, the QoS reference parameters may include a bit rate, a delay budget, and an error rate applicable to a set of PDUs.

[0012] Some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein may include operations, features, components, or instructions for: receiving an indication from a CN element that a communication link between a radio access network (RAN) element and a user equipment (UE) no longer supports or is no longer able to guarantee a GFBR for a QoS flow for transmitting a PDU set (i.e., a QoS flow with PDU set capability), wherein the indication includes an identification of one of the QoS reference parameters that corresponds to one of a plurality of alternative QoS parameter sets; determining PSDB, PSER, and GFBR values ​​for the PDU set based on the identified QoS reference parameter; and updating codec settings for a service based on the PDU set based on the determined PSDB, PSER, and GFBR values.

[0013] Various aspects may include a method performed at a first core network (CN) element. The method may include: receiving from an application function (AF) alternative service requirements for a protocol data unit (PDU) set supporting a data service of an application, wherein each of the alternative service requirements of the PDU set includes one or more QoS reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value that the application can adapt to; sending a policy and charging control (PCC) rule to a second CN element based on a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters of the alternative service requirements of the PDU set; receiving from the second CN element a radio access network (RAN) element and a user device; an indication that a communication link between the RAN element and the UE no longer supports or is no longer able to guarantee a current GFBR for a QoS flow for transmitting a PDU set, wherein the indication comprises a reference to one of a plurality of alternative QoS profiles (AQPs) identifying a PSDB value, a PSER value and a GFBR value to which the application can adapt; and a notification is sent to the AF that the communication link between the RAN element and the UE no longer supports or is no longer able to guarantee the GFBR for the QoS flow for transmitting a PDU set (i.e., a QoS flow with PDU set capability), wherein the notification comprises an identification of a QoS reference parameter that can be supported among the QoS reference parameters of the alternative service requirement of the PDU set.

[0014] A first core network (CN) element is described. The first CN element may include a memory and a processor, the processor being configured to: receive from an application function (AF) alternative service requirements of a protocol data unit (PDU) set supporting a data service of an application, wherein each of the alternative service requirements of the PDU set includes one or more QoS reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value adaptable to the application; send a policy and charging control (PCC) rule to a second CN element based on a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters of the alternative service requirements of the PDU set; receive from the CN element a radio access network (R The RAN sends an indication that the communication link between the RAN element and the user equipment (UE) no longer supports or is no longer able to guarantee the current GFBR of the QoS flow for transmitting the PDU set (i.e., the QoS flow with PDU set capability), wherein the indication includes a reference to one of multiple alternative QoS profiles (AQPs) identifying the PSDB value, PSER value and GFBR value that the application can adapt to; and sends a notification to the AF that the communication link between the RAN element and the UE no longer supports or is no longer able to guarantee the GFBR of the QoS flow for transmitting the PDU set, wherein the notification includes an identification of one of the QoS reference parameters of the alternative service requirement of the PDU set that can be supported.

[0015] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, the first CN entity may be a policy control function (PCF) and the second CN entity may be a session management function (SMF).

[0016] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, the first CN entity and the second CN entity may be the same entity or co-located entities.

[0017] Various aspects may include a method performed at a first core network (CN) element. The method may include: receiving a policy and charging control (PCC) rule for supporting data services for an application from a second CN element, the data services based on a QoS requirement for a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value; establishing a QoS flow (i.e., a PDU set-capable QoS flow) for transporting a PDU set for supporting data services for the application with a radio access network (RAN) element, including sending a QoS profile for the QoS flow for transporting the PDU set and one of a plurality of alternative QoS profiles (AQP) derived from the plurality of alternative QoS parameter sets to the RAN element; receiving a QoS profile from the RAN element with a user equipment (UE); an indication that the communication link with the UE no longer supports or is no longer able to guarantee a guaranteed flow bit rate (GFBR) for the QoS flow for transmitting the PDU set, wherein the indication includes a reference to an AQP in the multiple AQPs that identifies a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a GFBR value that the RAN element can support and that the application can adapt to; and sending a notification to the second CN element that the communication link with the UE no longer supports or is no longer able to guarantee the GFBR for the QoS flow for transmitting the PDU set (i.e., a QoS flow with PDU set capability), wherein the notification includes a reference to an alternative QoS parameter set in the alternative QoS parameter set that is associated with the AQP that the RAN element can support.

[0018] A first core network (CN) element is described. The first CN element may include a memory and a processor, the processor being configured to: receive a policy and charging control (PCC) rule for supporting a data service of an application from a second CN element, the data service being based on a QoS requirement of a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value; establish a QoS flow for transmitting a PDU set of the data service of the application with a radio access network (RAN) element, including sending a QoS profile of the QoS flow (i.e., a QoS flow with PDU set capability) for transmitting the PDU set and one of a plurality of alternative QoS profiles (AQP) derived from the plurality of alternative QoS parameter sets to the RAN element; receive a QoS profile for transmitting a PDU set from the RAN element to a user equipment (UE) E) an indication that the communication link with the UE no longer supports or is no longer able to guarantee a guaranteed flow bit rate (GFBR) for the QoS flow for transmitting the PDU set (i.e., a QoS flow with PDU set capability), wherein the indication includes a reference to one of the multiple AQPs that identifies a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a GFBR value that the RAN element can support and that the application can adapt to; and sending a notification to the second CN element that the communication link with the UE no longer supports or is no longer able to guarantee the GFBR for the QoS flow for transmitting the PDU set (i.e., the QoS flow with PDU set capability), wherein the notification includes a reference to one of the alternative QoS parameter sets that is associated with the AQP that the RAN element can support.

[0019] Some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein may include: receiving an indication from a RAN element that a communication link with the UE again supports or is capable of guaranteeing a GFBR for a QoS flow for transmitting a PDU set (i.e., a QoS flow with PDU set capability); and sending a notification to a second CN element that a communication link with the UE is again capable of guaranteeing a GFBR for a QoS flow for transmitting a PDU set.

[0020] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, the first CN entity may include a session management function (SMF) and the second CN entity may include a policy control function (PCF).

[0021] In some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein, the first CN entity and the second CN entity may be the same entity or co-located entities.

[0022] Various aspects may include a method performed at a radio access network (RAN) element. The method may include: receiving an alternative quality of service (QoS) profile (AQP) for a protocol data unit (PDU) set from a core network (CN) element; determining that a communication link with a user equipment (UE) no longer supports or is no longer able to guarantee the QoS profile of a current quality of service (QoS) flow (i.e., a PDU set-capable QoS flow) for transmitting the PDU set; determining that at least one of the AQPs that can be supported for the PDU set by checking whether the RAN element can support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value; and sending an indication to the CN element that the communication link with the UE no longer supports or is no longer able to guarantee the QoS profile of the current QoS flow for transmitting the PDU set, wherein the indication includes reference parameters for one of a plurality of AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which the application can add adaptation.

[0023] A radio access network (RAN) element is described. The RAN element may include a memory and a processor, the processor being configured to: receive an alternative quality of service (QoS) profile (AQP) for a protocol data unit (PDU) set from a core network (CN) element; determine that a communication link with a user equipment (UE) no longer supports or is no longer able to guarantee the QoS profile of a current quality of service (QoS) flow (i.e., a QoS flow with PDU set capability) for transmitting the PDU set; determine that at least one of the AQPs that can be supported for the PDU set is supported by checking whether the RAN element can support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value; and send an indication to the CN element that the communication link with the UE no longer supports or is no longer able to guarantee the QoS profile of the current QoS flow for transmitting the PDU set, wherein the indication includes reference parameters for one of a plurality of AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which the application can add adaptation.

[0024] Some examples of the methods, apparatus, and non-transitory processor-readable storage media described herein may include: determining that a communication link with the UE again supports or is capable of guaranteeing a QoS profile for a QoS flow for transmitting a set of PDUs; and sending an indication to a CN element that a communication link with the UE again supports or is capable of guaranteeing a QoS profile for a QoS flow for transmitting a set of PDUs.

[0025] Some aspects may include an apparatus for wireless communication at a first network element, the apparatus may include one or more memories and one or more processors, the one or more processors coupled to the one or more memories and configured to cause the first network element to provide an alternative service requirement for a PDU set of data services supporting an application to a second network element, wherein the alternative service requirement for the PDU set includes one or more QoS reference parameters and a combination of PSDB values, PSER values, and GFBR values ​​that the application can adapt. In some aspects, the one or more processors may be further configured to cause the first network element to adapt one or more parameters for services based on the PDU set based on information received from the second network element, and if the second network element cannot support a default QoS, the second network element will transmit the information. In some aspects, different alternative service requirements in the alternative service requirements for the PDU set include different combinations of PSDB, PSER, and GFBR values ​​that the application can adapt. In some aspects, the different combinations of PSDB, PSER, and GFBR values ​​can be prioritized in each of the alternative service requirements.

[0026] In some aspects, to adapt one or more parameters for a PDU set based service based on information received in response from a second network element, the one or more processors may be further configured to cause the first network element to: receive from the second network element an indication that a communication link between a third network element and the UE is no longer able to guarantee a GFBR for a QoS flow for transmission of the PDU set, wherein the indication includes an identification of one of the QoS reference parameters corresponding to one of a plurality of alternative QoS parameter sets; determine a PSDB, PSER, and GFBR value for the PDU set based on the identified QoS reference parameter; and update a codec setting for the PDU set based service based on the determined PSDB, PSER, and GFBR values. In some aspects, the second network element may be a core network element; and may receive from the core network element an indication that a communication link between the third network element and the UE is no longer able to guarantee a GFBR for a QoS flow for transmission of the PDU set as an indication that a communication link between a radio access network (RAN) and the UE no longer supports a GFBR for a QoS flow for transmission of the PDU set.

[0027] Some aspects may include an apparatus for wireless communication at a first network element, the apparatus may include one or more memories and one or more processors, the one or more processors coupled to the one or more memories and configured to cause the first network element to: obtain a QoS profile for a QoS flow for transmitting a PDU set and one of a plurality of alternative service requirements for a PDU set supporting data services of an application, wherein each of the alternative service requirements for the PDU set includes one or more QoS reference parameters and a combination of a PSDB value, a PSER value, and a GFBR value adaptable to the application; and determine a QoS profile for a QoS flow for transmitting a PDU set and one of a plurality of alternative service requirements for a PDU set supporting data services of an application based on a QoS profile derived from the one or more QoS reference parameters for the alternative service requirements for the PDU set. In some aspects, the one or more processors may be further configured to cause the first network element to determine that the communication link with the UE is capable of guaranteeing a QoS profile for the QoS flow for transmitting the PDU set, and to provide an indication that the communication link with the UE is capable of guaranteeing a QoS profile for the QoS flow for transmitting the PDU set, wherein the indication includes a reference to an alternative QoS profile from among the multiple alternative QoS profiles that identifies a PSDB value, a PSER value, and a GFBR value that the application can adapt to; and to provide a notification that the communication link between the second element and the UE is no longer capable of guaranteeing the GFBR for the QoS flow for transmitting the PDU set, wherein the notification includes an identification of a QoS reference parameter that can be supported from among the QoS reference parameters of the alternative service requirement for the PDU set. In some aspects, the one or more processors may be further configured to cause the first network element to determine that the communication link with the UE is capable of guaranteeing a QoS profile for the QoS flow for transmitting the PDU set, and to provide an indication that the communication link with the UE is capable of guaranteeing a QoS profile for the QoS flow for transmitting the PDU set. In some aspects, the first network element may include a policy control function (PCF) network element; may obtain alternative service requirements for a PDU set supporting data services of an application from an application function (AF) network element; may provide PCC rules to an SMF network element; may receive from the SMF network element an indication that a communication link between a second network element and a UE is no longer able to guarantee a current GFBR of a QoS flow for transporting the PDU set; and may provide to the AF network element a notification that a communication link between the second element and the UE is no longer able to guarantee a GFBR of a QoS flow for transporting the PDU set.

[0028] Some aspects may include an apparatus for wireless communication at a first network element, the apparatus may include one or more memories and one or more processors, the one or more processors coupled to the one or more memories and configured to cause the first network element to: obtain a PCC rule for supporting data traffic for an application, the data traffic may be based on a QoS requirement of a PDU set and a plurality of alternative QoS parameter sets including a PSDB value and a PSER value; establish a QoS flow for transmitting the PDU set for supporting the data traffic for the application with a second network element, wherein to establish the QoS flow, the one or more processors may be configured to cause the first network element to provide the second network element with a QoS configuration of the QoS flow for transmitting the PDU set file and one of a plurality of alternative QoS profiles derived from the plurality of alternative QoS parameter sets; receiving from the second network element an indication that the communication link with the UE can no longer guarantee the GFBR for the QoS flow for transmitting the PDU set, wherein the indication includes a reference to one of the plurality of alternative QoS profiles that identifies a PSDB value, a PSER value, and a GFBR value that the second network element can support and that the application can adapt to; and providing a notification that the communication link with the UE can no longer guarantee the GFBR for the QoS flow for transmitting the PDU set, wherein the notification includes a reference to one of the alternative QoS parameter sets in the alternative QoS parameter set that is associated with the AQP that the second network element can support. In some aspects, different alternative QoS profiles in the plurality of alternative QoS profiles for the PDU set include different combinations of PSDB, PSER, and GFBR. In some aspects, different alternative QoS profiles in the plurality of alternative QoS profiles for the PDU set include different combinations of PSDB, PSER, GFBR, and maximum data burst size (MDBV). In some aspects, the one or more processors may be further configured to cause the first network element to: receive from the second network element an indication that the communication link with the UE is capable of guaranteeing a GFBR for a PDU set session for application data services communicated between the second network element and the UE; and provide a notification that the communication link with the UE is capable of guaranteeing a GFBR for a QoS flow of a transport PDU set in a PDU session for application data services communicated between the second element and the UE. In some aspects, the first network element may be an SMF network element, may receive from a PCF network element a PCC rule for supporting application data services, the second network element may be a radio access network element, may send to the PCF network element a notification that the communication link with the UE is no longer capable of guaranteeing a GFBR for a QoS flow of a transport PDU set, and may send to the PCF network element a notification that the communication link with the UE is capable of guaranteeing a GFBR for a QoS flow of a transport PDU set in a PDU session for application data services communicated between the second element and the UE.

[0029] Some aspects may include an apparatus for wireless communication at a first network element, the apparatus may include: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories and configured to cause the first network element to: obtain an alternative QoS profile for a PDU set from a second network element; determine that a communication link with a UE is no longer able to guarantee a QoS profile for a current QoS flow for transmitting the PDU set; determine that at least one of the alternative QoS profiles for the PDU set can be supported by checking whether the first network element can support a GFBR value, a PSDB value, and a PSER value; and provide an indication to the second network element that the communication link with the UE is no longer able to guarantee the QoS profile for the current QoS flow for transmitting the PDU set, wherein the indication includes a reference parameter for an alternative QoS profile of a plurality of alternative QoS profiles, the reference parameter including a PSDB value, a PSER value, and a GFBR value to which an adaptation can be added. In some aspects, different ones of the alternative QoS profiles for the PDU set include different combinations of PSDB, PSER, and GFBR. In some aspects, different ones of the alternative QoS profiles for the PDU set include different combinations of PSDB, PSER, GFBR, and Maximum Data Burst Size (MDBV). In some aspects, the one or more processors may be further configured to cause the first network element to: determine that a communication link with the UE is capable of guaranteeing a QoS profile for a QoS flow for transmitting the PDU set; and provide an indication to the second network element that a communication link with the UE is capable of guaranteeing a QoS profile for a QoS flow for transmitting the PDU set. In some aspects, the first network element may be a radio access network, and the second network element may be a core network element.

[0030] Some aspects may include an apparatus for wireless communication at a first network element, the apparatus may include one or more memories and one or more processors, the one or more processors coupled to the memory and configured to cause the first network element to: receive an indication of a change in a bit rate or frame rate of a data flow between a second network element and a UE; in response to receiving the indication, establish one or more QoS parameters with a third network element to support the change in the bit rate or frame rate of the data flow; and provide a configuration message to the UE, the configuration message configuring the one or more UE communication parameters to implement the established QoS parameters. In some aspects, to establish the QoS parameters with the third network element, the one or more processors may be further configured to receive from the third network element reference parameters of one of a plurality of alternative QoS profiles previously established with the third network element for a set of PDUs supporting the data flow. In some aspects, the one or more processors may be further configured to establish with the third network element a plurality of alternative QoS profiles as part of establishing the data flow to the UE, wherein each of the alternative QoS profiles may be associated with the reference parameters and support a particular bit rate or frame rate between the first network element and the UE that is suitable for the communication link supporting the data flow. In some aspects, the one or more processors may be further configured to provide a request to the third network element to reestablish or update the QoS parameters.

[0031] Some aspects may include an apparatus for wireless communication at a first network element, the apparatus may include one or more memories and one or more processors, the one or more processors coupled to the one or more memories and configured to cause the first network element to: obtain an indication of a change in a bit rate or frame rate of a data flow; and establish one or more QoS parameters with a second network element to achieve the change in the bit rate or the frame rate. In some aspects, the one or more processors may be further configured to establish the QoS parameters with the second network element by providing the second network element with reference parameters of one of a plurality of alternative QoS profiles previously established with the second network element for a set of PDUs supporting the data flow. In some aspects, the one or more processors may be further configured to establish a plurality of alternative QoS profiles with the second network element as part of establishing a data flow to a UE, wherein each of the alternative QoS profiles may be associated with an identifier and support a particular bit rate or frame rate for a communication link between the second network element and the UE supporting the data flow. In some aspects, the one or more processors may be further configured to cause the first network element to: receive a request to reestablish or update QoS parameters from the second network element; and adjust a bit rate or frame rate of a data flow associated with the request to reestablish or update QoS parameters. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1A is a system block diagram illustrating an example communication system suitable for implementing any of the various aspects.

[0033] Figure 1B is a system block diagram illustrating an example decomposed base station architecture suitable for implementing any of the various aspects.

[0034] Figure 1C is a system block diagram illustrating an example communication system suitable for implementing any of the various aspects.

[0035] Figure 2 is a component block diagram illustrating an example computing and wireless modem system suitable for implementing any of the various aspects.

[0036] Figure 3 is a component block diagram illustrating a software architecture suitable for implementing any of the various aspects including a radio protocol stack for user plane and control plane in wireless communications.

[0037] Figure 4A is a block diagram illustrating an apparatus (eg, AF) for wireless communication that supports QoS management for a set of PDUs in accordance with various aspects.

[0038] Figure 4B is a block diagram illustrating an apparatus (eg, CN element) for wireless communication that supports QoS management for a set of PDUs in accordance with various aspects.

[0039] Figure 4C is a block diagram illustrating an apparatus (eg, CN element) for wireless communication that supports QoS management for a set of PDUs in accordance with various aspects.

[0040] Figure 4D is a block diagram illustrating an apparatus (eg, a RAN element) for wireless communications that supports QoS management for a set of PDUs in accordance with various aspects.

[0041] Figure 5A is a message flow diagram illustrating the operation of QoS flow establishment and notification control according to various aspects.

[0042] Figure 5A is a message flow diagram illustrating the operation of QoS flow establishment and notification control according to various aspects.

[0043] Figure 5C and Figure 5D is a table illustrating example alternative QoS parameters and alternative QoS parameter sets configured for use with PDU sets in accordance with various aspects.

[0044] Figure 6is a process flow diagram illustrating a method for QoS management for a PDU set according to various specific implementations and aspects.

[0045] Figure 7 is a process flow diagram illustrating a method for QoS management for a PDU set according to various specific implementations and aspects.

[0046] Fig. 8A is a process flow diagram illustrating a method for QoS management for a PDU set according to various specific implementations and aspects.

[0047] Figure 8B is a process flow diagram illustrating operations that may be performed as part of a method for QoS management for a PDU set in accordance with various implementations and aspects.

[0048] Fig.9A is a process flow diagram illustrating a method for QoS management for a PDU set according to various specific implementations and aspects.

[0049] Fig. 9B is a process flow diagram illustrating operations that may be performed as part of a method for QoS management for a PDU set in accordance with various implementations and aspects.

[0050] Fig. 10A is a block diagram illustrating a UE supporting wireless communication in accordance with various aspects.

[0051] Fig. 10B is a block diagram illustrating RAN elements supporting wireless communications in accordance with various aspects.

[0052] Fig. 10C is a block diagram illustrating elements of a CN element supporting wireless communications in accordance with various aspects.

[0053] Fig.11A is a process flow diagram illustrating a method for managing broadcast signals according to various aspects.

[0054] Fig. 11B is a process flow diagram illustrating operations that may be performed as part of a method for coordinated rate adaptation in accordance with various aspects.

[0055] Fig. 12A is a process flow diagram illustrating a method for coordinated rate adaptation in accordance with various aspects.

[0056] Fig. 12B and Fig. 12C is a process flow diagram illustrating operations that may be performed as part of a method for coordinated rate adaptation in accordance with various implementations and aspects.

[0057] Fig.13Ais a process flow diagram illustrating a method for coordinated rate adaptation in accordance with various aspects.

[0058] FIG. 13B to FIG. 13E is a process flow diagram illustrating operations that may be performed as part of a method for coordinated rate adaptation in accordance with various aspects.

[0059] Fig.14 is a block diagram of components of a UE suitable for use with the various aspects.

[0060] Fig.15 is a component block diagram of a network device suitable for use with various aspects. DETAILED DESCRIPTION

[0061] Various aspects will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar components. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

[0062] In some 5G communication networks, when an established data communication flow to an application executed on a user equipment (UE) becomes unavailable, data communication to / from the application may be interrupted when the network establishes a new connection. According to one or more aspects, an alternative parameter set (referred to as an "alternative QoS profile") for transmitting data to an application may be provided, which the communication network can use if the current data flow is no longer available. The availability of an alternative QoS profile enables the communication network to switch to another communication data flow instead of performing time-consuming operations to renegotiate the QoS requirements of the new data flow. An alternative parameter set may be provided for a set of packet data units (PDUs) that carry data to an application. One or more aspects include signaling between various network elements involved in identifying an alternative parameter set and changing the parameter set to support changes in communication flows when switching in a data flow is required.

[0063] According to one or more other aspects, operations can be implemented in one or more network elements for communicating when there is a change in bit rate or frame rate on an application executing on a UE, establishing new QoS parameters that will support the new bit rate or frame rate, and configuring communication parameters to implement the new QoS parameters. These operations enable switching to QoS parameters in a communication link to support the new bit rate or frame rate of the application without delays in renegotiating QoS requirements.

[0064] Some applications executed on a network computing device (such as an application server) and corresponding applications executed on a UE (such as an application client (AC)) can send and receive a large amount of information that cannot be conveyed in a single PDU, such as a large amount of audio, video, or multimedia information. For example, extended reality (XR) applications (e.g., virtual reality (VR) applications, augmented reality (AR) applications, mixed reality (MX) applications, and other similar applications) can generate a large amount of audio, video, or multimedia information, and the units (e.g., frames) of such information are too large to be conveyed in a single PDU. In order to convey (send, transmit) data generated by such applications, a PDU set is more appropriate.

[0065] A "PDU set" consists of one or more PDUs that carry a payload of an information unit generated at the application level (e.g., a frame or video slice for an XR media service, for example, as may be used in certain standards and technical reports such as Third Generation Partnership Project (3GPP) Technical Report (TR) 26.926

[27] ). In some implementations, an application must receive all PDUs in a PDU set to use the information in the payload conveyed by the PDU set. In some implementations, an application may recover part or all of an information unit when some PDUs are not received.

[0066] Applications that transmit and receive large amounts of information may be sensitive to QoS requirements. Changes in network conditions that reduce the network's ability to meet the QoS requirements of QoS flows may degrade the performance of such applications. In order to enable applications to adapt to changes in network conditions more quickly, some applications may utilize alternative QoS profiles or alternative service requirements. Alternative QoS profiles or alternative service requirements represent a combination of QoS parameters, including a packet delay budget (PDB), a packet error rate (PER), a guaranteed flow bit rate (GFBR), and in some cases a maximum data burst volume (MDBV) to which the application service can adapt. Additionally or alternatively, an alternative QoS profile or alternative service requirement represents a combination of QoS parameters that are acceptable or adaptable to an application executing on a UE. Additionally or alternatively, an alternative QoS profile or alternative service requirement represents a combination of QoS parameters, which may include a PDB to which the application can adapt, a PER to which the application can adapt, a GFBR to which the application can adapt, an MDBV to which the application can adapt, and a combination of these parameters. The availability of an alternative QoS profile or alternative service requirements enables the communication network to quickly switch to another QoS (i.e., one of the AQPs) rather than performing time-consuming operations to renegotiate the QoS requirements of the data flow. In various specific implementations, an alternative QoS profile can be provided for a GFBR QoS flow with notification control enabled. However, conventional AQP features are only applicable to PDU-based QoS flows. There is currently no mechanism that enables the use of an alternative QoS profile with a PDU-set-based QoS flow.

[0067] Various devices for wireless communication configured to perform operations of various aspects described herein may include a network element configured to act as an application function (AF), one or more network elements configured to act as a core network (CN) element, and a network element configured to act as a RAN element. These various devices may be configured to perform operations to utilize alternative service requirements or alternative QoS profiles (AQPs) with PDU sets, so that various network elements can quickly adapt to changes and changes in network conditions that reduce the ability of the network to meet the QoS requirements of applications supported by data services using PDU sets. In various aspects, one or more network elements may be configured with alternative QoS parameter sets, which include QoS parameters configured for use with PDU sets. In some aspects, the alternative QoS parameters configured for use with PDU sets may include PDU set delay budget (PSDB), PDU set error rate (PSER), guaranteed flow bit rate (GFBR) and / or maximum data burst size (MDBV). In various aspects, an alternative QoS profile or alternative service requirement configured for use with a PDU set may include QoS parameters PSDB, PSER, GFBR, and MDBV to which the application service can adapt. In some aspects, an alternative PDU set QoS parameter set may define an alternative set of QoS parameters for service data flows that require a QoS flow with PDU set capabilities. In some specific implementations, an alternative PDU set QoS parameter set may include PSER, PSDB, an uplink (UL) guaranteed bit rate QoS parameter, and a downlink (DL) guaranteed bit rate QoS parameter.

[0068] In some aspects, the apparatus for wireless communication may be a CN element (e.g., a policy control function (PCF), a session management function (SMF), or another similar element of the CN) that may be configured to perform operations for QoS flow binding configured for a PDU set. In some aspects, a CN element (e.g., an SMF or another suitable CN element) may provide a reference to an AQP that includes information related to a PDU set. For example, the SMF may be configured to provide a reference to a PCF to an AQP that includes information related to a PDU set. In some aspects, a CN element (e.g., a PCF or another suitable CN element) may be configured to report QoS reference parameters to an AF or request an alternative QoS parameter set corresponding to an alternative QoS parameter set referenced by another CN element (e.g., by an SMF or another suitable CN element).

[0069] In some aspects, the apparatus for wireless communication may be an AF configured to provide alternative service requirements in priority order. In some implementations, the alternative service requirements may include one or more QoS reference parameters in priority order, or one or more requested alternative QoS parameter sets in priority order (e.g., requested 5GS delay for a PDU set, requested error rate for a PDU set, and / or requested guaranteed flow bit rate for a PDU set).

[0070] In various aspects, the AF may send to the PCF alternative service requirements for a PDU set that supports data services for an application. In such aspects, the service requirements for the PDU set may include one or more QoS reference parameters and a combination of PSDB values, PSER values, and GFBR values ​​that the application can adapt. In some aspects, different alternative service requirements for the PDU set may include different combinations of PSDB, PSER, and GFBR values ​​that the application can adapt. In some aspects, different combinations of PSDB, PSER, and GFBR values ​​may be configured or arranged in priority order in each of the alternative service requirements. In some aspects, the QoS reference parameters may include a bit rate, delay budget, and error rate applicable to the PDU set.

[0071] In some aspects, the AF may receive an indication from the PCF that a communication link between the RAN element and the UE is no longer supported and therefore no longer able to guarantee a GFBR for a set of PDUs being communicated between the RAN element and the UE. In such aspects, the indication may include an identification of one of the QoS reference parameters corresponding to one of a plurality of alternative QoS parameter sets. The AF may determine a PSDB, PSER, and GFBR value for the set of PDUs based on the identified QoS reference parameter. The AF may update a codec setting for the set of PDUs being communicated between the RAN element and the UE based on the determined PSDB, PSER, and GFBR values.

[0072] In various aspects, a CN element (e.g., a PCF or another suitable CN element) may receive from an AF an alternative service requirement for a PDU set supporting a data service of an application. In such aspects, each of the alternative service requirements for the PDU set may include one or more QoS reference parameters and a combination of a PSDB value, a PSER value, and a GFBR value that the application can adapt. In some aspects, the CN element may send a policy and charging control (PCC) rule to a session management function (SMF) based on a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters of the alternative service requirements for the PDU set. In some aspects, the CN element may receive from the SMF an indication that a communication link between a device for wireless communication configured as a radio access network (RAN) element and a UE no longer supports and is therefore no longer able to guarantee a current GFBR for a PDU set being communicated between the RAN element and the UE (e.g., a notification that "the GFBR of the QoS flow is no longer supported or can no longer be guaranteed"). In such aspects, the indication may include a reference to one of a plurality of alternative QoS profiles (AQPs) that identifies an application-adaptable PSDB value, a PSER value, and a GFBR value. In some aspects, the CN element may send a notification to the AF that the communication link between the RAN element and the UE no longer supports or is no longer able to guarantee the GFBR for the PDU set being communicated between the RAN element and the UE, wherein the notification includes an identification of one of the QoS reference parameters of the alternative service requirement for the PDU set that can be supported.

[0073] In various aspects, a CN element (e.g., an SMF or another suitable CN element) may receive from a policy control function (PCF) a policy and charging control (PCC) rule for supporting data services for an application, the data services being based on QoS requirements for a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value. In some aspects, the CN element may establish a QoS flow for transporting a PDU set for supporting data services for the application (i.e., a PDU set-capable QoS flow for transporting the PDU set) with a radio access network (RAN) element for the PDU set, including sending a QoS profile for the PDU set and one of a plurality of alternative QoS profiles (AQPs) derived from the plurality of alternative QoS parameter sets to the RAN element. In some aspects, the CN element may receive an indication from the RAN element that the communication link with the UE no longer supports and therefore is no longer able to guarantee a guaranteed flow bit rate GFBR for a QoS flow of a transport PDU set for application data traffic communicated between the RAN element and the UE (i.e., a PDU set capable QoS flow) (e.g., a notification that "GFBR for the QoS flow is no longer supported or no longer able to be guaranteed"). In such aspects, the indication may include a reference to one of a plurality of AQPs that identifies a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a GFBR value that the RAN element can support and that the application can adapt. In some aspects, the CN element may send a notification to the PCF that the communication link with the UE no longer supports or is no longer able to guarantee the GFBR for the PDU set, wherein the notification includes a reference to one of the alternative QoS parameter sets that is associated with the AQP that the RAN element can support.

[0074] In some aspects, the CN element may receive an indication from the RAN element that the communication link with the UE is again supported and thus can again guarantee the GFBR of the QoS flow for transporting PDU sets for application data traffic communicated between the RAN element and the UE (i.e., a PDU set-capable QoS flow). In such aspects, the CN element may send a notification to the PCF that the communication link with the UE is again supported and thus can again guarantee the GFBR of the QoS flow for transporting PDU sets for application data traffic communicated between the RAN element and the UE (i.e., a PDU set-capable QoS flow).

[0075] In various aspects, a RAN element may receive an alternative quality of service (QoS) profile (AQP) for a set of protocol data units (PDUs) from a CN element. In some aspects, a RAN element may determine that a communication link with a user equipment (UE) no longer supports and therefore can no longer guarantee a quality of service (QoS) profile for a current set of PDUs being communicated between the RAN element and the UE. In some aspects, the RAN element may determine that at least one of the AQPs for the PDU set may be supported by checking whether the RAN element can support a GFBR value, a PSDB value, and a PSER value. In some aspects, the RAN element may send an indication to the CN element that the communication link with the UE no longer supports or can no longer guarantee a QoS profile for a QoS flow for the current set of PDUs being communicated between the RAN element and the UE (e.g., a notification that “GFBR for the QoS flow is no longer supported or can no longer be guaranteed”). In such aspects, the indication may include reference parameters for one of the multiple AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which an application may add adaptation. In some aspects, the RAN element may determine that the communication link with the UE is again supported and thus the QoS profile for the set of PDUs being communicated between the RAN element and the UE can be again guaranteed. In such aspects, the RAN element may send an indication to the CN element that the communication link with the UE is again supported and thus the QoS profile for the set of PDUs being communicated between the RAN element and the UE can be again guaranteed.

[0076] Various implementations improve network communications and wireless communications by enabling AF, CN elements, and RAN elements to perform operations to utilize AQP with PDU sets. In addition, utilizing AQP with PDU sets enables various network elements to quickly adapt to changes and variations in network conditions that degrade the network's ability to meet the QoS requirements of applications. In this way, various implementations improve the operational efficiency of network communications and wireless communications elements and systems.

[0077] The term "user equipment" (UE) is used herein to refer to any or all of the following: wireless communication devices, wireless appliances, cellular phones, smart phones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, smartbooks, ultrabooks, handheld computers, wireless email receivers, Internet-enabled multimedia cellular phones, wireless router devices, medical devices and equipment, biosensors / devices, wearable devices (including smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings and smart bracelets)), entertainment devices (e.g., wireless game controllers, music and video players, satellite radios, etc.), wireless network-enabled Internet of Things (IoT) devices (including smart meters / sensors, industrial manufacturing equipment, large and small machines and appliances for home or business use), wireless communication elements within autonomous and semi-autonomous vehicles, wireless devices attached to or incorporated into various mobile platforms, and similar electronic devices that include memory, wireless communication components and programmable processors.

[0078] The term "system on chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that includes multiple resources or processors integrated on a single substrate. A single SOC may include circuits for digital, analog, mixed signal, and radio frequency functions. A single SOC may also include any number of general or special processors (digital signal processors, modem processors, video processors, etc.), memory blocks (such as ROM, RAM, flash memory, etc.), and resources (such as timers, voltage regulators, oscillators, etc.). Each SOC may also include software for controlling the integrated resources and processors, as well as for controlling peripheral devices.

[0079] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs that are coupled together via high-speed communication circuits and packaged together in close proximity (such as on a single motherboard or in a single wireless device). The proximity of the SOCs facilitates high-speed communication and sharing of memory and resources.

[0080] As used herein, the terms "network", "system", "wireless network", "cellular network" and "wireless communication network" may interchangeably refer to a portion or all of a wireless network of a carrier associated with a wireless device and / or a subscription on a wireless device. The techniques described herein may be used in various wireless communication networks, such as code division multiple access (CDMA), time division multiple access (TDMA), FDMA, orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and other networks. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support at least one radio access technology, which may operate on one or more frequencies or frequency ranges. For example, a CDMA network may implement Universal Terrestrial Radio Access (UTRA) (including Wideband Code Division Multiple Access (WCDMA) standards), CDMA2000 (including IS-2000, IS-95 and / or IS-856 standards), and the like. In another example, a TDMA network may implement Enhanced Data Rates for Global System for Mobile Communications (GSM) Evolution (EDGE). In another example, an OFDMA network may implement Evolved UTRA (E-UTRA) (including the LTE standard), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Etc. Reference may be made to wireless networks using the LTE standard, and thus the terms "Evolved Universal Terrestrial Radio Access," "E-UTRAN," and "eNodeB" may also be used interchangeably herein to refer to wireless networks. However, such references are provided merely as examples and are not intended to exclude wireless networks using other communication standards. For example, although various third generation (3G) systems, fourth generation (4G) systems, and fifth generation (5G) systems are discussed herein, those systems are cited merely as examples and may be replaced with future generation systems (e.g., sixth generation (6G) or higher generation systems) in various examples.

[0081] Figure 1A 1 is a system block diagram illustrating an example communication system 100 suitable for implementing any of the various aspects. The communication system 100 may be a 5G New Radio (NR) network, or any other suitable network such as a Long Term Evolution (LTE) network. Figure 1A A 5G network is illustrated, but later generations of networks may include the same or similar elements. Therefore, references to 5G networks and 5G network elements in the following description are for illustrative purposes and are not intended to be limiting.

[0082] The communication system 100 may include a heterogeneous network architecture including a plurality of UEs (in the Figure 1A120a-120e). The communication system 100 may also include a plurality of network devices 110a, 110b, 110c and 110d and other network entities, such as base stations and network nodes. A network device is an entity that communicates with a UE and, in various aspects, may be referred to as a Node B, an LTE evolved Node B (eNodeB or eNB), an access point (AP), a radio head, a transmit receive point (TRP), a new radio base station (NR BS), a 5G Node B (NB), a next generation Node B (gNodeB or gNB), etc. In various communication network implementations or architectures, the network device may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc., such as a virtualized radio access network (vRAN) or an open radio access network (O-RAN). In addition, in various communication network implementations or architectures, the network device (or network element) may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a centralized unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (RT) RAN intelligent controller (RIC), or a non-real-time RIC. Each network device may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a network device, a network device subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used. The core network 140 may be any type of core network, such as an LTE core network (e.g., an evolved packet core (EPC) network), a 5G core network, etc. The core network may include a network element acting as an application function 142 (as further described herein) and a plurality of core network elements 144, including one or more network elements providing a session management function (SMF) and one or more network elements providing a policy control function (PCF).

[0083] The network devices 110a-110d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). Network equipment for macro cells may be referred to as macro nodes or macro base stations. Network equipment for pico cells may be referred to as pico nodes or pico base stations. Network equipment for femto cells may be referred to as femto nodes, femto base stations, home nodes, or home network devices. In Figure 1A In the example illustrated in , network device 110a may be a macro node of RAN 101, network device 110b may be a pico node for pico cell 102a, and network device 110c may be a femto node for femto cell 102b. Network devices 110a-110d may support one or more (e.g., three) cells. The terms “network device,” “network node,” “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably herein.

[0084] In some examples, the cell may not be stationary, and the geographic area of ​​the cell may move depending on the location of a network device such as a network node or a mobile network device. In some examples, the network devices 110a-110d may be interconnected to each other and to one or more other network devices (e.g., a base station or a network node (not illustrated)) in the communication system 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections, virtual networks, or combinations thereof).

[0085] The network devices 110a-110d may communicate with the core network 140 over a wired or wireless communication link 126. The UEs 120a-120e may communicate with the network nodes 110a-110d over a wireless communication link 122. The wired communication link 126 may use a variety of wired networks (such as Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections) that may use one or more wired communication protocols, such as Ethernet, point-to-point protocol, high-level data link control (HDLC), advanced data communications control protocol (ADCCP), and transmission control protocol / Internet protocol (TCP / IP).

[0086] The communication system 100 may also include a relay station (such as a relay network device 110d). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a network device or UE) and send data transmissions to a downstream station (e.g., a UE or network device). A relay station may also be a UE that is capable of relaying transmissions for other UEs. Figure 1A In the example illustrated in , a relay station 110d may communicate with a macro network device 110a and a UE 120d to facilitate communication between the network device 110a and the UE 120d. A relay station may also be referred to as a relay network device, a relay base station, a relay, or the like.

[0087] The communication system 100 may be a heterogeneous network including different types of network devices (e.g., macro network devices, pico network devices, femto network devices, relay network devices, etc.). These different types of network devices may have different transmit power levels, different coverage areas, and different effects on interference in the communication system 100. For example, a macro node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network device, a femto network device, and a relay network device may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0088] The network controller 130 may be coupled to a collection of network devices and may provide coordination and control of these network devices. The network controller 130 may communicate with the network devices via a backhaul. The network devices may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0089] UEs 120a, 120b, 120c may be dispersed throughout the communication system 100, and each UE may be stationary or mobile.UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, wireless device, etc.

[0090] The macro network device 110a may communicate with the communication network 140 over a wired or wireless communication link 126. The UEs 120a, 120b, 120c may communicate over a wireless communication link 122 with the network devices 110a-110d.

[0091] The wireless communication links 122 and 124 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication links include: 3GPP LTE, 3G, 4G, 5G (such as NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Other examples of RATs that may be used in one or more of the various wireless communication links within the communication system 100 include medium-range protocols (such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire) and relatively short-range RATs (such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE)).

[0092] Certain wireless networks (e.g., LTE) use orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, binary symbols, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for a system bandwidth of 1.25 megahertz (MHz), 2.5MHz, 5MHz, 10MHz, or 20MHz, the nominal fast file transfer (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

[0093] Although the description of some specific implementations may use terms and examples associated with LTE technology, some specific implementations may be applicable to other wireless communication systems (such as new radio (NR) or 5G networks). NR can utilize OFDM with a cyclic prefix (CP) on the uplink (UL) and downlink (DL), and includes support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of 100 MHz can be supported. NR resource blocks can span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 milliseconds (ms). Each radio frame may include 50 subframes with a length of 10 ms. Therefore, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction of each subframe may be dynamically switched. Each subframe may include DL / UL data and DL / UL control data. Beamforming may be supported and the beam direction may be dynamically configured. Multiple-input multiple-output (MIMO) transmission with precoding may also be supported. MIMO configuration in DL can support up to eight transmit antennas, multi-layer DL transmission with up to eight streams and up to two streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported.

[0094] Up to eight serving cells may be used to support aggregation of multiple cells. Alternatively, NR may support a different air interface other than the OFDM-based air interface.

[0095] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a network device, another device (e.g., a remote device), or some other entity. The wireless computing platform may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband Internet of Things) devices. UE 120a-120e may be included inside a housing that houses components of UE 120a-120e, such as processor components, memory components, similar components, or combinations thereof.

[0096] Generally speaking, any number of communication systems and any number of wireless networks may be deployed in a given geographic area. Each communication system and wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between communication systems of different RATs. In some cases, 4G / LTE and / or 5G / NR RAT networks may be deployed. For example, a 5G non-standalone (NSA) network may use 4G / LTE RAT on the 4G / LTE RAN side of a 5G NSA network and simultaneously use 5G / NR RAT on the 5G / NR RAN side of a 5G NSA network. Both 4G / LTE RAN and 5G / NR RAN may be connected to each other and to a 4G / LTE core network (e.g., EPC network) in a 5G NSA network. Other example network configurations may include a 5G standalone (SA) network in which a 5G / NR RAN is connected to a 5G core network.

[0097] In some implementations, two or more UEs 120a-120e (e.g., illustrated as UE 120a and UE 120e) may communicate directly (e.g., without using network nodes 110a-110d as an intermediary to communicate with each other) using one or more side link channels 124. For example, UEs 120a-120e may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a mesh network or similar network, a vehicle networking (V2X) protocol (which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a similar protocol), or a combination thereof. In this case, UEs 120a-120e may perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by network nodes 110a-110d.

[0098] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network element, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment (such as a base station (BS) or one or more units (or components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5GNB, an access point (AP), a transmit receive point (TRP), or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0099] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (referred to as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0100] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0101] Figure 1B is a system block diagram illustrating an example decomposed base station 160 architecture suitable for implementing any of the various aspects. Figure 1A and Figure 1B , the decomposed base station 160 architecture may include one or more central units (CU) 162, which may communicate directly with the core network 180 via a backhaul link, or indirectly with the core network 180 through one or more decomposed base station units (such as a near real-time (Near-RT) RAN intelligent controller (RIC) 164 via an E2 link, or a non-real-time (Non-RT) RIC 168 associated with a service management and orchestration (SMO) framework 166, or both). The CU 162 may communicate with one or more distributed units (DU) 170 via corresponding midhaul links (such as an F1 interface). The DU 170 may communicate with one or more radio units (RU) 172 via corresponding fronthaul links. The RU 172 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 172 simultaneously.

[0102] Each of the units (i.e., CU 162, DU 170, RU 172), as well as near-RT RIC 164, non-RT RIC 168, and SMO framework 166 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0103] In some aspects, CU 162 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 162. CU162 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 162 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 162 may be implemented to communicate with DU 170 for network control and signaling.

[0104] DU 170 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 172. In some aspects, DU 170 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 170 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 170 or with control functions hosted by CU 162.

[0105] The lower layer functionality may be implemented by one or more RUs 172. In some deployments, the RUs 172 controlled by the DUs 170 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splits (such as lower layer functional splits). In such an architecture, the RUs 172 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with the RUs 172 may be controlled by the corresponding DUs 170. In some scenarios, this configuration may enable the DUs 170 and CUs 162 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0106] The SMO framework 166 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 166 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 166 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 176) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 162, DU 170, RU 172, and near-RT RIC 164. In some specific implementations, the SMO framework 166 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 174) via the O1 interface. Additionally, in some specific implementations, the SMO framework 166 may communicate directly with one or more RUs 172 via the O1 interface. The SMO framework 166 may also include a non-RT RIC 168 configured to support the functionality of the SMO framework 166 .

[0107] The non-RT RIC 168 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 164. The non-RT RIC 168 may be coupled to or in communication with the near-RT RIC 164 (such as via an A1 interface). The near-RT RIC 164 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 162, one or more DUs 170, or both, and the O-eNB with the near-RT RIC 164.

[0108] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 164, the non-RT RIC 168 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 164 and may be received from a non-network data source or from a network function at the SMO framework 166 or the non-RT RIC 168. In some examples, the non-RT RIC 168 or the near-RT RIC 164 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 168 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 166 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0109] Figure 1C is a system block diagram illustrating an example communication system 182 suitable for implementing any of the various aspects. Figures 1A to 1C , the illustrated example computing system 182 may include an application server (AS) 184, an application function (AF) 185, a core network (CN) 186, a RAN 191, and a UE 192. The CN 186 may include functional elements such as a user plane function (UPF) 187, a network open function (NEF) / policy control function (PCF) 188, a session management function (SMF) 189, and an access and mobility management function (AMF) 190.

[0110] AS 194 may execute applications that send and / or receive data flows. AS 194 may communicate with UPF 187 via an interface such as an N6 interface. AF 185 may communicate with NEF / PCF 188 via an interface such as an N5 or N33 interface.

[0111] UPF 187 may perform operations including maintaining PDU sessions, packet routing and forwarding, packet inspection, policy enforcement in the user plane, and QoS handling. UPF 187 may communicate with RAN 191 via an interface such as an N3 interface. The NEF aspect of NEF / PCF 188 may perform operations to expose services and resources within and outside CN 186. The PCF aspect of NEF / PCF 188 may support a policy control framework, apply policies, access subscription information, and perform other operations to manage network behavior. SMF 189 may perform operations for session management, IP address allocation and management for UE 192, user plane selection, QoS and policy enforcement in the control plane, and operations for service registration, discovery, and establishment. AMF 190 may perform operations for mobility management, registration management, and connection management. AMF 190 may also select SMF 189 for managing the user session context of UE 192. The AMF 190 may communicate with the RAN 191 via an interface such as an N2 interface, and communicate with the UE 192 via an interface such as an N1 interface.

[0112] RAN 191 may include one or more elements of a decomposed base station architecture, aspects of which may be Figure 1B UE 192 may include an application client (AC) that receives data streams via RAN 191 and / or sends data streams to RAN 191 via a wireless communication link (eg, 122).

[0113] Figure 2 is a component block diagram illustrating an example computing and wireless modem system 200 suitable for implementing any of the various aspects. The various aspects may be implemented on a number of single-processor and multi-processor computer systems, including system-on-chip (SOC) or system-in-package (SIP).

[0114] refer to Figure 1A to Figure 2, the illustrated example computing system 200 (which in some aspects may be a SIP) includes two SOCs 202, 204, which include one or more processors constituting a processing system, which are coupled to a memory as described, and to a clock 206, a voltage regulator 208, and a wireless transceiver 266, which is configured to transmit and receive wireless communications to / from a UE (e.g., 120a-120e) or a network device (e.g., 110a-110d) via an antenna (not shown). In some implementations, the first SOC 202 may operate as a central processing unit (CPU) of the UE, which executes instructions of a software application by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions of the software application. In some implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (such as 5 Gbps, etc.) and / or ultra-high frequency short wavelength (such as 28 GHz millimeter wave spectrum, etc.) communications.

[0115] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (such as a vector coprocessor) connected to one or more of the one or more processors, one or more memories 220, custom circuits 222, system components and resources 224, interconnects / bus modules 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234, which may be configured as a processing system. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, a plurality of millimeter wave transceivers 256, a memory 258, and various additional processors 260, such as an application processor, a packet processor, etc.

[0116] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of other processors / cores. For example, the first SOC 202 may include a processor that executes a first type of operating system (such as FreeBSD, LINUX, OS X, etc.) and a processor that executes a second type of operating system (such as MICROSOFT WINDOWS10). In addition, any or all of the one or more processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (such as a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0117] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuits for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for presentation in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components for supporting one or more processors and software clients running on the UE. The system components and resources 224 and / or custom circuits 222 may also include circuits for docking with peripheral devices (such as cameras, electronic displays, wireless communication devices, external memory chips, etc.).

[0118] The first SOC 202 and the second SOC 204 may communicate via an interconnect / bus module 250. The various processors 210, 212, 214, 216, 218 may be interconnected to one or more memory elements 220, system components and resources 224, as well as custom circuits 222 and thermal management units 232 via an interconnect / bus module 226. Similarly, one or more processors 252 may be interconnected to a power management unit 254, a millimeter wave transceiver 256, a memory 258 and various additional processors 260 via an interconnect / bus module 264. The interconnect / bus modules 226, 250, 264 may include an array of reconfigurable logic gates and / or implement a bus architecture (such as CoreConnect, AMBA, etc.). Communications may be provided by advanced interconnects, such as a high-performance network on chip (NoC).

[0119] The first SOC 202 and / or the second SOC 204 may also include an input / output module (not illustrated) for communicating with resources external to the SOC, such as a clock 206 and a voltage regulator 208. The resources external to the SOC, such as the clock 206 and the voltage regulator 208, may be shared by two or more of the internal SOC processors / cores.

[0120] In addition to the example SIP 200 discussed above, some implementations may be realized in a variety of computing systems that may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0121] Figure 3 is a component block diagram illustrating a software architecture 300 suitable for implementing any of the various aspects including a radio protocol stack for a user plane and a control plane in wireless communications. Figures 1A to 3, UE 320 may implement software architecture 300 to facilitate communication between UE 320 (e.g., UE 120a-120e, 200) and network device 350 (e.g., network device 110a-110d) of a communication system (e.g., 100). In various aspects, the layers in software architecture 300 may form a logical connection with the corresponding layers in the software of network device 350. Software architecture 300 may be distributed between one or more processors (e.g., one or more processors 212, 214, 216, 218, 252, 260). Although illustrated with respect to one radio protocol stack, in a UE with multiple subscriber identity modules (SIMs), software architecture 300 may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., in a dual SIM wireless communication device, two protocol stacks are associated with two SIMs, respectively). Although described below with reference to LTE communication layers, software architecture 300 may support any of a variety of standards and protocols for wireless communication, and / or may include additional protocol stacks that support any of a variety of standards and protocols for wireless communication.

[0122] The software architecture 300 may include a non-access stratum (NAS) 302 and an access stratum (AS) 304. The NAS 302 may include functions and protocols to support packet filtering, security management, mobility control, session management, and services and signaling between a SIM of a UE (such as SIM 204) and its core network 140. The AS 304 may include functions and protocols to support communication between a SIM (such as SIM 204) and entities of a supported access network (such as network devices, network nodes, RUs, base stations, etc.). Specifically, the AS 304 may include at least three layers (layer 1, layer 2, and layer 3), each of which may include various sublayers.

[0123] In the user plane and control plane, layer 1 (L1) of AS 304 may be a physical layer (PHY) 306, which may oversee functions for transmitting and / or receiving over an air interface via a wireless transceiver (e.g., 266). Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) attachment, decoding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include various logical channels, including a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0124] In the user plane and the control plane, Layer 2 (L2) of AS 304 may be responsible for the link between UE 320 and network node 350 on physical layer 306. In some implementations, Layer 2 may include a medium access control (MAC) sublayer 308, a radio link control (RLC) sublayer 310, a packet data convergence protocol (PDCP) 312 sublayer, and a service data adaptation protocol (SDAP) 317 sublayer, each of which forms a logical connection terminated at network node 350.

[0125] In the control plane, layer 3 (L3) of AS 304 may include a radio resource control (RRC) sublayer 3. Although not shown, the software architecture 300 may include additional layer 3 sublayers, as well as various upper layers above layer 3. In some implementations, the RRC sublayer 313 may provide functionality including broadcasting system information, paging, and establishing and releasing RRC signaling connections between the UE 320 and the network node 350.

[0126] In various aspects, the SDAP sublayer 317 may provide mapping between quality of service (QoS) flows and data radio bearers (DRBs). In some implementations, the PDCP sublayer 312 may provide uplink functions including multiplexing between different radio bearers and logical channels, sequence number addition, handover data handling, integrity protection, encryption, and header compression. In the downlink, the PDCP sublayer 312 may provide functions including in-sequence delivery of data packets, duplicate data packet detection, integrity verification, decryption, and header decompression.

[0127] In the uplink, the RLC sublayer 310 may provide segmentation and concatenation of upper layer data packets, retransmission of lost data packets, and automatic repeat request (ARQ). In the downlink, the RLC sublayer 310 functions may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets, and ARQ.

[0128] In the uplink, the MAC sublayer 308 may provide functions including multiplexing between logical and transport channels, random access procedures, logical channel priorities, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions may include channel mapping within a cell, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0129] While the software architecture 300 may provide functionality for sending data over a physical medium, the software architecture 300 may also include at least one host layer 314 to provide data delivery services to various applications in the UE 320. In some implementations, the application-specific functionality provided by the at least one host layer 314 may provide an interface between the software architecture and a general-purpose processor (e.g., 202).

[0130] In other implementations, the software architecture 300 may include one or more higher logical layers (such as transport, session, presentation, application, etc.) that provide host layer functionality. For example, in some implementations, the software architecture 300 may include a network layer (such as an Internet Protocol (IP) layer) where the logical connection terminates at a packet data network (PDN) gateway (PGW). In some implementations, the software architecture 300 may include an application layer where the logical connection terminates at another device (such as an end-user device, a server, etc.). In some implementations, the software architecture 300 may further include a hardware interface 316 between the physical layer 306 and communication hardware (such as one or more radio frequency (RF) transceivers) in the AS 304.

[0131] In various network implementations or architectures, in the network device 350, the different logical layers 308 to 317 may be implemented in a converged or monolithic base station architecture, or alternatively in a disaggregated network device architecture, and the various logical layers may be implemented in one or more of a CU, DU, RU, near-RT RAN intelligent controller (RIC), or non-real-time (non-RT) RIC. In addition, the network device 350 may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc.

[0132] Figure 4A is a block diagram illustrating an application function (AF) 400a supporting QoS management for a PDU set in accordance with various aspects. Figures 1A to 4A , AF 400a (e.g., 185) is configured to communicate with other CN elements (e.g., PCF 188), elements of the RAN (e.g., 160, 191, 350) (i.e., RAN elements), and UEs (e.g., 120a-120e, 192, 200, 320). AF 400a may be configured with a receiver 402, a communication manager 404, and a transmitter 406. Receiver 402 may receive information associated with network communications, such as packets, control information, etc. Receiver 402 may be an example of various aspects of transceiver 256 or 266, and may be configured with wired or wireless communication components. Transmitter 406 may transmit information associated with RF communications, such as packets, control information, etc. Transmitter 406 may be an example of various aspects of transceiver 256 or 266, and may be configured with wired or wireless communication components.

[0133] The communication manager 404 can be an example of various aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 404 may include an alternative service requirement component 410, a QoS parameter component 412, and a PDU set component 414, which can communicate via a communication bus 416 or another suitable communication element. The communication manager 404 can send an alternative service requirement of a protocol data unit (PDU) set supporting the data service of the application to a core network (CN) element, wherein the alternative service requirement of the PDU set includes one or more quality of service (QoS) reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value that can be adapted by the application. In some aspects, different alternative service requirements for the PDU set include different combinations of PSDB, PSER, and GFBR values ​​that can be adapted by the application. In some aspects, different combinations of PSDB, PSER, and GFBR values ​​are arranged in priority order in each of the alternative service requirements. In some aspects, the QoS reference parameters include a bit rate, a delay budget, and an error rate applicable to a set of PDUs.

[0134] The communication manager 404 may receive an indication from a CN element that a communication link between a radio access network (RAN) element and a user equipment (UE) no longer supports and is therefore no longer able to guarantee a GFBR for a QoS flow for transmitting a PDU set (i.e., a QoS flow with PDU set capability), wherein the indication includes an identification of one of the QoS reference parameters corresponding to one of a plurality of alternative QoS parameter sets. The communication manager 404 may determine a PSDB, PSER, and GFBR value for the PDU set based on the identified QoS reference parameter. The communication manager 404 may update a codec setting for a service based on the PDU set based on the determined PSDB, PSER, and GFBR values.

[0135] Figure 4B is a block diagram illustrating a CN element 400b supporting QoS management for a PDU set according to various aspects. Figures 1A to 4B , CN element 400b (e.g., PCF 188) can be configured to communicate with AF (e.g., 185) and SMF (e.g., 189) and other CN elements. CN element 400b can be configured with receiver 420, communication manager 422 and transmitter 424. Receiver 420 can receive information associated with network communication, such as packets, control information, etc. Receiver 402 can be an example of various aspects of transceiver 256 or 266, which can include wired and wireless communication components. Transmitter 424 can transmit information associated with network communication, such as packets, control information, etc. Transmitter 424 can be an example of various aspects of transceiver 256 or 266.

[0136] The communication manager 422 may be an example of aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 422 may include an alternative service requirement component 430, a PCC component 432, and a QoS parameter component 434, which may communicate via a communication bus 436 or another suitable communication element. The communication manager 422 may receive, from an application function (AF), alternative service requirements for a set of protocol data units (PDUs) supporting data services of an application, wherein each of the alternative service requirements for the set of PDUs includes one or more QoS reference parameters and a combination of a PSDB value, a PSER value, and a GFBR value that the application can adapt. The communication manager 422 may send a policy and charging control (PCC) rule to a second CN element (e.g., an SMF) based on a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters for the alternative service requirements for the set of PDUs.

[0137] The communication manager 422 may receive an indication from a second CN element that a communication link between a radio access network (RAN) element and a user equipment (UE) no longer supports and therefore no longer can guarantee a current GFBR for a QoS flow for transporting a PDU set (i.e., a PDU set capable QoS flow), wherein the indication includes a reference to one of a plurality of alternative QoS profiles (AQPs) identifying an application adaptable PSDB value, a PSER value, and a GFBR value. The communication manager 422 may send a notification to the AF that a communication link between the RAN element and the UE no longer supports and therefore no longer can guarantee a GFBR for a QoS flow for transporting a PDU set (i.e., a PDU set capable QoS flow), wherein the notification includes an identification of one of the QoS reference parameters of the alternative service requirement for the PDU set that can be supported.

[0138] Figure 4C is a block diagram illustrating a CN element 400c supporting QoS management for a PDU set according to various aspects. Figures 1A to 4C , CN element 400c (e.g., SMF 189) can be configured to communicate with NEF / PCF (e.g., 188), AMF (e.g., 190) and UPF (e.g., 187) and other CN elements. CN element 400c can be configured with a receiver 440, a communication manager 442, and a transmitter 444. Receiver 440 can receive information associated with network communications, such as packets, control information, etc. Receiver 440 can be an example of various aspects of transceiver 256 or 266, which can include wired and wireless communication components. Transmitter 444 can transmit information associated with network communications, such as packets, control information, etc. Transmitter 444 can be an example of various aspects of transceiver 256 or 266, which can include wired and wireless communication components.

[0139] The communication manager 442 may be an example of aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 442 may include a policy and charging control (PCC) rule component 450, an AQP component 452, and a QoS parameter component 454, which may communicate via a communication bus 456 or another suitable communication element. The communication manager 442 may receive from a second CN element (e.g., a PCF) a policy and charging control (PCC) rule for supporting data services for an application, the data services being based on QoS requirements for a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value. The communication manager 442 can establish a QoS flow for transporting a PDU set for supporting data services of an application (i.e., a QoS flow with PDU set capability) with a radio access network (RAN) element, including sending or otherwise providing a QoS profile for the QoS flow for transporting the PDU set and one of multiple alternative QoS profiles (AQPs) derived from multiple alternative QoS parameter sets to the RAN element.

[0140] The communication manager 442 may receive an indication from the RAN element that the communication link with the UE no longer supports and therefore is no longer able to guarantee a GFBR for a QoS flow for transporting a PDU set (i.e., a QoS flow with PDU set capability), wherein the indication includes a reference to one of the multiple AQPs that identifies a PSDB value, a PSER value, and a GFBR value that the RAN element can support and that the application can adapt. The communication manager 442 may send a notification to the second CN element that the communication link with the UE no longer supports and therefore is no longer able to guarantee a GFBR for a QoS flow for transporting a PDU set, wherein the notification includes a reference to one of the alternative QoS parameter sets associated with the AQP that the RAN element can support. In some aspects, the communication manager 442 may receive an indication from the RAN element that the communication link with the UE again supports and therefore is again able to guarantee a GFBR for a QoS flow for transporting a PDU set (i.e., a QoS flow with PDU set capability). The communication manager 442 may send a notification to the second CN element that the communication link with the UE supports or is again able to guarantee a GFBR for a QoS flow for transporting a PDU set.

[0141] Figure 4D is a block diagram illustrating a RAN element 400d that supports QoS management for a PDU set in accordance with various aspects. Figures 1A to 4D, the RAN element 400d (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350) can be configured to communicate with UEs (e.g., UEs 120a-120e, 192, 200, 320), AMFs (e.g., 190), and UPFs (e.g., 187), as well as other CN elements. The RAN element 400d can be configured with a receiver 460, a communication manager 462, and a transmitter 464. The receiver 460 can receive information associated with network communications, such as packets, control information, and the like. The receiver 460 can be an example of aspects of the transceiver 256 or 266, which can include wired and wireless communication components. The transmitter 464 can transmit information associated with network communications, such as packets, control information, and the like. The transmitter 464 can be an example of aspects of the transceiver 256 or 266, which can include wired and wireless communication components.

[0142] The communication manager 462 may be an example of aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 462 may include an AQP component 470, a QoS parameter component 472, and a PDU set component 474, which may communicate via a communication bus 476 or another suitable communication element. The communication manager 442 may receive an alternative quality of service (QoS) profile (AQP) for a protocol data unit (PDU) set from a core network (CN) element (e.g., SMF). The communication manager 442 may determine that the communication link with the user equipment (UE) no longer supports and is therefore no longer able to guarantee the QoS profile of the current quality of service (QoS) flow (i.e., a QoS flow with PDU set capability) for transmitting the PDU set. The communication manager 442 may determine that at least one of the AQPs that can be supported for the PDU set can be determined by checking whether the RAN element can support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value. The communication manager 442 can send an indication to the CN element that the communication link with the UE no longer supports and therefore can no longer guarantee the QoS profile of the current QoS flow used to transmit the PDU set, wherein the indication includes reference parameters for one AQP among multiple AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which the application can add adaptation.

[0143] In some aspects, the communication manager 442 may determine that the communication link with the UE is again supported and thus the QoS profile for the set of PDUs being communicated between the RAN element and the UE can be again guaranteed. The communication manager 442 may send an indication to the CN element that the communication link with the UE is again supported and thus the QoS profile for the set of PDUs being communicated between the RAN element and the UE can be again guaranteed.

[0144] Figure 5A is a message flow diagram illustrating operations 500a of QoS flow establishment and notification control according to various aspects. Figures 1A to 5A , operations 500a may be performed by network elements including RAN element 502 (e.g., 160, 191, 350, 400a), SMF 504 (e.g., 189 or another suitable CN element), PCF 506 (e.g., 188 or another suitable CN element), and AF 508 (e.g., 185). Operations 500a may include two general operation phases, namely, a QoS flow establishment phase and a QoS notification control phase.

[0145] In block 510, the AF 508 and the PCF 506 may perform operations to establish an AF session for the QoS flow. In some implementations, the AF 508 may provide the PCF 506 with QoS requirements for the QoS flow, which may include a combination of GFBR, PSDB, and PSER values.

[0146] In block 512, PCF 506 may perform operations to generate policy and charging control (PCC) rules applicable to the QoS profile of the QoS flow. PCF 506 may communicate the PCC rules to SMF 504.

[0147] In block 514, the PCF 506 may perform operations to provide a QoS profile that conforms to the PDU set applicable to the QoS flow to the RAN element 502. In some implementations, the PCF 506 may provide the QoS profile to the RAN element 502 during operations performed for PDU session establishment or PDU session modification.

[0148] In block 516, the SMF 504 and the RAN element 502 perform operations to establish a QoS flow that transports the PDU set (i.e., a QoS flow with PDU set capability). The UPF (e.g., 187) and the UE (e.g., 120a-120e, 192, 200, 320) may send and / or receive data via the established QoS flow.

[0149] The RAN element 502 may monitor various parameters (i.e., radio conditions) of the wireless communication link between the UE and the RAN element 502. The RAN element 502 may perform operations to detect, for example, a change in such radio conditions in block 518. Due to the change in radio conditions, the RAN element 502 may determine that a QoS parameter (such as a PSDB value, a PSER value, or a GFBR value of a QoS profile) can no longer be supported and therefore can no longer be guaranteed.

[0150] In box 520, in response to determining that the RAN element 502 can no longer support and therefore can no longer guarantee the PSDB value, PSER value or GFBR value, the RAN element 502 can trigger (generate, send, transmit) a notification control signal or message to the SMF 504 indicating an appropriate message (such as "GFBR of QoS flow can no longer be guaranteed").

[0151] In block 522, SMF 504 may send a notification to PCF 506 indicating an appropriate message, such as "GFBR of QoS flow can no longer be guaranteed."

[0152] In block 524, PCF 506 may transmit a notification message or signal to AF 508 indicating appropriate information for the QoS flow, such as "QoS goals can no longer be met."

[0153] In block 526, AF 508 may change codec settings associated with the QoS flow in response to receiving the notification message or signal from PCF 506. In some implementations, the notification message or signal from PCF 506 may not indicate which QoS parameters the RAN element 502 can no longer support and therefore can no longer guarantee.

[0154] Figure 5B is a message flow diagram illustrating operations 500b of QoS flow establishment and notification control according to various aspects. Figures 1A to 5B , operations 500b may be performed by network elements including RAN element 502 (e.g., 160, 191, 350, 400a), SMF 504 (e.g., 189 or another suitable CN element), PCF 506 (e.g., 188 or another suitable CN element), and AF 508 (e.g., 185). Operations 500b may include two general operation phases, namely, a QoS flow establishment phase and a QoS notification control phase. In some specific implementations, operations 500b may enable various network elements (e.g., RAN element 502, SMF 504, PCF 506, AF 508, and / or other suitable network elements) to perform operations for QoS flow establishment and QoS notification control that employ AQP for QoS flows with PDU set capabilities.

[0155] In block 530, the AF 508 and PCF 506 may perform operations to establish an AF session for the QoS flow. In some implementations, the AF 508 may provide the PCF 506 with various alternative QoS requirements for the QoS flow, which may include different combinations of GFBR, PSDB, and PSER values.

[0156] In block 532, PCF 506 may perform operations to generate PCC rules for a default QoS profile applicable to the QoS flow and alternative requirements for various QoS parameters (eg, PSDB, PSER). PCF 506 may communicate the PCC rules to SMF 504.

[0157] In block 534, the PCF 506 may perform operations to provide the QoS profile that complies with the default PDU set and the alternative QoS profile (e.g., having a different PSDB value, PSER value, etc.) applicable to the QoS flow to the RAN element 502. In some implementations, the PCF 506 may provide the QoS profile and the alternative QoS profile to the RAN element 502 during operations performed for PDU session establishment or PDU session modification.

[0158] In block 536, the SMF 504 and the RAN element 502 perform operations to establish a QoS flow that transports the PDU set (i.e., a QoS flow with PDU set capability) using a default QoS profile. The UPF (e.g., 187) and the UE (e.g., 120a-120e, 192, 200, 320) may send and / or receive data via the established QoS flow.

[0159] The RAN element 502 may monitor various parameters (i.e., radio conditions) of the wireless communication link between the UE and the RAN element 502. In block 538, the RAN element 502 may perform operations to detect, for example, a change in such radio conditions. Due to the change in radio conditions, the RAN element 502 may determine that a QoS parameter (such as a PSDB value, a PSER value, or a GFBR value of a QoS profile) can no longer be supported and therefore can no longer be guaranteed. For example, if the default QoS profile for a QoS flow indicates that the PSDB, PSER, and GFBR are equal to 50 ms, 10 -5 and 100 Mbps, and the RAN originally supported this combination of values ​​for the PDU set QoS parameters, the RAN may now determine that due to, for example, poor radio conditions, the RAN may now support a PSDB value of no less than 100 ms. The RAN element 502 may also check (evaluate, test) various combinations of PSDB values, PSER values, and GFBR values ​​that the RAN element 502 may support, and may run an algorithm to determine whether any of the AQPs of the PDU set for the QoS flow matches (corresponds to) the PSDB value, PSER value, and GFBR value that the RAN element 502 may support. In the case of the previous example, assume that in step 534, in addition to the default QoS profile, the CN node previously indicated that the PSDB, PSER, and GFBR are equal to 100 ms, 100 ms, and 100 Mbps, respectively. -5and 100Mbps AQP#1, PSDB, PSER and GFBR equal to 50ms, 10 -5 and AQP#2 of 50Mbps and PSDB, PSER and GFBR equal to 50ms, 10 -4 and AQP#3 for 100Mbps, then in this case, the RAN can run an algorithm to compare the currently supported combination of QoS parameter values ​​with each previously offered AQP. In this case, the RAN node will determine that AQP#1 matches the currently supported combination of PDU set QoS parameters.

[0160] In block 540, in response to determining that the RAN element 502 can no longer support and therefore can no longer guarantee the PSDB value, PSER value, or GFBR value, the RAN element 502 may trigger (generate, send, transmit) a notification control signal or message to the SMF 504 indicating an appropriate message, such as "GFBR of the QoS flow can no longer be guaranteed." The notification control signal generated by the RAN element 502 may also include a reference (indication, identification, index) to the matching (corresponding) AQP for the PDU set. In the above example, the RAN will indicate a reference to AQP #1.

[0161] In block 542, SMF 504 may send a notification to PCF 506 indicating a suitable message, such as "GFBR of QoS flow can no longer be guaranteed". The notification sent by SMF 504 may also include a reference (indication, identification, index) to an alternative service requirement in the PCC rules. In the above example, the SMF will indicate a reference to the alternative service requirement associated with AQP#1.

[0162] In block 544, PCF 506 may send a notification message or signal to AF 508 indicating appropriate information for the QoS flow, such as "QoS targets can no longer be met." The notification message sent by PCF 506 may also include a reference (indication, identification, index) to an alternative QoS parameter set. In the above example, the PCF would indicate a reference to an alternative parameter set associated with the alternative service requirement associated with AQP #1.

[0163] In block 546, AF 508 may receive a notification message or signal from PCF 506 that includes information about which PSDB, PSER, and / or GFBR may be supported by RAN element 502. Based on such information, AF 508 may change codec settings associated with the QoS flow.

[0164] Figure 5C and Figure 5DTables 500c and 500d illustrate example alternative QoS parameters and alternative QoS parameter sets configured for use with PDU sets according to various aspects based on tables in ETSI Technical Specification (TS) 123.503. The alternative QoS parameter set may define an alternative QoS parameter set for a service data flow that requires a QoS flow with PDU sets capability. In some implementations, the alternative PDU set QoS parameter set (i.e., an alternative QoS parameter set configured for use with PDU sets / QoS flows with PDU sets capability) may include PSER, PSDB, uplink guaranteed bit rate QoS parameters, and downlink guaranteed bit rate QoS parameters.

[0165] refer to Figure 5C In some examples, alternative QoS parameter sets (illustrated below) may include PDU set delay budget and PDU set error rate. Figure 5D In some examples, the alternative PDU set QoS parameter set (exemplified below) may include a PDU set delay budget, a PDU set error rate, a guaranteed uplink bit rate (UL guarantee), and a guaranteed downlink bit rate (DL guarantee). The alternative QoS parameters illustrated in Tables 500c and 500d are exemplary only, and the alternative QoS parameters may be implemented using various names, labels, values, etc. (but not limited thereto).

[0166] Figure 6 is a process flow diagram illustrating a method 600 for QoS management for a PDU set according to various specific implementations and aspects. Figures 1A to 6 , the operations of method 600 may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260) of an application function (AF) (such as AF 185, 400a, 508).

[0167] In block 602, one or more processors may send alternative service requirements for a set of protocol data units (PDUs) supporting data services for an application to a policy control function (PCF). In some aspects, the alternative service requirements for the PDU set may include one or more quality of service (QoS) reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value that the application can adapt. In some specific implementations, different alternative service requirements for the PDU set may include different combinations of PSDB, PSER, and GFBR values ​​that the application can adapt. In some specific implementations, different combinations of PSDB, PSER, and GFBR values ​​may be arranged or represented in a priority order in each of the alternative service requirements. In some specific implementations, the QoS reference parameters may include a bit rate, a delay budget, and an error rate applicable to the PDU set. The components for performing the operations of block 602 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communication manager 404.

[0168] In block 604, one or more processors may receive an indication from the PCF that a communication link between a radio access network (RAN) element and a user equipment (UE) can no longer support and therefore can no longer guarantee a GFBR for a set of PDUs being communicated between the RAN element and the UE. In some aspects, the indication may include an identification of one of the QoS reference parameters that corresponds to one of a plurality of alternative QoS parameter sets. Means for performing the operations of block 604 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 404.

[0169] In block 606, one or more processors may determine PSDB, PSER, and GFBR values ​​for the service based on the PDU set based on the identified QoS reference parameters. Means for performing the operations of block 606 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communication manager 404.

[0170] In block 608, one or more processors may update the codec settings for the application service based on the PDU set based on the determined PSDB, PSER, and GFBR values. Means for performing the operations of block 608 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communication manager 404.

[0171] Figure 7is a process flow diagram illustrating a method 700 for QoS management for a PDU set according to various specific implementations and aspects. Figures 1A to 7 , the operations of method 700 may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260) of a core network (CN) element (such as PCF 188, 400b, 506 or another suitable network element).

[0172] In block 702, one or more processors may receive, from an application function (AF), alternative service requirements for a set of protocol data units (PDUs) supporting data services for an application. In some aspects, each of the alternative service requirements for the PDU sets may include a combination of one or more QoS reference parameters and an application-adaptable PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value. Means for performing the operations of block 702 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 422.

[0173] In block 704, one or more processors may send a policy and charging control (PCC) rule to a session management function (SMF) based on a plurality of alternative QoS parameter sets derived from one or more QoS reference parameters of the alternative service requirements of the PDU set. Means for performing the operations of block 704 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 422.

[0174] In block 706, one or more processors may receive from the SMF an indication that a communication link between a radio access network (RAN) element and a user equipment (UE) no longer supports and therefore no longer can guarantee a current GFBR for a QoS flow for transmitting a PDU set (i.e., a QoS flow with PDU set capability). In some aspects, the indication may include a reference to one of a plurality of alternative QoS profiles (AQPs) that identifies a PSDB value, a PSER value, and a GFBR value to which the application can adapt. Means for performing the operations of block 706 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 422.

[0175] In block 708, one or more processors may send a notification to the AF that the communication link between the RAN element and the UE no longer supports and therefore can no longer guarantee a GFBR for a QoS flow for transmitting a PDU set (i.e., a QoS flow with PDU set capability). In some aspects, the notification may include an identification of one of the QoS reference parameters of the alternative service requirement for the PDU set that can be supported. Means for performing the operations of block 708 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, the wireless transceiver 266, and the communication manager 422.

[0176] Fig. 8A is a process flow diagram illustrating a method 800a for QoS management for a PDU set according to various specific implementations and aspects. Figures 1A to 8A , the operations of method 800a may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260) of a core network (CN) element (such as SMF 189, 400c, 504 or another suitable network element).

[0177] In block 802, one or more processors may receive from a policy control function (PCF) a policy and charging control (PCC) rule for supporting data services for an application, the data services being based on QoS requirements for a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value. Means for performing the operations of block 802 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 442.

[0178] In block 804, one or more processors may establish a QoS flow for a transmission PDU set for supporting data traffic of an application (i.e., a PDU set-capable QoS flow) with a radio access network (RAN) element for the PDU set, including sending or otherwise providing a QoS profile for the PDU set and one of a plurality of alternative QoS profiles (AQPs) derived from a plurality of alternative QoS parameter sets to the RAN element. Means for performing the operations of block 804 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 442.

[0179] In block 806, one or more processors may receive an indication from a RAN element that a communication link with a user equipment (UE) no longer supports and therefore can no longer guarantee a guaranteed flow bit rate (GFBR) for a QoS flow for transmitting a PDU set. In some aspects, the indication may include a reference to one of a plurality of AQPs that identifies a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a GFBR value that the RAN element can support and that the application can adapt. Means for performing the operations of block 806 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 442.

[0180] In block 808, the one or more processors may send a notification to the PCF that the communication link with the UE is no longer supported and therefore can no longer guarantee the GFBR for the QoS flow for the transmission of the PDU set. In some aspects, the notification may include a reference to one of the alternative QoS parameter sets associated with the AQP that the RAN element can support. Means for performing the operations of block 808 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, the wireless transceiver 266, and the communication manager 442.

[0181] Figure 8B 1 to 12 are process flow diagrams illustrating operations 800b that may be performed as part of a method 800a for QoS management of a PDU set in accordance with various implementations and aspects. Figure 8B , operation 800b may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260) of a core network (CN) element (such as SMF 189, 400c, 504 or another suitable network element).

[0182] As described, after the one or more processors send a notification to the PCF in block 808 that the communication link with the UE is no longer supported and therefore can no longer guarantee the GFBR for the PDU set, the one or more processors may receive an indication from the RAN element that the communication link with the UE is again supported and therefore can again guarantee the GFBR for the QoS flow for transmitting the PDU set in block 810. Means for performing the operations of block 810 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communication manager 442.

[0183] In block 812, the one or more processors may send a notification to the PCF that the communication link with the UE is again supported and therefore the GFBR of the QoS flow for the transmission PDU set can be again guaranteed. Means for performing the operations of block 812 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communication manager 442.

[0184] Fig.9A is a process flow diagram illustrating a method 900a for QoS management for a PDU set according to various specific implementations and aspects. Figures 1A to 9A , the operations of method 900a may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260) of a RAN element (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350, 400d, 502).

[0185] In block 902, one or more processors may receive an alternative quality of service (QoS) profile (AQP) for a set of protocol data units (PDUs) from a core network (CN) element. Means for performing the operations of block 902 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 462.

[0186] In block 904, one or more processors may determine that a communication link with a user equipment (UE) no longer supports and therefore no longer can guarantee a QoS profile for a current quality of service (QoS) flow (i.e., a QoS flow with PDU set capability) for transmitting a PDU set. Means for performing the operations of block 904 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 462.

[0187] In block 906, the one or more processors may determine that at least one of the AQPs for the PDU set may be supported by checking whether the RAN element may support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value. Means for performing the operations of block 906 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 462.

[0188] In block 908, the one or more processors may send an indication to the CN element that the communication link with the UE no longer supports and therefore can no longer guarantee a QoS profile for a QoS flow of a current QoS flow for transmitting a set of PDUs. In some aspects, the indication includes reference parameters for an AQP in a plurality of AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which an application may add adaptation. Means for performing the operations of block 906 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 462.

[0189] Fig. 9B 1 to 2 is a process flow diagram illustrating operations 900b that may be performed as part of a method 900a for QoS management for a PDU set according to various specific implementations and aspects. Fig. 9B , operation 900b may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260) of a RAN element (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350, 400d, 502).

[0190] As described, in block 908, after the one or more processors send or otherwise provide an indication to the CN element that the communication link with the UE no longer supports and therefore is no longer able to guarantee the QoS profile for the QoS flow of the current PDU set being communicated between the RAN element and the UE, the one or more processors may determine that the communication link with the UE again supports and therefore is again able to guarantee the QoS profile for the QoS flow of the transmission PDU set. Means for performing the operations of block 910 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communication manager 462.

[0191] In block 912, the one or more processors may send an indication to the CN element that the communication link with the UE is again supported and therefore the QoS profile for the QoS flow for transmitting the PDU set can be again guaranteed. Means for performing the operations of block 912 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communication manager 462.

[0192] In another additional or alternative aspect, wireless communication network operations can be implemented in one or more network elements for communicating information when there is a change in bit rate or frame rate on an application executing on a UE, establishing new QoS parameters that will support the new bit rate or frame rate for the application, and configuring communication parameters to implement the new QoS parameters to support data communication to / from the UE application at the new bit rate or frame rate. These operations enable switching to QoS parameters in the communication link to support the new bit rate or frame rate of the application without delays in renegotiating QoS requirements.

[0193] Many applications executed by network computing devices (such as application servers) have the ability to adapt the bit rate or frame rate of a data stream in response to changes in the quality of service (QoS) of the communication link that conveys the data stream (such as available bandwidth, data delay, or data loss rate). The configuration of the user equipment (UE) with which the network computing device communicates the data stream may depend on the traffic pattern of the data stream that can be communicated to / from the UE via the radio access network (RAN). For example, extended reality (XR) applications (e.g., virtual reality (VR) applications, augmented reality (AR) applications, mixed reality (MX) applications, and other similar applications) can exhibit highly variable traffic patterns that include periodic bursts of data traffic that require high bit rates or frame rates, interspersed with periods of moderate data traffic that can be handled at lower bit rates or frame rates. As used herein, the term "bit rate" refers to the amount of information that can be conveyed per unit time (which can be expressed in bits). As used herein, the term "frame rate" refers to the amount of information that can be conveyed per unit time, typically image, audio, video, or multimedia information (which can be expressed in "frames" or another suitable measurement of information).

[0194] In 5G communication systems, the QoS model is based on QoS flows. QoS flows are the finest level of granularity within 5G communication systems and are the level at which policies and charging are implemented. QoS flow protocol data units (PDUs, e.g., packets) are classified and marked using unique QoS flow identifiers to enable QoS requirements to be applied to data flows.

[0195] In order to support data services of applications that exhibit variable data transmission rates, the communication link with the UE may be configured in a manner coordinated with the traffic pattern generated by the application. For example, the periodicity of the UE's discontinuous reception (DRX) parameters, semi-persistent scheduling (SRS) parameters, and / or configuration grant (CG) parameters may be configured based on the periodicity (e.g., frame rate) of the application's data services. As another example, the UE's logical channel prioritization (LCP) parameters may be configured based on the bit rate of the application's data services.

[0196] However, this adaptation by the application (e.g., application server) and the application receiver (e.g., UE) is performed at the application layer (e.g., layer 7 of the Open Systems Interconnection (OSI) model) between the application server and the UE. Some systems do not provide a mechanism for the radio access network (RAN) to adapt the configuration of the UE to coordinate with the adaptation performed by the application server. In the event of a mismatch between the traffic pattern of a data flow and the UE configuration, the system may not be able to meet the QoS requirements of the data flow.

[0197] In various aspects, application functions (AFs), core network (CN) elements, RAN elements, and UEs may perform operations to coordinate rate adaptation in anticipation of changes to the bit rate or frame rate of a data flow.

[0198] In some aspects, the data stream may include a larger proportion of downlink traffic (e.g., from an application to a UE). In such aspects, an application (e.g., executed at an application server or another suitable network element) may send an indication to the AF that the application will change the bit rate or frame rate of the data stream. In some aspects, the indication may also include a new bit rate and / or frame rate. In some aspects, the AF may provide or forward the indication to the RAN element. In some aspects, the AF may signal the indication to the RAN element when reestablishing (renegotiating) the QoS flow with the RAN element. In some examples, the AF may forward modifications to the QoS flow from the application (executed at the application server). In some aspects, the AF may send a signal to the RAN element, which implements the bit rate change in response to the signal (e.g., substantially immediately after receiving such a signal). In some aspects, the RAN element may reconfigure the communication parameters of the UE based on the new bit rate and / or frame rate of the data stream. In some examples, the UE configuration parameters may include one or more of a discontinuous reception (DRX) parameter, a semi-persistent scheduling (SPS) parameter, a configuration grant (CG) parameter, and / or a logical channel prioritization (LCP) parameter. In some aspects, the RAN element may perform a radio resource control (RRC) reconfiguration procedure to reconfigure the communication parameters of the UE. In some aspects, the RAN element may pre-configure a set of candidate communication parameters for the UE. In such aspects, the RAN element may send a medium access control-control element (MAC CE) to the UE including an indication of which candidate communication parameters to use.

[0199] In some aspects, the data stream may include a larger proportion of uplink traffic (e.g., from the UE to the application). In such aspects, the application may send an indication to the UE that the application will change the bit rate or frame rate of the data stream. In some aspects, the indication may include the new bit rate and / or frame rate to which the application will change. In some aspects, the UE may send a reconfiguration request to the RAN element. The reconfiguration request may include the new bit rate and / or frame rate indicated by the application. In some aspects, the UE may send the reconfiguration request via an RRC message (e.g., a UE assistance information message) or via a MAC CE. The RAN element may reconfigure the communication parameters of the UE based on the new bit rate and / or frame rate of the data stream. In some examples, the RAN element may reconfigure one or more of the DRX parameters, SPS parameters, CG parameters, and / or LCP parameters of the UE. In some aspects, the RAN element may perform a radio resource control (RRC) reconfiguration procedure to reconfigure the communication parameters of the UE. In some aspects, the RAN element may send a medium access control-control element (MAC CE) to the UE to reconfigure the communication parameters of the UE.

[0200] In various aspects, after the RAN successfully reconfigures the UE communication parameters, the RAN element can send a confirmation message to the application. After receiving the confirmation message from the RAN, the application can implement (apply) the change to the bit rate and / or frame rate of the data flow (i.e., use the new bit rate and / or frame rate to send the data flow).

[0201] In some aspects, the RAN element and the UE may each perform operations to coordinate the timing of implementing (applying, using) a new bit rate and / or frame rate. In order to minimize the duration of the mismatch between the traffic pattern of the data stream and the communication parameter setting of the UE (i.e., the configuration of the UE), the RAN element and the UE may each perform operations so that the change in the traffic pattern of the data stream caused by the new bit rate and / or frame rate and the change in the configuration of the UE are implemented (applied, changed) close to or substantially simultaneously (i.e., within a very short time interval). In some aspects, the RAN element may implement the new bit rate and / or frame rate, and the UE may use the updated (reconfigured) UE communication parameters at a first time (T1) no earlier than the RAN element receiving the confirmation message of the RRC reconfiguration of the UE or the MAC CE of the UE, and no later than the second time (T2) after the RAN element receives the confirmation message of the RRC reconfiguration of the UE or the MAC CE of the UE. In such aspects, the first time T1 and the second time T2 define a time interval during which the RAN element may implement the new bit rate and / or frame rate, and the UE may implement the updated (reconfigured) UE communication parameters. In some aspects, the application may provide an indication of a target time or target time interval at which the RAN element should implement a new bit rate and / or frame rate and the UE should implement updated (reconfigured) UE communication parameters. In such aspects, the RAN element may implement the new bit rate and / or frame rate and the UE may implement updated (reconfigured) UE communication parameters before the indicated target time or during the indicated target time interval. In some aspects, the application may send the target time and / or target time interval to the AF using an indication of an absolute time (e.g., clock time), and the AF may convert the indication of the absolute time into an indication of a network time (e.g., 5G network time), such as a time slot, index, or another time indication used by the communication network.

[0202] In various aspects, an element of a RAN ("RAN element") may receive an indication of a change in a bit rate or frame rate of a data flow between an AF and a UE. The RAN element may, in response to receiving the indication, establish one or more quality of service (QoS) parameters with a core network (CN) element to support the change in the bit rate or frame rate of the data flow. The RAN element may then send a configuration message to the UE that configures one or more UE communication parameters to implement the established QoS parameters. In some aspects, receiving an indication of a change in the bit rate or frame rate of the data flow may include receiving the indication from the UE. In some aspects, receiving an indication of a change in the bit rate or frame rate of the data flow may include receiving the indication from the AF via the CN element. In some aspects, the RAN element may receive an acknowledgment of the configuration message from the UE. After a time interval after receiving the acknowledgment from the UE, the RAN element may send the data flow to the UE using one or more UE communication parameters. In some aspects, sending or otherwise providing an application data flow to the UE using one or more UE communication parameters by the RAN element after a time interval after receiving the acknowledgment from the UE may include sending / providing the application data flow to the UE using one or more UE communication parameters after a time interval after receiving the acknowledgment from the UE. In some aspects, the one or more UE communication parameters may include one or more of a DRX parameter, an SPS parameter, a CG parameter, or an LCP parameter. In some aspects, negotiating QoS parameters with a CN element may include receiving from the CN element reference parameters of one of a plurality of alternative QoS profiles (AQPs) previously negotiated with the CN element for a set of protocol data units (PDUs) supporting a data flow. Some aspects may include negotiating with the CN element a plurality of AQPs as part of establishing a data flow to the UE, wherein each of the AQPs is associated with a reference parameter and supports a particular bit rate or frame rate between the RAN element and the UE that is suitable for a communication link supporting the data flow. Some aspects may include sending / providing to the CN element a request to reestablish or update QoS parameters.

[0203] In various aspects, a CN element (e.g., one or more computing device elements of a core network) may receive an indication of a change in a bit rate or frame rate of a data stream, and may negotiate quality of service (QoS) parameters with a radio access network (RAN) element to achieve the change in the bit rate or frame rate. In some aspects, receiving an indication of a change in the bit rate or frame rate of the data stream may include receiving an indication of a change in the bit rate or frame rate of the data stream from a UE. In some aspects, receiving an indication of a change in the bit rate or frame rate of the data stream may include receiving an indication of a change in the bit rate or frame rate of the data stream from an AF. Some aspects may include sending or otherwise providing a confirmation of the indication to the AF after completing the negotiation of the QoS parameters. In some aspects, negotiating QoS parameters with a RAN element may include sending / providing to the RAN element a reference parameter of one of a plurality of alternative QoS profiles (AQPs) previously negotiated with the RAN element for a set of protocol data units (PDUs) supporting the data stream. Some aspects may include negotiating with a RAN element a plurality of AQPs as part of establishing a data flow to a UE, wherein each of the AQPs is associated with an identifier and supports a particular bit rate or frame rate for a communication link between the RAN element and the UE supporting the data flow. Some aspects may include receiving from the RAN element a request to reestablish or update QoS parameters, and adjusting a bit rate or frame rate for the data flow associated with the request to reestablish or update QoS parameters. Some aspects may include receiving from the RAN element a QoS notification control message, and renegotiating with the RAN element a QoS profile for the data flow associated with the QoS notification control message.

[0204] In various aspects, a UE may send an indication of a change in a bit rate or frame rate of a data flow of an application client (AC) executed on the UE (such as a software application that utilizes the data flow and / or transmits information of the data flow) to a RAN element. The UE may receive a configuration message from the RAN element that configures one or more UE communication parameters to support the change in the bit rate or frame rate of the data flow, and the UE may use the one or more UE communication parameters to adjust communications with the RAN element. In some aspects, sending / providing an indication of a change in the bit rate or frame rate of the data flow to the RAN element may include sending / providing an indication of a change in the bit rate or frame rate of the data flow via radio resource control (RRC) signaling or a medium access control-control element (MAC CE). In some aspects, sending / providing an indication of a change in the bit rate or frame rate of the data flow to the RAN element may include sending / providing an indication of a specified bit rate or frame rate of the data flow. Some aspects may include sending / providing an acknowledgment of receiving the configuration message to the RAN element. In such aspects, adjusting communications with the RAN element using the one or more UE communication parameters may include adjusting communications with the RAN element using the one or more UE communication parameters after a time interval after sending an acknowledgment to the RAN element. In some examples, the one or more UE communication parameters received from the RAN element may include one or more of a DRX parameter, an SPS parameter, a CG parameter, or an LCP parameter.

[0205] Various aspects improve network communications and wireless communications by enabling UE, RAN and applications to coordinate data flow rate adaptation to reduce the mismatch between UE communication parameters (configuration) and the data rate or frame rate of the data flow. Various aspects improve network communications and wireless communications by enabling RAN and UE to meet QoS requirements of data flows.

[0206] Fig. 10A is a block diagram illustrating a UE 1000a supporting wireless communication according to various aspects. Figures 1A to 10A , UE 1000a (e.g., 120a-120e, 192, 200, 320), UE 1000a may be configured to communicate with an element of a RAN (e.g., 160, 191) (i.e., a RAN element). UE 1000a may be configured with a receiver 1002, a communication manager 1004, and a transmitter 1006. Receiver 1002 may receive information associated with RF communication, such as packets, control information, etc. Receiver 1002 may be an example of various aspects of transceiver 256 or 266. Transmitter 1002 may transmit information associated with RF communication, such as packets, control information, etc. Transmitter 1002 may be an example of various aspects of transceiver 256 or 266.

[0207] The communication manager 1004 may be an example of various aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 1004 may include a bit rate / frame rate component 1010 and a communication adjustment component 1012, which may communicate via a communication bus 1014 or another suitable communication element. The communication manager 1004 may send an indication of a change in the bit rate or frame rate of a data stream for an application client (AC) executed on the UE to the RAN element. The communication manager 1004 may receive a configuration message from the RAN element that configures one or more UE communication parameters to support a change in the bit rate or frame rate of the data stream. The communication manager 1004 may use one or more UE communication parameters to adjust communications with the RAN element. The communication manager 1004 may send an indication of a change in the bit rate or frame rate of the data stream via radio resource control (RRC) signaling or a medium access control-control element (MAC CE). The communication manager 1004 may send an indication of a specified bit rate or frame rate for the data stream. The communications manager 1004 may send an acknowledgement of receipt of the configuration message to the RAN element. The communications manager 1004 may adjust communications with the RAN element using one or more UE communications parameters after a time interval after sending the acknowledgement to the RAN element.

[0208] Fig. 10B is a block diagram illustrating a RAN element 1000b supporting wireless communications according to various aspects. Figures 1A to 10B , the RAN element 1000a (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350) can be configured to communicate with the UE (e.g., 120a-120e, 192, 200, 320, 1000a) and the core network (e.g., 140, 180, 186). The RAN element 1000b can be configured with a receiver 1020, a communication manager 1022, and a transmitter 1024. The receiver 1020 can receive information associated with RF and network communications, such as packets, control information, etc. The receiver 1002 can be an example of various aspects of the transceiver 256 or 266, which can include wired and wireless communication components. The transmitter 1002 can transmit information associated with RF and network communications, such as packets, control information, etc. The transmitter 1002 can be an example of various aspects of the transceiver 256 or 266.

[0209] The communication manager 1022 may be an example of various aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 1022 may include a bit rate / frame rate component 1020 and a QoS component 1032, which may communicate via a communication bus 1034 or another suitable communication element. The communication manager 1022 may receive an indication of a change in the bit rate or frame rate of a data stream between an application function AF (e.g., 185) and a UE. The communication manager 1022 may negotiate one or more QoS parameters with a CN element in response to receiving the indication to support the change in the bit rate or frame rate of the data stream. The communication manager 1022 may send a configuration message to the UE, which configures one or more UE communication parameters to implement the negotiated QoS parameters. The communication manager 1022 may receive the indication from the UE. The communication manager 1022 may receive the indication from the AF via the CN element. The communication manager 1022 may receive an acknowledgment of the configuration message from the UE, and may send a data stream to the UE using one or more UE communication parameters after a time interval after receiving the acknowledgment from the UE. The communication manager 1022 sends the application data flow to the UE using the one or more UE communication parameters after a time interval after receiving the confirmation from the UE. The communication manager 1022 can negotiate one or more QoS parameters with the CN element, including receiving from the CN element a reference parameter of one of a plurality of alternative QoS profiles (AQPs) previously negotiated with the CN element for a set of protocol data units (PDUs) for supporting the data flow. The communication manager 1022 can negotiate with the CN element a plurality of AQPs as part of establishing a data flow to the UE, wherein each of these AQPs is associated with a reference parameter and supports a specific bit rate or frame rate between the RAN and the UE that is suitable for a communication link supporting the data flow. The communication manager 1022 can send a request to the CN element to reestablish or update the QoS parameters.

[0210] Fig. 10C is a block diagram illustrating a CN element 1000c supporting wireless communication according to various aspects. FIG. 1A to FIG. 10C, the CN element 1000c (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350) can be configured to communicate with the RAN (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350) and the application server (e.g., 184) and the AF (e.g., 185). (e.g., 140, 180, 186). The CN element 1000c can be configured with a receiver 1040, a communication manager 1042, and a transmitter 1044. The receiver 1040 can receive information associated with network communications, such as packets, control information, etc. The receiver 1040 can be an example of aspects of the transceiver 256 or 266, which can include wired and wireless communication components. The transmitter 1044 can transmit information associated with network communications, such as packets, control information, etc. Transmitter 1002 may be an example of aspects of transceiver 256 or 266, which may include wired and wireless communication components.

[0211] The communication manager 1042 may be an example of aspects of the processors 212, 214, 216, 218, 210, 252. The communication manager 1042 may include a bit rate / frame rate component 1050 and a QoS component 1052, which may communicate via a communication bus 1054 or another suitable communication element. The communication manager 1042 may receive an indication of a change in the bit rate or frame rate of a data stream, and may negotiate one or more QoS parameters with the RAN element to achieve the change in the bit rate or frame rate. The communication manager 1042 may receive an indication of a change in the bit rate or frame rate of a data stream from the UE. The communication manager 1042 may receive an indication of a change in the bit rate or frame rate of a data stream from the AF. The communication manager 1042 may send an acknowledgment of the indication to the AF after completing the negotiation of the QoS parameters. The communication manager 1042 may send a reference parameter of one of a plurality of alternative QoS profiles (AQPs) previously negotiated with the RAN for a set of protocol data units (PDUs) supporting the data stream to the RAN element. The communications manager 1042 may negotiate a plurality of AQPs with a RAN element as part of establishing a data flow to a UE, wherein each of the AQPs is associated with an identifier and supports a particular bit rate or frame rate of a communications link between the RAN and the UE supporting the data flow. The communications manager 1042 may receive a request to reestablish or update QoS parameters from the RAN element, and may adjust a bit rate or frame rate of the data flow associated with the request to reestablish or update QoS parameters. The communications manager 1042 may receive a QoS notification control message from the RAN element, and may renegotiate with the RAN a QoS profile for the data flow associated with the QoS notification control message.

[0212] Fig.11A 1 to 2 is a process flow diagram illustrating a method 1100a for coordinating rate adaptation according to various aspects. Fig.11A , the operations of method 1100a may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a UE (such as UE 120a-120e, 192, 200, 320, 1000a).

[0213] In block 1102, one or more processors may send an indication of a change in the bit rate or frame rate of a data stream for an application client (AC) executed on a UE to a radio access network (RAN) element. In some aspects, one or more processors may send an indication of a change in the bit rate or frame rate of the data stream via radio resource control (RRC) signaling or a medium access control-control element (MAC CE). In some aspects, one or more processors may send an indication of a specified bit rate or frame rate for the data stream. The components for performing the operations of block 1102 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1004.

[0214] In block 1104, one or more processors may receive a configuration message from a RAN element that configures one or more UE communication parameters to support a change in a bit rate or frame rate of a data stream. In some aspects, the UE communication parameters received from the RAN element may include one or more of a discontinuous reception (DRX) parameter, a semi-persistent scheduling (SPS) parameter, a configuration grant (CG) parameter, or a logical channel prioritization (LCP) parameter. Means for performing the operations of block 1104 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1004.

[0215] In block 1106, one or more processors may use one or more UE communication parameters to adjust communications with RAN elements. Means for performing the operations of block 1106 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1004.

[0216] Fig. 11B is a process flow diagram illustrating operations 1100b that may be performed as part of a method 1100a for coordinated rate adaptation in accordance with various aspects. Fig. 11B, operations 1100b may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a UE (such as UEs 120a-120e, 192, 200, 320, 1000a).

[0217] As described, after the one or more processors receive a configuration message from the RAN element in block 1104 that configures one or more UE communication parameters to support a change in a bit rate or frame rate of a data flow, the one or more processors may send an acknowledgment of receipt of the configuration message to the RAN element in block 1108. Means for performing the operations of block 1108 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1004.

[0218] In block 1110, the one or more processors may use the one or more UE communication parameters to adjust communications with the RAN element after a time interval after sending an acknowledgement to the RAN element. Means for performing the operations of block 1110 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1004.

[0219] Fig. 12A 1 to 2 is a process flow diagram illustrating a method 1200a for coordinating rate adaptation according to various aspects. Fig. 12A , the operations of method 1200a may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a RAN element (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350, 1000b).

[0220] In block 1202, one or more processors may receive an indication of a change in a bit rate or frame rate of a data stream between an AF and a UE. In some aspects, the one or more processors may receive an indication of a change in a bit rate or frame rate of a data stream from a UE. In some aspects, the one or more processors may receive an indication of a change in a bit rate or frame rate of a data stream from an AF within a CN. Means for performing the operations of block 1202 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1022.

[0221] In block 1204, one or more processors may negotiate one or more QoS parameters with the CN element in response to receiving the indication to support a change in the bit rate or frame rate of the data flow. In some aspects, the one or more processors may receive from the CN element a reference parameter for one of a plurality of alternative QoS profiles (AQPs) previously negotiated with the CN element for a set of protocol data units (PDUs) supporting the data flow. In some aspects, the one or more processors may negotiate with the CN element a plurality of AQPs as part of establishing a data flow to the UE. In such aspects, each of these AQPs may be associated with a reference parameter and may support a specific bit rate or frame rate between the RAN and the UE that is suitable for a communication link supporting the data flow. The components for performing the operations of block 1204 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1022.

[0222] In block 1206, the one or more processors may send a configuration message to the UE that configures one or more UE communication parameters to achieve the negotiated QoS parameters. In some aspects, the one or more UE communication parameters may include one or more of a DRX parameter, an SPS parameter, a CG parameter, or an LCP parameter. Means for performing the operations of block 1206 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1022.

[0223] Fig. 12B is a process flow diagram illustrating operations 1200b that may be performed as part of a method 1200a for coordinated rate adaptation in accordance with various aspects. Fig. 12B , operation 1200b may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a RAN element (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350, 1000b).

[0224] As described, in block 1206, after the one or more processors send a configuration message to the UE that configures one or more UE communication parameters to implement the negotiated QoS parameters, in block 1210, the one or more processors may receive an acknowledgment of the configuration message from the UE. Means for performing the operations of block 1210 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1022.

[0225] In block 1212, the one or more processors may send a data stream to the UE using the one or more UE communication parameters after a time interval after receiving an acknowledgment from the UE. Means for performing the operations of block 1210 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1022.

[0226] Fig. 12C is a process flow diagram illustrating operations 1200c that may be performed as part of a method 1200a for coordinated rate adaptation in accordance with various aspects. Fig. 12C , operation 1200c may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a RAN element (e.g., 110a-110d, 162, 170, 172, 174, 191, 200, 350, 1000b).

[0227] As described, in block 1206, after the one or more processors send a configuration message to the UE that configures one or more UE communication parameters to implement the negotiated QoS parameters, the one or more processors may send a request to the CN element to reestablish or update the QoS parameters. Means for performing the operations of block 1220 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1022.

[0228] Fig.13A 1 to 2 is a process flow diagram illustrating a method 1300a for coordinating rate adaptation according to various aspects. Fig.13A , the operations of method 1300a may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a CN element (e.g., 140, 180, 186, 187, 188, 189, 190, 200, 1000c).

[0229] In block 1302, one or more processors may receive an indication of a change in a bit rate or frame rate of a data stream. In some aspects, the one or more processors may receive an indication of a change in a bit rate or frame rate of a data stream from a UE. In some aspects, the one or more processors may receive an indication of a change in a bit rate or frame rate of a data stream from an AF. Means for performing the operations of block 1302 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1042.

[0230] In block 1304, one or more processors may negotiate one or more quality of service (QoS) parameters with a radio access network (RAN) element to implement a change in bit rate or frame rate. Means for performing the operations of block 1304 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1042.

[0231] Fig. 13B is a process flow diagram illustrating operations 1300b that may be performed as part of a method 1300a for coordinated rate adaptation in accordance with various aspects. Fig. 13B , operation 1300b may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a CN element (e.g., 140, 180, 186, 187, 188, 189, 190, 200, 1000c).

[0232] As described, in block 1304, after the one or more processors negotiate QoS parameters with the RAN element to implement the change in bit rate or frame rate, the one or more processors may send an acknowledgment of the indication to the AF after completing the negotiation of the QoS parameters. Means for performing the operations of block 1310 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1042.

[0233] Fig. 13C is a process flow diagram illustrating operations 1300c that may be performed as part of a method 1300a for coordinated rate adaptation in accordance with various aspects. Fig. 13C , operation 1300c may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a CN element (e.g., 140, 180, 186, 187, 188, 189, 190, 200, 1000c).

[0234] As described, after the one or more processors receive an indication of a change in the bit rate or frame rate of the data flow in block 1302, the one or more processors may send reference parameters of one of a plurality of alternative QoS profiles (AQPs) previously negotiated with the RAN for a set of protocol data units (PDUs) supporting the data flow to the RAN element in block 1320. Means for performing the operations of block 1320 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1042.

[0235] In block 1322, one or more processors may negotiate multiple AQPs with the RAN element as part of establishing a data flow to the UE. In some aspects, each of these AQPs is associated with an identifier and supports a specific bit rate or frame rate of the communication link between the RAN and the UE supporting the data flow. Means for performing the operations of block 1322 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, the wireless transceiver 266, and the communication manager 1042.

[0236] Fig.13D is a process flow diagram illustrating operations 1300d that may be performed as part of a method 1300a for coordinated rate adaptation in accordance with various aspects. Fig.13D , operation 1300d may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a CN element (e.g., 140, 180, 186, 187, 188, 189, 190, 200, 1000c).

[0237] As described, after the one or more processors negotiate QoS parameters with the RAN element to implement a change in bit rate or frame rate in block 1304, the one or more processors may receive a request from the RAN element to reestablish or update the QoS parameters in block 1330. Means for performing the operations of block 1330 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1042.

[0238] In block 1332, one or more processors may adjust the bit rate or frame rate of the data stream associated with the request to reestablish or update the QoS parameters. Means for performing the operations of block 1332 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1042.

[0239] Fig.13E 1 to 1300e is a process flow diagram illustrating operations 1300e that may be performed as part of a method 1300a for coordinated rate adaptation in accordance with various aspects. Fig.13E , operation 1300e may be performed by a processor (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 274a) of a CN element (e.g., 140, 180, 186, 187, 188, 189, 190, 200, 1000c).

[0240] As described, after the one or more processors negotiate QoS parameters with the RAN element to implement a change in bit rate or frame rate in block 1304, the one or more processors may receive a QoS notification control message from the RAN element in block 1340. Means for performing the operations of block 1340 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, wireless transceiver 266, and communications manager 1042.

[0241] In block 1342, one or more processors may renegotiate with the RAN a QoS profile for the data flow associated with the QoS notification control message. Means for performing the operations of block 1340 may include one or more processors 210, 212, 214, 216, 218, 252, and 260, a wireless transceiver 266, and a communications manager 1042.

[0242] Fig.14 is a block diagram of components of a UE 1400 suitable for use with the various aspects. Figures 1A to 14 , various aspects may be implemented on a variety of UEs 1400 (e.g., UEs 120a-120e, 200, 320, 400a), an example of which is shown in Fig.14 1400 is illustrated in the form of a smart phone. The UE 1400 may include a first SOC 202 (e.g., a SOC-CPU) coupled to a second SOC 204 (e.g., a SOC with 5G capabilities). The first SOC 202 and the second SOC 204 may be coupled to an internal memory 1416, a display 1412 and may be coupled to a speaker 1414. Additionally, the UE 1400 may include an antenna 1404 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless transceiver 266, which is coupled to one or more processors in the first SOC 202 and / or the second SOC 204. The UE 1400 may include a menu selection button or rocker switch 1420 for receiving user input. The UE 1400 may include a sound coding / decoding (CODEC) circuit 1410, which digitizes the sound received from the microphone into data packets suitable for wireless transmission, and decodes the received sound data packets to generate an analog signal provided to the speaker to generate sound. One or more of the processors in the first SOC 202 and the second SOC 204, the wireless transceiver 266, and the CODEC 1410 may include a digital signal processor (DSP) circuit (not separately shown).

[0243] Fig.151 is a component block diagram of a network device 1500 suitable for use with the various aspects. Such network devices (e.g., AF 185, 400a, 508, PCF 188, 400b, 506, SMF 189, 400c, 504, RAN elements 110a-110d, 162, 170, 172, 174, 191, 200, 350, 400d, 502 and other CN elements) may include at least Fig.15 Components illustrated in . Figures 1A to 15 , the network device 1500 may generally include a processor 1501 coupled to a volatile memory 1502 and a large capacity non-volatile memory (such as a disk drive 1508). The network device 1500 may also include a peripheral memory access device 1506 coupled to the one or more processors 1501, such as a floppy disk drive, a compact disc (CD), or a digital video disc (DVD) drive. The network device 1500 may also include a network access port 1504 (or interface) coupled to the one or more processors 1501 for establishing a data connection with a network (such as the Internet or a local area network coupled to other system computers and servers). The network device 1500 may include one or more antennas 1507 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless communication link. The network device 1500 may include additional access ports for coupling to peripheral devices, external memory, or other devices, such as USB, Firewire, Thunderbolt, etc.

[0244] The one or more processors of the UE 1400 and the network device 1500 may be any programmable microprocessor, microcomputer, or one or more multi-processor chips that may be configured by software instructions (applications) to perform a variety of functions including some of the specific implementations described below. In some wireless devices, multiple processors may be provided, such as one processor dedicated to wireless communication functions within the SOC 204 and one processor dedicated to running other applications within the SOC 202. Software applications may be stored in one or more memories 1416, 1502, which are then accessed and loaded into the processor. One or more processors may include internal memory sufficient to store application software instructions.

[0245] The various aspects illustrated and described are provided merely as examples of various features of the claims. However, the features illustrated and described with respect to any given aspect are not necessarily limited to the associated aspect and may be used or combined with other aspects illustrated and described. In addition, the claims are not intended to be limited to any one example aspect. For example, one or more of the methods and operations disclosed herein may replace or be combined with one or more of the methods and operations disclosed herein.

[0246] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software being executed, which are configured to perform specific operations or functions. For example, a component can be, but is not limited to, a process, a processor, an object, an executable, a thread of execution, a program, or a computer running in a processor. By way of example, both an application running on a wireless device and a wireless device can be referred to as a component. One or more components may reside within a process or a thread of execution, and a component may be localized on a processor or core or distributed between two or more processors or cores. In addition, these components may be executed from various non-transitory computer-readable media having various instructions or data structures stored thereon. Each component may communicate via local or remote processes, function or procedure calls, electronic signals, data packets, memory read / write, and other known network, computer, processor, or process-related communication methodologies.

[0247] Many different cellular and mobile communication services and standards are available or expected in the future, all of which can be implemented and benefit from various aspects. Such services and standards include, for example, the Third Generation Partnership Project (3GPP), Long Term Evolution (LTE) system, third generation wireless mobile communication technology (3G), fourth generation wireless mobile communication technology (4G), fifth generation wireless mobile communication technology (5G) and later generation 3GPP technologies, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) system (e.g., cdmaOne, CDMA1020TM), Enhanced Data Rates for GSM Evolution (EDGE), Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA), Evolution Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Network (WLAN), Wi-Fi Protected Access I and II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling and / or content messages. It should be understood that any reference to terminology and / or technical details related to individual telecommunication standards or technologies is for illustrative purposes only and is not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language.

[0248] Specific implementation examples are described in the following paragraphs. Although some of the following specific implementation examples are described according to example methods, other example implementations may include: the example methods discussed in the following paragraphs implemented by an AF, CN element, or RAN element, the AF, CN element, or RAN element including a processor configured with processor-executable instructions for performing the operations of the methods of the following specific implementation examples; the example methods discussed in the following paragraphs implemented by an AF, CN element, or RAN element, the AF, CN element, or RAN element including components for performing the functions of the methods of the following specific implementation examples; and the example methods discussed in the following paragraphs may be implemented on a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the AF, CN element, or RAN element to perform the operations of the methods of the following specific implementation examples.

[0249] Embodiment 1. A method performed at an application function (AF), comprising: sending an alternative service requirement of a protocol data unit (PDU) set supporting a data service of an application to a core network (CN) element, wherein the alternative service requirement of the PDU set includes one or more quality of service (QoS) reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value to which the application can adapt.

[0250] Embodiment 2. The method according to embodiment 1, wherein different alternative service requirements of the PDU set include different combinations of PSDB, PSER and GFBR values ​​that the application can adapt to.

[0251] Embodiment 3. The method of any one of Embodiments 1 or 2, wherein the different combinations of PSDB, PSER, and GFBR values ​​are prioritized in each of the alternative service requirements.

[0252] Embodiment 4. The method according to any one of embodiments 1 to 3, wherein the QoS reference parameters include a bit rate, a delay budget, and an error rate applicable to a PDU set.

[0253] Embodiment 5. The method according to any one of Embodiments 1 to 4 further includes: receiving an indication from the CN element that the communication link between the radio access network (RAN) element and the user equipment (UE) can no longer guarantee the GFBR of the QoS flow for transmitting the PDU set, wherein the indication includes an identification of a QoS reference parameter in the QoS reference parameters corresponding to one of multiple alternative QoS parameter sets; determining the PSDB, PSER and GFBR values ​​of the PDU set based on the identified QoS reference parameter; and updating the codec settings of the service based on the PDU set based on the determined PSDB, PSER and GFBR values.

[0254] Embodiment 6. A method performed at a first core network (CN) element, comprising: receiving from an application function (AF) alternative service requirements for a protocol data unit (PDU) set supporting a data service of an application, wherein each of the alternative service requirements for the PDU set includes one or more QoS reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value that the application can adapt to; sending a policy and charging control (PCC) rule to a second CN element based on a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters of the alternative service requirements for the PDU set; and transmitting from the second CN element a policy and charging control (PCC) rule. The AF receives an indication that a communication link between a radio access network (RAN) element and a user equipment (UE) can no longer guarantee a current GFBR of a QoS flow for transmitting a PDU set, wherein the indication comprises a reference to one of a plurality of alternative QoS profiles (AQPs) identifying a PSDB value, a PSER value and a GFBR value to which the application can adapt; and sends a notification to the AF that the communication link between the RAN element and the UE can no longer guarantee the GFBR of the QoS flow for transmitting the PDU set, wherein the notification comprises an identification of one of the QoS reference parameters of the alternative service requirement of the PDU set that can be supported.

[0255] Embodiment 7. The method according to embodiment 6, wherein the first CN entity includes a policy control function (PCF) and the second CN entity includes a session management function (SMF).

[0256] Embodiment 8. The method according to any one of Embodiments 6 or 7, wherein the first CN entity and the second CN entity are the same entity or co-located entities.

[0257] Embodiment 9. A method performed by a first core network (CN) element, comprising: receiving a policy and charging control (PCC) rule for supporting a data service of an application from a second CN element, the data service being based on a QoS requirement of a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value; establishing a QoS flow for a transport PDU set of the data service supporting the application with a radio access network (RAN) element, comprising sending a QoS profile of the QoS flow for transporting the PDU set and one of a plurality of alternative QoS profiles (AQPs) derived from the plurality of alternative QoS parameter sets to the RAN element; and sending a QoS profile of the QoS flow for transporting the PDU set to the RAN element. Receiving an indication that a communication link with a user equipment (UE) can no longer guarantee a guaranteed flow bit rate (GFBR) for the QoS flow for transmitting a PDU set, wherein the indication comprises a reference to one of the multiple AQPs identifying a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a GFBR value that the RAN element can support and that the application can adapt to; and sending a notification to the second CN element that the communication link with the UE can no longer guarantee the GFBR for the QoS flow for transmitting a PDU set, wherein the notification comprises a reference to one of the alternative QoS parameter sets associated with the AQP that the RAN element can support.

[0258] Embodiment 10. The method according to Embodiment 9 further includes: receiving an indication from the RAN element that the communication link with the UE can again guarantee the GFBR of the PDU set session for the application data service communicated between the RAN element and the UE; and sending a notification to the second CN element that the communication link with the UE can again guarantee the GFBR of the QoS flow of the transmission PDU set in the PDU session for the application data service communicated between the RAN element and the UE.

[0259] Embodiment 11. The method according to any one of embodiments 9 or 10, wherein the first CN entity includes a session management function (SMF) and the second CN entity includes a policy control function (PCF).

[0260] Embodiment 12. The method of claim 9, wherein the first CN entity and the second CN entity are the same entity or co-located entities.

[0261] Embodiment 13. A method performed at a radio access network (RAN) element, comprising: receiving an alternative quality of service (QoS) profile (AQP) for a protocol data unit (PDU) set from a core network (CN) element; determining that a communication link with a user equipment (UE) can no longer guarantee the QoS profile of a current quality of service (QoS) flow for transmitting the PDU set; determining that at least one of the AQPs for the PDU set can be supported by checking whether the RAN element can support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value; and sending an indication to the CN element that the communication link with the UE can no longer guarantee the QoS profile of the current QoS flow for transmitting the PDU set, wherein the indication includes reference parameters for one of a plurality of AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which the application can add adaptation.

[0262] Embodiment 14. The method according to Embodiment 13 further includes: determining that the communication link with the UE can again guarantee the QoS profile of the QoS flow for transmitting the PDU set, and sending an indication to the CN element that the communication link with the UE can again guarantee the QoS profile of the QoS flow for transmitting the PDU set.

[0263] Embodiment 15. A method for wireless communication performed at a user equipment (UE), comprising: sending an indication of a change in the bit rate or frame rate of a data stream for an application client (AC) executed on the UE to a radio access network (RAN) element; receiving a configuration message from the RAN element, the configuration message configuring one or more UE communication parameters to support the change in the bit rate or the frame rate of the data stream; and using the one or more UE communication parameters to adjust communication with the RAN element.

[0264] Embodiment 16. A method according to embodiment 15, wherein sending the indication of the change in the bit rate or the frame rate of the data flow to the RAN element includes: sending the indication of the change in the bit rate or the frame rate of the data flow via radio resource control (RRC) signaling or medium access control-control element (MAC CE).

[0265] Embodiment 17. A method according to any one of Embodiments 15 or 16, wherein sending the indication of the change in the bit rate or the frame rate of the data flow to the RAN element includes: sending an indication of a specified bit rate or frame rate for the data flow.

[0266] Embodiment 18. The method according to any one of Embodiments 1 to 17 further includes: sending a confirmation of receiving the configuration message to the RAN element, wherein using the one or more UE communication parameters to adjust the communication with the RAN element includes: using the one or more UE communication parameters to adjust the communication with the RAN element after a time interval after sending the confirmation of receiving the configuration message to the RAN element.

[0267] Embodiment 19. A method according to any one of embodiments 1 to 18, wherein the one or more UE communication parameters received from the RAN element include one or more of discontinuous reception (DRX) parameters, semi-persistent scheduling (SPS) parameters, configuration grant (CG) parameters, or logical channel prioritization (LCP) parameters.

[0268] Embodiment 20. A method for wireless communication performed at a radio access network (RAN) element, comprising: receiving an indication of a change in the bit rate or frame rate of a data flow between an application function (AF) and a user equipment (UE); in response to receiving the indication, establishing one or more quality of service (QoS) parameters with a core network (CN) element to support the change in the bit rate or frame rate of the data flow; and sending a configuration message to the UE, the configuration message configuring one or more UE communication parameters to implement the established QoS parameters.

[0269] Embodiment 21. The method of embodiment 22, wherein receiving an indication of the change in the bit rate or the frame rate of the data stream comprises: receiving the indication from the UE.

[0270] Embodiment 23. A method according to any one of Embodiments 22, wherein receiving an indication of the change to the bit rate or the frame rate of the data stream comprises: receiving the indication from the AF via the CN element.

[0271] Embodiment 24. The method according to any one of Embodiments 21 or 23 further includes: receiving a confirmation of the configuration message from the UE; and sending the data stream to the UE using the one or more UE communication parameters after a time interval after receiving the confirmation from the UE.

[0272] Embodiment 25. A method according to embodiment 24, wherein sending an application data stream to the UE using the one or more UE communication parameters after a time interval after receiving the confirmation from the UE includes: sending the application data stream to the UE using the one or more UE communication parameters after a time interval after receiving the confirmation from the UE.

[0273] Embodiment 26. A method according to any one of embodiments 20 to 25, wherein the one or more UE communication parameters include one or more of discontinuous reception (DRX) parameters, semi-persistent scheduling (SPS) parameters, configuration grant (CG) parameters, or logical channel prioritization (LCP) parameters.

[0274] Embodiment 27. A method according to any one of embodiments 20 to 26, wherein establishing QoS parameters with the CN element includes: receiving from the CN element reference parameters of one of a plurality of alternative QoS profiles (AQPs) previously established with the CN element for a set of protocol data units (PDUs) for supporting the data flow.

[0275] Embodiment 28. The method according to any one of embodiments 20 to 27 further includes: establishing the multiple AQPs with the CN element as part of establishing the data flow to the UE, wherein each of the AQPs is associated with a reference parameter and supports a specific bit rate or frame rate between the RAN and the UE that is suitable for supporting the communication link of the data flow.

[0276] Embodiment 29. The method according to any one of embodiments 20 to 13 further includes: sending a request to the CN element to re-establish or update the QoS parameters.

[0277] Embodiment 30. A method for supporting wireless communications performed at a core network (CN) element, comprising: receiving an indication of a change in the bit rate or frame rate of a data stream; and establishing one or more quality of service (QoS) parameters with a radio access network (RAN) element to achieve the change in the bit rate or the frame rate.

[0278] Embodiment 31. A method according to embodiment 30, wherein receiving an indication of the change in the bit rate or the frame rate of the data stream includes: receiving an indication of the change in the bit rate or the frame rate of the data stream from the UE.

[0279] Embodiment 32. A method according to any one of embodiments 30 or 31, wherein receiving an indication of the change in the bit rate or frame rate of the data stream includes: receiving an indication of the change in the bit rate or the frame rate of the data stream from an application function (AF).

[0280] Embodiment 33. The method according to any one of embodiments 30 to 32 further includes: after completing the establishment of the one or more QoS parameters, sending a confirmation of the indication to the application function (AF).

[0281] Embodiment 34. A method according to any one of embodiments 30 to 33, wherein establishing QoS parameters with the RAN element includes: sending to the RAN element reference parameters of one of a plurality of alternative QoS profiles (AQPs) previously established with the RAN for a set of protocol data units (PDUs) supporting the data flow.

[0282] Embodiment 35. The method according to any one of embodiments 30 to 34 further includes: establishing the multiple AQPs with the RAN element as part of establishing the data flow to the UE, wherein each of the AQPs is associated with an identifier and supports a specific bit rate or frame rate of the communication link between the RAN and the UE that supports the data flow.

[0283] Embodiment 36. The method according to any one of Embodiments 30 to 35 further includes: receiving a request to reestablish or update the QoS parameters from the RAN element; and adjusting the bit rate or the frame rate of the data flow associated with the request to reestablish or update the QoS parameters.

[0284] Embodiment 37. The method according to any one of embodiments 30 to 36 further includes: receiving a QoS notification control message from the RAN element; and re-establishing with the RAN a QoS profile for the data flow associated with the QoS notification control message.

[0285] Embodiment 38. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories and configured, individually or collectively, to cause the first network element to: provide an alternative service requirement for a set of protocol data units (PDUs) supporting data services of an application to a second network element, wherein the alternative service requirement for the set of PDUs comprises one or more quality of service (QoS) reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value to which the application can adapt. Additionally or alternatively, the alternative QoS profile represents a combination of QoS parameters that the application executing on the UE can accept or adapt. Additionally or alternatively, the alternative service requirement or the alternative QoS profile represents a combination of QoS parameters, the QoS parameters comprising a PDB to which the application can adapt, a PER to which the application can adapt, a GFBR to which the application can adapt, an MDBV to which the application can adapt, and / or a combination of these parameters.

[0286] Embodiment 39. An apparatus as described in Embodiment 38, wherein the one or more processors are further configured, individually or collectively, to cause the first network element to adapt one or more parameters for a service based on a PDU set based on information received from the second network element, and if the second network element cannot support a default QoS, the second network element will transmit the information. Additionally or alternatively, if the second network element cannot support the QoS parameters for the current data flow, the second network element will notify the first network element of the condition by transmitting a message including information about the condition, and the one or more processors will be configured, individually or collectively, to cause the first network element to use the information to configure or adapt the QoS parameters for the PDU set to support further communications. In some aspects, the one or more parameters may be parameters specified in one or more of the alternative service requirements or the alternative QoS profile.

[0287] Embodiment 40. The apparatus of any one of Embodiments 38 or 39, wherein different ones of the alternative service requirements for a PDU set include different combinations of PSDB, PSER, and GFBR values ​​that the application can adapt to.

[0288] Embodiment 41. The apparatus of Embodiment 38, wherein the different combinations of PSDB, PSER, and GFBR values ​​are prioritized in each of the alternative service requirements.

[0289] Embodiment 42. An apparatus according to any one of embodiments 38 to 41, wherein in order to adapt one or more parameters for a PDU set-based service based on information received in response to the second network element, the one or more processors are further configured individually or collectively to cause the first network entity to: receive an indication from the second network element that the communication link between the third network element and the user equipment (UE) is no longer able to guarantee the GFBR of the QoS flow for transmitting the PDU set, wherein the indication includes an identification of a QoS reference parameter in the QoS reference parameters corresponding to one of multiple alternative QoS parameter sets or alternative service requirements; determine the PSDB, PSER and GFBR values ​​of the PDU set based on the identified QoS reference parameter; and update the codec settings of the PDU set-based service based on the determined PSDB, PSER and GFBR values.

[0290] Embodiment 43. An apparatus according to any one of Embodiments 38 to 42, wherein: the second network element is a core network element; and the indication that the communication link between the third network element and the user equipment (UE) can no longer guarantee the GFBR of the QoS flow for transmitting the PDU set is received from the core network, as an indication that the communication link between the radio access network (RAN) and the UE no longer supports the GFBR of the QoS flow for transmitting the PDU set.

[0291] Embodiment 44. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and being individually or collectively configured to cause the first network element to: obtain a QoS profile for a quality of service (QoS) flow for a transport protocol data unit (PDU) set and one of a plurality of alternative service requirements for a PDU set supporting data services of an application, wherein each of the alternative service requirements for the PDU set comprises one or more QoS reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value to which the application can adapt; based on the alternative service requirements from the PDU set, The invention relates to a method for providing a policy and charging control (PCC) rule by using a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters of the second network element; receiving an indication that a communication link between a second network element and a user equipment (UE) can no longer guarantee a current GFBR of a QoS flow for transmitting a PDU set, wherein the indication comprises a reference to one of a plurality of alternative QoS profiles (AQPs) identifying a PSDB value, a PSER value and a GFBR value to which the application can adapt; and providing a notification that the communication link between the second element and the UE can no longer guarantee the GFBR of the QoS flow for transmitting a PDU set, wherein the notification comprises an identification of one of the QoS reference parameters of the alternative service requirement for the PDU set that can be supported.

[0292] Embodiment 45. An apparatus according to embodiment 44, wherein the one or more processors are further configured individually or collectively to enable the first network element to: determine that the communication link with the UE is capable of again guaranteeing the QoS profile of the QoS flow for transmitting the PDU set; and provide an indication that the communication link with the UE is capable of guaranteeing the QoS profile of the QoS flow for transmitting the PDU set.

[0293] Embodiment 46. An apparatus according to any one of Embodiments 44 or 45, wherein: the first network element includes a policy control function (PCF) network element; obtains the alternative service requirements of the PDU set supporting the data service of the application from an application function (AF) network element; provides the PCC rules to a session management function (SMF) network element; receives from the SMF network element the indication that the communication link between the second network element and the user equipment (UE) can no longer guarantee the current GFBR of the QoS flow for transmitting the PDU set; and provides the AF network element with the notification that the communication link between the second element and the UE can no longer guarantee the GFBR of the QoS flow for transmitting the PDU set.

[0294] Embodiment 47. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and being individually or collectively configured to cause the first network element to: obtain a policy and charging control (PCC) rule for supporting a data service of an application, the data service being based on a QoS requirement of a PDU set and a plurality of alternative QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value; establish with a second network element a QoS flow for transmitting a PDU set for supporting the data service of the application, wherein in order to establish the QoS flow, the one or more processors are individually or collectively configured to cause the first network entity to provide the second network element with a QoS of the QoS flow for transmitting the PDU set. profile and one of a plurality of alternative QoS profiles (AQPs) derived from the plurality of alternative QoS parameter sets; receiving from the second network element an indication that a communication link with a user equipment (UE) can no longer guarantee a guaranteed flow bit rate (GFBR) for the QoS flow for transmitting a PDU set, wherein the indication comprises a reference to one of the plurality of AQPs identifying a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a GFBR value that the second network element can support and that the application can adapt to; and providing a notification that the communication link with the UE can no longer guarantee the GFBR for the QoS flow for transmitting a PDU set, wherein the notification comprises a reference to one of the alternative QoS parameter sets associated with the AQP that the second network element can support.

[0295] Embodiment 48. The apparatus of Embodiment 47, wherein different ones of the alternative QoS profiles for PDU sets include different combinations of PSDB, PSER, and GFBR.

[0296] Embodiment 49. The apparatus of embodiment 47, wherein different ones of the alternative QoS profiles for PDU sets include different combinations of PSDB, PSER, GFBR, and Maximum Data Burst Size (MDBV).

[0297] Embodiment 50. An apparatus according to any one of Embodiments 47 to 49, wherein the one or more processors are further configured, individually or collectively, to enable the first network element to: receive from the second network element an indication of the GFBR of the PDU set session for application data services communicated between the second network element and the UE, which is capable of guaranteeing that the communication link with the UE is capable of guaranteeing; and provide a notification of the GFBR of the QoS flow of the transport PDU set in the PDU session for application data services communicated between the second element and the UE, which is capable of guaranteeing that the communication link with the UE is capable of guaranteeing.

[0298] Embodiment 51. An apparatus according to any one of Embodiments 47 to 50, wherein: the first network element is a session management function (SMF) network element; PCC rules for supporting the data service of the application are received from a policy control function (PCF) network element; the second network element is a radio access network element; the notification that the communication link with the UE no longer guarantees the GFBR of the QoS flow for transmitting the PDU set is sent to the PCF network element; and the notification that the communication link with the UE can again guarantee the GFBR of the QoS flow for transmitting the PDU set in the PDU session for the application data service communicated between the second element and the UE is sent to the PCF network element.

[0299] Embodiment 52. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and being individually or collectively configured to cause the first network element to: obtain an alternative quality of service (QoS) profile (AQP) for a protocol data unit (PDU) set from a second network element; determine that a communication link with a user equipment (UE) is no longer able to guarantee the QoS profile of a current quality of service (QoS) flow for transmitting the PDU set; determine that at least one of the AQPs for the PDU set can be supported by checking whether the first network element is able to support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value; and provide an indication to the second network element that the communication link with the UE is no longer able to guarantee the QoS profile of the current QoS flow for transmitting the PDU set, wherein the indication includes reference parameters for one AQP among a plurality of AQPs, the reference parameters including a PSDB value, a PSER value, and a GFBR value to which an application can add adaptation.

[0300] Embodiment 53. The apparatus of Embodiment 52, wherein different ones of the alternative QoS profiles for PDU sets include different combinations of PSDB, PSER, and GFBR.

[0301] Embodiment 54. An apparatus according to any one of embodiments 52 or 53, wherein different alternative QoS profiles in the alternative QoS profiles for the PDU set include different combinations of PSDB, PSER, GFBR and maximum data burst size (MDBV).

[0302] Embodiment 55. An apparatus according to any one of embodiments 52 to 54, wherein the one or more processors are further configured individually or collectively to enable the first network element to: determine that the communication link with the UE is capable of guaranteeing the QoS profile of the QoS flow for transmitting the PDU set; and provide an indication to the second network element that the communication link with the UE is capable of guaranteeing the QoS profile of the QoS flow for transmitting the PDU set.

[0303] Embodiment 56. An apparatus as described in any one of Embodiments 52 to 55, wherein: the first network element is a radio access network; and the second network element is a core network element.

[0304] Embodiment 57. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the memories and being individually or collectively configured to cause the first network element to: receive an indication of a change in a bit rate or frame rate of a data stream between a second network element and a user equipment (UE); in response to receiving the indication, establish one or more quality of service (QoS) parameters with a third network element to support the change in the bit rate or frame rate of the data stream; and provide a configuration message to the UE, the configuration message configuring one or more UE communication parameters to implement the established QoS parameters.

[0305] Embodiment 58. An apparatus according to embodiment 57, wherein, in order to establish QoS parameters with the third network element, the one or more processors are further configured individually or collectively to: receive from the third network element reference parameters of one of a plurality of alternative QoS profiles (AQPs) previously established with the third network element for a set of protocol data units (PDUs) supporting the data flow.

[0306] Embodiment 59. An apparatus according to embodiment 57, wherein the one or more processors are further configured, individually or collectively, to: establish the multiple AQPs with the third network element as part of establishing the data flow to the UE, wherein each of the AQPs is associated with a reference parameter and supports a specific bit rate or frame rate between the first network element and the UE that is suitable for supporting the communication link of the data flow.

[0307] Embodiment 60. The apparatus of any one of Embodiments 57 to 59, wherein the one or more processors are further configured, individually or collectively, to provide a request to the third network element to reestablish or update the QoS parameters.

[0308] Embodiment 61. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories and configured individually or collectively to enable the first network element to: obtain an indication of a change in a bit rate or a frame rate of a data stream; and establish one or more quality of service (QoS) parameters with a second network element to achieve the change in the bit rate or the frame rate.

[0309] Embodiment 62. An apparatus according to embodiment 61, wherein the one or more processors are further configured, individually or collectively, to establish QoS parameters with the second network element by providing to the second network element reference parameters of one of a plurality of alternative QoS profiles (AQPs) previously established with the second network element for a set of protocol data units (PDUs) supporting the data flow.

[0310] Embodiment 63. An apparatus according to any one of embodiments 61 or 62, wherein the one or more processors are further configured, individually or collectively, to: establish the multiple AQPs with the second network element as part of establishing the data flow to the UE, wherein each of the AQPs is associated with an identifier and supports a specific bit rate or frame rate of the communication link between the second network element and the UE that supports the data flow.

[0311] Embodiment 64. An apparatus according to any one of embodiments 61 to 63, wherein the one or more processors are further configured, individually or collectively, to cause the first network element to: receive a request to reestablish or update the QoS parameters from the second network element; and adjust the bit rate or the frame rate of the data flow associated with the request to reestablish or update the QoS parameters.

[0312] Embodiment 65. An apparatus for performing wireless communications at a user equipment (UE), comprising: a processing system, the processing system comprising a processor circuit and a memory circuit, the memory circuit storing code and coupled to the processor circuit, the processing system being configured to cause the UE to execute one or more of the methods described in embodiments 15 to 19.

[0313] In some aspects, a single processor may perform all of the functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions together. For example, a first set of (one or more) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more of the processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

[0314] The foregoing method descriptions and process flow charts are provided only as illustrative examples and are not intended to require or imply that the operations of the various aspects must be performed in the order presented. As will be appreciated by those skilled in the art, the order of operations in the foregoing various aspects may be performed in any order. Words such as "thereafter", "then", "next", etc. are not intended to limit the order of operations; these words are used to guide the reader to read the description of the method. In addition, any reference to a claim element in the singular form (e.g., a reference using the article "one", "an", or "the") should not be interpreted as limiting the element to the singular.

[0315] The various illustrative logical blocks, modules, components, circuits, and algorithmic operations described in conjunction with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Although a technician may implement the described functionality in different ways for each specific application, such specific implementation decisions should not be interpreted as departing from the scope of the claims.

[0316] Hardware for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Although a general purpose processor may be a microprocessor, in an alternative, one or more processors may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver smart objects, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuits specific to a given function.

[0317] In one or more aspects, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored as one or more instructions or codes on a non-transient computer-readable storage medium or a non-transient processor-readable storage medium. The operation of the method or algorithm disclosed herein can be implemented in a processor-executable software module or a processor-executable instruction, which can reside on a non-transient computer-readable or processor-readable storage medium. A non-transient computer-readable or processor-readable storage medium can be any storage medium accessible by a computer or a processor. By way of example and without limitation, such non-transient computer-readable or processor-readable storage media can include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage smart object, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and blue discs, wherein disks generally reproduce data magnetically, and optical discs reproduce data optically with lasers. The above combinations are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transitory processor-readable storage medium and / or computer-readable storage medium, which may be incorporated into a computer program product.

[0318] The foregoing description of the disclosed aspects is provided to enable any person skilled in the art to make or use the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the claims. Thus, the present disclosure is not intended to be limited to the aspects shown herein, but should be accorded the broadest scope consistent with the appended claims and the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the first network element to: providing to the second network element an alternative service requirement for a set of protocol data units (PDUs) supporting a data service of the application, The alternative service requirements of the PDU set include one or more quality of service (QoS) reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value and a guaranteed flow bit rate (GFBR) value to which the application can adapt.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the first network element to adapt one or more parameters for a PDU set based service based on information received from the second network element, the second network element to transmit the information if the second network element is unable to support a default QoS.

3. The apparatus of claim 1, wherein different ones of the alternative service requirements for a PDU set include different combinations of PSDB, PSER, and GFBR values ​​that the application can adapt to.

4. The apparatus of claim 1, wherein the different combinations of PSDB, PSER, and GFBR values ​​are ranked in order of priority in each of the alternative service requirements.

5. The apparatus of claim 1 , wherein to adapt one or more parameters for a PDU set based service based on information received in response from the second network element, the one or more processors are further configured to cause the first network element to: receiving, from the second network element, an indication that a communication link between a third network element and a user equipment (UE) is no longer capable of guaranteeing the GFBR for a QoS flow for transmitting a set of PDUs, wherein the indication comprises an identification of one of the QoS reference parameters corresponding to one of a plurality of alternative QoS parameter sets; determining PSDB, PSER, and GFBR values ​​for the PDU set based on the identified QoS reference parameters; as well as The codec settings for the PDU set based service are updated based on the determined PSDB, PSER and GFBR values.

6. The device according to claim 1, wherein: The second network element is a core network element; and An indication is received from the core network element that a communication link between a third network element and a user equipment (UE) is no longer able to guarantee the GFBR of the QoS flow for transmitting a set of PDUs, as an indication that the communication link between a radio access network (RAN) and the UE no longer supports the GFBR of the QoS flow for transmitting a set of PDUs.

7. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the first network element to: obtaining a QoS profile for a quality of service (QoS) flow for transporting a set of protocol data units (PDUs) and one of a plurality of alternative service requirements for the set of PDUs supporting data services of an application, wherein each of the alternative service requirements for the set of PDUs comprises one or more QoS reference parameters and a combination of a PDU set delay budget (PSDB) value, a PDU set error rate (PSER) value, and a guaranteed flow bit rate (GFBR) value to which the application can adapt; providing policy and charging control (PCC) rules based on a plurality of alternative QoS parameter sets derived from the one or more QoS reference parameters of the alternative service requirements for a set of PDUs; receiving an indication that a communication link between the second network element and a user equipment (UE) is no longer capable of guaranteeing a current GFBR for a QoS flow for transmitting a set of PDUs, wherein the indication comprises a reference to one of a plurality of alternative QoS profiles identifying a PSDB value, a PSER value, and a GFBR value to which the application can adapt; as well as Providing a notification that the communication link between the second element and the UE can no longer guarantee the GFBR of the QoS flow for transmitting a PDU set, wherein the notification includes an identification of one of the QoS reference parameters of the alternative service requirement for the PDU set that can be supported.

8. The apparatus of claim 7, wherein the one or more processors are further configured to cause the first network element to: determining that the communication link with the UE can again guarantee the QoS profile of the QoS flow for transmitting a set of PDUs; and Providing an indication of the QoS profile of the QoS flow for transmitting a set of PDUs that the communication link with the UE is capable of guaranteeing.

9. The device according to claim 7, wherein: The first network element comprises a policy control function (PCF) network element; obtaining, from an application function (AF) network element, the alternative service requirement for a set of PDUs supporting a data service of the application; providing the PCC rules to a session management function (SMF) network element; receiving, from said SMF network element, said indication that said communication link between said second network element and said UE is no longer able to guarantee said current GFBR for a QoS flow for transporting a set of PDUs; as well as The notification is provided to the AF network element that the communication link between the second element and the UE is no longer able to guarantee the GFBR for the QoS flow for transmitting a set of PDUs.

10. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the first network element to: obtaining a policy and charging control (PCC) rule for supporting a data service for an application, the data service being based on a QoS requirement for a PDU set and a plurality of selected QoS parameter sets including a PDU set delay budget (PSDB) value and a PDU set error rate (PSER) value; establishing with a second network element a QoS flow for transporting a set of PDUs for supporting data traffic of the application, wherein to establish the QoS flow, the one or more processors are configured to cause the first network element to provide the second network element with a QoS profile of the QoS flow for transporting a set of PDUs and one of a plurality of alternative QoS profiles derived from the plurality of alternative QoS parameter sets; receiving an indication from the second network element that a communication link with a user equipment (UE) is no longer capable of guaranteeing a guaranteed flow bit rate (GFBR) for the QoS flow for transmitting a set of PDUs, wherein the indication comprises a reference to one of the plurality of alternative QoS profiles identifying a PDU Set Delay Budget (PSDB) value, a PDU Set Error Rate (PSER) value, and a GFBR value that the second network element is capable of supporting and that the application is capable of adapting to; and Providing a notification that the communication link with the UE is no longer able to guarantee the GFBR for the QoS flow for transmitting a set of PDUs, wherein the notification includes a reference to one of the alternative QoS parameter sets associated with the AQP that the second network element is capable of supporting.

11. The apparatus of claim 10, wherein different ones of the plurality of alternative QoS profiles for a PDU set comprise different combinations of PSDB, PSER, and GFBR.

12. The apparatus of claim 10, wherein different ones of the plurality of alternative QoS profiles for a PDU set comprise different combinations of PSDB, PSER, GFBR, and Maximum Data Burst Volume (MDBV).

13. The apparatus of claim 10, wherein the one or more processors are further configured to cause the first network element to: receiving from the second network element an indication of the GFBR for a PDU set session for application data traffic communicated between the second network element and the UE that the communication link with the UE is capable of guaranteeing the GFBR; and Providing notification of the GFBR of the QoS flow for a set of transport PDUs in a PDU session for application data traffic communicated between the second element and the UE is capable of guaranteeing that the communication link with the UE is capable of guaranteeing the GFBR of the QoS flow.

14. The device according to claim 13, wherein: The first network element is a session management function (SMF) network element; receiving, from a policy control function (PCF) network element, PCC rules for supporting data traffic for the application; the second network element being a radio access network element; sending said notification to said PCF network element that said communication link with said UE no longer guarantees said GFBR for said QoS flow for transmitting a set of PDUs; as well as Sending the notification to the PCF network element that the communication link with the UE can again guarantee the GFBR of the QoS flow for the transport PDU set in the PDU session for application data traffic communicated between the second element and the UE.

15. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the first network element to: obtaining, from a second network element, an alternative quality of service (QoS) profile (AQP) for a set of protocol data units (PDUs); determining that a communication link with a user equipment (UE) can no longer guarantee a QoS profile of a current quality of service (QoS) flow for transmitting the set of PDUs; determining that at least one of the alternative QoS profiles for a PDU set can be supported by checking whether the first network element can support a guaranteed flow bit rate (GFBR) value, a PDU set delay budget (PSDB) value, and a PDU set error rate (PSER) value; as well as providing an indication to the second network element that the communication link with the UE is no longer able to guarantee the QoS profile of the current QoS flow for transmitting a set of PDUs, wherein the indication comprises reference parameters for an alternative QoS profile among a plurality of alternative QoS profiles, the reference parameters comprising a PSDB value, a PSER value and a GFBR value to which an application can add adaptation.

16. The apparatus of claim 15, wherein different ones of the alternative QoS profiles for a PDU set comprise different combinations of PSDB, PSER, and GFBR.

17. The apparatus of claim 15, wherein different ones of the alternative QoS profiles for a PDU set comprise different combinations of PSDB, PSER, GFBR, and Maximum Data Burst Size (MDBV).

18. The apparatus of claim 15, wherein the one or more processors are further configured to cause the first network element to: determining that the communication link with the UE can guarantee the QoS profile of the QoS flow for transmitting a set of PDUs; and An indication is provided to the second network element that the communication link with the UE is capable of guaranteeing the QoS profile for the QoS flow for transporting a set of PDUs.

19. The apparatus of claim 15, wherein: The first network element is a radio access network; and The second network element is a core network element.

20. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors coupled to the memory and configured to cause the first network element to: receiving an indication of a change in a bit rate or frame rate of a data flow between a second network element and a user equipment (UE); in response to receiving the indication, establishing one or more quality of service (QoS) parameters with a third network element to support the change in the bit rate or frame rate of the data flow; as well as A configuration message is provided to the UE, the configuration message configuring one or more UE communication parameters to achieve the established QoS parameters.

21. An apparatus according to claim 20, wherein, in order to establish QoS parameters with the third network element, the one or more processors are further configured to: receive from the third network element reference parameters of one of a plurality of alternative QoS profiles previously established with the third network element for a set of protocol data units (PDUs) supporting the data flow.

22. An apparatus according to claim 21, wherein the one or more processors are further configured to: establish the multiple alternative QoS profiles with the third network element as part of establishing the data flow to the UE, wherein each of the alternative QoS profiles is associated with a reference parameter and supports a specific bit rate or frame rate between the first network element and the UE that is suitable for supporting the communication link of the data flow.

23. The apparatus of claim 20, wherein the one or more processors are further configured to provide a request to the third network element to reestablish or update the QoS parameters.

24. An apparatus for wireless communication at a first network element, comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the first network element to: obtaining an indication of a change in a bit rate or frame rate of a data stream; as well as One or more quality of service (QoS) parameters are established with a second network element to implement said changing of said bit rate or said frame rate.

25. The apparatus of claim 24, wherein the one or more processors are further configured to establish QoS parameters with the second network element by providing to the second network element reference parameters of one of a plurality of alternative QoS profiles previously established with the second network element for a set of protocol data units (PDUs) supporting the data flow.

26. The apparatus of claim 25, wherein the one or more processors are further configured to establish the plurality of alternative QoS profiles with the second network element as part of establishing the data flow to a user equipment (UE), wherein each of the alternative QoS profiles is associated with an identifier and supports a specific bit rate or frame rate for a communication link between the second network element and the UE that supports the data flow.

27. The apparatus of claim 24, wherein the one or more processors are further configured to cause the first network element to: receiving a request from the second network element to reestablish or update the QoS parameters; and The bit rate or the frame rate of the data flow associated with the request to reestablish or update the QoS parameters is adjusted.

Images