Communicating Data Burst Traffic Characteristics in an Rtp Header Extension for an Rtp Media Communication Session

This application claims the benefit of U.S. Provisional Application No. 63/697,108, filed Sep. 20, 2024, and of U.S. Provisional Application No. 63/771,986, filed Mar. 14, 2025, the entire contents of each of which are hereby incorporated by reference.

This disclosure relates to transport of data, such as media data, via a network.

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.

Video compression techniques perform spatial prediction and/or temporal prediction to reduce or remove redundancy inherent in video sequences. For block-based video coding, a video frame or slice may be partitioned into macroblocks. Each macroblock can be further partitioned. Macroblocks in an intra-coded (I) frame or slice are encoded using spatial prediction with respect to neighboring macroblocks. Macroblocks in an inter-coded (P or B) frame or slice may use spatial prediction with respect to neighboring macroblocks in the same frame or slice or temporal prediction with respect to other reference frames.

After video data has been encoded, the video data may be packetized for transmission or storage. The video 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.

In general, this disclosure describes techniques related to signaling data burst traffic characteristics for communicating data via a network. In general, a data burst may include multiple protocol data units (PDUs) that are sent in a short period of time. A sending device may determine the meaning of “a short period of time” for a data burst, e.g., based on an implementation of the sending device and/or data transmission. The data burst traffic characteristics may indicate a time between data bursts and/or a predicted size of a next data burst. Per techniques of this disclosure, the data burst traffic characteristics may be signaled in, e.g., an RTP header extension.

A sending device may signal a burst size value (e.g., “BSSize”) for a data burst. The sending device may predict this burst size value for the data burst before all data of the data burst has been formed, e.g., before all PDUs of the data burst have been formed. In some cases, the actual data burst size may differ from the predicted burst size value. Therefore, the sending device may send data indicating how the predicted burst size value is to be modified to determine the actual burst size value for the data burst. The data indicating how the predicted burst size value is to be modified may be sent in a subsequent PDU of the data burst, e.g., any later PDU up to or including an ordinal last PDU of the data burst. A receiving device may use the burst size value to perform resource allocation and/or to determine when receiving circuitry is to be disabled for a period of time. For example, a base station (e.g., a gNodeB or gNB) may allocate resources for receiving PDUs of the data burst using the BSSize value. Additionally or alternatively, a user equipment (UE) device may disable receive circuitry after all data of the current data burst has been received, e.g., until a time to next burst (TTNB) indicated for a subsequent data burst. In this manner, the base station and/or the UE may conserve resources, such as battery power, associated with receiving data of a communication session using the burst size value and an updated burst size value per techniques of this disclosure.

In one example, a method of communicating data via a network includes: receiving a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst; receiving a second PDU of the data burst after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst; updating the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and using the actual BSSize value to receive one or more subsequent PDUs of the data burst.

In another example, a device for communicating data via a network includes: a memory configured to store data; and a processing system implemented in circuitry and configured to: receive a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst; receive a second PDU after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst; update the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and use the actual BSSize value to receive one or more subsequent PDUs of the data burst.

In another example, a method of communicating data via a network includes: predicting a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs); sending a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed; after forming one or more additional PDUs of the plurality of PDUs, determining an actual BSSize value for the data burst; and sending a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.

In another example, a device for communicating data via a network, the device comprising: a memory configured to store data; and a processing system implemented in circuitry and configured to: predict a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs); send a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed; after forming one or more additional PDUs of the plurality of PDUs, determine an actual BSSize value for the data burst; and send a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.

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.

In general, this disclosure describes techniques related to communicating data representative of data burst traffic characteristics. These techniques may be used in combination with a transmission protocol, such as Real-time Transport Protocol (RTP) or QUIC. Per these techniques, the data burst traffic characteristics may be signaled in an RTP header extension or a QUIC header extension of a packet. In particular, these techniques may be used to signal protocol data unit (PDU) characteristics, where a PDU may correspond to a particular set of media data. A PDU Set may include each PDU of a variety of different types of media data that are to be presented at substantially the same playback time, e.g., one or more frames of video and/or audio data.

Traffic characteristics of a data burst may be communicated in network metadata. A data burst may represent a set of multiple PDUs generated and sent in a short period of time, e.g., per TS 23.501 clause 3.1. A sending device may determine the meaning of “a short period of time” for a data burst, e.g., based on an implementation of the sending device and/or data transmission. The characteristics may include a time gap between two adjacent data bursts and the size of each data burst. The characteristics may remain to some extent, even after the data bursts traverse a communication network. The traffic characteristic indication may help a radio access network (RAN) base station to schedule transmissions and/or to perform discontinuous reception (DRX) adaptation.

RTP header extensions may be used to communicate the data burst traffic characteristics, per the techniques of this disclosure. An existing RTP header extension for PDU Set marking may be enhanced, or a new RTP header extension may be dedicated to data burst traffic characteristics. Alternatively, other protocol headers may convey the data burst traffic characteristics, such as a QUIC header extension.

One data burst traffic characteristic is the time to the next data burst (TNDB). The starting time of TNDB may be the last packet of the current data burst or the first packet of the current data burst. Being the last packet of the current data burst may make the TNDB value more accurate, especially when the packets in a data burst are sent in a paced way (e.g., uniform inter-packet departure times), but this leaves the base station less reaction time. Being the first packet of the current data burst may lead to higher TNDB prediction error, but gives the base station more reaction time. There are times where flexibility in the definition of the starting time for TNDB may be beneficial, and to indicate the accuracy of the prediction of the TNDB value.

Another data burst traffic characteristic is the next data burst size. The value representing the next data burst size may need to be predicted. Such prediction can be difficult, but the prediction may be useful to the base station for resource allocation. Thus, it may be beneficial to provide an indication of an expected prediction error for the next data burst size.

Per techniques of this disclosure, a predicted data burst size for a current data burst may be updated while the current data burst is being transmitted. For example, a sending device (e.g., a server device) may predict the data burst size for a current data burst before all PDUs of the current data burst have been formed. The sending device may signal the predicted data burst size in data of an ordinal first PDU of the data burst. The prediction may be inaccurate or additional/less data may be transmitted as part of the data burst. Therefore, per techniques of this disclosure, the sending device may send data indicating how to modify the predicted data burst size (BSSize) to form an actual data burst size for the current data burst. For example, the sending device may send data indicating an offset to be applied to the predicted data burst size, such that the offset is to be added to or subtracted from the predicted data burst size value. As another example, the sending device may send the full size of the current data burst, which is to replace the predicted data burst size.

A receiving device, such as a base station (e.g., a gNodeB (gNB)) or a client device (e.g., a user equipment (UE)) may use the burst size to perform resource allocation and/or to schedule disabling of reception circuitry once all data of the current data burst has been received, for a period of time until a next scheduled data burst (e.g., a TTNB value). For example, a UE may be configured to determine an actual BSSize value for a current data burst and that a next data burst will begin at a time indicated by a TTNB value. Therefore, after having received an amount of data of the current data burst equal to the actual BSSize value, the UE may disable reception circuitry for a period of time from an end of the current burst until a time indicated by the TTNB value. In this manner, the UE may save battery power while also avoiding loss of data of a communication session. Similarly, a base station may allocate resources accurately for reception of the current data burst, which may avoid loss of data of a communication session. Moreover, a sending device may update characteristics of the current data burst, which may allow the sending device to send data faster, thereby reducing latency of transmission, rather than waiting until a subsequent data burst to send the additional data.

As various examples, a base station may use the prediction of the burst size and time to next burst information to select a resource allocation type, perform a frequency domain resource assignment and/or a time domain resource assignment, determine a modulation and coding scheme, or the like. Additionally or alternatively, the base station may allocate slots and/or symbols within slots to a UE involved in a communication session based on the time to next burst and burst size information. Additionally or alternatively, the base station may allocate resource blocks and/or resource block groups to the UE, configure subcarrier spacing, and/or configure bandwidth parts (BWPs) for the UE based on the time to next burst and burst size information for a current burst of the communication session that the UE is engaged in. Moreover, the base station may update resource allocation configuration based on the updated (actual) burst size value for a current data burst.

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.

1 FIG. 10 10 20 60 40 40 60 74 20 60 74 20 60 is a block diagram illustrating an example systemthat implements techniques for streaming media data over a network. In this example, systemincludes content preparation device, server device, and client device. Client deviceand server deviceare communicatively coupled by network, which may comprise the Internet. In some examples, content preparation deviceand server devicemay also be coupled by networkor another network, or may be directly communicatively coupled. In some examples, content preparation deviceand server devicemay comprise the same device.

