Network-assisted dynamic control of application layer forward error correction in a wireless communication network

The network-assisted dynamic control of AL-FEC configurations addresses the inefficiencies in managed and unmanaged networks by adapting to real-time bandwidth and network conditions, optimizing bandwidth usage and ensuring robust data transmission.

WO2024240415A1PCT designated stage expired Publication Date: 2024-11-28LENOVO (SINGAPORE) PTE LTD

Patent Information

Application Number
PCT/EP2024/060155
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-02-13
Filing Date
2024-04-15
Publication Date
2024-11-28

Smart Images

  • Figure EP2024060155_28112024_PF_FP_ABST
    Figure EP2024060155_28112024_PF_FP_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to a network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network function to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow for the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; and expose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.
Need to check novelty before this filing date? Find Prior Art

Description

NETWORK-ASSISTED DYNAMIC CONTROL OF APPLICATION LAYER FORWARD ERROR CORRECTION IN A WIRELESS COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of implementing network-assisted dynamic control of application layer forward error correction in a wireless communication network. In particular, this document defines a network function for wireless communication, a processor for wireless communication, a method performed by a network function, an Application Server for wireless communication, a method performed by an Application Server, a User Equipment for wireless communication, and a method performed by a user equipment.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at leastone,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] There is provided herein a network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network function to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow for the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; and expose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0005] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for servingAL-FEC encoded data, the QoS request configuration comprising an Application Layer Forward Error Correction (AL-FEC) information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; and expose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0006] There is further provided a method performed by a network function, the method comprising: applying a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generating a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; requesting, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribing to the second network function for a set of one or more network events corresponding to the QoS flow; and exposing a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0007] There is further provided an Application Server (AS) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the AS to: determine an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL-FEC redundancy level; encode a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration; route the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribe to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapt theAL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller.

[0008] There is further provided a method performed by an Application Server (AS), the method comprising: determining an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL-FEC redundancy level; encoding a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration; routing the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribing to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapting the AL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller.

[0009] There is further still provided a User Equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: request QoS assistance from an Application Function in a wireless communication network; receive confirmation of successful QoS allocation for a QoS flow; receive a bitrate indication from a node in the wireless communication network; and perform QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0010] There is yet further still provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: request QoS assistance from an Application Function in a wireless communication network; receive confirmation of successful QoS allocation for a QoS flow; receive a bitrate indication from a node in the wireless communication network; and perform QoS re-allocation, the QoS re-allocation comprising a change in an Application- Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0011] There is also provided a method performed by a user equipment, the method comprising: requesting QoS assistance from an Application Function in a wirelesscommunication network; receiving confirmation of successful QoS allocation for a QoS flow; receiving a bitrate indication from a node in the wireless communication network; and performing QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0013] Figure 2 provides an overview of the RTP and RTCP stack.

[0014] Figure 3 illustrates an overview of the WebRTC stack.

[0015] Figures 4a and 4b illustrate a packet format and header information for a Real- Time Transport (RTP) packet and for a Secure Real-Time Transport (SRTP) packet respectively.

[0016] Figure 5 illustrates an overview of a core network extended reality media architecture handling of Protocol Data Unit (PDU) Sets.

[0017] Figure 6 illustrates a 1-byte RTP header extension for PDU Set marking by the AS.

[0018] Figure 7 illustrates a 2-byte RTP header extension for PDU Set marking by the AS.

[0019] Figures 8a to 8d illustrate 5GS PDU Set-aware QoS handling framework description of PDU Set to QoS flow to Data Radio Bearer (DRB) mappings.

[0020] Figure 9 presents the role of FECFRAME and application of various FEC coding schemes.

[0021] Figure 10 illustrates bandwidth trade-offs between media content and redundant information E2E across a heterogeneous link.

[0022] Figure 11 illustrates a workflow 1100 in accordance with elements of the embodiments herein.

[0023] Figure 12 illustrates an example of a user equipment (UE) 1200 in accordance with aspects of the present disclosure.

[0024] Figure 13 illustrates an example of a processor 1300 in accordance with aspects of the present disclosure.

[0025] Figure 14 illustrates an example of a network equipment (NE) 1400 in accordance with aspects of the present disclosure.

[0026] Figure 15 illustrates a flowchart of a method 1500 performed by a UE in accordance with aspects of the present disclosure.

[0027] Figure 16 illustrates a flowchart of a method 1600 performed by a NE in accordance with aspects of the present disclosure.

[0028] Figure 17 illustrates a flowchart of a method 1700 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0029] Application Layer Forward Error Correction (AL-FEC) is a useful tool to robustly transmit data with low-latency over a lossy network when the round-trip time (RTT) exceeds service or application requirements. For example, AL-FEC may be applied where a RTT is at least 40 ms when an application requires video delivery with a delay budget of 15 ms. However, AL-FEC efficiency decays in managed networks which can offer Quality of Service (QoS) guarantees related to meeting delay budgets and error rates. In such networks, the redundancy added by AL-FEC unnecessarily consumes available bandwidth. The bandwidth used for AL-FEC might otherwise be made available for other users, or even for the service or application protected by AL-FEC to improve the Quality of Experience (QoE) of the service. Nonetheless, end-to-end (E2E) modern networks are heterogeneous, partly unmanaged and cannot always provide service guarantees. For instance, this would be applicable to data networks (such as Content Delivery Networks (CDNs), cloud networks etc.), or alternatively last-mile local networks (such as wired and / or wireless local area networks, personal and / or body area networks, wired and / orwireless tethering links etc.). There is this a need to balance the implementation of AL- FEC in response to changes in available bandwidth in a wireless communication network.

[0030] As such, there is provided herein a mechanism for the dynamic control of a content ratio, or alternatively a redundancy ratio, associated with AL-FEC encoded content over a data flow. The control of such ratios tends to facilitate full exploitation of available bandwidth in managed network segments, yet provide sufficient redundancy to counter potential losses in unmanaged network segments. The solutions presented herein use network assistance to enable an application to dynamically apply and switch among different AL-FEC configurations and exploit the available bandwidth to the benefit of optimized QoE. The network assistance described herein provides a dynamic FEC controller of the application with information related to the available bandwidth within the network. The network is most likely a wireless communication network and the available bandwidth may relate to the core network, and / or within the Radio Access Network (RAN). The dynamic FEC controller can use received information to determine the AL-FEC adaptation policy. The received information may comprise the available bandwidth metrics, bit rate recommendations, packet feedback information (e.g., RTCP sender reports and RTCP receiver reports), network pattern loss information, and / or round-trip time / network delay statistics. The AL-FEC adaptation policy may comprise an increase or decrease of either the content ratio or the redundancy ratio, of the AL-FEC encoder. The network assistance provided exposes the available network bit rate, or alternatively bit rate recommendations, based on queries aligned with a set of AL-FEC configurations and content ratios / redundancy ratios available for the.

[0031] The application may be an application multimedia sender. The application may comprise extended reality (XR) or cloud gaming (CG).

[0032] Aspects of the present disclosure are described in the context of a wireless communications system.

[0033] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies.In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0034] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0035] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0036] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0037] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0038] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0039] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets orinterconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0040] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0041] In the wireless communications system 100, the Nes 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the Nes 102 and the UEs 104 may support different resource structures. For example, the Nes 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the Nes 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the Nes 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The Nes 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0042] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0043] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a l ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0044] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0045] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the Nes 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the Nes 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the Nes 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0046] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., g=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / z=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0047] The concept of a Protocol Data Unit Set (PDU Set) has been used to group a series of logically related PDUs. The PDU Set may comprise the content of an application data unit (ADU). The PDUs of a PDU Set can thus be treated according to a same set of QoS requirements and associated constraints such as delay budget and error rate while providing enhanced support to a radio access network (RAN) for differentiated Quality of Service (QoS) handling at PDU Set level and with application-level content awareness. This improves the granularity of legacy 5G QoS flow framework allowing RAN to optimize the mapping between QoS flows and DRBs to meet challenging extended reality (XR) / cloud gaming (CG) media requirements (e.g., high-rate transmissions with short delay budgets).

[0048] A common content delivery approach of immersive and interactive media, e.g., in CG, virtual reality (VR), is the application of over-the-top Forward Error Correction (FEC), or alternatively Application Layer Forward Error Correction (AL-FEC). This allows for robust multimedia content delivery with reduced latency enabling interactive applications with high bandwidth usage by means of avoiding higher layer retransmissions and combating network losses.

[0049] Presented herein are solutions for configuration, signaling and control associated with the dynamic adaptation of media content ratio, or alternatively AL-FEC redundancy ratio, for the benefit of overall Quality of Experience (QoE) in dynamic wireless networks multimedia communications. The dynamic control of content ratio is achieved by network assistance upon configuration by the Application Service Provider (e.g., via an Application Function (AF)) and / or by means of the Operation, Administration and Management (0AM) configuration plane for a corresponding QoS flow with PDU Set and AL-FEC support.

[0050] A plethora of application and services where multimedia flows are multiplexed under a single network application session (i.e., a 5-tuple containing a source IP address, a destination IP address, a source network port, a destination network port, and a protocol number as identifier) relates to the domain of extended Reality (XR). Such XR applications and services are defines in 3GPP Technical Report TR 26.928 vl7.0.0 (Apr 2022), titled “Extended Reality (XR) in 5G”. As an example, an XR application based on WebRTC (i.e., WebRTC 1.0: Real-Time Communication Between Browsers (w3.org)), or alternatively, on RTP (RFC 3550) / SRTP (RFC 3711) protocol stack, may contain one or more multiple video streams and audio streams multiplexed with control and feedback metadata and application metadata (e.g., such as user pose information, user input actions etc) over a single application data network session. Such arrangements were contemplated in the Applicant’s co-pending applications: US provisional application 63 / 428,026 is titled “PDU Set-Aware Multimedia Applications and Associated Signalling” by Stoica et al., Applicant’s reference SMM920220198-US-PSP; and US provisional application 63 / 478,932 titled “Multimedia Subprotocols Over Real Time Protocol” by Stoica et al., Applicant’s reference SMM920220218-US-PSP.

[0051] It should be noted that while some of the examples and discussion hereafter use “XR” as a reference use case or family of applications for the solutions proposed herein, it should be readily apparent to the reader that that the proposed solutions are more generally applicable and may be employed in various different types of transport and network protocols stacks (e.g., QUIC, WebRTC, WebTransport to name but a few).

[0052] Furthermore, XR is referred to hereafter as an umbrella term for different types of realities, of which Virtual Reality, Augmented Reality, and Mixed Reality are examples.

[0053] Virtual Reality (VR) is a rendered version of a delivered visual and audio scene. The rendering is in this case designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. Virtual reality usually, but not necessarily, requires a user to wear a head mounted display (HMD), to completely replace the user's field of view with a simulated visual component, and to wear headphones, to provide the user with the accompanying audio. Some form of head and motion tracking of the user in VR is usually also necessary to allow the simulated visual and audio components to be updated to ensure that, from the user's perspective, items and sound sources remain consistent with the user's movements. In some implementations additional means to interact with the virtual reality simulation may be provided but are not strictly necessary.

[0054] Augmented Reality (AR) is when a user is provided with additional information or artificially generated items, or content overlaid upon their current environment. Such additional information or content will usually be visual and / or audible and their observation of their current environment may be direct, with no intermediate sensing, processing, and rendering, or indirect, where their perception of their environment is relayed via sensors and may be enhanced or processed.

[0055] Mixed Reality (MR) is an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene.

[0056] XR refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes representativeforms such as AR, MR and VR and the areas interpolated among them. The levels of virtuality range from partially sensory inputs to fully immersive VR. In some circles, a key aspect of XR is considered to be the extension of human experiences especially relating to the senses of existence (represented by VR) and the acquisition of cognition (represented by AR).

[0057] The XR video traffic is mainly composed of multiple DL / UL video streams of high resolution (e.g., at least 1080p dual -eye buffer usually), frames-per-second (e.g., 60+ fps) and high bandwidth (e.g., usually at least 20-30 Mbps) which need to be transmitted across a network with minimal delay (typically upper bounded by 10-15 ms) to maintain a reduced end-to-end application round-trip interaction delay and enable digital world immersion. The latter requirements are of critical importance given the XR application dependency on cloud / edge processing (e.g., content downloading / distribution, viewport configuration, generation and updates, media encoding / transcoding, viewport rendering etc.).

[0058] To support such stringent delay-critical requirements specific to real-time communications (RTC) with high bandwidth (e.g., XR video streams) an envisioned higher-layer protocol for delivery of XR immersive multimedia applications is RTP, cf. [Ref-5] In some implementations, secured RTP variants such as vanilla SRTP or web browser based WebRTC stacks may be used to serve XR applications across mobile communications networks such as 5G System (5GS) and alike.

[0059] RTP is a media codec agnostic network protocol with application-layer framing used to deliver multimedia (e.g., audio, video etc.) in real-time over IP networks, cf. RFC 3550 - RTP: A Transport Protocol for Real-Time Applications (ietf.org). It is used in conjunction with a sister protocol for control RTCP to provide end-to-end features such as jitter compensation, packet loss and out-of-order delivery detection, synchronization and source streams multiplexing.

