Protocol data unit set signalling with application layer forward error correction in a wireless communication network

By applying AL-FEC configuration to PDU Sets and marking PDU headers, the wireless communication network effectively addresses the challenges of packet loss and latency in high-bandwidth applications, ensuring robust and efficient delivery of multimedia content.

WO2024230956A1PCT designated stage expired Publication Date: 2024-11-14LENOVO (SINGAPORE) PTE LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/053751
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-01-11
Filing Date
2024-02-14
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently handling Protocol Data Unit (PDU) Sets with Application Layer Forward Error Correction (AL-FEC) in wireless communication networks, particularly in supporting high-bandwidth, low-latency applications like cloud gaming and virtual reality, where network congestion and packet loss are prevalent.

Method used

The implementation of AL-FEC configuration for generating PDU Sets, marking PDU headers to indicate the applied AL-FEC, and transmitting these sets to support Quality of Service (QoS) flows, enabling better network handling of AL-FEC content during challenging conditions by integrating AL-FEC information into the protocol data units and network headers.

Benefits of technology

This approach enhances the robustness of multimedia content delivery by reducing latency and bandwidth usage, improving network resilience against packet loss and congestion, and optimizing resource allocation in wireless communication networks for immersive media applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024053751_14112024_PF_FP_ABST
    Figure EP2024053751_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.
Need to check novelty before this filing date? Find Prior Art

Description

PROTOCOL DATA UNIT SET SIGNALLING WITH APPLICATION LAYER FORWARD ERROR CORRECTION IN A WIRELESS COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of implementing Protocol Data Unit (PDU) Set Signalling with Application Layer Forward Error Correction (AL-FEC) in a wireless communication network. In particular, this document defines an Application Server (AS), a User Equipment (UE), a processor, and a method performed by a device for wireless communication.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 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 least one,” “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 prefacedby 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] Accordingly, there is provided herein an 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one PDU Set based at least in part on coding at least one ADU of the ADUs by applying an AL-FEC configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

[0005] There is further provided a 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: receive ADUs of a multimedia application; generate at least one PDU Set based at least in part on coding at least one ADU of the ADUs by applying an AL-FEC configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

[0006] 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: receive ADUs of a multimedia application; generate at least one PDU Set based at least in part on coding at least one ADU of the ADUs by applying an AL-FEC configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

[0007] There is further still provided a method performed by a device for wireless communication, the method comprising: receiving ADUs of a multimedia application; generating at least one PDU Set based at least in part on coding at least one ADU of the ADUs by applying an AL-FEC configuration, wherein the PDU Set comprises at least one PDU; marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmitting the PDU Set.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0009] Figure 2 provides an overview of a Real-time Transport Protocol (RTP) and a Real-time Transport Control Protocol (RTCP) stack.

[0010] Figure 3 illustrates an overview of a Web Real-Time Communication (WebRTC) stack.

[0011] Figures 4a and 4b illustrate a packet format and header information for an RTP packet and for an Secure RTP (SRTP) packet respectively.

[0012] Figure 5 illustrates an overview of a core network Extended Reality and Media (XRM) architecture for handling of PDU Sets.

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

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

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

[0016] Figure 9 presents a role of an FEC FRAME (FECFRAME) and application of various FEC coding schemes.

[0017] Figure 10 illustrates an example of a core network XRM architecture implementing an arrangement described herein.

[0018] Figure 11 illustrates a 1-byte RTP header extension for PDU Set and AL-FEC information marking.

[0019] Figure 12 illustrates a 2-byte RTP header extension for PDU Set and AL-FEC information marking.

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

[0021] Figure 14 illustrates an example of a processor 1400 in accordance with aspects of the present disclosure.

[0022] Figure 15 illustrates an example of a NE 1500 in accordance with aspects of the present disclosure.

[0023] Figure 16 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0024] A wireless communications system, including network communication devices (e.g., AS) and user communication devices (e.g., UE) may support grouping of one or more logically related PDUs into a PDU Set. The PDU Set may include content of an ADU. The one or more PDUs of the PDU Set may be handled according to a same set of QoS parameters (e.g., requirements, restrictions), such as a delay budget and error rate, while providing improved support to a radio access network (RAN) for differentiated Quality of Service (QoS handling at a PDU Set level and with application-level content awareness. By enabling the wireless communication system to support handling of these PDUs of the PDU Set according to a same set of QoS parameters, the wireless communication system may improve the granularity of 5G QoS flow framework, allowing the RAN to improve a mapping between QoS flows and DRBs to meet demands of XR media requirements (e.g., high-rate transmissions with short delay budgets).

[0025] Some wireless communication systems may support content delivery of immersive and interactive media, such as in cloud gaming (CG), virtual reality (VR), by applying excessive Forward Error Correction (FEC), or alternatively AL-FEC. By applying FEC or AL-FEC, these wireless communication systems may provide robust multimedia content delivery with reduced latency, enabling applications (e.g., CG, VR, and the like) with high bandwidth usage by avoiding higher layer retransmissions and combating network losses.

[0026] Various aspects of the present disclosure relate to enabling one or more of a network communication device (e.g., AS) or a user communication device (e.g., a UE) to output (e.g., transmit) or obtain (e.g., receive) a configuration and signal (e.g., inform, indicate) to a network for support of QoS flows with integrated PDU Set handling and AL- FEC. For example, the configuration may include AL-FEC information and information elements (IES) that extend the PDU Set handling to include dynamic information of AL- FEC encoder added redundant information and provision to the network (e.g., a 5GS) to better handle AL-FEC content in case of challenging network conditions (e.g., network congestion events, network flow capacity outage, and the like).

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

[0028] 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 supportradio 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.

[0029] 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 RAN, a NodeB, an eNodeB (eNB), a nextgeneration 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.

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

[0031] 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 Intemet-of-Everything (loE) device, or Machine-Type Communication (MTC) device, among other examples.

[0032] 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 Vehi cl e-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.

[0033] 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).

[0034] 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 or interconnects 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.

[0035] 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 datanetwork 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 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).

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

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

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

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

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

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

[0042] The wireless communication system 100 may support various applications and services, in which multimedia flows are multiplexed under a single network application session (e.g., a 5-tuple containing a source Internet Protocol (IP) address, a destination IP address, a source network port, a destination network port, and a protocol number as identifier) relating to XR. Aspects of these applications and services are defined in 3 GPP 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 include 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.

[0043] It should be noted that while some examples described herein refer to XR- related services and applications, it should be readily apparent that the aspects of the present disclosure are more generally applicable and may be employed in various other types of services and applications, including transport and network protocols stacks (e.g.,Quick User Datagram Protocol Internet Connection (QUIC), WebRTC, WebTransport). Additionally, XR may include one or more different types of realities, such as VR, Augmented Reality (AR), and Mixed Reality (MR) are examples.

[0044] VR relates to 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. VR 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 might be necessary to allow the simulated visual and audio components to be updated to ensure that, from the user’s perspective, objects 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.

[0045] AR relates to a user being provided with additional information or artificially generated items (e.g., objects), or content overlaid on their current environment. Such additional information or content may 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. MR relates to an advanced form of AR, in which 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.

[0046] XR refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes representative forms 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 cases, 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).

[0047] XR video traffic may be composed of multiple downlink (DL) and / or uplink (UL) video streams of high resolution (e.g., 1080p dual-eye buffer usually), frames-per- second (e.g., 60+ fps), and high bandwidth (e.g., 20-30 Mbps), which need to be transmitted across a network with minimal delay (e.g., within 10-15 ms) to maintain a reduced end-to-end application round-trip interaction delay and enable digital world immersion. These delay-critical requirements are critical 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.).