20 22 24 22 26 22 24 28 20 60 60 1 FIG. Content preparation device, in the example of, comprises audio sourceand video source. Audio sourcemay comprise, for example, a microphone that produces electrical signals representative of captured audio data to be encoded by audio encoder. Alternatively, audio sourcemay 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 sourcemay comprise a video camera that produces video data to be encoded by video encoder, 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 deviceis not necessarily communicatively coupled to server devicein all examples, but may store multimedia content to a separate medium that is read by server device.

26 28 22 24 22 24 Raw audio and video data may comprise analog or digital data. Analog data may be digitized before being encoded by audio encoderand/or video encoder. Audio sourcemay obtain audio data from a speaking participant while the speaking participant is speaking, and video sourcemay simultaneously obtain video data of the speaking participant. In other examples, audio sourcemay comprise a computer-readable storage medium comprising stored audio data, and video sourcemay 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.

22 24 22 24 22 Audio frames that correspond to video frames are generally audio frames containing audio data that was captured (or generated) by audio sourcecontemporaneously with video data captured (or generated) by video sourcethat is contained within the video frames. For example, while a speaking participant generally produces audio data by speaking, audio sourcecaptures the audio data, and video sourcecaptures video data of the speaking participant at the same time, that is, while audio sourceis 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.

26 28 20 26 28 22 24 In some examples, audio encodermay 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 encodermay 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 devicemay include an internal clock from which audio encoderand/or video encodermay generate the timestamps, or that audio sourceand video sourcemay use to associate audio and video data, respectively, with a timestamp.

22 26 24 28 26 28 In some examples, audio sourcemay send data to audio encodercorresponding to a time at which audio data was recorded, and video sourcemay send data to video encodercorresponding to a time at which video data was recorded. In some examples, audio encodermay 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 encodermay 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.

26 28 Audio encodergenerally produces a stream of encoded audio data, while video encoderproduces 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.

1 FIG. 30 20 28 26 28 26 28 26 30 In the example of, encapsulation unitof content preparation devicereceives elementary streams comprising coded video data from video encoderand elementary streams comprising coded audio data from audio encoder. In some examples, video encoderand audio encodermay each include packetizers for forming PES packets from encoded data. In other examples, video encoderand audio encodermay each interface with respective packetizers for forming PES packets from encoded data. In still other examples, encapsulation unitmay include packetizers for forming PES packets from encoded audio and video data.

28 30 Video encodermay 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 which the PES packet belongs. Encapsulation unitis responsible for assembling elementary streams into streamable media data.

30 26 28 Encapsulation unitreceives PES packets for elementary streams of a media presentation from audio encoderand video encoderand 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 to Video Coding Layer (VCL) NAL units and non-VCL NAL units. VCL 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.

Non-VCL NAL units may include parameter set NAL units and 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.

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.

60 70 72 60 60 64 60 72 74 Server deviceincludes Real-time Transport Protocol (RTP) transmitting unitand network interface. In some examples, server devicemay include a plurality of network interfaces. Furthermore, any or all of the features of server devicemay 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 contentand include components that conform substantially to those of server device. In general, network interfaceis configured to send and receive data via network.

70 40 74 3550 70 70 72 60 74 RTP transmitting unitis configured to deliver media data to client devicevia networkaccording to RTP, which is standardized in Request for Comment (RFC)by the Internet Engineering Task Force (IETF). RTP transmitting unitmay 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 unitmay send media data via network interface, which may implement Uniform Datagram Protocol (UDP) and/or Internet protocol (IP). Thus, in some examples, server devicemay send media data via RTP and RTSP over UDP using network.

70 40 40 70 40 64 40 RTP transmitting unitmay receive an RTSP describe request from, e.g., client device. The RTSP describe request may include data indicating what types of data are supported by client device. RTP transmitting unitmay respond to client devicewith data indicating media streams, such as media content, that can be sent to client device, along with a corresponding network location identifier, such as a uniform resource locator (URL) or uniform resource name (URN).

70 40 64 40 70 60 70 40 74 70 70 40 RTP transmitting unitmay then receive an RTSP setup request from client device. 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) and a transport specifier, such as local ports for receiving RTP data and control data (e.g., RTCP data) on client device. RTP transmitting unitmay reply to the RTSP setup request with a confirmation and data representing ports of server deviceby which the RTP data and control data will be sent. RTP transmitting unitmay then receive an RTSP play request, to cause the media stream to be “played,” i.e., sent to client devicevia network. RTP transmitting unitmay also receive an RTSP teardown request to end the streaming session, in response to which, RTP transmitting unitmay stop sending media data to client devicefor the corresponding session.

52 60 40 52 60 64 40 RTP receiving unit, likewise, may initiate a media stream by initially sending an RTSP describe request to server device. The RTSP describe request may indicate types of data supported by client device. RTP receiving unitmay then receive a reply from server devicespecifying available media streams, such as media content, that can be sent to client device, along with a corresponding network location identifier, such as a uniform resource locator (URL) or uniform resource name (URN).

52 60 64 40 52 60 60 60 RTP receiving unitmay then generate an RTSP setup request and send the RTSP setup request to server device. As noted above, the RTSP setup request may contain the network location identifier for the requested media data (e.g., media content) and a transport specifier, such as local ports for receiving RTP data and control data (e.g., RTCP data) on client device. In response, RTP receiving unitmay receive a confirmation from server device, including ports of server devicethat server devicewill use to send media data and control data.

60 40 70 60 40 60 40 40 60 After establishing a media streaming session between server deviceand client device, RTP transmitting unitof server devicemay send media data (e.g., packets of media data) to client deviceaccording to the media streaming session. Server deviceand client devicemay exchange control data (e.g., RTCP data) indicating, for example, reception statistics by client device, such that server devicecan perform congestion control or otherwise diagnose and address transmission faults.

54 52 50 50 46 48 46 42 48 44 Network interfacemay receive and provide media of a selected media presentation to RTP receiving unit, which may in turn provide the media data to decapsulation unit. Decapsulation unitmay 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 decoderor video decoder, 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 decoderdecodes encoded audio data and sends the decoded audio data to audio output, while video decoderdecodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to video output.

28 48 26 46 30 52 50 28 48 26 46 28 48 26 46 30 52 50 Video encoder, video decoder, audio encoder, audio decoder, encapsulation unit, RTP receiving unit, and decapsulation uniteach 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 integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic circuitry, software, hardware, firmware or any combinations thereof. Each of video encoderand video decodermay 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 encoderand audio decodermay 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, video decoder, audio encoder, audio decoder, encapsulation unit, RTP receiving unit, and/or decapsulation unitmay comprise an integrated circuit, a microprocessor, and/or a wireless communication device, such as a cellular telephone.

40 60 20 40 60 20 60 Client device, server device, and/or content preparation devicemay 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 deviceand server device. However, it should be understood that content preparation devicemay be configured to perform these techniques, instead of (or in addition to) server device.

30 30 28 30 Encapsulation unitmay 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 unitmay receive encoded video data from video encoderin the form of PES packets of elementary streams. Encapsulation unitmay associate each elementary stream with a corresponding program.

30 Encapsulation unitmay 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. In one example, an access unit may comprise a coded picture in one time instance, which may be presented as a primary coded picture.

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 include 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.

30 30 32 30 32 40 32 32 After encapsulation unithas assembled NAL units and/or access units into a video file based on received data, encapsulation unitpasses the video file to output interfacefor output. In some examples, encapsulation unitmay store the video file locally or send the video file to a remote server via output interface, rather than sending the video file directly to client device. Output interfacemay 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 interfaceoutputs 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.

54 74 50 52 50 46 48 46 42 48 44 Network interfacemay receive a NAL unit or access unit via networkand provide the NAL unit or access unit to decapsulation unit, via RTP receiving unit. Decapsulation unitmay decapsulate a 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 decoderor video decoder, 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 decoderdecodes encoded audio data and sends the decoded audio data to audio output, while video decoderdecodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to video output.

60 40 70 1 FIG. Per techniques of this disclosure, server devicemay send data of a communication session to client devicevia a transport protocol, such as Real-time Transport Protocol (RTP) as shown in the example of. Alternatively, other transport protocols, such as QUIC, may be used. When QUIC is used, RTP transmitting unitmay instead be considered a QUIC transmitting unit.

60 40 Server devicemay send data of the communication session with client devicein data bursts, where a data burst may include a set of protocol data units (PDUs), i.e., a PDU Set. In general, a PDU Set may include all media data to be presented together at a common temporal instance, and each PDU may include data to be included at that common temporal instance. For example, slices of a frame of video data may be encapsulated and transmitted as a PDU. As such, a PDU Set may correspond to an access unit, as discussed above.