[0060] Figure 2 provides an overview of the RTP and RTCP stack. An IP layer 205 carries signalling from the data plane 210 and from the control plane 250. The data plane 210 stack comprises functions for a User Datagram Protocol (UDP) 212, RTP 216, RTCP 214, Media codecs 220 and quality control 222. The control plane 250 stack comprisesfunctions for UDP 252, Transmission Control Protocol (TCP) 254, Session Initiation Protocol (SIP) 262 and Session Description Protocol (SDP) 264.

[0061] SRTP is a secured version of RTP, cf. RFC 3711 - The Secure Real-time Transport Protocol (SRTP) (ietf.org), providing encryption (payload confidentiality), message authentication and integrity (header and payload signing), replay attack protection. Similarly, the SRTP sister protocol SRTCP provides the same functions to the RTCP counterpart. As such, in SRTP, the RTP header information is still accessible but non- modifiable, whereas the payload is encrypted. SRTP is used for this reason in the WebRTC stack which ensures secure RTC multimedia communications over web browser interfaces.

[0062] An overview of the WebRTC stack is provided in Figure 3. An IP layer carries signalling from the data plane and the control plane. The data plane stack comprises functions for UDP, Interactive Connectivity Establishment (ICE), Datagram Transport Layer Security (DTLS), SRTP, SRTCP, media codecs, Quality Control and Stream Control Transmission Protocol (SCTP). ICE may use the Session Traversal Utilities for NAT (STUN) protocol and Traversal Using Relays around NAT (TURN) to address real-time media content delivery across heterogeneous networks and NAT rules. Regarding real-time transport of information, the data carried over SCTP may be non-time critical, whereas SRTP, SRTCP, media codes, and Quality Control data may be time critical.

[0063] Figure 3 illustrates an overview of the WebRTC stack. As illustrated, an IP layer 305 carries signalling from the data plane 310 and the control plane 350. The data plane 310 stack comprises functions for User Datagram Protocol (UDP) 312, Interactive Connectivity Establishment (ICE) 324, Datagram Transport Layer Security (DTLS) 326, SRTP 317, SRTCP 315, media codecs 320, Quality Control 322 and SCTP 328. ICE 324 may use the Session Traversal Utilities for NAT (STUN) protocol and Traversal Using Relays around NAT (TURN) to address real-time media content delivery across heterogeneous networks and NAT rules and firewalls. The SCTP 328 data plane is mainly dedicated as an application data channel and may be non-time critical. The SRTP 317 based stack and elements of control, i.e., SRTCP 315, encoding, i.e., media codecs, and Quality of Service (QoS), i.e., Quality Control, are dedicated to time-critical transport. The control plane 350 stack comprises functions for Transmission Control Protocol (TCP) 354,Transport Layer Security (TLS) 356, Hypertext Transfer Protocol (HTTP) 358, WebSocket 366, Session Initiation Protocol (SIP) 362, Session Description Protocol (SDP) 364, Server- sent Events (SSE) 368 and Extensible Messaging and Presence Protocol (XMPP) 370.

[0064] As for both RTP and SRTP the header information is available for inspection and processing, an overview is provided below in Figure 4 together with a brief description of the individual fields. Figures 4a and 4b outlines the RTP / SRTP header information as being comprised of a fixed header information containing of first 12 bytes of the header information, and an additional header information about Contributing Source (CSRC) identifiers of the media flow and optional RTP extension headers.

[0065] Figure 4a illustrates a packet format and header information for an RTP packet 430 and Figure 4b illustrates a packet format and header information for an SRTP packet 460. The individual fixed header information and complete header information (including header extensions) is discussed for the RTP / SRTP packets further below. It can be noted that the Fixed Header Info comprises “V” 432, 462, “P” 433, 463, “X” 434, 464, “CC” 436, 466, “M” 438, 468, “PT” 440, 470, “Sequence number” 442, 472, “Timestamp” 444, 474, “Synchronization Source (SSRC) identifier” 446, 476, and “Contributing Source (CSRC) identifier” 448, 478.

[0066] “V” 432, 462 is 2 bits indicating the protocol version used.

[0067] “P” 433, 463 is a 1 bit field indicating that one or more zero-padded octets at the end of the payload are present, whereby, among others, the padding may be necessary for fixed-sized encrypted blocks or for carrying multiple RTP / SRTP packets over lower layer protocols.

[0068] “X” 434, 464 is a 1 bit indicating that the standard fixed RTP / SRTP header will be followed by an RTP header extension usually associated with a particular data / profile that will carry more information about the data (e.g., the frame marking RTP header extension for video data (as defined in IETF RFC 3711 - The Secure Real-time Transport Protocol (SRTP)), or generic RTP header extensions such as the RTP / SRTP extended protocol (as defined by w3.org in WebRTC 1.0: Real-Time Communication Between Browsers)).

[0069] CC” 436, 466 is a 4 bit field indicating number of contributing media sources (CSRC) that follow the fixed header

[0070] “M” 438, 468 is 1 bit intended to mark an information frame boundary in the packet stream, whose behaviour is exactly specified by RTP profiles (e.g., H.264, H.265, H.266, AVI etc.)

[0071] “PT” 440, 470 is 4 bits indicating the payload type, which in case of video profiles is dynamic and negotiated by means of SDP (e.g., 96 for H.264, 97 for H.265, 98 for AVI etc.)

[0072] “Sequence number” 442, 472 is 16 bits indicating the sequence number which increments by one with each RTP data packet sent over a session.

[0073] “Timestamp” 444, 474 is 32 bits indicating timestamp in ticks of the payload type clock reflecting the sampling instant of the first octet of the RTP data packet (associated for video stream with a video frame), whereas the first timestamp of the first RTP packet is selected at random.

[0074] “Synchronization Source (SSRC) identifier” 446, 476 is a 32 bit field indicating a random identifier for the source of a stream of RTP packets forming a part of the same timing and sequence number space, such that a receiver may group packets based on synchronization source for playback.

[0075] “Contributing Source (CSRC) identifier” 448, 478 is a list of up to 16 CSRC items of 32 bits each given the amount of CSRC mixed by RTP mixers within the current payload as signalled by the CC bits; the list identifies the contributing sources for the payload contained in this packet given the SSRC identifiers of the contributing sources.

[0076] The complete Header Information (incl. header extensions) comprises “RTP header extension” 448, 478.

[0077] “RTP header extension” 448, 478 is a variable length field present if the X bit is marked; the header extension is appended to the RTP fixed header information after the CSRC list if present; the RTP header extension is 32-bit aligned and formed of the following fields:• A 16-bit extension identifier defined by a profile and usually negotiated and determined via the Session Description Protocol (SDP) signalling mechanism;• A 16-bit length field describing the extension header length in 32-bits multiples excluding the first 32 bits corresponding to the 16 bits extension identifier and the 16 bits length fields itself; and• A 32-bit aligned header extension raw data field formatted according to some RTP header extension identifier specified format.

[0078] Herein a video frame may be referred to as a video coded representation of a still image presented in a sequence composing a video stream. On the other hand, a video frame may be composed of one or more video slices. A video slice is a coded video representation of a partition of a still image part of a video sequence. In some implementations video slices may be referred to as rectangular partitions (e.g., tiles) of the still image (e.g., H.266, AVI), whereby in other implementations video slices may be raster scan partitions of the still image (e.g., H.264, H.265, H.266 etc.). Similarly, we refer to a video layer as a video coding element either as a temporal video layer meant to increase the frames per second resolution and temporal level of details of a video sequence or as a spatial video layer meant to increase the number of video coded pixels and spatial resolution of individual video frames of a video sequence. The abstract concepts of video frame, video slice and / or video layers are applicable to MPEG family of modern hybrid video codecs (i.e., H.264 / H.265 / H.266), as well as other open video codecs such as AVI or VP9. The encapsulation format of video coded data to RTP / SRTP payloads is specified by Internet Standards for each individual video codec, e.g., H.264 by RFC 6184, H.265 by RFC 7798, AVI by RTP Payload Format For AVI (aomediacodec.github.io).

[0079] Note that for an XR application the media codecs used, and their configuration / configuration updates depend on the application implementation, and these are usually negotiated between a sender and a receiver upon session establishment / session update (e.g., RTP / SRTP). To this end, Session Description Protocol (SDP) signalling is used either as standalone signalling procedure or as part of the Session Initiation Protocol (SIP).

[0080] The XR Media (XRM) feature in 3 GPP Release 18 at the core network (CN) level introduced the concept of a PDU Set to handle QoS requirements of XRM applications and streams with a better granularity beyond 5G Rel-17 QoS flow possibilities. As such, according to 3GPP Technical Report TR 23.700-60 (v0.0.3), a PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services). In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing.

[0081] In addition, the PDU Set is associated with QoS requirements in terms of delay budget and error rate, which may be defined as PDU Set Delay Budget (PSDB), and / or as a PDU Set Error Rate (PSER) as defined in 3GPP Technical Report TR 23.700-60 (v0.0.3 - May 2022) titled “Study on XR (Extended Reality) and media services” and 3 GPP Technical Specification TS 23.501 (vl8.1.0 - April 2023) titled “System architecture for the 5G System (5GS)”. The PDU Set Delay Budget (PSDB) defines an upper bound for the time that a PDU-Set may be delayed between the UE and the N6 termination point at the UPF. PSDB applies to the DL PDU-Set received by the UPF over the N6 interface, and to the UL PDU-Set sent by the UE, and respectively. The PDU Set Error Rate (PSER) defines an upper bound for the rate of PDU-Sets (e.g. set of IP packets constituting a PDU-Set) that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3 GPP access). The PSER may be used to determine an upper bound for a rate of non-congestion- related packet losses.

[0082] Furthermore, per QoS flow PDU Sets may be configured with a PDU Set Integrated Handling Information (PSIHI), which indicates whether all the PDUs of the PDU Sets of the flow are needed for the usage of the PDU Set by the XR application, cf. 3GPP Technical Specification TS 23.501 (vl8.4.0 - Dec 2023) System architecture for the 5G System (5GS).

[0083] Figure 5 illustrates an overview of a core network (CN) XRM architecture handling of PDU Sets. Figure 5 shows a system 500 comprising an Extended Reality Media Application Function (XRM AF) 510, a Policy and Control Function (PCF) 515, aSession Management Function (SMF) 520, an Access and Mobility Function (AMF) 525, a Radio Access Network (RAN) 530, a User Equipment (UE) 535, a User Plane Function (UPF) 540, and an Extended Reality Application 545. The operation of system 500 will now be described in the example of downlink traffic, a similar process may operate for uplink traffic.

[0084] At 580, the XRM AF 510 determines PDU-set requirements.

[0085] At 581, the XRM AF 510 provides QoS requirements for packets of a PDU Set to the PCF 515 and information to identify the application (i.e. 5-tuple or application id). The QoS requirements may comprise PSDB and PSER. The XRM AF 510 may also include an importance parameter for a PDU Set and information for the core network to identify packets belonging to a PDU Set.

[0086] At 582, the PCF 515 derives QoS rules for the XR application and specific QoS requirements for the PDU Set and configures the SMF 520. The QoS rules may use a 5G QoS identifier (5QI) for XR media traffic. The PCF 515 sends the QoS rules to the SMF 520. The PCF 515 may include in the communication to the SMF 520 PCC rules per importance of a PDU Set. The PCC rules may be derived according to information received from the XRM AF 510 or based on an operator configuration.

[0087] At 583, the SMF 520 establishes a QoS flow according to the QoS rules by the PCF 515 and configures the UPF to route packets of the XR application to a QoS flow, and, in addition, to enable PDU Set handling. The SMF 520 also provides the QoS profile containing PDU Set QoS requirements to the RAN 530 via the AMF 525. The AMF 525 may provide the QoS profile containing PDU Set QoS requirements to the RAN 530 in an N2 SM container. Further, the AMF 525 may provide the QoS rules to the UE 535 in an N 1 SM container.

[0088] At 584, the UPF 540 inspects the packets and determines packets belonging to a PDU Set. Such a determination may be based on UPF implementation given, for instance by inspecting the RTP packet headers , as described in 3 GPP Technical Specification 23.501 V18.2.2 (Jun 2023) titled "System architecture for the 5G System (5GS)", or based on AS-marked PDU Set information transmitted over RTP PDU Set header extensions asdescribed in 3GPP TS 23.501 vl8.2.2 and 3GPP Technical Specification 26.522 vO.1.1 (Sep 2023) titled "5G Real-time Media Transport Protocol Configurations" i.e., urn:3gpp:pdu-set-marking:rel-18. The packet inspection may comprise inspecting the RTP packets. When the UPF 540 detects packets of a PDU Set the UPF 540 marks the packets belonging to a PDU Set within a GTP-U header. The GTP-U header information includes a PDU Set sequence number and the size of the PDU Set. The UPF 540 may also determine the importance of the PDU Set either based on UPF 540 implementation means, information provided by the XRM AF 510 or information provided as metadata from an XRM application server. Based on the importance of the PDU Set the UPF 540 may route the traffic to a corresponding QoS flow 1 (according to the rules received from the SMF 520) or include the importance of the PDU Set within a GTP-U header. QoS flow 1 may comprise GTP-U headers, and these may include PDU Set information.