[0048] To support these 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. 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 5GS, and the like. RTP is a media codec agnostic network protocol with application-layer framing used for delivery of multimedia (e.g., audio, video etc.) in realtime over IP networks. It is used in conjunction with an associated 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.

[0049] Figure 2 provides an overview of an RTP stack and an RTCP stack. An IP layer 205 carries signalling from a data plane 210 and a control plane 250. The data plane 210 stack may include one or more functions for a User Datagram Protocol (UDP) 212, an RTP 216, an RTCP 214, one or more Media Codecs 220, and a Quality Control 222. The control plane 250 stack may include one or more functions for a UDP 252, a Transmission Control Protocol (TCP) 254, a Session Initiation Protocol (SIP) 262, and a Session Description Protocol (SDP) 264.

[0050] SRTP is a secured version of RTP and may provide encryption (e.g., payload confidentiality), message authentication and integrity (e.g., header and payload signing), and / or replay attack protection. An SRTP associated protocol, SRTCP may support the same functionalities as the RTCP. As such, in SRTP, RTP header information may still beaccessible but unmodifiable, whereas a payload is encrypted. SRTP may be used for this reason in the WebRTC stack, which ensures secure RTC multimedia communications over web browser interfaces.

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

[0052] As illustrated in Figure 3, an IP layer 305 carries signalling from the data plane 310 and the control plane 350. The data plane stack 310 comprises functions for 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 data plane 728 is mainly dedicated as an application data channel and may be non-time critical. The SRTP based stack 317 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 TCP 354, Transport Layer Security (TLS) 356, Hypertext Transfer Protocol (HTTP) 358, WebSocket 366, SIP 362, SDP 364, Server- sent Events (SSE) 368 and Extensible Messaging and Presence Protocol (XMPP) 370.

[0053] 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 headerinformation, and an additional header information about Contributing Source (CSRC) identifiers of the media flow and optional RTP extension headers.

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

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

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

[0057] “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.

[0058] “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)).

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

[0060] “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.)

[0061] “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.)

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

[0063] “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.

[0064] “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.

[0065] “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.

[0066] Complete Header Information (incl. header extensions) comprises “RTP header extension” 448, 478.

[0067] “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 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.

[0068] 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).

[0069] 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 SIP.

[0070] The XR Media (XRM) feature in 3GPP Release 18 at the 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 morePDUs 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.

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

[0072] 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).

[0073] 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, a Session 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 willnow be described in the example of downlink traffic, a similar process may operate for uplink traffic.

[0074] At 580, the XRM AF 510 determines PDU Set requirements.

[0075] At 581, the XRM Application Function 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.

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

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

[0078] 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 3GPP 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 as described 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 RTPpackets. 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.

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

[0080] 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 mechanisms associated with the UL UE-to-RAN information passing are up to the specification and implementations of RAN signalling procedures.

[0081] However, in XRM Release 18, e.g. 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 Sets and determines for each PDU Set the PDU Set information below sent over to the NG-RAN in the GTP-U header.

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

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

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

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

[0086] 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 [Ref-6] 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).

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

[0088] The AS PDU Set information listed above is provided in some embodiments via a one-byte RTP Header Extension for the marking of PDU Sets, US provisional application 63 / 428,026 titled “PDU Set-Aware Multimedia Applications and Associated Signaling” by Stoica et al., Applicant’s reference SMM920220198-US-PSP, and End of Bursts as defined by 3GPP Technical Specification TS 26.522 vO.1.1 (Sep 2023), titled “5G Real-time Media Transport Protocol Configurations” and illustrated in Figure 6 above.

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

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

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

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

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

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

[0095] 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 0 and the lowest importance PDU Set of 15.

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

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

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

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

[0100] The above example relates 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.

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

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

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

[0104] 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 forlow importance PDU Sets 810 in both CN and RAN implementations but requires lower overhead and control within the 5GS QoS framework.

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

[0106] In various interactive XR applications 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).

[0107] 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).

[0108] Figure 9 presents the role of FECFRAME and application of various FEC coding schemes. Figure 9 provides an illustration of an AL-FEC XR application flow 900 including encoding, packetization and transport. The process 900 is performed by an application 910, a FECFRAME 920 AL-FEC generation block, a Transport Layer 930, and a FEC Scheme 940. The Transport later 930 may use the UDP.

[0109] 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 FECFRAMERaptor / RaptorQ encodes RTP packets as per RFC 6881 and RFC 6882. The FEC Scheme 940 may comprise Raptor, or RaptorQ. The process 900 comprises the following steps.

[0110] At 971, a sender 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 the corresponding repair packets, whereby the transmission point is considered to be downstream interface ingesting encoded PDUs post-encoding)).[OHl] At 972, the sender arranges the source packets (e.g., the RTP source packets) into a set of same-sized source symbols (that may represent smaller partitions into source symbols of configured size of source packets data).

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

[0113] At 974, 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 to a receiver.

[0114] Under FECFRAME requirements (i.e., RFC 6363), the sender shall 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.

[0115] At 975, the receiver receives source and repair packets.

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

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

[0118] 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 source packets 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.

[0119] 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 packetgenerated 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.

[0120] 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 RFC 6330 RTP Frame Marking RTP Header Extension (Nov 2021) - draft-ietf-avtext-fram emarking- 13, 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 the above FEC configuration only serves as one reference, it may be considered as a typical implementation.

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

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

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

[0124] If the RAN is PDU Set- 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 to meet QoS requirements of a DRB. For instance, in case of congestion, the RAN may drop some PDUs up to at most N-K PDUs of a PDU Set without comprising some of the repair, or alternatively redundant, PDUs of the PDU Set. 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 encoded PDUs, wherein K represents the number of source PDUs and N-K represents the number of repair / redundant PDUs. These RAN policies and associated signalling and procedures are described within Greek Patent Application Number 20220100751.

[0125] The radio layers require awareness of the instantaneous coding overhead on a per PDU Set basis in order to be able to perform radio level optimizations in terms of resource allocation, as described in Greek Patent Application Number 20220100751, e.g., discarding unnecessary PDUs of an AL-FEC encoded PDU Set, dropping AL-FEC encodedPDU Sets in case of congestion or when the ADU cannot be recovered etc. The UPF may signal (i.e., in DL direction) this information to the RAN over the GTP-U headers, or alternatively, the UE may identify and determine PDU Set information (i.e., in UL direction) on the traffic ingress at the access stratum, as described in Greek Patent Application Number 20220100750 to Stoica et al., [Applicants ref: SMM920220118-GR- NP] titled “Signalling PDU Sets with Application Layer Forward Error Correction in a Wireless Communication Network”. Yet relying on the UPF, or alternatively UE, to determine PDU Sets based only on UPF / UE implementation may lead to complex and inefficient UPF / UE processing with a lot of overhead requirements in configuration necessary to enable the UPF-specific and UE-specific PDU Set identification.