60 60 70 70 60 60 Accordingly, server devicemay construct a PDU Set for transmission in a data burst. Before having completely formed the PDU Set for a current data burst, server devicemay predict a size of the current data burst. RTP transmitting unitmay encapsulate an ordinal first PDU of the PDU Set for the current data burst with data indicating the predicted size of the current data burst as a burst size (BSSize) value. For example, RTP transmitting unitmay encapsulate the ordinal first PDU with an RTP header extension that signals the BSSize value (as a predicted BSSize value). The same RTP header extension, or a different RTP header extension, may also indicate a time to next burst (TTNB) value, which may indicate a time between the end of the current data burst to a time at which a subsequent data burst will begin, where this time between data bursts represents a time during which server devicewill not send time-sensitive data of the communication session. When QUIC is used, server devicemay instead encapsulate the ordinal first PDU with one or more QUIC header extensions signaling the time to next burst and burst size values.

60 60 60 60 60 While constructing the PDU Set for the current data burst, server devicemay determine that additional data is to be sent for the current data burst. For example, server devicemay receive additional data for a different PDU Set or additional data for the current PDU Set. Thus, server devicemay determine that the previously predicted burst size for the current data burst is not accurate. Therefore, server devicemay encapsulate a subsequent PDU of the PDU Set with an RTP header extension (or QUIC header extension) including data indicating how the previous predicted burst size value is to be updated to account for the new burst size. For example, server devicemay signal an offset relative to the predicted BSSize value or an entirely new BSSize value representing the total size of the current data burst.

40 60 40 52 40 52 40 1 FIG. Client devicemay represent a user equipment (UE) device that is communicatively coupled to server devicevia a radio access network (RAN). The RAN may include a base station, such as a gNB (not shown in). The base station may use the time to next burst, predicted burst size, and updated (actual) burst size information to perform resource allocation, as discussed above. The base station may also configure client deviceto disable RTP receiving unit(e.g., receiving circuitry) for a period of time between an end of a current data burst and a next data burst of the communication session. In this manner, client devicemay disable RTP receiving unitfor this period of time, which may save processing power and thereby conserve battery power, when client deviceis powered by a battery.

40 40 40 40 The base station and/or client devicemay also, during establishment of the communication session, communicate support for variable burst size information. For example, the base station and/or client devicemay send a session description protocol (SDP) message indicating whether the base station and/or client devicesupport updating burst size information per the techniques of this disclosure, e.g., for RTP sessions. For QUIC, the base station and/or client devicemay send such information in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet, and the information may be a transport parameter indicating whether such burst size updates are supported.

2 FIG. 2 FIG. 2 FIG. 150 150 152 154 162 164 166 150 is a block diagram illustrating elements of an example video file. 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, video fileincludes file type (FTYP) box, movie (MOOV) box, segment index (sidx) boxes, movie fragment (MOOF) boxes, and movie fragment random access (MFRA) box. Althoughrepresents 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, in accordance with the ISO base media file format and its extensions.

152 150 152 150 152 154 164 166 File type (FTYP) boxgenerally describes a file type for video file. File type boxmay include data that identifies a specification that describes a best use for video file. File type boxmay alternatively be placed before MOOV box, movie fragment boxes, and/or MFRA box.

154 156 158 160 156 150 156 150 150 150 150 150 2 FIG. MOOV box, in the example of, includes movie header (MVHD) box, track (TRAK) box, and one or more movie extends (MVEX) boxes. In general, MVHD boxmay describe general characteristics of video file. For example, MVHD boxmay include data that describes when video filewas originally created, when video filewas last modified, a timescale for video file, a duration of playback for video file, or other data that generally describes video file.

158 150 158 158 158 164 158 162 TRAK boxmay include data for a track of video file. TRAK boxmay include a track header (TKHD) box that describes characteristics of the track corresponding to TRAK box. In some examples, TRAK boxmay include coded video pictures, while in other examples, the coded video pictures of the track may be included in movie fragments, which may be referenced by data of TRAK boxand/or sidx boxes.

150 154 150 158 150 158 158 154 30 150 30 1 FIG. In some examples, video filemay include more than one track. Accordingly, MOOV boxmay include a number of TRAK boxes equal to the number of tracks in video file. TRAK boxmay describe characteristics of a corresponding track of video file. For example, TRAK boxmay describe temporal and/or spatial information for the corresponding track. A TRAK box similar to TRAK boxof MOOV boxmay describe characteristics of a parameter set track, when encapsulation unit() includes a parameter set track in a video file, such as video file. Encapsulation unitmay signal the presence of sequence level SEI messages in the parameter set track within the TRAK box describing the parameter set track.

160 164 150 164 154 164 154 164 154 MVEX boxesmay describe characteristics of corresponding movie fragments, e.g., to signal that video fileincludes movie fragments, in addition to video data included within MOOV box, if any. In the context of streaming video data, coded video pictures may be included in movie fragmentsrather than in MOOV box. Accordingly, all coded video samples may be included in movie fragments, rather than in MOOV box.

154 160 164 150 160 164 164 MOOV boxmay include a number of MVEX boxesequal to the number of movie fragmentsin video file. Each of MVEX boxesmay describe characteristics of a corresponding one of movie fragments. 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.

30 30 164 30 164 160 164 As noted above, encapsulation unitmay 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 include one or more VCL NAL units, which contain the information to construct all the pixels of the access unit and other associated non-VCL NAL units, such as SEI messages. Accordingly, encapsulation unitmay include a sequence data set, which may include sequence level SEI messages, in one of movie fragments. Encapsulation unitmay further signal the presence of a sequence data set and/or sequence level SEI messages as being present in one of movie fragmentswithin the one of MVEX boxescorresponding to the one of movie fragments.

162 150 162 150 SIDX boxesare optional elements of video file. That is, video files conforming to the 3GPP file format, or other such file formats, do not necessarily include SIDX boxes. 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). 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.”

162 150 SIDX boxesgenerally provide information representative of one or more sub-segments of a segment included in video file. For instance, such information may include playback times at which sub-segments begin and/or end, byte offsets for the sub-segments, 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 sub-segment, and the like.

164 164 164 164 164 150 2 FIG. Movie fragmentsmay include one or more coded video pictures. In some examples, movie fragmentsmay 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 fragmentsmay include sequence data sets in some examples. Each of movie fragmentsmay include a movie fragment header box (MFHD, not shown in). The MFHD box may describe characteristics of the corresponding movie fragment, such as a sequence number for the movie fragment. Movie fragmentsmay be included in order of sequence number in video file.

166 164 150 150 166 40 166 150 166 150 150 MFRA boxmay describe random access points within movie fragmentsof video file. 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. MFRA boxis generally optional and need not be included in video files, in some examples. Likewise, a client device, such as client device, does not necessarily need to reference MFRA boxto correctly decode and display video data of video file. MFRA boxmay include a number of track fragment random access (TFRA) boxes (not shown) equal to the number of tracks of video file, or in some examples, equal to the number of media tracks (e.g., non-hint tracks) of video file.

164 166 150 150 150 In some examples, movie fragmentsmay include one or more stream access points (SAPs), such as IDR pictures. Likewise, MFRA boxmay provide indications of locations within video fileof the SAPs. Accordingly, a temporal sub-sequence of video filemay be formed from SAPs of video file. 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.

3 4 FIGS.and 3 4 FIGS.and are conceptual diagrams illustrating respective examples of RTP header extensions for signaling the starting time of a time to the next data burst (TNDB). As discussed above, in general, the TNDB may correspond to the first PDU set of the current data burst or the last PDU of the current data burst. In the examples of, as discussed below, the TNDB may be signaled as either corresponding to the first PDU or the last PDU of the current data burst.

In some examples, the RTP header extension for PDU Set marking may signal whether the TNDB corresponds to the first PDU or the last PDU of the current burst. The existing RTP header extension for PDU Set marking may be modified to introduce one or two newly defined bits to indicate the start time of the TTNB. An existing reserved bit of the RTP header extension for PDU Set marking may be used for the indication. The indication may be by a codepoint of the existing reserved field, e.g., R=10 indicates the first PDU or R=01 indicates the last PDU.

3 FIG. 200 200 202 204 206 208 210 212 214 216 218 220 222 224 226 226 228 214 214 is a conceptual diagram illustrating an example one-byte format for an RTP header extensionfor PDU set marking per techniques of this disclosure. In this example, RTP header extensionincludes hex value 0×BE(8 bits), hex value 0×DE(8 bits), length field(16 bits), identifier (ID) value(4 bits), length (len) value(4 bits), E bit, R bits(2 bits), D bit, PSI bits(4 bits), PSSN field(10 bits), PSN field(6 bits), PSSize field(24 bits), NPDS fieldsA,B (total of 16 bits), and NTDB field(8 bits). In this example, the value of R bitsmay be set to 10 to indicate that the TNBD value corresponds to the first PDU of the burst, whereas the value of R bitsmay be set to 01 to indicate that the TNBD value corresponds to the last PDU of the burst.