[0089] At 585, the RAN 530 identifies packets belonging to a PDU Set (based on the GTP-U marking) and handles the packets of the PDU-set according to the QoS requirements of the PDU Set provided by the SMF 520. In one implementation the RAN 530 node may use a different radio bearer with higher QoS requirement (according to the PDU Set PSDB / PSER) to guarantee delivery of the packets of the PDU-set, while using a different radio bearer according to the 5QI of the QoS flow for the non-PDU-set packets.

[0090] The above example relates to downlink (DL) traffic. Reciprocal processing is applicable to uplink (UL) traffic wherein the role of UPF 540 packet inspection is taken by the UE 535 which is expected to inspect uplink packets, determine packets belonging to a PDU Set, and signal accordingly the PDU Set to the RAN 530 for scheduling and resource allocation corresponding to an associated DRB capable of fulfilling the PDU Set QoS requirements (i.e., PSDB and PSER). The low-level signalling mechanism associated with the UL UE-to-RAN information passing are up to the specification and implementations of RAN signalling procedures.

[0091] However, in XRM Release 18, i.e. 3GPP Technical Specification TS 23.501 vl 8.2.2 (Jun 2023) titled "System architecture for the 5G System (5GS)", once the PDU Set QoS integrated handling is enabled, the PSA UPF identifies PDUs that belong to PDU Setsand determines for each PDU Set the PDU Set information below sent over to the NG-RAN in the GTP-U header.

[0092] The PDU Set Information comprises:• PDU Set Sequence Number.• Indication of End PDU of the PDU Set.• PDU Sequence Number within a PDU Set.• PDU Set Size in bytes.• PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow.

[0093] The PDU Set information is then used by the NG-RAN for PDU Set based QoS handling as described above.

[0094] The NG-RAN may use Priority Levels as of across QoS Flows and PDU Set Importance within a QoS Flow for PDU Set level packet discarding in presence of congestion. Such Priority Levels are described in 3GPP TS 23.501 vl8.2.2 clause 5.7.3.3.

[0095] It is also specified in 3GPP TS 23.501 vl8.2.2 that the PSA UPF identifies PDUs that belong to PDU Sets and if the UPF receives a PDU that does not belong to a PDU Set based on Protocol Description for PDU Set identification (e.g., has not been marked with PDU Set information by the AS), then the UPF still maps the PDU to a PDU Set and determines the PDU Set Information as described above. This ensures that for a QoS flow with PDU Set enabled all the PDUs belong to a PDU Set. To this end, if the PSA UPF receives a PDU that does not belong to a PDU Set, it is assumed that the UPF determines the PDU Set Importance value based in some examples on pre-configuration and in other examples on an AS / AF signalled default importance.

[0096] The Protocol Description indicates the transport protocol used by the service data flow (e.g., RTP, SRTP) and additional information, such as:• RTP or SRTP;• RTP or SRTP with RTP Header Extensions, including:• RTP Header Extensions for PDU Set Marking as defined in RFC 3550 - RTP: A Transport Protocol for Real-Time Applications (ietf.org) and shown in Figure 6 or Figure 7, disucssed in detail below.• Other RTP Header Extensions based on RFC 8285 formats;• RTP or SRTP without RTP Header Extensions, but together with RTP Payload Format (e.g. H.264 or H.265);• RTP or SRTP with RTP Header Extensions for PDU Set Marking as defined in RFC 3550 “RTP: A Transport Protocol for Real-Time Applications” (ietf.org) and shown in Figure 5 or Figure 6, and together with RTP Payload Format (e.g. H.264 or H.265); and / or• RTP or SRTP with other RTP Header Extensions based on RFC 8285 formats, and together with RTP Payload Format (e.g. H.264 or H.265).