[0126] The solutions proposed herein use the AL-FEC information source, i.e., the multimedia sender, or alternatively the RTP sender / AL-FEC encoder, to provide the RAN with necessary AL-FEC information to enable RAN optimalizations with effective processing. Such solutions may be implemented with low complexity of UPF and UE nodes. The solutions presented herein have the added benefit that the AL-FEC decoder is placed at the application level, and as long as the AL-FEC coding scheme is MDS (e.g., Reed-Solomon codes), or has asymptotically MDS characteristics (e.g., Raptor / RaptorQ codes, Random Linear Network Codes (RLNC) families with at least 2A8 alphabets), the RAN and core network only require information about the PDU Set boundaries and the redundancy levels of the PDU Set to operate effectively, as described in Greek Patent Application Number 20220100751. This MDS assumption simplifies therefore the necessary configuration for AL-FEC efficient support over the 5GS and is practically furthermore common to widespread erasure error correction coding schemes typical of AL- FEC (e.g., Reed-Solomon, Raptor / RaptorQ, and latest some RLNC codes). In addition to the multimedia sender marking the PDU Set with PDU Set and AL-FEC information related to the AL-FEC encoded PDU Set content, the 5GS network may be enabled with support of the AL-FEC feature, which may be performed by a simple configuration option (e.g., at least a flag marking AL-FEC enablement) embedded as part of the protocol description associated with the user plane content distribution protocol used by the multimedia sender (e.g., RTP / SRTP, WebRTC).

[0127] Figure 10 illustrates an example of a core network XRM architecture implementing an arrangement described herein. Figure 10 shows a DL implementation of a general proposed solution for a QoS flow with AS marking PDU Sets with PDU Set information and AL-FEC within the content distribution protocol headers and UPF relaying the information to the gNB across the 5GS over GTP-U headers as configured by the SMF given the AL-FEC information element of the protocol description associated with the QoS flow. The protocol description may be configured by request of the application logic (e.g., at the UE) to the Media Session Handler Dynamic Policies APIs.

[0128] The high-level illustration of the solution shown in Figure 10 is illustrated with reference to DL traffic, i.e., from the AS to the UE. It should be apparent to the skilled reader that the the PDU Set identification approach from the UPF (i.e., the PDU Set module highlighted in Figure 10) may be applied to the UE, wherein the UE to gNB communication does not directly indicate PDU Set and / or AL-FEC information (as for instance the GTP-U tunnel does over N3 interface between UPF and gNB), but instead relies on UE Delay Status Report (DSR) / Buffer Status Report (BSR) reporting procedures to notify the gNB on the delay / buffer status associated with PDU Sets of a DRB, or alternatively a QoS flow, and respectively, regarding UE discard procedures for AL-FEC utilizing the identified redundancy level per PDU Set to discard PDUs for efficient radio resource utilization, e.g., as per PDU discarding solutions described within Greek Patent Application Number 20220100751. In the DL direction, the gNB may determine (e.g., similarly as the UE) based on implementation the discard policies associated with a QoS flow and its QoS requirements.