4 FIG. 250 250 252 256 258 260 262 264 266 268 270 270 272 274 276 278 264 264 1 is a conceptual diagram illustrating an example two-byte format for an RTP header extensionfor PDU set marking per techniques of this disclosure. In this example, RTP header extensionincludes hex value 0×100(12 bits), appbits 254 (4 bits), length field(16 bits), ID value(8 bits), len value(8 bits), S bit, R bits(2 bits), D bit, PSI value(4 bits), PSSN fieldsA,B (total of 10 bits), PSN field(6 bits), PSSize field(24 bits), NPDS field(16 bits), and NTDB field(8 bits). In this example, the value of R bitsmay be set to 10 to indicate that the TNBD value corresponds to the first PDU of the burst, whereas the value of R bitsmay be set toto indicate that the TNBD value corresponds to the last PDU of the burst.

5 6 FIGS.and In some examples, a dedicated RTP header extension for data burst traffic characteristics may be modified to indicate whether a TNDB value corresponds to a first PDU of the current burst or a last PDU of the current burst. Examples are shown in, as discussed below. In general, reserved bits of the RTP header extension for data burst traffic characteristics may be used to signal whether the TNDB value corresponds to the first PDU of the current burst or the last PDU of the current burst, as discussed below.

5 FIG. 300 300 302 304 306 308 310 312 314 316 318 320 322 324 324 314 314 is a conceptual diagram illustrating an example one-byte format for an RTP header extensionfor data burst traffic characteristics per techniques of this disclosure. In this example, RTP header extensionincludes hex value 0×BE(8 bits), hex value 0×DE(8 bits), length field(16 bits), identifier (ID) value(4 bits), length (len) value(4 bits), R bits(2 bits), S bit, D bit, RR field(4 bits), TCIN field(16 bits), BSSize field(24 bits), and TTNB fieldsA,B (total of 16 bits). In this example, the value of S bitmay be set to 1 to indicate that the TNBD value corresponds to the first PDU of the burst, whereas the value of S bitsmay be set to 0 to indicate that the TNBD value corresponds to the last PDU of the burst.

6 FIG. 350 350 352 354 356 358 360 362 364 366 368 370 370 372 374 364 364 362 362 362 364 is a conceptual diagram illustrating an example two-byte format for an RTP header extensionfor data burst traffic characteristics per techniques of this disclosure. In this example, RTP header extensionincludes hex value 0×100(12 bits), appbits(4 bits), length field(16 bits), ID value(8 bits), len value(8 bits), R bits(2 bits), S bit, D bit, RR bits(4 bits), TCIN fieldsA,B (16 bits total), BSSize field(24 bits), and TTNB field(16 bits). In this example, the value of S bitmay be set to 1 to indicate that the TNBD value corresponds to the first PDU of the burst, whereas the value of S bitmay be set to 0 to indicate that the TNBD value corresponds to the last PDU of the burst. Because R bitsare reserved, the expected value of R bitsmay be 00, thus the value of R bitsin combination with the value of S bitmay be 001 to indicate that the TNBD value corresponds to the first PDU of the burst or 000 to indicate that the TNDB value corresponds to the last PDU of the burst.

In addition or in the alternative, the accuracy of the TNDB value may be indicated by a field in an RTP header extension. This indication may include an integer component and a fractional component. The indication may represent jitter, standard deviation, or confidence interval. A value of y of the indication may mean+/−y units of time. The TNDB x with accuracy y may then be interpreted as x+/−y time units. For example, if the indication has 8 bits, the four most significant bits may represent the integer component and the four least significant bits may represent the fractional component. Assuming that the unit is in milliseconds, then the range may be from 0 to 16-1/256=15.996 ms for y. The RTP header extension may be RTP header extension for PDU set marking or the RTP header extension for data burst traffic characteristics.

In addition or in the alternative, the accuracy of the size of the next data burst (SNDB) may be indicated in a field of an RTP header extension. The indication may represent a jitter, standard deviation, or a confidence interval. In one example, a value y of the indication means+/−y units of data. The SNDB x with accuracy y may be interpreted as x+/−y data units. For example, the indication may have 8 bits, and the data unit may be 32 bits. As another example, the value may indicate relative error. For example, a value a of the indication may mean+/−a of the indicated SNDB, and SNDB x with accuracy a may be interpreted as x(1+/−a). For example, the indication may have 8 bits and represent a fractional number with the decimal point to the left of the MSB, hence 01000000 may mean 0.25 in decimal. The RTP header extension may be the RTP header extension for PDU Set marking with a new field for the indication, or the RTP header extension for data burst with a new field for the indication.

7 FIG. 7 FIG. 390 396 is a conceptual diagram illustrating example data bursts and protocol data units (PDUs) thereof. In this example,depicts current data burstand next data burst, each of which includes a respective PDU Set.

7 FIG. In general, data indicating a burst size may be sent in an ordinal first PDU of a data burst to which the burst size applies. Likewise, a time to next burst (TTNB) value, or a TNDB value, may represent the time difference between the departure time of an ordinal last PDU of the data burst and the departure time of the ordinal first PDU of the next data burst. That is, the TTNB value (or TNDB value) may represent a time period (or silent period) during which the traffic source guarantees not to send any delay-sensitive PDUs, as shown in.

7 FIG. 392 390 390 390 394 390 398 396 In particular, in the example of, an ordinal first PDUof current data burstmay include data indicating a burst size for current data burst. As discussed above, such burst size data may be carried in an RTP header extension or a QUIC header extension. Likewise, a TTNB value for current data burstrepresents a time period (or silent period) between a departure time of ordinal last PDUof current data burstand a departure time of ordinal first PDUof next data burst.

392 390 390 390 Moreover, per techniques of this disclosure, ordinal first PDUof current data burstmay include data (e.g., an RTP header extension or QUIC header extension) including a predicted burst size (BSSize) value for current data burst. At some point, a sending device may determine that this predicted BSSize value was inaccurate. Therefore, the sending device may encapsulate a subsequent PDU of the PDU Set with data indicating how the predicted BSSize value is to be modified (e.g., offset or replaced) with size data to obtain an actual BSSize value for current data burst.

8 FIG. 400 400 402 404 406 402 402 is a conceptual diagram illustrating an example Real-time Transport Protocol (RTP) header extensionthat may be used to signal data burst traffic characteristics per techniques of this disclosure. In this example, RTP header extensionincludes, among other fields, a reserved (R) field, burst size (BSSize) field, and time to next burst (TTNB) field. R fieldis an eight-bit field in this example and is reserved for future usage. R fieldmay have a value of 0 for all eight bits as set by a sending device and may be ignored by a receiving device.

404 404 400 404 BSSize fieldis a 24-bit field in this example. The value of BSSize fieldmay indicate a total size of the burst to be transmitted in bytes (including the overhead of RTP header extension). If the burst size is not known, the value of BSSize fieldmay be set to zero.

406 406 406 TTNB fieldis a 16-bit field in this example. The value of TTNB fieldmay indicate an approximate time, in tenths of a millisecond, to the next burst. If the time is not known, the value of TTNB fieldmay be set to a reserved value of 65535.

400 Per techniques of this disclosure, an ordinal first PDU of a current data burst may be encapsulated with RTP header extensionto indicate both a predicted BSSize value and a TTNB value. If the sending device determines that the predicted BSSize value was inaccurate, the sending device may update the BSSize value (e.g., with data indicating an offset or a replacement value). Thus, a receiving device may receive the update to the BSSize value to determine an actual BSSize value for the current data burst. The receiving device may be, for example, a base station, which may perform a new resource allocation procedure based on the actual BSSize value, to ensure that all PDUs of the PDU Set of the current data burst are received correctly. The base station may also reconfigure a communicatively coupled UE participating in the communication session based on the actual BSSize value, e.g., to disable reception circuitry for a time period between having received all PDUs of the current data burst and a time at which a subsequent data burst is to begin transmission.

9 FIG. 9 FIG. 420 430 420 422 422 422 430 432 432 432 432 is a conceptual diagram illustrating an example sequence of PDUs sent as part of a data burst. In some instances, constituent PDUs of a data burst may increase after the data burst indication has been sent. The example ofdepicts current burstand next burst. Current burstincludes white-shaded blocks representing PDUs, namely, PDUsA,B, andC. Next burstincludes grey-shaded blocks representing PDUs, namely, PDUsA,B,C, andD.

420 422 422 422 422 420 432 432 420 422 422 432 432 In this example, current burstincludes three audio PDUs, i.e., PDUsA-C. Encoding of a video frame may be finished after an ordinal first audio PDU (e.g., PDUA) was sent. PDUA may include an RTP header extension indicating that current burstincludes a data burst size (BSSize) of 3000B. Video PDUs, i.e., PDUsA-D, may be created and sent before the end of current burst, i.e., a current audio data burst. Each of PDUsA-C may be assumed to be 1000 bytes in this example, and each of PDUsA-D may be assumed to be 1000 bytes in this example.

