Expedited transfer indications in packets of media communication sessions
The ETI mechanism in packet headers efficiently toggles QoS configurations for media data, addressing inefficiencies in existing systems by reducing overhead and resource consumption, thereby improving media performance and power efficiency.
Patent Information
- Application Number
- PCT/US2026/025862
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-04-29
- Publication Date
- 2026-11-12
AI Technical Summary
Existing media communication systems face inefficiencies in signaling quality of service (QoS) changes for high and low payload data sets, leading to increased communication overhead and resource consumption.
Implementing an expedited transfer indication (ETI) mechanism using a single bit in packet headers to toggle QoS configurations for media data, allowing efficient signaling of QoS changes without requiring every packet to carry the indication.
Reduces communication overhead and resource consumption by dynamically adjusting QoS based on data payload, enhancing media performance and power efficiency in network devices.
Smart Images

Figure US2026025862_12112026_PF_FP_ABST
Abstract
Description
Qualcomm Ref. No. 2505105WO 1 / 56EXPEDITED TRANSFER INDICATIONS IN PACKETS OF MEDIA COMMUNICATION SESSIONS
[0001] This application claims priority to U.S. Provisional Application No. 63 / 800,106, filed May 5, 2025, the entire contents of which are hereby incorporated by reference.TECHNICAL FIELD
[0002] This disclosure relates to storage and transport of media data.BACKGROUND
[0003] Digital video capabilities can be incorporated into a wide range of devices, including digital televisions, digital direct broadcast systems, wireless broadcast systems, personal digital assistants (PDAs), laptop or desktop computers, digital cameras, digital recording devices, digital media players, video gaming devices, video game consoles, cellular or satellite radio telephones, video teleconferencing devices, and the like. Digital video devices implement video compression techniques, such as those described in the standards defined by MPEG-2, MPEG-4, ITU-T H.263 or ITU-T H.264 / MPEG-4, Part 10, Advanced Video Coding (AVC), ITU-T H.265 (also referred to as High Efficiency Video Coding (HEVC)), and extensions of such standards, to transmit and receive digital video information more efficiently.
[0004] After media data has been encoded, the video data may be packetized for transmission or storage. The media data may be assembled into a video file conforming to any of a variety of standards, such as the International Organization for Standardization (ISO) base media file format and extensions thereof, such as AVC.SUMMARY
[0005] In general, this disclosure describes techniques related to streaming media data, such as extended reality (XR) media data, e.g., augmented reality (AR), mixed reality (MR), or virtual reality (VR) media data. An AR media communication session, for example, may include certain sets of data that have a relatively high payload over a short amount of time (e.g., a data rate or bitrate exceeding a configured threshold), and other sets of data that have a relatively low payload or bitrate (e.g., below the configured threshold). Therefore, a sending device (e.g., an application server (AS) device) may1616-659WO01Qualcomm Ref. No. 2505105WO 2 / 56determine whether to enable an expedited transfer indication (ETI) for a set of packets. When ETI is enabled, a network device, such as a user plane function (UPF) device, a routing device, or the like, may process media data of the AR media communication session according to a first configured quality of service (QoS), whereas when ETI is disabled (i.e., not enabled), the network device may process the media data of the AR media communication session according to a second configured QoS. This disclosure describes techniques for signaling whether ETI is enabled or disabled using very low overhead signaling mechanisms, e.g., a single bit in a packet header extension, such as a real-time transport protocol (RTP) packet header extension, a QUIC header extension, or the like.
[0006] In one example, a method of exchanging media data includes: receiving, by a user plane function (UPF) device, a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF; encapsulating, by the UPF device, the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, including specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forwarding, by the UPF device, the first GTP-U packet to a destination of the SDF; receiving, by the UPF device, a second packet of the SDF including data representing that ETI is disabled for the SDF; encapsulating, by the UPF device, the second packet in a second GTP-U packet, including specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forwarding, by the UPF device, the second GTP-U packet to the destination of the SDF.
[0007] In another example, a user plane function (UPF) device for exchanging media data includes: a memory configured to store packets; and a processing system implemented in circuitry and configured to: receive a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF; encapsulate the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, wherein the processing system is configured to specify first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forward the first GTP-U packet to a destination of the SDF; receive a second packet of the SDF including data representing that ETI is disabled for the SDF; 1616-659WO01Qualcomm Ref. No. 2505105WO 3 / 56encapsulate the second packet in a second GTP-U packet, wherein the processing system is configured to specify second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forward the second GTP-U packet to the destination of the SDF.
[0008] In another example, a method of sending media data includes: determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled; determining that a second set of packets of the SDF correspond to a set of data having a size below the threshold; adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and sending the second set of packets to the UE device via the UPF device to cause the UPF to apply a second QoS configuration to the second set of packets based on ETI being disabled.
[0009] In another example, a device for exchanging media data includes: a memory configured to store media data; and a processing system implemented in circuitry and configured to: determine that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; add data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; send the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled; determine that a second set of packets of the SDF correspond to a set of data having a size below the threshold; add data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and send the second set of packets to the UE device via the UPF device to cause the UPF to apply a second QoS configuration to the second set of packets based on ETI being disabled.
[0010] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.1616-659WO01Qualcomm Ref. No. 2505105WO 4 / 56BRIEF DESCRIPTION OF DRAWINGS
[0011] FIG. 1 is a block diagram illustrating an example system that implements techniques for streaming media data over a network.
[0012] FIG. 2 is a block diagram illustrating elements of an example video file.
[0013] FIG. 3 is a block diagram illustrating an example set of network devices that may perform various aspects of the techniques of this disclosure.
[0014] FIG. 4 is a conceptual diagram illustrating packet structures for packets sent between various network devices.
[0015] FIG. 5 is a conceptual diagram illustrating an example QUIC packet.
[0016] FIG. 6 is a conceptual diagram illustrating an example of use of QUIC packets including QUIC header extensions including ETI information per techniques of this disclosure.
[0017] FIG. 7 is a graph illustrating an example indication of how ETI information may be used to determine an appropriate QoS per techniques of this disclosure.
[0018] FIG. 8 is a conceptual diagram illustrating a one-byte format for an RTP header extension including an ETI flag per techniques of this disclosure.
[0019] FIG. 9 is a flow diagram illustrating an example process for exchanging media data according to techniques of this disclosure.
[0020] FIG. 10 is a flowchart illustrating an example method of encapsulating packets into General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packets based on ETI information per techniques of this disclosure.
[0021] FIG. 11 is a flowchart illustrating another example method of encapsulating packets into GTP-U packets per techniques of this disclosure.
[0022] FIG. 12 is a flowchart illustrating an example method of sending packets of a media communication session including expedited transfer indication (ETI) information per techniques of this disclosure.DETAILED DESCRIPTION
[0023] In general, this disclosure describes techniques related to exchanging media data, such as extended reality (XR) media data, e.g., augmented reality (AR), mixed reality (MR), virtual reality (VR), or the like. Such media data may be exchanged between a user equipment (UE) device and a server device (e.g., an application server (AS) device), or between multiple UE devices engaged in an AR media communication session.1616-659WO01Qualcomm Ref. No. 2505105WO 5 / 56
[0024] In some cases, a relatively large amount of data may need to be sent quickly to a UE device that is participating in an AR media communication session. A policy and charging function (PCF) device may define policy and charging control (PCC) rules for various quality of service (QoS) configurations. A session management function (SMF) device may create packet detection rules (PDRs) for a service data flow (SDF) according to the PCC rules. The SDF may be identified by a network five-tuple, e.g., {source Internet protocol (IP) address, destination IP address, source port, destination port, protocol}. For example, the PCF device may define two PCC rules, one for a high QoS and one for a low QoS. The SMF device may in turn define two PDRs, one PDR associated with the high QoS and one PDR associated with the low QoS. The two PDRs may then effectively split a single SDF into two media flows.
[0025] A protocol data unit (PDU) may be a packet carrying media data of an AR media communication session in the packet payload. Per techniques of this disclosure, a PDU may also include data indicating whether to enable or disable an expedited transfer indication (ETI). When a PDU includes data indicating that ETI is enabled, a network device, such as a user plane function (UPF) device, routing device, or the like, may process packets of the SDF using the high QoS. When a PDU includes data indicating that ETI is disabled, the network device may process packets of the SDF using the low QoS. PDUs of the SDF also may omit an indication of ETI, in which case the network device may continue processing packets according to whether ETI was most recently enabled or disabled. In this manner, the ETI indication may act as a toggle to enable or disable ETI, but an ETI indication need not be provided for every packet. Certain packets in a media flow may not be able to carry an RTP header extension or QUIC header extension, such as real-time transport control protocol (RTCP) packets and traversal using relays around network address translation (TURN) packets.
[0026] The ETI indication may be a single bit that is included in, for example, a packet header, a packet header extension, metadata, or the like. Thus, packets of the AR media communication session need not include the packet header extension for every packet, and thus, need not include the ETI indication in every packet. In this manner, the techniques of this disclosure may be used to efficiently signal whether to enable or disable ETI, while avoiding inefficiencies that may otherwise occur if the ETI indication accompanied every packet of the AR media communication session. As one example, an RTP header extension for indicating data burst information or dynamically changing traffic characteristics may include the ETI indication. Such RTP header extensions are not 1616-659WO01Qualcomm Ref. No. 2505105WO 6 / 56sent for every RTP packet. As another example, a QUIC packet header extension may include the ETI indication, and the QUIC packet header extension need not be provided for every packet of a QUIC session. In this manner, the techniques of this disclosure may be used to efficiently signal whether to enable or disable ETI while avoiding overly increasing a communication overhead. Likewise, ETI may allow for efficient transport of large sets of media data on demand, while reducing network resource consumption when such large sets of media data are not being transported.
[0027] The techniques of this disclosure may be applied to video files conforming to video data encapsulated according to any of ISO base media file format, Scalable Video Coding (SVC) file format, Advanced Video Coding (AVC) file format, Third Generation Partnership Project (3GPP) file format, and / or Multiview Video Coding (MVC) file format, or other similar video file formats.
[0028] FIG. 1 is a block diagram illustrating an example system 10 that implements techniques for streaming media data over a network. In this example, system 10 includes content preparation device 20, server device 60, and client device 40. Client device 40 and server device 60 are communicatively coupled by network 74, which may comprise the Internet. In some examples, content preparation device 20 and server device 60 may also be coupled by network 74 or another network, or may be directly communicatively coupled. In some examples, content preparation device 20 and server device 60 may comprise the same device.
[0029] Content preparation device 20, in the example of FIG. 1, comprises audio source 22 and video source 24. Audio source 22 may comprise, for example, a microphone that produces electrical signals representative of captured audio data to be encoded by audio encoder 26. Alternatively, audio source 22 may comprise a storage medium storing previously recorded audio data, an audio data generator such as a computerized synthesizer, or any other source of audio data. Video source 24 may comprise a video camera that produces video data to be encoded by video encoder 28, a storage medium encoded with previously recorded video data, a video data generation unit such as a computer graphics source, or any other source of video data. Content preparation device 20 is not necessarily communicatively coupled to server device 60 in all examples, but may store multimedia content to a separate medium that is read by server device 60.
[0030] Raw audio and video data may comprise analog or digital data. Analog data may be digitized before being encoded by audio encoder 26 and / or video encoder 28. Audio source 22 may obtain audio data from a speaking participant while the speaking 1616-659WO01Qualcomm Ref. No. 2505105WO 7 / 56participant is speaking, and video source 24 may simultaneously obtain video data of the speaking participant. In other examples, audio source 22 may comprise a computer-readable storage medium comprising stored audio data, and video source 24 may comprise a computer-readable storage medium comprising stored video data. In this manner, the techniques described in this disclosure may be applied to live, streaming, real-time audio and video data or to archived, pre-recorded audio and video data.
[0031] Audio frames that correspond to video frames are generally audio frames containing audio data that was captured (or generated) by audio source 22 contemporaneously with video data captured (or generated) by video source 24 that is contained within the video frames. For example, while a speaking participant generally produces audio data by speaking, audio source 22 captures the audio data, and video source 24 captures video data of the speaking participant at the same time, that is, while audio source 22 is capturing the audio data. Hence, an audio frame may temporally correspond to one or more particular video frames. Accordingly, an audio frame corresponding to a video frame generally corresponds to a situation in which audio data and video data were captured at the same time and for which an audio frame and a video frame comprise, respectively, the audio data and the video data that was captured at the same time.
[0032] In some examples, audio encoder 26 may encode a timestamp in each encoded audio frame that represents a time at which the audio data for the encoded audio frame was recorded, and similarly, video encoder 28 may encode a timestamp in each encoded video frame that represents a time at which the video data for an encoded video frame was recorded. In such examples, an audio frame corresponding to a video frame may comprise an audio frame comprising a timestamp and a video frame comprising the same timestamp. Content preparation device 20 may include an internal clock from which audio encoder 26 and / or video encoder 28 may generate the timestamps, or that audio source 22 and video source 24 may use to associate audio and video data, respectively, with a timestamp.
[0033] In some examples, audio source 22 may send data to audio encoder 26 corresponding to a time at which audio data was recorded, and video source 24 may send data to video encoder 28 corresponding to a time at which video data was recorded. In some examples, audio encoder 26 may encode a sequence identifier in encoded audio data to indicate a relative temporal ordering of encoded audio data but without necessarily indicating an absolute time at which the audio data was recorded, and similarly, video 1616-659WO01Qualcomm Ref. No. 2505105WO 8 / 56encoder 28 may also use sequence identifiers to indicate a relative temporal ordering of encoded video data. Similarly, in some examples, a sequence identifier may be mapped or otherwise correlated with a timestamp.
[0034] Audio encoder 26 generally produces a stream of encoded audio data, while video encoder 28 produces a stream of encoded video data. Each individual stream of data (whether audio or video) may be referred to as an elementary stream. An elementary stream is a single, digitally coded (possibly compressed) component of a media presentation. For example, the coded video or audio part of the media presentation can be an elementary stream. An elementary stream may be converted into a packetized elementary stream (PES) before being encapsulated within a video file. Within the same media presentation, a stream ID may be used to distinguish the PES-packets belonging to one elementary stream from the other. The basic unit of data of an elementary stream is a packetized elementary stream (PES) packet. Thus, coded video data generally corresponds to elementary video streams. Similarly, audio data corresponds to one or more respective elementary streams.
[0035] In the example of FIG. 1, encapsulation unit 30 of content preparation device 20 receives elementary streams comprising coded video data from video encoder 28 and elementary streams comprising coded audio data from audio encoder 26. In some examples, video encoder 28 and audio encoder 26 may each include packetizers for forming PES packets from encoded data. In other examples, video encoder 28 and audio encoder 26 may each interface with respective packetizers for forming PES packets from encoded data. In still other examples, encapsulation unit 30 may include packetizers for forming PES packets from encoded audio and video data.
[0036] Video encoder 28 may encode video data of multimedia content in a variety of ways, to produce different representations of the multimedia content at various bitrates and with various characteristics, such as pixel resolutions, frame rates, conformance to various coding standards, conformance to various profiles and / or levels of profiles for various coding standards, representations having one or multiple views (e.g., for two-dimensional or three-dimensional playback), or other such characteristics. A representation, as used in this disclosure, may comprise one of audio data, video data, text data (e.g., for closed captions), or other such data. The representation may include an elementary stream, such as an audio elementary stream or a video elementary stream. Each PES packet may include a stream id that identifies the elementary stream to which1616-659WO01Qualcomm Ref. No. 2505105WO 9 / 56the PES packet belongs. Encapsulation unit 30 is responsible for assembling elementary streams into streamable media data.
[0037] Encapsulation unit 30 receives PES packets for elementary streams of a media presentation from audio encoder 26 and video encoder 28 and forms corresponding network abstraction layer (NAL) units from the PES packets. Coded video segments may be organized into NAL units, which provide a “network-friendly” video representation addressing applications such as video telephony, storage, broadcast, or streaming. NAL units can be categorized into Video Coding Layer (VCL) NAL units and non-VCL NAL units. VCL NAL units may contain the core compression engine and may include block, macroblock, and / or slice level data. Other NAL units may be non-VCL NAL units. In some examples, a coded picture in one time instance, normally presented as a primary coded picture, may be contained in an access unit, which may include one or more NAL units.
[0038] Non-VCL NAL units may include parameter set NAL units and supplemental enhancement information (SEI) NAL units, among others. Parameter sets may contain sequence-level header information (in sequence parameter sets (SPS)) and the infrequently changing picture-level header information (in picture parameter sets (PPS)). With parameter sets (e.g., PPS and SPS), infrequently changing information need not to be repeated for each sequence or picture; hence, coding efficiency may be improved. Furthermore, the use of parameter sets may enable out-of-band transmission of the important header information, avoiding the need for redundant transmissions for error resilience. In out-of-band transmission examples, parameter set NAL units may be transmitted on a different channel than other NAL units, such as SEI NAL units.
[0039] Supplemental Enhancement Information (SEI) may contain information that is not necessary for decoding the coded pictures samples from VCL NAL units, but may assist in processes related to decoding, display, error resilience, and other purposes. SEI messages may be contained in non-VCL NAL units. SEI messages are the normative part of some standard specifications, and thus are not always mandatory for standard compliant decoder implementation. SEI messages may be sequence level SEI messages or picture level SEI messages. Some sequence level information may be contained in SEI messages, such as scalability information SEI messages in the example of SVC and view scalability information SEI messages in MVC. These example SEI messages may convey information on, e.g., extraction of operation points and characteristics of the operation points.1616-659WO01Qualcomm Ref. No. 2505105WO 10 / 56
[0040] Server device 60 includes Real-time Transport Protocol (RTP) transmitting unit 70 and network interface 72. In some examples, server device 60 may include a plurality of network interfaces. Furthermore, any or all of the features of server device 60 may be implemented on other devices of a content delivery network, such as routers, bridges, proxy devices, switches, or other devices. In some examples, intermediate devices of a content delivery network may cache data of multimedia content 64 and include components that conform substantially to those of server device 60. In general, network interface 72 is configured to send and receive data via network 74.
[0041] RTP transmitting unit 70 is configured to deliver media data to client device 40 via network 74 according to RTP, which is standardized in Request for Comment (RFC) 3550 by the Internet Engineering Task Force (IETF). RTP transmitting unit 70 may also implement protocols related to RTP, such as RTP Control Protocol (RTCP), Real-time Streaming Protocol (RTSP), Session Initiation Protocol (SIP), and / or Session Description Protocol (SDP). RTP transmitting unit 70 may send media data via network interface 72, which may implement User Datagram Protocol (UDP) and / or Internet protocol (IP). Thus, in some examples, server device 60 may send media data via RTP and RTSP over UDP using network 74.
[0042] RTP transmitting unit 70 may receive an RTSP describe request from, e.g., client device 40. The RTSP describe request may include data indicating what types of data are supported by client device 40. RTP transmitting unit 70 may respond to client device 40 with data indicating media streams, such as media content 64, that can be sent to client device 40, along with a corresponding network location identifier, such as a uniform resource locator (URL) or uniform resource name (URN).
[0043] RTP transmitting unit 70 may then receive an RTSP setup request from client device 40. The RTSP setup request may generally indicate how a media stream is to be transported. The RTSP setup request may contain the network location identifier for the requested media data (e.g., media content 64) and a transport specifier, such as local ports for receiving RTP data and control data (e.g., RTCP data) on client device 40. RTP transmitting unit 70 may reply to the RTSP setup request with a confirmation and data representing ports of server device 60 by which the RTP data and control data will be sent. RTP transmitting unit 70 may then receive an RTSP play request, to cause the media stream to be “played,” i.e., sent to client device 40 via network 74. RTP transmitting unit 70 may also receive an RTSP teardown request to end the streaming session, in response1616-659WO01Qualcomm Ref. No. 2505105WO 11 / 56to which, RTP transmitting unit 70 may stop sending media data to client device 40 for the corresponding session.
[0044] RTP receiving unit 52, likewise, may initiate a media stream by initially sending an RTSP describe request to server device 60. The RTSP describe request may indicate types of data supported by client device 40. RTP receiving unit 52 may then receive a reply from server device 60 specifying available media streams, such as media content 64, that can be sent to client device 40, along with a corresponding network location identifier, such as a uniform resource locator (URL) or uniform resource name (URN).
[0045] RTP receiving unit 52 may then generate an RTSP setup request and send the RTSP setup request to server device 60. As noted above, the RTSP setup request may contain the network location identifier for the requested media data (e.g., media content 64) and a transport specifier, such as local ports for receiving RTP data and control data (e.g., RTCP data) on client device 40. In response, RTP receiving unit 52 may receive a confirmation from server device 60, including ports of server device 60 that server device 60 will use to send media data and control data.
[0046] After establishing a media streaming session between server device 60 and client device 40, RTP transmitting unit 70 of server device 60 may send media data (e.g., packets of media data) to client device 40 according to the media streaming session. Server device 60 and client device 40 may exchange control data (e.g., RTCP data) indicating, for example, reception statistics by client device 40, such that server device 60 can perform congestion control or otherwise diagnose and address transmission faults.
[0047] Per techniques of this disclosure, RTP transmitting unit 70 of server device 60 may further encapsulate certain packets of the media data with RTP header extensions including ETI information, as discussed in greater detail below. While RTP is used as one example transport protocol, other transport protocols, such as QUIC, may be used instead or in addition to RTP, consistent with techniques of this disclosure.
[0048] Although not shown explicitly in the example of FIG. 1, network 74 may include one or more network devices, such as a user plane function (UPF) device, a base station, and a radio access network (RAN). Client device 40 may represent an example of a user equipment (UE) device. Server device 60 and content preparation device 20 may represent examples of an application server (AS) device, an application function (AF) device, or a sending device. In some examples, content preparation device 20 may represent an application service provider (AP) device, while server device 60 may represent an application server (AS) device. Content preparation device 20 may host and 1616-659WO01Qualcomm Ref. No. 2505105WO 12 / 56serve manifest files, such as manifest file 66, while server device 60 may host multimedia content 64. In such examples, client device 40 may request manifest file 66 from content preparation device 20 and use data of manifest file 66 to determine that multimedia content 64 is available from server device 60. Server device 60 and client device 40 may implement techniques of this disclosure for exchanging media data.
[0049] Server device 60 (or content preparation device 20) may form packets including media data of a service data flow (SDF) to be sent to client device 40 via network 74. Server device 60 may also determine, for a set of packets of the packets of the SDF, whether to enable an expedited transfer indication (ETI) for the set of packets. That is, server device 60 may partition the media data of the media communication session with client device 40 into distinct sets of packets sent in order, and for each set of packets, determine whether to enable or disable ETI. For example, if an amount of media data of a particular set of packets exceeds a threshold, server device 60 may enable ETI for the set of packets, whereas if the amount of media data does not exceed the threshold, server device 60 may disable ETI. In particular, server device 60 may set a single bit of a packet of the set of packets indicating whether ETI is enabled for that packet and subsequent packets, up to a packet including the bit having a value indicating that the ETI setting is to be “flipped.” That is, if the initial packet indicates that ETI is to be enabled, ETI may remain enabled until a packet is received including data indicating that ETI is to be disabled; whereas if an initial packet indicates that ETI is to be disabled, ETI may remain disabled until a packet is received including data indicating that ETI is to be enabled. Enabling and disabling ETI may be toggled any number of times throughout the communication session.
[0050] Server device 60 may further send data representing rules for detecting packets including ETI information and whether the ETI information indicates that ETI is to be enabled or disabled. For example, server device 60 may send data indicating that ETI information will be included in an RTP header extension, a QUIC header extension, a UDP option field, metadata of a Media over QUIC (MoQ), or a hypertext transfer protocol (HTTP) datagram of a QUIC packet. The rules may further specify a quality of service (QoS) to which to map ETI being enabled or disabled, e.g., a 5G QoS indication (5QI).
[0051] A UPF device within network 74 may perform techniques of this disclosure for exchanging media data. When server device 60 sends data to client device 40, server device 60 may initially send the data (as well as the rules for detecting packets including ETI information) to the UPF device. The UPF device may receive a first packet of a 1616-659WO01Qualcomm Ref. No. 2505105WO 13 / 56service data flow (SDF) from, e.g., server device 60, where the first packet includes data representing that expedited transfer indication (ETI) is enabled for the SDF. The UPF device may encapsulate the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet. In particular, the UPF device may form the GTP-U packet to include information specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing the enabled ETI. The UPF device may forward the first GTP-U packet to a destination of the SDF, such as client device 40. Forwarding the first GTP-U packet to client device 40 may include forwarding the first GTP-U packet via a network tunnel that is communicatively coupled to a base station to which client device 40 is communicatively coupled via a RAN.
[0052] The UPF device may subsequently receive a second packet of the SDF including data representing a disabled ETI for the SDF from server device 60. The UPF device may encapsulate the second packet in a second GTP-U packet. Encapsulating the second packet may include specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing the disabled ETI. The second QoS information may differ from the first QoS information. The UPF device may forward the second GTP-U packet to the destination of the SDF, such as client device 40. Forwarding the second GTP-U packet to client device 40 may include forwarding the second GTP-U packet via the network tunnel.
[0053] Network interface 54 may receive and provide media of a selected media presentation to RTP receiving unit 52, which may in turn provide the media data to decapsulation unit 50. Decapsulation unit 50 may decapsulate elements of a video file into constituent PES streams, depacketize the PES streams to retrieve encoded data, and send the encoded data to either audio decoder 46 or video decoder 48, depending on whether the encoded data is part of an audio or video stream, e.g., as indicated by PES packet headers of the stream. Audio decoder 46 decodes encoded audio data and sends the decoded audio data to audio output 42, while video decoder 48 decodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to video output 44.
[0054] Video encoder 28, video decoder 48, audio encoder 26, audio decoder 46, encapsulation unit 30, RTP receiving unit 52, and decapsulation unit 50 each may be implemented as any of a variety of suitable processing circuitry, as applicable, such as one or more microprocessors, digital signal processors (DSPs), application specific 1616-659WO01Qualcomm Ref. No. 2505105WO 14 / 56integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic circuitry, software, hardware, firmware or any combinations thereof. Each of video encoder 28 and video decoder 48 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined video encoder / decoder (CODEC). Likewise, each of audio encoder 26 and audio decoder 46 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined CODEC. An apparatus including video encoder 28, video decoder 48, audio encoder 26, audio decoder 46, encapsulation unit 30, RTP receiving unit 52, and / or decapsulation unit 50 may comprise an integrated circuit, a microprocessor, and / or a wireless communication device, such as a cellular telephone.
[0055] Client device 40, server device 60, and / or content preparation device 20 may be configured to operate in accordance with the techniques of this disclosure. For purposes of example, this disclosure describes these techniques with respect to client device 40 and server device 60. However, it should be understood that content preparation device 20 may be configured to perform these techniques, instead of (or in addition to) server device 60.
[0056] Encapsulation unit 30 may form NAL units comprising a header that identifies a program to which the NAL unit belongs, as well as a payload, e.g., audio data, video data, or data that describes the transport or program stream to which the NAL unit corresponds. For example, in H.264 / AVC, a NAL unit includes a 1-byte header and a payload of varying size. A NAL unit including video data in its payload may comprise various granularity levels of video data. For example, a NAL unit may comprise a block of video data, a plurality of blocks, a slice of video data, or an entire picture of video data. Encapsulation unit 30 may receive encoded video data from video encoder 28 in the form of PES packets of elementary streams. Encapsulation unit 30 may associate each elementary stream with a corresponding program.
[0057] Encapsulation unit 30 may also assemble access units from a plurality of NAL units. In general, an access unit may comprise one or more NAL units for representing a frame of video data, as well as audio data corresponding to the frame when such audio data is available. An access unit generally includes all NAL units for one output time instance, e.g., all audio and video data for one time instance. For example, if each view has a frame rate of 20 frames per second (fps), then each time instance may correspond to a time interval of 0.05 seconds. During this time interval, the specific frames for all views of the same access unit (the same time instance) may be rendered simultaneously.1616-659WO01Qualcomm Ref. No. 2505105WO 15 / 56In one example, an access unit may comprise a coded picture in one time instance, which may be presented as a primary coded picture.
[0058] Accordingly, an access unit may comprise all audio and video frames of a common temporal instance, e.g., all views corresponding to time X. This disclosure also refers to an encoded picture of a particular view as a “view component.” That is, a view component may comprise an encoded picture (or frame) for a particular view at a particular time. Accordingly, an access unit may be defined as comprising all view components of a common temporal instance. The decoding order of access units need not necessarily be the same as the output or display order.
[0059] After encapsulation unit 30 has assembled NAL units and / or access units into a video file based on received data, encapsulation unit 30 passes the video file to output interface 32 for output. In some examples, encapsulation unit 30 may store the video file locally or send the video file to a remote server via output interface 32, rather than sending the video file directly to client device 40. Output interface 32 may comprise, for example, a transmitter, a transceiver, a device for writing data to a computer-readable medium such as, for example, an optical drive, a magnetic media drive (e.g., floppy drive), a universal serial bus (USB) port, a network interface, or other output interface. Output interface 32 outputs the video file to a computer-readable medium, such as, for example, a transmission signal, a magnetic medium, an optical medium, a memory, a flash drive, or other computer-readable medium.
[0060] Network interface 54 may receive a NAL unit or access unit via network 74 and provide the NAL unit or access unit to decapsulation unit 50, via RTP receiving unit 52. Decapsulation unit 50 may decapsulate elements of a video file into constituent PES streams, depacketize the PES streams to retrieve encoded data, and send the encoded data to either audio decoder 46 or video decoder 48, depending on whether the encoded data is part of an audio or video stream, e.g., as indicated by PES packet headers of the stream. Audio decoder 46 decodes encoded audio data and sends the decoded audio data to audio output 42, while video decoder 48 decodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to video output 44.
[0061] The configuration of system 10 illustrated in FIG. 1 may provide various technical benefits and advantages. By configuring the UPF device to receive a packet indicating whether ETI is enabled or disabled and to apply either a first QoS configuration or a second QoS configuration to that packet and to subsequent packets (until ETI is toggled by a subsequent packet), system 10 may reduce communication overhead. Conventional 1616-659WO01Qualcomm Ref. No. 2505105WO 16 / 56techniques have each packet of a media flow to include data indicating a respective QoS, causing large communication overhead and inefficiencies. By contrast, the techniques of this disclosure allow the UPF device to maintain a state variable for the ETI and update the state variable in response to receiving a different ETI value in a subsequent packet of the same media communication session, e.g., the same SDF. Furthermore, configuring the UPF device to encapsulate the packet in a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet specifying either first QoS information or second QoS information, the UPF device may seamlessly integrate the ETI state into established network tunneling protocols.
[0062] Moreover, transmitting the ETI only upon a change in status may avoid specifying QoS information in packets that lack capacity to carry an extension header, such as realtime transport control protocol (RTCP) packets or traversal using relays around network address translation (TURN) packets. Implementing the techniques of this disclosure may result in an efficient signaling mechanism. Consequently, the UPF device, server device 60, and client device 40 may achieve better media performance. Additionally, reducing the overall amount of data signalled via network 74 may provide power savings for devices of network 74.
[0063] FIG. 2 is a block diagram illustrating elements of an example video file 150. As described above, video files in accordance with the ISO base media file format and extensions thereof store data in a series of objects, referred to as “boxes.” In the example of FIG. 2, video file 150 includes file type (FTYP) box 152, movie (MOOV) box 154, segment index (sidx) boxes 162, movie fragment (MOOF) boxes 164, and movie fragment random access (MFRA) box 166. Although FIG. 2 represents an example of a video file, it should be understood that other media files may include other types of media data (e.g., audio data, timed text data, or the like) that is structured similarly to the data of video file 150, in accordance with the ISO base media file format and its extensions.
[0064] File type (FTYP) box 152 generally describes a file type for video file 150. File type box 152 may include data that identifies a specification that describes a best use for video file 150. File type box 152 may alternatively be placed before MOOV box 154, movie fragment boxes 164, and / or MFRA box 166.
[0065] MOOV box 154, in the example of FIG. 2, includes movie header (MVHD) box 156, track (TRAK) box 158, and one or more movie extends (MVEX) boxes 160. In general, MVHD box 156 may describe general characteristics of video file 150. For example, MVHD box 156 may include data that describes when video file 150 was 1616-659WO01Qualcomm Ref. No. 2505105WO 17 / 56originally created, when video file 150 was last modified, a timescale for video file 150, a duration of playback for video file 150, or other data that generally describes video file 150.
[0066] TRAK box 158 may include data for a track of video file 150. TRAK box 158 may include a track header (TKHD) box that describes characteristics of the track corresponding to TRAK box 158. In some examples, TRAK box 158 may include coded video pictures, while in other examples, the coded video pictures of the track may be included in movie fragments 164, which may be referenced by data of TRAK box 158 and / or sidx boxes 162.
[0067] In some examples, video file 150 may include more than one track. Accordingly, MOOV box 154 may include a number of TRAK boxes equal to the number of tracks in video file 150. TRAK box 158 may describe characteristics of a corresponding track of video file 150. For example, TRAK box 158 may describe temporal and / or spatial information for the corresponding track. A TRAK box similar to TRAK box 158 of MOOV box 154 may describe characteristics of a parameter set track, when encapsulation unit 30 (FIG. 1) includes a parameter set track in a video file, such as video file 150. Encapsulation unit 30 may signal the presence of sequence level SEI messages in the parameter set track within the TRAK box describing the parameter set track.
[0068] MVEX boxes 160 may describe characteristics of corresponding movie fragments 164, e.g., to signal that video file 150 includes movie fragments 164, in addition to video data included within MOOV box 154, if any. In the context of streaming video data, coded video pictures may be included in movie fragments 164 rather than in MOOV box 154. Accordingly, all coded video samples may be included in movie fragments 164, rather than in MOOV box 154.
[0069] MOOV box 154 may include a number of MVEX boxes 160 equal to the number of movie fragments 164 in video file 150. Each of MVEX boxes 160 may describe characteristics of a corresponding one of movie fragments 164. For example, each MVEX box may include a movie extends header box (MEHD) box that describes a temporal duration for the corresponding one of movie fragments 164.
[0070] As noted above, encapsulation unit 30 may store a sequence data set in a video sample that does not include actual coded video data. A video sample may generally correspond to an access unit, which is a representation of a coded picture at a specific time instance. In the context of AVC, the coded picture includes one or more VCL NAL units, which contain the information to construct all the pixels of the access unit and other 1616-659WO01Qualcomm Ref. No. 2505105WO 18 / 56associated non-VCL NAL units, such as SEI messages. Accordingly, encapsulation unit 30 may include a sequence data set, which may include sequence level SEI messages, in one of movie fragments 164. Encapsulation unit 30 may further signal the presence of a sequence data set and / or sequence level SEI messages as being present in one of movie fragments 164 within the one of MVEX boxes 160 corresponding to the one of movie fragments 164.
[0071] SIDX boxes 162 are optional elements of video file 150. That is, video files conforming to the 3 GPP file format, or other such file formats, do not necessarily include SIDX boxes 162. In accordance with the example of the 3GPP file format, a SIDX box may be used to identify a sub-segment of a segment (e.g., a segment contained within video file 150). The 3GPP file format defines a sub-segment as “a self-contained set of one or more consecutive movie fragment boxes with corresponding Media Data box(es) and a Media Data Box containing data referenced by a Movie Fragment Box must follow that Movie Fragment box and precede the next Movie Fragment box containing information about the same track.” The 3GPP file format also indicates that a SIDX box “contains a sequence of references to subsegments of the (sub)segment documented by the box. The referenced subsegments are contiguous in presentation time. Similarly, the bytes referred to by a Segment Index box are always contiguous within the segment. The referenced size gives the count of the number of bytes in the material referenced.”
[0072] SIDX boxes 162 generally provide information representative of one or more subsegments of a segment included in video file 150. For instance, such information may include playback times at which sub-segments begin and / or end, byte offsets for the subsegments, whether the sub-segments include (e.g., start with) a stream access point (SAP), a type for the SAP (e.g., whether the SAP is an instantaneous decoder refresh (IDR) picture, a clean random access (CRA) picture, a broken link access (BLA) picture, or the like), a position of the SAP (in terms of playback time and / or byte offset) in the subsegment, and the like.
[0073] Movie fragments 164 may include one or more coded video pictures. In some examples, movie fragments 164 may include one or more groups of pictures (GOPs), each of which may include a number of coded video pictures, e.g., frames or pictures. In addition, as described above, movie fragments 164 may include sequence data sets in some examples. Each of movie fragments 164 may include a movie fragment header box (MFHD, not shown in FIG. 2). The MFHD box may describe characteristics of the1616-659WO01Qualcomm Ref. No. 2505105WO 19 / 56corresponding movie fragment, such as a sequence number for the movie fragment. Movie fragments 164 may be included in order of sequence number in video file 150.
[0074] MFRA box 166 may describe random access points within movie fragments 164 of video file 150. This may assist with performing trick modes, such as performing seeks to particular temporal locations (i.e., playback times) within a segment encapsulated by video file 150. MFRA box 166 is generally optional and need not be included in video files, in some examples. Likewise, a client device, such as client device 40, does not necessarily need to reference MFRA box 166 to correctly decode and display video data of video file 150. MFRA box 166 may include a number of track fragment random access (TFRA) boxes (not shown) equal to the number of tracks of video file 150, or in some examples, equal to the number of media tracks (e.g., non-hint tracks) of video file 150.
[0075] In some examples, movie fragments 164 may include one or more stream access points (SAPs), such as IDR pictures. Likewise, MFRA box 166 may provide indications of locations within video file 150 of the SAPs. Accordingly, a temporal sub-sequence of video file 150 may be formed from SAPs of video file 150. The temporal sub-sequence may also include other pictures, such as P-frames and / or B-frames that depend from SAPs. Frames and / or slices of the temporal sub-sequence may be arranged within the segments such that frames / slices of the temporal sub-sequence that depend on other frames / slices of the sub-sequence can be properly decoded. For example, in the hierarchical arrangement of data, data used for prediction for other data may also be included in the temporal sub-sequence.
[0076] FIG. 3 is a block diagram illustrating an example set of network devices that may perform various aspects of the techniques of this disclosure. The example of FIG. 3 depicts sending device 200, user plane function (UPF) device 202, base station 206, user equipment (UE) device 208, application function (AF) device 218, policy and charging function (PCF) device 216, and session management function (SMF) device 214. Sending device 200 may correspond to server device 60 and / or content preparation device 20 of FIG. 1. UE device 208 may correspond to client device 40 of FIG. 1.
[0077] Sending device 200 (e.g., an application server (AS) device) may obtain video data to be sent to UE device 208 via communication session 210. To send the video data to UE device 208, sending device 200 may encode the video data (or receive encoded video data from an encoding device, not shown in FIG. 3). Sending device 200 may encapsulate packets including encoded video data (e.g., encoded slices of frames of video data) to form, e.g., RTP or QUIC packets, or other such packets for other transport 1616-659WO01Qualcomm Ref. No. 2505105WO 20 / 56protocols for carrying media data. Sending device 200 may, per techniques of this disclosure, add data representing an expedited transfer indication (ETI) to the packets to indicate whether to enable or disable ETI. As the packets are formed, sending device 200 may send the packets to UE device 208 via a network including UPF device 202. Although not shown in FIG. 3, there may be additional network devices between sending device 200 and UPF device 202, e.g., various network routing devices, gateways, bridges, switches, or the like.
[0078] In accordance with techniques of this disclosure, sending device 200 may determine that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold. Based on determining the size is above the threshold, sending device 200 may add data to at least an ordinal first packet of the first set of packets representing an enabled expedited transfer indication (ETI) for the first set of packets. Sending device 200 may send the first set of packets to a UE device 208 via UPF device 202. Sending the first set of packets with the enabled ETI may cause UPF device 202 to apply a first quality of service (QoS) configuration to the first set of packets based on the enabled ETI. Furthermore, sending device 200 may determine that a second set of packets of the SDF correspond to a set of data having a size below the threshold. Based on determining the size is below the threshold, sending device 200 may add data to at least an ordinal first packet of the second set of packets representing a disabled ETI for the second set of packets. Sending device 200 may send the second set of packets to UE device 208 via UPF device 202 to cause UPF device 202 to apply a second QoS configuration to the second set of packets based on the disabled ETI.
[0079] UE device 208 may request ETI processing for packets of communication session 210 from AF device 218. For example, UE device 208 may send a protocol description to AF device 218 including a request for ETI processing (e.g., an expedited data transfer). In this manner, AF device 218 may request expedited data transfer with reflective QoS to expedite transfer of larger payloads for IP flows, e.g., of AR / XR media communication sessions. AF device 218 may forward the protocol description to PCF device 216. PCF device 216 may then generate policy and charging control (PCC) rules for ETI processing based on the protocol description and send the PCC rules to SMF device 214. If UE device 208 supports reflective quality of service (QoS), PCF device 216 may generate PCC rules for each media flow based on a request from AF device 218. SMF device 214 may create respective packet detection rules (PDRs) for a service data flow (SDF) corresponding to communication session 210. The PDRs may include a first PDR rule for a high quality of 1616-659WO01Qualcomm Ref. No. 2505105WO 21 / 56service (QoS) and a second PDR rule for a low QoS. SMF device 214 may send the PDRs to UPF device 202, which may use the PDRs to detect data indicating whether to enable or disable ETI.
[0080] In some examples, the PDRs may indicate that the ETI data will be included in an RTP header extension. In some examples, the PDRs may indicate that the ETI data will be included in N6 metadata. In examples using N6 metadata, the N6 interface may represent the interface between a PDU Session Anchor (PSA) UPF and an external data network. Using N6 metadata to carry the ETI information may provide an additional signaling alternative that leverages existing core network interfaces to efficiently convey QoS requirements between the data network and the UPF. In some examples, the PDRs may indicate that the ETI data will be included in a QUIC packet header extension. In some examples, the PDRs may indicate that the ETI data will be included in a user datagram protocol (UDP) option field of UDP packets encapsulating PDUs. In some examples, the PDRs may indicate that the ETI data will be included in a metadata portion of a Media over QUIC (MoQ) object conveyed by a PDU. In some examples, the PDRs may indicate that the ETI data will be included in an HTTP datagram in a payload of a QUIC packet. In some examples, the PDRs may indicate that the ETI data will be included in a field in a header of a QUIC packet. In this manner, UPF device 202 may be configured to detect ETI data in a downlink service data flow.
[0081] UPF device 202 may include a memory configured to store packets and a processing system implemented in circuitry. The processing system of UPF device 202 may execute operations to perform techniques of this disclosure. Sending device 200 may also include a memory configured to store media data and a processing system implemented in circuitry.
[0082] UPF device 202 may thus receive the packets from sending device 200 and form General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) tunneled packets. For example, UPF device 202 may encapsulate the received packets with respective GTP-U headers. Per techniques of this disclosure, UPF device 202 may use the PDRs from SMF device 214 to detect ETI data of the packets and determine whether to process the packets using a first configured quality of service (QoS) or a second configured QoS. For example, the first QoS may correspond to 5G QoS Identifier (5QI) 7, which has a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3. Likewise, as an example, the second QoS may correspond to1616-659WO01Qualcomm Ref. No. 2505105WO 22 / 565QI 6, which has a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6. 5QI 7 and 5QI 6 are each for non-guaranteed bitrate (non-GBR) SDFs.
[0083] While described with respect to 5G networks and 5QI values, the techniques of this disclosure are also applicable to other generations of cellular networks, such as sixth generation (6G) networks. Furthermore, the techniques of this disclosure may be applicable to and implemented in accordance with various standardization efforts, such as the Third Generation Partnership Project (3 GPP) Release-20 (Rel-20) study item in Service and System Aspects 4 (SA4) regarding multimedia, such as FS Q4RTC MED.
[0084] In accordance with techniques of this disclosure, UPF device 202 may receive a first packet of a service data flow (SDF) including data representing an enabled expedited transfer indication (ETI) for the SDF. UPF device 202 may encapsulate the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet. Encapsulating the first packet may include specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing the enabled ETI. UPF device 202 may forward the first GTP-U packet to a destination of the SDF. In this example, UE device 208 represents the destination of the SDF. Forwarding the first GTP-U packet to UE device 208 may include forwarding the first GTP-U packet via network tunnel 204 that communicatively couples UPF device 202 to base station 206. Base station 206 may be communicatively coupled to UE device 208 via radio access network (RAN) 212.
[0085] UPF device 202 may subsequently receive a second packet of the SDF including data representing a disabled ETI for the SDF. UPF device 202 may encapsulate the second packet in a second GTP-U packet. Encapsulating the second packet may include specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing the disabled ETI. The second QoS information may differ from the first QoS information. UPF device 202 may forward the second GTP-U packet to the destination of the SDF. Forwarding the second GTP-U packet to UE device 208 may include forwarding the second GTP-U packet via network tunnel 204.
[0086] Base station 206 may receive the GTP-U packets and decapsulate the GTP-U packets to reproduce the original media packets. Base station 206 may allocate resources to reception of the GTP-U packets, e.g., based on a corresponding QoS for whether ETI is enabled or disabled. Base station 206 may then send the packets to UE device 208 via1616-659WO01Qualcomm Ref. No. 2505105WO 23 / 56radio access network (RAN) connection 212. UE device 208 may receive the packets from base station 206 via RAN connection 212.
[0087] The configuration of the network devices illustrated in FIG. 3 may provide various technical benefits and advantages. By configuring UPF device 202 to maintain a state variable for an ETI and update the state variable in response to receiving a different ETI value, the devices of FIG. 3 may reduce communication overhead. The techniques of this disclosure allow sending device 200 to transmit an ETI indication only upon determining a change in QoS requirements (e.g., when a set of packets either exceeds or does not exceed a threshold size). Consequently, avoiding the inclusion of an ETI in every packet may result in power savings for network devices and UE device 208. Furthermore, the ETI information may be a single bit of an RTP header extension, such that the RTP header extension may also be used to signal other data not related to ETI. Additionally, reducing signaling data may facilitate better overall media performance. Furthermore, maintaining the state variable at UPF device 202 may enable efficient routing without requiring complex changes to a core network, as UPF device 202 may reuse existing procedures for mapping packets to respective QoS configurations after determining the ETI.
[0088] FIG. 4 is a conceptual diagram illustrating packet structures for packets sent between various network devices. For example, FIG. 4 depicts AS device 250, which may correspond to sending device 200 of FIG. 3; UPF device 252, which may correspond to UPF device 202 of FIG. 3; RAN 254, which may correspond to RAN 212 including base station 206 of FIG. 3; and UE device 256, which may correspond to UE device 208 of FIG. 3.
[0089] Additionally, FIG. 4 depicts IP packet structure 230 for packets sent by AS device 250 to UPF device 252. In this example, IP packet structure 230 encapsulates a UDP packet, which encapsulates an RTP packet including an RTP header and RTP header extension and an RTP payload. The RTP packet is encapsulated by a UDP header to form the UDP packet. The UDP packet is encapsulated with an IP header to form the IP packet. Per techniques of this disclosure, ETI flag 232 has a value that either enables or disables ETI for the current and subsequent packets. ETI flag 232 may be included in the RTP header extension or in the UDP header (for purposes of example, FIG. 4 depicts ETI flag 232 as forming part of the RTP header extension). UPF device 252 may use ETI flag 232 to determine an appropriate QoS to which to apply to this and subsequent packets (until a packet with an opposite-valued ETI flag has been received).1616-659WO01Qualcomm Ref. No. 2505105WO 24 / 56
[0090] UPF device 252 encapsulates the IP packet with GTP-U header 242 to form GTP-U packet 240. GTP-U header 242 may include, among other data, quality of service (QoS) information, such as a 5G QoS Identifier (5QI) based on the value of ETI flag 232. For example, if ETI flag 232 indicates that ETI is enabled, GTP-U header 242 may specify a first 5QI, whereas if ETI flag 232 indicates that ETI is disabled, GTP-U header 242 may specify a second, different 5QI. Routers along a network tunnel between UPF device 252 and the base station of RAN 254 may use the 5QI value to determine a priority for sending packets. For example, if multiple packets are received simultaneously (e.g., from different sources), the routers may output packets having lower 5QI values (that is, higher priority) before outputting packets having higher 5QI values. The base station of RAN 254 may use the 5QI value for scheduling reception of GTP-U packets and to inform UE device 256 as to how to schedule reception of forthcoming packet(s).
[0091] FIG. 5 is a conceptual diagram illustrating an example QUIC packet 260. QUIC packet 260 may be referred to as a “1-RTT QUIC packet.” As shown in FIG. 5, QUIC packet 260 includes unencrypted data (labeled “QUIC (open)” and encrypted data (labeled “QUIC (encrypted)”). As shown in FIG. 5, QUIC header 262 for QUIC packet 260 includes both encrypted and unencrypted data. QUIC packet 260 includes QUIC header 262 including flags, Destination Connection ID 264, QUIC header extensions 266, and packet number 268, as well as payload 270 following QUIC header 262. In QUIC header 262, only part of the flags and Destination Connection ID 264 are unencrypted, as shown in FIG. 5. The flags include only 3 unencrypted bits in a 1-RTT packet format: Header Form (1) = 0; Fixed Bit (1) = 1; and Spin Bit (1). The spin bit need not be encrypted, because it has been determined that the spin bit does not leak any information to the network.
[0092] Per the techniques of this disclosure, one or more QUIC header extensions 266 may be added to QUIC packet 260 of FIG. 5, as shown in the example of FIG. 5. For example, such QUIC header extensions 266 may include unencrypted application layer information that may improve cross-layer efficiency if exposed to the network, e.g., an ETI flag, per techniques of this disclosure. QUIC header 262 itself may include data indicating the presence of QUIC header extensions 266. For example, QUIC header 262 may include a QUIC version number, where the QUIC version number indicates whether and / or how many QUIC header extensions 266 are present. Additionally or alternatively, QUIC header 262 may include a dedicated indicator that indicates whether one or more1616-659WO01Qualcomm Ref. No. 2505105WO 25 / 56QUIC header extensions 266 are included. For example, the dedicated indicator may be one of two reserved bits in the 1-RTT packet header.
[0093] QUIC packet 260 may carry one or more header extensions (e.g., extension elements). Each header extension may include a header and header extension data. The header may include an extension identifier that identifies the type of the header extension in a QUIC connection and an extension length indicating the length of the header extension, e.g., in bytes or other relevant size units (bits, words, etc.) The header extension data may include data or metadata to be communicated to the network transporting the QUIC packet. Multiple extension formats may be used, e.g., a one-byte format including the extension ID and extension length together in one-byte, or a two-byte format including the extension ID and extension length together in two bytes.
[0094] In some examples, all of QUIC header extensions 266 are unencrypted. An application or device receiving one or more of QUIC header extensions 266 may determine whether to use unencrypted QUIC header extension information, based on its implementation. In some examples, QUIC header 262 indicates which of QUIC header extensions 266 are encrypted or not encrypted, e.g., using a bitmap. For example, the bitmap may be an array of bits each corresponding to one of QUIC header extensions 266, where a value of 1 for the bit indicates that the QUIC header extension is encrypted and a value of 0 for the bit indicates that the QUIC header extension is unencrypted. In some examples, QUIC header extensions 266 may be ignored by an endpoint that does not support QUIC header extensions 266, and does not change the meaning of the conventional QUIC header fields.
[0095] In some examples, a QUIC packet with one or more header extensions may have a format similar to the following format:1-RTT Packet {Header Form (1) = 0,Fixed Bit (1) = 1,Spin Bit (1),Reserved Bits (2) = 10,Key Phase (1),Packet Number Length (2),Destination Connection ID (0 .. 160),Packet Number (8 .. 32),Extension ID (4) = 1,1616-659WO01Qualcomm Ref. No. 2505105WO 26 / 56Extension Length (4) = 12,Extension data (96),Extension ID (4) = 2,Extension Length (4) = 4,Extension data (32),Packet Payload (8 ..),}
[0096] In this example, the format represents a QUIC packet having two QUIC header extensions, indicated by respective extension ID, extension length, and extension data fields. The first QUIC header extension includes an extension ID value of 1 (represented by four bits), an extension length value of 12 (indicating that the extension data field has 12 bytes, i.e., 96 bits) and an extension data field of 96 bits of data. The second QUIC header extension includes an extension ID value of 2, an extension length value of 4 (indicating that the extension data field has 4 bytes, i.e., 32 bits), and an extension data field of 32 bits of data. In the format above, a field is represented by the field name, followed by a value in parentheses (indicating a number of bits for that field), and an optional assigned value for the field indicated by an equals sign followed by the value.
[0097] Negotiation of the use of QUIC header extensions 266 may be performed between two endpoint devices, such as between a UE device (e.g., UE device 208 of FIG. 3) and an AS device (e.g., sending device 200 of FIG. 3). In some examples, this negotiation may be performed in-band, where negotiation frames are exchanged during session setup. Negotiation data may be carried in some QUIC packets (e.g., initial packet, handshake packet(s), and / or 1-RTT packet(s)) during the handshake phase. In some examples, two frames are defined and sent as part of the normal payload of the initial packets. The two frames may include a “QUIC header extension request” frame, which carries the header extension IDs and respective definitions of the extensions.
[0098] The QUIC header extension request frame may be included in the initial packet from the client to the server, where the definition may be indicated by a URL, uniform resource identifier (URI), or uniform resource name (URN) (which may be registered with Internet Assigned Numbers Authority (LANA)). The two frames may also include a “QUIC header extension response” frame, which confirms support for the types of header extensions through indication of the respective header extension IDs, and may be included in the initial packet from the server to the client. Although the two initial packets are encrypted, this encryption generally uses a key derived from a cleartext connection ID 1616-659WO01Qualcomm Ref. No. 2505105WO 27 / 56and a well-known salt number, such that intermediate routers (e.g., UPF device 202) can inspect the packet(s) and decode the payload (carrying the request / response frames) to determine the meaning of the header extensions.
[0099] Alternatively, the two frames may be as indicated above, but the frames need not be encrypted in the QUIC packets (e.g., initial packet, handshake packet, and 1-RTT packet). This may reduce the complexity at intermediate routers (e.g., UPF device 202 of FIG. 3), but may change encryption procedures at QUIC endpoints (e.g., UE device 208 and sending device 200).
[0100] Per techniques of this disclosure, one of QUIC header extensions 266 may include data representing an ETI flag, e.g., a single bit indicating whether to enable or disable ETI (or expedited data transfer).
[0101] FIG. 6 is a conceptual diagram illustrating an example of use of UDP packet 300 including QUIC header extensions including ETI information per techniques of this disclosure. In some examples, a protocol description may include data indicating the protocol (QUIC), the type of the QUIC header extension being for PDU Set marking (PDU SET MARKING), which may further include ETI information, and a QUIC header extension identifier, e.g., 3. An AF device may extract the protocol description and send data representing the protocol description to the PCF device. The PCF device may generate the PCC rules and configure a session management function (SMF) device accordingly. The SMF device may configure UPF device 322 on how to identify QUIC packets with PDU Set marking.
[0102] UPF device 322 may identify (based on the protocol description) QUIC packets 300 with the QUIC header extensions including PDU Set marking data and ETI information 302 (e.g., an ETI flag). UPF device 322 may then extract the PDU Set marking information from the QUIC header extensions. UPF device 322 may then determine an appropriate QoS to apply to this and subsequent packets, based on the value of ETI information 302, e.g., QoS corresponding to 5QI 6 or 7. UPF device 322 may further encapsulate each UDP packet 300 into GTP-U packet 310 and add the extracted PDU Set marking information and / or burst information in GTP-U packet header 312. Routers along a network tunnel between UPF device 322 and RAN 324 may prioritize sending of packets based on QoS information signaled in GTP-U packet header 312. A base station of RAN 324 may use the PDU Set information extracted from the GTP-U packet header for scheduling, e.g., dropping an entire PDU Set with a high PDU Set1616-659WO01Qualcomm Ref. No. 2505105WO 28 / 56Importance (PSI) value (low importance level) among PDU Sets being received during a period of high network congestion, or otherwise adapting the behavior of UE 326.
[0103] The configuration of the packet structures and network devices illustrated in FIG.6 may provide various technical benefits and advantages. By using the example arrangement of ETI information 302 within a QUIC header extension of UDP packet 300, UPF device 322 may determine an appropriate quality of service (QoS) to apply to a current packet and subsequent packets until receiving a different ETI indication. This configuration may reduce communication overhead because UPF device 322 does not require ETI information 302 in every single packet of a service data flow. Avoiding a mandatory inclusion of a QUIC header extension for every packet reduces bandwidth consumption and increases network efficiency.
[0104] Furthermore, by using a single network tunnel for both a first QoS configuration and a second QoS configuration, UPF device 322 may simplify routing operations within a core network. UPF device 322 may seamlessly update QoS information within GTP-U packet header 312 without requiring complex network tunnel modifications. Implementing the techniques of this disclosure may result in better media performance and provide power savings for network devices, e.g., routers along the network tunnel, and UE 326.
[0105] FIG. 7 is a graph illustrating an example indication of how ETI information may be used to determine an appropriate QoS per techniques of this disclosure. The X-axis of the graph represents time, vertical arrows represent packets sent over time, and the Y-axis of the graph represents a QoS applied to the packets. In particular, the arrows have different line styles to indicate whether the packets include ETI enabling or disabling information, or no ETI information. Dot-dashed arrows indicate packets including ETI enabling information, dashed arrows indicate packets including ETI disabling information, and solid arrows represent packets without ETI information.
[0106] Per techniques of this disclosure, in this example, packet 400 of a group of packets 400, 410 includes data indicating that ETI is to be enabled (e.g., ETI=TRUE). Thus, a QoS corresponding to a 5QI of 7 is applied to packet 400 and subsequent packets 410. The QoS corresponding to a 5QI of 7 may have a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3.
[0107] The QoS corresponding to a 5QI of 7 may be applied until packet 420 is received, which includes data indicating that ETI is to be disabled (e.g., ETI=FALSE). Thus, packet 420 and subsequent packets (e.g., packet 430) are processed using a QoS corresponding 1616-659WO01Qualcomm Ref. No. 2505105WO 29 / 56to a 5QI of 6. The QoS corresponding to a 5QI of 6 may have a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6.
[0108] The QoS corresponding to a 5QI of 6 may be applied until packet 440 is received, which includes data indicating that ETI is to be enabled. Thus, packet 440 and packet 450 may be processed using a QoS corresponding to a 5QI of 7.
[0109] FIG. 8 is a conceptual diagram illustrating a one-byte format for an RTP header extension 500 including an ETI flag 512 per techniques of this disclosure. In particular, ETI flag 512 may be a single bit having a value of 1 to indicate that ETI is true (and thus, that this and subsequent packets should be processed with a high QoS, e.g., a QoS corresponding to a 5QI of 7) or a value of 0 to indicate that ETI is false (and thus, that this and subsequent packets should be processed with a low QoS, e.g., a QoS corresponding to a 5 QI of 6).
[0110] RTP header extension 500 may be a data burst (also referred to as a “dynamically changing traffic characteristic”) header extension or a PDU Set marking header extension, which are defined in 3GPP TS 26.522. These extensions include a set of reserved bits. Per techniques of this disclosure, one of the reserved bits indicated in 3GPP TS 26.522 may be used to indicate the ETI indication. The use of the reserved bit, e.g., for use as an ETI flag, may be negotiated between RTP sender and RTP receiver via SDP Offer / Answer messages.[OHl] RTP header extension 500 may be an RTP header extension dedicated to ETI, which can take the 1-byte format or 2-byte format. The use of such an RTP header extension may be negotiated between RTP sender and RTP receiver via SDP Offer / Answer messages.
[0112] As illustrated in FIG. 8, RTP header extension 500 may conform to an RTP header extension format including OxBE hex value 502, OxDE hex value 504, length value 506, identifier value 508, length value 510, ETI flag 512, and padding bits 514. Length value 506 may be a 16-bit length value. Identifier value 508 may be a four-bit identifier value, length value 510 may be a four-bit value indicating 0. ETI flag 512 may be a single bit having a value indicating whether ETI is enabled or disabled (e.g., ‘1’ indicates ETI is enabled and ‘0’ indicates that ETI is disabled). Padding bits 514 may be 7 padding bits whose value is not used in this example (or may be reserved for future use). Because the ETI flag may be represented by a single bit of information, it is not necessary to define a new, dedicated RTP header extension solely for the ETI flag, because doing so may be inefficient and consume unnecessary bandwidth. By leveraging a reserved bit within an 1616-659WO01Qualcomm Ref. No. 2505105WO 30 / 56existing header extension (such as the data burst or PDU Set marking header extensions), the techniques of this disclosure may reduce protocol overhead, avoid transmission of header extensions with all packets of a communication session, and improve overall network communication efficiency.
[0113] In other examples, a packet including ETI data may be a QUIC packet. The ETI data may be carried in any of a QUIC header extension, a UDP option field of a UDP packet encapsulating the QUIC packet, a metadata portion of a Media over QUIC (MoQ) object conveyed by a PDU of the QUIC packet, in an HTTP datagram in a payload of the QUIC packet, or in a field in a header of the QUIC packet.
[0114] FIG. 9 is a flow diagram illustrating an example process for exchanging media data according to techniques of this disclosure. The method of FIG. 9 may be performed by various devices, such as UE device 208, AF device 218, base station 206, PCF device 216, SMF device 214, UPF device 202, and sending device 200 of FIG. 3.
[0115] UPF device 202 may be a router configured to execute a user plane function. UPF device 202 of FIG. 3 may maintain a state variable for each ETI for each media flow configured by a PDR including ETI. UPF device 202 may update the state variable for a media flow when a different value for the ETI is received. The media flow may be a QoS flow.
[0116] In this example, initially, UE device 208 sends a protocol description to AF device 218 requesting ETI for a media communication session (520). Prior to sending the protocol description, UE device 208 and sending device 200 may negotiate (e.g., using SDP offer and answer messages) the use of ETI and how ETI will be signaled (e.g., in RTP header extensions, QUIC header extensions, or the like). AF device 218 may then forward the protocol description to PCF device 216 (522). PCF device 216 may generate two PCC rules as discussed above, one for each QoS (high QoS and low QoS). PCF device 216 may provide the PCC rules to SMF device 214 (524). SMF device 214 may, in turn, generate two PDRs corresponding to the PCC rules, one for high QoS and one for low QoS. SMF device 214 may then provide the PDRs to UPF device 202 (526).
[0117] UPF device 202 may then receive a packet including a PDU (526) and use the PDRs to detect whether the packet including the PDU includes an ETI value, and if so, whether the ETI value changes the ETI state for the corresponding media flow (i.e., a different ETI value) (528). If the ETI value is present and changes the ETI state, UPF device 202 may map the corresponding media flow to the other QoS. For example, if the current ETI is ETI enabled and a packet including an ETI value indicating that ETI is to 1616-659WO01Qualcomm Ref. No. 2505105WO 31 / 56be disabled, UPF device 202 may map the flow from a high QoS to a low QoS. As another example, if the current ETI is ETI disabled and a packet including an ETI value indicating that ETI is to be enabled, UPF device 202 may map the flow from a low QoS to a high QoS. UPF device 202 may then forward the packet (which may be encapsulated as a GTP-U packet) and subsequent packets to base station 206 (which may be a Next Generation NodeB (gNB) or other such device) (530). Base station 206 may forward the packets to UE device 208 (532).
[0118] In particular, sending device 200 may determine whether to enable or disable ETI based on an amount of data that is ready to be sent to UE device 208. If there is a relatively large amount of data to be sent in a short period of time (e.g., in excess of a threshold), sending device 200 may construct an ordinal first packet of an upcoming group of packets to include ETI data indicating that ETI is to be enabled. After that data has been sent, sending device 200 may determine whether ETI can be disabled, e.g., if an upcoming amount of data over a period of time is below the threshold. If so, sending device 200 may send a packet including ETI data indicating that ETI is to be disabled.
[0119] To provide redundancy and robustness against packet loss, sending device 200 may include the ETI data in a plurality of initial packets of the set of packets, rather than solely the ordinal first packet. For example, when changing the ETI state from disabled to enabled, sending device 200 may include the ETI data indicating that ETI is to be enabled in the first two, three, or more packets of the group of packets. In this manner, if the ordinal first packet is lost in transit, UPF device 202 may still receive the ETI state change from a subsequent packet of the plurality of initial packets, ensuring the new QoS configuration is applied to the remainder of the group of packets.
[0120] In this manner, the method of FIG. 9 represents an example of a method of exchanging media data including: in response to receiving a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF, processing subsequent packets of the SDF using a first quality of service (QoS) configuration; and in response to receiving a second packet of the SDF including data representing that ETI is disabled (i.e., not enabled) for the SDF, processing subsequent packets of the SDF using a second QoS configuration different than the first QoS configuration.
[0121] Likewise, the method of FIG. 9 also represents an example of a method of exchanging media data, including: receiving, by a user plane function (UPF) device, a first packet of a service data flow (SDF) including data representing that an expedited 1616-659WO01Qualcomm Ref. No. 2505105WO 32 / 56transfer indication (ETI) is enabled for the SDF; encapsulating, by the UPF device, the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, including specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forwarding, by the UPF device, the first GTP-U packet to a destination of the SDF; receiving, by the UPF device, a second packet of the SDF including data representing that ETI is disabled for the SDF; encapsulating, by the UPF device, the second packet in a second GTP-U packet, including specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forwarding, by the UPF device, the second GTP-U packet to the destination of the SDF.
[0122] Furthermore, the method of FIG. 9 also represents an example of a method of sending media data, including: determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device; determining that a second set of packets of the SDF correspond to a set of data having a size below the threshold; adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and sending the second set of packets to the UE device via the UPF device.
[0123] FIG. 10 is a flowchart illustrating an example method of encapsulating packets into General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packets based on ETI information per techniques of this disclosure. User plane function (UPF) device 202 of FIG. 3 may perform the method of FIG. 10. Other example UPF devices, such as UPF device 252 of FIG. 4 or UPF device 322 of FIG. 6, may also perform the method of FIG. 10.
[0124] UPF device 202 may initially receive quality of service (QoS) packet detection rules (550). Receiving the QoS packet detection rules may include receiving a first packet detection rule (PDR) for a service data flow (SDF). The first PDR is associated with a first QoS configuration. Receiving the QoS packet detection rules may also include receiving a second PDR for the SDF. The second PDR is associated with a second QoS1616-659WO01Qualcomm Ref. No. 2505105WO 33 / 56configuration. The first QoS configuration and the second QoS configuration may correspond to respective 5QI indications, as discussed above.
[0125] Subsequently, UPF device 202 receives a packet of a media communication session (552). UPF device 202 determines whether the packet includes data indicating that an expedited transfer indication (ETI) is enabled (554).
[0126] When the packet includes data indicating that ETI is enabled (YES branch of 554), UPF device 202 encapsulates the packet with a GTP-U header including a high priority 5G QoS Identifier (5QI) (560). Encapsulating the packet represents encapsulating the first packet in a GTP-U packet. Encapsulating the packet in the GTP-U packet includes specifying first QoS information in a header of the GTP-U packet based on the packet including the data representing that ETI is enabled. The first QoS information may be a configuration corresponding to a first 5QI. The first 5QI may equal 6. The first QoS configuration may, for example, have a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6.
[0127] Each packet of the media communication session may be encapsulated by a first real-time transport protocol (RTP) header. Packets including ETI information may further include an RTP header extension including the data representing whether ETI is enabled. The RTP header extension may conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
[0128] In some examples, the packets may be QUIC packets including a QUIC header extension including the data representing whether ETI is enabled. In some examples, the packets may be user datagram protocol (UDP) packets including a UDP option field including the data representing whether ETI is enabled. Alternatively, in some examples, the packets may include a Media over QUIC (MoQ) object including a first metadata portion including the data representing whether ETI is enabled. In some examples, the packets may be QUIC packets including an HTTP datagram including the data representing whether ETI is enabled.
[0129] UPF device 202 forwards the GTP-U packet (562) to a destination of the SDF. The destination of the SDF may be a user equipment (UE) device, such as UE device 208 of FIG. 3. Forwarding the first GTP-U packet to UE device 208 may include forwarding the first GTP-U packet via a network tunnel communicatively coupled to base station 206 of a RAN coupling base station 206 to UE device 208.1616-659WO01Qualcomm Ref. No. 2505105WO 34 / 56
[0130] After having received a packet for which ETI is enabled, UPF device 202 may receive a subsequent packet of the media communication session (564). UPF device 202 may then determine whether the subsequent packet includes ETI information (566). Based on the subsequent packet lacking ETI information (NO branch of 566), UPF device 202 continues to encapsulate the subsequent packet with the GTP-U header including the high priority 5QI (560). Based on the subsequent packet including ETI information (YES branch of 566), UPF device 202 determines whether the subsequent packet indicates ETI is enabled (554).
[0131] When a received packet includes data indicating that ETI is disabled (NO branch of 554), UPF device 202 encapsulates the packet with a GTP-U header including a lower priority 5QI (570). Encapsulating the packet represents encapsulating the second packet in a GTP-U packet. Encapsulating the packet in the GTP-U packet may include specifying second QoS information in a header of the GTP-U packet based on the packet including the data representing that ETI is disabled. The second QoS information is different than the first QoS information and indicates a relatively lower QoS than the first QoS information. For example, the second QoS information may be a configuration corresponding to a second 5QI. The second 5QI may equal 7. The second QoS configuration may have a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3.
[0132] UPF device 202 forwards the GTP-U packet (572) to the destination of the SDF, e.g., UE device 208. Forwarding the second GTP-U packet to UE device 208 may include forwarding the second GTP-U packet via the network tunnel communicatively coupling UPF device 202 to base station 206.
[0133] After forwarding the GTP-U packet including the relatively lower QoS information, UPF device 202 may receive a subsequent packet of the media communication session (574). UPF device 202 may then determine whether the subsequent packet includes ETI information (576). When the subsequent packet does not include ETI information (NO branch of 576), UPF device 202 continues to encapsulate the subsequent packet with the GTP-U header including the lower priority 5QI (570). However, if the subsequent packet includes ETI information (YES branch of 576), UPF device 202 determines whether the subsequent packet indicates ETI is enabled (554), and then whether the ETI information indicates that ETI is enabled or disabled, and encapsulates the subsequent packet to form a GTP-U packet either including the high QoS information or the lower QoS information based on whether ETI is enabled or disabled.1616-659WO01Qualcomm Ref. No. 2505105WO 35 / 56
[0134] In this manner, the method of FIG. 10 represents an example of a method of exchanging media data, including: receiving, by a user plane function (UPF) device, a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF; encapsulating, by the UPF device, the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, including specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forwarding, by the UPF device, the first GTP-U packet to a destination of the SDF; receiving, by the UPF device, a second packet of the SDF including data representing that ETI is disabled for the SDF; encapsulating, by the UPF device, the second packet in a second GTP-U packet, including specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forwarding, by the UPF device, the second GTP-U packet to the destination of the SDF.
[0135] FIG. 11 is a flowchart illustrating another example method of encapsulating packets into GTP-U packets per techniques of this disclosure. The method of FIG. 11 is explained with respect to UPF device 202 of FIG. 3. However, other UPF devices, such as UPF device 252 of FIG. 4 or UPF device 322 of FIG. 6, may also perform the method of FIG. 11.
[0136] Initially, UPF device 202 receives a first packet of a service data flow (SDF). In this example, the first packet includes data indicating that an expedited transfer indication (ETI) is enabled (580). Prior to receiving the first packet, UPF device 202 may receive a first packet detection rule (PDR) for the SDF. The first PDR may be associated with a first quality of service (QoS) configuration and indicate that packets including data indicating that ETI is enabled correspond to the first QoS configuration. UPF device 202 may also receive a second PDR for the SDF. The second PDR may be associated with a second QoS configuration and indicate that packets including data indicating that ETI is disabled correspond to the second QoS configuration.
[0137] UPF device 202 encapsulates the first packet with a GTP-U header including first QoS information (582) in a first GTP-U packet. Encapsulating the first packet in the first GTP-U packet may include specifying the first QoS information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled. The first QoS information may be a configuration corresponding to a first 5G 1616-659WO01Qualcomm Ref. No. 2505105WO 36 / 56QoS Identifier (5QI). The first 5QI may be 6. The first QoS configuration may have a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6.
[0138] The first packet may be encapsulated by a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled. The first RTP header extension may conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits. In other examples, the first packet may be a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled. The first packet may be a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled. The first packet may include a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled. The first packet may be a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled.
[0139] UPF device 202 forwards the first GTP-U packet to a destination (584), such as UE device 208 of FIG. 3. Forwarding the first GTP-U packet to UE device 208 may include forwarding the first GTP-U packet via network tunnel 204 communicatively coupled to base station 206. UE device 208 may be communicatively coupled to base station 206 via radio access network (RAN) 212.
[0140] In this example, subsequently, UPF device 202 receives a second packet of the SDF indicating that ETI is disabled (586). UPF device 202 encapsulates the second packet with a GTP-U header including second QoS information (588) in a second GTP-U packet. Encapsulating the second packet in the second GTP-U packet may include specifying the second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled. The second QoS information is different than the first QoS information. The second QoS information may be a configuration corresponding to a second 5QI. The second 5QI may be 7. The second QoS configuration may have a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3.
[0141] The second packet may be encapsulated by a second RTP header including a second RTP header extension including the data representing that ETI is disabled. The second RTP header extension may conform to the RTP header extension format including the OxBE hex value, the OxDE hex value, the 16-bit length value, the four-bit identifier 1616-659WO01Qualcomm Ref. No. 2505105WO 37 / 56value, the four-bit length, the single bit to indicate whether ETI is enabled or disabled, and the 7 padding bits. In other examples, the second packet comprises a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled. The second packet may comprise a second UDP packet including a second UDP option field including the data representing that ETI is disabled. The second packet may include a second MoQ object including a second metadata portion including the data representing that ETI is disabled. The second packet may comprise a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled. UPF device 202 then forwards the second GTP-U packet to the destination (590), e.g., UE device 208, e.g., via network tunnel 204 that communicatively couples UPF device 202 to base station 206.
[0142] In this manner, the method of FIG. 11 represents an example of a method of exchanging media data, including: receiving, by a user plane function (UPF) device, a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF; encapsulating, by the UPF device, the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, including specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forwarding, by the UPF device, the first GTP-U packet to a destination of the SDF; receiving, by the UPF device, a second packet of the SDF including data representing that ETI is disabled for the SDF; encapsulating, by the UPF device, the second packet in a second GTP-U packet, including specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forwarding, by the UPF device, the second GTP-U packet to the destination of the SDF.
[0143] FIG. 12 is a flowchart illustrating an example method of sending packets of a media communication session including expedited transfer indication (ETI) information per techniques of this disclosure. The method of FIG. 12 is described with respect to sending device 200 of FIG. 3. Other devices, such as server device 60 of FIG. 1, AS device 250 of FIG. 4, or application server 320 of FIG. 6, may also be configured to perform the method of FIG. 12.
[0144] In this example, initially, sending device 200 determines that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold 1616-659WO01Qualcomm Ref. No. 2505105WO 38 / 56(600). The set of data may represent a relatively high payload over a short amount of time, such as a data rate or a bitrate exceeding a configured threshold.
[0145] Based on the determination that the size of the set of data is above the threshold, sending device 200 adds data to at least an ordinal first packet of the first set of packets representing that ETI is enabled for the first set of packets (602). Adding the data representing that ETI is enabled may include encapsulating the ordinal first packet with a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled, such as RTP header extension 500 of FIG. 8. The first RTP header extension may conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
[0146] In other examples, adding the data representing that ETI is enabled may include formulating the ordinal first packet as a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled, e.g., as discussed with respect to FIG. 6. In some examples, adding the data representing that ETI is enabled may include formulating the ordinal first packet as a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled. In some examples, the ordinal first packet may be a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled. Generating the ordinal first packet may include formatting a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled.
[0147] Sending device 200 then sends the first set of packets to a user equipment (UE) device, e.g., UE device 208, via a user plane function (UPF) device, e.g., UPF device 202, to cause UPF device 202 to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled (604). The first QoS configuration may be a configuration corresponding to a first 5G QoS Identifier (5QI). The first 5QI may be a value of 6. The first QoS configuration may have a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6.
[0148] In this example, sending device 200 then determines that a second set of packets of the SDF corresponds to a set of data having a size below the threshold (606). The set of data having the size below the threshold may represent a relatively low payload or a relatively low bitrate for the media communication session.1616-659WO01Qualcomm Ref. No. 2505105WO 39 / 56
[0149] Based on the determination that the size of the set of data is below the threshold, sending device 200 adds data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets (608). Adding the data representing that ETI is disabled may include encapsulating the ordinal first packet of the second set of packets with a second RTP header including a second RTP header extension including the data representing that ETI is disabled. The second RTP header extension may conform to the RTP header extension format including the OxBE hex value, the OxDE hex value, the 16-bit length value, the four-bit identifier value, the four-bit length value, the single bit to indicate whether ETI is enabled or disabled, and the 7 padding bits.
[0150] In other examples, adding the data representing that ETI is disabled may include formulating the ordinal first packet of the second set of packets as a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled. In some examples, adding the data representing that ETI is disabled may include formulating the ordinal first packet of the second set of packets as a second UDP packet including a second UDP option field including the data representing that ETI is disabled. The ordinal first packet of the second set of packets may include a second MoQ object including a second metadata portion including the data representing that ETI is disabled. The ordinal first packet of the second set of packets may comprise a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled.
[0151] Sending device 200 may then send the second set of packets, including the ordinal first packet including the data indicating that ETI is disabled, to UE device 208 via UPF device 202 (610). The second QoS configuration is different from the first QoS configuration. The second QoS configuration may include a configuration corresponding to a second 5QI. The second 5QI may have a value of 7. The second QoS configuration may have a default priority level of 70, a delay budget of 100 ms, and a packet error rate of IO’3.
[0152] In this manner, the method of FIG. 12 represents an example of a method of sending media data, including: determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled; determining that a second set of packets of the SDF 1616-659WO01Qualcomm Ref. No. 2505105WO 40 / 56correspond to a set of data having a size below the threshold; adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and sending the second set of packets to the UE device via the UPF device to cause the UPF to apply a second QoS configuration to the second set of packets based on ETI being disabled.
[0153] Various examples of the techniques of this disclosure are summarized in the following clauses:
[0154] Clause 1 : A method of exchanging media data, the method comprising: in response to receiving a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF, processing subsequent packets of the SDF using a first quality of service (QoS) configuration; and in response to receiving a second packet of the SDF including data representing that ETI is disabled for the SDF, processing subsequent packets of the SDF using a second QoS configuration different than the first QoS configuration.
[0155] Clause 2: The method of clause 1, further comprising encapsulating the packets of the SDF to form tunneled packets and sending the tunneled packets to a user equipment (UE) device via a network tunnel communicatively coupled to a base station, wherein the UE device is communicatively coupled to the base station via a radio access network (RAN).
[0156] Clause 3: The method of any of clauses 1 and 2, further comprising receiving a first packet detection rule (PDR) for the SDF, the first PDR being associated with the first QoS configuration, and receiving a second PDR for the SDF, the second PDR being associated with the second QoS configuration.
[0157] Clause 4: A method of sending media data, the method comprising: determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device; determining that a second set of packets of the SDF correspond to a set of data having a size below the threshold; adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and sending the second set of packets to the UE device via the UPF device.1616-659WO01Qualcomm Ref. No. 2505105WO 41 / 56
[0158] Clause 5: The method of any of clauses 1-4, wherein the first QoS configuration comprises a configuration corresponding to a first 5G QoS Identifier (5QI), and wherein the second QoS configuration comprises a configuration corresponding to a second 5QI.
[0159] Clause 6: The method of clause 5, wherein the first 5QI is 7, and wherein the second 5QI is 6.
[0160] Clause 7: The method of any of clauses 1-6, wherein the first QoS has a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6, and wherein the second QoS has a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3.
[0161] Clause 8: The method of any of clauses 1-7, wherein the first packet is encapsulated by a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled, and wherein the second packet is encapsulated by a second RTP header including a second RTP header extension including the data representing that ETI is disabled.
[0162] Clause 9: The method of clause 8, wherein the first RTP header extension and the second RTP header extension conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
[0163] Clause 10: The method of any of clauses 1-7, wherein the first packet comprises a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled.
[0164] Clause 11: The method of any of clauses 1-7, wherein the first packet comprises a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled, and the second packet comprises a second UDP packet including a second UDP option field including the data representing that ETI is disabled.
[0165] Clause 12: The method of any of clauses 1-7, wherein the first packet includes a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled, and the second packet includes a second MoQ object including a second metadata portion including the data representing that ETI is disabled.1616-659WO01Qualcomm Ref. No. 2505105WO 42 / 56
[0166] Clause 13: The method of any of clauses 1-7, wherein the first packet comprises a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled.
[0167] Clause 14: A device for exchanging media data, the device comprising one or more means for performing the method of any of clauses 1-13.
[0168] Clause 15: The device of clause 14, wherein the one or more means comprise a processing system including one or more processors implemented in circuitry.
[0169] Clause 16: The device of any of clauses 14 and 15, further comprising a memory configured to store media data.
[0170] Clause 17: The device of any of clauses 14-16, wherein the device comprises at least one of: an integrated circuit; a microprocessor; or a wireless communication device.
[0171] Clause 18: A device for exchanging media data, the device comprising: means for, in response to receiving a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF, processing subsequent packets of the SDF using a first quality of service (QoS) configuration; and means for, in response to receiving a second packet of the SDF including data representing that ETI is disabled for the SDF, processing subsequent packets of the SDF using a second QoS configuration different than the first QoS configuration.
[0172] Clause 19: A device for exchanging media data, the device comprising: means for determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; means for adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; means for sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device; means for determining that a second set of packets of the SDF correspond to a set of data having a size below the threshold; means for adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and means for sending the second set of packets to the UE device via the UPF device.
[0173] Clause 20: A computer-readable storage medium having stored thereon instructions that, when executed, cause a processor to perform the method of any of clauses 1-13.
[0174] Clause 21 : Amethod of exchanging media data, the method comprising: receiving, by a user plane function (UPF) device, a first packet of a service data flow (SDF) 1616-659WO01Qualcomm Ref. No. 2505105WO 43 / 56including data representing that an expedited transfer indication (ETI) is enabled for the SDF; encapsulating, by the UPF device, the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, including specifying first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forwarding, by the UPF device, the first GTP-U packet to a destination of the SDF; receiving, by the UPF device, a second packet of the SDF including data representing that ETI is disabled for the SDF; encapsulating, by the UPF device, the second packet in a second GTP-U packet, including specifying second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forwarding, by the UPF device, the second GTP-U packet to the destination of the SDF.
[0175] Clause 22: The method of clause 21, wherein the destination of the SDF comprises a user equipment (UE) device, wherein forwarding the first GTP-U packet to the UE device comprises forwarding the first GTP-U packet via a network tunnel communicatively coupled to a base station, wherein the UE device is communicatively coupled to the base station via a radio access network (RAN), and wherein forwarding the second GTP-U packet to the UE device comprises forwarding the second GTP-U packet via the network tunnel.
[0176] Clause 23: The method of any of clauses 21 and 22, further comprising receiving a first packet detection rule (PDR) for the SDF, the first PDR being associated with the first QoS configuration, and receiving a second PDR for the SDF, the second PDR being associated with the second QoS configuration.
[0177] Clause 24: The method of any of clauses 21-23, wherein the first QoS information comprises a first 5G QoS Identifier (5QI), and wherein the second QoS information comprises a second 5 QI.
[0178] Clause 25: The method of clause 24, wherein the first 5QI is 7, and wherein the second 5QI is 6.
[0179] Clause 26: The method of any of clauses 21-25, wherein the first QoS information corresponds to a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6, and wherein the second QoS information corresponds to a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3.1616-659WO01Qualcomm Ref. No. 2505105WO 44 / 56
[0180] Clause 27: The method of any of clauses 21-26, wherein the first packet is encapsulated by a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled, and wherein the second packet is encapsulated by a second RTP header including a second RTP header extension including the data representing that ETI is disabled.
[0181] Clause 28: The method of clause 27, wherein the first RTP header extension and the second RTP header extension conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
[0182] Clause 29: The method of any of clauses 21-26, wherein the first packet comprises a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled.
[0183] Clause 30: The method of any of clauses 21-26, wherein the first packet comprises a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled, and the second packet comprises a second UDP packet including a second UDP option field including the data representing that ETI is disabled.
[0184] Clause 31 : The method of any of clauses 21-26, wherein the first packet includes a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled, and the second packet includes a second MoQ object including a second metadata portion including the data representing that ETI is disabled.
[0185] Clause 32: The method of any of clauses 21-26, wherein the first packet comprises a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled.
[0186] Clause 33: A user plane function (UPF) device for exchanging media data, the UPF device comprising: a memory configured to store packets; and a processing system implemented in circuitry and configured to: receive a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF; encapsulate the first packet in a first General Packet Radio Service (GPRS) 1616-659WO01Qualcomm Ref. No. 2505105WO 45 / 56Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, wherein the processing system is configured to specify first quality of service (QoS) information in a header of the first GTP-U packet based on the first packet including the data representing that ETI is enabled; forward the first GTP-U packet to a destination of the SDF; receive a second packet of the SDF including data representing that ETI is disabled for the SDF; encapsulate the second packet in a second GTP-U packet, wherein the processing system is configured to specify second QoS information in a header of the second GTP-U packet based on the second packet including the data representing that ETI is disabled, the second QoS information being different than the first QoS information; and forward the second GTP-U packet to the destination of the SDF.
[0187] Clause 34: The UPF device of clause 33, wherein the destination of the SDF comprises a user equipment (UE) device, wherein to forward the first GTP-U packet to the UE device, the processing system is configured to forward the first GTP-U packet via a network tunnel communicatively coupled to a base station, wherein the UE device is communicatively coupled to the base station via a radio access network (RAN), and wherein to forward the second GTP-U packet to the UE device, the processing system is configured to forward the second GTP-U packet via the network tunnel.
[0188] Clause 35: The UPF device of any of clauses 33 and 34, wherein the processing system is further configured to receive a first packet detection rule (PDR) for the SDF, the first PDR being associated with the first QoS configuration, and to receive a second PDR for the SDF, the second PDR being associated with the second QoS configuration.
[0189] Clause 36: The UPF device of any of clauses 33-35, wherein the first QoS information comprises a first 5G QoS Identifier (5QI), and wherein the second QoS information comprises a second 5QI.
[0190] Clause 37: The UPF device of any of clauses 33-36, wherein the first packet and the second packet comprise one of a set of real-time transport protocol (RTP) packets, a set of QUIC packets, a set of user datagram protocol (UDP) packets, a set of Media over QUIC (MoQ) packets, or a set of QUIC packets including HTTP datagrams.
[0191] Clause 38: A method of sending media data, the method comprising: determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF to apply a first quality of service (QoS) 1616-659WO01Qualcomm Ref. No. 2505105WO 46 / 56configuration to the first set of packets based on ETI being enabled; determining that a second set of packets of the SDF correspond to a set of data having a size below the threshold; adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and sending the second set of packets to the UE device via the UPF device to cause the UPF to apply a second QoS configuration to the second set of packets based on ETI being disabled.
[0192] Clause 39: The method of clause 38, wherein the first QoS configuration comprises a configuration corresponding to a first 5G QoS Identifier (5QI), and wherein the second QoS configuration comprises a configuration corresponding to a second 5QI.
[0193] Clause 40: The method of clause 39, wherein the first 5QI is 7, and wherein the second 5QI is 6.
[0194] Clause 41: The method of any of clauses 38-40, wherein the first QoS has a default priority level of 60, a delay budget of 300 ms, and a packet error rate of 10'6, and wherein the second QoS has a default priority level of 70, a delay budget of 100 ms, and a packet error rate of 10'3.
[0195] Clause 42: The method of any of clauses 38^11, wherein the first packet is encapsulated by a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled, and wherein the second packet is encapsulated by a second RTP header including a second RTP header extension including the data representing that ETI is disabled.
[0196] Clause 43 : The method of clause 42, wherein the first RTP header extension and the second RTP header extension conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
[0197] Clause 44: The method of any of clauses 38-41, wherein the first packet comprises a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled.
[0198] Clause 45 : The method of any of clauses 38-41 , wherein the first packet comprises a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled, and the second packet comprises a second UDP1616-659WO01Qualcomm Ref. No. 2505105WO 47 / 56packet including a second UDP option field including the data representing that ETI is disabled.
[0199] Clause 46: The method of any of clauses 38-41, wherein the first packet includes a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled, and the second packet includes a second MoQ object including a second metadata portion including the data representing that ETI is disabled.
[0200] Clause 47 : The method of any of clauses 38-41 , wherein the first packet comprises a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled.
[0201] Clause 48: A device for exchanging media data, the device comprising: a memory configured to store media data; and a processing system implemented in circuitry and configured to: determine that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold; add data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets; send the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled; determine that a second set of packets of the SDF correspond to a set of data having a size below the threshold; add data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; and send the second set of packets to the UE device via the UPF device to cause the UPF to apply a second QoS configuration to the second set of packets based on ETI being disabled.
[0202] Clause 49: The device of clause 48, wherein the processing system is further configured to send a first packet detection rule (PDR) for the SDF to the UPF device, the first PDR being associated with the first QoS configuration, and to send a second PDR for the SDF to the UPF device, the second PDR being associated with the second QoS configuration.
[0203] Clause 50: The device of clause 49, wherein the first QoS configuration comprises a configuration corresponding to a first 5G QoS Identifier (5QI), and wherein the second QoS configuration comprises a configuration corresponding to a second 5QI.
[0204] In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, 1616-659WO01Qualcomm Ref. No. 2505105WO 48 / 56the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code, and / or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.
[0205] By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0206] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for 1616-659WO01Qualcomm Ref. No. 2505105WO 49 / 56implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.
[0207] The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and / or firmware.
[0208] Various examples have been described. These and other examples are within the scope of the following claims.1616-659WO01
Claims
Qualcomm Ref. No. 2505105WO 50 / 56WHAT IS CLAIMED IS:
1. A method of exchanging media data, the method comprising:receiving, by a user plane function (UPF) device, a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF;encapsulating, by the UPF device, the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, including specifying first quality of service (QoS) information in a header of the first GTP-U packet, the first QoS information indicating that ETI is enabled for the first packet;forwarding, by the UPF device, the first GTP-U packet to a destination of the SDF ; receiving, by the UPF device, a second packet of the SDF including data representing that ETI is disabled for the SDF;encapsulating, by the UPF device, the second packet in a second GTP-U packet, including specifying second QoS information in a header of the second GTP-U packet, the second QoS information indicating that ETI is disabled for the second packet, the second QoS information being different than the first QoS information; and forwarding, by the UPF device, the second GTP-U packet to the destination of the SDF.
2. The method of claim 1,wherein the destination of the SDF comprises a user equipment (UE) device, wherein forwarding the first GTP-U packet to the UE device comprises forwarding the first GTP-U packet via a network tunnel communicatively coupled to a base station, wherein the UE device is communicatively coupled to the base station via a radio access network (RAN), andwherein forwarding the second GTP-U packet to the UE device comprises forwarding the second GTP-U packet via the network tunnel.
3. The method of claim 1, further comprising receiving a first packet detection rule (PDR) for the SDF, the first PDR being associated with the first QoS information, and receiving a second PDR for the SDF, the second PDR being associated with the second QoS information.1616-659WO01Qualcomm Ref. No. 2505105WO 51 / 564. The method of claim 1, wherein the first QoS information comprises a first 5G QoS Identifier (5QI), and wherein the second QoS information comprises a second 5QI.
5. The method of claim 4, wherein the first 5QI is 6, and wherein the second 5QI is 7.
6. The method of claim 1, wherein the first QoS information corresponds to a first priority level, a first delay budget, and a first packet error rate, and wherein the second QoS information corresponds to second priority level lower than the first priority level, a second delay budget lower than the first delay budget, and a second packet error rate lower than the first packet error rate.
7. The method of claim 1 , wherein the first packet is encapsulated by a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled, and wherein the second packet is encapsulated by a second RTP header including a second RTP header extension including the data representing that ETI is disabled.
8. The method of claim 7, wherein the first RTP header extension and the second RTP header extension conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
9. The method of claim 1, wherein the first packet comprises a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled.
10. The method of claim 1, wherein the first packet comprises a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled, and the second packet comprises a second UDP packet including a second UDP option field including the data representing that ETI is disabled.
11. The method of claim 1, wherein the first packet includes a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled, and the second packet includes a second MoQ object including a second metadata portion including the data representing that ETI is disabled.1616-659WO01Qualcomm Ref. No. 2505105WO 52 / 5612. The method of claim 1, wherein the first packet comprises a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled, and the second packet comprises a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled.
13. A user plane function (UPF) device for exchanging media data, the UPF device comprising:a memory configured to store packets; anda processing system implemented in circuitry and configured to:receive a first packet of a service data flow (SDF) including data representing that an expedited transfer indication (ETI) is enabled for the SDF;encapsulate the first packet in a first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Data Tunneling (GTP-U) packet, wherein the processing system is configured to specify first quality of service (QoS) information in a header of the first GTP-U packet, the first QoS information indicating that ETI is enabled for the first packet;forward the first GTP-U packet to a destination of the SDF; receive a second packet of the SDF including data representing that ETI is disabled for the SDF;encapsulate the second packet in a second GTP-U packet, wherein the processing system is configured to specify second QoS information in a header of the second GTP-U packet, the second QoS information indicating that ETI is disabled for the second packet, the second QoS information being different than the first QoS information; andforward the second GTP-U packet to the destination of the SDF.
14. The UPF device of claim 13,wherein the destination of the SDF comprises a user equipment (UE) device, wherein to forward the first GTP-U packet to the UE device, the processing system is configured to forward the first GTP-U packet via a network tunnel communicatively coupled to a base station, wherein the UE device is communicatively coupled to the base station via a radio access network (RAN), andwherein to forward the second GTP-U packet to the UE device, the processing system is configured to forward the second GTP-U packet via the network tunnel.1616-659WO01Qualcomm Ref. No. 2505105WO 53 / 5615. The UPF device of claim 13, wherein the processing system is further configured to receive a first packet detection rule (PDR) for the SDF, the first PDR being associated with the first QoS information, and to receive a second PDR for the SDF, the second PDR being associated with the second QoS information.
16. The UPF device of claim 13, wherein the first QoS information comprises a first 5G QoS Identifier (5QI), and wherein the second QoS information comprises a second 5QI.
17. The UPF device of claim 13, wherein the first packet and the second packet comprise one of a set of real-time transport protocol (RTP) packets, a set of QUIC packets, a set of user datagram protocol (UDP) packets, a set of Media over QUIC (MoQ) packets, or a set of QUIC packets including HTTP datagrams.
18. A method of sending media data, the method comprising:determining that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold;adding data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets;sending the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF device to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled;determining that a second set of packets of the SDF correspond to a set of data having a size below the threshold;adding data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; andsending the second set of packets to the UE device via the UPF device to cause the UPF device to apply a second QoS configuration to the second set of packets based on ETI being disabled.
19. The method of claim 18, wherein the first QoS configuration comprises a configuration corresponding to a first 5G QoS Identifier (5QI), and wherein the second QoS configuration comprises a configuration corresponding to a second 5QI.
20. The method of claim 19, wherein the first 5QI is 6, and wherein the second 5QI is 7.1616-659WO01Qualcomm Ref. No. 2505105WO 54 / 5621. The method of claim 18, wherein the first QoS information corresponds to a first priority level, a first delay budget, and a first packet error rate, and wherein the second QoS information corresponds to second priority level lower than the first priority level, a second delay budget lower than the first delay budget, and a second packet error rate lower than the first packet error rate.
22. The method of claim 18, wherein the ordinal first packet of the first set of packets is encapsulated by a first real-time transport protocol (RTP) header including a first RTP header extension including the data representing that ETI is enabled, and wherein the ordinal first packet of the second set of packets is encapsulated by a second RTP header including a second RTP header extension including the data representing that ETI is disabled.
23. The method of claim 22, wherein the first RTP header extension and the second RTP header extension conform to an RTP header extension format including a OxBE hex value, a OxDE hex value, a 16-bit length value, a four-bit identifier value, a four-bit length value, a single bit to indicate whether ETI is enabled or disabled, and 7 padding bits.
24. The method of claim 18, wherein the ordinal first packet of the first set of packets comprises a first QUIC packet including a first QUIC header extension including the data representing that ETI is enabled, and the ordinal first packet of the second set of packets comprises a second QUIC packet including a second QUIC header extension including the data representing that ETI is disabled.
25. The method of claim 18, wherein the ordinal first packet of the first set of packets comprises a first user datagram protocol (UDP) packet including a first UDP option field including the data representing that ETI is enabled, and the ordinal first packet of the second set of packets comprises a second UDP packet including a second UDP option field including the data representing that ETI is disabled.
26. The method of claim 18, wherein the ordinal first packet of the first set of packets includes a first Media over QUIC (MoQ) object including a first metadata portion including the data representing that ETI is enabled, and the ordinal first packet of the second set of packets includes a second MoQ object including a second metadata portion including the data representing that ETI is disabled.1616-659WO01Qualcomm Ref. No. 2505105WO 55 / 5627. The method of claim 18, wherein the ordinal first packet of the first set of packets comprises a first QUIC packet including a first HTTP datagram including the data representing that ETI is enabled, and the ordinal first packet of the second set of packets comprises a second QUIC packet including a second HTTP datagram including the data representing that ETI is disabled.
28. A device for exchanging media data, the device comprising:a memory configured to store media data; anda processing system implemented in circuitry and configured to:determine that a first set of packets of a service data flow (SDF) correspond to a set of data having a size above a threshold;add data to at least an ordinal first packet of the first set of packets representing that an expedited transfer indication (ETI) is enabled for the first set of packets;send the first set of packets to a user equipment (UE) device via a user plane function (UPF) device to cause the UPF device to apply a first quality of service (QoS) configuration to the first set of packets based on ETI being enabled;determine that a second set of packets of the SDF correspond to a set of data having a size below the threshold;add data to at least an ordinal first packet of the second set of packets representing that ETI is disabled for the second set of packets; andsend the second set of packets to the UE device via the UPF device to cause the UPF device to apply a second QoS configuration to the second set of packets based on ETI being disabled.
29. The device of claim 28, wherein the processing system is further configured to send a first packet detection rule (PDR) for the SDF to the UPF device, the first PDR being associated with the first QoS configuration, and to send a second PDR for the SDF to the UPF device, the second PDR being associated with the second QoS configuration.
30. The device of claim 29, wherein the first QoS configuration comprises a configuration corresponding to a first 5G QoS Identifier (5QI), and wherein the second QoS configuration comprises a configuration corresponding to a second 5QI.1616-659WO01