[0129] Figure 10 shows a system 1000 comprising an Extended Reality Media Application Function (XRM AF) 1010, a Policy and Control Function (PCF) 1015, a Session Management Function (SMF) 1020, an Access and Mobility Function (AMF) 1025, a Radio Access Network (RAN 1030, a User Equipment (UE) 1035, a User Plane Function (UPF) 1040, and an Extended Reality Application 1045.

[0130] In system 1000, AL-FEC encoded data associated with I-frames of video content are shown with a striped pattern, data associated with P-frames of video content are shown with a hash pattern, and data associated with B-frames of video content are shownwith a dotted pattern. The operation of system 1000 will now be described in the example of downlink traffic, a similar process may operate for uplink traffic.

[0131] At 1070: An AF (e.g., an XR AF 1010 as illustrated in Figure 10) requests the network via PCF / NEF N5 / N33 interfaces and associated APIs for a AS Session with QoS requirements. The QoS requirements may be mapped to a specific 5 tuple / IP flow (i.e., consisting of source / destination IP address, source / destination port and protocol) and may include application specific requirements for delay budget and rate allocation. The AF request may further include information comprising information elements, e.g., a protocol description, related to the PDU Set marking configuration and the AL-FEC configuration applied by corresponding AS (e.g., an XR video application AS with AL-FEC enabled as for instance depicted in Figure 10). The AF indication that the session may contain AL- FEC encoded PDU Sets may include information of the AL-FEC coding configuration used.

[0132] At 1071 : The PCF 1015 determines QoS rules given the AF request for an AS QoS session and the corresponding configuration. The PCF 1015 may determine if the UPF 1040 needs to detect PDU Set size change above a certain threshold. The threshold may be configurable based on operator preference. The QoS rules may include PCC rules and are based in part on the requested QoS session parameters, and / or operator configuration to accommodate the PSDB / PSER requirements of the application. The PCC rules include and provide information, e.g., the protocol description, about the protocol used, PDU Set marking and AL-FEC enabled configurations and are signalled to the SMF. The PCC rules may comprise PSDB, PSER and PSIHI requirements, and AL-FEC awareness and support.

[0133] At 1072: The SMF 1020 establishes the QoS flow according to the QoS rules provided by the PCF 1015.

[0134] At 1072a.: The SMF 1020 further configures the UPF 1040 to route packets of the XR application to the established QoS flow, and, in addition, to enable PDU Set handling with AL-FEC support based on AS marked PDU Set and AL-FEC information. The N4 rules may define, for example, how to detect PDU Set and AL-FEC dynamic information.

[0135] At 1072b.: The SMF 1020 also provides the QoS profile containing PDU Set QoS requirements to the RAN 1030 via the AMF 1025, indicating to the latter also that the source will provide AL-FEC encoded PDU Sets. The QoS profile may indicate that the AL-FEC feature is enabled.

[0136] At 1073: The AMF 1025 signals the radio layers with the QoS profiles of the SMF necessary to satisfy the application QoS requirements. The AMF 1025 indicates in addition that the source corresponding to the QoS flow applies AL-FEC encoding. In step 1073a this is indicated to the RAN 1030, e.g., a gNB, to allow the RAN to perform radio resource optimizations with AL-FEC awareness, e.g., based on indications of GTP-U header fields including AL-FEC information for the PDU Sets of the QoS flow. The AMF 1025 may signal to the RAN 1030 using an N2 SM container. The AMF 1025 may signal QoS profile w / PDSB Requirements, and that AL-FEC is enabled. In step 3b the AMF 1025 indicates in addition that the source corresponding to the QoS flow applies AL-FEC encoding additionally to the UE 1035. For UL QoS flows, the UE 1035 may use this information to determine its transmission behaviour relative to AL-FEC encoded PDU Sets in its buffer, and more specifically, determine any discarding, and / or prioritization mechanisms related to AL-FEC UL transmissions. The AMF 1025 may signal to the UE 1035 using an N1 SM container. The AMF 1025 may signal QoS profile w / PDSB Requirements, and that AL-FEC is enabled.

[0137] At 1074: The AS 1045 (e.g., an XR video AS depicted in Figure 10) delivers encoded content to the UPF 1040 on the IP flow configured by the AF request to the network. The service data flow content corresponds to AL-FEC encoded PDU Sets. The AS additionally marks the PDU Sets with information about each PDU Set and its corresponding AL-FEC encoding in the header information fields of the transport protocol, e.g., within RTP header extensions for PDU Set marking including an additional AL-FEC encoding information element.

[0138] At 1075: The UPF 1040 applies the SMF 1020 signalled protocol description including the information about PDU Set and AL-FEC information marking by the AS. The UPF 1040 extracts the AL-FEC information per PDU Set (e.g., number of repair / redundant PDUs out a total number of PDUs of a PDU Set, quota of repair / redundant PDUs out ofnumber of PDUs of a PDU Set, number of PDUs from a PDU Set that can be dropped without loss of the corresponding ADU etc.) and marks it together with other PDU Set information (e.g., PDU Set end marker, PDU Set Sequence Number, PDU Sequence Number, PDU Set Size, PDU Set Importance) in the GTP-U tunnel header information of the corresponding PDUs of each PDU Set. The PDU Sets of the QoS flow are routed over N3 / GTP-U tunnel to the RAN 1030.

[0139] At 1076: The RAN 1030 processes the GTP-U header information about PDU Sets and AL-FEC and applies the determined PDU Set and AL-FEC information per PDU Set of the QoS flow. The AL-FEC information is used by the RAN 1030 to perform optimized radio resource allocation with AL-FEC awareness (e.g., PDU / PDU Set discarding behaviour). Accordingly, AL-FEC support is enabled, and the RAN 1030 applies RAN discard / retransmission policies when needed (e.g., congestion, link loss conditions) with dynamic AL-FEC awareness.

[0140] The protocol description may be configured based on the requirements of the application for a QoS flow with integrated PDU Set handling. The application, either at the UE, or alternatively at the Application Service Provider (ASP) domain, sends a request to an AF for a dynamic policy for a QoS flow with PDU Set and AL-FEC enabled. In one implementation, the UE (e.g., a mobile terminal, a XR HMD etc.) performs the configuration by means of a Media Session Handler (MSH). The MSH provides an API to the UE, or alternatively the multimedia application residing on the UE, for requesting a dynamic policy for its service data flow, or alternatively QoS flow, including PDU Set feature and the AL-FEC enabled. The MSH posts the dynamic policy request from the application to a corresponding AF (e.g., over the M5_DynamicPolicies API, or alternatively RTC-5 equivalent API). In another implementation, the Application Service Provider, may provision the AF (e.g., via MI PolicyTemplatesProvisioning API, or alternatively RTC-1 equivalent API) with a set of dynamic policy templates including QoS requirements comprising further configurations for PDU Set feature and AL-FEC support enablement. The dynamic policies from the MSH may be selected at the AF based on the set of provisioned dynamic policies for the application by the ASP.

[0141] The information element comprising the AL-FEC configuration information (e.g., AL-FEC redundancy level) and the PDU Set marking configuration information may be common and may comprise both PDU Set and AL-FEC information elements. The PDU Set and AL-FEC marking information may be comprised within the same resource and object. The PDU Set and AL-FEC marking information may be comprised within the same resource and object. For example, the resource may be a DynamicPolicy resource, and the object may be a QoSSpecification, or alternatively a RTCQoSSpecification. In another example, the configuration object may be a PDUSetMarking object. The PDUSetMarking may be part of the QoSSpecification (o RTCQoSSpecification object), as part of the DynamicPolicy resource. One example data model for the PDUSetMarking configuration object is represented in table 1 below. Table 1 shows a PDUSetMarking extended data model for PDU Set marking and AL-FEC configuration including an information element for determining the state and presence of AL-FEC information in the PDU Set marking header originating at a multimedia sender (e.g., RTP sender with AL-FEC capability enabled / disabled).Table 1: PDUSetMarking extended data model for AL-FEC configuration

[0142] The AL-FEC redundancy information field, e.g., appLayerFec Active, indicates that the PDU Set marking in the RTP header extension comprises information regarding the AL-FEC redundancy level of the PDU Set PDUs.

[0143] The information element comprising the AL-FEC configuration information (e.g., AL-FEC coding scheme configuration, AL-FEC media type) may be additionally comprised as one or more standalone elements in the DynamicPolicy data model. For example, where the FEC coding scheme is registered with IANA as a valid RTP payload type (e.g., flexfec coding scheme, Raptor / RaptorQ coding scheme), the media identifier type of the DynamicPolicy resource may be assigned the IANA registered payload type, (e.g., as video / flexfec, audio / flexfec, application / flexfec, text / flexfec, video / raptorfec,audio / raptorfec, application / raptorfec, text / raptorfec etc.). In another example, the FEC coding scheme may be identified by means of a FEC Encoding ID, or a combination of a FEC Encoding ID and a FEC Instance ID as one of a fully specified coding scheme (i.e., an encoding scheme formally specified such that independent implementors can implement both encoder and decoder from an IETF RFC specification), under-specified coding scheme (a coding scheme such that a IETF RFC specification is not available, or for which a party exists that owns the encoding scheme and is not willing to disclose the codec algorithm / specification), or a coding scheme belonging to a IANA, or alternatively, standardized (e.g., by 3GPP, IETF etc.) encoding registry (e.g., IANA’ S FECFRAME registry for encoding IDs), as categorized by IETF.

[0144] By way of a further example, the FEC coding redundancy of the AL-FEC may be further described as one of ‘dynamic’ and ‘static’. The dynamic quantifier marks a coding redundancy level that may modify dynamically from PDU Set to PDU Set as decided by the AL-FEC encoder, i.e., the multimedia source application. The static quantifier marks a coding redundancy level that may not modify dynamically and is static, e.g., 30% redundant PDUs for each PDU Set, or alternatively a fixed number (e.g., 2) redundant PDUs for each PDU Set, for all PDU Sets of the QoS flow. In case of a static redundancy level type, the policy request for an AS QoS session may further include the static redundancy level. This may be either a fixed redundancy quota, or alternatively a fixed number of redundant / repair PDUs per PDU Set. For instance, an example of a standalone AL-FEC configuration information element comprised in the DynamicPolicy data model is listed below in Table 2. Table 2 shows a configuration data model example for the AL-FEC configuration information including information elements identifying the AL-FEC encoding scheme, AL-FEC redundancy level type, and respectively AL-FEC static redundancy level, if applicable.Table 2: A configuration data model for the AL-FEC configuration information

[0145] The AS (which may be a multimedia RTP sender) may include an AL-FEC encoder. The AS sender may then determine ADUs corresponding to the multimedia data flows of the application and perform packetization towards transport over a network. The resulting PDUs correspond to the same ADU are further encoded based on an AL-FEC configuration and grouped in a PDU Set. Thus, the PDU Set comprises all PDUs carrying data for one ADU. The AS may further mark the output encoded PDU Set with PDU Set and AL-FEC information. The AL-FEC information may comprise an AL-FEC redundancy level information element. The information element may be:• An information element indicating the number of PDUs out of the encoded PDU Set that may be discarded over the communication links (e.g., by the RAN, or alternatively, by the UE) without dropping the original ADU information content; generally, this is equal for an MDS coding scheme (e.g., Reed-Solomon, Raptor / RaptorQ etc.) to the number of added redundant / repair PDUs;• An information element indicating the number of redundant / repair PDUs and a total number of PDUs of an encoded PDU Set with AL-FEC; and / or• An information element indicating the quota of redundant / repair PDUs out of a total number of PDUs of an encoded PDU Set with AL-FEC.

[0146] Furthermore, the AL-FEC redundancy level information element may be comprised within the RTP header extension for PDU Set marking. The AL-FEC redundancy level may be added as an optional field expanding the existing um:3gpp:pdu- set-marking:rel-18 RTP header extension in both its one-byte and two-byte formats. For example, the RTP header extension may additionally include a byte field called AL-FEC Redundancy Level (AFRL). The AFRL may be formed of 8 bits and comprise the number of redundant / repair PDUs added (i.e., the number of PDUs that may be lost from the PDU Set in case of MDS codes without loss of the PDU Set payload) by the AL-FEC encoder at a multimedia source to an AL-FEC encoded PDU Set. In an example where a PDU Set is comprised of 28 encoded PDUs each containing a payload of 1200 Bytes, the AFRL may indicate 6 redundant / repair PDUs. The rest of the 22 PDUs being source PDUs corresponding to the unencoded ADU associated with the PDU Set. Examples of the AFRL field are provided with reference to the one-byte and two-byte formats of the urn:3gpp:pdu- set-marking:rel-18 RTP header extension in Figures 11 and 12. In other implementations of the AFRL field, the AFRL field may comprise of another number of bits (e.g., 4-bits, 16- bits, 24-bits, 32-bits etc.).

[0147] Figure 11 illustrates a 1-byte RTP header extension 1100 for PDU Set and AL- FEC information marking including optional additional field AL-FEC Redundancy Level (AFRL, 1111). In this example the AFRL is an 8-bit field capturing the number of redundant PDUs of an AL-FEC that may be dropped out of a PDU Set without losing thecorresponding PDU Set payload / ADU information. The semantics associated with the PDU Set information fields of the RTP header extension syntaxes outlined in Figure 11 correspond to those described above with reference to figure 6.

[0148] Figure 12 illustrates a 2-byte RTP header extension 1200 for PDU Set and AL- FEC information marking including optional additional field AL-FEC Redundancy Level (AFRL, 1211). In this example the AFRL is an 8-bit field capturing the number of redundant PDUs of an AL-FEC that may be dropped out of a PDU Set without losing the corresponding PDU Set payload / ADU information. The semantics associated with the PDU Set information fields of the RTP header extension syntaxes outlined in Figure 12 correspond to those described above with reference to Figure 6 and Figure 7.

[0149] The presence of the AFRL field in the PDU Set marking RTP header extension may indicate that AL-FEC may have been used for the PDU Set. An AFRL set to 0 may indicate that the PDU Set does not contain any redundant / repair PDUs. This may signify that the PDU Set is uncoded and no AL-FEC has been used. Further, an AFRL may vary from PDU Set to PDU Set as per the AL-FEC dynamic encoding of PDU Sets.

[0150] The AFRL presence of the AFRL field in the PDU Set marking RTP header extension may be indicated by means of an SDP offer / answer procedure. An SDP offerer (e.g., a RTP sender / a RTP peer) may indicate an SDP offer to an SDP answerer (e.g., a RTP receiver / another RTP peer). The SDP offer may include signalling indicating that the AFRL has been added to the fixed PDU Set marking RTP header extensions, and the SDP may further include a set of AL-FEC encoding configurations. The SDP answerer repeats the offer parameters including the acceptable AL-FEC encoding and AFRL field configuration. For example, in case the SDP answerer supports the AFRL field and one AL-FEC encoding configuration, the SDP answerer will repeat and indicate these to the SDP offerer. The presence of the AFRL field in the PDU Set marking RTP header extension may be indicated by means of an extension attribute optional property. The following is an example implementation of ABNF syntax of a possible realization of the latter, with the AFRL extension attributes property al-fec-redundancy-level indicating the presence of the AFRL field.a=extmap:" 1*5DIGIT [" / " direction] SP extensionname SP extensionattributes extensionname = "urn:3gpp:pdu-set-marking:rel-18" extensionattributes = [format SP] "pdu-set-size" [SP] “num-of-pdus” [SP] “al-fec- redundancy -1 evel” format = "short" / "long"

[0151] According to one example, when the PDU Set and AL-FEC (e.g., based on an MDS coding scheme such as Reed-Solomon, Raptor / RaptorQ etc.) are enabled for a QoS flow and the multimedia source marks each PDU Set with PDU Set information and AL- FEC information, the AL-FEC dynamic information per PDU Set may help the radio layers determine optimized radio resource allocation and discard behaviour given the QoS parameters of the QoS flow (e.g., PSDB / PSER, PSIHI). For example, when the PDU Set Integrated Handling Indicator (PSIHI) is enabled for the QoS flow, the RAN scheduler may determine by implementation that it cannot send within the available PSDB the entire PDU Set. For instance, the RAN may decide to discard the PDUs that cannot be successfully scheduled within the PSDB duration. If the discarded PDUs exceed the number of redundant PDUs marked for the PDU Set then the RAN may decide to drop the entire PDU Set. However, if the discarded PDUs are less than or equal to the number of PDUs marked for the PDU Set then the RAN may decide to not drop the entire PDU Set, and transmit the remainder PDUs.

[0152] Figure 13 illustrates an example of a UE 1300 in accordance with aspects of the present disclosure. The UE 1300 may include a processor 1302, a memory 1304, a controller 1306, and a transceiver 1308. The processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, 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.

[0153] The processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, 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.

[0154] The processor 1302 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 1302 may be configured to operate the memory 1304. In some other implementations, the memory 1304 may be integrated into the processor 1302. The processor 1302 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the UE 1300 to perform various functions of the present disclosure.

[0155] The memory 1304 may include volatile or non-volatile memory. The memory 1304 may store computer-readable, computer-executable code including instructions when executed by the processor 1302 cause the UE 1300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1304 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.

[0156] In some implementations, the processor 1302 and the memory 1304 coupled with the processor 1302 may be configured to cause the UE 1300 to perform one or more of the functions described herein (e.g., executing, by the processor 1302, instructions stored in the memory 1304). For example, the processor 1302 may support wireless communication at the UE 1300 in accordance with examples as disclosed herein. The UE 1300 may be configured to support a means for receiving Application Data Units (ADUs) of amultimedia application; generating at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmitting the PDU Set.

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

[0158] In some implementations, the UE 1300 may include at least one transceiver 1308. In some other implementations, the UE 1300 may have more than one transceiver 1308. The transceiver 1308 may represent a wireless transceiver. The transceiver 1308 may include one or more receiver chains 1310, one or more transmitter chains 1312, or a combination thereof.

[0159] A receiver chain 1310 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1310 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1310 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1310 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 1310 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0160] A transmitter chain 1312 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1312 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 amplitudemodulation (QAM). The transmitter chain 1312 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 1312 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0161] Figure 14 illustrates an example of a processor 1400 in accordance with aspects of the present disclosure. The processor 1400 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1400 may include a controller 1402 configured to perform various operations in accordance with examples as described herein. The processor 1400 may optionally include at least one memory 1404, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1400 may optionally include one or more arithmetic-logic units (ALUs) 1406. 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).