420 432 432 422 422 432 432 432 Current burstmay incorporate video PDUsA-D and become a new data burst. The BSSize of the new data burst, in this example, is much larger than 3000 bytes (namely, 7000 bytes, in this example), due to inclusion of each of PDUsA-C and PDUsA-D. A traffic source may therefore need to update the BSSize value, preferably in first video PDUA.

432 432 422 Alternatively, the original BSSize indication of 3000 bytes may be kept accurate by delaying transmission of video PDUsA-D until after PDUC has been sent. However, this would increase the delay of the video data burst, which may cause poor performance through introduction of latency, which may diminish performance of certain applications, such as AR/XR applications.

60 1 FIG. Accordingly, this disclosure describes techniques that may be used to indicate an updated BSSize value. A traffic source, such as server deviceof, may indicate an update to a previously signaled BSSize value if one or more PDUs not belonging to the current data burst are sent after transmission of an ordinal first PDU of the current data burst and before transmission of the ordinal last PDU of the current data burst to form a new data burst. This indication may be included in a header extension (e.g., an RTP header extension or a QUIC header extension) of a second or subsequent PDU following the ordinal first PDU of the current data burst.

One or more PDUs not belonging to the current data burst may or may not be delay sensitive. If the one or more PDUs are delay sensitive, the BSSize value may be updated to avoid delay that may otherwise be caused by a base station not obtaining enough resource allocation based on the outdated BSSize information. If the one or more PDUs are not delay sensitive, the BSSize value may still need to be updated because the base station cannot distinguish delay sensitive from non-delay sensitive PDUs. Alternatively, the source device may delay transmission of the non-delay sensitive PDUs, e.g., until the end of the current data burst.

A subsequent PDU including an updated BSSize value may be one of the PDUs not belonging to the current data burst. The updated BSSize value may indicate the size of the remaining PDUs of the new data burst or the size of all of the PDUs of the new data burst. The BSSize value indicating a size of the remaining PDUs of the new data burst may simplify operation at a network entity (e.g., a base station, such as a gNB), because the network entity only needs to allocate resources for the remaining PDUs of the new data burst. The BSSize value indicating a size of all of the PDUs of the new data burst may require the network entity to keep a state variable to store the BSSize of the current data burst and to adjust resource allocation based on the updated BSSize value.

A traffic source may include data indicating that the updated BSSize value is an update to a previously transmitted BSSize value. Such data may be included in the same PDU that includes the updated BSSize value. This indication may be carried out using a new bit or a reserved bit, e.g., in the RTP header extension or in the QUIC header extension. A bit value of 1 may indicate that the BSSize value is an updated BSSize value, and therefore, the previous BSSize value is obsolete and should be ignored or updated by a receiving network entity. A bit value of 0 may indicate that the BSSize is not an update of a previous BSSize value, and therefore, the BSSize value carried in the PDU does not make the previous BSSize value obsolete.

extensionname=“urn:3gpp:sa4:5grtp: dynamic-traffic-characteristics-rel19” extensionattributes=[format SP][BSSize-update]where the presence of BSSize-update indicates support for BSSize update, and absence indicates no support for such updates. This data may be signaled as an option during session setup. For example, session description protocol (SDP) signaling may be used to signal whether data for a new BSSize value of a current data burst may override/render obsolete a previously sent BSSize value for the current data burst. If the PDUs are carried by RTP packets, an example augmented Backus-Naur form (ABNF) syntax for the data may be:

Additionally or alternatively, various other messages (e.g., Initial packets, handshake packets, 1-RTT packets of QUIC) may include BSSize update negotiation data, e.g., as a transport parameter. For example, during a QUIC handshake phase, both a sending device and a receiving device may send transport parameters as declarations that are made unilaterally indicating support of various features, such as BSSize update data per techniques of this disclosure.

10 FIG. 10 FIG. 1 FIG. 1 FIG. 450 452 456 458 450 60 20 458 40 is a block diagram illustrating an example set of network devices that may perform various aspects of the techniques of this disclosure. The example ofdepicts sending device, user plane function (UPF) device, base station, and user equipment (UE) device. Sending devicemay correspond to server deviceand/or content preparation deviceof. UE devicemay correspond to client deviceof.

450 458 460 458 450 450 10 FIG. Sending device(e.g., an application server (AS) device) may obtain video data to be sent to UE devicevia communication session. To send the video data to UE device, sending devicemay encode the video data (or receive encoded video data from an encoding device, not shown in). Sending devicemay encapsulate packets including encoded video data (e.g., encoded slices of frames of video data) to form real-time transport protocol (RTP) packets. Such RTP packets may correspond to PDUs of respective data bursts.

450 450 450 458 452 450 452 10 FIG. Sending devicemay add an RTP header extensions to certain PDUs to indicate burst size data for a current data burst. For example, sending devicemay add such RTP header extensions to ordinal first PDUs and/or to PDUs indicating a burst size update for the current data burst. As the RTP packets are formed, sending devicemay send the RTP packets to UE devicevia a network including UPF device. Although not shown in, there may be additional network devices between sending deviceand UPF device, e.g., various network routing devices, gateways, bridges, switches, or the like.

452 450 452 452 452 452 456 454 454 454 456 UPF devicemay receive the RTP packets from sending deviceand form GTP-U tunneled packets. For example, UPF devicemay encapsulate the RTP packets with respective GTP-U headers. Per techniques of this disclosure, UPF devicemay extract the burst size data from the RTP header extensions of the RTP packets, e.g., from respective RTP header extensions. UPF devicemay then form the GTP-U headers to include corresponding burst size data. UPF devicemay send the GTP-U packets to base stationvia network tunnel. Network tunnelmay include other network devices, such as network routing devices, configured to forward the GTP-U packets along network tunnelto base station.

456 456 456 458 456 458 462 Base stationmay receive the GTP-U packets and decapsulate the GTP-U packets to reproduce the RTP packets. Base stationmay allocate resources to reception of the GTP-U packets based on the burst size data (and reallocate resources in response to burst size updates). For example, base stationmay instruct UE deviceto disable data reception after the total amount of data corresponding to the burst size for the current data burst has been received for a period of time corresponding to a signaled time to next burst (e.g., TTNB or TNBD value) per techniques of this disclosure. Base stationmay then send the RTP packets to UE devicevia radio access network (RAN) connection.

458 456 462 458 458 460 462 458 UE devicemay receive the RTP packets from base stationvia RAN connection. In particular, UE devicemay be a battery powered device, such as a cellphone. Thus, to preserve battery power, UE devicemay disable reception of packets for communication sessionvia RAN connectionfor idle period times indicated by the TNBD/TTNB values following reception of all data for the current data burst as indicated by the burst size data. For example, during idle period times, UE devicemay power down reception circuitry, then power up the reception circuitry at the end of the idle period.

11 FIG. 11 FIG. 1 FIG. 10 FIG. 11 FIG. 10 FIG. 60 450 450 is a flowchart illustrating an example method for sending data of a communication session per techniques of this disclosure. The method ofmay be performed by a sending device, such as server deviceofor sending deviceof. For purposes of example and explanation, the method ofis explained with respect to sending deviceof.

450 458 456 450 450 10 FIG. Initially, sending devicemay perform a session negotiation for a communication session with a receiving device, such as UE deviceand/or base stationof. The session negotiation may include receiving, from the receiving device, data indicating whether the receiving device supports updating a data burst size (BSSize) value for a current data burst while the current data burst is being sent per techniques of this disclosure. For example, sending devicemay receive a session description protocol (SDP) message from the receiving device indicating whether the receiving device supports BSSize value updates per these techniques. As another example, sending devicemay receive a transport parameter indicating support for data burst size updates for the data bursts of the communication session, e.g., in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

450 500 450 450 502 8 450 450 504 5 6 FIGS., Sending devicemay then predict a burst size (BSSize) value for a current data burst of a communication session with the receiving device (). For example, sending devicemay determine that protocol data units (PDUs) of a PDU Set to be sent in the current data burst are to be sent via Real-time Transport Protocol (RTP). Thus, sending devicemay signal data representing the predicted BSSize value with an ordinal first PDU of the data burst (), e.g., in an RTP header extension that encapsulates the ordinal first PDU of the data burst, such as discussed above with respect to, orabove. The RTP header extension may also include data representing a time to next burst, which may be signaled relative to a time at which an ordinal last PDU of the PDU Set of the current data burst as discussed above. Alternatively, sending devicemay encapsulate the ordinal first PDU with a QUIC header extension including the predicted BSSize value (and possibly also the time to next burst value). Sending devicemay then send the ordinal first PDU to the receiving device ().