[0097] When RTP Header Extensions for PDU Set Marking (as defined in RFC 3550 - RTP: A Transport Protocol for Real-Time Applications (ietf.org) or other RTP header extensions based on RFC 8285 are included, the differentiation between different RTP Header Extension Types may be supported. In addition, when RTP Payload Format is included, the differentiation between different RTP Payload Formats may be supported.

[0098] The AS PDU Set information listed above is provided in some embodiments via a RTP Header Extension for the marking of PDU Sets, e.g., US provisional application 63 / 478,932 titled “MULTIMEDIA SUBPROTOCOLS OVER REAL TIME PROTOCOL” by Stoica et al., Applicant’s reference SMM920220218-US-PSP. In addition, the PDU Set information may further include in an End of Data Burst indication, as defined by 3 GPP Technical Specification TS 26.522 vO.1.1 (Sep 2023), titled “5G Real-time Media Transport Protocol Configurations”.

[0099] Figure 6 illustrates a 1-byte RTP header extension for PDU Set marking by the AS as per 3GPP TS 26.522 vO.1.1.

[0100] Similarly, figure 7 illustrates a 2-byte RTP header extension for PDU Set marking by the AS as per 3GPP TS 26.522 vO.1.1.

[0101] The semantics of the fields denoted in Figure 6 and Figure 7 of the RTP Header Extension for the marking of PDU Set and End of Bursts are as follows.

[0102] End PDU of the PDU Set [E] (1 bit field) 632, 732 is a flag set to 1 for the last PDU of the PDU Set and set to 0 for all other PDUs of the PDU Set.

[0103] Reserved [R] (2 bits field) 633, 733 is reserved for future use.

[0104] End of Data Burst [D] (1 bit field) 634, 734 indicates the end of a Data Burst being set to a non-zero value when the end of data burst is present and 0 otherwise.

[0105] PDU Set Importance [PSI] (4 bits field) 635, 735 indicates the importance of a PDU Set compared to other PDU Sets within the same QoS flow. Lower values indicate a higher importance PDU Set with the highest importance PDU Set of 1 and the lowest importance PDU Set of 15. A PSI value of 0 provides no information about the PDU Set importance and may be used when the importance of a PDU Set cannot be determined, or is unknown.

[0106] PDU Set Sequence Number [PSSN] (10 bits field) 636, 736 encodes the sequence number of the PDU Set to which the current PDU belongs acting as a 10-bit numerical identifier for the PDU Set and wraps around at 1023.

[0107] PDU Sequence Number within a PDU Set [PSN] (6 bits field) 637, 737 indicates the sequence number of the current PDU within the PDU Set. The PSN is set to 0 for the first PDU in the PDU Set and incremented monotonically for every PDU in the PDU Set in order of transmission from the sender. PSN wraps around 63.

[0108] PDU Set Size [PSSize] (24 bits field) 638, 738 indicates the total size of all PDUs of the PDU Set to which this PDU belongs. This field is optional and subject to an SDP signalling offer / answer negotiation, where the AS may indicate whether it will be able to provide the size of the PDU Set for that RTP stream. If not enabled, the field is not present. If enabled, but the AS is not able to determine the PDU Set Size for a particular PDU Set, it should set the value to 0 in all PDUs of that PDU Set. The PSSize indicates the size of a PDU Set including RTP / UDP / IP header encapsulation overhead of its corresponding PDUs. The PSSize is expressed in bytes.

[0109] Number of PDUs in the PDU Set [NPDS] (16 bits) 639, 739 is the number of PDUs within the PDU Set indicates the total number of PDUs belonging to the same PDU Set. This field is optional and subject to an SDP signalling offer / answer negotiation, where the Application Server may indicate whether it will be able to provide the number of PDUs within the PDU Set for that RTP stream. It is recommended to add the Number of PDUs in the PDU Set field when the PDU Set Size field is present.

[0110] The above examples relate to downlink (DL) traffic. Reciprocal processing is applicable to UL whereas the role of UPF packet inspection is taken by the user equipment (UE) which is expected to inspect packets, determine packets belonging to a PDU Set, and signal accordingly the PDU Set to the RAN for scheduling and resource allocation corresponding to an associated DRB capable of fulfilling the PDU Set QoS requirements (i.e., PSDB and PSER). The low-level signalling mechanism associated with the UL UE-to- RAN information passing are up to the specification and implementations of RAN signalling procedures and rely on buffer status reporting (BSR) and delay status reporting (DSR) procedures.

[0111] Figures 8a to 8d illustrate 5GS PDU Set-aware QoS handling framework description of PDU Set to QoS flow to DRB mappings. Depending on the QoS flow mappings and RAN procedures, several alternative PDU Set to QoS flow to DRB mappings are possible given two distinct PDU Sets with different PDU Set attributes, such as PDU Set importance. Figure 8 illustrates some options where two PDU Sets 810 of different importance and characteristics are mapped to QoS flows 820 and respectively to Data Radio Bearers (DRBs) 830. Consider in this example PDU Set 1 to be of high importance with strict QoS requirements (i.e., PSDB, PSER etc.) and PDU Set 2 to be of low importance with potentially lower QoS requirements (i.e., PSDB, PSER etc.) than PDU Set 1. As illustrated in Figure 8, the PDU Set 810 to QoS flow 820 to DRB 830 can take the following instantiations depending on QoS flow policies and Layer 2 RAN procedures.

[0112] Figure 8a illustrates 1-to-l-to-l mapping: whereby the separation of QoS flows 820 and DRBs 830 is complete between high and low importance PDU Sets 810 optimizing finely the radio and network resources on a per PDU Set basis.

[0113] Figure 8b illustrates M-to-M-to-1 mapping: whereby the separation between high and low importance PDU Sets 810 is performed only at QoS flow level, whereas the same DRB 830 is used for the over-the-air transmission of both PDU Sets 810, which may lead to overprovisioning of radio resources for low importance PDU Sets 810 yet require a lower overhead of RAN complexity and management.

[0114] Figure 8c illustrates M-to-l-to-1 mapping: whereby there is no separation between the QoS flows 820 and DRBs 830 of different importance PDU Sets 810 and the higher importance PDU Set QoS requirements are prioritized in handling the QoS management across both CN and RAN; this may lead to overprovisioning of resources for low importance PDU Sets 810 in both CN and RAN implementations but requires lower overhead and control within the 5GS QoS framework.

[0115] Figure 8d illustrates M-to-l-to-M mapping: whereby there is no separation across the QoS flows 820 between PDU Set importance levels, yet distinct DRBs 830 are used to cater for the individual requirements of the distinct importance levels; this compromises the QoS flow management complexity and uses PDU Set information to filter the PDU Sets 810 on different DRBs 830 in order to better match the QoS requirements at RAN level and optimize resource allocation according to individual PDU Set needs.

[0116] In various interactive XR applications application-level forward error correction (AL-FEC) might be used as a method to combat congestion and packet loss. This use exploits multicast, broadcast topologies as well as unicast path diversity either at the network routing level or at the physical layer (e.g., in 5GS this would be applicable to dual connectivity (DC), carrier aggregation (CA) as well as multi-TRP transmissions). This applies for instance to 1D / 2D parity check codes (e.g. RFC 8627), Raptor codes (e.g., RFC 5032), RaptorQ codes (e.g., RFC 6330), and LDPC staircase codes (e.g., RFC 6816).

[0117] A generic forward error correction framework (FECFRAME) has been defined by IETF as RFC 6363 which allows for various FEC Schemes to be applied for AL-FEC. FECFRAME specifies source packet and repair packet formats and FEC Scheme configuration procedures for AL-FEC both over transport layer (e.g., UDP), as well as over RTP layer or alike (e.g., WebRTC).

[0118] Figure 9 presents the role of FECFRAME and application of various FEC coding schemes, and shows the encoding and packetization procedures associated with the FECFRAME framework. Figure 9 provides an illustration of an AL-FEC XR application flow 900 including encoding, packetization and transport. The AL-FEC XR application flow 900 is performed at a sender by an application 910, a FECFRAME block 920, a transport layer 930, and a FEC Scheme 940. The transport layer 930 may use the User Datagram Protocol (UDP).

[0119] In some embodiments, a popular AL-FEC coding scheme given its efficient encoding / decoding is Raptor coding (RFC 5032), or alternatively, in other embodiments, its optimized version RaptorQ coding (RFC 6330). Applied in the context of FECFRAME Raptor / RaptorQ encodes RTP packets as per RFC 6881 and RFC 6882. The FEC Scheme 940 may comprise Raptor, or RaptorQ. The AL-FEC XR application flow 900 comprises the following steps.

[0120] At 971, an application 910 generates a set of ADUs. The ADUs comprise media content. The media content may comprise video, audio, haptic, text or general application data. The media content is served by the application towards a remote endpoint. The remote endpoint may be a receiver. The ADUs may be packetized according to a content delivery protocol. The content delivery protocol may be RTP, or alternatively SRTP, and each ADU may comprise one or more RTP packets.

[0121] At 972, a the ADUs are processed by a 920 FECFRAME sender which determines a set of source packets (e.g., RTP source packets) representing an ADU as a source block, to be protected jointly based on an AL-FEC coding configuration (e.g., the FECFRAME Configuration Information containing• a FEC Scheme identifier,• a maximum source block length (MSBL) or alternatively K max for Raptor / RaptorQ,• an encoding symbol size (i.e., a T parameter for Raptor / RaptorQ coding schemes),• a repair-window duration (i.e., a maximum time in milliseconds and / or microseconds that spans the transmission of the source packets and thecorresponding repair packets, whereby the transmission point is considered to be downstream interface ingesting encoded PDUs post-encoding)).

[0122] At 972, the sender further arranges the source packets (e.g., the RTP source packets) to construct a set of same-sized source symbols. The construction of source symbols may comprise partitioning of source data packets into source symbols of a configured size. Each source symbol may have the same configured size. The set of source symbols forms the source block for AL-FEC encoding.

[0123] At 973, the FECFRAME sender 920 inputs the constructed source block to the FEC encoder encoding with the FEC Scheme 940.

[0124] At 974, the sender applies FEC encoding scheme (e.g., Raptor / RaptorQ, Reed- Solomon codes, 2D parity codes etc.) according to the AL-FEC configuration (e.g., FECFRAME Configuration Information) to generate and construct the required number of repair symbols.

[0125] At 975, the repair symbols generated by the FEC Scheme 940 are input to the FECFRAME sender 920 for packetization. The repair symbols are complemented by metadata related to the AL-FEC configuration, representing information elements of the FEC Scheme applied at encoding. The metadata may be FECFRAME specific and may contain source FEC Payload IDs, repair FEC Payload IDs, or alternatively an Encoding Symbol ID (ESI). The metadata may further contain the size of the symbol block, or alternatively the number of source symbols and a common transport object identifier for the source and repair symbols.

[0126] At 976, the sender performs packetization of the repair symbols into repair packets (e.g., RTP repair packets according to RFC 6882) and sends the repair packets and the source packets for transmission over a packet network to a receiver. The source symbols may be repacketized in some implementations into source packets including new metadata related to the AL-FEC configuration. Other implementations may reuse the original source packets and only provide the metadata related to the AL-FEC configuration for the repair packets to aid a receiver to decode the AL-FEC encoded content. As an example, the original RTP packets as the source packets may be transmitted with thecorresponding RTP repair packets produced by the AL-FEC encoding. The RTP repair packets may reference the RTP source packets by means of the metadata related to the AL- FEC configuration (e.g., FEC Payload ID, ESI, common transport object identifier, etc.).

[0127] At 977, the FECFRAME sender releases the AL-FEC encoded source and repair packets to a lower transport layer 930 for transmission to a receiver. The AL-FEC encoded source and repair packets may be RTP packets and the lower transport layer may be UDP, or TCP. Under FECFRAME requirements (i.e., RFC 6363), the sender may transmit the source and repair packets in different source and repair flows, e.g., RTP streams, to allow for legacy (non-FEC) applications processing of source packets similar to any systematic code. However, the sender may also use FECFRAME to transmit the source and repair packets jointly within the same data flow (e.g., same RTP session over a single UDP port), multiplexing the source and repair RTP streams.

[0128] The receiver receives over the transport layer source and repair packets.

[0129] If all the source packets are successfully received, no FEC recovery is needed and the FEC repair packets can be discarded.

[0130] If there are however missing source packets the repair packets can be processed and used to recover the lost information within a latency corresponding to at least a repairwindow time configured by the application FEC configuration.

[0131] For example, it may be required that ADU source PDUs (e.g., the source RTP PDUs) contain an additional footer representing a Payload ID. This may then be used on the receiver side to determine if an encoded PDU is lost and to aid selection and usage of proper recovery slot for decoding missing packets based on the encoded available PDUs, i.e., either source or repair PDUs. In many embodiments where RTP / SRTP is used, this information is readily available as part of the RTP / SRTP sequence number which acts as a Payload ID replacement. In such implementations the source RTP / SRTP packets resulting from a FECFRAME encoding are sent unchanged similarly to any systematic coding procedure. This provides backwards compatibility to receivers not supporting AL-FEC for example. For instance, a scheme used to encode the source and repair PDUs as RTP / SRTP packets may be using therefore the sequence number of the original RTP / SRTP sourcepackets as a Payload ID replacement (e.g., for Raptor / RaptorQ code, in Single Sequenced Flow encoding mode according to RFC 6681). This indicates thus the dependency of encoded repair RTP / SRTP packets to the block of RTP / SRTP source packets jointly encoded aiding the decoder endpoint in efficient decoding.

[0132] Alternatively, other generic AL-FEC based content delivery protocols may be considered in alignment with RFC 5052, i.e., the Forward Error Correction (FEC) Building Block. Similar to the FECFRAME scheme, the Application Data Units (ADUs) are not sent directly to the network, but are added to a source block AL-FEC encoder. The encoder systematically encodes and generates packets of equal size, including repair packets, to add redundancy and then distribute the content. The ADU (e.g., a video frame, a video slice, or alternatively a generic object) has assigned some size F and some additional properties (e.g., the type of the ADU - video, audio, etc., its importance, its delay constraints etc.). The ADU is split into a source block with K encoding symbols, each of size T. The encoding symbols form the payloads of the K source packets, whereby each repair packet generated up to a desired set of N-K repair packets include the source block size K, the Encoding Symbol Id (ESI). Each of the repair packets may further include some of the ADU and encoding operation properties (e.g., additional encoding parameters needed to construct a certain repair packet etc.). In addition, the size F of the ADU may be carried as part of the source block. As such, the K source packets, and the N-K repair packets constitute the AL-FEC encoded content of the ADU and may be sent and treated commonly as the same ADU. The source and repair packets would share therefore a common Transport Object Identifier (TOI). Parameters F, K, T and N are AL-FEC encoding parameters.

[0133] The FEC Payload ID (i.e., the information carried in every packet header), essentially only requires carrying the ESI and the source block size K given T is fixed. As an example, for RaptorQ as defined in IETF RFC 6330 by M. Luby et al and titled “RaptorQ Forward Error Correction Scheme for Object Delivery” August 2011, the maximum source block size is 56403, i.e., 16 bits are sufficient to encode the size of K. It is also expected that to signal the ESI, 1 or 2 bytes would be sufficient for most applications. Additionally, a TOI may be carried as clarified above, again using 1 or 2 bytes. While theabove FEC configuration only serves as one reference, it may be considered as a typical implementation.

[0134] Generally, at a receiver, if one or more packets associated with the ADU are lost a maximum delay of an ADU needs to be set, typically compared to the render time, after which only received packets are processed as part of the ADU. In case of Maximum Distance Separable (MDS) codes, i.e., the ones that meet the Singleton Bound such as Reed-Solomon codes, alternatively the Raptor codes family, if at least K packets are received for an ADU within the time budget, the ADU can be fully recovered. If less than K packets are received, the ADU cannot be recovered and one of the following two error handling modes may be applied upon configuration:• ADU loss: If more than N-K of the packets associated to the ADU are lost, the entire ADU is lost.• Suffix loss: If more than N-K of the packets associated to the ADU are lost, then only the correct prefix preceding the first loss of a source packet is used to generate a partially received ADU.

[0135] Raptor / RaptorQ FEC Scheme recovery properties determine that recovery of K encoded source packets is possible from any K + h coded source or repair packets with a probability 1 —256ft+1, whereby an encoded symbol corresponds to an encoded packet. This implies that recovering K encoded source symbols from a set of N encoded source and repair packets where only K + 1 encoded packets have been received is essentially 99.99%, i.e., very large. In other embodiments, whereby an encoded packet corresponds to more than one encoded symbol, a high probability of recovery is maintained also after packetization thus allowing Raptor / RaptorQ codes to achieve strong error correction performance.

[0136] Based on the above, when ADU is systematically AL-FEC encoded, a PDU Set is formed of the source PDUs corresponding to the original, non-encoded ADU, and their corresponding repair PDUs as described for instance in Greek Patent Application Number 20220100751 to Stoica et al., [Applicants ref: SMM920220119-GR-NP] - “Efficient Transmission of PDU Sets in a Wireless Communication Network”. In case of non-systematic AL-FEC schemes, the PDU Set is formed of the AL-FEC encoded ADU, including its parity, or alternatively repair / redundant PDUs.

[0137] If the RAN is PDU Set-aware and AL-FEC-aware the RAN may dynamically optimize system capacity and delivery of PDU Sets comprising AL-FEC encoded ADUs by dropping irrelevant or redundant content. For instance, in case of congestion, or alternatively when activated for a QoS flow, the RAN may drop up to N-K PDUs of an AL- FEC encoded PDU Set up without compromising the recovery of the PDU Set payload. Similarly, the RAN may drop all PDUs of a PDU Set comprising an AL-FEC encoded ADU when it detects it cannot transmit any PDUs accounting to at least K PDUs, wherein K represents the number of sources, or alternatively content, PDUs and N-K represents the number of repair, or alternatively redundant, PDUs. Such RAN policies and associated signaling and procedures are described relative to the 5G system within Greek Patent Application Number 20220100751 [Applicants ref: SMM920220119-GR-NP] and Greek Patent Application Number 20240100017 [Applicants ref: SMM920230182-GR-NP],

[0138] The RAN may be signalled (e.g., by means of QoS flow rules / network policy) to reduce the load on the air-interface and actively discard redundant packets (i.e., outside the context of congestion events) in case of serving AL-FEC encoded traffic over a data radio bearer (DRB). The RAN may be signalled with a static AL-FEC content ratio (i.e., ratio of originally uncoded PDUs to ratio of all AL-FEC coded PDUs of a PDU Set, or alternatively, ratio of originally uncoded ADU size to ratio of AL-FEC encoded PDU Set size) via control plane procedures and interfaces (e.g., by means of AF to PCF / NEF signalling followed by PCC rules and corresponding QoS rules derivation at the SMF, the QoS rules further signalled to the AMF / RAN by the SMF), or alternatively with a dynamic AL-FEC content ratio via user plane protocol extensions (e.g. by means of RTP header extensions providing AL-FEC content or redundancy levels on a per PDU Set basis). The RAN discard behaviour of redundant PDUs frees bandwidth and radio resources by removing the AL-FEC elements of traffic associated with DRB. This mainly benefits other UEs, while the subject UE whose redundant PDUs are discarded is not impacted as the network ensures enough PDUs are available for recovering transmitted data directly.

[0139] Figure 10 illustrates bandwidth trade-offs between media content and redundant information E2E across a heterogeneous link. Figure 10a illustrates the content ratio, or alternatively the redundancy ratio (i.e., the ratio between the repair / redundant PDUs of a PDU Set and the source / originally uncoded PDUs of the PDU Set), versus the concept of available bandwidth across three different network segments (i.e., from right to left): the data network 1026, the core network 1028, and the radio access network 1030 for delivering data, in the form of PDUs from an AS of an Application Service Provider to a client device 1035. The client device 1035 may be a UE. Figure 10a presents an AS QoS session corresponding to a QoS flow configured to typical XR dual -eye buffered 2K x 2K content in DL at 30 Mbps, or similarly to a highly dynamic UHD CG application. In case of good network conditions, as displayed in Figure 10a, the redundant content is consuming the bandwidth available without any benefits as low loss or even no loss is incurred. As an example, RAN behaviour for active discarding of AL-FEC redundant PDUs, the RAN side, mitigates the unnecessary usage of bandwidth through redundant content by actively discarding the redundant AL-FEC PDUs to free system capacity for other users. In contrast, Figure 10b shows a scenario where loss is incurred on the data network 1026 segment, whereas the managed segments (i.e., core network 1028 and radio network 1030) handle the QoS flow within the QoS requirements. In Figure 10c another scenario is shown where the radio network 1030 experiences losses which can be mitigated with low-latency by leveraging and transmitting the AL-FEC redundant PDUs. Losses in any of the network segments may consume the redundant PDUs, while an active discarding radio network behaviour will always discard any unnecessary redundancy.

[0140] The concepts of content ratio and redundancy ratio are related. The content ratio _ may be defined as CR = — , the ratio between the repair / redundant PDUs (i.e., N-K) of aPDU Set and all the encoded PDUs of the PDU Set (i.e., N). Further, a redundancy ratio may be defined as RR = — — , the ratio between the redundant PDUs (i.e., N-K) of a PDUSet and the source / originally uncoded PDUs of the PDU Set (i.e., K). The relationship between content ratio and redundancy ratio may thus be summarized as RR = CR ■

[0141] An Application Service Provider (ASP) may actively enable discard behavior as part of request for AFQoSSession to PCF. The ASP may provision an AF to configure a QoS session for the AS serving AL-FEC content wherein the QoS flow requested is aware of both the PDU Set and the AL-FEC encoding, and additionally, may request, or alternatively allow, the network (e.g., the RAN) to actively (i.e., not only in presence of congestion) discard redundant PDUs according to the AL-FEC content ratio, or alternatively redundancy ratio, configuration. In one implementation, the active discard behavior request may be comprised within an AF request for AS session with QoS towards a NEF / PCF, wherein the active discard behavior is corresponding to a set of AL-FEC content ratios / redundancy ratios that may be applied statically, or dynamically, by the AS / ASP during AL-FEC encoding procedure. The request for QoS may additionally comprise QoS parameter requirements, such as PSDB, PSER, PSIHI, or alternatively, PDB, PER, which signal the QoS flow expected behavior from the AS / ASP, including packet / PDU Set error rates. In addition, the AF may request and configure network assistance for bit rate recommendations by providing a set of desired bit rates corresponding to the AL-FEC configuration. Example configurations may include, besides the delay budget and data rates, also a set of AL-FEC configurations and content / redundancy ratios. These can be used by the network / client (MSH) to determine the network-assisted bitrate recommendation. For example, such a configuration in the case of a DL AL-FEC encoded data flow may comprise information elements that provide the following information:• a request for QoS session for a flow marked by a 5 -tuple or application ID• a set of QoS application requirements (e.g., maxDesBwDlBitRate = 30 Mbps, minDesBwDlBitRate = 20 Mbps, desLatency = 15 ms, maxDesLatency = 20 ms, desLoss = 1%, and so on)• indication of activation of active AL-FEC redundant PDUs discarding (e.g., activeAL-FECDiscard enabled)• a set of AL-FEC configurations.

[0142] The set of AL-FEC configurations may comprise, for example:• AL-FECCodingSchemelD = 0 o AL-FECCodingScheme = None (i.e., no AL-FEC encoding)o isAL-FECMaximumDistanceSeparable = FALSE, o AL-FECRedundantRatio = 0% (all 30 Mbps dedicated to media content)■ Scheme 0 may be applicable in a situation when the packet loss E2E is minimal (« 1%) (or alternatively BW E2E is sufficient) and available bit rate at the radio layers supports the maximum desired bandwidth data rate for DL media content (i.e., 30 Mbps).• AL-FECCodingSchemelD = 1 o AL-FECCodingScheme = RaptorQ, o isAL-FECMaximumDistanceSeparable = TRUE, o AL-FECRedundantRatio = 10% (-2.7 Mbps redundant content and -27.3 Mbps media content)■ Scheme 1 may be applicable in a situation when the packet loss E2E is low (typically -1%) (or alternatively BW E2E is high) and available bit rate at the radio layers supports at least 91% of the maximum desired bandwidth data rate for DL media content (i.e., 30 Mbps).• AL-FECCodingSchemelD = 2 o AL-FECCodingScheme = RaptorQ, o isAL-FECMaximumDistanceSeparable = TRUE, o AL-FECRedundantRatio = 30% (-6.9 Mbps redundant content and -23 Mbps media content)■ Scheme 2 may be applicable in a situation when the loss E2E is moderate (typically -2-3%) (or alternatively BW is moderate) and available bit rate at the radio layers supports at least 77% of the maximum desired bandwidth data rate for DL media content (i.e., 30 Mbps).• AL-FECCodingSchemelD = 3 o AL-FECCodingScheme = RaptorQ, o isAL-FECMaximumDistanceSeparable = TRUE, o AL-FECRedundantRatio = 50% (10 Mbps redundant content and 20 Mbps media content)■ Scheme 3 may be applicable in a situation when the loss E2E is high (typically >5%) (or alternatively BW is varying signification / low) and available bit rate at the radio layers supports at least 66% of the maximum desired bandwidth data rate for DL media content (i.e., 30 Mbps).

[0143] These AL-FEC configurations may be provided by the ASP as part of the dynamic AL-FEC adaptation policy an encoder may take. The AF configuration and request to the network for AS QoS session with assistance for AL-FEC may be provisioned via the ASP. The ASP may provision the QoS requirements and AL-FEC configuration utilizing policy and content generation templates for the media. The templates may be shared with the AF through provisioning and policy template APIs at the interface between the ASP and the AF, or alternatively in the 5G real-time communications subsystem. The interface between the ASP and the AF may comprise Ml or RTC-1 interface in the 5G media streaming subsystem. Assistance for AL-FEC may comprise active discard AL-FEC redundant PDUs being enabled.

[0144] To be able to dynamically adapt the AL-FEC ratio in the presence of active network discarding, an AS, or alternatively an ASP, may use a network (i.e., RAN / core network) estimation of the available bandwidth that can be exploited at lower layers. This information can be combined with feedback procedures that yield auxiliary metrics / features. The feedback procedures may comprise RTCP sender and receiver reports as per RFC 3550, extended reports for E2E bandwidth estimation, e.g., RFC 8888, or RTCP receiver report-based RTT estimation. Auxiliary metrics / features may comprise RTT statistics (e.g., first and second order statistics, such as average, variance / standard deviation estimates), packet loss pattern, RTCP -based E2E bandwidth estimation and so on. These information elements, including the available bit rate / bit rate recommendation at the lower layers, may generate routines capable of adapting the AL-FEC redundancy to cope with any losses E2E while also considering the network active discarding at the lower radio layers.

[0145] Bit rate recommendation described herein may be integrated with existent media subsystems. For example, a network assistance session (e.g., as per 3GPP TS 26.501V18.4.0 Jan 2024 “5G Media Streaming (5GMS); General description and architecture”, or alternatively 3GPP TS 26.506 vl8.1.0 Jan 2024 “5G Real-time Media Communication Architecture (Stage 2)”) provides a bit rate recommendation of the lower layers. The bit rate recommendation provides the available bandwidth estimate of the radio layers of the network and may be different than the actual bandwidth served for a logical channel. The bit rate recommendation may be upper limited by the maximum data rate requirements configured by the AF for a QoS flow associated with the logical channel queried (e.g., 30 Mbps corresponding to a maxDataRate configuration of 30 Mbps by the AF to the PCF / NEF for a QoS Session for the AS). Alternatively, the bit rate recommendation may be upper limited by the physical layer limitations (e.g., system load, available radio resources, and so on) and radio configuration associated with the logical channel (e.g., applicable MCS, number of spatial layers, and so on). Regardless of which of the above alternatives is implemented, the bit rate recommendation is the bit rate which the gNB recommends at the physical layer for the corresponding logical channel and traffic direction. For example, the gNB may recommend a bit rate without an active query based on 0AM configuration as triggered by an event such as a periodic timer, radio / DRB / QoS flow configuration changes, and so on.

[0146] The bit rate recommendation may be acquired by direct interaction between the media client in the UE, e.g., through the Media Session Handler (MSH), by means of a UE modem firmware interface which exposes the UE query and network reply for a bit rate recommendation. The procedure of bit rate recommendation query and reply from the network is thus based on the Medium Access Control (MAC) Control Element (CE) request-reply exchange for bit rate recommendation as of 3GPP TS 38.321 vl8.0.0 Jan 2024 “NR; Medium Access Control (MAC) protocol specification”, specifically clause 5.18.10 thereof. The UE queries the network for a bit rate recommendation providing a target bit rate within the query (e.g., 25.000 Kbps) and the corresponding logical channel identifier associated with the QoS flow with AL-FEC active discarding and AL-FEC encoded traffic, and a traffic direction (i.e., UL / DL). The network replies to the query with the recommended bit rate MAC CE to indicate the recommended bit rate for the UE on the queried logical channel and traffic direction. The UE client (e.g., the Media SessionHandler) may expose the information to the application logic (e.g., the AL-FEC dynamic encoder residing for instance at the AS / ASP) in several ways:• directly via a MSH API exposed at reference point M6, or alternatively RTC-6, wherein the network assistance bit rate recommendation is made available to an application client; o the application client may further communicate the information to a corresponding ASP / AS by application-specific means (e.g., via M8, or RTC- 8 reference points and corresponding APIs)• through the AF wherein the MSH notifies the AF of the bit rate recommendation and the AF acts as a network-assistance server to other network entities (e.g., the AS) via new service-based interfaces exposing APIs to consume such information (a new AF to AS interface e.g., M3, or alternatively RTC-3, exposing such network assistance APIs to the AS), or alternatively, via existent service-based interfaces exposing network assistance APIs (e.g., M5, or alternatively RTC-5, exposing such network assistance APIs to the MSH).

[0147] The bit rate recommendation may be acquired by the application logic through the AF. The AF may this act as a service exposing the network assistance to other network entities, such as the AS or the UE client (i.e., through the MSH). For example, the AF may become aware of any changes in network policy and corresponding data rates associated with the one or more QoS flows of and AL-FEC encoded service based on exposed network notifications at the NEF. The AF subscribes to QoS flow updates associated with the service (e.g., 5-tuple, application ID) of the AL-FEC encoded traffic. Once notified of network capacity changes and QoS changes the AF processes the updates and provides corresponding bit rate recommendations (i.e., the bit rates supported by the network) to other network entities. An example of such other network entities is the MSH on the UE side, which may further expose the received recommendations to the UE application client. The MSH may thus be notified over M5_NetworkAssistance APIs. Such M5_NetworkAssistance APIs are a new interface directly interacting with the AS. In other implementations, the AF may additionally interact with other network entities under the direct control, or configuration of the ASP, e.g., the AS. For instance, an AS may negotiate and open a network assistance session with the AF. The session may be authenticated andauthorized as provisioned by the ASP. For instance the ASP may limit the access to bit rate recommendations and network assistance to a specific subset of ASs. The subset of ASs may be defined based on a characteristic such as service access, or geolocation. During a network assistance session, the AS may then request bit rate recommendation assistance information from the AF which forwards the determined recommended bit rate. The bit rate recommendation may be corresponding to a QoS flow and traffic direction (e.g., UL / DL). The QoS flow and data traffic carried therein may be encoded with AL-FEC according to a configuration provisioned by the ASP and signaled to the network by the AF entity acting as network assistance server.

[0148] It should be noted that the network assistance may further comprise both service-based interfaces and corresponding APIs to provide a data rate increase as a delivery boost for AL-FEC encoded data flows and corresponding QoS flows. The procedures for delivery boost may be based on access network assistance, via MAC CE bit rate recommendation procedures or based on AF policy change request given the provisioned AL-FEC enabled policy templates. The request for the delivery boost may be coupled with an ASP policy to modify (i.e., reduce, increase or eliminate) AL-FEC based on the network (i.e., core network and RAN) and E2E transport characteristics regarding delay, available bandwidth and pattern loss. For instance, in some implementations the AS may lower the AL-FEC encoding when the delivery boost is requested, and the network accepts it. As an example, for a delivery boost request from 30 to 40 Mbps, the AF is notified by the Npcf Policy Authorization notification service or Nnef Monitoring Event procedure to receive QoS changes. The AF receives these policy change notifications asynchronously and may forward them to other network entities under the control of the ASP, i.e., the AS (e.g., via a notification service for delivery boost exposed towards ASes over M3 / RTC-3 reference point), or alternatively to the UE client, via the MSH. In case the AS gets notified of the change, the AS may apply a provisioned AL-FEC policy reducing for instance the redundancy ratio from 30% (i.e., from ~6.9 Mbps redundant content at 30 Mbps) to 10%, (i.e., ~3.7 Mbps redundant content at 40 Mbps) and keep the bandwidth overhead of the redundant packets within certain limits. Such a delivery boost could be reused for RTC as well, but if AL-FEC is enabled, the content ratio needs to be adapted to avoid overconsuming bandwidth with redundant content.

[0149] Upon configuration of the ASP, the AS may completely disable AL-FEC when the traffic is served over a managed mobile network such as 5G System and its corresponding 5G NR, or equivalents thereof. The ASP may detect the mobile network by means of ASP network configuration and policy rules and decide to disable AL-FEC and instead utilize an AS session with guaranteed QoS without AL-FEC to utilize the full available bandwidth for improving visual quality and QoE rather than unnecessary redundancy. The QoS flow configuration without AL-FEC may comprise PDU Set support and may be restricted to specific AS entities belonging to an operator group or geographic region.

[0150] The adaptation loop of a dynamic controller at a sender device may be based on metrics, the metrics determining a necessary redundancy level sufficient to counter any link loss E2E while not consuming too much of the available latency. Furthermore, the adaptation loop may comprise the active discard operation of AL-FEC traffic at the network level. The entity (e.g., the AS, or alternatively the ASP) in control of the dynamic controller may signal the adaptation loop capability to the network by at least activating or enabling the active AL-FEC network discard feature and providing the network with one or more AL-FEC configurations, including at least an AL-FEC content ratio, or alternatively, a redundancy ratio. For example, the dynamic controller may fix the AL-FEC configuration to a static level of redundancy and not modify it regardless of the active discarding of the RAN. Alternatively, the AL-FEC level may be controlled by the dynamic AL-FEC controller based on at least:• network-assisted bit rate recommendations;• RAN discard procedure dropping up to all redundant PDUs, i.e., N-K, of the PDUs associated with an AL-FEC encoded ADU, or alternatively, a PDU Set;• E2E (i.e., between AS and client UE) RTT and bandwidth in-band (user plane, e.g., as based on RTCP feedback) measurements and sample statistics; and / or• as well as other metrics to the choice of the implementation.

[0151] A workflow 1100 in accordance with elements of the embodiments herein is displayed in Figure 11. Workflow 1100 is performed by a UE 1135, a PCF / SMF 1115 / 1120, an AF 1110, an ASP 1112, a remote endpoint 1145, and a dynamic AL-FEC controller 1150. Two options for network assistance are shown: a first option 1150 and asecond option 1160. The first option 1150 comprises steps 1178 to 1181. The second option 1160 comprises steps 1182 to 1184. The second option 1160 additionally involves communications between UE modem 1138 and RAN 1130.

[0152] A real-time communications session (e.g., based on RTP / SRTP, or alternatively WebRTC protocols) is established between two endpoints (the UE 1135 and the remote endpoint 1045) using external signalling mechanisms. The remote endpoint 1045 may be a peer UE or an AS under the control of the ASP. The external signalling mechanisms may involve SDP signalling procedures including ICE candidates or TURN servers’ information exchange as provided by the ASP, or alternatively, by a mobile network operator. Each endpoint of the connection that is using the 5G system may benefit from 5G network support (e.g., such as the network assistance for dynamic AL-FEC control loop adaptation as described herein). With reference to Figure 11, the workflow 1100 comprises the following steps.

[0153] At 1170, a provisioning session may have been created by the ASP 1112 with the MNO to provision an AF 1110 with content and dynamic policy templates (including AL-FEC configuration details), AS / edge service access information and so on.

[0154] At 1171, an application 1136 running on the UE 1135 uses application-specific signalling functions (e.g., SDP procedure) to establish an RTC session with the remote endpoint 1145.

[0155] Steps 1172 to 1176 are broadly related to QoS Allocation. The QoS allocation may include allocation of an AL-FEC configuration.

[0156] At 1172, the application 1136 starts the RTC session by informing the MSH 1137 about the new RTC session. The application 1136 shares information about the media streams and their associated 5-Tuples, media services, access information, and / or application ID. The request to start the RTC session may be sent over the RTC-6 interface.

[0157] At 1173, the MSH 1137 requests network assistance for the RTC session and provides the transport and bandwidth information to the network support AF 1110. In some implementations this step may be skipped as the AF 1110 may be directly configured byASP provisioning information regarding the desired network assistance for the RTC session. The request for QoS assistance may be sent over the RTC-5 interface.

[0158] At 1174, the Network Support AF 1110 uses the N5 or N33 interface to request QoS allocation. It may request differential charging based on pre-existing ASP provisioning for these sessions, including for instance QoS flow treatment with AL-FEC and / or PDU Set support, wherein an AL-FEC initial configuration (i.e., containing at least AL-FEC scheme configuration, redundancy level and indication whether active AL-FEC discarding by RAN is enabled). The request may comprise a request for QoS for a session. The request may be sent using the N5 or N33 interface. The request may be sent to the PCF 1115 either directly (i.e., over N5), or via the Network Exposure Function (NEF) (i.e., over N33).

[0159] At 1175, confirmation of QoS allocation is notified to the Network Support AF 1110. This may be conveyed over the N5 or N33 interfaces. The Network Support AF 1110 may also already subscribe to events related to the QoS flows of the RTC session with the PCF 1115 and SMF 1120. This may be done via the NEF interface N33 exposing the network monitoring service.

[0160] At 1176, the Network Support AF routes the QoS allocation confirmation to the MSH to complete the QoS allocation step for the RTC session. This may be conveyed via the RTC-5 interface.

[0161] At 1177, the RTC session UL / DL traffic flow starts being served by the network on the allocated QoS flow(s) as configured. The UL / DL traffic flow includes AL-FEC. The DL traffic may contain RTP / SRTP streams, RTCP / SRTCP reports and data channel corresponding to WebRTC. The UL traffic may similarly contain some RTP / SRTP streams, RTCP / SRTCP reports including feedback reports regarding the DL RTP / SRTP streams, and data channel corresponding to WebRTC.

[0162] Two alternative options of network assistance are illustrated in figure 11. The first option 1150 is for AF -based network assistance and comprises steps 1178 to 1181.

[0163] At 1178, the Network Support AF 1110 subscribes (if not done already upon QoS allocation step) to events related to the QoS flows of the RTC session with the PCFand SMF. This may be done via the NEF interface N33 exposing the network monitoring service, or over the N5 interface via the PCF 1115.

[0164] At 1179, the Network Support AF 1110 receives asynchronously notifications about changes to the QoS flows of the RTC session. These notifications may be sent from the PCF 1115 and / or the SMF 1120. These may be sent using the N5 or N33 interface.

[0165] At 1180, the Network Support AF 1110 sends notifications to the MSH 1137 about changes to the QoS of the session over the RTC-5 service APIs for network assistance. This information may contain for example bit rate recommendations. This may be conveyed via the RTC-5 interface.

[0166] At 1181, the Network Support AF 1110 also sends notifications to the remote endpoint 1145 (e.g., an AS) about changes to the QoS of the session over new RTC-3 service APIs for network assistance. This information may contain for example bit rate recommendations. This may be conveyed via the RTC-3 interface.

[0167] The second option 1160 is for Access Network Bitrate Recommendation (ANBR) and comprises steps 1182 to 1184.

[0168] At 1182, as an alternative to the first option 1150, the MSH 1137 may interact with the UE modem 1138 to trigger the query of the access network recommended bitrate on the uplink or downlink direction according to the configured QoS flows.

[0169] At 1183, the UE modem 1138 then sends the ANBRQ (Access Network Bit Rate Query) message (i.e., the MAC CE bit rate recommendation request as defined for NR access in 3GPP TS 38.321 vl8.0.0 (Jan 2024) titled “NR; Medium Access Control (MAC) protocol specification” or for LTE access in 3GPP TS 36.321 vl8.0.0 (Jan 2024) “Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification”). This is typically sent over the Uu interface.

[0170] At 1184, the RAN 1130, based on the network status, returns the recommended bitrate to the UE modem 1138 as requested. The recommended bit rate is in Kbps at the physical layer at the time when the gNB recommendation decision is made. The gNB (or alternatively the UE without support from gNB in some cases) may determine thecorresponding IP layer bitrate based on the long-term average of the IP packet sizes, L2 header sizes, and ROHC header sizes, but the translation methodologies and the estimation error levels required to implement accurate media bitrate adaptation have not been specified and are up to the implementation of individual estimator routines.

[0171] At 1185, the bit rate recommendation is shared with the RTC application logic for AL-FEC dynamic control. This may be done in different ways. One path may include first UE client notification from the MSH over RTC-6 network assistance APIs, followed by user plane feedback (i.e., over RTC-4 reference point from UE client application to AS), e.g., based on RTCP receiver reports with extensions for bit rate recommendation, or alternatively, RTCP extended reports including bit rate recommendation / congestion control information. An alternative path may include control plane signalling from the MSH to the Network Support AF over a network assistance notification at RTC-5 network assistance service. The notification is further routed from the Network Support AF to the AS over RTC-3 new network assistance service and corresponding APIs. The notifications may be shared asynchronously or upon client request at the service operation points for network assistance. The notification may be sent via the RTC-6 and RTC-4 interfaces or the RTC-5 and RTC-3 interfaces.

[0172] At 1186, the dynamic AL-FEC controller 1150 is fed the network assistance information which may comprise the network bit rate recommendation. In addition, the dynamic AL-FEC controller may use other inputs such as E2E RTT estimates, bandwidth estimates, network loss patterns and corresponding statistics thereof, as well as AL-FEC policies of the ASP to determine the dynamic control and adaptation of the AL-FEC redundancy level. The dynamic AL-FEC controller may change the AL-FEC redundancy level upon network QoS changes, RTC content delivery QoE metrics, or ASP policy.

[0173] At 1187, the remote endpoint 1145 (e.g., the AS) requests to the Network Support AF dynamic policy changes (e.g., over RTC-3 dynamic policy service APIs) given the determined dynamic AL-FEC changes (as well as other QoS parameter changes) based on the policy templates provisioned by the ASP. The request may be sent over the RTC-3 interface.

[0174] At 1188, the Network Support AF 1110 requests dynamic QoS change for the QoS flows of the RTC session. The request includes an updated AL-FEC config.

[0175] At 1189, the RTC session is served over the updated QoS including a new AL- FEC redundancy level. The RTC session thus provides continued DL and / or UL content delivery. The DL includes adapted AL-FEC redundancy ratio. The UL may comprise RTC content delivery such as (S)RTP streams, (S)RTCP feedback, etc.

[0176] Figure 12 illustrates an example of a UE 1200 in accordance with aspects of the present disclosure. The UE 1200 may include a processor 1202, a memory 1204, a controller 1206, and a transceiver 1208. The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0177] The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0178] The processor 1202 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1202 may be configured to operate the memory 1204. In some other implementations, the memory 1204 may be integrated into the processor 1202. The processor 1202 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the UE 1200 to perform various functions of the present disclosure.