[0162] The processor 1400 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 1400) 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).

[0163] The controller 1402 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 1400 to cause the processor 1400 to support various operations in accordance with examples as described herein. For example, the controller 1402 may operate as a control unit of the processor 1400, generating control signals that manage the operation of variouscomponents of the processor 1400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

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

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

[0166] The memory 1404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1400, cause the processor 1400 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 1402 and / or the processor 1400 may be configured to execute computer-readable instructions stored in the memory 1404 to cause the processor 1400 to perform various functions. For example, the processor 1400 and / or the controller 1402 may be coupled with or to the memory 1404, the processor 1400, the controller 1402, and the memory 1404 maybe configured to perform various functions described herein. In some examples, the processor 1400 may include multiple processors and the memory 1404 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.

[0167] The one or more ALUs 1406 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1406 may reside within or on a processor chipset (e.g., the processor 1400). In some other implementations, the one or more ALUs 1406 may reside external to the processor chipset (e.g., the processor 1400). One or more ALUs 1406 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1406 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1406 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 1406 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1406 to handle conditional operations, comparisons, and bitwise operations.

[0168] The processor 1400 may support wireless communication in accordance with examples as disclosed herein. The processor 1400 may be configured to or operable to support a means for receiving Application Data Units (ADUs) of a multimedia application; generating at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmitting the PDU Set.