450 506 450 450 508 450 510 450 450 512 As noted above, the ordinal first PDU may be sent before all PDUs of the PDU Set of the current data burst have been fully formed. Therefore, sending devicemay proceed to construct one or more additional PDUs of the PDU Set of the current data burst (). In the process of constructing the one or more additional PDUs, sending devicemay determine that the predicted BSSize value for the current data burst is not accurate, e.g., because additional data needs to be sent as part of the current data burst. Therefore, sending devicemay determine an updated BSSize for the current data burst (). Sending devicemay further signal the updated (actual) BSSize value with a subsequent PDU of the current data burst (). For example, sending devicemay encapsulate the subsequent PDU with an RTP header extension or QUIC header extension indicating the updated BSSize value. The updated BSSize value may be signaled as a difference (delta) relative to the original predicted BSSize value or a most recently transmitted BSSize value, or may be signaled as an absolute size of all PDUs of the PDU Set of the current data burst. Sending devicemay then proceed to send remaining PDUs of the PDU Set of the current data burst ().

11 FIG. In this manner, the method ofrepresents an example of a method of communicating data via a network, including: predicting a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs); sending a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed; after forming one or more additional PDUs of the plurality of PDUs, determining an actual BSSize value for the data burst; and sending a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.

12 FIG. 12 FIG. 1 FIG. 10 FIG. 10 FIG. 12 FIG. 10 FIG. 40 458 456 456 is a flowchart illustrating an example method for receiving data of a communication session per techniques of this disclosure. The method ofmay be performed by a receiving device, such as client deviceof, UE deviceof, or a base station, such as base stationof. For purposes of explanation and example, the method ofis discussed with respect to base stationof.

456 60 450 456 450 456 456 1 FIG. 10 FIG. Initially, base stationmay signal support for updates to current data burst size values, e.g., during a session negotiation for a communication session with a sending device, such as server deviceofor sending deviceof. For example, base stationmay send a session description protocol (SDP) message to sending deviceindicating whether base stationsupports BSSize value updates per these techniques. As another example, base stationmay send a transport parameter indicating support for data burst size updates for the data bursts of the communication session, e.g., in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

456 550 456 552 10 FIG. During the communication session, base stationmay receive an ordinal first PDU of a PDU Set of a current data burst (). The ordinal first PDU may be encapsulated with an RTP header extension, QUIC header extension, or the like, including data representing a predicted burst size (BSSize) value for the current data burst. Alternatively, as discussed with respect to, an RTP packet or QUIC packet may further be encapsulated by a tunnel header, such as a GTP-U tunnel header, which may include the BSSize value. Thus, base stationmay determine the predicted BSSize for the current data burst (), e.g., from the RTP header extension, QUIC header extension, tunnel header, or the like.

456 554 456 456 458 458 456 458 Base stationmay then allocate resources to receive subsequent data of the current data burst according to the predicted BSSize value (). For example, base stationmay perform frequency domain and/or temporal domain resource assignments, determine a modulation scheme, determine a coding scheme, allocate slots/symbols, allocate resource blocks/resource block groups, configure subcarrier spacing, and/or configure bandwidth parts (BWPs) to receive PDUs of the PDU Set of the current data burst based on the predicted BSSize value. Additionally or alternatively, base stationmay configure UE deviceusing the predicted BSSize value, e.g., to disable reception circuitry during a time between receiving all data of the current data burst until a time of the next data burst, which may conserve battery power and/or processing power of UE device. Base stationmay forward the ordinal first PDU to UE device.

456 556 456 456 560 456 458 Base stationmay also receive a subsequent PDU of the PDU Set of the current data burst (). Per techniques of this disclosure, the subsequent PDU may include an update to the predicted BSSize value, e.g., in an RTP extension header, QUIC extension header, tunnel header, or the like. The update may indicate a difference (delta) to be applied to the predicted BSSize value, a replacement BSSize value, or the like. Thus, base stationmay determine the actual BSSize value for the current data burst using the update data. Base stationmay then update the predicted BSSize value to the actual BSSize value for the current data burst (). Base stationmay also forward the subsequent PDU to UE device.

456 562 456 456 458 458 458 Base stationmay then reallocate resources based on the actual BSSize value (). For example, base stationmay perform frequency domain and/or temporal domain resource assignments, determine a modulation scheme, determine a coding scheme, allocate slots/symbols, allocate resource blocks/resource block groups, configure subcarrier spacing, and/or configure bandwidth parts (BWPs) to receive PDUs of the PDU Set of the current data burst based on the predicted BSSize value. Additionally or alternatively, base stationmay reconfigure UE deviceusing the predicted BSSize value, e.g., to disable reception circuitry during a time between receiving all data of the current data burst (based on the updated, actual BSSize value) until a time of the next data burst, which may conserve battery power and/or processing power of UE device, while also allowing UE deviceto receive all data of the current data burst.

456 564 458 Base stationmay then receive remaining PDUs of the current data burst using the reallocated resources () and send the remaining PDUs to UE device.

12 FIG. In this manner, the method ofrepresents an example of a method of communicating data via a network, including: receiving a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst; receiving a second PDU of the data burst after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst; updating the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and using the actual BSSize value to receive one or more subsequent PDUs of the data burst.

Various examples of the techniques of this disclosure are summarized in the clauses below:

Clause 1: A method of communicating media data, the method comprising communicating a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value and data representing whether the TNDB value is relative to an ordinal first protocol data unit (PDU) of a current data burst or to an ordinal last PDU of the current data burst.

Clause 2: The method of clause 1, wherein the RTP header extension comprises an RTP header extension for PDU Set marking.

Clause 3: The method of clause 2, wherein the RTP header extension for PDU Set marking has a one-byte format.

Clause 4: The method of clause 2, wherein the RTP header extension for PDU Set marking has a two-byte format.

Clause 5: The method of any of clauses 2-4, wherein the RTP header extension for PDU Set marking includes a two-bit value comprising the data representing whether the TNDB value is relative to the ordinal first PDU of the current data burst or to the ordinal last PDU of the current data burst.

Clause 6: The method of clause 5, wherein the two-bit value comprises a value of 10 to indicate that the TNDB value is relative to the ordinal first PDU of the current data burst or a value of 01 to indicate that the TNDB value is relative to the ordinal last PDU of the current data burst.

Clause 7: The method of clause 1, wherein the RTP header extension comprises an RTP header extension for data burst traffic characteristics.

Clause 8: The method of clause 7, wherein the RTP header extension for data burst traffic characteristics has a one-byte format.

Clause 9: The method of clause 7, wherein the RTP header extension for data burst traffic characteristics has a two-byte format.

Clause 10: The method of any of clauses 7-9, wherein the RTP header extension for data burst traffic characteristics includes a one-bit value comprising the data representing whether the TNDB value is relative to the ordinal first PDU of the current data burst or to the ordinal last PDU of the current data burst.

Clause 11: The method of clause 10, wherein the one-bit value comprises a value of 1 to indicate that the TNDB value is relative to the ordinal first PDU of the current data burst or a value of 0 to indicate that the TNDB value is relative to the ordinal last PDU of the current data burst.

Clause 12: The method of any of clauses 1-11, further comprising communicating data representing accuracy of the TNDB value.

Clause 13: The method of clause 12, wherein the data representing the accuracy of the TNDB value includes an integer component and a fractional component.

Clause 14: The method of any of clauses 12 and 13, wherein the data representing the accuracy of the TNDB value represents one of a jitter, a standard deviation, or a confidence interval.

Clause 15: The method of any of clauses 12-14, wherein the data representing the accuracy of the TNDB value comprises a value of y indicating +/−y units of time, such that the TNDB value of x with accuracy y indicates that the TNDB is in the range [x−y, x+y].

Clause 16: The method of any of clauses 12-15, wherein communicating the data representing the accuracy of the TNDB value comprises communicating the data representing the accuracy of the TNDB value in an RTP header extension.

Clause 17: The method of clause 16, wherein the RTP header extension comprises an RTP header extension for PDU Set marking.

Clause 18: The method of clause 16, wherein the RTP header extension comprises an RTP header extension for data burst traffic characteristics.

Clause 19: The method of any of clauses 1-18, further comprising communicating data representing an accuracy of a size of the next data burst (SNDB) value.

Clause 20: The method of clause 19, wherein the data representing the accuracy of the SNDB value represents one of a jitter, a standard deviation, or a confidence interval.

Clause 21: The method of any of clauses 19 and 20, wherein the data representing the accuracy of the SNDB value x represents an absolute error value y, such that the SNDB is in the range [x−y, x+y].

Clause 22: The method of any of clauses 19 and 20, wherein the data representing the accuracy of the SNDB value x represents a relative error value a, such that the SNDB is in the range [x(1−a), x(1+a)].