[0179] The memory 1204 may include volatile or non-volatile memory. The memory 1204 may store computer-readable, computer-executable code including instructions whenexecuted by the processor 1202 cause the UE 1200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1204 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general -purpose or special-purpose computer.

[0180] In some implementations, the processor 1202 and the memory 1204 coupled with the processor 1202 may be configured to cause the UE 1200 to perform one or more of the functions described herein (e.g., executing, by the processor 1202, instructions stored in the memory 1204). For example, the processor 1202 may support wireless communication at the UE 1200 in accordance with examples as disclosed herein. The UE 1200 may be configured to support a means for requesting QoS assistance from an Application Function in a wireless communication network; receiving confirmation of successful QoS allocation for a QoS flow; receiving a bitrate indication from a node in the wireless communication network; and performing QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0181] The controller 1206 may manage input and output signals for the UE 1200. The controller 1206 may also manage peripherals not integrated into the UE 1200. In some implementations, the controller 1206 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1206 may be implemented as part of the processor 1202.

[0182] In some implementations, the UE 1200 may include at least one transceiver 1208. In some other implementations, the UE 1200 may have more than one transceiver 1208. The transceiver 1208 may represent a wireless transceiver. The transceiver 1208 may include one or more receiver chains 1210, one or more transmitter chains 1212, or a combination thereof.