[0169] Figure 15 illustrates an example of a NE 1500 in accordance with aspects of the present disclosure. The NE 1500 may include a processor 1502, a memory 1504, a controller 1506, and a transceiver 1508. The processor 1502, the memory 1504, the controller 1506, or the transceiver 1508, or various combinations thereof or variouscomponents 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.

[0170] The processor 1502, the memory 1504, the controller 1506, or the transceiver 1508, 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.

[0171] The processor 1502 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 1502 may be configured to operate the memory 1504. In some other implementations, the memory 1504 may be integrated into the processor 1502. The processor 1502 may be configured to execute computer-readable instructions stored in the memory 1504 to cause the NE 1500 to perform various functions of the present disclosure.

[0172] The memory 1504 may include volatile or non-volatile memory. The memory 1504 may store computer-readable, computer-executable code including instructions when executed by the processor 1502 cause the NE 1500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1504 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.

[0173] In some implementations, the processor 1502 and the memory 1504 coupled with the processor 1502 may be configured to cause the NE 1500 to perform one or more of the functions described herein (e.g., executing, by the processor 1502, instructions stored in the memory 1504). For example, the processor 1502 may support wireless communicationat the NE 1500 in accordance with examples as disclosed herein. The NE 1500 may be configured to support a means for receiving Application Data Units (ADUs) of a multimedia application; generating at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmitting the PDU Set.

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

[0175] In some implementations, the NE 1500 may include at least one transceiver 1508. In some other implementations, the NE 1500 may have more than one transceiver 1508. The transceiver 1508 may represent a wireless transceiver. The transceiver 1508 may include one or more receiver chains 1510, one or more transmitter chains 1512, or a combination thereof.

[0176] A receiver chain 1510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1510 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1510 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 1510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0177] A transmitter chain 1512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1512 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 tosupport 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 1512 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 1512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

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

[0179] At 1602, the method may include receiving Application Data Units (ADUs) of a multimedia application. 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 UE as described with reference to Figure 13. In other implementations, aspects of the operations of 1602 may be performed by a NE as described with reference to Figure 15.

[0180] At 1604, the method may include generating at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU. 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 UE as described with reference to Figure 13. In other implementations, aspects of the operations of 1604 may be performed by a NE as described with reference to Figure 15.

[0181] At 1606, the method may include marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set. 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 UE as described with reference to Figure 13. In other implementations, aspects of the operations of 1606 may be performed by a NE as described with reference to Figure 15.

[0182] At 1608, the method may include transmitting the PDU Set. The operations of 1608 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1608 may be performed a UE as described with reference to Figure 13. In other implementations, aspects of the operations of 1608 may be performed by a NE as described with reference to Figure 15.

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

[0184] Accordingly, there is provided herein 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL- FEC configuration for the PDU Set; and transmit the PDU Set.

[0185] Such an arrangement tends to enable AL-FEC support in a wireless communications network for QoS flows and facilitates PDU Set integrated handling. The AL-FEC information and configuration elements allow a wireless communications network to better cope with AL-FEC content in case of challenging wireless network conditions.

[0186] The processor may be further configured to cause the AS to transmit a request for establishment of a Quality of Service (QoS) flow, the QoS flow for a service data flow comprising the AL-FEC encoded PDU Set.

[0187] The request for establishment of a QoS flow may comprise a dynamic policy configuration. The dynamic policy configuration may comprise at least one of: a service data flow information; a set of QoS delay budget and rate requirements; a media type information; a PDU Set marking information; and a subset of the AL-FEC encoding configuration.

[0188] The request for the establishment of a QoS flow may be sent to an Application Function (AF). The AF may be provisioned by an Application Service Provider (ASP) of the multimedia application with one or more policy templates for the dynamic policy configuration. The AF may communicate the request to a second network function. The second network function may comprise a Policy Control Function. The second network function may comprise a Network Exposure Function.

[0189] The request for the establishment of a QoS flow may comprise a dynamic policy configuration, the dynamic policy configuration comprising a subset of the AL-FEC encoding configuration, wherein the subset of the AL-FEC encoding configuration comprises information of at least one of: a Forward Error Correction (FEC) Encoding Identifier (ID) field, the FEC Encoding ID identifying in part the AL-FEC encoding configuration; a FEC Instance Identifier (ID) field, the FEC Instance ID identifying in part the AL-FEC encoding configuration and parameters; a Maximum Distance Separable (MDS) indicator field, the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic; a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern; a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota of number of redundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

[0190] The dynamic policy configuration may comprise a common information element indicating that PDU Set information included within PDU headers include at least AL-FEC information elements.

[0191] The PDU Set information within PDU header may be included within a Realtime Transport Protocol (RTP) extension header element, and wherein the RTP extension header element for PDU Set information comprises at least one of: a field indicating a total number of PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as anumber of redundant PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a ratio of redundant PDUs to total PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a threshold of PDUs that may be lost by a network without the loss of the ADU corresponding to the AL-FEC encoded PDU Set; a field indicating a PDU Set Sequence Number; a field indicating a PDU Sequence Number of a PDU within the PDU Set; a field indicating an end PDU of the PDU Set; a field indicating a PDU Set Importance; and / or a field indicating a PDU Set Size in bytes.

[0192] The presence of the AL-FEC redundancy level field in the RTP header extension element for PDU Set marking may be indicated by an RTP extension attribute by means of SDP offer / answer procedure.

[0193] There is further 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

[0194] The processor may be further configured to cause the UE to transmit a request for establishment of a Quality of Service (QoS) flow, the QoS flow for a service data flow comprising the AL-FEC encoded PDU Set.

[0195] The request for establishment of a QoS flow may comprise a dynamic policy configuration. The dynamic policy configuration may comprise at least one of: a service data flow information; a set of QoS delay budget and rate requirements; a media type information; a PDU Set marking information; and a subset of the AL-FEC encoding configuration.

[0196] The request for the establishment of a QoS flow is sent to a Media Service Handler (MSH). The MSH may be arranged to handle the dynamic policy configuration of the multimedia application. The MSH may communicate the request to a second networkfunction. The second network function may be an Application Function (AF). The AF may be provisioned by an Application Service Provider (ASP) of the multimedia application with one or more policy templates for the dynamic policy configuration. The AF may process the request from the MSH and relay it to a third network function. In such an example, the third network function may comprise a Policy Control Function.Alternatively, in such an example the third network function may comprise a Network Exposure Function.

[0197] The request for the establishment of a QoS flow may comprise a dynamic policy configuration, the dynamic policy configuration comprising a subset of the AL-FEC encoding configuration, wherein the dynamic policy configuration further comprises a common information element indicating that the PDU Set information included within PDU headers includes at least AL-FEC information elements; wherein the subset of the AL-FEC encoding configuration comprises information of at least one of: a Forward Error Correction (FEC) Encoding Identifier (ID) field, the FEC Encoding ID identifying in part the AL-FEC encoding configuration; a FEC Instance Identifier (ID) field, the FEC Instance ID identifying in part the AL-FEC encoding configuration and parameters; a Maximum Distance Separable (MDS) indicator field, the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic; a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern; a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota of number of redundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