Clause 23: The method of any of clauses 19-22, wherein communicating the data representing the accuracy of the SNDB value comprises communicating the data representing the accuracy of the TNDB value in an RTP header extension.

Clause 24: The method of clause 23, wherein the RTP header extension comprises an RTP header extension for PDU Set marking.

Clause 25: The method of clause 23, wherein the RTP header extension comprises an RTP header extension for data burst traffic characteristics.

Clause 26: The method of any of clauses 1-25, wherein the TNDB value comprises a burst size update for the current data burst.

Clause 27: The method of clause 26, wherein communicating the RTP header extension comprises communicating a PDU of the current data burst including the RTP header extension after having communicated an ordinal first PDU of the current data burst including an RTP header extension including a first TNDB value for the current data burst.

Clause 28: The method of any of clauses 26 and 27, wherein the burst size update represents a remaining amount of data for the current data burst.

Clause 29: The method of any of clauses 26 and 27, wherein the burst size update represents a total amount of data for the current data burst including data for one or more previous PDUs of the current data burst.

Clause 30: The method of any of clauses 26-29, wherein the RTP header extension further includes data indicating that the TNDB value represents an update to a previously communicated TNDB value for the current data burst.

Clause 31: The method of any of clauses 26-30, further comprising communicating negotiation data representing support for burst size updates for data bursts during session establishment for a communication session.

Clause 32: The method of clause 31, wherein communicating the negotiation data comprises communicating session description protocol (SDP) data.

Clause 33: The method of clause 32, wherein the SDP data conforms to an augmented Backus-Naur format of: extensionname=“urn:3gpp:sa4:5grtp:dynamic-traffic-characteristics-rel19”; extensionattributes=[format SP][BSSize-update].

Clause 34: The method of clause 31, wherein communicating the negotiation data comprises communicating a transport parameter representing a unilateral declaration of support for burst size updates.

Clause 35: The method of any of clauses 1-34, wherein communicating comprises sending.

Clause 36: The method of any of clauses 1-34, wherein communicating comprises receiving.

Clause 37: The method of clause 36, wherein receiving comprises receiving by a base station, the method further comprising allocating resources based on the TNDB value.

Clause 38: A method of communicating media data, the method comprising: sending an ordinal first protocol data unit (PDU) of a current data burst of a media communication session, the ordinal first PDU including data representing a burst size for the current data burst; and after sending the ordinal first PDU of the current data burst, sending a second PDU of the current data burst, the second PDU including data representing a burst size update for the current data burst.

Clause 39: A method of communicating media data, the method comprising: receiving an ordinal first protocol data unit (PDU) of a current data burst of a media communication session, the ordinal first PDU including data representing a burst size for the current data burst; allocating resources for receiving remaining PDUs of the current data burst according to the burst size; after receiving the ordinal first PDU of the current data burst, receiving a second PDU of the current data burst, the second PDU including data representing a burst size update for the current data burst; and reallocating resources for receiving the remaining PDUs of the current data burst according to the burst size update.

Clause 40: The method of any of clauses 38 and 39, wherein the data representing the burst size update is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

Clause 41: The method of clause 40, further comprising communicating negotiation data representing support for burst size updates for data bursts during session establishment for a communication session.

Clause 42: The method of clause 41, wherein communicating the negotiation data comprises communicating session description protocol (SDP) data.

Clause 43: The method of clause 42, wherein the SDP data conforms to an augmented Backus-Naur format of: extensionname=“urn:3gpp:sa4:5grtp:dynamic-traffic-characteristics-rel19”; extensionattributes=[format SP][BSSize-update].

Clause 44: The method of any of clauses 38 and 39, wherein the data representing the burst size update is included in a QUIC header encapsulating the second PDU.

Clause 45: The method of clause 44, further comprising communicating negotiation data representing support for burst size updates for data bursts during session establishment for a communication session.

Clause 46: The method of clause 45, wherein communicating the negotiation data comprises communicating the negotiation data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

Clause 47: The method of any of clauses 45 and 46, wherein the negotiation data comprises a transport parameter indicating support for data burst size updates for data bursts.

Clause 48: A device for retrieving media data, the device comprising one or more means for performing the method of any of clauses 1-47.

Clause 49: The device of clause 48, wherein the one or more means comprise a memory and a processing system implemented in circuitry.

Clause 50: The device of clause 48, wherein the device comprises at least one of: an integrated circuit; a microprocessor; or a wireless communication device.

Clause 51: A device for communicating media data, the device comprising means for communicating a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value and data representing whether the TNDB value is relative to an ordinal first protocol data unit (PDU) of a current data burst or to an ordinal last PDU of the current data burst.

Clause 52: A device for communicating media data, the device comprising: means for sending an ordinal first protocol data unit (PDU) of a current data burst of a media communication session, the ordinal first PDU including data representing a burst size for the current data burst; and means for sending, after sending the ordinal first PDU of the current data burst, a second PDU of the current data burst, the second PDU including data representing a burst size update for the current data burst.

Clause 53: A device for communicating media data, the device comprising: means for receiving an ordinal first protocol data unit (PDU) of a current data burst of a media communication session, the ordinal first PDU including data representing a burst size for the current data burst; means for allocating resources for receiving remaining PDUs of the current data burst according to the burst size; means for receiving, after receiving the ordinal first PDU of the current data burst, a second PDU of the current data burst, the second PDU including data representing a burst size update for the current data burst; and means for reallocating resources for receiving the remaining PDUs of the current data burst according to the burst size update.

Clause 54: The device of clause 53, wherein the device comprises a base station of a radio access network (RAN).

Clause 55: A method of communicating data via a network, the method comprising: receiving a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst; receiving a second PDU after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst; updating the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and using the actual BSSize value to receive one or more subsequent PDUs of the data burst.

Clause 56: The method of clause 55, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

Clause 57: The method of clause 56, further comprising sending data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 58: The method of clause 57, wherein sending the data representing the support for burst size updates comprises sending session description protocol (SDP) data.

Clause 59: The method of clause 58, wherein the SDP data conforms to an augmented Backus-Naur format of: extensionname=“urn:3gpp:sa4:5grtp:dynamic-traffic-characteristics-rel19”; extensionattributes=[format SP][BSSize-update].

Clause 60: The method of clause 55, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

Clause 61: The method of clause 60, further comprising sending data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 62: The method of clause 61, wherein sending the data representing the support for burst size updates comprises sending the data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

Clause 63: The method of clause 61, wherein sending the data representing the support for burst size updates comprises sending a transport parameter indicating the support for data burst size updates for the data bursts of the communication session.

Clause 64: The method of clause 55, wherein using the actual BSSize value to receive the one or more subsequent PDUs of the data burst comprises: in response to the predicted BSSize value, performing a first resource allocation based on the predicted BSSize value to allocate first resources to receive data having a first size corresponding to the predicted BSSize value; and in response to updating the predicted BSSize value to the actual BSSize value, performing a second resource allocation based on the actual BSSize value to allocate second resources to receive data having a second size corresponding to the actual BSSize value.

Clause 65: The method of clause 55, wherein using the actual BSSize value to receive the one or more subsequent PDUs of the data burst comprises: in response to the predicted BSSize value, scheduling reception circuitry to stop receiving data after having received a first amount of data corresponding to the predicted BSSize value; and in response to the actual BSSize value, rescheduling the reception circuitry to stop receiving data after having received a second amount of data corresponding to the actual BSSize value.

Clause 66: The method of clause 55, wherein the data for updating the predicted BSSize value comprises a size of remaining PDUs of the data burst, and wherein updating the predicted BSSize value comprises adding the size of the remaining PDUs to the predicted BSSize value to form the actual BSSize value.

Clause 67: The method of clause 55, wherein the data for updating the predicted BSSize value comprises a size of all PDUs of the data burst, and wherein updating the predicted BSSize value comprises replacing the predicted BSSize value with the size of all PDUs of the data burst to form the actual BSSize value.

Clause 68: The method of clause 55, further comprising receiving a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value relative to an ordinal last PDU of the data burst.

Clause 69: The method of clause 68, wherein the RTP header extension comprises an RTP header extension for PDU Set marking.

Clause 70: The method of clause 69, wherein the RTP header extension for PDU Set marking has a one-byte format.

Clause 71: The method of clause 69, wherein the RTP header extension for PDU Set marking has a two-byte format.

Clause 72: The method of any of clauses 69-71, wherein the RTP header extension for PDU Set marking includes a two-bit value comprising the data representing whether the TNDB value is relative to the ordinal first PDU of the current data burst or to the ordinal last PDU of the current data burst.

Clause 73: The method of clause 72, wherein the two-bit value comprises a value of 10 to indicate that the TNDB value is relative to the ordinal first PDU of the current data burst or a value of 01 to indicate that the TNDB value is relative to the ordinal last PDU of the current data burst.