[0183] A receiver chain 1210 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1210may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1210 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1210 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0184] A transmitter chain 1212 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1212 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1212 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0185] Figure 13 illustrates an example of a processor 1300 in accordance with aspects of the present disclosure. The processor 1300 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1300 may include a controller 1302 configured to perform various operations in accordance with examples as described herein. The processor 1300 may optionally include at least one memory 1304, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1300 may optionally include one or more arithmetic-logic units (ALUs) 1306. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0186] The processor 1300 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing,determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1300) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0187] The controller 1302 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein. For example, the controller 1302 may operate as a control unit of the processor 1300, generating control signals that manage the operation of various components of the processor 1300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0188] The controller 1302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1304 and determine subsequent instruction(s) to be executed to cause the processor 1300 to support various operations in accordance with examples as described herein. The controller 1302 may be configured to track memory address of instructions associated with the memory 1304. The controller 1302 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1302 may be configured to manage flow of data within the processor 1300. The controller 1302 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1300.

[0189] The memory 1304 may include one or more caches (e.g., memory local to or included in the processor 1300 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1304 may reside within or on a processor chipset (e.g., local to the processor 1300). In some other implementations, the memory 1304 may reside external to the processor chipset (e.g., remote to the processor 1300).

[0190] The memory 1304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1300, cause the processor 1300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1302 and / or the processor 1300 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the processor 1300 to perform various functions. For example, the processor 1300 and / or the controller 1302 may be coupled with or to the memory 1304, the processor 1300, the controller 1302, and the memory 1304 may be configured to perform various functions described herein. In some examples, the processor 1300 may include multiple processors and the memory 1304 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0191] The one or more ALUs 1306 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1306 may reside within or on a processor chipset (e.g., the processor 1300). In some other implementations, the one or more ALUs 1306 may reside external to the processor chipset (e.g., the processor 1300). One or more ALUs 1306 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1306 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1306 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1306 may support logical operations such as AND,OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1306 to handle conditional operations, comparisons, and bitwise operations.

[0192] The processor 1300 may support wireless communication in accordance with examples as disclosed herein. The processor 1300 may be configured to or operable to support a means for requesting QoS assistance from an Application Function in a wireless communication network; receiving confirmation of successful QoS allocation for a QoS flow; receiving a bitrate indication from a node in the wireless communication network; and performing QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0193] Figure 14 illustrates an example of a NE 1400 in accordance with aspects of the present disclosure. The NE 1400 may include a processor 1402, a memory 1404, a controller 1406, and a transceiver 1408. The processor 1402, the memory 1404, the controller 1406, or the transceiver 1408, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0194] The processor 1402, the memory 1404, the controller 1406, or the transceiver 1408, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0195] The processor 1402 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1402 may be configured to operate the memory 1404. In some other implementations, the memory 1404 may be integrated into the processor 1402. The processor 1402 may be configured to execute computer-readable instructionsstored in the memory 1404 to cause the NE 1400 to perform various functions of the present disclosure.