[0198] 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADUof the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

[0199] There is further still provided a method performed by a device for wireless communication, the method comprising: receiving Application Data Units (ADUs) of a multimedia application; generating at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmitting the PDU Set.

[0200] The device may be a User Equipment (UE). The device may be an Application Server (AS). The Application Data Units (ADUs) may be referred to as received ADUs. The ADUs may be associated with a multimedia application. The association may comprise the ADUs being generated by or for the multimedia application. The generating may comprise AL-FEC encoding of ADUs with an MDS AL-FEC encoding configuration. In one case, the encoding configuration may comprise a Raptor / RaptorQ, or other Digital Fountain encoding. In another case, the encoding configuration may comprise a Reed- Solomon encoding. In other cases, the encoding configuration may comprise a flexible parity check or other Random Linear Network Coding encodings.

[0201] Typically, one ADU would be encoded into one PDU Set. However, there may be cases when aggregation is applied and multiple ADUs are coded together to a single PDU Set. The multiple ADUs are likely small ADUs, such as video codec parameter sets, SEI messages, and / or video frame / video slice combinations.

[0202] The method may further comprise marking PDU headers with information comprising characteristics of the PDU Set. The PDU Set may be transmitted to a network. The PDU Set may be transmitted to a network device. The network device may comprise a User Plane Function (UPF). The UPF may receive the AL-FEC encoded ADUs and identify their corresponding encoded PDU Sets. The received encoded ADUs may comprise one or more source PDUs and either repair PDUs, or alternatively redundant PDUs. The UPF mayidentify the AL-FEC coding configuration used to encode ADUs and determine the corresponding encoded PDU Sets. The identification of each PDU Set may be based at least in part on the information, or alternatively metadata, associated with the PDU Set. The association may comprise the information as part of the marking of PDU headers with information comprising characteristics of the PDU Set and the AL-FEC encoding information. The UPF may further route and transmit the determined PDU Set to another network device. The PDU Set may be transmitted to a base station of a wireless communication network.

[0203] The method may further comprise transmitting a request for establishment of a Quality of Service (QoS) flow, the QoS flow for a service data flow comprising the AL- FEC encoded PDU Set.

[0204] The request for establishment of a QoS flow may comprise a dynamic policy configuration. The dynamic policy configuration may comprise at least one of: a service data flow information; a set of QoS delay budget and rate requirements; a media type information; a PDU Set marking information; and a subset of the AL-FEC encoding configuration.

[0205] The request for the establishment of a QoS flow may be sent to a first network function. The first network function may communicate the request to a second network function. The second network function may comprise a Policy Control Function. The second network function may comprise a Network Exposure Function.

[0206] The first network function may comprise an Application Function (AF) or a Media Service Handler (MSH). The AF may be provisioned by an Application Service Provider (ASP) of the multimedia application with one or more policy templates for the dynamic policy configuration. The MSH may be arranged to handle the dynamic policy configuration of the multimedia application.

[0207] The request for the establishment of a QoS flow comprises a dynamic policy configuration, the dynamic policy configuration comprising a subset of the AL-FEC encoding configuration, wherein the subset of the AL-FEC encoding configuration comprises information of at least one of: a Forward Error Correction (FEC) EncodingIdentifier (ID) field, the FEC Encoding ID identifying in part the AL-FEC encoding configuration; a FEC Instance Identifier (ID) field, the FEC Instance ID identifying in part the AL-FEC encoding configuration and parameters; a Maximum Distance Separable (MDS) indicator field, the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic; a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern; a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota of number of redundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

[0208] The dynamic policy configuration may comprise a common information element indicating that PDU Set information included within PDU headers include at least AL-FEC information elements.

[0209] The PDU Set information within the PDU header may be included within a Real-time Transport Protocol (RTP) extension header element. The RTP extension header element for PDU Set information may comprise at least one of a field indicating a total number of PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a number of redundant PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a ratio of redundant PDUs to total PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a threshold of PDUs that may be lost by a network without the loss of the ADU corresponding to the AL-FEC encoded PDU Set; a field indicating a PDU Set Sequence Number; a field indicating a PDU Sequence Number of a PDU within the PDU Set; a field indicating an end PDU of the PDU Set; a field indicating a PDU Set Importance; and / or a field indicating a PDU Set Size in bytes.

[0210] The presence of the AL-FEC redundancy level field in the RTP header extension element for PDU Set marking may be indicated by an RTP extension attribute by means of SDP offer / answer procedure.

[0211] The device may comprise a User Equipment (UE) or an Application Server (AS).

[0212] The contents disclosed herein provide novel configuration and signalling elements enabling AL-FEC support in a wireless communications network (e.g., 5GS) for QoS flows with PDU Set integrated handling, such as:• signalling of AL-FEC configuration as part of the UE / ASP request for an AS QoS session with PDU Set and AL-FEC support;• various configuration options necessary to describe the AL-FEC encoding of the source to the network (e.g., 5GS);• extension of an existent RTP header extension for PDU Set marking to include (dynamic) AL-FEC redundancy level information to aid the network better manage redundant content in the face of air-interface challenging conditions (e.g., congestion events, capacity outage etc);• integration end-to-end of the proposed signalling and configuration solutions with the 5GS and 5G NR.

[0213] Accordingly, there is provided herein a method in a wireless communications device, the method comprising: receiving application data units (ADUs) of a multimedia application; applying an Application Layer Forward Error Correction encoding configuration corresponding to the multimedia application to encode each ADU to a PDU Set, the PDU Set comprising one or more AL-FEC encoded PDUs; marking PDU headers with information comprising characteristics of the PDU Set and of corresponding AL-FEC of the PDU Set, the marked PDU headers corresponding to one or more headers of the PDUs belonging to the PDU Set; and (known) transmitting the PDU Sets with the marked PDU headers to a network.

[0214] The device may indicate to the network by means of a first network function communicating to a second network function a request for an establishment of a Quality of Service (QoS) flow for a service data flow comprising AL-FEC encoded PDU Sets, the request comprising of a dynamic policy configuration including the service data flowinformation, a set of QoS delay budget and rate requirements, a media type information, a PDU Set marking information and a subset of the AL-FEC encoding configuration.

[0215] The first network function may be one of: an Application Function (AF), the AF provisioned by an Application Service Provider (ASP) of the multimedia application with one or more policy templates for the dynamic policy configuration; and a Media Service Handler (MSH), the MSH comprising handling the dynamic policy configuration of the multimedia application.

[0216] The dynamic policy configuration may comprise a common information element corresponding to the marked PDU headers, the common information element indicating the PDU Set marking and AL-FEC information elements available in the marked PDU headers.

[0217] The marked PDU headers may correspond to a Real-time Transport Protocol (RTP) extension header element for PDU Set marking.

[0218] The RTP extension header element for PDU Set marking may comprise at least one of:• a field indicating a total number of PDUs in the PDU Set;• a field indicating an AL-FEC redundancy level as a number of redundant PDUs in the PDU Set;• a field indicating an AL-FEC redundancy level as a quota of redundant PDUs vs. total PDUs in the PDU Set;• a field indicating an AL-FEC redundancy level as a threshold of PDUs that may be lost by the network without the loss of the ADU corresponding to the AL-FEC encoded PDU Set.• a field indicating a PDU Set Sequence Number;• a field indicating a PDU Sequence Number of a PDU within the PDU Set;• a field indicating an end PDU of the PDU Set;• a field indicating a PDU Set Importance; and• a field indicating a PDU Set Size in bytes;