Clause 74: The method of clause 68, wherein the RTP header extension comprises an RTP header extension for data burst traffic characteristics.

Clause 75: The method of clause 74, wherein the RTP header extension for data burst traffic characteristics has a one-byte format.

Clause 76: The method of clause 74, wherein the RTP header extension for data burst traffic characteristics has a two-byte format.

Clause 77: The method of any of clauses 74-76, wherein the RTP header extension for data burst traffic characteristics includes a one-bit value comprising the data representing whether the TNDB value is relative to the ordinal first PDU of the current data burst or to the ordinal last PDU of the current data burst.

Clause 78: The method of clause 77, wherein the one-bit value comprises a value of 1 to indicate that the TNDB value is relative to the ordinal first PDU of the current data burst or a value of 0 to indicate that the TNDB value is relative to the ordinal last PDU of the current data burst.

Clause 79: The method of any of clauses 1-78, further comprising communicating data representing accuracy of the TNDB value.

Clause 80: The method of clause 79, wherein the data representing the accuracy of the TNDB value includes an integer component and a fractional component.

Clause 81: The method of any of clauses 79 and 80, wherein the data representing the accuracy of the TNDB value represents one of a jitter, a standard deviation, or a confidence interval.

Clause 82: The method of any of clauses 79-81, wherein the data representing the accuracy of the TNDB value comprises a value of y indicating +/−y units of time, such that the TNDB value of x with accuracy y indicates that the TNDB is in the range [x−y, x+y].

Clause 83: The method of any of clauses 79-82, wherein communicating the data representing the accuracy of the TNDB value comprises communicating the data representing the accuracy of the TNDB value in an RTP header extension.

Clause 84: The method of clause 83, wherein the RTP header extension comprises an RTP header extension for PDU Set marking.

Clause 85: The method of clause 83, wherein the RTP header extension comprises an RTP header extension for data burst traffic characteristics.

Clause 86: The method of any of clauses 1-85, further comprising communicating data representing an accuracy of a size of the next data burst (SNDB) value.

Clause 87: The method of clause 86, wherein the data representing the accuracy of the SNDB value represents one of a jitter, a standard deviation, or a confidence interval.

Clause 88: The method of any of clauses 86 and 87, wherein the data representing the accuracy of the SNDB value x represents an absolute error value y, such that the SNDB is in the range [x−y, x+y].

Clause 89: The method of any of clauses 86 and 87, wherein the data representing the accuracy of the SNDB value x represents a relative error value a, such that the SNDB is in the range [x(1−a), x(1+a)].

Clause 90: The method of any of clauses 86-89, wherein communicating the data representing the accuracy of the SNDB value comprises communicating the data representing the accuracy of the TNDB value in an RTP header extension.

Clause 91: The method of clause 90, wherein the RTP header extension comprises an RTP header extension for PDU Set marking.

Clause 92: The method of clause 90, wherein the RTP header extension comprises an RTP header extension for data burst traffic characteristics.

Clause 93: A device for communicating data via a network, the device comprising: a memory configured to store data; and a processing system implemented in circuitry and configured to: receive a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst; receive a second PDU after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst; update the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and use the actual BSSize value to receive one or more subsequent PDUs of the data burst.

Clause 94: The device of clause 93, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

Clause 95: The device of clause 94, wherein the processing system is further configured to send data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 96: The device of clause 95, wherein to send the data representing the support for burst size updates, the processing system is configured to send session description protocol (SDP) data.

Clause 97: The method of clause 96, wherein the SDP data conforms to an augmented Backus-Naur format of: extensionname=“urn:3gpp:sa4:5grtp:dynamic-traffic-characteristics-rel19”; extensionattributes=[format SP][BSSize-update].

Clause 98: The device of clause 93, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

Clause 99: The device of clause 98, wherein the processing system is further configured to send data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 100: The device of clause 99, wherein to send the data representing the support for burst size updates, the processing system is configured to send the data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

Clause 101: The device of clause 99, wherein to send the data representing the support for burst size updates, the processing system is configured to send a transport parameter indicating the support for data burst size updates for the data bursts of the communication session.

Clause 102: The device of clause 93, wherein to use the actual BSSize value to receive the one or more subsequent PDUs of the data burst, the processing system is configured to: in response to the predicted BSSize value, perform a first resource allocation based on the predicted BSSize value to allocate first resources to receive data having a first size corresponding to the predicted BSSize value; and in response to updating the predicted BSSize value to the actual BSSize value, perform a second resource allocation based on the actual BSSize value to allocate second resources to receive data having a second size corresponding to the actual BSSize value.

Clause 103: The device of clause 93, wherein to use the actual BSSize value to receive the one or more subsequent PDUs of the data burst, the processing system is configured to: in response to the predicted BSSize value, schedule reception circuitry to stop receiving data after having received a first amount of data corresponding to the predicted BSSize value; and in response to the actual BSSize value, reschedule the reception circuitry to stop receiving data after having received a second amount of data corresponding to the actual BSSize value.

Clause 104: The device of clause 93, wherein the data for updating the predicted BSSize value comprises a size of remaining PDUs of the data burst, and wherein to update the predicted BSSize value, the processing system is configured to add the size of the remaining PDUs to the predicted BSSize value to form the actual BSSize value.

Clause 105: The device of clause 93, wherein the data for updating the predicted BSSize value comprises a size of all PDUs of the data burst, and wherein to update the predicted BSSize value, the processing system is configured to replace the predicted BSSize value with the size of all PDUs of the data burst to form the actual BSSize value.

Clause 106: The device of clause 93, wherein the processing system is further configured to receive a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value relative to an ordinal last PDU of the data burst.

Clause 107: A method of communicating data via a network, the method comprising: predicting a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs); sending a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed; after forming one or more additional PDUs of the plurality of PDUs, determining an actual BSSize value for the data burst; and sending a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.

Clause 108: The method of clause 107, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

Clause 109: The method of clause 108, further comprising receiving data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 110: The method of clause 109, wherein receiving the data representing the support for burst size updates comprises receiving session description protocol (SDP) data.

Clause 111: The method of clause 110, wherein the SDP data conforms to an augmented Backus-Naur format of: extensionname=“urn:3gpp:sa4:5grtp:dynamic-traffic-characteristics-rel19”; extensionattributes=[format SP][BSSize-update].

Clause 112: The method of clause 107, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

Clause 113: The method of clause 112, further comprising receiving data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 114: The method of clause 113, wherein receiving the data representing the support for burst size updates comprises receiving the data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

Clause 115: The method of clause 113, wherein receiving the data representing the support for burst size updates comprises receiving a transport parameter indicating the support for data burst size updates for the data bursts of the communication session.

Clause 116: The method of clause 107, wherein the data for updating the predicted BSSize value comprises a size of remaining PDUs of the data burst.

Clause 117: The method of clause 107, wherein the data for updating the predicted BSSize value comprises a size of all PDUs of the data burst.

Clause 118: The method of clause 107, further comprising sending a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value relative to the ordinal last PDU of the data burst.

Clause 119: A device for communicating data via a network, the device comprising: a memory configured to store data; and a processing system implemented in circuitry and configured to: predict a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs); send a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed; after forming one or more additional PDUs of the plurality of PDUs, determine an actual BSSize value for the data burst; and send a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.

Clause 120: The device of clause 119, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

Clause 121: The device of clause 120, wherein the processing system is further configured to receive data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 122: The device of clause 121, wherein to receive the data representing the support for burst size updates, the processing system is configured to receive session description protocol (SDP) data.

Clause 123: The device of clause 122, wherein the SDP data conforms to an augmented Backus-Naur format of: extensionname=“urn:3gpp:sa4:5grtp:dynamic-traffic-characteristics-rel19”; extensionattributes=[format SP][BSSize-update].

Clause 124: The device of clause 119, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

Clause 125: The device of clause 124, wherein the processing system is further configured to receive data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

Clause 126: The device of clause 125, wherein to receive the data representing the support for burst size updates, the processing system is configured to receive the data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

Clause 127: The device of clause 125, wherein to receive the data representing the support for burst size updates, the processing system is configured to receive a transport parameter indicating the support for data burst size updates for the data bursts of the communication session.

Clause 128: The device of clause 119, wherein the data for updating the predicted BSSize value comprises a size of remaining PDUs of the data burst.

Clause 129: The device of clause 119, wherein the data for updating the predicted BSSize value comprises a size of all PDUs of the data burst.

Clause 130: The device of clause 119, wherein the processing system is further configured to send a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value relative to the ordinal last PDU of the data burst.

In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the 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.

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.

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 implementation 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.

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.

Various examples have been described. These and other examples are within the scope of the following claims.