[0196] The memory 1404 may include volatile or non-volatile memory. The memory 1404 may store computer-readable, computer-executable code including instructions when executed by the processor 1402 cause the NE 1400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1404 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0197] In some implementations, the processor 1402 and the memory 1404 coupled with the processor 1402 may be configured to cause the NE 1400 to perform one or more of the functions described herein (e.g., executing, by the processor 1402, instructions stored in the memory 1404). For example, the processor 1402 may support wireless communication at the NE 1400 in accordance with examples as disclosed herein. The NE 1400 may be configured to support a means for applying a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generating a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; requesting, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribing to the second network function for a set of one or more network events corresponding to the QoS flow; and exposing a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0198] Alternatively, the NE 1400 may be configured to or operable to support a means for determining an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL-FECredundancy level; encoding a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration; routing the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribing to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapting the AL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller.

[0199] The controller 1406 may manage input and output signals for the NE 1400. The controller 1406 may also manage peripherals not integrated into the NE 1400. In some implementations, the controller 1406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1406 may be implemented as part of the processor 1402.

[0200] In some implementations, the NE 1400 may include at least one transceiver 1408. In some other implementations, the NE 1400 may have more than one transceiver 1408. The transceiver 1408 may represent a wireless transceiver. The transceiver 1408 may include one or more receiver chains 1410, one or more transmitter chains 1412, or a combination thereof.

[0201] A receiver chain 1410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1410 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1410 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1410 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1410 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0202] A transmitter chain 1412 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal fortransmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0203] Figure 15 illustrates a flowchart of a method 1500 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0204] At 1502, the method 1500 may include requesting QoS assistance from an Application Function in a wireless communication network. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a UE as described with reference to Figure 12.

[0205] At 1504, the method 1500 may include receiving confirmation of successful QoS allocation for a QoS flow. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a UE as described with reference to Figure 12.

[0206] At 1506, the method 1500 may include receiving a bitrate indication from a node in the wireless communication network. The operations of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1506 may be performed a UE as described with reference to Figure 12.

[0207] At 1508, the method 1500 may include performing QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL- FEC) configuration corresponding to the QoS flow. The operations of 1508 may be performed in accordance with examples as described herein. In some implementations,aspects of the operations of 1508 may be performed a UE as described with reference to Figure 12.

[0208] It should be noted that the method 1500 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0209] Figure 16 illustrates a flowchart of a method 1600 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0210] At 1602, the method 1600 may include applying a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations. The operations of 1602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1602 may be performed by a NE as described with reference to Figure 14.

[0211] At 1604, the method 1600 may include generating a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy. The operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by a NE as described with reference to Figure 14.

[0212] At 1606, the method 1600 may include requesting, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration. The operations of 1606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1606 may be performed a NE as described with reference to Figure 14.

[0213] At 1608, the method 1600 may include subscribing to the second network function for a set of one or more network events corresponding to the QoS flow. Theoperations of 1608 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1608 may be performed by a NE as described with reference to Figure 14.

[0214] At 1610, the method 1600 may include exposing a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow. The operations of 1610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1610 may be performed a NE as described with reference to Figure 14.

[0215] Figure 17 illustrates a flowchart of a method 1700 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0216] At 1702, the method 1700 may include determining an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL-FEC redundancy level. The operations of 1702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1702 may be performed by a NE as described with reference to Figure 14.

[0217] At 1704, the method 1700 may include encoding a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration. The operations of 1704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1704 may be performed by a NE as described with reference to Figure 14.

[0218] At 1706, the method 1700 may include routing the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow. The operations of 1706 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1706 may be performed a NE as described with reference to Figure 14.

[0219] At 1708, the method 1700 may include subscribing to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes. The operations of 1708 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1708 may be performed by a NE as described with reference to Figure 14.

[0220] At 1710, the method 1700 may include adapting the AL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller. The operations of 1710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1710 may be performed a NE as described with reference to Figure 14.

[0221] There is provided herein a network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network function to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow for the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; and expose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0222] Such a network function tends to enable an application to dynamically apply and switch among different AL-FEC configurations and exploit the available bandwidth within a wireless communication network to the benefit of optimized Quality of Experience (QoE). A network assistance may provide a dynamic FEC controller of the application withinformation related to the available bandwidth within the network (i.e., within the core network, and / or within the Radio Access network (RAN)). The dynamic FEC controller can as such use (i.e., per specific implementation) the available bandwidth metrics, or alternatively bit rate recommendations, with additional packet feedback information (e.g., RTCP sender reports and RTCP receiver reports), network pattern loss information, roundtrip time / network delay statistics in order to determine the AL-FEC adaptation policy and increase, or decrease, the content ratio, or alternatively the redundancy ratio, of the AL- FEC encoder. The network assistance provided by the network function may thus expose the available network bit rate, or alternatively bit rate recommendations, based on queries aligned with a set of AL-FEC configurations and content ratios / redundancy ratios available for an application multimedia sender.

[0223] Exposing a service comprises the network function providing Application Programming Interfaces (APIs) to application consumers. The network function may comprise a network support Application Function. The APIs provide access to service functionality to application consumers. The service functionality may be network assistance or dynamic policy. The application consumers may be application clients, or alternatively application servers which implement the application logic and communicate the application AL-FEC encoded multimedia content.

[0224] The set of provisioning configurations may comprise a set of provisioning configuration templates. The set of one or more network events may comprise a network notifications event. The set of one or more network events may comprise a plurality of network notifications events. The network assistance service may be exposed by a network assistance API.

[0225] The set of provisioning configurations may originate at an Application Service Provider (ASP). The set of provisioning configurations may comprise at least one of: service access information; content delivery protocols information related to the type of one or more media types of the service and preferred delivery protocols; and / or policy template information, wherein policy templates comprise QoS application requirements.

[0226] Service access information may correspond to: one or more AS; one or more Interactive Connectivity Establishment (ICE) candidates; and / or one or more TraversalUsing Relays around Network Address Translation (TURN) servers necessary to route the service across a network.

[0227] Policy templates may optionally include at least one of desired maximum / minimum bit rates, desired maximum / minimum delay budget, desired packet loss, Protocol Data Unit (PDU) Set marking information and / or AL-FEC coding scheme information.

[0228] The at least one processor may be further configured to cause the network function to determine dynamic policy based on the policy template information, the dynamic policy further comprising for each service data flow descriptor and each media component of the AS session at least one of a desired maximum / minimum bit rate, desired maximum / minimum delay budget, desired packet loss, Protocol Data Unit (PDU) Set marking information, and / or AL-FEC coding scheme information.

[0229] The dynamic policy usually corresponds to a service data flow description and a media component. The service data flow description might be a 5-tuple. The media component may comprise a video stream, audio stream, and / or haptic stream etc.

[0230] The dynamic policy may comprise a set of AL-FEC coding scheme configurations applicable by the AS for the AS session, wherein each of the AL-FEC coding scheme configurations comprises at least one of: an AL-FEC mapping identifier; an AL-FEC codec configuration; an AL-FEC redundancy level; a content ratio / redundancy ratio level; a Boolean information element for marking Maximum Distance Separability corresponding to the AL-FEC codec configuration; and an information element indicating whether active discarding of redundant AL-FEC PDUs at the Radio Access Network (RAN) is one of supported or not supported.

[0231] The AL-FEC codec configuration may comprise, for instance, an AL-FEC scheme standardized for Internet Assigned Numbers Authority (IANA) for Real-Time Transport Protocol (RTP), i.e., RaptorQ / Raptor, Reed-Solomon, Random Linear Network Codes (RLNC), Flexible Forward Error Correction (FlexFEC) etc.

[0232] The AL-FEC coding schemes configurations may be integrated as part of the dynamic policy request from a media client to the network for a QoS flow with PDU Set and AL-FEC support.

[0233] The information element indicating whether active discarding of redundant AL- FEC PDUs at the RAN is one of supported or not supported may be further provisioned by an ASP and may be limited to a set of specific AS. The AL-FEC information element within the QoS request configuration for the AS session may comprise one of the AL-FEC coding scheme configurations of the dynamic policy.

[0234] The second network function may be either a Policy Control Function (PCF) or a Network Exposure Function (NEF). The consumer function may be one of a Media Session Handler (MSH) or the AS of the AS Session. The MSH may be a networked functionality embedded within a client UE.

[0235] The network assistance information may correspond to a network bit rate recommendation.

[0236] The generation of the QoS request configuration by the at least one processor may be triggered dynamically by an indication of a change of the dynamic policy originating over the dynamic policy service from one of the Media Session Handler (MSH); and the AS, the AS determining dynamically at least the modification of the AL- FEC information element; wherein the change of dynamic policy is based in part on the network assistance information.

[0237] The modification of the AL-FEC information element may comprise a change of the AL-FEC coding scheme configuration, respectively of the AL-FEC mapping, the AL-FEC codec, the AL-FEC redundancy level, the support for the active discard of redundant AL-FEC PDUs at the RAN.

[0238] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for servingAL-FEC encoded data, the QoS request configuration comprising an Application Layer Forward Error Correction (AL-FEC) information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; and expose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0239] There is further provided a method performed by a network function, the method comprising: applying a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generating a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; requesting, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribing to the second network function for a set of one or more network events corresponding to the QoS flow; and exposing a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0240] The network assistance service tends to enable an application to dynamically apply and switch among different AL-FEC configurations and exploit the available bandwidth to the benefit of optimized Quality of Experience (QoE). The network assistance may provide a dynamic FEC controller of the application with information related to the available bandwidth within the network (i.e., within the core network, and / or within the Radio Access network (RAN)). The dynamic FEC controller can as such use (i.e., per specific implementation) the available bandwidth metrics, or alternatively bit rate recommendations, with additional packet feedback information (e.g., RTCP sender reports and RTCP receiver reports), network pattern loss information, round-trip time / network delay statistics in order to determine the AL-FEC adaptation policy and increase, ordecrease, the content ratio, or alternatively the redundancy ratio, of the AL-FEC encoder. The network assistance provided may thus expose the available network bit rate, or alternatively bit rate recommendations, based on queries aligned with a set of AL-FEC configurations and content ratios / redundancy ratios available for an application multimedia sender.

[0241] Exposing a service comprises, in the network function providing Application Programming Interfaces (APIs) to application consumers. The network function may comprise a network support Application Function. The APIs provide access to service functionality to application consumers. The service functionality may be network assistance or dynamic policy. The application consumers may be application clients, or alternatively application servers which implement the application logic and communicate the application AL-FEC encoded multimedia content.

[0242] The set of provisioning configurations may originate at an Application Service Provider (ASP). The set of provisioning configurations may comprise at least one of: service access information; content delivery protocols information related to the type of one or more media types of the service and preferred delivery protocols; and / or policy template information, wherein policy templates comprise QoS application requirements.

[0243] Service access information may correspond to: one or more AS; one or more Interactive Connectivity Establishment (ICE) candidates; and / or one or more Traversal Using Relays around Network Address Translation (TURN) servers necessary to route the service across a network.

[0244] Policy templates may optionally include at least one of desired maximum / minimum bit rates, desired maximum / minimum delay budget, desired packet loss, PDU Set marking information and / or AL-FEC coding scheme information.

[0245] The dynamic policy may be determined based on the policy template information, the dynamic policy further comprising for each service data flow descriptor and each media component of the AS session at least one of a desired maximum / minimum bit rate, desired maximum / minimum delay budget, desired packet loss, Protocol Data Unit (PDU) Set marking information, and / or AL-FEC coding scheme information.

[0246] The dynamic policy usually corresponds to a service data flow description and a media component. The service data flow description might be a 5-tuple. The media component may comprise a video stream, audio stream, and / or haptic stream etc.

[0247] The dynamic policy may comprise a set of AL-FEC coding schemes configurations applicable by the AS for the AS session, wherein each of the AL-FEC coding schemes configuration comprises at least one of: an AL-FEC mapping identifier; an AL-FEC codec configuration; an AL-FEC redundancy level; a content ratio / redundancy ratio level; a Boolean information element for marking Maximum Distance Separability corresponding to the AL-FEC codec configuration; and an information element indicating whether active discarding of redundant AL-FEC PDUs at the Radio Access Network (RAN) is one of supported or not supported.

[0248] The AL-FEC codec configuration may comprise, for instance, an AL-FEC scheme standardized for IANA for RTP, i.e., RaptorQ / Raptor, Reed-Solomon, Random Linear Network Codes (RLNC), Flexible Forward Error Correction (FlexFEC) etc.

[0249] The AL-FEC coding schemes configurations may be integrated as part of the dynamic policy request from a media client to the network for a QoS flow with PDU Set and AL-FEC support.

[0250] The information element indicating whether active discarding of redundant AL- FEC Protocol Data Units (PDUs) at the Radio Access Network (RAN) is one of supported or not supported may be further provisioned by an ASP and may be limited to a set of specific AS. The AL-FEC information element within the QoS request configuration for the AS session comprises one of the AL-FEC coding scheme configurations of the dynamic policy.

[0251] The second network function may be either a Policy Control Function (PCF) or a Network Exposure Function (NEF). The consumer function may be a Media Session Handler (MSH) or an AS of the AS Session. The MSH may be a networked functionality embedded within a client UE. The network assistance information may correspond to a network bit rate recommendation.

[0252] The generation of the QoS request configuration may be triggered dynamically by an indication of a change of the dynamic policy originating over the dynamic policy service from one of: the Media Session Handler (MSH); and the AS, the AS determining dynamically at least the modification of the AL-FEC information element, wherein the change of dynamic policy is based in part on the network assistance information.