[0219] The second network function may be one of a Policy Control Function; and a Network Exposure Function. The AF may be provisioned by an Application Service Provider (ASP) of the multimedia application with one or more policy templates for the dynamic policy configuration.

[0220] The wireless communications device may comprise one of a User Equipment (UE); and an Application Server (AS).

[0221] The subset of the AL-FEC encoding configuration may comprise information of at least one of• a Forward Error Correction (FEC) Encoding identifier (ID) field; the FEC Encoding ID identifying in part the AL-FEC encoding configuration;• a FEC Instance identifier (ID) field; the FEC instance ID identifying in part the AL- FEC encoding configuration and parameters;• a Maximum Distance Separable (MDS) indicator field; the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic;• a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern;• a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or• a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota ofnumber of redundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

[0222] The presence of the AL-FEC redundancy level field in the RTP header extension element for PDU Set marking may be indicated by an RTP extension attribute by means of SDP offer / answer procedure.

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

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

Claims

CLAIMSWhat is claimed is:

1. 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

2. The AS of claim 1, wherein the processor is further configured to cause the AS to: transmit a request for establishment of a Quality of Service (QoS) flow, the QoS flow for a service data flow comprising the AL-FEC encoded PDU Set.

3. The AS of claim 2, wherein the request for the establishment of a QoS flow is sent to an Application Function (AF).

4. The AS of claim 3, wherein the request for the establishment of a QoS flow comprises a dynamic policy configuration, the dynamic policy configuration comprising a subset of the AL-FEC encoding configuration, wherein the subset of the AL-FEC encoding configuration comprises information of at least one of: a Forward Error Correction (FEC) Encoding Identifier (ID) field, the FEC Encoding ID identifying in part the AL-FEC encoding configuration; a FEC Instance Identifier (ID) field, the FEC Instance ID identifying in part the AL- FEC encoding configuration and parameters;a Maximum Distance Separable (MDS) indicator field, the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic; a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern; a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota of number of redundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

5. The AS of claim 4, wherein the dynamic policy configuration comprises a common information element indicating that PDU Set information included within PDU headers include at least AL-FEC information elements.

6. The AS of any preceding claim, wherein the PDU Set information within PDU header is included within a Real-time Transport Protocol (RTP) extension header element, and wherein the RTP extension header element for PDU Set information comprises at least one of a field indicating a total number of PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a number of redundant PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a ratio of redundant PDUs to total PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a threshold of PDUs that may be lost by a network without the loss of the ADU corresponding to the AL-FEC encoded PDU Set; a field indicating a PDU Set Sequence Number; a field indicating a PDU Sequence Number of a PDU within the PDU Set; a field indicating an end PDU of the PDU Set;a field indicating a PDU Set Importance; and / or a field indicating a PDU Set Size in bytes.

7. 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: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

8. The UE of claim 7, wherein the processor is further configured to cause the UE to: transmit a request for establishment of a Quality of Service (QoS) flow, the QoS flow for a service data flow comprising the AL-FEC encoded PDU Set.

9. The UE of claim 8, wherein the request for the establishment of a QoS flow is sent to a Media Service Handler (MSH).

10. The UE of claim 8, wherein the request for the establishment of a QoS flow comprises a dynamic policy configuration, the dynamic policy configuration comprising a subset of the AL-FEC encoding configuration, wherein the dynamic policy configuration further comprises a common information element indicating that the PDU Set information included within PDU headers includes at least AL-FEC information elements; wherein the subset of the AL-FEC encoding configuration comprises information of at least one of: a Forward Error Correction (FEC) Encoding Identifier (ID) field, the FEC Encoding ID identifying in part the AL-FEC encoding configuration;a FEC Instance Identifier (ID) field, the FEC Instance ID identifying in part the AL- FEC encoding configuration and parameters; a Maximum Distance Separable (MDS) indicator field, the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic; a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern; a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota of number of redundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

11. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive Application Data Units (ADUs) of a multimedia application; generate at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU; mark at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmit the PDU Set.

12. A method performed by a device for wireless communication, the method comprising: receiving Application Data Units (ADUs) of a multimedia application; generating at least one Protocol Data Unit (PDU) Set based at least in part on coding at least one ADU of the ADUs by applying an Application Layer Forward Error Correction (AL-FEC) configuration, wherein the PDU Set comprises at least one PDU;marking at least one PDU header of the PDU Set to indicate the applied AL-FEC configuration for the PDU Set; and transmitting the PDU Set.

13. The method of claim 12, further comprising: transmitting a request for establishment of a Quality of Service (QoS) flow, the QoS flow for a service data flow comprising the AL-FEC encoded PDU Set.

14. The method of claim 13, wherein the request for the establishment of a QoS flow is sent to a first network function.

15. The method of claim 14, wherein the first network function comprises an Application Function (AF) or a Media Service Handler (MSH).

16. The method of claim 13, wherein the request for the establishment of a QoS flow comprises a dynamic policy configuration, the dynamic policy configuration comprising a subset of the AL-FEC encoding configuration, wherein the subset of the AL-FEC encoding configuration comprises information of at least one of: a Forward Error Correction (FEC) Encoding Identifier (ID) field, the FEC Encoding ID identifying in part the AL-FEC encoding configuration; a FEC Instance Identifier (ID) field, the FEC Instance ID identifying in part the AL- FEC encoding configuration and parameters; a Maximum Distance Separable (MDS) indicator field, the MDS indicator determining if the AL-FEC encoding configuration has an MDS encoding characteristic; a static redundancy level indicator field, the static redundancy level indicator determining if the AL-FEC encoding configuration generates a static redundancy pattern; a static redundancy PDU level indicator field, the static redundancy PDU level determining that the static redundancy pattern consists of a static number of redundant PDUs generated by the AL-FEC encoding configuration for each PDU Set; and / or a static redundancy per cent level indicator field, the static redundancy per cent level determining that the static redundancy pattern consists of a static quota of number ofredundant PDUs per number of total PDUs generated by the AL-FEC encoding configuration for each PDU Set.

17. The method of claim 16, wherein the dynamic policy configuration comprises a common information element indicating that PDU Set information included within PDU headers include at least AL-FEC information elements.

18. The method of any of claims 12 to 17, wherein the PDU Set information within PDU header is included within a Real-time Transport Protocol (RTP) extension header element.

19. The method of claim 18, wherein the RTP extension header element for PDU Set information comprises at least one of: a field indicating a total number of PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a number of redundant PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a ratio of redundant PDUs to total PDUs in the PDU Set; a field indicating an AL-FEC redundancy level as a threshold of PDUs that may be lost by a network without the loss of the ADU corresponding to the AL-FEC encoded PDU Set; a field indicating a PDU Set Sequence Number; a field indicating a PDU Sequence Number of a PDU within the PDU Set; a field indicating an end PDU of the PDU Set; a field indicating a PDU Set Importance; and / or a field indicating a PDU Set Size in bytes.

20. The method of any of claims 12 to 19, wherein the device comprises a User Equipment (UE) or an Application Server (AS).

Citation Information

Patent Citations

  • Method, system and devices for transmitting multimedia service in next network generation

    CN101616139A

  • Method and system of adaptive application layer FEC for MPEG media transport

    US20190044645A1

  • Apparatus and method for sending / receiving packet in multimedia communication system

    US20190273579A1

  • GR20220100750A

  • GR20220100751A