[0253] The modification of the AL-FEC information element may comprise a change of the AL-FEC coding scheme configuration, respectively of the AL-FEC mapping, the AL-FEC codec, the AL-FEC redundancy level, the support for the active discard of redundant AL-FEC PDUs at the RAN.

[0254] There is further provided an Application Server (AS) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the AS to: determine an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL-FEC redundancy level; encode a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration; route the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribe to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapt the AL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller.

[0255] There is further provided a method performed by an Application Server (AS), the method comprising: determining an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL-FEC redundancy level; encoding a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration; routing the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribing to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapting the AL-FEC configuration, the adaptionbased at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller.

[0256] The AL-FEC configuration may be in part dynamically modified by the dynamic AL-FEC controller.

[0257] There is further still provided a User Equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: request QoS assistance from an Application Function in a wireless communication network; receive confirmation of successful QoS allocation for a QoS flow; receive a bitrate indication from a node in the wireless communication network; and perform QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0258] There is yet further still provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: request QoS assistance from an Application Function in a wireless communication network; receive confirmation of successful QoS allocation for a QoS flow; receive a bitrate indication from a node in the wireless communication network; and perform QoS re-allocation, the QoS re-allocation comprising a change in an Application- Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0259] There is also provided a method performed by a user equipment, the method comprising: requesting QoS assistance from an Application Function in a wireless communication network; receiving confirmation of successful QoS allocation for a QoS flow; receiving a bitrate indication from a node in the wireless communication network; and performing QoS re-allocation, the QoS re-allocation comprising a change in an Application-Layer Forward Error Correction (AL-FEC) configuration corresponding to the QoS flow.

[0260] The node in the wireless communication network may comprise the Application function or the Radio Access Network.

[0261] There is described herein a method to allow and account for an active RAN to discard AL-FEC redundant PDUs while performing AL-FEC dynamic adaptation; the method considers the network bit rate recommendations to control the AL-FEC redundancy level and trade-off redundancy for QoE given transport over heterogenous networks mixing QoS guarantees with best effort service. There are further described apparatuses that implement the method, i.e., the AF operating as a network assistance server, and the UE interacting with the network to obtain RAN-level network assistance.; There are further described configuration elements, i.e., enablement of active RAN discarding of AL-FEC redundant PDUs when the ASP / AS is capable of dynamic adaptation handling the non- congestion-based discarding. There are further described new network assistance interfaces exposed to the AS from the AF for consumption of the network assistance bit rate recommendation as inputs towards dynamic AL-FEC controllers.

[0262] A method at a network function, the method comprising: applying a provisioning configuration from a set of provisioning configuration templates; generating a Quality of Service (QoS) request configuration for an Application Server (AS) session, the QoS request comprising an AL-FEC information element corresponding to the AS session serving AL-FEC encoded data, the AL-FEC information element based on at least the provisioning configuration templates and a dynamic policy; requesting from a second network function a QoS flow comprising the AS session based on the QoS request configuration; subscribing to the second network function for network notifications events corresponding to the QoS flow; and exposing a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

[0263] The set of provisioning configuration templates may originate at an Application Service Provider.

[0264] The set of provisioning configuration templates may comprise information related at least one of service access information corresponding to one or more AS, to one or more Interactive Connectivity Establishment (ICE) candidates and optionally to one or more Traversal Using Relays around Network Address Translation (TURN) servers necessary to route the service across a network; content delivery protocols informationrelated to the type of one or more media types of the service and preferred delivery protocols; and / or policy template information, the policy templates comprising QoS application requirements optionally including desired maximum / minimum bit rates, desired maximum / minimum delay budget, desired packet loss, PDU Set marking information and AL-FEC coding scheme information.

[0265] The dynamic policy is determined based on the policy template information, the dynamic policy further comprising for each AS session service data flow descriptor and media component at least one of a desired maximum / minimum bit rate, desired maximum / minimum delay budget, desired packet loss, PDU Set marking information and AL-FEC coding scheme information.

[0266] The dynamic policy AL-FEC configuration comprises a set of AL-FEC coding schemes configurations applicable by the AS for the AS session, each of the AL-FEC coding scheme configuration comprising of at least one of: an AL-FEC mapping identifier; an AL-FEC codec configuration [e.g., as for instance an AL-FEC scheme standardized for IANA for RTP, i.e., RaptorQ / Raptor, Reed-Solomon, Random Linear Network Codes (RLNC), Flexible Forward Error Correction (FlexFEC) etc.]; an AL-FEC redundancy level [or alternatively a content ratio / redundancy ratio level]; a Boolean information element for marking Maximum Distance Separability corresponding to the AL-FEC codec configuration; and / or an information element indicating whether active discarding of redundant AL-FEC Protocol Data Units (PDUs) at the Radio Access Network (RAN) is one of supported or not supported [this feature may be further provisioned by an ASP and may be limited to a set of specific AS],

[0267] The AL-FEC information element within the QoS request for the AS session comprises one of the AL-FEC coding scheme configuration of the dynamic policy.

[0268] The second network function may be one of: a Policy Control Function (PCF); and a Network Exposure Function (NEF).

[0269] The consumer function is one of: a Media Session Handler (MSH) [e.g., the MSH may be a networked functionality embedded within a client UE]; and the AS of the AS Session.

[0270] The network assistance information may correspond at least to a network bit rate recommendation.

[0271] The generation of the QoS request is triggered dynamically by an indication of a change of the dynamic policy originating over the dynamic policy service from one of: the Media Session Handler (MSH); and the AS, the AS determining dynamically at least the modification of the AL-FEC information element [e.g., the change of the AL-FEC coding scheme configuration, respectively of the AL-FEC mapping, the AL-FEC codec, the AL- FEC redundancy level, the support for the active discard of redundant AL-FEC PDUs at the RAN]; wherein the change of dynamic policy is based in part on the network assistance information.

[0272] There is further provided a method at an AS, the method comprising: determining an AL-FEC configuration, the AL-FEC configuration being in part dynamically modified by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining the AL-FEC redundancy level; applying the AL-FEC configuration to encode a PDU Set, the PDU Set comprising one or more PDUs; routing the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribing to a network assistance service session at a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapting the AL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and the dynamic AL-FEC controller.

[0273] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0274] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0275] The following abbreviations are relevant in the field addressed by this document: 3GPP, 3rd generation partnership project; 5G, fifth generation; 5GS, 5G System; 5QI, 5G QoS Identifier; AF, application function; AMF, access and mobility function; AR, augmented reality; AS, application server; ASP, application service provider; DL, downlink; NAL, network abstraction layer; PCF, policy control function; PDU, protocol data unit; PPS, picture parameter set; PSA UPF, PDU session anchor UPF; PSI, PDU set importance; QoE, quality of experience; QoS, quality of service; RAN, radio access network; RTCP, real-time control protocol; RTP, real-time protocol; SDU, service data unit; SMF, session management function; SRTCP, secure real-time control protocol; SRTP, secure real-time protocol; UE, user equipment; UL, uplink; UPF, user plane function; VCL, video coding layer; VPS, video parameter set; VR , virtual reality; XR, extended reality; XR AS, XR application server; and XRM, XR media.

Claims

CLAIMSWhat is claimed is:

1. A network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network function to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL- FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow for the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; and expose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

2. The network function of claim 1, wherein the set of provisioning configurations originate at an Application Service Provider (ASP).

3. The network function of claim 1 or 2, wherein the set of provisioning configurations comprises at least one of: service access information; content delivery protocols information related to a type of one or more media types of a service and preferred delivery protocols; and / orpolicy template information, wherein policy templates comprise QoS application requirements.

4. The network function of claim 3, whereby the at least one processor is further configured to cause the network function to determine dynamic policy based on the policy template information, the dynamic policy further comprising for each service data flow descriptor and each media component of the AS session at least one of a desired maximum / minimum bit rate, desired maximum / minimum delay budget, desired packet loss, Protocol Data Unit (PDU) Set marking information, and / or AL-FEC coding scheme information.

5. The network function of claim 4, wherein the dynamic policy comprises a set of AL-FEC coding scheme configurations applicable by the AS for the AS session, wherein each of the AL-FEC coding scheme configurations comprises at least one of: an AL-FEC mapping identifier; an AL-FEC codec configuration; an AL-FEC redundancy level; a content ratio / redundancy ratio level; a Boolean information element for marking Maximum Distance Separability corresponding to the AL-FEC codec configuration; and an information element indicating whether active discarding of redundant AL-FEC PDUs at a Radio Access Network (RAN) is one of supported or not supported.

6. The network function of claim 5, wherein the AL-FEC information element within the QoS request configuration for the AS session comprises one of the AL-FEC coding scheme configurations of the dynamic policy.

7. The network function of any claim 1 to 6, wherein the second network function is one of: a Policy Control Function (PCF); and a Network Exposure Function (NEF).

8. The network function of any claim 1 to 7, wherein the consumer function is one of a Media Session Handler (MSH); and the AS of the AS Session.

9. The network function of any claim 1 to 8, wherein the network assistance information corresponds to a network bit rate recommendation.

10. The network function of any claims 8 or 9, wherein the generation of the QoS request configuration by the at least one processor is triggered dynamically by an indication of a change of the dynamic policy originating over the dynamic policy service from one of: the Media Session Handler (MSH); and the AS, the AS determining dynamically at least the modification of the AL-FEC information element, wherein the change of dynamic policy is based in part on the network assistance information.

11. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: apply a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generate a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving AL-FEC encoded data, the QoS request configuration comprising an Application Layer Forward Error Correction (AL-FEC) information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; request, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribe to the second network function for a set of one or more network events corresponding to the QoS flow; andexpose a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

12. A method performed by a network function, the method comprising: applying a provisioning configuration, the provisioning configuration being a member of a set of provisioning configurations; generating a Quality of Service (QoS) request configuration for an Application Server (AS) session, the AS session for serving Application Layer Forward Error Correction (AL-FEC) encoded data, the QoS request configuration comprising an AL-FEC information element for the AS session, the AL-FEC information element based on the applied provisioning configuration and a dynamic policy; requesting, from a second network function, a QoS flow comprising the AS session based on the QoS request configuration; subscribing to the second network function for a set of one or more network events corresponding to the QoS flow; and exposing a network assistance service and a dynamic policy service to a consumer function, the network assistance service providing network assistance information of the QoS flow.

13. The method of claim 12, wherein the set of provisioning configurations originate at an Application Service Provider (ASP).

14. The method of claim 12 or 13, whereby the set of provisioning configurations comprises at least one of: service access information; content delivery protocols information related to the type of one or more media types of a service and preferred delivery protocols; and / or policy template information, wherein policy templates comprise QoS application requirements.

15. The method of claim 14, whereby the dynamic policy is determined based on the policy template information, the dynamic policy further comprising for each service data flow descriptor and each media component of the AS session at least one of a desired maximum / minimum bit rate, desired maximum / minimum delay budget, desired packet loss, Protocol Data Unit (PDU) Set marking information, and / or AL-FEC coding scheme information.

16. The method of claim 15, wherein the dynamic policy comprises a set of AL-FEC coding schemes configurations applicable by the AS for the AS session, wherein each of the AL-FEC coding schemes configuration comprises at least one of: an AL-FEC mapping identifier; an AL-FEC codec configuration; an AL-FEC redundancy level; a content ratio / redundancy ratio level; a Boolean information element for marking Maximum Distance Separability corresponding to the AL-FEC codec configuration; and an information element indicating whether active discarding of redundant AL-FEC PDUs at the Radio Access Network (RAN) is one of supported or not supported.

17. The method of claim 16, wherein the AL-FEC information element within the QoS request configuration for the AS session comprises one of the AL-FEC coding scheme configurations of the dynamic policy.

18. The method of any claim 12 to 17, wherein the second network function is one of a Policy Control Function (PCF); and a Network Exposure Function (NEF).

19. The method of any claim 12 to 18, wherein the consumer function is one of a Media Session Handler (MSH); and the AS of the AS Session.

20. An Application Server (AS) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the AS to: determine an AL-FEC configuration, the AL-FEC configuration defined by a dynamic AL-FEC controller, the dynamic AL-FEC controller determining at least an AL- FEC redundancy level; encode a PDU Set, the PDU Set comprising one or more PDUs, the encoding performed according to the AL-FEC configuration; route the AL-FEC encoded PDU Set to a network function configured to map the PDU Set to a QoS flow; subscribe to a network assistance service session provided by a second network function, the network assistance service session providing network assistance information related to the QoS flow changes; and adapt the AL-FEC configuration, the adaption based at least in part on the network assistance information indicating QoS flow changes and identifying the dynamic AL-FEC controller.

Citation Information

Patent Citations

  • Combination therapies for treating cancer

    US62634789P0

  • 5g support for webrtc

    US20230362214A1

  • GR20220100751A

  • GR20240100017A

  • US63428026P

Cited By

  • Downlink data processing method and device, equipment and storage medium

    CN121814874A

  • Downlink data processing method and device, equipment and storage medium

    CN121814874B